From owner-freebsd-current@freebsd.org Sun Oct 21 05:26:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39D5BFCEA1A for ; Sun, 21 Oct 2018 05:26:07 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABA917C3E6 for ; Sun, 21 Oct 2018 05:26:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ot1-x32e.google.com with SMTP id x4so35555455otg.3 for ; Sat, 20 Oct 2018 22:26:06 -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=xel93zY/hksjuHQWfar85z2RX0efluMAgb0cI0jusmU=; b=gWhGK4hupBsEt7bcr/ZAGxBu+Icj0fh3fMG/qrAvBif6JMQ5iFhbHgRq88RS5I9QFz 8pSuknjqAfRyV2Vg9fBh6jNKwuGGzmSUKFIOwAAEfKszP2pEwA3Al+UtUjyxqG3ulNpI TaIpJxOnhS3/OBHCGtT4PqHozdPfsjqHCO0x4qCZYXK9eC591HE5JHEbX1GdpcLEhyH8 t0gp3uCN4yV7U9XsRVBK/Uc6/FD3LT2a7WaPe8j7XrYr5LnrzAk/qPEUKYIJEAUnEm9a oMa1ONzz58q7JWDZmSTQq7bYQDbbmQUkWCqbWQgO5ZMEcu0NpwqClTHaqxa0JrtcyxBi X20A== 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=xel93zY/hksjuHQWfar85z2RX0efluMAgb0cI0jusmU=; b=YmcOPUFo7NjQzsdMQUteCtc6QbcJ3I0P0Tv5VeFgpvj20TJrIFAKGUquBKTO6MA2LP fyIi1KFwfzZAf6S7QJoNRDskH10ma4at1zhC/NqLXPxjDXi0PpbOPplQSfSSwwGw5Wuu MSur4u61Ju4pmwrcgNSSH7q/9NDkTFSq/SbWj7DqB1foForqEGM4tzeHMqjuZD70kRgY GLbxk1WE+cMRXmm8Cwx6IkFej6lZkXOXKeJOnKAuJB/zDVDpERWabpSS8SLN/UtjRPCQ S5DNobVhVeKTnCNo9VgRSnvMaENnIVsvDUBsD3iNRvRihYu4Bq/CXqLI2YvetrpV/FF0 /pFg== X-Gm-Message-State: ABuFfogG4HoDZVai7y74ARynVPVoG0C4+vcVrQMLQu835SpIXETFagly E9G6MgWwVMTZijZ5kwXJYl4JJGD3/iZKxqyiFLHooiOv X-Google-Smtp-Source: ACcGV635U+xmCglf9uaBqMvGg4Ii+O1cypXbTvk4V4A4oZGHpfZM1mKMvmDXplhg8oLKtbRdYRuLaaIwgsj/XcFqv+g= X-Received: by 2002:a9d:2b33:: with SMTP id o48mr28069456otb.315.1540099565743; Sat, 20 Oct 2018 22:26:05 -0700 (PDT) MIME-Version: 1.0 References: <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com> In-Reply-To: From: Kevin Oberman Date: Sat, 20 Oct 2018 22:25:48 -0700 Message-ID: Subject: =?UTF-8?B?UmU6IERSTTogcmFkZW9ua21zIOKApiBjYW4gbm90IGJlIHVubG9hZGVkIChrZXJuZWwgcA==?= =?UTF-8?B?YW5pYykpIOKApg==?= To: Hans Petter Selasky Cc: Graham Perrin , FreeBSD Current 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: Sun, 21 Oct 2018 05:26:07 -0000 On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky wrote= : > On 10/20/18 3:10 AM, Graham Perrin wrote: > > On 20/10/2018 00:01, Graham Perrin wrote: > > > >> kldunload radeonkms > >> > >> =E2=80=93 results in a kernel panic. > > > > Found, at < > https://github.com/FreeBSDDesktop/kms-drm/issues/90#issuecomment-41585902= 1> > under 'drm-devel-kmod g20180822 screen freeze': > > > >>> =E2=80=A6 normally you never unload the graphics driver so we haven't= spent > time on proper cleanup. Also, the drm module will cause panic if you try > load load it again after unload. > > > > ---- > > > > Is the principle for -next- the same as for -devel-, should I simply > _never_ attempt to unload the module? > > > > $ date ; uname -v > > Sat 20 Oct 2018 02:06:21 BST > > FreeBSD 12.0-BETA1 r339438 GENERIC > > $ pkg query '%o %v %R' drm-kmod drm-next-kmod gpu-firmware-kmod > > graphics/drm-next-kmod 4.11.g20180822 poudriere > > graphics/gpu-firmware-kmod g20180825 FreeBSD > > I recommend building these modules from source, /usr/src which match you > currently installed kernel! > > --HPS > This is a really good practice for all kernel modules from ports. If you build your kernel from source, put them into /etc/rc.conf to define PORTS_MODULES to always rebuild all modules when the kernel is built. Even if you install packages for your release, you need to realize that packages are built against the oldest supported minor release of a major release and that works or all ports that only have to match system ABIs which remain stable for the life of a major release. But, while the KBI (Kernel Binary Interface) usually remains stable, it occasionally does and did between 11.1 and 11.2 which meant that two ports failed when installed from packages on 11.2 system until 11.1 went EOL this month. I really wish that the portsmgr team would come up with a policy to maintain an archive of port based kernel modules whenever there is a minor release where people who have broken systems can get trusted packages. Some people are really not very capable of building from ports. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-current@freebsd.org Sun Oct 21 05:04:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3B42FCE023 for ; Sun, 21 Oct 2018 05:04:44 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-10.consmr.mail.gq1.yahoo.com (sonic315-10.consmr.mail.gq1.yahoo.com [98.137.65.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A37C7BA36 for ; Sun, 21 Oct 2018 05:04:44 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: P3yGGcwVM1l_HSjX0D8ng5EdbqnEz9XguxC1nynD_9j3v9gc2PTuf.wR4vRq0Vl bRR5ZCC4_.q0cM5r_OaAP0VJgCcbXDk_gn.EAbayITR1Ze6YpanFVPkLIKRcCE4ThtUseVR2f34t 8HwLhF8zIICTYDfBiFnYbyZvFfE66VmQ9bZR.PJllavbBr8wF3NGUfIDmZt2X2fRELWfEL3xkkd9 AxFg6IRyyV81GjQhBV_y9nfAPgmcGGRFDfUarHWz4zueyVqDrC2zvAahWggwAEz_qYMazyaZK.KV sMRHjXa7Y16CeJWMw.X5CEBceWCQpH1KVQbTTAxLnlpqHl.m_.w_kDo.AalUgiY7O5kXFkuxeqNC Ca2kPRsNWVmUCOPjkbtJrZr7xYNpKzudiyD__0XhwnAzYvsF3q7H4_cDVlp.h6P67Eeb0yADod_Y R2b1GxIwjlWwCt1ser2QVNjHKmC7neA5MbrbMSa0ap2NeEnxawauyfBlsGtnsrBVBBkSyQKtO4ti fL4yqYZnPd9.f1kYNPxhEpPZ_VTwLnT3b5z1MDe8GVrph8bdq37k.JeBlDp2yWyIAFX61tGs8aoe IAovRvkQT9u.IcejPMIc683biLCjCafItptQ3ILO2c0.sw4M3ozYP3k1U2tQDHVVRQ67BZVlUtxN 8asdBujo.VVzXfOd2j1lUNXU_Yy1cgnbs3nYKiVyQkUHOgoDt2UkbKDDXyYoFhlIhaqGhGcjndXh BZpO31YeLSih8.tftX.rboEy_5nCreCkFlUzrsNIHdQh4bm0EFmgtyswtmAfvnMJ8wnNaXDp5JBR YptNvDpAmzwPKKAPH4RLtoTe5nZ.LxAo0PB_PicBc8u6.xEIP9IWN_mb.pxiRRrLGyQR_pzoRXG8 0d..cs8ZaKW2TV7RSsMuoj3ASnXBv6DfVtIwkGNAzYQiRSYpGJq90SK5yYDun4EJrmssr6uIYcum ZeAhfKtPfdkTC0rwZEFEU.UDOeBW9dQsC5vcPCGIkIwXXsGWzpxrMTDnwOhh5NB72yutP6ykaDJl EqEaym1GH5U.9AZMjdOa5fDQM1v6pxwWQhIKCVaj44vPYHBMj4nt6JaTjwjD8VmCrujO_piE1gU. 5YkxB_Z0. Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Sun, 21 Oct 2018 05:04:42 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp428.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 5bc75eeb86c3ebe70c4e718968e9b5b0; Sun, 21 Oct 2018 05:04:37 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ -r336532 broke it ] Date: Sat, 20 Oct 2018 22:04:36 -0700 References: <2A425DE4-2B5B-474D-8B95-81890DE4D8A1@yahoo.com> To: Warner Losh , FreeBSD Current , freebsd-stable@freebsd.org In-Reply-To: <2A425DE4-2B5B-474D-8B95-81890DE4D8A1@yahoo.com> Message-Id: <9D2A6528-F888-4833-A52B-8F9B4D66592C@yahoo.com> X-Mailer: Apple Mail (2.3445.9.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, 21 Oct 2018 05:04:45 -0000 [I found what change lead to the 1950X boot crashing with BTX halted.] On 2018-Oct-20, at 12:44 PM, Mark Millard wrote: > [Adding some vintage information for a loader > that allowed a native boot.] > > On 2018-Oct-20, at 4:00 AM, Mark Millard wrote: > >> I attempted to jump from head -r334014 to -r339076 >> on a threadripper 1950X board and the native >> FreeBSD boot failed very early. (Hyper-V use of >> the same media did not have this issue.) >> >> But copying over an older /boot/loader from another >> storage device with a FreeBSD head version that has >> not been updated yet got past the problem being >> reported here. (For other reasons, the kernel has >> been moved back to -r338804 --and with that, >> and the older /boot/loader, the 1950X native-boots >> FreeBSD all the way just fine.) > > I found one /boot/loader.old that was dated > in the update'd file system as 2018-May 20, > instead of 2018-Apr-03 from the older file > system. May 20 would apparently mean a little > below -r334014 . It native-booted okay, as did > the April one. > > [I do not know how to inspect a /boot/loader* > to find out what -r?????? it is from.] > > Unfortunately, I had done more than one -r339076 > install from -r334014 before rebooting and > no -r334014 loaders were still present: > the other *.old files from a few minutes before > the ones I had the boot problem with. > > I might be able to extract loaders from various: > > https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz > > materials and try substituting them in order to > narrow the range for works -> fails. If I can, > this likely would take a fair amount of time in > my context. > > Other notes: > > It turns out that only Hyper-V based use needed > a -r334804 kernel: Native booting with the older > loaders and newer kernels works fine. > > Windows 10 Pro 64bit also has no problems > booting and operating the machine. > > The native-boot problem does seem to be freeBSD > loader-vintage specific. > >> For the BTX failure the display ends up with >> (hand transcribed, ". . ." for an omission): >> >> BTX loader 1.00 BTX version is 1.02 >> Console: internal video/keyboard >> BIOS drive C: is disk0 >> . . . >> BIOS drive P: is disk13 >> - >> int=00000000 err=00000000 efl=00010246 eip=000096fd >> eax=74d48000 ebx=74d4e5e0 ecx=00000011 edx=00000000 >> esi=74d4e380 edi=74d4e5b0 ebp=00091da0 esp=00091d60 >> cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 >> cs:eip=66 f7 77 04 0f b7 c0 89-44 24 0c 89 5c 24 04 8b >> 45 08 89 04 24 83 64 24-10 00 c7 44 24 08 01 00 >> ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >> 00 00 00 00 00 00 00 00-f0 1d 89 00 00 00 00 00 >> BTX halted > > I've no clue what of that output might be loader vintage > specific. It might not be of use without knowing the > exact build of the loader. > >> The board is a GIGABYTE X399 AORUS Gaming 7 (rev 1.0). >> It has 96 GiBytes of ECC RAM, just 6 DIMMs installed. > > For reference for the board's BIOS: > > Version: F11e > Dated: 2018-Sep-17 > Description: Update AGESA 1.1.0.1a Using: https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz materials I found that: -r336492: worked (loader vs. zfsloader: not linked) (no more amd64 builds until . . .) -r336538: failed (loader vs. zfsloader: linked) (Later ones that I tried also failed.) Looks like this broke for booting the 1950X system in question when the following was checked in: Author: imp Date: Fri Jul 20 05:17:37 2018 New Revision: 336532 URL: https://svnweb.freebsd.org/changeset/base/336532 Log: Collapse zfsloader functionality back down into loader. . . . === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Oct 21 07:05:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5317AFD84FC for ; Sun, 21 Oct 2018 07:05:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-20.consmr.mail.ne1.yahoo.com (sonic306-20.consmr.mail.ne1.yahoo.com [66.163.189.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C232A7F4A4 for ; Sun, 21 Oct 2018 07:05:20 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: jWLG8HUVM1mwQQiCD1mwtXnbbtWv3JyPmvtM4mz9EQArlDvI4hOgczShz6a4n82 w6eGFdBoAznpMLcr34LE7cguXiHSo2Zubl9ymvEKSvXpAa9L5rvDSnimCsQo9oOAEbBPY63XQsJA tePee0rUzWPgwKY1_g7a7cK863Tx58y0VKJocceKfoZb8FZgyAujhzn1IATLbes80DgmcAyanTmw YsdUHXegsz_sBYE1bwW6p4MRiMq4Uavi.Elak03MfAMCPjRQiOseNY2Wc75iF54jeZV4Py0RXX4l oAjJo_bQGNy62jPxFGGoloE8PS1TM4DFqaF3FlR03iH4GaQkMJ75KHKVuCk_w7uu6f8k1b_nts1I 9kCRkFJi_kdZ.MfWbE9tcDQ63YLItz2lppadi.SnzBdFQV_vF_VR.DCUmPq2xEF.p5TC09HAqR2B A4yI.smMieV5dph9MgSvWJvLZm7d38aGb32NFtt1ejdO67C.t0kH0NU7luTx0J68WFz8fiNFolhN T9nfw756NN7cUC_KmHkGy3JzRy.U3lxyJbPiGdvcbZJ402m3E6m8UykI4up0cnWdFUlWN6EDlW7B YrGMpoSqGWJ6E2KlSp4nKIc_YXG.r8ZqR_yzNjFQsCKbYp8U4qQMTS4IilEp8WHPCg8S1zw0j3FF S1lgwz08AvOsQjQtZAo4yRW5MStWNqII0OtTJr3QltgzuKjGVTdgyG1bey4PR.TFSUolzVdRZn_c dujppwm3roKKRP1YlWU8faMNazV6c84ks2IcObd6v_XqsuWLMXII8Be0Kk4yQ9njdc_ZguJrXsNi _R5usNQkAvmDOs.gegkeMLTPL_0LEE4Wo3zdqMQQ2jePWRPJX3Lq3oUmlSLrmMKyBACeKucIwy1H 0uoO8rDo_dp96wCjv7gwNfrkC7mPZmxRE2MwqqkeG9.c64V3go7DNP1n9LQ8h99XIJCvZIzfNEns fVCah4kHJVMrZquLkMD5bFeuE6RGFT4FIdev.fm57O1V9_mwvJu_xj_SatbSsBmb3wL4OumXEBNQ 2bilcPQcTY4orQ4JjPyeLpxs0W164Ct5a9Xjtn9uuIo2np.Dz0orYsp2eXo_9zXGGhNdecwkkSrS p1LgkGEcSGor3 Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ne1.yahoo.com with HTTP; Sun, 21 Oct 2018 07:05:13 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp430.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e89355a7d2acd1525effad1bfa37ced7; Sun, 21 Oct 2018 07:05:09 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ -r336532 broke it ] From: Mark Millard In-Reply-To: Date: Sun, 21 Oct 2018 00:05:07 -0700 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <30DD2F47-C8CB-4CEC-8563-C7083D0EAEEF@yahoo.com> References: <2A425DE4-2B5B-474D-8B95-81890DE4D8A1@yahoo.com> <9D2A6528-F888-4833-A52B-8F9B4D66592C@yahoo.com> To: Warner Losh X-Mailer: Apple Mail (2.3445.9.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, 21 Oct 2018 07:05:21 -0000 On 2018-Oct-20, at 10:32 PM, Warner Losh wrote: > On Sat, Oct 20, 2018 at 11:04 PM Mark Millard = wrote: > [I found what change lead to the 1950X boot crashing > with BTX halted.] >=20 >> On 2018-Oct-20, at 12:44 PM, Mark Millard = wrote: >>=20 >> > [Adding some vintage information for a loader >> > that allowed a native boot.] >> >=20 >> > On 2018-Oct-20, at 4:00 AM, Mark Millard = wrote: >> >=20 >> >> I attempted to jump from head -r334014 to -r339076 >> >> on a threadripper 1950X board and the native >> >> FreeBSD boot failed very early. (Hyper-V use of >> >> the same media did not have this issue.) >> >>=20 >> >> But copying over an older /boot/loader from another >> >> storage device with a FreeBSD head version that has >> >> not been updated yet got past the problem being >> >> reported here. (For other reasons, the kernel has >> >> been moved back to -r338804 --and with that, >> >> and the older /boot/loader, the 1950X native-boots >> >> FreeBSD all the way just fine.) >> >=20 >> > I found one /boot/loader.old that was dated >> > in the update'd file system as 2018-May 20, >> > instead of 2018-Apr-03 from the older file >> > system. May 20 would apparently mean a little >> > below -r334014 . It native-booted okay, as did >> > the April one. >> >=20 >> > [I do not know how to inspect a /boot/loader* >> > to find out what -r?????? it is from.] >> >=20 >> > Unfortunately, I had done more than one -r339076 >> > install from -r334014 before rebooting and >> > no -r334014 loaders were still present: >> > the other *.old files from a few minutes before >> > the ones I had the boot problem with. >> >=20 >> > I might be able to extract loaders from various: >> >=20 >> > = https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz >> >=20 >> > materials and try substituting them in order to >> > narrow the range for works -> fails. If I can, >> > this likely would take a fair amount of time in >> > my context. >> >=20 >> > Other notes: >> >=20 >> > It turns out that only Hyper-V based use needed >> > a -r334804 kernel: Native booting with the older >> > loaders and newer kernels works fine. >> >=20 >> > Windows 10 Pro 64bit also has no problems >> > booting and operating the machine. >> >=20 >> > The native-boot problem does seem to be freeBSD >> > loader-vintage specific. >> >=20 >> >> For the BTX failure the display ends up with >> >> (hand transcribed, ". . ." for an omission): >> >>=20 >> >> BTX loader 1.00 BTX version is 1.02 >> >> Console: internal video/keyboard >> >> BIOS drive C: is disk0 >> >> . . . >> >> BIOS drive P: is disk13 >> >> - >> >> int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000096fd >> >> eax=3D74d48000 ebx=3D74d4e5e0 ecx=3D00000011 edx=3D00000000 >> >> esi=3D74d4e380 edi=3D74d4e5b0 ebp=3D00091da0 esp=3D00091d60 >> >> cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 >> >> cs:eip=3D66 f7 77 04 0f b7 c0 89-44 24 0c 89 5c 24 04 8b >> >> 45 08 89 04 24 83 64 24-10 00 c7 44 24 08 01 00 >> >> ss:esp=3D00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >> >> 00 00 00 00 00 00 00 00-f0 1d 89 00 00 00 00 00 >> >> BTX halted >> >=20 >> > I've no clue what of that output might be loader vintage >> > specific. It might not be of use without knowing the >> > exact build of the loader. >> >=20 >> >> The board is a GIGABYTE X399 AORUS Gaming 7 (rev 1.0). >> >> It has 96 GiBytes of ECC RAM, just 6 DIMMs installed. >> >=20 >> > For reference for the board's BIOS: >> >=20 >> > Version: F11e >> > Dated: 2018-Sep-17 >> > Description: Update AGESA 1.1.0.1a >>=20 >> Using: >>=20 >> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz >>=20 >> materials I found that: >>=20 >> -r336492: worked (loader vs. zfsloader: not linked) >> (no more amd64 builds until . . .) >> -r336538: failed (loader vs. zfsloader: linked) >>=20 >> (Later ones that I tried also failed.) >>=20 >> Looks like this broke for booting the 1950X=20 >> system in question when the following was >> checked in: >>=20 >> Author: imp >> Date: Fri Jul 20 05:17:37 2018 >> New Revision: 336532 >> URL:=20 >> https://svnweb.freebsd.org/changeset/base/336532 >>=20 >>=20 >> Log: >> Collapse zfsloader functionality back down into loader. >>=20 > Yea, this shouldn't matter. It worked on all the systems I tried it = on. >=20 > So my first question: is this a ZFS system? Second, does it also have = UFS? If yes to both, which one do you want it to boot off of? No zfs in use at all. It has been years since I experimented with ZFS and reverted back to UFS. # gpart show -l =3D> 40 937703008 da0 GPT (447G) 40 1024 1 FBSDFSSDboot (512K) 1064 746586112 2 FBSDFSSDroot (356G) 746587176 31457280 3 FBSDFSSDswap (15G) 778044456 159383552 4 FBSDFSSDswap2 (76G) 937428008 275040 - free - (134M) . . . Doing: gpart bootcode -p /boot/gptboot -i 1 da0 and the trying a modern /boot/loader did not change anything: still "BTX halted" for a native boot. (No problem under Hyper-V.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun Oct 21 05:33:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37685FCECA5 for ; Sun, 21 Oct 2018 05:33:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB37C7C66B for ; Sun, 21 Oct 2018 05:33:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2c.google.com with SMTP id y195so11899433vsc.7 for ; Sat, 20 Oct 2018 22:33:06 -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=kUKgelnR/9ZNnTV7CH73US5ATf0tjH9vz/9vHslTP4s=; b=Jub/DD5z1+K3SPrVE/1bisP+B65Kh885EtAXNIoWkpwS5wz74uPTgV1Zp4SndTdl18 Wi9drpon8oYe1nOl5LpwuJglFbviwY3+0/9Ad0QdhyI0duLFIbdLaB8jb09ZM6kyIR2o 4Ir8t29GwspATPzEnGPyCiexEVzlXQs9bTFFdvNIoKv/Y89x9i2fj8B65H685Z8wX+qU PhS/JAieNgFnQa6CCzB+UsYkvZZL5Vge4RWahM/JrTQef0CiQQTHeG/DVtmUj2IBQznA E27DWdGtPaKKbBUpOAsViNy24ysQUrtHwtuLD6xcVKg0RD0QFCGxYHzD+JiTuR18Le1k BhWA== 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=kUKgelnR/9ZNnTV7CH73US5ATf0tjH9vz/9vHslTP4s=; b=hokl2JPfwSb+/ce01lptXGwT+DfCodKtoK0mncjFg2ezMkhpQaT51YXpbJd3YbahUx pGaMvkEzjqMUg8RKtjr6J85NBS0KPdIEft4rxEklou8adky6+nAIa9UbYL8kmhRb67x/ +csJ9LPj9Dr+wmKZCIJnGyJQya7rga4qV/uYAYKjVamaeybipSLUNdLXF1H7o2I41ly6 ZoIByYXtoCOxiqiw+cNgjsdCDtLudhSUvl/Lt2uGhgx4QtaENShWRdTPJ+35dvGsuEYF dzUerTttTk8BKuIauurzMDlD+ie2KE6fAI4OoK0/yEIg+kps0Z0hEAswi1K4GjZKnSdj wZGg== X-Gm-Message-State: ABuFfojBqRBfpOxyyArPiJ/6kXe/t7WlI61ZeNMA7sbdI8Ae7WWx9r7O yJGnLmuRR8CbCH3WKVSgEfl7ecZWj1g2C2BLxXEyuQ== X-Google-Smtp-Source: ACcGV62XNY/usfM1g+WiVbz5G80uCojTDwQsIkfJXzn4hCE7OQUOfHKFZjWZ//boenDL+0OsZ5AKG7lWgBV0cX3RhYo= X-Received: by 2002:a67:e86:: with SMTP id 128mr16550240vso.201.1540099985869; Sat, 20 Oct 2018 22:33:05 -0700 (PDT) MIME-Version: 1.0 References: <2A425DE4-2B5B-474D-8B95-81890DE4D8A1@yahoo.com> <9D2A6528-F888-4833-A52B-8F9B4D66592C@yahoo.com> In-Reply-To: <9D2A6528-F888-4833-A52B-8F9B4D66592C@yahoo.com> From: Warner Losh Date: Sat, 20 Oct 2018 23:32:54 -0600 Message-ID: Subject: Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ -r336532 broke it ] To: Mark Millard Cc: FreeBSD Current , FreeBSD-STABLE Mailing List 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, 21 Oct 2018 05:33:07 -0000 On Sat, Oct 20, 2018 at 11:04 PM Mark Millard wrote: > [I found what change lead to the 1950X boot crashing > with BTX halted.] > > On 2018-Oct-20, at 12:44 PM, Mark Millard wrote: > > > [Adding some vintage information for a loader > > that allowed a native boot.] > > > > On 2018-Oct-20, at 4:00 AM, Mark Millard wrote: > > > >> I attempted to jump from head -r334014 to -r339076 > >> on a threadripper 1950X board and the native > >> FreeBSD boot failed very early. (Hyper-V use of > >> the same media did not have this issue.) > >> > >> But copying over an older /boot/loader from another > >> storage device with a FreeBSD head version that has > >> not been updated yet got past the problem being > >> reported here. (For other reasons, the kernel has > >> been moved back to -r338804 --and with that, > >> and the older /boot/loader, the 1950X native-boots > >> FreeBSD all the way just fine.) > > > > I found one /boot/loader.old that was dated > > in the update'd file system as 2018-May 20, > > instead of 2018-Apr-03 from the older file > > system. May 20 would apparently mean a little > > below -r334014 . It native-booted okay, as did > > the April one. > > > > [I do not know how to inspect a /boot/loader* > > to find out what -r?????? it is from.] > > > > Unfortunately, I had done more than one -r339076 > > install from -r334014 before rebooting and > > no -r334014 loaders were still present: > > the other *.old files from a few minutes before > > the ones I had the boot problem with. > > > > I might be able to extract loaders from various: > > > > https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz > > > > materials and try substituting them in order to > > narrow the range for works -> fails. If I can, > > this likely would take a fair amount of time in > > my context. > > > > Other notes: > > > > It turns out that only Hyper-V based use needed > > a -r334804 kernel: Native booting with the older > > loaders and newer kernels works fine. > > > > Windows 10 Pro 64bit also has no problems > > booting and operating the machine. > > > > The native-boot problem does seem to be freeBSD > > loader-vintage specific. > > > >> For the BTX failure the display ends up with > >> (hand transcribed, ". . ." for an omission): > >> > >> BTX loader 1.00 BTX version is 1.02 > >> Console: internal video/keyboard > >> BIOS drive C: is disk0 > >> . . . > >> BIOS drive P: is disk13 > >> - > >> int=00000000 err=00000000 efl=00010246 eip=000096fd > >> eax=74d48000 ebx=74d4e5e0 ecx=00000011 edx=00000000 > >> esi=74d4e380 edi=74d4e5b0 ebp=00091da0 esp=00091d60 > >> cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > >> cs:eip=66 f7 77 04 0f b7 c0 89-44 24 0c 89 5c 24 04 8b > >> 45 08 89 04 24 83 64 24-10 00 c7 44 24 08 01 00 > >> ss:esp=00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > >> 00 00 00 00 00 00 00 00-f0 1d 89 00 00 00 00 00 > >> BTX halted > > > > I've no clue what of that output might be loader vintage > > specific. It might not be of use without knowing the > > exact build of the loader. > > > >> The board is a GIGABYTE X399 AORUS Gaming 7 (rev 1.0). > >> It has 96 GiBytes of ECC RAM, just 6 DIMMs installed. > > > > For reference for the board's BIOS: > > > > Version: F11e > > Dated: 2018-Sep-17 > > Description: Update AGESA 1.1.0.1a > > Using: > > https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz > > materials I found that: > > -r336492: worked (loader vs. zfsloader: not linked) > (no more amd64 builds until . . .) > -r336538: failed (loader vs. zfsloader: linked) > > (Later ones that I tried also failed.) > > Looks like this broke for booting the 1950X > system in question when the following was > checked in: > > Author: imp > Date: Fri Jul 20 05:17:37 2018 > New Revision: 336532 > URL: > https://svnweb.freebsd.org/changeset/base/336532 > > > Log: > Collapse zfsloader functionality back down into loader. > Yea, this shouldn't matter. It worked on all the systems I tried it on. So my first question: is this a ZFS system? Second, does it also have UFS? If yes to both, which one do you want it to boot off of? Warner From owner-freebsd-current@freebsd.org Sun Oct 21 08:41:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 625CBFE4FB2 for ; Sun, 21 Oct 2018 08:41:50 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2CFA82933 for ; Sun, 21 Oct 2018 08:41:49 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x431.google.com with SMTP id d2-v6so41623402wro.7 for ; Sun, 21 Oct 2018 01:41:49 -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=fBT550xnXFaYowzOm4qx/jb+/Jce2DceMBPDPsEjeTU=; b=H7pgBTw+zBoh7w4mQfJrSAiHr5Ow19zCgSpHRfzshC+52Z7vrZDskUhCyV2BzSj4hW LZWryNTb8+2zr+Clcy4w/GAtFZvkADho6BLkvLCwsq3QoIsNQRQotFFWNyvkVIAZ4Spm vmbq5f0IQrtvA4vAintrARt2HpiAhmWYN2hc0NZsw3d8gpop4aV43zcayYBPr3SzW5zt 6QKSoytgASc9YzjFHr03Cct9o1xTsebpVKtdhJF3iVIQwtj7/ip5vg+p4LENp78jIG6G qwcQETmYH2xE4wcpApLB5DM3qY7LZbRiueHf1tE2hY3ARM+qkJ8l+D7QvcChjOLsI6xb 5MuQ== 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=fBT550xnXFaYowzOm4qx/jb+/Jce2DceMBPDPsEjeTU=; b=YIhRI4xzdiViGd5LeRnUCdX++pEt3DJUtn2cp8/zNMJlL7i72jDzRW5FNxl099gQmG zGnwEtQiZ/OVBNoeu16wJ/jCznzTYbdQI0pSExcBv/jyC24HYVfFsYzHbq2kznkqmRYj zODWwZZ5Z3g07R9Y1QjqnNlP2UJb/ZH+XvrQ0CfvBKrpROZ0AieOTprWkRGLpFnfmCRu a8lwbpySv7gyyFzbCblIShljUW6+LK7R9Yvuf4QN9tjMMvr1nJ1MnxI2UtuPRLuU9byr EpjYhDkVdwpQs38+BeQve49lDpHTU5ugWbej0JrSXcyTcL4Fo3daCgQrQkfZmsuKyv5H Q2Fg== X-Gm-Message-State: AGRZ1gJUeE93KHdsiXJ185UfzGgORa2lE28q+2dxLImARxS6fvMwvoAh 8dpChEhP6AD6fYxqH86lZWurUzvEU9A= X-Google-Smtp-Source: AJdET5ctpV3KbrKxYyxot56X5t6QYH8fdWaBFYiTK96atA5dbsNn+j0AmwO2Ipo+9i/zQsg2Xho1QQ== X-Received: by 2002:adf:9403:: with SMTP id 3-v6mr183825wrq.54.1540111308088; Sun, 21 Oct 2018 01:41:48 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id i7-v6sm9498074wmd.41.2018.10.21.01.41.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Oct 2018 01:41:46 -0700 (PDT) To: FreeBSD Current From: Graham Perrin Subject: A new stable/12 poudriere jail is inferior to its stable/12 host Message-ID: <4364c553-9a52-3348-6772-f2d4a806b5ba@gmail.com> Date: Sun, 21 Oct 2018 09:41:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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: Sun, 21 Oct 2018 08:41:50 -0000 With the host already at r339438, creation of a jail (method: svn (other methods failed)) resulted in inferior version r339435. Is this normal? Re: I want the version of the jail to match the version of the host before I use poudriere to build kernel modules, and so on. ---- root@momh167-gjp4-hpelitebook8570p-freebsd:~ # poudriere jail -c -v stable/12 -j stable -m svn … [09:01:29] Recording filesystem state for clean... done [09:01:30] Jail stable 12.0-BETA1 1200085 amd64 is ready to be used root@momh167-gjp4-hpelitebook8570p-freebsd:~ # date ; uname -v Sun 21 Oct 2018 08:27:33 BST FreeBSD 12.0-BETA1 r339438 GENERIC root@momh167-gjp4-hpelitebook8570p-freebsd:~ # history … 1002  23:22   poudriere jail -c -v stable@339445 -j stable 1003  23:23   date ; uname -v 1004  23:23   poudriere jail -c -v stable/12 -j stable 1005  23:24   poudriere jail -c -v r339445 -j stable 1006  23:24   poudriere jail -c -v stable/12 -j stable -m http 1007  23:24   poudriere jail -c -v stable/12 -j stable -m ftp 1008  23:24   poudriere jail -c -v stable/12 -j stable -m svn 1009  8:27    date ; uname -v 1010  8:29    history root@momh167-gjp4-hpelitebook8570p-freebsd:~ # poudriere jail -i -j stable Jail name:         stable Jail version:      12.0-BETA1 1200085 Jail vcs version:  r339435 Jail arch:         amd64 Jail method:       svn Jail mount:        /usr/local/poudriere/jails/stable Jail fs:           hpelitebook8570p/poudriere/jails/stable Jail updated:      2018-10-20 23:24:51 Tree name:         default Tree method:       portsnap Status:             root@momh167-gjp4-hpelitebook8570p-freebsd:~ # From owner-freebsd-current@freebsd.org Sun Oct 21 09:07:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6690AFE5DAA for ; Sun, 21 Oct 2018 09:07:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2BFC183524 for ; Sun, 21 Oct 2018 09:07:27 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id E2986FE5D9A; Sun, 21 Oct 2018 09:07:26 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C140FFE5D93 for ; Sun, 21 Oct 2018 09:07:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 45D278351D for ; Sun, 21 Oct 2018 09:07:25 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [178.17.145.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6413E2600F9; Sun, 21 Oct 2018 11:07:24 +0200 (CEST) Subject: Re: Page fault in midi/sequencer.c To: Peter Holm , current@freebsd.org References: <20181020165604.GA4946@x2.osted.lan> From: Hans Petter Selasky Message-ID: <612cae90-cd82-6ade-ad9a-349d32965d88@selasky.org> Date: Sun, 21 Oct 2018 11:06:54 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <20181020165604.GA4946@x2.osted.lan> Content-Type: multipart/mixed; boundary="------------7DA408B79955E35972546159" 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: Sun, 21 Oct 2018 09:07:27 -0000 This is a multi-part message in MIME format. --------------7DA408B79955E35972546159 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 10/20/18 6:56 PM, Peter Holm wrote: > I can trigger this on 13.0-CURRENT r339445 with a non-root test program: > > Calling uiomove() with the following non-sleepable locks held: > exclusive sleep mutex seqflq (seqflq) r = 0 (0xfffff80003860c08) locked @ dev/sound/midi/sequencer.c:952 > stack backtrace: > #0 0xffffffff80bfe263 at witness_debugger+0x73 > #1 0xffffffff80bff1b8 at witness_warn+0x448 > #2 0xffffffff80bf6a91 at uiomove_faultflag+0x71 > #3 0xffffffff809439e6 at mseq_write+0x4c6 > #4 0xffffffff80a4f725 at devfs_write_f+0x185 > #5 0xffffffff80c02a87 at dofilewrite+0x97 > #6 0xffffffff80c0287f at kern_pwritev+0x5f > #7 0xffffffff80c0277d at sys_pwrite+0x8d > #8 0xffffffff81070af7 at amd64_syscall+0x2a7 > #9 0xffffffff8104a4ad at fast_syscall_common+0x101 > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex seqflq (seqflq) r = 0 (0xfffff80003860c08) locked @ dev/sound/midi/sequencer.c:952 > stack backtrace: > #0 0xffffffff80bfe263 at witness_debugger+0x73 > #1 0xffffffff80bff1b8 at witness_warn+0x448 > #2 0xffffffff810700d3 at trap_pfault+0x53 > #3 0xffffffff8106f70a at trap+0x2ba > #4 0xffffffff81049bc5 at calltrap+0x8 > #5 0xffffffff80bf6b42 at uiomove_faultflag+0x122 > #6 0xffffffff809439e6 at mseq_write+0x4c6 > #7 0xffffffff80a4f725 at devfs_write_f+0x185 > #8 0xffffffff80c02a87 at dofilewrite+0x97 > #9 0xffffffff80c0287f at kern_pwritev+0x5f > #10 0xffffffff80c0277d at sys_pwrite+0x8d > #11 0xffffffff81070af7 at amd64_syscall+0x2a7 > #12 0xffffffff8104a4ad at fast_syscall_common+0x101 > > > Fatal trap 12: page fault while in kernel mode > cpuid = 4; apic id = 04 > fault virtual address = 0x20ea6b > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff8106d32d > stack pointer = 0x28:0xfffffe00a844a660 > frame pointer = 0x28:0xfffffe00a844a660 > 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 = 2356 (xxx) > [ thread pid 2356 tid 100278 ] > Stopped at copyin_nosmap_erms+0xdd: movl (%rsi),%edx > db> > Hi, Can you test the attached patch? --HPS --------------7DA408B79955E35972546159 Content-Type: text/x-patch; name="seq.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="seq.diff" Index: sys/dev/sound/midi/sequencer.c =================================================================== --- sys/dev/sound/midi/sequencer.c (revision 339376) +++ sys/dev/sound/midi/sequencer.c (working copy) @@ -921,7 +921,9 @@ SEQ_DEBUG(8, printf("midiread: uiomove cc=%d\n", used)); MIDIQ_DEQ(scp->in_q, buf, used); + mtx_unlock(&scp->seq_lock); retval = uiomove(buf, used, uio); + mtx_lock(&scp->seq_lock); if (retval) goto err1; } @@ -996,7 +998,9 @@ retval = ENXIO; goto err0; } + mtx_unlock(&scp->seq_lock); retval = uiomove(event, used, uio); + mtx_lock(&scp->seq_lock); if (retval) goto err0; @@ -1034,7 +1038,9 @@ SEQ_DEBUG(2, printf("seq_write: SEQ_FULLSIZE flusing buffer.\n")); while (uio->uio_resid > 0) { + mtx_unlock(&scp->seq_lock); retval = uiomove(event, EV_SZ, uio); + mtx_lock(&scp->seq_lock); if (retval) goto err0; @@ -1045,6 +1051,7 @@ } retval = EINVAL; if (ev_code >= 128) { + int error; /* * Some sort of an extended event. The size is eight @@ -1054,7 +1061,10 @@ SEQ_DEBUG(2, printf("seq_write: invalid level two event %x.\n", ev_code)); goto err0; } - if (uiomove((caddr_t)&event[4], 4, uio)) { + mtx_unlock(&scp->seq_lock); + error = uiomove((caddr_t)&event[4], 4, uio); + mtx_lock(&scp->seq_lock); + if (error) { SEQ_DEBUG(2, printf("seq_write: user memory mangled?\n")); goto err0; --------------7DA408B79955E35972546159-- From owner-freebsd-current@freebsd.org Sun Oct 21 13:14:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9BC7FF0DE4 for ; Sun, 21 Oct 2018 13:14:20 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22BAB8D2D7 for ; Sun, 21 Oct 2018 13:14:20 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x329.google.com with SMTP id i8-v6so7602842wmg.0 for ; Sun, 21 Oct 2018 06:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=5RcMZIMkM3hjhkZgzlIkiuQpZz4bGiM0yK2KPyFf74U=; b=Elh3xqM0oqQWkKAexaHDXT9o0ECSnwZycuUO1Fgz/5leitXmXJQJf0GammfKBDYPyH knRsOQON58hwDhGpwE8MI4u8jCawUuhxXCCyF0ktfmwAQ4RidImH/ookflL99hE14MWI 58wNofi3ZxPUmws0uYW/zJkdTt9vSYwnEt+CfOdkqwHU0w6ZJKtlUsfvsf3ZzYHPwQSG SrIA1PSlAmCQzF9KcR/CZhchlUZLma8qiq/5n4kY/E/wmQXwku7tIzxr5jhRx6yq4Ld3 AOxHK5tcAXLcT+J8HZ2GtZB6BVoR8oiqnI769FYulaZE980XclQtbdPpi2FZN1Dy4oZi RAJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=5RcMZIMkM3hjhkZgzlIkiuQpZz4bGiM0yK2KPyFf74U=; b=ntk0Q6JN1Gs49yL8mnNacGR5RE4SB1xYO+YO7dpDRkaU6VpPmVHk+OELRyx26g7/z6 iFDdKIw18b5SnKEnRf/YyO5UCNNPLM6pQJoDqbUbwq2xU5onPEaBy5d+7Mm/Gq5Gu5Le u+b5gaNvegVUhaCMjENkdzn9nybjB93jTyTEIi/X0I0f44qH0Mbhap3uUkOW+mPpUDs9 CYAf3wOjHFkeM0CYmjRS5BRT+9CIh8kCAloWVSN+zO6Msz2gUdQYT/vJuBYvcsc72Oz4 SbtJ2lPxMXiTqBBJ3KtOIrNKUcVZiifhVEZGqu9kyTUoRiyVXOVOOPNrRTinkVUo2Irg F+Kw== X-Gm-Message-State: ABuFfogPcyTfccFUAOWz2HWwLn2vmOnJGjmC7utsW87T3PrFDeL8f2VR JzxlWtQqr0zzERjdRdI+VGe67bp3OmE= X-Google-Smtp-Source: ACcGV63PS2YJ9uhhozZNxWwxSDBMsxLS0V0bjce1MBQrPym7/8nZrVkYxsLkArZSXxBoK9b9CK+YBQ== X-Received: by 2002:a1c:1d6:: with SMTP id 205-v6mr12506211wmb.0.1540127658965; Sun, 21 Oct 2018 06:14:18 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id x8-v6sm75346204wrd.54.2018.10.21.06.14.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Oct 2018 06:14:17 -0700 (PDT) Subject: Re: A new stable/12 poudriere jail is inferior to its stable/12 host To: FreeBSD Current References: <4364c553-9a52-3348-6772-f2d4a806b5ba@gmail.com> <20181021123126.GB1163@albert.catwhisker.org> From: Graham Perrin Message-ID: <29470acd-f263-1159-784a-edd1a351fa71@gmail.com> Date: Sun, 21 Oct 2018 14:14:16 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181021123126.GB1163@albert.catwhisker.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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: Sun, 21 Oct 2018 13:14:20 -0000 On 21/10/2018 13:31, David Wolfskill wrote: > On Sun, Oct 21, 2018 at 09:41:46AM +0100, Graham Perrin wrote: >> With the host already at r339438, >> creation of a jail (method: svn (other methods failed)) resulted in >> inferior version r339435. >> >> Is this normal? >> >> Re: I want the version of the jail to match the version of the host before I use poudriere to build kernel modules, and so on. >> >> .... > r339438 is a revision in stable/11. That's weird, because I recently successfully ran: svn switch '^/stable/12' /usr/src prior to a successful update of the system. From owner-freebsd-current@freebsd.org Sun Oct 21 12:31:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3F14FEF268 for ; Sun, 21 Oct 2018 12:31:29 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 EE5128BC9D for ; Sun, 21 Oct 2018 12:31:28 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w9LCVQTi002552; Sun, 21 Oct 2018 12:31:26 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w9LCVQUP002551; Sun, 21 Oct 2018 05:31:26 -0700 (PDT) (envelope-from david) Date: Sun, 21 Oct 2018 05:31:26 -0700 From: David Wolfskill To: Graham Perrin Cc: FreeBSD Current Subject: Re: A new stable/12 poudriere jail is inferior to its stable/12 host Message-ID: <20181021123126.GB1163@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Graham Perrin , FreeBSD Current References: <4364c553-9a52-3348-6772-f2d4a806b5ba@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DKU6Jbt7q3WqK7+M" Content-Disposition: inline In-Reply-To: <4364c553-9a52-3348-6772-f2d4a806b5ba@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-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: Sun, 21 Oct 2018 12:31:30 -0000 --DKU6Jbt7q3WqK7+M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 21, 2018 at 09:41:46AM +0100, Graham Perrin wrote: > With the host already at r339438, > creation of a jail (method: svn (other methods failed)) resulted in > inferior version r339435. >=20 > Is this normal? >=20 > Re: I want the version of the jail to match the version of the host b= efore I use poudriere to build kernel modules, and so on. >=20 > .... r339438 is a revision in stable/11. r339435 is a revision in stable/12. That bit of confusion illustrates why I believe that it's useful for uname to show the revision of the branch in question as of the last time the sources were updated, rather than (just) the last revision that happened to be committed to the entire repository as of the last time the sources were updated. Thus, I have uname strings like: FreeBSD localhost 11.2-STABLE FreeBSD 11.2-STABLE #770 r339442M/339445: Fr= i Oct 19 03:45:47 PDT 2018 root@g1-215.catwhisker.org:/common/S1/obj/us= r/src/sys/CANARY amd64 FreeBSD localhost 11.2-STABLE FreeBSD 11.2-STABLE #771 r339446M/339530: Su= n Oct 21 03:37:18 PDT 2018 root@localhost:/common/S1/obj/usr/src/sys/CA= NARY amd64 FreeBSD localhost 13.0-CURRENT FreeBSD 13.0-CURRENT #144 r339436M/339445: F= ri Oct 19 15:59:43 PDT 2018 root@localhost:/common/S4/obj/usr/src/amd64= =2Eamd64/sys/CANARY amd64 FreeBSD localhost 13.0-CURRENT FreeBSD 13.0-CURRENT #145 r339530M/339530: S= un Oct 21 04:46:46 PDT 2018 root@localhost:/common/S4/obj/usr/src/amd64= =2Eamd64/sys/CANARY amd64 See the bottom of for additional details, if you're interested. Peace, david --=20 David H. Wolfskill david@catwhisker.org Women (and decent men): vote against supporters of Trump's misogyny! See http://www.catwhisker.org/~david/publickey.gpg for my public key. --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlvMcZ5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfwDQf/THgaHokaymSVGmTttdwuLrYCJv9s7ggm9UQHS6P1mx4hxOy+iM5eFf5w UK4g3Ubu97cGNqUPmuIca8Gr+EwPVkdE7xiZSTqljt/PR7ylOOa2F5EQA1QqGr4M tbxXVampCb/qLMM9JIWjgDp1uq1hCzO5GvX0EdgTWp5T53YSo83WzJi3IK9eiJAp DzSbrBwojwHzTBEMDLBxrZwYdi0gCzkZeLL3QQWgGRE43OksJbSG57NR6slLPn9X 1FzSlTRPY8Hwn/1PUB9+P8qJ/PQe1V3Mp+9CJSstWI9/Wn21JrFRZBwSuinfctWj 9ahtmyp4sbh5YUuUIqBES74B5/yrCA== =5DOc -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M-- From owner-freebsd-current@freebsd.org Sun Oct 21 14:44:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 782AFFF489C for ; Sun, 21 Oct 2018 14:44:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13A069093E for ; Sun, 21 Oct 2018 14:44:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe29.google.com with SMTP id i10so28007259vsm.13 for ; Sun, 21 Oct 2018 07:44:34 -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=XZtWOLLa5Rj/HUGLmmLF7JbRlmuJDaavY2Oi6a8hP00=; b=GVA05YPNrq1nvRV9k38dPSU9JsipcT3OtKUr8i9nLtNgLFQNB3xR0A7/2ZFHyDIonP tlthXGLC0uN2h7uLl6kcjHPXhXRZH1AMf0ZIRd32ZnWUoM3naav+yl1jvGxqNxDSDPxP 2B8BMR5uZFfQ9uOeZbQ+OhzyjgmzMOIIbQzcxh2y4ksVFEmiRUKs5zOsp+pR6ZOjMXzM sfPHRREiCTskOdyjjYgp3s/dmaCLbgZfDC7hkRyDUYcFkPc2t0kvBn0++vcI/suO3beG b+jLH2MOTej9h9Vk0FY5J5oiELwFVRbOQorS38EqvQhXKxvuRg5S6vUCKENmNS5T8hiq WQ9w== 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=XZtWOLLa5Rj/HUGLmmLF7JbRlmuJDaavY2Oi6a8hP00=; b=NFnQjZOUWsKbt1CgdbpKKfT5PvnlBhEw0sbSgndKaj6LMRlETWdHokD+mKyqlLev1A UdgSkEuvUflbjt8ePIJyrxnXdpVfFJKE0LQli+D3Ad5q5qGVG2GLdbXmXWEyKSWxAIzv VzC+YURpi1b8/81fEJCrNaBM1MBazp5N0+yaHuiLp/l8fDkQxYDB5Cv0db7cFbxL9SSM fzd1LnIYN4J9SxU+Qa2LQi+Pn5cfkP7K4Mq/6Bnu59R5A+y/gXIjGDdyqzMGlc7adhvq 6dWxHM17yVTmXXz1d9fbELisJaSvJcSBdYXx/kjtZ1gzjunbeIgOA1Opak84/7fb+Ul9 U5BQ== X-Gm-Message-State: ABuFfoj89HoARzyH27WhyQngEClj+I9MEqFXC8mhzoyz8yLJREIR4jCz waZ3y0QGolw2BjMxf0EJaPUIit+P8P8p1grxgi4d1Dfx X-Google-Smtp-Source: ACcGV60Gdpllekw0+BJDlUjQEwgiAPSRXBo8dzZdDrnE2g6FXoF3wduTv1LjR9cbdfr3Y5HjrxB31jdxKaYWvum22q4= X-Received: by 2002:a67:4dc7:: with SMTP id i68mr17445440vsg.46.1540133073302; Sun, 21 Oct 2018 07:44:33 -0700 (PDT) MIME-Version: 1.0 References: <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com> In-Reply-To: From: Warner Losh Date: Sun, 21 Oct 2018 08:44:21 -0600 Message-ID: Subject: =?UTF-8?B?UmU6IERSTTogcmFkZW9ua21zIOKApiBjYW4gbm90IGJlIHVubG9hZGVkIChrZXJuZWwgcA==?= =?UTF-8?B?YW5pYykpIOKApg==?= To: Kevin Oberman Cc: Hans Petter Selasky , Graham Perrin , FreeBSD Current 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: Sun, 21 Oct 2018 14:44:34 -0000 On Sun, Oct 21, 2018, 2:29 AM Kevin Oberman wrote: > On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky > wrote: > > > On 10/20/18 3:10 AM, Graham Perrin wrote: > > > On 20/10/2018 00:01, Graham Perrin wrote: > > > > > >> kldunload radeonkms > > >> > > >> =E2=80=93 results in a kernel panic. > > > > > > Found, at < > > > https://github.com/FreeBSDDesktop/kms-drm/issues/90#issuecomment-41585902= 1 > > > > under 'drm-devel-kmod g20180822 screen freeze': > > > > > >>> =E2=80=A6 normally you never unload the graphics driver so we haven= 't spent > > time on proper cleanup. Also, the drm module will cause panic if you tr= y > > load load it again after unload. > > > > > > ---- > > > > > > Is the principle for -next- the same as for -devel-, should I simply > > _never_ attempt to unload the module? > > > > > > $ date ; uname -v > > > Sat 20 Oct 2018 02:06:21 BST > > > FreeBSD 12.0-BETA1 r339438 GENERIC > > > $ pkg query '%o %v %R' drm-kmod drm-next-kmod gpu-firmware-kmod > > > graphics/drm-next-kmod 4.11.g20180822 poudriere > > > graphics/gpu-firmware-kmod g20180825 FreeBSD > > > > I recommend building these modules from source, /usr/src which match yo= u > > currently installed kernel! > > > > --HPS > > > This is a really good practice for all kernel modules from ports. If you > build your kernel from source, put them into /etc/rc.conf to define > PORTS_MODULES to always rebuild all modules when the kernel is built. Eve= n > if you install packages for your release, you need to realize that packag= es > are built against the oldest supported minor release of a major release a= nd > that works or all ports that only have to match system ABIs which remain > stable for the life of a major release. But, while the KBI (Kernel Binary > Interface) usually remains stable, it occasionally does and did between > 11.1 and 11.2 which meant that two ports failed when installed from > packages on 11.2 system until 11.1 went EOL this month. > > I really wish that the portsmgr team would come up with a policy to > maintain an archive of port based kernel modules whenever there is a mino= r > release where people who have broken systems can get trusted packages. So= me > people are really not very capable of building from ports. > I've reviewed patches from jhb that rebuild when the kernel is rebuilt. Having the package would be better but is more tricky. Warner -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > 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 Oct 21 16:10:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA60EFF8660 for ; Sun, 21 Oct 2018 16:09:59 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.in-berlin.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68FA99442A for ; Sun, 21 Oct 2018 16:09:58 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) X-Envelope-From: h2+lists2018@fsfe.org X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id w9LG9pAM032693 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 21 Oct 2018 18:09:51 +0200 To: freebsd-current@freebsd.org From: Hannes Hauswedell Openpgp: preference=signencrypt Autocrypt: addr=h2+lists2018@fsfe.org; prefer-encrypt=mutual; keydata= mDMEWjvrCBYJKwYBBAHaRw8BAQdA69H3pIQlZtmfHWcHtdO/QHaSCGncSJ5WCcrEOyLNGFq0 KUhhbm5lcyBIYXVzd2VkZWxsIDxoYW5uZXNAaGF1c3dlZGVsbC5uZXQ+iJkEExYIAEECGwMF CQPCZwAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUC WjvrdQIZAQAKCRBvny4w7LN5d/StAQClFHWUmhZehalNE7JFiRuNpwi0/v2jKA+IU7/IvjPj HQD+JC3jTzmchT+R+SMGM4aNvHSnkM3r7z2Y46syUJz6bwC0H0hhbm5lcyBIYXVzd2VkZWxs IDxoMkBmc2ZlLm9yZz6IlgQTFggAPhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+tWAhsD BQkDwmcABQsJCAcCBhUICQoLAgQWAgMBAh4BAheAAAoJEG+fLjDss3l3qg8A/io/KtgVK0C0 RQO4dTv4Cfof7i7Jz6BgJKNCDQnmvFl6AP0VeYDCvWJksngds2ZKz89jboAzAEzAU4/Gmx2G DJpiD7QxSGFubmVzIEhhdXN3ZWRlbGwgPHBvbGl0aWtAaGFubmVzLmhhdXN3ZWRlbGwubmV0 PoiWBBMWCAA+FiEE71b2aqaDPjLOBT9Vb58uMOyzeXcFAlo764MCGwMFCQPCZwAFCwkIBwIG FQgJCgsCBBYCAwECHgECF4AACgkQb58uMOyzeXc2RwD+PG/X0gaPyWXQfhsVC0h+KcRDRNXC U862y9AgstX0bQQBAP+oSMSu1TECWEZAlsijAL2IMpYJLObC0GRGcySHHlYOuDgEWjvrCBIK KwYBBAGXVQEFAQEHQDkbc3o1Tx1VoU3R/FTBZU466MK/hCV4wR5+LIYpy/VBAwEIB7g4BFo7 6wgSCisGAQQBl1UBBQEBB0A5G3N6NU8dVaFN0fxUwWVOOujCv4QleMEefiyGKcv1QQMBCAeI fgQYFggAJhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+sIAhsMBQkDwmcAAAoJEG+fLjDs s3l3NmoBAPybRpTZWiShUDJRfmqSxH0EzcdRuXQC72D8DapTcrrpAQCubhUI634RzxbXYvxa WQctZgBLkfsw+qv+FWB2PfExDA== Subject: Current status of Ryzen (non-)support Organization: Free Software Foundation Europe Message-ID: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> Date: Sun, 21 Oct 2018 18:09:50 +0200 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ShaDdOCSjudtpvqD7xAUvipDLzgguCBZP" 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, 21 Oct 2018 16:10:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ShaDdOCSjudtpvqD7xAUvipDLzgguCBZP Content-Type: multipart/mixed; boundary="D4CAS05cxZvYTHxRlhSBVe1qEICj7hjy2"; protected-headers="v1" From: Hannes Hauswedell To: freebsd-current@freebsd.org Message-ID: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> Subject: Current status of Ryzen (non-)support --D4CAS05cxZvYTHxRlhSBVe1qEICj7hjy2 Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable Hi everyone, I wanted to ask what the current status of Ryzen support is and/or whether any new changes are planned. My situation: * second generation Ryzen: 2600X * running -CURRENT * I have done the things described here: https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html= * no full system freezes, but under load, e.g. building with 12 threads, programs start to segfault. * memtest86 ran through without issues * on a Linux dual boot I haven't had any issues Is this a known problem? Anythings I can do about it? I thought the Ryzen problem were only supposed to happen with first generation CPUs... Thanks and regards, Hannes --D4CAS05cxZvYTHxRlhSBVe1qEICj7hjy2-- --ShaDdOCSjudtpvqD7xAUvipDLzgguCBZP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUCW8ykzgAKCRBvny4w7LN5 d0D3AQD8j6z94eOclW3kYhsKTmo7p1FxWK3Z6PKS3xf5HoFprQD/bSo+iDza6B7u zk9cAaeBEo06D4S9LcUK+Yx4hdqtQQk= =PBCc -----END PGP SIGNATURE----- --ShaDdOCSjudtpvqD7xAUvipDLzgguCBZP-- From owner-freebsd-current@freebsd.org Sun Oct 21 07:10:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EADCBFD85AF; Sun, 21 Oct 2018 07:10:00 +0000 (UTC) (envelope-from sneakywumpus@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55E6A7F4CA; Sun, 21 Oct 2018 07:10:00 +0000 (UTC) (envelope-from sneakywumpus@gmail.com) Received: by mail-ed1-x52d.google.com with SMTP id r25-v6so221428edy.0; Sun, 21 Oct 2018 00:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=7u9iiALqAGP7k4Sjd+u+AtUNYyK03ExN/BAVWaA4TI4=; b=vA2lEseynr0jqgIE4Z8Wu/rC5ZEE4z315oXXbSXoxEZgupUVwazjc6nuak9G0uliFt mAkYbzcnf53RHu/lxraUCFU3Y/+AqTQ9aQLFwmdVRXRnq/fRgpcsQq2iEqXWiMllgdwV 84clow8hrSMseWWGgfjmYWXhSDd+JLbAJCMLCilKCdMTk5yXuE9fr31rnYKcjj8Tbo3f zHfgi6vmzTN3ApxgDEn+RqAofY5kP+Yys7rweeE88lWgd86Tcz7ikZaMAqKMz58IPgqb jfqG5pr9QmcWDEA2mlsF11ju/9DjWjvy6hl5buO5u5aAWcmVeTVhjdHQARwTQ4CUFtq/ xOrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=7u9iiALqAGP7k4Sjd+u+AtUNYyK03ExN/BAVWaA4TI4=; b=m6p+D7GNUql6/PVUbVGk+EeXnHlF/m7DVoy4FKaY4CMsxUNW44R6STEYQyV1B8D69X 9ZCwBR49dznPTV3E1b9D7gq1Igs1HROXd/V3Puwf27Bekp9ddGJ/ASusahyXTjmjfvTw mepJwHHr4zMLI0IqGj2HpJT2wVeGqF3WI/ah1idihwZbmbMlgjZOuM8X2vhN7OproZdZ q9DN5uTK1OdLbMXipM+XNL99VUmLg8w4iQnteOgZRjsd9Hwu14/hvpRPLUt82mqSpu5z y0papGH7EYPegI/2pZ+8rBzXyMJrfTB70W1z4c+T2/sTPEFVmRHZ+ljyo/dumzF2kcYU DoTA== X-Gm-Message-State: ABuFfojLmr1PxFi/Rs+XxtSnjZvj4y0r+d/yxx5BOOTZcdjJD0MlEf+m 0Ox4Sm3gwMSRA8Qr2Cz1rcYevnhL X-Google-Smtp-Source: ACcGV62xAdJVQV/vZxD4CK0xH4wyvrJWaFb4+SV9zIKivp4yIdqXo7GJrGdRRPcP83hrMXCObd/UFg== X-Received: by 2002:aa7:cf82:: with SMTP id z2-v6mr10399524edx.208.1540105798796; Sun, 21 Oct 2018 00:09:58 -0700 (PDT) Received: from ed209.ocp.lan (ip4d14e2e6.dynamic.kabel-deutschland.de. [77.20.226.230]) by smtp.gmail.com with ESMTPSA id 18-v6sm11029947edt.34.2018.10.21.00.09.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Oct 2018 00:09:58 -0700 (PDT) From: Thomas Eberhardt Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: clang debugging code in stable/12 and current Message-Id: Date: Sun, 21 Oct 2018 09:09:57 +0200 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3445.100.39) X-Mailman-Approved-At: Sun, 21 Oct 2018 16:19:40 +0000 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, 21 Oct 2018 07:10:01 -0000 It looks like the enabling of debugging code in clang/llvm was flipped = around during the stable/12 branch. See the definition of NDEBUG in lib/clang/llvm.build.mk line 20: current before r339436: #CFLAGS+=3D -DNDEBUG after r339436: CFLAGS+=3D -DNDEBUG stable/12 at r339435: #CFLAGS+=3D -DNDEBUG i.e. debugging code is now disabled in current and enabled in stable/12. From owner-freebsd-current@freebsd.org Sun Oct 21 17:33:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1CFEFFBCF9 for ; Sun, 21 Oct 2018 17:33:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 1D47E711EF for ; Sun, 21 Oct 2018 17:33:39 +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 w9LHXStk003844 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Oct 2018 20:33:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9LHXStk003844 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w9LHXRgW003843; Sun, 21 Oct 2018 20:33:27 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 21 Oct 2018 20:33:27 +0300 From: Konstantin Belousov To: Hannes Hauswedell Cc: freebsd-current@freebsd.org Subject: Re: Current status of Ryzen (non-)support Message-ID: <20181021173327.GJ5335@kib.kiev.ua> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> User-Agent: Mutt/1.10.1 (2018-07-13) 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-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, 21 Oct 2018 17:33:39 -0000 On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: > Hi everyone, > > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. > > My situation: > * second generation Ryzen: 2600X > * running -CURRENT > * I have done the things described here: > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html This was based on the public errata document for the first gen ryzen. I am not aware of the erratas ('revision guides' in AMD terminology) for the second gen ryzens. For now you can only get fixes for microcode from your BIOS updates. > * no full system freezes, but under load, e.g. building with 12 threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues Or look at the Linux sources and see if any workarounds are applied and chicken bits are set for your CPU. > > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation CPUs... > > Thanks and regards, > Hannes > From owner-freebsd-current@freebsd.org Sun Oct 21 19:51:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 409EAFFEAF0 for ; Sun, 21 Oct 2018 19:51:26 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 8BAF775872 for ; Sun, 21 Oct 2018 19:51:25 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w9LJpMru007478; Sun, 21 Oct 2018 19:51:22 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w9LJpM3I007477; Sun, 21 Oct 2018 12:51:22 -0700 (PDT) (envelope-from david) Date: Sun, 21 Oct 2018 12:51:22 -0700 From: David Wolfskill To: Graham Perrin Cc: FreeBSD Current Subject: Re: A new stable/12 poudriere jail is inferior to its stable/12 host Message-ID: <20181021195122.GA5358@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Graham Perrin , FreeBSD Current References: <4364c553-9a52-3348-6772-f2d4a806b5ba@gmail.com> <20181021123126.GB1163@albert.catwhisker.org> <29470acd-f263-1159-784a-edd1a351fa71@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <29470acd-f263-1159-784a-edd1a351fa71@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-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: Sun, 21 Oct 2018 19:51:26 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 21, 2018 at 02:14:16PM +0100, Graham Perrin wrote: > On 21/10/2018 13:31, David Wolfskill wrote: > > On Sun, Oct 21, 2018 at 09:41:46AM +0100, Graham Perrin wrote: > >> With the host already at r339438, > >> creation of a jail (method: svn (other methods failed)) resulted in > >> inferior version r339435. > >> > >> Is this normal? > >> > >> Re: I want the version of the jail to match the version of the hos= t before I use poudriere to build kernel modules, and so on. > >> > >> .... > > r339438 is a revision in stable/11. =E2=80=A6 >=20 > That's weird, because I recently successfully ran: >=20 > svn switch '^/stable/12' /usr/src >=20 > =E2=80=93 prior to a successful update of the system. Sure. On my laptop (for example), I have a local private SVN mirror repo. It is currently at r339530. On each of 3 different slices, I have stable/11, stable/12, and head; the corresponding working directories (which have been updated since the repo was last updated) are currently at r339446, r339435, and r339530 (respectively). FreeBSD's newvers.sh would put "r339530M" in the uname string for each of those. My version places "r339446M/339530", "r339435M/339530", and "r339530M/339530" (respectively) in the uname string to try to help clarify which revision in each branch last affected that branch. Peace, david --=20 David H. Wolfskill david@catwhisker.org Women (and decent men): vote against supporters of Trump's misogyny! See http://www.catwhisker.org/~david/publickey.gpg for my public key. --T4sUOijqQbZv57TR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlvM2LpfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7he8Pwf+P8hyYZPNAq/GCcccIXnikpS6+bOFivJrE7HRII12awuk6iNzvfpTmoN4 Zk7dApp9smtU4vswY+rlIt0O9HcHtULixCyhX0hQbN2r9oOYdArZ9TM1YPTu/At6 1l4lCzXzKkgL3wwpw0MNLSacIGK3e2Cu5HSA+NeBlR5BdfV5K7sAetd0L298e7jo SkNOKTRVfmvGgjOisZXNlyrQOoZ8zuBtJB4o/UUCJlu05wYz/mm06NYDHCkQlM/s Pnz00G+VYxY7utGLN8ijfOPGwdjH1ZYQqrjAZ5GvgBQuzC57Dbb3kX/xKIIKXXkK BxtMkYd0Paahq48XfiZDhVxC5wHx2g== =fOUN -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-current@freebsd.org Sun Oct 21 21:14:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E16910369AE for ; Sun, 21 Oct 2018 21:14:32 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2150278E95 for ; Sun, 21 Oct 2018 21:14:31 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-ed1-x52f.google.com with SMTP id z21-v6so36017968edb.11 for ; Sun, 21 Oct 2018 14:14:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=2QRRSLJYZ+VblV+yFnzpjBYutX/vEeG0feZWC0g3Ue4=; b=SobRJlZYWsnZnG9S/9NLx8m95iTh0ybeowgDHdAz5sAMk4BuTjADP2MG8Qtor+kEcM zPQ2WuYV6qQjcdqTl245/sH1CrLjSEAxmcrPDdvJY4VooOFMuzehT5qXTSqD0d20dk0b F9Y/3bpSnBc3OmGgNZhJlQuaFz6yfvCZqyYLxFyPfN4YdOfoIZHMKyX5aeOVK1rORP9u lyR/AH9GP8v/X31rhSkV0BL9b9CEaPYyRFKGswtS+Zff1uGcEozOjBe39p97qKYtKi8+ pYcqQUys3gef9kIJPU3egVq4Wufust8+hVcwlKAsVIP/zYxGgvui6tLpO1tASvbZi1jw H9KA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=2QRRSLJYZ+VblV+yFnzpjBYutX/vEeG0feZWC0g3Ue4=; b=LSVf00tfssZG4ZKBaT2m+4PyV7sh58UoZsHsfTsKGPprWeI1nK5/Ij+WOhbuadfKmU Jcw6McOhseB0suoZrxf4kox0v12UsMWe7m1yPY61AaMIQpSCkHYNaAY2zuOwEeNZDTFp +wrNoufp7jgN8NhLSHcYeYuU2Hgvy4wsmHbCR29szpQoppsvt6Ny0OUmx2NKKcnBuXfl dLH79noQH7mDaotOgMur2TMUTpFMZoB7ti26IUwk+E9Kn5oDG0MOJk9OyxkRUvGOfqiG o2tCsHl45BYHCNSprUZIkT03Pdf1bzelaGjU/YNtRRwODPtJcZuNIkwo5+AqTdiWB0DK 2aNQ== X-Gm-Message-State: ABuFfogapRONkxHgeTFhX6YRH12LpsZWwIE0xIB1o/yznGUEj5VMQt9I l2boyyyJGXR/HDrsieymBRhURtYw X-Google-Smtp-Source: ACcGV63SkqdnR2QJK2wopyRyRdo/VS0kw8t+r8MPZNBgLHRxm/lKn6dmxXdurLn55qq5sR6kH0lMsw== X-Received: by 2002:a50:b246:: with SMTP id o64-v6mr12035753edd.80.1540156470701; Sun, 21 Oct 2018 14:14:30 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:343b:eee8:f5b6:623c]) by smtp.gmail.com with ESMTPSA id ha9-v6sm6390586ejb.77.2018.10.21.14.14.29 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 21 Oct 2018 14:14:29 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Mon, 22 Oct 2018 00:14:25 +0300 To: Hannes Hauswedell Cc: freebsd-current@freebsd.org Subject: Re: Current status of Ryzen (non-)support Message-ID: <20181022001425.41651e45@gmail.com> In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 21 Oct 2018 21:14:32 -0000 On Sun, 21 Oct 2018 18:09:50 +0200 Hannes Hauswedell wrote: > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. > > My situation: > * second generation Ryzen: 2600X > * running -CURRENT > * I have done the things described here: > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > * no full system freezes, but under load, e.g. building with 12 > threads, programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues > > 1300X (25 week), 2200G, 2700X - OK on 11.2 I do not apply any fixes provided by @kib in "Ryzen public erratas". Mine FreeBSD configs and tunings: http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/11.2/base/ http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/11.2/wks/ Asrock Taichi x370 have strange proublems with PCI-e devices on BIOS ver > 4.60: after load any smbus drivers pcie stop work or do it very strange. Also with PinnaclePI-AM4_1.0.0.5 mine amdtemp driver read strange temperature, @cem should know more about this. http://forum.asrock.com/forum_posts.asp?TID=9833&PID=56770� Last time I have segfaults on bad mem modules contacts (fix: clean and reinstall) and mine coller do many pressure. From owner-freebsd-current@freebsd.org Mon Oct 22 00:12:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A130D104C596 for ; Mon, 22 Oct 2018 00:12:02 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-10.consmr.mail.gq1.yahoo.com (sonic307-10.consmr.mail.gq1.yahoo.com [98.137.64.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2893A7DCDC for ; Mon, 22 Oct 2018 00:12:01 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: oHF4aGwVM1kqQuodVW3ySR9ih7PdFliZKJX4ZJsAQPMFpmbCmxdcLz0TJiI67l6 eDnXQC0CRRKH5yzT52Uf9J3xp_5QHcLBaKhO8sCfYSgnPjnNBbG7AjovxmVtmslSTtyw_ZhB.0or OzRM4mVxdP0aXa39bXwrsOvFY3EiCrIyyOFNIn5bUZem5QZ3n6ul30_YS4UDPGNRH9Wr9eonsJyB L0uU0BEhX7yM8UNo8XsQMOJAUGtC.sU_1hJVJkEFzqa3F4gpfGkqNK.8TBgNxRT._S60H.pgvKLY b7Aukh8kJAHd8gi2gAnAL_ne8DQDcmBY3647EnpKcfEc6CUiMTG5uPCE_70FiUt2xpzgAh0_jxzK RvXQkkLfTX2Zu_lA9HoCzpDACUlyYZiBt0ytrPDwRw92IqOyQszKvSXCB2on5_tinh65c7PHK4QZ frdq9CDskV0EXIzwE8UA37qiJtTGUQ8l3ASnCv485xSurYMwXQzWRw5wZS_UCDYbc9FUfSmqais1 kt9j8UK0rGzAHUln0Xpvjz4ViMGpjhfaCTLFUhUEbRmatAKaoFk3b3ak77J75Jx7bg_tyq5NgHZ1 PreHvumKDf6DMDWN1NDiCB8vqjErjMU1UdOptfeW0Xwtm1V2KmTWG7WDuzLkXZvszj28zH0.O5nM zLnjlbdaGH7IHj1sd26ULiAIkt.HqsuiZpi3hqOLe0KnT3kIv0z.zSVz2KF5GA_eYEYsIXS6IlH4 qpIROozNAgyOg5jbpp981GYIMKo5l9e6P6XlPjb_jSUueXjtpf89D263joIYszX2UNRI2psh.ykk 8PwuWusqZGMVFY593Fj1q7pwkLmQBAFSYs_Rb69VJ5ESelpEluL12TUvgyuU95xHJtwGM4VZ0RAc YVX2XsT0AzvZxreRlWTyyguYpp4shSKGne7WVnanmlpx2eUMy48Tw1Ne0D6fXYtp1WWQHuqcTTyt R_vfoWuXklw1DRGAwQvsJjCe2TPdGr.gCGjN1p_dVzfAT_UH7T.c1kCDqYAGuHz8EUBLzh6APt4g q0CLNY2Soa1PiKOAlrLHNiEHAGuETUpcer0Hpxjc5zsjKCfKYgYnbig6J2khDNFngnUjBNCF4ro8 M1pFUurU- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Mon, 22 Oct 2018 00:11:54 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp422.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 06b8f75994a09b5d566b5f2a28055cc7; Mon, 22 Oct 2018 00:11:50 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r339076's boot loader fails to boot threadripper 1950X system (BTX halted); an earlier version works [ WITHOUT_ZFS= fixes it ] From: Mark Millard In-Reply-To: <30DD2F47-C8CB-4CEC-8563-C7083D0EAEEF@yahoo.com> Date: Sun, 21 Oct 2018 17:11:50 -0700 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <83E0D72D-04AD-48A6-89B0-4E4D6B79D749@yahoo.com> References: <2A425DE4-2B5B-474D-8B95-81890DE4D8A1@yahoo.com> <9D2A6528-F888-4833-A52B-8F9B4D66592C@yahoo.com> <30DD2F47-C8CB-4CEC-8563-C7083D0EAEEF@yahoo.com> To: Warner Losh X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 00:12:02 -0000 [Building and installing based on WITHOUT_ZFS=3D allows the resulting loader to work correctly on the 1950X.] On 2018-Oct-21, at 12:05 AM, Mark Millard wrote: > On 2018-Oct-20, at 10:32 PM, Warner Losh wrote: >=20 >> On Sat, Oct 20, 2018 at 11:04 PM Mark Millard = wrote: >> [I found what change lead to the 1950X boot crashing >> with BTX halted.] >>=20 >>> On 2018-Oct-20, at 12:44 PM, Mark Millard = wrote: >>>=20 >>>> [Adding some vintage information for a loader >>>> that allowed a native boot.] >>>>=20 >>>> On 2018-Oct-20, at 4:00 AM, Mark Millard = wrote: >>>>=20 >>>>> I attempted to jump from head -r334014 to -r339076 >>>>> on a threadripper 1950X board and the native >>>>> FreeBSD boot failed very early. (Hyper-V use of >>>>> the same media did not have this issue.) >>>>>=20 >>>>> But copying over an older /boot/loader from another >>>>> storage device with a FreeBSD head version that has >>>>> not been updated yet got past the problem being >>>>> reported here. (For other reasons, the kernel has >>>>> been moved back to -r338804 --and with that, >>>>> and the older /boot/loader, the 1950X native-boots >>>>> FreeBSD all the way just fine.) >>>>=20 >>>> I found one /boot/loader.old that was dated >>>> in the update'd file system as 2018-May 20, >>>> instead of 2018-Apr-03 from the older file >>>> system. May 20 would apparently mean a little >>>> below -r334014 . It native-booted okay, as did >>>> the April one. >>>>=20 >>>> [I do not know how to inspect a /boot/loader* >>>> to find out what -r?????? it is from.] >>>>=20 >>>> Unfortunately, I had done more than one -r339076 >>>> install from -r334014 before rebooting and >>>> no -r334014 loaders were still present: >>>> the other *.old files from a few minutes before >>>> the ones I had the boot problem with. >>>>=20 >>>> I might be able to extract loaders from various: >>>>=20 >>>> = https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz >>>>=20 >>>> materials and try substituting them in order to >>>> narrow the range for works -> fails. If I can, >>>> this likely would take a fair amount of time in >>>> my context. >>>>=20 >>>> Other notes: >>>>=20 >>>> It turns out that only Hyper-V based use needed >>>> a -r334804 kernel: Native booting with the older >>>> loaders and newer kernels works fine. >>>>=20 >>>> Windows 10 Pro 64bit also has no problems >>>> booting and operating the machine. >>>>=20 >>>> The native-boot problem does seem to be freeBSD >>>> loader-vintage specific. >>>>=20 >>>>> For the BTX failure the display ends up with >>>>> (hand transcribed, ". . ." for an omission): >>>>>=20 >>>>> BTX loader 1.00 BTX version is 1.02 >>>>> Console: internal video/keyboard >>>>> BIOS drive C: is disk0 >>>>> . . . >>>>> BIOS drive P: is disk13 >>>>> - >>>>> int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000096fd >>>>> eax=3D74d48000 ebx=3D74d4e5e0 ecx=3D00000011 edx=3D00000000 >>>>> esi=3D74d4e380 edi=3D74d4e5b0 ebp=3D00091da0 esp=3D00091d60 >>>>> cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 >>>>> cs:eip=3D66 f7 77 04 0f b7 c0 89-44 24 0c 89 5c 24 04 8b >>>>> 45 08 89 04 24 83 64 24-10 00 c7 44 24 08 01 00 >>>>> ss:esp=3D00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >>>>> 00 00 00 00 00 00 00 00-f0 1d 89 00 00 00 00 00 >>>>> BTX halted >>>>=20 >>>> I've no clue what of that output might be loader vintage >>>> specific. It might not be of use without knowing the >>>> exact build of the loader. >>>>=20 >>>>> The board is a GIGABYTE X399 AORUS Gaming 7 (rev 1.0). >>>>> It has 96 GiBytes of ECC RAM, just 6 DIMMs installed. >>>>=20 >>>> For reference for the board's BIOS: >>>>=20 >>>> Version: F11e >>>> Dated: 2018-Sep-17 >>>> Description: Update AGESA 1.1.0.1a >>>=20 >>> Using: >>>=20 >>> = https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/base.txz >>>=20 >>> materials I found that: >>>=20 >>> -r336492: worked (loader vs. zfsloader: not linked) >>> (no more amd64 builds until . . .) >>> -r336538: failed (loader vs. zfsloader: linked) >>>=20 >>> (Later ones that I tried also failed.) >>>=20 >>> Looks like this broke for booting the 1950X=20 >>> system in question when the following was >>> checked in: >>>=20 >>> Author: imp >>> Date: Fri Jul 20 05:17:37 2018 >>> New Revision: 336532 >>> URL:=20 >>> https://svnweb.freebsd.org/changeset/base/336532 >>>=20 >>>=20 >>> Log: >>> Collapse zfsloader functionality back down into loader. >>>=20 >> Yea, this shouldn't matter. It worked on all the systems I tried it = on. >>=20 >> So my first question: is this a ZFS system? Second, does it also have = UFS? If yes to both, which one do you want it to boot off of? >=20 > No zfs in use at all. It has been years since > I experimented with ZFS and reverted back to > UFS. >=20 > # gpart show -l > =3D> 40 937703008 da0 GPT (447G) > 40 1024 1 FBSDFSSDboot (512K) > 1064 746586112 2 FBSDFSSDroot (356G) > 746587176 31457280 3 FBSDFSSDswap (15G) > 778044456 159383552 4 FBSDFSSDswap2 (76G) > 937428008 275040 - free - (134M) > . . . >=20 > Doing: >=20 > gpart bootcode -p /boot/gptboot -i 1 da0 >=20 > and the trying a modern /boot/loader > did not change anything: still "BTX halted" > for a native boot. (No problem under Hyper-V.) I added WITHOUT_ZFS=3D to my equivalents of src.conf files for targeting amd64, built, and installed. The result native-boots just fine. The crash is somehow specific to loader code tied to LOADER_ZFS_SUPPORT being defined. Of course, this leaves me unable to native-boot an official, modern, unmodified build on the 1950X machine. While I do not actively use ZFS these days, I'd always left it built and installed in case I decided to do something with it at some point. I do not normally try to minimize configurations. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 00:14:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0315104C821 for ; Mon, 22 Oct 2018 00:14:12 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost2.sentex.ca", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CFB77DF08 for ; Mon, 22 Oct 2018 00:14:12 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5:0:0:0:11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w9M0EBkF052774 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 21 Oct 2018 20:14:11 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w9M0E87N092229; Sun, 21 Oct 2018 20:14:08 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: boot message: sendmsg on igb0: No buffer space available To: Dave Cottlehuber , FreeBSD-Current References: <1540024300.854927.1548557744.23034585@webmail.messagingengine.com> From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= xsBNBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAHNHG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT7CwHgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnnOwE0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAcLAXwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: Date: Sun, 21 Oct 2018 20:14:09 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1540024300.854927.1548557744.23034585@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Scanned-By: MIMEDefang 2.83 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, 22 Oct 2018 00:14:13 -0000 On 10/20/2018 4:31 AM, Dave Cottlehuber wrote: > On Fri, 19 Oct 2018, at 19:46, Mike Tancsa wrote: >> Feeding entropy: . >> lo0: link state changed to UP >> sendmsg on igb0: No buffer space available >> igb0: link state changed to UP >> cxl1: link state changed to UP >> Starting Network: lo0 igb0 cxl0 cxl1. > I=E2=80=99m reasonably sure that this occurs when dhclient is trying be= fore the > interface is available for use - is that likely in your case? Perhaps, but why the difference previous versions?=C2=A0 Should not the interface be up'd before starting dhclient ? =C2=A0=C2=A0=C2=A0 ---Mike From owner-freebsd-current@freebsd.org Mon Oct 22 00:28:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D7ACFD646A for ; Mon, 22 Oct 2018 00:28:00 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [104.225.8.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freebsd-11-64", Issuer "freebsd-11-64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C86BC7E8CA for ; Mon, 22 Oct 2018 00:27:59 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [104.225.8.138]) by mail.neu.net (8.15.2/8.15.2) with ESMTPS id w9M0Gqb3072447 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 21 Oct 2018 20:16:53 -0400 (EDT) (envelope-from andy@neu.net) Date: Sun, 21 Oct 2018 20:16:52 -0400 (EDT) From: AN To: freebsd-current@freebsd.org Subject: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error - portupgrade Message-ID: User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Status: No, score=0.0 required=2.9 tests=none autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.neu.net 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, 22 Oct 2018 00:28:00 -0000 Hi: Just upgraded a machine to 13-current: FreeBSD 13.0-CURRENT FreeBSD 13.0-CURRENT #18 r339556: Sun Oct 21 17:33:46 EDT 2018 root@sparc:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1300000 I deleted /usr/ports and did a fresh svnlite co into /usr/ports. When trying to rebuild all ports I get the following, it continues endlessly until ctrl/c. # portupgrade -vaf pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended ---> Session started at: Sun, 21 Oct 2018 19:02:02 -0400 [Reading data from pkg(8) ... pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended - 30 packages found - done] Fetching the ports index ... pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370670592:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1924: Any help is appreciated, thanks for reading. From owner-freebsd-current@freebsd.org Mon Oct 22 02:55:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BDAFFD9A49 for ; Mon, 22 Oct 2018 02:55:57 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic303-20.consmr.mail.ne1.yahoo.com (sonic303-20.consmr.mail.ne1.yahoo.com [66.163.188.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9838883D21 for ; Mon, 22 Oct 2018 02:55:56 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: VhEc3yYVM1k27JbELO4NkN7laW5z9kZeYwLQiUT6T.uyBpPw_0X33QJ0Y9exs52 yHjduUpNNJZ1Al4NKZh3p5drtqSW8Sxg92C6dVmaepk7IbYGz7e9xtO91p.S8OFSHkurb2xYQZ0. VbAeCfozjVG3uzidMiCmJ72bo7OhGdOiT.ESPt77Gp1GixbYXXZ7nnf0MloJxOsFLXoY_INH8Vke 4JBOCBWqAU.MSKevbmGbQnO3CSK0F_891BlvTT1Uu0PtWLZm70N6KEJUd_ByvH9iCw253VZ.73ch TuTNDsx1QVbmF67SOFuIIi5xrvB0YeF99w_wyxw3X5UXetArI0SoUqeNGXTRubzoUSUiPWP5FdB5 F7gJuLQWZh2xXRz8Il5O0ZxNeD.LjN4hW06X5MCyZG9lpKFwAW1v4uMRliaXfsYhz.55zIfqRhjC DFDThFihasvl5PtEP.eAXMDHEOT9_wLMlgjE_67pQ9Rk7t4i4dSBTsRfbcj891Fui5s_qptE28P. YgYc.LlB.zYxzoFpw6Lxzqj3Z4WRGN9MmMSAzawXkKNEc6Z7T0lfNgVw8Mq31n.Hhuen3VH_wAnB pWEQn_Q_tZJrGCQRwgDiJb9Y13EHDo77qClRxZmDeNSG9uae6U2oRdP2U9xM4YlIqaNiJZPEAkM3 BhvbVRqlDfB8V56Q0RWktd8gIgbEi70W13mon_A8WVlBC13G_nEI_Ib0hkoZ4OzqYWxnEdCbHsT1 voDYbKSUdp6TPNVv8b08i.t7fRwY.mEzU5STqw.psxCu1.DeA5ad5ifsDezXvk8uWc.DHIGFIGNF iXVCX7Zbx2xCSud2VGbYWhZCfkqsYU6_5hk3rCmfYS2L_7kGdPa32ywCWNnVLy4gQnr699hIKOw2 XzT.Iq.hpcC7fQoZcBC4JVEVtLAGRXw6qfyaQR5Y8TevBM_q4k3qW9OWD_GxO968F5KTJRoPGK2w PgwReTKid3O72BiDX.8EcUisQM.4e.GUWxiE6taro893QLR4eOWNEn4fyvppTjPptZSO0EXH7c_n EfCBx9Wkrarnxltpg9_XqJ59m.XN_3DYTXApZYPFIFFzBqKTnrRNhE9HkwGPDTMIq7aOd1mKfgq1 ._Z58 Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Mon, 22 Oct 2018 02:55:49 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp404.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 804ecb38ee3d4126093554721b6b1f8d; Mon, 22 Oct 2018 02:55:46 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated Date: Sun, 21 Oct 2018 19:55:45 -0700 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> To: Konstantin Belousov , FreeBSD Current , freebsd-stable@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 02:55:57 -0000 [I built based on WITHOUT_ZFS=3D for other reasons. But, after installing the build, Hyper-V based boots are working.] On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: >=20 >> I attempted to jump from head -r334014 to -r339076 >> on a threadripper 1950X board and the boot fails. >> This is both native booting and under Hyper-V, >> same machine and root file system in both cases. >=20 > I did my investigation under Hyper-V after seeing > a boot failure native. >=20 > Looks like the native failure is even earlier, > before db> is even possible, possibly during > early loader activity. >=20 > So this report is really for running under > Hyper-V: -r338804 boots and -r338810 does > not. By contrast -r334804 does not boot native. > (But I've little information for that context.) >=20 > Sorry for the confusion. I rushed the report > in hopes of getting to sleep. It was not to be. >=20 >> It fails just after the FreeBSD/SMP lines, >> reporting "kernel trap 9 with interrupts disabled". >>=20 >> It fails in pmap_force_invaldiate_cache_range at >> a clflusl (%rax) instruction that produces a >> "Fatal trap 9: general protection fault while >> in kernel mode". cpudid=3D0 apic id=3D 00 >>=20 >> I used kernel.txz files from: >>=20 >> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >>=20 >> to narrow the range of kernel builds for working -> failing >> and got: >>=20 >> -r338804 boots fine >> (no amd64 kernel builds between to try) >> -r338810+ fails (any that I tried, anyway) >>=20 >> In that range is -r338807 : >>=20 >> QUOTE >> Author: kib >> Date: Wed Sep 19 19:35:02 2018 >> New Revision: 338807 >> URL:=20 >> https://svnweb.freebsd.org/changeset/base/338807 >>=20 >>=20 >> Log: >> Convert x86 cache invalidation functions to ifuncs. >>=20 >> This simplifies the runtime logic and reduces the number of >> runtime-constant branches. >>=20 >> Reviewed by: alc, markj >> Sponsored by: The FreeBSD Foundation >> Approved by: re (gjb) >> Differential revision:=09 >> https://reviews.freebsd.org/D16736 >>=20 >> Modified: >> head/sys/amd64/amd64/pmap.c >> head/sys/amd64/include/pmap.h >> head/sys/dev/drm2/drm_os_freebsd.c >> head/sys/dev/drm2/i915/intel_ringbuffer.c >> head/sys/i386/i386/pmap.c >> head/sys/i386/i386/vm_machdep.c >> head/sys/i386/include/pmap.h >> head/sys/x86/iommu/intel_utils.c >> END QUOTE >>=20 >> There do seem to be changes associated with >> clflush(...) use. Looking at: >>=20 >> = https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=3D339= 432 >>=20 >> it appears that pmap_force_invalidate_cache_range has not >> changed since -r338807. >>=20 >> It seems that -r338806 and -r3388810 would be unlikely >> contributors. >=20 I went after my native-boot loader problem first because I could switch kernels via the loader for booting FreeBSD under Hyper-V. Switching loaders is more of a problem. In order to avoid the loader-time crash I switched to building installing based on WITHOUT_ZFS=3D . I've had no active use of ZFS in years. (The old official-build loaders that worked were non-ZFS ones.) This took care of the native-boot loader-crash --and, to my surprise, also the Hyper-V-boot kernel-time crash. My private builds now boot the 1950X in both contexts just fine. During my early investigation I did pick up specific changes from after -r339076 that seemed to be tied to Ryzen and such. (They made no difference to the boot problems at the time but I saw no reason to remove them.) # uname -apKU FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 r339076:339432M: Sun = Oct 21 16:44:25 PDT 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1200084 1200084 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 03:29:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39912FE598B for ; Mon, 22 Oct 2018 03:29:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B12A68514D for ; Mon, 22 Oct 2018 03:29:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2d.google.com with SMTP id e126so28676499vsc.9 for ; Sun, 21 Oct 2018 20:29:02 -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=9pm7BX5piXUzbLjtx4i7rZTJvhkWQAPzMzflVHKzHzA=; b=r7Bja/HtGDUwvRQk7RMVscP2SBVmbtinMhtyIWn/BAI/QFdiGW34DwakBZvOBO3TXh fwjggsbyS1kGGdfWzPU6V4DmKjfZ66rwbwnLA5AAa4XBs35+nJXdKnMcYaZlrwzsxXZF vdwZj7tmrlZgsKzA/czD4HGapxyankcBmqkfGtCGkNu4ixA7nbHBWdxkQh/aofUnTEA0 ZcVqx7gKukXfBNEXWHx5pNWdiPlfoDY7e4FWPR/0j3JIGLH67OD8xoSLqSLZ56uDPyYK XdoSJQ/aUZ1Hqg+YbDvH1EDOoeZyUcLKRTTBp5KwjOtB8/KypPqevZ0E0w5+3K3ShdCD 7XAg== 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=9pm7BX5piXUzbLjtx4i7rZTJvhkWQAPzMzflVHKzHzA=; b=RJxrLqfZ/xzZ/H04vTgieHeKrD+eCD71pZKwRNguE1fk5yUvofq2KGBO2RifbupeSf PImVGf/ajG7QhnFOs0YWLsEGVXQ7Pig0CZyDZ2wCX4raVyn7+4xVERMKnMKs7FrvcVxe RLZe70m00FHdrAQjeql3sVTEyfRDsgk5v7T5LfuR7IXt7uIdYr9dKFU86DKoXzG7wFyb kvpAzq0aflAvXcqRGbwXsuQGOkSCfF3R4QC7O7NOoHEqJtFgtplem9s9MN/EZ8Pc1Y7w bMPTHMxznzzaVJTqXpWo5kt0dSnsUxaoBH+iVyxR+s8aCkI+DgoImFzn0XjtufbyPqYI 6sgA== X-Gm-Message-State: ABuFfogTxCPZhbABCULCGd6BZiBk+n+pRlLBq04UJmKyJVXCYkbibocJ hXldrOQO4OjLM+03R55bt2CSgrZCv8psdv0CC/eV+A== X-Google-Smtp-Source: ACcGV606LRAE5fUoQyP7pGPBP3ltaPXRBVSTKjYaqkORID371gRbPcsm5s8Tsfn2UVtrtu1/eafnbFdO/EK8mE6qfUE= X-Received: by 2002:a67:4dc7:: with SMTP id i68mr18183109vsg.46.1540178942064; Sun, 21 Oct 2018 20:29:02 -0700 (PDT) MIME-Version: 1.0 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> In-Reply-To: From: Warner Losh Date: Sun, 21 Oct 2018 21:28:51 -0600 Message-ID: Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated To: Mark Millard Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List 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, 22 Oct 2018 03:29:03 -0000 On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < freebsd-stable@freebsd.org> wrote: > [I built based on WITHOUT_ZFS= for other reasons. But, > after installing the build, Hyper-V based boots are > working.] > > On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > > > On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: > > > >> I attempted to jump from head -r334014 to -r339076 > >> on a threadripper 1950X board and the boot fails. > >> This is both native booting and under Hyper-V, > >> same machine and root file system in both cases. > > > > I did my investigation under Hyper-V after seeing > > a boot failure native. > > > > Looks like the native failure is even earlier, > > before db> is even possible, possibly during > > early loader activity. > > > > So this report is really for running under > > Hyper-V: -r338804 boots and -r338810 does > > not. By contrast -r334804 does not boot native. > > (But I've little information for that context.) > > > > Sorry for the confusion. I rushed the report > > in hopes of getting to sleep. It was not to be. > > > >> It fails just after the FreeBSD/SMP lines, > >> reporting "kernel trap 9 with interrupts disabled". > >> > >> It fails in pmap_force_invaldiate_cache_range at > >> a clflusl (%rax) instruction that produces a > >> "Fatal trap 9: general protection fault while > >> in kernel mode". cpudid=0 apic id= 00 > >> > >> I used kernel.txz files from: > >> > >> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ > >> > >> to narrow the range of kernel builds for working -> failing > >> and got: > >> > >> -r338804 boots fine > >> (no amd64 kernel builds between to try) > >> -r338810+ fails (any that I tried, anyway) > >> > >> In that range is -r338807 : > >> > >> QUOTE > >> Author: kib > >> Date: Wed Sep 19 19:35:02 2018 > >> New Revision: 338807 > >> URL: > >> https://svnweb.freebsd.org/changeset/base/338807 > >> > >> > >> Log: > >> Convert x86 cache invalidation functions to ifuncs. > >> > >> This simplifies the runtime logic and reduces the number of > >> runtime-constant branches. > >> > >> Reviewed by: alc, markj > >> Sponsored by: The FreeBSD Foundation > >> Approved by: re (gjb) > >> Differential revision: > >> https://reviews.freebsd.org/D16736 > >> > >> Modified: > >> head/sys/amd64/amd64/pmap.c > >> head/sys/amd64/include/pmap.h > >> head/sys/dev/drm2/drm_os_freebsd.c > >> head/sys/dev/drm2/i915/intel_ringbuffer.c > >> head/sys/i386/i386/pmap.c > >> head/sys/i386/i386/vm_machdep.c > >> head/sys/i386/include/pmap.h > >> head/sys/x86/iommu/intel_utils.c > >> END QUOTE > >> > >> There do seem to be changes associated with > >> clflush(...) use. Looking at: > >> > >> > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=339432 > >> > >> it appears that pmap_force_invalidate_cache_range has not > >> changed since -r338807. > >> > >> It seems that -r338806 and -r3388810 would be unlikely > >> contributors. > > > > I went after my native-boot loader problem first because I > could switch kernels via the loader for booting FreeBSD under > Hyper-V. Switching loaders is more of a problem. > > In order to avoid the loader-time crash I switched to building > installing based on WITHOUT_ZFS= . I've had no active use of > ZFS in years. (The old official-build loaders that worked were > non-ZFS ones.) > > This took care of the native-boot loader-crash --and, to my > surprise, also the Hyper-V-boot kernel-time crash. > > My private builds now boot the 1950X in both contexts just > fine. > > During my early investigation I did pick up specific changes > from after -r339076 that seemed to be tied to Ryzen and such. > (They made no difference to the boot problems at the time > but I saw no reason to remove them.) > > # uname -apKU > FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 r339076:339432M: Sun > Oct 21 16:44:25 PDT 2018 markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-NODBG > amd64 amd64 1200084 1200084 > The phrase "no active use" bothers me. What does that mean? Are there any Warner From owner-freebsd-current@freebsd.org Mon Oct 22 03:30:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CF84FE5A60 for ; Mon, 22 Oct 2018 03:30:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5365585328 for ; Mon, 22 Oct 2018 03:30:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe33.google.com with SMTP id i10so28643674vsm.13 for ; Sun, 21 Oct 2018 20:30:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:from:date:message-id:subject:to:cc; bh=Ht5DIerp556qK0YwFNRGn4D34h+CICXjOmHriUjRbMY=; b=jhOm6EgDYtSEDKy4mn2nndadRCMlAOO1f+TFYoAQNdNHfLx3yYHGsVGJ9TY++473fe fVDk5nwfgUU67NqMKhb7ox5XOvVitGAUUAeFAns5HKc8XsVk0Rm1Tj7oDl94ITc5QMxP biVO7ZddCzhgfGINPGh6piaKh7mTgxB5dJD8hCiVl/+ubknPNMW0+74T68mLDSIhGdbP B+MnJ6QQe7V5AijrwGhj98O8PH8CnGmUKgI0br+atUDb0U/C116pj9WRkMnNBc7qcy70 G/qxm/WzEr/Jqnads7IEBWSOg7bQPFch2mdkk7vo9KR03a1doFcMa8N5bnPlbR58k6g7 Yu1g== 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:from:date:message-id :subject:to:cc; bh=Ht5DIerp556qK0YwFNRGn4D34h+CICXjOmHriUjRbMY=; b=nvs4kjYJgLJubbUhNa9ZbYY5B6Pn4FRJFead7HYwEDNq/k4V/n0EizRssSlzag3W2/ zWDggFOiy4EcYn6t66isDYrg+byF+VgA6TEMSpDL5W9ou1YXSKXBlGCBD50BHuy0yvLo QvzYr6Krg+XO966gp5vF4RUGsFCsITgUrgbR4IGakHlL5UQssupvG/9YzMmcfywg+4EO B4eJJmlucT9uxmN/453p+I2G29OgKh3ucyOdKMsf4s4cT7lsneM9V8d5ZrMzijNabrqb IvUl7zhevBKXsaFGCxWsDnJCCSbe+s2wtVd5etDBEelHrulZxYmL1eE8h9E665oJO16a e7kA== X-Gm-Message-State: ABuFfohh6V4bMA2XjDkcoHg0xHOXUVAHZeQmA39j013LVjuE6xMJM/+K q3dD5wnHNEoIH5Dypeu6GNAXP6R6uwzvOz73BGVB54cm X-Google-Smtp-Source: ACcGV61ItgNznFjKRg5GoRmi7YvDINjSnwPzyRMxqliqgxGcug0W/UH/SIQuJC2ODSju2XM5pwb/aYjuBFtNm8GY3+c= X-Received: by 2002:a67:2704:: with SMTP id n4mr18714119vsn.209.1540179014632; Sun, 21 Oct 2018 20:30:14 -0700 (PDT) MIME-Version: 1.0 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> From: Warner Losh Date: Sun, 21 Oct 2018 21:30:03 -0600 Message-ID: Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated To: Mark Millard Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List 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, 22 Oct 2018 03:30:16 -0000 On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < > freebsd-stable@freebsd.org> wrote: > >> [I built based on WITHOUT_ZFS= for other reasons. But, >> after installing the build, Hyper-V based boots are >> working.] >> >> On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: >> >> > On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: >> > >> >> I attempted to jump from head -r334014 to -r339076 >> >> on a threadripper 1950X board and the boot fails. >> >> This is both native booting and under Hyper-V, >> >> same machine and root file system in both cases. >> > >> > I did my investigation under Hyper-V after seeing >> > a boot failure native. >> > >> > Looks like the native failure is even earlier, >> > before db> is even possible, possibly during >> > early loader activity. >> > >> > So this report is really for running under >> > Hyper-V: -r338804 boots and -r338810 does >> > not. By contrast -r334804 does not boot native. >> > (But I've little information for that context.) >> > >> > Sorry for the confusion. I rushed the report >> > in hopes of getting to sleep. It was not to be. >> > >> >> It fails just after the FreeBSD/SMP lines, >> >> reporting "kernel trap 9 with interrupts disabled". >> >> >> >> It fails in pmap_force_invaldiate_cache_range at >> >> a clflusl (%rax) instruction that produces a >> >> "Fatal trap 9: general protection fault while >> >> in kernel mode". cpudid=0 apic id= 00 >> >> >> >> I used kernel.txz files from: >> >> >> >> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >> >> >> >> to narrow the range of kernel builds for working -> failing >> >> and got: >> >> >> >> -r338804 boots fine >> >> (no amd64 kernel builds between to try) >> >> -r338810+ fails (any that I tried, anyway) >> >> >> >> In that range is -r338807 : >> >> >> >> QUOTE >> >> Author: kib >> >> Date: Wed Sep 19 19:35:02 2018 >> >> New Revision: 338807 >> >> URL: >> >> https://svnweb.freebsd.org/changeset/base/338807 >> >> >> >> >> >> Log: >> >> Convert x86 cache invalidation functions to ifuncs. >> >> >> >> This simplifies the runtime logic and reduces the number of >> >> runtime-constant branches. >> >> >> >> Reviewed by: alc, markj >> >> Sponsored by: The FreeBSD Foundation >> >> Approved by: re (gjb) >> >> Differential revision: >> >> https://reviews.freebsd.org/D16736 >> >> >> >> Modified: >> >> head/sys/amd64/amd64/pmap.c >> >> head/sys/amd64/include/pmap.h >> >> head/sys/dev/drm2/drm_os_freebsd.c >> >> head/sys/dev/drm2/i915/intel_ringbuffer.c >> >> head/sys/i386/i386/pmap.c >> >> head/sys/i386/i386/vm_machdep.c >> >> head/sys/i386/include/pmap.h >> >> head/sys/x86/iommu/intel_utils.c >> >> END QUOTE >> >> >> >> There do seem to be changes associated with >> >> clflush(...) use. Looking at: >> >> >> >> >> https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=339432 >> >> >> >> it appears that pmap_force_invalidate_cache_range has not >> >> changed since -r338807. >> >> >> >> It seems that -r338806 and -r3388810 would be unlikely >> >> contributors. >> > >> >> I went after my native-boot loader problem first because I >> could switch kernels via the loader for booting FreeBSD under >> Hyper-V. Switching loaders is more of a problem. >> >> In order to avoid the loader-time crash I switched to building >> installing based on WITHOUT_ZFS= . I've had no active use of >> ZFS in years. (The old official-build loaders that worked were >> non-ZFS ones.) >> >> This took care of the native-boot loader-crash --and, to my >> surprise, also the Hyper-V-boot kernel-time crash. >> >> My private builds now boot the 1950X in both contexts just >> fine. >> >> During my early investigation I did pick up specific changes >> from after -r339076 that seemed to be tied to Ryzen and such. >> (They made no difference to the boot problems at the time >> but I saw no reason to remove them.) >> >> # uname -apKU >> FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 r339076:339432M: Sun >> Oct 21 16:44:25 PDT 2018 markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-NODBG >> amd64 amd64 1200084 1200084 > > (stupid gmail) The phrase "no active use" bothers me. What does that mean? Are there any ZFS pools or any disks that any whiff of ZFSish thing on it at all? Clearly, there's something in the zfs boot loader that's freaking out by something on your system, but absent that information I can't help you. Warner From owner-freebsd-current@freebsd.org Mon Oct 22 03:34:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A07AFE7070 for ; Mon, 22 Oct 2018 03:34:59 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1860A85B58 for ; Mon, 22 Oct 2018 03:34:59 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x332.google.com with SMTP id y144-v6so8709367wmd.4 for ; Sun, 21 Oct 2018 20:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=mq9K3lAhXg7yOeYzjTv0PjVuuLlY+jXNBtV5kmN1BpU=; b=jpC0ulSr2KUwkV+irBJ8i+fTHSR6IYZpdpJbT2c5f/nrjXF5gO7E8HlqnT4zkkEVP1 FvZhC31CC3X2TiKOHSm95gCeCDzMP5FI7DzVixh0THpXUgBJ+B6NI3nxkk06LzGUAKAv A3Q6QV253JIkpJc8F+78GBjz/9Y0Do9ry0SOsQyvVP4ZZC29MKRGmzVDJdVN58j6j8pj Q6SM1jWCqVQ6UHLnGupZ6yRIUWnQTIoLkqeND14eo9t26R0h6QbiAacKtHQPykRMKVWp unIjfZxsZ1AzlBOIKIpWwJLLwlTaKDNIHm8XLhBdRX/cD4vxy/J7joHoVjG2k+oWXiIp KfPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=mq9K3lAhXg7yOeYzjTv0PjVuuLlY+jXNBtV5kmN1BpU=; b=At3ZOe8ehgeA0m/gvGuHCEdV4N7sYTyc+G9jj3Vmq9AoBJ9HNzEdfF+9TrE9FfCZl7 f5hqCTOj6Dng7/2fiY4XMGTUAB/rnR1jLU7lwzfRbGDkjdWnrWWP6CvZ/wU2sTImD14I qTZfmKy1VsA3Y3QFDgUe2T992Xbti51xPiR1tgtUnpbwsx4ivTdUKX4S6cUk+eleWM14 SxP1QM/fQyrc5tlIeeivmNFO0t8PLMG1wYFwFavQ/eeHpEyDpjfnK/HCgy9SWkfIozLE 9TlqHbMFzctQvgGgLW3d9lEhT24GyYqJah34T3s1xoWzXdoZvoKYaotmYs3w7kGqJtsM Mc/Q== X-Gm-Message-State: ABuFfogB1qNZYfJIWXtuOEUAhmgHiMhOuksOB+BR6aHZ3ZDKV1L0dDDg o1ai6Q4mz98QH1a6TEv7r0WjdB09+II= X-Google-Smtp-Source: ACcGV61/qKyuDuWt0yLStFaVU7/VH1SPMsWVqIX/E4+lIq8Pp1syUHiavBll/NirrxTXry4zUOh7sQ== X-Received: by 2002:a1c:3403:: with SMTP id b3-v6mr13900797wma.108.1540179296924; Sun, 21 Oct 2018 20:34:56 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id 199-v6sm7731057wme.39.2018.10.21.20.34.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Oct 2018 20:34:56 -0700 (PDT) Subject: Re: DRM: radeonkms no longer usable following a switch to stable, FreeBSD 12.0-BETA1 From: Graham Perrin To: FreeBSD Current References: <16278ced-e565-917f-5015-5083d2171bb0@gmail.com> Message-ID: <81d1e9cc-cdfe-81ec-1168-54b2fa397c59@gmail.com> Date: Mon, 22 Oct 2018 04:34:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <16278ced-e565-917f-5015-5083d2171bb0@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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: Mon, 22 Oct 2018 03:34:59 -0000 tl;dr it seems that rc.conf can handle radeonkms and sddm _if_ I enable CSM at boot _and if_ I have: /usr/local/etc/X11/xorg.conf.d/driver-vesa.conf Not truly benefiting from radeonkms. AFAICT if I exclude the VESA workaround and manually load radeonkmos and start sddm, then as previously noted: … /usr/local/bin/xauth: (stdin):1:  bad "remove" command line /usr/local/bin/xauth: (stdin):2:  bad "add" command line /usr/local/bin/xauth: (stdin):1:  bad "remove" command line /usr/local/bin/xauth: (stdin):2:  bad "add" command line … What next? Any suggestions? TIA ---- root@momh167-gjp4-hpelitebook8570p-freebsd:~ # date ; uname -v Mon 22 Oct 2018 04:10:51 BST FreeBSD 12.0-BETA1 GENERIC root@momh167-gjp4-hpelitebook8570p-freebsd:~ # poudriere jail -i -j stable | grep r3 Jail vcs version:  r339435 root@momh167-gjp4-hpelitebook8570p-freebsd:~ # poudriere ports -u [00:00:00] Updating portstree "default" with portsnap...Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date.  done root@momh167-gjp4-hpelitebook8570p-freebsd:~ # poudriere bulk -j stable graphics/gpu-firmware-kmod graphics/drm-kmod graphics/drm-next-kmod x11/xorg[00:00:01] Creating the reference jail... done [00:00:02] Mounting system devices for stable-default [00:00:02] Mounting ports/packages/distfiles [00:00:02] Stashing existing package repository [00:00:02] Mounting ccache from: /var/cache/ccache [00:00:02] Mounting packages from: /usr/local/poudriere/data/packages/stable-default [00:00:02] Copying /var/db/ports from: /usr/local/etc/poudriere.d/options [00:00:03] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf -> /usr/local/poudriere/data/.m/stable-default/ref/etc/resolv.conf [00:00:03] Starting jail stable-default [00:00:06] Logs: /usr/local/poudriere/data/logs/bulk/stable-default/2018-10-22_04h12m09s [00:00:06] Loading MOVED for /usr/local/poudriere/data/.m/stable-default/ref/usr/ports [00:00:07] Ports supports: FLAVORS SELECTED_OPTIONS [00:00:07] Gathering ports metadata [00:00:18] Calculating ports order and dependencies [00:00:19] Sanity checking the repository [00:00:19] Checking packages for incremental rebuild needs [00:00:34] Deleting stale symlinks... done [00:00:34] Deleting empty directories... done [00:00:34] Cleaning the build queue [00:00:34] Sanity checking build queue [00:00:34] Processing PRIORITY_BOOST [00:00:34] Balancing pool [00:00:34] Recording filesystem state for prepkg... done [00:00:40] No package built, no need to update the repository [00:00:40] Committing packages to repository [00:00:40] Removing old packages [stable-default] [2018-10-22_04h12m09s] [committing:] Queued: 0  Built: 0  Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 0   Time: 00:00:34 [00:00:40] Logs: /usr/local/poudriere/data/logs/bulk/stable-default/2018-10-22_04h12m09s [00:00:40] Cleaning up [00:00:40] Unmounting file systems root@momh167-gjp4-hpelitebook8570p-freebsd:~ # pkg which /usr/local/bin/xauth /usr/local/bin/xauth was installed by package xauth-1.0.10 root@momh167-gjp4-hpelitebook8570p-freebsd:~ # pkg query '%o %v %R' gpu-firmware-kmod drm-kmod drm-next-kmod xorg graphics/gpu-firmware-kmod g20180825 poudriere graphics/drm-kmod g20180930 poudriere graphics/drm-next-kmod 4.11.g20180822 poudriere x11/xorg 7.7_3 poudriere root@momh167-gjp4-hpelitebook8570p-freebsd:~ # cat /usr/local/etc/X11/xorg.conf.d/driver-vesa.conf Section "Device"   Identifier "Card0"   Driver "vesa" EndSection root@momh167-gjp4-hpelitebook8570p-freebsd:~ # grep 'adeon\|sddm' /etc/rc.conf # kldload radeonkms kld_list="/boot/modules/radeonkms.ko" sddm_enable="YES" root@momh167-gjp4-hpelitebook8570p-freebsd:~ # From owner-freebsd-current@freebsd.org Mon Oct 22 06:24:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92195FEB022 for ; Mon, 22 Oct 2018 06:24:48 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic302-20.consmr.mail.gq1.yahoo.com (sonic302-20.consmr.mail.gq1.yahoo.com [98.137.68.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1452B8A947 for ; Mon, 22 Oct 2018 06:24:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: ErJBlfwVM1lfgwU6ltYo8BAg0SJQD7.4XnuSdvhbbh6XYcvxnlNyIKEtDbthJkb 5WJYfDF3JzNMxa5s6mY3GwqWjMh4f7KgphAZh_bABXJWDllGuEKNBiVUZNT5aWOr2jt1a59lXeNc Rq5oRj6T0rsaKOPiUrgVDGiUU85IWiTUfCm8zdZuCITHoM8g8yGggNBBtiDoq2hfWIYQopN_odwE eOt6LyzkTsry0uw5.xKclpYo2atTdfwfoAyli66rITFq4OUvWs55gvTymD4nvkVJi2lRRNorp86v y8f.pfr9sijGagUexB35bmB.Oj_Apj45lzewZp_9xZsk9TOE_T3FBDew9EQ1KDY8kIvXl9hIKXbu 6MdeBPlHdVveyo0WdLEG3sNZ5f_TrC39lU7a5.wnqMn8dFxh4Cpat6ZPgWDWf_gPQkafaIrRX5fc 4n7rTTG2_5LQW3DrNIrMMKvRMZlyyYtQr1Uuhn01Ll7Sg_zDmLen9A_76pgFJBvgq3bZzopey_Fz zFo0So_05fM4vQmZCoRU_Kh5MjiMr6Q7LsmhPCVT7ZU7Vthn4ZzCicxSJd6vZHImKapyL8JixfK5 1xy_kPdvDI4N10.aDv2FRwFx.uEeWmaqhD7GWuZZpk7ofr0CzU9xJCjtx_Td76Y3aALc6WBnDr2O d9XswEmMqtpqx9M6fNxICiBEoHQIQteRXcTd1tTWpJqwO0ZVZn3eu5_I_5.0GhzLslQe6QKSsFUR iTpkyvVL8DQs3x7N8megRp1oRJYR2cLFixHDI4GI4_tXoxwkj2syr7exmgz8.wDIHECEGuHyAZNA 7FPDmmpHEEr61FdJUr9fF7q7GbJj3Ku7PWkohaIXa6CsuWcr3TOMZS2SKycqApPTlRtaja7yYxja Dp78XD3LXU2Vzb44o8yorgdvkNXC1aUtYrinrFdtgAmQKsLbjl18zb9DvbeZImcIXG7BvhWwPeQB jnO6YmLI8HoiG.W7YvM8HDOcjzU9cjfKOl6JyhkFDn9Nb8obJd84ppv139z6P5iVgGSW6wfHfcWB etiokcpLtKM_zw8mgXd4SzRXUar4dA1xD3GWHIXZMTHaRiPyUoPN1_7n8hLgzpNZLRtkecVUWKOn jqtHs8x4- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.gq1.yahoo.com with HTTP; Mon, 22 Oct 2018 06:24:46 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp420.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID df388ffb0415382608330f6a339da29d; Mon, 22 Oct 2018 06:24:44 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: Date: Sun, 21 Oct 2018 23:24:43 -0700 Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <50C22D2F-0D72-4485-9AE2-E22EC336F8CB@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> To: Warner Losh X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 06:24:48 -0000 On 2018-Oct-21, at 8:30 PM, Warner Losh wrote: > On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >=20 > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable = wrote: >> [I built based on WITHOUT_ZFS=3D for other reasons. But, >> after installing the build, Hyper-V based boots are >> working.] >>=20 >> On 2018-Oct-20, at 2:09 AM, Mark Millard = wrote: >>=20 >> > On 2018-Oct-20, at 1:39 AM, Mark Millard = wrote: >> >=20 >> >> I attempted to jump from head -r334014 to -r339076 >> >> on a threadripper 1950X board and the boot fails. >> >> This is both native booting and under Hyper-V, >> >> same machine and root file system in both cases. >> >=20 >> > I did my investigation under Hyper-V after seeing >> > a boot failure native. >> >=20 >> > Looks like the native failure is even earlier, >> > before db> is even possible, possibly during >> > early loader activity. >> >=20 >> > So this report is really for running under >> > Hyper-V: -r338804 boots and -r338810 does >> > not. By contrast -r334804 does not boot native. >> > (But I've little information for that context.) >> >=20 >> > Sorry for the confusion. I rushed the report >> > in hopes of getting to sleep. It was not to be. >> >=20 >> >> It fails just after the FreeBSD/SMP lines, >> >> reporting "kernel trap 9 with interrupts disabled". >> >>=20 >> >> It fails in pmap_force_invaldiate_cache_range at >> >> a clflusl (%rax) instruction that produces a >> >> "Fatal trap 9: general protection fault while >> >> in kernel mode". cpudid=3D0 apic id=3D 00 >> >>=20 >> >> I used kernel.txz files from: >> >>=20 >> >> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >> >>=20 >> >> to narrow the range of kernel builds for working -> failing >> >> and got: >> >>=20 >> >> -r338804 boots fine >> >> (no amd64 kernel builds between to try) >> >> -r338810+ fails (any that I tried, anyway) >> >>=20 >> >> In that range is -r338807 : >> >>=20 >> >> QUOTE >> >> Author: kib >> >> Date: Wed Sep 19 19:35:02 2018 >> >> New Revision: 338807 >> >> URL:=20 >> >> https://svnweb.freebsd.org/changeset/base/338807 >> >>=20 >> >>=20 >> >> Log: >> >> Convert x86 cache invalidation functions to ifuncs. >> >>=20 >> >> This simplifies the runtime logic and reduces the number of >> >> runtime-constant branches. >> >>=20 >> >> Reviewed by: alc, markj >> >> Sponsored by: The FreeBSD Foundation >> >> Approved by: re (gjb) >> >> Differential revision: =20 >> >> https://reviews.freebsd.org/D16736 >> >>=20 >> >> Modified: >> >> head/sys/amd64/amd64/pmap.c >> >> head/sys/amd64/include/pmap.h >> >> head/sys/dev/drm2/drm_os_freebsd.c >> >> head/sys/dev/drm2/i915/intel_ringbuffer.c >> >> head/sys/i386/i386/pmap.c >> >> head/sys/i386/i386/vm_machdep.c >> >> head/sys/i386/include/pmap.h >> >> head/sys/x86/iommu/intel_utils.c >> >> END QUOTE >> >>=20 >> >> There do seem to be changes associated with >> >> clflush(...) use. Looking at: >> >>=20 >> >> = https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=3D339= 432 >> >>=20 >> >> it appears that pmap_force_invalidate_cache_range has not >> >> changed since -r338807. >> >>=20 >> >> It seems that -r338806 and -r3388810 would be unlikely >> >> contributors. >> >=20 >>=20 >> I went after my native-boot loader problem first because I >> could switch kernels via the loader for booting FreeBSD under >> Hyper-V. Switching loaders is more of a problem. >>=20 >> In order to avoid the loader-time crash I switched to building >> installing based on WITHOUT_ZFS=3D . I've had no active use of >> ZFS in years. (The old official-build loaders that worked were >> non-ZFS ones.) >>=20 >> This took care of the native-boot loader-crash --and, to my >> surprise, also the Hyper-V-boot kernel-time crash. >>=20 >> My private builds now boot the 1950X in both contexts just >> fine. >>=20 >> During my early investigation I did pick up specific changes >> from after -r339076 that seemed to be tied to Ryzen and such. >> (They made no difference to the boot problems at the time >> but I saw no reason to remove them.) >>=20 >> # uname -apKU >> FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 r339076:339432M: = Sun Oct 21 16:44:25 PDT 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG amd64 amd64 1200084 1200084 >>=20 >> (stupid gmail)=20 >=20 > The phrase "no active use" bothers me. What does that mean? Are there = any ZFS pools or any disks that any whiff of ZFSish thing on it at all? = Clearly, there's something in the zfs boot loader that's freaking out by = something on your system, but absent that information I can't help you. No ZFS pools: Strictly UFS for FreeBSD file systems for the last few years, UFS before I had access to the 1950X system. I've never before bothered to use WITHOUT_ZFS=3D in my builds. So the system had the ZFS support, such as kernel modules, over all the time that this system had been in use. Prior to the recent versions I saw no such problems. But the default loader was not ZFS capable. As seen in the under-Hyper-V use-context: # gpart show -p =3D> 40 937703008 da0 GPT (447G) 40 1024 da0p1 freebsd-boot (512K) 1064 746586112 da0p2 freebsd-ufs (356G) 746587176 31457280 da0p3 freebsd-swap (15G) 778044456 159383552 da0p4 freebsd-swap (76G) 937428008 275040 - free - (134M) =3D> 40 937703008 da1 GPT (447G) 40 1024 da1p1 freebsd-boot (512K) 1064 369098752 da1p2 freebsd-ufs (176G) 369099816 406846424 da1p3 freebsd-swap (194G) 775946240 130024488 - free - (62G) 905970728 31457280 da1p4 freebsd-swap (15G) 937428008 275040 - free - (134M) =3D> 40 419430320 da2 GPT (200G) 40 4056 - free - (2.0M) 4096 419426263 da2p1 freebsd-ufs (200G) 419430359 1 - free - (512B) =3D> 40 2000409184 da3 GPT (954G) 40 1024 da3p1 freebsd-boot (512K) 1064 2000408159 da3p2 freebsd-ufs (954G) 2000409223 1 - free - (512B) So no ZFS pools. The above context never had the ZFS-capable loader problem but did have the kernel problem. I was booting the 356G freebsd-ufs partition: the only one that I have updated the FreeBSD version on so far. FreeBSD booted natively more drives are seen in gpart show, some not from/for FreeBSD. But the above drives are present and I was booting from the same partition of the same drive: the 356G freebsd-ufs partition. Still no ZFS pools anywhere: # gpart show -p =3D> 34 4000797293 nvd0 GPT (1.9T) 34 262144 nvd0p1 ms-reserved (128M) 262178 2014 - free - (1.0M) 264192 3600451584 nvd0p2 ms-basic-data (1.7T) 3600715776 400081551 - free - (191G) =3D> 40 937703008 nvd1 GPT (447G) 40 1024 nvd1p1 freebsd-boot (512K) 1064 746586112 nvd1p2 freebsd-ufs (356G) 746587176 31457280 nvd1p3 freebsd-swap (15G) 778044456 159383552 nvd1p4 freebsd-swap (76G) 937428008 275040 - free - (134M) =3D> 40 937703008 nvd2 GPT (447G) 40 1024 nvd2p1 freebsd-boot (512K) 1064 369098752 nvd2p2 freebsd-ufs (176G) 369099816 406846424 nvd2p3 freebsd-swap (194G) 775946240 130024488 - free - (62G) 905970728 31457280 nvd2p4 freebsd-swap (15G) 937428008 275040 - free - (134M) =3D> 34 2000409197 nvd3 GPT (954G) 34 2014 - free - (1.0M) 2048 1021952 nvd3p1 ms-recovery (499M) 1024000 202752 nvd3p2 efi (99M) 1226752 32768 nvd3p3 ms-reserved (16M) 1259520 1859119104 nvd3p4 ms-basic-data (886G) 1860378624 140030607 - free - (67G) =3D> 40 2000409184 nvd4 GPT (954G) 40 1024 nvd4p1 freebsd-boot (512K) 1064 2000408159 nvd4p2 freebsd-ufs (954G) 2000409223 1 - free - (512B) =3D> 63 2000409201 ada0 MBR (954G) 63 1985 - free - (993K) 2048 4096 ada0s1 linux-data (2.0M) 6144 2093056 - free - (1.0G) 2099200 1998309376 ada0s2 linux-lvm (953G) 2000408576 688 - free - (344K) =3D> 34 2000409197 ada1 GPT (954G) 34 262144 ada1p1 ms-reserved (128M) 262178 2000147053 - free - (954G) =3D> 34 2000409197 ada2 GPT (954G) 34 262144 ada2p1 ms-reserved (128M) 262178 2000147053 - free - (954G) =3D> 34 1953497022 da0 GPT (932G) 34 262144 da0p1 ms-reserved (128M) 262178 2014 - free - (1.0M) 264192 1953230848 da0p2 ms-basic-data (931G) 1953495040 2016 - free - (1.0M) =3D> 1 60062499 da1 MBR (29G) 1 31 - free - (16K) 32 60062468 da1s1 fat32lba (29G) The 356G freebsd-ufs partition is the only one of the freebsd-ufs partitions updated so far. This is the context that had the problem with the ZFS-capable loaders --but no later kernel problem when a not-ZFS-capable loader was used (via copying over an older one --until I did the WITHOUT_ZFS=3D build/install). As for the ZFS-capable loader: May it has problems when it sees one or more of: ms-reserved (on GPT) ms-basic-data (on GPT) (NTFS file system) ms-recovery (on GPT) efi (on GPT) linux-data (on MBR) linux-lvm (on MBR) fat32lba (on MBR) (given that none of these is available in the Hyper-V context as the virtual machine has been configured). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 09:01:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDC54FF01B0 for ; Mon, 22 Oct 2018 09:01:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 62C088FD51 for ; Mon, 22 Oct 2018 09:01:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2814CFF01AE; Mon, 22 Oct 2018 09:01:21 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16F97FF01AB for ; Mon, 22 Oct 2018 09:01:21 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 AEA0B8FC4C for ; Mon, 22 Oct 2018 09:01:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [178.17.145.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 7A414260174; Mon, 22 Oct 2018 11:01:13 +0200 (CEST) Subject: Re: Page fault in midi/sequencer.c To: Peter Holm , current@freebsd.org References: <20181020165604.GA4946@x2.osted.lan> From: Hans Petter Selasky Message-ID: Date: Mon, 22 Oct 2018 11:00:41 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <20181020165604.GA4946@x2.osted.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 22 Oct 2018 09:01:21 -0000 On 10/20/18 6:56 PM, Peter Holm wrote: > I can trigger this on 13.0-CURRENT r339445 with a non-root test program: > Hi, The following commits should fix the issues you experience: https://svnweb.freebsd.org/changeset/base/339581 https://svnweb.freebsd.org/changeset/base/339582 https://svnweb.freebsd.org/changeset/base/339583 --HPS From owner-freebsd-current@freebsd.org Mon Oct 22 09:28:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1215FF0F1B; Mon, 22 Oct 2018 09:28:23 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp001.me.com (pv33p00im-asmtp001.me.com [17.142.194.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56E3570B0D; Mon, 22 Oct 2018 09:28:23 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp001.me.com by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PGZ00400U1AD700@pv33p00im-asmtp001.me.com>; Mon, 22 Oct 2018 09:28:11 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PGZ00FNHUA5JG20@pv33p00im-asmtp001.me.com>; Mon, 22 Oct 2018 09:27:46 +0000 (GMT) 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-1807170000 definitions=main-1810220085 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-21_14:,, signatures=0 From: Toomas Soome Message-id: <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated Date: Mon, 22 Oct 2018 12:27:40 +0300 In-reply-to: Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh To: Mark Millard References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> X-Mailer: Apple Mail (2.3445.100.39) 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: Mon, 22 Oct 2018 09:28:24 -0000 > On 22 Oct 2018, at 06:30, Warner Losh wrote: >=20 > On Sun, Oct 21, 2018 at 9:28 PM Warner Losh > wrote: >=20 >>=20 >>=20 >> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >> freebsd-stable@freebsd.org> wrote: >>=20 >>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >>> after installing the build, Hyper-V based boots are >>> working.] >>>=20 >>> On 2018-Oct-20, at 2:09 AM, Mark Millard = wrote: >>>=20 >>>> On 2018-Oct-20, at 1:39 AM, Mark Millard = wrote: >>>>=20 >>>>> I attempted to jump from head -r334014 to -r339076 >>>>> on a threadripper 1950X board and the boot fails. >>>>> This is both native booting and under Hyper-V, >>>>> same machine and root file system in both cases. >>>>=20 >>>> I did my investigation under Hyper-V after seeing >>>> a boot failure native. >>>>=20 >>>> Looks like the native failure is even earlier, >>>> before db> is even possible, possibly during >>>> early loader activity. >>>>=20 >>>> So this report is really for running under >>>> Hyper-V: -r338804 boots and -r338810 does >>>> not. By contrast -r334804 does not boot native. >>>> (But I've little information for that context.) >>>>=20 >>>> Sorry for the confusion. I rushed the report >>>> in hopes of getting to sleep. It was not to be. >>>>=20 >>>>> It fails just after the FreeBSD/SMP lines, >>>>> reporting "kernel trap 9 with interrupts disabled". >>>>>=20 >>>>> It fails in pmap_force_invaldiate_cache_range at >>>>> a clflusl (%rax) instruction that produces a >>>>> "Fatal trap 9: general protection fault while >>>>> in kernel mode". cpudid=3D0 apic id=3D 00 >>>>>=20 >>>>> I used kernel.txz files from: >>>>>=20 >>>>> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >>>>>=20 >>>>> to narrow the range of kernel builds for working -> failing >>>>> and got: >>>>>=20 >>>>> -r338804 boots fine >>>>> (no amd64 kernel builds between to try) >>>>> -r338810+ fails (any that I tried, anyway) >>>>>=20 >>>>> In that range is -r338807 : >>>>>=20 >>>>> QUOTE >>>>> Author: kib >>>>> Date: Wed Sep 19 19:35:02 2018 >>>>> New Revision: 338807 >>>>> URL: >>>>> https://svnweb.freebsd.org/changeset/base/338807 >>>>>=20 >>>>>=20 >>>>> Log: >>>>> Convert x86 cache invalidation functions to ifuncs. >>>>>=20 >>>>> This simplifies the runtime logic and reduces the number of >>>>> runtime-constant branches. >>>>>=20 >>>>> Reviewed by: alc, markj >>>>> Sponsored by: The FreeBSD Foundation >>>>> Approved by: re (gjb) >>>>> Differential revision: >>>>> https://reviews.freebsd.org/D16736 >>>>>=20 >>>>> Modified: >>>>> head/sys/amd64/amd64/pmap.c >>>>> head/sys/amd64/include/pmap.h >>>>> head/sys/dev/drm2/drm_os_freebsd.c >>>>> head/sys/dev/drm2/i915/intel_ringbuffer.c >>>>> head/sys/i386/i386/pmap.c >>>>> head/sys/i386/i386/vm_machdep.c >>>>> head/sys/i386/include/pmap.h >>>>> head/sys/x86/iommu/intel_utils.c >>>>> END QUOTE >>>>>=20 >>>>> There do seem to be changes associated with >>>>> clflush(...) use. Looking at: >>>>>=20 >>>>>=20 >>> = https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=3D339= 432 >>>>>=20 >>>>> it appears that pmap_force_invalidate_cache_range has not >>>>> changed since -r338807. >>>>>=20 >>>>> It seems that -r338806 and -r3388810 would be unlikely >>>>> contributors. >>>>=20 >>>=20 >>> I went after my native-boot loader problem first because I >>> could switch kernels via the loader for booting FreeBSD under >>> Hyper-V. Switching loaders is more of a problem. >>>=20 >>> In order to avoid the loader-time crash I switched to building >>> installing based on WITHOUT_ZFS=3D . I've had no active use of >>> ZFS in years. (The old official-build loaders that worked were >>> non-ZFS ones.) >>>=20 >>> This took care of the native-boot loader-crash --and, to my >>> surprise, also the Hyper-V-boot kernel-time crash. >>>=20 >>> My private builds now boot the 1950X in both contexts just >>> fine. >>>=20 >>> During my early investigation I did pick up specific changes >>> from after -r339076 that seemed to be tied to Ryzen and such. >>> (They made no difference to the boot problems at the time >>> but I saw no reason to remove them.) >>>=20 >>> # uname -apKU >>> FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 r339076:339432M: = Sun >>> Oct 21 16:44:25 PDT 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG >>> amd64 amd64 1200084 1200084 >>=20 >>=20 > (stupid gmail) >=20 > The phrase "no active use" bothers me. What does that mean? Are there = any > ZFS pools or any disks that any whiff of ZFSish thing on it at all? > Clearly, there's something in the zfs boot loader that's freaking out = by > something on your system, but absent that information I can't help = you. >=20 It would help to get output from loader lsdev -v command. Also if you = could test boot loader with UEFI - for example get to loader prompt via = usb/cd boot and then get the same lsdev -v output. I would be interested = to see the sector size information and if the UEFI loader does also have = issues. If it does, I=E2=80=99d like to see the outputs from commands: zpool status zpool import thanks, toomas From owner-freebsd-current@freebsd.org Mon Oct 22 09:30:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0EA4FF1103 for ; Mon, 22 Oct 2018 09:30:30 +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 5264B70DAC for ; Mon, 22 Oct 2018 09:30:29 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Mon, 22 Oct 2018 09:30:22 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id E56197BA-21D1-4B5A-A5B1-7E7B5EEFBAB3.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Mon, 22 Oct 2018 09:30:22 +0000 Date: Mon, 22 Oct 2018 12:30:17 +0300 From: Greg V Subject: Re: Current status of Ryzen (non-)support To: Hannes Hauswedell Cc: freebsd-current@freebsd.org Message-Id: <1540200618.1834.0@smtp.migadu.com> In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=DGPkRN6FkJFlzKw4oruVy0lCbSv5u9uQtGM7xrONPS0=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=WdWKBKO/Iz5vrBAhrBvuB5eJmbXhWf1Md5F6nA74fA3QoER9F6sVSGROSwF031V4nl9m1r8ba4d6cDplY10+wfFz15Ebnsx46vIM924hU45Y3ouOxJoWXNiOI7VKPLM4CF6DgbRUMDSCunHbBmSrA4nJy4OTbl0bo/vTQgnoSLs= 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, 22 Oct 2018 09:30:31 -0000 On Sun, Oct 21, 2018 at 7:09 PM, Hannes Hauswedell=20 wrote: > Hi everyone, >=20 > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. >=20 > My situation: > * second generation Ryzen: 2600X > * running -CURRENT > * I have done the things described here: > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > * no full system freezes, but under load, e.g. building with 12=20 > threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues >=20 > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation=20 > CPUs... First gen (R7 1700) here, overclocked to 3.9GHz, also running CURRENT=20 =97 never had any unexpected segfaults, even when building with 16=20 threads. The only bug is that the bottom (chipset) PCIe slot breaks when an NVMe=20 SSD is installed / chipset USB3 ports don't work: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231923 = From owner-freebsd-current@freebsd.org Mon Oct 22 09:35:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BFB2FF1675 for ; Mon, 22 Oct 2018 09:35:26 +0000 (UTC) (envelope-from pho@holm.cc) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2D1047132B for ; Mon, 22 Oct 2018 09:35:26 +0000 (UTC) (envelope-from pho@holm.cc) Received: by mailman.ysv.freebsd.org (Postfix) id E6338FF1674; Mon, 22 Oct 2018 09:35:25 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D51FDFF1673 for ; Mon, 22 Oct 2018 09:35:25 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) (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 8517271329 for ; Mon, 22 Oct 2018 09:35:25 +0000 (UTC) (envelope-from pho@holm.cc) Received: from x2.osted.lan (87-58-223-204-dynamic.dk.customer.tdc.net [87.58.223.204]) by relay01.pair.com (Postfix) with ESMTP id 780D8D00B7F; Mon, 22 Oct 2018 05:35:18 -0400 (EDT) Received: from x2.osted.lan (localhost [127.0.0.1]) by x2.osted.lan (8.15.2/8.15.2) with ESMTPS id w9M9ZG6Q097549 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Oct 2018 11:35:16 +0200 (CEST) (envelope-from pho@x2.osted.lan) Received: (from pho@localhost) by x2.osted.lan (8.15.2/8.15.2/Submit) id w9M9ZGnq097548; Mon, 22 Oct 2018 11:35:16 +0200 (CEST) (envelope-from pho) Date: Mon, 22 Oct 2018 11:35:16 +0200 From: Peter Holm To: Hans Petter Selasky Cc: current@freebsd.org Subject: Re: Page fault in midi/sequencer.c Message-ID: <20181022093516.GA97520@x2.osted.lan> References: <20181020165604.GA4946@x2.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) 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, 22 Oct 2018 09:35:26 -0000 On Mon, Oct 22, 2018 at 11:00:41AM +0200, Hans Petter Selasky wrote: > On 10/20/18 6:56 PM, Peter Holm wrote: > > I can trigger this on 13.0-CURRENT r339445 with a non-root test program: > > > > Hi, > > The following commits should fix the issues you experience: > > https://svnweb.freebsd.org/changeset/base/339581 > https://svnweb.freebsd.org/changeset/base/339582 > https://svnweb.freebsd.org/changeset/base/339583 > > --HPS Thank you for fixing this! -- Peter From owner-freebsd-current@freebsd.org Mon Oct 22 10:58:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E7E5FF3F65 for ; Mon, 22 Oct 2018 10:58:24 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-21.consmr.mail.gq1.yahoo.com (sonic312-21.consmr.mail.gq1.yahoo.com [98.137.69.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD62073F86 for ; Mon, 22 Oct 2018 10:58:23 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: jmsiP_MVM1n8vGRln0v_NdtwvOGOFRVfqOjq_tK7FuCCkJE8xVpxRr0wZ1Xg81o QiAnwNQAvT7oBTqXdlPZ8gdOf0rAVJcTaEq7tAUj6n.h40F9UH0yZpc7E11zjw9fLdpbVI2IsJz9 UXMzIpNmMUyKFBU67JwmsidRgwS1h_Ser_t9mO21fvKBqaBdU3Ky0bg3xqdjMXCAby5y.OA7.TrC JhYKbCqzNJnkls5ybdcGzsWxBHju1_V0p4VehYHdqhX9b9snK1QrgrQqB1NhW8lY5O61w.9FHFI2 S.1ncyuH4oJeUYO0vh8vr4YYL0LLGF65i9vromKAhSVZW76aDyunkJuoitMiDlnpobUj9UNX0tqM .ftbqYXg4YFKwLwW4xtkIWoQZd7.IAFB1YSyHrqkZbRJokad_dqqVCeN.uESG0e0ZPVymFH7XKaU MY2DcMa7F.8ZJxvQOAb3XZQYsVZUOS9m49ZA5b9VmLS2kQ7DPSAtD6e3H9rd.AfjZZsRl.SJTCuE 4OMOELm.LNw2n2J5bmre8ejN.QW.fJuiXwlq5IYfgaAUzw71i7VQoodjAOxADjh3zZcCZ4reXC3o W_G51zQh5LlDUWRSxdwgNjFOMnUWrXdI9bYdqzUnEJeuX.yTH8rqfh67LycEhhwrnDgsMF3D2fjK WiwDnfzs.Pd.gNFmtGzFjNBAAGKsgXgZWwu4MNMfnYgmMtTrXmq5K.dtTCv_m_HDa1Yd8naQrmpA 8PUIqligyJXitB9THNSNJyE_Lhw02LeVUcEruOBho_S8MhRdYK7lprQ4W.9Ze2PBJqxYPK_yaeGF DIPWcEEFp0Ege.6KrcyD.JOXA5yW9ias.JjGlfsLYGQJ4b1mLpOWi2YF2fgMjwPNEZjzs55fjpaK 2DkwL0J5iJ6VH4i.7FEF.mPNxemspRX0EsVPNqIwSM4y25MwTT65WrPsFIGXA0mlip1jW683kzXT hjKKF7OKIvkOfm1JAbE9iARdflPgecVCf3H1GU9gXCB6BBOcl9Kq_TFtFu9lmO.FvOhza7hGuHwh XEKKuR3cXZC8CeU.Xv6TLcXlIi61VDYTM4xUp2eNkfWYj61yPpyI4iVxFkId9it4_rxrnhd0N.zg - Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Mon, 22 Oct 2018 10:58:17 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp421.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID bd82cf856c822e6019f6f9fc4922c776; Mon, 22 Oct 2018 10:58:12 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> Date: Mon, 22 Oct 2018 03:58:12 -0700 Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh Content-Transfer-Encoding: quoted-printable Message-Id: <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> To: Toomas Soome X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 10:58:24 -0000 On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >=20 >> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>=20 >> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >>=20 >>>=20 >>>=20 >>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >>> freebsd-stable@freebsd.org> wrote: >>>=20 >>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >>>> after installing the build, Hyper-V based boots are >>>> working.] >>>>=20 >>>> On 2018-Oct-20, at 2:09 AM, Mark Millard = wrote: >>>>=20 >>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard = wrote: >>>>>=20 >>>>>> I attempted to jump from head -r334014 to -r339076 >>>>>> on a threadripper 1950X board and the boot fails. >>>>>> This is both native booting and under Hyper-V, >>>>>> same machine and root file system in both cases. >>>>>=20 >>>>> I did my investigation under Hyper-V after seeing >>>>> a boot failure native. >>>>>=20 >>>>> Looks like the native failure is even earlier, >>>>> before db> is even possible, possibly during >>>>> early loader activity. >>>>>=20 >>>>> So this report is really for running under >>>>> Hyper-V: -r338804 boots and -r338810 does >>>>> not. By contrast -r334804 does not boot native. >>>>> (But I've little information for that context.) >>>>>=20 >>>>> Sorry for the confusion. I rushed the report >>>>> in hopes of getting to sleep. It was not to be. >>>>>=20 >>>>>> It fails just after the FreeBSD/SMP lines, >>>>>> reporting "kernel trap 9 with interrupts disabled". >>>>>>=20 >>>>>> It fails in pmap_force_invaldiate_cache_range at >>>>>> a clflusl (%rax) instruction that produces a >>>>>> "Fatal trap 9: general protection fault while >>>>>> in kernel mode". cpudid=3D0 apic id=3D 00 >>>>>>=20 >>>>>> I used kernel.txz files from: >>>>>>=20 >>>>>> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >>>>>>=20 >>>>>> to narrow the range of kernel builds for working -> failing >>>>>> and got: >>>>>>=20 >>>>>> -r338804 boots fine >>>>>> (no amd64 kernel builds between to try) >>>>>> -r338810+ fails (any that I tried, anyway) >>>>>>=20 >>>>>> In that range is -r338807 : >>>>>>=20 >>>>>> QUOTE >>>>>> Author: kib >>>>>> Date: Wed Sep 19 19:35:02 2018 >>>>>> New Revision: 338807 >>>>>> URL: >>>>>> https://svnweb.freebsd.org/changeset/base/338807 >>>>>>=20 >>>>>>=20 >>>>>> Log: >>>>>> Convert x86 cache invalidation functions to ifuncs. >>>>>>=20 >>>>>> This simplifies the runtime logic and reduces the number of >>>>>> runtime-constant branches. >>>>>>=20 >>>>>> Reviewed by: alc, markj >>>>>> Sponsored by: The FreeBSD Foundation >>>>>> Approved by: re (gjb) >>>>>> Differential revision: >>>>>> https://reviews.freebsd.org/D16736 >>>>>>=20 >>>>>> Modified: >>>>>> head/sys/amd64/amd64/pmap.c >>>>>> head/sys/amd64/include/pmap.h >>>>>> head/sys/dev/drm2/drm_os_freebsd.c >>>>>> head/sys/dev/drm2/i915/intel_ringbuffer.c >>>>>> head/sys/i386/i386/pmap.c >>>>>> head/sys/i386/i386/vm_machdep.c >>>>>> head/sys/i386/include/pmap.h >>>>>> head/sys/x86/iommu/intel_utils.c >>>>>> END QUOTE >>>>>>=20 >>>>>> There do seem to be changes associated with >>>>>> clflush(...) use. Looking at: >>>>>>=20 >>>>>>=20 >>>> = https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=3D339= 432 >>>>>>=20 >>>>>> it appears that pmap_force_invalidate_cache_range has not >>>>>> changed since -r338807. >>>>>>=20 >>>>>> It seems that -r338806 and -r3388810 would be unlikely >>>>>> contributors. >>>>>=20 >>>>=20 >>>> I went after my native-boot loader problem first because I >>>> could switch kernels via the loader for booting FreeBSD under >>>> Hyper-V. Switching loaders is more of a problem. >>>>=20 >>>> In order to avoid the loader-time crash I switched to building >>>> installing based on WITHOUT_ZFS=3D . I've had no active use of >>>> ZFS in years. (The old official-build loaders that worked were >>>> non-ZFS ones.) >>>>=20 >>>> This took care of the native-boot loader-crash --and, to my >>>> surprise, also the Hyper-V-boot kernel-time crash. >>>>=20 >>>> My private builds now boot the 1950X in both contexts just >>>> fine. >>>>=20 >>>> During my early investigation I did pick up specific changes >>>> from after -r339076 that seemed to be tied to Ryzen and such. >>>> (They made no difference to the boot problems at the time >>>> but I saw no reason to remove them.) >>>>=20 >>>> # uname -apKU >>>> FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 = r339076:339432M: Sun >>>> Oct 21 16:44:25 PDT 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG >>>> amd64 amd64 1200084 1200084 >>>=20 >>>=20 >> (stupid gmail) >>=20 >> The phrase "no active use" bothers me. What does that mean? Are there = any >> ZFS pools or any disks that any whiff of ZFSish thing on it at all? >> Clearly, there's something in the zfs boot loader that's freaking out = by >> something on your system, but absent that information I can't help = you. >>=20 >=20 > It would help to get output from loader lsdev -v command. That turned out to be very interesting: The non-ZFS loader crashes during the listing, during disk8, which shows a x0 instead of a x512. Hand transcribed from pictures: OK lsdev -v disk devices disk0: BIOS drive C (937703088 x 512): disk0p1: FreeBSD boot 512K disk0p2: FreeBSD UFS 356G disk0p3: FreeBSD swap 15G disp0p4: FreeBSD swap 76G disk1: BIOS drive D (16514064 x 512): disk1s1: Linux 2048KB disk1s2: Unknown 952GB disk2: BIOS drive E (16514064 x 512): disk2p1: Unknown 128MB disk3: BIOS drive F (16514064 x 512): disk3p1: Unknown 128MB disk4: BIOS drive G (16434495 x 512): disk2p1: Unknown 128MB disk4p2: DOS/Windwos 1716GB disk5: BIOS drive H (16434495 x 512): disk5p1: FreeBSD boot 512K disk5p2: FreeBSD UFS 176G disk5p3: FreeBSD swap 193G disp5p4: FreeBSD swap 15G disk6: BIOS drive I (16434495 x 512): disk6p1: Unknown 499MB disk6p2: EFI 99MB disk6p3: Unknown 16MB disp6p4: DOS/Windows 886G dis7: BIOS drive H (16434495 x 512): disk7p1: FreeBSD boot 512K disk7p2: FreeBSD UFS 953G disk8: BIOS drive K (262144 x 0): int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000286bd eax=3D00000000 ebx=3D72b50430 ecx=3D00000000 edx=3D00000000 esi=3D00000000 edi=3D00092080 ebp=3D00091eec esp=3D00091ea8 cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 cs:eip=3Df7 f1 89 c1 85 d2 0f 85-d8 01 00 00 6a 05 58 85 f6 0f 88 75 01 00 00 89-cb c1 fb 1f 89 ca 03 55 ss:esp=3D09 00 00 00 00 00 00 00-0a 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00-78 1f 09 00 33 45 04 00 BTX halted I expect that "disk8" is what gpart show -p from a native boot showed as: =3D> 1 60062499 da1 MBR (29G) 1 31 - free - (16K) 32 60062468 da1s1 fat32lba (29G) (That gpart show -p output is in another of the list messages.) > Also if you could test boot loader with UEFI - for example get to = loader prompt via usb/cd boot and then get the same lsdev -v output. Still true given the above crash? Or, going the other way, should "drive8" be left as it is in order to be sure to do this test with the drive present? If I do this test later, it will take a bit to get media to do it with. (It is about 4AM in the morning and I've yet to get to sleep.) Note: I've never tried a UEFI based boot of FreeBSD on this machine (but the Windows 10 Pro x64 is EFI based). The only FreeBSD context using a EFI partition to boot that I have used is on an arm aarch64 Cortex-A57 system. > I would be interested to see the sector size information and if the = UEFI loader does also have issues. Understood. > If it does, I=E2=80=99d like to see the outputs from commands: > zpool status > zpool import Independent of the UEFI test . . . I do have a -r331924 head version on another one of the devices and can native-boot that. It still has its ZFS software (but a default loader without ZFS). Trying from that context, hand transcribed: # zpool status ZFS filesystem version: 5 ZFS storage pool version: features support (5000) no pools available # zpool import # [That was based on the old (default) loader being a non-ZFS one.] =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 11:07:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EC68FF56DF; Mon, 22 Oct 2018 11:07:42 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp003.me.com (pv33p00im-asmtp003.me.com [17.142.194.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC715745F1; Mon, 22 Oct 2018 11:07:41 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp003.me.com by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PGZ00M00YLYQV00@pv33p00im-asmtp003.me.com>; Mon, 22 Oct 2018 11:07:40 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PGZ00JOQYWKOS00@pv33p00im-asmtp003.me.com>; Mon, 22 Oct 2018 11:07:38 +0000 (GMT) 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-1807170000 definitions=main-1810220099 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-21_14:,, signatures=0 From: Toomas Soome Message-id: <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated Date: Mon, 22 Oct 2018 14:07:31 +0300 In-reply-to: <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh To: Mark Millard References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> X-Mailer: Apple Mail (2.3445.100.39) 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: Mon, 22 Oct 2018 11:07:43 -0000 > On 22 Oct 2018, at 13:58, Mark Millard wrote: >=20 > On 2018-Oct-22, at 2:27 AM, Toomas Soome > wrote: >>=20 >>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>>=20 >>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >>>=20 >>>>=20 >>>>=20 >>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >>>> freebsd-stable@freebsd.org> wrote: >>>>=20 >>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >>>>> after installing the build, Hyper-V based boots are >>>>> working.] >>>>>=20 >>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard = wrote: >>>>>=20 >>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard = wrote: >>>>>>=20 >>>>>>> I attempted to jump from head -r334014 to -r339076 >>>>>>> on a threadripper 1950X board and the boot fails. >>>>>>> This is both native booting and under Hyper-V, >>>>>>> same machine and root file system in both cases. >>>>>>=20 >>>>>> I did my investigation under Hyper-V after seeing >>>>>> a boot failure native. >>>>>>=20 >>>>>> Looks like the native failure is even earlier, >>>>>> before db> is even possible, possibly during >>>>>> early loader activity. >>>>>>=20 >>>>>> So this report is really for running under >>>>>> Hyper-V: -r338804 boots and -r338810 does >>>>>> not. By contrast -r334804 does not boot native. >>>>>> (But I've little information for that context.) >>>>>>=20 >>>>>> Sorry for the confusion. I rushed the report >>>>>> in hopes of getting to sleep. It was not to be. >>>>>>=20 >>>>>>> It fails just after the FreeBSD/SMP lines, >>>>>>> reporting "kernel trap 9 with interrupts disabled". >>>>>>>=20 >>>>>>> It fails in pmap_force_invaldiate_cache_range at >>>>>>> a clflusl (%rax) instruction that produces a >>>>>>> "Fatal trap 9: general protection fault while >>>>>>> in kernel mode". cpudid=3D0 apic id=3D 00 >>>>>>>=20 >>>>>>> I used kernel.txz files from: >>>>>>>=20 >>>>>>> https://artifact.ci.freebsd.org/snapshot/head/r*/amd64/amd64/ >>>>>>>=20 >>>>>>> to narrow the range of kernel builds for working -> failing >>>>>>> and got: >>>>>>>=20 >>>>>>> -r338804 boots fine >>>>>>> (no amd64 kernel builds between to try) >>>>>>> -r338810+ fails (any that I tried, anyway) >>>>>>>=20 >>>>>>> In that range is -r338807 : >>>>>>>=20 >>>>>>> QUOTE >>>>>>> Author: kib >>>>>>> Date: Wed Sep 19 19:35:02 2018 >>>>>>> New Revision: 338807 >>>>>>> URL: >>>>>>> https://svnweb.freebsd.org/changeset/base/338807 >>>>>>>=20 >>>>>>>=20 >>>>>>> Log: >>>>>>> Convert x86 cache invalidation functions to ifuncs. >>>>>>>=20 >>>>>>> This simplifies the runtime logic and reduces the number of >>>>>>> runtime-constant branches. >>>>>>>=20 >>>>>>> Reviewed by: alc, markj >>>>>>> Sponsored by: The FreeBSD Foundation >>>>>>> Approved by: re (gjb) >>>>>>> Differential revision: >>>>>>> https://reviews.freebsd.org/D16736 >>>>>>>=20 >>>>>>> Modified: >>>>>>> head/sys/amd64/amd64/pmap.c >>>>>>> head/sys/amd64/include/pmap.h >>>>>>> head/sys/dev/drm2/drm_os_freebsd.c >>>>>>> head/sys/dev/drm2/i915/intel_ringbuffer.c >>>>>>> head/sys/i386/i386/pmap.c >>>>>>> head/sys/i386/i386/vm_machdep.c >>>>>>> head/sys/i386/include/pmap.h >>>>>>> head/sys/x86/iommu/intel_utils.c >>>>>>> END QUOTE >>>>>>>=20 >>>>>>> There do seem to be changes associated with >>>>>>> clflush(...) use. Looking at: >>>>>>>=20 >>>>>>>=20 >>>>> = https://svnweb.freebsd.org/base/head/sys/amd64/amd64/pmap.c?annotate=3D339= 432 >>>>>>>=20 >>>>>>> it appears that pmap_force_invalidate_cache_range has not >>>>>>> changed since -r338807. >>>>>>>=20 >>>>>>> It seems that -r338806 and -r3388810 would be unlikely >>>>>>> contributors. >>>>>>=20 >>>>>=20 >>>>> I went after my native-boot loader problem first because I >>>>> could switch kernels via the loader for booting FreeBSD under >>>>> Hyper-V. Switching loaders is more of a problem. >>>>>=20 >>>>> In order to avoid the loader-time crash I switched to building >>>>> installing based on WITHOUT_ZFS=3D . I've had no active use of >>>>> ZFS in years. (The old official-build loaders that worked were >>>>> non-ZFS ones.) >>>>>=20 >>>>> This took care of the native-boot loader-crash --and, to my >>>>> surprise, also the Hyper-V-boot kernel-time crash. >>>>>=20 >>>>> My private builds now boot the 1950X in both contexts just >>>>> fine. >>>>>=20 >>>>> During my early investigation I did pick up specific changes >>>>> from after -r339076 that seemed to be tied to Ryzen and such. >>>>> (They made no difference to the boot problems at the time >>>>> but I saw no reason to remove them.) >>>>>=20 >>>>> # uname -apKU >>>>> FreeBSD FBSDFSSD 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 #5 = r339076:339432M: Sun >>>>> Oct 21 16:44:25 PDT 2018 = markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/G= ENERIC-NODBG >>>>> amd64 amd64 1200084 1200084 >>>>=20 >>>>=20 >>> (stupid gmail) >>>=20 >>> The phrase "no active use" bothers me. What does that mean? Are = there any >>> ZFS pools or any disks that any whiff of ZFSish thing on it at all? >>> Clearly, there's something in the zfs boot loader that's freaking = out by >>> something on your system, but absent that information I can't help = you. >>>=20 >>=20 >> It would help to get output from loader lsdev -v command. >=20 > That turned out to be very interesting: The non-ZFS loader > crashes during the listing, during disk8, which shows a > x0 instead of a x512. >=20 Yes, thats the root cause there. The non-zfs loader does only *read* the = boot disk, thats why the issue was not revealed there.=20 It would help to identify the sector size for that disk, at least from = OS, so we can compare with what we can get from INT13. I have pretty good idea what to look there, but I am afraid we need to = run few tests with you to understand why that disk is reporting sector = size 0 there. rgds, toomas > Hand transcribed from pictures: >=20 > OK lsdev -v > disk devices > disk0: BIOS drive C (937703088 x 512): > disk0p1: FreeBSD boot 512K > disk0p2: FreeBSD UFS 356G > disk0p3: FreeBSD swap 15G > disp0p4: FreeBSD swap 76G > disk1: BIOS drive D (16514064 x 512): > disk1s1: Linux 2048KB > disk1s2: Unknown 952GB > disk2: BIOS drive E (16514064 x 512): > disk2p1: Unknown 128MB > disk3: BIOS drive F (16514064 x 512): > disk3p1: Unknown 128MB > disk4: BIOS drive G (16434495 x 512): > disk2p1: Unknown 128MB > disk4p2: DOS/Windwos 1716GB > disk5: BIOS drive H (16434495 x 512): > disk5p1: FreeBSD boot 512K > disk5p2: FreeBSD UFS 176G > disk5p3: FreeBSD swap 193G > disp5p4: FreeBSD swap 15G > disk6: BIOS drive I (16434495 x 512): > disk6p1: Unknown 499MB > disk6p2: EFI 99MB > disk6p3: Unknown 16MB > disp6p4: DOS/Windows 886G > dis7: BIOS drive H (16434495 x 512): > disk7p1: FreeBSD boot 512K > disk7p2: FreeBSD UFS 953G > disk8: BIOS drive K (262144 x 0): >=20 > int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000286bd > eax=3D00000000 ebx=3D72b50430 ecx=3D00000000 edx=3D00000000 > esi=3D00000000 edi=3D00092080 ebp=3D00091eec esp=3D00091ea8 > cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 > cs:eip=3Df7 f1 89 c1 85 d2 0f 85-d8 01 00 00 6a 05 58 85 > f6 0f 88 75 01 00 00 89-cb c1 fb 1f = 89 ca 03 55 > ss:esp=3D09 00 00 00 00 00 00 = 00-0a 00 00 00 02 00 00 00 > 00 00 00 00 00 00 00 = 00-78 1f 09 00 33 45 04 00 > BTX halted >=20 > I expect that "disk8" is what gpart show -p > from a native boot showed as: >=20 > =3D> 1 60062499 da1 MBR (29G) > 1 31 - free - (16K) > 32 =C2=A060062468 da1s1 fat32lba = (29G) >=20 > (That gpart show -p output is in another of the > list messages.) >=20 >> Also if you could test boot loader with UEFI - for example get to = loader prompt via usb/cd boot and then get the same lsdev -v output. >=20 > Still true given the above crash? Or, going the > other way, should "drive8" be left as it is in > order to be sure to do this test with the drive > present? >=20 > If I do this test later, it will take a bit to > get media to do it with. (It is about 4AM in the > morning and I've yet to get to sleep.) >=20 > Note: I've never tried a UEFI based boot of FreeBSD > on this machine (but the Windows 10 Pro x64 is EFI > based). The only FreeBSD context using a EFI partition > to boot that I have used is on an arm aarch64 > Cortex-A57 system. >=20 >> I would be interested to see the sector size information and if the = UEFI loader does also have issues. >=20 > Understood. >=20 >> If it does, I=E2=80=99d like to see the outputs from commands: >=20 >> zpool status >> zpool import >=20 > Independent of the UEFI test . . . >=20 > I do have a -r331924 head version on another one > of the devices and can native-boot that. It still > has its ZFS software (but a default loader without > ZFS). >=20 > Trying from that context, hand transcribed: >=20 > # zpool status > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > no pools available > # zpool import > # >=20 > [That was based on the old (default) loader being > a non-ZFS one.] >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 12:39:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB786FFAADF for ; Mon, 22 Oct 2018 12:39:42 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-36.consmr.mail.ne1.yahoo.com (sonic317-36.consmr.mail.ne1.yahoo.com [66.163.184.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 665517814B for ; Mon, 22 Oct 2018 12:39:42 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: nlUpYekVM1k8LPpTgXb9Li5gPeIldEl8aqVIdYJXYqvkVWIBy7JB5VFeM88wIj8 VpDBN7di71903oVbJ41QQR11rKqeXQxO9g6QIcOGGFQAeNJtZZvB6m0Gqi6jcxhQkk8b_xHBNdrU vao7NXBhHHqO_scUV8dNQLswK.Sa53CM6EWNaM5d05Y0wc5aHv9_4CYRc8q_Qh8ektVElCfrdooZ 4nUr_WlwcmN8IeSKCHDnOTMjXpnWq4eI4h.8F7K5c45gUZ5sm9r1PWerKVDvWTjdrX1qGZsnnpT. _x1vcLs_7QkshHdbQDAB1ii9E5yZyac_mawffk2v3hUUam8pRCJuZO5Qkica8E72NtSYWFHJ4O0Z 5ycn8OPGS7dzHyi4OVuaYY_KD1SPRKWkCIb5UCtlpwQeHqWJE_zJc4sMPtI2UURFWNsP_OGg.kyp CjsBt2wNvhy4UHjPCMl444RZW7esGCh1Td96QVq0uoBEWP2Hqe5EavdU5FZ28WhnY8xmY72pU01t JtgubyA0AvSobhDrjaXLMYv3S.ufB1cEnshlVo67vSmgNwv6gwEGbr4rrDZFrfq4roK6PTsodIkt jPGlT_BFzQ.xW1Ir9mC_0b.aCufA0kE5wwVQlKoArpf.Ha5YRWyJh4906SpfNfkJUMky2MbYwHVo u9T.AQj1wRFvTmhjrun6RYPFlXIRklMAY8UKKkCwjOcg6dPLcTd61PQyufGy78aYfVU27RduSrWZ mYEBvqvh6saC5.0KL7GelR0bb2O5Q0rEAZ8fPdLZtnUSIAr.GnFxNfHq2Vm5sOYxBZXKs9AgBjPO gqJ2a8FPcny60zVKhhl4jQLWLT0HONnKRtkS1AUpQdfVbki2UtrHW.kFJx99ACud3aWmCGGcthyP vBSJFTiBvifp2J4nwxNoS61n8p0ca1rHmBm4njv9sviREY2IY5rLOnZDkF5nyuDKdRTctgD1gH8S J6uliQl4f6Hn0lrzwOQWYPKgi.daBchxP_Cwt0PQJbAzWtRUU9Kkoohvb0T8tmhDkmgyo9Naqqj7 HCUQuO7WjUVf5SG90MZf9o35Q65xgXITfaPFUdCdfJ.bsWxuChJUc.TfBVTZKLMa19vaO9lgHPyI uQeA- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.ne1.yahoo.com with HTTP; Mon, 22 Oct 2018 12:39:41 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp422.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a3206d9ee5ade17a4a95cd6b0065b2c0; Mon, 22 Oct 2018 12:39:37 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> Date: Mon, 22 Oct 2018 05:39:36 -0700 Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh Content-Transfer-Encoding: quoted-printable Message-Id: <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> To: Toomas Soome X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 12:39:43 -0000 On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > On 22 Oct 2018, at 13:58, Mark Millard wrote: >>=20 >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >>>=20 >>>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>>>=20 >>>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >>>>=20 >>>>>=20 >>>>>=20 >>>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >>>>> freebsd-stable@freebsd.org> wrote: >>>>>=20 >>>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >>>>>> after installing the build, Hyper-V based boots are >>>>>> working.] >>>>>>=20 >>>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard = wrote: >>>>>>=20 >>>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard = wrote: >>>>>>> . . . >>>>=20 >>>=20 >>> It would help to get output from loader lsdev -v command. >>=20 >> That turned out to be very interesting: The non-ZFS loader >> crashes during the listing, during disk8, which shows a >> x0 instead of a x512. >>=20 >=20 > Yes, thats the root cause there. The non-zfs loader does only *read* = the boot disk, thats why the issue was not revealed there.=20 >=20 > It would help to identify the sector size for that disk, at least from = OS, so we can compare with what we can get from INT13. >=20 > I have pretty good idea what to look there, but I am afraid we need to = run few tests with you to understand why that disk is reporting sector = size 0 there. >=20 >=20 Looks like I guessed wrong about the device for "drive8". So I unplugged the only other external storage device, so the original drives 0-13 become 0-11 overall. The machine has a multi-LUN media card reader with no cards plugged in. It is built-in rather than one that I plugged into a port. It has 4 LUN's. So 8+4=3D12 and drives 0-7 show up with media before it tries any of the 4 LUN's with no card in place. I conclude that "drive8" is an empty LUN in a media card reader. I conclude that there is no sector size available for any of the empty LUNs in the media reader. >=20 >=20 >> Hand transcribed from pictures: >>=20 >> OK lsdev -v >> disk devices >> disk0: BIOS drive C (937703088 x 512): >> disk0p1: FreeBSD boot 512K >> disk0p2: FreeBSD UFS 356G >> disk0p3: FreeBSD swap 15G >> disp0p4: FreeBSD swap 76G >> disk1: BIOS drive D (16514064 x 512): >> disk1s1: Linux 2048KB >> disk1s2: Unknown 952GB >> disk2: BIOS drive E (16514064 x 512): >> disk2p1: Unknown 128MB >> disk3: BIOS drive F (16514064 x 512): >> disk3p1: Unknown 128MB >> disk4: BIOS drive G (16434495 x 512): >> disk2p1: Unknown 128MB >> disk4p2: DOS/Windwos 1716GB >> disk5: BIOS drive H (16434495 x 512): >> disk5p1: FreeBSD boot 512K >> disk5p2: FreeBSD UFS 176G >> disk5p3: FreeBSD swap 193G >> disp5p4: FreeBSD swap 15G >> disk6: BIOS drive I (16434495 x 512): >> disk6p1: Unknown 499MB >> disk6p2: EFI 99MB >> disk6p3: Unknown 16MB >> disp6p4: DOS/Windows 886G >> dis7: BIOS drive H (16434495 x 512): >> disk7p1: FreeBSD boot 512K >> disk7p2: FreeBSD UFS 953G >> disk8: BIOS drive K (262144 x 0): >>=20 >> int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000286bd >> eax=3D00000000 ebx=3D72b50430 ecx=3D00000000 edx=3D00000000 >> esi=3D00000000 edi=3D00092080 ebp=3D00091eec esp=3D00091ea8 >> cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 >> cs:eip=3Df7 f1 89 c1 85 d2 0f 85-d8 01 00 00 6a 05 58 85 >> f6 0f 88 75 01 00 00 89-cb c1 fb 1f 89 ca 03 55 >> ss:esp=3D09 00 00 00 00 00 00 00-0a 00 00 00 02 00 00 00 >> 00 00 00 00 00 00 00 00-78 1f 09 00 33 45 04 00 >> BTX halted >>=20 >> I expect that "disk8" is what gpart show -p >> from a native boot showed as: >>=20 >> =3D> 1 60062499 da1 MBR (29G) >> 1 31 - free - (16K) >> 32 60062468 da1s1 fat32lba (29G) >>=20 >> (That gpart show -p output is in another of the >> list messages.) >>=20 >>> Also if you could test boot loader with UEFI - for example get to = loader prompt via usb/cd boot and then get the same lsdev -v output. >>=20 >> Still true given the above crash? Or, going the >> other way, should "drive8" be left as it is in >> order to be sure to do this test with the drive >> present? >>=20 >> If I do this test later, it will take a bit to >> get media to do it with. (It is about 4AM in the >> morning and I've yet to get to sleep.) >>=20 >> Note: I've never tried a UEFI based boot of FreeBSD >> on this machine (but the Windows 10 Pro x64 is EFI >> based). The only FreeBSD context using a EFI partition >> to boot that I have used is on an arm aarch64 >> Cortex-A57 system. >>=20 >>> I would be interested to see the sector size information and if the = UEFI loader does also have issues. >>=20 >> Understood. >>=20 >>> If it does, I=E2=80=99d like to see the outputs from commands: >>=20 >>> zpool status >>> zpool import >>=20 >> Independent of the UEFI test . . . >>=20 >> I do have a -r331924 head version on another one >> of the devices and can native-boot that. It still >> has its ZFS software (but a default loader without >> ZFS). >>=20 >> Trying from that context, hand transcribed: >>=20 >> # zpool status >> ZFS filesystem version: 5 >> ZFS storage pool version: features support (5000) >> no pools available >> # zpool import >> # >>=20 >> [That was based on the old (default) loader being >> a non-ZFS one.] >=20 >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 15:10:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A76FFFF6A3 for ; Mon, 22 Oct 2018 15:10:22 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta02.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (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 E10477E36B for ; Mon, 22 Oct 2018 15:10:21 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id EbVwg9i06CD6SEbVygY14U; Mon, 22 Oct 2018 14:49:06 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id w9MEn3ol040019 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 22 Oct 2018 10:49:04 -0400 (EDT) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] To: freebsd-current@freebsd.org Reply-To: lausts@acm.org From: Thomas Laus Subject: Head won't build tool-chain at r339586 Openpgp: preference=signencrypt Autocrypt: addr=lausts@acm.org; prefer-encrypt=mutual; keydata= xsDiBDx1NWwRBADARalI5I8kGeBYYYWnZB73T1fU4333yCuRokRvzlAZ5Zhb3hqsNdTEMheN FDjZSL8J5jeJtvSRinY2p09CxpAMoJR9zHLmHl+zEOY8fInbB+KiFtSfGf0blSEY9/+isQP9 xmUIQWUj0kwVtrns7m1HrYLiI07NVFzbHNKqQcbPuwCg0n/KKi+VJiUs5MqLKwGuPotGeZME AIluMetTQwfLyovundMwFYlSZ/Z8JjkMybqgKuiRrZnaBVVZ80NjAYZI73yAZPfQh9mvFxW9 ipc2tSALwDy/tYDpQRK0k+0EsDmwG/wM6OarkqSuFcYx+tP86+2+6Xitn6E/hriIWa/ZQVef /fx7dZzdwhXH6fd34v8o/BuqhawLBACs4MTMGbdSmyI56vCMXWY1yxRPmuygd4vUnXqYwlrM Ee/LjQdreg1zTAJnnW1K+PgOUW/jvS+uAbgxLa3i59/Z4Uu7nB6G1y+Y1cThojUsLnvoJlt1 4XE1U/vnOcvO3evo6knB1qjbAMsZGaVleiVKDq+7XE7swe4WtBJKbYJthc0cVGhvbWFzIExh dXMgPGxhdXN0c0BhY20ub3JnPsJ/BBMRAgA/AheAAh4BBgsJCAcDAgYVCAIJCgsEFgIDAQIZ ARYhBBloSoDtPqFEokqZd+v/gtRiCDbPBQJaRO3QBQkfyKbkAAoJEOv/gtRiCDbPi+UAnAm8 +zuC7S1JQEjx/OU4asYWvLdcAJ0V59C0iowNwnxyPHBnYBQpOoDScc7BTQRFspgcEAgAjXsi 9WqowAKZ7d2ix6t7fiYgu2QBGWq36NvN+cPBJIu0CnagL1v4W1UrRW/0cInLzgqlWrSU7SFg y1+rGBlusMHf8/faGeZD0XwMdYgTIYdjdK5VZ0GaRWUs0LbHAOJQkOFRHLMAEG8wrc3f1xrn uVJ4JPOA81kTmTXvYTyQNXJBySc0oNSgvSut8aBbNGBZhw9U2V3yXXnnMeWR8+DYrriYdOdR eK7S0LNN8TPY60PJx3KLN9vUY9Cb5Ly0NavF3wREPQqYlNfTMoG/GA/n8XB6SCoMj73oKCyw FLbckBUjFsl7wTeKKvU68V8kWG762fscXhOhRduETGrja09MbwADBQf/WiycmdfNtB41+vvT HQqz9tm3ZHAW2yE53CxfQpvlyS/KwnWgLjl/iV0SHRDede0NJ5yTEqPVhqq7WCdlqVsHPSpX FfvyOgbNmjPmOY/a1nW4UnWSqA7bgQvkthahhoLeHzkU8YKupW0m05RIBpqQER6HwBOksTq4 sWV/lUy1P0VT8GqqPLNklKe2BEu+KhuhLV6XwEG3VrHNoY6/R5CMGvBhZbtiUViCZktmxJAj Fq0VCcuj7+Oo52eq4BL2vMrzLX+2Ib1JSWid6t0N+grXxbr2mv7H2V2/4Vo0XI3IKxPX1mdG y9RBkbRUGyV9A8RlaS0QTnXvsxZTjOnmjxPX68JmBBgRAgAmAhsMFiEEGWhKgO0+oUSiSpl3 6/+C1GIINs8FAlpE7dwFCRaLREAACgkQ6/+C1GIINs9JdgCfeHMtCRjzubbkAvAVg5wQo7gF moUAoL39iRV66xSZ0w/I00RnFU3jsmiz Message-ID: Date: Mon, 22 Oct 2018 10:49:03 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfAxgIu1/zhzbXTup6kriIxYNB68JtfLEDCV8Bf28MYEFQbL/cqzIL+PnlJrIzZtgJZ40aoagswg7bk9ub5ucgO9/ns2ZDo5q+BskXt0WFT/JT+qMDljM o83gCIz6u+K2fIvkTWzWsYWOTOFUSl7lQxDP6+CPKF8+ixs/lohXZqOt 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, 22 Oct 2018 15:10:22 -0000 Group: I have been building HEAD for the past several years about every 2 weeks. I updated my base source today from r339234 to r339586 and the buildworld stops because a missing libarchive.so.7 dependency. It is looking for libcrypto.so.9 which has not been built at this part of the toolchain process yet. I deleted my source tree and performed a clean checkout. I deleted my /usr/obj/* and my /tmp directory. There wasn't any special procedure or notes in /usr/UPDATING to let me know of any other required steps to perform this update. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Mon Oct 22 16:05:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7BB71036B43 for ; Mon, 22 Oct 2018 16:05:16 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 86BC481BC3; Mon, 22 Oct 2018 16:05:16 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id D901F3C475F; Mon, 22 Oct 2018 16:05:08 +0000 (UTC) Date: Mon, 22 Oct 2018 16:05:08 +0000 From: Brooks Davis To: Rick Macklem Cc: Brooks Davis , FreeBSD Current , Josh Paetzel Subject: Re: which way to update export_args structure? Message-ID: <20181022160508.GB45769@spindle.one-eyed-alien.net> References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) 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, 22 Oct 2018 16:05:17 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 20, 2018 at 01:17:37AM +0000, Rick Macklem wrote: > Brooks Davis wrote: > > Yes, I think that's the right way foward. Thanks for following up. > >Rick Macklem wrote: > >> Just in case you missed it in the email thread, in your general questi= on below... > >> Did you mean/suggest that the fields of "struct export_args" be passed= in as > >> separate options to nmount(2)? > >> > >> This sounds like a reasonable idea to me and I can ping Josh Paetzel w= =2Er.t. the > >> changes to mountd.c to do it. (We are still in the testing stage for t= he updated > >> struct, so we might as well get that working first.) > >> > Well, Josh and I now have the code working via. passing the export_args > structure into the kernel using the "export" nmount(2) option. >=20 > I have coded a partial patch (not complete nor tested) to pass the fields= in as > separate nmount(2) arguments. Since the patch has gotten fairly large > already, I wanted to see if people do think this is the correct approach. > (I'll admit I don't understand why having the arguments would matter, giv= en > that only mountd does it. Would anyone run a 32bit mountd on a 64bit ker= nel?) >=20 > Anyhow, here's the partial patch showing the main changes when going from > passing in "struct export_args" to passing in separate fields: >=20 > --- kern/vfs_mount.c.nofsid2 2018-10-16 23:45:33.540348000 -0400 > +++ kern/vfs_mount.c 2018-10-19 20:01:14.927370000 -0400 > @@ -277,6 +277,7 @@ vfs_buildopts(struct uio *auio, struct v > size_t memused, namelen, optlen; > unsigned int i, iovcnt; > int error; > + char *cp; > =20 > opts =3D malloc(sizeof(struct vfsoptlist), M_MOUNT, M_WAITOK); > TAILQ_INIT(opts); > @@ -325,7 +326,7 @@ vfs_buildopts(struct uio *auio, struct v > } > if (optlen !=3D 0) { > opt->len =3D optlen; > - opt->value =3D malloc(optlen, M_MOUNT, M_WAITOK); > + opt->value =3D malloc(optlen + 1, M_MOUNT, M_WAITOK); > if (auio->uio_segflg =3D=3D UIO_SYSSPACE) { > bcopy(auio->uio_iov[i + 1].iov_base, opt->value, > optlen); > @@ -335,6 +336,8 @@ vfs_buildopts(struct uio *auio, struct v > if (error) > goto bad; > } > + cp =3D (char *)opt->value; > + cp[optlen] =3D '\0'; > } > } > vfs_sanitizeopts(opts); > @@ -961,6 +964,8 @@ vfs_domount_update( > int error, export_error, i, len; > uint64_t flag; > struct o2export_args o2export; > + char *endptr; > + int gotexp; > =20 > ASSERT_VOP_ELOCKED(vp, __func__); > KASSERT((fsflags & MNT_UPDATE) !=3D 0, ("MNT_UPDATE should be here")); > @@ -1033,36 +1038,117 @@ vfs_domount_update( > =20 > export_error =3D 0; > /* Process the export option. */ > - if (error =3D=3D 0 && vfs_getopt(mp->mnt_optnew, "export", &bufp, > - &len) =3D=3D 0) { > - /* Assume that there is only 1 ABI for each length. */ > - switch (len) { > - case (sizeof(struct oexport_args)): > - case (sizeof(struct o2export_args)): > - memset(&export, 0, sizeof(export)); > - memset(&o2export, 0, sizeof(o2export)); > - memcpy(&o2export, bufp, len); > - export.ex_flags =3D (u_int)o2export.ex_flags; > - export.ex_root =3D o2export.ex_root; > - export.ex_anon =3D o2export.ex_anon; > - export.ex_addr =3D o2export.ex_addr; > - export.ex_addrlen =3D o2export.ex_addrlen; > - export.ex_mask =3D o2export.ex_mask; > - export.ex_masklen =3D o2export.ex_masklen; > - export.ex_indexfile =3D o2export.ex_indexfile; > - export.ex_numsecflavors =3D o2export.ex_numsecflavors; > - for (i =3D 0; i < MAXSECFLAVORS; i++) > - export.ex_secflavors[i] =3D > - o2export.ex_secflavors[i]; > - export_error =3D vfs_export(mp, &export); > - break; > - case (sizeof(export)): > - bcopy(bufp, &export, len); > - export_error =3D vfs_export(mp, &export); > - break; > - default: > - export_error =3D EINVAL; > - break; > + if (error =3D=3D 0) { > + gotexp =3D 0; > + memset(&export, 0, sizeof(export)); > + if (vfs_getopt(mp->mnt_optnew, "export.exflags", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_flags =3D strtouq(bufp, &endptr, 0); > + if (endptr =3D=3D bufp) > + export_error =3D EINVAL; > + } This pattern involving strtouq seems wrong to me. We should probably pass a pointer to the integer type (which should always be an explicitly sized type). If it didn't contradict the first sentence of the description in vfs_getopt.9, I'd say we should pass int and long values in the length with a NULL buffer. > + if (vfs_getopt(mp->mnt_optnew, "export.root", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_root =3D strtouq(bufp, &endptr, 0); > + if (endptr =3D=3D bufp) > + export_error =3D EINVAL; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.anonuid", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_anon.cr_uid =3D strtouq(bufp, &endptr, 0); > + if (endptr !=3D bufp) > + export.ex_anon.cr_version =3D XUCRED_VERSION; > + else > + export_error =3D EINVAL; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.anongroups", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_anon.cr_ngroups =3D len / sizeof(gid_t); > + if (export.ex_anon.cr_ngroups > XU_NGROUPS) { > + export.ex_suppgroups =3D mallocarray( > + sizeof(gid_t), > + export.ex_anon.cr_ngroups, M_TEMP, > + M_WAITOK); > + memcpy(export.ex_suppgroups, bufp, len); > + } else > + memcpy(export.ex_anon.cr_groups, bufp, > + len); > + } > + if (vfs_getopt(mp->mnt_optnew, "export.addr", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_addr =3D malloc(len, M_TEMP, M_WAITOK); > + memcpy(export.ex_addr, bufp, len); > + export.ex_addrlen =3D len; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.mask", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_mask =3D malloc(len, M_TEMP, M_WAITOK); > + memcpy(export.ex_mask, bufp, len); > + export.ex_masklen =3D len; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.indexfile", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_indexfile =3D malloc(len + 1, M_TEMP, > + M_WAITOK); > + memcpy(export.ex_indexfile, bufp, len); > + export.ex_indexfile[len] =3D '\0'; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.secflavors", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_numsecflavors =3D len / sizeof(uint32_t); > + if (export.ex_numsecflavors <=3D MAXSECFLAVORS) > + memcpy(export.ex_secflavors, bufp, len); > + else > + export_error =3D EINVAL; > + } > + if (vfs_getopt(mp->mnt_optnew, "export.fsid", &bufp, > + &len) =3D=3D 0) { > + gotexp =3D 1; > + export.ex_fsid =3D strtouq(bufp, &endptr, 0); > + if (endptr =3D=3D bufp) > + export_error =3D EINVAL; > + } > + if (vfs_getopt(mp->mnt_optnew, "export", &bufp, &len) =3D=3D 0) { > + /* Assume that there is only 1 ABI for each length. */ > + switch (len) { > + case (sizeof(struct oexport_args)): > + case (sizeof(struct o2export_args)): > + memset(&export, 0, sizeof(export)); I think this is now redundant. > + memset(&o2export, 0, sizeof(o2export)); This is certainly redundant given that you immediately copy over it. > + memcpy(&o2export, bufp, len); > + export.ex_flags =3D (u_int)o2export.ex_flags; > + export.ex_root =3D o2export.ex_root; > + export.ex_anon =3D o2export.ex_anon; > + export.ex_addr =3D o2export.ex_addr; > + export.ex_addrlen =3D o2export.ex_addrlen; > + export.ex_mask =3D o2export.ex_mask; > + export.ex_masklen =3D o2export.ex_masklen; > + export.ex_indexfile =3D o2export.ex_indexfile; > + export.ex_numsecflavors =3D o2export.ex_numsecflavors; > + for (i =3D 0; i < MAXSECFLAVORS; i++) > + export.ex_secflavors[i] =3D > + o2export.ex_secflavors[i]; > + export_error =3D vfs_export(mp, &export); > + break; > + default: > + export_error =3D EINVAL; > + break; > + } > + } else if (gotexp !=3D 0) { > + if (export_error =3D=3D 0) > + export_error =3D vfs_export(mp, &export); > + free(export.ex_addr, M_TEMP); > + free(export.ex_mask, M_TEMP); > + free(export.ex_indexfile, M_TEMP); > + free(export.ex_suppgroups, M_TEMP); > } > } > =20 > So, what to people think about this? rick This is the direction I'd been thinking. FWIW, the usecase is more that once you've moved away from the struct it's easy to make incremental changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward size-independent interfaces helps both causes though. -- Brooks --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbzfU0AAoJEKzQXbSebgfARYkH+wU8A8kgPfMM4YqY2aH/iGFa DShMfk9QXYsq0scUXBx62LssofXMO6l3ptJo6OyfQFd7JW63K/GKE/5mM1/oXQmh SL7vSDqinh0TiqhZLhf1DEb94A96nZc9QnW29s+U1J0uSkrhCH3uk9MGBjqEHvmy L5S122NnFXxB9DMiZERUOD+VebjwBGBX30z6HLeO79b8ql3dIziTggGcnk6I90qz UvWz+02wr1g+TNy1QJJmKChhhtLwPiBOI6un09WwfLPGVf6b+Egwplvt1nWvCBdv VUZSBrgSFwurFb1uv53Cz/p9F32+qcdyPx6pl/P5TcktGUO+PNtBYLV6VoTn7F0= =JT8t -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-current@freebsd.org Mon Oct 22 16:26:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A969B1037812 for ; Mon, 22 Oct 2018 16:26:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x936.google.com (mail-ua1-x936.google.com [IPv6:2607:f8b0:4864:20::936]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4098F82E20 for ; Mon, 22 Oct 2018 16:26:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x936.google.com with SMTP id m18so10187048uaq.2 for ; Mon, 22 Oct 2018 09:26:36 -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=3jLHZnuVsyGnFbCHnV1R2lxzjTZ/hPnraRgZQVp1bCc=; b=vJysLy1SMgSRkKnbYwfhoGy1INLZ1GkISHpfTmlNMdB3frJhOe9sz6N9cV/6wSGe7/ cEoTvAvC4FeTZf0l0i7Fsari6Hg7Hsd9BUkXWVuVs9dSlNHp5lMS1GAAxxoUJVJxpBbZ +uyxhO2lFnjgB4w8LQEEcqN685V88b776FiS7gyCdvHQ7gts5c62vW5dqYKNaNuZedUE DlJJ/qymTPNScnnKAbp6UzqSJMY95OIOpNSIE5yOGVKwbr/ykYuGDyfibPpKsjsixC58 mWK0qwuHBKX5wLfL4h6xSu4VUE8PEMUBq+/Mr59+vgMh68FPZdC+YR9+H5UYZY3gAq/2 JpKg== 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=3jLHZnuVsyGnFbCHnV1R2lxzjTZ/hPnraRgZQVp1bCc=; b=hDq2DUd1CBhYxJa3VUUrhSGays7gkJWq3eXjmSzcabXHsHkYMSDd3vsimdIOmo6sps 5wBPI9nZ400EYBxReOr3/bmpoLDyeMKt5IIMHRm5GYNSYUHDCR5ScxZIhDPFzmhXcdGC 7sZl93IgMScd2Uo3WICUy0JS3IYruim31XjKa0TpHMBpglmIKw684e/yr9zq7LlWT42y pLPFHiuYxdMi+WczFd4S80xxEIeNM9v4jaV051CZ+/Voeo/0decKu+yqcVoHzOpvmKzQ apEc32x8vvstiH+OFCmO+RqsJop/pYi4s9XdusqI7MlGl27974+/JU2vony4UeGBqPxx 7LoA== X-Gm-Message-State: ABuFfoigJxlLNi0zq+ztNaBrMZUmcZu4Y6MxYYxD62M+td4edtpTiJcZ s+Oq1OAiAo9z61Q/7pk95wTclp402U5Wlf3Dg8yPAg== X-Google-Smtp-Source: ACcGV60yZOoYwEZQ4zUIlMefVNPWacJ672/LwGVvso5LaIY+v5eKKwHXiEOS+BasZJcIIBAHT3DKwrETFsSOHYmMsRE= X-Received: by 2002:ab0:a97:: with SMTP id d23mr20230823uak.39.1540225595474; Mon, 22 Oct 2018 09:26:35 -0700 (PDT) MIME-Version: 1.0 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> In-Reply-To: <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> From: Warner Losh Date: Mon, 22 Oct 2018 10:26:23 -0600 Message-ID: Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated To: Mark Millard Cc: Toomas Soome , Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List 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: Mon, 22 Oct 2018 16:26:37 -0000 On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote: > On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > > > On 22 Oct 2018, at 13:58, Mark Millard wrote: > >> > >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: > >>> > >>>> On 22 Oct 2018, at 06:30, Warner Losh wrote: > >>>> > >>>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > >>>> > >>>>> > >>>>> > >>>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < > >>>>> freebsd-stable@freebsd.org> wrote: > >>>>> > >>>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, > >>>>>> after installing the build, Hyper-V based boots are > >>>>>> working.] > >>>>>> > >>>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard > wrote: > >>>>>> > >>>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard > wrote: > >>>>>>> . . . > >>>> > >>> > >>> It would help to get output from loader lsdev -v command. > >> > >> That turned out to be very interesting: The non-ZFS loader > >> crashes during the listing, during disk8, which shows a > >> x0 instead of a x512. > >> > > > > Yes, thats the root cause there. The non-zfs loader does only *read* th= e > boot disk, thats why the issue was not revealed there. > > > > It would help to identify the sector size for that disk, at least from > OS, so we can compare with what we can get from INT13. > > > > I have pretty good idea what to look there, but I am afraid we need to > run few tests with you to understand why that disk is reporting sector si= ze > 0 there. > > > > > > Looks like I guessed wrong about the device > for "drive8". > > So I unplugged the only other external > storage device, so the original drives > 0-13 become 0-11 overall. > > The machine has a multi-LUN media card reader with > no cards plugged in. It is built-in rather than > one that I plugged into a port. It has 4 LUN's. > > So 8+4=3D12 and drives 0-7 show up with media before > it tries any of the 4 LUN's with no card in place. > > I conclude that "drive8" is an empty LUN in a media > card reader. > > I conclude that there is no sector size available for > any of the empty LUNs in the media reader. > I think you are probably right and we're hitting some divide by 0 error when we should just ignore the disk. Warner > > > > > >> Hand transcribed from pictures: > >> > >> OK lsdev -v > >> disk devices > >> disk0: BIOS drive C (937703088 x 512): > >> disk0p1: FreeBSD boot 512K > >> disk0p2: FreeBSD UFS 356G > >> disk0p3: FreeBSD swap 15G > >> disp0p4: FreeBSD swap 76G > >> disk1: BIOS drive D (16514064 x 512): > >> disk1s1: Linux 2048KB > >> disk1s2: Unknown 952GB > >> disk2: BIOS drive E (16514064 x 512): > >> disk2p1: Unknown 128MB > >> disk3: BIOS drive F (16514064 x 512): > >> disk3p1: Unknown 128MB > >> disk4: BIOS drive G (16434495 x 512): > >> disk2p1: Unknown 128MB > >> disk4p2: DOS/Windwos 1716GB > >> disk5: BIOS drive H (16434495 x 512): > >> disk5p1: FreeBSD boot 512K > >> disk5p2: FreeBSD UFS 176G > >> disk5p3: FreeBSD swap 193G > >> disp5p4: FreeBSD swap 15G > >> disk6: BIOS drive I (16434495 x 512): > >> disk6p1: Unknown 499MB > >> disk6p2: EFI 99MB > >> disk6p3: Unknown 16MB > >> disp6p4: DOS/Windows 886G > >> dis7: BIOS drive H (16434495 x 512): > >> disk7p1: FreeBSD boot 512K > >> disk7p2: FreeBSD UFS 953G > >> disk8: BIOS drive K (262144 x 0): > >> > >> int=3D00000000 err=3D00000000 efl=3D00010246 eip=3D000286bd > >> eax=3D00000000 ebx=3D72b50430 ecx=3D00000000 edx=3D00000000 > >> esi=3D00000000 edi=3D00092080 ebp=3D00091eec esp=3D00091ea8 > >> cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 > >> cs:eip=3Df7 f1 89 c1 85 d2 0f 85-d8 01 00 00 6a 05 58 85 > >> f6 0f 88 75 01 00 00 89-cb c1 fb 1f 89 ca 03 55 > >> ss:esp=3D09 00 00 00 00 00 00 00-0a 00 00 00 02 00 00 00 > >> 00 00 00 00 00 00 00 00-78 1f 09 00 33 45 04 00 > >> BTX halted > >> > >> I expect that "disk8" is what gpart show -p > >> from a native boot showed as: > >> > >> =3D> 1 60062499 da1 MBR (29G) > >> 1 31 - free - (16K) > >> 32 60062468 da1s1 fat32lba (29G) > >> > >> (That gpart show -p output is in another of the > >> list messages.) > >> > >>> Also if you could test boot loader with UEFI - for example get to > loader prompt via usb/cd boot and then get the same lsdev -v output. > >> > >> Still true given the above crash? Or, going the > >> other way, should "drive8" be left as it is in > >> order to be sure to do this test with the drive > >> present? > >> > >> If I do this test later, it will take a bit to > >> get media to do it with. (It is about 4AM in the > >> morning and I've yet to get to sleep.) > >> > >> Note: I've never tried a UEFI based boot of FreeBSD > >> on this machine (but the Windows 10 Pro x64 is EFI > >> based). The only FreeBSD context using a EFI partition > >> to boot that I have used is on an arm aarch64 > >> Cortex-A57 system. > >> > >>> I would be interested to see the sector size information and if the > UEFI loader does also have issues. > >> > >> Understood. > >> > >>> If it does, I=E2=80=99d like to see the outputs from commands: > >> > >>> zpool status > >>> zpool import > >> > >> Independent of the UEFI test . . . > >> > >> I do have a -r331924 head version on another one > >> of the devices and can native-boot that. It still > >> has its ZFS software (but a default loader without > >> ZFS). > >> > >> Trying from that context, hand transcribed: > >> > >> # zpool status > >> ZFS filesystem version: 5 > >> ZFS storage pool version: features support (5000) > >> no pools available > >> # zpool import > >> # > >> > >> [That was based on the old (default) loader being > >> a non-ZFS one.] > > > > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > From owner-freebsd-current@freebsd.org Mon Oct 22 16:49:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 057E21038943 for ; Mon, 22 Oct 2018 16:49:25 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 A8A7E844E4; Mon, 22 Oct 2018 16:49:24 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1C50921FBC; Mon, 22 Oct 2018 12:49:24 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Mon, 22 Oct 2018 12:49:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm1; bh=Trzjgumyq3pjQgP+4YQmiFDtFd8AonHNSoeB4Ng9t Uo=; b=HcZVZtQSDHUOmAM9Y0wYJB84154Rzy7dcWhzJlTaAFyXkiSTWLC92n+jv L/xquzIi/6PR5ScTpwQT/r6QKy8uXuZBwTmPTe1wAi9uP4v5/DMuuPRw/xAJYLgT Pyk26eTUzYkX959vrxxG6/VEZzF69G417Crir0P7ucg44WOAaHaquhRx5gRHPtTb U6dvuDmFapNhErYoDrG76h0BjbfzSBJeHFU9EsqRRKjaHJ+ys3pXvq9okj9MIHzd dZEKU+y6U2pdl/gF1VR8ZPTXTm5vcXVgqBkukplnpau0szOkj6UYLpM4tvE3XQPr rQ9E+s7VujP5CYK7yi1wLtB2aFUcQ== X-ME-Sender: X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 8DEC16227D; Mon, 22 Oct 2018 12:49:23 -0400 (EDT) Message-Id: <1540226963.490541.1550623304.5D6A95A6@webmail.messagingengine.com> From: Josh Paetzel To: Brooks Davis , Rick Macklem Cc: FreeBSD Current MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b315a288 Date: Mon, 22 Oct 2018 11:49:23 -0500 In-Reply-To: <20181022160508.GB45769@spindle.one-eyed-alien.net> References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> <20181022160508.GB45769@spindle.one-eyed-alien.net> Subject: Re: which way to update export_args structure? 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, 22 Oct 2018 16:49:25 -0000 On Mon, Oct 22, 2018, at 11:05 AM, Brooks Davis wrote: > > This is the direction I'd been thinking. FWIW, the usecase is more that > once you've moved away from the struct it's easy to make incremental > changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward > size-independent interfaces helps both causes though. > > -- Brooks > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) Brooks, What is the benefit or usecase for running a 32 bit mountd on a 64 bit kernel? -- Thanks, Josh Paetzel From owner-freebsd-current@freebsd.org Mon Oct 22 17:01:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 280D110390C7 for ; Mon, 22 Oct 2018 17:01:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-21.consmr.mail.bf2.yahoo.com (sonic312-21.consmr.mail.bf2.yahoo.com [74.6.128.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB84384F87 for ; Mon, 22 Oct 2018 17:01:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: kseHqggVM1njVTk2ZdUDlI10knkwfLuPJgMRo55EloMZKp4eOhhc4iVdLa.PH8W 5UO1DO1U.iqyEnsjhXxslnqxtfXz4DbkbRtmyVLZU.E8c_FIAxZjTWC6RXvPW0nZYXkmG9Mvhsok jv5bPFC0pqBkI_0AJjPsnZUlfrUyYS33_pfgOoZgCF.DWYvT65_Fjd6AoiDYzbMpotww6O2Pfkpb kEIPfrBEC7hn4NffOCPQ6QYC.C_7KAzNzAf8jgJx6Vyr5suLVsF06ND36nQMDXxBB_pZAeRIUh5r C7BXUrMkCGqyPt9p0Hs3qvGK1vxa41SMZa7pUQVl4adyr4jj4J0e9PxkiO2JGFaP1G4bxWY6HH8I Vjyv5b1Kr4_K3ZG26hu33S4iR7Qzrc62CKbYBuBW9EXYSZ7bkEvxp.64RsPfeclxmy1t8EEp3krj 3S6DFfr57lfu0GGTTDNVbxFeMNAnFdeVb3dFdqXZH1LJlITmE2PqHrH6oqfep2iHiWrsfcQXLSTx RCbMLLQ9FzuARO49Q5Fwb..ILZjlG.jnuwhLPvHYl7JIr6_U4Wv6_uZTF4zSR8EBCijoIUsj3E.s _JWkPcqHW4pMU6wHXnPnWi6G086eTbWTF1ltR97MpjVPPzX4vMZLeAaMlku7j1JzOj4ajSFX.dkP IBVW0BPyfTL_SPujp2x3Jh_G2avHJnZjWXTovZBA0DhPmJ3tV2QR__cE8NYrmMX0QAI6dZW_lQef h.xOTyysv2GOeaddXugQmMa4dfmnuNjGTIxsvdghA20xGzg4YXxt_oz4RMOIANQLG2Fzof38zKMC f0GmiP22q1JZfecL8dlY54oLvtpU1b1HjGQM3hc7jcNwws1Bl97OlmzOjrd9WwaCRpc__oseZDQc l4iUfmc9EXXPJDQsCovqm3scliVMHnGxFPNryS.Cmmb.ByrDf_7dW6o684aytD.N48eygQrKetcT jgT6LUcMYGtNWpQ_eq2fR0_hH6TfUhB86ZsXQqIsLXweNbaaSvd0aMQWOv0Gfd0Z73SUImEujRKh TqIpcLIuZGphzU5IZizhk8xkvxQ9K9iI67u4LLruh69KuyPaKupKfTYemESXKCEt51gqTNT9XgtJ Y0sx0obFX Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Mon, 22 Oct 2018 17:01:21 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp423.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 42bcd5d7160751ce49e2f3a1377a76b2; Mon, 22 Oct 2018 17:01:19 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: Date: Mon, 22 Oct 2018 10:01:17 -0700 Cc: Toomas Soome , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> To: Warner Losh , Konstantin Belousov X-Mailer: Apple Mail (2.3445.9.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: Mon, 22 Oct 2018 17:01:22 -0000 [I will note the the loader problem has been shown to not be involved in the kernel problem that this "Subject:" was originally for.] On 2018-Oct-22, at 9:26 AM, Warner Losh wrote: > On Mon, Oct 22, 2018 at 6:39 AM Mark Millard = wrote: >> On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: >>=20 >> > On 22 Oct 2018, at 13:58, Mark Millard = wrote: >> >>=20 >> >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >> >>>=20 >> >>>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >> >>>>=20 >> >>>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh = wrote: >> >>>>=20 >> >>>>>=20 >> >>>>>=20 >> >>>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable = < >> >>>>> freebsd-stable@freebsd.org> wrote: >> >>>>>=20 >> >>>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >> >>>>>> after installing the build, Hyper-V based boots are >> >>>>>> working.] >> >>>>>>=20 >> >>>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: >> >>>>>>=20 >> >>>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: >> >>>>>>> . . . >> >>>>=20 >> >>>=20 >> >>> It would help to get output from loader lsdev -v command. >> >>=20 >> >> That turned out to be very interesting: The non-ZFS loader >> >> crashes during the listing, during disk8, which shows a >> >> x0 instead of a x512. >> >>=20 >> >=20 >> > Yes, thats the root cause there. The non-zfs loader does only = *read* the boot disk, thats why the issue was not revealed there.=20 >> >=20 >> > It would help to identify the sector size for that disk, at least = from OS, so we can compare with what we can get from INT13. >> >=20 >> > I have pretty good idea what to look there, but I am afraid we need = to run few tests with you to understand why that disk is reporting = sector size 0 there. >> >=20 >> >=20 >>=20 >> Looks like I guessed wrong about the device >> for "drive8". >>=20 >> So I unplugged the only other external >> storage device, so the original drives >> 0-13 become 0-11 overall. >>=20 >> The machine has a multi-LUN media card reader with >> no cards plugged in. It is built-in rather than >> one that I plugged into a port. It has 4 LUN's. >>=20 >> So 8+4=3D12 and drives 0-7 show up with media before >> it tries any of the 4 LUN's with no card in place. >>=20 >> I conclude that "drive8" is an empty LUN in a media >> card reader. >>=20 >> I conclude that there is no sector size available for >> any of the empty LUNs in the media reader. >>=20 > I think you are probably right and we're hitting some divide by 0 = error when we should just ignore the disk. In the Hyper-V context, the loader and kernel do not see the 4-LUN media reader at all: only drives with normal freebsd-* style partitions and free space. This explains why I did not see a loader problem in that context. So I conclude that the kernel crash under Hyper-V associated with -r338807 is a separate issue even though WITHOUT_ZFS=3D seems to have avoided the crash. My plan is to continue with the -r338807 investigation after the loader problem is fixed in my builds. Then I've go back to trying builds using WITH_ZFS=3D (implicit), both native boots and Hyper-V based ones. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon Oct 22 17:02:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5978D1039415 for ; Mon, 22 Oct 2018 17:02:54 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 EC84F852B8 for ; Mon, 22 Oct 2018 17:02:53 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 18F833C475F; Mon, 22 Oct 2018 17:02:53 +0000 (UTC) Date: Mon, 22 Oct 2018 17:02:53 +0000 From: Brooks Davis To: Josh Paetzel Cc: Rick Macklem , FreeBSD Current Subject: Re: which way to update export_args structure? Message-ID: <20181022170253.GC45769@spindle.one-eyed-alien.net> References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> <20181022160508.GB45769@spindle.one-eyed-alien.net> <1540226963.490541.1550623304.5D6A95A6@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Content-Disposition: inline In-Reply-To: <1540226963.490541.1550623304.5D6A95A6@webmail.messagingengine.com> User-Agent: Mutt/1.9.4 (2018-02-28) 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, 22 Oct 2018 17:02:54 -0000 --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 22, 2018 at 11:49:23AM -0500, Josh Paetzel wrote: >=20 >=20 > On Mon, Oct 22, 2018, at 11:05 AM, Brooks Davis wrote: >=20 > >=20 > > This is the direction I'd been thinking. FWIW, the usecase is more that > > once you've moved away from the struct it's easy to make incremental > > changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward > > size-independent interfaces helps both causes though. > What is the benefit or usecase for running a 32 bit mountd on a 64 bit ke= rnel? In practice there isn't much of one. If the support had been there, I'd have tried to use it in CheriBSD to run with our 128-bit pointers. The bigger benefit is that now when you want to add something you just add it and handle the case when it's missing rather than having to add another compat shim for old structs. FWIW, I don't feel all that strongly about this case. If you two don't find it worthwhile to make this change, that's entierly reasonable. It just felt like the use of the export struct within the nmount interface was a conversion bandaid vs an intentional decision. -- Brooks --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbzgK8AAoJEKzQXbSebgfAaNEH/AwLxsk9EKHsjVV/OFz8099f qmyuTiZhZFg81cb/bn75PXSdxD6PkbtGZkssywdkBqMeGg9n7R9FL/7De8dWO7tv r8rRsg3HZjBMihcR3A3aUg/I9PhgEWpVvDNf7qjSq8H7SdxAR1DTplR7dHjNv9TW kxI98rsjTAQcaQgqZBmlnWqdaHqwlkrQqkVn5HD7nbz97v+d771FyHb465qbbEgZ theRnT/mWw9vliDjyJ0mKiy5Aocqx2C3/+M9NVAUvP8IcJgUVvFXud4T/oIeruL5 LxiRxem9BkvJa/hTt92l/E8LyYnSuwYgl3HGNASMCIM31bOaI2SpkOoIzIxPwiI= =MIJp -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7-- From owner-freebsd-current@freebsd.org Mon Oct 22 17:17:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CF5A104D0B1 for ; Mon, 22 Oct 2018 17:17:05 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A87A8635F for ; Mon, 22 Oct 2018 17:17:04 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9MHGrmv011543; Mon, 22 Oct 2018 10:16:53 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9MHGru3011542; Mon, 22 Oct 2018 10:16:53 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810221716.w9MHGru3011542@pdx.rh.CN85.dnsmgr.net> Subject: Re: A new stable/12 poudriere jail is inferior to its stable/12 host In-Reply-To: <20181021195122.GA5358@albert.catwhisker.org> To: David Wolfskill Date: Mon, 22 Oct 2018 10:16:53 -0700 (PDT) CC: Graham Perrin , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 22 Oct 2018 17:17:05 -0000 -- Start of PGP signed section. > On Sun, Oct 21, 2018 at 02:14:16PM +0100, Graham Perrin wrote: > > On 21/10/2018 13:31, David Wolfskill wrote: > > > On Sun, Oct 21, 2018 at 09:41:46AM +0100, Graham Perrin wrote: > > >> With the host already at r339438, > > >> creation of a jail (method: svn (other methods failed)) resulted in > > >> inferior version r339435. > > >> > > >> Is this normal? > > >> > > >> Re: I want the version of the jail to match the version of the host before I use poudriere to build kernel modules, and so on. > > >> > > >> .... > > > r339438 is a revision in stable/11. ? > > > > That's weird, because I recently successfully ran: > > > > svn switch '^/stable/12' /usr/src > > > > ? prior to a successful update of the system. > > Sure. On my laptop (for example), I have a local private SVN mirror > repo. It is currently at r339530. > > On each of 3 different slices, I have stable/11, stable/12, and > head; the corresponding working directories (which have been updated > since the repo was last updated) are currently at r339446, r339435, > and r339530 (respectively). > > FreeBSD's newvers.sh would put "r339530M" in the uname string for > each of those. > > My version places "r339446M/339530", "r339435M/339530", and > "r339530M/339530" (respectively) in the uname string to try to help > clarify which revision in each branch last affected that branch. Yes please! -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Oct 22 18:33:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD1001053527 for ; Mon, 22 Oct 2018 18:33:20 +0000 (UTC) (envelope-from michael.adm@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3674489E13 for ; Mon, 22 Oct 2018 18:33:17 +0000 (UTC) (envelope-from michael.adm@gmail.com) Received: by mail-ed1-x536.google.com with SMTP id t10-v6so6169265eds.12 for ; Mon, 22 Oct 2018 11:33:17 -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=r7DHKmZTuJIqPxyV/LWsxzp6T+Lcwz7LtSzFqebNNBI=; b=XHAyXrgXCUc8V4BtoCKypyfj1dePHcJUysad7KoWWnOwR2VWVwS/3kgkyiBP3HsDjw /WP4RSIfi7KKZpSX33XE84zcCvNwYnjwwDaDZLjyCIIdd7RVx2YsqkGcFcSCMS5BqGyt feSk8FP5qvUUYcepF1rjym22CVqUJ5MbNta3M0Sq+k+Hw14KHHoTGNj+yum+dTtGCZdo M/7IZA07TswhaSNXUt0WOgFcfsWXs5NaQPv2rjuNJ0874xNL5GEoY1cqJqacbzceJg4z A4FSXu+mDjqOCEXlu9Uhfv9dSfSbxRtMRPiTMvxszOTBngvsqMvy6zs02CJCDv3VmOhf NxxQ== 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=r7DHKmZTuJIqPxyV/LWsxzp6T+Lcwz7LtSzFqebNNBI=; b=uTuxdekxKhwraFqXOLUe5Pn/2bhYKl9na0fF26S3QsAOpe0kvDMIZQKpva/agDWaXY ktJWZKvCy3fcvPqOjczwlSFA6vZu6bsDiLObuiWWhrG2whIgntDzY/Tq6jwnrW6Ud55y KlZ6PG7j7gQvz2zqiAGEH79Gs03qOZAWUta0X0d+2MnWJqEFqhk4AcHK32tHlKnpuKjo JkTRSCVE1JMZP56vOiT1ZyTaeOrFO8daO/H7L63iZJE6nTfg+riqdquA6ObgvSCi9y2J /kGobqQ5atrxUVqPCLl6tvaIjKCLL6ahAWFcQg/oKidUOlw5yiVbfXKzpVPkK0m8T+bA kl7g== X-Gm-Message-State: ABuFfogr+cWUPK7Yzw/CW09sBVZR0A0JuXsPumWG4hudy/nzBb135wRG QAdROXZg70egrAXKc4TWWKYFv289VF8MBxd1yOqrYrdE X-Google-Smtp-Source: ACcGV62RVKhQqVGO73jBjsqQxewPUWpMCCvcV150c2CM/XQVGH/Qkrfg/MrkTqnVOvfkmwp8izti3uuG7zJIvZe+k7E= X-Received: by 2002:a17:906:c7d3:: with SMTP id dc19-v6mr35499613ejb.232.1540233195473; Mon, 22 Oct 2018 11:33:15 -0700 (PDT) MIME-Version: 1.0 From: Michael Pro Date: Mon, 22 Oct 2018 21:33:04 +0300 Message-ID: Subject: Hyper-V FreeBSD-CURRENT Guest and SR-IOV Pass Through To: FreeBSD-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Mon, 22 Oct 2018 19:08:33 +0000 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, 22 Oct 2018 18:33:21 -0000 When we try to enable the SR-IOV function of Network-Adapter in the properties of the virtual machine, we get f12rw kernel: hn0: got notify, nvs type 128 f12rw kernel: pcib0: on vmbus0 f12rw kernel: pcib0: failed to get resource for cfg window f12rw kernel: device_attach: pcib0 attach returned 6 In Windows Guest systems 10G SR-IOV function works perfect on this Hyper-V hosts. Hyper-V 2016 and Hyper-V 2019 (windows servers) HOSTS, Network adapters Intel X540-T2, X540-T1, X520-T1, X540-AT2 and 10G 2P X540-t. FreeBSD Guest system ( /var/log/messages ): f12rw syslogd: kernel boot file is /boot/kernel/kernel f12rw kernel: ---<>--- f12rw kernel: Copyright (c) 1992-2018 The FreeBSD Project. f12rw kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 f12rw kernel: The Regents of the University of California. All rights reserved. f12rw kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. f12rw kernel: FreeBSD 13.0-CURRENT #0 e1b49380456(master)-dirty: Sat Oct 20 15:26:15 EEST 2018 f12rw kernel: root@f12rw:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-DBGless amd64 f12rw kernel: FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) f12rw kernel: SRAT: Ignoring memory at addr 0x3f0000000 f12rw kernel: SRAT: Ignoring memory at addr 0x1000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x10000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x20000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x40000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x80000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x9e8000000 f12rw kernel: SRAT: Ignoring memory at addr 0x8800000000 f12rw kernel: SRAT: Ignoring memory at addr 0x18000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x30000000000 f12rw kernel: SRAT: Ignoring memory at addr 0x60000000000 f12rw kernel: SRAT: Ignoring memory at addr 0xc0000000000 f12rw kernel: VT(efifb): resolution 1024x768 f12rw kernel: Hyper-V Version: 10.0.17763 [SP0] f12rw kernel: Features=0x2e7f f12rw kernel: PM Features=0x0 [C2] f12rw kernel: Features3=0xbed7b2 f12rw kernel: Timecounter "Hyper-V" frequency 10000000 Hz quality 2000 f12rw kernel: module_register: cannot register pci/ixv from kernel; already loaded from if_ixv.ko f12rw kernel: Module pci/ixv failed to register: 17 f12rw kernel: CPU: Genuine Intel(R) CPU 0000 @ 2.90GHz (2900.00-MHz K8-class CPU) f12rw kernel: Origin="GenuineIntel" Id=0x406f0 Family=0x6 Model=0x4f Stepping=0 f12rw kernel: Features=0x1f83fbff f12rw kernel: Features2=0xfeda3203 f12rw kernel: AMD Features=0x2c100800 f12rw kernel: AMD Features2=0x121 f12rw kernel: Structured Extended Features=0x1c2fb9 f12rw kernel: Structured Extended Features3=0x20000000 f12rw kernel: XSAVE Features=0x1 f12rw kernel: IA32_ARCH_CAPS=0x4 f12rw kernel: Hypervisor: Origin = "Microsoft Hv" f12rw kernel: real memory = 16777216000 (16000 MB) f12rw kernel: avail memory = 16249954304 (15497 MB) f12rw kernel: Event timer "LAPIC" quality 100 f12rw kernel: ACPI APIC Table: f12rw kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs f12rw kernel: FreeBSD/SMP: 2 package(s) x 2 core(s) x 2 hardware threads f12rw kernel: random: unblocking device. f12rw kernel: ioapic0 irqs 0-23 on motherboard f12rw kernel: Launching APs: 1 3 2 6 7 4 5 f12rw kernel: Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000 f12rw kernel: random: entropy device external interface f12rw kernel: [ath_hal] loaded f12rw kernel: kbd0 at kbdmux0 f12rw kernel: module_register_init: MOD_LOAD (vesa, 0xffffffff811cdc50, 0) error 19 f12rw kernel: random: registering fast source Intel Secure Key RNG f12rw kernel: random: fast provider: "Intel Secure Key RNG" f12rw kernel: netmap: loaded module f12rw kernel: nexus0 f12rw kernel: efirtc0: on motherboard f12rw kernel: efirtc0: registered as a time-of-day clock, resolution 1.000000s f12rw kernel: cryptosoft0: on motherboard f12rw kernel: acpi0: on motherboard f12rw kernel: atrtc0: port 0x70-0x71 irq 8 on acpi0 f12rw kernel: atrtc0: registered as a time-of-day clock, resolution 1.000000s f12rw kernel: Event timer "RTC" frequency 32768 Hz quality 0 f12rw kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 f12rw kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 f12rw kernel: cpu0: on acpi0 f12rw kernel: acpi_syscontainer0: iomem 0xf8000000-0xffffffff,0xfe0000000-0xfffffffff on acpi0 f12rw kernel: vmbus0: on acpi_syscontainer0 f12rw kernel: vmbus_res0: irq 5 on acpi0 f12rw kernel: Timecounters tick every 10.000 msec f12rw kernel: ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to deny, logging disabled f12rw kernel: DUMMYNET 0xfffff801fc02b0c0 with IPv6 initialized (100409) f12rw kernel: load_dn_sched dn_sched RR loaded f12rw kernel: load_dn_sched dn_sched WF2Q+ loaded f12rw kernel: load_dn_sched dn_sched FIFO loaded f12rw kernel: load_dn_sched dn_sched FQ_CODEL loaded f12rw kernel: load_dn_sched dn_sched FQ_PIE loaded f12rw kernel: load_dn_sched dn_sched PRIO loaded f12rw kernel: load_dn_sched dn_sched QFQ loaded f12rw kernel: load_dn_aqm dn_aqm CODEL loaded f12rw kernel: load_dn_aqm dn_aqm PIE loaded f12rw kernel: usb_needs_explore_all: no devclass f12rw kernel: vmbus0: version 3.0 f12rw kernel: hvet0: on vmbus0 f12rw kernel: Event timer "Hyper-V" frequency 10000000 Hz quality 1000 f12rw kernel: hvkbd0: on vmbus0 f12rw kernel: hvheartbeat0: on vmbus0 f12rw kernel: hvkvp0: on vmbus0 f12rw kernel: hvshutdown0: on vmbus0 f12rw kernel: hvtimesync0: on vmbus0 f12rw kernel: hvtimesync0: RTT f12rw kernel: hvvss0: on vmbus0 f12rw kernel: hn0: on vmbus0 f12rw kernel: hn0: Ethernet address: 00:15:5d:00:8b:13 f12rw kernel: hn0: link state changed to UP f12rw kernel: storvsc0: on vmbus0 f12rw kernel: hn1: on vmbus0 f12rw kernel: da0 at storvsc0 bus 0 scbus0 target 0 lun 0 f12rw kernel: da0: Fixed Direct Access SPC-3 SCSI device f12rw kernel: da0: 300.000MB/s transfers f12rw kernel: da0: Command Queueing enabled f12rw kernel: da0: 61440MB (125829120 512 byte sectors) f12rw kernel: da1 at storvsc0 bus 0 scbus0 target 0 lun 1 f12rw kernel: da1: Fixed Direct Access SPC-3 SCSI device f12rw kernel: da1: 300.000MB/s transfers f12rw kernel: da1: Command Queueing enabled f12rw kernel: da1: 409600MB (838860800 512 byte sectors) f12rw kernel: hn1: Ethernet address: 00:15:5d:00:8b:14 f12rw kernel: hn1: link state changed to UP f12rw kernel: hn2: on vmbus0 f12rw kernel: hn2: Ethernet address: 00:15:5d:00:8b:1b f12rw kernel: hn2: link state changed to UP f12rw kernel: hn3: on vmbus0 f12rw kernel: hn3: Ethernet address: 00:15:5d:00:8b:1c f12rw kernel: hn3: link state changed to UP f12rw kernel: hn4: on vmbus0 f12rw kernel: hn4: Ethernet address: 00:15:5d:00:8b:29 f12rw kernel: hn4: link state changed to UP f12rw kernel: Trying to mount root from ufs:/dev/da0p2 [rw]... f12rw kernel: lo0: link state changed to UP f12rw kernel: . f12rw login[1288]: ROOT LOGIN (root) ON ttyv0 From owner-freebsd-current@freebsd.org Mon Oct 22 19:53:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6A8A106B20E; Mon, 22 Oct 2018 19:53:49 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it1-f173.google.com (mail-it1-f173.google.com [209.85.166.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F1D08FADA; Mon, 22 Oct 2018 19:53:49 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it1-f173.google.com with SMTP id m15so14136986itl.4; Mon, 22 Oct 2018 12:53:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bQtoNQXXJbKvVmkPES/dF69kfQql03uL5TMcfS4Tga8=; b=ibKkQlSq0w4AMC2pf21EX4dW1MIdwA0dyNWWRQO9h1xWLXuwAnxCxzumQ0y5A1Y2+q DKdZ24Ak65MXEP6WW4ePC5dGp6JKcA1M8n2EK0ccmtofdbTJYVOPbIIJb4FPQScQY4Hz DGgFDwvqT7b3pRy6PTI3D3vWeH1OwiH2z64WKagvMH2lXjb06LCm1uZYmaHd51eqNLjK T8mSAbV9ps/KUlNpVu2+kvCkBcEYJS8ORaeOaRqlEmhxCNf70AVU22TNChArgjBrHsqV kg0VHaFwJ0JfjaOtJiuKlW2nto0rCqI+4gZ1Zt21WqIr+YKooYttxl63Y/RZK3P95Sjq DKCA== X-Gm-Message-State: ABuFfoiHycFK0tLdu4U8BET9NcDaDbS/cqRYBSWk9aVV0MgW/v0yMV0h WdDMSkRKbnGorGihVgOeY5X7YrURlxRgcvtKS08/36FZtEc= X-Google-Smtp-Source: ACcGV6362Z/9/M86CUOw1kCpVBZcSLUZ9aDAamXDu88FAY2rymm8ftCqr+AdeWLjlug7nsWdasanlEQwY5x7VupC/4Q= X-Received: by 2002:a24:430d:: with SMTP id s13-v6mr10344631itb.33.1540237577832; Mon, 22 Oct 2018 12:46:17 -0700 (PDT) MIME-Version: 1.0 From: Ed Maste Date: Mon, 22 Oct 2018 11:47:34 -0400 Message-ID: Subject: ctm(1) deprecation in the FreeBSD base system? To: FreeBSD Current , ctm-users@freebsd.org 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: Mon, 22 Oct 2018 19:53:50 -0000 The ctm(1) client remains in the FreeBSD base system, although FreeBSD-hosted ctm infrastructure was shut down some time ago. I suspect it is time to remove it from the base system (perhaps making a port). How much use does ctm have these days? From owner-freebsd-current@freebsd.org Mon Oct 22 19:57:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8346F106B577; Mon, 22 Oct 2018 19:57:44 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD5748FE73; Mon, 22 Oct 2018 19:57:43 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9MJvdxo012869; Mon, 22 Oct 2018 12:57:39 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9MJvdXx012868; Mon, 22 Oct 2018 12:57:39 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: To: Ed Maste Date: Mon, 22 Oct 2018 12:57:39 -0700 (PDT) CC: FreeBSD Current , ctm-users@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 22 Oct 2018 19:57:44 -0000 > The ctm(1) client remains in the FreeBSD base system, although > FreeBSD-hosted ctm infrastructure was shut down some time ago. I > suspect it is time to remove it from the base system (perhaps making a > port). > > How much use does ctm have these days? I do not know that other than I do know that I have seen one data point in the last 14 days of a user who was infact using ctm though I can not associate a username/email address with that memory. A search of the last 30 days of @freebsd.org public mail may yield a hit. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Oct 22 20:10:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38BCB106BD5A; Mon, 22 Oct 2018 20:10:17 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id C8D3D707AB; Mon, 22 Oct 2018 20:10:16 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 7EFFA1483E; Mon, 22 Oct 2018 20:10:09 +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 w9MKA8RS007290 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Oct 2018 20:10:08 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w9MKA7Hd007289; Mon, 22 Oct 2018 20:10:07 GMT (envelope-from phk) To: "Rodney W. Grimes" cc: Ed Maste , FreeBSD Current , ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-reply-to: <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net> From: "Poul-Henning Kamp" References: <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7287.1540239007.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Oct 2018 20:10:07 +0000 Message-ID: <7288.1540239007@critter.freebsd.dk> 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, 22 Oct 2018 20:10:17 -0000 -------- In message <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net>, "Rodney W= . Gri mes" writes: >I do not know that other than I do know that I have seen >one data point in the last 14 days of a user who was infact >using ctm though I can not associate a username/email address >with that memory. > >A search of the last 30 days of @freebsd.org public mail >may yield a hit. I think Julian Stacy is still running CTM generation ? -- = 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 Mon Oct 22 20:17:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEE36106C32F for ; Mon, 22 Oct 2018 20:17:17 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-it1-f174.google.com (mail-it1-f174.google.com [209.85.166.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FE3A70E22 for ; Mon, 22 Oct 2018 20:17:17 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by mail-it1-f174.google.com with SMTP id k206-v6so13379351ite.0 for ; Mon, 22 Oct 2018 13:17:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UtDPvV/z6Gfd1HXZftTDxPJz3qJJQc4qE4w6AUzIjro=; b=Sq8wNZqRUNaMCxHNYcvt8MRxh+WsXOzYTgSfih0u/U7dNRdNpT+tLtdrBjdPYI1MdB kQPBl0siMefJCxdCVuEKVKc9B70ABiUPw8kgyiBr1zLj8V+M0ma5XC0KujOAfVEuYQXw EjT0eA7iHUdS69RVa0F1GsosiceUGwRs4iO1E0UjuVxiQP/AG3g3o4u+WwfUkAlq9GtR 8JXGHbU7qbpHW8FZCZx0yak1N7iwMHrc6Z2g7MhqjGdywh18xN1/0ZV2qzASiaqxCX1i TBErYQHbhmaeg9EBAk4qTyXxJjUk/ZieFCnMe2Nb8exiW5ACBnKk5+iKbtiNoGllD5x2 ES8w== X-Gm-Message-State: ABuFfojqtMZAHIXzChig1FRx67efqpEF8YcKhiW41CkT2uFJlPDGxY1b jrh5ZxJHgU3MVwZHuCuPgFzTfVAj X-Google-Smtp-Source: ACcGV61P1OWMgPMIGFy5jXfZ2Y6Y9rhnhY2bvPwFgweoLkdpCH2vZ9nVhT/sdcIop2jaXjQricu2ww== X-Received: by 2002:a24:cf07:: with SMTP id y7-v6mr11475745itf.161.1540239430695; Mon, 22 Oct 2018 13:17:10 -0700 (PDT) Received: from mail-it1-f176.google.com (mail-it1-f176.google.com. [209.85.166.176]) by smtp.gmail.com with ESMTPSA id p8-v6sm4479443iog.60.2018.10.22.13.17.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Oct 2018 13:17:10 -0700 (PDT) Received: by mail-it1-f176.google.com with SMTP id k206-v6so13379250ite.0 for ; Mon, 22 Oct 2018 13:17:09 -0700 (PDT) X-Received: by 2002:a24:1082:: with SMTP id 124-v6mr3144562ity.86.1540239429489; Mon, 22 Oct 2018 13:17:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eric Joyner Date: Mon, 22 Oct 2018 13:16:32 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Hyper-V FreeBSD-CURRENT Guest and SR-IOV Pass Through To: michael.adm@gmail.com Cc: FreeBSD Current 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, 22 Oct 2018 20:17:18 -0000 None of the Intel networking drivers on FreeBSD support Hyper-V. Could you try "Discrete Device Assignment" instead? Create the VFs on the host somehow, then pass them through to the VMs? That looks like it might work for the FreeBSD VF drivers. - Eric On Mon, Oct 22, 2018 at 12:11 PM Michael Pro wrote: > When we try to enable the SR-IOV function of Network-Adapter in the > properties of the virtual machine, we get > > f12rw kernel: hn0: got notify, nvs type 128 > f12rw kernel: pcib0: on vmbus0 > f12rw kernel: pcib0: failed to get resource for cfg window > f12rw kernel: device_attach: pcib0 attach returned 6 > > In Windows Guest systems 10G SR-IOV function works perfect on this > Hyper-V hosts. > > Hyper-V 2016 and Hyper-V 2019 (windows servers) HOSTS, > Network adapters Intel X540-T2, X540-T1, X520-T1, X540-AT2 and 10G 2P > X540-t. > > FreeBSD Guest system ( /var/log/messages ): > > f12rw syslogd: kernel boot file is /boot/kernel/kernel > f12rw kernel: ---<>--- > f12rw kernel: Copyright (c) 1992-2018 The FreeBSD Project. > f12rw kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, > 1992, 1993, 1994 > f12rw kernel: The Regents of the University of California. All > rights reserved. > f12rw kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. > f12rw kernel: FreeBSD 13.0-CURRENT #0 e1b49380456(master)-dirty: Sat > Oct 20 15:26:15 EEST 2018 > f12rw kernel: > root@f12rw:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-DBGless amd64 > f12rw kernel: FreeBSD clang version 6.0.1 (tags/RELEASE_601/final > 335540) (based on LLVM 6.0.1) > f12rw kernel: SRAT: Ignoring memory at addr 0x3f0000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x1000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x10000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x20000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x40000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x80000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x9e8000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x8800000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x18000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x30000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0x60000000000 > f12rw kernel: SRAT: Ignoring memory at addr 0xc0000000000 > f12rw kernel: VT(efifb): resolution 1024x768 > f12rw kernel: Hyper-V Version: 10.0.17763 [SP0] > f12rw kernel: > > Features=0x2e7f > f12rw kernel: PM Features=0x0 [C2] > f12rw kernel: > Features3=0xbed7b2 > f12rw kernel: Timecounter "Hyper-V" frequency 10000000 Hz quality 2000 > f12rw kernel: module_register: cannot register pci/ixv from kernel; > already loaded from if_ixv.ko > f12rw kernel: Module pci/ixv failed to register: 17 > f12rw kernel: CPU: Genuine Intel(R) CPU 0000 @ 2.90GHz (2900.00-MHz > K8-class CPU) > f12rw kernel: Origin="GenuineIntel" Id=0x406f0 Family=0x6 > Model=0x4f Stepping=0 > f12rw kernel: > > Features=0x1f83fbff > f12rw kernel: > > Features2=0xfeda3203 > f12rw kernel: AMD Features=0x2c100800 > f12rw kernel: AMD Features2=0x121 > f12rw kernel: Structured Extended > > Features=0x1c2fb9 > f12rw kernel: Structured Extended Features3=0x20000000 > f12rw kernel: XSAVE Features=0x1 > f12rw kernel: IA32_ARCH_CAPS=0x4 > f12rw kernel: Hypervisor: Origin = "Microsoft Hv" > f12rw kernel: real memory = 16777216000 (16000 MB) > f12rw kernel: avail memory = 16249954304 (15497 MB) > f12rw kernel: Event timer "LAPIC" quality 100 > f12rw kernel: ACPI APIC Table: > f12rw kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > f12rw kernel: FreeBSD/SMP: 2 package(s) x 2 core(s) x 2 hardware threads > f12rw kernel: random: unblocking device. > f12rw kernel: ioapic0 irqs 0-23 on motherboard > f12rw kernel: Launching APs: 1 3 2 6 7 4 5 > f12rw kernel: Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000 > f12rw kernel: random: entropy device external interface > f12rw kernel: [ath_hal] loaded > f12rw kernel: kbd0 at kbdmux0 > f12rw kernel: module_register_init: MOD_LOAD (vesa, > 0xffffffff811cdc50, 0) error 19 > f12rw kernel: random: registering fast source Intel Secure Key RNG > f12rw kernel: random: fast provider: "Intel Secure Key RNG" > f12rw kernel: netmap: loaded module > f12rw kernel: nexus0 > f12rw kernel: efirtc0: on motherboard > f12rw kernel: efirtc0: registered as a time-of-day clock, resolution > 1.000000s > f12rw kernel: cryptosoft0: on motherboard > f12rw kernel: acpi0: on motherboard > f12rw kernel: atrtc0: port 0x70-0x71 irq 8 on acpi0 > f12rw kernel: atrtc0: registered as a time-of-day clock, resolution > 1.000000s > f12rw kernel: Event timer "RTC" frequency 32768 Hz quality 0 > f12rw kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > f12rw kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port > 0x408-0x40b on acpi0 > f12rw kernel: cpu0: on acpi0 > f12rw kernel: acpi_syscontainer0: iomem > 0xf8000000-0xffffffff,0xfe0000000-0xfffffffff on acpi0 > f12rw kernel: vmbus0: on acpi_syscontainer0 > f12rw kernel: vmbus_res0: irq 5 on acpi0 > f12rw kernel: Timecounters tick every 10.000 msec > f12rw kernel: ipfw2 (+ipv6) initialized, divert enabled, nat enabled, > default to deny, logging disabled > f12rw kernel: DUMMYNET 0xfffff801fc02b0c0 with IPv6 initialized (100409) > f12rw kernel: load_dn_sched dn_sched RR loaded > f12rw kernel: load_dn_sched dn_sched WF2Q+ loaded > f12rw kernel: load_dn_sched dn_sched FIFO loaded > f12rw kernel: load_dn_sched dn_sched FQ_CODEL loaded > f12rw kernel: load_dn_sched dn_sched FQ_PIE loaded > f12rw kernel: load_dn_sched dn_sched PRIO loaded > f12rw kernel: load_dn_sched dn_sched QFQ loaded > f12rw kernel: load_dn_aqm dn_aqm CODEL loaded > f12rw kernel: load_dn_aqm dn_aqm PIE loaded > f12rw kernel: usb_needs_explore_all: no devclass > f12rw kernel: vmbus0: version 3.0 > f12rw kernel: hvet0: on vmbus0 > f12rw kernel: Event timer "Hyper-V" frequency 10000000 Hz quality 1000 > f12rw kernel: hvkbd0: on vmbus0 > f12rw kernel: hvheartbeat0: on vmbus0 > f12rw kernel: hvkvp0: on vmbus0 > f12rw kernel: hvshutdown0: on vmbus0 > f12rw kernel: hvtimesync0: on vmbus0 > f12rw kernel: hvtimesync0: RTT > f12rw kernel: hvvss0: on vmbus0 > f12rw kernel: hn0: on vmbus0 > f12rw kernel: hn0: Ethernet address: 00:15:5d:00:8b:13 > f12rw kernel: hn0: link state changed to UP > f12rw kernel: storvsc0: on vmbus0 > f12rw kernel: hn1: on vmbus0 > f12rw kernel: da0 at storvsc0 bus 0 scbus0 target 0 lun 0 > f12rw kernel: da0: Fixed Direct Access SPC-3 SCSI > device > f12rw kernel: da0: 300.000MB/s transfers > f12rw kernel: da0: Command Queueing enabled > f12rw kernel: da0: 61440MB (125829120 512 byte sectors) > f12rw kernel: da1 at storvsc0 bus 0 scbus0 target 0 lun 1 > f12rw kernel: da1: Fixed Direct Access SPC-3 SCSI > device > f12rw kernel: da1: 300.000MB/s transfers > f12rw kernel: da1: Command Queueing enabled > f12rw kernel: da1: 409600MB (838860800 512 byte sectors) > f12rw kernel: hn1: Ethernet address: 00:15:5d:00:8b:14 > f12rw kernel: hn1: link state changed to UP > f12rw kernel: hn2: on vmbus0 > f12rw kernel: hn2: Ethernet address: 00:15:5d:00:8b:1b > f12rw kernel: hn2: link state changed to UP > f12rw kernel: hn3: on vmbus0 > f12rw kernel: hn3: Ethernet address: 00:15:5d:00:8b:1c > f12rw kernel: hn3: link state changed to UP > f12rw kernel: hn4: on vmbus0 > f12rw kernel: hn4: Ethernet address: 00:15:5d:00:8b:29 > f12rw kernel: hn4: link state changed to UP > f12rw kernel: Trying to mount root from ufs:/dev/da0p2 [rw]... > f12rw kernel: lo0: link state changed to UP > f12rw kernel: . > f12rw login[1288]: ROOT LOGIN (root) ON ttyv0 > _______________________________________________ > 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 Oct 22 20:38:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2CD1106D7A2; Mon, 22 Oct 2018 20:38:27 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4314F728B7; Mon, 22 Oct 2018 20:38:27 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9MKcPSV013244; Mon, 22 Oct 2018 13:38:25 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9MKcP4L013243; Mon, 22 Oct 2018 13:38:25 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: <7288.1540239007@critter.freebsd.dk> To: Poul-Henning Kamp Date: Mon, 22 Oct 2018 13:38:25 -0700 (PDT) CC: Ed Maste , FreeBSD Current , ctm-users@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 22 Oct 2018 20:38:27 -0000 > -------- > In message <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net>, "Rodney W. Gri > mes" writes: > > >I do not know that other than I do know that I have seen > >one data point in the last 14 days of a user who was infact > >using ctm though I can not associate a username/email address > >with that memory. > > > >A search of the last 30 days of @freebsd.org public mail > >may yield a hit. > > I think Julian Stacy is still running CTM generation ? Ah, yes, that brought back enough brain cells, confirmed that is who I saw with ctm usage. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Oct 22 20:52:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AA7FFD60CF for ; Mon, 22 Oct 2018 20:52:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7EF673290 for ; Mon, 22 Oct 2018 20:52:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2d.google.com with SMTP id c10so30578366vsk.2 for ; Mon, 22 Oct 2018 13:52: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=U++9Dttxuih7I5jqVunXWSWpoCVEp097mlCVDCo9z4U=; b=onjRkGXq6C6Vwq0qykim6PD8DlAU9Op1AJM5z7jwkJh1+kqTCUwotlnOZkVHJHkB4y rL3b1p/cBgfBwA9t43J2zEhXd7VZg/6sl+BOVQfd8h5mmWniwK7csDqY8GFoq3LKrAD3 t9geGK6ZTmMqFKzhx5OfTgMsO3iUpj/LUR7x0zQojp8dzTjPF0Z9lPF/GdjMhJdaSIQc ESTaAgTcz71KR32AhfJMKS0EwOEZhasO+555uMv2hMiImpQDzj3skxwukVgPC9kaYP8O OnZepCp9CDrqjgLfrCPyfOOl3Uhcm8XwzUj+Djw+5ekjXFTrpr4wq5JwlrUD3XE8Huji 2LKQ== 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=U++9Dttxuih7I5jqVunXWSWpoCVEp097mlCVDCo9z4U=; b=cXVYPNgBCf4H6qjDXGGlZBKPj3uPB8WU7JNlDaoJEe3FR0cjOZ4e+gOmirK+x1Di5H Rl060b9h5pWE/4E0rOWhr5W24z6p+vJRnMeZI1Qx87nEStMesYptdLehC8xYBr87igoA z9yfFQDWQv+DJKot6x1gQbUDwfmCJE7W4nQElJ/3C9JBl8EtOFbFkcBStc7ZYL1mE/kL fYqdP6yKDSCMV1j0CYX2SobtHU4Kndw73032CcfaqRegdnfw6zh8WcuDxNnSrvo4DVsw 2AHbShCFpvVkP4G3veNjXcfM+Dd3It0XuCDSDgmZU7EDT0Y9ngaStVsz8v48Esg81AGy eOXg== X-Gm-Message-State: ABuFfogspcJmbHV5iBGcIr3Xi1f4X3Uyk2FaPmXk5zux0Sb+sDyWBYe9 qikfR0y5LzeDUEmFp0OTYKH2u70dzOJ2mxYAM/YqPA== X-Google-Smtp-Source: ACcGV62kRlpgOeFdXPOkGCjHPaB+d01Bcumms3XYpaD5mCfdM5lVi3T85dzuqV/qusCODJ8L4kL4d+WqUAO10Uf3y9g= X-Received: by 2002:a67:f757:: with SMTP id w23mr19705491vso.76.1540241550965; Mon, 22 Oct 2018 13:52:30 -0700 (PDT) MIME-Version: 1.0 References: <7288.1540239007@critter.freebsd.dk> <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Mon, 22 Oct 2018 14:52:19 -0600 Message-ID: Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: "Rodney W. Grimes" Cc: Poul-Henning Kamp , Ed Maste , FreeBSD Current , ctm-users@freebsd.org 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, 22 Oct 2018 20:52:32 -0000 On Mon, Oct 22, 2018 at 2:40 PM Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > -------- > > In message <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net>, > "Rodney W. Gri > > mes" writes: > > > > >I do not know that other than I do know that I have seen > > >one data point in the last 14 days of a user who was infact > > >using ctm though I can not associate a username/email address > > >with that memory. > > > > > >A search of the last 30 days of @freebsd.org public mail > > >may yield a hit. > > > > I think Julian Stacy is still running CTM generation ? > > Ah, yes, that brought back enough brain cells, > confirmed that is who I saw with ctm usage. > Do we need it in base? Or can we make it a port? Warner From owner-freebsd-current@freebsd.org Mon Oct 22 20:58:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42164FD646F; Mon, 22 Oct 2018 20:58:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C2501736B0; Mon, 22 Oct 2018 20:58:39 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CCDC.dip0.t-ipconnect.de [46.82.204.220]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w9MKwVS8055417 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2018 20:58:35 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w9MKwQwG027209; Mon, 22 Oct 2018 22:58:26 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w9MKw2dE050298; Mon, 22 Oct 2018 22:58:14 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201810222058.w9MKw2dE050298@fire.js.berklix.net> To: "Rodney W. Grimes" cc: Poul-Henning Kamp , ctm-users@freebsd.org, FreeBSD Current , Ed Maste Subject: Re: ctm(1) deprecation in the FreeBSD base system? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 22 Oct 2018 13:38:25 -0700." <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> Date: Mon, 22 Oct 2018 22:58:02 +0200 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, 22 Oct 2018 20:58:40 -0000 Hi, Reference: > From: "Rodney W. Grimes" > Date: Mon, 22 Oct 2018 13:38:25 -0700 (PDT) "Rodney W. Grimes" wrote: > > -------- > > In message <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net>, "Rodney W. Gri > > mes" writes: > > > > >I do not know that other than I do know that I have seen > > >one data point in the last 14 days of a user who was infact > > >using ctm though I can not associate a username/email address > > >with that memory. > > > > > >A search of the last 30 days of @freebsd.org public mail > > >may yield a hit. > > > > I think Julian Stacy is still running CTM generation ? > > Ah, yes, that brought back enough brain cells, > confirmed that is who I saw with ctm usage. Stephen Montgomery generates the CTM deltas, & sends them through the mailman lists on freebsd.org (which arent listed but are there as far as I recall) , & as he doesn't have enough space, he also rsyncs bases & deltas to the ftp repository server I host Not that many use CTM, perhaps mostly because many have unrestricted flat rate free bandwidth 24/7, so they can fetch another easier way, & partly because even where CTM really scores, for those with intermittent access or expensive data transfer (eg some mobile tarrifs perhaps), some of those people arent aware of CTM, as we havent kept up the www.freebsd.org etc docs. http://ctm.berklix.org Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.uk https://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative From owner-freebsd-current@freebsd.org Mon Oct 22 20:58:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 980C7FD648F; Mon, 22 Oct 2018 20:58:46 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 2FD89736C0; Mon, 22 Oct 2018 20:58:46 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 39DE514831; Mon, 22 Oct 2018 20:58:45 +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 w9MKwivC007834 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Oct 2018 20:58:44 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w9MKwiLS007833; Mon, 22 Oct 2018 20:58:44 GMT (envelope-from phk) To: Warner Losh cc: "Rodney W. Grimes" , Ed Maste , FreeBSD Current , ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-reply-to: From: "Poul-Henning Kamp" References: <7288.1540239007@critter.freebsd.dk> <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7831.1540241924.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Oct 2018 20:58:44 +0000 Message-ID: <7832.1540241924@critter.freebsd.dk> 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, 22 Oct 2018 20:58:46 -0000 -------- In message , Warner Losh writes: >> > I think Julian Stacy is still running CTM generation ? >> >> Ah, yes, that brought back enough brain cells, >> confirmed that is who I saw with ctm usage. > >Do we need it in base? Or can we make it a port? Absolutely make it a port! -- = 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 Mon Oct 22 21:09:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37AB4FD6A5F for ; Mon, 22 Oct 2018 21:09:43 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ABBE073DDF; Mon, 22 Oct 2018 21:09:42 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CCDC.dip0.t-ipconnect.de [46.82.204.220]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w9ML9ZcM055720 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2018 21:09:39 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w9ML9UfP027280; Mon, 22 Oct 2018 23:09:30 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w9ML96bF050497; Mon, 22 Oct 2018 23:09:18 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201810222109.w9ML96bF050497@fire.js.berklix.net> To: Stefan Esser cc: FreeBSD Current , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= , Stefan Esser Subject: Re: careless commits disrupt From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Fri, 12 Oct 2018 11:44:59 +0200." Date: Mon, 22 Oct 2018 23:09:06 +0200 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, 22 Oct 2018 21:09:43 -0000 Hi, Reference: > From: Stefan Esser > Date: Fri, 12 Oct 2018 11:44:59 +0200 Stefan Esser wrote: > Am 12.10.18 um 07:39 schrieb Dag-Erling Sm�rgrav: > > Julian H. Stacey writes: > >> Stefan Esser writes: > >>> You should also delete old files: > >>> > >>> cd /usr/src > >>> make delete-old > >>> make delete-old-libs > >> I just ran that. It deleted lots of stuff. & I'd only run it 2 days ago. > >> I should have run it just before buildworld though. > >> It's not suggested in the top of > >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > >> just at base of page. > > > > That's because you should *never* run delete-old or delete-old-libs from > > a source tree that is newer than your installed system. It may delete > > files which have been obsoleted by changes you haven't yet built and > > installed, to the point where you may be unable to build and install > > those changes. In this particular case, it will, at the very least, > > break ssh and svn / svnlite. > > Yes, sorry, running make delete-old-libs before buildworld is no good > idea, unless the old libraries have been copied to /usr/lib/compat before. > > > The advice to run "make delete-old-libs" came from the following message > from Glen Barber: > > https://lists.freebsd.org/pipermail/freebsd-current/2018-October/071581.html > > But the advice was not to delete old files before make buildworld, but only > before starting the required port upgrades ... > > > I might have mentioned, that I always preserve old shared libraries in > /usr/lib/compat before running "make delete-old-libs". Good idea, are you doing that manually, or do you have a patch to share ? > This allows to run > old binaries, but prevents linking of new binaries against these libraries > (should not matter for make buildworld, but for building ports, which I do > at in the same script that invokes buildworld for critical kernel modules > that are to be built from ports). > > No binary or library should reference a library whose path contains > /compat/ after all upgrades have been performed, obviously ... > > Regards, STefan Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.uk https://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative From owner-freebsd-current@freebsd.org Mon Oct 22 21:11:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C6D6FD6B4B; Mon, 22 Oct 2018 21:11:48 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9477B74008; Mon, 22 Oct 2018 21:11:47 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9MLBi5o013665; Mon, 22 Oct 2018 14:11:44 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9MLBisu013664; Mon, 22 Oct 2018 14:11:44 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810222111.w9MLBisu013664@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: <7832.1540241924@critter.freebsd.dk> To: Poul-Henning Kamp Date: Mon, 22 Oct 2018 14:11:43 -0700 (PDT) CC: Warner Losh , Ed Maste , FreeBSD Current , ctm-users@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 22 Oct 2018 21:11:48 -0000 > -------- > In message > , Warner Losh writes: > > >> > I think Julian Stacy is still running CTM generation ? > >> > >> Ah, yes, that brought back enough brain cells, > >> confirmed that is who I saw with ctm usage. > > > >Do we need it in base? Or can we make it a port? > > Absolutely make it a port! > I concur, but please hold off on the svn rm until Stephen Montgomery and Julian have acked that they can quickly and easily transition to a port, then I would even be fine with a MFC gone in(13) to stable/12 and an immediate rm from head. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Oct 22 21:21:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 554BAFD72AE; Mon, 22 Oct 2018 21:21:49 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D4F0274893; Mon, 22 Oct 2018 21:21:48 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CCDC.dip0.t-ipconnect.de [46.82.204.220]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w9MLLg8Z056105 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2018 21:21:47 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w9MLLb6i027364; Mon, 22 Oct 2018 23:21:37 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w9MLLJh4050701; Mon, 22 Oct 2018 23:21:31 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201810222121.w9MLLJh4050701@fire.js.berklix.net> To: "Rodney W. Grimes" cc: Ed Maste , FreeBSD Current , ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 22 Oct 2018 12:57:39 -0700." <201810221957.w9MJvdXx012868@pdx.rh.CN85.dnsmgr.net> Date: Mon, 22 Oct 2018 23:21:19 +0200 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, 22 Oct 2018 21:21:49 -0000 "Rodney W. Grimes" wrote: > > The ctm(1) client remains in the FreeBSD base system, although > > FreeBSD-hosted ctm infrastructure was shut down some time ago. I > > suspect it is time to remove it from the base system (perhaps making a > > port). > > > > How much use does ctm have these days? > > I do not know that other than I do know that I have seen > one data point in the last 14 days of a user who was infact > using ctm though I can not associate a username/email address > with that memory. > > A search of the last 30 days of @freebsd.org public mail > may yield a hit. A fair guess, but it wouldn't indicate CTM usage well, as we only use the ctm@ list to discuss if something breaks, or to warn if a server will go out for maintenance. more misleading still: the ctm-announce@ list https://lists.freebsd.org/mailman/listinfo/ctm-announce hasnt been used in years, because Stephen doesnt have write access to it. I did write someone years back asking that Stephen be given write access, but it slipped between the cracks. If anyone fixes that to give Stephen Montgomery Smith write access to ctm-announce, it would be nice if you consider giving me write access too to ctm-announce@ as I occasionaly announce server outages eg https://lists.freebsd.org/pipermail/ctm-users/2018-September/000526.html Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.uk https://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative From owner-freebsd-current@freebsd.org Mon Oct 22 21:24:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03A9FFD73B3 for ; Mon, 22 Oct 2018 21:24:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670087.outbound.protection.outlook.com [40.107.67.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 978BA74B42; Mon, 22 Oct 2018 21:24:07 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM (52.132.50.155) by YTOSPR01MB018.CANPRD01.PROD.OUTLOOK.COM (52.132.51.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.30; Mon, 22 Oct 2018 21:24:06 +0000 Received: from YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM ([fe80::b09c:c689:9517:ea2b]) by YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM ([fe80::b09c:c689:9517:ea2b%4]) with mapi id 15.20.1250.028; Mon, 22 Oct 2018 21:24:06 +0000 From: Rick Macklem To: Brooks Davis CC: FreeBSD Current , Josh Paetzel Subject: Re: which way to update export_args structure? Thread-Topic: which way to update export_args structure? Thread-Index: AQHUWq0WJEV5v0B9NEODb8Fv+fAB/qUNrJCAgAZGIdGAAanmAIAR0AV4gAQgCwCAAFONFg== Date: Mon, 22 Oct 2018 21:24:06 +0000 Message-ID: References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> , <20181022160508.GB45769@spindle.one-eyed-alien.net> In-Reply-To: <20181022160508.GB45769@spindle.one-eyed-alien.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOSPR01MB018; 6:3qQdqH1quYIykgqanG+0CgGLzppQncCCvZOMqz3fKuakFm0oVAcCb9Yfdxy9qOvWX2BYdic6w/AyCAWQy0qSYxvLvPxOvb3CK7y7AfcdOLrhbKVU6TPZZ6ZUMu1PLcJRinKX/G/YbkvazIPWb8n0LQCbGeHvJxQOr54RMdkX35952zsbuNfjFhGPsFW+3ztsSVmG1bPcEPsaPzId/egTaIv0HO5eOKjjSVxl4Qd/V0I1r1xb05Vy/3h+wN4rYZ5orWHMTRZwb9nMCIyoRENPdmgBohw2k59zPzho3ErtIpbAB9dWtWAndMslwf5+KNZfB9GBNTSSVQ4XURATIApkB/hVO2Nbp6C1btP5pxRqPzThOBusIeAtYmgFJ6sRSgf8WwvUMjaBB3Iz3SUJXtQGYZ4ut3yRyorxTcD1C8zCdI1EdbjoFx6AcxIJ1XBHZk3/gzxghdSJMlneT36W+A313w==; 5:qmQHRCxwk3M6q63IMPTkTva0i0wvc0x4C1vbQB1CgqE0UnkAxJ80RDJ2Oxa+c8jXEkjLpZ5heyEBs5Z1IBC3qM5UE73FgRYf7h2VaOjP1gVIXWfJ8+AY1b+YTFgNv8rrDqbQtFaU5XcOVd0+NupLby3dq65dha3gMLEjDM7OGZY=; 7:Zt8NEH8fRSnMu9p3uD+oLtO9cdy0IFm+rQ0EUJGbmHmkxvTQ/TZHM3fc75IEJq/zfmVfsJqnqLXaxUapmX49hyGSP0/dInyHd8dIXBHZ39sfXrjGdex9/CRH900/FM08XxBK0Gr0ORwLpa8EYUAeEkSejbp1kaYNSVOdgYQge5u2/Tm7YFds4k0T2dkYzBhskISOQAQEudIrteY57kWQGgkcBeNaQyIbV068U6/TNRFOFc7GYcCIqMknqTLIFa8z x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 1549bd33-ebcb-441c-8964-08d63864b289 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOSPR01MB018; x-ms-traffictypediagnostic: YTOSPR01MB018: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231355)(944501410)(52105095)(3002001)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:YTOSPR01MB018; BCL:0; PCL:0; RULEID:; SRVR:YTOSPR01MB018; x-forefront-prvs: 08331F819E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(346002)(366004)(39860400002)(376002)(199004)(189003)(106356001)(76176011)(11346002)(7696005)(476003)(446003)(2906002)(5250100002)(14454004)(33656002)(74316002)(8936002)(186003)(81166006)(105586002)(14444005)(81156014)(97736004)(256004)(54906003)(46003)(55016002)(305945005)(6916009)(9686003)(786003)(6436002)(316002)(25786009)(71190400001)(8676002)(71200400001)(229853002)(102836004)(93886005)(478600001)(6506007)(6246003)(86362001)(99286004)(74482002)(5660300001)(53936002)(486006)(2900100001)(68736007)(4326008)(43043002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOSPR01MB018; H:YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: 9hcY7WVZaCRgcIZuq8aoWigXC0o6xDquUeFqpomUsBm+OYG4aOUOqPsZGFO4TnuDqDLrnq+ySae/6JQKFbXllFA7mrlxioD8cq+lREwYY7jGpC3JfNZZICzCmVC53FPL2TrVv0FcGto35hIMvtnOJ1bJDJut1TTciNC5xKIbLuzqt5+X6pUxa190sSAmNM397Tri4o3WmZ64L0Y226y0X2rm30QDrpbTR/EfpmxF1JnDcvPQ/iEwWKHhMKdVmmkKPSgjSp44fRx2pDAXleFNRjkSaLtVWEJ6BM062QyI+rNu/AtupM0YOPkD7pjBPtmmuPD/jmMMR9LC1AmNagSp3212J91NiStB7HcF5HBE/vQ= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 1549bd33-ebcb-441c-8964-08d63864b289 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2018 21:24:06.2278 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOSPR01MB018 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, 22 Oct 2018 21:24:08 -0000 Brooks Davis wrote: On Sat, Oct 20, 2018 at 01:17:37AM +0000, Rick Macklem wrote: [lots of stuff snipped] >> + if (error =3D=3D 0) { >> + gotexp =3D 0; >> + memset(&export, 0, sizeof(export)); >> + if (vfs_getopt(mp->mnt_optnew, "export.exflags", &bufp, >> + &len) =3D=3D 0) { >> + gotexp =3D 1; >> + export.ex_flags =3D strtouq(bufp, &endptr, 0); >> + if (endptr =3D=3D bufp) >> + export_error =3D EINVAL; >> + } > >This pattern involving strtouq seems wrong to me. We should probably >pass a pointer to the integer type (which should always be an explicitly >sized type). Thanks for noticing this. I was "on the fence" w.r.t. whether the arguments= should all be architecture neutral (ascii representation or ???). (I didn't bother doing the code for the net addresses in ascii notation.) It looks like you don't see that as needed, so I will just pass the binary = numbers in. (We could put them in Big Endian order, if someone thinks that is necessary= ?) >If it didn't contradict the first sentence of the description in >vfs_getopt.9, I'd say we should pass int and long values in the length >with a NULL buffer. Heh, heh. That would be a sneaky hack. I like it, but will resist and use t= he bufp. [more stuff snipped] >> + if (vfs_getopt(mp->mnt_optnew, "export", &bufp, &len) =3D= =3D 0) { >> + /* Assume that there is only 1 ABI for each length= . */ >> + switch (len) { >> + case (sizeof(struct oexport_args)): >> + case (sizeof(struct o2export_args)): >> + memset(&export, 0, sizeof(export)); > >I think this is now redundant. I'll be looking at the code to-day, but I think there is at least one field (ex_suppgroups) that needs to be set NULL so that the free() won't blow up. (I tend to bzero()/memset(0) so that any future additional fields don't hav= e to be explicitly set 0/NULL in the compatibility code, but it there aren't curren= tly any, I may take this out. This code doesn't get executed frequently, so efficien= cy at the "save a few instructions" level doesn't matter, imho.) >> + memset(&o2export, 0, sizeof(o2export)); > >This is certainly redundant given that you immediately copy over it. Yep. This was just cruft left over from a previous version of the patch. >This is the direction I'd been thinking. FWIW, the usecase is more that >once you've moved away from the struct it's easy to make incremental >changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward >size-independent interfaces helps both causes though. Cool. I'll finish the patch to-day and then let Josh work on mountd.c. Thanks for your comments, rick From owner-freebsd-current@freebsd.org Mon Oct 22 21:25:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA4BAFD7570; Mon, 22 Oct 2018 21:25:53 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 366ED74E0E; Mon, 22 Oct 2018 21:25:53 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9MLPlVs013783; Mon, 22 Oct 2018 14:25:47 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9MLPlH8013782; Mon, 22 Oct 2018 14:25:47 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810222125.w9MLPlH8013782@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: <201810222121.w9MLLJh4050701@fire.js.berklix.net> To: "Julian H. Stacey" Date: Mon, 22 Oct 2018 14:25:47 -0700 (PDT) CC: Ed Maste , FreeBSD Current , ctm-users@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 22 Oct 2018 21:25:53 -0000 > "Rodney W. Grimes" wrote: > > > The ctm(1) client remains in the FreeBSD base system, although > > > FreeBSD-hosted ctm infrastructure was shut down some time ago. I > > > suspect it is time to remove it from the base system (perhaps making a > > > port). > > > > > > How much use does ctm have these days? > > > > I do not know that other than I do know that I have seen > > one data point in the last 14 days of a user who was infact > > using ctm though I can not associate a username/email address > > with that memory. > > > > A search of the last 30 days of @freebsd.org public mail > > may yield a hit. > > A fair guess, but it wouldn't indicate CTM usage well, > as we only use the ctm@ list to discuss if something breaks, > or to warn if a server will go out for maintenance. The search was only to find YOU, as I knew my above 14 day reference to a user was a message on a mail list that contained the word "ctm". > more misleading still: the ctm-announce@ list > https://lists.freebsd.org/mailman/listinfo/ctm-announce > hasnt been used in years, because Stephen doesnt have > write access to it. I did write someone years back asking that > Stephen be given write access, but it slipped between the cracks. > If anyone fixes that to give Stephen Montgomery Smith write access to > ctm-announce, it would be nice if you consider giving me write access too to > ctm-announce@ as I occasionaly announce server outages eg > https://lists.freebsd.org/pipermail/ctm-users/2018-September/000526.html That should be possible, though I have no idea of where to even ask. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Oct 22 21:32:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E34A8FD7B31; Mon, 22 Oct 2018 21:32:39 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 505C675577; Mon, 22 Oct 2018 21:32:39 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CCDC.dip0.t-ipconnect.de [46.82.204.220]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w9MLWW9a056496 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2018 21:32:37 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w9MLWRpx027449; Mon, 22 Oct 2018 23:32:27 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w9MLVvxC050976; Mon, 22 Oct 2018 23:32:09 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201810222132.w9MLVvxC050976@fire.js.berklix.net> To: "Rodney W. Grimes" cc: Poul-Henning Kamp , Warner Losh , Ed Maste , FreeBSD Current , ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 22 Oct 2018 14:11:43 -0700." <201810222111.w9MLBisu013664@pdx.rh.CN85.dnsmgr.net> Date: Mon, 22 Oct 2018 23:31:57 +0200 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, 22 Oct 2018 21:32:40 -0000 Hi, Reference: > From: "Rodney W. Grimes" > Date: Mon, 22 Oct 2018 14:11:43 -0700 (PDT) "Rodney W. Grimes" wrote: > > -------- > > In message > > , Warner Losh writes: > > > > >> > I think Julian Stacy is still running CTM generation ? > > >> > > >> Ah, yes, that brought back enough brain cells, > > >> confirmed that is who I saw with ctm usage. > > > > > >Do we need it in base? Or can we make it a port? > > > > Absolutely make it a port! > > > > I concur, but please hold off on the svn rm until > Stephen Montgomery and Julian have acked that they > can quickly and easily transition to a port, then > I would even be fine with a MFC gone in(13) to > stable/12 and an immediate rm from head. Thanks Rod. I dont foresee a problem if its moved to ports. ( Unusual, as I often do predict problems moving to ports/ ) Let's wait for Stephen's thoughts, & other ctm users. Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.uk https://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative From owner-freebsd-current@freebsd.org Mon Oct 22 22:00:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF8C4FD8AA2 for ; Mon, 22 Oct 2018 22:00:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-qb1can01on062b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe5c::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 663FE766CD; Mon, 22 Oct 2018 22:00:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM (52.132.50.155) by YTOPR0101MB1017.CANPRD01.PROD.OUTLOOK.COM (52.132.47.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.29; Mon, 22 Oct 2018 21:59:52 +0000 Received: from YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM ([fe80::b09c:c689:9517:ea2b]) by YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM ([fe80::b09c:c689:9517:ea2b%4]) with mapi id 15.20.1250.028; Mon, 22 Oct 2018 21:59:52 +0000 From: Rick Macklem To: Brooks Davis CC: FreeBSD Current , Josh Paetzel Subject: Re: which way to update export_args structure? Thread-Topic: which way to update export_args structure? Thread-Index: AQHUWq0WJEV5v0B9NEODb8Fv+fAB/qUNrJCAgAZGIdGAAanmAIAR0AV4gAQgCwCAAFONFoAADjq0 Date: Mon, 22 Oct 2018 21:59:52 +0000 Message-ID: References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> , <20181022160508.GB45769@spindle.one-eyed-alien.net>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1017; 6:HO5cH8VEE4Jx6123tKoz1Njl1oqTr/UmVg772r3oLSUXogiAnRy+7sn8r9QsAvuDik3U3DpOScbhBZwkSiH6KlUN1u7fVGjcD4lyJe6cujobbUkHp8xP7u+lPpo4c4JkhIZzX5CJglTCspelRyBFnR2Gw5LhXW3hWV5I1TDBNEGZPqVCfWhG/EmZ6pqof6xSKHo9z4PK40xFOFBCD7JlepRsvsjefeyhK1qdCOmLhz2ii5b+yOtWfwTTgQr8lxy1sz90Slwm2jPcRxxhVKXobO4jg7wqb9L7h4TBgDT9PJMqsmr6bOSo1v6/gwbiKPjnsznQDeD5ym8clLhZ82wyfsLOc+/CC1xwoernUAZWXaLfB/DMm0KPobPR2e/BzuNfj57dprgJ0Lj/G21axXFafdCljTCx3u1NInwFRMtR7yrYOS9IDLXt9mxNqTeOTnSrdCMnatzRbuUuMi7g7qxFbA==; 5:kPVzeDNDkvIb+6juMEQ69kLedVXAmQv+iTdLZNhh0aoJNznPKPOfXftaD0KZM1Tpc00duJj++BM/demHtB0yNnk095UIAkA9KnV+rM701vONC0qbkAXf8iwalCiEzu+0wHa69/w4oZRbrBbDE7soMBrq1dcPBAE0OZHe8YuGERk=; 7:DK8EC8a1Q/vkYPi5TV+uqcJtBB70wOYALLKyrAmNQxFaglFXnd9nr3kdMyKC+VX2bfy7x+SjTVwOpRH8d6/jX3v5ZNAj6ri8aFNNp3Zl9P3d79I49KZg8HXH0SpopFKyh5emHnLFK23JGdxDz+iASyCoQiTfQBN4SJfXtsoH+5vsJStDuUNHaoQkXXrtiwqimNQ8XfC3nZcZHdutCY29k8A4ruVpK75PYPvL7hFEhCxo0T5VHIiLYfSCakxpZv2f x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 913c07ea-99e1-43bd-4cec-08d63869b1c2 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1017; x-ms-traffictypediagnostic: YTOPR0101MB1017: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(788757137089)(18154293887054); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(3231355)(944501410)(52105095)(10201501046)(93006095)(93001095)(148016)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:YTOPR0101MB1017; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1017; x-forefront-prvs: 08331F819E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(136003)(396003)(376002)(346002)(189003)(199004)(256004)(186003)(86362001)(9686003)(486006)(6246003)(76176011)(93886005)(229853002)(46003)(5250100002)(15650500001)(8676002)(14444005)(6506007)(6916009)(5660300001)(25786009)(97736004)(71190400001)(71200400001)(33656002)(93156006)(2906002)(74482002)(305945005)(68736007)(4326008)(478600001)(106356001)(105586002)(53936002)(99286004)(81156014)(55016002)(81166006)(786003)(54906003)(316002)(2900100001)(446003)(8936002)(11346002)(6436002)(7696005)(476003)(14454004)(74316002)(53546011)(2940100002)(102836004)(586874002)(43043002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1017; H:YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: +bhQwQDXHidIpAZKu9Gj4sVqpEntrAYZ+7Y1miJRvEd/5T09LNJXD0B28QGQoAgQkhrLGzwBCHhvaIuqXzpeTeRGkYPukesk06r9UgYicPVPF5Fnak0g6AkeUhW/k/P/2TtlmFE3O3oYsRps9H4UUif5G2KwGmYaWhN4KkLh8gSbAGFt8xJbnKkmJxsANVtXx8RwvuC5kKF+QrC9kWphEIk26f0Lq5STZuvxoW+6sP7WWosAAZowg3mo8XwzKVZhfsDXQ7CXyoDUB2RpgqpGfvoKalDw6JtGBX/vLYZgXx6gZq4OSLwVMiwX2SAph1Ut+WnNi9UOpcIbPVXC5NRKwfNuSjgIfKfmYIgcZyKpaEc= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 913c07ea-99e1-43bd-4cec-08d63869b1c2 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2018 21:59:52.3588 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1017 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, 22 Oct 2018 22:00:12 -0000 ________________________________________ From: owner-freebsd-current@freebsd.org = on behalf of Rick Macklem Sent: Monday, October 22, 2018 5:24 PM To: Brooks Davis Cc: FreeBSD Current; Josh Paetzel Subject: Re: which way to update export_args structure? Brooks Davis wrote: On Sat, Oct 20, 2018 at 01:17:37AM +0000, Rick Macklem wrote: [lots of stuff snipped] >> + if (vfs_getopt(mp->mnt_optnew, "export", &bufp, &len) =3D= =3D 0) { >> + /* Assume that there is only 1 ABI for each length= . */ >> + switch (len) { >> + case (sizeof(struct oexport_args)): >> + case (sizeof(struct o2export_args)): ... >> + memset(&o2export, 0, sizeof(o2export)); > >This is certainly redundant given that you immediately copy over it. Actually, I just looked and this code is correct. The trick is that "len" m= ight equal sizeof(struct oexport_args) which is < sizeof(struct o2export_args). As such, the memcpy() may only replace the first fields of "struct o2export= _args". I've added a comment to the patch to clarify this. rick From owner-freebsd-current@freebsd.org Mon Oct 22 22:00:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B22FCFD8AFD for ; Mon, 22 Oct 2018 22:00:57 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.in-berlin.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47D1C76788 for ; Mon, 22 Oct 2018 22:00:56 +0000 (UTC) (envelope-from h2+lists2018@fsfe.org) X-Envelope-From: h2+lists2018@fsfe.org X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id w9MM0nJP028810 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 23 Oct 2018 00:00:49 +0200 To: freebsd-current@freebsd.org References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> From: Hannes Hauswedell Openpgp: preference=signencrypt Autocrypt: addr=h2+lists2018@fsfe.org; prefer-encrypt=mutual; keydata= mDMEWjvrCBYJKwYBBAHaRw8BAQdA69H3pIQlZtmfHWcHtdO/QHaSCGncSJ5WCcrEOyLNGFq0 KUhhbm5lcyBIYXVzd2VkZWxsIDxoYW5uZXNAaGF1c3dlZGVsbC5uZXQ+iJkEExYIAEECGwMF CQPCZwAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUC WjvrdQIZAQAKCRBvny4w7LN5d/StAQClFHWUmhZehalNE7JFiRuNpwi0/v2jKA+IU7/IvjPj HQD+JC3jTzmchT+R+SMGM4aNvHSnkM3r7z2Y46syUJz6bwC0H0hhbm5lcyBIYXVzd2VkZWxs IDxoMkBmc2ZlLm9yZz6IlgQTFggAPhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+tWAhsD BQkDwmcABQsJCAcCBhUICQoLAgQWAgMBAh4BAheAAAoJEG+fLjDss3l3qg8A/io/KtgVK0C0 RQO4dTv4Cfof7i7Jz6BgJKNCDQnmvFl6AP0VeYDCvWJksngds2ZKz89jboAzAEzAU4/Gmx2G DJpiD7QxSGFubmVzIEhhdXN3ZWRlbGwgPHBvbGl0aWtAaGFubmVzLmhhdXN3ZWRlbGwubmV0 PoiWBBMWCAA+FiEE71b2aqaDPjLOBT9Vb58uMOyzeXcFAlo764MCGwMFCQPCZwAFCwkIBwIG FQgJCgsCBBYCAwECHgECF4AACgkQb58uMOyzeXc2RwD+PG/X0gaPyWXQfhsVC0h+KcRDRNXC U862y9AgstX0bQQBAP+oSMSu1TECWEZAlsijAL2IMpYJLObC0GRGcySHHlYOuDgEWjvrCBIK KwYBBAGXVQEFAQEHQDkbc3o1Tx1VoU3R/FTBZU466MK/hCV4wR5+LIYpy/VBAwEIB7g4BFo7 6wgSCisGAQQBl1UBBQEBB0A5G3N6NU8dVaFN0fxUwWVOOujCv4QleMEefiyGKcv1QQMBCAeI fgQYFggAJhYhBO9W9mqmgz4yzgU/VW+fLjDss3l3BQJaO+sIAhsMBQkDwmcAAAoJEG+fLjDs s3l3NmoBAPybRpTZWiShUDJRfmqSxH0EzcdRuXQC72D8DapTcrrpAQCubhUI634RzxbXYvxa WQctZgBLkfsw+qv+FWB2PfExDA== Subject: Re: Current status of Ryzen (non-)support Message-ID: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Date: Tue, 23 Oct 2018 00:00:39 +0200 MIME-Version: 1.0 In-Reply-To: <20181021173327.GJ5335@kib.kiev.ua> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV" 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, 22 Oct 2018 22:00:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV Content-Type: multipart/mixed; boundary="LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me"; protected-headers="v1" From: Hannes Hauswedell To: freebsd-current@freebsd.org Message-ID: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Subject: Re: Current status of Ryzen (non-)support References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> In-Reply-To: <20181021173327.GJ5335@kib.kiev.ua> --LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 21.10.18 19:33, Konstantin Belousov wrote: > On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: >> Hi everyone, >> >> I wanted to ask what the current status of Ryzen support is and/or >> whether any new changes are planned. >> >> My situation: >> * second generation Ryzen: 2600X >> * running -CURRENT >> * I have done the things described here: >> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.h= tml > This was based on the public errata document for the first gen ryzen. > I am not aware of the erratas ('revision guides' in AMD terminology) > for the second gen ryzens. >=20 > For now you can only get fixes for microcode from your BIOS updates. >=20 Thanks for the replies everyone! I ran stress-ng --vm 12 --vm-bytes 12G --verify -v and could reproducibly produce memory issues on FreeBSD, but not on Linux= =2E After updating the BIOS and deactivating swap on FreeBSD they seem to be gone now, I am still investigating whether turning swap back on brings them back which would hint at a possible disk problem or whether the BIOS update changed this behaviour. Disk initially appeared more plausible, but further tests suggest against it (it's a fairly new SSD, multiple ZFS scrubs show now errors, there are no smart errors or other errors reported by the kernel in regard to the disk). Best regards, Hannes --=20 pgp-key: https://hannes.hauswedell.net/hannes_hauswedell_public_key.asc fingerprint: EF56 F66A A683 3E32 CE05 3F55 6F9F 2E30 ECB3 7977 --LDrIDj0YwWjWeXysQ05ONSkk1imU4W9Me-- --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQTvVvZqpoM+Ms4FP1Vvny4w7LN5dwUCW85IkAAKCRBvny4w7LN5 dzX/AP9X1o39KyRRuXhQBtEbQwhpQciafOyd2rCcy+ouZRZOUgD/dy1ctvyxi+wV uMvKRVnKyvqfHIwj76iE5qRnE/uXGQY= =hMi1 -----END PGP SIGNATURE----- --8x5LMPkBHahSYc4UliLd6P2QVCpF5GcuV-- From owner-freebsd-current@freebsd.org Mon Oct 22 22:01:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56A41FD8B6C for ; Mon, 22 Oct 2018 22:01:36 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 00EBF769BA; Mon, 22 Oct 2018 22:01:35 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 2FD363C475F; Mon, 22 Oct 2018 22:01:35 +0000 (UTC) Date: Mon, 22 Oct 2018 22:01:35 +0000 From: Brooks Davis To: Rick Macklem Cc: Brooks Davis , FreeBSD Current , Josh Paetzel Subject: Re: which way to update export_args structure? Message-ID: <20181022220135.GA96662@spindle.one-eyed-alien.net> References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> <20181022160508.GB45769@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) 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, 22 Oct 2018 22:01:36 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 22, 2018 at 09:59:52PM +0000, Rick Macklem wrote: >=20 > ________________________________________ > From: owner-freebsd-current@freebsd.org on behalf of Rick Macklem > Sent: Monday, October 22, 2018 5:24 PM > To: Brooks Davis > Cc: FreeBSD Current; Josh Paetzel > Subject: Re: which way to update export_args structure? >=20 > Brooks Davis wrote: > On Sat, Oct 20, 2018 at 01:17:37AM +0000, Rick Macklem wrote: > [lots of stuff snipped] > >> + if (vfs_getopt(mp->mnt_optnew, "export", &bufp, &len) = =3D=3D 0) { > >> + /* Assume that there is only 1 ABI for each leng= th. */ > >> + switch (len) { > >> + case (sizeof(struct oexport_args)): > >> + case (sizeof(struct o2export_args)): > ... > >> + memset(&o2export, 0, sizeof(o2export)); > > > >This is certainly redundant given that you immediately copy over it. > Actually, I just looked and this code is correct. The trick is that "len"= might > equal sizeof(struct oexport_args) which is < sizeof(struct o2export_args). > As such, the memcpy() may only replace the first fields of "struct o2expo= rt_args". > I've added a comment to the patch to clarify this. Ah, that makes sense. -- Brooks --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbzki+AAoJEKzQXbSebgfAokIH/3YpNlWA/ssiR4NB/I7rbhOL EGGSKuQSzxtqjwQL7vA65z2HK2dpJ9hFOogEj/zNBGpmp0FJuHWTX/dLY9Z5W/PD yIANbLUkwKhhyGuEBoRl5d/X031Kl+CdOPkLBSGrDeC4f92wy7CtisT1Ss+pY85B lBs2mOZ01tKucyHRHUOLT+T0STJHMff1ZTtdINFTi1Y4TUVFjrLHpX6pJs+SHkjK 6H46gUQUxrTn/Q0FGMb3OOxDTsNuwybaI84EEfxeC1Eimfdz14BsabPFqafQpmI2 nuo6RwNBPHNQGIoTAL3vOd89EfD5khtqpeiWqpm/M/XNA7p56K5yiRhdBIpt+mQ= =/6MX -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-current@freebsd.org Tue Oct 23 01:43:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02595FF0DC2 for ; Tue, 23 Oct 2018 01:43:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-12.consmr.mail.bf2.yahoo.com (sonic304-12.consmr.mail.bf2.yahoo.com [74.6.128.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8D0DE8094F for ; Tue, 23 Oct 2018 01:43:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: .FqKwM4VM1kvm6HuSbkUubvD1CfRWK8UaOtmkzZ_._EBC.ecC3.F41ytmoRRDNE iV7cpHptQ9QTx8VQYCFcSi7hKADlEvDqahE_xlzRuYd.WehjYJ387t6ohq2xaXR_XIFyJj3I.Fqz uxGAzXu2BCYgSAFAbpNaukseUcQXSmwXQAClr2itL1sDpZXCKqeCAoq_Av6u.Z3WBOKN.qEQkYI8 RObafkHbYq1xaoTpitTnqb0.FFm_vG2keRk5Tzbde0lRZ6d2qNKsiwn2mWoF5v3xIj2YKcunmWU5 0D3ShbK49fsg5lztYMtIypEEB2zPS2k04Ho1FSOnvFx3e_FQ78tCRN2l5L08KHbRqA_OrnKVOW.X dCRRRNvCd_fzO8lwUVGYFcoWknrg3ihWjkwlKq53GLlveuy3eAuOGTDVzN4Proe1xjUZs0TWPiwF bExFEsD_YtFDO.fVPbPEm0de5Ku1tx3fPU8AUSLb1JIdPjz5vsMOH3UdwkGlAuLPvjaM3FxA6yfb kv0fKr_feS3T.W3GKyOFc0tzTvkZRLNj33D.NAy9BP8bT4ex0o6LpUFT89DgRczQ_nRGmuVreV.Z tlV6B7q2VeU3L34vUmZk9xP0MdyQijq0iRP_ojiQz5Av2nMUgjpEvy5pTEc89FLrVMY7MS1HACPV _avD8k4wOP4gkoIq9jd3K81dCPb5S9X1wSKrUyWHiZBIqHFMxLO4dIzcpnmWz5906avnQNES5wxV HFfW6bBg_X0Ao7dJpBCoDhTioDlbznr8DkcXP9Pia4Oic0Q.HYzDDG8KHl5_8AP9YCTvUQRk6Hoq oOhBKIOzn4QP_yugtu78_DGYCTDW5gu7Vi_eEPDI6Tg1Wkzd7iNd.djUSc.HGNCFe5R.F.LqwdjQ hKbIf3xe_qM9ZFXcGGYAeUqOA._sPl0sOIRfE5GIJ.L1RwDAT1fQO24QnvaMUxWWDyoUbtiIzegD yrHSAAzA5sEj4RKRkfLT__D3kj4bmz41r9Vo7_XknoGbh5b9VjrdCivIXJukz7bpKTFmEaZA7Wvy bk6S1cvSr.17jAv7qAEBCshliLGKvoxpiwOvVkzrNfgozJY.itUi9Po3X5QRxfpeAYQd_TUIpepP GfKx_2j0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Tue, 23 Oct 2018 01:43:27 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp420.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 04876bb04a8c3eb2f8320caaf7413218; Tue, 23 Oct 2018 01:43:23 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> Date: Mon, 22 Oct 2018 18:43:21 -0700 Cc: Toomas Soome , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <302639EA-55AA-4A41-BC03-4D48E6A09000@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> To: Warner Losh , Konstantin Belousov X-Mailer: Apple Mail (2.3445.9.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: Tue, 23 Oct 2018 01:43:29 -0000 [I' unable to reproduce the under-Hyper-V early kernel crash for WITH_ZFS=3D (implicit) build that includes the for-loaders patch I was given to try.] On 2018-Oct-22, at 10:01 AM, Mark Millard wrote: > [I will note the the loader problem has been shown to > not be involved in the kernel problem that this > "Subject:" was originally for.] >=20 > On 2018-Oct-22, at 9:26 AM, Warner Losh wrote: >=20 >> On Mon, Oct 22, 2018 at 6:39 AM Mark Millard = wrote: >>> On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: >>>=20 >>>> On 22 Oct 2018, at 13:58, Mark Millard = wrote: >>>>>=20 >>>>> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >>>>>>=20 >>>>>>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>>>>>>=20 >>>>>>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh = wrote: >>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable = < >>>>>>>> freebsd-stable@freebsd.org> wrote: >>>>>>>>=20 >>>>>>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >>>>>>>>> after installing the build, Hyper-V based boots are >>>>>>>>> working.] >>>>>>>>>=20 >>>>>>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: >>>>>>>>>=20 >>>>>>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: >>>>>>>>>> . . . >>>>>>>=20 >>>>>>=20 >>>>>> It would help to get output from loader lsdev -v command. >>>>>=20 >>>>> That turned out to be very interesting: The non-ZFS loader >>>>> crashes during the listing, during disk8, which shows a >>>>> x0 instead of a x512. >>>>>=20 >>>>=20 >>>> Yes, thats the root cause there. The non-zfs loader does only = *read* the boot disk, thats why the issue was not revealed there.=20 >>>>=20 >>>> It would help to identify the sector size for that disk, at least = from OS, so we can compare with what we can get from INT13. >>>>=20 >>>> I have pretty good idea what to look there, but I am afraid we need = to run few tests with you to understand why that disk is reporting = sector size 0 there. >>>>=20 >>>>=20 >>>=20 >>> Looks like I guessed wrong about the device >>> for "drive8". >>>=20 >>> So I unplugged the only other external >>> storage device, so the original drives >>> 0-13 become 0-11 overall. >>>=20 >>> The machine has a multi-LUN media card reader with >>> no cards plugged in. It is built-in rather than >>> one that I plugged into a port. It has 4 LUN's. >>>=20 >>> So 8+4=3D12 and drives 0-7 show up with media before >>> it tries any of the 4 LUN's with no card in place. >>>=20 >>> I conclude that "drive8" is an empty LUN in a media >>> card reader. >>>=20 >>> I conclude that there is no sector size available for >>> any of the empty LUNs in the media reader. >>>=20 >> I think you are probably right and we're hitting some divide by 0 = error when we should just ignore the disk. >=20 > In the Hyper-V context, the loader and kernel do not > see the 4-LUN media reader at all: only drives with > normal freebsd-* style partitions and free space. > This explains why I did not see a loader problem > in that context. >=20 > So I conclude that the kernel crash under Hyper-V > associated with -r338807 is a separate issue even > though WITHOUT_ZFS=3D seems to have avoided the > crash. >=20 > My plan is to continue with the -r338807 investigation > after the loader problem is fixed in my builds. Then > I've go back to trying builds using WITH_ZFS=3D (implicit), > both native boots and Hyper-V based ones. So much for my ability to make that inference correctly: The WITH_ZFS=3D (implicit) build worked fine for booting natively and via Hyper-V when the patch to fix the loaders was included in what to build. I'm now unable to reproduce this kernel-time crash. The patch was from: https://reviews.freebsd.org/D11174 The empty LUN's in the media reader now get messages that look something like: disk8: Read 1 sector(s) from 0 to 0xffffe000 (0x8000): 0x31 early in the loader activity. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue Oct 23 03:27:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E08BFFDC48 for ; Tue, 23 Oct 2018 03:27:12 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8C3B85A68 for ; Tue, 23 Oct 2018 03:27:11 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from [10.153.163.240] (mobile-166-171-184-58.mycingular.net [166.171.184.58]) (authenticated bits=0) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTPSA id w9N3NZYs028106 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 22 Oct 2018 23:23:49 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Mon, 22 Oct 2018 23:23:51 -0400 (EDT) Mime-Version: 1.0 (1.0) Subject: Re: Current status of Ryzen (non-)support From: Daniel Eischen X-Mailer: iPhone Mail (16A405) In-Reply-To: <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> Date: Mon, 22 Oct 2018 23:23:32 -0400 Cc: freebsd-current@freebsd.org Message-Id: <7E247566-47FA-4BD7-ACBE-984C0DB9AC2D@freebsd.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> <20181021173327.GJ5335@kib.kiev.ua> <6845b53c-63db-7a76-cddb-2ca1b8408e1b@hauswedell.net> To: Hannes Hauswedell 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, 23 Oct 2018 03:27:12 -0000 Sent from my iPhone > On Oct 22, 2018, at 6:00 PM, Hannes Hauswedell wro= te: >=20 >> On 21.10.18 19:33, Konstantin Belousov wrote: >>> On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: >>> Hi everyone, >>>=20 >>> I wanted to ask what the current status of Ryzen support is and/or >>> whether any new changes are planned. >>>=20 >>> My situation: >>> * second generation Ryzen: 2600X >>> * running -CURRENT >>> * I have done the things described here: >>> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.htm= l >> This was based on the public errata document for the first gen ryzen. >> I am not aware of the erratas ('revision guides' in AMD terminology) >> for the second gen ryzens. Coming in a little late on this thread, just upgraded my 10 year old system t= o an AMD Ryzen 5 2400G. I noticed that the link below, and alluded to in th= e above pipermail link, does mention the 2nd gen Ryzen processors. Apologie= s if I misunderstood the above response. https://developer.amd.com/wp-content/resources/55449_1.12.pdf Also, my cpuid (Id=3D0x810f10 Family=3D0x17 Model=3D0x11) isn't mentioned i= n the above errata, so I guess it's not quite up to date for more recent 2nd= gen Ryzen, even though the 2400G was released months before the dated errat= a. I've not applied any of the sysctls mentioned in the above email, but have u= pdated my BIOS to the latest (ASUS X470-PRO). I've not experienced any prob= lems in several j8 buildworlds or poudriere runs (building roughly 1000 port= s). -- DE= From owner-freebsd-current@freebsd.org Tue Oct 23 06:28:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AA321039241 for ; Tue, 23 Oct 2018 06:28:43 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2C1A18C0E4; Tue, 23 Oct 2018 06:28:43 +0000 (UTC) (envelope-from des@des.no) Received: from next.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 9E90181EA; Tue, 23 Oct 2018 06:28:42 +0000 (UTC) Received: by next.des.no (Postfix, from userid 1001) id 8115E101AD; Tue, 23 Oct 2018 08:28:42 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Julian H. Stacey" Cc: Stefan Esser , FreeBSD Current , Stefan Esser Subject: Re: careless commits disrupt In-Reply-To: <201810222109.w9ML96bF050497@fire.js.berklix.net> (Julian H. Stacey's message of "Mon, 22 Oct 2018 23:09:06 +0200") References: <201810222109.w9ML96bF050497@fire.js.berklix.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Date: Tue, 23 Oct 2018 08:28:42 +0200 Message-ID: <86efch41np.fsf@next.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 23 Oct 2018 06:28:43 -0000 "Julian H. Stacey" writes: > Stefan Esser writes: > > I might have mentioned, that I always preserve old shared libraries > > in /usr/lib/compat before running "make delete-old-libs". > Good idea, are you doing that manually, or do you have a patch to > share ? # pkg install -y misc/compat9x misc/compat10x misc/compat11x DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@freebsd.org Tue Oct 23 09:20:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F2FC1072376 for ; Tue, 23 Oct 2018 09:20:58 +0000 (UTC) (envelope-from pho@holm.cc) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1EB137213D for ; Tue, 23 Oct 2018 09:20:58 +0000 (UTC) (envelope-from pho@holm.cc) Received: by mailman.ysv.freebsd.org (Postfix) id D82841072375; Tue, 23 Oct 2018 09:20:57 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6F5B1072374 for ; Tue, 23 Oct 2018 09:20:57 +0000 (UTC) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) (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 7C85B7213B for ; Tue, 23 Oct 2018 09:20:57 +0000 (UTC) (envelope-from pho@holm.cc) Received: from x2.osted.lan (87-58-223-204-dynamic.dk.customer.tdc.net [87.58.223.204]) by relay01.pair.com (Postfix) with ESMTP id 34945D010BA for ; Tue, 23 Oct 2018 05:20:56 -0400 (EDT) Received: from x2.osted.lan (localhost [127.0.0.1]) by x2.osted.lan (8.15.2/8.15.2) with ESMTPS id w9N9KsIv023017 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 23 Oct 2018 11:20:54 +0200 (CEST) (envelope-from pho@x2.osted.lan) Received: (from pho@localhost) by x2.osted.lan (8.15.2/8.15.2/Submit) id w9N9KsW3023016 for current@freebsd.org; Tue, 23 Oct 2018 11:20:54 +0200 (CEST) (envelope-from pho) Date: Tue, 23 Oct 2018 11:20:54 +0200 From: Peter Holm To: current@freebsd.org Subject: panic: mtx_lock() by idle thread ... mutex igb0 @ ../../../net/iflib.c:2084 Message-ID: <20181023092053.GA22982@x2.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) 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, 23 Oct 2018 09:20:58 -0000 Feeding entropy: . lo0: link state changed to UP panic: mtx_lock() by idle thread 0xfffff800036ac000 on sleep mutex igb0 @ ../../../net/iflib.c:2084 cpuid = 4 time = 1540286062 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe007876e610 vpanic() at vpanic+0x1a3/frame 0xfffffe007876e670 panic() at panic+0x43/frame 0xfffffe007876e6d0 __mtx_lock_flags() at __mtx_lock_flags+0x15a/frame 0xfffffe007876e720 iflib_admin_intr_deferred() at iflib_admin_intr_deferred+0x2a/frame 0xfffffe007876e750 em_msix_link() at em_msix_link+0x84/frame 0xfffffe007876e780 iflib_fast_intr_ctx() at iflib_fast_intr_ctx+0x21/frame 0xfffffe007876e7a0 intr_event_handle() at intr_event_handle+0xbb/frame 0xfffffe007876e7f0 intr_execute_handlers() at intr_execute_handlers+0x58/frame 0xfffffe007876e820 lapic_handle_intr() at lapic_handle_intr+0x5f/frame 0xfffffe007876e840 Xapic_isr1() at Xapic_isr1+0xd9/frame 0xfffffe007876e840 --- interrupt, rip = 0xffffffff811e6be6, rsp = 0xfffffe007876e910, rbp = 0xfffffe007876e910 --- acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfffffe007876e910 acpi_cpu_idle() at acpi_cpu_idle+0x23d/frame 0xfffffe007876e960 cpu_idle_acpi() at cpu_idle_acpi+0x3f/frame 0xfffffe007876e980 cpu_idle() at cpu_idle+0xa7/frame 0xfffffe007876e9a0 sched_idletd() at sched_idletd+0x517/frame 0xfffffe007876ea70 fork_exit() at fork_exit+0x84/frame 0xfffffe007876eab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe007876eab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 11 tid 100007 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> x/s version version: FreeBSD 13.0-CURRENT r339638 PHO-GENERIC\012 db> -- Peter From owner-freebsd-current@freebsd.org Tue Oct 23 06:04:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8C16103852E for ; Tue, 23 Oct 2018 06:04:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 853558B544 for ; Tue, 23 Oct 2018 06:04:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4B0E7103852D; Tue, 23 Oct 2018 06:04:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A0C3103852B for ; Tue, 23 Oct 2018 06:04:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE2E78B541 for ; Tue, 23 Oct 2018 06:04:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2A07911D08 for ; Tue, 23 Oct 2018 06:04:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9N648qu008599 for ; Tue, 23 Oct 2018 06:04:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9N648ct008598 for current@FreeBSD.org; Tue, 23 Oct 2018 06:04:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Date: Tue, 23 Oct 2018 06:04:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: nh.techn@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10- mfc-stable11- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 23 Oct 2018 10:25:00 +0000 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, 23 Oct 2018 06:04:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 Nicolas Hainaux changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nh.techn@gmail.com --- Comment #32 from Nicolas Hainaux --- I plainly agree with James T. Koerting that, for the reasons he clearly sta= ted, this should not be kept as an open bug. As an ezjail user, I'd rather suggest to keep the per-jail configuration via jail_* variables until there is a reliable solution to drop it. Even until = 13.0 or 14.0 if this is necessary. I do not want to replace ezjail by unreliable or "fat" tools and hope the authors of jail(8) will find a solution and/or take the config file managem= ent functionality proposed by erdgeist into consideration. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Tue Oct 23 10:53:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1A201074ACA; Tue, 23 Oct 2018 10:53:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3EAE875690; Tue, 23 Oct 2018 10:53:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id BB2ACA60; Tue, 23 Oct 2018 13:53:16 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) To: Toomas Soome , Mark Millard Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> From: Lev Serebryakov Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> Date: Tue, 23 Oct 2018 13:53:10 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="O7ARNd9jBNRfZsJ3VM4Jo7ZbtsO6XdNev" 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, 23 Oct 2018 10:53:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --O7ARNd9jBNRfZsJ3VM4Jo7ZbtsO6XdNev Content-Type: multipart/mixed; boundary="xcEBM7iiIpxxFQd7aqLkTSuFwPGzPGsDj"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: Toomas Soome , Mark Millard Cc: Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh Message-ID: <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> Subject: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> In-Reply-To: <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> --xcEBM7iiIpxxFQd7aqLkTSuFwPGzPGsDj Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.10.2018 12:27, Toomas Soome wrote: > It would help to get output from loader lsdev -v command. current loader crashes on "lsdev" for me: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232483 (it is not threadripper-related, my hardware is Intel Atom). --=20 // Lev Serebryakov --xcEBM7iiIpxxFQd7aqLkTSuFwPGzPGsDj-- --O7ARNd9jBNRfZsJ3VM4Jo7ZbtsO6XdNev Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvO/ZdfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R4922hAAp//mV2M5mGHV4ZRBbTZKrHiLUUXKk1sR1DAMjZ/D5aRaH+k2S5v08/LO NZt2G1U37edc9UNGUWTRgHT1Mv5MwRqrCcdkt8/NOXLetQap5e9j685LD5cnS8q5 VKpyj7WT7uKo+lPbRRkTDVQPGFDwJcj5DE2W1jcnQpkz2W9p12i/u5RMfcawZ2Qy exHIb82AMlegnHdE807QKvxQRueJ3CS78a29M8HYQaXujaTyTrkm7pqppDwmwDhH darRK7WLDQrSePUsPgydkXHSiUl1nKAI8wdq2fOCSD9v9oQb8SuF6ykdU5dICbd1 A9/nDfXwOW8XzdOXEFPApUQCq1Hpk1eTZX6QmlKFUzO6fbZpNTx1/019iNZNPWbz hHE0tu+D1WsolDtqngvR/Qyp9Xzh9wtc8PEmYCM9VefaP1i5S9vXpasVMNUW2BRq 8eo4iVdqd+ST66mUTQzOFwe8Yy6/gPWw7LPh8mkHszkxLPRuonl9bONhcnTvV0a4 8RluUELPzBC7N75J3GYnl20JzEJgUIhJpo8d7eCDCw/R2+d99CRrkktazBy7u53U SgxQ2elcOKkLAVU5xArqnz+H7X24HvG8CDY/55kK6+hy1cNd8e+Fqaeks4slNQSe AwOatzRfGJaMJ/gmgvFJ5/Ma0Gpp0B7nafQASU29vCkFzK+SbR4= =iVab -----END PGP SIGNATURE----- --O7ARNd9jBNRfZsJ3VM4Jo7ZbtsO6XdNev-- From owner-freebsd-current@freebsd.org Tue Oct 23 11:37:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97F591076189 for ; Tue, 23 Oct 2018 11:37:37 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 31224770AC for ; Tue, 23 Oct 2018 11:37:37 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id E96C21076188; Tue, 23 Oct 2018 11:37:36 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D798A1076187 for ; Tue, 23 Oct 2018 11:37:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 408A2770AB for ; Tue, 23 Oct 2018 11:37:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w9NBbY6h053564 for ; Tue, 23 Oct 2018 11:37:34 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w9NBbY5r053563 for current@freebsd.org; Tue, 23 Oct 2018 04:37:34 -0700 (PDT) (envelope-from david) Date: Tue, 23 Oct 2018 04:37:34 -0700 From: David Wolfskill To: current@freebsd.org Subject: Panic during network initialization after r339583 -> r339639 Message-ID: <20181023113734.GQ5358@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="k++jrJxptm7IAPkr" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-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, 23 Oct 2018 11:37:37 -0000 --k++jrJxptm7IAPkr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Gory details in . I snapped some screenshots, but can't associate using laptop's iwn(4) (in stable/11, stable/12, or head/13) at the place I'm currently staying. (I may be able to at least get the screenshots uploaded to the Web server later on today.) But since I was able to get a dump, they are probably not very interesting. It looks (to my semi-trained eye) as if iflib is implicated -- partly because the backtrace mentions it (ref. frame #14 from the backtrace in core.txt.8), and partly because I only saw the panic on my laptop, the wired NIC for which is em(4), while my build machine (which uses rl(4)) had no issues. I'm happy to poke and/or test, but will need some direction to do so. Peace, david --=20 David H. Wolfskill david@catwhisker.org Women (and decent men): vote against supporters of Trump's misogyny! See http://www.catwhisker.org/~david/publickey.gpg for my public key. --k++jrJxptm7IAPkr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlvPB/1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hdsjQf/U/fRfsCqSKuuXcveAosHeJkYRCOXSffq0zQaz8iY6dJeWaKX+9QxauUB 9ryRe9IbuYDZITuieoDBKCLHEGWJNJGGMUFFXwzAcbgwzKrPSKxQ9MfN1LHAPLPp OicWWnPZSmrx/szegbySQ31Qb0HAHXKTVa9CFBiDNnKEuaYPPuJEiolm+kadkfUl OfQ7ByWFdQqESyA9/ibiUSdAY6C20KC3i5Jm3j9xRWa3BkqXy0yBxk/dc+Pw/Z5e I6NUQT4BLcrXl6PgLauzk0q/yznxlfhViAYiIqOx0cYK7UGEEvdUXFSQcpCTwLdJ pJsdb0iNX1sRolaFxzZRySzOFT5sXw== =QQU2 -----END PGP SIGNATURE----- --k++jrJxptm7IAPkr-- From owner-freebsd-current@freebsd.org Tue Oct 23 11:54:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25E381076C4A; Tue, 23 Oct 2018 11:54:36 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp001.me.com (pv33p00im-asmtp001.me.com [17.142.194.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4BE277CA8; Tue, 23 Oct 2018 11:54:35 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp001.me.com by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH100N00VH87W00@pv33p00im-asmtp001.me.com>; Tue, 23 Oct 2018 11:54:21 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH1006SKVQCF130@pv33p00im-asmtp001.me.com>; Tue, 23 Oct 2018 11:54:18 +0000 (GMT) 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=865 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810230103 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_03:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) From: Toomas Soome In-reply-to: <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> Date: Tue, 23 Oct 2018 14:54:11 +0300 Cc: Mark Millard , Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List , Warner Losh Content-transfer-encoding: quoted-printable Message-id: <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> To: lev@FreeBSD.org X-Mailer: Apple Mail (2.3445.100.39) 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, 23 Oct 2018 11:54:36 -0000 > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: >=20 > On 22.10.2018 12:27, Toomas Soome wrote: >=20 >> It would help to get output from loader lsdev -v command. > current loader crashes on "lsdev" for me: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232483 (it is not > threadripper-related, my hardware is Intel Atom). >=20 > --=20 > // Lev Serebryakov >=20 That error means something is corrupting the memory, it is hard to guess = what exactly and debugging it is nasty - it means we would need to track = down what was allocated before this memory block (guard1 is marker = inserted in front of the allocated memory block).=20 Fortunately the code to print the partition table is in = stand/common/disk.c and the partition code is just next to it and so it = should be relatively easy to find the guilty one=E2=80=A6 I will try to = see if I can replicate the issue. rgds, toomas= From owner-freebsd-current@freebsd.org Tue Oct 23 12:03:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFE3B1077CD4 for ; Tue, 23 Oct 2018 12:03:38 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 383EF787D3 for ; Tue, 23 Oct 2018 12:03:38 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd31.aul.t-online.de (fwd31.aul.t-online.de [172.20.26.136]) by mailout07.t-online.de (Postfix) with SMTP id 432BF42DB515; Tue, 23 Oct 2018 14:03:29 +0200 (CEST) Received: from Stefans-MBP-LAN.fritz.box (Gu1KeaZcwhLgQq1i5PLTJhZjjn4t2fV0kuwa85nWTKmS4ENHSMWrBQ4lYbLqG4Mg2X@[80.128.111.25]) by fwd31.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1gEvP9-1gCz7w0; Tue, 23 Oct 2018 14:03:23 +0200 Subject: Re: careless commits disrupt To: "Julian H. Stacey" References: <201810222109.w9ML96bF050497@fire.js.berklix.net> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Cc: FreeBSD Current Message-ID: <3736ed03-e849-fb14-daac-2653d86f6202@freebsd.org> Date: Tue, 23 Oct 2018 14:03:21 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <201810222109.w9ML96bF050497@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: Gu1KeaZcwhLgQq1i5PLTJhZjjn4t2fV0kuwa85nWTKmS4ENHSMWrBQ4lYbLqG4Mg2X X-TOI-MSGID: a8e47845-405d-4e03-9b4c-00469aec5336 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, 23 Oct 2018 12:03:39 -0000 Am 22.10.18 um 23:09 schrieb Julian H. Stacey: > Hi, Reference: >> From: Stefan Esser >> Date: Fri, 12 Oct 2018 11:44:59 +0200 > > Stefan Esser wrote: >> I might have mentioned, that I always preserve old shared libraries in >> /usr/lib/compat before running "make delete-old-libs". > > Good idea, are you doing that manually, or do you have a patch to share ? I do it manually, but I have a script that checks for programs in the base system and packages that use any library moved to the lib/compat directory - see below. The base system checks should never give any output (unless there are old and obsolete binaries). I use the package list to identify packages that must be rebuilt to make the compat libraries obsolete. Since there may be shared library version conflicts, if some Regards, STefan ------------------------------------------------------------ #!/bin/sh find_compat_depend () { local dir="$1" local pattern="$2" find "$dir" -type f ${pattern:+-name "$pattern"} \ -exec sh -c "ldd {} 2>/dev/null | grep -lq /compat/ && echo {}" \; } echo "Base system programs referencing compat libraries:" find_compat_depend /bin "" find_compat_depend /sbin "" find_compat_depend /libexec "" #find_compat_depend /lib "lib*.so.*" find_compat_depend /usr/bin "" find_compat_depend /usr/sbin "" find_compat_depend /usr/libexec "" #find_compat_depend /usr/lib "lib*.so.*" echo echo "Installed packages referencing compat libraries:" { find_compat_depend /usr/local/bin "" find_compat_depend /usr/local/sbin "" find_compat_depend /usr/local/libexec "" find_compat_depend /usr/local/lib "lib*.so.*" } | xargs pkg which -q | sort -u From owner-freebsd-current@freebsd.org Tue Oct 23 12:13:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8405107875A for ; Tue, 23 Oct 2018 12:13:28 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5769479213 for ; Tue, 23 Oct 2018 12:13:28 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm1-x32b.google.com with SMTP id y144-v6so1527780wmd.4 for ; Tue, 23 Oct 2018 05:13:28 -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=c6ht0FQxeZa3/i+yUuKq+R9sCcWPeDER4hI6vfI/HyE=; b=h+9psTy6QnjcqTZvihDcvNn/5o3HFnMiEMluh6lnTsNyfISmwaXGAOrl+KXffJidJB 8xxDjQqiCOiG1+Sov4ckDdgBQfmVoB4oY7N4gmYK0BGDx+i8sm26zuG6On/t8dm92m0M OTlNqazGgvToySRjZJYAWRUcQOgzTWn/ZNmvaEa8qZudzjQD7Z3B79oPbhQFVYpCNoLo oULqAG5teF6Ct1krV+JOtNO8TWoX98XNpaV/n9UYGHwYn1Owz6TA5ecVa0xEwBXqUZJv VB+o3sT5hDNLRw54rbGSsXulmspP3x/Pm640yStmkuQNmGTcaG9wp2diYcFQ814bb2t0 tEIw== 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=c6ht0FQxeZa3/i+yUuKq+R9sCcWPeDER4hI6vfI/HyE=; b=E2ekUBxvUWY2rjeUvlfIfCC1HneA5MfFfyx/r0owZT5BTnaq1oyCkJQcjREAfJhzHc AQL4Ml9P/gjxzofjI7OEm9loF6hwN3iuZZuBytoYC/tjORDRmQLKhp4GqUSGldeVqHvO 7ZfX5ImCMe7pr9VC7lUR7mkAio6biopOfLMsymm1vpXxxSp/FO8/aA72N8YSrkZceggj s3i68WybRGOFc5pur56EPaxPAvmeUgqoGXh6QQd6biN271vfy16oy3UIWHClM0h8m9vW tNsc1kYoB8ro9RMLjHqwh4LIGxcEKlYxCDIDNr7h4t6cCyoYKSjfeDX6E8s/KFwHYRyq Y5LA== X-Gm-Message-State: AGRZ1gL4u5+5vtjnOYGYouwe49TLM3Z2cl2obACsurq63FCDbdkYIiUZ 75YJ4xrdwa7fBtA21U9EvWbpfyl0kwPxHbk3nvKv0Fq2 X-Google-Smtp-Source: ACcGV63TAZdVrhL3itxa+ECDIH2hqtAkMwcMvgKWhVm7j9b9k/o8+ZMevMUUtyWB6RowVd4y4JnOos5BJVxHX9X/ALw= X-Received: by 2002:a1c:540d:: with SMTP id i13-v6mr20674357wmb.149.1540296807058; Tue, 23 Oct 2018 05:13:27 -0700 (PDT) MIME-Version: 1.0 From: Rajesh Kumar Date: Tue, 23 Oct 2018 17:43:15 +0530 Message-ID: Subject: Facing kernel panic during early boot from 12.0 ALPHA9 To: freebsd-current@freebsd.org 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, 23 Oct 2018 12:13:29 -0000 Hi, I have a amd64 based board, where I could able to install upto FreeBSD 12.0 ALPHA8 without issues. But starting ALPHA9, I start to see the below panic during early boot. Looks like some sleep at unwanted place. I am using the memstick image from dowload page. Please let me know if you need any details. *Panic logs :* GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb ---<>--- Copyright (c) 1992-2018 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 The FreeBSD Foundation. FreeBSD 12.0-ALPHA9 r339271 GENERIC amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. panic: vm_wait in early boot cpuid = 0 time = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff827098d0 vpanic() at vpanic+0x1a3/frame 0xffffffff82709930 panic() at panic+0x43/frame 0xffffffff82709990 vm_wait_domain() at vm_wait_domain+0xf9/frame 0xffffffff827099c0 vm_domain_alloc_fail() at vm_domain_alloc_fail+0x94/frame 0xffffffff827099f0 vm_page_alloc_domain_after() at vm_page_alloc_domain_after+0x274/frame 0xffffffff82709a60 uma_small_alloc() at uma_small_alloc+0x6e/frame 0xffffffff82709a90 keg_alloc_slab() at keg_alloc_slab+0xf0/frame 0xffffffff82709af0 uma_prealloc() at uma_prealloc+0x92/frame 0xffffffff82709b30 vm_map_startup() at vm_map_startup+0x5f/frame 0xffffffff82709b40 vm_mem_init() at vm_mem_init+0x32/frame 0xffffffff82709b50 mi_startup() at mi_startup+0x118/frame 0xffffffff82709b70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> From owner-freebsd-current@freebsd.org Tue Oct 23 13:34:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 131B5FD8211 for ; Tue, 23 Oct 2018 13:34:11 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 939437C7DD for ; Tue, 23 Oct 2018 13:34:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5316CFD8210; Tue, 23 Oct 2018 13:34:10 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17FF4FD820E for ; Tue, 23 Oct 2018 13:34:10 +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 5EEF37C7DC for ; Tue, 23 Oct 2018 13:34:09 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id EwmDgFhu6wyxUEwmEg5uoq; Tue, 23 Oct 2018 07:31:19 -0600 X-Authority-Analysis: v=2.3 cv=NPJhBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=L5pwM6nWxzsA:10 a=smKx5t2vBNcA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=JAf30KXuAAAA:8 a=rzMZ-3yBw-4F_tpLsLoA:9 a=uSnc8RNxw--Ehlio:21 a=A-CdkixMKYLPDdc6:21 a=CjuIK1q_8ugA:10 a=NR8yHBxYWkd_9nzaK00A:9 a=IdUJQhtMm-1W7y6i:21 a=VsYnbOFOZ_BIUkMe:21 a=6noWI1lLVKuiNAC_:21 a=_W_S_7VecoQA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=GEL62FyrTCmHtEug2d3R:22 Received: from [25.80.87.246] (unknown [72.143.225.166]) by spqr.komquats.com (Postfix) with ESMTPSA id 5EFA6212; Tue, 23 Oct 2018 06:31:16 -0700 (PDT) MIME-Version: 1.0 From: Cy Schubert Subject: RE: Panic during network initialization after r339583 -> r339639 Date: Tue, 23 Oct 2018 06:31:17 -0700 To: "current@freebsd.org" Message-Id: <20181023133116.5EFA6212@spqr.komquats.com> X-CMAE-Envelope: MS4wfA2wnxFaz8vk2QyLbvzbx/wsde/wUyMnOCDYmpOnlRMgj8UI/dDVkRgDcwhxWUznHYehhMCA/lkia8sE7J3zSzQdfg1eJ/QnaGmpevGkwGSmQ1fikIkZ dSg3GWThPHJZztq8EJja0ILuiM3mjqcxW6n53O/llJAd0iS+Dr63Bs/aQzf8OAYGZ6M5cbY0AcGhmw== 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, 23 Oct 2018 13:34:11 -0000 This is caused by https://svnweb.freebsd.org/changeset/base/339634. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: David Wolfskill Sent: 23/10/2018 04:39 To: current@freebsd.org Subject: Panic during network initialization after r339583 -> r339639 Gory details in . I snapped some screenshots, but can't associate using laptop's iwn(4) (in stable/11, stable/12, or head/13) at the place I'm currently staying. (I may be able to at least get the screenshots uploaded to the Web server later on today.) But since I was able to get a dump, they are probably not very interesting. It looks (to my semi-trained eye) as if iflib is implicated -- partly because the backtrace mentions it (ref. frame #14 from the backtrace in core.txt.8), and partly because I only saw the panic on my laptop, the wired NIC for which is em(4), while my build machine (which uses rl(4)) had no issues. I'm happy to poke and/or test, but will need some direction to do so. Peace, david --=20 David H. Wolfskill david@catwhisker.org Women (and decent men): vote against supporters of Trump's misogyny! See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Tue Oct 23 13:35:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8D4BFD826E for ; Tue, 23 Oct 2018 13:35:10 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C64E7C8D1 for ; Tue, 23 Oct 2018 13:35:10 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it1-x130.google.com with SMTP id p64-v6so2092915itp.0 for ; Tue, 23 Oct 2018 06:35:10 -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=WrTwGzUZ/TiGJQtKG69p89AMunrPpqLPYvZcWL/qo0Y=; b=D0tA4kA+s1NBFDne6ld5ehSPYIUVBLXsMg7mvBroh3uooc6AbD/qPvfAXVk7+5UD+2 g3bBRFBehEvVNg6RsNf/yMC5VW29v28JCL1Jia9SsFv0MGCVYQmDpSeV8oW2fut6Fozp 9CI7ASG8P2gZ84EuCO6iKZVt0LALgBoQfrbh8zNTsyUdLT2YpXEu2ijnd35Axoyq4Cru tOgWGRWL2NW9Yq+KGiKZtU7UWpTjbcq32hTQx3a/bW0NI5a8vgEs92RzeYG09iTtuKlk zh0GN8AFJCmm164CwpiGq7Dg5r1bcfuOELwJGhLg5wu3A/lYiTYrbXRTuvaaETFHqGrj A2wA== 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=WrTwGzUZ/TiGJQtKG69p89AMunrPpqLPYvZcWL/qo0Y=; b=lxoK2+OXiPU/dnmZZn3S11x3UBZwGMkV6meIf2FXk1JxXijJdpTxe6JrXeSyCzU+d9 k7Rpc1t+x6tdav5oFoQ2jueHasKpNlBxGcf2id4rQLCs9pCD8oIF23LyxWMtltJW7GQv uW8t+l0jZdlkvjKS/Eahy0WijblafqNKcvY/EdReoOqjyQf/NSfKgAbrBFi+Ip/SfIjt j43Kty0ayellIUXfhPxJUmUkCQ6JwoyPEy6NiqDanlPclGpTQhsMjbgLrHrc/cL4BUmA WUs4udmoz2OEU0n9BYA6eihaZjE+l/GuSWWic36zd+Qskn1VPER35cuSJYHJWEkLHDJm s4hw== X-Gm-Message-State: ABuFfogLnBNlKiufW+zgs/rWpTS7Pb5ChGucQTRuHCzER8RH+UET4fTm Cgskob0XJB4Gh/M8aXz+btI= X-Google-Smtp-Source: ACcGV62jR5pREv7iRYsbfKPBGBXwRawneM2iF/I+XjWG/x9+1uxEZYsgH8mgQUHBbSnX6i9Xk1MFZA== X-Received: by 2002:a02:4f02:: with SMTP id c2-v6mr15105437jab.2.1540301709605; Tue, 23 Oct 2018 06:35:09 -0700 (PDT) Received: from raichu (toroon0560w-lp130-08-67-71-176-199.dsl.bell.ca. [67.71.176.199]) by smtp.gmail.com with ESMTPSA id u21-v6sm470245ioc.43.2018.10.23.06.35.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 06:35:08 -0700 (PDT) Sender: Mark Johnston Date: Tue, 23 Oct 2018 09:35:04 -0400 From: Mark Johnston To: Rajesh Kumar Cc: freebsd-current@freebsd.org Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 Message-ID: <20181023133504.GA28755@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-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, 23 Oct 2018 13:35:11 -0000 On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote: > Hi, > > I have a amd64 based board, where I could able to install upto FreeBSD 12.0 > ALPHA8 without issues. But starting ALPHA9, I start to see the below panic > during early boot. Looks like some sleep at unwanted place. I am using > the memstick image from dowload page. > > Please let me know if you need any details. I'm having trouble seeing what might have changed between ALPHA8 and 9 to cause this. At this point we've initialized the vm_phys page allocator, so we're not constrained by vm.boot_pages. >From the db> prompt, could you please run "show page" and "show pageq", and post the output? From owner-freebsd-current@freebsd.org Tue Oct 23 13:40:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FB73FD85A2 for ; Tue, 23 Oct 2018 13:40:16 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D1167CD28; Tue, 23 Oct 2018 13:40:15 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm1-x32e.google.com with SMTP id y11-v6so1842200wma.3; Tue, 23 Oct 2018 06:40: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=I+HXzV6/PmCOS8SEnsZEDYebcoPjeDOlKvGjncZLfpw=; b=F9s76DsY3WEwgceEmCtR5LGYV+FjHJZZ7H/uzL8XARP6pyiZEUj51Tl4T3tdiwjJwj SAjp4lI5Al8jSzFkzFFXUgpZmoYGnIAJ1SI21Rp4BtcNDsfPJ7g+0+ufAgtRRdGE3e79 K1HEvlsPo4JA/gqkouPux8wOkVi2pjPJjuUL23c4lpyqJVe4N4SwMqtdqwgWwRjh6hVo ngAOstgAzJOnEagu4dUlKCyMO6vsFq5Lw0ImisvN6ilS0AFEwaw3Myu5pRUoZl354b9c EeWqMHA8n830xowkl3UWP3Uv7QTZ7YCONcyOfk3wzxdSDkXNZICYCu3DuNb17CTrjC5t PC9A== 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=I+HXzV6/PmCOS8SEnsZEDYebcoPjeDOlKvGjncZLfpw=; b=bmFsimmaeki5oMkHyLTSXKYqud7cm0i7I2ZIiO8+02LO36H+Zibrc1uBP6CzUYHsGR 7sgnwkUMuzLs1ATtfzZt5chrEaWl09OMG7Vp5YN7TsTFQZVCWfq7N9/BTS33ru9aWdp9 Sl4826sHGxcIA3jrTug7KHRkzqxLYrh8MQ3fq7X5jJwkWw9euMdX4O/4XmhOK0QJ4bPr MCuMcWWT3VeUO/L6UOFAp2f76wIOijurhVsl+Xd4aLfpcyVtkpCVmmLn7xTILlL2hoRf eAV5lE3dWpFd2I3+4RKb6BSR3s7XbtNeg5Dwyb4PeSLUq2sw+3GYtksugaHdFW0xYREQ SeuA== X-Gm-Message-State: ABuFfohODgHROWF0Q0RD+0mw8DN7b75Iq/V1SiUcfHP/3oCzdCMr7JPe JDWU0TDVdt1YEMNk50iPZYFLb+69OWcE4tKCc77W5tn3 X-Google-Smtp-Source: ACcGV62gOEj1HeVYs312pxtHAtLy2ty+jAYrH/hoyFxsG0sFG68JN94PpStR1WpkCP8b0fjQ1s/kRVgCthn95k1grhE= X-Received: by 2002:a1c:4b15:: with SMTP id y21-v6mr20021752wma.122.1540302014221; Tue, 23 Oct 2018 06:40:14 -0700 (PDT) MIME-Version: 1.0 References: <20181023133504.GA28755@raichu> In-Reply-To: <20181023133504.GA28755@raichu> From: Rajesh Kumar Date: Tue, 23 Oct 2018 19:10:02 +0530 Message-ID: Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 To: markj@freebsd.org Cc: freebsd-current@freebsd.org 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, 23 Oct 2018 13:40:16 -0000 Hi Mark, > From the db> prompt, could you please run "show page" and "show pageq", > and post the output? The system gets hung when it runs to db prompt. I only have the option to force shutdown at that point. Is there any other way, I can collect what you need? On Tue, Oct 23, 2018 at 7:05 PM Mark Johnston wrote: > On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board, where I could able to install upto FreeBSD > 12.0 > > ALPHA8 without issues. But starting ALPHA9, I start to see the below > panic > > during early boot. Looks like some sleep at unwanted place. I am using > > the memstick image from dowload page. > > > > Please let me know if you need any details. > > I'm having trouble seeing what might have changed between ALPHA8 and 9 > to cause this. At this point we've initialized the vm_phys page > allocator, so we're not constrained by vm.boot_pages. > > From the db> prompt, could you please run "show page" and "show pageq", > and post the output? > From owner-freebsd-current@freebsd.org Tue Oct 23 13:51:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29B7CFD8F79 for ; Tue, 23 Oct 2018 13:51:55 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B1A847DA93 for ; Tue, 23 Oct 2018 13:51:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it1-x12a.google.com with SMTP id 134-v6so1962998itz.2 for ; Tue, 23 Oct 2018 06:51:54 -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=3XytoKaJ6DCB4ydUC6xeFsyqK7WbG0XzVfj8Tr+rNmc=; b=BAufr8UH9zQjY9in/oYlAWtQ4ag4AR8iljs7CIabnr7WUF4GilB4JgvHdjJzlIZbyB x7zARlKuhqwsKTD9EE21AHlSJgrUfjbH29VAWxZTVYxxm0agf8rnzskveDYhZlcFwcz1 jL8G7J3QiSps1RujnJCd4U3ND+jY1XJ8LZvETRtOpKsDg0qrG0HlIZPXJ0KdoaH1PJq9 Sq1qjI71324sXsI1ukKhgbn/fkWZfpHmYFQiBCcjXN+KOVqWYfo0+QG0czv2jGE+2LBG qHeLyhvEqqfY2XlHRbY9vmhGmC35NtKtJMr1JokJKPDma306VIC7RmJCWCF9PxtsoJaJ 48kw== 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=3XytoKaJ6DCB4ydUC6xeFsyqK7WbG0XzVfj8Tr+rNmc=; b=e7oiHiJa3fk3Omw7xlkYb304f19YFSwViViDWLU6aPOrdg9tAWOe6a5+6Nr0zkFiEM jvWFZU4R60wI+J8+soL+24+OODwOwMc1ogBNNaQE6jVyxlaU1m73ptx7Md74yu67DReX q2tAUn/IPqG4sSyb6d9qsKhBAW6ZpocFPv2+3+EmeNRD84uuxaH87WIYZNMakScK9gEh 0vNUcQJrxRLvC/3/EJDGHkwf/gJdUyR/rfoLsIuk9zTiW++RHeG6MFuQVxTJK8QZeWa8 vdu1MSGWo0aemwBZenHtvN2cdZHCAnt9NK1DcG1tJoghftSHhaMi0e/TezAYpqqN34EW uasw== X-Gm-Message-State: ABuFfogIbTifp7KUP5lyK1/pDAksvmHuCgRGIiRYJW2sWJGSgYYV15fu 4BBYZ0gVSfhmdVeEoN/AtN8= X-Google-Smtp-Source: ACcGV63vl7J7wfoVnsK1n+CpaeE9cfTI5Plgyf+c10mjHO6Pziq5KAw60l+TE4Kxtjv2jgmRrGyvFg== X-Received: by 2002:a24:81c1:: with SMTP id q184-v6mr13472954itd.152.1540302713906; Tue, 23 Oct 2018 06:51:53 -0700 (PDT) Received: from raichu (toroon0560w-lp130-08-67-71-176-199.dsl.bell.ca. [67.71.176.199]) by smtp.gmail.com with ESMTPSA id p16-v6sm673881itc.42.2018.10.23.06.51.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 06:51:52 -0700 (PDT) Sender: Mark Johnston Date: Tue, 23 Oct 2018 09:51:50 -0400 From: Mark Johnston To: Rajesh Kumar Cc: freebsd-current@freebsd.org Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 Message-ID: <20181023135150.GC28755@raichu> References: <20181023133504.GA28755@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-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, 23 Oct 2018 13:51:55 -0000 On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > Hi Mark, > > > From the db> prompt, could you please run "show page" and "show pageq", > > and post the output? > > The system gets hung when it runs to db prompt. I only have the option to > force shutdown at that point. Is there any other way, I can collect what > you need? Could you instead provide output from "sysctl vm" while the system has booted ALPHA8? > On Tue, Oct 23, 2018 at 7:05 PM Mark Johnston wrote: > > > On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote: > > > Hi, > > > > > > I have a amd64 based board, where I could able to install upto FreeBSD > > 12.0 > > > ALPHA8 without issues. But starting ALPHA9, I start to see the below > > panic > > > during early boot. Looks like some sleep at unwanted place. I am using > > > the memstick image from dowload page. > > > > > > Please let me know if you need any details. > > > > I'm having trouble seeing what might have changed between ALPHA8 and 9 > > to cause this. At this point we've initialized the vm_phys page > > allocator, so we're not constrained by vm.boot_pages. > > > > From the db> prompt, could you please run "show page" and "show pageq", > > and post the output? > > From owner-freebsd-current@freebsd.org Tue Oct 23 14:20:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08CF7FD9925 for ; Tue, 23 Oct 2018 14:20:09 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7ABDD7EACB; Tue, 23 Oct 2018 14:20:08 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm1-x333.google.com with SMTP id r63-v6so1989389wma.4; Tue, 23 Oct 2018 07:20: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=2ep5Y0hzWkC/H3UWqffFdY2prbAYTtzRii17WEKsh7o=; b=NzkLxBKUt34oY1arIl0Ta9aP2V5UCfTrIKztJzqGjUy29F7gEt8Bzy1qfa95logsSH JNMB3i2pNI1ek6PL7YTealwC2qo+cO7ijRGmrcs6tduo/xhbb0XLUNdy3yIlMtsDAWoG k36wdz48uO5Daqv7rcTDvB/R0PiHyjrkzqHMYc3LB0XeQQ8LqJSDkL+1wd7GO2Za6+fg 6r0279dQPmKf8lBguJkR/S28O6Dgx6C6ZafkmPqvVcwCak7WLbarjZGCJpgHracuFqif WyB/jZUSqWxlMHRdnOAgzs+AOSwU26ss/Aa8GBA57pbTyhnlkUW6+BouXgI6aUK/arE+ ggNA== 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=2ep5Y0hzWkC/H3UWqffFdY2prbAYTtzRii17WEKsh7o=; b=iTHgkgYFAjuuki1RpC0OgyIh+H4Fn3YqKYnqU596NPso5jVKdACufqlQJQmTyzACmM Z0wZgObeKuAtATiqi3DGymGVu/pfBT0IHgu93lGz5WSqWWv+TtNfyckBZhyurGiRFUL0 EWTHMjUvFZj5yB7bwsYtzI7dnpZOuU/L0nqlcUzFLbIdDLyt0af2OO9qMRt6oO+4wnaY uc45gPyVAVCgdoow1pqEGtLCUyA4ZIlGRYySRCvuQWpqVz/oiqYKqU9ilJaBe3Q0+CmN ctvmycME0hITP2aJ1E6tecGj7TI9kxfHc+1QqTznA1zQnl62VfFL/1WzKUtTCdbH3yXV LFWg== X-Gm-Message-State: ABuFfogPzDS3RzKgsxoH0EawyLZLHVj4FwwYUkl7HS2YfDDLYkVTsF7z jsSGNyFRPsPLD+yWj2ISBPDPcwjxQ0pPN5hHweLmOw== X-Google-Smtp-Source: ACcGV60CQJtpgLPN/eGqp2gWa7ccP5e5a8jk/HLZPWAuKl381GQvDV5QcFhR6K5Id0DKGzFBverVxp0PaVoSer9z1Og= X-Received: by 2002:a1c:b143:: with SMTP id a64-v6mr21088510wmf.109.1540304407208; Tue, 23 Oct 2018 07:20:07 -0700 (PDT) MIME-Version: 1.0 References: <20181023133504.GA28755@raichu> <20181023135150.GC28755@raichu> In-Reply-To: <20181023135150.GC28755@raichu> From: Rajesh Kumar Date: Tue, 23 Oct 2018 19:49:54 +0530 Message-ID: Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 To: markj@freebsd.org Cc: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="00000000000009e4780578e61132" 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, 23 Oct 2018 14:20:09 -0000 --00000000000009e4780578e61132 Content-Type: text/plain; charset="UTF-8" Hi Mark, Please find attached the "sysctl vm" output with ALPHA8. On Tue, Oct 23, 2018 at 7:21 PM Mark Johnston wrote: > On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > > Hi Mark, > > > > > From the db> prompt, could you please run "show page" and "show pageq", > > > and post the output? > > > > The system gets hung when it runs to db prompt. I only have the option to > > force shutdown at that point. Is there any other way, I can collect what > > you need? > > Could you instead provide output from "sysctl vm" while the system has > booted ALPHA8? > > > On Tue, Oct 23, 2018 at 7:05 PM Mark Johnston wrote: > > > > > On Tue, Oct 23, 2018 at 05:43:15PM +0530, Rajesh Kumar wrote: > > > > Hi, > > > > > > > > I have a amd64 based board, where I could able to install upto > FreeBSD > > > 12.0 > > > > ALPHA8 without issues. But starting ALPHA9, I start to see the below > > > panic > > > > during early boot. Looks like some sleep at unwanted place. I am > using > > > > the memstick image from dowload page. > > > > > > > > Please let me know if you need any details. > > > > > > I'm having trouble seeing what might have changed between ALPHA8 and 9 > > > to cause this. At this point we've initialized the vm_phys page > > > allocator, so we're not constrained by vm.boot_pages. > > > > > > From the db> prompt, could you please run "show page" and "show pageq", > > > and post the output? > > > > --00000000000009e4780578e61132 Content-Type: text/plain; charset="US-ASCII"; name="sysctl_vm_output_alpha8.txt" Content-Disposition: attachment; filename="sysctl_vm_output_alpha8.txt" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_jnltgp0p0 dm0udm10b3RhbDogClN5c3RlbSB3aWRlIHRvdGFscyBjb21wdXRlZCBldmVyeSBmaXZlIHNlY29u ZHM6ICh2YWx1ZXMgaW4ga2lsb2J5dGVzKQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PQpQcm9jZXNzZXM6CQkoUlVOUTogMSBEaXNrIFdhaXQ6IDAgUGFnZSBX YWl0OiAwIFNsZWVwOiAyNCkKVmlydHVhbCBNZW1vcnk6CQkoVG90YWw6IDUzODUxNDk5MksgQWN0 aXZlOiA1Mzg1MDIwNTZLKQpSZWFsIE1lbW9yeToJCShUb3RhbDogNDgzNDRLIEFjdGl2ZTogNDc2 NTZLKQpTaGFyZWQgVmlydHVhbCBNZW1vcnk6CShUb3RhbDogMjM5MTJLIEFjdGl2ZTogMTEwMDRL KQpTaGFyZWQgUmVhbCBNZW1vcnk6CShUb3RhbDogOTg4OEsgQWN0aXZlOiA5MjI0SykKRnJlZSBN ZW1vcnk6CTY0NTk0MjM2Swp2bS5sb2FkYXZnOiB7IDAuMTQgMC4wNiAwLjAyIH0Kdm0udl9mcmVl X21pbjogMTAyODM3CnZtLnZfZnJlZV90YXJnZXQ6IDM0NzQ0OAp2bS52X2ZyZWVfcmVzZXJ2ZWQ6 IDIxMzAwCnZtLnZfaW5hY3RpdmVfdGFyZ2V0OiA1MjExNzIKdm0udl9wYWdlb3V0X2ZyZWVfbWlu OiAzNAp2bS5zd2FwX2VuYWJsZWQ6IDEKdm0ub3ZlcmNvbW1pdDogMAp2bS5kb21haW4uMC5waWRj dHJsLmtkZDogOAp2bS5kb21haW4uMC5waWRjdHJsLmtpZDogNAp2bS5kb21haW4uMC5waWRjdHJs LmtwZDogMwp2bS5kb21haW4uMC5waWRjdHJsLmJvdW5kOiA1NTU5MTY4CnZtLmRvbWFpbi4wLnBp ZGN0cmwuaW50ZXJ2YWw6IDEwMAp2bS5kb21haW4uMC5waWRjdHJsLnNldHBvaW50OiAzNDc0NDgK dm0uZG9tYWluLjAucGlkY3RybC50aWNrczogMjE0Njk0OTg4Nwp2bS5kb21haW4uMC5waWRjdHJs Lm91dHB1dDogMAp2bS5kb21haW4uMC5waWRjdHJsLmlucHV0OiAxNjE0ODU2OQp2bS5kb21haW4u MC5waWRjdHJsLmRlcml2YXRpdmU6IDM0CnZtLmRvbWFpbi4wLnBpZGN0cmwuaW50ZWdyYWw6IDAK dm0uZG9tYWluLjAucGlkY3RybC5vbGRlcnJvcjogLTE1ODAxMTU1CnZtLmRvbWFpbi4wLnBpZGN0 cmwuZXJyb3I6IC0xNTgwMTEyMQp2bS5kb21haW4uMC5zdGF0cy5mcmVlX3NldmVyZTogNjIwNjgK dm0uZG9tYWluLjAuc3RhdHMuZnJlZV9taW46IDEwMjgzNwp2bS5kb21haW4uMC5zdGF0cy5mcmVl X3Jlc2VydmVkOiAyMTMwMAp2bS5kb21haW4uMC5zdGF0cy5mcmVlX3RhcmdldDogMzQ3NDQ4CnZt LmRvbWFpbi4wLnN0YXRzLmluYWN0aXZlX3RhcmdldDogNTIxMTcyCnZtLmRvbWFpbi4wLnN0YXRz LnVuc3dwcGRwZ3M6IDAKdm0uZG9tYWluLjAuc3RhdHMudW5zd2FwcGFibGU6IDAKdm0uZG9tYWlu LjAuc3RhdHMubGF1bmRwZHBnczogMAp2bS5kb21haW4uMC5zdGF0cy5sYXVuZHJ5OiAwCnZtLmRv bWFpbi4wLnN0YXRzLmluYWN0cGRwZ3M6IDAKdm0uZG9tYWluLjAuc3RhdHMuaW5hY3RpdmU6IDUy NQp2bS5kb21haW4uMC5zdGF0cy5hY3RwZHBnczogMjczCnZtLmRvbWFpbi4wLnN0YXRzLmFjdGl2 ZTogNDg4Ngp2bS5kb21haW4uMC5zdGF0cy5mcmVlX2NvdW50OiAxNjE0ODU1Mwp2bS5rdm1fZnJl ZTogMjE5NTQ2MDE5MDIwOAp2bS5rdm1fc2l6ZTogMjE5OTAyMzI1MTQ1Ngp2bS5wbWFwLmFkX2Vt dWxhdGlvbl9zdXBlcnBhZ2VfcHJvbW90aW9uczogMAp2bS5wbWFwLm51bV9zdXBlcnBhZ2VfYWNj ZXNzZWRfZW11bGF0aW9uczogMAp2bS5wbWFwLm51bV9hY2Nlc3NlZF9lbXVsYXRpb25zOiAwCnZt LnBtYXAubnVtX2RpcnR5X2VtdWxhdGlvbnM6IDAKdm0ucG1hcC5wZHBlLmRlbW90aW9uczogMwp2 bS5wbWFwLnBkZS5wcm9tb3Rpb25zOiA3OTcKdm0ucG1hcC5wZGUucF9mYWlsdXJlczogMAp2bS5w bWFwLnBkZS5tYXBwaW5nczogMAp2bS5wbWFwLnBkZS5kZW1vdGlvbnM6IDM5MAp2bS5wbWFwLnBj aWRfc2F2ZV9jbnQ6IDAKdm0ucG1hcC5wdGk6IDAKdm0ucG1hcC5pbnZwY2lkX3dvcmtzOiAwCnZt LnBtYXAucGNpZF9lbmFibGVkOiAwCnZtLnBtYXAucGdfcHNfZW5hYmxlZDogMQp2bS5wbWFwLnBh dF93b3JrczogMQp2bS5zd2FwX2lkbGVfdGhyZXNob2xkMjogMTAKdm0uc3dhcF9pZGxlX3RocmVz aG9sZDE6IDIKdm0uc3dhcF9pZGxlX2VuYWJsZWQ6IDAKdm0ucmVzZXJ2LnJlY2xhaW1lZDogMAp2 bS5yZXNlcnYucGFydHBvcHE6IApET01BSU4gICAgTEVWRUwgICAgIFNJWkUgIE5VTUJFUgoKICAg ICAwLCAgICAgIC0xLCAyNTEwODhLLCAgICAxMjgKCnZtLnJlc2Vydi5mdWxscG9wOiAxMjEKdm0u cmVzZXJ2LmZyZWVkOiA3OTUyCnZtLnJlc2Vydi5icm9rZW46IDAKdm0ubmRvbWFpbnM6IDEKdm0u cGh5c19sb2NhbGl0eTogCjA6IC0xIAoKdm0ucGh5c19zZWdzOiAKU0VHTUVOVCAwOgoKc3RhcnQ6 ICAgICAweDEwMDAwCmVuZDogICAgICAgMHg5ZjAwMApkb21haW46ICAgIDAKZnJlZSBsaXN0OiAw eGZmZmZmZmZmODIwNGZlMzAKClNFR01FTlQgMToKCnN0YXJ0OiAgICAgMHgxMDAwMDAKZW5kOiAg ICAgICAweDEwMDAwMDAKZG9tYWluOiAgICAwCmZyZWUgbGlzdDogMHhmZmZmZmZmZjgyMDRmZTMw CgpTRUdNRU5UIDI6CgpzdGFydDogICAgIDB4MTAwMDAwMAplbmQ6ICAgICAgIDB4MjcwZjAwMApk b21haW46ICAgIDAKZnJlZSBsaXN0OiAweGZmZmZmZmZmODIwNGZiYzAKClNFR01FTlQgMzoKCnN0 YXJ0OiAgICAgMHgyNzE3MDAwCmVuZDogICAgICAgMHgyNzRjMDAwCmRvbWFpbjogICAgMApmcmVl IGxpc3Q6IDB4ZmZmZmZmZmY4MjA0ZmJjMAoKU0VHTUVOVCA0OgoKc3RhcnQ6ICAgICAweDI4MDAw MDAKZW5kOiAgICAgICAweDcyOGUwMDAwCmRvbWFpbjogICAgMApmcmVlIGxpc3Q6IDB4ZmZmZmZm ZmY4MjA0ZmJjMAoKU0VHTUVOVCA1OgoKc3RhcnQ6ICAgICAweDcyOTBhMDAwCmVuZDogICAgICAg MHg3ODc3ZDAwMApkb21haW46ICAgIDAKZnJlZSBsaXN0OiAweGZmZmZmZmZmODIwNGZiYzAKClNF R01FTlQgNjoKCnN0YXJ0OiAgICAgMHg3OWU3ODAwMAplbmQ6ICAgICAgIDB4NzllYWMwMDAKZG9t YWluOiAgICAwCmZyZWUgbGlzdDogMHhmZmZmZmZmZjgyMDRmYmMwCgpTRUdNRU5UIDc6CgpzdGFy dDogICAgIDB4N2E2ODEwMDAKZW5kOiAgICAgICAweDdjMDAwMDAwCmRvbWFpbjogICAgMApmcmVl IGxpc3Q6IDB4ZmZmZmZmZmY4MjA0ZmJjMAoKU0VHTUVOVCA4OgoKc3RhcnQ6ICAgICAweDEwMDAw MDAwMAplbmQ6ICAgICAgIDB4MTAxNWNiMzAwMApkb21haW46ICAgIDAKZnJlZSBsaXN0OiAweGZm ZmZmZmZmODIwNGZiYzAKCnZtLnBoeXNfZnJlZTogCkRPTUFJTiAwOgoKRlJFRSBMSVNUIDA6Cgog IE9SREVSIChTSVpFKSAgfCAgTlVNQkVSCiAgICAgICAgICAgICAgICB8ICBQT09MIDAgIHwgIFBP T0wgMQotLSAgICAgICAgICAgIC0tIC0tICAgICAgLS0gLS0gICAgICAtLQogIDEyICggMTYzODRL KSAgfCAgICAzOTI2ICB8ICAgICAgIDAKICAxMSAoICA4MTkySykgIHwgICAgICAgMCAgfCAgICAg ICAxCiAgMTAgKCAgNDA5NkspICB8ICAgICAgIDEgIHwgICAgICAgMQogICA5ICggIDIwNDhLKSAg fCAgICAgICAxICB8ICAgICAgIDAKICAgOCAoICAxMDI0SykgIHwgICAgICAgMCAgfCAgICAgICAw CiAgIDcgKCAgIDUxMkspICB8ICAgICAgIDAgIHwgICAgICAgMAogICA2ICggICAyNTZLKSAgfCAg ICAgICAwICB8ICAgICAgIDEKICAgNSAoICAgMTI4SykgIHwgICAgICAgMCAgfCAgICAgICAxCiAg IDQgKCAgICA2NEspICB8ICAgICAgIDEgIHwgICAgICAgMQogICAzICggICAgMzJLKSAgfCAgICAg ICAwICB8ICAgICAgIDAKICAgMiAoICAgIDE2SykgIHwgICAgICAgMSAgfCAgICAgICAxCiAgIDEg KCAgICAgOEspICB8ICAgICAgIDAgIHwgICAgICAgMAogICAwICggICAgIDRLKSAgfCAgICAgICAx ICB8ICAgICAgIDEKCkZSRUUgTElTVCAxOgoKICBPUkRFUiAoU0laRSkgIHwgIE5VTUJFUgogICAg ICAgICAgICAgICAgfCAgUE9PTCAwICB8ICBQT09MIDEKLS0gICAgICAgICAgICAtLSAtLSAgICAg IC0tIC0tICAgICAgLS0KICAxMiAoIDE2Mzg0SykgIHwgICAgICAgMCAgfCAgICAgICAwCiAgMTEg KCAgODE5MkspICB8ICAgICAgIDAgIHwgICAgICAgMAogIDEwICggIDQwOTZLKSAgfCAgICAgICAw ICB8ICAgICAgIDAKICAgOSAoICAyMDQ4SykgIHwgICAgICAgMCAgfCAgICAgICAwCiAgIDggKCAg MTAyNEspICB8ICAgICAgIDAgIHwgICAgICAgMAogICA3ICggICA1MTJLKSAgfCAgICAgICAwICB8 ICAgICAgIDAKICAgNiAoICAgMjU2SykgIHwgICAgICAgMSAgfCAgICAgICAwCiAgIDUgKCAgIDEy OEspICB8ICAgICAgIDEgIHwgICAgICAgMAogICA0ICggICAgNjRLKSAgfCAgICAgICAyICB8ICAg ICAgIDAKICAgMyAoICAgIDMySykgIHwgICAgICAgMSAgfCAgICAgICAwCiAgIDIgKCAgICAxNksp ICB8ICAgICAgIDAgIHwgICAgICAgMAogICAxICggICAgIDhLKSAgfCAgICAgICAxICB8ICAgICAg IDAKICAgMCAoICAgICA0SykgIHwgICAgICAgMCAgfCAgICAgICAwCgp2bS5tYXhfd2lyZWQ6IDU0 MDYzMzQKdm0uYmFja2dyb3VuZF9sYXVuZGVyX21heDogMjA0ODAKdm0uYmFja2dyb3VuZF9sYXVu ZGVyX3JhdGU6IDQwOTYKdm0uYWN0X3NjYW5fbGF1bmRyeV93ZWlnaHQ6IDMKdm0ucGFnZW91dF9v b21fc2VxOiAxMgp2bS5wYWdlb3V0X2xvY2tfbWlzczogMAp2bS5kaXNhYmxlX3N3YXBzcGFjZV9w YWdlb3V0czogMAp2bS5sb3dtZW1fcGVyaW9kOiAxMAp2bS5wYWdlb3V0X3VwZGF0ZV9wZXJpb2Q6 IDYwMAp2bS5wYW5pY19vbl9vb206IDAKdm0ucGFnZV9ibGFja2xpc3Q6IAp2bS50cnlyZWxvY2tf cmVzdGFydDogMAp2bS5ib290X3BhZ2VzOiAxMDYKdm0ub2xkX21zeW5jOiAwCnZtLm9sZF9tbG9j azogMAp2bS5zdGF0cy5vYmplY3QuYnlwYXNzZXM6IDEwODkKdm0uc3RhdHMub2JqZWN0LmNvbGxh cHNlczogNjE0MQp2bS5zdGF0cy52bS52X3BkcGFnZXM6IDI3Mwp2bS5zdGF0cy52bS52X3RjYWNo ZWQ6IDAKdm0uc3RhdHMudm0udl9jYWNoZV9jb3VudDogMAp2bS5zdGF0cy52bS52X2ZyZWVfc2V2 ZXJlOiA2MjA2OAp2bS5zdGF0cy52bS52X2ludGVycnVwdF9mcmVlX21pbjogMgp2bS5zdGF0cy52 bS52X3BhZ2VvdXRfZnJlZV9taW46IDM0CnZtLnN0YXRzLnZtLnZfbGF1bmRyeV9jb3VudDogMAp2 bS5zdGF0cy52bS52X2luYWN0aXZlX2NvdW50OiA1MjUKdm0uc3RhdHMudm0udl9pbmFjdGl2ZV90 YXJnZXQ6IDUyMTE3Mgp2bS5zdGF0cy52bS52X2FjdGl2ZV9jb3VudDogNDg4Ngp2bS5zdGF0cy52 bS52X3dpcmVfY291bnQ6IDExNjgwNgp2bS5zdGF0cy52bS52X2ZyZWVfY291bnQ6IDE2MTQ4NTQ5 CnZtLnN0YXRzLnZtLnZfZnJlZV9taW46IDEwMjgzNwp2bS5zdGF0cy52bS52X2ZyZWVfdGFyZ2V0 OiAzNDc0NDgKdm0uc3RhdHMudm0udl9mcmVlX3Jlc2VydmVkOiAyMTMwMAp2bS5zdGF0cy52bS52 X3BhZ2VfY291bnQ6IDE2MzA3Nzg0CnZtLnN0YXRzLnZtLnZfcGFnZV9zaXplOiA0MDk2CnZtLnN0 YXRzLnZtLnZfa3RocmVhZHBhZ2VzOiAwCnZtLnN0YXRzLnZtLnZfcmZvcmtwYWdlczogMTE0CnZt LnN0YXRzLnZtLnZfdmZvcmtwYWdlczogODE3MAp2bS5zdGF0cy52bS52X2ZvcmtwYWdlczogMTg4 ODcwCnZtLnN0YXRzLnZtLnZfa3RocmVhZHM6IDE0OAp2bS5zdGF0cy52bS52X3Jmb3JrczogMgp2 bS5zdGF0cy52bS52X3Zmb3JrczogMjI3CnZtLnN0YXRzLnZtLnZfZm9ya3M6IDE3OTIKdm0uc3Rh dHMudm0udl90ZnJlZTogODQ1MTU5CnZtLnN0YXRzLnZtLnZfcGZyZWU6IDE1NjMxMgp2bS5zdGF0 cy52bS52X2RmcmVlOiAwCnZtLnN0YXRzLnZtLnZfcGRzaG9ydGZhbGxzOiAwCnZtLnN0YXRzLnZt LnZfcGR3YWtldXBzOiAwCnZtLnN0YXRzLnZtLnZfcmVhY3RpdmF0ZWQ6IDAKdm0uc3RhdHMudm0u dl9pbnRyYW5zOiAwCnZtLnN0YXRzLnZtLnZfdm5vZGVwZ3NvdXQ6IDAKdm0uc3RhdHMudm0udl92 bm9kZXBnc2luOiAzNzUxCnZtLnN0YXRzLnZtLnZfdm5vZGVvdXQ6IDAKdm0uc3RhdHMudm0udl92 bm9kZWluOiA1MTEKdm0uc3RhdHMudm0udl9zd2FwcGdzb3V0OiAwCnZtLnN0YXRzLnZtLnZfc3dh cHBnc2luOiAwCnZtLnN0YXRzLnZtLnZfc3dhcG91dDogMAp2bS5zdGF0cy52bS52X3N3YXBpbjog MAp2bS5zdGF0cy52bS52X296Zm9kOiAwCnZtLnN0YXRzLnZtLnZfemZvZDogMjA4MzM0CnZtLnN0 YXRzLnZtLnZfY293X29wdGltOiA3NAp2bS5zdGF0cy52bS52X2Nvd19mYXVsdHM6IDc3MjM4CnZt LnN0YXRzLnZtLnZfaW9fZmF1bHRzOiA0MDcKdm0uc3RhdHMudm0udl92bV9mYXVsdHM6IDMyMzY5 NAp2bS5zdGF0cy5zeXMudl9zb2Z0OiAxMDUzCnZtLnN0YXRzLnN5cy52X2ludHI6IDI4MTQKdm0u c3RhdHMuc3lzLnZfc3lzY2FsbDogODIzMDIwCnZtLnN0YXRzLnN5cy52X3RyYXA6IDMyNjEyNgp2 bS5zdGF0cy5zeXMudl9zd3RjaDogMzc1MjUKdm0udl9mcmVlX3NldmVyZTogNjIwNjgKdm0ubWF4 X2tlcm5lbF9hZGRyZXNzOiAxODQ0Njc0NDA3MzcwOTU0NzUyMAp2bS5taW5fa2VybmVsX2FkZHJl c3M6IDE4NDQ2NzQxODc0Njg2Mjk2MDY0CnZtLmtzdGFja3M6IDEyNTMKdm0ua3N0YWNrX2NhY2hl X3NpemU6IDEyOAp2bS56b25lX3dhcm5pbmdzOiAxCnZtLnpvbmVfY291bnQ6IDIxNgp2bS5kZWJ1 Zy5za2lwcGVkOiAwCnZtLmRlYnVnLnRyYXNoZWQ6IDAKdm0uZGVidWcuZGl2aXNvcjogMQp2bS5u c3dhcGRldjogMQp2bS5kbW1heDogMzIKdm0uc3dhcF9mcmFnbWVudGF0aW9uOiAKRnJlZSBzcGFj ZSBvbiBkZXZpY2UgYWRhMHAzOgpudW1iZXIgb2YgbWF4aW1hbCBmcmVlIHJhbmdlczogMQpsYXJn ZXN0IGZyZWUgcmFuZ2U6IDk4NjEwNwphdmVyYWdlIG1heGltYWwgZnJlZSByYW5nZSBzaXplOiA5 ODYxMDcKbnVtYmVyIG9mIG1heGltYWwgZnJlZSByYW5nZXMgb2YgZGlmZmVyZW50IHNpemVzOgog ICAgICAgICAgICAgICBjb3VudCAgfCAgc2l6ZSByYW5nZQogICAgICAgICAgICAgICAtLS0tLSAg fCAgLS0tLS0tLS0tLQogICAgICAgICAgICAgICAgICAgMSAgfCAgOTg2MTA3Cgp2bS5zd2FwX2Fz eW5jX21heDogNAp2bS5zd2FwX21heHBhZ2VzOiAxMzA0NjI0MTYKdm0uc3d6b25lOiAxMTA4OTMw NTM2CnZtLnN3YXBfcmVzZXJ2ZWQ6IDYyNjY2MzQyNAp2bS5zd2FwX3RvdGFsOiA0MDM5MTAyNDY0 CnZtLnBoeXNfcGFnZXJfY2x1c3RlcjogMTAyNAp2bS5rbWVtX21hcF9mcmVlOiA2NjQ5OTMwNTQ3 Mgp2bS5rbWVtX21hcF9zaXplOiAyOTczNzc3OTIKdm0ua21lbV9zaXplX3NjYWxlOiAxCnZtLmtt ZW1fc2l6ZV9tYXg6IDEzMTk0MTM5NTA4NzQKdm0ua21lbV9zaXplX21pbjogMAp2bS5rbWVtX3pt YXg6IDY1NTM2CnZtLmttZW1fc2l6ZTogNjY3OTY2ODMyNjQKdm0ubWRfbWFsbG9jX3dhaXQ6IDAK --00000000000009e4780578e61132-- From owner-freebsd-current@freebsd.org Tue Oct 23 14:21:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8518FD9AD9 for ; Tue, 23 Oct 2018 14:21:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 216C37F309 for ; Tue, 23 Oct 2018 14:21:51 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 0E9E7AC6 for ; Tue, 23 Oct 2018 17:21:50 +0300 (MSK) To: freebsd-current@freebsd.org Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: Date: Tue, 23 Oct 2018 17:21:49 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XWLO5CMBFeC7616r8migOSeFJATQYXPOF" 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, 23 Oct 2018 14:21:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XWLO5CMBFeC7616r8migOSeFJATQYXPOF Content-Type: multipart/mixed; boundary="M3SDvgw8oNEVpDHD0nysfUZZffDBRPHTE"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-current@freebsd.org Message-ID: Subject: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable --M3SDvgw8oNEVpDHD0nysfUZZffDBRPHTE Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I've built 13/current kernel with "-fno-optimize-sibling-calls" option to have full and true stacks. And my test stand (which is lousy Atom D2500, I need to admit) becomes unusable with such kernel. Here are NO any errors or message on console, but system drops ssh connection after several seconds (soemtimes before logon, sometimes right after showing shell), timeouts connections to it, etc. When I able to run "top -SH" (for several seconds!) it shows 98% idle! --=20 // Lev Serebryakov --M3SDvgw8oNEVpDHD0nysfUZZffDBRPHTE-- --XWLO5CMBFeC7616r8migOSeFJATQYXPOF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvPLn1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R4+PXg//Y7NK6p6nQi3kANfBCIDOrllWZnjKtLLMPTnIuotvgMUEvHIa32gkk3hu VAXjOyIMLVZ8I+q51O7YZEChMdGqmJ83+qMro4TwUEPboCjM32xC4SgWeehRzcA5 +4Tv8XYIXfWfReOAtwP0Al9pop5Xyh0vahYN0tLc50c5Lro2seXBbtK+BDfJD+aR PdTMwKhnpOu6eqFVHQcO2Tj+aVQeQxKTiLVgYOsPzYc+ZpIpJ9psje96arRXBQWK JGBHG4VddmlJUGryZHxYr/+NEm/+zrw3LW44AgXOpeotSQhH5q2uWlsAnGAuvgtE vTi3mSdYaAeeqhcCKnYalM/F6oaDdVGIvnDsTQRkq911iHp13Q3gkgWVLrQ2On5Q cohprBa9SWQXMPAlN4xlWZGfCa2xChgc1Az1AIxtyV7mjKtW4NBJrxy/Dg71j8Xg 7UGpA1AedV5dU8KtXKmBLbR/d4HdviOlAxcq7QpN9H9kYZyl6bjcom5QnxYaKV5Y j03iAYt36JKWnOVtw4XPRXKcGkPHha0VwiWrbPYAySFbwTV7US4sAV4RGSrdWmtF o/eMQ+pp7LJf7WO4qFhrQ5H+W6jTFnOP10mG5TdabnvCIfYn0sC4kULyC6rWU4YT zLFl892fHWdD6Fnn7jT2Wekrd47VnshLHXLnhVpbb82MCsKoiBI= =Twxn -----END PGP SIGNATURE----- --XWLO5CMBFeC7616r8migOSeFJATQYXPOF-- From owner-freebsd-current@freebsd.org Tue Oct 23 14:25:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87AEEFD9CAE for ; Tue, 23 Oct 2018 14:25:14 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id F3DE77F590 for ; Tue, 23 Oct 2018 14:25:13 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 37CCEAC8 for ; Tue, 23 Oct 2018 17:25:13 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable From: Lev Serebryakov To: freebsd-current@freebsd.org References: Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> Date: Tue, 23 Oct 2018 17:25:12 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="esSOgfIXQMP5gUhUNQqE2uyMCG8hXxCXD" 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, 23 Oct 2018 14:25:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --esSOgfIXQMP5gUhUNQqE2uyMCG8hXxCXD Content-Type: multipart/mixed; boundary="SXUPbFBSUNOaifU0Vg1sqkdN1GUFodaOY"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-current@freebsd.org Message-ID: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> Subject: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable References: In-Reply-To: --SXUPbFBSUNOaifU0Vg1sqkdN1GUFodaOY Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 23.10.2018 17:21, Lev Serebryakov wrote: > Here are NO any errors or message on console, but system drops ssh > connection after several seconds (soemtimes before logon, sometimes > right after showing shell), timeouts connections to it, etc. >=20 > When I able to run "top -SH" (for several seconds!) it shows 98% idle!= It is as simple as this: it crashes and reboots each 1-2 minutes... --=20 // Lev Serebryakov --SXUPbFBSUNOaifU0Vg1sqkdN1GUFodaOY-- --esSOgfIXQMP5gUhUNQqE2uyMCG8hXxCXD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvPL0hfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R48bwQ//fvh8HN38W8cGif04VdYNpNGVPErUzDnO18BfRI10pjnXARk5ywaECAWp +SS6v1Ya6DqzG4LMcXxrneT5HtG57UDhAxgEL31pOSbcPdWlqqz4VapxJTB6Q+lf c/Q1dcN+uO64nPPyXEfu2ovU4JGqcfldPJG/BZOJUxJxUH/7XRVb1+Ll4bDKVRfk 3VYjqzF851Saa/7gsGcEPl+t4Kl3fllWghhGZ9sMr8nzieUktnCE5tL0EyuFhGLU /tbTbPPswEHUpM59dbm8Em8PVRxED3RCY83P42gfoduZQiqwH3rqTk/o716nM2yM 4et+RSWZmvRCbwkBVQH8worUzUFgDy5BdU7VpTzfEla3DKJCSg77QYQglmj9rq74 kqu3/3xZVJxwQ2mOiqETJCvA79VU5MdXY1SDhcLnDBPuL4SIiRyQr5212g7WzYld WqEXw9jyzedP1bZONO7VlUdzPDlKtg/FWRQejFvXJfuu1ovJxwdLkyEgNPm/r4o3 pbn1e+QipcbNcweXJP0JLFkC+bF2LdWQYE3h6U5JW6yZu7K+Cqj9xyOHhS8+KCwj z2d0Tay+EvcQzrVq1IrKh90SOQNhSEczaays19bDWuAbsRVn+Fk7h9bmc3uy1/os arKMmdJAsYpH7lAaGjaBi9RptbL7pjf0SvnD0OUrsH00bjCP5rM= =ELpb -----END PGP SIGNATURE----- --esSOgfIXQMP5gUhUNQqE2uyMCG8hXxCXD-- From owner-freebsd-current@freebsd.org Tue Oct 23 14:41:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB4D0FE5431 for ; Tue, 23 Oct 2018 14:41:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 29FA47FEA8 for ; Tue, 23 Oct 2018 14:41:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.186] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id B82EAACB for ; Tue, 23 Oct 2018 17:41:34 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Solved (Was: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable) To: freebsd-current@freebsd.org References: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> From: Lev Serebryakov Openpgp: preference=signencrypt Autocrypt: addr=lev@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFKbGksBEADeguVs+XyJc3mL3iiOBqDd16wSk97YTJYOi4VsHsINzJr09oFvNDiaDBIi fLn2p8XcJvehcsF2GSgrfXfw+uK4O1jyNIKJmiYA0EtE+ZbRtvDrrE0w6Q8+SDeKA21SWh3Y vSQ0DJUontbgW55ER2CbEiIUTIn34uQ0kmESAaw/v5p/9ue8yPTmURvv130FqPFz8VPzltqL NxyGt54TxPfKAzAHEIwxlEZ63JOwzloKh1UDBExcsf9nJO08/TAVgR5UZ5njFBPzaaquhRoP qPJLEQQDqxPIlvMNtHKf7iIebE4BHeqgCdJA0BoiR6gpa0wlsZtdrTPK3n4wYSphLvGbhfOZ YW/hbcu7HYS/FImkVxB3iY17kcC1UTnx4ZaYeASPBGOOPbXky1lLfmDGWIFT//70yx+G17qD OZzF1SvJJhGvh6ilFYaWMX7T+nIp6Mcafc4D7AakXM+XdubNXOMlCJhzPcZ0skgAEnYV587w V7em5fDVwQccwvtfezzqKeJAU5TGiywBHSR5Svzk2FwRNf6M//hWkpq0SRR63iOhkHGOAEBi 69GfEIwH2/w24rLxP0E+Hqq8n+EWNkPatw1Mhcl5PKkdvGCjJUaGNMkpBffjyYo254JXRscR eEnwdIkJt4ErDvjb2/UrOFq31wWMOiLzJeVchAgvTHBMRfP9aQARAQABzShMZXYgU2VyZWJy eWFrb3YgPGxldkBzZXJlYnJ5YWtvdi5zcGIucnU+wsGCBBMBCAAsAhsDBwsJCAcDAgEGFQgC CQoLBBYCAwECHgECF4ACGQEFAlKbP8wFCQlmJwEACgkQ6rA8WL/cR4/6VBAAjRMyyX3PBFx/ HxyiIZ698EfwlWUua8Ft4crtrdK52m0qNkbBB9BH8xQgBHG32A1CwyzQnzxHgZuoOWMjh+Qq WJv7dmpM/q/c1GCJHhlPgewXrciTwpAamZILN071u+1GCPWwGRPzfQ/U+k63KJWx9ozf4doM WTTom6Cqcssi4J1u5kkt52a5ZRhsCK9pEVGilk36XTP9BakGrnMSIxF/NK4xeZVX2q+Nuqvf RchyofKXVgLEDLwb1cd/baLtBpDzy0PTN2Zl2lX4kOA6jwTKsqRya9A1Vui1KXwPh2XViTQ1 7Y3l5qg/M+sR73DohezP6bO6huOnLhty17jAqHPNlD6RonDo+j8uIlEg4iMSTN3MhzkBAu0Q pe3ucQ0o1767JiXN3fsNvRzSFhLVNDqPLce4uKlMogsbreXWvdgHGTN1ybOHGbybZnP77yHz uNBacbmG3vL/OLXMqwLdL2JXoiec4DmXjjCdhTBl5xLV9Hz/6VWKqElteg8QFVvHB3tHWzJ4 /rpiVEixytCIII6DS33BXZ0h2EOkK/6AYA2SJxy1vgOH4SZBtDBHoezmHV2nFnq5O0c7AuAB 7WPWgQG0sEwHQPZmg/baRGitRJnaxf/Gvf1DeD1x1VrcoVke2vwBcgDM3kugP8L9hsqic2D3 dI+gP76haeuvNNZr3y9L9zvOwU0EUpsaSwEQALRr3B+OjY/cnJPstz5CVsVWyEZtJtrNviZr tBgbkhlkPm98sEWR4+gbpyeufdYJengDjeGzMDKcLB7h5fICS/j6A8XdlJ40TlbPfNgb6OHa ebaIYKTJpXKR9sD7ZyGivYMofm0em40wGUX7BIkdkomaWj+wUiS0CdXU0FWDj9wv73+Eim+X zZyXeFgIPv97v+pET7DfwKkADOfrkW9s4OfvGVjd+wm35wc8EngQEz0qdPBxx74X7vZFAxlA SXu8gDBJGYt2Bkc3QwULnfeXrZJWgqNPR5o44gGu96yaiOFaN/C6CJtev5ZEX+0ZxbvsHHB7 Z5AtsRURKpZ4w5HFHGhzHtDtoAKgeZ/gbhTVXPHvNQR818eN+Nl5BV8BRF/8yhR6VlJb8GYw h8oKDeVGVYC34+raHZQAM9WoBnN7jlt4T9zzPwtmw5mIahGFgvw1KDr7OItN2ZgtZ20UYC5m Go602nmHq0aPbU6SwGi1xohrliNsKaaciYiMaVIGRQq8iGr9Fe2HlvaA3BpB275i/gCVlUdG y5XLAv+yQMUvn5Z7XVsMroxDk/O+ae1ElyBvKiKyfWGJXTg5XUukkkyQmfWPxWUGoNA1P/P4 GMHSu7/Rqe/7m4uPu/RyTTqsSjjKJdP9kBwEzvqPtXsVoZuShtrptRQJDYflhgE4qmKSMKen ABEBAAHCwWUEGAECAA8FAlKbGksCGwwFCRLMAwAACgkQ6rA8WL/cR48RkA//SNzeW3CI8KHx rA0aeHW6Nb5ieoqVRBGLyjBM06RX6vHB9v4dJL6Z+yV2jGN2s+XZX2HILbuTOwcTxGkI3xTT e0cDXVaF5K8R/liigUjtwuC2v/sWgoWyUmK1Cy9CPYdcXmFq6nESfkUe8DYiGOUULdHq5w63 F53yOZ72iXRBQBZgkhPtRFu4lPYIzOsMag9DIJ9CthR1r0ziqU/keb94Qt3l+aXK7CwGdY7X T4zUIMHNYsuAuyX+NJIXfsN68TT6m7QmlUwxPs13nxmoVQzm4ruV+hlQKh1MtbsjWRkNgPxF IPiqoAEhy8QoddlSvRTwL5Z7zFQiwMdiXU7toL8pfzj/zJR1jELXKMipijrt5MLrV8XX3OPN yZZvh95VIl8mv+iAqwSZUufd2EJnvj5TObB0eH+a+34NWf/XqA3fPjE6KHzmdnw9PZjPEjlx JCPECSs+6gse1+GaEfKYuXzB/ENe2ctlcfx5iQJXFc+/+zG/uU/JX/pXJHA12CUfB5g7lH6X BZIHvRo3VTCDjXgbF5xxDAe5V4exf8d4oSNjQIFLYxxN7zkvH89EN6RPfRgsWN7bYArCwfS9 MOgs9pFeCOewR6qieK150aoqNENGfKFXJup+5VVl6I0mU+j0rgVDZDht2/QgP/Tb4lGBe+ai pOGaK/GYNR+Ad6bUmokKsx4= Organization: FreeBSD Message-ID: Date: Tue, 23 Oct 2018 17:41:34 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="10MJTHzbO7SLBnwcbkEjsYEh8IkIqyek3" 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, 23 Oct 2018 14:41:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --10MJTHzbO7SLBnwcbkEjsYEh8IkIqyek3 Content-Type: multipart/mixed; boundary="0l5Utody5Cg5sjk1y5NldqfqlCSLL9fbY"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-current@freebsd.org Message-ID: Subject: Solved (Was: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable) References: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> In-Reply-To: <23463306-1c33-8d82-dbf4-fe5913407f89@FreeBSD.org> --0l5Utody5Cg5sjk1y5NldqfqlCSLL9fbY Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 23.10.2018 17:25, Lev Serebryakov wrote: >> Here are NO any errors or message on console, but system drops ssh >> connection after several seconds (soemtimes before logon, sometimes >> right after showing shell), timeouts connections to it, etc. >> >> When I able to run "top -SH" (for several seconds!) it shows 98% idle= ! > It is as simple as this: it crashes and reboots each 1-2 minutes... Stack overflow. I've increased kernel stack size and now it works (slowl= y). --=20 // Lev Serebryakov --0l5Utody5Cg5sjk1y5NldqfqlCSLL9fbY-- --10MJTHzbO7SLBnwcbkEjsYEh8IkIqyek3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlvPMx5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R4/PvBAAmsfYt6D0ubdRNYJqXYWVQD3Fznpf+kgtOeaV9ScaJZirKXl7rYCIAznO 42krVd8PgcrEYmi7dOAGYWQDJI+B9PFaDhA6XDJYPBxbOexogMpTfOIG68TRVztI UDQoOAvJdS2ohvWoXH2bwheK7a2wDvFsoaD0lwKdEewr/Ga99J4vegBrKTDpijVP AX48PHrOmAN2M78A4TboL1VdjAaQLRvcKFCpkQHgaLdEITLnhe7BBLsNRZSU8BCl znVLccZXJKLurbVx0U16vhaUmz1OMBupKn8AgESVjqHM84GADAA/Tr/TsxcbM8AM 9pUelo3n5AggEe3yKyuZjGdVcY/KA+I1NmoMvcUjmz5JAk7OJOZqmGGvLvp9mzwQ FZqFVeHJkiceMRXAssGqeMXvhL1He5w1x0BF+E+UFVSbBWlYOVfRgH+DaKGPHj2L /Gg+aybYIyD0imJPT86VJii5kWqTVuzDpXqhvuphToUVawGORT9MQqfTBVAmYCME SK433row2LsaWPYAKct0qQhSIKUq57klg0c9IWeWwdHVWhgDUl57TxyH9Cs+ZDkV l/nu/C2zKfOlI7CXptKEipt2hLyICR0kBzNy0BU2LO+10nrqCDf61uUs3cLxyVKC Q7sDt6S3aAmbeSEzFdWAq+GbxJzR2BWtMHt7ESTcT/u/OWuaj0Y= =GPSd -----END PGP SIGNATURE----- --10MJTHzbO7SLBnwcbkEjsYEh8IkIqyek3-- From owner-freebsd-current@freebsd.org Tue Oct 23 14:54:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FCCCFE59E0 for ; Tue, 23 Oct 2018 14:54:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 906EC8074E for ; Tue, 23 Oct 2018 14:54:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vk1-xa31.google.com with SMTP id l186so409987vke.0 for ; Tue, 23 Oct 2018 07:54:36 -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=vvQxqfuWBQciKwhpIarGU400W90ZCuhktLB/QJwN7Bo=; b=XWwAXSVSJyIsk6tvdcJQYMvSdEQbEQz7xtgbTY6N1UnlSexZcmk438mp/P22nIU4Sz 9P/qX3XVLQaWaYZFsI3thQRrQDIzpfNbSNKjGMfmj2MSNI6vcFeutarvsCfC9rAtw+VN iMmI59JhDF/cdFeXVDdHFYbp20BB61JVkT8RaLWmZxDUwXI18VqwQS3y7LxM1eE68/Wv /Ct89RXUcO6fritj0DMwmxBrg5jz8kgkqCwC3odNVfGlZQgOieGtRUJqsh/aLKriCHY/ haSf5yeVWTasm/2a05VM31OTglq7XRKHS9hmjV5lvBFYBpxdXwr0Wty1NsDDxqF//e8A 9mug== 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=vvQxqfuWBQciKwhpIarGU400W90ZCuhktLB/QJwN7Bo=; b=PpZOqapixmxcrLrkoAlbGG09tBAfp8RdzJowXe5YTYU6RzdFb8yE1Zt2PEAMyt4Akc hWNTawV2qxdjzDnpZSTcD/20P/tQmPyuykbWBleW9dKsMDyVjmbr60ZeQ08JJY2/ocWw 1VjtvHVFfoBf3VYyEZa5qzMDIh/S025M1SOsSQzZbGUlbrIBVKDvt67QZ1EYHTacj/M0 TcR8nzmNSMPRPvwfjE0p10qHUwUxSb2leMuJvWGB4N6OLyWV4AoS65fIoMPEB8nXcJXy UMvPP/qUKDt2AuJU7uwFgP554/W6zCeMUjkF7kpjP+1cQvDlh5SLy7fo8Dhdiuqil/ID 4pSQ== X-Gm-Message-State: ABuFfogsPgtlUkatu41ADEg9/AWMH6hDB6yRHrMCaoeNQXAhDuPqPy7P XMGggO4rz52feC3FCHK3RYg9oUGLtHys5+X7VgnRdA== X-Google-Smtp-Source: ACcGV62WIfXVRIeoF3Ehkz2Q79a25KWE+L4hiGGvb5ChnhpXW7XtiikUoi7X7tzmC2YoIHsj4OlrThwPOLSZ3/FDu70= X-Received: by 2002:a1f:2d07:: with SMTP id t7mr12662343vkt.45.1540306475850; Tue, 23 Oct 2018 07:54:35 -0700 (PDT) MIME-Version: 1.0 References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> In-Reply-To: <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> From: Warner Losh Date: Tue, 23 Oct 2018 08:54:24 -0600 Message-ID: Subject: Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) To: Toomas Soome Cc: Lev Serebryakov , Mark Millard , Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List 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: Tue, 23 Oct 2018 14:54:37 -0000 On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232483 (it is not > > threadripper-related, my hardware is Intel Atom). > > > > -- > > // Lev Serebryakov > > > > That error means something is corrupting the memory, it is hard to guess > what exactly and debugging it is nasty - it means we would need to track > down what was allocated before this memory block (guard1 is marker insert= ed > in front of the allocated memory block). > > Fortunately the code to print the partition table is in > stand/common/disk.c and the partition code is just next to it and so it > should be relatively easy to find the guilty one=E2=80=A6 I will try to s= ee if I > can replicate the issue. > We've had reports of other systems mysteriously hanging on boot with the new boot loader, but not older ones. It isn't limited to new AMD boxes, but it's been seen on other Intel boxes of various flavors. When we crash, it seems like we don't have a good recovery like we do with BTX. Maybe they are related? Warner From owner-freebsd-current@freebsd.org Tue Oct 23 15:12:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BF0EFE9270 for ; Tue, 23 Oct 2018 15:12:30 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92E5A81416 for ; Tue, 23 Oct 2018 15:12:29 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lj1-f172.google.com with SMTP id v6-v6so1727912ljc.11 for ; Tue, 23 Oct 2018 08:12:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=m/5Y+ELf8gk0o3XJnD7StKSf0V931AdyQcJSKUzV3uw=; b=koTAEL1999+Iv9jGiaG94hnnn6kW1eqiPfDYh+is4XI1WQQxRBGE/pihJCZy/QH1Xq CK5Mcp8/sHcnZuwLs819fpKz3As37nw25E1ylIQv4PdU1EVnuTzUq1o9AdMty23hpgQ5 Z8wsBDAoxyGb3ExE57dbWbov9T0jkd0C252fz4vzhHM55tIL4iSS093eJlakHiTdS4n7 l1PcYvDc97g182MBYvEt2BfFX9KlFt6Leil6cC91Ybxizzq82hdIDX+f5a4jPoNYZoAo DaRdJ0cK5Ngq5wK69DltWr66SjaGm0RnJspg5PEtGLv6Wq45FPl1e5Ix309vmsMpF5BU G8rw== X-Gm-Message-State: AGRZ1gIFeGMbz5A01ea1XN+oGSX4yTAtMuepas2ASuA9ASkmCxc0d3id /bN+7AlaNvBG20CvQFxQavm9SPhp X-Google-Smtp-Source: ACcGV63dYlYbxhp7OhA7RnnewDP5NUkthaeO7e2CpFMWJlKp8q0fiVZRRDJ57d3T5b90ScwVjbnM2w== X-Received: by 2002:a2e:594f:: with SMTP id n76-v6mr2475650ljb.70.1540307547707; Tue, 23 Oct 2018 08:12:27 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id e21-v6sm251191lfc.48.2018.10.23.08.12.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 08:12:20 -0700 (PDT) To: FreeBSD Current From: Andriy Gapon Subject: [CFT] patch for suspend on systems with shared interrupts Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Tue, 23 Oct 2018 18:12:17 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 23 Oct 2018 15:12:30 -0000 I am working on a patch to improve stability of suspend (and resume) on systems where an interrupt line (legacy PCI) is shared by multiple devices. If you have such a system and you experience hangs during suspend or resume, could you please test the patch? It's easy to check if you have shared interrupt. For example, you can run devinfo -u and check 'Interrupt request lines' of the output for any repeating numbers. I would also appreciate any reviews of the change. Especially, because it introduces new methods to the bus interface. I would like to ensure that the new methods are reasonable. The change is here: https://reviews.freebsd.org/D15755 Thank you. -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Oct 23 15:16:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13F06FE9488; Tue, 23 Oct 2018 15:16:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 9394B816BA; Tue, 23 Oct 2018 15:16:50 +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 w9NFGeIP062271 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Oct 2018 18:16:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9NFGeIP062271 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w9NFGe0A062270; Tue, 23 Oct 2018 18:16:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 23 Oct 2018 18:16:39 +0300 From: Konstantin Belousov To: Warner Losh Cc: Toomas Soome , Lev Serebryakov , Mark Millard , Konstantin Belousov , FreeBSD Current , FreeBSD-STABLE Mailing List Subject: Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated) Message-ID: <20181023151639.GX5335@kib.kiev.ua> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <18e270f6-c811-3f5e-bf65-76c895782c8f@FreeBSD.org> <7B44DEC3-9E79-46E0-BC02-E6C95680BF77@me.com> 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.10.1 (2018-07-13) 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-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, 23 Oct 2018 15:16:51 -0000 On Tue, Oct 23, 2018 at 08:54:24AM -0600, Warner Losh wrote: > On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > > > >> It would help to get output from loader lsdev -v command. > > > current loader crashes on "lsdev" for me: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232483 (it is not > > > threadripper-related, my hardware is Intel Atom). > > > > > > -- > > > // Lev Serebryakov > > > > > > > That error means something is corrupting the memory, it is hard to guess > > what exactly and debugging it is nasty - it means we would need to track > > down what was allocated before this memory block (guard1 is marker inserted > > in front of the allocated memory block). > > > > Fortunately the code to print the partition table is in > > stand/common/disk.c and the partition code is just next to it and so it > > should be relatively easy to find the guilty one… I will try to see if I > > can replicate the issue. > > > > We've had reports of other systems mysteriously hanging on boot with the > new boot loader, but not older ones. It isn't limited to new AMD boxes, but > it's been seen on other Intel boxes of various flavors. When we crash, it > seems like we don't have a good recovery like we do with BTX. Maybe they > are related? There is the 'grab_faults' command which might be used to get information about the fault (as in, CPU fault due to the programming mistake). You need to issue it before doing something that can cause the fault. It is not enabled by default due to the methods it uses to catch the exceptions. I recently noted that at least UEFI 2.7 provides debugging interfaces which can be used to achieve the same fault interception effect without hacks. From owner-freebsd-current@freebsd.org Tue Oct 23 15:30:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B5D7FE9B35 for ; Tue, 23 Oct 2018 15:30:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D72881D88; Tue, 23 Oct 2018 15:30:12 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg1-x544.google.com with SMTP id i4-v6so818733pgq.9; Tue, 23 Oct 2018 08:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0MhFJ64VzBiH4WqGDtU33x6KY4GqriCDxfbxwK6plnY=; b=q0Pf3j18HefsZecvZ9ur/xNE8aGnTlYnXj656QLqySqu0j/k3/y82lUqPWY0OOzckG BUOzfQFulK+qPgqcYNRPyB2zxpRhIwaWqqycF4YUDpC62ozPwTHV6cn20gTtY9ubQBNj JygWhOufFqDMnhpQdcgMmG4u0MuTozj1lZLv/mlt7cqhfHQ56Ewl64IgFBTcnr9jG+4T mqgvQYt+aHTeIkSDpg8QQFm/iZymlGJzkekxNCW5C2wnBNWCPHWA/KTidbBAv1y7hDjd EcCHtv20emaTvF9NXqg9vcALG0RyTHlTwk8ohFxWaAvPtNXd7Ebtm3OXzMqNAV7ditqd 6Dhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0MhFJ64VzBiH4WqGDtU33x6KY4GqriCDxfbxwK6plnY=; b=m67y/tH3bfBUzGJPIwNUoOp6K+fe4KaZeeYbPYL15VRPgFBjC58UDa+DSEEymNhL5V JvkYEzilfE1QEQeUAw0ofPo+Z3ND42070sNJxbmkLh8SKcfa7yjvjPLDwTA0DJqnkT2V 813FxUszcMabI1dKWbeJ8aeKn1N4TIvpPugVhHYgN8gH+bbIjuhn0zT3dAuySplj38vN 7fBeNcGkvD049/ZnE1y7znqZRpBnHlagrZLPvQuNsUMSs7BgIIiKkCDRzV/U38bM417v clUC8rRKahchEG5u60Yt5MuIXd66z6IvVQdfpPMh45eKt+eIxoWKopQ2q3l9mV79p/lM QyHg== X-Gm-Message-State: ABuFfogQ1D88qSHKXODnwlZhsu5GQhaY5dbaT8ryZWvmnuz2WLdH+kxk iHboeE6on+jFUafHlRZG47k4RYdH X-Google-Smtp-Source: ACcGV63bEGmRgdQG2B6mXn8D/M4STO/PecQc5r+JZWjrx2A+QF12oXrq19dceTda6+MPQUmzUYyU+A== X-Received: by 2002:aa7:80cd:: with SMTP id a13-v6mr49654616pfn.86.1540308611190; Tue, 23 Oct 2018 08:30:11 -0700 (PDT) Received: from ?IPv6:2607:fb90:816a:e308:8064:6dd6:884e:be4b? ([2607:fb90:816a:e308:8064:6dd6:884e:be4b]) by smtp.gmail.com with ESMTPSA id a16-v6sm6510759pgb.6.2018.10.23.08.30.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Oct 2018 08:30:10 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: which way to update export_args structure? From: Enji Cooper X-Mailer: iPhone Mail (16A404) In-Reply-To: <1540226963.490541.1550623304.5D6A95A6@webmail.messagingengine.com> Date: Tue, 23 Oct 2018 08:30:09 -0700 Cc: Brooks Davis , Rick Macklem , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <5BE9C124-9EA0-4B5D-BE0F-7A1F6C727250@gmail.com> References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> <20181022160508.GB45769@spindle.one-eyed-alien.net> <1540226963.490541.1550623304.5D6A95A6@webmail.messagingengine.com> To: Josh Paetzel 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, 23 Oct 2018 15:30:13 -0000 > On Oct 22, 2018, at 09:49, Josh Paetzel wrote: >=20 >=20 >=20 >> On Mon, Oct 22, 2018, at 11:05 AM, Brooks Davis wrote: >>=20 >>=20 >> This is the direction I'd been thinking. FWIW, the usecase is more that >> once you've moved away from the struct it's easy to make incremental >> changes then to use a 32-bit mountd on a 64-bit kernel. Moving toward >> size-independent interfaces helps both causes though. >>=20 >> -- Brooks >> Email had 1 attachment: >> + signature.asc >> 1k (application/pgp-signature) >=20 >=20 > Brooks, >=20 > What is the benefit or usecase for running a 32 bit mountd on a 64 bit ker= nel? There generally isn=E2=80=99t a case for doing this, but running a 32-bit mo= untd in a 32-bit chroot can allow someone with a working 32-bit environment a= t a company (for instance) to rebuild environments which rely on NFS mounts a= nd the like. This is an esoteric usecase, but I=E2=80=99ve seen it used before (and I=E2=80= =99ve used it myself ;)..). I don=E2=80=99t think this niche usecase should hinder forward progress in t= erms of modernizing the base OS though. Biarch usecases are diminishing over= time. -Enji= From owner-freebsd-current@freebsd.org Tue Oct 23 15:28:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9431FE9A9E; Tue, 23 Oct 2018 15:28:18 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from um-nip3-missouri-out.um.umsystem.edu (um-nip3-missouri-out.um.umsystem.edu [198.209.49.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "um-tip1.um.umsystem.edu", Issuer "InCommon RSA Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CEE3E81D42; Tue, 23 Oct 2018 15:28:17 +0000 (UTC) (envelope-from stephen@missouri.edu) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FxBAD0PM9b/xk40cZjGgEBAQEBAgEBA?= =?us-ascii?q?QEHAgEBAQGBZQKCA4FlMoNrlDWFTJNXgXkBCwEsgUuCdQIXhRQhPQUMAQMBAQI?= =?us-ascii?q?BAQICAmkohTwGIxFFEAIBCBoCJgICAjAVEAIEAQwBBwEBFYMIggKmXYEuiE4BB?= =?us-ascii?q?4FLgQuKVxeCAIE4gW1+iAGCVwKKWZN3CQKQbB2QMJZEAgICAgkCFIFtAQ6BVXI?= =?us-ascii?q?TgyiCJReOGoIXimYBgR4BAQ?= X-IPAS-Result: =?us-ascii?q?A2FxBAD0PM9b/xk40cZjGgEBAQEBAgEBAQEHAgEBAQGBZQK?= =?us-ascii?q?CA4FlMoNrlDWFTJNXgXkBCwEsgUuCdQIXhRQhPQUMAQMBAQIBAQICAmkohTwGI?= =?us-ascii?q?xFFEAIBCBoCJgICAjAVEAIEAQwBBwEBFYMIggKmXYEuiE4BB4FLgQuKVxeCAIE?= =?us-ascii?q?4gW1+iAGCVwKKWZN3CQKQbB2QMJZEAgICAgkCFIFtAQ6BVXITgyiCJReOGoIXi?= =?us-ascii?q?mYBgR4BAQ?= Received: from ex2-t17.um.umsystem.edu ([198.209.56.25]) by um-nip3-exch-relay.um.umsystem.edu with ESMTP; 23 Oct 2018 10:27:07 -0500 Received: from EX2-N14.um.umsystem.edu (198.209.56.22) by EX2-T17.um.umsystem.edu (198.209.56.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1531.3; Tue, 23 Oct 2018 10:27:06 -0500 Received: from EX2-N14.um.umsystem.edu ([198.209.56.22]) by EX2-N14.um.umsystem.edu ([198.209.56.22]) with mapi id 15.01.1531.003; Tue, 23 Oct 2018 10:27:06 -0500 From: "Montgomery-Smith, Stephen" To: "Julian H. Stacey" , "Rodney W. Grimes" CC: "ctm-users@freebsd.org" , Poul-Henning Kamp , FreeBSD Current , Ed Maste , Warner Losh Subject: Re: ctm(1) deprecation in the FreeBSD base system? Thread-Topic: ctm(1) deprecation in the FreeBSD base system? Thread-Index: AQHUak6oFha2k0mYvU+8ASXkS/fskqUtSOmA Date: Tue, 23 Oct 2018 15:27:06 +0000 Message-ID: References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> In-Reply-To: <201810222132.w9MLVvxC050976@fire.js.berklix.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 x-originating-ip: [128.206.49.160] Content-Type: text/plain; charset="utf-8" Content-ID: <9EC24256A0EA5A4BA569B28D753BA66F@missouri.edu> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 23 Oct 2018 15:36:14 +0000 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, 23 Oct 2018 15:28:18 -0000 SSBoYXZlIG5vIHByb2JsZW0gdHVybmluZyBjdG0gaW50byBhIHBvcnQuICBCdXQgSSB3b3VsZCBh cHByZWNpYXRlDQphZHZpY2Ugb24gd2hldGhlciB0aGVyZSBpcyBhIHN0YW5kYXJkIG9yIGVhc3kg cHJvY2VzcyBmb3IgY29udmVydGluZw0Kc29mdHdhcmUgZnJvbSB0aGUgRnJlZUJTRCBiYXNlIHRv IGEgcG9ydC4gIElmIG5vdCwgSSBjYW4gbXVkZGxlIG15IHdheQ0KdGhyb3VnaCBpdC4gIEJ1dCBn aXZlIG1lIHNvbWUgdGltZSAoYSBmZXcgbW9udGhzKSB0byBnZXQgaXQgZG9uZSwNCmJlY2F1c2Ug dGhlIHJlc3Qgb2YgbXkgbGlmZSBpcyBtYWtpbmcgaGVhdnkgZGVtYW5kcyBvbiBtZSByaWdodCBu b3cuDQoNCkkgZG8gaGF2ZSB3cml0ZSBhY2Nlc3MgdG8gY3RtLWFubm91bmNlQCwgb3IgYXQgbGVh c3QgSSBkaWQgdGhlIGxhc3QgdGltZQ0KSSBjaGVja2VkLiAgSSBkb24ndCB1c2UgaXQgdmVyeSBt dWNoLCBiZWNhdXNlIEkgbGlrZSBmb3IgcGVvcGxlIHRvIGhhdmUNCnRoZSBhYmlsaXR5IHRvIHJl cGx5IHRvIG15IG1lc3NhZ2VzLg0KDQpJIGRvIHJlYWxpemUgdGhhdCB0aGUgbnVtYmVyIG9mIHBl b3BsZSB1c2luZyBjdG0gaXMgdmVyeSBsb3cuICBJIHVzZWQgdG8NCmJlIGEgdXNlciBteXNlbGYs IGJ1dCBub3cgSSBmaW5kIHN2biBhIGxvdCBtb3JlIGNvbnZlbmllbnQuICBCdXQgdGhlDQplZmZv cnQgZm9yIG1lIHRvIG1haW50YWluIGN0bSBpc24ndCB0aGF0IGdyZWF0LCBzbyBJIGFtIHdpbGxp bmcgdG8ga2VlcA0KaXQgbW92aW5nIGZvciB0aGUgZmV3Lg0KDQpCZXN0IHJlZ2FyZHMsDQpTdGVw aGVuIE1vbnRnb21lcnktU21pdGgNCkNUTSBtYWludGFpbmVy From owner-freebsd-current@freebsd.org Tue Oct 23 15:38:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFE5CFEA209 for ; Tue, 23 Oct 2018 15:38:23 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 217EB827A1; Tue, 23 Oct 2018 15:38:23 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9NFcIl5021282; Tue, 23 Oct 2018 08:38:18 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9NFcIrf021281; Tue, 23 Oct 2018 08:38:18 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810231538.w9NFcIrf021281@pdx.rh.CN85.dnsmgr.net> Subject: Re: careless commits disrupt In-Reply-To: <3736ed03-e849-fb14-daac-2653d86f6202@freebsd.org> To: Stefan Esser Date: Tue, 23 Oct 2018 08:38:18 -0700 (PDT) CC: "Julian H. Stacey" , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 23 Oct 2018 15:38:23 -0000 > Am 22.10.18 um 23:09 schrieb Julian H. Stacey: > > Hi, Reference: > >> From: Stefan Esser > >> Date: Fri, 12 Oct 2018 11:44:59 +0200 > > > > Stefan Esser wrote: > >> I might have mentioned, that I always preserve old shared libraries in > >> /usr/lib/compat before running "make delete-old-libs". > > > > Good idea, are you doing that manually, or do you have a patch to share ? > > I do it manually, but I have a script that checks for programs in the > base system and packages that use any library moved to the lib/compat > directory - see below. > > The base system checks should never give any output (unless there are > old and obsolete binaries). > > I use the package list to identify packages that must be rebuilt to > make the compat libraries obsolete. Since there may be shared library > version conflicts, if some > > Regards, STefan > > ------------------------------------------------------------ > > #!/bin/sh > > find_compat_depend () { > local dir="$1" > local pattern="$2" > > find "$dir" -type f ${pattern:+-name "$pattern"} \ > -exec sh -c "ldd {} 2>/dev/null | grep -lq /compat/ && echo {}" \; > } > > echo "Base system programs referencing compat libraries:" > find_compat_depend /bin "" > find_compat_depend /sbin "" > find_compat_depend /libexec "" > #find_compat_depend /lib "lib*.so.*" > find_compat_depend /usr/bin "" > find_compat_depend /usr/sbin "" > find_compat_depend /usr/libexec "" > #find_compat_depend /usr/lib "lib*.so.*" > > echo > echo "Installed packages referencing compat libraries:" > { > find_compat_depend /usr/local/bin "" > find_compat_depend /usr/local/sbin "" > find_compat_depend /usr/local/libexec "" > find_compat_depend /usr/local/lib "lib*.so.*" > } | xargs pkg which -q | sort -u Could this be added in a more generic way to pkg? pkg finddep $PATH $ALTLIBDIR I see this as "Very Useful" (TM) -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Oct 23 16:44:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E06BFEBFA7; Tue, 23 Oct 2018 16:44:43 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCFA084EFD; Tue, 23 Oct 2018 16:44:42 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd14.aul.t-online.de (fwd14.aul.t-online.de [172.20.26.242]) by mailout12.t-online.de (Postfix) with SMTP id 9803841C4D78; Tue, 23 Oct 2018 18:44:35 +0200 (CEST) Received: from Stefans-MBP-LAN.fritz.box (TcTrn6ZBghe2xKiKhX4nXe1P4-uKLx4MDGUMYRKowcmYHMkniM1ohs0SDiEdXSpQUV@[80.128.111.25]) by fwd14.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1gEznA-2PbQh60; Tue, 23 Oct 2018 18:44:28 +0200 Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: "Montgomery-Smith, Stephen" , "Julian H. Stacey" , "Rodney W. Grimes" Cc: "ctm-users@freebsd.org" , Poul-Henning Kamp , FreeBSD Current , Ed Maste , Warner Losh References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Message-ID: Date: Tue, 23 Oct 2018 18:44:27 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-ID: TcTrn6ZBghe2xKiKhX4nXe1P4-uKLx4MDGUMYRKowcmYHMkniM1ohs0SDiEdXSpQUV X-TOI-MSGID: 77a89d11-27b2-4a7b-9220-1d5fd8628276 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, 23 Oct 2018 16:44:43 -0000 Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > I have no problem turning ctm into a port. But I would appreciate > advice on whether there is a standard or easy process for converting > software from the FreeBSD base to a port. If not, I can muddle my way > through it. But give me some time (a few months) to get it done, > because the rest of my life is making heavy demands on me right now. Hi Stephen, I could spend a few hours to perform the conversion to a port and to test it. I've a happy CTM user, many years ago, and I can understand that it still may be useful in special situations. The source archive will need to be hosted somewhere. Do you have a preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? Regards, STefan From owner-freebsd-current@freebsd.org Tue Oct 23 17:04:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B4D2FECA63 for ; Tue, 23 Oct 2018 17:04:35 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADFA485BB5; Tue, 23 Oct 2018 17:04:34 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w9NH4WjA094838 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Oct 2018 10:04:32 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w9NH4Wbp094837; Tue, 23 Oct 2018 10:04:32 -0700 (PDT) (envelope-from jmg) Date: Tue, 23 Oct 2018 10:04:32 -0700 From: John-Mark Gurney To: Brooks Davis Cc: Rick Macklem , FreeBSD Current , Josh Paetzel Subject: Re: which way to update export_args structure? Message-ID: <20181023170432.GA75530@funkthat.com> Mail-Followup-To: Brooks Davis , Rick Macklem , FreeBSD Current , Josh Paetzel References: <20181003155133.GA57729@spindle.one-eyed-alien.net> <20181008170428.GB9766@spindle.one-eyed-alien.net> <20181022160508.GB45769@spindle.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xB0nW4MQa6jZONgY" Content-Disposition: inline In-Reply-To: <20181022160508.GB45769@spindle.one-eyed-alien.net> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Tue, 23 Oct 2018 10:04:33 -0700 (PDT) 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, 23 Oct 2018 17:04:35 -0000 --xB0nW4MQa6jZONgY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Brooks Davis wrote this message on Mon, Oct 22, 2018 at 16:05 +0000: > > + switch (len) { > > + case (sizeof(struct oexport_args)): > > + case (sizeof(struct o2export_args)): > > + memset(&export, 0, sizeof(export)); >=20 > I think this is now redundant. >=20 > > + memset(&o2export, 0, sizeof(o2export)); >=20 > This is certainly redundant given that you immediately copy over it. This is not redundant if sizeof oexport_args < sizeof o2export, and len =3D=3D sizeof oexport_args... It zeros out the remaining of the buffer= =2E. > > + memcpy(&o2export, bufp, len); --=20 John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." --xB0nW4MQa6jZONgY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJbz1SfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2MEI1RTRGMTNDNzYyMDZDNjEyMDBCNjAy MDVGMEIzM0REMDA2QURBAAoJECBfCzPdAGratBAQAJJ5iFD1v7pXoqcfux12Zh7R 23ii+X8jMbDICtS1L6OP85Wa1dHHrzTz8h5Ro17Ri9dMPYj0M18/3l7XnUBMBWLt aXqiaCIjBB9eKafHWIbXSbxyxPLrp2H86C2ZPBB4gtcFMxUYNt5rLWLw3NBm5Mz1 GAdxDMBlhIyAPCuFI6F9ioDE2tJNKgz0M0TUvuNRUZO5RocRbH8JD+Ny2nrdcZsl CUx1He9E1xDP/JkRbgdbHY2X0tp2YqWlHjKFrfM0r9rq4pXsPDgDGp6dKY5Pcb9O qREf3Id2c17YtyUKR6W6UyNrbgSOZhRQrc/zWzmNzdjoj2t9pwnzV23sR0McHVuw BOQS4rBU70j3ZdGeqLqWfrvFPUwDNU/Ez3jQ8N2fXnP31hrSClqyjltcTBCyuarM dJ4zyS9XD6UNOZea5sUpPe+x0yqrFzM/UYp/pJaDhqDo+oIcPCQ9tYHE1STVlaYM OGRlBbdoB6ORoX+XQYGojpsTFIL5Wj4KJQcOnPYLd4LYi2BmHaoCJSlHsLxMocvK CkkUHWpmCRSr8uTbkNSW0Ipb7kas5I62SSYRxLH+7sRRYS4IdeuFG9D4wzWVpi5A ZEUMcgbLF6eVRUc81OiPu55bsfSooBFY+l5PsZapOVfSav7HL2Eto7DkeJUElCb+ qPlXiBwJ6KincWDNn5+a =quRR -----END PGP SIGNATURE----- --xB0nW4MQa6jZONgY-- From owner-freebsd-current@freebsd.org Tue Oct 23 17:06:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD869FECBD8 for ; Tue, 23 Oct 2018 17:06:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E13E85E23 for ; Tue, 23 Oct 2018 17:06:51 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x92b.google.com with SMTP id c21so788697uap.7 for ; Tue, 23 Oct 2018 10:06:51 -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=7Up7cl1Kjqmm4TMghiE4veG9oVPWRT9qnl/NijPLn+c=; b=McoBZ9A1nBBkFajtuHH9HuPwZL815iJKzMfZQw9WBHAF+V+HLfP3WTdSJIZ4xI8PB/ T8CH3FINPIjj75OGUOErE+cV4hanCZQ1vU6SYA9QuypUmBsNLa8ghQAF2gYt4oItFF+d R7xwrF1gcHwFzGitkGizGNvqANWnxRBKt6x+iKBXH4f0y6YHgZrqe5fquE3BiHnBBNNT sgboXHxCaRkL/V6TJVbggnXDez+jdV7byGBuYAynMj5Gm5MQiXZNHizYeFUGIdZ2ZuLL K1AtCMXwQPTDrdK8Ix61eoT8l/776O7AVSmdoFT2q3UIiLGk6QeDWlGqff3GYKbDOqcC 9utQ== 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=7Up7cl1Kjqmm4TMghiE4veG9oVPWRT9qnl/NijPLn+c=; b=ob33dA+/2+AtXFhyh2cC/JDsvUtHxoUPSQAgnQm8cJbHOtGhHZfF6XvJ6dCrhJj8bk q+9GDwv/eUT75zKJ8qvVfWYlTUDUhmRa1BInRR+p6YOPndlcyzlg5EiQX7hTfsZA5VoR 7YBovXNn2zR891ZlfpMIYkMO+yhyq+9XWlhIgOkenMzwGmhaBxkmnldiiUhCOhu82ljG 4lFNeyz2Ofoolf/UYJI458AAbOas7UrJ/73wooQepStniQQ8gMGTVonDy+aweDnPLxKF +Jbzam/MAeAtch4rpnZmbbW35XwVRda0XV+ZCZFwR5F3E8Y6sAPrKJipc8e/6jeCO8q8 wT9w== X-Gm-Message-State: ABuFfogur0EeiGzUMwp/ecvIaTvIG7adXTCBvpL4vh1brxf7Z1cD5Y1Z i4XuLJF2Z4bnaSG4NOufVoHiiUvGDCnUlE0oQzSihg== X-Google-Smtp-Source: ACcGV60ZQME9qhXbmVI3YZs1tVY7tLc0SykD9QHtjyPQNZryaav+kOHc8yxrnuHlWa2JMwf/Z0RiRUO4qha//i8ANLA= X-Received: by 2002:ab0:53c3:: with SMTP id l3mr21613666uaa.16.1540314410410; Tue, 23 Oct 2018 10:06:50 -0700 (PDT) MIME-Version: 1.0 References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> In-Reply-To: From: Warner Losh Date: Tue, 23 Oct 2018 11:06:39 -0600 Message-ID: Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: Stefan Esser Cc: "Montgomery-Smith, Stephen" , "Julian H. Stacey" , "Rodney W. Grimes" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste 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, 23 Oct 2018 17:06:52 -0000 On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser wrote: > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > I have no problem turning ctm into a port. But I would appreciate > > advice on whether there is a standard or easy process for converting > > software from the FreeBSD base to a port. If not, I can muddle my way > > through it. But give me some time (a few months) to get it done, > > because the rest of my life is making heavy demands on me right now. > > Hi Stephen, > > I could spend a few hours to perform the conversion to a port and to > test it. I've a happy CTM user, many years ago, and I can understand > that it still may be useful in special situations. > > The source archive will need to be hosted somewhere. Do you have a > preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? > It's trivial to setup a new repository on github.com/freebsd/ctm for this purpose. With the right magic, we could even retain the commit history. Warner From owner-freebsd-current@freebsd.org Tue Oct 23 17:58:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D400AFEE289 for ; Tue, 23 Oct 2018 17:58:51 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "saper.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A40388B30 for ; Tue, 23 Oct 2018 17:58:51 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id w9NHwnWB021657 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 23 Oct 2018 17:58:49 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1540317529; bh=YkeMhK56XqlWCuxsUwIrcrNhgtWItGSRcmt2JaEkZY4=; h=Date:From:To:Subject; b=St8xQi8Xgrhw0Rtw/saOzVk9cFFCGQ/z/83kFUe/Fiv+uQXBD3/zJPBB34YLVyokF u3KAwBZlbllLi2fvNe2DeWisSuUmgBvxc1MP6mIkq/IzVS1ZkTgMdollwU+/XqEqJP 4+xp8boN1xnWNpmzxgRKWrdjciKzjkF3lNNLHL0Y= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id w9NHwndd021654 for ; Tue, 23 Oct 2018 17:58:49 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Tue, 23 Oct 2018 17:58:48 +0000 From: Marcin Cieslak To: FreeBSD Current Subject: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="1563967779-1725412313-1540317529=:5494" 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, 23 Oct 2018 17:58:52 -0000 --1563967779-1725412313-1540317529=:5494 Content-Type: text/plain; charset=US-ASCII Hello, I have a freshly built 12.0-ALPHA10 (r339406) and the kernel panicked at some point (another mail coming on that). I have a full dump partition enabled, but during savecore quite lot BFD assertion messages appear: Tue Oct 23 18:45:53 CEST 2018 FreeBSD radziecki 12.0-ALPHA10 FreeBSD 12.0-ALPHA10 r339406 GENERIC amd64 panic: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...BFD: /boot/kernel/kernel: invalid relocation type 37 BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 The kernel has been built on 11.1 with LD=/usr/bin/ld.lld Is this something that matters at all? Marcin --1563967779-1725412313-1540317529=:5494 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: BASE64 Content-Description: S/MIME Cryptographic Signature Content-Disposition: attachment; filename=smime.p7s MIIOSwYJKoZIhvcNAQcCoIIOPDCCDjgCAQExDzANBglghkgBZQMEAgEFADAL BgkqhkiG9w0BBwGgggqQMIIElzCCA3+gAwIBAgIOSBtqCKJEiNNcmz3JSA0w DQYJKoZIhvcNAQELBQAwTDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENB IC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24xEzARBgNVBAMTCkdsb2JhbFNp Z24wHhcNMTYwNjE1MDAwMDAwWhcNMjQwNjE1MDAwMDAwWjBdMQswCQYDVQQG EwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xv YmFsU2lnbiBQZXJzb25hbFNpZ24gMSBDQSAtIFNIQTI1NiAtIEczMIIBIjAN BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyrCba00KOKyGuwh9h+/MAcZm ZUF9OxGKA56AADHaDE08rB0WEbgm6J4XvJP3OGQ7cgHdVJu6XMZkRd6EcfjD yRrIwE6oAVWJe57co3gKk/XxvuubSZuUahrcOiv3D2qaHwva4zumubxQQI4f unEzRIJHPiNjaq0cCcZsMcp5pxsEz8aG0sr8Oh80sxKNnzPmuUETLESktfMC pQKHUGmWXLsG6sgCZOezUjDjKpPKW7l4PUt0TEBEyqLhifv9/YPn5C4o10PP daDazZPeKNif2PVQ5u0HRnkFrHh4wmmrMtY22Mse3eR01gD6rEEGWf+gdzuy EQE+ZVlNhCP4gXjdBQIDAQABo4IBZDCCAWAwDgYDVR0PAQH/BAQDAgEGMCcG A1UdJQQgMB4GCCsGAQUFBwMCBggrBgEFBQcDBAYIKwYBBQUHAwkwEgYDVR0T AQH/BAgwBgEB/wIBADAdBgNVHQ4EFgQUlifCwqX3HPgCenpkr2NvMtKYwrEw HwYDVR0jBBgwFoAUj/BLf6guRSSuTVD6Y5qL3uLdG7wwPgYIKwYBBQUHAQEE MjAwMC4GCCsGAQUFBzABhiJodHRwOi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20v cm9vdHIzMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuZ2xvYmFsc2ln bi5jb20vcm9vdC1yMy5jcmwwWQYDVR0gBFIwUDALBgkrBgEEAaAyASgwQQYJ KwYBBAGgMgFfMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNp Z24uY29tL3JlcG9zaXRvcnkvMA0GCSqGSIb3DQEBCwUAA4IBAQCxh3ekjKKy RrUdfI6D1U7qUggdFLksiU+KiIqJzJG6GXcQ2KiBy2tF3+KYb0IixXMpIVli VXlcD5Vh4tiMxJ4WONMFt3f7/53gSXLf24WMwErubc+mGMzgUGE5HKC98PcK UV/5pPggQdzPxCBNeiXnLU1tCGYhPatFTDhUBGaVhBeuUCbgR9gpXJ9guqrD OVwouKvovdIeI5KEAcoAAiSL6naeLk/GbKUaBFa2RxXC17e+YyBWtWlWDEM3 1V8pUIx76lkO8IJYREhLcg/LnyoYy5wcrzI6pbX2vw1x/jR3GHSC1AEdoqbE xui2XLLlSa6y9yQNgdkPz7GTLmpwIT+dMIIF8TCCBNmgAwIBAgIMGk4Oe/1h 2+wMOby/MA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQK ExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQDEypHbG9iYWxTaWduIFBlcnNv bmFsU2lnbiAxIENBIC0gU0hBMjU2IC0gRzMwHhcNMTcwNTI1MDg0NDE2WhcN MjAwNTI1MDg0NDE2WjA8MRkwFwYDVQQDDBBzYXBlckBzYXBlci5pbmZvMR8w HQYJKoZIhvcNAQkBFhBzYXBlckBzYXBlci5pbmZvMIICIjANBgkqhkiG9w0B AQEFAAOCAg8AMIICCgKCAgEA2sO3aQNus/oe4ZBZ4fu1Y1mzxnUYAkb4k/dw gMFc2Kd0eRoOY0AHj4rTEi/vVzzizxjLbEwXzQ9cBEAu/PqS8WsOmhZXtlfi szPDmP7ZpOwmNTWKSd9O7jHu9uTCGfEOsocQNYH2ULD1gVFkgKb8jHf+3u9d uCzh6qMomTtwLrCGEP70Lq385xUzRaD6qbOeIB99tpzgvMR6Z0GPTt4z8tLM kfdtohq5llwZ5vYnj/hJohVS9iLMQMHW4nuLj/mLZNaYE1CWJBT1rBwn5YPJ uR6811O9eAP7aX4iG8k1jkiBh+QNgGRBIK4GIdqy7IVRhA7v2OlpLYHMk4zP 9Fs3M+56QromVKBnxfzLhuYMUK6ugj9jwskNVitqlEFUeyfgvmR1jnPRp1Nd XGJllTNwGicR8wkaRj14RxfrvTZfwXs8OBODKFupqun/tNzdpOgyHMGQACss 9yv2SnLGCJvJK3rGIdRZEiUhLZH/Ct4L92dBhev+SjUqWKbHb4yIlGMgLdoh nwqatuWw7iyOeInjcinX7ghiIKDWhulUN493Fzl6kaUBtIIcrb7jzZ2pHAQT WUmuVnCTHk6NtoWB09lvuK77fw4GfxLWDFWkBQiJYPVBrmxlrkCKzrWdTMfS W9BiEC10jT1sSimUBIjDz22RkfsApeBJoAIWjiOZogILu9MCAwEAAaOCAdAw ggHMMA4GA1UdDwEB/wQEAwIFoDCBngYIKwYBBQUHAQEEgZEwgY4wTQYIKwYB BQUHMAKGQWh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dz cGVyc29uYWxzaWduMXNoYTJnM29jc3AuY3J0MD0GCCsGAQUFBzABhjFodHRw Oi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24xc2hhMmcz MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBz Oi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMAkGA1UdEwQCMAAw RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9n c3BlcnNvbmFsc2lnbjFzaGEyZzMuY3JsMBsGA1UdEQQUMBKBEHNhcGVyQHNh cGVyLmluZm8wHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1Ud DgQWBBReBINaGUKUo7HCrIjsKLKERu6ooTAfBgNVHSMEGDAWgBSWJ8LCpfcc +AJ6emSvY28y0pjCsTANBgkqhkiG9w0BAQsFAAOCAQEAC0VK968ySq/6B+Kd ecjVThQOKtVXuG17Krfk0xz7OPYR/V+qZtBFm2Uc6tkUEmAmq3Tyf+SE3TTX Q58eJFq0uCTUhIY714ioJs1uVWBz8rPyJ3swkOfDaUXUxkQsBsf73VfKjUk4 kB5MTrApLYUe35NmEY3FqyyX13elhW1tp864vOKM2Git61cYoRn/bwd/z2JM Zkxwkd5JgvmM+p4Da+WO4CUsGzdrZEH8X/8NQIzWtUDIh7VEQZFX5fot/KvH Am8AajtpmNqTfMyg6LfcfJUXSFqXn/KEWu4Td62vX6Pd70dYKUZxnLwYvGqG A4Ktrp9zyrUzxLbmdaPln7CstjGCA38wggN7AgEBMG0wXTELMAkGA1UEBhMC QkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2Jh bFNpZ24gUGVyc29uYWxTaWduIDEgQ0EgLSBTSEEyNTYgLSBHMwIMGk4Oe/1h 2+wMOby/MA0GCWCGSAFlAwQCAQUAoIHkMBgGCSqGSIb3DQEJAzELBgkqhkiG 9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE4MTAyMzE3NTg0OFowLwYJKoZIhvcN AQkEMSIEIDPC7HZOyoWQZ848f54wqnXn57AWI7jfab4FdNR4j0+tMHkGCSqG SIb3DQEJDzFsMGowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjALBglghkgB ZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIIC AIwD5TFHEQvCKaBIMpcrwegON1ujEPxoIYkStFByiqPB1SbeEcyE+VsuFCcm W5fZadNeNbb+hbW5IZ76J/wTdYU+rVzF1wYmZEEqrqyWwAnwF4OrnfSIJ+a1 +SdaBMxu+i7oDT/GaZ17+Y0qjd10Wo5pp1/6hjuhL9cgKZOK8Ev/5ahvXq+B USeWZebQFI2yRPl/4PmlBNQlSUdiUxPLhe6hC+ZFABCEaurHcQ5sNV5/wvhh uJtuE+cEcBo1Lq39NRCMWYLPdIWg7br3oG5dNxZ1XFdD7L5BTwtYxfUvgs5B /sZXMvngr+V6zCPglODUbGxiK7Gr/7I6ktbFu/QFVcxE5aSyEb3iOy3KPe1H 43QTLgfebHL8ysG4+a769zX+ycgnMTEhsmv5wec2zmijF5qsZBZK9if4dOJx qFAjOqXPJrr7ERCkwnfTGlddJNSZkjLHCqFThznGewPPObJ15teM2CvV2+tH WD38eMud6UOjXFK4ntvsPjHxEmSR7FvPa0lRmsvxZtkfgSYIxpIebojV+wV4 TtPBuMoUxLJwpXhvJViyxFeYYoO7TnVnOkQs116ZpWHrVdFM2urLReAeY41/ P1LJiCFO0yL4qVjlkduu4Lxk9haHIUQG0TWGd2oJFEwdWdYu36a29YAY/oX2 jDLqZS8wjOeNc/OD488QRJBs --1563967779-1725412313-1540317529=:5494-- From owner-freebsd-current@freebsd.org Tue Oct 23 18:13:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11DDEFEEE69; Tue, 23 Oct 2018 18:13:09 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7225889976; Tue, 23 Oct 2018 18:13:08 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9NID0pp022434; Tue, 23 Oct 2018 11:13:00 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9NID0ck022433; Tue, 23 Oct 2018 11:13:00 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810231813.w9NID0ck022433@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: To: Stefan Esser Date: Tue, 23 Oct 2018 11:13:00 -0700 (PDT) CC: "Montgomery-Smith, Stephen" , "Julian H. Stacey" , "ctm-users@freebsd.org" , Poul-Henning Kamp , FreeBSD Current , Ed Maste , Warner Losh X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 23 Oct 2018 18:13:09 -0000 > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > I have no problem turning ctm into a port. But I would appreciate > > advice on whether there is a standard or easy process for converting > > software from the FreeBSD base to a port. If not, I can muddle my way > > through it. But give me some time (a few months) to get it done, > > because the rest of my life is making heavy demands on me right now. > > Hi Stephen, > > I could spend a few hours to perform the conversion to a port and to > test it. I've a happy CTM user, many years ago, and I can understand > that it still may be useful in special situations. > > The source archive will need to be hosted somewhere. Do you have a > preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? Doesnt the project have a place for doing this already? Any commiters ~username/ would work, but is probably not optimal. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Oct 23 18:18:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A804FF018F; Tue, 23 Oct 2018 18:18:13 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8B3689C7D; Tue, 23 Oct 2018 18:18:12 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd22.aul.t-online.de (fwd22.aul.t-online.de [172.20.26.127]) by mailout02.t-online.de (Postfix) with SMTP id 28FF141A8883; Tue, 23 Oct 2018 20:18:05 +0200 (CEST) Received: from Stefans-MBP-LAN.fritz.box (rfdqqaZbwh-0CglrTVwDr8D9GsE9zaMsNUy6lQ98Jj4HXxQHSE9OxPyNacPcLaRgLu@[80.128.111.25]) by fwd22.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1gF1Fi-3FkfkO0; Tue, 23 Oct 2018 20:18:02 +0200 Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: Warner Losh Cc: "Montgomery-Smith, Stephen" , "Julian H. Stacey" , "Rodney W. Grimes" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Message-ID: Date: Tue, 23 Oct 2018 20:18:01 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 8bit X-ID: rfdqqaZbwh-0CglrTVwDr8D9GsE9zaMsNUy6lQ98Jj4HXxQHSE9OxPyNacPcLaRgLu X-TOI-MSGID: 4d488592-f23e-411b-b1e6-0e92627d3e95 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, 23 Oct 2018 18:18:13 -0000 Am 23.10.18 um 19:06 schrieb Warner Losh: > > > On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser > wrote: > > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > I have no problem turning ctm into a port. But I would appreciate > > advice on whether there is a standard or easy process for converting > > software from the FreeBSD base to a port. If not, I can muddle my way > > through it. But give me some time (a few months) to get it done, > > because the rest of my life is making heavy demands on me right now. > > Hi Stephen, > > I could spend a few hours to perform the conversion to a port and to > test it. I've a happy CTM user, many years ago, and I can understand > that it still may be useful in special situations. > > The source archive will need to be hosted somewhere. Do you have a > preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? > > > It's trivial to setup a new repository on github.com/freebsd/ctm > for this purpose. With the right magic, we > could even retain the commit history. I have a complete port (in the sense that it builds, installs, packages), but there are a few details, that should be fixed on that occasion: 1) The man-pages install in man1 for binaries in sbin (--> change to man8) 2) The Makefiles use LIBADD (--> change to use LDADD) 3) The README file contains a reference to CVSUP (--> clean up) I do not have write access to freebsd on Github, and I'd appreciate if it was possible to move the files from src/usr.sbin/ctm there (with history would of course be preferable, but I'm not sure that it is of much use). I could then push my local changes (required to make the port build) to the Github repo (or add a few small patch files to the port). The port Makefile that I have prepared is attached below for reference. Regards, STefan --------------------------------------------------------------------- # $FreeBSD$ PORTNAME= ctm PORTVERSION= 2.0 CATEGORIES= ports-mgmt MAINTAINER= se@FreeBSD.org COMMENT= Create, receive, and apply FreeBSD source updates per mail LICENSE= Beerware LICENSE_NAME= Beerware LICENSE_TEXT= "THE BEER-WARE LICENSE" (Revision 42): \ wrote this file. As long as you retain this notice you \ can do whatever you want with this stuff. If we meet some day, and you think \ this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp LICENSE_PERMS= dist-mirror dist-sell pkg-mirror pkg-sell auto-accept USES= tar:txz #USE_GITHUB= yes #GH_ACCOUNT= freebsd do-install: .for f in ctm ctm_dequeue ctm_rmail ctm_smail ${INSTALL_PROGRAM} ${WRKSRC}/${f}/${f} \ ${STAGEDIR}${PREFIX}/sbin .endfor .for f in ctm ctm_rmail ${INSTALL_MAN} ${WRKSRC}/${f}/${f}.1 \ ${STAGEDIR}${MAN1PREFIX}/man/man1 # should be man8 .endfor .for f in ctm_dequeue ctm_smail ${INSTALL_MAN} ${WRKSRC}/ctm_rmail/ctm_rmail.1 \ ${STAGEDIR}${MAN1PREFIX}/man/man1/${f}.1 # should be man8 .endfor .include From owner-freebsd-current@freebsd.org Tue Oct 23 17:20:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54F9CFED1F6; Tue, 23 Oct 2018 17:20:34 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from um-tip1-missouri-out.um.umsystem.edu (um-tip1-missouri-out.um.umsystem.edu [198.209.49.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "um-tip1.um.umsystem.edu", Issuer "InCommon RSA Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 535578650A; Tue, 23 Oct 2018 17:20:33 +0000 (UTC) (envelope-from stephen@missouri.edu) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2FcAABoV89b/x840cZjGgEBAQEBAgEBA?= =?us-ascii?q?QEHAgEBAQGBZYIFgWUymCCBaCWZDwELASyBS4J1AoUrITgWAQMBAQIBAQICAmk?= =?us-ascii?q?cDIQfLDI/AQV5EAIBCA4KLjIlAgQBDAEHAQEVgwiCAqh7iE8BB4FLi2IXggCBO?= =?us-ascii?q?AyBYX6EaIVwAopZiXCKBwkCkGwIFZAwkzCDFAICAgIJAhSBWiKBVXITgnMBAQE?= =?us-ascii?q?yixiFPoIXimYBgR4BAQ?= X-IPAS-Result: =?us-ascii?q?A2FcAABoV89b/x840cZjGgEBAQEBAgEBAQEHAgEBAQGBZYI?= =?us-ascii?q?FgWUymCCBaCWZDwELASyBS4J1AoUrITgWAQMBAQIBAQICAmkcDIQfLDI/AQV5E?= =?us-ascii?q?AIBCA4KLjIlAgQBDAEHAQEVgwiCAqh7iE8BB4FLi2IXggCBOAyBYX6EaIVwAop?= =?us-ascii?q?ZiXCKBwkCkGwIFZAwkzCDFAICAgIJAhSBWiKBVXITgnMBAQEyixiFPoIXimYBg?= =?us-ascii?q?R4BAQ?= Received: from ex2-t21.um.umsystem.edu ([198.209.56.31]) by um-tip1-exch-relay.um.umsystem.edu with ESMTP; 23 Oct 2018 12:19:08 -0500 Received: from EX2-N14.um.umsystem.edu (198.209.56.22) by EX2-T21.um.umsystem.edu (198.209.56.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1531.3; Tue, 23 Oct 2018 12:19:08 -0500 Received: from EX2-N14.um.umsystem.edu ([198.209.56.22]) by EX2-N14.um.umsystem.edu ([198.209.56.22]) with mapi id 15.01.1531.003; Tue, 23 Oct 2018 12:19:08 -0500 From: "Montgomery-Smith, Stephen" To: Stefan Esser , "Julian H. Stacey" , "Rodney W. Grimes" CC: "ctm-users@freebsd.org" , Poul-Henning Kamp , FreeBSD Current , Ed Maste , Warner Losh Subject: Re: ctm(1) deprecation in the FreeBSD base system? Thread-Topic: ctm(1) deprecation in the FreeBSD base system? Thread-Index: AQHUak6oFha2k0mYvU+8ASXkS/fskqUtSOmAgAAVnYCAAAmwgA== Date: Tue, 23 Oct 2018 17:19:08 +0000 Message-ID: <24540054-74b7-8b1e-3ab9-36882f2eb0a1@missouri.edu> References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 x-originating-ip: [128.206.49.160] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 23 Oct 2018 18:31:29 +0000 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, 23 Oct 2018 17:20:34 -0000 On 10/23/18 11:44 AM, Stefan Esser wrote: > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: >> I have no problem turning ctm into a port. But I would appreciate >> advice on whether there is a standard or easy process for converting >> software from the FreeBSD base to a port. If not, I can muddle my way >> through it. But give me some time (a few months) to get it done, >> because the rest of my life is making heavy demands on me right now. >=20 > Hi Stephen, >=20 > I could spend a few hours to perform the conversion to a port and to > test it. I've a happy CTM user, many years ago, and I can understand > that it still may be useful in special situations. >=20 > The source archive will need to be hosted somewhere. Do you have a > preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? That would be great. I have familiarity with github, using svn to checkout and commit. So=20 that may be the best choice. Don't forget to include the patches here: ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/svn-cur/ From owner-freebsd-current@freebsd.org Tue Oct 23 18:35:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76B30FF0D85 for ; Tue, 23 Oct 2018 18:35:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0ECD58ACD6 for ; Tue, 23 Oct 2018 18:35:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe31.google.com with SMTP id y195so1519986vsc.7 for ; Tue, 23 Oct 2018 11:35:07 -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=dn8eMI5FIsNIyQMUrtXC5mROUJVie0ao+0bQGtivqng=; b=zJVw7FwssO1Rkky1ZCk/WVtNmKd+AU85omhq4PAFhANh7/9FsWtX7oS8oX/jdxiERc mfoZCIAWXPDd9Er6k501333+dNyLATKD858QsTZik59ZQ7LZP6CtIzUHmNn0QiwmajO7 I+yCLbky5MXK/ai9mNEduYwCVctnWJ/b50pQFHV0xoPqbft/QLSQ5XeRsyQ5njhW0dwg HR6mawwFptIFUw6nbC35Kc1S20mX51X/r0tDY9Pz6mHJJNqRLYHistUxvVSLgBb7UKJr bbczz/7/Cwptygi1Gkz/LyteKrWHjE9HB7NicZJzwQeFKd+rZWVd3xoHBUt4/K9sfzuq dGNQ== 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=dn8eMI5FIsNIyQMUrtXC5mROUJVie0ao+0bQGtivqng=; b=VQm/soan7//1ksm9rUy2a7qMnf8XKWUO6cE/6XOjn2CavRAH6GFOfAU1Hun5n94ed3 ToZc4sxwXf81gJ/w44gGXqKhd1vJTSyksNQcmTndy0r/KiK1N6KWO5yJ/qJQnUjmTCTc dTW+C1PIM9fXv08wjhCnUctCrU8cD70oa6Rg9Z2fkvOboGjojcyvbynJpR92IyVZb53y yvpmcFUrKQwy4zMp43gjfH9tTmYYbgwisGNvjOnCG87vyJBYPLfFd/txRtPLMGwjjPiw G8q3bKfraJmqclt09X3NRAQgwjyEhzOTB/BpKHd3lY6kPeHORi4ATdNydO2n4y7P7Gg5 inBQ== X-Gm-Message-State: ABuFfoiq+egomCcMlSKPYAaXSvVxZiYTrO7ZuoTn/TMbtOdJhb+Qe4dR eAobUbkRDuhOxBh0nKQti3x6hpVpmLpoNhDa3iGiIA== X-Google-Smtp-Source: ACcGV63/bV6kACPjJT4/p3IJCqp4EHi6+tOXBiT9og7KGJ+qf4R0iue8QB1jCHPVn6K3W3oatEALt85B50JqJ4yUlLU= X-Received: by 2002:a67:2704:: with SMTP id n4mr22037192vsn.209.1540319706426; Tue, 23 Oct 2018 11:35:06 -0700 (PDT) MIME-Version: 1.0 References: <201810222132.w9MLVvxC050976@fire.js.berklix.net> In-Reply-To: From: Warner Losh Date: Tue, 23 Oct 2018 12:34:53 -0600 Message-ID: Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: Stefan Esser Cc: "Montgomery-Smith, Stephen" , "Julian H. Stacey" , "Rodney W. Grimes" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste 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, 23 Oct 2018 18:35:07 -0000 On Tue, Oct 23, 2018, 12:18 PM Stefan Esser wrote: > Am 23.10.18 um 19:06 schrieb Warner Losh: > > > > > > On Tue, Oct 23, 2018 at 10:44 AM Stefan Esser > > wrote: > > > > Am 23.10.18 um 17:27 schrieb Montgomery-Smith, Stephen: > > > I have no problem turning ctm into a port. But I would appreciate > > > advice on whether there is a standard or easy process for > converting > > > software from the FreeBSD base to a port. If not, I can muddle my > way > > > through it. But give me some time (a few months) to get it done, > > > because the rest of my life is making heavy demands on me right > now. > > > > Hi Stephen, > > > > I could spend a few hours to perform the conversion to a port and to > > test it. I've a happy CTM user, many years ago, and I can understand > > that it still may be useful in special situations. > > > > The source archive will need to be hosted somewhere. Do you have a > > preference (e.g., on a FreeBSD server, or on Github, Gitlab, ...)? > > > > > > It's trivial to setup a new repository on github.com/freebsd/ctm > > for this purpose. With the right magic, > we > > could even retain the commit history. > > > I have a complete port (in the sense that it builds, installs, packages), > but there are a few details, that should be fixed on that occasion: > > 1) The man-pages install in man1 for binaries in sbin (--> change to man8) > 2) The Makefiles use LIBADD (--> change to use LDADD) > 3) The README file contains a reference to CVSUP (--> clean up) > > I do not have write access to freebsd on Github, and I'd appreciate if it > was possible to move the files from src/usr.sbin/ctm there (with history > would of course be preferable, but I'm not sure that it is of much use). > I can do this. We have many ports that are managed via github. What is your github id? Warner I could then push my local changes (required to make the port build) to > the Github repo (or add a few small patch files to the port). > > The port Makefile that I have prepared is attached below for reference. > > Regards, STefan > > --------------------------------------------------------------------- > # $FreeBSD$ > > > > > PORTNAME= ctm > PORTVERSION= 2.0 > CATEGORIES= ports-mgmt > > MAINTAINER= se@FreeBSD.org > COMMENT= Create, receive, and apply FreeBSD source updates per mail > > LICENSE= Beerware > LICENSE_NAME= Beerware > LICENSE_TEXT= "THE BEER-WARE LICENSE" (Revision 42): \ > wrote this file. As long as you retain > this > notice you \ > can do whatever you want with this stuff. If we meet some > day, > and you think \ > this stuff is worth it, you can buy me a beer in return. > Poul-Henning Kamp > LICENSE_PERMS= dist-mirror dist-sell pkg-mirror pkg-sell auto-accept > > USES= tar:txz > > #USE_GITHUB= yes > > > > #GH_ACCOUNT= freebsd > > > > > do-install: > .for f in ctm ctm_dequeue ctm_rmail ctm_smail > ${INSTALL_PROGRAM} ${WRKSRC}/${f}/${f} \ > ${STAGEDIR}${PREFIX}/sbin > .endfor > .for f in ctm ctm_rmail > ${INSTALL_MAN} ${WRKSRC}/${f}/${f}.1 \ > ${STAGEDIR}${MAN1PREFIX}/man/man1 # should be man8 > > > > .endfor > .for f in ctm_dequeue ctm_smail > ${INSTALL_MAN} ${WRKSRC}/ctm_rmail/ctm_rmail.1 \ > ${STAGEDIR}${MAN1PREFIX}/man/man1/${f}.1 # should > be > man8 > > > .endfor > > .include > From owner-freebsd-current@freebsd.org Tue Oct 23 17:45:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3312FEDABB for ; Tue, 23 Oct 2018 17:45:11 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7632C87210 for ; Tue, 23 Oct 2018 17:45:11 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc2f.google.com with SMTP id j75-v6so899166ywj.10 for ; Tue, 23 Oct 2018 10:45:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=0Z9CXi0rdG56GqE0kiwDyLg64vBEWtYTxnUD4rRahGI=; b=MFwlxGMJcIA/Em4znthOnep8JWQaDkZ1hy+CIuslJb8qt/0f99/Bt01w4bbzqM05KR aKuU/tS/Hzf3h+Ib+Q13fNygw43bwO7hKNN1Fq78ip89LWHRRSxyPIkQnI+5dCOgfW6H 3kl6Ex3oujBROJbW9gpHdLKcz55UL8Gb+rz91Ky9QUDPsNKyk7BvGf0DhS99Ijzt83y2 3htMMxGysUeIB6eLjOjLtRGm3FIInfm+LacJ1QT7R1R0s2t7jEnKrWqOYVeZHGa84z5a An7F45mnAOTUhDm4A60Urq4gHD2KhAfheoOSPS2IgUHv8frNJv5ve8Qro3k9tLbxOPsq CUQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=0Z9CXi0rdG56GqE0kiwDyLg64vBEWtYTxnUD4rRahGI=; b=TVC2VWXDnC/UQNIGcSTZYUuh8cMd8xmLOr4bxj8xAo2vWwGJsGhPojHqmR/OY081M3 SS8RZ1FDOBAXL1FRB8qZwBKBg0aQtWP7Vw6gowepc5kfNICTlp4wzPyKrlUoHYtGK67t JvWLUZOLnAGFGk7fGA1VJFb9gr6i1PuI4Kms38Wh2xPQCeIgbDerocacpn4Eov3mYl8i 3kIYDo2mGT6a3KlRD5NXgKKgoVEkSl7PWK9BrXFOuM8+V9W5v8OmPsSeijgNTBuPWRnW /JBGLRZgvhv3QWrLn1nHPQ3l3fzQCpvoXAT1SL8zNELG5pUc8mLbuhpju7TnwanV+5Pd vhzw== X-Gm-Message-State: ABuFfohvAn/lOZCLBZk6/MKKwFCmuraNVSn5FkPfOwF+tAkUiZW4NDPO B55YX27B/WNjIktbK1ZAjypAwGogYwN+evZD9sfU/b+MAb4= X-Google-Smtp-Source: ACcGV60ILNd2hFgE2lwrbwF33TsBfH2Ym66dN8Auj3xedKVwxjl7JY0O3l9LReliuMebCL/lntV14/KRnbvzXb1g8iI= X-Received: by 2002:a81:b710:: with SMTP id v16-v6mr6382608ywh.177.1540316710317; Tue, 23 Oct 2018 10:45:10 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 10:45:09 -0700 (PDT) From: Harry Newton Date: Tue, 23 Oct 2018 18:45:09 +0100 X-Google-Sender-Auth: VcG25OmnF6BUP96nIIScCMEf3U8 Message-ID: Subject: UEFI boot hangs after loader To: freebsd-current@freebsd.org X-Mailman-Approved-At: Tue, 23 Oct 2018 19:39:23 +0000 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, 23 Oct 2018 17:45:12 -0000 Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 r339529 by source. Have a problem with booting which hangs after: >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Probing 5 block devices ... done ZFS found the following pools: zroot UFS found no partitions Consoles: EFI console FreeBSD/amd64 EFI loader, Revision 1.1 Command line arguments: loader.efi EFI version 2.31 EFI Firmware: American Megatrends (rev 4.654) Console: efi(0) Load Path: HD(4, GPT [ ... ] Load Device: Pci Root [ ... ] Boot Current: 0001 Boot Order: 0001 [x] Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI - So it gets into loader.efi which runs but stops I think just before loading the kernel. Partitions: => 40 250069600 ada0 GPT (119G) 40 1600 1 efi (800K) 1640 1024 2 freebsd-boot (512K) 2664 1432 - free - (716K) 4096 4194304 3 freebsd-swap (2.0G) 4198400 245870592 4 freebsd-zfs (117G) 250068992 648 - free - (324K) and the EFI partition is FAT 12. I can't provide (at the moment) any output from efibootmgr: root@gryphon:~ # efibootmgr -v efibootmgr: efi variables not supported on this system. root? kldload efirt? root@gryphon:~ # kldload efirt kldload: can't load efirt: module already loaded or in kernel which I don't understand. I'm going to rebuild the kernel (currently GENERIC) and see if that allows me to load efirt / use efibootmgr. In the meantime, I should be very grateful for any advice. ( Currently booting using a 11-RELEASE memstick image and dropping into its loader to get to the installed 12-STABLE ). /Harry From owner-freebsd-current@freebsd.org Tue Oct 23 19:49:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 921F8FF9FFF; Tue, 23 Oct 2018 19:49:28 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C41B8D225; Tue, 23 Oct 2018 19:49:27 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CCDC.dip0.t-ipconnect.de [46.82.204.220]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w9NJnGP4031827 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Oct 2018 19:49:21 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w9NJnBD1036074; Tue, 23 Oct 2018 21:49:11 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w9NJmYlC078288; Tue, 23 Oct 2018 21:48:46 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201810231948.w9NJmYlC078288@fire.js.berklix.net> To: Warner Losh cc: Stefan Esser , "Montgomery-Smith, Stephen" , "Rodney W. Grimes" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste Subject: Re: ctm(1) deprecation in the FreeBSD base system? From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Tue, 23 Oct 2018 12:34:53 -0600." Date: Tue, 23 Oct 2018 21:48:34 +0200 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, 23 Oct 2018 19:49:28 -0000 A cost(=time)/benefit look on moving ctm from src/ to ports/ : - No tangible architecture benefit (its not like purging an old driver to makes kernel support simpler, or avoiding clashing libs etc) - FreeBSD would shrink 0.028 % of the size of src/ cd /pub/FreeBSD/branches/-current/src du -s -k . # 1223922 du -s -k `find . -type d -name \*ctm\*` 196 ./usr.sbin/ctm 74 ./usr.sbin/ctm/ctm 12 ./usr.sbin/ctm/ctm_dequeue 44 ./usr.sbin/ctm/ctm_rmail 18 ./usr.sbin/ctm/ctm_smail dc 196 74 12 44 18 + + + + p 344 dc 344000000000 1223922 / p 281063 # then move 9 points xcalc 344 / 1223922 # 0.0002810636 Those who would do the work might want to ponder if 0.028 % is best use of their time, or if more fun & benefit to work on some other part of FreeBSD ? Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.uk https://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative From owner-freebsd-current@freebsd.org Tue Oct 23 19:56:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E4F9FFA499 for ; Tue, 23 Oct 2018 19:56:24 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-hyfv10021501.me.com (pv50p00im-hyfv10021501.me.com [17.58.6.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C17098D949 for ; Tue, 23 Oct 2018 19:56:23 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv50p00im-hyfv10021501.me.com by pv50p00im-hyfv10021501.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH200D00HWHKJ00@pv50p00im-hyfv10021501.me.com> for freebsd-current@freebsd.org; Tue, 23 Oct 2018 19:56:15 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv50p00im-hyfv10021501.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH200PKTI1N9C10@pv50p00im-hyfv10021501.me.com>; Tue, 23 Oct 2018 19:56:15 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 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-1807170000 definitions=main-1810230162 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_06:,, signatures=0 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader From: Toomas Soome In-reply-to: Date: Tue, 23 Oct 2018 22:56:09 +0300 Cc: FreeBSD Current Content-transfer-encoding: quoted-printable Message-id: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> References: To: Harry Newton X-Mailer: Apple Mail (2.3445.100.39) 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, 23 Oct 2018 19:56:24 -0000 Do you get boot menu? if so, press esc to get to ok prompt, then type = start - if its bootfort based loader, it will load the kernel and = modules. lsmod will then list the loaded files. If the loader prompt is still usable, then next command would be: boot rgds, toomas > On 23 Oct 2018, at 20:45, Harry Newton wrote: >=20 > Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 = r339529 > by source. Have a problem with booting which hangs after: >=20 >>> FreeBSD EFI boot block > Loader path: /boot/loader.efi >=20 > Initializing modules: ZFS UFS > Probing 5 block devices ... done > ZFS found the following pools: zroot > UFS found no partitions > Consoles: EFI console > FreeBSD/amd64 EFI loader, Revision 1.1 >=20 > Command line arguments: loader.efi > EFI version 2.31 > EFI Firmware: American Megatrends (rev 4.654) > Console: efi(0) > Load Path: HD(4, GPT [ ... ] > Load Device: Pci Root [ ... ] > Boot Current: 0001 > Boot Order: 0001 [x] > Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > - >=20 > So it gets into loader.efi which runs but stops I think just before = loading > the kernel. Partitions: >=20 > =3D> 40 250069600 ada0 GPT (119G) > 40 1600 1 efi (800K) > 1640 1024 2 freebsd-boot (512K) > 2664 1432 - free - (716K) > 4096 4194304 3 freebsd-swap (2.0G) > 4198400 245870592 4 freebsd-zfs (117G) > 250068992 648 - free - (324K) >=20 > and the EFI partition is FAT 12. >=20 > I can't provide (at the moment) any output from efibootmgr: >=20 > root@gryphon:~ # efibootmgr -v > efibootmgr: efi variables not supported on this system. root? kldload = efirt? > root@gryphon:~ # kldload efirt > kldload: can't load efirt: module already loaded or in kernel >=20 > which I don't understand. >=20 > I'm going to rebuild the kernel (currently GENERIC) and see if that = allows > me to load efirt / use efibootmgr. >=20 > In the meantime, I should be very grateful for any advice. >=20 > ( Currently booting using a 11-RELEASE memstick image and dropping = into its > loader to get to the installed 12-STABLE ). >=20 > /Harry > _______________________________________________ > 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 Oct 23 20:01:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DB2DFFA6F8 for ; Tue, 23 Oct 2018 20:01:41 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E4528DBFF for ; Tue, 23 Oct 2018 20:01:41 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc30.google.com with SMTP id v1-v6so1083985ywv.6 for ; Tue, 23 Oct 2018 13:01:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=E2EfpoH/sgTAtEkvX5lsrSfelW7PAFBFW3BivlpzWAE=; b=wgPFq0giDWQJyClfrTmvYEKXR6XEZ+OoPzwC5tpfkAXUxAdnV8rtStTYuT1cJxDEVp 3dfntJs0wRgpEc/jgFp4s16Cpb4iLrHlPmMkrV5bzQbBAqbhF4WRY11LEER+h67ORlNL z90Xppa6EK+vBZ0bUEUzAHvrHzfflbHHwi07qpIvUh8FpiPAkO1pnsXSha8MihUzkiLj jJY/Bta1lco6+zgZBLxEeuGF/9GiAZcFq/Ei54v8QDlJ9Vg6sKipIKNlCgAGIlBJ+ZN0 EYWPTmbgVLf5Crmh7Im0wfCU48nRFXIRuLhd+OiZ4Egb6yOrzOJRZd7unjSWNFEFJiiB NM3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=E2EfpoH/sgTAtEkvX5lsrSfelW7PAFBFW3BivlpzWAE=; b=eAcHaXccsDYS4d/LrPhzFRpukhSvp8vE1gpCcGY7FSleT4LvyqGB32avI1RtBzUVQK rdHs9wc9SJjlAiPujEZ40x1/b+Lq5b9ATyVewDkL7G7AOWVcDcph2xG27DX3r8TBgoU0 c/YtZa8ST0cVY24n0bMJ2M+bEe5gXcsf88xC3oSGRVtNuUPSmIC+Du5KXkR0YA4SqgF5 ct+kQDjmgsP8z8VB7H/mRK14BZ8FnKlgtP3wIvVk6AvHI3rygZ94RU4Ak2grSFAoWOIM DhHU3WD9ndXkAQAC9Jj3YkquoS4g9UcBBBJvjGZiDnMvyBKSYsk6sWwkfJAMcY/oAu3R CnXg== X-Gm-Message-State: ABuFfoica9VE/Jz6+ZFjFNIgmO6AAMstCeDPcJb4HEMLGZnz58c1fb+t 3Oe4rnC33JUNvwFRzdhnThMZe0sMRAUsaFO+9WpLDzhg X-Google-Smtp-Source: ACcGV61jlAq30UpKPv8Qr3pJPcx0Wl+VM086a6xFiL7iKN5PEccCbk7gXwOHNJdoSHOkMYRY4Zs1dhYxpkXb9B+BBhQ= X-Received: by 2002:a0d:d705:: with SMTP id z5-v6mr8037144ywd.22.1540324900427; Tue, 23 Oct 2018 13:01:40 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 13:01:39 -0700 (PDT) In-Reply-To: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 21:01:39 +0100 X-Google-Sender-Auth: 91HZyH7LWxepw0MPV-QuINCwoSE Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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: Tue, 23 Oct 2018 20:01:41 -0000 If boot menu is the screen where you get the options for various kernels and the picture of the daemon head, no. It stops at the point in my email =E2=80=94 though not as I said just before the kernel is loaded but in poin= t of fact before the menu. I've also rebuilt the kernel and still can't use efibootmgr which is puzzling me. /H On 23 October 2018 at 20:56, Toomas Soome wrote: > Do you get boot menu? if so, press esc to get to ok prompt, then type > start - if its bootfort based loader, it will load the kernel and modules= . > lsmod will then list the loaded files. > > If the loader prompt is still usable, then next command would be: boot > > rgds, > toomas > > > On 23 Oct 2018, at 20:45, Harry Newton wrote: > > > > Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 r3395= 29 > > by source. Have a problem with booting which hangs after: > > > >>> FreeBSD EFI boot block > > Loader path: /boot/loader.efi > > > > Initializing modules: ZFS UFS > > Probing 5 block devices ... done > > ZFS found the following pools: zroot > > UFS found no partitions > > Consoles: EFI console > > FreeBSD/amd64 EFI loader, Revision 1.1 > > > > Command line arguments: loader.efi > > EFI version 2.31 > > EFI Firmware: American Megatrends (rev 4.654) > > Console: efi(0) > > Load Path: HD(4, GPT [ ... ] > > Load Device: Pci Root [ ... ] > > Boot Current: 0001 > > Boot Order: 0001 [x] > > Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > > - > > > > So it gets into loader.efi which runs but stops I think just before > loading > > the kernel. Partitions: > > > > =3D> 40 250069600 ada0 GPT (119G) > > 40 1600 1 efi (800K) > > 1640 1024 2 freebsd-boot (512K) > > 2664 1432 - free - (716K) > > 4096 4194304 3 freebsd-swap (2.0G) > > 4198400 245870592 4 freebsd-zfs (117G) > > 250068992 648 - free - (324K) > > > > and the EFI partition is FAT 12. > > > > I can't provide (at the moment) any output from efibootmgr: > > > > root@gryphon:~ # efibootmgr -v > > efibootmgr: efi variables not supported on this system. root? kldload > efirt? > > root@gryphon:~ # kldload efirt > > kldload: can't load efirt: module already loaded or in kernel > > > > which I don't understand. > > > > I'm going to rebuild the kernel (currently GENERIC) and see if that > allows > > me to load efirt / use efibootmgr. > > > > In the meantime, I should be very grateful for any advice. > > > > ( Currently booting using a 11-RELEASE memstick image and dropping into > its > > loader to get to the installed 12-STABLE ). > > > > /Harry > > _______________________________________________ > > 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" > > --=20 Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:04:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EBC8FFA91B for ; Tue, 23 Oct 2018 20:04:22 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp003.me.com (pv33p00im-asmtp003.me.com [17.142.194.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DB958DEDF for ; Tue, 23 Oct 2018 20:04:22 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp003.me.com by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH200700I9ONG00@pv33p00im-asmtp003.me.com> for freebsd-current@freebsd.org; Tue, 23 Oct 2018 20:03:39 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH200BNIIDXHZ10@pv33p00im-asmtp003.me.com>; Tue, 23 Oct 2018 20:03:36 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 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-1807170000 definitions=main-1810230163 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_06:,, signatures=0 From: Toomas Soome Message-id: <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader Date: Tue, 23 Oct 2018 23:03:32 +0300 In-reply-to: Cc: FreeBSD Current To: Harry Newton References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> X-Mailer: Apple Mail (2.3445.100.39) 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: Tue, 23 Oct 2018 20:04:22 -0000 hm. in that case, whats the content of /boot/loader.rc ? rgds, toomas > On 23 Oct 2018, at 23:01, Harry Newton wrote: >=20 > If boot menu is the screen where you get the options for various = kernels and the picture of the daemon head, no. It stops at the point = in my email =E2=80=94 though not as I said just before the kernel is = loaded but in point of fact before the menu. >=20 > I've also rebuilt the kernel and still can't use efibootmgr which is = puzzling me. >=20 > /H >=20 >=20 > On 23 October 2018 at 20:56, Toomas Soome > wrote: > Do you get boot menu? if so, press esc to get to ok prompt, then type = start - if its bootfort based loader, it will load the kernel and = modules. lsmod will then list the loaded files. >=20 > If the loader prompt is still usable, then next command would be: boot >=20 > rgds, > toomas >=20 > > On 23 Oct 2018, at 20:45, Harry Newton > wrote: > >=20 > > Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 = r339529 > > by source. Have a problem with booting which hangs after: > >=20 > >>> FreeBSD EFI boot block > > Loader path: /boot/loader.efi > >=20 > > Initializing modules: ZFS UFS > > Probing 5 block devices ... done > > ZFS found the following pools: zroot > > UFS found no partitions > > Consoles: EFI console > > FreeBSD/amd64 EFI loader, Revision 1.1 > >=20 > > Command line arguments: loader.efi > > EFI version 2.31 > > EFI Firmware: American Megatrends (rev 4.654) > > Console: efi(0) > > Load Path: HD(4, GPT [ ... ] > > Load Device: Pci Root [ ... ] > > Boot Current: 0001 > > Boot Order: 0001 [x] > > Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > > - > >=20 > > So it gets into loader.efi which runs but stops I think just before = loading > > the kernel. Partitions: > >=20 > > =3D> 40 250069600 ada0 GPT (119G) > > 40 1600 1 efi (800K) > > 1640 1024 2 freebsd-boot (512K) > > 2664 1432 - free - (716K) > > 4096 4194304 3 freebsd-swap (2.0G) > > 4198400 245870592 4 freebsd-zfs (117G) > > 250068992 648 - free - (324K) > >=20 > > and the EFI partition is FAT 12. > >=20 > > I can't provide (at the moment) any output from efibootmgr: > >=20 > > root@gryphon:~ # efibootmgr -v > > efibootmgr: efi variables not supported on this system. root? = kldload efirt? > > root@gryphon:~ # kldload efirt > > kldload: can't load efirt: module already loaded or in kernel > >=20 > > which I don't understand. > >=20 > > I'm going to rebuild the kernel (currently GENERIC) and see if that = allows > > me to load efirt / use efibootmgr. > >=20 > > In the meantime, I should be very grateful for any advice. > >=20 > > ( Currently booting using a 11-RELEASE memstick image and dropping = into its > > loader to get to the installed 12-STABLE ). > >=20 > > /Harry > > _______________________________________________ > > 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 = " >=20 >=20 >=20 >=20 > --=20 > Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:08:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CA78FFAAE1 for ; Tue, 23 Oct 2018 20:08:33 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24EB98E0AE for ; Tue, 23 Oct 2018 20:08:33 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yb1-xb30.google.com with SMTP id j9-v6so1119524ybj.6 for ; Tue, 23 Oct 2018 13:08:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=X1ZI3YRxcqOpwYNk0O7alceKPhLoPk8xFhuMAC91ltg=; b=o7OXQwpi+rBNh5sOg1OtyIKTs3r1huOt6Jrvw1gfhujZDSpwmlQJJ+WAIv7E1UOZ0Q YP/d6F2p5iRxEcwt39p2N4V/EYJGrR88Igx2auLT0iJSxHSQFaAvvS2hg2TogpOAyjMJ xGcNsTDRqiuG0Ve1YMcTa1B0Kx4xgIuupZU+U2P+0k4cIbK3PiIU9C4cwBks5wJPRDVX Cl0zCFN3PXLSpllzWfflh8bvbhvhIgyqfWmeKLN/acONtIDNod8u+PuLbC2VQmHdnBgW 0xBECco0b17AAlKOR8QOQB5Cw6RIe1MnWOr42bc94GrZ6dDORwrQPos66kQfyB8FySo8 vFKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=X1ZI3YRxcqOpwYNk0O7alceKPhLoPk8xFhuMAC91ltg=; b=hvqEqsPWKSDKr/GrV4kicA88Xhsc5iMPUjLXrinutx4/KdthpeXkdUE2EutvAVdUe8 tHZilDaKiGltlHb/Ehr3WgTuyN5a1xaGL7e4LSTI89/QqluBejH2JrcN9P8ojDl6Ugkv kUBfRIcHglYN5iwmpWOyIYX0iN15Q0mdrxT9CQvl6vm+qICdOy3GWpDd1iI9+Fmvd4oO oUyCGFIhhLx0fzccbXqeKVXPE40zimuev3pv1OlpPyqMRv98TdoK2Vd2R8AHtdJAzwH9 dtYDi/wYOsviEYXDeydNcdo5yvAktc++myzRpuV+UJ7O5hFijP1sTXqTMowUcjPFP0NH M/aw== X-Gm-Message-State: AGRZ1gLOUsVIw144VRgD0yVAPOfjDCbBGH0ocJ+e8ppyUKbLaY0ZgygF BoUmPuVXV7G4bsZWgGHu1sHwu8xI6k9UNo9eKBdpvA== X-Google-Smtp-Source: AJdET5cMv0Jda5wgEzLiy4+muFrT8bSEqOFoByF9YVFGZcA8SST058EAQAA43Dh2Tw0yMvQQ7jZePQo4kwE4Vf5wH4k= X-Received: by 2002:a25:5b87:: with SMTP id p129-v6mr3332471ybb.102.1540325312483; Tue, 23 Oct 2018 13:08:32 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 13:08:32 -0700 (PDT) In-Reply-To: <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 21:08:32 +0100 X-Google-Sender-Auth: Kmb6YAzN1q1xbEmMJkm3jhkhYk0 Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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: Tue, 23 Oct 2018 20:08:33 -0000 So it's got FORTH in it, but my loader is lua based, and also doesn't appear to read loader.rc. /H On 23 October 2018 at 21:03, Toomas Soome wrote: > hm. in that case, whats the content of /boot/loader.rc ? > > rgds, > toomas > > > On 23 Oct 2018, at 23:01, Harry Newton wrote: > > If boot menu is the screen where you get the options for various kernels > and the picture of the daemon head, no. It stops at the point in my emai= l > =E2=80=94 though not as I said just before the kernel is loaded but in po= int of > fact before the menu. > > I've also rebuilt the kernel and still can't use efibootmgr which is > puzzling me. > > /H > > > On 23 October 2018 at 20:56, Toomas Soome wrote: > >> Do you get boot menu? if so, press esc to get to ok prompt, then type >> start - if its bootfort based loader, it will load the kernel and module= s. >> lsmod will then list the loaded files. >> >> If the loader prompt is still usable, then next command would be: boot >> >> rgds, >> toomas >> >> > On 23 Oct 2018, at 20:45, Harry Newton wrote: >> > >> > Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 >> r339529 >> > by source. Have a problem with booting which hangs after: >> > >> >>> FreeBSD EFI boot block >> > Loader path: /boot/loader.efi >> > >> > Initializing modules: ZFS UFS >> > Probing 5 block devices ... done >> > ZFS found the following pools: zroot >> > UFS found no partitions >> > Consoles: EFI console >> > FreeBSD/amd64 EFI loader, Revision 1.1 >> > >> > Command line arguments: loader.efi >> > EFI version 2.31 >> > EFI Firmware: American Megatrends (rev 4.654) >> > Console: efi(0) >> > Load Path: HD(4, GPT [ ... ] >> > Load Device: Pci Root [ ... ] >> > Boot Current: 0001 >> > Boot Order: 0001 [x] >> > Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >> > - >> > >> > So it gets into loader.efi which runs but stops I think just before >> loading >> > the kernel. Partitions: >> > >> > =3D> 40 250069600 ada0 GPT (119G) >> > 40 1600 1 efi (800K) >> > 1640 1024 2 freebsd-boot (512K) >> > 2664 1432 - free - (716K) >> > 4096 4194304 3 freebsd-swap (2.0G) >> > 4198400 245870592 4 freebsd-zfs (117G) >> > 250068992 648 - free - (324K) >> > >> > and the EFI partition is FAT 12. >> > >> > I can't provide (at the moment) any output from efibootmgr: >> > >> > root@gryphon:~ # efibootmgr -v >> > efibootmgr: efi variables not supported on this system. root? kldload >> efirt? >> > root@gryphon:~ # kldload efirt >> > kldload: can't load efirt: module already loaded or in kernel >> > >> > which I don't understand. >> > >> > I'm going to rebuild the kernel (currently GENERIC) and see if that >> allows >> > me to load efirt / use efibootmgr. >> > >> > In the meantime, I should be very grateful for any advice. >> > >> > ( Currently booting using a 11-RELEASE memstick image and dropping int= o >> its >> > loader to get to the installed 12-STABLE ). >> > >> > /Harry >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> reebsd.org" >> >> > > > -- > Harry Newton > > > --=20 Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:13:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE75BFFB08C; Tue, 23 Oct 2018 20:13:29 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 21CA38E6AF; Tue, 23 Oct 2018 20:13:28 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9NKDO6q023343; Tue, 23 Oct 2018 13:13:24 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9NKDOQC023342; Tue, 23 Oct 2018 13:13:24 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810232013.w9NKDOQC023342@pdx.rh.CN85.dnsmgr.net> Subject: Re: ctm(1) deprecation in the FreeBSD base system? In-Reply-To: <201810231948.w9NJmYlC078288@fire.js.berklix.net> To: "Julian H. Stacey" Date: Tue, 23 Oct 2018 13:13:24 -0700 (PDT) CC: Warner Losh , Stefan Esser , "Montgomery-Smith, Stephen" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 23 Oct 2018 20:13:29 -0000 > A cost(=time)/benefit look on moving ctm from src/ to ports/ : > - No tangible architecture benefit (its not like purging an old driver > to makes kernel support simpler, or avoiding clashing libs etc) > - FreeBSD would shrink 0.028 % of the size of src/ > cd /pub/FreeBSD/branches/-current/src > du -s -k . # 1223922 > du -s -k `find . -type d -name \*ctm\*` > 196 ./usr.sbin/ctm > 74 ./usr.sbin/ctm/ctm > 12 ./usr.sbin/ctm/ctm_dequeue > 44 ./usr.sbin/ctm/ctm_rmail > 18 ./usr.sbin/ctm/ctm_smail > dc 196 74 12 44 18 + + + + p 344 > dc 344000000000 1223922 / p 281063 # then move 9 points > xcalc 344 / 1223922 # 0.0002810636 > > Those who would do the work might want to ponder if 0.028 % is best use of > their time, or if more fun & benefit to work on some other part of FreeBSD ? At the most/least we should not go very far, the only thing that needs done soon is a gonein(13) commited to head and MFC'ed to stable/12 by thursday. All the other details should wait until a depreication policy revision is completed that includes how to deal with this. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Oct 23 20:17:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FB6AFFB34A for ; Tue, 23 Oct 2018 20:17:27 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp001.me.com (pv33p00im-asmtp001.me.com [17.142.194.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B48468E8CF for ; Tue, 23 Oct 2018 20:17:26 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp001.me.com by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH200C00I9MUI00@pv33p00im-asmtp001.me.com> for freebsd-current@freebsd.org; Tue, 23 Oct 2018 20:17:13 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH200BBAJ0IWW20@pv33p00im-asmtp001.me.com>; Tue, 23 Oct 2018 20:17:09 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 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-1807170000 definitions=main-1810230166 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_06:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader From: Toomas Soome In-reply-to: Date: Tue, 23 Oct 2018 23:17:05 +0300 Cc: FreeBSD Current Content-transfer-encoding: quoted-printable Message-id: <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> To: Harry Newton X-Mailer: Apple Mail (2.3445.100.39) 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, 23 Oct 2018 20:17:27 -0000 ok, in that case I=E2=80=99d suggest to test out if forth based one is = still working - at least you can get the bootable system. And then there = is a chance to debug the lua version too (note it should be possible to = chain /boot/loader_lua.efi). rgds, toomas > On 23 Oct 2018, at 23:08, Harry Newton wrote: >=20 > So it's got FORTH in it, but my loader is lua based, and also doesn't > appear to read loader.rc. >=20 > /H >=20 > On 23 October 2018 at 21:03, Toomas Soome wrote: >=20 >> hm. in that case, whats the content of /boot/loader.rc ? >>=20 >> rgds, >> toomas >>=20 >>=20 >> On 23 Oct 2018, at 23:01, Harry Newton wrote: >>=20 >> If boot menu is the screen where you get the options for various = kernels >> and the picture of the daemon head, no. It stops at the point in my = email >> =E2=80=94 though not as I said just before the kernel is loaded but = in point of >> fact before the menu. >>=20 >> I've also rebuilt the kernel and still can't use efibootmgr which is >> puzzling me. >>=20 >> /H >>=20 >>=20 >> On 23 October 2018 at 20:56, Toomas Soome wrote: >>=20 >>> Do you get boot menu? if so, press esc to get to ok prompt, then = type >>> start - if its bootfort based loader, it will load the kernel and = modules. >>> lsmod will then list the loaded files. >>>=20 >>> If the loader prompt is still usable, then next command would be: = boot >>>=20 >>> rgds, >>> toomas >>>=20 >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: >>>>=20 >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 >>> r339529 >>>> by source. Have a problem with booting which hangs after: >>>>=20 >>>>>> FreeBSD EFI boot block >>>> Loader path: /boot/loader.efi >>>>=20 >>>> Initializing modules: ZFS UFS >>>> Probing 5 block devices ... done >>>> ZFS found the following pools: zroot >>>> UFS found no partitions >>>> Consoles: EFI console >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>>>=20 >>>> Command line arguments: loader.efi >>>> EFI version 2.31 >>>> EFI Firmware: American Megatrends (rev 4.654) >>>> Console: efi(0) >>>> Load Path: HD(4, GPT [ ... ] >>>> Load Device: Pci Root [ ... ] >>>> Boot Current: 0001 >>>> Boot Order: 0001 [x] >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >>>> - >>>>=20 >>>> So it gets into loader.efi which runs but stops I think just before >>> loading >>>> the kernel. Partitions: >>>>=20 >>>> =3D> 40 250069600 ada0 GPT (119G) >>>> 40 1600 1 efi (800K) >>>> 1640 1024 2 freebsd-boot (512K) >>>> 2664 1432 - free - (716K) >>>> 4096 4194304 3 freebsd-swap (2.0G) >>>> 4198400 245870592 4 freebsd-zfs (117G) >>>> 250068992 648 - free - (324K) >>>>=20 >>>> and the EFI partition is FAT 12. >>>>=20 >>>> I can't provide (at the moment) any output from efibootmgr: >>>>=20 >>>> root@gryphon:~ # efibootmgr -v >>>> efibootmgr: efi variables not supported on this system. root? = kldload >>> efirt? >>>> root@gryphon:~ # kldload efirt >>>> kldload: can't load efirt: module already loaded or in kernel >>>>=20 >>>> which I don't understand. >>>>=20 >>>> I'm going to rebuild the kernel (currently GENERIC) and see if that >>> allows >>>> me to load efirt / use efibootmgr. >>>>=20 >>>> In the meantime, I should be very grateful for any advice. >>>>=20 >>>> ( Currently booting using a 11-RELEASE memstick image and dropping = into >>> its >>>> loader to get to the installed 12-STABLE ). >>>>=20 >>>> /Harry >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>>=20 >>>=20 >>=20 >>=20 >> -- >> Harry Newton >>=20 >>=20 >>=20 >=20 >=20 > --=20 > Harry Newton > _______________________________________________ > 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 Oct 23 20:21:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91D24FFB63C for ; Tue, 23 Oct 2018 20:21:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B8038ECB9 for ; Tue, 23 Oct 2018 20:21:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x932.google.com with SMTP id c21so1020247uap.7 for ; Tue, 23 Oct 2018 13:21:59 -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=rgbDgsqLEzDX1FLEujh197ceWBfJWb19PT+pq9SjjaU=; b=jkufZn7NnMnpllCbMGHnaGre/hrBa/L3k40Ae0dBJmqvp5o7gm/CCCIFenrS5vS/og XLFJQMS441xR7kymRmuYKIw2EHs6R1FTC6zMtGWqSipQ/OebWv9vDBR7YLUJ4V3zBnZH xvd0sG0I8EgpYmVMJiD2x+F7bQVzQ5tUtpc9UMU6sKd8633g4b3SpIPkveroqxvBJlIM e5MFk65lW/+BKYky8Q5PJWxR6dJIxOerz31KmiX4wF0T2OKL5SoASWH+yoKH7Em+nfGj NPwR0kYevRXpnJX7TA/k0XjZQVvcof7AYqo9RajKNNPNLXXyIhJ9NBW/t4ZAL/2EdoH4 OeWA== 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=rgbDgsqLEzDX1FLEujh197ceWBfJWb19PT+pq9SjjaU=; b=p4XqCgTzomopdZtRcqM7zKpa3FSHKUWA/6DrWtU7Eld0qCKLTUEQa+91YsmtOrlpWn 7Vh+IpvouT1L7cMd1/wxrYFWb4vPSRvijW+qBKx8wvcsCpmcGkYRKMDcrOJsYGLBb0/U 60M0r7LYMumtOJja/bEReWorJW/2DVKa9fzxt43472tzt1B0/5W/0dDX+zts+fqZ2gO5 ZFFFqvzlLgHLQyrZRu+lhmsjBHYjeRUeOOFv5u591rObZYvORzgUT/pPRehkalVCwZLc pPewWsp2MaQ1YiOdcL5h/fwS7A+RgnW3Qcx3ejEtQFk5kyP3eF/7HhxEfjyBnb5qKBW6 69Rw== X-Gm-Message-State: ABuFfoj6WOjijt+WDGYdoELFrKLDeE44ktPgRQmWnDpZpgRsb4ui0Ee2 /xlFul7WRy27pyjweriFOYGTLdowO92wf/rxK1LxIQ== X-Google-Smtp-Source: ACcGV618+q7dLbQgP/isggCrUIvfjXI0AvZXRr2G/+N6f606N2Znp/T4FTaiHS7XRzRUEQ8O1E0uEqoQXElaMvWPdkI= X-Received: by 2002:ab0:14a4:: with SMTP id d33mr21661517uae.41.1540326118303; Tue, 23 Oct 2018 13:21:58 -0700 (PDT) MIME-Version: 1.0 References: <201810231948.w9NJmYlC078288@fire.js.berklix.net> <201810232013.w9NKDOQC023342@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201810232013.w9NKDOQC023342@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Tue, 23 Oct 2018 14:21:47 -0600 Message-ID: Subject: Re: ctm(1) deprecation in the FreeBSD base system? To: "Rodney W. Grimes" Cc: "Julian H. Stacey" , Stefan Esser , "Montgomery-Smith, Stephen" , ctm-users@freebsd.org, Poul-Henning Kamp , FreeBSD Current , Ed Maste 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, 23 Oct 2018 20:21:59 -0000 On Tue, Oct 23, 2018 at 2:13 PM Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > A cost(=time)/benefit look on moving ctm from src/ to ports/ : > > - No tangible architecture benefit (its not like purging an old driver > > to makes kernel support simpler, or avoiding clashing libs etc) > > - FreeBSD would shrink 0.028 % of the size of src/ > > cd /pub/FreeBSD/branches/-current/src > > du -s -k . # 1223922 > > du -s -k `find . -type d -name \*ctm\*` > > 196 ./usr.sbin/ctm > > 74 ./usr.sbin/ctm/ctm > > 12 ./usr.sbin/ctm/ctm_dequeue > > 44 ./usr.sbin/ctm/ctm_rmail > > 18 ./usr.sbin/ctm/ctm_smail > > dc 196 74 12 44 18 + + + + p 344 > > dc 344000000000 1223922 / p 281063 # then move 9 points > > xcalc 344 / 1223922 # 0.0002810636 > > > > Those who would do the work might want to ponder if 0.028 % is best use > of > > their time, or if more fun & benefit to work on some other part of > FreeBSD ? > > At the most/least we should not go very far, > the only thing that needs done soon is a gonein(13) commited > to head and MFC'ed to stable/12 by thursday. > > All the other details should wait until a depreication policy > revision is completed that includes how to deal with this. > There's no reason at all to wait. We can create the port. We can create the github repo. We can move the history there. We won't be removing it before we have a chance to socialize the removal and give people a chance to cut over. None of this requires a new policy. Everybody agrees we should do it. We shouldn't let some perceived policy get in the way of just moving forward. Warner From owner-freebsd-current@freebsd.org Tue Oct 23 20:22:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F0A4FFB667 for ; Tue, 23 Oct 2018 20:22:07 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 145048ECE3 for ; Tue, 23 Oct 2018 20:22:07 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yb1-xb29.google.com with SMTP id o204-v6so1131273yba.9 for ; Tue, 23 Oct 2018 13:22:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xpmRjQutNo3PCVnCV4KE2tXAxpD+Z+zyr4OEBXSYvc8=; b=10f57ahHa/X1wzJ+zKxzHqyLJl5YK66GGpb2ABmyNrOMTB0dPTM3oTnrmfBhbPVYhA gDhNeRMr950uWeI3+fIEGYCD6ZEFTV8fK/9KQMfo4KtaG/IYVEeP+7wdRkYhOrse0/QU CG4Dl2vJOFOywTHVQigOrjEzA54S5e/aG6XwG1difmcGNxcQl7YKOBSGtkwVmUI7u5OS K1GfD/Fxcv92p+yL62/QXcTZDoc05ruJX5+Uw47mh972Fb410+xMRJUz6lHZVoUPjoyS biG6HszKs/e9i9bgiXPcClu1OU9OoUKi4ya76IT10AtdizaVZqM7WUADeq1RDLQlX8OF As0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xpmRjQutNo3PCVnCV4KE2tXAxpD+Z+zyr4OEBXSYvc8=; b=RFZaHPqQG4e87FrQk0P7QpNqU6vSQ/ucOP/cpbTFbqptYFWTrI7eh9li+fzlY+i82J 4NjZkAHmBo6zdPQEAPoJVDzk8ac7yU6an7QG8cwTmyrjmOXf4XxCq/EfQJu2nZWa34C6 S2jZk3BevgneU9Lw4tdEc+axZCjkcV4I78CiTaNWyvWwjP1hB3qzbuzTEzkm3O3ZAJjN wE0F5l78pcVXCuyCzs7hkXfce9fG0qe4zLHuGGbmATbaMItK9CBIL8ZrMvXMLydAtFQd F/FmOwODaep1o3l/jdBpbZlasBLNbgshCz2QjnlrE6LAac90E9dSno5o1PVoWL6Udt4x Evgg== X-Gm-Message-State: ABuFfoiYYusDoysuljbQsmZhU7NDvXiuVrFLnYtKoZozxx3vW56vLMAU y6EkpTdWjhFA5SQ7uyzCYKCncfFoq0xcODSBseKzHQ== X-Google-Smtp-Source: ACcGV60ogEmu61LclCp9ZIsgugHz3m4ZDsHbnqCRlTGEmpysSR4sHe4rvy1j6mglF8sYlnc0LNoomnwM/jmHt45A0YY= X-Received: by 2002:a25:b941:: with SMTP id s1-v6mr36929044ybm.60.1540326126497; Tue, 23 Oct 2018 13:22:06 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 13:22:05 -0700 (PDT) In-Reply-To: <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 21:22:05 +0100 X-Google-Sender-Auth: 3pTFtEbOFZGq3xl7htj5zhOX6wk Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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: Tue, 23 Oct 2018 20:22:07 -0000 Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INTERP in /etc/make.conf and then reinstall just the loader and boot parts onto the UEFI partition ? If so, how ? On 23 October 2018 at 21:17, Toomas Soome wrote: > ok, in that case I=E2=80=99d suggest to test out if forth based one is st= ill > working - at least you can get the bootable system. And then there is a > chance to debug the lua version too (note it should be possible to chain > /boot/loader_lua.efi). > > rgds, > toomas > > > On 23 Oct 2018, at 23:08, Harry Newton wrote: > > > > So it's got FORTH in it, but my loader is lua based, and also doesn't > > appear to read loader.rc. > > > > /H > > > > On 23 October 2018 at 21:03, Toomas Soome wrote: > > > >> hm. in that case, whats the content of /boot/loader.rc ? > >> > >> rgds, > >> toomas > >> > >> > >> On 23 Oct 2018, at 23:01, Harry Newton wrote: > >> > >> If boot menu is the screen where you get the options for various kerne= ls > >> and the picture of the daemon head, no. It stops at the point in my > email > >> =E2=80=94 though not as I said just before the kernel is loaded but in= point of > >> fact before the menu. > >> > >> I've also rebuilt the kernel and still can't use efibootmgr which is > >> puzzling me. > >> > >> /H > >> > >> > >> On 23 October 2018 at 20:56, Toomas Soome wrote: > >> > >>> Do you get boot menu? if so, press esc to get to ok prompt, then type > >>> start - if its bootfort based loader, it will load the kernel and > modules. > >>> lsmod will then list the loaded files. > >>> > >>> If the loader prompt is still usable, then next command would be: boo= t > >>> > >>> rgds, > >>> toomas > >>> > >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: > >>>> > >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 > >>> r339529 > >>>> by source. Have a problem with booting which hangs after: > >>>> > >>>>>> FreeBSD EFI boot block > >>>> Loader path: /boot/loader.efi > >>>> > >>>> Initializing modules: ZFS UFS > >>>> Probing 5 block devices ... done > >>>> ZFS found the following pools: zroot > >>>> UFS found no partitions > >>>> Consoles: EFI console > >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>> > >>>> Command line arguments: loader.efi > >>>> EFI version 2.31 > >>>> EFI Firmware: American Megatrends (rev 4.654) > >>>> Console: efi(0) > >>>> Load Path: HD(4, GPT [ ... ] > >>>> Load Device: Pci Root [ ... ] > >>>> Boot Current: 0001 > >>>> Boot Order: 0001 [x] > >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>>> - > >>>> > >>>> So it gets into loader.efi which runs but stops I think just before > >>> loading > >>>> the kernel. Partitions: > >>>> > >>>> =3D> 40 250069600 ada0 GPT (119G) > >>>> 40 1600 1 efi (800K) > >>>> 1640 1024 2 freebsd-boot (512K) > >>>> 2664 1432 - free - (716K) > >>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>> 250068992 648 - free - (324K) > >>>> > >>>> and the EFI partition is FAT 12. > >>>> > >>>> I can't provide (at the moment) any output from efibootmgr: > >>>> > >>>> root@gryphon:~ # efibootmgr -v > >>>> efibootmgr: efi variables not supported on this system. root? kldloa= d > >>> efirt? > >>>> root@gryphon:~ # kldload efirt > >>>> kldload: can't load efirt: module already loaded or in kernel > >>>> > >>>> which I don't understand. > >>>> > >>>> I'm going to rebuild the kernel (currently GENERIC) and see if that > >>> allows > >>>> me to load efirt / use efibootmgr. > >>>> > >>>> In the meantime, I should be very grateful for any advice. > >>>> > >>>> ( Currently booting using a 11-RELEASE memstick image and dropping > into > >>> its > >>>> loader to get to the installed 12-STABLE ). > >>>> > >>>> /Harry > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org mailing list > >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>> reebsd.org" > >>> > >>> > >> > >> > >> -- > >> Harry Newton > >> > >> > >> > > > > > > -- > > Harry Newton > > _______________________________________________ > > 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" > > --=20 Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:31:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4881CFFBA0F for ; Tue, 23 Oct 2018 20:31:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp003.me.com (pv33p00im-asmtp003.me.com [17.142.194.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB6EC8F143 for ; Tue, 23 Oct 2018 20:31:03 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp003.me.com by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH200700GKFU100@pv33p00im-asmtp003.me.com> for freebsd-current@freebsd.org; Tue, 23 Oct 2018 20:30:47 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH200B1FJN49A40@pv33p00im-asmtp003.me.com>; Tue, 23 Oct 2018 20:30:44 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 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-1807170000 definitions=main-1810230167 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_06:,, signatures=0 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader Date: Tue, 23 Oct 2018 23:30:39 +0300 In-reply-to: Cc: FreeBSD Current To: Harry Newton References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> X-Mailer: Apple Mail (2.3445.100.39) 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: Tue, 23 Oct 2018 20:31:04 -0000 you should have the binaries in boot - just ln (or copy) one to = loader.efi rgds, toomas > On 23 Oct 2018, at 23:22, Harry Newton wrote: >=20 > Yes ... so as everything is built, can I just alter = LOADER_DEFAULT_INTERP in /etc/make.conf and then reinstall just the = loader and boot parts onto the UEFI partition ? If so, how ? >=20 >=20 > On 23 October 2018 at 21:17, Toomas Soome > wrote: > ok, in that case I=E2=80=99d suggest to test out if forth based one is = still working - at least you can get the bootable system. And then there = is a chance to debug the lua version too (note it should be possible to = chain /boot/loader_lua.efi). >=20 > rgds, > toomas >=20 > > On 23 Oct 2018, at 23:08, Harry Newton > wrote: > >=20 > > So it's got FORTH in it, but my loader is lua based, and also = doesn't > > appear to read loader.rc. > >=20 > > /H > >=20 > > On 23 October 2018 at 21:03, Toomas Soome > wrote: > >=20 > >> hm. in that case, whats the content of /boot/loader.rc ? > >>=20 > >> rgds, > >> toomas > >>=20 > >>=20 > >> On 23 Oct 2018, at 23:01, Harry Newton > wrote: > >>=20 > >> If boot menu is the screen where you get the options for various = kernels > >> and the picture of the daemon head, no. It stops at the point in = my email > >> =E2=80=94 though not as I said just before the kernel is loaded but = in point of > >> fact before the menu. > >>=20 > >> I've also rebuilt the kernel and still can't use efibootmgr which = is > >> puzzling me. > >>=20 > >> /H > >>=20 > >>=20 > >> On 23 October 2018 at 20:56, Toomas Soome > wrote: > >>=20 > >>> Do you get boot menu? if so, press esc to get to ok prompt, then = type > >>> start - if its bootfort based loader, it will load the kernel and = modules. > >>> lsmod will then list the loaded files. > >>>=20 > >>> If the loader prompt is still usable, then next command would be: = boot > >>>=20 > >>> rgds, > >>> toomas > >>>=20 > >>>> On 23 Oct 2018, at 20:45, Harry Newton > wrote: > >>>>=20 > >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 > >>> r339529 > >>>> by source. Have a problem with booting which hangs after: > >>>>=20 > >>>>>> FreeBSD EFI boot block > >>>> Loader path: /boot/loader.efi > >>>>=20 > >>>> Initializing modules: ZFS UFS > >>>> Probing 5 block devices ... done > >>>> ZFS found the following pools: zroot > >>>> UFS found no partitions > >>>> Consoles: EFI console > >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>>=20 > >>>> Command line arguments: loader.efi > >>>> EFI version 2.31 > >>>> EFI Firmware: American Megatrends (rev 4.654) > >>>> Console: efi(0) > >>>> Load Path: HD(4, GPT [ ... ] > >>>> Load Device: Pci Root [ ... ] > >>>> Boot Current: 0001 > >>>> Boot Order: 0001 [x] > >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>>> - > >>>>=20 > >>>> So it gets into loader.efi which runs but stops I think just = before > >>> loading > >>>> the kernel. Partitions: > >>>>=20 > >>>> =3D> 40 250069600 ada0 GPT (119G) > >>>> 40 1600 1 efi (800K) > >>>> 1640 1024 2 freebsd-boot (512K) > >>>> 2664 1432 - free - (716K) > >>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>> 250068992 648 - free - (324K) > >>>>=20 > >>>> and the EFI partition is FAT 12. > >>>>=20 > >>>> I can't provide (at the moment) any output from efibootmgr: > >>>>=20 > >>>> root@gryphon:~ # efibootmgr -v > >>>> efibootmgr: efi variables not supported on this system. root? = kldload > >>> efirt? > >>>> root@gryphon:~ # kldload efirt > >>>> kldload: can't load efirt: module already loaded or in kernel > >>>>=20 > >>>> which I don't understand. > >>>>=20 > >>>> I'm going to rebuild the kernel (currently GENERIC) and see if = that > >>> allows > >>>> me to load efirt / use efibootmgr. > >>>>=20 > >>>> In the meantime, I should be very grateful for any advice. > >>>>=20 > >>>> ( Currently booting using a 11-RELEASE memstick image and = dropping into > >>> its > >>>> loader to get to the installed 12-STABLE ). > >>>>=20 > >>>> /Harry > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org = mailing list > >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current = > >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>> reebsd.org " > >>>=20 > >>>=20 > >>=20 > >>=20 > >> -- > >> Harry Newton > >>=20 > >>=20 > >>=20 > >=20 > >=20 > > --=20 > > Harry Newton > > _______________________________________________ > > 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 = " >=20 >=20 >=20 >=20 > --=20 > Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:33:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D71CDFFC062 for ; Tue, 23 Oct 2018 20:33:57 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc2b.google.com (mail-yw1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 690388F613 for ; Tue, 23 Oct 2018 20:33:57 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc2b.google.com with SMTP id i185-v6so1116385ywa.12 for ; Tue, 23 Oct 2018 13:33:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=g7MlBMyQT48v6rL6p0xIWN+ttIDqaccClv2WuCQNR7Q=; b=bVKhjJUZ4VZ9EZgRpqd3iXn0sXNx63iYBDYqsilUDzYOAod7w+lYhOV4/Yx8DLJ0Jl Mmo66JJIitYL5ojwTvqtKos4GZR2FvFw3eumCQVqkBQdaZ6eRNUOOqjatTZCuzRQddBF 7NIDAy7MnottDM9p+6conIEh/5qn2GFinUte2aJdNhOm1jBA4VXn0/NfF6Qe+UxhgOct satvsenfzBPsc8o9XErYMg0m6TLF0i9dKoul/qVTEhwv8yWeS0M8Drw1R0As8mU2Iyzc 0wVRsqvQrQzScFV2QtTgbZS2MujJZXv5mrqz18ssZAsrvu9hu0oxzxdG0vgzH/J84jIQ O0BA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=g7MlBMyQT48v6rL6p0xIWN+ttIDqaccClv2WuCQNR7Q=; b=cnl7cfQIw8m9iulenZlFVsvGZ08ZkV9XySpVcqiTUb0A0i9KZfFWaRlw+kVAsgBPD3 O1iX4SOIbodAIvUNFrYyfeMPJ8qd5GETkoYgdce5llVqYWOeW2zijGR4h6axMH554WDb y6denCqFIqrHMwCPESwjD9cunrj6WbNkE06ZuKtx1ZrDxOBPXgWrXe9IL/T32UUH38RZ raLdCqJq6k40aiIRTqrO5CmJ04S1S8oHbV+VU7mmwT2hCg1cZrOlTkaeIPEnAk27O1jT JptgsnI5fFgGi3pQ/QsDOcsZCgWbtjgTK1vLaSskMqaiFDy9hgOvd6ASDhGziLTQ0N+W zrZQ== X-Gm-Message-State: ABuFfojGMYC8RHV7NLjfl+VNAct2MoVCG2tOba9xauuVDgxylTp2Y9s6 OU52NClKCmGgtp7L49bvMQoR34A9PlJ7dLUKjmRCig== X-Google-Smtp-Source: ACcGV63iqdrbyFiYosUbmQ7EhrCOpUhUCp7pB4nRMhGZTydGHvnRkqviRfO6NiDDfTEpaUazsSi1kr8Db8gMVRbQ3uo= X-Received: by 2002:a0d:f144:: with SMTP id a65-v6mr37115066ywf.330.1540326836805; Tue, 23 Oct 2018 13:33:56 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 13:33:55 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 21:33:55 +0100 X-Google-Sender-Auth: aVpBpjBSY4aUYoV7YcAqXI833Hs Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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: Tue, 23 Oct 2018 20:33:58 -0000 Right ... I've the binaries in /boot, freshly made. This might be a silly question ... do I not need to copy them (or dd the boot1.efifat image) to the EFI partition ? /H On 23 October 2018 at 21:30, Toomas Soome wrote: > you should have the binaries in boot - just ln (or copy) one to loader.ef= i > > rgds, > toomas > > > On 23 Oct 2018, at 23:22, Harry Newton wrote: > > Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INTERP > in /etc/make.conf and then reinstall just the loader and boot parts onto > the UEFI partition ? If so, how ? > > > On 23 October 2018 at 21:17, Toomas Soome wrote: > >> ok, in that case I=E2=80=99d suggest to test out if forth based one is s= till >> working - at least you can get the bootable system. And then there is a >> chance to debug the lua version too (note it should be possible to chain >> /boot/loader_lua.efi). >> >> rgds, >> toomas >> >> > On 23 Oct 2018, at 23:08, Harry Newton wrote: >> > >> > So it's got FORTH in it, but my loader is lua based, and also doesn't >> > appear to read loader.rc. >> > >> > /H >> > >> > On 23 October 2018 at 21:03, Toomas Soome wrote: >> > >> >> hm. in that case, whats the content of /boot/loader.rc ? >> >> >> >> rgds, >> >> toomas >> >> >> >> >> >> On 23 Oct 2018, at 23:01, Harry Newton wrote: >> >> >> >> If boot menu is the screen where you get the options for various >> kernels >> >> and the picture of the daemon head, no. It stops at the point in my >> email >> >> =E2=80=94 though not as I said just before the kernel is loaded but i= n point of >> >> fact before the menu. >> >> >> >> I've also rebuilt the kernel and still can't use efibootmgr which is >> >> puzzling me. >> >> >> >> /H >> >> >> >> >> >> On 23 October 2018 at 20:56, Toomas Soome wrote: >> >> >> >>> Do you get boot menu? if so, press esc to get to ok prompt, then typ= e >> >>> start - if its bootfort based loader, it will load the kernel and >> modules. >> >>> lsmod will then list the loaded files. >> >>> >> >>> If the loader prompt is still usable, then next command would be: bo= ot >> >>> >> >>> rgds, >> >>> toomas >> >>> >> >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: >> >>>> >> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 >> >>> r339529 >> >>>> by source. Have a problem with booting which hangs after: >> >>>> >> >>>>>> FreeBSD EFI boot block >> >>>> Loader path: /boot/loader.efi >> >>>> >> >>>> Initializing modules: ZFS UFS >> >>>> Probing 5 block devices ... done >> >>>> ZFS found the following pools: zroot >> >>>> UFS found no partitions >> >>>> Consoles: EFI console >> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >> >>>> >> >>>> Command line arguments: loader.efi >> >>>> EFI version 2.31 >> >>>> EFI Firmware: American Megatrends (rev 4.654) >> >>>> Console: efi(0) >> >>>> Load Path: HD(4, GPT [ ... ] >> >>>> Load Device: Pci Root [ ... ] >> >>>> Boot Current: 0001 >> >>>> Boot Order: 0001 [x] >> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >> >>>> - >> >>>> >> >>>> So it gets into loader.efi which runs but stops I think just before >> >>> loading >> >>>> the kernel. Partitions: >> >>>> >> >>>> =3D> 40 250069600 ada0 GPT (119G) >> >>>> 40 1600 1 efi (800K) >> >>>> 1640 1024 2 freebsd-boot (512K) >> >>>> 2664 1432 - free - (716K) >> >>>> 4096 4194304 3 freebsd-swap (2.0G) >> >>>> 4198400 245870592 4 freebsd-zfs (117G) >> >>>> 250068992 648 - free - (324K) >> >>>> >> >>>> and the EFI partition is FAT 12. >> >>>> >> >>>> I can't provide (at the moment) any output from efibootmgr: >> >>>> >> >>>> root@gryphon:~ # efibootmgr -v >> >>>> efibootmgr: efi variables not supported on this system. root? kldlo= ad >> >>> efirt? >> >>>> root@gryphon:~ # kldload efirt >> >>>> kldload: can't load efirt: module already loaded or in kernel >> >>>> >> >>>> which I don't understand. >> >>>> >> >>>> I'm going to rebuild the kernel (currently GENERIC) and see if that >> >>> allows >> >>>> me to load efirt / use efibootmgr. >> >>>> >> >>>> In the meantime, I should be very grateful for any advice. >> >>>> >> >>>> ( Currently booting using a 11-RELEASE memstick image and dropping >> into >> >>> its >> >>>> loader to get to the installed 12-STABLE ). >> >>>> >> >>>> /Harry >> >>>> _______________________________________________ >> >>>> freebsd-current@freebsd.org mailing list >> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> >>> reebsd.org" >> >>> >> >>> >> >> >> >> >> >> -- >> >> Harry Newton >> >> >> >> >> >> >> > >> > >> > -- >> > Harry Newton >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> reebsd.org" >> >> > > > -- > Harry Newton > > > --=20 Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 20:57:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2D70FFC953; Tue, 23 Oct 2018 20:57:55 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout02.bt.lon5.cpcloud.co.uk (rgout0207.bt.lon5.cpcloud.co.uk [65.20.0.206]) by mx1.freebsd.org (Postfix) with ESMTP id 1722170141; Tue, 23 Oct 2018 20:57:54 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 86.142.105.36 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-RazorGate-Vade-Classification: clean X-RazorGate-Vade-Verdict: clean 0 X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtkedrgeeggdduheefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvfhfjgfufffkgggtgffothesthejghdtvddtvdenucfhrhhomhepfdfvhhhomhgrshcuufhprghrrhgvvhhohhhnfdcuoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecukfhppeekiedrudegvddruddthedrfeeinecurfgrrhgrmhephhgvlhhopefvhhhomhgrshfrvedpihhnvghtpeekiedrudegvddruddthedrfeeipdhmrghilhhfrhhomhepoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqpdhrtghpthhtohepoegtthhmqdhushgvrhhssehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeovghmrghsthgvsehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeofhhrvggvsghsugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrgheqpdhrtghpthhtohepoehfrhgvvggsshguqdhrfihgsehpugigrdhrhhdrtghnkeehrdgunhhsmhhgrhdrnhgvtheqpdhrtghpthhtohepoehimhhpsegsshguihhmphdrtghomheqpdhrtghpthhtohepoehphhhksehphhhkrdhf rhgvvggsshgurdgukheqnecuvehluhhsthgvrhfuihiivgeptd X-RazorGate-Vade-Classification: clean X-RazorGate-Vade-Verdict: clean 0 X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtkedrgeeggdduheehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvfhfjgfufffkgggtgffothesthejghdtvddtvdenucfhrhhomhepfdfvhhhomhgrshcuufhprghrrhgvvhhohhhnfdcuoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecukfhppeekiedrudegvddruddthedrfeeinecurfgrrhgrmhephhgvlhhopefvhhhomhgrshfrvedpihhnvghtpeekiedrudegvddruddthedrfeeipdhmrghilhhfrhhomhepoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqpdhrtghpthhtohepoegtthhmqdhushgvrhhssehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeovghmrghsthgvsehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeofhhrvggvsghsugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrgheqpdhrtghpthhtohepoehphhhksehphhhkrdhfrhgvvggsshgurdgukheqnecuvehluhhsthgvrhfuihiivgeptd X-RazorGate-Vade-Classification: clean X-RazorGate-Vade-Verdict: clean 0 X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtkedrgeeggdduheehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvfhfjgfufffkgggtgffothesthejghdtvddtvdenucfhrhhomhepfdfvhhhomhgrshcuufhprghrrhgvvhhohhhnfdcuoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecukfhppeekiedrudegvddruddthedrfeeinecurfgrrhgrmhephhgvlhhopefvhhhomhgrshfrvedpihhnvghtpeekiedrudegvddruddthedrfeeipdhmrghilhhfrhhomhepoefvhhhomhgrshdrufhprghrrhgvvhhohhhnsegsthhinhhtvghrnhgvthdrtghomheqpdhrtghpthhtohepoegtthhmqdhushgvrhhssehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeovghmrghsthgvsehfrhgvvggsshgurdhorhhgqedprhgtphhtthhopeeofhhrvggvsghsugdqtghurhhrvghnthesfhhrvggvsghsugdrohhrgheqpdhrtghpthhtohepoehphhhksehphhhkrdhfrhgvvggsshgurdgukheqnecuvehluhhsthgvrhfuihiivgepge Received: from ThomasPC (86.142.105.36) by rgout02.bt.lon5.cpcloud.co.uk (9.0.019.26-1) (authenticated as Thomas.Sparrevohn) id 5B93D5940405739A; Tue, 23 Oct 2018 21:53:52 +0100 From: "Thomas Sparrevohn" To: "'Poul-Henning Kamp'" , "'Warner Losh'" Cc: "'Rodney W. Grimes'" , "'Ed Maste'" , "'FreeBSD Current'" , References: <7288.1540239007@critter.freebsd.dk> <201810222038.w9MKcP4L013243@pdx.rh.CN85.dnsmgr.net> <7832.1540241924@critter.freebsd.dk> In-Reply-To: <7832.1540241924@critter.freebsd.dk> Subject: RE: ctm(1) deprecation in the FreeBSD base system? Date: Tue, 23 Oct 2018 21:53:52 +0100 Message-ID: <009a01d46b12$81fe7f70$85fb7e50$@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQGhl4lQMphGAj+Sjvex/i2hCwXaPgKSquXoAnN1lhMBTYVtr6VgWGPA Content-Language: en-gb 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, 23 Oct 2018 20:57:55 -0000 And more importantly a great thanks for ctm from all of us who depended on it for ages ;-) -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Poul-Henning Kamp Sent: 22 October 2018 21:59 To: Warner Losh Cc: Rodney W. Grimes ; Ed Maste ; FreeBSD Current ; ctm-users@freebsd.org Subject: Re: ctm(1) deprecation in the FreeBSD base system? -------- In message , Warner Losh writes: >> > I think Julian Stacy is still running CTM generation ? >> >> Ah, yes, that brought back enough brain cells, confirmed that is who >> I saw with ctm usage. > >Do we need it in base? Or can we make it a port? Absolutely make it a port! -- 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. _______________________________________________ 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 Oct 23 21:23:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDE38FFD44B for ; Tue, 23 Oct 2018 21:23:44 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc2d.google.com (mail-yw1-xc2d.google.com [IPv6:2607:f8b0:4864:20::c2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83D9470FED for ; Tue, 23 Oct 2018 21:23:44 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc2d.google.com with SMTP id v199-v6so1192458ywg.1 for ; Tue, 23 Oct 2018 14:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=vIGIkl64F3FZIIfsdw1WcTx9918ISt225gzSCsYYpqs=; b=MHvx+ia/5OkPuNc/Lc0m+kG0wUG4ZoWAZB5K3YYJNW2G36kDgNMNFYvWAKYH9U87QB 9E6TZzbAkv1+ZDJQ6fFYgr9dzgBTxHV/beiy3DmbmUJUCB+M1/3cyhFHm0kLkCL2JKgO hW0QxUz5Ku+UdXBJq84Y00cacuzS165hJFKnnPYkryzyCuf4CF+elFnGnvg1IGXgX5sI eEnvbtP1CatoMoHNdViFXexzaHPNbY7ENUgTmD0S/AQm33eNeB3nRFjkQPP8Bz3DOS38 EDtNWnHJ+BHOjabOoFy46IleEzSxulaV1gk6g+nAen+LL88dbvBIc5cSmyOIs2Jc4apS vyMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=vIGIkl64F3FZIIfsdw1WcTx9918ISt225gzSCsYYpqs=; b=NNHVB6jzPDoDAQGNcR4BrgdZswxAmqQD3Ev2ptgCPgNknXoQ94J3siMTpYPBK7f9PT PTyC0uMqdIbtLuxnEzZRb6rrSpUaNtM6CB3Owc+pWKDJD7tV09dBVjDHVf33PSYweJBk SF/arEvO04UxFVo0rvNKq3DgqkCz4m9hLd4ERLBxuMJ+vosjGWJ+1PKtaG0YJ+FVR+rJ hcghTHKxKuxMahfN0ZRYyQVkM42kgDD8aH4OO7bE8M5wVgx3FQsTA/XjGxkRHAIKmmUi 2DE9BUXcTc3ZMz5iaeXllTZz/MBqNImCE3jyYT5Vy5HFgqkYaLSGBBGYp77D7H0fBGMA 3UgQ== X-Gm-Message-State: ABuFfohlDh+lmATphjf8uAVWoFkYW98TLPESZMu7J82IwCb+UR58og5o IfMi/DyMvV7BSGLW7IUneRJnXPtlMLuZYZR/9uMYaw== X-Google-Smtp-Source: ACcGV612UxGyHu9xW3QBrBxt3YSyww0eaYZXOk6ZQwj8aLtDY37m0/QBw09K3iaQ7DQKyw+LLX8yTAc/uc7VeAmSLUI= X-Received: by 2002:a0d:d705:: with SMTP id z5-v6mr8294144ywd.22.1540329823773; Tue, 23 Oct 2018 14:23:43 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Tue, 23 Oct 2018 14:23:43 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Tue, 23 Oct 2018 22:23:43 +0100 X-Google-Sender-Auth: 9DCYC3DlT_jtMBm0KUuAKwaO6KQ Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: FreeBSD Current 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: Tue, 23 Oct 2018 21:23:45 -0000 I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-made th= e binaries in /boot but this doesn't solve the problem. It did copy /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8) which is what is called from /boot/boot1.efi and which contains the strings I see on the console before the hang. But it must then call / read something else and I don't think it can find it. Not sure why it doesn't produce an error message. I *think* it may be something to do with EFI variables, but as efibootmgr doesn't work I can't explore this, despite efirt being in the kernel. Suggestions received welcomed, and new suggestions / leads to follow also very much welcomed. /H On 23 October 2018 at 21:33, Harry Newton wrote: > Right ... I've the binaries in /boot, freshly made. This might be a sill= y > question ... do I not need to copy them (or dd the boot1.efifat image) to > the EFI partition ? > > /H > > On 23 October 2018 at 21:30, Toomas Soome wrote: > >> you should have the binaries in boot - just ln (or copy) one to loader.e= fi >> >> rgds, >> toomas >> >> >> On 23 Oct 2018, at 23:22, Harry Newton wrote: >> >> Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INTER= P >> in /etc/make.conf and then reinstall just the loader and boot parts onto >> the UEFI partition ? If so, how ? >> >> >> On 23 October 2018 at 21:17, Toomas Soome wrote: >> >>> ok, in that case I=E2=80=99d suggest to test out if forth based one is = still >>> working - at least you can get the bootable system. And then there is a >>> chance to debug the lua version too (note it should be possible to chai= n >>> /boot/loader_lua.efi). >>> >>> rgds, >>> toomas >>> >>> > On 23 Oct 2018, at 23:08, Harry Newton wrote: >>> > >>> > So it's got FORTH in it, but my loader is lua based, and also doesn't >>> > appear to read loader.rc. >>> > >>> > /H >>> > >>> > On 23 October 2018 at 21:03, Toomas Soome wrote: >>> > >>> >> hm. in that case, whats the content of /boot/loader.rc ? >>> >> >>> >> rgds, >>> >> toomas >>> >> >>> >> >>> >> On 23 Oct 2018, at 23:01, Harry Newton wrote: >>> >> >>> >> If boot menu is the screen where you get the options for various >>> kernels >>> >> and the picture of the daemon head, no. It stops at the point in my >>> email >>> >> =E2=80=94 though not as I said just before the kernel is loaded but = in point >>> of >>> >> fact before the menu. >>> >> >>> >> I've also rebuilt the kernel and still can't use efibootmgr which is >>> >> puzzling me. >>> >> >>> >> /H >>> >> >>> >> >>> >> On 23 October 2018 at 20:56, Toomas Soome wrote: >>> >> >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, then ty= pe >>> >>> start - if its bootfort based loader, it will load the kernel and >>> modules. >>> >>> lsmod will then list the loaded files. >>> >>> >>> >>> If the loader prompt is still usable, then next command would be: >>> boot >>> >>> >>> >>> rgds, >>> >>> toomas >>> >>> >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: >>> >>>> >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA1 >>> >>> r339529 >>> >>>> by source. Have a problem with booting which hangs after: >>> >>>> >>> >>>>>> FreeBSD EFI boot block >>> >>>> Loader path: /boot/loader.efi >>> >>>> >>> >>>> Initializing modules: ZFS UFS >>> >>>> Probing 5 block devices ... done >>> >>>> ZFS found the following pools: zroot >>> >>>> UFS found no partitions >>> >>>> Consoles: EFI console >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>> >>>> >>> >>>> Command line arguments: loader.efi >>> >>>> EFI version 2.31 >>> >>>> EFI Firmware: American Megatrends (rev 4.654) >>> >>>> Console: efi(0) >>> >>>> Load Path: HD(4, GPT [ ... ] >>> >>>> Load Device: Pci Root [ ... ] >>> >>>> Boot Current: 0001 >>> >>>> Boot Order: 0001 [x] >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >>> >>>> - >>> >>>> >>> >>>> So it gets into loader.efi which runs but stops I think just befor= e >>> >>> loading >>> >>>> the kernel. Partitions: >>> >>>> >>> >>>> =3D> 40 250069600 ada0 GPT (119G) >>> >>>> 40 1600 1 efi (800K) >>> >>>> 1640 1024 2 freebsd-boot (512K) >>> >>>> 2664 1432 - free - (716K) >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) >>> >>>> 250068992 648 - free - (324K) >>> >>>> >>> >>>> and the EFI partition is FAT 12. >>> >>>> >>> >>>> I can't provide (at the moment) any output from efibootmgr: >>> >>>> >>> >>>> root@gryphon:~ # efibootmgr -v >>> >>>> efibootmgr: efi variables not supported on this system. root? >>> kldload >>> >>> efirt? >>> >>>> root@gryphon:~ # kldload efirt >>> >>>> kldload: can't load efirt: module already loaded or in kernel >>> >>>> >>> >>>> which I don't understand. >>> >>>> >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see if tha= t >>> >>> allows >>> >>>> me to load efirt / use efibootmgr. >>> >>>> >>> >>>> In the meantime, I should be very grateful for any advice. >>> >>>> >>> >>>> ( Currently booting using a 11-RELEASE memstick image and dropping >>> into >>> >>> its >>> >>>> loader to get to the installed 12-STABLE ). >>> >>>> >>> >>>> /Harry >>> >>>> _______________________________________________ >>> >>>> freebsd-current@freebsd.org mailing list >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> >>> reebsd.org" >>> >>> >>> >>> >>> >> >>> >> >>> >> -- >>> >> Harry Newton >>> >> >>> >> >>> >> >>> > >>> > >>> > -- >>> > Harry Newton >>> > _______________________________________________ >>> > freebsd-current@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >>> >> >> >> -- >> Harry Newton >> >> >> > > > -- > Harry Newton > --=20 Harry Newton From owner-freebsd-current@freebsd.org Tue Oct 23 21:39:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B37FFFDCC0 for ; Tue, 23 Oct 2018 21:39:25 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.227]) (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 C838A71A19 for ; Tue, 23 Oct 2018 21:39:24 +0000 (UTC) (envelope-from lausts@acm.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id F4OOgZai4vVJ9F4ORgihW1; Tue, 23 Oct 2018 21:39:16 +0000 Received: from [192.168.1.100] (presario [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id w9NLdCRh044824 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 23 Oct 2018 17:39:12 -0400 (EDT) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host presario [192.168.1.100] claimed to be [192.168.1.100] Reply-To: lausts@acm.org Subject: FIXED - Head won't build tool-chain at r339586 To: freebsd-current@freebsd.org References: From: Thomas Laus Openpgp: preference=signencrypt Autocrypt: addr=lausts@acm.org; prefer-encrypt=mutual; keydata= xsDiBDx1NWwRBADARalI5I8kGeBYYYWnZB73T1fU4333yCuRokRvzlAZ5Zhb3hqsNdTEMheN FDjZSL8J5jeJtvSRinY2p09CxpAMoJR9zHLmHl+zEOY8fInbB+KiFtSfGf0blSEY9/+isQP9 xmUIQWUj0kwVtrns7m1HrYLiI07NVFzbHNKqQcbPuwCg0n/KKi+VJiUs5MqLKwGuPotGeZME AIluMetTQwfLyovundMwFYlSZ/Z8JjkMybqgKuiRrZnaBVVZ80NjAYZI73yAZPfQh9mvFxW9 ipc2tSALwDy/tYDpQRK0k+0EsDmwG/wM6OarkqSuFcYx+tP86+2+6Xitn6E/hriIWa/ZQVef /fx7dZzdwhXH6fd34v8o/BuqhawLBACs4MTMGbdSmyI56vCMXWY1yxRPmuygd4vUnXqYwlrM Ee/LjQdreg1zTAJnnW1K+PgOUW/jvS+uAbgxLa3i59/Z4Uu7nB6G1y+Y1cThojUsLnvoJlt1 4XE1U/vnOcvO3evo6knB1qjbAMsZGaVleiVKDq+7XE7swe4WtBJKbYJthc0cVGhvbWFzIExh dXMgPGxhdXN0c0BhY20ub3JnPsJ/BBMRAgA/AheAAh4BBgsJCAcDAgYVCAIJCgsEFgIDAQIZ ARYhBBloSoDtPqFEokqZd+v/gtRiCDbPBQJaRO3QBQkfyKbkAAoJEOv/gtRiCDbPi+UAnAm8 +zuC7S1JQEjx/OU4asYWvLdcAJ0V59C0iowNwnxyPHBnYBQpOoDScc7BTQRFspgcEAgAjXsi 9WqowAKZ7d2ix6t7fiYgu2QBGWq36NvN+cPBJIu0CnagL1v4W1UrRW/0cInLzgqlWrSU7SFg y1+rGBlusMHf8/faGeZD0XwMdYgTIYdjdK5VZ0GaRWUs0LbHAOJQkOFRHLMAEG8wrc3f1xrn uVJ4JPOA81kTmTXvYTyQNXJBySc0oNSgvSut8aBbNGBZhw9U2V3yXXnnMeWR8+DYrriYdOdR eK7S0LNN8TPY60PJx3KLN9vUY9Cb5Ly0NavF3wREPQqYlNfTMoG/GA/n8XB6SCoMj73oKCyw FLbckBUjFsl7wTeKKvU68V8kWG762fscXhOhRduETGrja09MbwADBQf/WiycmdfNtB41+vvT HQqz9tm3ZHAW2yE53CxfQpvlyS/KwnWgLjl/iV0SHRDede0NJ5yTEqPVhqq7WCdlqVsHPSpX FfvyOgbNmjPmOY/a1nW4UnWSqA7bgQvkthahhoLeHzkU8YKupW0m05RIBpqQER6HwBOksTq4 sWV/lUy1P0VT8GqqPLNklKe2BEu+KhuhLV6XwEG3VrHNoY6/R5CMGvBhZbtiUViCZktmxJAj Fq0VCcuj7+Oo52eq4BL2vMrzLX+2Ib1JSWid6t0N+grXxbr2mv7H2V2/4Vo0XI3IKxPX1mdG y9RBkbRUGyV9A8RlaS0QTnXvsxZTjOnmjxPX68JmBBgRAgAmAhsMFiEEGWhKgO0+oUSiSpl3 6/+C1GIINs8FAlpE7dwFCRaLREAACgkQ6/+C1GIINs9JdgCfeHMtCRjzubbkAvAVg5wQo7gF moUAoL39iRV66xSZ0w/I00RnFU3jsmiz Message-ID: Date: Tue, 23 Oct 2018 17:39:11 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfHuXT27OHdavMyREBh0MAXU5z7PxUP+TP/JAQ+2Gg1ef+xj/+vSTSRetsIbpDMZ9zpaft6h7Bikh5OI55MHo/bxIuYMOaUJursoSQLXVgjiD9+9632Jp 5pR9jlCdE9tWanldats0WxtmA5SQ7g/QwEkawV/hSJEmLTJRls9EymvP 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, 23 Oct 2018 21:39:25 -0000 On 10/22/18 10:49 AM, Thomas Laus wrote: > I have been building HEAD for the past several years about every 2 > weeks. I updated my base source today from r339234 to r339586 and the > buildworld stops because a missing libarchive.so.7 dependency. It is > looking for libcrypto.so.9 which has not been built at this part of the > toolchain process yet. > > I deleted my source tree and performed a clean checkout. I deleted my > /usr/obj/* and my /tmp directory. There wasn't any special procedure or > notes in /usr/UPDATING to let me know of any other required steps to > perform this update. > It looks like I had a circular dependency created after an aborted 'installworld'. An updated libarchive was installed before libcrypto.so.9 was installed. Installing libcrypto depends on libarchive. Libarchive after the updated installation required libcrypto.so.9, which had not been installed yet. I used beadm to rollback my system two weeks to the last successful build. I ran svn update to bring me to the latest source update and then performed a buildworld followed by a new kernel. I manually installed the freshly built libarchive.so.9 and to be safe, also installed the rebuilt libarchive. Installworld finished successfully. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF From owner-freebsd-current@freebsd.org Tue Oct 23 21:51:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69E51FFE596 for ; Tue, 23 Oct 2018 21:51:54 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BC577249B for ; Tue, 23 Oct 2018 21:51:54 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id CC86C255E7 for ; Tue, 23 Oct 2018 21:51:53 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f178.google.com with SMTP id k11-v6so2835465lja.5 for ; Tue, 23 Oct 2018 14:51:53 -0700 (PDT) X-Gm-Message-State: AGRZ1gJL61RoXRyTsViBNDA+5YYmXUe89V3gVw3M6DGvhHAubhFkE3if mkgpXjbYFf8SMd9fZJMNm652cByNMpgjKJL/huM= X-Google-Smtp-Source: AJdET5fy6exr/T0JHY8bs2tnJOh0AUJzeD1mpCN9pQqCr6DUsJklgqnBjXbv//AucT2DgZ+pj3lDDsplvCG2umW6qo8= X-Received: by 2002:a2e:8945:: with SMTP id b5-v6mr29144ljk.20.1540331512302; Tue, 23 Oct 2018 14:51:52 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> In-Reply-To: From: Kyle Evans Date: Tue, 23 Oct 2018 16:51:39 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: UEFI boot hangs after loader To: hn@yewbarrow.net Cc: Toomas Soome , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 23 Oct 2018 21:51:54 -0000 Hi, I suspect 4th vs. lua has no impact here, given the output shown -- can you throw one of the installer images [0] on some removable media and give that a shot for booting? If that works, we can explore UEFI variables from there. efibootmgr will only work on a successful UEFI boot, unfortunately- if we didn't make uefi loader -> kernel transition, then we don't have access to runtime services. Thanks, Kyle Evans [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-made = the > binaries in /boot but this doesn't solve the problem. It did copy > /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8) > which is what is called from /boot/boot1.efi and which contains the strin= gs > I see on the console before the hang. But it must then call / read > something else and I don't think it can find it. Not sure why it doesn't > produce an error message. I *think* it may be something to do with EFI > variables, but as efibootmgr doesn't work I can't explore this, despite > efirt being in the kernel. > > Suggestions received welcomed, and new suggestions / leads to follow also > very much welcomed. > > /H > > > On 23 October 2018 at 21:33, Harry Newton wrote: > > > Right ... I've the binaries in /boot, freshly made. This might be a si= lly > > question ... do I not need to copy them (or dd the boot1.efifat image) = to > > the EFI partition ? > > > > /H > > > > On 23 October 2018 at 21:30, Toomas Soome wrote: > > > >> you should have the binaries in boot - just ln (or copy) one to loader= .efi > >> > >> rgds, > >> toomas > >> > >> > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: > >> > >> Yes ... so as everything is built, can I just alter LOADER_DEFAULT_INT= ERP > >> in /etc/make.conf and then reinstall just the loader and boot parts on= to > >> the UEFI partition ? If so, how ? > >> > >> > >> On 23 October 2018 at 21:17, Toomas Soome wrote: > >> > >>> ok, in that case I=E2=80=99d suggest to test out if forth based one i= s still > >>> working - at least you can get the bootable system. And then there is= a > >>> chance to debug the lua version too (note it should be possible to ch= ain > >>> /boot/loader_lua.efi). > >>> > >>> rgds, > >>> toomas > >>> > >>> > On 23 Oct 2018, at 23:08, Harry Newton wrote: > >>> > > >>> > So it's got FORTH in it, but my loader is lua based, and also doesn= 't > >>> > appear to read loader.rc. > >>> > > >>> > /H > >>> > > >>> > On 23 October 2018 at 21:03, Toomas Soome wrote: > >>> > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? > >>> >> > >>> >> rgds, > >>> >> toomas > >>> >> > >>> >> > >>> >> On 23 Oct 2018, at 23:01, Harry Newton wrote: > >>> >> > >>> >> If boot menu is the screen where you get the options for various > >>> kernels > >>> >> and the picture of the daemon head, no. It stops at the point in = my > >>> email > >>> >> =E2=80=94 though not as I said just before the kernel is loaded bu= t in point > >>> of > >>> >> fact before the menu. > >>> >> > >>> >> I've also rebuilt the kernel and still can't use efibootmgr which = is > >>> >> puzzling me. > >>> >> > >>> >> /H > >>> >> > >>> >> > >>> >> On 23 October 2018 at 20:56, Toomas Soome wrote: > >>> >> > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, then = type > >>> >>> start - if its bootfort based loader, it will load the kernel and > >>> modules. > >>> >>> lsmod will then list the loaded files. > >>> >>> > >>> >>> If the loader prompt is still usable, then next command would be: > >>> boot > >>> >>> > >>> >>> rgds, > >>> >>> toomas > >>> >>> > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton wrote: > >>> >>>> > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BETA= 1 > >>> >>> r339529 > >>> >>>> by source. Have a problem with booting which hangs after: > >>> >>>> > >>> >>>>>> FreeBSD EFI boot block > >>> >>>> Loader path: /boot/loader.efi > >>> >>>> > >>> >>>> Initializing modules: ZFS UFS > >>> >>>> Probing 5 block devices ... done > >>> >>>> ZFS found the following pools: zroot > >>> >>>> UFS found no partitions > >>> >>>> Consoles: EFI console > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>> >>>> > >>> >>>> Command line arguments: loader.efi > >>> >>>> EFI version 2.31 > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) > >>> >>>> Console: efi(0) > >>> >>>> Load Path: HD(4, GPT [ ... ] > >>> >>>> Load Device: Pci Root [ ... ] > >>> >>>> Boot Current: 0001 > >>> >>>> Boot Order: 0001 [x] > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>> >>>> - > >>> >>>> > >>> >>>> So it gets into loader.efi which runs but stops I think just bef= ore > >>> >>> loading > >>> >>>> the kernel. Partitions: > >>> >>>> > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) > >>> >>>> 40 1600 1 efi (800K) > >>> >>>> 1640 1024 2 freebsd-boot (512K) > >>> >>>> 2664 1432 - free - (716K) > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) > >>> >>>> 250068992 648 - free - (324K) > >>> >>>> > >>> >>>> and the EFI partition is FAT 12. > >>> >>>> > >>> >>>> I can't provide (at the moment) any output from efibootmgr: > >>> >>>> > >>> >>>> root@gryphon:~ # efibootmgr -v > >>> >>>> efibootmgr: efi variables not supported on this system. root? > >>> kldload > >>> >>> efirt? > >>> >>>> root@gryphon:~ # kldload efirt > >>> >>>> kldload: can't load efirt: module already loaded or in kernel > >>> >>>> > >>> >>>> which I don't understand. > >>> >>>> > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see if t= hat > >>> >>> allows > >>> >>>> me to load efirt / use efibootmgr. > >>> >>>> > >>> >>>> In the meantime, I should be very grateful for any advice. > >>> >>>> > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and droppi= ng > >>> into > >>> >>> its > >>> >>>> loader to get to the installed 12-STABLE ). > >>> >>>> > >>> >>>> /Harry > >>> >>>> _______________________________________________ > >>> >>>> freebsd-current@freebsd.org mailing list > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>> >>> reebsd.org" > >>> >>> > >>> >>> > >>> >> > >>> >> > >>> >> -- > >>> >> Harry Newton > >>> >> > >>> >> > >>> >> > >>> > > >>> > > >>> > -- > >>> > Harry Newton > >>> > _______________________________________________ > >>> > freebsd-current@freebsd.org mailing list > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>> reebsd.org" > >>> > >>> > >> > >> > >> -- > >> Harry Newton > >> > >> > >> > > > > > > -- > > Harry Newton > > > > > > -- > Harry Newton > _______________________________________________ > 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 Oct 23 22:52:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75584100827C for ; Tue, 23 Oct 2018 22:52:01 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 162FB74BD1 for ; Tue, 23 Oct 2018 22:52:01 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CE84A100827B; Tue, 23 Oct 2018 22:52:00 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD413100827A for ; Tue, 23 Oct 2018 22:52:00 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7097F74BBD for ; Tue, 23 Oct 2018 22:52:00 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io1-f42.google.com (mail-io1-f42.google.com [209.85.166.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 54B6F25BFF for ; Tue, 23 Oct 2018 22:52:00 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io1-f42.google.com with SMTP id n18-v6so1950334ioa.9 for ; Tue, 23 Oct 2018 15:52:00 -0700 (PDT) X-Gm-Message-State: AGRZ1gIWc58dsrHfnKVBC4C2z2SzNDURd7sKfV3Aa4PBF3UI3Jn/KnAa qBxYo0jp7wmB/a1DjcTN8jE6Q4svZpCmUTfD/pA= X-Google-Smtp-Source: AJdET5cA7nZeiaB7gN+byPaKBS82YJLl7+76a+ve/mlYS+ht98r+d1UCGqyIhams8m0eOKk8iFa4em/BMc0Al5MZqIM= X-Received: by 2002:a6b:db12:: with SMTP id t18-v6mr13028000ioc.132.1540335119798; Tue, 23 Oct 2018 15:51:59 -0700 (PDT) MIME-Version: 1.0 References: <20181023092053.GA22982@x2.osted.lan> In-Reply-To: <20181023092053.GA22982@x2.osted.lan> From: Matthew Macy Date: Tue, 23 Oct 2018 15:51:48 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: mtx_lock() by idle thread ... mutex igb0 @ ../../../net/iflib.c:2084 To: Peter Holm Cc: current@freebsd.org 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: Tue, 23 Oct 2018 22:52:01 -0000 Will fix. On Tue, Oct 23, 2018 at 2:21 AM Peter Holm wrote: > > Feeding entropy: . > lo0: link state changed to UP > panic: mtx_lock() by idle thread 0xfffff800036ac000 on sleep mutex igb0 @ ../../../net/iflib.c:2084 > cpuid = 4 > time = 1540286062 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe007876e610 > vpanic() at vpanic+0x1a3/frame 0xfffffe007876e670 > panic() at panic+0x43/frame 0xfffffe007876e6d0 > __mtx_lock_flags() at __mtx_lock_flags+0x15a/frame 0xfffffe007876e720 > iflib_admin_intr_deferred() at iflib_admin_intr_deferred+0x2a/frame 0xfffffe007876e750 > em_msix_link() at em_msix_link+0x84/frame 0xfffffe007876e780 > iflib_fast_intr_ctx() at iflib_fast_intr_ctx+0x21/frame 0xfffffe007876e7a0 > intr_event_handle() at intr_event_handle+0xbb/frame 0xfffffe007876e7f0 > intr_execute_handlers() at intr_execute_handlers+0x58/frame 0xfffffe007876e820 > lapic_handle_intr() at lapic_handle_intr+0x5f/frame 0xfffffe007876e840 > Xapic_isr1() at Xapic_isr1+0xd9/frame 0xfffffe007876e840 > --- interrupt, rip = 0xffffffff811e6be6, rsp = 0xfffffe007876e910, rbp = 0xfffffe007876e910 --- > acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfffffe007876e910 > acpi_cpu_idle() at acpi_cpu_idle+0x23d/frame 0xfffffe007876e960 > cpu_idle_acpi() at cpu_idle_acpi+0x3f/frame 0xfffffe007876e980 > cpu_idle() at cpu_idle+0xa7/frame 0xfffffe007876e9a0 > sched_idletd() at sched_idletd+0x517/frame 0xfffffe007876ea70 > fork_exit() at fork_exit+0x84/frame 0xfffffe007876eab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe007876eab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 11 tid 100007 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> x/s version > version: FreeBSD 13.0-CURRENT r339638 PHO-GENERIC\012 > db> > -- > Peter > _______________________________________________ > 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 Wed Oct 24 00:06:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D79F1038079 for ; Wed, 24 Oct 2018 00:06:41 +0000 (UTC) (envelope-from miwi.fbsd@gmail.com) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC8CB77CA2 for ; Wed, 24 Oct 2018 00:06:40 +0000 (UTC) (envelope-from miwi.fbsd@gmail.com) Received: by mail-lj1-f172.google.com with SMTP id z21-v6so3071534ljz.0 for ; Tue, 23 Oct 2018 17:06:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7qFcfV8QHCiNpPVjINvlhtOH3Kf3n2LWwXSAkhBSlXs=; b=b2tDD17Q102PGzUB/NKq5RRDBSM2hkInP5BulBy90yTGje3YWAcnmNaqN9nG7J/WV8 WwSyMR4acXW2HWvS0FTLgB6N5RO67jF6+0DWe8YVFK2wzFZGJi5M7CxrasiM6G8Ip7Ej +ObF9jN8PCYQBQaP7/EB1WcDIyVMPp4SCzdbzSZFRyADs/pBbSYKkrNVgL7Z3O+71yDw UWFH2eKFxAI5RnYw3U9BdZN6INREQ034M9iPzWgXAB14VD25xR307rEg/KLY12TnouDd jzdiXNI2S7qxxr4Z9X5hKh54ipZxGi4crZpK74ABtiNoWmoOyJHTCyv67pW9RTNgS4uE 1uhQ== X-Gm-Message-State: AGRZ1gI55ahkGbSB5Zt/PV3U8Ldq8SYPtSFyd4qwpUhJRYi1yRdYM16K GNniezYpWrqXLXQdGuHhaom3HJktP8rkGb1GWwFX2lqs X-Google-Smtp-Source: AJdET5c0jijGUOXxUGjPVbXrlNV+lXzpb21hsodSIMDVdygGU2CrF0WjoYnaQBuly4fRiDLlsKRxPVZ2ipswQ0otOAI= X-Received: by 2002:a2e:88da:: with SMTP id a26-v6mr202779ljk.85.1540339598876; Tue, 23 Oct 2018 17:06:38 -0700 (PDT) MIME-Version: 1.0 From: Martin Wilke Date: Wed, 24 Oct 2018 08:06:27 +0800 Message-ID: Subject: build is broken To: freebsd-current@freebsd.org 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, 24 Oct 2018 00:06:41 -0000 as of rev: 339671 build fails https://dpaste.de/NCeV/raw - Miwi -- +-----------------oOO--(_)--OOo-------------------------+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest From owner-freebsd-current@freebsd.org Wed Oct 24 00:11:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDF6910386FE for ; Wed, 24 Oct 2018 00:11:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7839E7834A for ; Wed, 24 Oct 2018 00:11:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x932.google.com with SMTP id g10so382415uak.5 for ; Tue, 23 Oct 2018 17:11:30 -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=fAVeD8R0h78PgUtNIfVmuDOAkIx8HvuY9VcgUTk9o0M=; b=om/xa/07WjP6rIy5CrCeBuIHdTZxGkCJ7bjjzjfg1+hN2VwnE1B/ICyPdgp8AYhFZP 5Ot3q3I/rWvVYP9aeqxe132vs0SwsEvAAo+ZmyU41AAkLz7XTwz9tCfoBgNqgzVj4whF elWgLiTzQszkNyKcNaL8W+CFPZnzEKXAsONOskpwZOGM8dGs+vfQxXWQyOki5ATK8bOi abXJbZkijRtNNsEXwDyFCl+fLN3gif10+uc0InarJR03gxNmUqZp4pKhKWmGWTe/Ea4+ t+N1iQrs3pCgXi4eWTUe45Eo+PacY2apQzV1I0j6cEAfchZwxAlmJt7rzaddpb2uHZH1 eKMw== 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=fAVeD8R0h78PgUtNIfVmuDOAkIx8HvuY9VcgUTk9o0M=; b=sDQddlfB5rmVcYTdY3IvQuj9HZVOdgH881Kjw6KlQd6cj8rUs+ZovfY6cP5oG1yGSA IRfDpyxVm1y6qJh0347Mmtw/z7UhtDRYS9AKoi8LNup7Fsfy8PMtfb28qezG031KCFej VgmtZlnzYyHkPo2ag6MaGowU+t9rF9dE9t7d290Jrjh7YscaqSMjxVyaLy4g4XobSqeF QxDnC3OgO/8KeEiXvk2XweEMSeiZPpxtNc+B8zcagSNQ/Q3N8G1Ov9F1ft4XEeJLd863 kZ6Nq6fcfkIX2FTwI+XPqJtgWLhWANW8UQRlq2vKioxYbSAeQjldjTpkE3z7LikBqK6w GCPQ== X-Gm-Message-State: AGRZ1gIeU2qezEWlqzbsMKrLQnHf35ASnvDAnCpTkwsBmLYex/Qq2Xxf u3foM5z8fOCiUHvWCKP2fLFz08O6cziKvHtA3BpbGg== X-Google-Smtp-Source: AJdET5fmF1vcguMNWA4D+C6GxVIGwZuK6qucduVLz6iChDiac5YWI2814YJ65CkLKkC15kumafgDTTMjHHcrniLvzlo= X-Received: by 2002:ab0:1089:: with SMTP id d9mr192645uab.42.1540339889904; Tue, 23 Oct 2018 17:11:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Tue, 23 Oct 2018 18:11:18 -0600 Message-ID: Subject: Re: build is broken To: Martin Wilke Cc: FreeBSD Current 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, 24 Oct 2018 00:11:31 -0000 Konstantin fixed it a few minutes ago. Warner On Tue, Oct 23, 2018, 6:09 PM Martin Wilke wrote: > as of rev: 339671 > > build fails > > https://dpaste.de/NCeV/raw > > - Miwi > -- > +-----------------oOO--(_)--OOo-------------------------+ > With best Regards, > Martin Wilke (miwi_(at)_FreeBSD.org) > > Mess with the Best, Die like the Rest > _______________________________________________ > 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 Wed Oct 24 00:21:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC81F1038F94 for ; Wed, 24 Oct 2018 00:21:09 +0000 (UTC) (envelope-from miwi.fbsd@gmail.com) Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3265478F78 for ; Wed, 24 Oct 2018 00:21:09 +0000 (UTC) (envelope-from miwi.fbsd@gmail.com) Received: by mail-lf1-f41.google.com with SMTP id q6-v6so1829204lfh.9 for ; Tue, 23 Oct 2018 17:21:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Otbvub7FYSeHXU6L4hvq710gq7CZgKGaqTUgdV270rE=; b=g6h7vGr9m0tveSj+ok9a15iDJLvo84G9Psgt9/dMJzDDy9d1/FOjz2yLIqRdb0Ij/Z d7fOw9vrJMvLQeSJ6ChIyCxYgDp24LQEM6Tqu+iCS6CAN7zM3xegE6kBE03V0iqBGip1 LlIcngViN72Rb/2dZ9Aj9owGGY42gdVlqV1XAT/swyk4fnfjFyYCVqjPJiafNqeDEpER gPtBWe/RJ4v0zdXdVSCJNEm8SoNLuhHrhGGoWpII6+PS1Rn7Cxq1PWTFWPnQ0W8IGWQb VBUZyrXKKubD2rV7bsOAgoOj4n532yQ/ySJU5biBCOeA40RnIzFvqyvPBkyYsJqDjdPW v9WQ== X-Gm-Message-State: ABuFfogOLtwzGHyRMEC8Lr3jOM1zUuDe7ZvqJQw5eulFS+93tOx6Umot V1ynbHbjL0pRnszab33UdZXz0OwTQ4pjOGkJH0S/nQ== X-Google-Smtp-Source: ACcGV63VsmmlbwZaRuYUuIBMYSnKUMepobM11cLTza1F1njdaPmg8G1LrsKMMhIMrnBP1t3uq15IeAGycmTeYUOBiiU= X-Received: by 2002:a19:2203:: with SMTP id i3mr13297681lfi.2.1540340461550; Tue, 23 Oct 2018 17:21:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Martin Wilke Date: Wed, 24 Oct 2018 08:20:47 +0800 Message-ID: Subject: Re: build is broken To: imp@bsdimp.com Cc: freebsd-current@freebsd.org 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, 24 Oct 2018 00:21:10 -0000 Thanks. On Wed, Oct 24, 2018 at 8:11 AM Warner Losh wrote: > Konstantin fixed it a few minutes ago. > > Warner > > On Tue, Oct 23, 2018, 6:09 PM Martin Wilke wrote: > >> as of rev: 339671 >> >> build fails >> >> https://dpaste.de/NCeV/raw >> >> - Miwi >> -- >> +-----------------oOO--(_)--OOo-------------------------+ >> With best Regards, >> Martin Wilke (miwi_(at)_FreeBSD.org) >> >> Mess with the Best, Die like the Rest >> _______________________________________________ >> 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 >> " >> > -- +-----------------oOO--(_)--OOo-------------------------+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest From owner-freebsd-current@freebsd.org Wed Oct 24 13:03:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4C29107991A for ; Wed, 24 Oct 2018 13:03:40 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yb1-xb44.google.com (mail-yb1-xb44.google.com [IPv6:2607:f8b0:4864:20::b44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3540E8686E for ; Wed, 24 Oct 2018 13:03:40 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yb1-xb44.google.com with SMTP id o204-v6so2068049yba.9 for ; Wed, 24 Oct 2018 06:03:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=04P0cBdp2GX/NtJ/kH7UANBTBuw8DNOmGfXbuTfvA84=; b=eqqbvr6iC5lBlmVKlu+nEiWncnw+BFVp/Xpzt8d/OTJriCLbIQUGlDYngHugC//ARM 60vDju/npNDvjO6AbOZdy2hqTTTznQ+gqcGrbH99ZpN8ukIqOTpm3NebXoBmuLHLMvHz G6k9qSJ6yERn2qt3qFIBSDA+mzk/ejjBhUud/PBk7LFl4pzZFBmnfyXZbfj1mfAx8tu2 7yytjB2o0GgTLQKjjLNMjZSeKqTWXMszzFDoCf1PuLa4xHIU95TH9Vdqap0UP6/j7fB+ gAr47b5XNI2sVA4w1vZiW/rexIAi6vHymO8I4e+8X010Wfga8r0mJVf8sa43iIFxQdmu SdXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=04P0cBdp2GX/NtJ/kH7UANBTBuw8DNOmGfXbuTfvA84=; b=RM0qDTnJj7eWtfFJm+pqgSLdcvfFXbYQuFWsC+klDvXcwB9gQV6Pf/OYl8kcsKUfof K9xr+vhVdb5zE6S36sX17X1h2aZeU0exf8A5m/0SXMTPhfnagJcd6ycjhrGJDDbMWJ8X MNE5R8YJetm2SehWKTnxZaSUPGUnjsLHgmCM0CFmZFApeoI4LFxMinqOiw9qkvN/1mM2 gAezPq4qq022fBZB46pmYMrpufMV4E7KiqwSIa/ps7d2y0up1akSdDMQd5rr2xAbM3zk LhfQuGyMuJUvljkIBAFRJPFFpTrCKquCrab3yOx8IaIP2ZCrTzl2C+Z+SDcOVKX3maQA Vftw== X-Gm-Message-State: AGRZ1gJor7OoJYvTbETdat+lwsEjUp3gbxNT6OwVRY3RXp4pglCzXOTk 2o3Nt5r0uavIyvOzJoW0acN2bBDdFv53nPdddWlII8Uws70= X-Google-Smtp-Source: AJdET5eyUnFggbIWEePqMkqxsClJ8cNiEU/dRO3i8PvYoJhuVJJDiX5wiEl5etLXx4IXhS4uof4zphiFTlurUg7fMCc= X-Received: by 2002:a25:4d44:: with SMTP id a65-v6mr1148188ybb.481.1540365202988; Wed, 24 Oct 2018 00:13:22 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Wed, 24 Oct 2018 00:13:22 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Wed, 24 Oct 2018 08:13:22 +0100 X-Google-Sender-Auth: _vTE_HTqBLgd28q2C4YE5zJWQrw Message-ID: Subject: Re: UEFI boot hangs after loader To: Kyle Evans Cc: Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 13:03:41 -0000 Booted with the installer image makes efibootmgr to work as you said: gryphon# efibootmgr -v BootCurrent: 0002 Timeout : 2 seconds BootOrder : 0001, 0002 Boot0001* UEFI OS HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\BO= OTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null) However it (efibootmgr) hangs and doesn't return to the shell, though it is interruptible with ^C. The partition listed against Boot0001 is my efi partition. /H On 23 October 2018 at 22:51, Kyle Evans wrote: > Hi, > > I suspect 4th vs. lua has no impact here, given the output shown -- > can you throw one of the installer images [0] on some removable media > and give that a shot for booting? If that works, we can explore UEFI > variables from there. > > efibootmgr will only work on a successful UEFI boot, unfortunately- if > we didn't make uefi loader -> kernel transition, then we don't have > access to runtime services. > > Thanks, > > Kyle Evans > > [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0= / > > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: > > > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-mad= e > the > > binaries in /boot but this doesn't solve the problem. It did copy > > /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8) > > which is what is called from /boot/boot1.efi and which contains the > strings > > I see on the console before the hang. But it must then call / read > > something else and I don't think it can find it. Not sure why it doesn= 't > > produce an error message. I *think* it may be something to do with EFI > > variables, but as efibootmgr doesn't work I can't explore this, despite > > efirt being in the kernel. > > > > Suggestions received welcomed, and new suggestions / leads to follow al= so > > very much welcomed. > > > > /H > > > > > > On 23 October 2018 at 21:33, Harry Newton wrote: > > > > > Right ... I've the binaries in /boot, freshly made. This might be a > silly > > > question ... do I not need to copy them (or dd the boot1.efifat image= ) > to > > > the EFI partition ? > > > > > > /H > > > > > > On 23 October 2018 at 21:30, Toomas Soome wrote: > > > > > >> you should have the binaries in boot - just ln (or copy) one to > loader.efi > > >> > > >> rgds, > > >> toomas > > >> > > >> > > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: > > >> > > >> Yes ... so as everything is built, can I just alter > LOADER_DEFAULT_INTERP > > >> in /etc/make.conf and then reinstall just the loader and boot parts > onto > > >> the UEFI partition ? If so, how ? > > >> > > >> > > >> On 23 October 2018 at 21:17, Toomas Soome wrote: > > >> > > >>> ok, in that case I=E2=80=99d suggest to test out if forth based one= is still > > >>> working - at least you can get the bootable system. And then there > is a > > >>> chance to debug the lua version too (note it should be possible to > chain > > >>> /boot/loader_lua.efi). > > >>> > > >>> rgds, > > >>> toomas > > >>> > > >>> > On 23 Oct 2018, at 23:08, Harry Newton wrote: > > >>> > > > >>> > So it's got FORTH in it, but my loader is lua based, and also > doesn't > > >>> > appear to read loader.rc. > > >>> > > > >>> > /H > > >>> > > > >>> > On 23 October 2018 at 21:03, Toomas Soome wrote: > > >>> > > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? > > >>> >> > > >>> >> rgds, > > >>> >> toomas > > >>> >> > > >>> >> > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton wrote: > > >>> >> > > >>> >> If boot menu is the screen where you get the options for various > > >>> kernels > > >>> >> and the picture of the daemon head, no. It stops at the point i= n > my > > >>> email > > >>> >> =E2=80=94 though not as I said just before the kernel is loaded = but in > point > > >>> of > > >>> >> fact before the menu. > > >>> >> > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr whic= h > is > > >>> >> puzzling me. > > >>> >> > > >>> >> /H > > >>> >> > > >>> >> > > >>> >> On 23 October 2018 at 20:56, Toomas Soome wrote: > > >>> >> > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, the= n > type > > >>> >>> start - if its bootfort based loader, it will load the kernel a= nd > > >>> modules. > > >>> >>> lsmod will then list the loaded files. > > >>> >>> > > >>> >>> If the loader prompt is still usable, then next command would b= e: > > >>> boot > > >>> >>> > > >>> >>> rgds, > > >>> >>> toomas > > >>> >>> > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton > wrote: > > >>> >>>> > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to > 12.0-BETA1 > > >>> >>> r339529 > > >>> >>>> by source. Have a problem with booting which hangs after: > > >>> >>>> > > >>> >>>>>> FreeBSD EFI boot block > > >>> >>>> Loader path: /boot/loader.efi > > >>> >>>> > > >>> >>>> Initializing modules: ZFS UFS > > >>> >>>> Probing 5 block devices ... done > > >>> >>>> ZFS found the following pools: zroot > > >>> >>>> UFS found no partitions > > >>> >>>> Consoles: EFI console > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > > >>> >>>> > > >>> >>>> Command line arguments: loader.efi > > >>> >>>> EFI version 2.31 > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) > > >>> >>>> Console: efi(0) > > >>> >>>> Load Path: HD(4, GPT [ ... ] > > >>> >>>> Load Device: Pci Root [ ... ] > > >>> >>>> Boot Current: 0001 > > >>> >>>> Boot Order: 0001 [x] > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > > >>> >>>> - > > >>> >>>> > > >>> >>>> So it gets into loader.efi which runs but stops I think just > before > > >>> >>> loading > > >>> >>>> the kernel. Partitions: > > >>> >>>> > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) > > >>> >>>> 40 1600 1 efi (800K) > > >>> >>>> 1640 1024 2 freebsd-boot (512K) > > >>> >>>> 2664 1432 - free - (716K) > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) > > >>> >>>> 250068992 648 - free - (324K) > > >>> >>>> > > >>> >>>> and the EFI partition is FAT 12. > > >>> >>>> > > >>> >>>> I can't provide (at the moment) any output from efibootmgr: > > >>> >>>> > > >>> >>>> root@gryphon:~ # efibootmgr -v > > >>> >>>> efibootmgr: efi variables not supported on this system. root? > > >>> kldload > > >>> >>> efirt? > > >>> >>>> root@gryphon:~ # kldload efirt > > >>> >>>> kldload: can't load efirt: module already loaded or in kernel > > >>> >>>> > > >>> >>>> which I don't understand. > > >>> >>>> > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see if > that > > >>> >>> allows > > >>> >>>> me to load efirt / use efibootmgr. > > >>> >>>> > > >>> >>>> In the meantime, I should be very grateful for any advice. > > >>> >>>> > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and > dropping > > >>> into > > >>> >>> its > > >>> >>>> loader to get to the installed 12-STABLE ). > > >>> >>>> > > >>> >>>> /Harry > > >>> >>>> _______________________________________________ > > >>> >>>> freebsd-current@freebsd.org mailing list > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>> >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@= f > > >>> >>> reebsd.org" > > >>> >>> > > >>> >>> > > >>> >> > > >>> >> > > >>> >> -- > > >>> >> Harry Newton > > >>> >> > > >>> >> > > >>> >> > > >>> > > > >>> > > > >>> > -- > > >>> > Harry Newton > > >>> > _______________________________________________ > > >>> > freebsd-current@freebsd.org mailing list > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > > >>> reebsd.org" > > >>> > > >>> > > >> > > >> > > >> -- > > >> Harry Newton > > >> > > >> > > >> > > > > > > > > > -- > > > Harry Newton > > > > > > > > > > > -- > > Harry Newton > > _______________________________________________ > > 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" > --=20 Harry Newton From owner-freebsd-current@freebsd.org Wed Oct 24 13:14:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7692107B4E5 for ; Wed, 24 Oct 2018 13:14:26 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc43.google.com (mail-yw1-xc43.google.com [IPv6:2607:f8b0:4864:20::c43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B18789BCF for ; Wed, 24 Oct 2018 13:14:26 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc43.google.com with SMTP id 135-v6so2025351ywo.8 for ; Wed, 24 Oct 2018 06:14:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=h0tI2QlySqKcnRnPXB4ML1l/hOJIfWPVHLRjarz2lVc=; b=0PICO4KGWzG9h0Bi7rUSfR8YS+cv3CNhlM+Mp0MV2FbLMyY0u8jxEDCff/BPABFcsE +5lZxNRDDbz46AbUvfcaD0iuFfbIwdZsEXWdvcO/eeKD4VnaKtUN+s69E6wOwn4E+tBr qUcnpjv5TvoBg7B4k6u5Qe3g9lquY8oN3FeybNzflJCarz7JxxrrvkCvBwYEyZ00HcfS ZZ/cEs6S4TWxIxk04Rd+6FY1lYD7Em1MgL+XGu/6hj/kESTFcKKAh4BIFvV6a/9eaarY PMUzOG/jK5c2v/JcQ1MdPP/05wZFLD2rhWITkN+a5xZGmjA9xCIPmLE2929ClrfNStPA nmlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=h0tI2QlySqKcnRnPXB4ML1l/hOJIfWPVHLRjarz2lVc=; b=ETbIWkE+VWkmnWWoGGShuAZ2r24jB09IUgNeO9CvIhP9q8HBF/d/iy6FhzxoU9DYXy fUuGpgq4ANFK4Vako0A6kK+6PqkU5GLhX3JFpQao96iKsuTK59hr+0NIOPtqivJFL0nd BsoJh7obdV8sKDt9SoQvAdwPTu80+zc5spN75kjufd9zn1LaGMT5jh3njnvu0Umt/Wmd L/NH0DENpoTUgAkobxqmteo1e3r+eT9MF9IUKf6KirYFIbI+ml3ftC8UFomTnWZc7Ms6 Mm4HsJ6nI1pGgea+G9AxsHn7y4LEl0pxXOKdVxiWqB8a8zfE9dD1KVv1Uft1gqTUa3BH lKHA== X-Gm-Message-State: AGRZ1gIzB2nqOfSdR/mGR88xlhY2FNUFzx9lGoE524Clu4QtysA9yuyV /8UtFLYl1Utz6zI90u1PBMtbnvSzQ2bQnRVunUKlig== X-Google-Smtp-Source: AJdET5cycVolRuJlXawKL2E7Ts1D/bbAha027F2FvVIwHB78KMIi22+z3Xk3QqiTgNAQt3NqLo99MzX4fP7pF7ey6Hc= X-Received: by 2002:a0d:d705:: with SMTP id z5-v6mr1263222ywd.22.1540367755287; Wed, 24 Oct 2018 00:55:55 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:e0cd:0:0:0:0:0 with HTTP; Wed, 24 Oct 2018 00:55:54 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Wed, 24 Oct 2018 08:55:54 +0100 X-Google-Sender-Auth: 80HR668uku2P1i0Nu8TfwF9qZLg Message-ID: Subject: Re: UEFI boot hangs after loader To: Kyle Evans Cc: Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 13:14:27 -0000 Re the efibootmgr hang: it appears to be in / under the call to efidp_format_device_path() in efibootmgr.c which is called with -v. Without -v: gryphon# efibootmgr BootCurrent: 0002 Timeout : 2 seconds BootOrder : 0001, 0002 Boot0001* UEFI OS + Boot0002* UEFI: USB Flash Memory1.00 gryphon# On 24 October 2018 at 08:13, Harry Newton wrote: > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS HD(1,GPT,b19ccd5d-7c6a-11e7- > ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\BOOTX64.EFI) > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > However it (efibootmgr) hangs and doesn't return to the shell, though it > is interruptible with ^C. > > The partition listed against Boot0001 is my efi partition. > > /H > > On 23 October 2018 at 22:51, Kyle Evans wrote: > >> Hi, >> >> I suspect 4th vs. lua has no impact here, given the output shown -- >> can you throw one of the installer images [0] on some removable media >> and give that a shot for booting? If that works, we can explore UEFI >> variables from there. >> >> efibootmgr will only work on a successful UEFI boot, unfortunately- if >> we didn't make uefi loader -> kernel transition, then we don't have >> access to runtime services. >> >> Thanks, >> >> Kyle Evans >> >> [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IM >> AGES/12.0/ >> >> On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: >> > >> > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-ma= de >> the >> > binaries in /boot but this doesn't solve the problem. It did copy >> > /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8= ) >> > which is what is called from /boot/boot1.efi and which contains the >> strings >> > I see on the console before the hang. But it must then call / read >> > something else and I don't think it can find it. Not sure why it >> doesn't >> > produce an error message. I *think* it may be something to do with EF= I >> > variables, but as efibootmgr doesn't work I can't explore this, despit= e >> > efirt being in the kernel. >> > >> > Suggestions received welcomed, and new suggestions / leads to follow >> also >> > very much welcomed. >> > >> > /H >> > >> > >> > On 23 October 2018 at 21:33, Harry Newton wrote: >> > >> > > Right ... I've the binaries in /boot, freshly made. This might be a >> silly >> > > question ... do I not need to copy them (or dd the boot1.efifat >> image) to >> > > the EFI partition ? >> > > >> > > /H >> > > >> > > On 23 October 2018 at 21:30, Toomas Soome wrote: >> > > >> > >> you should have the binaries in boot - just ln (or copy) one to >> loader.efi >> > >> >> > >> rgds, >> > >> toomas >> > >> >> > >> >> > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: >> > >> >> > >> Yes ... so as everything is built, can I just alter >> LOADER_DEFAULT_INTERP >> > >> in /etc/make.conf and then reinstall just the loader and boot parts >> onto >> > >> the UEFI partition ? If so, how ? >> > >> >> > >> >> > >> On 23 October 2018 at 21:17, Toomas Soome wrote: >> > >> >> > >>> ok, in that case I=E2=80=99d suggest to test out if forth based on= e is still >> > >>> working - at least you can get the bootable system. And then there >> is a >> > >>> chance to debug the lua version too (note it should be possible to >> chain >> > >>> /boot/loader_lua.efi). >> > >>> >> > >>> rgds, >> > >>> toomas >> > >>> >> > >>> > On 23 Oct 2018, at 23:08, Harry Newton wrote: >> > >>> > >> > >>> > So it's got FORTH in it, but my loader is lua based, and also >> doesn't >> > >>> > appear to read loader.rc. >> > >>> > >> > >>> > /H >> > >>> > >> > >>> > On 23 October 2018 at 21:03, Toomas Soome wrote: >> > >>> > >> > >>> >> hm. in that case, whats the content of /boot/loader.rc ? >> > >>> >> >> > >>> >> rgds, >> > >>> >> toomas >> > >>> >> >> > >>> >> >> > >>> >> On 23 Oct 2018, at 23:01, Harry Newton wrote= : >> > >>> >> >> > >>> >> If boot menu is the screen where you get the options for variou= s >> > >>> kernels >> > >>> >> and the picture of the daemon head, no. It stops at the point >> in my >> > >>> email >> > >>> >> =E2=80=94 though not as I said just before the kernel is loaded= but in >> point >> > >>> of >> > >>> >> fact before the menu. >> > >>> >> >> > >>> >> I've also rebuilt the kernel and still can't use efibootmgr >> which is >> > >>> >> puzzling me. >> > >>> >> >> > >>> >> /H >> > >>> >> >> > >>> >> >> > >>> >> On 23 October 2018 at 20:56, Toomas Soome wrote= : >> > >>> >> >> > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, >> then type >> > >>> >>> start - if its bootfort based loader, it will load the kernel >> and >> > >>> modules. >> > >>> >>> lsmod will then list the loaded files. >> > >>> >>> >> > >>> >>> If the loader prompt is still usable, then next command would >> be: >> > >>> boot >> > >>> >>> >> > >>> >>> rgds, >> > >>> >>> toomas >> > >>> >>> >> > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton >> wrote: >> > >>> >>>> >> > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >> 12.0-BETA1 >> > >>> >>> r339529 >> > >>> >>>> by source. Have a problem with booting which hangs after: >> > >>> >>>> >> > >>> >>>>>> FreeBSD EFI boot block >> > >>> >>>> Loader path: /boot/loader.efi >> > >>> >>>> >> > >>> >>>> Initializing modules: ZFS UFS >> > >>> >>>> Probing 5 block devices ... done >> > >>> >>>> ZFS found the following pools: zroot >> > >>> >>>> UFS found no partitions >> > >>> >>>> Consoles: EFI console >> > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >> > >>> >>>> >> > >>> >>>> Command line arguments: loader.efi >> > >>> >>>> EFI version 2.31 >> > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) >> > >>> >>>> Console: efi(0) >> > >>> >>>> Load Path: HD(4, GPT [ ... ] >> > >>> >>>> Load Device: Pci Root [ ... ] >> > >>> >>>> Boot Current: 0001 >> > >>> >>>> Boot Order: 0001 [x] >> > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >> > >>> >>>> - >> > >>> >>>> >> > >>> >>>> So it gets into loader.efi which runs but stops I think just >> before >> > >>> >>> loading >> > >>> >>>> the kernel. Partitions: >> > >>> >>>> >> > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) >> > >>> >>>> 40 1600 1 efi (800K) >> > >>> >>>> 1640 1024 2 freebsd-boot (512K) >> > >>> >>>> 2664 1432 - free - (716K) >> > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) >> > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) >> > >>> >>>> 250068992 648 - free - (324K) >> > >>> >>>> >> > >>> >>>> and the EFI partition is FAT 12. >> > >>> >>>> >> > >>> >>>> I can't provide (at the moment) any output from efibootmgr: >> > >>> >>>> >> > >>> >>>> root@gryphon:~ # efibootmgr -v >> > >>> >>>> efibootmgr: efi variables not supported on this system. root? >> > >>> kldload >> > >>> >>> efirt? >> > >>> >>>> root@gryphon:~ # kldload efirt >> > >>> >>>> kldload: can't load efirt: module already loaded or in kernel >> > >>> >>>> >> > >>> >>>> which I don't understand. >> > >>> >>>> >> > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see i= f >> that >> > >>> >>> allows >> > >>> >>>> me to load efirt / use efibootmgr. >> > >>> >>>> >> > >>> >>>> In the meantime, I should be very grateful for any advice. >> > >>> >>>> >> > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and >> dropping >> > >>> into >> > >>> >>> its >> > >>> >>>> loader to get to the installed 12-STABLE ). >> > >>> >>>> >> > >>> >>>> /Harry >> > >>> >>>> _______________________________________________ >> > >>> >>>> freebsd-current@freebsd.org mailing list >> > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > >>> >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe= @f >> > >>> >>> reebsd.org" >> > >>> >>> >> > >>> >>> >> > >>> >> >> > >>> >> >> > >>> >> -- >> > >>> >> Harry Newton >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> > >> > >>> > >> > >>> > -- >> > >>> > Harry Newton >> > >>> > _______________________________________________ >> > >>> > freebsd-current@freebsd.org mailing list >> > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> > >>> reebsd.org" >> > >>> >> > >>> >> > >> >> > >> >> > >> -- >> > >> Harry Newton >> > >> >> > >> >> > >> >> > > >> > > >> > > -- >> > > Harry Newton >> > > >> > >> > >> > >> > -- >> > Harry Newton >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> reebsd.org" >> > > > > -- > Harry Newton > --=20 Harry Newton From owner-freebsd-current@freebsd.org Wed Oct 24 13:42:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7882FD9AD1; Wed, 24 Oct 2018 13:42:22 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B0108EBB0; Wed, 24 Oct 2018 13:42:22 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wm1-x332.google.com with SMTP id y144-v6so5439255wmd.4; Wed, 24 Oct 2018 06:42:22 -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=FmuqzWnIzVv/GkgUrKokOkwlmAIzkEMw7rzkWhzSit4=; b=eawrv0EvyT3T5hVrDsP724sQVc5cujw80a7bg4eBuQhrPwqTMt9mfZjJg7Huseon59 pzhQrSQ4AFbe9SEIOJn8bIsZXNd40XfyaqtfYKhsefTULUTwYZb9WX1F9VCRI9920r7M 0voZ5xLNdHk/IUatNBTH+bV7FtJfeqERe26SniodweEfvPG6z+vQk3gRXPsobE5GLo25 RuDB99omQhci3Gje6YBzM56kYUAQPwQF8SvTRbJMsJ3igWpr7wFo5Y93gcVnOOn02TF4 063Rgw/ZO2YPUazCFdPk2FoPWCKl6u/qJznnM3hCvSggfCZzSuMktB3YohnLVY/4pCHM vjzA== 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=FmuqzWnIzVv/GkgUrKokOkwlmAIzkEMw7rzkWhzSit4=; b=srKHyrYvl13zyl8s22gueQ+fF/REpMe/e0e+RMNrbJIZOfVmbNFaTa2QkEnyrW4FyU fTCGcloQgSg69HGSu8u8OJXGuBvO9zTG1YvSYKqyDS0mXZJAbnEOhIY+ZLBnfHjIVVWy hUebgFogFuAgfv2MvsrS3irJl0wuLRb5PhpIfpUu0VkBCQ4ZKE2wzTTSjmNAblSOIgRv adfH8Yej9s8MkkW/doyUA/VZ6MiXlLTESIOed95Q7januSyxU/ioGfYJr+EEnF0hukqM OXU3EQoEKz35SOAPkJ5Bb5xSJdy2FA4wy2eRTib8oGA1YcGCMQi5fraXFUM0OAh5P1DP EBGg== X-Gm-Message-State: AGRZ1gKWiJJNLXKmUvY6kMLvwsFGRdaEdwBHwiXLkt0VaGWHPMoCfpy+ NYLxN7JOjoFi3xll4lZhE/wkLPBVMO6BZ3Z3Y3d44oCN X-Google-Smtp-Source: AJdET5fnHDOcz2X2ovKE3zuhiDk4mEVEwvmbeSlwz5IXAa28ZjuFVQ5varsYexn4QZlcN2mEoff95TsbsMQuK0VMqKs= X-Received: by 2002:a1c:540d:: with SMTP id i13-v6mr2145358wmb.149.1540377663172; Wed, 24 Oct 2018 03:41:03 -0700 (PDT) MIME-Version: 1.0 From: Rajesh Kumar Date: Wed, 24 Oct 2018 16:10:51 +0530 Message-ID: Subject: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: freebsd-drivers@freebsd.org, freebsd-current@freebsd.org 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, 24 Oct 2018 13:42:23 -0000 Hi, I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, I needed the following tunables to be set from loader prompt to get it booted (otherwise machine reboots continuously). hw.usb.xhci.msi=0 hw.usb.xhci.msix=0 hw.pci.enable_msi=0 hw.pci.enable_msix=0 But, when I tried with 12.0 - ALPHA4, I could able to get it booted without any tunables. So, has anything changed significantly on PCI MSI/MSI-X path? Note: I have a forum topic with my observations about the issue on 11.1/11.2 in the following thread https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ Let me know if you need any details. From owner-freebsd-current@freebsd.org Wed Oct 24 14:09:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00A07FEA4E8 for ; Wed, 24 Oct 2018 14:09:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8978B92E5A for ; Wed, 24 Oct 2018 14:09:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe33.google.com with SMTP id l6so3217856vsj.13 for ; Wed, 24 Oct 2018 07:09:23 -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=PdyTM1Px/CNs5hVfniX6WnaUXA6bblEmimeK5ZmIHZ4=; b=XAM6SKMH3yvjwhe/gBsP8PSbYJKQ01J1dhhDr+5wRLy2eQIAEpSpKyKGGHuSV4p6lW M6PIPHWahf62MN0DemPH9tD3XwEoGzBlGGy95SBA0NFlpqKD9EbSI63gv4ZV8uC7WHkL EoSnXX683s+NLkUHhi0AP+563Tdjs5Hbxzgl4rvJxEidLy+c8JXrHVDheNOG2+ULJ/6x /a6hbGuQbG5m6rpT0ozQDo6CiIgxXyE/oA0dTShH3c75u1w0yewcEKGG0ExpKm+W2jv+ L+Rs63izX+dLokYqdmQ5IoYrs6lgCifpozFFhX6gk4QtgBgWFDlbe/H0KDIuiQ1DP0A4 iOuA== 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=PdyTM1Px/CNs5hVfniX6WnaUXA6bblEmimeK5ZmIHZ4=; b=Maqd4iLZ/uy7js1Q73rfxSXRfSU+ZzDzQ33PY+n3jGH4QOEBCUPGv9BDYetULOMdWU HEst4zY6czswoCZeyqJTVeLEUjexEYipFuc40GxSLaM5fOABBA/mIPCtjH+vtnLHeW2b bBXQruH8MfMIb3Yaxie1BIooaLWhz+H/4fehNoakReIoZov1mhZW8xKr5dJha7L6MC3W +lbkLNAH4LbWuANIh5+oVQpee9Drl6MxNCj39+gS6jOMHHHzFVS53m3ykptC+1HOoNtM DMh+/NrRLgpXsi/Qmv1InVUcZ0tiWDIe1ApfqVOw/DFyXvdrrlqnRSMw/2t8mSlsU1bK c+cA== X-Gm-Message-State: AGRZ1gJ2NY5BymXhp21xbYz1G1FMn1V1fn1ORvo13PlB+ALArdYwQEnc T14IvQsCDH10pc70g38bJPD9Jj7BTmczkRI8Pf9gcubNiN0= X-Google-Smtp-Source: AJdET5dosEu/nQduRLSRuKg2WfOBglLlPmIeE6FqnGHpFdUhUINTZ8+qiL4kIhh596IRsVPphUSCKZC2kKVIxn/Y6b0= X-Received: by 2002:a67:4988:: with SMTP id d8mr1190259vsg.41.1540390162593; Wed, 24 Oct 2018 07:09:22 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> In-Reply-To: From: Warner Losh Date: Wed, 24 Oct 2018 08:09:11 -0600 Message-ID: Subject: Re: UEFI boot hangs after loader To: hn@yewbarrow.net Cc: Kyle Evans , Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 14:09:24 -0000 On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: > Booted with the installer image makes efibootmgr to work as you said: > > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds > BootOrder : 0001, 0002 > Boot0001* UEFI OS > > HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\= BOOTX64.EFI) > ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > > However it (efibootmgr) hangs and doesn't return to the shell, though it = is > interruptible with ^C. > > The partition listed against Boot0001 is my efi partition. > Can you do something like: sudo efivar -N --hex `sudo efivar | grep Boot0002` so I can have an example of a naughty boot variable? That's almost certainly causing the heart-burn. Warner > /H > > On 23 October 2018 at 22:51, Kyle Evans wrote: > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for booting? If that works, we can explore UEFI > > variables from there. > > > > efibootmgr will only work on a successful UEFI boot, unfortunately- if > > we didn't make uefi loader -> kernel transition, then we don't have > > access to runtime services. > > > > Thanks, > > > > Kyle Evans > > > > [0] > https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ > > > > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: > > > > > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-m= ade > > the > > > binaries in /boot but this doesn't solve the problem. It did copy > > > /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(= 8) > > > which is what is called from /boot/boot1.efi and which contains the > > strings > > > I see on the console before the hang. But it must then call / read > > > something else and I don't think it can find it. Not sure why it > doesn't > > > produce an error message. I *think* it may be something to do with E= FI > > > variables, but as efibootmgr doesn't work I can't explore this, despi= te > > > efirt being in the kernel. > > > > > > Suggestions received welcomed, and new suggestions / leads to follow > also > > > very much welcomed. > > > > > > /H > > > > > > > > > On 23 October 2018 at 21:33, Harry Newton wrote: > > > > > > > Right ... I've the binaries in /boot, freshly made. This might be = a > > silly > > > > question ... do I not need to copy them (or dd the boot1.efifat > image) > > to > > > > the EFI partition ? > > > > > > > > /H > > > > > > > > On 23 October 2018 at 21:30, Toomas Soome wrote: > > > > > > > >> you should have the binaries in boot - just ln (or copy) one to > > loader.efi > > > >> > > > >> rgds, > > > >> toomas > > > >> > > > >> > > > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: > > > >> > > > >> Yes ... so as everything is built, can I just alter > > LOADER_DEFAULT_INTERP > > > >> in /etc/make.conf and then reinstall just the loader and boot part= s > > onto > > > >> the UEFI partition ? If so, how ? > > > >> > > > >> > > > >> On 23 October 2018 at 21:17, Toomas Soome wrote: > > > >> > > > >>> ok, in that case I=E2=80=99d suggest to test out if forth based o= ne is > still > > > >>> working - at least you can get the bootable system. And then ther= e > > is a > > > >>> chance to debug the lua version too (note it should be possible t= o > > chain > > > >>> /boot/loader_lua.efi). > > > >>> > > > >>> rgds, > > > >>> toomas > > > >>> > > > >>> > On 23 Oct 2018, at 23:08, Harry Newton wrote= : > > > >>> > > > > >>> > So it's got FORTH in it, but my loader is lua based, and also > > doesn't > > > >>> > appear to read loader.rc. > > > >>> > > > > >>> > /H > > > >>> > > > > >>> > On 23 October 2018 at 21:03, Toomas Soome wrote= : > > > >>> > > > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? > > > >>> >> > > > >>> >> rgds, > > > >>> >> toomas > > > >>> >> > > > >>> >> > > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton > wrote: > > > >>> >> > > > >>> >> If boot menu is the screen where you get the options for vario= us > > > >>> kernels > > > >>> >> and the picture of the daemon head, no. It stops at the point > in > > my > > > >>> email > > > >>> >> =E2=80=94 though not as I said just before the kernel is loade= d but in > > point > > > >>> of > > > >>> >> fact before the menu. > > > >>> >> > > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr > which > > is > > > >>> >> puzzling me. > > > >>> >> > > > >>> >> /H > > > >>> >> > > > >>> >> > > > >>> >> On 23 October 2018 at 20:56, Toomas Soome > wrote: > > > >>> >> > > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, > then > > type > > > >>> >>> start - if its bootfort based loader, it will load the kernel > and > > > >>> modules. > > > >>> >>> lsmod will then list the loaded files. > > > >>> >>> > > > >>> >>> If the loader prompt is still usable, then next command would > be: > > > >>> boot > > > >>> >>> > > > >>> >>> rgds, > > > >>> >>> toomas > > > >>> >>> > > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton > > wrote: > > > >>> >>>> > > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to > > 12.0-BETA1 > > > >>> >>> r339529 > > > >>> >>>> by source. Have a problem with booting which hangs after: > > > >>> >>>> > > > >>> >>>>>> FreeBSD EFI boot block > > > >>> >>>> Loader path: /boot/loader.efi > > > >>> >>>> > > > >>> >>>> Initializing modules: ZFS UFS > > > >>> >>>> Probing 5 block devices ... done > > > >>> >>>> ZFS found the following pools: zroot > > > >>> >>>> UFS found no partitions > > > >>> >>>> Consoles: EFI console > > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > > > >>> >>>> > > > >>> >>>> Command line arguments: loader.efi > > > >>> >>>> EFI version 2.31 > > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) > > > >>> >>>> Console: efi(0) > > > >>> >>>> Load Path: HD(4, GPT [ ... ] > > > >>> >>>> Load Device: Pci Root [ ... ] > > > >>> >>>> Boot Current: 0001 > > > >>> >>>> Boot Order: 0001 [x] > > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EF= I > > > >>> >>>> - > > > >>> >>>> > > > >>> >>>> So it gets into loader.efi which runs but stops I think just > > before > > > >>> >>> loading > > > >>> >>>> the kernel. Partitions: > > > >>> >>>> > > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) > > > >>> >>>> 40 1600 1 efi (800K) > > > >>> >>>> 1640 1024 2 freebsd-boot (512K) > > > >>> >>>> 2664 1432 - free - (716K) > > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) > > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) > > > >>> >>>> 250068992 648 - free - (324K) > > > >>> >>>> > > > >>> >>>> and the EFI partition is FAT 12. > > > >>> >>>> > > > >>> >>>> I can't provide (at the moment) any output from efibootmgr: > > > >>> >>>> > > > >>> >>>> root@gryphon:~ # efibootmgr -v > > > >>> >>>> efibootmgr: efi variables not supported on this system. root= ? > > > >>> kldload > > > >>> >>> efirt? > > > >>> >>>> root@gryphon:~ # kldload efirt > > > >>> >>>> kldload: can't load efirt: module already loaded or in kerne= l > > > >>> >>>> > > > >>> >>>> which I don't understand. > > > >>> >>>> > > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see = if > > that > > > >>> >>> allows > > > >>> >>>> me to load efirt / use efibootmgr. > > > >>> >>>> > > > >>> >>>> In the meantime, I should be very grateful for any advice. > > > >>> >>>> > > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and > > dropping > > > >>> into > > > >>> >>> its > > > >>> >>>> loader to get to the installed 12-STABLE ). > > > >>> >>>> > > > >>> >>>> /Harry > > > >>> >>>> _______________________________________________ > > > >>> >>>> freebsd-current@freebsd.org mailing list > > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > >>> >>>> To unsubscribe, send any mail to > "freebsd-current-unsubscribe@f > > > >>> >>> reebsd.org" > > > >>> >>> > > > >>> >>> > > > >>> >> > > > >>> >> > > > >>> >> -- > > > >>> >> Harry Newton > > > >>> >> > > > >>> >> > > > >>> >> > > > >>> > > > > >>> > > > > >>> > -- > > > >>> > Harry Newton > > > >>> > _______________________________________________ > > > >>> > freebsd-current@freebsd.org mailing list > > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > > > >>> reebsd.org" > > > >>> > > > >>> > > > >> > > > >> > > > >> -- > > > >> Harry Newton > > > >> > > > >> > > > >> > > > > > > > > > > > > -- > > > > Harry Newton > > > > > > > > > > > > > > > > -- > > > Harry Newton > > > _______________________________________________ > > > 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" > > > > > > -- > Harry Newton > _______________________________________________ > 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 Wed Oct 24 15:34:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28457FEEFEE for ; Wed, 24 Oct 2018 15:34:33 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp001.me.com (pv33p00im-asmtp001.me.com [17.142.194.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A509A69C8F; Wed, 24 Oct 2018 15:34:32 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp001.me.com by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH300J00B2SAN00@pv33p00im-asmtp001.me.com>; Wed, 24 Oct 2018 06:33:42 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH300FX4BIG4L00@pv33p00im-asmtp001.me.com>; Wed, 24 Oct 2018 06:32:46 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=2 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-1807170000 definitions=main-1810240060 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-24_03:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader From: Toomas Soome In-reply-to: Date: Wed, 24 Oct 2018 09:32:39 +0300 Cc: FreeBSD Current , Kyle Evans Content-transfer-encoding: quoted-printable Message-id: <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> To: Harry Newton X-Mailer: Apple Mail (2.3445.100.39) 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, 24 Oct 2018 15:34:33 -0000 > On 24 Oct 2018, at 00:51, Kyle Evans wrote: >=20 > Hi, >=20 > I suspect 4th vs. lua has no impact here, given the output shown -- > can you throw one of the installer images [0] on some removable media > and give that a shot for booting? If that works, we can explore UEFI > variables from there. >=20 Yes, thats my guess too, my guess is that since in general the uefi boot = is working, in this case it has to be some corner case, and I would = start checking with boot variable related code; specifically, I=E2=80=99d = suggest to patch (temporarily) the find_currdev() in efi/loader/main.c = to set do_bootmgr =3D false and see if that will fix the boot. Then we = can explore what is happening in match_boot_info()=20 rgds, toomas > efibootmgr will only work on a successful UEFI boot, unfortunately- if > we didn't make uefi loader -> kernel transition, then we don't have > access to runtime services. >=20 > Thanks, >=20 > Kyle Evans >=20 > [0] = https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ >=20 > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: >>=20 >> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and = re-made the >> binaries in /boot but this doesn't solve the problem. It did copy >> /boot/loader_4th.efi to /boot/loader.efi which is (according to = uefi(8) >> which is what is called from /boot/boot1.efi and which contains the = strings >> I see on the console before the hang. But it must then call / read >> something else and I don't think it can find it. Not sure why it = doesn't >> produce an error message. I *think* it may be something to do with = EFI >> variables, but as efibootmgr doesn't work I can't explore this, = despite >> efirt being in the kernel. >>=20 >> Suggestions received welcomed, and new suggestions / leads to follow = also >> very much welcomed. >>=20 >> /H >>=20 >>=20 >> On 23 October 2018 at 21:33, Harry Newton wrote: >>=20 >>> Right ... I've the binaries in /boot, freshly made. This might be a = silly >>> question ... do I not need to copy them (or dd the boot1.efifat = image) to >>> the EFI partition ? >>>=20 >>> /H >>>=20 >>> On 23 October 2018 at 21:30, Toomas Soome wrote: >>>=20 >>>> you should have the binaries in boot - just ln (or copy) one to = loader.efi >>>>=20 >>>> rgds, >>>> toomas >>>>=20 >>>>=20 >>>> On 23 Oct 2018, at 23:22, Harry Newton wrote: >>>>=20 >>>> Yes ... so as everything is built, can I just alter = LOADER_DEFAULT_INTERP >>>> in /etc/make.conf and then reinstall just the loader and boot parts = onto >>>> the UEFI partition ? If so, how ? >>>>=20 >>>>=20 >>>> On 23 October 2018 at 21:17, Toomas Soome wrote: >>>>=20 >>>>> ok, in that case I=E2=80=99d suggest to test out if forth based = one is still >>>>> working - at least you can get the bootable system. And then there = is a >>>>> chance to debug the lua version too (note it should be possible to = chain >>>>> /boot/loader_lua.efi). >>>>>=20 >>>>> rgds, >>>>> toomas >>>>>=20 >>>>>> On 23 Oct 2018, at 23:08, Harry Newton wrote: >>>>>>=20 >>>>>> So it's got FORTH in it, but my loader is lua based, and also = doesn't >>>>>> appear to read loader.rc. >>>>>>=20 >>>>>> /H >>>>>>=20 >>>>>> On 23 October 2018 at 21:03, Toomas Soome wrote: >>>>>>=20 >>>>>>> hm. in that case, whats the content of /boot/loader.rc ? >>>>>>>=20 >>>>>>> rgds, >>>>>>> toomas >>>>>>>=20 >>>>>>>=20 >>>>>>> On 23 Oct 2018, at 23:01, Harry Newton wrote: >>>>>>>=20 >>>>>>> If boot menu is the screen where you get the options for various >>>>> kernels >>>>>>> and the picture of the daemon head, no. It stops at the point = in my >>>>> email >>>>>>> =E2=80=94 though not as I said just before the kernel is loaded = but in point >>>>> of >>>>>>> fact before the menu. >>>>>>>=20 >>>>>>> I've also rebuilt the kernel and still can't use efibootmgr = which is >>>>>>> puzzling me. >>>>>>>=20 >>>>>>> /H >>>>>>>=20 >>>>>>>=20 >>>>>>> On 23 October 2018 at 20:56, Toomas Soome wrote: >>>>>>>=20 >>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, = then type >>>>>>>> start - if its bootfort based loader, it will load the kernel = and >>>>> modules. >>>>>>>> lsmod will then list the loaded files. >>>>>>>>=20 >>>>>>>> If the loader prompt is still usable, then next command would = be: >>>>> boot >>>>>>>>=20 >>>>>>>> rgds, >>>>>>>> toomas >>>>>>>>=20 >>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton = wrote: >>>>>>>>>=20 >>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to = 12.0-BETA1 >>>>>>>> r339529 >>>>>>>>> by source. Have a problem with booting which hangs after: >>>>>>>>>=20 >>>>>>>>>>> FreeBSD EFI boot block >>>>>>>>> Loader path: /boot/loader.efi >>>>>>>>>=20 >>>>>>>>> Initializing modules: ZFS UFS >>>>>>>>> Probing 5 block devices ... done >>>>>>>>> ZFS found the following pools: zroot >>>>>>>>> UFS found no partitions >>>>>>>>> Consoles: EFI console >>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>>>>>>>>=20 >>>>>>>>> Command line arguments: loader.efi >>>>>>>>> EFI version 2.31 >>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) >>>>>>>>> Console: efi(0) >>>>>>>>> Load Path: HD(4, GPT [ ... ] >>>>>>>>> Load Device: Pci Root [ ... ] >>>>>>>>> Boot Current: 0001 >>>>>>>>> Boot Order: 0001 [x] >>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >>>>>>>>> - >>>>>>>>>=20 >>>>>>>>> So it gets into loader.efi which runs but stops I think just = before >>>>>>>> loading >>>>>>>>> the kernel. Partitions: >>>>>>>>>=20 >>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) >>>>>>>>> 40 1600 1 efi (800K) >>>>>>>>> 1640 1024 2 freebsd-boot (512K) >>>>>>>>> 2664 1432 - free - (716K) >>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) >>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) >>>>>>>>> 250068992 648 - free - (324K) >>>>>>>>>=20 >>>>>>>>> and the EFI partition is FAT 12. >>>>>>>>>=20 >>>>>>>>> I can't provide (at the moment) any output from efibootmgr: >>>>>>>>>=20 >>>>>>>>> root@gryphon:~ # efibootmgr -v >>>>>>>>> efibootmgr: efi variables not supported on this system. root? >>>>> kldload >>>>>>>> efirt? >>>>>>>>> root@gryphon:~ # kldload efirt >>>>>>>>> kldload: can't load efirt: module already loaded or in kernel >>>>>>>>>=20 >>>>>>>>> which I don't understand. >>>>>>>>>=20 >>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see if = that >>>>>>>> allows >>>>>>>>> me to load efirt / use efibootmgr. >>>>>>>>>=20 >>>>>>>>> In the meantime, I should be very grateful for any advice. >>>>>>>>>=20 >>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and = dropping >>>>> into >>>>>>>> its >>>>>>>>> loader to get to the installed 12-STABLE ). >>>>>>>>>=20 >>>>>>>>> /Harry >>>>>>>>> _______________________________________________ >>>>>>>>> freebsd-current@freebsd.org mailing list >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>>>> To unsubscribe, send any mail to = "freebsd-current-unsubscribe@f >>>>>>>> reebsd.org" >>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> -- >>>>>>> Harry Newton >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> -- >>>>>> Harry Newton >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>>>> reebsd.org" >>>>>=20 >>>>>=20 >>>>=20 >>>>=20 >>>> -- >>>> Harry Newton >>>>=20 >>>>=20 >>>>=20 >>>=20 >>>=20 >>> -- >>> Harry Newton >>>=20 >>=20 >>=20 >>=20 >> -- >> Harry Newton >> _______________________________________________ >> 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 Wed Oct 24 15:22:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61744FEE7CF for ; Wed, 24 Oct 2018 15:22:51 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F40D597AB5 for ; Wed, 24 Oct 2018 15:22:50 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B8FA9FEE7CE; Wed, 24 Oct 2018 15:22:50 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7C1BFEE7CD for ; Wed, 24 Oct 2018 15:22:50 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45DDE97AB3 for ; Wed, 24 Oct 2018 15:22:50 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mail-yb1-xb2c.google.com with SMTP id w16-v6so2288087ybp.3 for ; Wed, 24 Oct 2018 08:22:50 -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=nLjJGGqI5+3WffCj99XY0h1X7DpauW0byJJVaDZkAwU=; b=amNqr+RsXv+Qd5YKtr9ZTjMQixWLa7wLFUT2tYH0+FX1rPiWsgGeAgR8RG+f4dqa6k j6VOjVKBK5KrzSAWD/vGC+UWZS7flQJhouUVS9b1T6+QPUMT8rlhoxtpQUqYRN+C0TSr SFAyXEvOwhDVY6fuKgtzDIHgZtKx2U028UPasS5VREr6AxYBYYJCelD8+JogXm1OKEsC cd7QCsEbVC7BXYTcJJlTY1QnemszDXeXWhBVFoKxuA4u186dWccVb+AH2tWvqtkMg3L0 dvaBZxPoqpxc82slLqAUzkibLmNmFjOIt4JDcVPdSDgELnP0VIrtbPlU4UgEZtgkOdWz b9uw== 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=nLjJGGqI5+3WffCj99XY0h1X7DpauW0byJJVaDZkAwU=; b=b+ulH+TiI/WdU9qJie0WQrwv/oC+P6ay1LYLYxN1aNzQhr0q6KzhYYgvI1nn8BdlJR pBQKHqKGJMRPINBVZkwfNg+yPTBhRlyuQna31yy8O2hQJbUGX1Xm3N+qODRnCVYo3i6w 72JuUka66V4UYTenwNSqijZ4Azg7jpHuMbQCc6nNnX/nH8LZt25j4gdg3QQ10W0SEdFu I2o+Osh+9p6HVh9UVnsg0BEXt0GHhMgKHKRCbJByhFNoYsKbeKfDOi54FQ/RbFDGMPUf 5O3Qhl6TthzvVCjPxpg4CXVIW8nXUz7Kb3O/73qZ4cHLfMrLBw46NB69OrptWo1I00Sn jRlQ== X-Gm-Message-State: AGRZ1gLOdpyntB7T7gOVG/TwF1G7F6kDfsuX+jt/parBNrzAUbQOLN3c GXEePc5UcXwgEVxfhvQiNwGaKNc/e4WKZpVYDYlKAQZc X-Google-Smtp-Source: AJdET5f3AuudhKV2VwV3WOJ1gzQbqeGGfmIYjRRiqeikM3k1tR4lMJGJpCWc+4p4SS9aFf4qHvecsdnG6rEiqbKWHP4= X-Received: by 2002:a25:3753:: with SMTP id e80-v6mr2679607yba.245.1540394569194; Wed, 24 Oct 2018 08:22:49 -0700 (PDT) MIME-Version: 1.0 From: Leandro Date: Wed, 24 Oct 2018 12:22:38 -0300 Message-ID: Subject: UFS panics To: current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Wed, 24 Oct 2018 15:35:07 +0000 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, 24 Oct 2018 15:22:51 -0000 Hello, I'm seeing a kernel panic when trying to move a specific file. panic: Bad effnlink fip 0xc0000004a2c69a00, fdp 0xc000000497093be0, tdp 0xc0000004be6295a0 cpuid = 72 time = 1540283798 KDB: stack backtrace: 0xe0000000adb8dcc0: at .kdb_backtrace+0x5c 0xe0000000adb8ddf0: at .vpanic+0x1b4 0xe0000000adb8deb0: at .panic+0x38 0xe0000000adb8df40: at .ufs_readdir+0x2f24 0xe0000000adb8e1b0: at .VOP_RENAME_APV+0x190 0xe0000000adb8e240: at .kern_renameat+0x3c0 0xe0000000adb8e540: at .sys_rename+0x2c 0xe0000000adb8e5c0: at .trap+0x65c 0xe0000000adb8e780: at .powerpc_interrupt+0x290 0xe0000000adb8e820: user SC trap by 0x81010b7b8: srr1=0x900000000000f032 r1=0x3fffffffffffc490 cr=0x34000028 xer=0x20000000 ctr=0x81010b7b0 r2=0x8102c5950 KDB: enter: panic Using 'ls' or 'rm' on the file gives a "Bad file descriptor" error. Using 'cat', I get another panic, but now during open. Everything indicates that the file system is in an inconsistent state. Therefore, I would just like to ask the following: is it expected for kernel panics to happen when there are errors in the file system? Thanks, Leandro From owner-freebsd-current@freebsd.org Wed Oct 24 16:19:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C321FFB254 for ; Wed, 24 Oct 2018 16:19:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5BA56C16C for ; Wed, 24 Oct 2018 16:19:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2b.google.com with SMTP id w194so3527338vsc.11 for ; Wed, 24 Oct 2018 09:19:44 -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=A4ycx9KcXxNxfe46abSF22gKB3VHCVjNLvD30bJMg6M=; b=oQaZvl+4X34/tqLB4EtiOcylqfRuAcRidGztJva2CTjDveCkvfNDDKDp4SvAab3+py iVu5rwq2qRaxUcLIV28rtE19qqeTFEN5BrkcnvdaRT+McVfVCYZ/wZULI/TUJMVryYno NA+utaUtwV+GaXz8WC/hezeX9AryL8t/fTEIqtRC8aaQ3gJIFfOTLbXGXUxxjE9NreNd AwIOAfFKOn1fkiBUVVYWC5qVV6po0oYiKCOfEXVolnY97ZHX5XNC7+7LWpOWYqD3jAsI yLsxVmFoa+0bAdIiuosgWJ3I4uLaOD3WOtCaM2fO9sbO5yGqH+BgBqjg11p54J1d2/VY Xb2w== 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=A4ycx9KcXxNxfe46abSF22gKB3VHCVjNLvD30bJMg6M=; b=O+15Au92vDAteKXD4ANAz7E7n+JQHEvOwOWqWEP4mENjcN00s0c76vSqb0flDBOaJK FsWPRYJwtU5BbvSLfrJQ378dcBjGwJOpDFDkjd+T5rVJJzY7wCiGN0vgcrt2gdPc0LpN tn0pdlnftt3mqLXjfhEjJzzn1isucQcLupPT2NCpAHleHNAwxNnHN41VrSWxzyicRyeV wLak0uTzfgz5u9EoHZt1FE3IsKESm/NUUkkFnTSap1Gu+goGKA2WLbkC16rygIq8nptL FWn/HUUKhOvjFj6jUxOWpQNBvykI+LO1trORrT76F4lc9ZyLNGOwHqqKIw/JeAKiul6r S6ug== X-Gm-Message-State: AGRZ1gI05+oXiG6ywHER7NeEUDKG0OT2563HUM2cdDqpuhOVtnewYf9m 01SqOTZ8LaftgYxAqnZRN9whC4N5Q8DzB7La/q+YCQ== X-Google-Smtp-Source: AJdET5de5Hqux/XJu6L9xWyzy5YIYxZc/DPox4ZvWtjCwx2HrMM7+Tantb4VLSGbtiSf8VnODo0Irc1xQl9uFYiM2GQ= X-Received: by 2002:a67:2704:: with SMTP id n4mr1473208vsn.209.1540397983646; Wed, 24 Oct 2018 09:19:43 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> In-Reply-To: <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> From: Warner Losh Date: Wed, 24 Oct 2018 10:19:32 -0600 Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome Cc: Harry Newton , FreeBSD Current , Kyle Evans 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: Wed, 24 Oct 2018 16:19:45 -0000 On Wed, Oct 24, 2018 at 9:36 AM Toomas Soome wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for booting? If that works, we can explore UEFI > > variables from there. > > > > > Yes, thats my guess too, my guess is that since in general the uefi boot > is working, in this case it has to be some corner case, and I would start > checking with boot variable related code; specifically, I=E2=80=99d sugge= st to > patch (temporarily) the find_currdev() in efi/loader/main.c to set > do_bootmgr =3D false and see if that will fix the boot. Then we can explo= re > what is happening in match_boot_info() > I think there's a BootXXXX variable that we're poking our nose into and falling into cloud-koo-koo land. That's really the only substantial bit of free-form data that we're touching, and so it's the biggest risk. There's also a piece of data in efibootmgr -v hanging... There's a lot of sanity checking in the code, but we'll likely find there's one missing. Warner > rgds, > toomas > > > efibootmgr will only work on a successful UEFI boot, unfortunately- if > > we didn't make uefi loader -> kernel transition, then we don't have > > access to runtime services. > > > > Thanks, > > > > Kyle Evans > > > > [0] > https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ > > > > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: > >> > >> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-ma= de > the > >> binaries in /boot but this doesn't solve the problem. It did copy > >> /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8= ) > >> which is what is called from /boot/boot1.efi and which contains the > strings > >> I see on the console before the hang. But it must then call / read > >> something else and I don't think it can find it. Not sure why it > doesn't > >> produce an error message. I *think* it may be something to do with EF= I > >> variables, but as efibootmgr doesn't work I can't explore this, despit= e > >> efirt being in the kernel. > >> > >> Suggestions received welcomed, and new suggestions / leads to follow > also > >> very much welcomed. > >> > >> /H > >> > >> > >> On 23 October 2018 at 21:33, Harry Newton wrote: > >> > >>> Right ... I've the binaries in /boot, freshly made. This might be a > silly > >>> question ... do I not need to copy them (or dd the boot1.efifat image= ) > to > >>> the EFI partition ? > >>> > >>> /H > >>> > >>> On 23 October 2018 at 21:30, Toomas Soome wrote: > >>> > >>>> you should have the binaries in boot - just ln (or copy) one to > loader.efi > >>>> > >>>> rgds, > >>>> toomas > >>>> > >>>> > >>>> On 23 Oct 2018, at 23:22, Harry Newton wrote: > >>>> > >>>> Yes ... so as everything is built, can I just alter > LOADER_DEFAULT_INTERP > >>>> in /etc/make.conf and then reinstall just the loader and boot parts > onto > >>>> the UEFI partition ? If so, how ? > >>>> > >>>> > >>>> On 23 October 2018 at 21:17, Toomas Soome wrote: > >>>> > >>>>> ok, in that case I=E2=80=99d suggest to test out if forth based one= is still > >>>>> working - at least you can get the bootable system. And then there > is a > >>>>> chance to debug the lua version too (note it should be possible to > chain > >>>>> /boot/loader_lua.efi). > >>>>> > >>>>> rgds, > >>>>> toomas > >>>>> > >>>>>> On 23 Oct 2018, at 23:08, Harry Newton wrote: > >>>>>> > >>>>>> So it's got FORTH in it, but my loader is lua based, and also > doesn't > >>>>>> appear to read loader.rc. > >>>>>> > >>>>>> /H > >>>>>> > >>>>>> On 23 October 2018 at 21:03, Toomas Soome wrote: > >>>>>> > >>>>>>> hm. in that case, whats the content of /boot/loader.rc ? > >>>>>>> > >>>>>>> rgds, > >>>>>>> toomas > >>>>>>> > >>>>>>> > >>>>>>> On 23 Oct 2018, at 23:01, Harry Newton wrote: > >>>>>>> > >>>>>>> If boot menu is the screen where you get the options for various > >>>>> kernels > >>>>>>> and the picture of the daemon head, no. It stops at the point in > my > >>>>> email > >>>>>>> =E2=80=94 though not as I said just before the kernel is loaded b= ut in > point > >>>>> of > >>>>>>> fact before the menu. > >>>>>>> > >>>>>>> I've also rebuilt the kernel and still can't use efibootmgr which > is > >>>>>>> puzzling me. > >>>>>>> > >>>>>>> /H > >>>>>>> > >>>>>>> > >>>>>>> On 23 October 2018 at 20:56, Toomas Soome wrote: > >>>>>>> > >>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, then > type > >>>>>>>> start - if its bootfort based loader, it will load the kernel an= d > >>>>> modules. > >>>>>>>> lsmod will then list the loaded files. > >>>>>>>> > >>>>>>>> If the loader prompt is still usable, then next command would be= : > >>>>> boot > >>>>>>>> > >>>>>>>> rgds, > >>>>>>>> toomas > >>>>>>>> > >>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton wrote= : > >>>>>>>>> > >>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BET= A1 > >>>>>>>> r339529 > >>>>>>>>> by source. Have a problem with booting which hangs after: > >>>>>>>>> > >>>>>>>>>>> FreeBSD EFI boot block > >>>>>>>>> Loader path: /boot/loader.efi > >>>>>>>>> > >>>>>>>>> Initializing modules: ZFS UFS > >>>>>>>>> Probing 5 block devices ... done > >>>>>>>>> ZFS found the following pools: zroot > >>>>>>>>> UFS found no partitions > >>>>>>>>> Consoles: EFI console > >>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>>>>>>> > >>>>>>>>> Command line arguments: loader.efi > >>>>>>>>> EFI version 2.31 > >>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) > >>>>>>>>> Console: efi(0) > >>>>>>>>> Load Path: HD(4, GPT [ ... ] > >>>>>>>>> Load Device: Pci Root [ ... ] > >>>>>>>>> Boot Current: 0001 > >>>>>>>>> Boot Order: 0001 [x] > >>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>>>>>>>> - > >>>>>>>>> > >>>>>>>>> So it gets into loader.efi which runs but stops I think just > before > >>>>>>>> loading > >>>>>>>>> the kernel. Partitions: > >>>>>>>>> > >>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) > >>>>>>>>> 40 1600 1 efi (800K) > >>>>>>>>> 1640 1024 2 freebsd-boot (512K) > >>>>>>>>> 2664 1432 - free - (716K) > >>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>>>>>>> 250068992 648 - free - (324K) > >>>>>>>>> > >>>>>>>>> and the EFI partition is FAT 12. > >>>>>>>>> > >>>>>>>>> I can't provide (at the moment) any output from efibootmgr: > >>>>>>>>> > >>>>>>>>> root@gryphon:~ # efibootmgr -v > >>>>>>>>> efibootmgr: efi variables not supported on this system. root? > >>>>> kldload > >>>>>>>> efirt? > >>>>>>>>> root@gryphon:~ # kldload efirt > >>>>>>>>> kldload: can't load efirt: module already loaded or in kernel > >>>>>>>>> > >>>>>>>>> which I don't understand. > >>>>>>>>> > >>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see if > that > >>>>>>>> allows > >>>>>>>>> me to load efirt / use efibootmgr. > >>>>>>>>> > >>>>>>>>> In the meantime, I should be very grateful for any advice. > >>>>>>>>> > >>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and > dropping > >>>>> into > >>>>>>>> its > >>>>>>>>> loader to get to the installed 12-STABLE ). > >>>>>>>>> > >>>>>>>>> /Harry > >>>>>>>>> _______________________________________________ > >>>>>>>>> freebsd-current@freebsd.org mailing list > >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>>>>> reebsd.org" > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Harry Newton > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Harry Newton > >>>>>> _______________________________________________ > >>>>>> freebsd-current@freebsd.org mailing list > >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>> reebsd.org" > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Harry Newton > >>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> Harry Newton > >>> > >> > >> > >> > >> -- > >> Harry Newton > >> _______________________________________________ > >> 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" > > _______________________________________________ > 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 Wed Oct 24 16:33:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EC5DFFBF83 for ; Wed, 24 Oct 2018 16:33:59 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 201CD6D083 for ; Wed, 24 Oct 2018 16:33:59 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc29.google.com with SMTP id x185-v6so1960911ywa.0 for ; Wed, 24 Oct 2018 09:33:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5XSofmSMK++WZbCuIJNSfAO/yfP/W0ZQi+tA6JRKdwo=; b=pPWvkG3CCpPEB5K1P1TvSOHY0czIEPgxghHEaaaBkuJzccfVKG9u+P6cTsV8XhS37d VaFop6IxmqAYmBUGWyDYyqJtpJDxJlR3fUg7gbBU+07pYbUPPgWXj7SzRa0wlKWKWWfb k0YJH+waKaNqbS2Eg+xMDZlzOmoadLtV737QNELV5rZRuyekdzW96b4w5Vd20svB5FaO 2BXHagPoMfzMyCYtK5e5iBxZkjNYvQvxWNSsCIVLnB430hUMSGtbgFjRYBeZzUy3DcW6 qQ6wtAquHYUedSIGhgqgEhXFadYGetVVPmzKEChez7RaT/HSH79VnRVAebKZduyP47JV YYgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5XSofmSMK++WZbCuIJNSfAO/yfP/W0ZQi+tA6JRKdwo=; b=YA5Xn311ZNhXtY4QkgW37vxnSkoVsIXjq3eYYWoaGsFNe48uUgh1ufuie4KPpTL4Ue pNfRnXCFTAmrSfeQGCKrahVPockDHmqTulAD1YLEmwqkN5aj9Ov8fdzxeAu6xsm5VzWX hvHOxU0jAGFnpl4jDuXUGHiBhMkKTSb9v9L9t2caGKTc/8rSuGSNbcTOukZ5mfTY70xg YkuJcB7EnXSlrA29lmCNkR51aIuqGLLzDbzUBlpu4PRTjyqYnHmVbF9TrNwqt5iHShLW qA24bMK3By80Jn3CvDi870rJas4voYuAV720KEGqZMj93WHfrYtOSsJX29R0HGvmxSuv aQYQ== X-Gm-Message-State: AGRZ1gJzASUaxmD1MnMZ3BZzcyrIrWzdShnoPRtNXewad5n4Fm+CL7Bj QG/boep7uQ3u0LAKlC+r1Ykf3H5iiJr3cLvGrcy9fQ== X-Google-Smtp-Source: AJdET5e2jv0TLEx+IJ9D0m1enxzTHKJPSfvzAt41iUl9JfO78baVaCfSdhbgKa/BbewdTyrzfbUT87EhXxaeJID1OZg= X-Received: by 2002:a81:5214:: with SMTP id g20-v6mr3062541ywb.252.1540398838314; Wed, 24 Oct 2018 09:33:58 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:807:0:0:0:0:0 with HTTP; Wed, 24 Oct 2018 09:33:57 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Wed, 24 Oct 2018 17:33:57 +0100 X-Google-Sender-Auth: 20gqSsSf782uwSSoO67hcbCpxjI Message-ID: Subject: Re: UEFI boot hangs after loader To: Warner Losh Cc: Kyle Evans , Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 16:33:59 -0000 gryphon# efivar -N --hex $(efivar | grep Boot0002) 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 00e0: 7f ff 04 00 00 00 42 4f gryphon# On 24 October 2018 at 15:09, Warner Losh wrote: > > > On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: > >> Booted with the installer image makes efibootmgr to work as you said: >> >> gryphon# efibootmgr -v >> BootCurrent: 0002 >> Timeout : 2 seconds >> BootOrder : 0001, 0002 >> Boot0001* UEFI OS >> HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/ >> File(\EFI\BOOT\BOOTX64.EFI) >> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) >> >> However it (efibootmgr) hangs and doesn't return to the shell, though it >> is >> interruptible with ^C. >> >> The partition listed against Boot0001 is my efi partition. >> > > Can you do something like: > > sudo efivar -N --hex `sudo efivar | grep Boot0002` > > so I can have an example of a naughty boot variable? That's almost > certainly causing the heart-burn. > > Warner > > > >> /H >> >> On 23 October 2018 at 22:51, Kyle Evans wrote: >> >> > Hi, >> > >> > I suspect 4th vs. lua has no impact here, given the output shown -- >> > can you throw one of the installer images [0] on some removable media >> > and give that a shot for booting? If that works, we can explore UEFI >> > variables from there. >> > >> > efibootmgr will only work on a successful UEFI boot, unfortunately- if >> > we didn't make uefi loader -> kernel transition, then we don't have >> > access to runtime services. >> > >> > Thanks, >> > >> > Kyle Evans >> > >> > [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO- >> IMAGES/12.0/ >> > >> > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: >> > > >> > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-= made >> > the >> > > binaries in /boot but this doesn't solve the problem. It did copy >> > > /boot/loader_4th.efi to /boot/loader.efi which is (according to >> uefi(8) >> > > which is what is called from /boot/boot1.efi and which contains the >> > strings >> > > I see on the console before the hang. But it must then call / read >> > > something else and I don't think it can find it. Not sure why it >> doesn't >> > > produce an error message. I *think* it may be something to do with >> EFI >> > > variables, but as efibootmgr doesn't work I can't explore this, >> despite >> > > efirt being in the kernel. >> > > >> > > Suggestions received welcomed, and new suggestions / leads to follow >> also >> > > very much welcomed. >> > > >> > > /H >> > > >> > > >> > > On 23 October 2018 at 21:33, Harry Newton wrote: >> > > >> > > > Right ... I've the binaries in /boot, freshly made. This might be= a >> > silly >> > > > question ... do I not need to copy them (or dd the boot1.efifat >> image) >> > to >> > > > the EFI partition ? >> > > > >> > > > /H >> > > > >> > > > On 23 October 2018 at 21:30, Toomas Soome wrote: >> > > > >> > > >> you should have the binaries in boot - just ln (or copy) one to >> > loader.efi >> > > >> >> > > >> rgds, >> > > >> toomas >> > > >> >> > > >> >> > > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: >> > > >> >> > > >> Yes ... so as everything is built, can I just alter >> > LOADER_DEFAULT_INTERP >> > > >> in /etc/make.conf and then reinstall just the loader and boot par= ts >> > onto >> > > >> the UEFI partition ? If so, how ? >> > > >> >> > > >> >> > > >> On 23 October 2018 at 21:17, Toomas Soome wrote: >> > > >> >> > > >>> ok, in that case I=E2=80=99d suggest to test out if forth based = one is >> still >> > > >>> working - at least you can get the bootable system. And then the= re >> > is a >> > > >>> chance to debug the lua version too (note it should be possible = to >> > chain >> > > >>> /boot/loader_lua.efi). >> > > >>> >> > > >>> rgds, >> > > >>> toomas >> > > >>> >> > > >>> > On 23 Oct 2018, at 23:08, Harry Newton >> wrote: >> > > >>> > >> > > >>> > So it's got FORTH in it, but my loader is lua based, and also >> > doesn't >> > > >>> > appear to read loader.rc. >> > > >>> > >> > > >>> > /H >> > > >>> > >> > > >>> > On 23 October 2018 at 21:03, Toomas Soome >> wrote: >> > > >>> > >> > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? >> > > >>> >> >> > > >>> >> rgds, >> > > >>> >> toomas >> > > >>> >> >> > > >>> >> >> > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton >> wrote: >> > > >>> >> >> > > >>> >> If boot menu is the screen where you get the options for >> various >> > > >>> kernels >> > > >>> >> and the picture of the daemon head, no. It stops at the poin= t >> in >> > my >> > > >>> email >> > > >>> >> =E2=80=94 though not as I said just before the kernel is load= ed but in >> > point >> > > >>> of >> > > >>> >> fact before the menu. >> > > >>> >> >> > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr >> which >> > is >> > > >>> >> puzzling me. >> > > >>> >> >> > > >>> >> /H >> > > >>> >> >> > > >>> >> >> > > >>> >> On 23 October 2018 at 20:56, Toomas Soome >> wrote: >> > > >>> >> >> > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, >> then >> > type >> > > >>> >>> start - if its bootfort based loader, it will load the kerne= l >> and >> > > >>> modules. >> > > >>> >>> lsmod will then list the loaded files. >> > > >>> >>> >> > > >>> >>> If the loader prompt is still usable, then next command woul= d >> be: >> > > >>> boot >> > > >>> >>> >> > > >>> >>> rgds, >> > > >>> >>> toomas >> > > >>> >>> >> > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton >> > wrote: >> > > >>> >>>> >> > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >> > 12.0-BETA1 >> > > >>> >>> r339529 >> > > >>> >>>> by source. Have a problem with booting which hangs after: >> > > >>> >>>> >> > > >>> >>>>>> FreeBSD EFI boot block >> > > >>> >>>> Loader path: /boot/loader.efi >> > > >>> >>>> >> > > >>> >>>> Initializing modules: ZFS UFS >> > > >>> >>>> Probing 5 block devices ... done >> > > >>> >>>> ZFS found the following pools: zroot >> > > >>> >>>> UFS found no partitions >> > > >>> >>>> Consoles: EFI console >> > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >> > > >>> >>>> >> > > >>> >>>> Command line arguments: loader.efi >> > > >>> >>>> EFI version 2.31 >> > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) >> > > >>> >>>> Console: efi(0) >> > > >>> >>>> Load Path: HD(4, GPT [ ... ] >> > > >>> >>>> Load Device: Pci Root [ ... ] >> > > >>> >>>> Boot Current: 0001 >> > > >>> >>>> Boot Order: 0001 [x] >> > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.E= FI >> > > >>> >>>> - >> > > >>> >>>> >> > > >>> >>>> So it gets into loader.efi which runs but stops I think jus= t >> > before >> > > >>> >>> loading >> > > >>> >>>> the kernel. Partitions: >> > > >>> >>>> >> > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) >> > > >>> >>>> 40 1600 1 efi (800K) >> > > >>> >>>> 1640 1024 2 freebsd-boot (512K) >> > > >>> >>>> 2664 1432 - free - (716K) >> > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) >> > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) >> > > >>> >>>> 250068992 648 - free - (324K) >> > > >>> >>>> >> > > >>> >>>> and the EFI partition is FAT 12. >> > > >>> >>>> >> > > >>> >>>> I can't provide (at the moment) any output from efibootmgr: >> > > >>> >>>> >> > > >>> >>>> root@gryphon:~ # efibootmgr -v >> > > >>> >>>> efibootmgr: efi variables not supported on this system. roo= t? >> > > >>> kldload >> > > >>> >>> efirt? >> > > >>> >>>> root@gryphon:~ # kldload efirt >> > > >>> >>>> kldload: can't load efirt: module already loaded or in kern= el >> > > >>> >>>> >> > > >>> >>>> which I don't understand. >> > > >>> >>>> >> > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see >> if >> > that >> > > >>> >>> allows >> > > >>> >>>> me to load efirt / use efibootmgr. >> > > >>> >>>> >> > > >>> >>>> In the meantime, I should be very grateful for any advice. >> > > >>> >>>> >> > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and >> > dropping >> > > >>> into >> > > >>> >>> its >> > > >>> >>>> loader to get to the installed 12-STABLE ). >> > > >>> >>>> >> > > >>> >>>> /Harry >> > > >>> >>>> _______________________________________________ >> > > >>> >>>> freebsd-current@freebsd.org mailing list >> > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > > >>> >>>> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@f >> > > >>> >>> reebsd.org" >> > > >>> >>> >> > > >>> >>> >> > > >>> >> >> > > >>> >> >> > > >>> >> -- >> > > >>> >> Harry Newton >> > > >>> >> >> > > >>> >> >> > > >>> >> >> > > >>> > >> > > >>> > >> > > >>> > -- >> > > >>> > Harry Newton >> > > >>> > _______________________________________________ >> > > >>> > freebsd-current@freebsd.org mailing list >> > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@= f >> > > >>> reebsd.org" >> > > >>> >> > > >>> >> > > >> >> > > >> >> > > >> -- >> > > >> Harry Newton >> > > >> >> > > >> >> > > >> >> > > > >> > > > >> > > > -- >> > > > Harry Newton >> > > > >> > > >> > > >> > > >> > > -- >> > > Harry Newton >> > > _______________________________________________ >> > > 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" >> > >> >> >> >> -- >> Harry Newton >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> > --=20 Harry Newton From owner-freebsd-current@freebsd.org Wed Oct 24 16:55:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03542FFCED3 for ; Wed, 24 Oct 2018 16:55:49 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv33p00im-asmtp002.me.com (pv33p00im-asmtp002.me.com [17.142.194.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F5C86E53B; Wed, 24 Oct 2018 16:55:48 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.pv33p00im-asmtp002.me.com by pv33p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH300000EOOEP00@pv33p00im-asmtp002.me.com>; Wed, 24 Oct 2018 07:55:26 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by pv33p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH3009LFFC6YY40@pv33p00im-asmtp002.me.com>; Wed, 24 Oct 2018 07:55:23 +0000 (GMT) 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-1807170000 definitions=main-1810240072 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-24_04:,, signatures=0 From: Toomas Soome Message-id: <53C30F4F-07A3-4983-88A6-7A762008E109@me.com> MIME-version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: UEFI boot hangs after loader Date: Wed, 24 Oct 2018 10:55:17 +0300 In-reply-to: Cc: Kyle Evans , FreeBSD Current To: Harry Newton References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> X-Mailer: Apple Mail (2.3445.100.39) 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: Wed, 24 Oct 2018 16:55:49 -0000 > On 24 Oct 2018, at 10:13, Harry Newton wrote: >=20 > Booted with the installer image makes efibootmgr to work as you said: >=20 > gryphon# efibootmgr -v > BootCurrent: 0002 > Timeout : 2 seconds=20 > BootOrder : 0001, 0002=20 > Boot0001* UEFI OS = HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\B= OOTX64.EFI) ada0p1:/EFI/BOOT/BOOTX64.EFI (null)=20 >=20 > However it (efibootmgr) hangs and doesn't return to the shell, though = it is interruptible with ^C. >=20 > The partition listed against Boot0001 is my efi partition. My guess is that the loader.efi is hung by exactly the same reason - = there is some bad (unexpected) value, also the printed out (null) hints = about weirdness there, because we normally get (null) when NULL pointer = was passed to printf(). So either we should debug the loader.efi or = efibootmgr to identify why it is hung and fix the code to avoid it.=20 rgds, toomas >=20 > /H >=20 > On 23 October 2018 at 22:51, Kyle Evans > wrote: > Hi, >=20 > I suspect 4th vs. lua has no impact here, given the output shown -- > can you throw one of the installer images [0] on some removable media > and give that a shot for booting? If that works, we can explore UEFI > variables from there. >=20 > efibootmgr will only work on a successful UEFI boot, unfortunately- if > we didn't make uefi loader -> kernel transition, then we don't have > access to runtime services. >=20 > Thanks, >=20 > Kyle Evans >=20 > [0] = https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ = >=20 > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton > wrote: > > > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and = re-made the > > binaries in /boot but this doesn't solve the problem. It did copy > > /boot/loader_4th.efi to /boot/loader.efi which is (according to = uefi(8) > > which is what is called from /boot/boot1.efi and which contains the = strings > > I see on the console before the hang. But it must then call / read > > something else and I don't think it can find it. Not sure why it = doesn't > > produce an error message. I *think* it may be something to do with = EFI > > variables, but as efibootmgr doesn't work I can't explore this, = despite > > efirt being in the kernel. > > > > Suggestions received welcomed, and new suggestions / leads to follow = also > > very much welcomed. > > > > /H > > > > > > On 23 October 2018 at 21:33, Harry Newton > wrote: > > > > > Right ... I've the binaries in /boot, freshly made. This might be = a silly > > > question ... do I not need to copy them (or dd the boot1.efifat = image) to > > > the EFI partition ? > > > > > > /H > > > > > > On 23 October 2018 at 21:30, Toomas Soome > wrote: > > > > > >> you should have the binaries in boot - just ln (or copy) one to = loader.efi > > >> > > >> rgds, > > >> toomas > > >> > > >> > > >> On 23 Oct 2018, at 23:22, Harry Newton > wrote: > > >> > > >> Yes ... so as everything is built, can I just alter = LOADER_DEFAULT_INTERP > > >> in /etc/make.conf and then reinstall just the loader and boot = parts onto > > >> the UEFI partition ? If so, how ? > > >> > > >> > > >> On 23 October 2018 at 21:17, Toomas Soome > wrote: > > >> > > >>> ok, in that case I=E2=80=99d suggest to test out if forth based = one is still > > >>> working - at least you can get the bootable system. And then = there is a > > >>> chance to debug the lua version too (note it should be possible = to chain > > >>> /boot/loader_lua.efi). > > >>> > > >>> rgds, > > >>> toomas > > >>> > > >>> > On 23 Oct 2018, at 23:08, Harry Newton > wrote: > > >>> > > > >>> > So it's got FORTH in it, but my loader is lua based, and also = doesn't > > >>> > appear to read loader.rc. > > >>> > > > >>> > /H > > >>> > > > >>> > On 23 October 2018 at 21:03, Toomas Soome > wrote: > > >>> > > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? > > >>> >> > > >>> >> rgds, > > >>> >> toomas > > >>> >> > > >>> >> > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton > wrote: > > >>> >> > > >>> >> If boot menu is the screen where you get the options for = various > > >>> kernels > > >>> >> and the picture of the daemon head, no. It stops at the = point in my > > >>> email > > >>> >> =E2=80=94 though not as I said just before the kernel is = loaded but in point > > >>> of > > >>> >> fact before the menu. > > >>> >> > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr = which is > > >>> >> puzzling me. > > >>> >> > > >>> >> /H > > >>> >> > > >>> >> > > >>> >> On 23 October 2018 at 20:56, Toomas Soome > wrote: > > >>> >> > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, = then type > > >>> >>> start - if its bootfort based loader, it will load the = kernel and > > >>> modules. > > >>> >>> lsmod will then list the loaded files. > > >>> >>> > > >>> >>> If the loader prompt is still usable, then next command = would be: > > >>> boot > > >>> >>> > > >>> >>> rgds, > > >>> >>> toomas > > >>> >>> > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton > wrote: > > >>> >>>> > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to = 12.0-BETA1 > > >>> >>> r339529 > > >>> >>>> by source. Have a problem with booting which hangs after: > > >>> >>>> > > >>> >>>>>> FreeBSD EFI boot block > > >>> >>>> Loader path: /boot/loader.efi > > >>> >>>> > > >>> >>>> Initializing modules: ZFS UFS > > >>> >>>> Probing 5 block devices ... done > > >>> >>>> ZFS found the following pools: zroot > > >>> >>>> UFS found no partitions > > >>> >>>> Consoles: EFI console > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 > > >>> >>>> > > >>> >>>> Command line arguments: loader.efi > > >>> >>>> EFI version 2.31 > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) > > >>> >>>> Console: efi(0) > > >>> >>>> Load Path: HD(4, GPT [ ... ] > > >>> >>>> Load Device: Pci Root [ ... ] > > >>> >>>> Boot Current: 0001 > > >>> >>>> Boot Order: 0001 [x] > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] = /\EFI\BOOT\BOOTX64.EFI > > >>> >>>> - > > >>> >>>> > > >>> >>>> So it gets into loader.efi which runs but stops I think = just before > > >>> >>> loading > > >>> >>>> the kernel. Partitions: > > >>> >>>> > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) > > >>> >>>> 40 1600 1 efi (800K) > > >>> >>>> 1640 1024 2 freebsd-boot (512K) > > >>> >>>> 2664 1432 - free - (716K) > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) > > >>> >>>> 250068992 648 - free - (324K) > > >>> >>>> > > >>> >>>> and the EFI partition is FAT 12. > > >>> >>>> > > >>> >>>> I can't provide (at the moment) any output from efibootmgr: > > >>> >>>> > > >>> >>>> root@gryphon:~ # efibootmgr -v > > >>> >>>> efibootmgr: efi variables not supported on this system. = root? > > >>> kldload > > >>> >>> efirt? > > >>> >>>> root@gryphon:~ # kldload efirt > > >>> >>>> kldload: can't load efirt: module already loaded or in = kernel > > >>> >>>> > > >>> >>>> which I don't understand. > > >>> >>>> > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and see = if that > > >>> >>> allows > > >>> >>>> me to load efirt / use efibootmgr. > > >>> >>>> > > >>> >>>> In the meantime, I should be very grateful for any advice. > > >>> >>>> > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and = dropping > > >>> into > > >>> >>> its > > >>> >>>> loader to get to the installed 12-STABLE ). > > >>> >>>> > > >>> >>>> /Harry > > >>> >>>> _______________________________________________ > > >>> >>>> freebsd-current@freebsd.org = mailing list > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current = > > >>> >>>> To unsubscribe, send any mail to = "freebsd-current-unsubscribe@f > > >>> >>> reebsd.org " > > >>> >>> > > >>> >>> > > >>> >> > > >>> >> > > >>> >> -- > > >>> >> Harry Newton > > >>> >> > > >>> >> > > >>> >> > > >>> > > > >>> > > > >>> > -- > > >>> > Harry Newton > > >>> > _______________________________________________ > > >>> > freebsd-current@freebsd.org = mailing list > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current = > > >>> > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@f > > >>> reebsd.org " > > >>> > > >>> > > >> > > >> > > >> -- > > >> Harry Newton > > >> > > >> > > >> > > > > > > > > > -- > > > Harry Newton > > > > > > > > > > > -- > > Harry Newton > > _______________________________________________ > > 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 = " >=20 >=20 >=20 > --=20 > Harry Newton From owner-freebsd-current@freebsd.org Wed Oct 24 17:26:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3717FFE05C for ; Wed, 24 Oct 2018 17:26:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E7DA6FE1A for ; Wed, 24 Oct 2018 17:26:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2a.google.com with SMTP id e126so3681667vsc.9 for ; Wed, 24 Oct 2018 10:26:04 -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=BSzRdrN4P2MFNq1sP4ZqHgD7bIkbED+8QGdIj9Gaclk=; b=Du9ukhRHYu5sS61CHe7JEodsStkuNneTlXzSgqZ1Vh2G4JnJI366l9dg+uOlArLAbl Uh8RVz3ctZ9sGfE16x26OPMq82lgbtf6M71791TAJ/KaxL4Zume/NBUafvb1sRGEReeQ c4Mls95I+UzEg4fvnvq5sIP1KDr3rz6srvOwRASISrvCNYsuNvkjbzXJxl/OxJZsyR0K LkPq1g25PPdbNTfOvwYkddb6ogxQZ3mxvD483zsG3Th1w4YOxEQKaOwazOs1ibGVu/YA zrKJAolCuYMsNFhPLairKp6FHz300BArIdvqPmAyWjc7TINxbSzYTZYaIRK6J8gColji vlbQ== 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=BSzRdrN4P2MFNq1sP4ZqHgD7bIkbED+8QGdIj9Gaclk=; b=OlM4uNbA9HrDJ3vuM8ESNT1/cIGBCEfzwVvexuqOc+o4qxcLyyEk1+QunNA1eyvCoG YU1dxJh5/TwNfgkzMP/xLrRE/MT2mRRxquZN5B8ilRk9AyN8K6DuJ/kAmOlLarT6FP4x 8ODwTtbMb8ztIV0RLR9IXJn+EVxchyuQGyr0RonUGyCK5GkftEwDnt1AJY8jG79t8Yje EYb+uxgoF8XqGojZ6/Ad3VAVWiz0w4KsegVKcoeqRiZ7dwEo8JzZZR++Pifb5GNHy6Et aVLWSm183niUckKYSC8V8Yghms5PNU03wc2s/9d6p2NVeyC/Ro13ywV/kv/LL0OkoUzJ Heag== X-Gm-Message-State: AGRZ1gKmAaGBvAhfqT8DQoYyFQWDls6VUa2YszdtP8eE8n5xJweuctnp 9zetMARZw6W0fcmlE6hZyyc/WkWldVbXdNqFmztyLA== X-Google-Smtp-Source: AJdET5cbny5Dab6PnBdQGkg81fO+7bEAZhFnxpnG/uN2aIh74BJmEVNeSH6incyh2M8BssvLOrOY2BfHHwuYQRcpgms= X-Received: by 2002:a67:e86:: with SMTP id 128mr1521106vso.201.1540401963293; Wed, 24 Oct 2018 10:26:03 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> In-Reply-To: From: Warner Losh Date: Wed, 24 Oct 2018 11:25:51 -0600 Message-ID: Subject: Re: UEFI boot hangs after loader To: Harry Newton Cc: Kyle Evans , Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 17:26:05 -0000 On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > gryphon# efivar -N --hex $(efivar | grep Boot0002) > 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 > 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 > 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 > 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 > 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 > 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 > 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 > 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff > 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 > 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 > 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 > 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 > 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 > 00e0: 7f ff 04 00 00 00 42 4f > gryphon# > Perfect. I'll decode this and see if I can figure out where we're going AFU= . Warner > On 24 October 2018 at 15:09, Warner Losh wrote: > >> >> >> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: >> >>> Booted with the installer image makes efibootmgr to work as you said: >>> >>> gryphon# efibootmgr -v >>> BootCurrent: 0002 >>> Timeout : 2 seconds >>> BootOrder : 0001, 0002 >>> Boot0001* UEFI OS >>> >>> HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOO= T\BOOTX64.EFI) >>> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) >>> >>> However it (efibootmgr) hangs and doesn't return to the shell, though i= t >>> is >>> interruptible with ^C. >>> >>> The partition listed against Boot0001 is my efi partition. >>> >> >> Can you do something like: >> >> sudo efivar -N --hex `sudo efivar | grep Boot0002` >> >> so I can have an example of a naughty boot variable? That's almost >> certainly causing the heart-burn. >> >> Warner >> >> >> >>> /H >>> >>> On 23 October 2018 at 22:51, Kyle Evans wrote: >>> >>> > Hi, >>> > >>> > I suspect 4th vs. lua has no impact here, given the output shown -- >>> > can you throw one of the installer images [0] on some removable media >>> > and give that a shot for booting? If that works, we can explore UEFI >>> > variables from there. >>> > >>> > efibootmgr will only work on a successful UEFI boot, unfortunately- i= f >>> > we didn't make uefi loader -> kernel transition, then we don't have >>> > access to runtime services. >>> > >>> > Thanks, >>> > >>> > Kyle Evans >>> > >>> > [0] >>> https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ >>> > >>> > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote= : >>> > > >>> > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and >>> re-made >>> > the >>> > > binaries in /boot but this doesn't solve the problem. It did copy >>> > > /boot/loader_4th.efi to /boot/loader.efi which is (according to >>> uefi(8) >>> > > which is what is called from /boot/boot1.efi and which contains the >>> > strings >>> > > I see on the console before the hang. But it must then call / read >>> > > something else and I don't think it can find it. Not sure why it >>> doesn't >>> > > produce an error message. I *think* it may be something to do with >>> EFI >>> > > variables, but as efibootmgr doesn't work I can't explore this, >>> despite >>> > > efirt being in the kernel. >>> > > >>> > > Suggestions received welcomed, and new suggestions / leads to follo= w >>> also >>> > > very much welcomed. >>> > > >>> > > /H >>> > > >>> > > >>> > > On 23 October 2018 at 21:33, Harry Newton wrote: >>> > > >>> > > > Right ... I've the binaries in /boot, freshly made. This might b= e >>> a >>> > silly >>> > > > question ... do I not need to copy them (or dd the boot1.efifat >>> image) >>> > to >>> > > > the EFI partition ? >>> > > > >>> > > > /H >>> > > > >>> > > > On 23 October 2018 at 21:30, Toomas Soome wrote: >>> > > > >>> > > >> you should have the binaries in boot - just ln (or copy) one to >>> > loader.efi >>> > > >> >>> > > >> rgds, >>> > > >> toomas >>> > > >> >>> > > >> >>> > > >> On 23 Oct 2018, at 23:22, Harry Newton wrote: >>> > > >> >>> > > >> Yes ... so as everything is built, can I just alter >>> > LOADER_DEFAULT_INTERP >>> > > >> in /etc/make.conf and then reinstall just the loader and boot >>> parts >>> > onto >>> > > >> the UEFI partition ? If so, how ? >>> > > >> >>> > > >> >>> > > >> On 23 October 2018 at 21:17, Toomas Soome wrote: >>> > > >> >>> > > >>> ok, in that case I=E2=80=99d suggest to test out if forth based= one is >>> still >>> > > >>> working - at least you can get the bootable system. And then >>> there >>> > is a >>> > > >>> chance to debug the lua version too (note it should be possible >>> to >>> > chain >>> > > >>> /boot/loader_lua.efi). >>> > > >>> >>> > > >>> rgds, >>> > > >>> toomas >>> > > >>> >>> > > >>> > On 23 Oct 2018, at 23:08, Harry Newton >>> wrote: >>> > > >>> > >>> > > >>> > So it's got FORTH in it, but my loader is lua based, and also >>> > doesn't >>> > > >>> > appear to read loader.rc. >>> > > >>> > >>> > > >>> > /H >>> > > >>> > >>> > > >>> > On 23 October 2018 at 21:03, Toomas Soome >>> wrote: >>> > > >>> > >>> > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? >>> > > >>> >> >>> > > >>> >> rgds, >>> > > >>> >> toomas >>> > > >>> >> >>> > > >>> >> >>> > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton >>> wrote: >>> > > >>> >> >>> > > >>> >> If boot menu is the screen where you get the options for >>> various >>> > > >>> kernels >>> > > >>> >> and the picture of the daemon head, no. It stops at the >>> point in >>> > my >>> > > >>> email >>> > > >>> >> =E2=80=94 though not as I said just before the kernel is loa= ded but in >>> > point >>> > > >>> of >>> > > >>> >> fact before the menu. >>> > > >>> >> >>> > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr >>> which >>> > is >>> > > >>> >> puzzling me. >>> > > >>> >> >>> > > >>> >> /H >>> > > >>> >> >>> > > >>> >> >>> > > >>> >> On 23 October 2018 at 20:56, Toomas Soome >>> wrote: >>> > > >>> >> >>> > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt, >>> then >>> > type >>> > > >>> >>> start - if its bootfort based loader, it will load the >>> kernel and >>> > > >>> modules. >>> > > >>> >>> lsmod will then list the loaded files. >>> > > >>> >>> >>> > > >>> >>> If the loader prompt is still usable, then next command >>> would be: >>> > > >>> boot >>> > > >>> >>> >>> > > >>> >>> rgds, >>> > > >>> >>> toomas >>> > > >>> >>> >>> > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton >>> > wrote: >>> > > >>> >>>> >>> > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >>> > 12.0-BETA1 >>> > > >>> >>> r339529 >>> > > >>> >>>> by source. Have a problem with booting which hangs after: >>> > > >>> >>>> >>> > > >>> >>>>>> FreeBSD EFI boot block >>> > > >>> >>>> Loader path: /boot/loader.efi >>> > > >>> >>>> >>> > > >>> >>>> Initializing modules: ZFS UFS >>> > > >>> >>>> Probing 5 block devices ... done >>> > > >>> >>>> ZFS found the following pools: zroot >>> > > >>> >>>> UFS found no partitions >>> > > >>> >>>> Consoles: EFI console >>> > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>> > > >>> >>>> >>> > > >>> >>>> Command line arguments: loader.efi >>> > > >>> >>>> EFI version 2.31 >>> > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) >>> > > >>> >>>> Console: efi(0) >>> > > >>> >>>> Load Path: HD(4, GPT [ ... ] >>> > > >>> >>>> Load Device: Pci Root [ ... ] >>> > > >>> >>>> Boot Current: 0001 >>> > > >>> >>>> Boot Order: 0001 [x] >>> > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] >>> /\EFI\BOOT\BOOTX64.EFI >>> > > >>> >>>> - >>> > > >>> >>>> >>> > > >>> >>>> So it gets into loader.efi which runs but stops I think ju= st >>> > before >>> > > >>> >>> loading >>> > > >>> >>>> the kernel. Partitions: >>> > > >>> >>>> >>> > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) >>> > > >>> >>>> 40 1600 1 efi (800K) >>> > > >>> >>>> 1640 1024 2 freebsd-boot (512K) >>> > > >>> >>>> 2664 1432 - free - (716K) >>> > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) >>> > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) >>> > > >>> >>>> 250068992 648 - free - (324K) >>> > > >>> >>>> >>> > > >>> >>>> and the EFI partition is FAT 12. >>> > > >>> >>>> >>> > > >>> >>>> I can't provide (at the moment) any output from efibootmgr= : >>> > > >>> >>>> >>> > > >>> >>>> root@gryphon:~ # efibootmgr -v >>> > > >>> >>>> efibootmgr: efi variables not supported on this system. >>> root? >>> > > >>> kldload >>> > > >>> >>> efirt? >>> > > >>> >>>> root@gryphon:~ # kldload efirt >>> > > >>> >>>> kldload: can't load efirt: module already loaded or in >>> kernel >>> > > >>> >>>> >>> > > >>> >>>> which I don't understand. >>> > > >>> >>>> >>> > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and se= e >>> if >>> > that >>> > > >>> >>> allows >>> > > >>> >>>> me to load efirt / use efibootmgr. >>> > > >>> >>>> >>> > > >>> >>>> In the meantime, I should be very grateful for any advice. >>> > > >>> >>>> >>> > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and >>> > dropping >>> > > >>> into >>> > > >>> >>> its >>> > > >>> >>>> loader to get to the installed 12-STABLE ). >>> > > >>> >>>> >>> > > >>> >>>> /Harry >>> > > >>> >>>> _______________________________________________ >>> > > >>> >>>> freebsd-current@freebsd.org mailing list >>> > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > > >>> >>>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@f >>> > > >>> >>> reebsd.org" >>> > > >>> >>> >>> > > >>> >>> >>> > > >>> >> >>> > > >>> >> >>> > > >>> >> -- >>> > > >>> >> Harry Newton >>> > > >>> >> >>> > > >>> >> >>> > > >>> >> >>> > > >>> > >>> > > >>> > >>> > > >>> > -- >>> > > >>> > Harry Newton >>> > > >>> > _______________________________________________ >>> > > >>> > freebsd-current@freebsd.org mailing list >>> > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > > >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe= @f >>> > > >>> reebsd.org" >>> > > >>> >>> > > >>> >>> > > >> >>> > > >> >>> > > >> -- >>> > > >> Harry Newton >>> > > >> >>> > > >> >>> > > >> >>> > > > >>> > > > >>> > > > -- >>> > > > Harry Newton >>> > > > >>> > > >>> > > >>> > > >>> > > -- >>> > > Harry Newton >>> > > _______________________________________________ >>> > > 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" >>> > >>> >>> >>> >>> -- >>> Harry Newton >>> _______________________________________________ >>> 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" >>> >> > > > -- > Harry Newton > From owner-freebsd-current@freebsd.org Wed Oct 24 17:28:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50EA1FFE18E for ; Wed, 24 Oct 2018 17:28:02 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D422970037 for ; Wed, 24 Oct 2018 17:28:01 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yb1-xb2c.google.com with SMTP id p144-v6so2455616yba.11 for ; Wed, 24 Oct 2018 10:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ZQf3jQy8QcMt/LiiYVN2/TF4cPHuhDthWYjBFthYVwk=; b=TO7BGp/jKXfkf6lGYK0Y1Y/soSz5Jr1OO86gft+znk9yRY0ME0N9jthVQ9Xkn+K5Jy ZZT9ZsE4EmPu8RQeMETyJY8QWt3LeGJXI4sL9JfUS6lni2mLgsjpJxM82KudA8iHjZOf AJa2OhzSxan0RmTLH1rk+wWW4g2HlaucOEcDPeNSyIL7WiKeoLqiOkWxBQwOLirT1hFi tMeUf18D619UebaBlrdgXpBHqOnn/6TYuJy/CHpoqRAsiveqGmudoWszhcN8bcpWfyrL VH7+T8dDWrok3/sTMY9ArVD34wsL5RkWmCDlS99NbXIm7Ck5XO86mXQXkg+RFWQP36jd Zm3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ZQf3jQy8QcMt/LiiYVN2/TF4cPHuhDthWYjBFthYVwk=; b=m07yy+VKbGhSeY+sn0ZzAEI8voZPUB3N6paBe1PTRvcjtYvVGr/pTEDmNVn2q3gSgz ypC1okDmpBh27lNHgXRyQZF56j560wqSeo7lkXZMem3z+EmY/6dXHTBvUvodVVuq9jyl RkLJ/v2lcrjdyLAdRh9WElOoE7Cc8qmDMPpKnenRX3HxZwitJYV++x1FWdTGTrhqIQYf DXNLPKZcLrHIONLA41asGzRxFjaPEDesCuePHWp20flg5mZJdMev7/pOE3QSM+w2Mbuf at8M3ZMbOtLPMPVh3cKhL2UC6BXNWWqJIaPmK1ViRgvm4LecWUdFGLlhD53GL+YsUItu fSyw== X-Gm-Message-State: AGRZ1gJYt5se/utXDckjwQOstxcL69SMbSN/QBbDeH4DgRXe0joW7sXG PM5CafeJluKWJq2oSjKcHz4b/q8qBdgmlmRgIR+bEVYh X-Google-Smtp-Source: AJdET5fscGntH2AtCQIEJeoqo8CchUaC5VYsJvxendyldIGUmfnf5PyLLTyse2/n5gAsDhADh4D+k3CYSBkXyblAcEc= X-Received: by 2002:a25:a83:: with SMTP id 125-v6mr3181577ybk.212.1540402080963; Wed, 24 Oct 2018 10:28:00 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:807:0:0:0:0:0 with HTTP; Wed, 24 Oct 2018 10:28:00 -0700 (PDT) In-Reply-To: References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Harry Newton Date: Wed, 24 Oct 2018 18:28:00 +0100 X-Google-Sender-Auth: DcdtYB6pKBYwtEm6GqFK8Uodsqs Message-ID: Subject: Re: UEFI boot hangs after loader To: Warner Losh Cc: Kyle Evans , Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 17:28:02 -0000 Thanks =E2=80=94 please let me if there's anything I can do to help. On 24 October 2018 at 18:25, Warner Losh wrote: > > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) >> 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >> 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 >> 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 >> 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 >> 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 >> 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 >> 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 >> 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff >> 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 >> 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 >> 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 >> 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 >> 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 >> 00e0: 7f ff 04 00 00 00 42 4f >> gryphon# >> > > Perfect. I'll decode this and see if I can figure out where we're going > AFU. > > Warner > > >> On 24 October 2018 at 15:09, Warner Losh wrote: >> >>> >>> >>> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote: >>> >>>> Booted with the installer image makes efibootmgr to work as you said: >>>> >>>> gryphon# efibootmgr -v >>>> BootCurrent: 0002 >>>> Timeout : 2 seconds >>>> BootOrder : 0001, 0002 >>>> Boot0001* UEFI OS >>>> HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/ >>>> File(\EFI\BOOT\BOOTX64.EFI) >>>> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) >>>> >>>> However it (efibootmgr) hangs and doesn't return to the shell, though >>>> it is >>>> interruptible with ^C. >>>> >>>> The partition listed against Boot0001 is my efi partition. >>>> >>> >>> Can you do something like: >>> >>> sudo efivar -N --hex `sudo efivar | grep Boot0002` >>> >>> so I can have an example of a naughty boot variable? That's almost >>> certainly causing the heart-burn. >>> >>> Warner >>> >>> >>> >>>> /H >>>> >>>> On 23 October 2018 at 22:51, Kyle Evans wrote: >>>> >>>> > Hi, >>>> > >>>> > I suspect 4th vs. lua has no impact here, given the output shown -- >>>> > can you throw one of the installer images [0] on some removable medi= a >>>> > and give that a shot for booting? If that works, we can explore UEFI >>>> > variables from there. >>>> > >>>> > efibootmgr will only work on a successful UEFI boot, unfortunately- = if >>>> > we didn't make uefi loader -> kernel transition, then we don't have >>>> > access to runtime services. >>>> > >>>> > Thanks, >>>> > >>>> > Kyle Evans >>>> > >>>> > [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO- >>>> IMAGES/12.0/ >>>> > >>>> > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton >>>> wrote: >>>> > > >>>> > > I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and >>>> re-made >>>> > the >>>> > > binaries in /boot but this doesn't solve the problem. It did copy >>>> > > /boot/loader_4th.efi to /boot/loader.efi which is (according to >>>> uefi(8) >>>> > > which is what is called from /boot/boot1.efi and which contains th= e >>>> > strings >>>> > > I see on the console before the hang. But it must then call / rea= d >>>> > > something else and I don't think it can find it. Not sure why it >>>> doesn't >>>> > > produce an error message. I *think* it may be something to do wit= h >>>> EFI >>>> > > variables, but as efibootmgr doesn't work I can't explore this, >>>> despite >>>> > > efirt being in the kernel. >>>> > > >>>> > > Suggestions received welcomed, and new suggestions / leads to >>>> follow also >>>> > > very much welcomed. >>>> > > >>>> > > /H >>>> > > >>>> > > >>>> > > On 23 October 2018 at 21:33, Harry Newton wrote= : >>>> > > >>>> > > > Right ... I've the binaries in /boot, freshly made. This might >>>> be a >>>> > silly >>>> > > > question ... do I not need to copy them (or dd the boot1.efifat >>>> image) >>>> > to >>>> > > > the EFI partition ? >>>> > > > >>>> > > > /H >>>> > > > >>>> > > > On 23 October 2018 at 21:30, Toomas Soome wrote: >>>> > > > >>>> > > >> you should have the binaries in boot - just ln (or copy) one to >>>> > loader.efi >>>> > > >> >>>> > > >> rgds, >>>> > > >> toomas >>>> > > >> >>>> > > >> >>>> > > >> On 23 Oct 2018, at 23:22, Harry Newton wrote= : >>>> > > >> >>>> > > >> Yes ... so as everything is built, can I just alter >>>> > LOADER_DEFAULT_INTERP >>>> > > >> in /etc/make.conf and then reinstall just the loader and boot >>>> parts >>>> > onto >>>> > > >> the UEFI partition ? If so, how ? >>>> > > >> >>>> > > >> >>>> > > >> On 23 October 2018 at 21:17, Toomas Soome wrote= : >>>> > > >> >>>> > > >>> ok, in that case I=E2=80=99d suggest to test out if forth base= d one is >>>> still >>>> > > >>> working - at least you can get the bootable system. And then >>>> there >>>> > is a >>>> > > >>> chance to debug the lua version too (note it should be possibl= e >>>> to >>>> > chain >>>> > > >>> /boot/loader_lua.efi). >>>> > > >>> >>>> > > >>> rgds, >>>> > > >>> toomas >>>> > > >>> >>>> > > >>> > On 23 Oct 2018, at 23:08, Harry Newton >>>> wrote: >>>> > > >>> > >>>> > > >>> > So it's got FORTH in it, but my loader is lua based, and als= o >>>> > doesn't >>>> > > >>> > appear to read loader.rc. >>>> > > >>> > >>>> > > >>> > /H >>>> > > >>> > >>>> > > >>> > On 23 October 2018 at 21:03, Toomas Soome >>>> wrote: >>>> > > >>> > >>>> > > >>> >> hm. in that case, whats the content of /boot/loader.rc ? >>>> > > >>> >> >>>> > > >>> >> rgds, >>>> > > >>> >> toomas >>>> > > >>> >> >>>> > > >>> >> >>>> > > >>> >> On 23 Oct 2018, at 23:01, Harry Newton >>>> wrote: >>>> > > >>> >> >>>> > > >>> >> If boot menu is the screen where you get the options for >>>> various >>>> > > >>> kernels >>>> > > >>> >> and the picture of the daemon head, no. It stops at the >>>> point in >>>> > my >>>> > > >>> email >>>> > > >>> >> =E2=80=94 though not as I said just before the kernel is lo= aded but >>>> in >>>> > point >>>> > > >>> of >>>> > > >>> >> fact before the menu. >>>> > > >>> >> >>>> > > >>> >> I've also rebuilt the kernel and still can't use efibootmgr >>>> which >>>> > is >>>> > > >>> >> puzzling me. >>>> > > >>> >> >>>> > > >>> >> /H >>>> > > >>> >> >>>> > > >>> >> >>>> > > >>> >> On 23 October 2018 at 20:56, Toomas Soome >>>> wrote: >>>> > > >>> >> >>>> > > >>> >>> Do you get boot menu? if so, press esc to get to ok prompt= , >>>> then >>>> > type >>>> > > >>> >>> start - if its bootfort based loader, it will load the >>>> kernel and >>>> > > >>> modules. >>>> > > >>> >>> lsmod will then list the loaded files. >>>> > > >>> >>> >>>> > > >>> >>> If the loader prompt is still usable, then next command >>>> would be: >>>> > > >>> boot >>>> > > >>> >>> >>>> > > >>> >>> rgds, >>>> > > >>> >>> toomas >>>> > > >>> >>> >>>> > > >>> >>>> On 23 Oct 2018, at 20:45, Harry Newton >>>> > wrote: >>>> > > >>> >>>> >>>> > > >>> >>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >>>> > 12.0-BETA1 >>>> > > >>> >>> r339529 >>>> > > >>> >>>> by source. Have a problem with booting which hangs after= : >>>> > > >>> >>>> >>>> > > >>> >>>>>> FreeBSD EFI boot block >>>> > > >>> >>>> Loader path: /boot/loader.efi >>>> > > >>> >>>> >>>> > > >>> >>>> Initializing modules: ZFS UFS >>>> > > >>> >>>> Probing 5 block devices ... done >>>> > > >>> >>>> ZFS found the following pools: zroot >>>> > > >>> >>>> UFS found no partitions >>>> > > >>> >>>> Consoles: EFI console >>>> > > >>> >>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>>> > > >>> >>>> >>>> > > >>> >>>> Command line arguments: loader.efi >>>> > > >>> >>>> EFI version 2.31 >>>> > > >>> >>>> EFI Firmware: American Megatrends (rev 4.654) >>>> > > >>> >>>> Console: efi(0) >>>> > > >>> >>>> Load Path: HD(4, GPT [ ... ] >>>> > > >>> >>>> Load Device: Pci Root [ ... ] >>>> > > >>> >>>> Boot Current: 0001 >>>> > > >>> >>>> Boot Order: 0001 [x] >>>> > > >>> >>>> Boot Info Path: HS(1, GPT, [ ... ] >>>> /\EFI\BOOT\BOOTX64.EFI >>>> > > >>> >>>> - >>>> > > >>> >>>> >>>> > > >>> >>>> So it gets into loader.efi which runs but stops I think >>>> just >>>> > before >>>> > > >>> >>> loading >>>> > > >>> >>>> the kernel. Partitions: >>>> > > >>> >>>> >>>> > > >>> >>>> =3D> 40 250069600 ada0 GPT (119G) >>>> > > >>> >>>> 40 1600 1 efi (800K) >>>> > > >>> >>>> 1640 1024 2 freebsd-boot (512K) >>>> > > >>> >>>> 2664 1432 - free - (716K) >>>> > > >>> >>>> 4096 4194304 3 freebsd-swap (2.0G) >>>> > > >>> >>>> 4198400 245870592 4 freebsd-zfs (117G) >>>> > > >>> >>>> 250068992 648 - free - (324K) >>>> > > >>> >>>> >>>> > > >>> >>>> and the EFI partition is FAT 12. >>>> > > >>> >>>> >>>> > > >>> >>>> I can't provide (at the moment) any output from efibootmg= r: >>>> > > >>> >>>> >>>> > > >>> >>>> root@gryphon:~ # efibootmgr -v >>>> > > >>> >>>> efibootmgr: efi variables not supported on this system. >>>> root? >>>> > > >>> kldload >>>> > > >>> >>> efirt? >>>> > > >>> >>>> root@gryphon:~ # kldload efirt >>>> > > >>> >>>> kldload: can't load efirt: module already loaded or in >>>> kernel >>>> > > >>> >>>> >>>> > > >>> >>>> which I don't understand. >>>> > > >>> >>>> >>>> > > >>> >>>> I'm going to rebuild the kernel (currently GENERIC) and >>>> see if >>>> > that >>>> > > >>> >>> allows >>>> > > >>> >>>> me to load efirt / use efibootmgr. >>>> > > >>> >>>> >>>> > > >>> >>>> In the meantime, I should be very grateful for any advice= . >>>> > > >>> >>>> >>>> > > >>> >>>> ( Currently booting using a 11-RELEASE memstick image and >>>> > dropping >>>> > > >>> into >>>> > > >>> >>> its >>>> > > >>> >>>> loader to get to the installed 12-STABLE ). >>>> > > >>> >>>> >>>> > > >>> >>>> /Harry >>>> > > >>> >>>> _______________________________________________ >>>> > > >>> >>>> freebsd-current@freebsd.org mailing list >>>> > > >>> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-curren= t >>>> > > >>> >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@f >>>> > > >>> >>> reebsd.org" >>>> > > >>> >>> >>>> > > >>> >>> >>>> > > >>> >> >>>> > > >>> >> >>>> > > >>> >> -- >>>> > > >>> >> Harry Newton >>>> > > >>> >> >>>> > > >>> >> >>>> > > >>> >> >>>> > > >>> > >>>> > > >>> > >>>> > > >>> > -- >>>> > > >>> > Harry Newton >>>> > > >>> > _______________________________________________ >>>> > > >>> > freebsd-current@freebsd.org mailing list >>>> > > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> > > >>> > To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@f >>>> > > >>> reebsd.org" >>>> > > >>> >>>> > > >>> >>>> > > >> >>>> > > >> >>>> > > >> -- >>>> > > >> Harry Newton >>>> > > >> >>>> > > >> >>>> > > >> >>>> > > > >>>> > > > >>>> > > > -- >>>> > > > Harry Newton >>>> > > > >>>> > > >>>> > > >>>> > > >>>> > > -- >>>> > > Harry Newton >>>> > > _______________________________________________ >>>> > > 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" >>>> > >>>> >>>> >>>> >>>> -- >>>> Harry Newton >>>> _______________________________________________ >>>> 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" >>>> >>> >> >> >> -- >> Harry Newton >> > --=20 Harry Newton From owner-freebsd-current@freebsd.org Wed Oct 24 17:47:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEE40FFED1F for ; Wed, 24 Oct 2018 17:47:24 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6277D710E9; Wed, 24 Oct 2018 17:47:24 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (static-71-168-218-4.cmdnnj.fios.verizon.net [71.168.218.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jkim/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 39B84D095; Wed, 24 Oct 2018 17:47:24 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: UEFI boot hangs after loader To: Warner Losh , Harry Newton Cc: Kyle Evans , Toomas Soome , FreeBSD Current References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> From: Jung-uk Kim Openpgp: preference=signencrypt Autocrypt: addr=jkim@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJBztUBCAChqNyGqmFuNo0U7MBzsD+q/G6Cv0l7LGVrOAsgh34M8wIWhD+tztDWMVfn AhxNDd0ceCj2bYOe67sTQxAScEcbt2FfvPOLp9MEXb9qohZj172Gwkk7dnhOhZZKhVGVZKM4 NcsuBDUzgf4f3Vdzj4wg6WlqplnTZo8lPE4hZWvZHoFIyunPTJWenybeV1xnxK7JkUdSvQR0 fA59RfTTECMwTrSEfYGUnxIDBraxJ7Ecs/0hGQ7sljIj8WBvlRDU5fU1xfF35aw56T8POQRq F4E6RVJW3YGuTpSwgtGZOTfygcLRhAiq3dFC3JNLaTVTpM8PjOinJyt9AU6RoITGOKwDABEB AAHNHkp1bmctdWsgS2ltIDxqa2ltQEZyZWVCU0Qub3JnPsLAfQQTAQoAJwUCUkHO1QIbAwUJ E0/POwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRB8n5Ym/NvxRqyzB/wL7QtsIpeGfGIA ZPMtgXMucM3NWzomyQMln2j2efUkDKthzh9jBxgF53TjOr7imwIt0PT2k1bqctPrq5IRqnu9 mGroqaCLE3LG2/E3jEaao4k9PO6efwlioyivUo5NrqIQOQ4k3EAXw7d2y0Dk1VpTgdMrnUAB hj7lGlLqS4ydcrf24DdbCRGdEQwqd9DBeBgbWynxAJMgbZBhYVEyIHuQKkJ8qY0ibIPXXuF0 KYDeH0qUHtWV2K3srNyPtymUkBQD84Pl1GWRYx05XdUHDmnX0JV3lg0BfYJZgZv0ehPQrMfY Fd9abTkf9FHQYz1JtsC8wUuRgqElRd6+YAGf8Tt9zsBNBFJBztUBCADLtSrP44El2VoJmH14 OFrlOgxzZnbn+Y/Gf1k12mJBiR+A+pBeRLD50p7AiTrjHRxO3cHcl9Dh0uf1VSbXgp8Or0ye iP/86fZPd4k5HXNmDTLL0HecPE08SCqGZ0W8vllQrokB1QxxRUB+fFMPJyMCjDAZ7P9fFTOS dTw1bJSTtOD8Sx8MpZUa9ti06bXFlVYDlaqSdgk181SSx+ZbSKkQR8CIMARlHwiLsa3Z9q9O EJr20HPyxe0AlTvwvFndH61hg7ds63eRvglwRnNON28VXO/lvKXq7Br/CiiyhFdKfINIx2Z5 htYq22tgGTW7mBURbIKoECFBTX9Lv6BXz6w9ABEBAAHCwGUEGAEKAA8FAlJBztUCGwwFCRNP zzsACgkQfJ+WJvzb8UZcJQf+IsTCxUEqY7W/pT84sMg5/QD3s6ufTRncvq14fEOxCNq1Rf4Q 9P+tOFa8GZfKDGB2BFGIrW7uT5mlmKdK1vO6ZIA930y5kUsnCmBUEBJkE2ciSQk01aB/1o62 Q3Gk/F6BwtNY9OXiqF7AcAo+K/BMIaqb26QKeh+IIgK1NN9dQiq3ByTbl4zpGZa6MmsnnRTu mzGKt2nkz7vBzH6+hZp1OzGZikgjjhYWVFoJo1dvf/rv4obs0ZJEqFPQs/1Qa1dbkKBv6odB XJpPH0ssOluTY24d1XxTiKTwmWvHeQkOKRAIfD7VTtF4TesoZYkf7hsh3e3VwXhptSLFnEOi WwYofg== Message-ID: <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> Date: Wed, 24 Oct 2018 13:47:16 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6YQ9ZCTcMVw91DDlUHa6JZDeoMPqZaEHa" 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, 24 Oct 2018 17:47:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6YQ9ZCTcMVw91DDlUHa6JZDeoMPqZaEHa Content-Type: multipart/mixed; boundary="ei2Kmkk4IfMlSr6K5wLYoLjvuy9Iwfoij"; protected-headers="v1" From: Jung-uk Kim To: Warner Losh , Harry Newton Cc: Kyle Evans , Toomas Soome , FreeBSD Current Message-ID: <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> Subject: Re: UEFI boot hangs after loader References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> In-Reply-To: --ei2Kmkk4IfMlSr6K5wLYoLjvuy9Iwfoij Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 18. 10. 24., Warner Losh wrote: > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote:= >=20 >> gryphon# efivar -N --hex $(efivar | grep Boot0002) >> 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 >> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 >> 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 >> 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 >> 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 >> 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 >> 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 >> 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 >> 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff >> 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 >> 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 >> 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 >> 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 >> 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 >> 00e0: 7f ff 04 00 00 00 42 4f >> gryphon# >> >=20 > Perfect. I'll decode this and see if I can figure out where we're going= AFU. It looks familiar. http://docs.freebsd.org/cgi/mid.cgi?eadf5d63-a65a-338e-a3e0-f91b410052fa Jung-uk Kim >> On 24 October 2018 at 15:09, Warner Losh wrote: >> >>> >>> >>> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote= : >>> >>>> Booted with the installer image makes efibootmgr to work as you said= : >>>> >>>> gryphon# efibootmgr -v >>>> BootCurrent: 0002 >>>> Timeout : 2 seconds >>>> BootOrder : 0001, 0002 >>>> Boot0001* UEFI OS >>>> >>>> HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\= BOOT\BOOTX64.EFI) >>>> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) >>>> >>>> However it (efibootmgr) hangs and doesn't return to the shell, thoug= h it >>>> is >>>> interruptible with ^C. >>>> >>>> The partition listed against Boot0001 is my efi partition. >>>> >>> >>> Can you do something like: >>> >>> sudo efivar -N --hex `sudo efivar | grep Boot0002` >>> >>> so I can have an example of a naughty boot variable? That's almost >>> certainly causing the heart-burn. >>> >>> Warner >>> >>> >>> >>>> /H >>>> >>>> On 23 October 2018 at 22:51, Kyle Evans wrote: >>>> >>>>> Hi, >>>>> >>>>> I suspect 4th vs. lua has no impact here, given the output shown --= >>>>> can you throw one of the installer images [0] on some removable med= ia >>>>> and give that a shot for booting? If that works, we can explore UEF= I >>>>> variables from there. >>>>> >>>>> efibootmgr will only work on a successful UEFI boot, unfortunately-= if >>>>> we didn't make uefi loader -> kernel transition, then we don't have= >>>>> access to runtime services. >>>>> >>>>> Thanks, >>>>> >>>>> Kyle Evans >>>>> >>>>> [0] >>>> https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.= 0/ >>>>> >>>>> On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wro= te: >>>>>> >>>>>> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and >>>> re-made >>>>> the >>>>>> binaries in /boot but this doesn't solve the problem. It did copy= >>>>>> /boot/loader_4th.efi to /boot/loader.efi which is (according to >>>> uefi(8) >>>>>> which is what is called from /boot/boot1.efi and which contains th= e >>>>> strings >>>>>> I see on the console before the hang. But it must then call / rea= d >>>>>> something else and I don't think it can find it. Not sure why it >>>> doesn't >>>>>> produce an error message. I *think* it may be something to do wit= h >>>> EFI >>>>>> variables, but as efibootmgr doesn't work I can't explore this, >>>> despite >>>>>> efirt being in the kernel. >>>>>> >>>>>> Suggestions received welcomed, and new suggestions / leads to foll= ow >>>> also >>>>>> very much welcomed. >>>>>> >>>>>> /H >>>>>> >>>>>> >>>>>> On 23 October 2018 at 21:33, Harry Newton wrote= : >>>>>> >>>>>>> Right ... I've the binaries in /boot, freshly made. This might b= e >>>> a >>>>> silly >>>>>>> question ... do I not need to copy them (or dd the boot1.efifat >>>> image) >>>>> to >>>>>>> the EFI partition ? >>>>>>> >>>>>>> /H >>>>>>> >>>>>>> On 23 October 2018 at 21:30, Toomas Soome wrote: >>>>>>> >>>>>>>> you should have the binaries in boot - just ln (or copy) one to >>>>> loader.efi >>>>>>>> >>>>>>>> rgds, >>>>>>>> toomas >>>>>>>> >>>>>>>> >>>>>>>> On 23 Oct 2018, at 23:22, Harry Newton wrote:= >>>>>>>> >>>>>>>> Yes ... so as everything is built, can I just alter >>>>> LOADER_DEFAULT_INTERP >>>>>>>> in /etc/make.conf and then reinstall just the loader and boot >>>> parts >>>>> onto >>>>>>>> the UEFI partition ? If so, how ? >>>>>>>> >>>>>>>> >>>>>>>> On 23 October 2018 at 21:17, Toomas Soome wrote:= >>>>>>>> >>>>>>>>> ok, in that case I=E2=80=99d suggest to test out if forth based= one is >>>> still >>>>>>>>> working - at least you can get the bootable system. And then >>>> there >>>>> is a >>>>>>>>> chance to debug the lua version too (note it should be possible= >>>> to >>>>> chain >>>>>>>>> /boot/loader_lua.efi). >>>>>>>>> >>>>>>>>> rgds, >>>>>>>>> toomas >>>>>>>>> >>>>>>>>>> On 23 Oct 2018, at 23:08, Harry Newton >>>> wrote: >>>>>>>>>> >>>>>>>>>> So it's got FORTH in it, but my loader is lua based, and also >>>>> doesn't >>>>>>>>>> appear to read loader.rc. >>>>>>>>>> >>>>>>>>>> /H >>>>>>>>>> >>>>>>>>>> On 23 October 2018 at 21:03, Toomas Soome >>>> wrote: >>>>>>>>>> >>>>>>>>>>> hm. in that case, whats the content of /boot/loader.rc ? >>>>>>>>>>> >>>>>>>>>>> rgds, >>>>>>>>>>> toomas >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 23 Oct 2018, at 23:01, Harry Newton >>>> wrote: >>>>>>>>>>> >>>>>>>>>>> If boot menu is the screen where you get the options for >>>> various >>>>>>>>> kernels >>>>>>>>>>> and the picture of the daemon head, no. It stops at the >>>> point in >>>>> my >>>>>>>>> email >>>>>>>>>>> =E2=80=94 though not as I said just before the kernel is load= ed but in >>>>> point >>>>>>>>> of >>>>>>>>>>> fact before the menu. >>>>>>>>>>> >>>>>>>>>>> I've also rebuilt the kernel and still can't use efibootmgr >>>> which >>>>> is >>>>>>>>>>> puzzling me. >>>>>>>>>>> >>>>>>>>>>> /H >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 23 October 2018 at 20:56, Toomas Soome >>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, >>>> then >>>>> type >>>>>>>>>>>> start - if its bootfort based loader, it will load the >>>> kernel and >>>>>>>>> modules. >>>>>>>>>>>> lsmod will then list the loaded files. >>>>>>>>>>>> >>>>>>>>>>>> If the loader prompt is still usable, then next command >>>> would be: >>>>>>>>> boot >>>>>>>>>>>> >>>>>>>>>>>> rgds, >>>>>>>>>>>> toomas >>>>>>>>>>>> >>>>>>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton >>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >>>>> 12.0-BETA1 >>>>>>>>>>>> r339529 >>>>>>>>>>>>> by source. Have a problem with booting which hangs after: >>>>>>>>>>>>> >>>>>>>>>>>>>>> FreeBSD EFI boot block >>>>>>>>>>>>> Loader path: /boot/loader.efi >>>>>>>>>>>>> >>>>>>>>>>>>> Initializing modules: ZFS UFS >>>>>>>>>>>>> Probing 5 block devices ... done >>>>>>>>>>>>> ZFS found the following pools: zroot >>>>>>>>>>>>> UFS found no partitions >>>>>>>>>>>>> Consoles: EFI console >>>>>>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 >>>>>>>>>>>>> >>>>>>>>>>>>> Command line arguments: loader.efi >>>>>>>>>>>>> EFI version 2.31 >>>>>>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) >>>>>>>>>>>>> Console: efi(0) >>>>>>>>>>>>> Load Path: HD(4, GPT [ ... ] >>>>>>>>>>>>> Load Device: Pci Root [ ... ] >>>>>>>>>>>>> Boot Current: 0001 >>>>>>>>>>>>> Boot Order: 0001 [x] >>>>>>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] >>>> /\EFI\BOOT\BOOTX64.EFI >>>>>>>>>>>>> - >>>>>>>>>>>>> >>>>>>>>>>>>> So it gets into loader.efi which runs but stops I think jus= t >>>>> before >>>>>>>>>>>> loading >>>>>>>>>>>>> the kernel. Partitions: >>>>>>>>>>>>> >>>>>>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) >>>>>>>>>>>>> 40 1600 1 efi (800K) >>>>>>>>>>>>> 1640 1024 2 freebsd-boot (512K) >>>>>>>>>>>>> 2664 1432 - free - (716K) >>>>>>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) >>>>>>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) >>>>>>>>>>>>> 250068992 648 - free - (324K) >>>>>>>>>>>>> >>>>>>>>>>>>> and the EFI partition is FAT 12. >>>>>>>>>>>>> >>>>>>>>>>>>> I can't provide (at the moment) any output from efibootmgr:= >>>>>>>>>>>>> >>>>>>>>>>>>> root@gryphon:~ # efibootmgr -v >>>>>>>>>>>>> efibootmgr: efi variables not supported on this system. >>>> root? >>>>>>>>> kldload >>>>>>>>>>>> efirt? >>>>>>>>>>>>> root@gryphon:~ # kldload efirt >>>>>>>>>>>>> kldload: can't load efirt: module already loaded or in >>>> kernel >>>>>>>>>>>>> >>>>>>>>>>>>> which I don't understand. >>>>>>>>>>>>> >>>>>>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see= >>>> if >>>>> that >>>>>>>>>>>> allows >>>>>>>>>>>>> me to load efirt / use efibootmgr. >>>>>>>>>>>>> >>>>>>>>>>>>> In the meantime, I should be very grateful for any advice. >>>>>>>>>>>>> >>>>>>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and >>>>> dropping >>>>>>>>> into >>>>>>>>>>>> its >>>>>>>>>>>>> loader to get to the installed 12-STABLE ). >>>>>>>>>>>>> >>>>>>>>>>>>> /Harry --ei2Kmkk4IfMlSr6K5wLYoLjvuy9Iwfoij-- --6YQ9ZCTcMVw91DDlUHa6JZDeoMPqZaEHa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlvQsCUACgkQfJ+WJvzb 8UYlSgf8CyNpYkuNjtNOpFbBpP2PpM0BlEh9KBT3LpCKtIklwLqaIwOkBxFTRxwl BWtgvbVKjb3H0T9YaLK4KdLSBCyy1sfRBS4eJwkak03slZhqyxAAryVRludH4xt2 xDwtHCRNUELDaceonkrb18mBM1RQmlmua5EL/18Dr4Xu6iiKQzjH92558aAVw6A1 YGGryrdp1MVZBLZmHdhJvHDDz2Yed6kBFXyR0Dw03c2wslkH1M8CsuQ4h7bCwDDP cNv7cYFNlQ1f754uTIMnxVxo6Ao3EchNhemDDm2lwHoHe6QM2zWlzfIwvtnBS46e dHr7nhbXuyYtR4WbZ33Q/1jSz6DrPQ== =Rgav -----END PGP SIGNATURE----- --6YQ9ZCTcMVw91DDlUHa6JZDeoMPqZaEHa-- From owner-freebsd-current@freebsd.org Wed Oct 24 18:35:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64ABA1008FFE for ; Wed, 24 Oct 2018 18:35:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAF1E7431F for ; Wed, 24 Oct 2018 18:35:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2f.google.com with SMTP id k14so1937149vsm.10 for ; Wed, 24 Oct 2018 11:35:21 -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=84wbit+JAdB7DYXrxUlbadOwwRh/YhPxcv7ggyi8niQ=; b=XHQZ3EuoEQ5br/7NkOpxbuHhl23A4CjKA1QaEtcZv2vhyXr+0dKgk7zYOBXLi8sVyG /o6fOVJUR2SFD5J5SLOtoiBsn4vHBkoRAAr1rZmtCFCzKrpw0/DMPZXKu44iIjbcxDEr ax9Ev8Jbm0FR9lMvzakrYdPyyrBgk7KbXLkJ9/VBAESZSV0Pa5W65tS/48oO24pwUJH3 +RoVDWACH8hgHPJdzFKGGIAGlhd/DqOZmz7Ml2Gn6urWPdoDoYMDYUkgQw/ECPLHkx4m P7L8GH2H9JOtdNdURegxCDPY6od6wl/i1WnivgWN3q9zk65HJtS5d5vdcucOLHd4aKEp bWJw== 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=84wbit+JAdB7DYXrxUlbadOwwRh/YhPxcv7ggyi8niQ=; b=Xn2bkb0t9bjrOiIwkEFzDThK/yCPqGPOFhB/h+tmuCCbdKwHoV/+OR62lqiUbvhtaB Dq82LuI/MiUR0a40Uhsx2KCMOclDffzFci5sk5FjU8aDZUxV7BYQY6//HHX5w0VWnyBU IYAWaLVsPNp8BoOzQdG2ipCGay69CfsxU1a16AIWRWqr97SJWGXTmrbIpYrvmUAZG2JP YdeGEj4/SW2gY5JSqx8TqxfJHCD8f09LLqBcGTBjtC1KmdGyOkNllHVrDSmKnBmjRBiW LA4grLLU4U/Bgy9kGUH6UPkUdUPxyg39ewfS2xv/KjRTstxKvJD78BgkLSuaovvwxfKv ojpQ== X-Gm-Message-State: AGRZ1gJpd6Gkz86FJV7xGzgUs7rLA2Vf0KItXkhyq9MUoNERUUL5fPYj gmTbvekIpD4dsM6SjvYFiaB0an24emRjrj6rtT46eA== X-Google-Smtp-Source: AJdET5cZEhj8Wv+H/frmf5RTLZXKrkhE7+NDbSpjHEO+RFb57w8vDfgODzrrw/URZB+KcfcRe0xF0BjGWtXxAVRl01Y= X-Received: by 2002:a67:f757:: with SMTP id w23mr1684906vso.76.1540406121149; Wed, 24 Oct 2018 11:35:21 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> In-Reply-To: <2c936e35-7bcf-95f9-f99d-60d3c9408d39@FreeBSD.org> From: Warner Losh Date: Wed, 24 Oct 2018 12:35:09 -0600 Message-ID: Subject: Re: UEFI boot hangs after loader To: Jung-uk Kim Cc: Harry Newton , Kyle Evans , Toomas Soome , FreeBSD Current 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: Wed, 24 Oct 2018 18:35:22 -0000 On Wed, Oct 24, 2018 at 11:47 AM Jung-uk Kim wrote: > On 18. 10. 24., Warner Losh wrote: > > On Wed, Oct 24, 2018 at 10:33 AM Harry Newton wrote: > > > >> gryphon# efivar -N --hex $(efivar | grep Boot0002) > >> 0000: 01 00 00 00 98 00 55 00 45 00 46 00 49 00 3a 00 > >> 0010: 20 00 4b 00 69 00 6e 00 67 00 73 00 74 00 6f 00 > >> 0020: 6e 00 44 00 61 00 74 00 61 00 54 00 72 00 61 00 > >> 0030: 76 00 65 00 6c 00 65 00 72 00 20 00 32 00 2e 00 > >> 0040: 30 00 31 00 2e 00 30 00 30 00 00 00 02 01 0c 00 > >> 0050: d0 41 03 0a 00 00 00 00 01 01 06 00 00 14 03 05 > >> 0060: 06 00 03 00 04 01 2a 00 01 00 00 00 01 00 00 00 > >> 0070: 00 00 00 00 40 06 00 00 00 00 00 00 90 90 90 90 > >> 0080: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 7f ff > >> 0090: 04 00 01 04 4e 00 ef 47 64 2d c9 3b a0 41 ac 19 > >> 00a0: 4d 51 d0 1b 4c e6 4b 00 69 00 6e 00 67 00 73 00 > >> 00b0: 74 00 6f 00 6e 00 44 00 61 00 74 00 61 00 54 00 > >> 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00 > >> 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00 > >> 00e0: 7f ff 04 00 00 00 42 4f > >> gryphon# > >> > > > > Perfect. I'll decode this and see if I can figure out where we're going > AFU. > > It looks familiar. > > http://docs.freebsd.org/cgi/mid.cgi?eadf5d63-a65a-338e-a3e0-f91b410052fa > > Jung-uk Kim > His loader variable works for me (sigh). Your loader variable doesn't. I totally forgot you'd sent that as well. Thanks for the pointer. It's quite helpful. Warner > >> On 24 October 2018 at 15:09, Warner Losh wrote: > >> > >>> > >>> > >>> On Wed, Oct 24, 2018 at 7:05 AM Harry Newton wrote= : > >>> > >>>> Booted with the installer image makes efibootmgr to work as you said= : > >>>> > >>>> gryphon# efibootmgr -v > >>>> BootCurrent: 0002 > >>>> Timeout : 2 seconds > >>>> BootOrder : 0001, 0002 > >>>> Boot0001* UEFI OS > >>>> > >>>> > HD(1,GPT,b19ccd5d-7c6a-11e7-ae3e-28b2bde107e4,0x28,0x640)/File(\EFI\BOOT\= BOOTX64.EFI) > >>>> ada0p1:/EFI/BOOT/BOOTX64.EFI (null) > >>>> > >>>> However it (efibootmgr) hangs and doesn't return to the shell, thoug= h > it > >>>> is > >>>> interruptible with ^C. > >>>> > >>>> The partition listed against Boot0001 is my efi partition. > >>>> > >>> > >>> Can you do something like: > >>> > >>> sudo efivar -N --hex `sudo efivar | grep Boot0002` > >>> > >>> so I can have an example of a naughty boot variable? That's almost > >>> certainly causing the heart-burn. > >>> > >>> Warner > >>> > >>> > >>> > >>>> /H > >>>> > >>>> On 23 October 2018 at 22:51, Kyle Evans wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I suspect 4th vs. lua has no impact here, given the output shown -- > >>>>> can you throw one of the installer images [0] on some removable med= ia > >>>>> and give that a shot for booting? If that works, we can explore UEF= I > >>>>> variables from there. > >>>>> > >>>>> efibootmgr will only work on a successful UEFI boot, unfortunately- > if > >>>>> we didn't make uefi loader -> kernel transition, then we don't have > >>>>> access to runtime services. > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Kyle Evans > >>>>> > >>>>> [0] > >>>> > https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ > >>>>> > >>>>> On Tue, Oct 23, 2018 at 4:23 PM Harry Newton > wrote: > >>>>>> > >>>>>> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and > >>>> re-made > >>>>> the > >>>>>> binaries in /boot but this doesn't solve the problem. It did copy > >>>>>> /boot/loader_4th.efi to /boot/loader.efi which is (according to > >>>> uefi(8) > >>>>>> which is what is called from /boot/boot1.efi and which contains th= e > >>>>> strings > >>>>>> I see on the console before the hang. But it must then call / rea= d > >>>>>> something else and I don't think it can find it. Not sure why it > >>>> doesn't > >>>>>> produce an error message. I *think* it may be something to do wit= h > >>>> EFI > >>>>>> variables, but as efibootmgr doesn't work I can't explore this, > >>>> despite > >>>>>> efirt being in the kernel. > >>>>>> > >>>>>> Suggestions received welcomed, and new suggestions / leads to foll= ow > >>>> also > >>>>>> very much welcomed. > >>>>>> > >>>>>> /H > >>>>>> > >>>>>> > >>>>>> On 23 October 2018 at 21:33, Harry Newton wrote= : > >>>>>> > >>>>>>> Right ... I've the binaries in /boot, freshly made. This might b= e > >>>> a > >>>>> silly > >>>>>>> question ... do I not need to copy them (or dd the boot1.efifat > >>>> image) > >>>>> to > >>>>>>> the EFI partition ? > >>>>>>> > >>>>>>> /H > >>>>>>> > >>>>>>> On 23 October 2018 at 21:30, Toomas Soome wrote: > >>>>>>> > >>>>>>>> you should have the binaries in boot - just ln (or copy) one to > >>>>> loader.efi > >>>>>>>> > >>>>>>>> rgds, > >>>>>>>> toomas > >>>>>>>> > >>>>>>>> > >>>>>>>> On 23 Oct 2018, at 23:22, Harry Newton wrote: > >>>>>>>> > >>>>>>>> Yes ... so as everything is built, can I just alter > >>>>> LOADER_DEFAULT_INTERP > >>>>>>>> in /etc/make.conf and then reinstall just the loader and boot > >>>> parts > >>>>> onto > >>>>>>>> the UEFI partition ? If so, how ? > >>>>>>>> > >>>>>>>> > >>>>>>>> On 23 October 2018 at 21:17, Toomas Soome wrote: > >>>>>>>> > >>>>>>>>> ok, in that case I=E2=80=99d suggest to test out if forth based= one is > >>>> still > >>>>>>>>> working - at least you can get the bootable system. And then > >>>> there > >>>>> is a > >>>>>>>>> chance to debug the lua version too (note it should be possible > >>>> to > >>>>> chain > >>>>>>>>> /boot/loader_lua.efi). > >>>>>>>>> > >>>>>>>>> rgds, > >>>>>>>>> toomas > >>>>>>>>> > >>>>>>>>>> On 23 Oct 2018, at 23:08, Harry Newton > >>>> wrote: > >>>>>>>>>> > >>>>>>>>>> So it's got FORTH in it, but my loader is lua based, and also > >>>>> doesn't > >>>>>>>>>> appear to read loader.rc. > >>>>>>>>>> > >>>>>>>>>> /H > >>>>>>>>>> > >>>>>>>>>> On 23 October 2018 at 21:03, Toomas Soome > >>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> hm. in that case, whats the content of /boot/loader.rc ? > >>>>>>>>>>> > >>>>>>>>>>> rgds, > >>>>>>>>>>> toomas > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> On 23 Oct 2018, at 23:01, Harry Newton > >>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>> If boot menu is the screen where you get the options for > >>>> various > >>>>>>>>> kernels > >>>>>>>>>>> and the picture of the daemon head, no. It stops at the > >>>> point in > >>>>> my > >>>>>>>>> email > >>>>>>>>>>> =E2=80=94 though not as I said just before the kernel is load= ed but in > >>>>> point > >>>>>>>>> of > >>>>>>>>>>> fact before the menu. > >>>>>>>>>>> > >>>>>>>>>>> I've also rebuilt the kernel and still can't use efibootmgr > >>>> which > >>>>> is > >>>>>>>>>>> puzzling me. > >>>>>>>>>>> > >>>>>>>>>>> /H > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> On 23 October 2018 at 20:56, Toomas Soome > >>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, > >>>> then > >>>>> type > >>>>>>>>>>>> start - if its bootfort based loader, it will load the > >>>> kernel and > >>>>>>>>> modules. > >>>>>>>>>>>> lsmod will then list the loaded files. > >>>>>>>>>>>> > >>>>>>>>>>>> If the loader prompt is still usable, then next command > >>>> would be: > >>>>>>>>> boot > >>>>>>>>>>>> > >>>>>>>>>>>> rgds, > >>>>>>>>>>>> toomas > >>>>>>>>>>>> > >>>>>>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton > >>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to > >>>>> 12.0-BETA1 > >>>>>>>>>>>> r339529 > >>>>>>>>>>>>> by source. Have a problem with booting which hangs after: > >>>>>>>>>>>>> > >>>>>>>>>>>>>>> FreeBSD EFI boot block > >>>>>>>>>>>>> Loader path: /boot/loader.efi > >>>>>>>>>>>>> > >>>>>>>>>>>>> Initializing modules: ZFS UFS > >>>>>>>>>>>>> Probing 5 block devices ... done > >>>>>>>>>>>>> ZFS found the following pools: zroot > >>>>>>>>>>>>> UFS found no partitions > >>>>>>>>>>>>> Consoles: EFI console > >>>>>>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>>>>>>>>>>> > >>>>>>>>>>>>> Command line arguments: loader.efi > >>>>>>>>>>>>> EFI version 2.31 > >>>>>>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) > >>>>>>>>>>>>> Console: efi(0) > >>>>>>>>>>>>> Load Path: HD(4, GPT [ ... ] > >>>>>>>>>>>>> Load Device: Pci Root [ ... ] > >>>>>>>>>>>>> Boot Current: 0001 > >>>>>>>>>>>>> Boot Order: 0001 [x] > >>>>>>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] > >>>> /\EFI\BOOT\BOOTX64.EFI > >>>>>>>>>>>>> - > >>>>>>>>>>>>> > >>>>>>>>>>>>> So it gets into loader.efi which runs but stops I think jus= t > >>>>> before > >>>>>>>>>>>> loading > >>>>>>>>>>>>> the kernel. Partitions: > >>>>>>>>>>>>> > >>>>>>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) > >>>>>>>>>>>>> 40 1600 1 efi (800K) > >>>>>>>>>>>>> 1640 1024 2 freebsd-boot (512K) > >>>>>>>>>>>>> 2664 1432 - free - (716K) > >>>>>>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>>>>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>>>>>>>>>>> 250068992 648 - free - (324K) > >>>>>>>>>>>>> > >>>>>>>>>>>>> and the EFI partition is FAT 12. > >>>>>>>>>>>>> > >>>>>>>>>>>>> I can't provide (at the moment) any output from efibootmgr: > >>>>>>>>>>>>> > >>>>>>>>>>>>> root@gryphon:~ # efibootmgr -v > >>>>>>>>>>>>> efibootmgr: efi variables not supported on this system. > >>>> root? > >>>>>>>>> kldload > >>>>>>>>>>>> efirt? > >>>>>>>>>>>>> root@gryphon:~ # kldload efirt > >>>>>>>>>>>>> kldload: can't load efirt: module already loaded or in > >>>> kernel > >>>>>>>>>>>>> > >>>>>>>>>>>>> which I don't understand. > >>>>>>>>>>>>> > >>>>>>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see > >>>> if > >>>>> that > >>>>>>>>>>>> allows > >>>>>>>>>>>>> me to load efirt / use efibootmgr. > >>>>>>>>>>>>> > >>>>>>>>>>>>> In the meantime, I should be very grateful for any advice. > >>>>>>>>>>>>> > >>>>>>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and > >>>>> dropping > >>>>>>>>> into > >>>>>>>>>>>> its > >>>>>>>>>>>>> loader to get to the installed 12-STABLE ). > >>>>>>>>>>>>> > >>>>>>>>>>>>> /Harry > > From owner-freebsd-current@freebsd.org Wed Oct 24 19:44:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFFC51037EBD for ; Wed, 24 Oct 2018 19:44:16 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B21C76FB8 for ; Wed, 24 Oct 2018 19:44:16 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id E988910AFCD; Wed, 24 Oct 2018 15:44:14 -0400 (EDT) Subject: Re: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 To: Marcin Cieslak , FreeBSD Current References: From: John Baldwin Message-ID: <65f4cac9-99be-265f-e461-b166d52d226b@FreeBSD.org> Date: Wed, 24 Oct 2018 12:44:14 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 24 Oct 2018 15:44:15 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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, 24 Oct 2018 19:44:17 -0000 On 10/23/18 10:58 AM, Marcin Cieslak wrote: > Hello, I have a freshly built 12.0-ALPHA10 (r339406) and the kernel > panicked at some point (another mail coming on that). > > I have a full dump partition enabled, but during savecore > quite lot BFD assertion messages appear: > > Tue Oct 23 18:45:53 CEST 2018 > > FreeBSD radziecki 12.0-ALPHA10 FreeBSD 12.0-ALPHA10 r339406 GENERIC amd64 > > panic: > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"...BFD: /boot/kernel/kernel: invalid relocation type 37 > BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 > > The kernel has been built on 11.1 with LD=/usr/bin/ld.lld > > Is this something that matters at all? It is not something that is likely to be fixed. If you pkg install gdb from ports, is the kgdb it includes able to examine the crash dump? -- John Baldwin From owner-freebsd-current@freebsd.org Wed Oct 24 19:47:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91E281037FBE; Wed, 24 Oct 2018 19:47:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46F14770FD; Wed, 24 Oct 2018 19:47:13 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id E84B710A87D; Wed, 24 Oct 2018 15:47:11 -0400 (EDT) Subject: Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: Rajesh Kumar , freebsd-drivers@freebsd.org, freebsd-current@freebsd.org References: From: John Baldwin Message-ID: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> Date: Wed, 24 Oct 2018 12:47:11 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 24 Oct 2018 15:47:12 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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, 24 Oct 2018 19:47:13 -0000 On 10/24/18 3:40 AM, Rajesh Kumar wrote: > Hi, > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, I > needed the following tunables to be set from loader prompt to get it booted > (otherwise machine reboots continuously). > > hw.usb.xhci.msi=0 > hw.usb.xhci.msix=0 > hw.pci.enable_msi=0 > hw.pci.enable_msix=0 > > But, when I tried with 12.0 - ALPHA4, I could able to get it booted without > any tunables. So, has anything changed significantly on PCI MSI/MSI-X > path? > > Note: I have a forum topic with my observations about the issue on > 11.1/11.2 in the following thread > https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ > > Let me know if you need any details. I believe this was fixed by r338360. -- John Baldwin From owner-freebsd-current@freebsd.org Wed Oct 24 21:08:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 305031070459 for ; Wed, 24 Oct 2018 21:08:17 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B8F5C7A828 for ; Wed, 24 Oct 2018 21:08:16 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7AFAA1070456; Wed, 24 Oct 2018 21:08:16 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5917D1070455 for ; Wed, 24 Oct 2018 21:08:16 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 DFC767A827 for ; Wed, 24 Oct 2018 21:08:15 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (unknown [75.161.243.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id E6C291AFBDA; Wed, 24 Oct 2018 13:19:37 +0000 (UTC) Subject: Re: UFS panics To: Leandro , current@freebsd.org References: From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: Date: Wed, 24 Oct 2018 15:08:11 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="13Pvg2EADJrDNSKvtkHoP8nJcj4EIaE6O" 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, 24 Oct 2018 21:08:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --13Pvg2EADJrDNSKvtkHoP8nJcj4EIaE6O Content-Type: multipart/mixed; boundary="D4ozwyZTZnd6kGLEV5PoJqGIsfeEfuWaB"; protected-headers="v1" From: Sean Bruno To: Leandro , current@freebsd.org Message-ID: Subject: Re: UFS panics References: In-Reply-To: --D4ozwyZTZnd6kGLEV5PoJqGIsfeEfuWaB Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/24/18 9:22 AM, Leandro wrote: > Hello, >=20 > I'm seeing a kernel panic when trying to move a specific file. >=20 > panic: Bad effnlink fip 0xc0000004a2c69a00, fdp 0xc000000497093be0, > tdp 0xc0000004be6295a0 > cpuid =3D 72 > time =3D 1540283798 > KDB: stack backtrace: > 0xe0000000adb8dcc0: at .kdb_backtrace+0x5c > 0xe0000000adb8ddf0: at .vpanic+0x1b4 > 0xe0000000adb8deb0: at .panic+0x38 > 0xe0000000adb8df40: at .ufs_readdir+0x2f24 > 0xe0000000adb8e1b0: at .VOP_RENAME_APV+0x190 > 0xe0000000adb8e240: at .kern_renameat+0x3c0 > 0xe0000000adb8e540: at .sys_rename+0x2c > 0xe0000000adb8e5c0: at .trap+0x65c > 0xe0000000adb8e780: at .powerpc_interrupt+0x290 > 0xe0000000adb8e820: user SC trap by 0x81010b7b8: srr1=3D0x900000000000f= 032 > r1=3D0x3fffffffffffc490 cr=3D0x34000028 xer=3D0x20000000 > ctr=3D0x81010b7b0 r2=3D0x8102c5950 > KDB: enter: panic >=20 > Using 'ls' or 'rm' on the file gives a "Bad file descriptor" error. > Using 'cat', I get another panic, but now during open. > Everything indicates that the file system is in an inconsistent state. >=20 > Therefore, I would just like to ask the following: is it expected for > kernel panics to happen when there are errors in the file system? >=20 > Thanks, > Leandro > _________________________ I can't make much sense of the ppc backtrace here, but I assume this is U= FS? If it is, UFS tends to panic to protect data in an error case and ZFS tends to go read-only in an error case. (over generalization here, but its been my experience). sean --D4ozwyZTZnd6kGLEV5PoJqGIsfeEfuWaB-- --13Pvg2EADJrDNSKvtkHoP8nJcj4EIaE6O Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlvQ3z1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LZt3AgAnO1Yl08iSOBg0GjK5d5nhHzGvmch46O2aTQK5/TUdx6IjdUx2lNDA5LG uSb/QnOPdCdlJjgizpdtph6QSiVHe3oR/3P7Tk6idaTwYFWcB48Pp7lsUBhg8v+/ jajleh/yIDvCgI+WQ+6/p2K0KvyGYa9VN7GHE0riXKBpMOPldT/csBcowmk7oCHf DOuT4JnK/HYz/Sqh9OBXJwbT39sEDBFi0BCHAbAeATtYZyJBxh1NQ9zpFx53D0ZB TXIS0QM/6BwzXh/3g/rW6EsNXk5sGampeRHqAWIRQmgYnIz8LXK/c5K5oF7++aF8 9Xj1shrWq17Ur1aBMDL3YH9slFJ6rQ== =Ufkm -----END PGP SIGNATURE----- --13Pvg2EADJrDNSKvtkHoP8nJcj4EIaE6O-- From owner-freebsd-current@freebsd.org Wed Oct 24 22:58:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78E2B1072D37 for ; Wed, 24 Oct 2018 22:58:13 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 169487D9FE for ; Wed, 24 Oct 2018 22:58:13 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: by mailman.ysv.freebsd.org (Postfix) id CF9E91072D36; Wed, 24 Oct 2018 22:58:12 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE1481072D35 for ; Wed, 24 Oct 2018 22:58:12 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga106.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D1EF7D9FC; Wed, 24 Oct 2018 22:58:11 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2018 15:56:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,422,1534834800"; d="scan'208";a="102226846" Received: from orsmsx103.amr.corp.intel.com ([10.22.225.130]) by fmsmga001.fm.intel.com with ESMTP; 24 Oct 2018 15:56:52 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.89]) by ORSMSX103.amr.corp.intel.com ([169.254.5.46]) with mapi id 14.03.0319.002; Wed, 24 Oct 2018 15:56:52 -0700 From: "Pieper, Jeffrey E" To: Matthew Macy , Peter Holm CC: "current@freebsd.org" Subject: Re: panic: mtx_lock() by idle thread ... mutex igb0 @ ../../../net/iflib.c:2084 Thread-Topic: panic: mtx_lock() by idle thread ... mutex igb0 @ ../../../net/iflib.c:2084 Thread-Index: AQHUarIoWESwCTM6fUOn390H6LKAjqUt5ekAgAEeZoA= Date: Wed, 24 Oct 2018 22:56:51 +0000 Message-ID: References: <20181023092053.GA22982@x2.osted.lan> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.10.3.181015 x-originating-ip: [10.241.224.76] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.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, 24 Oct 2018 22:58:13 -0000 SSB0aGluayB0aGlzIHdhcyBjYXVzZWQgYnkgaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL0Qx NzQwNCB3aGljaCBoYXMgYmVlbiByZXZlcnRlZC4gaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3Jn L0QxNzY3NCB3aWxsIHJlcGxhY2UgaXQuDQoNClRoYW5rcywNCkplZmYNCg0K77u/T24gMTAvMjMv MTgsIDM6NTQgUE0sICJvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcgb24gYmVoYWxm IG9mIE1hdHRoZXcgTWFjeSIgPG93bmVyLWZyZWVic2QtY3VycmVudEBmcmVlYnNkLm9yZyBvbiBi ZWhhbGYgb2YgbW1hY3lAZnJlZWJzZC5vcmc+IHdyb3RlOg0KDQogICAgV2lsbCBmaXguDQogICAg T24gVHVlLCBPY3QgMjMsIDIwMTggYXQgMjoyMSBBTSBQZXRlciBIb2xtIDxwZXRlckBob2xtLmNj PiB3cm90ZToNCiAgICA+DQogICAgPiBGZWVkaW5nIGVudHJvcHk6IC4NCiAgICA+IGxvMDogbGlu ayBzdGF0ZSBjaGFuZ2VkIHRvIFVQDQogICAgPiBwYW5pYzogbXR4X2xvY2soKSBieSBpZGxlIHRo cmVhZCAweGZmZmZmODAwMDM2YWMwMDAgb24gc2xlZXAgbXV0ZXggaWdiMCBAIC4uLy4uLy4uL25l dC9pZmxpYi5jOjIwODQNCiAgICA+IGNwdWlkID0gNA0KICAgID4gdGltZSA9IDE1NDAyODYwNjIN CiAgICA+IEtEQjogc3RhY2sgYmFja3RyYWNlOg0KICAgID4gZGJfdHJhY2Vfc2VsZl93cmFwcGVy KCkgYXQgZGJfdHJhY2Vfc2VsZl93cmFwcGVyKzB4MmIvZnJhbWUgMHhmZmZmZmUwMDc4NzZlNjEw DQogICAgPiB2cGFuaWMoKSBhdCB2cGFuaWMrMHgxYTMvZnJhbWUgMHhmZmZmZmUwMDc4NzZlNjcw DQogICAgPiBwYW5pYygpIGF0IHBhbmljKzB4NDMvZnJhbWUgMHhmZmZmZmUwMDc4NzZlNmQwDQog ICAgPiBfX210eF9sb2NrX2ZsYWdzKCkgYXQgX19tdHhfbG9ja19mbGFncysweDE1YS9mcmFtZSAw eGZmZmZmZTAwNzg3NmU3MjANCiAgICA+IGlmbGliX2FkbWluX2ludHJfZGVmZXJyZWQoKSBhdCBp ZmxpYl9hZG1pbl9pbnRyX2RlZmVycmVkKzB4MmEvZnJhbWUgMHhmZmZmZmUwMDc4NzZlNzUwDQog ICAgPiBlbV9tc2l4X2xpbmsoKSBhdCBlbV9tc2l4X2xpbmsrMHg4NC9mcmFtZSAweGZmZmZmZTAw Nzg3NmU3ODANCiAgICA+IGlmbGliX2Zhc3RfaW50cl9jdHgoKSBhdCBpZmxpYl9mYXN0X2ludHJf Y3R4KzB4MjEvZnJhbWUgMHhmZmZmZmUwMDc4NzZlN2EwDQogICAgPiBpbnRyX2V2ZW50X2hhbmRs ZSgpIGF0IGludHJfZXZlbnRfaGFuZGxlKzB4YmIvZnJhbWUgMHhmZmZmZmUwMDc4NzZlN2YwDQog ICAgPiBpbnRyX2V4ZWN1dGVfaGFuZGxlcnMoKSBhdCBpbnRyX2V4ZWN1dGVfaGFuZGxlcnMrMHg1 OC9mcmFtZSAweGZmZmZmZTAwNzg3NmU4MjANCiAgICA+IGxhcGljX2hhbmRsZV9pbnRyKCkgYXQg bGFwaWNfaGFuZGxlX2ludHIrMHg1Zi9mcmFtZSAweGZmZmZmZTAwNzg3NmU4NDANCiAgICA+IFhh cGljX2lzcjEoKSBhdCBYYXBpY19pc3IxKzB4ZDkvZnJhbWUgMHhmZmZmZmUwMDc4NzZlODQwDQog ICAgPiAtLS0gaW50ZXJydXB0LCByaXAgPSAweGZmZmZmZmZmODExZTZiZTYsIHJzcCA9IDB4ZmZm ZmZlMDA3ODc2ZTkxMCwgcmJwID0gMHhmZmZmZmUwMDc4NzZlOTEwIC0tLQ0KICAgID4gYWNwaV9j cHVfYzEoKSBhdCBhY3BpX2NwdV9jMSsweDYvZnJhbWUgMHhmZmZmZmUwMDc4NzZlOTEwDQogICAg PiBhY3BpX2NwdV9pZGxlKCkgYXQgYWNwaV9jcHVfaWRsZSsweDIzZC9mcmFtZSAweGZmZmZmZTAw Nzg3NmU5NjANCiAgICA+IGNwdV9pZGxlX2FjcGkoKSBhdCBjcHVfaWRsZV9hY3BpKzB4M2YvZnJh bWUgMHhmZmZmZmUwMDc4NzZlOTgwDQogICAgPiBjcHVfaWRsZSgpIGF0IGNwdV9pZGxlKzB4YTcv ZnJhbWUgMHhmZmZmZmUwMDc4NzZlOWEwDQogICAgPiBzY2hlZF9pZGxldGQoKSBhdCBzY2hlZF9p ZGxldGQrMHg1MTcvZnJhbWUgMHhmZmZmZmUwMDc4NzZlYTcwDQogICAgPiBmb3JrX2V4aXQoKSBh dCBmb3JrX2V4aXQrMHg4NC9mcmFtZSAweGZmZmZmZTAwNzg3NmVhYjANCiAgICA+IGZvcmtfdHJh bXBvbGluZSgpIGF0IGZvcmtfdHJhbXBvbGluZSsweGUvZnJhbWUgMHhmZmZmZmUwMDc4NzZlYWIw DQogICAgPiAtLS0gdHJhcCAwLCByaXAgPSAwLCByc3AgPSAwLCByYnAgPSAwIC0tLQ0KICAgID4g S0RCOiBlbnRlcjogcGFuaWMNCiAgICA+IFsgdGhyZWFkIHBpZCAxMSB0aWQgMTAwMDA3IF0NCiAg ICA+IFN0b3BwZWQgYXQgICAgICBrZGJfZW50ZXIrMHgzYjogbW92cSAgICAkMCxrZGJfd2h5DQog ICAgPiBkYj4geC9zIHZlcnNpb24NCiAgICA+IHZlcnNpb246ICAgICAgICBGcmVlQlNEIDEzLjAt Q1VSUkVOVCByMzM5NjM4IFBITy1HRU5FUklDXDAxMg0KICAgID4gZGI+DQogICAgPiAtLQ0KICAg ID4gUGV0ZXINCiAgICA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fDQogICAgPiBmcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0DQog ICAgPiBodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1j dXJyZW50DQogICAgPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1j dXJyZW50LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KICAgIF9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qu b3JnIG1haWxpbmcgbGlzdA0KICAgIGh0dHBzOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9s aXN0aW5mby9mcmVlYnNkLWN1cnJlbnQNCiAgICBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFp bCB0byAiZnJlZWJzZC1jdXJyZW50LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KICAgIA0KDQo= From owner-freebsd-current@freebsd.org Thu Oct 25 05:47:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFDD5FEC8A8; Thu, 25 Oct 2018 05:47:24 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 2712271A59; Thu, 25 Oct 2018 05:47:23 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 1A0D22AFF2; Thu, 25 Oct 2018 14:47:14 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id A2D8C16A3C; Thu, 25 Oct 2018 14:47:13 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 2BBC816A3B; Thu, 25 Oct 2018 14:47:10 +0900 (JST) Date: Thu, 25 Oct 2018 14:46:00 +0900 (JST) Message-Id: <20181025.144600.389146980619447771.yasu@utahime.org> To: freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Regression of dtrace on 13-CURRENT From: Yasuhiro KIMURA X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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, 25 Oct 2018 05:47:25 -0000 Hello. On 13-CURRENT r339548 build of lang/perl5.26 fails with configure error. ---------------------------------------------------------------------- yasu@rolling-vm-freebsd1[2100]% uname -a FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT r339548 GENERIC_UTAHIME amd64 yasu@rolling-vm-freebsd1[2101]% pwd /usr/ports/lang/perl5.26 yasu@rolling-vm-freebsd1[2102]% make ===> License ART10 GPLv1+ accepted by the user ===> perl5.26-5.26.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by perl5.26-5.26.2 for building ===> Extracting for perl5.26-5.26.2 => SHA256 Checksum OK for perl/perl-5.26.2.tar.xz. /bin/ln -s libperl.so.5.26.2 /usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/libperl.so /bin/ln -s libperl.so.5.26.2 /usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/libperl.so.5.26 ===> Patching for perl5.26-5.26.2 ===> Applying FreeBSD patches for perl5.26-5.26.2 /usr/bin/sed -i.bak -e 's|/usr/local|/usr/local|g' /usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/Configure /usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/hints/freebsd.sh /usr/bin/sed -i.bak -e '/do_installprivlib = 0 if .versiononly/d; /^if.*nopods.*versiononly || /s/.*/if (1) {/' /usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/installperl ===> Configuring for perl5.26-5.26.2 First let's make sure your kit is complete. Checking... (snip) Colon-separated list of additional directories for perl to search? [none] Checking out function prototypes... Support DTrace if available? [y] Where is the dtrace executable? (~name ok) [/usr/sbin/dtrace] *** Configure: Fatal Error: /usr/sbin/dtrace doesn't support -h flag *** *** Your installed dtrace doesn't support the -h switch to compile a D *** program into a C header. Can't continue. ===> Script "Configure" failed unexpectedly. Please report the problem to mat@FreeBSD.org [maintainer] and attach the "/usr0/freebsd/ports/work/net/freebsd/ports/head/lang/perl5.26/work/perl-5.26.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /net/freebsd/ports/head/lang/perl5.26 yasu@rolling-vm-freebsd1[2103]% ---------------------------------------------------------------------- In perl-5.26.2/Configure there is following test. ---------------------------------------------------------------------- if $test -f $dtrace then if $dtrace -h -s ../perldtrace.d \ -o perldtrace.tmp >/dev/null 2>&1 \ && rm -f perldtrace.tmp then echo " " echo "Good: your $dtrace knows about the -h flag." else cat >&2 < Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91D78FEE44C for ; Thu, 25 Oct 2018 06:29:48 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 3254B72FCC; Thu, 25 Oct 2018 06:29:48 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 5482AE3FD6; Thu, 25 Oct 2018 00:30:19 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xUkKdPnHcxHJ; Thu, 25 Oct 2018 00:30:19 -0600 (MDT) Received: from Rebeccas-iPhone.mail (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 00:30:19 -0600 (MDT) Date: Thu, 25 Oct 2018 00:25:12 -0600 From: Rebecca Cran To: freebsd-current@freebsd.org Cc: imp@freebsd.org Message-ID: Subject: 12-BETA1 contains warning about non-PNP ISA device X-Mailer: Airmail iOS (372) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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, 25 Oct 2018 06:29:48 -0000 I noticed a warning on a new AMD system running 12-BETA1: =20 non-PNP ISA device will be removed from GENERIC in =46reeBSD 12. =20 It looks like it was introduced by Warner in r327120. Should those device= s have been removed already=3F =E2=80=94 =20 Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 07:37:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EC74FFC72E for ; Thu, 25 Oct 2018 07:37:54 +0000 (UTC) (envelope-from current@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CA7AC75192 for ; Thu, 25 Oct 2018 07:37:53 +0000 (UTC) (envelope-from current@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8F7D8FFC72D; Thu, 25 Oct 2018 07:37:53 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DBD2FFC72C for ; Thu, 25 Oct 2018 07:37:53 +0000 (UTC) (envelope-from current@freebsd.org) Received: from host079.com.br (host079.com.br [104.131.98.123]) by mx1.freebsd.org (Postfix) with ESMTP id 2011C75191 for ; Thu, 25 Oct 2018 07:37:53 +0000 (UTC) (envelope-from current@freebsd.org) Received: by host079.com.br (Postfix, from userid 1000) id 2FFBD2AF903; Thu, 25 Oct 2018 02:49:49 -0400 (EDT) To: current@freebsd.org Subject: Información importante al cliente. - clave (10535) X-Mailer: Microsoft Office Outlook, Build 17.551210 From: current@freebsd.org Reply-To: current@freebsd.org X-Mailer: iGMail [www.ig.com.br] X-Originating-Email: current@freebsd.org X-Sender: current@freebsd.org X-iGspam-global: Unsure, spamicity=0.570081 - pe=5.74e-01 - pf=0.574081 - pg=0.574081 Message-Id: <20181025072724.2FFBD2AF903@host079.com.br> Date: Thu, 25 Oct 2018 02:49:49 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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, 25 Oct 2018 07:37:54 -0000 From owner-freebsd-current@freebsd.org Thu Oct 25 09:14:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D22B510085D1 for ; Thu, 25 Oct 2018 09:14:43 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "saper.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6156078698; Thu, 25 Oct 2018 09:14:43 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id w9P9EeD2003159 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 Oct 2018 09:14:40 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1540458881; bh=Ku+BrGseaPdgQ/kBCx8MQLeCDpGbBXGt+Mc0SvOJeDk=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=XWQ/mwiof2B1jNPNGMYlTS9q3RXEtMgyXbVOt7KqnOKlUxAqBNhUvofKC30jx1/nD wyl5sTvKB+UJHC03peS6KABJsa8veNiQR15mxs0XB3zTpoSrhkmJBlbzYiHRtMljdz 8W6sZv3UREAoUJnnJTRZNF8iWccTbtFTIsRN0MEU= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id w9P9EeeU003156; Thu, 25 Oct 2018 09:14:40 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Thu, 25 Oct 2018 09:14:39 +0000 From: Marcin Cieslak To: John Baldwin cc: FreeBSD Current Subject: Re: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 In-Reply-To: <65f4cac9-99be-265f-e461-b166d52d226b@FreeBSD.org> Message-ID: References: <65f4cac9-99be-265f-e461-b166d52d226b@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="1563967779-2031317455-1540458880=:5494" 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, 25 Oct 2018 09:14:44 -0000 --1563967779-2031317455-1540458880=:5494 Content-Type: text/plain; charset=US-ASCII On Wed, 24 Oct 2018, John Baldwin wrote: > On 10/23/18 10:58 AM, Marcin Cieslak wrote: > > This GDB was configured as "amd64-marcel-freebsd"...BFD: /boot/kernel/kernel: invalid relocation type 37 > > BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 > > > > The kernel has been built on 11.1 with LD=/usr/bin/ld.lld > > > > Is this something that matters at all? > > It is not something that is likely to be fixed. If you pkg install gdb from > ports, is the kgdb it includes able to examine the crash dump? Not really (using 8.2 from ports): # /usr/local/bin/kgdb82 -n 5 /usr/obj/usr/src/sys/GENERIC/kernel.debug GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD] Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd11.1". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/obj/usr/src/sys/GENERIC/kernel.debug...done. thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) With regular base kgdb I can open it but I can't get any backtrace or anything: Cannot access memory at address 0x0 (kgdb) info reg rax 0x0 0 rbx 0x0 0 rcx 0x0 0 rdx 0x0 0 rsi 0x0 0 rdi 0x0 0 rbp 0x0 0x0 rsp 0x0 0x0 r8 0x0 0 r9 0x0 0 r10 0x0 0 r11 0x0 0 r12 0x0 0 r13 0x0 0 r14 0x0 0 r15 0x0 0 rip 0x0 0 eflags 0x0 0 cs 0x0 0 ss 0x0 0 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 What should I try next? at what stage is bfd involved in the savecore process? Marcin --1563967779-2031317455-1540458880=:5494 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: BASE64 Content-Description: S/MIME Cryptographic Signature Content-Disposition: attachment; filename=smime.p7s MIIOSwYJKoZIhvcNAQcCoIIOPDCCDjgCAQExDzANBglghkgBZQMEAgEFADAL BgkqhkiG9w0BBwGgggqQMIIElzCCA3+gAwIBAgIOSBtqCKJEiNNcmz3JSA0w DQYJKoZIhvcNAQELBQAwTDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENB IC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24xEzARBgNVBAMTCkdsb2JhbFNp Z24wHhcNMTYwNjE1MDAwMDAwWhcNMjQwNjE1MDAwMDAwWjBdMQswCQYDVQQG EwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xv YmFsU2lnbiBQZXJzb25hbFNpZ24gMSBDQSAtIFNIQTI1NiAtIEczMIIBIjAN BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyrCba00KOKyGuwh9h+/MAcZm ZUF9OxGKA56AADHaDE08rB0WEbgm6J4XvJP3OGQ7cgHdVJu6XMZkRd6EcfjD yRrIwE6oAVWJe57co3gKk/XxvuubSZuUahrcOiv3D2qaHwva4zumubxQQI4f unEzRIJHPiNjaq0cCcZsMcp5pxsEz8aG0sr8Oh80sxKNnzPmuUETLESktfMC pQKHUGmWXLsG6sgCZOezUjDjKpPKW7l4PUt0TEBEyqLhifv9/YPn5C4o10PP daDazZPeKNif2PVQ5u0HRnkFrHh4wmmrMtY22Mse3eR01gD6rEEGWf+gdzuy EQE+ZVlNhCP4gXjdBQIDAQABo4IBZDCCAWAwDgYDVR0PAQH/BAQDAgEGMCcG A1UdJQQgMB4GCCsGAQUFBwMCBggrBgEFBQcDBAYIKwYBBQUHAwkwEgYDVR0T AQH/BAgwBgEB/wIBADAdBgNVHQ4EFgQUlifCwqX3HPgCenpkr2NvMtKYwrEw HwYDVR0jBBgwFoAUj/BLf6guRSSuTVD6Y5qL3uLdG7wwPgYIKwYBBQUHAQEE MjAwMC4GCCsGAQUFBzABhiJodHRwOi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20v cm9vdHIzMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuZ2xvYmFsc2ln bi5jb20vcm9vdC1yMy5jcmwwWQYDVR0gBFIwUDALBgkrBgEEAaAyASgwQQYJ KwYBBAGgMgFfMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNp Z24uY29tL3JlcG9zaXRvcnkvMA0GCSqGSIb3DQEBCwUAA4IBAQCxh3ekjKKy RrUdfI6D1U7qUggdFLksiU+KiIqJzJG6GXcQ2KiBy2tF3+KYb0IixXMpIVli VXlcD5Vh4tiMxJ4WONMFt3f7/53gSXLf24WMwErubc+mGMzgUGE5HKC98PcK UV/5pPggQdzPxCBNeiXnLU1tCGYhPatFTDhUBGaVhBeuUCbgR9gpXJ9guqrD OVwouKvovdIeI5KEAcoAAiSL6naeLk/GbKUaBFa2RxXC17e+YyBWtWlWDEM3 1V8pUIx76lkO8IJYREhLcg/LnyoYy5wcrzI6pbX2vw1x/jR3GHSC1AEdoqbE xui2XLLlSa6y9yQNgdkPz7GTLmpwIT+dMIIF8TCCBNmgAwIBAgIMGk4Oe/1h 2+wMOby/MA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQK ExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQDEypHbG9iYWxTaWduIFBlcnNv bmFsU2lnbiAxIENBIC0gU0hBMjU2IC0gRzMwHhcNMTcwNTI1MDg0NDE2WhcN MjAwNTI1MDg0NDE2WjA8MRkwFwYDVQQDDBBzYXBlckBzYXBlci5pbmZvMR8w HQYJKoZIhvcNAQkBFhBzYXBlckBzYXBlci5pbmZvMIICIjANBgkqhkiG9w0B AQEFAAOCAg8AMIICCgKCAgEA2sO3aQNus/oe4ZBZ4fu1Y1mzxnUYAkb4k/dw gMFc2Kd0eRoOY0AHj4rTEi/vVzzizxjLbEwXzQ9cBEAu/PqS8WsOmhZXtlfi szPDmP7ZpOwmNTWKSd9O7jHu9uTCGfEOsocQNYH2ULD1gVFkgKb8jHf+3u9d uCzh6qMomTtwLrCGEP70Lq385xUzRaD6qbOeIB99tpzgvMR6Z0GPTt4z8tLM kfdtohq5llwZ5vYnj/hJohVS9iLMQMHW4nuLj/mLZNaYE1CWJBT1rBwn5YPJ uR6811O9eAP7aX4iG8k1jkiBh+QNgGRBIK4GIdqy7IVRhA7v2OlpLYHMk4zP 9Fs3M+56QromVKBnxfzLhuYMUK6ugj9jwskNVitqlEFUeyfgvmR1jnPRp1Nd XGJllTNwGicR8wkaRj14RxfrvTZfwXs8OBODKFupqun/tNzdpOgyHMGQACss 9yv2SnLGCJvJK3rGIdRZEiUhLZH/Ct4L92dBhev+SjUqWKbHb4yIlGMgLdoh nwqatuWw7iyOeInjcinX7ghiIKDWhulUN493Fzl6kaUBtIIcrb7jzZ2pHAQT WUmuVnCTHk6NtoWB09lvuK77fw4GfxLWDFWkBQiJYPVBrmxlrkCKzrWdTMfS W9BiEC10jT1sSimUBIjDz22RkfsApeBJoAIWjiOZogILu9MCAwEAAaOCAdAw ggHMMA4GA1UdDwEB/wQEAwIFoDCBngYIKwYBBQUHAQEEgZEwgY4wTQYIKwYB BQUHMAKGQWh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dz cGVyc29uYWxzaWduMXNoYTJnM29jc3AuY3J0MD0GCCsGAQUFBzABhjFodHRw Oi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24xc2hhMmcz MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBz Oi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMAkGA1UdEwQCMAAw RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9n c3BlcnNvbmFsc2lnbjFzaGEyZzMuY3JsMBsGA1UdEQQUMBKBEHNhcGVyQHNh cGVyLmluZm8wHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1Ud DgQWBBReBINaGUKUo7HCrIjsKLKERu6ooTAfBgNVHSMEGDAWgBSWJ8LCpfcc +AJ6emSvY28y0pjCsTANBgkqhkiG9w0BAQsFAAOCAQEAC0VK968ySq/6B+Kd ecjVThQOKtVXuG17Krfk0xz7OPYR/V+qZtBFm2Uc6tkUEmAmq3Tyf+SE3TTX Q58eJFq0uCTUhIY714ioJs1uVWBz8rPyJ3swkOfDaUXUxkQsBsf73VfKjUk4 kB5MTrApLYUe35NmEY3FqyyX13elhW1tp864vOKM2Git61cYoRn/bwd/z2JM Zkxwkd5JgvmM+p4Da+WO4CUsGzdrZEH8X/8NQIzWtUDIh7VEQZFX5fot/KvH Am8AajtpmNqTfMyg6LfcfJUXSFqXn/KEWu4Td62vX6Pd70dYKUZxnLwYvGqG A4Ktrp9zyrUzxLbmdaPln7CstjGCA38wggN7AgEBMG0wXTELMAkGA1UEBhMC QkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2Jh bFNpZ24gUGVyc29uYWxTaWduIDEgQ0EgLSBTSEEyNTYgLSBHMwIMGk4Oe/1h 2+wMOby/MA0GCWCGSAFlAwQCAQUAoIHkMBgGCSqGSIb3DQEJAzELBgkqhkiG 9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE4MTAyNTA5MTQ0MFowLwYJKoZIhvcN AQkEMSIEIJ6wMTa3A3IcG/BRrwZYGTdrb9A4POn9XblUMpLkcmojMHkGCSqG SIb3DQEJDzFsMGowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjALBglghkgB ZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIIC AGWaesytIFMUgP2jTqH5gItWNiOGey7SUgByXyVgJh8GVs1qFEoXd/dMyE2o kmsMKZ1XRk/2zCZCQVZN6TJSeoCYSjVSxek8dLflzGt2U04apAbMwqAzzxHw 2QSYQEZtFuP9d2rRsPAF325n/eejDfObcCICbo6DdAwua9r6dpYqnpNsT9oP q5rW6oWo/gX8s4+Ek/02L06l1nF/JXEa2W5Uqks3PBQypeaP1dM23vqoUPpc ZvfHixEXvl1RfDCFizVEYPEfhHXucFZWW4U81DoMKToKqY20eHbd95IfvJXu E14Yy5OfZs8a8+11aP4etpXY+eSSGleeNGgvPh9oDIk6k5gQG3KD74VGpxqW d/9Cp2DeQB8exvtEIGpi0/ISsHNoopkISeOMOy3JUGrjizzVzuPbzbKFWoRD ODnswdieFskdIlCsvnd9zMd98Fu0gBl4cxVP0OVQJOJUjb5CT8YeRV9rH2xb aVwbxgQnzZ1MZp3fCZw6HYqSHGvRx9NLfPIbD37Z8uInEhoBthS2G0dGH1M7 wIMf2bXMxxgawjv6Fe0RfiKm1AbehFFyNNvjf1eU3G/lPfR47Obf0q1//Vtl kny6qy7gCbC6///2gfdKGKi4GV611qoVAKbYOnIqChTM1VpCsL8R0olIdoef PINJYmQfweeEgDjUCJVV3gO9 --1563967779-2031317455-1540458880=:5494-- From owner-freebsd-current@freebsd.org Thu Oct 25 09:16:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DD1B10086EC; Thu, 25 Oct 2018 09:16:56 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 29072787C5; Thu, 25 Oct 2018 09:16:55 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 0643D2B03B; Thu, 25 Oct 2018 18:16:52 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 767FF16B64; Thu, 25 Oct 2018 18:16:52 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 8338416B63; Thu, 25 Oct 2018 18:16:51 +0900 (JST) Date: Thu, 25 Oct 2018 18:16:40 +0900 (JST) Message-Id: <20181025.181640.425868578161549129.yasu@utahime.org> To: freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: Regression of dtrace on 13-CURRENT From: Yasuhiro KIMURA In-Reply-To: <20181025.144600.389146980619447771.yasu@utahime.org> References: <20181025.144600.389146980619447771.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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, 25 Oct 2018 09:16:56 -0000 From: Yasuhiro KIMURA Subject: Regression of dtrace on 13-CURRENT Date: Thu, 25 Oct 2018 14:46:00 +0900 (JST) > So there is regression about dtrace between r339436 and r339548. I submitted this problem to Bugzilla. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Yasuhiro KIMURA From owner-freebsd-current@freebsd.org Thu Oct 25 11:02:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A84A21039B82 for ; Thu, 25 Oct 2018 11:02:59 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1253E7C0E8; Thu, 25 Oct 2018 11:02:58 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9PB2rYD034095; Thu, 25 Oct 2018 04:02:53 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9PB2pXv034094; Thu, 25 Oct 2018 04:02:51 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> Subject: Re: 12-BETA1 contains warning about non-PNP ISA device In-Reply-To: To: Rebecca Cran Date: Thu, 25 Oct 2018 04:02:51 -0700 (PDT) CC: freebsd-current@freebsd.org, imp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 25 Oct 2018 11:02:59 -0000 > I noticed a warning on a new AMD system running 12-BETA1: > > non-PNP ISA device will be removed from GENERIC in FreeBSD 12. Can you please reply with the specific device. If you have seen one it may be an issue to removing it, especially if this is on a "new AMD" system. > > It looks like it was introduced by Warner in r327120. Should those devices have been removed already? Yes, and they well be removed from GENERIC in BETA2, as I just approved the RFA to merge that fix to stable/12. Thanks, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu Oct 25 11:38:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27BED107112A for ; Thu, 25 Oct 2018 11:38:49 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "saper.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB2057D3B7 for ; Thu, 25 Oct 2018 11:38:48 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id w9PBcleh006956 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 25 Oct 2018 11:38:47 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1540467527; bh=M6OfRtBBchx/g8E8fgGRrN5+VGEdixwaBoPL0KTeH18=; h=Date:From:To:Subject; b=JiUJm7v78VHTfgXXHrchJY7h0yIv8Bg8t+K2DqPxBIIemmZAM4KkCsdlslwVcYimn Zwjks1MhU72zZJgmYK27i4sIxQ737ThdUo0EWjB3XXxOyvhznns2M8gGrv5SVqwV5A SSfPt6pySJJvIfPrU4GrihifzMLjlqYprI7+p3jc= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id w9PBclw2006953 for ; Thu, 25 Oct 2018 11:38:47 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Thu, 25 Oct 2018 11:38:46 +0000 From: Marcin Cieslak To: FreeBSD Current Subject: fix WARNING pid 24503 (uhsoctl): ioctl sign-extension ioctl ffffffff8044692b Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="1563967779-879112639-1540467527=:5494" 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, 25 Oct 2018 11:38:49 -0000 --1563967779-879112639-1540467527=:5494 Content-Type: text/plain; charset=US-ASCII The following patch seems to fix the signed ioctl value warnings in uhsoctl(). The code is the same in the current and stable branches. Marcin Index: usr.sbin/uhsoctl/uhsoctl.c =================================================================== --- usr.sbin/uhsoctl/uhsoctl.c (revision 339406) +++ usr.sbin/uhsoctl/uhsoctl.c (working copy) @@ -360,7 +360,7 @@ /* Add/remove IP address from an interface */ static int -ifaddr_ad(int d, const char *ifnam, struct sockaddr *sa, struct sockaddr *mask) +ifaddr_ad(unsigned long d, const char *ifnam, struct sockaddr *sa, struct sockaddr *mask) { struct ifaliasreq req; int fd, error; --1563967779-879112639-1540467527=:5494 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: BASE64 Content-Description: S/MIME Cryptographic Signature Content-Disposition: attachment; filename=smime.p7s MIIOSwYJKoZIhvcNAQcCoIIOPDCCDjgCAQExDzANBglghkgBZQMEAgEFADAL BgkqhkiG9w0BBwGgggqQMIIElzCCA3+gAwIBAgIOSBtqCKJEiNNcmz3JSA0w DQYJKoZIhvcNAQELBQAwTDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENB IC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24xEzARBgNVBAMTCkdsb2JhbFNp Z24wHhcNMTYwNjE1MDAwMDAwWhcNMjQwNjE1MDAwMDAwWjBdMQswCQYDVQQG EwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEzMDEGA1UEAxMqR2xv YmFsU2lnbiBQZXJzb25hbFNpZ24gMSBDQSAtIFNIQTI1NiAtIEczMIIBIjAN BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyrCba00KOKyGuwh9h+/MAcZm ZUF9OxGKA56AADHaDE08rB0WEbgm6J4XvJP3OGQ7cgHdVJu6XMZkRd6EcfjD yRrIwE6oAVWJe57co3gKk/XxvuubSZuUahrcOiv3D2qaHwva4zumubxQQI4f unEzRIJHPiNjaq0cCcZsMcp5pxsEz8aG0sr8Oh80sxKNnzPmuUETLESktfMC pQKHUGmWXLsG6sgCZOezUjDjKpPKW7l4PUt0TEBEyqLhifv9/YPn5C4o10PP daDazZPeKNif2PVQ5u0HRnkFrHh4wmmrMtY22Mse3eR01gD6rEEGWf+gdzuy EQE+ZVlNhCP4gXjdBQIDAQABo4IBZDCCAWAwDgYDVR0PAQH/BAQDAgEGMCcG A1UdJQQgMB4GCCsGAQUFBwMCBggrBgEFBQcDBAYIKwYBBQUHAwkwEgYDVR0T AQH/BAgwBgEB/wIBADAdBgNVHQ4EFgQUlifCwqX3HPgCenpkr2NvMtKYwrEw HwYDVR0jBBgwFoAUj/BLf6guRSSuTVD6Y5qL3uLdG7wwPgYIKwYBBQUHAQEE MjAwMC4GCCsGAQUFBzABhiJodHRwOi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20v cm9vdHIzMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuZ2xvYmFsc2ln bi5jb20vcm9vdC1yMy5jcmwwWQYDVR0gBFIwUDALBgkrBgEEAaAyASgwQQYJ KwYBBAGgMgFfMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNp Z24uY29tL3JlcG9zaXRvcnkvMA0GCSqGSIb3DQEBCwUAA4IBAQCxh3ekjKKy RrUdfI6D1U7qUggdFLksiU+KiIqJzJG6GXcQ2KiBy2tF3+KYb0IixXMpIVli VXlcD5Vh4tiMxJ4WONMFt3f7/53gSXLf24WMwErubc+mGMzgUGE5HKC98PcK UV/5pPggQdzPxCBNeiXnLU1tCGYhPatFTDhUBGaVhBeuUCbgR9gpXJ9guqrD OVwouKvovdIeI5KEAcoAAiSL6naeLk/GbKUaBFa2RxXC17e+YyBWtWlWDEM3 1V8pUIx76lkO8IJYREhLcg/LnyoYy5wcrzI6pbX2vw1x/jR3GHSC1AEdoqbE xui2XLLlSa6y9yQNgdkPz7GTLmpwIT+dMIIF8TCCBNmgAwIBAgIMGk4Oe/1h 2+wMOby/MA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNVBAYTAkJFMRkwFwYDVQQK ExBHbG9iYWxTaWduIG52LXNhMTMwMQYDVQQDEypHbG9iYWxTaWduIFBlcnNv bmFsU2lnbiAxIENBIC0gU0hBMjU2IC0gRzMwHhcNMTcwNTI1MDg0NDE2WhcN MjAwNTI1MDg0NDE2WjA8MRkwFwYDVQQDDBBzYXBlckBzYXBlci5pbmZvMR8w HQYJKoZIhvcNAQkBFhBzYXBlckBzYXBlci5pbmZvMIICIjANBgkqhkiG9w0B AQEFAAOCAg8AMIICCgKCAgEA2sO3aQNus/oe4ZBZ4fu1Y1mzxnUYAkb4k/dw gMFc2Kd0eRoOY0AHj4rTEi/vVzzizxjLbEwXzQ9cBEAu/PqS8WsOmhZXtlfi szPDmP7ZpOwmNTWKSd9O7jHu9uTCGfEOsocQNYH2ULD1gVFkgKb8jHf+3u9d uCzh6qMomTtwLrCGEP70Lq385xUzRaD6qbOeIB99tpzgvMR6Z0GPTt4z8tLM kfdtohq5llwZ5vYnj/hJohVS9iLMQMHW4nuLj/mLZNaYE1CWJBT1rBwn5YPJ uR6811O9eAP7aX4iG8k1jkiBh+QNgGRBIK4GIdqy7IVRhA7v2OlpLYHMk4zP 9Fs3M+56QromVKBnxfzLhuYMUK6ugj9jwskNVitqlEFUeyfgvmR1jnPRp1Nd XGJllTNwGicR8wkaRj14RxfrvTZfwXs8OBODKFupqun/tNzdpOgyHMGQACss 9yv2SnLGCJvJK3rGIdRZEiUhLZH/Ct4L92dBhev+SjUqWKbHb4yIlGMgLdoh nwqatuWw7iyOeInjcinX7ghiIKDWhulUN493Fzl6kaUBtIIcrb7jzZ2pHAQT WUmuVnCTHk6NtoWB09lvuK77fw4GfxLWDFWkBQiJYPVBrmxlrkCKzrWdTMfS W9BiEC10jT1sSimUBIjDz22RkfsApeBJoAIWjiOZogILu9MCAwEAAaOCAdAw ggHMMA4GA1UdDwEB/wQEAwIFoDCBngYIKwYBBQUHAQEEgZEwgY4wTQYIKwYB BQUHMAKGQWh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dz cGVyc29uYWxzaWduMXNoYTJnM29jc3AuY3J0MD0GCCsGAQUFBzABhjFodHRw Oi8vb2NzcDIuZ2xvYmFsc2lnbi5jb20vZ3NwZXJzb25hbHNpZ24xc2hhMmcz MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBz Oi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMAkGA1UdEwQCMAAw RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9n c3BlcnNvbmFsc2lnbjFzaGEyZzMuY3JsMBsGA1UdEQQUMBKBEHNhcGVyQHNh cGVyLmluZm8wHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1Ud DgQWBBReBINaGUKUo7HCrIjsKLKERu6ooTAfBgNVHSMEGDAWgBSWJ8LCpfcc +AJ6emSvY28y0pjCsTANBgkqhkiG9w0BAQsFAAOCAQEAC0VK968ySq/6B+Kd ecjVThQOKtVXuG17Krfk0xz7OPYR/V+qZtBFm2Uc6tkUEmAmq3Tyf+SE3TTX Q58eJFq0uCTUhIY714ioJs1uVWBz8rPyJ3swkOfDaUXUxkQsBsf73VfKjUk4 kB5MTrApLYUe35NmEY3FqyyX13elhW1tp864vOKM2Git61cYoRn/bwd/z2JM Zkxwkd5JgvmM+p4Da+WO4CUsGzdrZEH8X/8NQIzWtUDIh7VEQZFX5fot/KvH Am8AajtpmNqTfMyg6LfcfJUXSFqXn/KEWu4Td62vX6Pd70dYKUZxnLwYvGqG A4Ktrp9zyrUzxLbmdaPln7CstjGCA38wggN7AgEBMG0wXTELMAkGA1UEBhMC QkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExMzAxBgNVBAMTKkdsb2Jh bFNpZ24gUGVyc29uYWxTaWduIDEgQ0EgLSBTSEEyNTYgLSBHMwIMGk4Oe/1h 2+wMOby/MA0GCWCGSAFlAwQCAQUAoIHkMBgGCSqGSIb3DQEJAzELBgkqhkiG 9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE4MTAyNTExMzg0NlowLwYJKoZIhvcN AQkEMSIEIFS73cS1xsDW4DAX24yl1Tk4LgcrsIreomA28S5dfBFnMHkGCSqG SIb3DQEJDzFsMGowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBFjALBglghkgB ZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIIC AGermuSsq4GsQzdNixJQsOpQkJJbqSDCDsLnDuLOcDjr4yNkXPBO8ZBXhhty i71EIF8hZj+oFsMdTgJBOI9tY9u444bHxbbOlElblYhEF96/Qkae7ZupWHvs aZXvxsh/aAUz4yInYNwa9IrvgDxcxWTGZ5r9tc1O4jv09OMoZrmkTbxtPxtp 1yD4FpkrnSmhXcSlxfbPOxn9ahoF2UNnB0QPXnu7DYNNE7GAJOiwLouBrvSe j+kvgAzQdEqyCQ5F0+qCX1o77AgJI1478ihD1XanxOxi+vwwQtaM4gT97d9U 4fvydGDLZRwoRrF2/NUWJLXMVh69Un/XFO63SUpfWrbW7f/jPQTfU+ks7/yc QgugB3Avz8Mz0URgp253V2unBEdtCUrIbzcRs1QWXOZaJ+XHkrFuekJjSJ5W 3OhFi61SlEKuUg5+GTva2tRYBQ6dgZ9buvTiL9ShQWXO7s/kbrh++S3FwTRi Bc5zFc7AcMHSjQ3ukowT8Zz3gmVezplmg8t8vDuF7LK8rwL4h0HgxzvK0WIo dqHvwBed6DEqVeW9J7a0lJuxyfNkELce5yEQ/gHWR3G0Uek2cj3u2D9YJ78v 7LLWihXIf7+zVJO9F+bBme13FRql3OojS3zmnkfUn0xV9ygjqvqGQ6i+u/7y cHzh4UZXZV6XsRI6XF9ce0wq --1563967779-879112639-1540467527=:5494-- From owner-freebsd-current@freebsd.org Thu Oct 25 11:58:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16CD31071CE0 for ; Thu, 25 Oct 2018 11:58:00 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8AE167E14B; Thu, 25 Oct 2018 11:57:59 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9PBvtIc034407; Thu, 25 Oct 2018 04:57:55 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9PBvsWg034406; Thu, 25 Oct 2018 04:57:54 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810251157.w9PBvsWg034406@pdx.rh.CN85.dnsmgr.net> Subject: Re: 12-BETA1 contains warning about non-PNP ISA device In-Reply-To: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> To: "Rodney W. Grimes" Date: Thu, 25 Oct 2018 04:57:54 -0700 (PDT) CC: Rebecca Cran , freebsd-current@freebsd.org, imp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 25 Oct 2018 11:58:00 -0000 > > I noticed a warning on a new AMD system running 12-BETA1: > > > > non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > Can you please reply with the specific device. > If you have seen one it may be an issue to removing it, > especially if this is on a "new AMD" system. Further investigation shows me that this comes from generic code in sys/isa/isa_common.c, and does not come from any specific driver markings. > > It looks like it was introduced by Warner in r327120. Should those devices have been removed already? > > Yes, and they well be removed from GENERIC in BETA2, > as I just approved the RFA to merge that fix to stable/12. That is an incorrect statement, what I approved does not in any way effect this error that I can tell. Thanks, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu Oct 25 12:49:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E79A1074C16 for ; Thu, 25 Oct 2018 12:49:54 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic307-54.consmr.mail.ir2.yahoo.com (sonic307-54.consmr.mail.ir2.yahoo.com [87.248.110.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABFAD8066F for ; Thu, 25 Oct 2018 12:49:53 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: p.u.vlEVM1kCxPwL8nSzfdmmmkyO2SvCBD5Gex9wUD10BNL5FpLro8_.0LdlEkF FhJjsNQzmxiSOmHWxLvpRpDiayCSmvojEZtBMIdKdA2HmxwQRkP1YSZuRPOZUU4R4pWrxcTBfQ6I wrLEFmyPyJP8QxvKx.p_D4EQTXM6xRa65rHOO0N5jBWtr_Xdtn1C1YIUqd.1z6F0JjDXGQ_V24hr SwBcBYqoKIDJ79K5_LwAnkZ153r7T61.z579KTkc3HrTT2eR.MIbkZOLdpw8FQFIr1Z9A6xh7nlS y_uYw1bNUWens0wgjtrbl0S2ti9vN15c0Ag.c5DSX9YsDZxtdhiq38FdyDoz8b8s1pJnETrK.sNC msVfHMyFUTlFm0LKuu2AM.R9Q_Y476B295zuUQ33B4gRcgum8JwITVfxwnJ7TmItk5Q0hssedbSQ Liy26LKCw2F4roQsekd1yIMsG0J80v7pIyG3hVfJj18L8CtrBS9LNPaSWeo7FhuImQK8wYgIF2NI oRuicdhYuty9rMYWOunLhs_FUhhMHsXhLwnHeCVURIO_wtMN6D3Ih.DvF1R1c6lyNJ9HVDgY76WX vtOahVmJ.zyEPcC3UtKn624NSSiZvNvFg0JkPzTqYTxsdLRjbbgMdC7ADHueT1oOoeqZeSm.wU3u WikihfFjkaqkMH0wn4ZwUqasUCerGb5HDIATlPWpLn0vzgvSeuKAvXUL_.sdGQgafjj5SLDo0Duc ztRpL8SnIfOgQzCjuN9NwwvV2NSfv0uKkmwm7QORFsfq8oWZTtZbKzGcrk_wDngcj.MTIWay4wk6 A20TS30Txpi6WiN6DXtkba6BKzFrIPxPgY8lfNUPElv6VQKcd5jIKrh3j1HSVLLH6Cb3.FwRfRDJ IQVHc0wySkHjKclzz0yHISR4i7Y60t8.tWqz.O_9PObf3nZHa1aH9kXSpfEKa_xYX0xXVmWbO9jh rtLYeo.X9ZgSvWjNLvB_gBssmpIPJOr6og8g3LHo._Z_C5rDQoo09elM1PNr2DObQg1FBM.87pCN 51ty3lCIwQsB7fa0S1CYgAzHL.KmC8k6Tzo_PNcksLMsiqERhIgP195zgYI_V6HsGyvAeFB9oxAB HNPuoKw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ir2.yahoo.com with HTTP; Thu, 25 Oct 2018 12:49:46 +0000 Received: from 80.244.81.252 (EHLO [10.0.0.5]) ([80.244.81.252]) by smtp415.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID ed2a0e636c9ea7c97bfe66b48527f53e for ; Thu, 25 Oct 2018 12:49:44 +0000 (UTC) To: freebsd-current From: Per Gunnarsson Openpgp: preference=signencrypt Autocrypt: addr=p.gunnarsson@yahoo.com; keydata= xsJuBFEarnMRCADHJa1GgO8EKAbE/ueVE4e+x8rImF6O6NUoTngCzuEjhXDyV4bmb7qSZcsQ /kIUfAy1BF5H5imdMdez5q4Ia78qJ/8kQMt+jWnwTIcWl+vj5wnDHJxwsr+SXZvQa//Fwjc7 31sHFtplTG1NZAaZgMSp4zYkJqA2c1a4tZ9b9zW/zvbsqfs4s5gU+8TSqA+0Q9JIMpJ0jGpi +NKtsn7eOomR7surIzQj7sLIwEoOwDsslvZR3Jy3xEwtbkI8pixP48LvrFrWW3O7ExZiMYGx OxcEPfc0yrAzuySBVXoO0ksOY86cqNubOCqvhqJEYKmTnUb+9clIJeHnGXuGgwAfNbFXAQCA 8SDkW9Poskc6UDE/Hem91De6MFrEgijOCbKOHVWWWQf9EfOVARXPun7R6/vE7TIPZz02loT9 /udrMxej84xSkvecm/lsanMn8CxH2u/0jG4HozRx0gW2UWGhlfZdw8h5jIY1A8lfQl/JkOWf lAIlsWcsKaSMsekkb89+SXliNkHk+fduTZ+qE6Mk6cRU3w5hzRBY6sEvvCK3ObcBei3Mez2C YP0GUPWefrkdeAX5Y1FLGKKo8NYl7rAZ70ia64kwBc6do1Wra83ldWCKEfgVCmy400VultqV H3tKnbuCZTGWFtdARCzflAE0tJcI8bLCMR11vKTPAWxaZNQID/NrF5f121D2K4oO1e8oyo/O jUxsJ4coKLyDbqlnQ9/ByiWBXwgAgaxmhIRl5LO3nJQR0eGBRDD3BgLWymennYQc1vHtR+pT X8GN/buphdttrT/US2bMWcAv1TOPPmrBBfnBEo9fK1dY8uR4ictd01IaHmYtlJVWvDyIhUWD 8/BMt4LKulbW1sgNz6u6WE3UqTn89mh3MLsEfibGaGcGK6CBtVhzwhWFXjw3XtQ8cnAKmJbr 8jdvNq3mSL0ztzSVUKeKXv0WzlR7uLGw2WIcwQU5erMD8nvWgsdM0a7ckdbDMEUEv0+LUxqp SiFwZRxq8TiixCdbiCxwSm5ItCxvHUGiJ/UwhnDqCa9Q5smJGl4VbWX125Hi8ftyHR+BhS9z vaIrsKUjrs1IUGVyIEd1bm5hcnNzb24gKEkgaG9wZSBJIHF1aXQgc21va2luZykgPHBlci5n dW5uYXJzc29uQGxhcHBzdG9ja2hvbG0uc2U+wn4EExEIACYCGwMHCwkIBwMCAQYVCAIJCgsE FgIDAQIeAQIXgAUCU5sBwQIZAQAKCRBsLkqi18cUloCZAQCAKx3L7ZJFNVYHVXuXCUMgLl1y bJy1nEhwAOFD9QE/0QD+PnSmMNsZIQqQLEYfWdFeBsG+z5IrJQKvZrWreRKhXoHOwU0EURqu cxAIAOtRZJMKzyEunqZvUdy35hsz4YkYtEMlBss8+oBsLIfkmhs9unI7U7PG8zNXboBQoN2a rP4G3ZQZzRUtgpTcdIANaQnh/NGbFTnzyqgPoGafkLxoXRJxM4D4mGpGeUO5ZymcRd5eBQ9I fNXZR10/08oPTc+1bQETjs9YNNWMvSjtPBm7d/CeunT6gtUiabSSRwIuUPSKHt+mpmDHbW1m 9LLc2QQkRhQaX0uDzlhRbrvwI5eS8kDtmHVU1ajWRDiL+SGGswVhJSUI8sA16DNiZwl2lINE lyK4hTP9qh861L76Ccwv5aS5kF8pcEa3QRgG2KmXKBGK/8uL55cJ3ppx098AAwUH/2JlweMj bBcdVP+yaRdMzcQ093iB5iZO7JLxrlpSRCoNhfkpmEUjxCIrnzM6Xz1Y67iIeLiOU8+Kynil gxVE5YGuYm8cIaIwQXWUYwLHTfEOQxYVfZeXUj46x2ybIKtXL51TqKhP4hwVXe9OXjKtC7In Vd5sXrfmmVPeKhoE2gRqWPUKdRyUjinJuyoGLyoyuyNbBACIer2LyJOow73nJIae1BjQY0JT S3zCppyJ6MyLtE79huM6GWPORmKtIv2xotcicdCtunXHPnzcaPNlBQAUXxwJsvteBAl44pMO jvSkeb0yNFcVqUMHHwMetTXq9avxsHAVt1TPkSB5VyuATEHCYQQYEQgACQUCURqucwIbDAAK CRBsLkqi18cUljEUAP0ZZel5fZ5DfgEVaLdtkDmbsK5fokMR63uFTD6ZKr1mRAD/YIHV4z19 nwv6UkxfsZ9B8E848aa+WoHR1APVwxaK2xM= Subject: pkg problem on FreeBSD 13.0-CURRENT Message-ID: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> Date: Thu, 25 Oct 2018 14:49:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Thu, 25 Oct 2018 12:49:54 -0000 FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC=C2=A0 am= d64 pkg-static install -f pkg pkg-static: Warning: Major OS version upgrade detected.=C2=A0 Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not Found repository FreeBSD has no meta file, using default settings pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/packagesite.txz: Not Found= Unable to update repository FreeBSD Error updating repositories! Regards, Per Gunnarsson From owner-freebsd-current@freebsd.org Thu Oct 25 12:57:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A3081075015 for ; Thu, 25 Oct 2018 12:57:32 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 E6EC780B37 for ; Thu, 25 Oct 2018 12:57:31 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gFfCe-000FbD-9M; Thu, 25 Oct 2018 14:57:32 +0200 Date: Thu, 25 Oct 2018 14:57:32 +0200 From: Kurt Jaeger To: Per Gunnarsson Cc: freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Message-ID: <20181025125732.GG28382@home.opsec.eu> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> 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, 25 Oct 2018 12:57:32 -0000 Hi! > FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC amd64 > > pkg-static install -f pkg > pkg-static: Warning: Major OS version upgrade detected. Running > "pkg-static install -f pkg" recommended > Updating FreeBSD repository catalogue... > pkg-static: Repository FreeBSD load error: access repo > file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory > pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not > Found The package builders are not yet providing packages for 13.0-CURRENT. It's being worked on, but will take a little more time. -- pi@FreeBSD.org +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Thu Oct 25 14:10:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C6731077CFB for ; Thu, 25 Oct 2018 14:10:43 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) (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 183E3845CA; Thu, 25 Oct 2018 14:10:42 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from disco.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 4CDF556484; Thu, 25 Oct 2018 09:10:40 -0500 (CDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: "Rodney W. Grimes" Cc: Rebecca Cran , freebsd-current@freebsd.org, imp@freebsd.org References: <201810251157.w9PBvsWg034406@pdx.rh.CN85.dnsmgr.net> From: Eric van Gyzen Message-ID: <7d4646ec-797c-7c0e-abfa-4c3bf3dfd0d5@vangyzen.net> Date: Thu, 25 Oct 2018 09:10:38 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <201810251157.w9PBvsWg034406@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 25 Oct 2018 14:10:43 -0000 On 10/25/18 6:57 AM, Rodney W. Grimes wrote: >>> I noticed a warning on a new AMD system running 12-BETA1: >>> >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12. >> Can you please reply with the specific device. >> If you have seen one it may be an issue to removing it, >> especially if this is on a "new AMD" system. > > Further investigation shows me that this comes from > generic code in sys/isa/isa_common.c, and does not > come from any specific driver markings. My new Ryzen says: atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. Believe it or not, my motherboard has a PS/2 connector, so I could actually use this driver someday. Eric From owner-freebsd-current@freebsd.org Thu Oct 25 14:29:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F7D310787B8 for ; Thu, 25 Oct 2018 14:29:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD1E485696 for ; Thu, 25 Oct 2018 14:29:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x932.google.com with SMTP id w12so3307655uam.9 for ; Thu, 25 Oct 2018 07:29:35 -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=HGYf1lWaPU3rcAekl7Tz3cVRYWUTzO94H3Wm59u1Yh8=; b=j2oYkYNA0gEfYlObpn45CTCrD/jSYLKM95YRDktj5zjOtHSXE2Vmmx1c/gcwwS39Ms ECCcf8SmEQj9v23DjA1kIOsof7jFl8D32iHAru7tBAALdDG5swdEs+0J5EGSPmvU8PEz nhDAXA4DNEeP/iXbndl1a52SMgI5ceCMob98q+qv6ZbTeTUJDIPCE/4bOON35O3+wn3g XgVcc/dlLy8Yenn5DE52e/df2D85d3rogJJzNXArG3c3wRl9kgV9kT6/su5CXQtuD+Pu oPEcxzK4tzn55hGQCmWuFdjFZnrzkojVRfZdjrdSmFvHlxAm+bDgYCGIkaRJxJKg8xWQ 0cew== 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=HGYf1lWaPU3rcAekl7Tz3cVRYWUTzO94H3Wm59u1Yh8=; b=Rs9jLcZ6ZeAf7GjJG5WXO8FdT7HSxn/GGExKC53Za8DtkcMzT6Kd7bc/QFKCbDsHfU vOuLBozzg3VrCIs8al9WPXQpFHCYTAVWq7qQrxvcnEz7+scN1Gn+8zOQE6T1oBoYrW2u AKIqEUUhber2GEFViNHyKni9Oyl+7VDhpEfTA9NbFlDi8h5DSe7WpoKnaU0t+JRpI9IN ZOQfOVrO4YCOqVrbRLWcS5OHAhQJk24yI7KL2VdxZPrrQ2D3jumzJyFvIn0gSWiGbnEB 8dtLDgfMgxroB2WBORWbtdzFeD8VgKJ1LqojMCQR2u4h2UNjiGApxOshvPSwmTvsP+0A fWSg== X-Gm-Message-State: AGRZ1gIbvN+lhy1sjdcqMV+RK1qo1wL/BGDOaHsHPjg8iTyWSe+gKc0C wUdFFCkwP0TK4nThi7QCEO9OCJWrEnx4+mIEzTNZ9w== X-Google-Smtp-Source: AJdET5cnRbJeJi3CgiE6J96EkV5s6yp2LQqS4u+MLKZy3GHZMhzOIAp0XKdOL9sUAdpj55Ow4vc/IMgHC5v6uujk57g= X-Received: by 2002:ab0:2086:: with SMTP id r6mr820112uak.39.1540477774710; Thu, 25 Oct 2018 07:29:34 -0700 (PDT) MIME-Version: 1.0 References: <201810251157.w9PBvsWg034406@pdx.rh.CN85.dnsmgr.net> <7d4646ec-797c-7c0e-abfa-4c3bf3dfd0d5@vangyzen.net> In-Reply-To: <7d4646ec-797c-7c0e-abfa-4c3bf3dfd0d5@vangyzen.net> From: Warner Losh Date: Thu, 25 Oct 2018 08:29:22 -0600 Message-ID: Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: Eric van Gyzen Cc: "Rodney W. Grimes" , rebecca@bluestop.org, FreeBSD Current , Warner Losh 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, 25 Oct 2018 14:29:36 -0000 On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen wrote: > On 10/25/18 6:57 AM, Rodney W. Grimes wrote: > >>> I noticed a warning on a new AMD system running 12-BETA1: > >>> > >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > >> Can you please reply with the specific device. > >> If you have seen one it may be an issue to removing it, > >> especially if this is on a "new AMD" system. > > > > Further investigation shows me that this comes from > > generic code in sys/isa/isa_common.c, and does not > > come from any specific driver markings. > > My new Ryzen says: > > atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > > Believe it or not, my motherboard has a PS/2 connector, so I could > actually use this driver someday. > I'll look into this. Rest assured, we won't be removing this. In theory, all such devices should be attaching via ACPI. Can you send me the output of 'devinfo -v' off list? Warner From owner-freebsd-current@freebsd.org Thu Oct 25 14:32:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E40E11078A5E for ; Thu, 25 Oct 2018 14:32:36 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 664A385A9C; Thu, 25 Oct 2018 14:32:36 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w9PEWRv7035302; Thu, 25 Oct 2018 07:32:27 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w9PEWRi5035301; Thu, 25 Oct 2018 07:32:27 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201810251432.w9PEWRi5035301@pdx.rh.CN85.dnsmgr.net> Subject: Re: 12-BETA1 contains warning about non-PNP ISA device In-Reply-To: To: Warner Losh Date: Thu, 25 Oct 2018 07:32:27 -0700 (PDT) CC: Eric van Gyzen , rebecca@bluestop.org, FreeBSD Current , Warner Losh X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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, 25 Oct 2018 14:32:37 -0000 > On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen wrote: > > > On 10/25/18 6:57 AM, Rodney W. Grimes wrote: > > >>> I noticed a warning on a new AMD system running 12-BETA1: > > >>> > > >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > > >> Can you please reply with the specific device. > > >> If you have seen one it may be an issue to removing it, > > >> especially if this is on a "new AMD" system. > > > > > > Further investigation shows me that this comes from > > > generic code in sys/isa/isa_common.c, and does not > > > come from any specific driver markings. > > > > My new Ryzen says: > > > > atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > > > > Believe it or not, my motherboard has a PS/2 connector, so I could > > actually use this driver someday. > > > > I'll look into this. Rest assured, we won't be removing this. In theory, > all such devices should be attaching via ACPI. > > Can you send me the output of 'devinfo -v' off list? I suspect something funny happens when there is already a USB keyboard plugged in that has been enumerated by ACPI, I would be willing to speculate that it leaves the legacy port visible as a legacy non PnP/Non ACPI device. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu Oct 25 15:19:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92DC2107ABFC for ; Thu, 25 Oct 2018 15:19:48 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 2CE5F88E42; Thu, 25 Oct 2018 15:19:48 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (unknown [75.161.243.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 3DACC1AFBDA; Thu, 25 Oct 2018 07:31:38 +0000 (UTC) Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: Kurt Jaeger , Per Gunnarsson Cc: freebsd-current References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> Date: Thu, 25 Oct 2018 09:19:42 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20181025125732.GG28382@home.opsec.eu> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MR1x8sjIpVFp0uTwQqpyK0JssGpk0ukQI" 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, 25 Oct 2018 15:19:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MR1x8sjIpVFp0uTwQqpyK0JssGpk0ukQI Content-Type: multipart/mixed; boundary="iNJVGTOSrsvaXTpZe7uRZUhlWbsMMiFOt"; protected-headers="v1" From: Sean Bruno To: Kurt Jaeger , Per Gunnarsson Cc: freebsd-current Message-ID: <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> Subject: Re: pkg problem on FreeBSD 13.0-CURRENT References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> In-Reply-To: <20181025125732.GG28382@home.opsec.eu> --iNJVGTOSrsvaXTpZe7uRZUhlWbsMMiFOt Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/25/18 6:57 AM, Kurt Jaeger wrote: > Hi! >=20 >> FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC=C2=A0= amd64 >> >> pkg-static install -f pkg >> pkg-static: Warning: Major OS version upgrade detected.=C2=A0 Running >> "pkg-static install -f pkg" recommended >> Updating FreeBSD repository catalogue... >> pkg-static: Repository FreeBSD load error: access repo >> file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or director= y >> pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: N= ot >> Found >=20 > The package builders are not yet providing packages for 13.0-CURRENT. >=20 > It's being worked on, but will take a little more time. >=20 Portmgr has pushed out packages for 13, give 'em a spin and see what happens. sean --iNJVGTOSrsvaXTpZe7uRZUhlWbsMMiFOt-- --MR1x8sjIpVFp0uTwQqpyK0JssGpk0ukQI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlvR3w9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LZjSQf+OgOn2uuLSOHvGQbKL2byRCEMAianJvpA4rb7BqrLzE36dl1Z0xe0gNMs oI5mokm9JIfyE2ie1Ohi0XZJ7CfPD6WFW01y5QLyQmvyGTwn66LDchn+6o/25YKP bNIDPR5pdUciUH8WVOxFgsy0HOTdek9VVLko8jHxQOrY9lX9W7AZRcheGjExVSRF geI9MLcvK89am/o24rZP5RbeBLdCKi032gsMr0cKqICQzBbIrckk3jn8isa27/zB xQW05ohCqUAtpzqmReMj/zcLyHkdSzjlQK9pTmhkUnu/9Eq+cZtRYCzRTiuR9ZcG DfGLyYXkdQTABX1E+T3NxoRuelkMqw== =ZUBK -----END PGP SIGNATURE----- --MR1x8sjIpVFp0uTwQqpyK0JssGpk0ukQI-- From owner-freebsd-current@freebsd.org Thu Oct 25 15:35:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A8EE107B6AA for ; Thu, 25 Oct 2018 15:35:08 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 C785089A18; Thu, 25 Oct 2018 15:35:07 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id D3BF2E4DED; Thu, 25 Oct 2018 09:35:44 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yh8th6Pz-qPR; Thu, 25 Oct 2018 09:35:44 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 09:35:44 -0600 (MDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: "Rodney W. Grimes" Cc: freebsd-current@freebsd.org, imp@freebsd.org References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> From: Rebecca Cran Message-ID: <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> Date: Thu, 25 Oct 2018 09:35:05 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed 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: Thu, 25 Oct 2018 15:35:08 -0000 On 10/25/18 5:02 AM, Rodney W. Grimes wrote: > Can you please reply with the specific device. > If you have seen one it may be an issue to removing it, > especially if this is on a "new AMD" system. This is a new Ryzen system. For me, I get warnings about atkbdc0 and uart0: 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. uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0 uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > Yes, and they well be removed from GENERIC in BETA2, > as I just approved the RFA to merge that fix to stable/12. Thanks, good to know they haven't been forgotten about. -- Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 15:53:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 987A2107C937 for ; Thu, 25 Oct 2018 15:53:38 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 35F318B0EA for ; Thu, 25 Oct 2018 15:53:38 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id EF35010B670; Thu, 25 Oct 2018 11:53:36 -0400 (EDT) Subject: Re: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 To: Marcin Cieslak References: <65f4cac9-99be-265f-e461-b166d52d226b@FreeBSD.org> Cc: FreeBSD Current From: John Baldwin Message-ID: Date: Thu, 25 Oct 2018 08:53:35 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 25 Oct 2018 11:53:37 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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, 25 Oct 2018 15:53:38 -0000 On 10/25/18 2:14 AM, Marcin Cieslak wrote: > On Wed, 24 Oct 2018, John Baldwin wrote: > >> On 10/23/18 10:58 AM, Marcin Cieslak wrote: >>> This GDB was configured as "amd64-marcel-freebsd"...BFD: /boot/kernel/kernel: invalid relocation type 37 >>> BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276 >>> >>> The kernel has been built on 11.1 with LD=/usr/bin/ld.lld >>> >>> Is this something that matters at all? >> >> It is not something that is likely to be fixed. If you pkg install gdb from >> ports, is the kgdb it includes able to examine the crash dump? > > Not really (using 8.2 from ports): > > # /usr/local/bin/kgdb82 -n 5 /usr/obj/usr/src/sys/GENERIC/kernel.debug > GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD] > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-portbld-freebsd11.1". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > . > Find the GDB manual and other documentation resources online at: > . > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/obj/usr/src/sys/GENERIC/kernel.debug...done. > thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion `tp' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) This usually means the kernel image you are using doesn't match the vmcore, so it's reading garbage data from the vmcore since the symbol offsets are wrong. You can test this by doing what crashinfo does: compare the version string in the /var/crash/info.5 file with 'p version' in kgdb (or gdb) of the kernel without a vmcore. -- John Baldwin From owner-freebsd-current@freebsd.org Thu Oct 25 16:00:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F15B107CE47 for ; Thu, 25 Oct 2018 16:00:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD8C58B5E0 for ; Thu, 25 Oct 2018 16:00:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe2f.google.com with SMTP id q15so5856986vso.1 for ; Thu, 25 Oct 2018 09:00:33 -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=n2RcM6sy8Ndmussmq1GebOVpxBnR6audOLbockrSQVg=; b=g5bv/mwxo1jLfdjYgWifTEgrRZig18uMG+WScTr2wcbBYkMpWv6ieJji2ICtpLbv6G g9PsgOQD/xKn26bztjYbDYuHmG6GUOmceCgdzdnjlDD4lUdewGYAG0OFT1+izoZjFbVT k6Kky0DSw9Z+CagQruKe7dDCuLw8GcdU1TsLKESIJdSPQJxpJ3Y6eiVC96PRU5IIUGy0 /pLBiSDBrfuQYdGf46vqjEHTDQoPvOIy4gN+X/5haPA7oAW3FfC55J7wC4/N/IMzkf7e CFxqCDpOiRkkmvHtJW2nUjCRRmq8s91StY9cm5Zq6O1lWDH0OeGrnzJoBkE6SplSqBM8 Y2Cg== 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=n2RcM6sy8Ndmussmq1GebOVpxBnR6audOLbockrSQVg=; b=SO7dynH2vtW5nSS7bdsZdQlOL3Qr9liY9kAqcqWfGK0ZkAnPIoTX+SF52yCKJSzLKX t0adZqaVZr1kTwdyDYcHhiKjYWZmJenjh8/Ecrr+qWXmxd1Ka59kJ3/B3GJMOAh1SplM p/GHqjBUNn/nXOrPAvwq6oGMicPPIL5bshlxViaSLs0axWREloAXyZBZ8W6WMvZt0no3 96MU7wLBX5jJvdL+xSvfS6U6DimBvr0Gpp6nUpSQpeUw1Cl8DOS9erRhIyY28e0TiSNZ W2f18TX3045Ft94ksz/57oM+ybCqS4SbgArMDWr0fJJHb6uQDTx8Uenjm+Q4r0q4TaCU +Pag== X-Gm-Message-State: AGRZ1gLfFZ1s5Fy0s2GT7E4+w4b+pY6It34dfMQp85r4BGjTHZV3MY0E X2/8tLuN9FDdtQggz1gjSP7d+wikN7/IJpIHhaNzsg== X-Google-Smtp-Source: AJdET5cdE9sIbdlU34YYDg+kNuacqPkR0rF/uzeSKgPFrVCfE6Nac/+7lqF4qX+XF8CE1QVYPxaWq2Qcc0HU4FLGujM= X-Received: by 2002:a67:4988:: with SMTP id d8mr959918vsg.41.1540483232966; Thu, 25 Oct 2018 09:00:32 -0700 (PDT) MIME-Version: 1.0 References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> In-Reply-To: <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> From: Warner Losh Date: Thu, 25 Oct 2018 10:00:20 -0600 Message-ID: Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: rebecca@bluestop.org Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh 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, 25 Oct 2018 16:00:34 -0000 On Thu, Oct 25, 2018 at 9:35 AM Rebecca Cran wrote: > On 10/25/18 5:02 AM, Rodney W. Grimes wrote: > > > Can you please reply with the specific device. > > If you have seen one it may be an issue to removing it, > > especially if this is on a "new AMD" system. > > > This is a new Ryzen system. For me, I get warnings about atkbdc0 and uart0: > > > 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. > uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0 > uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. > I suspect you can just lose those hints in the hints file and be fine. The uart should attach via acpi. The keyboard won't, however, since it isn't enabled. Can you try removing these lines from your hints file and see if the problem persists? Note this is for debugging purposes only. hint.atkbdc.0.at="isa" hint.uart.0.at="isa" Warner From owner-freebsd-current@freebsd.org Thu Oct 25 16:06:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9875A107D4C1 for ; Thu, 25 Oct 2018 16:06:00 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic303-20.consmr.mail.ir2.yahoo.com (sonic303-20.consmr.mail.ir2.yahoo.com [77.238.178.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00B9D8BDF6 for ; Thu, 25 Oct 2018 16:05:59 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: jtJIZvwVM1kB6cSD4tSl5ky8spMVLipBEHMHT5MxZpvcCdVwCM3WH4XDYTV2OcN eaczOlgvB8wnk8A.pyJEiFr9iEdpZM2quo2Ax8h_B6s4OT.qrq87xAuqWszmXE49R1TEeExysvrq 2_oc0D6oqZgDBlCYBn4dUoXoSqlr9lVf5L6egNgy5MLegXv5uVjYRLu99rng0gk8r1Vbqw9_FBw3 KDXlRfdRonSf7qbz0Xq4yWv77TaM0YE2ykF2b8km3q34xE6oOBcSevmZmtOpQPCuPevp0DY5TEYP 84TKr4Ud8LCMLTj75QljqSMzOKKQMEMv2TCEpn7QpsSSdI2PZ.FYzhcJBaufQ6Y.g8ipurU9bbYA 1hc.w8uXUU38flqfHih7hCRMxQekSgJh3WP_U.R8AapsG5CTPsli.vUfwj2WSfj30mHlrEaypH17 3Pm3kMLKMtCHjOILCvjaLnfcl.YcMALUqQZe8TpnUqdzZQ494KwfcRO70JiZZTH4Pmz043R6vwOm XuvcE0mvLC3rclDciJQiO.AwN6JFJFYNFZ0WkU6IYsoxqoh_OTuq4iuJl_nlCABM3ag.ltvoBY_O GsA7ZBQSogxGPz1xHksqwuIxtto8TpOxNthv_uyp2LQ9jm38i3wx9gtyBOD02bUPNDjLtauN2L52 5kz5xde2YgRio_XFfGwIB1TAkJJpuURwXFhID6Jk98xQ5aY0M6VJsCIHhnlKO5tp6OidUDH2mej5 sHhAWz5h8NKV694.epfWYYAz6zoJ5oo.oZ1LP1Xu1.D30MWmedKkSH4q6NOBTBRbfmx7w0UHcbbV axUkrgrrYmGa4bHOPIzzPaM_bWQ0IC01BzxYytJqOgJhwqrsi0hsvfe._9E0MOr9kTzyZDJ_qWcb 0w.5m4dRwiO8etQDTUhHOa2ww6A45C4nrdtiX9aIHCa_dMCgNqpXFe.LnWcFIG5Mlx4d2oAES7KY T87RGutAjlIDmE2xBMmWSb47s65CnDHXVxod0XbGx7OxqW.eyWtK5Q2BPGc9u.ssS9yx1Z7lZae7 mU8Bx3IGHnMUeyNd.pP3qtEPdLvkgoDxja6VX0QBstSI- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ir2.yahoo.com with HTTP; Thu, 25 Oct 2018 16:05:52 +0000 Received: from 80.244.81.252 (EHLO [10.0.0.5]) ([80.244.81.252]) by smtp430.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 1cebb618b5a4e1a9a1525c1045c7111b; Thu, 25 Oct 2018 16:05:50 +0000 (UTC) Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: Sean Bruno , Kurt Jaeger Cc: freebsd-current References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> From: Per Gunnarsson Openpgp: preference=signencrypt Autocrypt: addr=p.gunnarsson@yahoo.com; keydata= xsJuBFEarnMRCADHJa1GgO8EKAbE/ueVE4e+x8rImF6O6NUoTngCzuEjhXDyV4bmb7qSZcsQ /kIUfAy1BF5H5imdMdez5q4Ia78qJ/8kQMt+jWnwTIcWl+vj5wnDHJxwsr+SXZvQa//Fwjc7 31sHFtplTG1NZAaZgMSp4zYkJqA2c1a4tZ9b9zW/zvbsqfs4s5gU+8TSqA+0Q9JIMpJ0jGpi +NKtsn7eOomR7surIzQj7sLIwEoOwDsslvZR3Jy3xEwtbkI8pixP48LvrFrWW3O7ExZiMYGx OxcEPfc0yrAzuySBVXoO0ksOY86cqNubOCqvhqJEYKmTnUb+9clIJeHnGXuGgwAfNbFXAQCA 8SDkW9Poskc6UDE/Hem91De6MFrEgijOCbKOHVWWWQf9EfOVARXPun7R6/vE7TIPZz02loT9 /udrMxej84xSkvecm/lsanMn8CxH2u/0jG4HozRx0gW2UWGhlfZdw8h5jIY1A8lfQl/JkOWf lAIlsWcsKaSMsekkb89+SXliNkHk+fduTZ+qE6Mk6cRU3w5hzRBY6sEvvCK3ObcBei3Mez2C YP0GUPWefrkdeAX5Y1FLGKKo8NYl7rAZ70ia64kwBc6do1Wra83ldWCKEfgVCmy400VultqV H3tKnbuCZTGWFtdARCzflAE0tJcI8bLCMR11vKTPAWxaZNQID/NrF5f121D2K4oO1e8oyo/O jUxsJ4coKLyDbqlnQ9/ByiWBXwgAgaxmhIRl5LO3nJQR0eGBRDD3BgLWymennYQc1vHtR+pT X8GN/buphdttrT/US2bMWcAv1TOPPmrBBfnBEo9fK1dY8uR4ictd01IaHmYtlJVWvDyIhUWD 8/BMt4LKulbW1sgNz6u6WE3UqTn89mh3MLsEfibGaGcGK6CBtVhzwhWFXjw3XtQ8cnAKmJbr 8jdvNq3mSL0ztzSVUKeKXv0WzlR7uLGw2WIcwQU5erMD8nvWgsdM0a7ckdbDMEUEv0+LUxqp SiFwZRxq8TiixCdbiCxwSm5ItCxvHUGiJ/UwhnDqCa9Q5smJGl4VbWX125Hi8ftyHR+BhS9z vaIrsKUjrs1IUGVyIEd1bm5hcnNzb24gKEkgaG9wZSBJIHF1aXQgc21va2luZykgPHBlci5n dW5uYXJzc29uQGxhcHBzdG9ja2hvbG0uc2U+wn4EExEIACYCGwMHCwkIBwMCAQYVCAIJCgsE FgIDAQIeAQIXgAUCU5sBwQIZAQAKCRBsLkqi18cUloCZAQCAKx3L7ZJFNVYHVXuXCUMgLl1y bJy1nEhwAOFD9QE/0QD+PnSmMNsZIQqQLEYfWdFeBsG+z5IrJQKvZrWreRKhXoHOwU0EURqu cxAIAOtRZJMKzyEunqZvUdy35hsz4YkYtEMlBss8+oBsLIfkmhs9unI7U7PG8zNXboBQoN2a rP4G3ZQZzRUtgpTcdIANaQnh/NGbFTnzyqgPoGafkLxoXRJxM4D4mGpGeUO5ZymcRd5eBQ9I fNXZR10/08oPTc+1bQETjs9YNNWMvSjtPBm7d/CeunT6gtUiabSSRwIuUPSKHt+mpmDHbW1m 9LLc2QQkRhQaX0uDzlhRbrvwI5eS8kDtmHVU1ajWRDiL+SGGswVhJSUI8sA16DNiZwl2lINE lyK4hTP9qh861L76Ccwv5aS5kF8pcEa3QRgG2KmXKBGK/8uL55cJ3ppx098AAwUH/2JlweMj bBcdVP+yaRdMzcQ093iB5iZO7JLxrlpSRCoNhfkpmEUjxCIrnzM6Xz1Y67iIeLiOU8+Kynil gxVE5YGuYm8cIaIwQXWUYwLHTfEOQxYVfZeXUj46x2ybIKtXL51TqKhP4hwVXe9OXjKtC7In Vd5sXrfmmVPeKhoE2gRqWPUKdRyUjinJuyoGLyoyuyNbBACIer2LyJOow73nJIae1BjQY0JT S3zCppyJ6MyLtE79huM6GWPORmKtIv2xotcicdCtunXHPnzcaPNlBQAUXxwJsvteBAl44pMO jvSkeb0yNFcVqUMHHwMetTXq9avxsHAVt1TPkSB5VyuATEHCYQQYEQgACQUCURqucwIbDAAK CRBsLkqi18cUljEUAP0ZZel5fZ5DfgEVaLdtkDmbsK5fokMR63uFTD6ZKr1mRAD/YIHV4z19 nwv6UkxfsZ9B8E848aa+WoHR1APVwxaK2xM= Message-ID: Date: Thu, 25 Oct 2018 18:05:31 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GopJnBzD7HUzHDBsC01ObbbG2RPeja7ae" 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, 25 Oct 2018 16:06:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GopJnBzD7HUzHDBsC01ObbbG2RPeja7ae Content-Type: multipart/mixed; boundary="iGeDDOY01iSS34mi2z6E6aGkSQrfB6Q1d"; protected-headers="v1" From: Per Gunnarsson To: Sean Bruno , Kurt Jaeger Cc: freebsd-current Message-ID: Subject: Re: pkg problem on FreeBSD 13.0-CURRENT References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> In-Reply-To: <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> --iGeDDOY01iSS34mi2z6E6aGkSQrfB6Q1d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US On 10/25/18 5:19 PM, Sean Bruno wrote: > pkg-static install -f pkg It works better now, but there are some complaints. root@konjak:/usr # pkg-static install -f pkg pkg-static: Warning: Major OS version upgrade detected.=C2=A0 Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory Fetching meta.txz: 100%=C2=A0=C2=A0=C2=A0 944 B=C2=A0=C2=A0 0.9kB/s=C2=A0= =C2=A0=C2=A0 00:01=C2=A0=C2=A0=C2=A0 pkg-static: error reading public key: error:00000000:lib(0):func(0):reason(0) pkg-static: No trusted certificate has been used to sign the repository repository FreeBSD has no meta file, using default settings Fetching packagesite.txz: 100%=C2=A0=C2=A0=C2=A0 6 MiB=C2=A0=C2=A0 2.2MB/= s=C2=A0=C2=A0=C2=A0 00:03=C2=A0=C2=A0=C2=A0 pkg-static: error reading public key: error:00000000:lib(0):func(0):reason(0) pkg-static: No trusted certificate has been used to sign the repository Unable to update repository FreeBSD Error updating repositories! --iGeDDOY01iSS34mi2z6E6aGkSQrfB6Q1d-- --GopJnBzD7HUzHDBsC01ObbbG2RPeja7ae Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQSmuhu2gfduiZfHpA9sLkqi18cUlgUCW9Hp3QAKCRBsLkqi18cU lna7AP9v8LZzcd02MUDNQl21jjupLYdZrVDmuNKfDbfItlWbOAD/eANgGS67QdDg RDRCqcuw+uzkDCNj2mWOtZTTLBMFlVk= =emAC -----END PGP SIGNATURE----- --GopJnBzD7HUzHDBsC01ObbbG2RPeja7ae-- From owner-freebsd-current@freebsd.org Thu Oct 25 16:15:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBDFA107DCAD for ; Thu, 25 Oct 2018 16:15:45 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 4C6DB8C4B4 for ; Thu, 25 Oct 2018 16:15:45 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gFiIT-000G3z-An; Thu, 25 Oct 2018 18:15:45 +0200 Date: Thu, 25 Oct 2018 18:15:45 +0200 From: Kurt Jaeger To: Per Gunnarsson Cc: freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Message-ID: <20181025161545.GH28382@home.opsec.eu> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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, 25 Oct 2018 16:15:45 -0000 Hi! > On 10/25/18 5:19 PM, Sean Bruno wrote: > > pkg-static install -f pkg > > It works better now, but there are some complaints. If it's only the certificate issue, try this: cd /usr/local/etc cp pkg.conf.sample pkg.conf vi pkg.conf ------------- PKG_ENV : { SSL_NO_VERIFY_PEER: 1 } ------------- -- pi@FreeBSD.org +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Thu Oct 25 16:16:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37C70107DD6F for ; Thu, 25 Oct 2018 16:16:51 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 CA7BC8C5A2; Thu, 25 Oct 2018 16:16:50 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 3D303E4F94; Thu, 25 Oct 2018 10:17:28 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 15w0V05-Hv6D; Thu, 25 Oct 2018 10:17:28 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 10:17:27 -0600 (MDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: Warner Losh Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> From: Rebecca Cran Message-ID: Date: Thu, 25 Oct 2018 10:16:49 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed 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: Thu, 25 Oct 2018 16:16:51 -0000 On 10/25/18 10:00 AM, Warner Losh wrote: > > I suspect you can just lose those hints in the hints file and be fine. The > uart should attach via acpi. The keyboard won't, however, since it isn't > enabled. Can you try removing these lines from your hints file and see if > the problem persists? Note this is for debugging purposes only. > > hint.atkbdc.0.at="isa" > hint.uart.0.at="isa" That seems to work. After also removing uart1 from the hints file, I get: uart0: <16x50 with 256 byte FIFO> iomem 0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0 uart1: <16x50 with 256 byte FIFO> iomem 0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0 uart2: <16x50 with 256 byte FIFO> iomem 0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0 uart3: <16x50 with 256 byte FIFO> iomem 0xfedcf000-0xfedcffff,0xfedcd000-0xfedcdfff irq 4 on acpi0 -- Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 16:18:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 865DD107DEC3 for ; Thu, 25 Oct 2018 16:18:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F9E08C744 for ; Thu, 25 Oct 2018 16:18:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x92a.google.com with SMTP id m18so3471025uaq.2 for ; Thu, 25 Oct 2018 09:18:43 -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=7fE0Dv+PTQxUnPWj0P03Zqi3uVSG9LwxLe6TN1EMWfU=; b=ISs1HSp9SdtGCHfGUyFZ6sIAF8SawVYewAOyTBmG7z2izZMe41OABOJdRTzVeYXI6T /FAr3aCeDiCpqbkdWFMe3+rZiZ0BH2Mpof+ttknXEYeiGmUM25W0GDASNCpOzi60/rae F9tBvMiNfEbAylrRp6dtXMIWto8FhMqz7z+BC5sRBZ8Y40NYbklt7P8Gc3P+iOJFpHyg X+YMlUaWDRxzkk4ZU6e71nKcWh4sz+W2iL/UMPk+qXBxSW7Adf3UdEnnkDO+qzkDqdCn vtcW4DJNn2JAHXcYtZ4DoX+guyP3HtEAde5Wy8GsVxpv1sfJp6B4xjomo0t8Cxbqj6Jy Wlfw== 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=7fE0Dv+PTQxUnPWj0P03Zqi3uVSG9LwxLe6TN1EMWfU=; b=Ss7lwYOTBUZ7powjzeUUufgOIdolH254evJTxD2ixxjXFr4KqSYCN/ye6iz7dRg2c+ 2QxHyB5Lwy+0TJcG4db2iyiwXoza4drscJ2kk3AeLr5stWo/Dl++aSfHosJdWELU9lC0 QOh1P0QHvYQ4Vsk4Z2QTWN1HrMmpGrHynRUfcf8wn4CPA5MKTtLt6wvVcu70PvcsSmXf U7VnR/uH8KG8JUR/OXKN5YYzgursTJBBwccTeVlwNYilzcwYcpozgYQ+1OZQkm+k9Wdq Y8M9zzkFcHNfF1GgqVOu1VwWcD7Kx5d+KbKjNqoBkdQsYnclmsYqa309Ut4l0qMC3+kA u2yw== X-Gm-Message-State: AGRZ1gIysg77VnPu+Hbqt7msps08T1IOgNcT9IPc/j+XBmxTfvUS+Tza /k8AfmenEaD6S7KAcyoTARQCpdD5hLBjPn9R/MhwJg== X-Google-Smtp-Source: AJdET5edJhmyOmA7dbF+oz23WLaaRDJxKf9TlDXECX/yukLdCAOnxWCanAPWIuG2UF7u2wtsGAMM0d3m/ASbbyUsiGk= X-Received: by 2002:ab0:14a4:: with SMTP id d33mr984722uae.41.1540484322209; Thu, 25 Oct 2018 09:18:42 -0700 (PDT) MIME-Version: 1.0 References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> In-Reply-To: From: Warner Losh Date: Thu, 25 Oct 2018 10:18:30 -0600 Message-ID: Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: rebecca@bluestop.org Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh 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, 25 Oct 2018 16:18:43 -0000 On Thu, Oct 25, 2018 at 10:16 AM Rebecca Cran wrote: > On 10/25/18 10:00 AM, Warner Losh wrote: > > > > > I suspect you can just lose those hints in the hints file and be fine. > The > > uart should attach via acpi. The keyboard won't, however, since it isn't > > enabled. Can you try removing these lines from your hints file and see if > > the problem persists? Note this is for debugging purposes only. > > > > hint.atkbdc.0.at="isa" > > hint.uart.0.at="isa" > > > That seems to work. After also removing uart1 from the hints file, I get: > > > uart0: <16x50 with 256 byte FIFO> iomem > 0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0 > uart1: <16x50 with 256 byte FIFO> iomem > 0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0 > uart2: <16x50 with 256 byte FIFO> iomem > 0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0 > uart3: <16x50 with 256 byte FIFO> iomem > 0xfedcf000-0xfedcffff,0xfedcd000-0xfedcdfff irq 4 on acpi0 > That seems incorrect. It looks like we're attaching too much. what does devinfo -v | grep uart tell you? Warner From owner-freebsd-current@freebsd.org Thu Oct 25 16:20:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CB0F107E0D8 for ; Thu, 25 Oct 2018 16:20:37 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 BECFC8C94F; Thu, 25 Oct 2018 16:20:36 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 00106E4FB6; Thu, 25 Oct 2018 10:21:13 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NYnsJdLhdejL; Thu, 25 Oct 2018 10:21:13 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 10:21:13 -0600 (MDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: Warner Losh Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> From: Rebecca Cran Message-ID: Date: Thu, 25 Oct 2018 10:20:34 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Thu, 25 Oct 2018 16:20:37 -0000 On 10/25/18 10:18 AM, Warner Losh wrote: > > That seems incorrect. It looks like we're attaching too much. what does > devinfo -v | grep uart tell you?     uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0     uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1     uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2     uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 -- Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 16:26:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB3D7107E83B for ; Thu, 25 Oct 2018 16:26:47 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 7691F8D17E; Thu, 25 Oct 2018 16:26:47 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id AD5B3E4FCE; Thu, 25 Oct 2018 10:27:24 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GOm0l7BM7rhP; Thu, 25 Oct 2018 10:27:24 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 10:27:24 -0600 (MDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device From: Rebecca Cran To: Warner Losh Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> Message-ID: Date: Thu, 25 Oct 2018 10:26:45 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Thu, 25 Oct 2018 16:26:48 -0000 On 10/25/18 10:20 AM, Rebecca Cran wrote: > >     uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 >     uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 >     uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 >     uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 Also, in case it's useful - the output of "devinfo -v | grep -i uart":     uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0     unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART (disabled)     uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1     unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART (disabled)     uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2     uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 -- Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 16:31:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AD6B107EDD9 for ; Thu, 25 Oct 2018 16:31:12 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga102.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57B6D8D58C; Thu, 25 Oct 2018 16:31:11 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2018 09:30:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,424,1534834800"; d="scan'208";a="84136572" Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga007.jf.intel.com with ESMTP; 25 Oct 2018 09:30:01 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.89]) by ORSMSX108.amr.corp.intel.com ([169.254.2.163]) with mapi id 14.03.0319.002; Thu, 25 Oct 2018 09:30:00 -0700 From: "Pieper, Jeffrey E" To: Kurt Jaeger , Per Gunnarsson CC: freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Thread-Topic: pkg problem on FreeBSD 13.0-CURRENT Thread-Index: AQHUbGGj58W/Xhty/EWeNbK1/nBuB6UwYSsAgAAnuACAAAzNgIAAAtyA//+OowA= Date: Thu, 25 Oct 2018 16:29:59 +0000 Message-ID: <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> In-Reply-To: <20181025161545.GH28382@home.opsec.eu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.10.3.181015 x-originating-ip: [10.241.224.76] Content-Type: text/plain; charset="utf-8" Content-ID: <4C6DBBB87B9EB54F861DBFB28A63AC05@intel.com> Content-Transfer-Encoding: base64 MIME-Version: 1.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, 25 Oct 2018 16:31:12 -0000 SSdtIHNlZWluZzoNCg0KSW5zdGFsbGluZyBwa2ctMS4xMC41XzUuLi4NCkV4dHJhY3RpbmcgcGtn LTEuMTAuNV81OiAxMDAlDQpsZC1lbGYuc28uMTogU2hhcmVkIG9iamVjdCAibGlic3NsLnNvLjki IG5vdCBmb3VuZCwgcmVxdWlyZWQgYnkgInBrZyINCg0KVGhhbmtzLA0KSmVmZg0KDQrvu79PbiAx MC8yNS8xOCwgOToxOCBBTSwgIm93bmVyLWZyZWVic2QtY3VycmVudEBmcmVlYnNkLm9yZyBvbiBi ZWhhbGYgb2YgS3VydCBKYWVnZXIiIDxvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcg b24gYmVoYWxmIG9mIHBpQGZyZWVic2Qub3JnPiB3cm90ZToNCg0KICAgIEhpIQ0KICAgIA0KICAg ID4gT24gMTAvMjUvMTggNToxOSBQTSwgU2VhbiBCcnVubyB3cm90ZToNCiAgICA+ID4gcGtnLXN0 YXRpYyBpbnN0YWxsIC1mIHBrZw0KICAgID4gDQogICAgPiBJdCB3b3JrcyBiZXR0ZXIgbm93LCBi dXQgdGhlcmUgYXJlIHNvbWUgY29tcGxhaW50cy4NCiAgICANCiAgICBJZiBpdCdzIG9ubHkgdGhl IGNlcnRpZmljYXRlIGlzc3VlLCB0cnkgdGhpczoNCiAgICANCiAgICBjZCAvdXNyL2xvY2FsL2V0 Yw0KICAgIGNwIHBrZy5jb25mLnNhbXBsZSBwa2cuY29uZg0KICAgIHZpIHBrZy5jb25mDQogICAg LS0tLS0tLS0tLS0tLQ0KICAgIFBLR19FTlYgOiB7DQogICAgICAgICAgICBTU0xfTk9fVkVSSUZZ X1BFRVI6IDENCiAgICB9DQogICAgLS0tLS0tLS0tLS0tLQ0KICAgIA0KICAgIC0tIA0KICAgIHBp QEZyZWVCU0Qub3JnICAgICAgICAgKzQ5IDE3MSAzMTAxMzcyICAgICAgICAgICAgICAyIHllYXJz IHRvIGdvICENCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fXw0KICAgIGZyZWVic2QtY3VycmVudEBmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QNCiAgICBo dHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1jdXJyZW50 DQogICAgVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2QtY3VycmVudC11 bnN1YnNjcmliZUBmcmVlYnNkLm9yZyINCiAgICANCg0K From owner-freebsd-current@freebsd.org Thu Oct 25 16:41:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F7F0107F664 for ; Thu, 25 Oct 2018 16:41:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A1848DED3 for ; Thu, 25 Oct 2018 16:41:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe33.google.com with SMTP id 125so598285vsi.0 for ; Thu, 25 Oct 2018 09:41:44 -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=W0Dam7rUTXtSbw8sEjwDHwOvaO3WwoZWPRrwP13PqSM=; b=Fz8w9KKCGIpS3/9czRCGr1wMFA5YQjR1liDLm3Uu7gajuXSsLt4pm/OfIOtcLTehgh 0hViU6KMT999gxknGotbaKNo+m2UPIlEHLH1UXnfPyRhjwINdrkEMT1ykw3+4Tua5GFt 2XETaAa6AkMxFHoQedUBfuojyF3QCk2o3k8/R1ejmP8jqoBGgKG6UniJz0NooVfTqXZI rK68PrppS+P0NcGPs1w/ieZ6cGiF6KgjO+GuBAKUyTskNVGiLplwnnQdW6apDoHmvrRh /yJxqvn1XYKTOuRuosdZyWHH3LTNNzyRC9CeLtRaW7GepUEf/t6BBUqr5ViOHuUTgwQZ 9SnA== 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=W0Dam7rUTXtSbw8sEjwDHwOvaO3WwoZWPRrwP13PqSM=; b=t1tbhjhCarGVFQ0lSoi4ujRcHhUk5rPqHLba0HRXH+gle6UxTwKUv/twfkXNtLZ8mb bBe1+aOB1j0fBMvYWxqWeHOTkCeTwg+HEIWHNsGBj8vKqICxEqAua56cnnGPHkjQNcNM OQBDI2gBi5axXk88YmbIQm2XU90mLyoUEY96tDmhoL6UOkPR4hblyJsAdPiYR96uF18c 6CtkYM9wXdKyF/J9b79QliwXhggsxKmyZ/Hi8H+hb/GXA2kwA3fljqNBY7gsOHt2VGV5 7RfuiMrSSR9WxcIJDAdiMEMx6SKNLHl5JbZ+ockzQuvnHl44EUK/quqRgZgqEjBmjS+P eLQg== X-Gm-Message-State: AGRZ1gJJmom3JjrvxqEDjw/S3llmAzqy4FXNU6LFApTlyhkeqsttr3Hq DzhyeW4b28OHynjU/mDTsmmMn/GUIAwxV64yxTKLsM1i X-Google-Smtp-Source: AJdET5fxwu+oFbs2OlkCWOK1BVRT5wNqEM7kHpaRfL3NmnALZEUIkQYZQOWZtqJxyPfEJle4KVoz49h/wKL5HhU2KmM= X-Received: by 2002:a67:4988:: with SMTP id d8mr1033140vsg.41.1540485703458; Thu, 25 Oct 2018 09:41:43 -0700 (PDT) MIME-Version: 1.0 References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> In-Reply-To: <20181025161545.GH28382@home.opsec.eu> From: Warner Losh Date: Thu, 25 Oct 2018 10:19:22 -0600 Message-ID: Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: Kurt Jaeger Cc: p.gunnarsson@yahoo.com, FreeBSD Current 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, 25 Oct 2018 16:41:44 -0000 On Thu, Oct 25, 2018 at 10:17 AM Kurt Jaeger wrote: > Hi! > > > On 10/25/18 5:19 PM, Sean Bruno wrote: > > > pkg-static install -f pkg > > > > It works better now, but there are some complaints. > > If it's only the certificate issue, try this: > > cd /usr/local/etc > cp pkg.conf.sample pkg.conf > vi pkg.conf > ------------- > PKG_ENV : { > SSL_NO_VERIFY_PEER: 1 > } > ------------- > The issues I've hit needing pkg-static to power through are all shared-library issues. Warner From owner-freebsd-current@freebsd.org Thu Oct 25 16:46:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C2A2107F951 for ; Thu, 25 Oct 2018 16:46:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 34B668E21C for ; Thu, 25 Oct 2018 16:46:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe34.google.com with SMTP id e126so5945540vsc.9 for ; Thu, 25 Oct 2018 09:46:32 -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=B7pcYA9b2EolxzXaSyVU9VoE24C/71ENiCPZGdIfKds=; b=WbadmQMQ/OXEMuaqr9vUwL8zW/FLcM0MEWPQpFjpzDhs03cObsJQQ9Xp5fvk1ZV7lk Zxz1TR/23fUn0YC1yH6czoLRx7Aabvhs+L0D63BeVEClEb45Wf3enK3J/N8yK5G8r3qF ApHVrgBE5jv46qanDKhioNUIMhBsnwCHxIwaM+srS7HQb4HtpOXKmZJTDdYeOAfMs9q4 CVqXhmVlmRR4ZMczeAVWXDZy7MP4V8mKn+iKrP2EersKXHmp9afqvgS4N9XxKjE9ZbiQ JDpmG3cKS9F7PeXYjgweNWgbvVQlEqkVYhKaGGr5HnMN1UMIi+2DeabKnWz2dVCqofYt FSww== 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=B7pcYA9b2EolxzXaSyVU9VoE24C/71ENiCPZGdIfKds=; b=pUjOFMIm5wlUvcTP97siy0hCkTYt2YbSiecpqBPziHR7QuK4qPrEvoLbHn91AnMT4F RyNDYdyCqssiIgChtBVJQktxlEHCQHWZbMqdXoxApI8iz93mt0y/jJyRgCkfdNhHiPoh BQdQYu5xDNorLRSmGudn0NjLSNF3KvCgMgS1aoXLodZ5bnm/sNdhpDa/u4/9zt6qGYYn OPfyx+EcBPmH325iK/ooWb1g/PCqd5aHj6lBFAHuwx/djahqKx8wnDtPcejVdg/lfJOI MZpdx4RiadBwcMUZLXFV6DGZEfXEZTx5Tp37qdJOCm3qpQ+vp5KizMB4mW7Zmv1Lg6Dm NBnA== X-Gm-Message-State: AGRZ1gJIby1oxm6dfIIxPaHXJkGnUEEepzsRNLMGV/tsqIRqncHs2Q/X z1v0RQJq/3pci+jVzhuI/0BPGRu6aeMDWWMHpMbpEmI2 X-Google-Smtp-Source: AJdET5d7YIWk+TZqqC2qd/8eTZkhM5cdXlWvFyrNcpOnhQVuOQPfi8ufsE99bo6yG/RwqlkINNNUBybMumqFhvtvk+A= X-Received: by 2002:a67:2704:: with SMTP id n4mr1064448vsn.209.1540485991552; Thu, 25 Oct 2018 09:46:31 -0700 (PDT) MIME-Version: 1.0 References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> In-Reply-To: From: Warner Losh Date: Thu, 25 Oct 2018 10:46:20 -0600 Message-ID: Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: rebecca@bluestop.org Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh 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, 25 Oct 2018 16:46:32 -0000 On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran wrote: > On 10/25/18 10:20 AM, Rebecca Cran wrote: > > > > > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 > > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 > > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 > > uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 > > > Also, in case it's useful - the output of "devinfo -v | grep -i uart": > > > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 > unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART > (disabled) > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 > unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART > (disabled) > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 > uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 > Oh! that looks mostly right, though IIRC the higher UIDs might be something else. Harmless enough for now, though. I also think you might be able to test if we can remove a special case kludge we have for the AMDI0020 device since it looks like it has STA_ that might be sane now. Are you up for that? Warner From owner-freebsd-current@freebsd.org Thu Oct 25 16:47:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 213F4107FABD for ; Thu, 25 Oct 2018 16:47:58 +0000 (UTC) (envelope-from bwidawsk@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA0E48E351; Thu, 25 Oct 2018 16:47:57 +0000 (UTC) (envelope-from bwidawsk@freebsd.org) Received: from smtp.freebsd.org (unknown [134.134.139.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bwidawsk) by smtp.freebsd.org (Postfix) with ESMTPSA id 3B88A15C79; Thu, 25 Oct 2018 16:47:57 +0000 (UTC) (envelope-from bwidawsk@freebsd.org) Date: Thu, 25 Oct 2018 09:47:55 -0700 From: Ben Widawsky To: "Pieper, Jeffrey E" Cc: Kurt Jaeger , Per Gunnarsson , freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Message-ID: <20181025164755.uypkous3cat3hmf6@smtp.freebsd.org> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> User-Agent: NeoMutt/20180716-415-c1edc0 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, 25 Oct 2018 16:47:58 -0000 You'll need to update base first, and ideally update all your packages before make delete-old and make delete-old-libs On 18-10-25 16:29:59, Pieper, Jeffrey E wrote: > I'm seeing: > > Installing pkg-1.10.5_5... > Extracting pkg-1.10.5_5: 100% > ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg" > > Thanks, > Jeff > > On 10/25/18, 9:18 AM, "owner-freebsd-current@freebsd.org on behalf of Kurt Jaeger" wrote: > > Hi! > > > On 10/25/18 5:19 PM, Sean Bruno wrote: > > > pkg-static install -f pkg > > > > It works better now, but there are some complaints. > > If it's only the certificate issue, try this: > > cd /usr/local/etc > cp pkg.conf.sample pkg.conf > vi pkg.conf > ------------- > PKG_ENV : { > SSL_NO_VERIFY_PEER: 1 > } > ------------- > > -- > pi@FreeBSD.org +49 171 3101372 2 years 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" > > > _______________________________________________ > 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 Oct 25 16:48:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BD67107FAF8 for ; Thu, 25 Oct 2018 16:48:04 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 8FA038E364; Thu, 25 Oct 2018 16:48:03 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id C40E2E503B; Thu, 25 Oct 2018 10:48:40 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9rTPDWrmgEdZ; Thu, 25 Oct 2018 10:48:40 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 10:48:40 -0600 (MDT) Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: Warner Losh Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> From: Rebecca Cran Message-ID: <5ae66b54-2692-5e44-8021-b1401f2bd6d9@bluestop.org> Date: Thu, 25 Oct 2018 10:48:01 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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, 25 Oct 2018 16:48:04 -0000 On 10/25/18 10:46 AM, Warner Losh wrote: > > Oh! that looks mostly right, though IIRC the higher UIDs might be > something else. Harmless enough for now, though. Thanks. > > I also think you might be able to test if we can remove a special case > kludge we have for the AMDI0020 device since it looks like it has STA_ > that might be sane now. Are you up for that? > Sure! -- Rebecca From owner-freebsd-current@freebsd.org Thu Oct 25 16:49:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D242107FBF8 for ; Thu, 25 Oct 2018 16:49:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 241098E457 for ; Thu, 25 Oct 2018 16:49:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vs1-xe34.google.com with SMTP id r83so5952884vsc.4 for ; Thu, 25 Oct 2018 09:49:00 -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=T1/wyGI04FossgIOhHC9dskwoIqa6mGWsQcW+wGF1CE=; b=o3tZzu3e4GD6ACl0iwJQ/iis2ufWXZPfHisf21OL7v0c/noEXiHlMaCJI2o+14FDJT W8xcTct54yi9sAot0XW1+a9DPsc6mRFVKbFlzJDQgTVMbB0TJFN35Mv3vPP2AhUSh5bZ DCpK5piIjfaJ6/l3kxEaCDyyhFWLWysnHFgdZN/Jft3OtBb2tM8c3Gf711397hSCMMok y0Do/iWbbqsKggQGFtM+WPPoahZbUtNw66rodDQJut8aftgiyBousGqe4gUlsV56oQ27 V0yUJO20aAF4dGJs4ScKtgAs+quxIX3fFPt8cwl7IJHeUt4kGQOuhcUtn1lEv5JBslEk 7xGw== 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=T1/wyGI04FossgIOhHC9dskwoIqa6mGWsQcW+wGF1CE=; b=mxOeVZfPPJCXYa35GmhtqQh+xxdSqRQ/kzZ0HnYraJISZvfrQvIn7JsnFCNTcivBPw yHXoLf/jwwD+/3N6Y8X4j8mS4XJ7wcd1tP9FoNzuHKmE8mS7CoLfOYLoOyk22EJ/RFMS Arb9QOMRR9j+4Mb6T6wY4wwTh6kSif6na1QzZ1XC6zsnsBWXl9f4ZXj5Knbwq8wrFKOd gHcuVBB2jkuf36HhtHSq824tOr3Dce1BKZde3YpJAXXgMQZdJTLGgL84Ak7I/QqWmcRW a5io7l2F6zOWgm9TZrOxylqSSvNDhCkYBQJE7/GYoO3etGD4A+YzsYgnTklPJlOKBPVm a7mw== X-Gm-Message-State: AGRZ1gKXrZExTIdoLzDGvpIg4QKJXlGLnIOhrhwq4fQMONpxNJ48xMC6 zhitGgtqEFtVG22tzVCb8jJ6QPQTz1JT8tSG88pUbd4q X-Google-Smtp-Source: AJdET5fknzryi818qkyu9Hg1bvKKkD6/GA0pzuequVTGV4co9sxyg2wsrNcKmB6lXKyBxo3G6ES91vEV8+L2fpqM5F0= X-Received: by 2002:a67:2704:: with SMTP id n4mr1068157vsn.209.1540486139566; Thu, 25 Oct 2018 09:48:59 -0700 (PDT) MIME-Version: 1.0 References: <201810251102.w9PB2pXv034094@pdx.rh.CN85.dnsmgr.net> <3ec80228-d9fc-a411-c8c5-9bc9cc6e0856@bluestop.org> In-Reply-To: From: Warner Losh Date: Thu, 25 Oct 2018 10:48:47 -0600 Message-ID: Subject: Re: 12-BETA1 contains warning about non-PNP ISA device To: rebecca@bluestop.org Cc: "Rodney W. Grimes" , FreeBSD Current , Warner Losh 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, 25 Oct 2018 16:49:00 -0000 On Thu, Oct 25, 2018 at 10:46 AM Warner Losh wrote: > > > On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran > wrote: > >> On 10/25/18 10:20 AM, Rebecca Cran wrote: >> >> > >> > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 >> > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 >> > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 >> > uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 >> >> >> Also, in case it's useful - the output of "devinfo -v | grep -i uart": >> >> >> uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0 >> unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART >> (disabled) >> uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1 >> unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART >> (disabled) >> uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2 >> uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3 >> > > Oh! that looks mostly right, though IIRC the higher UIDs might be > something else. Harmless enough for now, though. > > I also think you might be able to test if we can remove a special case > kludge we have for the AMDI0020 device since it looks like it has STA_ that > might be sane now. Are you up for that? > Oh, wait, no. Other aml dumps show it's still lame :( Warner From owner-freebsd-current@freebsd.org Thu Oct 25 16:51:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01A81107FED3 for ; Thu, 25 Oct 2018 16:51:58 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 8677D8E770; Thu, 25 Oct 2018 16:51:57 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (unknown [75.161.243.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 4467A1AFBDA; Thu, 25 Oct 2018 09:03:50 +0000 (UTC) Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: "Pieper, Jeffrey E" , Kurt Jaeger , Per Gunnarsson Cc: freebsd-current References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: <2a418d58-8c85-cbfd-a485-01f268d40ee4@freebsd.org> Date: Thu, 25 Oct 2018 10:51:52 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jPrOMhcPM0R3z4XRF8qNbmpwlcgMLJoKJ" 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, 25 Oct 2018 16:51:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jPrOMhcPM0R3z4XRF8qNbmpwlcgMLJoKJ Content-Type: multipart/mixed; boundary="Huk98orjOdYxSb5DlX2lOTa3Q81BGN49E"; protected-headers="v1" From: Sean Bruno To: "Pieper, Jeffrey E" , Kurt Jaeger , Per Gunnarsson Cc: freebsd-current Message-ID: <2a418d58-8c85-cbfd-a485-01f268d40ee4@freebsd.org> Subject: Re: pkg problem on FreeBSD 13.0-CURRENT References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> In-Reply-To: <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> --Huk98orjOdYxSb5DlX2lOTa3Q81BGN49E Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 10/25/18 10:29 AM, Pieper, Jeffrey E wrote: > I'm seeing: >=20 > Installing pkg-1.10.5_5... > Extracting pkg-1.10.5_5: 100% > ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg" >=20 > Thanks, > Jeff Is this before or after the move of libssl.so.9 -> libssl.so.111 ? https://svnweb.freebsd.org/changeset/base/339709 sean --Huk98orjOdYxSb5DlX2lOTa3Q81BGN49E-- --jPrOMhcPM0R3z4XRF8qNbmpwlcgMLJoKJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlvR9KhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LaYFggA1P+G6X1WDgXlWi4c0cqdty/8PCD3Mm86qanagV8POHfcNqAupCTmvR0N iHQ8Divts6De5w5BMzoF4jM+FhPt58HOCGPyBnx6TLtL9M57FCdmuY6ezhvEg3bv n4k6kv3fHmfslIt+4K2UPHoshwEjHaW3HcSlwI2tx9XG11SHSLxO6Ip6W1dN0tYL x+sXag5Xrom2VZWGBeQeqiQPr57EdbO0IdO9iQcnNgDqiUqcGviczhMRl6BPYL73 QXlUlPs/Gogn7jq9VCPZUeBtDAmNAI6/iqiMzK94TJe3oqffXMaagEQYM2L8UYdU 6DrO/F2N1GRNgZ/F2ufuBb8LBdBogQ== =K6kI -----END PGP SIGNATURE----- --jPrOMhcPM0R3z4XRF8qNbmpwlcgMLJoKJ-- From owner-freebsd-current@freebsd.org Thu Oct 25 16:52:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77FB110850E4 for ; Thu, 25 Oct 2018 16:52:24 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) Received: from sonic304-22.consmr.mail.ir2.yahoo.com (sonic304-22.consmr.mail.ir2.yahoo.com [77.238.179.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E4A2F8E967 for ; Thu, 25 Oct 2018 16:52:23 +0000 (UTC) (envelope-from p.gunnarsson@yahoo.com) X-YMail-OSG: A532nsAVM1meUOWjKz0xRD_ORYOWWMBUEzHO.ZmI9yMHKduDuB.ULjNZv0B5WuH Ltq1BbBlz6KQ9I4CdfsT8clYG7YbfAyMxmy3j1BQ571QgC04gohfny.SpBur241jzKGICO5kmG6j S9EjcboI07RRokPi6I3uefvx1hLv0JJoTut2ZPfBFRJEMrVM0pnpIUNfYADdHZx6wiQX75UCyrHq JAHFQ8savYL8wcB3Pf1iNXwXGc8MmlHWSC6r0AJZkUeybPaPnNwynFgEdBhjesjnF6xfG8Dc8fsm f1CqF9qmrDP2ANxpkIxwmB2_.XZdgKkftR08anhOmFJrF4cGopNc.0aWgYVVB9bMMuFrxtqf6BFd caRW2lmLKbjFYjoW6XK_RAojfjfspI0M3loVxY0X5cENzT9j98yQ1b7EBwP7LHeI7CqK2fPqAwTY a0qG2Cqu8qBkfa00s39mNn5U9ngQpcNqjVpg8nXD5x9EPLMW25Z0E_ewKaEzE35MA72Y.gbTnMsl ZgpLpQJ3Ade1EpH0QcJSf3W1D4V2PBII3B7R_WRRxDvZk1qvnQLYYCdGSsDBmjF2F3TGAbQej9_W sv6VuCoKX2KvsUx7CtMFkvWi1L9CAkmJXcCpowWqwI8pzm1.B5jaiUWBNzeIcQDq7fObAZIb.YSX kKGqywhuzB5mYtInaaRFtcdIZ1iv2aFPgQz_qCtetWF78UulpO7E2EfiF.CxVw.rcmv1HGnyYRz2 ooTtWYHubcXUVFPWUAbiHziYXKwBOC5AnYRyZC1oP89_X9a50WvA42eU_jJ2BHavpJ.hzTIvcfj2 qw2MqafVAl9eV1svZ8h1i6ogFrkyyyBNkVN9T6PmhMr266j0wzEiyYLW_oaagfrhfYA_cHDtjoLX 7QWKCQajHpxkhS4Bayyo9mGSlK612L17nOI3MD5WjjoWBlg8dCvRvG3IuEJGpkOE2x7EXrWxEZZL bM37UT41YgnUJSk6GQtt6dahQ84w1yAydQykFx29ekeBKXdNzSCfsrhxLPHwt0KinPbz3_yQWC91 Te2pXk0oXGnd4CTJKiwUoktahxtm18ntVvw0VRjbUNc3F1MEQOH5LZsN_u4U- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ir2.yahoo.com with HTTP; Thu, 25 Oct 2018 16:52:17 +0000 Received: from 80.244.81.252 (EHLO [10.0.0.5]) ([80.244.81.252]) by smtp410.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4d7e181a608d12db8f51eec2c4fe313e; Thu, 25 Oct 2018 16:52:14 +0000 (UTC) Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: "Pieper, Jeffrey E" , Kurt Jaeger Cc: freebsd-current References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> From: Per Gunnarsson Openpgp: preference=signencrypt Autocrypt: addr=p.gunnarsson@yahoo.com; keydata= xsJuBFEarnMRCADHJa1GgO8EKAbE/ueVE4e+x8rImF6O6NUoTngCzuEjhXDyV4bmb7qSZcsQ /kIUfAy1BF5H5imdMdez5q4Ia78qJ/8kQMt+jWnwTIcWl+vj5wnDHJxwsr+SXZvQa//Fwjc7 31sHFtplTG1NZAaZgMSp4zYkJqA2c1a4tZ9b9zW/zvbsqfs4s5gU+8TSqA+0Q9JIMpJ0jGpi +NKtsn7eOomR7surIzQj7sLIwEoOwDsslvZR3Jy3xEwtbkI8pixP48LvrFrWW3O7ExZiMYGx OxcEPfc0yrAzuySBVXoO0ksOY86cqNubOCqvhqJEYKmTnUb+9clIJeHnGXuGgwAfNbFXAQCA 8SDkW9Poskc6UDE/Hem91De6MFrEgijOCbKOHVWWWQf9EfOVARXPun7R6/vE7TIPZz02loT9 /udrMxej84xSkvecm/lsanMn8CxH2u/0jG4HozRx0gW2UWGhlfZdw8h5jIY1A8lfQl/JkOWf lAIlsWcsKaSMsekkb89+SXliNkHk+fduTZ+qE6Mk6cRU3w5hzRBY6sEvvCK3ObcBei3Mez2C YP0GUPWefrkdeAX5Y1FLGKKo8NYl7rAZ70ia64kwBc6do1Wra83ldWCKEfgVCmy400VultqV H3tKnbuCZTGWFtdARCzflAE0tJcI8bLCMR11vKTPAWxaZNQID/NrF5f121D2K4oO1e8oyo/O jUxsJ4coKLyDbqlnQ9/ByiWBXwgAgaxmhIRl5LO3nJQR0eGBRDD3BgLWymennYQc1vHtR+pT X8GN/buphdttrT/US2bMWcAv1TOPPmrBBfnBEo9fK1dY8uR4ictd01IaHmYtlJVWvDyIhUWD 8/BMt4LKulbW1sgNz6u6WE3UqTn89mh3MLsEfibGaGcGK6CBtVhzwhWFXjw3XtQ8cnAKmJbr 8jdvNq3mSL0ztzSVUKeKXv0WzlR7uLGw2WIcwQU5erMD8nvWgsdM0a7ckdbDMEUEv0+LUxqp SiFwZRxq8TiixCdbiCxwSm5ItCxvHUGiJ/UwhnDqCa9Q5smJGl4VbWX125Hi8ftyHR+BhS9z vaIrsKUjrs1IUGVyIEd1bm5hcnNzb24gKEkgaG9wZSBJIHF1aXQgc21va2luZykgPHBlci5n dW5uYXJzc29uQGxhcHBzdG9ja2hvbG0uc2U+wn4EExEIACYCGwMHCwkIBwMCAQYVCAIJCgsE FgIDAQIeAQIXgAUCU5sBwQIZAQAKCRBsLkqi18cUloCZAQCAKx3L7ZJFNVYHVXuXCUMgLl1y bJy1nEhwAOFD9QE/0QD+PnSmMNsZIQqQLEYfWdFeBsG+z5IrJQKvZrWreRKhXoHOwU0EURqu cxAIAOtRZJMKzyEunqZvUdy35hsz4YkYtEMlBss8+oBsLIfkmhs9unI7U7PG8zNXboBQoN2a rP4G3ZQZzRUtgpTcdIANaQnh/NGbFTnzyqgPoGafkLxoXRJxM4D4mGpGeUO5ZymcRd5eBQ9I fNXZR10/08oPTc+1bQETjs9YNNWMvSjtPBm7d/CeunT6gtUiabSSRwIuUPSKHt+mpmDHbW1m 9LLc2QQkRhQaX0uDzlhRbrvwI5eS8kDtmHVU1ajWRDiL+SGGswVhJSUI8sA16DNiZwl2lINE lyK4hTP9qh861L76Ccwv5aS5kF8pcEa3QRgG2KmXKBGK/8uL55cJ3ppx098AAwUH/2JlweMj bBcdVP+yaRdMzcQ093iB5iZO7JLxrlpSRCoNhfkpmEUjxCIrnzM6Xz1Y67iIeLiOU8+Kynil gxVE5YGuYm8cIaIwQXWUYwLHTfEOQxYVfZeXUj46x2ybIKtXL51TqKhP4hwVXe9OXjKtC7In Vd5sXrfmmVPeKhoE2gRqWPUKdRyUjinJuyoGLyoyuyNbBACIer2LyJOow73nJIae1BjQY0JT S3zCppyJ6MyLtE79huM6GWPORmKtIv2xotcicdCtunXHPnzcaPNlBQAUXxwJsvteBAl44pMO jvSkeb0yNFcVqUMHHwMetTXq9avxsHAVt1TPkSB5VyuATEHCYQQYEQgACQUCURqucwIbDAAK CRBsLkqi18cUljEUAP0ZZel5fZ5DfgEVaLdtkDmbsK5fokMR63uFTD6ZKr1mRAD/YIHV4z19 nwv6UkxfsZ9B8E848aa+WoHR1APVwxaK2xM= Message-ID: Date: Thu, 25 Oct 2018 18:52:13 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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: Thu, 25 Oct 2018 16:52:24 -0000 I rebuilt pkg from ports and it seems to work now. When I think about it there was a note in UPDATING that I maybe should have read. 20181009:         OpenSSL has been updated to version 1.1.1.  This update included         additional various API changes througout the base system.  It is         important to rebuild third-party software after upgrading.  The value         of __FreeBSD_version has been bumped accordingly. On 10/25/18 6:29 PM, Pieper, Jeffrey E wrote: > I'm seeing: > > Installing pkg-1.10.5_5... > Extracting pkg-1.10.5_5: 100% > ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg" > > Thanks, > Jeff > > On 10/25/18, 9:18 AM, "owner-freebsd-current@freebsd.org on behalf of Kurt Jaeger" wrote: > > Hi! > > > On 10/25/18 5:19 PM, Sean Bruno wrote: > > > pkg-static install -f pkg > > > > It works better now, but there are some complaints. > > If it's only the certificate issue, try this: > > cd /usr/local/etc > cp pkg.conf.sample pkg.conf > vi pkg.conf > ------------- > PKG_ENV : { > SSL_NO_VERIFY_PEER: 1 > } > ------------- > > -- > pi@FreeBSD.org +49 171 3101372 2 years 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 Oct 25 16:53:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E54310851C7 for ; Thu, 25 Oct 2018 16:53:16 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga102.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59A0C8EA91; Thu, 25 Oct 2018 16:53:14 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2018 09:53:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,425,1534834800"; d="scan'208";a="103268485" Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by orsmga002.jf.intel.com with ESMTP; 25 Oct 2018 09:53:07 -0700 Received: from orsmsx161.amr.corp.intel.com (10.22.240.84) by ORSMSX108.amr.corp.intel.com (10.22.240.6) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 25 Oct 2018 09:53:07 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.89]) by ORSMSX161.amr.corp.intel.com ([169.254.4.49]) with mapi id 14.03.0319.002; Thu, 25 Oct 2018 09:53:07 -0700 From: "Pieper, Jeffrey E" To: Ben Widawsky CC: Kurt Jaeger , Per Gunnarsson , freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Thread-Topic: pkg problem on FreeBSD 13.0-CURRENT Thread-Index: AQHUbGGj58W/Xhty/EWeNbK1/nBuB6UwYSsAgAAnuACAAAzNgIAAAtyA//+OowCAAHpagP//jBoA Date: Thu, 25 Oct 2018 16:53:06 +0000 Message-ID: <0ADB9EDD-6424-4BBB-8C0A-0162AC7803BC@intel.com> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> <20181025164755.uypkous3cat3hmf6@smtp.freebsd.org> In-Reply-To: <20181025164755.uypkous3cat3hmf6@smtp.freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.10.3.181015 x-originating-ip: [10.241.224.76] Content-Type: text/plain; charset="utf-8" Content-ID: <215B8437893D8C4D98FBC52642AFAA68@intel.com> Content-Transfer-Encoding: base64 MIME-Version: 1.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, 25 Oct 2018 16:53:16 -0000 VGhpcyBhIG5ldyBidWlsZCBmcm9tIGRpc3RmaWxlcyAoZ2VuZXJhdGVkIGZyb20gc3JjKSB3aXRo IG5vIHBhY2thZ2VzIGluc3RhbGxlZC4NCg0KVGhhbmtzLA0KSmVmZg0KDQrvu79PbiAxMC8yNS8x OCwgOTo0OCBBTSwgIkJlbiBXaWRhd3NreSIgPGJ3aWRhd3NrQGZyZWVic2Qub3JnPiB3cm90ZToN Cg0KICAgIFlvdSdsbCBuZWVkIHRvIHVwZGF0ZSBiYXNlIGZpcnN0LCBhbmQgaWRlYWxseSB1cGRh dGUgYWxsIHlvdXIgcGFja2FnZXMgYmVmb3JlDQogICAgbWFrZSBkZWxldGUtb2xkIGFuZCBtYWtl IGRlbGV0ZS1vbGQtbGlicw0KICAgIA0KICAgIE9uIDE4LTEwLTI1IDE2OjI5OjU5LCBQaWVwZXIs IEplZmZyZXkgRSB3cm90ZToNCiAgICA+IEknbSBzZWVpbmc6DQogICAgPiANCiAgICA+IEluc3Rh bGxpbmcgcGtnLTEuMTAuNV81Li4uDQogICAgPiBFeHRyYWN0aW5nIHBrZy0xLjEwLjVfNTogMTAw JQ0KICAgID4gbGQtZWxmLnNvLjE6IFNoYXJlZCBvYmplY3QgImxpYnNzbC5zby45IiBub3QgZm91 bmQsIHJlcXVpcmVkIGJ5ICJwa2ciDQogICAgPiANCiAgICA+IFRoYW5rcywNCiAgICA+IEplZmYN CiAgICA+IA0KICAgID4gT24gMTAvMjUvMTgsIDk6MTggQU0sICJvd25lci1mcmVlYnNkLWN1cnJl bnRAZnJlZWJzZC5vcmcgb24gYmVoYWxmIG9mIEt1cnQgSmFlZ2VyIiA8b3duZXItZnJlZWJzZC1j dXJyZW50QGZyZWVic2Qub3JnIG9uIGJlaGFsZiBvZiBwaUBmcmVlYnNkLm9yZz4gd3JvdGU6DQog ICAgPiANCiAgICA+ICAgICBIaSENCiAgICA+ICAgICANCiAgICA+ICAgICA+IE9uIDEwLzI1LzE4 IDU6MTkgUE0sIFNlYW4gQnJ1bm8gd3JvdGU6DQogICAgPiAgICAgPiA+IHBrZy1zdGF0aWMgaW5z dGFsbCAtZiBwa2cNCiAgICA+ICAgICA+IA0KICAgID4gICAgID4gSXQgd29ya3MgYmV0dGVyIG5v dywgYnV0IHRoZXJlIGFyZSBzb21lIGNvbXBsYWludHMuDQogICAgPiAgICAgDQogICAgPiAgICAg SWYgaXQncyBvbmx5IHRoZSBjZXJ0aWZpY2F0ZSBpc3N1ZSwgdHJ5IHRoaXM6DQogICAgPiAgICAg DQogICAgPiAgICAgY2QgL3Vzci9sb2NhbC9ldGMNCiAgICA+ICAgICBjcCBwa2cuY29uZi5zYW1w bGUgcGtnLmNvbmYNCiAgICA+ICAgICB2aSBwa2cuY29uZg0KICAgID4gICAgIC0tLS0tLS0tLS0t LS0NCiAgICA+ICAgICBQS0dfRU5WIDogew0KICAgID4gICAgICAgICAgICAgU1NMX05PX1ZFUklG WV9QRUVSOiAxDQogICAgPiAgICAgfQ0KICAgID4gICAgIC0tLS0tLS0tLS0tLS0NCiAgICA+ICAg ICANCiAgICA+ICAgICAtLSANCiAgICA+ICAgICBwaUBGcmVlQlNELm9yZyAgICAgICAgICs0OSAx NzEgMzEwMTM3MiAgICAgICAgICAgICAgMiB5ZWFycyB0byBnbyAhDQogICAgPiAgICAgX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICA+ICAgICBmcmVl YnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0DQogICAgPiAgICAgaHR0cHM6Ly9s aXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtY3VycmVudA0KICAgID4g ICAgIFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWN1cnJlbnQtdW5z dWJzY3JpYmVAZnJlZWJzZC5vcmciDQogICAgPiAgICAgDQogICAgPiANCiAgICA+IF9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgPiBmcmVlYnNkLWN1 cnJlbnRAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0DQogICAgPiBodHRwczovL2xpc3RzLmZyZWVi c2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1jdXJyZW50DQogICAgPiBUbyB1bnN1YnNj cmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJzZC1jdXJyZW50LXVuc3Vic2NyaWJlQGZyZWVi c2Qub3JnIg0KICAgIA0KDQo= From owner-freebsd-current@freebsd.org Thu Oct 25 16:55:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E39C1085464 for ; Thu, 25 Oct 2018 16:55:48 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga106.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1503A8ED28; Thu, 25 Oct 2018 16:55:47 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Oct 2018 09:55:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,425,1534834800"; d="scan'208";a="275599298" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by fmsmga006.fm.intel.com with ESMTP; 25 Oct 2018 09:55:46 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.89]) by ORSMSX106.amr.corp.intel.com ([169.254.1.85]) with mapi id 14.03.0319.002; Thu, 25 Oct 2018 09:55:46 -0700 From: "Pieper, Jeffrey E" To: Sean Bruno , Kurt Jaeger , "Per Gunnarsson" CC: freebsd-current Subject: Re: pkg problem on FreeBSD 13.0-CURRENT Thread-Topic: pkg problem on FreeBSD 13.0-CURRENT Thread-Index: AQHUbGGj58W/Xhty/EWeNbK1/nBuB6UwYSsAgAAnuACAAAzNgIAAAtyA//+OowCAAHt1AP//i72A Date: Thu, 25 Oct 2018 16:55:45 +0000 Message-ID: <5CE4041D-DC06-4356-90DF-4ADFE70B5AD9@intel.com> References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> <2a418d58-8c85-cbfd-a485-01f268d40ee4@freebsd.org> In-Reply-To: <2a418d58-8c85-cbfd-a485-01f268d40ee4@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.10.3.181015 x-originating-ip: [10.241.224.76] Content-Type: text/plain; charset="utf-8" Content-ID: <8DFA30AA4728094492767481C2DC0ECC@intel.com> Content-Transfer-Encoding: base64 MIME-Version: 1.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, 25 Oct 2018 16:55:48 -0000 VGhpcyB3YXMgYnVpbGQgdGhpcyBtb3JuaW5nIGFuZCBpbmNsdWRlczogDQoNCmNvbW1pdCBmMzcy NTZhMDFmZTEyZmU0ZDY1MTI4YzgyYzY4MDRkNDdkZDUxMWMxDQpBdXRob3I6IGtpYiA8a2liQEZy ZWVCU0Qub3JnPg0KRGF0ZTogICBUaHUgT2N0IDI1IDEzOjM3OjU3IDIwMTggKzAwMDANCg0KICAg IEJ1bXAgYmFzZSBPcGVuU1NMIGxpYnJhcmllcyB2ZXJzaW9ucyB0byBhdm9pZCBjb25mbGljdCB3 aXRoIHBvcnQncyBsaWJyYXJpZXMuDQogICAgDQogICAgUmVwb3J0ZWQgYnk6ICAgIG1hbnkNCiAg ICBSZXZpZXdlZCBieTogICAgZ2piDQogICAgU3BvbnNvcmVkIGJ5OiAgIFRoZSBGcmVlQlNEIEZv dW5kYXRpb24NCiAgICBNRkMgYWZ0ZXI6ICAgICAgMyBob3Vycw0KDQpKZWZmDQrvu78NCg0KT24g MTAvMjUvMTgsIDk6NTIgQU0sICJTZWFuIEJydW5vIiA8c2JydW5vQGZyZWVic2Qub3JnPiB3cm90 ZToNCg0KICAgIA0KICAgIA0KICAgIE9uIDEwLzI1LzE4IDEwOjI5IEFNLCBQaWVwZXIsIEplZmZy ZXkgRSB3cm90ZToNCiAgICA+IEknbSBzZWVpbmc6DQogICAgPiANCiAgICA+IEluc3RhbGxpbmcg cGtnLTEuMTAuNV81Li4uDQogICAgPiBFeHRyYWN0aW5nIHBrZy0xLjEwLjVfNTogMTAwJQ0KICAg ID4gbGQtZWxmLnNvLjE6IFNoYXJlZCBvYmplY3QgImxpYnNzbC5zby45IiBub3QgZm91bmQsIHJl cXVpcmVkIGJ5ICJwa2ciDQogICAgPiANCiAgICA+IFRoYW5rcywNCiAgICA+IEplZmYNCiAgICAN CiAgICBJcyB0aGlzIGJlZm9yZSBvciBhZnRlciB0aGUgbW92ZSBvZiBsaWJzc2wuc28uOSAtPiBs aWJzc2wuc28uMTExID8NCiAgICANCiAgICBodHRwczovL3N2bndlYi5mcmVlYnNkLm9yZy9jaGFu Z2VzZXQvYmFzZS8zMzk3MDkNCiAgICANCiAgICBzZWFuDQogICAgDQogICAgDQoNCg== From owner-freebsd-current@freebsd.org Thu Oct 25 17:25:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D5461086DCB; Thu, 25 Oct 2018 17:25:00 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87A9969EFB; Thu, 25 Oct 2018 17:24:59 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wr1-x432.google.com with SMTP id l6-v6so10175877wrt.1; Thu, 25 Oct 2018 10:24:59 -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=6Wrubset3IpjY2z6yCwGo8u43H9U/nYor2Ikd3Svu0Y=; b=N6AWct3bLNX4HjK7pHH2R0QByC0hSqdJfmVFq0Ota7C3Q0OqJL8UHLngizZFs/tbFT OfYL2/ka3gqTRiRX8HXrSN5RV7WzhlLq2VmLh9FijbCXRoh7RMkj7PcMHO/LSV5Z3cvn TssPvncuZaph8keM1OwvLTt71pjxVXwmiTzG93A+BngmYOf8YOrH0XAtz36K24zTpav0 ApJ5HG4TYVttIBKQg7YfLmTuVlRcf04I7+acvys3UP4RmDyGvKa4Tem167Lp1+InyylX Ba3D9bVfP4ANK98VRP/xoYuOhBzj8Swk4Ey5nmN8LvhhB6tmLW38WYieDj315SpCZvmE zmog== 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=6Wrubset3IpjY2z6yCwGo8u43H9U/nYor2Ikd3Svu0Y=; b=Qg0XSVcFctBLiSHCSS6DiGaiMtwsLxhjPMsopk9Cw7LJ3B6CB4XT8wUw8xKjPe5DAk nrwy7JeXXpk+UyE/Kl2fxiGxVMoqfNsPNNg0JVDkXtb6BS9ybXBvMLwWbhVAN4ci0/+w i8aBocj7552cJP8jG4PHSsxxBgIAgEc1Sum3nbyGQ3RZkSDdTtFXkBvZVmW48zxD5+lB /Z8dJVTrDCd6P82j5wP6KdIYa8nwDKEB9JyadHOWrb0Z+5CvPKDNtDyjOLkFrihkgltE e17wk+F9wV4bT/ONwEcUyinBbOtv28mTIgI4ibyzEwFYbu/z6DXRvNQbzdVP0oAEOKh7 sXmA== X-Gm-Message-State: AGRZ1gKBawOCvco+aYxYMMdLs+/iaRGDmTP7u7CU7bKQ3cQtVeV3+YvT I7SQXfn8H5B1mN5YS4DTgk+QJph6AA3YXrx6biD/Ow== X-Google-Smtp-Source: AJdET5c8Nmd7jiN0sb34IRNDQjXX672F5wdQsqzdcl++QvUPK/lDRr41R1Evzg9IB8/s4qUWLvgza1QxjoS4mewLd/o= X-Received: by 2002:adf:a144:: with SMTP id r4-v6mr2769259wrr.169.1540488298171; Thu, 25 Oct 2018 10:24:58 -0700 (PDT) MIME-Version: 1.0 References: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> In-Reply-To: <2a595c73-4a93-6e3f-f93d-9038baeeb18a@FreeBSD.org> From: Rajesh Kumar Date: Thu, 25 Oct 2018 22:54:45 +0530 Message-ID: Subject: Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path? To: jhb@freebsd.org Cc: freebsd-drivers@freebsd.org, freebsd-current@freebsd.org 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, 25 Oct 2018 17:25:00 -0000 Hi John, Thanks a lot. It helps. I backported the changes to 11.2 and tried booting in my board with success without any need for the said tunables. I see those changes are marked for MFC after 2 Weeks. But I don't see them still in stable/11 branch. So, will it be taken into stable/11 branch by any chance? If not, can the backported changes be submitted for review to take into stable/11 branch? On Thu, Oct 25, 2018 at 1:17 AM John Baldwin wrote: > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that, > I > > needed the following tunables to be set from loader prompt to get it > booted > > (otherwise machine reboots continuously). > > > > hw.usb.xhci.msi=0 > > hw.usb.xhci.msix=0 > > hw.pci.enable_msi=0 > > hw.pci.enable_msix=0 > > > > But, when I tried with 12.0 - ALPHA4, I could able to get it booted > without > > any tunables. So, has anything changed significantly on PCI MSI/MSI-X > > path? > > > > Note: I have a forum topic with my observations about the issue on > > 11.1/11.2 in the following thread > > > https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ > > > > Let me know if you need any details. > > I believe this was fixed by r338360. > > -- > John Baldwin > From owner-freebsd-current@freebsd.org Thu Oct 25 17:31:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C05EB108728B for ; Thu, 25 Oct 2018 17:31:00 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47EFD6A32A for ; Thu, 25 Oct 2018 17:31:00 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd35.google.com with SMTP id p83-v6so5978918iod.12 for ; Thu, 25 Oct 2018 10:31:00 -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=Q14Dt4tIzgMqLHCZbOc9ZD1cWSNljfUm65wu4KFMybI=; b=Yo195jC/BUlDJz20UUaVuuGJsn1BZLP6zgHh/WbKwvZMdB48835mrYbJXSogWyjw89 IYvV/t5CRwlMlS1+6OIm7TCvgmOZ2kS2vFbPxDZFU4uCbEcvq91IrlioYqYKXFcRfkqU efWpvrHkQw/J7Qr2GAv9I4TEGL7+1/LjfHAMpXFRpJkcdAIOZAd0CIYNTfLkSmjKCg2g zm9IKR34RYPeNu/0B/6b3AH3ZO4aMKawTgGzEdBYh6p7q+0kfLIfOps4XifBDvv15ZOk wtkPAkLOYRJxt8CxRBWomlcjUwLxXRQoeBdFQaolLknGD/4T/pB/bFXiEqKTUzQqx6rz Mc+g== 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=Q14Dt4tIzgMqLHCZbOc9ZD1cWSNljfUm65wu4KFMybI=; b=FBWw1BcPKbA2rPR+PI3ZTcZG5divUNd4OCLfUw8tO+3zZa/7cPK1vX/UNR0yiJmYle YAWQ88q2vFqbx1GMq4P7lMcaPtnqk3eMvZ9fibcOhW2q3/wIoWBXhmGN/V5wMpGiL8Pl ip18ab8lne+3cu3bFzjrs0rRTqP3KfhfAh56bcBPW+63zOOBSpE84SfsrtvAVV0b+S3t KMCIYKCQDfdCt/QnEr/M/YNSP55LWHAyHxUMPfjufYcDoqGuXUwXTXNzrhbtEpZV3ZMi ei+GLL71HY7s9dzNikiM2ZzTrov/zc1XpkOO2FIWChlSd/EweqC1GLMXjoDmlbqpFS2J 5N8Q== X-Gm-Message-State: AGRZ1gJGPQn8WbuDfgm8ISB66naeehJOwzVV5bA7FXdISekxgK6DlvVC LQjZNqlFSmuU76mMBplnNkw= X-Google-Smtp-Source: AJdET5e7VoJ9CFQoCJC0lWcE+eN95qw6YmUcNYFbfpq//sLjEmTMRnBXcySGe29EIQMxcxySDvU6Wg== X-Received: by 2002:a6b:8c50:: with SMTP id o77-v6mr91451iod.63.1540488659569; Thu, 25 Oct 2018 10:30:59 -0700 (PDT) Received: from raichu (toroon0560w-lp130-08-67-71-176-199.dsl.bell.ca. [67.71.176.199]) by smtp.gmail.com with ESMTPSA id s10-v6sm1222339itb.38.2018.10.25.10.30.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Oct 2018 10:30:58 -0700 (PDT) Sender: Mark Johnston Date: Thu, 25 Oct 2018 13:30:56 -0400 From: Mark Johnston To: Rajesh Kumar Cc: freebsd-current@freebsd.org Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 Message-ID: <20181025173056.GD73360@raichu> References: <20181023133504.GA28755@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-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: Thu, 25 Oct 2018 17:31:00 -0000 On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > Hi Mark, > > > From the db> prompt, could you please run "show page" and "show pageq", > > and post the output? > > The system gets hung when it runs to db prompt. I only have the option to > force shutdown at that point. Is there any other way, I can collect what > you need? Just a followup for the list: the issue should be fixed by the following two patches: https://reviews.freebsd.org/D17418 https://reviews.freebsd.org/D17704 From owner-freebsd-current@freebsd.org Thu Oct 25 13:13:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 302C71075922; Thu, 25 Oct 2018 13:13:44 +0000 (UTC) (envelope-from ronald@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CAE3781618; Thu, 25 Oct 2018 13:13:43 +0000 (UTC) (envelope-from ronald@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1gFfSB-0007BD-L9; Thu, 25 Oct 2018 15:13:35 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, "FreeBSD Current" , freebsd-fs@freebsd.org Date: Thu, 25 Oct 2018 15:13:36 +0200 Subject: tmpfs corrupt file (aarch64/12.0-ALPHA5) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 76f3589a93270604ea078d468a2051b3 X-Mailman-Approved-At: Thu, 25 Oct 2018 20:07:37 +0000 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, 25 Oct 2018 13:13:44 -0000 Hello, I'm running this small script which generates changelog file in gzipped JSON format. TMPDIR=/var/tmp START=1 END=$(( $START + $STEP - 1 )) while test $START -lt 300000 do svnlite log --xml -r $START:$END -v ~/src/freebsd-base > $TMPDIR/bla.xml bin/xml2json.py > $TMPDIR/commits.$START-$END.json gzip -f $TMPDIR/commits.$START-$END.json START=$(( $START + $STEP )) END=$(( $START + $STEP - 1 )) done So $TMPDIR/bla.xml is overwritten every iteration. Well: - If $TMPDIR=/var/tmp which is on UFS the script works. - If %TMPDIR=/tmp which is tmpfs the xml2json.py script very often gives errors about the XML structure of bla.xml like if the file is truncated or empty. So it looks like something is happening on tmpfs that the data is not yet 'synced'. Can this be a threading/cpu-cache issue on aarch64? This is on an RPI3B+. FreeBSD rpi3 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 #5 r338616: Wed Sep 12 22:23:05 CEST 2018 builder@rpi3:/data/src/obj-head/data/src/head/arm64.aarch64/sys/GENERIC-NODEBUG arm64 Can I do more testing or provide more information before creating a PR about this? Regards, Ronald. From owner-freebsd-current@freebsd.org Thu Oct 25 20:29:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E83FF1087A04 for ; Thu, 25 Oct 2018 20:29:36 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 84ECE71A6E; Thu, 25 Oct 2018 20:29:36 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id C6B39E5464; Thu, 25 Oct 2018 14:30:13 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ddo8LS_9CiEu; Thu, 25 Oct 2018 14:30:13 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Thu, 25 Oct 2018 14:30:13 -0600 (MDT) To: FreeBSD Current Cc: des@freebsd.org From: Rebecca Cran Subject: Warning about $local_unbound_tls not being set properly, on first boot of 12.0-BETA1 Message-ID: <67e3f1b9-622f-dd69-c593-efa873e27823@bluestop.org> Date: Thu, 25 Oct 2018 14:29:34 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed 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: Thu, 25 Oct 2018 20:29:37 -0000 After installing 12.0-BETA1, on the first boot I noticed a warning about $local_unbound_tls not being set properly. It looks like that flag was only added recently by Dag-Erling, in "Add support for DNS-over-TLS to the local_unbound service." -- Rebecca From owner-freebsd-current@freebsd.org Fri Oct 26 06:49:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F94F10D8D18 for ; Fri, 26 Oct 2018 06:49:07 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 873CC873A5 for ; Fri, 26 Oct 2018 06:49:06 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id i8-v6so335167wmg.0 for ; Thu, 25 Oct 2018 23:49:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=RBWgzBEkpTZ455U+zAmybu9a5Kl/fm24m1agQRAwS5M=; b=Wu6Qs5+gRIJpb8QWAqwtJLQ5ECEnhn81vAy2Bjthv0d7ReV3ZH2FpPaJN5xkYHdz9i lpDzp7fI3y3NNH59qaDMHJNXmdym1H2rOC0yMxBjWpjhvexZ40thje3zrMS1kuJlch8C NBpdlmdYlrTdBuh5Jld/A823onfwRjYkvswSCCCcN9PQlIN9XaT5+UOa2rhtWbY31a6O tHezS67TejO4/lzb2DQIGLYaQ54nNrMSggC4lhb9aWqkqx9NXtS8S3qRzHxPZ5zMheqt kvBs7D7ntCXKvAou1cR7QeXHFsE0C0TNXhd1hPH5v2Mh8g4h7OAtjAmTz5lzZ9TWcMk9 A1bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=RBWgzBEkpTZ455U+zAmybu9a5Kl/fm24m1agQRAwS5M=; b=gF8uJq3rblhIP9LDO2CBOovZaq6yU9Rjc2B5AdEt75gOzn9CD2GpiBLhheaLGKPpwA ErTL6pPaYjgJkxDrlaDznZ3kb6dxLYb2UiR/2gZ0zz0Rs9ALnbWGhn116NhuL9Ba7yyS xULyk19xiU2sywPU4KkKNhcgc74k+sypq2fgRw9DwHQNknAbrWEabjiL6AhR0aETQKbI +0QY3BT4DYZ99TS+Jll6q919gS8CUWq+Re7v31KwKFhdf7S+p6wDt3k+bJSBSVZ8zzLS NI8WgLB9E8jPlMsdTKEyQE95qKAXafv/77rsf0m7Ugj/iApQeI9rGS8DnYa05EDlLmM9 qnOQ== X-Gm-Message-State: AGRZ1gKF/SxVGvkx+K1Vhbw70dcp5tjsi+SiaM7qg0U8ThG2kkodlXII Euha97d0elox1kVGTlsAu+S/y3oe8M0= X-Google-Smtp-Source: AJdET5cNLV4Y/fqmYu8ohu7gMm/8i4LDAA9KRUuU1VEy1Y+Kgm1usJAPpCMNNpi6wG2Ffag7Fsiz9w== X-Received: by 2002:a1c:80d4:: with SMTP id b203-v6mr4545671wmd.100.1540536543993; Thu, 25 Oct 2018 23:49:03 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id c64-v6sm2392147wma.44.2018.10.25.23.49.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Oct 2018 23:49:01 -0700 (PDT) Subject: Re: DRM: radeonkms no longer usable following a switch to stable, FreeBSD 12.0-BETA1 From: Graham Perrin To: FreeBSD Current References: <16278ced-e565-917f-5015-5083d2171bb0@gmail.com> <81d1e9cc-cdfe-81ec-1168-54b2fa397c59@gmail.com> Message-ID: Date: Fri, 26 Oct 2018 07:49:01 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <81d1e9cc-cdfe-81ec-1168-54b2fa397c59@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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: Fri, 26 Oct 2018 06:49:07 -0000 On 22/10/2018 04:34, Graham Perrin wrote: > … > /usr/local/bin/xauth: (stdin):1:  bad "remove" command line > /usr/local/bin/xauth: (stdin):2:  bad "add" command line > /usr/local/bin/xauth: (stdin):1:  bad "remove" command line > /usr/local/bin/xauth: (stdin):2:  bad "add" command line > … > > What next? Any suggestions? tl;dr worked around by stepping away from stable; I stepped up to 13.0-CURRENT. Summary information:  . From owner-freebsd-current@freebsd.org Fri Oct 26 14:05:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EA1310E83D3 for ; Fri, 26 Oct 2018 14:05:28 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD77478D83; Fri, 26 Oct 2018 14:05:27 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-wr1-x42d.google.com with SMTP id u1-v6so1522128wrn.0; Fri, 26 Oct 2018 07:05:27 -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=sc0eDnMEMyL5rFKFkPM70Lvsb6gs22WBWsjzpm70SOo=; b=lQ/VOAhUS5mymBcNF4CGki8kbZJ0tF1tstisLIDwkS8oEUswrT6Gv3oP6V7eIubgkK Nof0wv5e8y6T8LhxEjRVcEVO4IGsDAXwOFkJdfCfd7b+IQH29ZE48bAZ4wroflQhKVwP oEAK1mC3mpr39KSVEQHVTqVZ96mE63Bzdr8Uw97IaT0OC+dt7y566AnA8K3Ism2/yXPx UVl2XtTJphzH1gDquxo1ntOfDGvqQB4rgdsGVy7QGHnpO2hmB3A4G+ZfbQkzbSwjuz/f fLqpctld8MHkC5873m9Q92xSwrXX8cnAgBSMs7SRwy0uQ9yzqmsrXGaj2aCyJEACq/Oz vMhw== 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=sc0eDnMEMyL5rFKFkPM70Lvsb6gs22WBWsjzpm70SOo=; b=s3YHdZqB1tMHK8o8Czu10dCqFLfCJWJ5sYfzJLcpqiIU3/KtKH6YUpNp0C+C01wMMY OpfZTos6SWbQCwk9z8Y9v7mx3Iqb0cut3R+bhdbktl1n0L5tceC26kgBzskvB4hvfReh nrkFv/H1t2HKo11mwRdNUUzOBiZuCJnQk492jUc4mDFeAKFOUMs1bF/SKhFk57C7qoTO D4DhyTgaO9+vme4Tx6HW40f0iFApqJ+RUa5is3OzAU25YNWXeygTMRG5IeikCALYhx0z BsLIWmogrEvYYYSFz+o2dzRdysuTZkHv7Q+3QmbWnln8jDoq5n38LH/vtNYlUV7qXs3r lMww== X-Gm-Message-State: AGRZ1gKKBgYp8X8inVhCGcK/umvV7ft9u8C8n78ozITzldJyNqJI57mb rFZaq4yh2GTGVpBLVe20Ce2YdnCQeM80yHpGyynCGw== X-Google-Smtp-Source: AJdET5enbuKVDufbQhiQ1faXo0kCew39oeMeGJMA0QESPyuIzMgzhf35LT8oEPiC5ZgW6tp4r97kKjQ6etHKX3iC9yo= X-Received: by 2002:adf:a144:: with SMTP id r4-v6mr5744405wrr.169.1540562726412; Fri, 26 Oct 2018 07:05:26 -0700 (PDT) MIME-Version: 1.0 References: <20181023133504.GA28755@raichu> <20181025173056.GD73360@raichu> In-Reply-To: <20181025173056.GD73360@raichu> From: Rajesh Kumar Date: Fri, 26 Oct 2018 19:35:14 +0530 Message-ID: Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 To: markj@freebsd.org Cc: freebsd-current@freebsd.org 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: Fri, 26 Oct 2018 14:05:28 -0000 Hi Mark, Thanks for the inputs. With the two patches you pointed out, I could able to compile from current, install and boot properly without any panic. Will these changes be taken into stable/12 and be part of upcoming 12.0 releases? On Thu, Oct 25, 2018 at 11:01 PM Mark Johnston wrote: > On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > > Hi Mark, > > > > > From the db> prompt, could you please run "show page" and "show pageq", > > > and post the output? > > > > The system gets hung when it runs to db prompt. I only have the option to > > force shutdown at that point. Is there any other way, I can collect what > > you need? > > Just a followup for the list: the issue should be fixed by the > following two patches: > https://reviews.freebsd.org/D17418 > https://reviews.freebsd.org/D17704 > From owner-freebsd-current@freebsd.org Fri Oct 26 16:48:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADC6F10EB675 for ; Fri, 26 Oct 2018 16:48:11 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 444427E267 for ; Fri, 26 Oct 2018 16:48:11 +0000 (UTC) (envelope-from des@des.no) Received: from next.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 01297451E; Fri, 26 Oct 2018 16:48:03 +0000 (UTC) Received: by next.des.no (Postfix, from userid 1001) id C4F43101E0; Fri, 26 Oct 2018 18:48:03 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Rebecca Cran Cc: FreeBSD Current Subject: Re: Warning about $local_unbound_tls not being set properly, on first boot of 12.0-BETA1 In-Reply-To: <67e3f1b9-622f-dd69-c593-efa873e27823@bluestop.org> (Rebecca Cran's message of "Thu, 25 Oct 2018 14:29:34 -0600") References: <67e3f1b9-622f-dd69-c593-efa873e27823@bluestop.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Date: Fri, 26 Oct 2018 18:48:03 +0200 Message-ID: <86d0rwhcxo.fsf@next.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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, 26 Oct 2018 16:48:11 -0000 Rebecca Cran writes: > After installing 12.0-BETA1, on the first boot I noticed a warning > about $local_unbound_tls not being set properly. Ah, I should probably have added it to /etc/defaults/rc.conf. Can you do that (just set it to =E2=80=9Cno=E2=80=9D) and let me know if it helps? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@freebsd.org Fri Oct 26 17:15:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 235C710EC41F for ; Fri, 26 Oct 2018 17:15:25 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 B78C77F80D for ; Fri, 26 Oct 2018 17:15:24 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id DC2AAE6CBC; Fri, 26 Oct 2018 11:15:55 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id VY8vx04-XvJu; Fri, 26 Oct 2018 11:15:55 -0600 (MDT) Received: from c02t93w9h03m.hgst.com (unknown [199.255.45.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Fri, 26 Oct 2018 11:15:55 -0600 (MDT) Subject: Re: Warning about $local_unbound_tls not being set properly, on first boot of 12.0-BETA1 To: =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= Cc: FreeBSD Current References: <67e3f1b9-622f-dd69-c593-efa873e27823@bluestop.org> <86d0rwhcxo.fsf@next.des.no> From: Rebecca Cran Message-ID: <5e7aee8a-8df2-608f-f9fc-d5643a66a709@bluestop.org> Date: Fri, 26 Oct 2018 11:15:15 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <86d0rwhcxo.fsf@next.des.no> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Fri, 26 Oct 2018 17:15:25 -0000 On 10/26/18 10:48 AM, Dag-Erling Smørgrav wrote: > Rebecca Cran writes: >> After installing 12.0-BETA1, on the first boot I noticed a warning >> about $local_unbound_tls not being set properly. > Ah, I should probably have added it to /etc/defaults/rc.conf. Can you > do that (just set it to “no”) and let me know if it helps? That worked: the warning disappeared. -- Rebecca From owner-freebsd-current@freebsd.org Fri Oct 26 18:14:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E9F610ED5D5 for ; Fri, 26 Oct 2018 18:14:10 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 881B88136C for ; Fri, 26 Oct 2018 18:14:09 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: by mail-io1-xd31.google.com with SMTP id q18-v6so1278499iod.5 for ; Fri, 26 Oct 2018 11:14:09 -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=bTcWCnLMHtLb/x9PKFjHFsicQclufV8PdfFoMioZ1pk=; b=L0Ugs67VIM5UY3no2k6R8rwZ4FbhZa5IqlznQj2tfb4yNonJKF4o+JsWuP4lZziz77 Rt1DpKpwNhLJDW1ya6EwJKQKZ4Px4TyEr19cAq3xeyjloXdwVmlW+vh3AxJuWlVRvi+r QFaBlEgj4Q1WgbA9aAi+FHX3udzwXgO06zYXpPPPDJEpQAba0JhRa9+HUM8beWTqJoM6 45nO2QEsgSVxodB6BYZTOVd7ZI4PjKu1dka/Dd8YE/xVDOKuzdO8DjsRg5evq4yWjduM r/HYEc7S4GNUmpZm21WXLni3LyEVCKqBA5DrbFADFk/08OGHCxweYGNX9CsXK7izsmUS Rz5g== 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=bTcWCnLMHtLb/x9PKFjHFsicQclufV8PdfFoMioZ1pk=; b=PI8l8uQhUIn4mEZUh03YhNnzuvVzuwwygqSFEPPtUYk9czkzObf/V9GyLhFZQYKsS0 R5kJqFcBlxA1lFhvLcYZlX9EquTXRk3pAWH3g7cFJJ7DHOtC8Aihict1gYsxfoO8SVvC JcyPucxkOYY/KZ7YUyVoY2eZWp2Ja6T5PM9YsI72uizgbDQ9E22NbOhSbx6ZeuQa98Fa Eb5ou2jZtQvH2tGOzfdADMB4ZQLks7EDlJuEEKMCoRNwYvAOqi4Jv7lmEXXG57TxF2ik XCIIFKfdZLhyeCMR2BfksSSfz/J4SJpsrkN1AfGxgtvS3GHuiMQCmR8vBKrmgmGzm1zE ll5w== X-Gm-Message-State: AGRZ1gI4JdMBGxeD4kWZWG4GlvfMPcVAcXNMskpLjagWEc2Y2BXPQOvH NAk2KytIt5OS4sv4/Vi49zhUdGYGBg8t7l4Vi1fBbg== X-Google-Smtp-Source: AJdET5euY2Y3hWBqCkKYZcSEHaf85AAw5MMxa0LfOl2P43l2Nk85prgeFfP1nrqwpQOm0wmhao0lWKUhpDX5W0qzK6A= X-Received: by 2002:a6b:ba86:: with SMTP id k128-v6mr3048745iof.254.1540577648748; Fri, 26 Oct 2018 11:14:08 -0700 (PDT) MIME-Version: 1.0 References: <20181009213425.GG61558@FreeBSD.org> <346b8805-f4d3-dc90-c882-d72f640b6a5c@protected-networks.net> In-Reply-To: From: Oleg Lelchuk Date: Fri, 26 Oct 2018 14:13:57 -0400 Message-ID: Subject: Re: HEADS-UP: OpenSSL 1.1.1 in 12.0 To: ronald-lists@klop.ws Cc: freebsd-current@freebsd.org 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: Fri, 26 Oct 2018 18:14:10 -0000 libtorrent still can't be built with the new openssl On Sat, Oct 13, 2018 at 4:40 AM Ronald Klop wrote: > On Sat, 13 Oct 2018 02:00:16 +0200, Don Lewis > wrote: > > > On 11 Oct, Don Lewis wrote: > >> On 11 Oct, Don Lewis wrote: > >>> On 11 Oct, freebsd.current@clogic.com.ua wrote: > >>>> On 2018-10-10 06:14, Michael Butler wrote: > >>>>> On 10/9/18 5:34 PM, Glen Barber wrote: > >>>>>> OpenSSL has been updated to version 1.1.1 as of r339270. > >>>>>> > >>>>>> It is important to rebuild third-party packages before running: > >>>>>> > >>>>>> # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > >>>>>> > >>>>>> Thank you for your patience while this work was in progress, and > >>>>>> thank > >>>>>> you to all involved for their hard work in getting things ready for > >>>>>> this > >>>>>> update. > >>>>> > >>>>> So far, I've found two ports that will no longer build. They are: > >>>>> > >>>>> net-mgmt/net-snmp > >>>>> security/opencryptoki > >>>>> > >>>>> I simply chose those that were linked to /usr/lib/libssl.so.8 where > >>>>> the > >>>>> openssl update creates libssl.so.9. There may be more I haven't found > >>>>> yet, > >>>>> > >>>>> imb > >>>> > >>>> You always can add DEFAULT_VERSIONS+=ssl=openssl to /etc/make.conf to > >>>> use openssl from ports. > >>>> Anyway, I think apps from ports need to use openssl from ports. > >>> > >>> I've been doing this for a long time, but I still see a fair amount of > >>> breakage with the new base OpenSSL. I suspect that some ports are > >>> incorrectly stumbling across the new bits in base even though they > >>> shouldn't be looking there. > >> > >> security/p5-Net-SSLeay is hardwired to use base OpenSSL, so changing the > >> default version can't be done to unbreak p5-IO-Socket-SSL. > >> > >> devel/libsoup appears to allow the OpenSSL version to be set, but > >> doesn't > >> have an option for GSSAPI, so it attempts to use base GSSAPI with ports > >> OpenSSL which is not a valid combo. > >> > >> emulators/virtualbox-ose is hardwired to use base OpenSSL. > > > > I now think the problem with virtualbox-ose is not the port. Rather it > > is the fact that that the base libssl.so and the libssl.so installed by > > the security/openssl have the same shared library version number even > > though they are radically different OpenSSL versions. > > > I added this to libmap.conf: > cat /etc/libmap.conf > # $FreeBSD: head/libexec/rtld-elf/libmap.conf 338741 2018-09-18 00:25:00Z > brd $ > includedir /usr/local/etc/libmap.d > libssl.so.8 libssl.so.9 > libcrypto.so.8 libcrypto.so.9 > > This made pkg run again. And now I'm waiting for the next pkg build to > run > pkg upgrade -f and upgrade everything. > I guess that will solve all issues. > > Ronald. > _______________________________________________ > 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 Fri Oct 26 18:59:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB0741085834 for ; Fri, 26 Oct 2018 18:59:05 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-it1-x133.google.com (mail-it1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AECD833EF for ; Fri, 26 Oct 2018 18:59:05 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-it1-x133.google.com with SMTP id k206-v6so2755457ite.0 for ; Fri, 26 Oct 2018 11:59:05 -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=D6d7w2bVxlbpxoUh22YqWGOsg2LasY1qgYCo6HS4tGg=; b=XY+TWBF3fHCVhpSemDyK7uFK94JwYJuLD13SZIdb70bU1h+yiYkPaKxPhDHD2X7R1P Y0cH9VCcyjC7pPp/cZInAySWds4263lgfWVvN2JNZf6HCcouQqoBSsLoQG3WDg4WzGSL 5ads2O7U8MymWnKGwkEylyN3j7XGD+hLkfKvT+oUTlfQR8UrQPVF+abVJBYD8CseK2HO jDZORqKlqwazZA0GegsAnvTJRffHvy053eeqAfMmPV3AUvnicdvsBSZyR0IP3pO3o0tA cUnFqd7oofmkwgcVbxxSsZ+CwljVNvmH3H5rfcLUDJTLfkkxKIEvkvLFfvhJ0SMvNIV1 jPfQ== 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=D6d7w2bVxlbpxoUh22YqWGOsg2LasY1qgYCo6HS4tGg=; b=mY3etF6yJWbLEXQUGx1Y83Iv2EPQjJ+pGmJJBIOxMnYFD1lDVq7VYbAZ7YYykKF0V3 T/og5fY9o2kVn0At1y6qafYHdporFkNwAmed08Wal7jA2j6GoqMz35REip7tfzoa3s4Z oMEPiZcAPAa+hC87MBLl4DY84GYRfyu3RY2/G79HZt6Ip9z7JJRWyEDjB2iBR+1DkDRb zaTO425ykpbf2tWRhOn9SaqHpG7c6i0ur2CAn/gA2n7tBSFzixAltQQXtMH+v85Elxqq E+2pAL/pOQagQCKgVC0+/XHImZwRAI7HTxzQIqdLpG+q00XPlPvIqnkLbjS//UlX94kE iQ3Q== X-Gm-Message-State: AGRZ1gKHVVh0UN+eyH3LpIdA7Mupg2jrVRxmgBrVtmsCrtsDAW+pmgw/ PQyF697GJIqdR1gujs9tXBg= X-Google-Smtp-Source: AJdET5ccBUB3QAXCfsjeGyaGK83hm0crWI0SDVA/d0nGoYGuDwiCWoQ26Tf6Zeu06o9IIBX4v0M91w== X-Received: by 2002:a24:61d2:: with SMTP id s201-v6mr3976020itc.64.1540580344321; Fri, 26 Oct 2018 11:59:04 -0700 (PDT) Received: from raichu (toroon0560w-lp130-08-67-71-176-199.dsl.bell.ca. [67.71.176.199]) by smtp.gmail.com with ESMTPSA id u206-v6sm6845466iod.18.2018.10.26.11.59.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 26 Oct 2018 11:59:03 -0700 (PDT) Sender: Mark Johnston Date: Fri, 26 Oct 2018 14:58:57 -0400 From: Mark Johnston To: Rajesh Kumar Cc: freebsd-current@freebsd.org Subject: Re: Facing kernel panic during early boot from 12.0 ALPHA9 Message-ID: <20181026185857.GA33894@raichu> References: <20181023133504.GA28755@raichu> <20181025173056.GD73360@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-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: Fri, 26 Oct 2018 18:59:05 -0000 On Fri, Oct 26, 2018 at 07:35:14PM +0530, Rajesh Kumar wrote: > Hi Mark, > > Thanks for the inputs. With the two patches you pointed out, I could able > to compile from current, install and boot properly without any panic. > > Will these changes be taken into stable/12 and be part of upcoming 12.0 > releases? Yes, I will attempt to get them into 12.0. > On Thu, Oct 25, 2018 at 11:01 PM Mark Johnston wrote: > > > On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote: > > > Hi Mark, > > > > > > > From the db> prompt, could you please run "show page" and "show pageq", > > > > and post the output? > > > > > > The system gets hung when it runs to db prompt. I only have the option to > > > force shutdown at that point. Is there any other way, I can collect what > > > you need? > > > > Just a followup for the list: the issue should be fixed by the > > following two patches: > > https://reviews.freebsd.org/D17418 > > https://reviews.freebsd.org/D17704 > > From owner-freebsd-current@freebsd.org Fri Oct 26 21:47:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B84B10C7ED2 for ; Fri, 26 Oct 2018 21:47:21 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: from mail-yw1-xc41.google.com (mail-yw1-xc41.google.com [IPv6:2607:f8b0:4864:20::c41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9B216BFFA for ; Fri, 26 Oct 2018 21:47:20 +0000 (UTC) (envelope-from harry@yewbarrow.net) Received: by mail-yw1-xc41.google.com with SMTP id t78-v6so1048299ywg.11 for ; Fri, 26 Oct 2018 14:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yewbarrow-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FotkN9dCxgX3eWChTVgn0lC5f7UbHl60YtGorWK8woY=; b=OASvfaCBmXT2rZbXPb0t/9yyra/pD7F352gmbIrXPJy4FQ1/B2PBET7qVMV3WzBTNC nnXKttEuIfbw3Xi3VHH6kJ8ERvT967OiAPqhBp2eYnOx6jE24jgG8YJA6F1MHzVQFzLh 7HbYbj1kDgSMWtxG94UFFaY/N61Zy/1vbXIR3mN33SQtp71L2yBYuft9O0X6+o4T7LEp bxIqABxmpeZ8VKoaJeqtVPzFH/K41i67IpUR1x78fGZujE6J/cC/3m9Z73/2DbGul0u2 N/HCyauCatPta7JG+ek0HaOts2ZZzAoWdvM/gZhJOT9QNYEhatecrmbIBKYpdtaw+Jty aK4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FotkN9dCxgX3eWChTVgn0lC5f7UbHl60YtGorWK8woY=; b=qqIR4zfSPzLq0TzINh5JBkDIiZfuB/S7oEOvMqJ+7tC+0WtzECGDbgYaKMfdeT/Zpl 8TbUW2btPPQJPkeBthyrJTn1y8BKSY8inIAnMw4rsZH18n1njgQSVUI3zWythXtUm5h3 hEymDmfE3I1L80goRFIuYBJ3KruQw5nFqqC5BsBVGjzIhv8Y6mimcRzs7zHgjsdnXrPI wmDS9XPk7XJZK/YOBbvtmW1rP7KUP+S3nZ7DvwTQBgNjiOtaMd9vtOP2cavKYYmxzN0X m0n+Xzbq98E3jHXHB1Cy0SDEr2jkkbs5GrCqso78jggg3ZyuMB7wgVc5u5s5fXF5ux7f O0FQ== X-Gm-Message-State: AGRZ1gIiG99xLKm486kAjp2zWGu/jYTQ1e/P2KxVeeaJaq1cNuckP7Oq PPBx6QuLWRh3GL5tCqNnPfF+xxVIZdko1rhSO+FUYQ== X-Google-Smtp-Source: AJdET5fBjPMd2V4Pi8g773iql7WbM2zViP1ZX2fgGCH2s0WGdc9JA4MCFXN0pmvz0mw65JPj7FuAJjenxexpOhy9L5k= X-Received: by 2002:a81:5214:: with SMTP id g20-v6mr5454524ywb.252.1540590439937; Fri, 26 Oct 2018 14:47:19 -0700 (PDT) MIME-Version: 1.0 Sender: harry@yewbarrow.net Received: by 2002:a25:807:0:0:0:0:0 with HTTP; Fri, 26 Oct 2018 14:47:19 -0700 (PDT) In-Reply-To: <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> From: Harry Newton Date: Fri, 26 Oct 2018 22:47:19 +0100 X-Google-Sender-Auth: kAS60LKsv_LZVwbJKFTiNaTdTn8 Message-ID: Subject: Re: UEFI boot hangs after loader To: Toomas Soome , imp@bsdimp.com Cc: FreeBSD Current , Kyle Evans 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, 26 Oct 2018 21:47:21 -0000 So patching out find_currdev() in efi/loader/main.c allows the machine to boot. The hang occurs in the call to efi_devpath_name() in match_boot_info() because the (last) call to ConvertDevicePathToText() call does not return. /H On 24 October 2018 at 07:32, Toomas Soome wrote: > > > > On 24 Oct 2018, at 00:51, Kyle Evans wrote: > > > > Hi, > > > > I suspect 4th vs. lua has no impact here, given the output shown -- > > can you throw one of the installer images [0] on some removable media > > and give that a shot for booting? If that works, we can explore UEFI > > variables from there. > > > > > Yes, thats my guess too, my guess is that since in general the uefi boot > is working, in this case it has to be some corner case, and I would start > checking with boot variable related code; specifically, I=E2=80=99d sugge= st to > patch (temporarily) the find_currdev() in efi/loader/main.c to set > do_bootmgr =3D false and see if that will fix the boot. Then we can explo= re > what is happening in match_boot_info() > > rgds, > toomas > > > efibootmgr will only work on a successful UEFI boot, unfortunately- if > > we didn't make uefi loader -> kernel transition, then we don't have > > access to runtime services. > > > > Thanks, > > > > Kyle Evans > > > > [0] https://download.freebsd.org/ftp/releases/amd64/amd64/ISO- > IMAGES/12.0/ > > > > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: > >> > >> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-ma= de > the > >> binaries in /boot but this doesn't solve the problem. It did copy > >> /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(8= ) > >> which is what is called from /boot/boot1.efi and which contains the > strings > >> I see on the console before the hang. But it must then call / read > >> something else and I don't think it can find it. Not sure why it > doesn't > >> produce an error message. I *think* it may be something to do with EF= I > >> variables, but as efibootmgr doesn't work I can't explore this, despit= e > >> efirt being in the kernel. > >> > >> Suggestions received welcomed, and new suggestions / leads to follow > also > >> very much welcomed. > >> > >> /H > >> > >> > >> On 23 October 2018 at 21:33, Harry Newton wrote: > >> > >>> Right ... I've the binaries in /boot, freshly made. This might be a > silly > >>> question ... do I not need to copy them (or dd the boot1.efifat image= ) > to > >>> the EFI partition ? > >>> > >>> /H > >>> > >>> On 23 October 2018 at 21:30, Toomas Soome wrote: > >>> > >>>> you should have the binaries in boot - just ln (or copy) one to > loader.efi > >>>> > >>>> rgds, > >>>> toomas > >>>> > >>>> > >>>> On 23 Oct 2018, at 23:22, Harry Newton wrote: > >>>> > >>>> Yes ... so as everything is built, can I just alter > LOADER_DEFAULT_INTERP > >>>> in /etc/make.conf and then reinstall just the loader and boot parts > onto > >>>> the UEFI partition ? If so, how ? > >>>> > >>>> > >>>> On 23 October 2018 at 21:17, Toomas Soome wrote: > >>>> > >>>>> ok, in that case I=E2=80=99d suggest to test out if forth based one= is still > >>>>> working - at least you can get the bootable system. And then there > is a > >>>>> chance to debug the lua version too (note it should be possible to > chain > >>>>> /boot/loader_lua.efi). > >>>>> > >>>>> rgds, > >>>>> toomas > >>>>> > >>>>>> On 23 Oct 2018, at 23:08, Harry Newton wrote: > >>>>>> > >>>>>> So it's got FORTH in it, but my loader is lua based, and also > doesn't > >>>>>> appear to read loader.rc. > >>>>>> > >>>>>> /H > >>>>>> > >>>>>> On 23 October 2018 at 21:03, Toomas Soome wrote: > >>>>>> > >>>>>>> hm. in that case, whats the content of /boot/loader.rc ? > >>>>>>> > >>>>>>> rgds, > >>>>>>> toomas > >>>>>>> > >>>>>>> > >>>>>>> On 23 Oct 2018, at 23:01, Harry Newton wrote: > >>>>>>> > >>>>>>> If boot menu is the screen where you get the options for various > >>>>> kernels > >>>>>>> and the picture of the daemon head, no. It stops at the point in > my > >>>>> email > >>>>>>> =E2=80=94 though not as I said just before the kernel is loaded b= ut in > point > >>>>> of > >>>>>>> fact before the menu. > >>>>>>> > >>>>>>> I've also rebuilt the kernel and still can't use efibootmgr which > is > >>>>>>> puzzling me. > >>>>>>> > >>>>>>> /H > >>>>>>> > >>>>>>> > >>>>>>> On 23 October 2018 at 20:56, Toomas Soome wrote: > >>>>>>> > >>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, then > type > >>>>>>>> start - if its bootfort based loader, it will load the kernel an= d > >>>>> modules. > >>>>>>>> lsmod will then list the loaded files. > >>>>>>>> > >>>>>>>> If the loader prompt is still usable, then next command would be= : > >>>>> boot > >>>>>>>> > >>>>>>>> rgds, > >>>>>>>> toomas > >>>>>>>> > >>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton wrote= : > >>>>>>>>> > >>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to 12.0-BET= A1 > >>>>>>>> r339529 > >>>>>>>>> by source. Have a problem with booting which hangs after: > >>>>>>>>> > >>>>>>>>>>> FreeBSD EFI boot block > >>>>>>>>> Loader path: /boot/loader.efi > >>>>>>>>> > >>>>>>>>> Initializing modules: ZFS UFS > >>>>>>>>> Probing 5 block devices ... done > >>>>>>>>> ZFS found the following pools: zroot > >>>>>>>>> UFS found no partitions > >>>>>>>>> Consoles: EFI console > >>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 > >>>>>>>>> > >>>>>>>>> Command line arguments: loader.efi > >>>>>>>>> EFI version 2.31 > >>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) > >>>>>>>>> Console: efi(0) > >>>>>>>>> Load Path: HD(4, GPT [ ... ] > >>>>>>>>> Load Device: Pci Root [ ... ] > >>>>>>>>> Boot Current: 0001 > >>>>>>>>> Boot Order: 0001 [x] > >>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI > >>>>>>>>> - > >>>>>>>>> > >>>>>>>>> So it gets into loader.efi which runs but stops I think just > before > >>>>>>>> loading > >>>>>>>>> the kernel. Partitions: > >>>>>>>>> > >>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) > >>>>>>>>> 40 1600 1 efi (800K) > >>>>>>>>> 1640 1024 2 freebsd-boot (512K) > >>>>>>>>> 2664 1432 - free - (716K) > >>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) > >>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) > >>>>>>>>> 250068992 648 - free - (324K) > >>>>>>>>> > >>>>>>>>> and the EFI partition is FAT 12. > >>>>>>>>> > >>>>>>>>> I can't provide (at the moment) any output from efibootmgr: > >>>>>>>>> > >>>>>>>>> root@gryphon:~ # efibootmgr -v > >>>>>>>>> efibootmgr: efi variables not supported on this system. root? > >>>>> kldload > >>>>>>>> efirt? > >>>>>>>>> root@gryphon:~ # kldload efirt > >>>>>>>>> kldload: can't load efirt: module already loaded or in kernel > >>>>>>>>> > >>>>>>>>> which I don't understand. > >>>>>>>>> > >>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see if > that > >>>>>>>> allows > >>>>>>>>> me to load efirt / use efibootmgr. > >>>>>>>>> > >>>>>>>>> In the meantime, I should be very grateful for any advice. > >>>>>>>>> > >>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and > dropping > >>>>> into > >>>>>>>> its > >>>>>>>>> loader to get to the installed 12-STABLE ). > >>>>>>>>> > >>>>>>>>> /Harry > >>>>>>>>> _______________________________________________ > >>>>>>>>> freebsd-current@freebsd.org mailing list > >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>>>>> reebsd.org" > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Harry Newton > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Harry Newton > >>>>>> _______________________________________________ > >>>>>> freebsd-current@freebsd.org mailing list > >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f > >>>>> reebsd.org" > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Harry Newton > >>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> Harry Newton > >>> > >> > >> > >> > >> -- > >> Harry Newton > >> _______________________________________________ > >> 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" > > --=20 Harry Newton From owner-freebsd-current@freebsd.org Fri Oct 26 21:58:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71D0310C9366 for ; Fri, 26 Oct 2018 21:58:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07CEA6CE23 for ; Fri, 26 Oct 2018 21:58:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-vk1-xa2a.google.com with SMTP id k77so659893vke.12 for ; Fri, 26 Oct 2018 14:58:25 -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=6zlTyI7yuSOjETaweh2KiDv1j6DMK626FozdzCg0D+Q=; b=iSodRC8TT5Iu3OVTaroZkUdaoyZsW9OAxTf2dCrfKEHhgoyLSasInmTswaya6V/xbE Z+G1ylwyEr5YlZBmJjUpV75SBP2zUr0hoT44OuvvuX7iD0Ih2rk36vdHMzgzRUv5Prxt jjFt/U0xjdI07Rl/ayGGdnEx7bm7y8QpV2/VCu9qSylYlMfOXjB9uPul0H8HQxCwwXnL yKI233wj06aMkocGZ+C4N6hxUti47McMFCFRZQDxVHtwOIhVkL7GQTbVoodwZ60Ff2nb Hx+FtF1w4PEZV2Isya7bR0J3MVBUvGrMijR1NlJJC2R9n91OCz9LhoTDo8QqnRwnSlyG XixQ== 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=6zlTyI7yuSOjETaweh2KiDv1j6DMK626FozdzCg0D+Q=; b=YLuYWqXY30nGVOh0xD5ryoRp17jnD8yYBhDh262TEXAbW2b40VW/oKmj+ze+lsoSkq rd1sukREZN9lA8IHHJWXgm8w7XiTwBIJgpro0rl3tnm6eBfqp72wSUds83Y5GvzSiDnB RMGhbYD5aiVsB5GWiEhVckY0Pa4jpLQMFIQH+ISCYdUcmHDYLgrZmMwY9OT9hRFLOT6X 5+Ld4hZj3ECd/8AbMCZfgcZE+A6tDfvRHFZUsEutxbzCaUIROipyIYM/YEzlF1Zz2qYB 75sdPAu6/28AFSl6Ti/Mkget4TaFLrkXbecsFRvbM0Qw5674YZwat1B/lMgrL37TxhwL dsHQ== X-Gm-Message-State: AGRZ1gJMVhxuuxR0glnJbOyKa99KrXtOZUE0XYKFHQck8nDqCwVIqars i9FVBWsz4RzZMS9nMX7m0YsKYfjrpZnran4sJ20htw== X-Google-Smtp-Source: AJdET5e2Na/Bj8RdeVHxjDuQWlIKm86KJlaQbeXg/OWHA0qiSYtnbl7nNGgBTipO+hD3bc4aSm/tDtvBAonHt2ds5hw= X-Received: by 2002:a1f:b547:: with SMTP id e68-v6mr2398077vkf.72.1540591104076; Fri, 26 Oct 2018 14:58:24 -0700 (PDT) MIME-Version: 1.0 References: <282E6F72-6573-4F0E-81AB-25110855EBB7@me.com> <2950121D-C985-4F2E-A512-FB73CFDF48BC@me.com> <4457A5DC-A577-4782-B1E8-306236908D5D@me.com> <3A48C6FA-805E-4B36-8C7D-A98422EBC7A5@me.com> In-Reply-To: From: Warner Losh Date: Fri, 26 Oct 2018 15:58:04 -0600 Message-ID: Subject: Re: UEFI boot hangs after loader To: Harry Newton Cc: Toomas Soome , FreeBSD Current , Kyle Evans 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, 26 Oct 2018 21:58:25 -0000 I've recreated something like this in efivar as well... I need to study the code for how to improve it to have sanity limits... I hope to have a patch soon... Thanks for this data point. I think I'm on the right track. Warner On Fri, Oct 26, 2018 at 3:47 PM Harry Newton wrote: > So patching out find_currdev() in efi/loader/main.c allows the machine to > boot. The hang occurs in the call to efi_devpath_name() in > match_boot_info() because the (last) call to ConvertDevicePathToText() ca= ll > does not return. > > /H > > On 24 October 2018 at 07:32, Toomas Soome wrote: > >> >> >> > On 24 Oct 2018, at 00:51, Kyle Evans wrote: >> > >> > Hi, >> > >> > I suspect 4th vs. lua has no impact here, given the output shown -- >> > can you throw one of the installer images [0] on some removable media >> > and give that a shot for booting? If that works, we can explore UEFI >> > variables from there. >> > >> >> >> Yes, thats my guess too, my guess is that since in general the uefi boot >> is working, in this case it has to be some corner case, and I would star= t >> checking with boot variable related code; specifically, I=E2=80=99d sugg= est to >> patch (temporarily) the find_currdev() in efi/loader/main.c to set >> do_bootmgr =3D false and see if that will fix the boot. Then we can expl= ore >> what is happening in match_boot_info() >> >> rgds, >> toomas >> >> > efibootmgr will only work on a successful UEFI boot, unfortunately- if >> > we didn't make uefi loader -> kernel transition, then we don't have >> > access to runtime services. >> > >> > Thanks, >> > >> > Kyle Evans >> > >> > [0] >> https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/ >> > >> > On Tue, Oct 23, 2018 at 4:23 PM Harry Newton wrote: >> >> >> >> I set LOADER_DEFAULT_INTERP=3D4th and went in /usr/src/stand and re-m= ade >> the >> >> binaries in /boot but this doesn't solve the problem. It did copy >> >> /boot/loader_4th.efi to /boot/loader.efi which is (according to uefi(= 8) >> >> which is what is called from /boot/boot1.efi and which contains the >> strings >> >> I see on the console before the hang. But it must then call / read >> >> something else and I don't think it can find it. Not sure why it >> doesn't >> >> produce an error message. I *think* it may be something to do with E= FI >> >> variables, but as efibootmgr doesn't work I can't explore this, despi= te >> >> efirt being in the kernel. >> >> >> >> Suggestions received welcomed, and new suggestions / leads to follow >> also >> >> very much welcomed. >> >> >> >> /H >> >> >> >> >> >> On 23 October 2018 at 21:33, Harry Newton wrote: >> >> >> >>> Right ... I've the binaries in /boot, freshly made. This might be a >> silly >> >>> question ... do I not need to copy them (or dd the boot1.efifat >> image) to >> >>> the EFI partition ? >> >>> >> >>> /H >> >>> >> >>> On 23 October 2018 at 21:30, Toomas Soome wrote: >> >>> >> >>>> you should have the binaries in boot - just ln (or copy) one to >> loader.efi >> >>>> >> >>>> rgds, >> >>>> toomas >> >>>> >> >>>> >> >>>> On 23 Oct 2018, at 23:22, Harry Newton wrote: >> >>>> >> >>>> Yes ... so as everything is built, can I just alter >> LOADER_DEFAULT_INTERP >> >>>> in /etc/make.conf and then reinstall just the loader and boot parts >> onto >> >>>> the UEFI partition ? If so, how ? >> >>>> >> >>>> >> >>>> On 23 October 2018 at 21:17, Toomas Soome wrote: >> >>>> >> >>>>> ok, in that case I=E2=80=99d suggest to test out if forth based on= e is still >> >>>>> working - at least you can get the bootable system. And then there >> is a >> >>>>> chance to debug the lua version too (note it should be possible to >> chain >> >>>>> /boot/loader_lua.efi). >> >>>>> >> >>>>> rgds, >> >>>>> toomas >> >>>>> >> >>>>>> On 23 Oct 2018, at 23:08, Harry Newton wrote: >> >>>>>> >> >>>>>> So it's got FORTH in it, but my loader is lua based, and also >> doesn't >> >>>>>> appear to read loader.rc. >> >>>>>> >> >>>>>> /H >> >>>>>> >> >>>>>> On 23 October 2018 at 21:03, Toomas Soome wrote: >> >>>>>> >> >>>>>>> hm. in that case, whats the content of /boot/loader.rc ? >> >>>>>>> >> >>>>>>> rgds, >> >>>>>>> toomas >> >>>>>>> >> >>>>>>> >> >>>>>>> On 23 Oct 2018, at 23:01, Harry Newton wrote: >> >>>>>>> >> >>>>>>> If boot menu is the screen where you get the options for various >> >>>>> kernels >> >>>>>>> and the picture of the daemon head, no. It stops at the point i= n >> my >> >>>>> email >> >>>>>>> =E2=80=94 though not as I said just before the kernel is loaded = but in >> point >> >>>>> of >> >>>>>>> fact before the menu. >> >>>>>>> >> >>>>>>> I've also rebuilt the kernel and still can't use efibootmgr whic= h >> is >> >>>>>>> puzzling me. >> >>>>>>> >> >>>>>>> /H >> >>>>>>> >> >>>>>>> >> >>>>>>> On 23 October 2018 at 20:56, Toomas Soome wrote: >> >>>>>>> >> >>>>>>>> Do you get boot menu? if so, press esc to get to ok prompt, the= n >> type >> >>>>>>>> start - if its bootfort based loader, it will load the kernel a= nd >> >>>>> modules. >> >>>>>>>> lsmod will then list the loaded files. >> >>>>>>>> >> >>>>>>>> If the loader prompt is still usable, then next command would b= e: >> >>>>> boot >> >>>>>>>> >> >>>>>>>> rgds, >> >>>>>>>> toomas >> >>>>>>>> >> >>>>>>>>> On 23 Oct 2018, at 20:45, Harry Newton >> wrote: >> >>>>>>>>> >> >>>>>>>>> Just upgraded my Asus UX303L (amd64) from 11-STABLE to >> 12.0-BETA1 >> >>>>>>>> r339529 >> >>>>>>>>> by source. Have a problem with booting which hangs after: >> >>>>>>>>> >> >>>>>>>>>>> FreeBSD EFI boot block >> >>>>>>>>> Loader path: /boot/loader.efi >> >>>>>>>>> >> >>>>>>>>> Initializing modules: ZFS UFS >> >>>>>>>>> Probing 5 block devices ... done >> >>>>>>>>> ZFS found the following pools: zroot >> >>>>>>>>> UFS found no partitions >> >>>>>>>>> Consoles: EFI console >> >>>>>>>>> FreeBSD/amd64 EFI loader, Revision 1.1 >> >>>>>>>>> >> >>>>>>>>> Command line arguments: loader.efi >> >>>>>>>>> EFI version 2.31 >> >>>>>>>>> EFI Firmware: American Megatrends (rev 4.654) >> >>>>>>>>> Console: efi(0) >> >>>>>>>>> Load Path: HD(4, GPT [ ... ] >> >>>>>>>>> Load Device: Pci Root [ ... ] >> >>>>>>>>> Boot Current: 0001 >> >>>>>>>>> Boot Order: 0001 [x] >> >>>>>>>>> Boot Info Path: HS(1, GPT, [ ... ] /\EFI\BOOT\BOOTX64.EFI >> >>>>>>>>> - >> >>>>>>>>> >> >>>>>>>>> So it gets into loader.efi which runs but stops I think just >> before >> >>>>>>>> loading >> >>>>>>>>> the kernel. Partitions: >> >>>>>>>>> >> >>>>>>>>> =3D> 40 250069600 ada0 GPT (119G) >> >>>>>>>>> 40 1600 1 efi (800K) >> >>>>>>>>> 1640 1024 2 freebsd-boot (512K) >> >>>>>>>>> 2664 1432 - free - (716K) >> >>>>>>>>> 4096 4194304 3 freebsd-swap (2.0G) >> >>>>>>>>> 4198400 245870592 4 freebsd-zfs (117G) >> >>>>>>>>> 250068992 648 - free - (324K) >> >>>>>>>>> >> >>>>>>>>> and the EFI partition is FAT 12. >> >>>>>>>>> >> >>>>>>>>> I can't provide (at the moment) any output from efibootmgr: >> >>>>>>>>> >> >>>>>>>>> root@gryphon:~ # efibootmgr -v >> >>>>>>>>> efibootmgr: efi variables not supported on this system. root? >> >>>>> kldload >> >>>>>>>> efirt? >> >>>>>>>>> root@gryphon:~ # kldload efirt >> >>>>>>>>> kldload: can't load efirt: module already loaded or in kernel >> >>>>>>>>> >> >>>>>>>>> which I don't understand. >> >>>>>>>>> >> >>>>>>>>> I'm going to rebuild the kernel (currently GENERIC) and see if >> that >> >>>>>>>> allows >> >>>>>>>>> me to load efirt / use efibootmgr. >> >>>>>>>>> >> >>>>>>>>> In the meantime, I should be very grateful for any advice. >> >>>>>>>>> >> >>>>>>>>> ( Currently booting using a 11-RELEASE memstick image and >> dropping >> >>>>> into >> >>>>>>>> its >> >>>>>>>>> loader to get to the installed 12-STABLE ). >> >>>>>>>>> >> >>>>>>>>> /Harry >> >>>>>>>>> _______________________________________________ >> >>>>>>>>> freebsd-current@freebsd.org mailing list >> >>>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >>>>>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@= f >> >>>>>>>> reebsd.org" >> >>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> -- >> >>>>>>> Harry Newton >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> Harry Newton >> >>>>>> _______________________________________________ >> >>>>>> freebsd-current@freebsd.org mailing list >> >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> >>>>> reebsd.org" >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Harry Newton >> >>>> >> >>>> >> >>>> >> >>> >> >>> >> >>> -- >> >>> Harry Newton >> >>> >> >> >> >> >> >> >> >> -- >> >> Harry Newton >> >> _______________________________________________ >> >> 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" >> >> > > > -- > Harry Newton > From owner-freebsd-current@freebsd.org Sat Oct 27 06:24:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44E3610DBB11 for ; Sat, 27 Oct 2018 06:24:07 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D8342806EA for ; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9B21E10DBB10; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89E5510DBB0F for ; Sat, 27 Oct 2018 06:24:06 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE30A806E6 for ; Sat, 27 Oct 2018 06:24:05 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w9R6NvVj083980 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Oct 2018 23:23:58 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w9R6Nv3c083979; Fri, 26 Oct 2018 23:23:57 -0700 (PDT) (envelope-from jmg) Date: Fri, 26 Oct 2018 23:23:57 -0700 From: John-Mark Gurney To: Leandro Cc: current@freebsd.org Subject: Re: UFS panics Message-ID: <20181027062357.GE75530@funkthat.com> Mail-Followup-To: Leandro , current@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Fri, 26 Oct 2018 23:23:58 -0700 (PDT) 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, 27 Oct 2018 06:24:07 -0000 Leandro wrote this message on Wed, Oct 24, 2018 at 12:22 -0300: > I'm seeing a kernel panic when trying to move a specific file. > > panic: Bad effnlink fip 0xc0000004a2c69a00, fdp 0xc000000497093be0, > tdp 0xc0000004be6295a0 > cpuid = 72 > time = 1540283798 > KDB: stack backtrace: > 0xe0000000adb8dcc0: at .kdb_backtrace+0x5c > 0xe0000000adb8ddf0: at .vpanic+0x1b4 > 0xe0000000adb8deb0: at .panic+0x38 > 0xe0000000adb8df40: at .ufs_readdir+0x2f24 > 0xe0000000adb8e1b0: at .VOP_RENAME_APV+0x190 > 0xe0000000adb8e240: at .kern_renameat+0x3c0 > 0xe0000000adb8e540: at .sys_rename+0x2c > 0xe0000000adb8e5c0: at .trap+0x65c > 0xe0000000adb8e780: at .powerpc_interrupt+0x290 > 0xe0000000adb8e820: user SC trap by 0x81010b7b8: srr1=0x900000000000f032 > r1=0x3fffffffffffc490 cr=0x34000028 xer=0x20000000 > ctr=0x81010b7b0 r2=0x8102c5950 > KDB: enter: panic > > Using 'ls' or 'rm' on the file gives a "Bad file descriptor" error. > Using 'cat', I get another panic, but now during open. > Everything indicates that the file system is in an inconsistent state. > > Therefore, I would just like to ask the following: is it expected for > kernel panics to happen when there are errors in the file system? Have you unmounted the file system, and tried to do a fsck on it? That you're getting a bad file descriptor sounds like it might be a directory entry pointing to a bad inode. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@freebsd.org Sat Oct 27 08:07:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22FF410DEC9A for ; Sat, 27 Oct 2018 08:07:50 +0000 (UTC) (envelope-from markiyan.kushnir@gmail.com) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A775C83E7A; Sat, 27 Oct 2018 08:07:49 +0000 (UTC) (envelope-from markiyan.kushnir@gmail.com) Received: by mail-oi1-x232.google.com with SMTP id c25-v6so3013672oiy.0; Sat, 27 Oct 2018 01:07: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=lS4iH8DCU4uv9DlEjonu9m5Dv3NtXiDLS8sht/UYtDI=; b=JKqK3RnN/v6b2P+vaUTqkcRhLhGvAMrfJDp3kNxRvcCChtm4cLnVbQlXn3sknebFGx NGMNPwZL4f04vYoS/peS5b6bQ45gxXekGmcr4aXhV2r3xD29yxGZji2Rwhw7wISHBmf0 VgFwRw6OW1WQyslwFp4zEM0QLnM3BooH+Th5lmADaexxCqvzZljwtIl39mt3UcdtyrGR knT6mBrfVIKoP0D8LQgsBLnqQJZ81zb+AwppxfDpm4J4B9A0coFIk4BiP0SbqdDuwubJ +z249zLKHOQ+SdReR4tlbxBJ7Zx/VpASJdAj6dqCVAvkwh26BrQw2yj/eKK0GzwBwS2+ mntQ== 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=lS4iH8DCU4uv9DlEjonu9m5Dv3NtXiDLS8sht/UYtDI=; b=G8JPgcPfbhxd/aBdyt0+tr0FI2bwvKwZAml3BVMFnv6H9TR7+UAidvtLxQoIuy2PcR HhPvyfzQ/4w7sqcwCmtLBsl/GClTkeorHAC+wUPd3qEoFLSn/XgIk6N4hiCiu+3NOJG9 WpXn3+b6kH77lY75iigM55LFM9OzIuJZTKnROOXlMo99SA38klecwdaioCTAYli60D4j 3/skAAkit7lf9tsGt7JYZvuO9FjmKreI4gpgEKDr9y2+1W/CYKDA1wkRFyGqZam3Guk0 CqjOXOkwwU4oIGSYWnL3e0EoRbQticj8TJdj/q9jRfhsigBhLV7qDol4gAdKW2QEGS0q knXw== X-Gm-Message-State: AGRZ1gJwuCyHk57dxKi1W0Ye9SVeIcOgysxe57QDedQzkTeKktIVLtyP NKNS4Alk54CwzS5cXkFibUQi2bwWUTKLW5Ah84Z4B65J X-Google-Smtp-Source: AJdET5eCogYOBdeWnMi6JJ06RXH0Ts3x/FmaU/MjiXRRQLDTMlaIdHqnBheI7kuBvrFoDuMVQENeKbT6hP898BwoRQA= X-Received: by 2002:a54:4085:: with SMTP id i5-v6mr3858773oii.302.1540627668526; Sat, 27 Oct 2018 01:07:48 -0700 (PDT) MIME-Version: 1.0 References: <67b03ad1-9b9c-5b5c-f6b6-3bbc716daf55@yahoo.com> <20181025125732.GG28382@home.opsec.eu> <8352d047-f75f-50f9-e322-443401a7b16f@freebsd.org> <20181025161545.GH28382@home.opsec.eu> <52EFEA27-9BF1-47D5-BDFF-2B5E86F15018@intel.com> <2a418d58-8c85-cbfd-a485-01f268d40ee4@freebsd.org> <5CE4041D-DC06-4356-90DF-4ADFE70B5AD9@intel.com> In-Reply-To: <5CE4041D-DC06-4356-90DF-4ADFE70B5AD9@intel.com> From: Markiyan Kushnir Date: Sat, 27 Oct 2018 11:07:36 +0300 Message-ID: Subject: Re: pkg problem on FreeBSD 13.0-CURRENT To: jeffrey.e.pieper@intel.com Cc: sbruno@freebsd.org, pi@freebsd.org, p.gunnarsson@yahoo.com, freebsd-current@freebsd.org 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, 27 Oct 2018 08:07:50 -0000 Until it settles down, you can make your own build of ports-mgmt/pkg? -- Markiyan =D1=87=D1=82, 25 =D0=B6=D0=BE=D0=B2=D1=82. 2018 =D0=BE 20:05 Pieper, Jeffre= y E =D0=BF=D0=B8=D1=88=D0=B5: > This was build this morning and includes: > > commit f37256a01fe12fe4d65128c82c6804d47dd511c1 > Author: kib > Date: Thu Oct 25 13:37:57 2018 +0000 > > Bump base OpenSSL libraries versions to avoid conflict with port's > libraries. > > Reported by: many > Reviewed by: gjb > Sponsored by: The FreeBSD Foundation > MFC after: 3 hours > > Jeff > =EF=BB=BF > > On 10/25/18, 9:52 AM, "Sean Bruno" wrote: > > > > On 10/25/18 10:29 AM, Pieper, Jeffrey E wrote: > > I'm seeing: > > > > Installing pkg-1.10.5_5... > > Extracting pkg-1.10.5_5: 100% > > ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pk= g" > > > > Thanks, > > Jeff > > Is this before or after the move of libssl.so.9 -> libssl.so.111 ? > > https://svnweb.freebsd.org/changeset/base/339709 > > sean > > > > _______________________________________________ > 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 Sat Oct 27 15:34:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39D1E10C738C for ; Sat, 27 Oct 2018 15:34:25 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B1F876EB06 for ; Sat, 27 Oct 2018 15:34:24 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 77B0B10C738A; Sat, 27 Oct 2018 15:34:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DDDA10C7389 for ; Sat, 27 Oct 2018 15:34:24 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDF406EB05 for ; Sat, 27 Oct 2018 15:34:23 +0000 (UTC) (envelope-from leandro.lupori@gmail.com) Received: by mail-yw1-xc2e.google.com with SMTP id f192-v6so81042ywh.7 for ; Sat, 27 Oct 2018 08:34:23 -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; bh=cre6/v0tjPxqWFYmxw/juNwzFMTiN9N2EX2r4yUQNU8=; b=pPEg/kfoY61a16DcNpaeV46JDNCmiiwj5SEV65slQp32eyM9HgjYTjHHt6P8Vr47Hc ywf96ZkjhFD08svqT68/tEkNeHwdrWtpzYbKkyvIvR+XOgq21421rWAbrDlNWysCPtCa lE1QH2vPFWhN67JYD+DmkzJjug8KELSPpWjE8AszWfPqel5lgda+oFMbn9FhcJslO2E2 MCN6BvS/gBJcTln96KGI4wtmkyUauUUqOiy5bgizyrp+VHg/C4HtzrFYOt6qIuH9XQ4C PXVl0Hx1aGRbN62jt8kMzE5QZqPCzhI9PkkbvqN3oVIVxd+kavYi4F8QRhWq6kNgpEv8 +SwQ== 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; bh=cre6/v0tjPxqWFYmxw/juNwzFMTiN9N2EX2r4yUQNU8=; b=ldoV7Pj+XwujO9CInmrj3hT5/0ixEP1ZumKbGqIOyMye4f8LE9MMDK5rkW8vcnmqww MSEVvLznMlkfZgUoGYIJYujW/KYeyBNmzcV/4lko1vPV/aI4TPLNhHh2ub0WxMID4Ten P9f2bzAXdYXtiARiiyb1JchBRL3kMqlUEVLUVxYaEF6NqELYjaH5sLygVaL41+ECV3PB rPllElUrUXkLmpmowyu7sOvOLY4+BKlKI5/QCk0yyetjzG/d3yHohsRPgb+8gVrhUZ93 TrZ/TpbI5CLvbncnDqEeOcDS1fyAUVSzGLn7X7CNuJIk/dmikKFmNa7zQ/yC5uxgP0jw fV3A== X-Gm-Message-State: AGRZ1gL5rDnx6UCbjWVlSOtWzHk/wVRFkhR5kkjceIAPW6w+YbeNR98w TTdpNITPWZFSgbUmByQXtHBGXd8ioha9UIZnvpYxUg== X-Google-Smtp-Source: AJdET5eGoVDN54gVwWvmwLyypqtjaHvPUuxVM3EoRmTq/KH0nj+YY5+Bg/m9lHBtRlLO/XPB8mesOgeNhl59GIYDBR0= X-Received: by 2002:a0d:d2c6:: with SMTP id u189-v6mr7203780ywd.97.1540654462929; Sat, 27 Oct 2018 08:34:22 -0700 (PDT) MIME-Version: 1.0 References: <20181027062357.GE75530@funkthat.com> In-Reply-To: <20181027062357.GE75530@funkthat.com> From: Leandro Date: Sat, 27 Oct 2018 12:34:11 -0300 Message-ID: Subject: Re: UFS panics To: current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Sat, 27 Oct 2018 15:36:27 +0000 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, 27 Oct 2018 15:34:25 -0000 Yes, I ran fsck in single user mode and it fixed some errors, one of them was the entry that was causing the panic, that was removed. I just wanted to confirm if panics on UFS were expected if the file system had errors, that Sean and Kirk confirmed, or if it should be investigated. On Sat, Oct 27, 2018 at 3:24 AM John-Mark Gurney wrote: > > Leandro wrote this message on Wed, Oct 24, 2018 at 12:22 -0300: > > I'm seeing a kernel panic when trying to move a specific file. > > > > panic: Bad effnlink fip 0xc0000004a2c69a00, fdp 0xc000000497093be0, > > tdp 0xc0000004be6295a0 > > cpuid = 72 > > time = 1540283798 > > KDB: stack backtrace: > > 0xe0000000adb8dcc0: at .kdb_backtrace+0x5c > > 0xe0000000adb8ddf0: at .vpanic+0x1b4 > > 0xe0000000adb8deb0: at .panic+0x38 > > 0xe0000000adb8df40: at .ufs_readdir+0x2f24 > > 0xe0000000adb8e1b0: at .VOP_RENAME_APV+0x190 > > 0xe0000000adb8e240: at .kern_renameat+0x3c0 > > 0xe0000000adb8e540: at .sys_rename+0x2c > > 0xe0000000adb8e5c0: at .trap+0x65c > > 0xe0000000adb8e780: at .powerpc_interrupt+0x290 > > 0xe0000000adb8e820: user SC trap by 0x81010b7b8: srr1=0x900000000000f032 > > r1=0x3fffffffffffc490 cr=0x34000028 xer=0x20000000 > > ctr=0x81010b7b0 r2=0x8102c5950 > > KDB: enter: panic > > > > Using 'ls' or 'rm' on the file gives a "Bad file descriptor" error. > > Using 'cat', I get another panic, but now during open. > > Everything indicates that the file system is in an inconsistent state. > > > > Therefore, I would just like to ask the following: is it expected for > > kernel panics to happen when there are errors in the file system? > > Have you unmounted the file system, and tried to do a fsck on it? That > you're getting a bad file descriptor sounds like it might be a directory > entry pointing to a bad inode. > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@freebsd.org Sat Oct 27 15:49:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9E0D10C7B9F for ; Sat, 27 Oct 2018 15:49:18 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 548B76F395 for ; Sat, 27 Oct 2018 15:49:18 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id F2108E7BAD for ; Sat, 27 Oct 2018 09:49:55 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9B3XujZxQIis for ; Sat, 27 Oct 2018 09:49:55 -0600 (MDT) Received: from Rebeccas-iPhone.mail (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Sat, 27 Oct 2018 09:49:55 -0600 (MDT) Date: Sat, 27 Oct 2018 09:40:40 -0600 From: Rebecca Cran To: freebsd-current@freebsd.org Message-ID: Subject: 13-CURRENT lua loader complains dynamic libs not supported X-Mailer: Airmail iOS (372) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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, 27 Oct 2018 15:49:19 -0000 When booting a recent 13-CURRENT installation, I=E2=80=99m seeing the fol= lowing: =20 Startup error in /boot/lua/loader.lua: =20 LUA ERROR: /boot/lua/loader.lua:45: error loading module =E2=80=98local=E2= =80=99 from file =E2=80=98/usr/local/lib/lua/5.3/local.so=E2=80=99: dynamic libraries not enabled: check your Lua installation. I then have to load the zfs module manually. =20 =E2=80=94 =20 Rebecca From owner-freebsd-current@freebsd.org Sat Oct 27 16:14:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE03A10C9900 for ; Sat, 27 Oct 2018 16:14:49 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 441FE701D4 for ; Sat, 27 Oct 2018 16:14:48 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from [192.168.1.14] ([90.76.61.156]) by mwinf5d01 with ME id sgEf1y00d3NFUbe03gEfq5; Sat, 27 Oct 2018 18:14:40 +0200 X-ME-Helo: [192.168.1.14] X-ME-Date: Sat, 27 Oct 2018 18:14:40 +0200 X-ME-IP: 90.76.61.156 Subject: Re: HEADS-UP: OpenSSL 1.1.1 in 12.0 To: freebsd-current@freebsd.org References: <20181009213425.GG61558@FreeBSD.org> From: David Marec Message-ID: Date: Sat, 27 Oct 2018 18:14:39 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181009213425.GG61558@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 27 Oct 2018 16:14:50 -0000 On 09/10/2018 23:34, Glen Barber wrote: > OpenSSL has been updated to version 1.1.1 as of r339270. > > It is important to rebuild third-party packages before running: > > # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > I just do a fresh install a FreeBSD-12 from http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/12.0-BETA2 It sounds that "pkg" shipped with 12-BETA-2 still use the old library: root@matarje:/usr/lib # ls -l libssl* -r--r--r-- 1 root wheel 4386406 Oct 26 03:08 libssl.a lrwxr-xr-x 1 root wheel 13 Oct 26 03:08 libssl.so -> libssl.so.111 -r--r--r-- 1 root wheel 604936 Oct 26 03:08 libssl.so.111 -r--r--r-- 1 root wheel 4493898 Oct 26 03:08 libssl_p.a root@matarje:/usr/lib # pkg upgrade ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg" root@matarje:/usr/lib # pkg-static upgrade Updating FreeBSD repository catalogue... pkg-static: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 pkg-static: error reading public key: error:00000000:lib(0):func(0):reason(0) pkg-static: No trusted certificate has been used to sign the repository repository FreeBSD has no meta file, using default settings Fetching packagesite.txz: 100% 6 MiB 2.1MB/s 00:03 pkg-static: error reading public key: error:00000000:lib(0):func(0):reason(0) pkg-static: No trusted certificate has been used to sign the repository Unable to update repository FreeBSD Error updating repositories! regards -- David Marec https://lapinbilly.eu/ From owner-freebsd-current@freebsd.org Sat Oct 27 16:27:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3207810C9DF9 for ; Sat, 27 Oct 2018 16:27:05 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA5E57083E; Sat, 27 Oct 2018 16:27:04 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 6C13AF8BD; Sat, 27 Oct 2018 16:27:04 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 27 Oct 2018 16:27:01 +0000 From: Glen Barber To: David Marec Cc: freebsd-current@freebsd.org Subject: Re: HEADS-UP: OpenSSL 1.1.1 in 12.0 Message-ID: <20181027162701.GK61572@FreeBSD.org> References: <20181009213425.GG61558@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="OOq1TgGhe8eTwFBO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-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: Sat, 27 Oct 2018 16:27:05 -0000 --OOq1TgGhe8eTwFBO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 27, 2018 at 06:14:39PM +0200, David Marec wrote: > On 09/10/2018 23:34, Glen Barber wrote: > > OpenSSL has been updated to version 1.1.1 as of r339270. > >=20 > > It is important to rebuild third-party packages before running: > >=20 > > # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > >=20 >=20 >=20 > I just do a fresh install a FreeBSD-12 from > http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/12.0-BETA2 >=20 > It sounds that "pkg" shipped with 12-BETA-2 still use the old library: >=20 > root@matarje:/usr/lib # ls -l libssl* > -r--r--r-- 1 root wheel 4386406 Oct 26 03:08 libssl.a > lrwxr-xr-x 1 root wheel 13 Oct 26 03:08 libssl.so -> libssl.so.111 > -r--r--r-- 1 root wheel 604936 Oct 26 03:08 libssl.so.111 > -r--r--r-- 1 root wheel 4493898 Oct 26 03:08 libssl_p.a > root@matarje:/usr/lib # pkg upgrade > ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg" >=20 >=20 > root@matarje:/usr/lib # pkg-static upgrade > Updating FreeBSD repository catalogue... > pkg-static: Repository FreeBSD load error: access repo > file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory > Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 > pkg-static: error reading public key: > error:00000000:lib(0):func(0):reason(0) > pkg-static: No trusted certificate has been used to sign the repository > repository FreeBSD has no meta file, using default settings > Fetching packagesite.txz: 100% 6 MiB 2.1MB/s 00:03 > pkg-static: error reading public key: > error:00000000:lib(0):func(0):reason(0) > pkg-static: No trusted certificate has been used to sign the repository > Unable to update repository FreeBSD > Error updating repositories! >=20 There was an issue with the pkg-static binary which is used to sign the package repository, which was fixed in pkg-1.10.5_5. However, the build jails did not get updated until after libssl.so and libcrypto.so were bumped from .9 to .111. Package builds are currently in progress (this will be noted in the upcoming BETA2 announcement text I am currently drafting). It will be about 48 hours, give or take, before binary packages from the repository at pkg.freebsd.org are updated. Glen --OOq1TgGhe8eTwFBO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvUkdEACgkQAxRYpUeP 4pP8tQ//eevP07bMw8z+JOpWdO68d5LzPTEMe2TWWMFPWjdcX322ekSyiYB8WsTq I0zLQWo4WnmXNto888HLyJo6Vfpwg2ZMTYXHBY/RZgrHECB9B95Qig419+5RkfUp 74M8sj+YxpyB4cHrjeOU4hvXL5hYxM8ZGpSkJcghR7tnF0vaSsMHjlu5PODZywHf d0BScs6gvZlwyXYkqypH9XCRKpSt2JnKxGNS191EShBZZCVhkLX0dHXmfHbuCSUg vZR0GhrwM226Bq/kPm9OFTpkx6RCe3pzEZ44Qu01RePQnYjos5YGrxeJtGWzXclI k0XjUHE39qqdUSGzxrsgsdQ6b49pk2BpG/T4zLTKGaN6bv65FPUtcV9Fh/ck6N3o SaLOUZNb43yAtu1O/58m4lZSGh4H5v9VEW0KQqZKggP6QFbLuHFTwPccFIecRw13 4j0EaSwo5IxgTxPXYk65KmrzubO9HqnUeoneblUfXtWs/CQUyiGfAV/wslmcWA0I UNEb3vEHIb9DXbkX0JwWcsKKwMYfPxglEcCtQeZR+gippa7cMTn/XT0JfJd29QRF tIaWlWlV4Fh8oQ5hF+l+QA2o5bT82ycHgcL6XOFzaDIuptFxTvq1Cxov0cfQcDUs qQRwHWsA5rjTTZEPl6A0z41lDGCacSBdTXRtBm3p0l0gNfEXX40= =WwsA -----END PGP SIGNATURE----- --OOq1TgGhe8eTwFBO-- From owner-freebsd-current@freebsd.org Sat Oct 27 16:35:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6549210CB38A for ; Sat, 27 Oct 2018 16:35:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A22A70F02 for ; Sat, 27 Oct 2018 16:35:02 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id ACB0027F2A for ; Sat, 27 Oct 2018 16:35:01 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f50.google.com with SMTP id p11-v6so3113261lfc.6 for ; Sat, 27 Oct 2018 09:35:01 -0700 (PDT) X-Gm-Message-State: AGRZ1gJ5wKICIrFKzVAFwbbj1x2GSQ+WPZ6fI/Wu7oc4672it3TMxfVQ gmy5twQs0IlorNycFaaM9CW//8dJRTPRLklNX1Q= X-Google-Smtp-Source: AJdET5fRcpi+tVSzvtZNhd9qroE2FBFm7xvegAt/JAEfN6fX4duTbOwnKXAm/H+dKDwTuqPzHCmyVN5EXHwg5TdvJlU= X-Received: by 2002:a19:6803:: with SMTP id d3-v6mr4882143lfc.45.1540658100169; Sat, 27 Oct 2018 09:35:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Sat, 27 Oct 2018 11:34:48 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 13-CURRENT lua loader complains dynamic libs not supported To: rebecca@bluestop.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, 27 Oct 2018 16:35:02 -0000 On Sat, Oct 27, 2018 at 10:49 AM Rebecca Cran wrote: > > When booting a recent 13-CURRENT installation, I=E2=80=99m seeing the fol= lowing: > > Startup error in /boot/lua/loader.lua: > LUA ERROR: /boot/lua/loader.lua:45: error loading module =E2=80=98local= =E2=80=99 from file =E2=80=98/usr/local/lib/lua/5.3/local.so=E2=80=99: > dynamic libraries not enabled: check your Lua installation. Hmm... something's definitely amiss here- there's no reason this should be munging through /usr/local/... at all- it's not in the LUA_PATH. I'd be interested in knowing if there's anything funky about your build or run setup- I have lua53 installed, but I don't seem to have any odd interactions. > I then have to load the zfs module manually. This should also not be a thing; try-include (loader.lua:45) is designed to use pcall, which should sandbox the actual inclusion and recover from failures more neatly. From owner-freebsd-current@freebsd.org Sat Oct 27 16:48:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBB7410CC12F for ; Sat, 27 Oct 2018 16:48:37 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2989F719A0 for ; Sat, 27 Oct 2018 16:48:36 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from [192.168.1.14] ([90.76.61.156]) by mwinf5d01 with ME id sgob1y00b3NFUbe03gobWL; Sat, 27 Oct 2018 18:48:35 +0200 X-ME-Helo: [192.168.1.14] X-ME-Date: Sat, 27 Oct 2018 18:48:35 +0200 X-ME-IP: 90.76.61.156 Subject: Re: HEADS-UP: OpenSSL 1.1.1 in 12.0 To: freebsd-current@freebsd.org References: <20181009213425.GG61558@FreeBSD.org> <20181027162701.GK61572@FreeBSD.org> From: David Marec Message-ID: <1b43dd07-f52a-d4bc-8785-64c33dc09ed8@davenulle.org> Date: Sat, 27 Oct 2018 18:48:35 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181027162701.GK61572@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 27 Oct 2018 16:48:38 -0000 On 27/10/2018 18:27, Glen Barber wrote: > > Package builds are currently in progress (this will be noted in the > upcoming BETA2 announcement text I am currently drafting). It will be > about 48 hours, give or take, before binary packages from the repository > at pkg.freebsd.org are updated. Thanks, I missed the fact that there was no announcement yet for this release. Regards, -- David Marec https://lapinbilly.eu/ From owner-freebsd-current@freebsd.org Sat Oct 27 17:03:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24E9310CC8BD; Sat, 27 Oct 2018 17:03:51 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB70D72395; Sat, 27 Oct 2018 17:03:50 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 4D08110378; Sat, 27 Oct 2018 17:03:50 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 27 Oct 2018 17:03:48 +0000 From: Glen Barber To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181027170348.GN61572@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed User-Agent: Mutt/1.10.1 (2018-07-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: Sat, 27 Oct 2018 17:03:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The second BETA build of the 12.0-RELEASE release cycle is now available. Please see the "SPECIAL NOTE" below regarding upgrading from FreeBSD 10.x and 11.x for important information regarding geli(4)-backed filesystems. Also note, pkg(8) builds for consumers of pre-built packages from pkg.freebsd.org are currently in progress, and are expected to be completed roughly within the next 48 hours or so. The status of the package builds for 12.0 can be monitored at: amd64: https://pkg-status.freebsd.org/builds/default:default:120amd64:483081:beefy6 i386: https://pkg-status.freebsd.org/builds/default:default:120i386:483081:beefy5 Installation images are available for: o 12.0-BETA2 amd64 GENERIC o 12.0-BETA2 i386 GENERIC o 12.0-BETA2 powerpc GENERIC o 12.0-BETA2 powerpc64 GENERIC64 o 12.0-BETA2 powerpcspe MPC85XXSPE o 12.0-BETA2 sparc64 GENERIC o 12.0-BETA2 armv6 RPI-B o 12.0-BETA2 armv7 BANANAPI o 12.0-BETA2 armv7 BEAGLEBONE o 12.0-BETA2 armv7 CUBIEBOARD o 12.0-BETA2 armv7 CUBIEBOARD2 o 12.0-BETA2 armv7 CUBOX-HUMMINGBOARD o 12.0-BETA2 armv7 RPI2 o 12.0-BETA2 armv7 PANDABOARD o 12.0-BETA2 armv7 WANDBOARD o 12.0-BETA2 armv7 GENERICSD o 12.0-BETA2 aarch64 GENERIC o 12.0-BETA2 aarch64 RPI3 o 12.0-BETA2 aarch64 PINE64 o 12.0-BETA2 aarch64 PINE64-LTS Note regarding arm SD card images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.0/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "stable/12" branch. A summary of changes since 12.0-BETA1 includes: o A debug option during binary compilation which was missed when branching stable/12 had been turned off. o The gif_interfaces rc.conf(5) variable had been restored. (PR 204700) o The timezone database files have been updated to version 2018f. o The debug.witness.trace entry in sysctl.conf(5) on installation media had been removed. o A system panic triggered by a combination of lagg(4) and vlan(4) had been fixed. (PR 227654) o The ability to prevent interrupting the boot process without entering the password in loader.conf(5) had been fixed. (PR 207069) o Several drivers originally targeted for removal in 12.0-RELEASE had been removed from the GENERIC kernel configuration on amd64 and i386. o An off-by-one error that could lead to a system panic with the sound(4) driver had been fixed. o The mlx5(4) driver had been updated to notify when a port on ConnectX-6 network cards had been turned off due to insufficient power. o The filter_reloc() function in objcopy(1) had been restored, which fixes building GCC. o The shared library version of OpenSSL in the base system had been increased from '9' to '111' in order to prevent shared library version collisions with OpenSSL installed via pkg(8) or the Ports Collection. o Updates to the Linux compatibility layer. o The ae(4), bm(4), cs(4), de(4), dme(4), ed(4), ep(4), ex(4), fe(4), pcn(4), sf(4), sn(4), tl(4), tx(4), txp(4), vx(4), wb(4), and xe(4) drivers have been deprecated. Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 12.0-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/12.0-BETA2/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: ap-south-1 region: ami-0583e82d9f9b02835 eu-west-3 region: ami-044ce5b3fd2843a38 eu-west-2 region: ami-086a9877c239380f5 eu-west-1 region: ami-0b1ca64572a572ce9 ap-northeast-2 region: ami-02c873fbf77df6121 ap-northeast-1 region: ami-0286bd92d79a033a5 sa-east-1 region: ami-0ac69a7ca63c716de ca-central-1 region: ami-0b438a859e4c53d2d ap-southeast-1 region: ami-07354987a154b009d ap-southeast-2 region: ami-0a92d4f626a93b504 eu-central-1 region: ami-02de1425eea91f842 us-east-1 region: ami-09d9338f8864dfc2b us-east-2 region: ami-00996ecb76c9f185e us-west-1 region: ami-00ca4c4ad84830c4d us-west-2 region: ami-08b7e86ee097b8a62 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-12.0-BETA2 % vagrant up === Upgrading === === SPECIAL NOTE === This only affects systems that employ geli(4)-backed encrypted filesystems and currently running 11.x or 10.x. Upgrades from 12.0-BETA1, either via source-based upgrades or binary patches via freebsd-update(8), are unaffected. An issue affecting backwards compatibility with geli(4)-backed filesystems and an updated geli(8) binary after r332361 prevents mounting encrypted filesystems with an older geli(8) binary from 11.x and 10.x. For example, if /usr/src and /usr/obj are mount points on an encrypted filesystem, the geli(8) binary that exists from 11.x or 10.x after rebooting the system after 'installworld' will fail to attach the encrypted filesystems when performing a source-based upgrade following the documented upgrade path in UPDATING. For binary upgrades using freebsd-update(8) from 11.x and 10.x, the recommended upgrade flow is to install the kernel patches, reboot, install the userland patches, reboot, remove old libraries after rebuilding third-party software. In this case, the initial reboot after the kernel patches are applied can cause the same scenario where the old geli(8) binary cannot attach the geli(4)-backed filesystem. A fix had been committed to head as r339804, and is expected to be included in BETA3. For those without remote console access and do not wish to upgrade via sources, it is advised to wait for BETA3 to upgrade from 11.x and 10.x. === END SPECIAL NOTE === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 12.0-BETA2 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 11.x. Alternatively, the user can install misc/compat11x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 12.0-BETA2 amd64 GENERIC: SHA512 (FreeBSD-12.0-BETA2-amd64-bootonly.iso) = 7049f1f36ca0c5d75b2e4d7b7a6737952e11c3ed8f03398abe079e3cae1cfd9076534e555c6206d2c2db1bd84f7d55abf2e9033a47f5dd3dfc1dd9543c7fba6d SHA512 (FreeBSD-12.0-BETA2-amd64-bootonly.iso.xz) = c8144f7bf9e77ffe41ce54b39318511fd78b3a3b0aed6f6035d4f1b982b4fbc3736465afa3db4f190ff772f4e2dd5d009cfcec0e047a2419ddec8ddd7c329d9e SHA512 (FreeBSD-12.0-BETA2-amd64-disc1.iso) = d5f933c0ee8b0f5275055bf8dd5f637c0c5475f7fb1965fb61c7ab8dcd69a8953721d584b2345f78ece85be23f6ad820d701cbbfc7f83eb5cf24d81cf92707e9 SHA512 (FreeBSD-12.0-BETA2-amd64-disc1.iso.xz) = 7fa0315b686e852a81330c5c043d7b75344d7a46c79fd4103cb20b27ea6ec02cb5698acf51378801f8ea67e3faf6880b283d070e9d9171a1bc90a1c25dc0b822 SHA512 (FreeBSD-12.0-BETA2-amd64-dvd1.iso) = 73910edb5920086e0651835a779327cdc859441713f8079d8ec1740fb3b3325c0e4bb91594683215301e9f6520df3cc40837bd40205800cd26e8fab6e8aa91f9 SHA512 (FreeBSD-12.0-BETA2-amd64-dvd1.iso.xz) = c59ee0898fda9250cdb42d34cf58cf97819269e624554f8224b249e6616887e4a31b0d73396cc4085f8326acf173c62ac532ad9da9d7992ee76301224fe0bf16 SHA512 (FreeBSD-12.0-BETA2-amd64-memstick.img) = c530e8aec8d3576873f1c8c49e148ced81323b664c77b32c70e74caadff352f469189497b771c7c72d301c9323206f4d8efe3b718add03d05bbab540ac2e598c SHA512 (FreeBSD-12.0-BETA2-amd64-memstick.img.xz) = 467985f4c9e68ce4524150607946296e798521fdd96417146449fbec7d500ed07a04d9d2ade1503f687389aa8526f483fcd09ebbb9d60dd8b2088a8a62593089 SHA512 (FreeBSD-12.0-BETA2-amd64-mini-memstick.img) = d7b87c89914a03a299112b9433813391158ef8717e80acd43ee2d68fc86ecfffdd1337f6adce319474ea1bb7072dedeed4a4f292b7e8a6664628f17f7c61d40b SHA512 (FreeBSD-12.0-BETA2-amd64-mini-memstick.img.xz) = 163d8cca4364c1a079513ce7109782df257566f2ed18a4560b2ccc3f8f4545f7c939e162415fcd5cd4446279a7f91a2b2bb25ef5299734e3dbd5074f70a0eab3 SHA256 (FreeBSD-12.0-BETA2-amd64-bootonly.iso) = 4cdf796166976f69fe8ad1dbab8809aed3c39ac67b6aa5a098546bd8ee648d24 SHA256 (FreeBSD-12.0-BETA2-amd64-bootonly.iso.xz) = 37961d9e36823d277967b36a41f71eb22b5b48aa7f522f6e0fcf9cfd05690f55 SHA256 (FreeBSD-12.0-BETA2-amd64-disc1.iso) = 783013e07a49dd1e52c71a6be38715068b62ba86c9b603f514aed3445184a3d9 SHA256 (FreeBSD-12.0-BETA2-amd64-disc1.iso.xz) = 6d7d903368acc786166a2fc311155346aabdfbc16e2fcf5b9b12ebf99cccd9ef SHA256 (FreeBSD-12.0-BETA2-amd64-dvd1.iso) = e975916fa7524e56287536196c1398871bec29b78fe21d17239cd89fad55b4f4 SHA256 (FreeBSD-12.0-BETA2-amd64-dvd1.iso.xz) = acec0829d75d3f40c7d0283cb07e0374dfeb34bd6e219f7ad9c54afe233ed35c SHA256 (FreeBSD-12.0-BETA2-amd64-memstick.img) = a52547bc527b109b4291e75fb3c41642b8497e3af6269dc583973eadbc57d46d SHA256 (FreeBSD-12.0-BETA2-amd64-memstick.img.xz) = 69b9b8186e8b07e27f0980d8273baa94f8d78f51b3389bd327673dca06b816f7 SHA256 (FreeBSD-12.0-BETA2-amd64-mini-memstick.img) = cfba4be1c0bced50b65f55432b8f858a63553b40b392ba3b627c12e002ed4536 SHA256 (FreeBSD-12.0-BETA2-amd64-mini-memstick.img.xz) = a542f1a1de60e10b7d42e8659796e3e530d1e386e8ae8493b07c6740a6a3ab5a o 12.0-BETA2 i386 GENERIC: SHA512 (FreeBSD-12.0-BETA2-i386-bootonly.iso) = 4e1a1d94280569a52eac77b2bb9b71920dfa5c30f203f4890f36b040e646f98c1b8e8ed092b05146ea92e9ee5e807be3b68b425037ef8c993f42ae2543da1e46 SHA512 (FreeBSD-12.0-BETA2-i386-bootonly.iso.xz) = 0295d61be8f8be66f1ceca60d35eca5e7a24263ed98023b290dc8e28469397abfa5712ba1e5e2acdb63bfeb025c6238c235cbe7bdc99d785afa24a41872ec099 SHA512 (FreeBSD-12.0-BETA2-i386-disc1.iso) = ae00ad58df05bf137872a0a4d7273088898aca5dc1efc3b19de14594bac2f56c9a33aad1dd20d674ead2cc79aa8c9f4e5f1cf91dc4c809abe98f6d3f647d01e1 SHA512 (FreeBSD-12.0-BETA2-i386-disc1.iso.xz) = d4a8e862419083b72113eaa9ccdf5935472bd0484277efa11b80322702e85506e6f3eed9dcc17168c5486a6ef58eb126443eafde579d60e2dbfee3a22a048d5f SHA512 (FreeBSD-12.0-BETA2-i386-dvd1.iso) = 96a63e831e1a4a133e0bad7d1f05cb62ac87a0f968a9f2faaf9c2dc189923445e0564f780980473e59ea150545c9bc8d5ba032984deddd7364af48712318c9f9 SHA512 (FreeBSD-12.0-BETA2-i386-dvd1.iso.xz) = 697a391e9be31cd68043a13d9b984f628c6aa9a5cb57de8a12908dc2ded6a72532e64c50e08563a059323c5c6783a8b88f5f110280309bbbcaf6fe3d3c60e611 SHA512 (FreeBSD-12.0-BETA2-i386-memstick.img) = 23bebfee595475234d1da16456b151a481f231f8a2b2d586bd2fc21ca54b262439144f129adf0de8c1359ffd096b78113e8feb5fd4ce5c9c35d77bf62cd185c4 SHA512 (FreeBSD-12.0-BETA2-i386-memstick.img.xz) = 4c314a77f70d2ae6aa5ce169ae2384c8985fbdfdae086a198eb386d0f07a6d162e2c3d9ce6e279625e71c665db10b1229e13280e8d1e1d93339cc60cf556ef76 SHA512 (FreeBSD-12.0-BETA2-i386-mini-memstick.img) = ada9820d9a1ed4c5d822a18e1ffd07b847f13bb703b601a436ba0519867d2641ad4fb41527f44e48646559ece2b51a0c7cebaec94845ff9966f330b21cc49d11 SHA512 (FreeBSD-12.0-BETA2-i386-mini-memstick.img.xz) = 65074b9a0616c96a1706b0e742db40fc736212f5e0e6ae76c45b06b809b2a78a2286cee0811c48562fbbbfd2439a7f4ddb0dc46d7348da49ecfe90e73d4a9b30 SHA256 (FreeBSD-12.0-BETA2-i386-bootonly.iso) = 1e20fd137f4e72f18faa731e01d7ce35e0959a917e83d077fe6df22d619d4426 SHA256 (FreeBSD-12.0-BETA2-i386-bootonly.iso.xz) = c93430b38fbece7fd8c9b52f2c0a2fcd9039b28dbb80fa54d63088cc77c9e2c7 SHA256 (FreeBSD-12.0-BETA2-i386-disc1.iso) = ac682be4dedb1f64a1dc43560ac5d7589f199591d5e80f21f3dfad207ddebd77 SHA256 (FreeBSD-12.0-BETA2-i386-disc1.iso.xz) = 631685fa219b19ec1d6565ee4c958523791d4df89b31091f9582185f52350d15 SHA256 (FreeBSD-12.0-BETA2-i386-dvd1.iso) = bae0b0d014238666b4ee0c45a9acd3d87d656eda6b8b98565ccac553fc062800 SHA256 (FreeBSD-12.0-BETA2-i386-dvd1.iso.xz) = f9e1da032658def2093ae1bdcf2ca4b54e1d546661d273d5d9a53f4e80e8ae11 SHA256 (FreeBSD-12.0-BETA2-i386-memstick.img) = 9289a1adcbb663b902cd302a730b8e8fa6343bdd0a62e9233cca1ac5f9fba7e9 SHA256 (FreeBSD-12.0-BETA2-i386-memstick.img.xz) = a3638be972a95cebd2fb822ea4487251d69e4cb031ef7b952e3d209cde5a601b SHA256 (FreeBSD-12.0-BETA2-i386-mini-memstick.img) = 16d5e5cf2d652d681fb01e626af4257bf9c1a0921d9000a499a636323b48146b SHA256 (FreeBSD-12.0-BETA2-i386-mini-memstick.img.xz) = a74f9464492edcff2268d17fa6fab47c2425c2c4e6950ff974acac85d1ca5b9a o 12.0-BETA2 powerpc GENERIC: SHA512 (FreeBSD-12.0-BETA2-powerpc-bootonly.iso) = 391b14d0e529538cac0fc065a560f7f69faf90672c5acff3d64003f1367e0768d8e60a1380dff13a0029a2304f4d16a2d008b4308a4d4485ec9cc8ee0ee5a90d SHA512 (FreeBSD-12.0-BETA2-powerpc-bootonly.iso.xz) = c7bd4b6e7425afc9f471bf2f6a99dfd16f25d66ab1704b3dbe96e22f818845a3dde8b4d5c79cc01bfa241bdc1ac249496de5df55114465dec5bcb49b66aab632 SHA512 (FreeBSD-12.0-BETA2-powerpc-disc1.iso) = 1cfbd7fe856b290e44f3e56a2b93292a8bf5b2cd8e151612785156b14cdbdba2400bc16aa557ba8a49a78cd390c8d1565636602e7ecfbb8cdc4ee5881665bf11 SHA512 (FreeBSD-12.0-BETA2-powerpc-disc1.iso.xz) = e95095ba7d09b6011daaf3d568f8240118a0cf2e1d806c9c83d836a2c8a9adbc5f7e13d39d415d173024c98083274f40d230e421ad9d85dce349910f3978626a SHA512 (FreeBSD-12.0-BETA2-powerpc-dvd1.iso) = b8d3c4bb97571894b4b19c44716c07df03134a81c59a7a9888e1e875999f39e57ccd42449583370c2f12163cb0b9d44f902270528920226b675cf168a1b56b00 SHA512 (FreeBSD-12.0-BETA2-powerpc-dvd1.iso.xz) = b2ba366ce704806696aa4a44696822bf6ae051ad05fbca5cc3850421bafec5e4be639444ef5e53ecfd5ba4108b3b707f099f78605d4d739b0000541935805b7f SHA512 (FreeBSD-12.0-BETA2-powerpc-memstick.img) = 8fcfdc38f219f985a0f26562f241f2c069d398c20747b72b6d30493f45b5b1c0dab8ffd992c06e70faf139fefec4dac7f6a457a8498f94005018739fb15129b6 SHA512 (FreeBSD-12.0-BETA2-powerpc-memstick.img.xz) = 2daea4ca33969a830c655aebc2b7586e159092fe2f6ac9412f6a9cb2687fa149281a82a95d02e3f2dcacb42bf7d328a652c0be59765463c6ec35a7073e33745a SHA512 (FreeBSD-12.0-BETA2-powerpc-mini-memstick.img) = a0d5a6f6ac54de97f2bb87d558ae4263ec967d8fa914c621baa971264acd3f35947cd5f4bad9f8b8dc83331646d51d7cfdedef69a83f1d8894f1b7e830dfa12f SHA512 (FreeBSD-12.0-BETA2-powerpc-mini-memstick.img.xz) = 2b75e5cc26438f3b3edcebdd3e39cb9f0a15b640d2df2849279f19797f6a030a4b911c0fe4b940bc2acec335444a15e5255cfacc5326609060e98d480d2d8afc SHA256 (FreeBSD-12.0-BETA2-powerpc-bootonly.iso) = 2fc1a9fe0f5628424a0d60fbfe01ec5087906286753668abe0d76cdb5700686d SHA256 (FreeBSD-12.0-BETA2-powerpc-bootonly.iso.xz) = d5b4ed3f172907aa261159e645423b200c226776445975004bfcba9fbfb0d204 SHA256 (FreeBSD-12.0-BETA2-powerpc-disc1.iso) = 5573fe67afe90fd24159753f2e97525ac31106449894b24fc72f0daec01d00bc SHA256 (FreeBSD-12.0-BETA2-powerpc-disc1.iso.xz) = 02eab2f4450d11e7c4348a0923b371abb314b45abf34793d805670b7f838ed10 SHA256 (FreeBSD-12.0-BETA2-powerpc-dvd1.iso) = f3635703e1e8401030d5bee6a4b698fd64f4805a7b4bff73cd9162a827eb1d83 SHA256 (FreeBSD-12.0-BETA2-powerpc-dvd1.iso.xz) = d20483cb3dc169d8b803d227ae9886d5ae8784173cf8889d9381ea8c169627b6 SHA256 (FreeBSD-12.0-BETA2-powerpc-memstick.img) = f8931aa9e369cbc3679fb0d47925934997ca37d7d7c3f18a124d7653a69787c0 SHA256 (FreeBSD-12.0-BETA2-powerpc-memstick.img.xz) = 7f71587aaa1aad1777aac4faeda586defe2ae4687b8dd9bd5c77702a9b065a84 SHA256 (FreeBSD-12.0-BETA2-powerpc-mini-memstick.img) = ba74664527a78b0c81c3232b766d55b74e59432fa6634789a0867fcc34013985 SHA256 (FreeBSD-12.0-BETA2-powerpc-mini-memstick.img.xz) = b4fa68d8fe3a970eb5ae54a2a0d31537b17cc5d1149e1da524688e6cf7d3e4e1 o 12.0-BETA2 powerpc64 GENERIC64: SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-bootonly.iso) = 9230d68b87aeb1537e60a85c97bb7b9afcdb568b9f1da93c9336117b127339a5fef1a93c1bf81bbe15577ccfb51d7eccdeeb63f43c0663f772faa2fe02aa45fd SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-bootonly.iso.xz) = 9c68f14e44e34e1bfa13b88de5f3ccb3c1f63619bee7aa80644739a74b961f1ce119c417d7d60ebd787045e783e885f67199e5d9f7c8b15435af7bf239748363 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-disc1.iso) = cb86c89407d2d28b6d8542701e63567a7122010c1577bf79e3c43a198f2b11b008aad1f341d1c01347640d2dbb8752cf1f4a38301bc68d761106148e52629182 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-disc1.iso.xz) = b80a2b3f2b7d16148df6b418fe4139eefe028eed4a6b9159e20570433468a6f956fc634a7043df5335dccca754d125603be3034787af793126b9c8ae37d276b2 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-dvd1.iso) = da25903597615dde23b2e85c9d5e4e854df121bc8b1635034357c5aaa49b5398529a2eb790d0f05a7ab51e577c4e89c013c847d7287a7a479dac81d6a44b534a SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-dvd1.iso.xz) = d5b48958308aac9c1c1d0ed8d5f1cbe95c9534625429045d71abd947e3c1e228ca057e3aaf6319fa5d16291062386fd02d37bddabda192fe05aab2defeb6f180 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-memstick.img) = ad6806f0eb9a5d18f88693a9ee8fb94bbda5ced5a58dc2773e89f0be9a17ac96b283c290e1e7c5dd11869994efe5bc83151c92fc72dd2f14a7c928d0631063cd SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-memstick.img.xz) = 619d330a614614f71c61c57a36520c8920173204b48071875d8c224c27ff515506468f740158593c36dccebf8bdc852b4e414bdc7ec7f671df9fc58decff915e SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-mini-memstick.img) = 38e7067636dcef434a05c901545a1d830dc631a5cfbb84c0e358d82471f7a4c20867734e26ff2683022f096899ee2f22914bbf2385ac2ad84e9c0095c5ef7484 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = 5d06db66ac5a65b8e1ff308a3580e5d6cca98e8bafda29f0c992655b26d4c2d4a1aa9d635bebc360258842f861411dc3328cae2a690d4d9a1c5d19456e06cdb4 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-bootonly.iso) = e55d91b1519de522ccd83c88e03a8443c9a1cd07007a538670900d214c8be903 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-bootonly.iso.xz) = 7c15ede01b92c34fd36b7159bbecfce4bb0493f4c91106acfe196a9ae4f4bf9e SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-disc1.iso) = eb0c776827139bdc6c9322d3a4b9cd3919a40e0ff91be2ae53f6a18356c35485 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-disc1.iso.xz) = d00b67b4c6ca6c5b0eb21be5bef93aec385235df2ff1f8b52eb51d940da2beee SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-dvd1.iso) = 11cbd2c6d4ca588122eee63aae1eae519abef7ec171e33c05518674d5a7dd701 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-dvd1.iso.xz) = ce2afa03d4a2fe1b175e27d1d22fd124439f9cd80ae0c6fadb25e7677f035b30 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-memstick.img) = e631d50a4c8c8ca35f8d2d6fb5f64172ff71c52fbd23377eee20618a029c6f8f SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-memstick.img.xz) = 83374921b1b16f96f199ca4940bbc1695e75013e838dab01de10fbaa4befd475 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-mini-memstick.img) = 1b94fca0f51f6565605fd6e5fdf6649fab0081054ebe6f547a2b88194e29f78c SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = 531259a9b791e3f741d377179bd4dcae9d652586676ba595006e15e20d86a002 o 12.0-BETA2 powerpcspe MPC85XXSPE: SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-bootonly.iso) = 072d9e5a3fd9e3c85368ef7fc5bf6a1f8669ab47053dfbe7e6261c1db7c95b968a99e0e841e87fb143fc91d54d96a1d0e56eae1976c1bc820fc318aabe543fd9 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-bootonly.iso.xz) = 332b61ed7ae009a90a007b092c9412ae3887237e572e30961994f012db69b222df90fa1528a0a091d653b2dbd1c53027adb05d4c9ae266934b05ec0af57346ee SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-disc1.iso) = e1fd6598468d1147b395eab809c78f85d1457faea8af09b60d896cedf8029ab753a9bf9e8569ec2a709c29d67ddb64d45377384c500f3b2e318f582145ceca5e SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-disc1.iso.xz) = 27b6d6ba66138b8741666ceda4c7b1f873164ba7534f4a2bb39d99f8abba7d63af5f9f7575db4c63015a813bc5748fc38c2d80b38218bb4c4450a29d7ed124b8 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-dvd1.iso) = ff66e9c77eb0b19c9dbc53b60da0ad99f320f12684572cd9dbb037d9c3e601f4b050a9422d93811263d75bf49c6491fa2945f4e4fbdd5e60a92ace086fd681e0 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-dvd1.iso.xz) = 21c690dedc4aa9dec0deec45860694c11e7f1b13bb24ba9fcf4f64c6b03dc608fc32d0bafe4598ed4523ac1293b8761062b25b0a0440c3282a8721cc7082b320 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-memstick.img) = d5de7bed2b600347d6fe79c61f811129332e08aa06ab5cb9239966615c32bf806d8adff55a0dd0ebb6e3a335c8bb5ac2adf096279f0c411ba9a25e9fa8c409d4 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-memstick.img.xz) = d4fed456257cd0053f5e2e0069962cc8dcf823d15b53486b493e6b0e15dac1b8738bfb903308b9e14df2310ce29517cc70efff0e1d3476fa7fb5926c3f5410c3 SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-mini-memstick.img) = f6c343a8669977478487d778f1362e027c60aa40457343cc2385f70e73570cb03c3c33058a24953cc50fabfa23507cd73701ede322034b14aecacdb9bb70c61b SHA512 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-mini-memstick.img.xz) = 8f953fccb34d151928f06ab350e11a641dae2776419ade2f52315af62f81ec8449f77c3700261f7244c1cea6b3413b1cf240a32e0254b6ea1590ac0a2949e7c0 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-bootonly.iso) = d19c08e4578456e00f077e2dc0390819264707c747eddc6b58fd131eff83a956 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-bootonly.iso.xz) = 5a4d7c358602031da7614521d749dc04be7cefee122c261ee30772ceefd4f96b SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-disc1.iso) = e922ef7c0c79c498baee09c4073ff933b60f278263f60b1fbcae530dc4d5031a SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-disc1.iso.xz) = 68c7f51da4f637583efe976eed15641d9bd19cf934a8907108da8849ffd39ce9 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-dvd1.iso) = 6a0f7fde3cbd9f38f30b61b6ea72484e27b7573258fe3b399b00dbc7be326011 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-dvd1.iso.xz) = 3333122e1727d31b09c5bfcb8bcc86e498df1e1cadfa0f2e2e59b9ce376a2af1 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-memstick.img) = 5fd1ff68f02d5d3886f560d76b0486358b408ea73681c1fcb30387be53099765 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-memstick.img.xz) = e5f9fb1c7aaca16fc9188d6e8154ad01f09dea888364930eec4a3497aed6a25a SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-mini-memstick.img) = 49b02b39b24793925a7a42193791e335540cb6a2980affc96a3c46d854825016 SHA256 (FreeBSD-12.0-BETA2-powerpc-powerpcspe-mini-memstick.img.xz) = 26a9b4b75c2e724d01fa4622e430eb98cd266848ec9b4a42a8c38f8819c80b1e o 12.0-BETA2 sparc64 GENERIC: SHA512 (FreeBSD-12.0-BETA2-sparc64-bootonly.iso) = 07a6288686de08bc82a566d2788a80bac266d5b659a5bace400e31048871cf483135e397a574ef495a634725b867f0dafea597ed3a1885d257839305481540e8 SHA512 (FreeBSD-12.0-BETA2-sparc64-bootonly.iso.xz) = 315e29b1754359220cb5ff3106a5292d4198cc1a13c3c9b62e8b36730f83aba428a505b68a6ad99133ebf1d798809ce5b7439c787987210b52d0b1d54b97b39a SHA512 (FreeBSD-12.0-BETA2-sparc64-disc1.iso) = 7784ffd1b53d9d7177b2fb1e42c5a1883b3cdc62634230b7950ad35a57c6f37dc972e37d8e035704653a32609b37928d5a41bd0c00847e56860bc36e11e282f2 SHA512 (FreeBSD-12.0-BETA2-sparc64-disc1.iso.xz) = 048e5b90e782f6df5546ebeae6a41f17df682e237bb91a5e6613ab0558680e12c4a2d61cccec4c8996d4b5eb7f7aa4690943758b8344aecad96a4cc5c2d34e7c SHA512 (FreeBSD-12.0-BETA2-sparc64-dvd1.iso) = 026efcfe8b44045a8398bc7d53ec9de3e4bf2a08b4949a7f6f7050ff84488ff06e12aec708d123074b1136a70c038a01133a7cc03942268737030c35ca801fe5 SHA512 (FreeBSD-12.0-BETA2-sparc64-dvd1.iso.xz) = 430a89a9c8329f22f346b3086bff653bc7ac4b511bb5ee6d236ad5ecc8497ea56288357000849baddbdd153c6e81e36a85c60db2460a1d50335038996050742b SHA256 (FreeBSD-12.0-BETA2-sparc64-bootonly.iso) = 1df4fbb1d41b8830d9e072b6ff9e526d3f0613415747e3d0c537daa67b4a923e SHA256 (FreeBSD-12.0-BETA2-sparc64-bootonly.iso.xz) = 009f1f400ba60046739787b84f19ca054036638605ebc6742d25762612fbc633 SHA256 (FreeBSD-12.0-BETA2-sparc64-disc1.iso) = ad7238f0aa39714d99a8e0db2286a4f71017c217b22ec91932a0a1b57d807275 SHA256 (FreeBSD-12.0-BETA2-sparc64-disc1.iso.xz) = d54cde882e7be35e3c4beb08bf058992ab2ce8d9aab4b3d82f2a1228ff075672 SHA256 (FreeBSD-12.0-BETA2-sparc64-dvd1.iso) = c5e0f8f6843f8989165059b7c58341e2e6f6f626311d3a76fbba9b78491207de SHA256 (FreeBSD-12.0-BETA2-sparc64-dvd1.iso.xz) = cad649d008855094a7015a7c91492e147ae3c12de4b1a9b3cae856b707ec33a4 o 12.0-BETA2 armv6 RPI-B: SHA512 (FreeBSD-12.0-BETA2-arm-armv6-RPI-B.img.xz) = 5ff1542b02494b542221e367aa51de79481f6424af571c0afe9d1d6e065043628e5f21365e337a57b2a69c9b20d053866c54439e7cf10a35f7e6d21d7698bda6 SHA256 (FreeBSD-12.0-BETA2-arm-armv6-RPI-B.img.xz) = 2fe7d2050e458b3060799562001cb3051eaac219727c9939faaa4f1c6e332f8e o 12.0-BETA2 armv7 BANANAPI: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-BANANAPI.img.xz) = 470d68331b0a381cb89102ae8d2f6bd75ccce62271b4a5adfe94ed429d1f6b804480258a2df86ed505b21dbd2c484a61342d53631a487de3f4bbd96ac4216081 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-BANANAPI.img.xz) = 5c3d6646636e56a14879bfc04c475a1479874f654e4de4f0c7b560c7c19c6470 o 12.0-BETA2 armv7 BEAGLEBONE: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-BEAGLEBONE.img.xz) = 4184beb7b5fcd8ecd9b5f113d1650aae2fa62c898b7a824bf9651a6a4ca06bc24b49dbd2415711b861677227815b521298272ee565f87c793f381cbe66531543 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-BEAGLEBONE.img.xz) = fd220d37a0a59cc2aef263f17fb4e4126ab7f10c5957431597d667b267fc5f21 o 12.0-BETA2 armv7 CUBIEBOARD: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-CUBIEBOARD.img.xz) = 0eaa8e4c001077631edc3894e4f4a337e868b16ddbef66601066e1d6e5ae0c9284d0875192e006f370d0a6ac657e0841deeb7459988888b559f82052dc256018 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-CUBIEBOARD.img.xz) = 620d31eafb1ed2f320406fc7914907638a1331c3395a0bae1fb42fd134445db4 o 12.0-BETA2 armv7 CUBIEBOARD2: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-CUBIEBOARD2.img.xz) = 01fb57a3e03416ae6a0ffff502bcd7e131e231e37fe503515dac78ff0a6f5739b72636a6dd90b060fddd1694e3b4177b93b76d1362b93cf0424f888d483cfd4d SHA256 (FreeBSD-12.0-BETA2-arm-armv7-CUBIEBOARD2.img.xz) = 64b6c5be10afda00676fece9276231e41efc37ff1de82b3fb634a02b665094ab o 12.0-BETA2 armv7 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 86ab1dc6136984109051a8bf5094ca49b23f2c57beb48647b5dfcb5d2ba0af77f7dda11e22c8fcc6e1640d4edb3f7e266939f4356349057ba393632a14d605d0 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 6d95c51718febc73b97eb57e8987b21729c81fdc323399de666c984bde098e38 o 12.0-BETA2 armv7 RPI2: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-RPI2.img.xz) = e75efe957a84ca8b58441784f9bde8b0efb8e8d60672f6654252267b0dd5dffb17d2c16ccb81aff494e862b89fda6ed82a8e467c5f9b5cb81b4f3acaac6d727b SHA256 (FreeBSD-12.0-BETA2-arm-armv7-RPI2.img.xz) = ecbdee268dfa184cff20d5cad8f92d88a989a74df7aee34054e52287ec54bc8a o 12.0-BETA2 armv7 PANDABOARD: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-PANDABOARD.img.xz) = d1c34d8fb034500dcc809a626bf99213eb6f5fb4c7ef3bd1e92a86d0ee957da6f70b660193c2659f45ec653fb79da91088f590a4591d1c1af4b9a50586ef67d5 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-PANDABOARD.img.xz) = a87f4da81fda05a1a95821a92180c5a7ada7331cad55c68c19da9ce495e66ff6 o 12.0-BETA2 armv7 WANDBOARD: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-WANDBOARD.img.xz) = b6d17c62c889be8789631b9dcb9557311aa55a033ba81b9a7c6142df7c0addfce5cb8e60aae32ed455d49bd9400b96fd2e8ae75a2c3a19194db066a8806fb394 SHA256 (FreeBSD-12.0-BETA2-arm-armv7-WANDBOARD.img.xz) = 7fced8f9660593c94b089468e1a39d985b6573294a0529d0befaa7aed44eea27 o 12.0-BETA2 armv7 GENERICSD: SHA512 (FreeBSD-12.0-BETA2-arm-armv7-GENERICSD.img.xz) = cd741fcdeb84a6f286c2068c025baca9202b0d4def07471bb28b90c17a70f4e576925eb0382bd72a34b8442592054f840de8ba62b2c5c209347033675beb0a5d SHA256 (FreeBSD-12.0-BETA2-arm-armv7-GENERICSD.img.xz) = 1341712cebbe2f6de5d53cc7be8f19f00e9d93cc68b4f1113d74b0c6f5e8b094 o 12.0-BETA2 aarch64 GENERIC: SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-memstick.img) = 3b48f703bbb7021c4e81aa8e9557327466210329c99542651d417cf6a736159f6821d2d4ff496b85315a18b27fa5b0ef941bba2596d76cbf4a0395f9a6c3b375 SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-memstick.img.xz) = ae73677cedafbcd34ee15d77731959c66e41c36ed8bd540cb11783ed050c8ec97ffac8f6ca66593e672352280a370b3db5817d95f322ab0ab536c9cd78d8534e SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-mini-memstick.img) = 1040b00f4f51f7bf31509e17c8d71d557136e224f8df26752354548eb579b957c8dab7e33afa5db31efa2a0ed941052d36b0840fdc03dfc56e5c4813b1877d53 SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-mini-memstick.img.xz) = d1fa9b34069196d1ee8e7bf586c54a96f11311f48812bf6cbbf8b70d362d06f0183e735ea09a577189c87e48624b6891b5ae76dbf3fd8f9bf7b617d2a8b1abbc SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-memstick.img) = 5a3dc5eb0f77708230c758514a364f1a7c876249f9db7d9b2f28f4a9aaaa471c SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-memstick.img.xz) = e9265da7632aaedaae7522b46c070ab753fadc95c25d18f2575cc89c388ba725 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-mini-memstick.img) = f11bcb04c5a01ac9ed1a4d52badbc219465e357b948916991cf0bfaf522adcca SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-mini-memstick.img.xz) = e8d621d81553c324db38e2b2ced882dbdcaa1cb49b992604cbdc9cdc9f170c79 o 12.0-BETA2 aarch64 RPI3: SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-RPI3.img.xz) = 4d7ca4331f9648ad5a58a4c4e8f1610dad79154259ec1b28fef916a4907f1503a1b217daa1852a1a80a3e8167db301a4a8ba701b9e8762af46a2088114450147 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-RPI3.img.xz) = 32c30b5f147cf907c358d4cf165f89eb9c19b6efaf774382b54fc16e85c97275 o 12.0-BETA2 aarch64 PINE64: SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-PINE64.img.xz) = 7d722293cbfeb7ee8e9a7c8dcbdcc68968812c5e8e11100bec8f4b1f3ffbd2e85316ba22fdbad6069b2d1d6b9f49138cd89dab1e0e54572d9c3118b7aa7bfbe0 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-PINE64.img.xz) = c312894aed64214445105cde247680d63a0a200519e520e29eeceec2c871e560 o 12.0-BETA2 aarch64 PINE64-LTS: SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64-PINE64-LTS.img.xz) = 4fa99218ffafcba0ecd1b90e5cf45f46d1efc85eec19e0c9694b0fdc3bedbf3004ff9778113502ad7372b8da1ba836abc9ac9fe599e0e182b64e1ffab2000705 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64-PINE64-LTS.img.xz) = 2bd455b2d1240e8de242ef0508884e9b1b643777a990495e971e9dc43d81b5ec == VM IMAGE CHECKSUMS == o 12.0-BETA2 amd64: SHA512 (FreeBSD-12.0-BETA2-amd64.qcow2.xz) = 93ed99166aeed01ecf550241da220bad79b4ce9e488436436d06d9f81cbd60c41dbd8bbd0ee990dac64bd4c8d3244d4b15756aaccdad0608e484632c4a2d0bf9 SHA512 (FreeBSD-12.0-BETA2-amd64.raw.xz) = c0e7528f356ca77287250ea88183c03918878e0e475d4ff6ab85ce295320cc2d96c42534fc1b2c2b6b33cbf6373bd6ba7505198656e4bdb58d1b9009aa153c04 SHA512 (FreeBSD-12.0-BETA2-amd64.vhd.xz) = 16de137358b951b9a494411c17c5341c065c5bdaf2dc2189f3e9b991be3e9b713ca80ba8152102a3b6e52e467d745a5957f320c723920d3541605d14b2c01a24 SHA512 (FreeBSD-12.0-BETA2-amd64.vmdk.xz) = 7b89dcccf585b69f8923c1f4e3d66a415cb8f0911d358a88eb2fa4152e2caa02235eaf87424602d5cc034829a043de5723a0b7ed9dee25376697657adb1686ad SHA256 (FreeBSD-12.0-BETA2-amd64.qcow2.xz) = baacea152de96ce9e6927f62a788a9c91f5af1daaa7626c2266ea79b559f3294 SHA256 (FreeBSD-12.0-BETA2-amd64.raw.xz) = 68ca7b91b695a3cfef9d57b4748b301243eddd07014c8a11a87043df7db39c97 SHA256 (FreeBSD-12.0-BETA2-amd64.vhd.xz) = c097b26004cdc67054d81f9ee5f68c3d50fb78ea849a02eb38028ad5952221b4 SHA256 (FreeBSD-12.0-BETA2-amd64.vmdk.xz) = e3b10c2093fb8c5460735a41794100b6f742a1c7e44a04d76555e46395463452 o 12.0-BETA2 i386: SHA512 (FreeBSD-12.0-BETA2-i386.qcow2.xz) = 42181a82bbc57d3e3f77adb08b40a24383400ab6fafb0c669b47a4374e0f0f248f347edc3035dd530aa49e405994d3b2da6c2e1b52756f5fee07363d067950d7 SHA512 (FreeBSD-12.0-BETA2-i386.raw.xz) = b71d0bd84892f642e4c7a2d420571d87e3e9ea96a3e42d2f1474b7a00aa4a9ae44163bef0634683afbe0fdb3292e224cd5077ea3499c70b1c6e876a5e7fc54aa SHA512 (FreeBSD-12.0-BETA2-i386.vhd.xz) = 39f736d929cc6f9c3a60a9c125022264f0fef844a90595a4eefe1fd8992ad2193610a81fcffadc3d651b4b1130f11fef70d4ec2c8cd592a9e68a389b928dd5aa SHA512 (FreeBSD-12.0-BETA2-i386.vmdk.xz) = c634329b31376cad46c7a048ff66332021ddb44805688925ab0d6b18837bcd3025a3552c561a90a8f7b9cb8ff4d75bcc644501c3c98443ef604ff4d4ba39b5c8 SHA256 (FreeBSD-12.0-BETA2-i386.qcow2.xz) = 77441e363f2730d6894dca6fa2f5c2b75108ba343482d90c73c2891840a53ed8 SHA256 (FreeBSD-12.0-BETA2-i386.raw.xz) = 67292a382f5540e5c395b54567c23e877e5a5c9a4c0e8af22f3b66e153d355f9 SHA256 (FreeBSD-12.0-BETA2-i386.vhd.xz) = 1f6c08b99c35c010a4046644cabb6609e7a4f7179a401b920c1a7db10727d64a SHA256 (FreeBSD-12.0-BETA2-i386.vmdk.xz) = 71589c1d5fe7239358b36aba195eed23b0d39509d2cdc4a74c6b1c241b9aab1b o 12.0-BETA2 aarch64: SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64.qcow2.xz) = 1f0072782c58451ec3db8ac64d7210d2bf1f123787c9cac3d11bbbe6d6ec28f3fe7b8b58c90c4c175bb95cddc97185ad176920bb476b1bcfb8002a60a4345d7d SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64.raw.xz) = 767d37503cfa64a3ca8068bde8b0160c6c4e8cbadb8bddbc3208f65a37a51378f83b142a8245e4339ff628579034c5cb45adae4a5e0fa04ad3067405b9992aaa SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64.vhd.xz) = b0d0f1f98351ca7c56c880f21d5ba7367a4c623aceb5264b5705428cb9a6a98a93777a45ca26e99d06fff9b8c5195fa7bb08050afcb048defdbc35bd4b7ddfd5 SHA512 (FreeBSD-12.0-BETA2-arm64-aarch64.vmdk.xz) = a5a2c4431596e1f346906a0c7b299ec56ce84857dd4853d84e272f5f29e35d046180a4245e1561b187ff44814435ae8cbcb202055f7441588357d55da6c83d72 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64.qcow2.xz) = 420d265a3e3e03296b2c2ab40d1cf425656b8ef4b6a4c345997aa820846db193 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64.raw.xz) = eed7a78a511c0004064d17f52e06c4c6af2700fd9b831ed2fb60fc0274052b53 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64.vhd.xz) = c6a3116cf29cdd270a6d4fc14c9b7ae4d745069b0bf60a7f7840201783117b58 SHA256 (FreeBSD-12.0-BETA2-arm64-aarch64.vmdk.xz) = a850248b8b798f34070fa7b317bc90a2436c086b73facac85baedf09d0db8d7c Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvUmnQACgkQAxRYpUeP 4pPNrA//ZFGYf9Q2yLv4LoCVneNgGF/Bblw1UBHyL6kKcOzpcLfaGF1C3o563303 yZD1jgl32F6+1/q63R04RxuKQdk2+lOH9adW8tC490sywTOHNgs1ecrk3N+NwII1 XLCT56pJ1Is3rrd1Kjd9Hg45ej6oU1F5JvUj8/MgJ3THsyGirfzgcplrYRqacXdX KE4w/PNj4LeV9pWW2kcKbiB5mP/MrrZy3Clb+ASxusrx+q2pVsXenXrCXAKOTCZo /L0htS6kc5y86yDM4yR5exBWzOLbNUAx7VTCSVZoeyOES/WVeYG7oENUlHqhl1Z/ mH2k7IsqVMJwJo3Ve4RcUwSC51Im43oVhluQCWAbCIykpnxdEEeWN1U5WG/sQ+gq /RNUcuGpbezb8tKQO82PDiOoXXoLCV1OyrpEb39R6hD4q3r1TAoZ5aIAmpH8vYBT 0MkwLARu8jvyj03SWtEJlpTStiiJgI9Ux4dvM0vcovMKfYYpzTvTFxJpUXb5UeJo RKhle2pDWGqzTXJmXraA4mCX5xIL2gJKjKB+4CXHhnFBd3z0vYlNeW5h6CnBFWJN AB/Z4J7AnXhtWKWMr9YZvtPN1lcHFvSZVcsNStbtQzP9T5r1Cjqtw+z3WuoKWP2T wPRFFm+XoawbkFuxJe5MpwAdwHonskC0fBPUgSSKiGv6cV1Ip0c= =jdw/ -----END PGP SIGNATURE----- From owner-freebsd-current@freebsd.org Sat Oct 27 17:49:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B0D210CDD89; Sat, 27 Oct 2018 17:49:16 +0000 (UTC) (envelope-from gjb@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)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 447C074361; Sat, 27 Oct 2018 17:49:16 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id EA3171156F; Sat, 27 Oct 2018 17:49:15 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Sat, 27 Oct 2018 17:49:13 +0000 From: Glen Barber To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: FreeBSD Release Engineering Team Subject: Re: FreeBSD 12.0-BETA2 Now Available Message-ID: <20181027174913.GO61572@FreeBSD.org> Reply-To: FreeBSD Release Engineering Team References: <20181027170348.GN61572@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed In-Reply-To: <20181027170348.GN61572@FreeBSD.org> User-Agent: Mutt/1.10.1 (2018-07-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: Sat, 27 Oct 2018 17:49:16 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 One minor correction: On Sat, Oct 27, 2018 at 05:03:48PM +0000, Glen Barber wrote: > === SPECIAL NOTE === > This only affects systems that employ geli(4)-backed encrypted > filesystems and currently running 11.x or 10.x. Upgrades from > 12.0-BETA1, either via source-based upgrades or binary patches > via freebsd-update(8), are unaffected. > > An issue affecting backwards compatibility with geli(4)-backed > filesystems and an updated geli(8) binary after r332361 prevents > mounting encrypted filesystems with an older geli(8) binary from 11.x > and 10.x. For example, if /usr/src and /usr/obj are mount points on an > encrypted filesystem, the geli(8) binary that exists from 11.x or 10.x > after rebooting the system after 'installworld' will fail to attach the ^^^^^^^^^^^^ This should have stated 'installkernel' instead of 'installworld.' > encrypted filesystems when performing a source-based upgrade following > the documented upgrade path in UPDATING. > > For binary upgrades using freebsd-update(8) from 11.x and 10.x, the > recommended upgrade flow is to install the kernel patches, reboot, > install the userland patches, reboot, remove old libraries after > rebuilding third-party software. In this case, the initial reboot after > the kernel patches are applied can cause the same scenario where the old > geli(8) binary cannot attach the geli(4)-backed filesystem. > > A fix had been committed to head as r339804, and is expected to be > included in BETA3. For those without remote console access and do not > wish to upgrade via sources, it is advised to wait for BETA3 to upgrade > from 11.x and 10.x. > === END SPECIAL NOTE === > Glen -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlvUpRkACgkQAxRYpUeP 4pPRWA//agHzejU7vcrGfq65EcHyghnZtZI8Wl8ZRlWD6uBf34glFmqdj7GwuXeD QlqbFC+KXwjoCgR6rYU8UfPQkAD3RSXweODOGO95bRglK9zYRH53K5vvxG26fMdb 5IOgMFCRmZh8HGoJoQ6ckV8Nc83ETP7Sym+9nXDar0Dea7rhXnrZcc31HMGVWZDC 1Tj0Rm0HbESLqAUOA9HffAOl8gLO5WPnfOcYnNXGfYz0RSmjPbLKRe2wEeedZP6c hC4pspmMQeSge0KPDHgK8rf3/1mieyvfMGKFHKNzROOtw5hc0DFv+lnPQx7b8JcK S9dRKKQJWyvb7A4VgHGa9Rh/FXhf1gg/47TqQ+IrAYAf/zMBkKRgaEY1WajwAPCP QE3AE8ksGeGMImqkFVDUxrgCDTlJBKjYynfPuqe62mqhPdu3+WvlPmdEtgWEk54B Ad0RJjoSLe01usJ4p2g6HiYr9nwqDlLay+z8ZJFYeMHWcibTKKAY/pSflXv+mFhI t7U4bTzxwBBOMjUscd3UTAkEE7rfBU3DjfR6vTtvq0EfkXL13P0jdcvRRW38gAmV RsKmOhFBmzBsC+AqhDkqjIgmulnhw0dZ/IgmAEUOrRTzJUYrG6sXs7u0WSx0S79+ KIFChoa8RncTWYuM6o76MyjahPYrOhscCwAwiWMVqEFv8MQt0ic= =DEys -----END PGP SIGNATURE----- From owner-freebsd-current@freebsd.org Sat Oct 27 21:00:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A165810D3119 for ; Sat, 27 Oct 2018 21:00:24 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C43837AA57 for ; Sat, 27 Oct 2018 21:00:23 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 860B010D3109; Sat, 27 Oct 2018 21:00:23 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73F7C10D3108; Sat, 27 Oct 2018 21:00:23 +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 11FCA7AA56; Sat, 27 Oct 2018 21:00:23 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 42jCtY3sgdzDhyN; Sat, 27 Oct 2018 21:00:21 +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 qKLcVUkzsRmF; Sat, 27 Oct 2018 21:00:20 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:201:9eda:3eff:fe70:24c0]) by mail.daemonic.se (Postfix) with ESMTPSA id 42jCtX4bbZzDhyM; Sat, 27 Oct 2018 21:00:20 +0000 (UTC) From: Niclas Zeising Subject: FreeBSD x11-servers/xorg-server and CVE-2018-14665 To: current@freebsd.org, stable@freebsd.org, x11@freebsd.org, ports@freebsd.org Reply-To: x11@freebsd.org Message-ID: Date: Sat, 27 Oct 2018 23:00:19 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 27 Oct 2018 21:00:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 [ cross posted to several FreeBSD lists. Please keep replies to x11@FreeBSD.org ] Hi! As some of you are aware, the X.org project posted a security advisory on October 25 regarding a vulnerability in xorg-server [1]. This has been given the identifier CVE-2018-14665 [2]. The version of xorg-server in the FreeBSD ports tree is not vulnerable. In short, there is a vulnerability in versions 1.19 through 1.20.2 of xorg-server, when installed setuid root, which allows an attacker to overwrite or create any file on the system. By using this vulnerability, a local user can gain root privileges. There are several articles about this [3] [4]. The code in question was introduced on xorg-server 1.19, and as FreeBSD is still using xorg-server 1.18.4 we are not vulnerable to this issue. If you have questions or comments regarding this, don't hesitate to contact me or to send a message to the x11@FreeBSD.org mailing list. Regards - -- Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnica.com/information-technology/2018/10/x-org-bug-that-gives-attackers-root-bites-openbsd-and-other-big-name-oses/ [4] https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+Ll/478KgNjo+JKEu41LV7uLVVEFAlvU0WMACgkQu41LV7uL VVGgBw/+O7pIgdU5IvommsSetDAHPmdq3wy2j5mnWTjZXxz4qRe6pVJ6a0hJdkLw 8eSZGvPSo05Tnzk3Vx0cFdZ0hPIxm6Yp7dDpO6sXKDlxQrqDoxjPkjGMPj0897F+ 4hw7RWW9O5EEDlBHjL8+Uektkk2N7MjrlbNc2IZ+eHnH8XjQ5yDOFHT9NKLeAZeP ReJR/kN/+tW9VtzJtolk7vnksc8OF8ortsPX7dEXzoc1uHwppEoDlwQZrVRVuyCk j6JzrOthEVEnxvdvVmcQueijhzKE/2g1Ix82gYEfcHA1172kMWJka1m9Og2mKGqW 8aqKilpCv6koPXtWACeG5P8nG9+SpDH6HMhjpjQqdKG80x+0I9dbAu5mL9fTVKjp iFcY+8EQzsUYHEkvS9qk4dgiMR7MMXPM3JtOQOQ94hjoFcIp9toqeDr9U2DuRxAS LC4EQ1heaiqEtlCOMfkX5BExpBQ3fs+JrTqcDtIHujp7Cv8p19fhmehoXc3hzL0z xco1ubCOmLmR6Yed+BUxBcguMn37vE6KXDMoW0yQ/jmYt9a4EtECh/bTun81DZwN gEaFqutcnxzX1AWrYv92VT65OnA9pFXjmb4oU9OQRAiwnP7a8Is0nc7fnSrdtO/Y CoHWnZKI3hoMMWSXsfEc67RNtJyUnnGLHVvIt1VWrkL1+/WCm6k= =xBK6 -----END PGP SIGNATURE----- From owner-freebsd-current@freebsd.org Sat Oct 27 21:17:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C790110D3A1A for ; Sat, 27 Oct 2018 21:17:06 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6AAA07B603 for ; Sat, 27 Oct 2018 21:17:06 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2CEEE10D3A15; Sat, 27 Oct 2018 21:17:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B71010D3A14; Sat, 27 Oct 2018 21:17:06 +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 AF0FB7B602; Sat, 27 Oct 2018 21:17:05 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 42jDFr53TMzDhxn; Sat, 27 Oct 2018 21:17:04 +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 0sUZs4-3mvln; Sat, 27 Oct 2018 21:17:04 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:201:9eda:3eff:fe70:24c0]) by mail.daemonic.se (Postfix) with ESMTPSA id 42jDFr1WDLzDhFd; Sat, 27 Oct 2018 21:17:04 +0000 (UTC) Subject: Re: FreeBSD x11-servers/xorg-server and CVE-2018-14665 From: Niclas Zeising To: current@freebsd.org, stable@freebsd.org, x11@freebsd.org, ports@freebsd.org Reply-To: x11@freebsd.org References: Message-ID: <53177232-9cce-c794-c90d-7f1eff9666aa@freebsd.org> Date: Sat, 27 Oct 2018 23:17:03 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 27 Oct 2018 21:17:06 -0000 On 10/27/18 11:00 PM, Niclas Zeising wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > [ cross posted to several FreeBSD lists. > Please keep replies to x11@FreeBSD.org ] > Yes, I know the signature is BAD. GPG is as user friendly as always. I'm about to re-send this with a (hopefully) good signature. Apologies for the spam. -- Niclas Zeising From owner-freebsd-current@freebsd.org Sat Oct 27 21:22:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1181510D449A for ; Sat, 27 Oct 2018 21:22:52 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A37587BF56 for ; Sat, 27 Oct 2018 21:22:51 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6897110D4493; Sat, 27 Oct 2018 21:22:51 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DB1110D4492; Sat, 27 Oct 2018 21:22:51 +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 D30DD7BF54; Sat, 27 Oct 2018 21:22:50 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 42jDNT6ND0zDhxn; Sat, 27 Oct 2018 21:22:49 +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 IB-N7HZ4VFOY; Sat, 27 Oct 2018 21:22:49 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:201:9eda:3eff:fe70:24c0]) by mail.daemonic.se (Postfix) with ESMTPSA id 42jDNT0nLWzDhFd; Sat, 27 Oct 2018 21:22:49 +0000 (UTC) To: current@freebsd.org, stable@freebsd.org, ports@freebsd.org, x11@freebsd.org From: Niclas Zeising Subject: FreeBSD x11-servers/xorg-server and CVE-2018-14665 Message-ID: <843df95a-ae39-4fd4-9d30-9cd369776f3f@freebsd.org> Date: Sat, 27 Oct 2018 23:22:48 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 27 Oct 2018 21:22:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 [ cross posted to several FreeBSD lists. Please keep replies to x11@FreeBSD.org ] Hi! As some of you are aware, the X.org project posted a security advisory on October 25 regarding a vulnerability in xorg-server [1]. This has been given the identifier CVE-2018-14665 [2]. The version of xorg-server in the FreeBSD ports tree is not vulnerable. In short, there is a vulnerability in versions 1.19 through 1.20.2 of xorg-server, when installed setuid root, which allows an attacker to overwrite or create any file on the system. By using this vulnerability, a local user can gain root privileges. There are several articles about this [3] [4]. The code in question was introduced on xorg-server 1.19, and as FreeBSD is still using xorg-server 1.18.4 we are not vulnerable to this issue. If you have questions or comments regarding this, don't hesitate to contact me or to send a message to the x11@FreeBSD.org mailing list. Regards Niclas Zeising FreeBSD X11/Graphics Team [1] https://lists.x.org/archives/xorg-announce/2018-October/002927.html [2] https://nvd.nist.gov/vuln/detail/CVE-2018-14665 [3] https://arstechnica.com/information-technology/2018/10/x-org-bug-that-gives-attackers-root-bites-openbsd-and-other-big-name-oses/ [4] https://www.securepatterns.com/2018/10/cve-2018-14665-xorg-x-server.html -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+Ll/478KgNjo+JKEu41LV7uLVVEFAlvU1AgACgkQu41LV7uL VVEbJA//X6jZBPlBgv86w0zD2kxvBEu9wdx4Ib2MwRHAFmnhkv4vkOK37cmkNl35 PJII8TE+9+AoOdm+jybZqJJDqyl54uLh1M46BTuE4LQkvhCyHlMKUaBaQmcBMGyE 9j/hKKr4aaHXwFKZS+Cy/KhKytAOR6le1r07KlmWBTw6SPq4Bm8+KWXjceiFdlkF GvCF35PeiJ+aIBIT/5ufVJHaUqNZZF8jtuCpNEgSotLogX/HfWYvMhf/ExC6JijA OuYLjw/xZmGNKg68QM0AN1dFB83JYx/eIZMVCRWj9Rt/ypeF7ISM/qkypW1OOHMr a9uwEhO6qTr7drfb/pX4/Y+Z9/pumIWQIZgAI9aYzBY9T+op2qifKTFEqpxfXTCj wuFDKP270la3prhs2hp+q+LgsGxTv9BelodQh5NsNHuKWb6Fzro7Vsy189wg6ulK E+tQ8qNbWQLfUHVCkCthe1nfLAX2KrOEgDMxWjlgPM5BPIU8JancCjuz02wQ6AiU lBMfMCW4b5fDZZMqSNNpDW0kiAvXt+aewA23tAmhNSSmSRFXUXlV6UKw3anU3R0G xVkN8dXnkhWSVfMWXUy92aYHUr1eTZDclSEZlrgJGfLI+DY2OXWDnvsUwm2wPhIR YSYvrI2iJa31qoF05t6bpJY3USRORHg+OlrGlVnOPXK4rar/Z6M= =0NLO -----END PGP SIGNATURE----- From owner-freebsd-current@freebsd.org Sat Oct 27 21:48:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0BF810D5148 for ; Sat, 27 Oct 2018 21:48:44 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 4E0307D0CC; Sat, 27 Oct 2018 21:48:43 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id E3802E8087; Sat, 27 Oct 2018 15:49:15 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4yB4jkIrsGDs; Sat, 27 Oct 2018 15:49:15 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sat, 27 Oct 2018 15:49:15 -0600 (MDT) Subject: Re: 13-CURRENT lua loader complains dynamic libs not supported To: Kyle Evans Cc: FreeBSD Current References: From: Rebecca Cran Message-ID: <0094cff7-02c2-bca1-3cdc-190c1ad08a59@bluestop.org> Date: Sat, 27 Oct 2018 15:48:36 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Sat, 27 Oct 2018 21:48:44 -0000 On 10/27/18 10:34 AM, Kyle Evans wrote: > > Hmm... something's definitely amiss here- there's no reason this > should be munging through /usr/local/... at all- it's not in the > LUA_PATH. I'd be interested in knowing if there's anything funky about > your build or run setup- I have lua53 installed, but I don't seem to > have any odd interactions. I don't even have lua installed: /usr/local/lib/lua doesn't exist! I just updated to b9d1ddaf9ff163befda062c8c272fc91b176ac0a from github and verified that "git diff master..upstream/master" doesn't show any changes. "strings /boot/loader_lua" shows "/usr/local/lib/lua/5.3/?.so;/usr/local/lib/lua/5.3/loadall.so;./?.so" grepping for "usr/local" in the source tree (stand/) shows: ./liblua/luaconf.h:205:#define LUA_ROOT    "/usr/local/" -- Rebecca From owner-freebsd-current@freebsd.org Sat Oct 27 22:38:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B911410D660E for ; Sat, 27 Oct 2018 22:38:02 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 5789D7E60D; Sat, 27 Oct 2018 22:38:02 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 16DE4E80ED; Sat, 27 Oct 2018 16:38:40 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yPe2_qtr_kV1; Sat, 27 Oct 2018 16:38:39 -0600 (MDT) Received: from cube.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sat, 27 Oct 2018 16:38:39 -0600 (MDT) From: Rebecca Cran Subject: "arc4random: no preloaded entropy cache" printed once per CPU on startup To: FreeBSD Current , cem@freebsd.org Message-ID: <7e275fec-0d8d-88c1-8dc5-47fc893436b2@bluestop.org> Date: Sat, 27 Oct 2018 16:38:00 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Sat, 27 Oct 2018 22:38:02 -0000 On a normal boot (not verbose) of -CURRENT from today's sources I'm getting the following message printed once for each logical CPU: arc4random: no preloaded entropy cache Since other messages, including the same one in random_harvestq.c are under bootverbose, should this one in arc4random.c be too? I guess another question is _why_ this message is being displayed, since it looks like it should only happen if an entropy stash (/entropy?) is missing:         /*          * This is making the best of what may be an insecure          * Situation. If the loader(8) did not have an entropy          * stash from the previous shutdown to load, then we will          * be improperly seeded. The answer is to make sure there          * is an entropy stash at shutdown time.          */ -- Rebecca