From owner-freebsd-current@freebsd.org Sun May 20 02:57: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 7FDACEEF6F6 for ; Sun, 20 May 2018 02:57:06 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic314-15.consmr.mail.bf2.yahoo.com (sonic314-15.consmr.mail.bf2.yahoo.com [74.6.132.125]) (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 1764A6B35D for ; Sun, 20 May 2018 02:57:05 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: uwIeZ4AVM1l0pAxLGFB1g8c8qcVOUJGqD2OlSDOVi_xJZhh2cK5sqF.6F2PzqE. scwEQ5mPc.Ip5EQhjkr.PYJIbS2Xw4exCecycDhKUjakWQIJJxTWxvVkW0oc.RFKg99Gls59U0qY WT5O57w08iIKtbjGb1rZV8ptybD0z2bqoFcNtj32grosDfe7_tAV6R1PwM67MyhkA6_zPfY4CEGE 7X0jeiLP4Pw5Fj3D.TawpNwmAF1SB85HQrHi4ttHGdBDMy_Rh4_j3.gIdFY.auq5rcQgnGPczndV PcMMeYPiTBPx8OjhQq6sJjotX6TMZbz188ELLzt7iOLa5mbGPi852Lh.UROqkmnpVPJ1fZNabNyF oocYog0q2i6z3yOEBzfGeHCpxdAMPWbc9ifXFCgKyK5jSaSVkCIkC_4p8sKmYUu_llYOVVXmzpgO Bz3QHiIAo1VZDuTDbkEcbkVFXzZ8W4C3eRnXBQGXjxxUIQEGW9l4_EaymO9SjsBOuhuAwP.EdweQ qAmEFOMwPeez0Bqr_.S0UnJHksdKoBmqVQA40H_nXFZahF1Eg4GOeruaAmz3bbI126aBZ_PJzwcd Mh6reE28cQgbYE8M.i3A5sX3XWJ9ehN5DuxBeH.vK6fgkfKpupi_kq.0MuV.10aI4JoNBvclZ9BU o9g-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Sun, 20 May 2018 02:56:59 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp426.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8a2f960f33fb449453dde59fa45bb71b; Sun, 20 May 2018 02:56:56 +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.3 \(3445.6.18\)) Subject: head -r333905 broke the builds Message-Id: <1E5B6B0B-82B2-45F2-B10D-B5227C8BDFBC@yahoo.com> Date: Sat, 19 May 2018 19:56:54 -0700 To: mmacy@FreeBSD.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 02:57:06 -0000 https://ci.freebsd.org shows all the builds being broken and going through the list -r333903 was working but -r333905 and later are not. (I ignore riscv64 here.) Using powerpc64 as an -r333905 example: --- sourcefilter.o --- In file included from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/netinet/ip_var.h:39, from /usr/src/lib/libc/net/sourcefilter.c:43: /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = error: expected declaration specifiers or '...' before 'epoch_cb_count' cc1: warnings being treated as errors /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = warning: data definition has no type or storage class /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = error: expected declaration specifiers or '...' before 'epoch_cb_task' /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: 'struct grouptask' declared inside parameter list /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: its scope is only this definition or declaration, which is = probably not what you want /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: data definition has no type or storage class /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = error: conflicting types for 'DPCPU_DECLARE' /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = error: previous declaration of 'DPCPU_DECLARE' was here /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h: In = function 'epoch_enter_preempt': /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: 'curthread' undeclared (first use in this function) /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: (Each undeclared identifier is reported only once /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: for each function it appears in.) /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h: In = function 'epoch_exit_preempt': /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:81: = error: 'curthread' undeclared (first use in this function) This seems to match up with: Author: mmacy Date: Sun May 20 00:22:28 2018 New Revision: 333905 URL:=20 https://svnweb.freebsd.org/changeset/base/333905 Log: ip(6)_freemoptions: defer imo destruction to epoch callback task =20 Avoid the ugly unlock / lock of the inpcbinfo where we need to figure out what kind of lock we hold by simply deferring the operation to another context. (Also a small dependency for converting the pcbinfo read lock to epoch) Modified: head/sys/netinet/in_mcast.c head/sys/netinet/in_pcb.c head/sys/netinet/ip_var.h head/sys/netinet6/in6_mcast.c head/sys/netinet6/in6_var.h head/sys/netinet6/ip6_var.h =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun May 20 03:50: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 47B39EF1375 for ; Sun, 20 May 2018 03:50:37 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic306-21.consmr.mail.gq1.yahoo.com (sonic306-21.consmr.mail.gq1.yahoo.com [98.137.68.84]) (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 C8D116D16D for ; Sun, 20 May 2018 03:50:36 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: JakAo6IVM1l0jgd3HdA6bg9VuLBY..cb4NQ6IcLB5l0QFXlLNjVvUMAezfTPEyW HXIzPPmL97AWloEuNCcuaZLh4sbaegziYdsXJYczUqj0NGW.qR.UuN.ugyHJG5jw4twJQOgrOzav h8mnj_isFbsIVmI89cKSM4puL4ZRMaAhNrkh1IyzAjdKZWP8OMBPy25BvlgG6VXbtx7nbQWcJWt8 FoBwuv_N7a1fIG5_5chv3vBwG8A6j2Tv8i8KqeOXBSeDa_q5TTYpPsjdTvHHPlARL4a_98x4Bhr7 B9tOO3G3rPYkejBLeiGjLf5iO6Ym9HJ3vKFBewekLJ0dSJD3iEkut6wAl24CPm_c4eR9WPOnSZYU hQ1Qwpc5WWmLzT9BNSzcoJhfF9jQ4JipAPKfkbNJgxqJkBfL45YBVLSETfWqHFiJ2loBNOJrLAVW Ffl9KoD3uJF2KUmdqFSMpOiqsUsULwBpSlRl.BBdjepDccLdRvM_Put3EBHou6IQdFpZgi5.tn9d 8kg9uVHAm7E.D95RVi55VG0fgkojZSoHkEUd_lgpp7C68Vnb5S7JUbPqxUI.5GjEjTVxxQbyIZ5. pbu4P5wAYT7LFaYydxJCA_dQgHbdWzd__017TGVgaf.QIDFg90WuBUqmdM9c2PDyGZPT307Ylq1H .Zw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Sun, 20 May 2018 03:50:34 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp417.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c43db7733ab226b5970c5675e64ccd25; Sun, 20 May 2018 03:50:34 +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.3 \(3445.6.18\)) Subject: Re: head -r333905 broke the builds [ -r333906 changed the details but they are still broken] Date: Sat, 19 May 2018 20:50:33 -0700 References: <1E5B6B0B-82B2-45F2-B10D-B5227C8BDFBC@yahoo.com> To: mmacy@FreeBSD.org, FreeBSD Current In-Reply-To: <1E5B6B0B-82B2-45F2-B10D-B5227C8BDFBC@yahoo.com> Message-Id: <31730734-59C9-44C1-9B2B-27DEA5BE867E@yahoo.com> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 03:50:37 -0000 On 2018-May-19, at 7:56 PM, Mark Millard = wrote: > https://ci.freebsd.org shows all the builds being broken and > going through the list -r333903 was working but -r333905 and > later are not. (I ignore riscv64 here.) >=20 > Using powerpc64 as an -r333905 example: >=20 > --- sourcefilter.o --- > In file included from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/netinet/ip_var.h:39, > from /usr/src/lib/libc/net/sourcefilter.c:43: > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = error: expected declaration specifiers or '...' before 'epoch_cb_count' > cc1: warnings being treated as errors > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = warning: data definition has no type or storage class > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = error: expected declaration specifiers or '...' before 'epoch_cb_task' > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: 'struct grouptask' declared inside parameter list > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: its scope is only this definition or declaration, which is = probably not what you want > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = warning: data definition has no type or storage class > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:43: = error: conflicting types for 'DPCPU_DECLARE' > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:42: = error: previous declaration of 'DPCPU_DECLARE' was here > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h: In = function 'epoch_enter_preempt': > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: 'curthread' undeclared (first use in this function) > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: (Each undeclared identifier is reported only once > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:68: = error: for each function it appears in.) > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h: In = function 'epoch_exit_preempt': > /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:81: = error: 'curthread' undeclared (first use in this function) >=20 >=20 > This seems to match up with: >=20 > Author: mmacy > Date: Sun May 20 00:22:28 2018 > New Revision: 333905 > URL:=20 > https://svnweb.freebsd.org/changeset/base/333905 >=20 >=20 > Log: > ip(6)_freemoptions: defer imo destruction to epoch callback task >=20 > Avoid the ugly unlock / lock of the inpcbinfo where we need to > figure out what kind of lock we hold by simply deferring the > operation to another context. (Also a small dependency for > converting the pcbinfo read lock to epoch) >=20 > Modified: > head/sys/netinet/in_mcast.c > head/sys/netinet/in_pcb.c > head/sys/netinet/ip_var.h > head/sys/netinet6/in6_mcast.c > head/sys/netinet6/in6_var.h > head/sys/netinet6/ip6_var.h It looks like -r333906 changed the error details. Using i386 from ci.freebsd.org this time: --- all_subdir_usr.sbin/sendmail --- In file included from /usr/src/contrib/sendmail/src/daemon.c:51: In file included from = /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_var.h:39: In file included from = /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/epoch.h:33: In file included from = /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/proc.h:47: In file included from = /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/filedesc.h:42: /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/priority.h:128:8: error: = redefinition of 'priority' struct priority { ^ /usr/src/contrib/sendmail/src/sendmail.h:1081:8: note: previous = definition is here struct priority ^ This seems to happen for -r333906 and later versions on all targets, including amd64. (I'm ignoring riscv64 that has been broken for a long time.) powerpc64 agrees despite the gcc 4.2.1: --- all_subdir_usr.sbin/sendmail --- In file included from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/filedesc.h:42, from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/proc.h:47, from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/epoch.h:33, from = /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/netinet/ip_var.h:39, from /usr/src/contrib/sendmail/src/daemon.c:51: /usr/obj/usr/src/powerpc.powerpc64/tmp/usr/include/sys/priority.h:128: = error: redefinition of 'struct priority' =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun May 20 05:35: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 926D6EF539E for ; Sun, 20 May 2018 05:35:28 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic312-23.consmr.mail.gq1.yahoo.com (sonic312-23.consmr.mail.gq1.yahoo.com [98.137.69.204]) (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 0BC0E7121D for ; Sun, 20 May 2018 05:35:27 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: Qr7K_foVM1kqDkESxa0bvDqvX_ahtDLquMjOzfhuU9T4SWvLLK6ki2CuhOR64dm R_V93LevJVKdQ8bc73cwDwCcI.ejenkX44WhImChuNkmcBpvkIBf4_WulYiyA6STg5aP21OxhRyH cmSL_CjadFPaia3LqRKTDNwhF7TzsaOahDB.LywmruDP65etU5XprHCXPnmjEWfKW1_eTIywcJl0 dd8LcpNF.sFTpxgi71ZKcTCcZWsaf9m2tkcdgvNnXMLm0yibEQW.WD.h44ds_m9uyY__XcPlWoJo ud2vceYS90Ne27MEBwi6Hvf_j3YUcEFu19566qEK4n8w8E86iubwkmb_jaNj3ZbIHCaTnALNUxmk nrKSQmAuqIHBPjXlfVzShr3TMF.jXoMMgk3BzrEFcp2JcnivpY2X7MJwsZRmeClYounbTUBYf9Ty 6PScyWgdKtY71FCUUI97VvS1tVwT0WKyrLhbUXTXURRjE1sgH0CkJLmLy.2wf_qaSDj_UWBlafjs pV2sZIvSgd6AFFKYfI0jfTVZbH5jzeFfszu8ZVHBjwQDAg4B377JyxW5UUWEUAU43CBa_ay2pUhA 04hS1hiJKfBuMbfW8PLNHNTBK54KQ9Qp5tlqXwV.D5hruId7ePEFv4lUyFlYgLf2Iz0vOxtID4n8 3fQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Sun, 20 May 2018 05:35:26 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp423.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 110b0820a184852b1928d91e12cf55b5; Sun, 20 May 2018 05:35:24 +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.3 \(3445.6.18\)) Subject: head -r333919 seems to have broken the builds Message-Id: <24CC317E-3083-4E38-8497-AEAAF4F887C6@yahoo.com> Date: Sat, 19 May 2018 22:35:23 -0700 To: Eitan Adler , FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 05:35:28 -0000 After -r333913 (by mmacy) fixed the builds, -r333919 seems to have broken them again (in a different way). On ci.freebsd.org various TARGET_ARCH's (mips, mips64, powerpc64, sparc64) are getting things like: --- all_subdir_lib/libmagic --- softmagic.pico: In function `msetoffset': /usr/src/contrib/file/src/softmagic.c:1442: undefined reference to = `buffer_init' /usr/src/contrib/file/src/softmagic.c:1426: undefined reference to = `buffer_fill' /usr/src/contrib/file/src/softmagic.c:1436: undefined reference to = `buffer_init' funcs.pico: In function `file_buffer': /usr/src/contrib/file/src/funcs.c:188: undefined reference to = `buffer_init' /usr/src/contrib/file/src/funcs.c:321: undefined reference to = `buffer_fini' ascmagic.pico: In function `file_ascmagic_with_encoding': /usr/src/contrib/file/src/ascmagic.c:147: undefined reference to = `buffer_init' /usr/src/contrib/file/src/ascmagic.c:153: undefined reference to = `buffer_fini' /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: libmagic.so.4.full: = hidden symbol `buffer_fini' isn't defined /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: final link failed: = Nonrepresentable section on output The other TARGET_ARCH's have not progressed to -r333919 yet. (I ignore riscv64 that has been broken for a long time.) =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun May 20 10:46: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 C22D0EB11B6 for ; Sun, 20 May 2018 10:46:44 +0000 (UTC) (envelope-from kp@krion.cc) Received: from krion.cc (krion.cc [148.251.235.209]) (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 6294D7A8A9 for ; Sun, 20 May 2018 10:46:44 +0000 (UTC) (envelope-from kp@krion.cc) Received: from krion.cc (krion.cc [148.251.235.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by krion.cc (Postfix) with ESMTPSA id 90F674CE25 for ; Sun, 20 May 2018 12:46:32 +0200 (CEST) Date: Sun, 20 May 2018 12:46:32 +0200 From: Kirill Ponomarev To: freebsd-current@freebsd.org Subject: buildworld / poudriere Message-ID: <20180520104631.GA1897@krion.cc> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 10:46:44 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Updating poudriere jail from r331491 to r333924 fails with: --- Sema/DelayedDiagnostic.o --- In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/lib/Sema/DelayedDiagno stic.cpp:17: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/include/clang/Sema/Del ayedDiagnostic.h:25: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/include/clang/Sema/Sem a.h:18: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/include/clang/AST/Attr .h:17: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/include/clang/AST/Attr Iterator.h:17: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/tools/clang/include/clang/Basic/LL VM.h:22: In file included from /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/include/llvm/Support/Casting.h:19: /usr/local/poudriere/jails/head-amd64/usr/src/contrib/llvm/include/llvm/Support/type_traits.h:18:10: fatal error: ' type_traits' file not found #include ^~~~~~~~~~~~~ Any hints? --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEJCHRFhEAQujKni1pDyI9/LMCykUFAlsBUgcACgkQDyI9/LMC ykXqqwf8DlhZMRlK8AS35gWG6WNKAdKDTlXeqNQgpPp1YxLZ0ErHtXQG6WEKRTXC I4pOuu1uDxMVcd0X/hcpejZiAXgajdpBWXZtqrp3l629foutTi0PjwzGOYJz0Qco dPgYM9oscoDXAoibS2eotUk6Rda91FydUREgICJYBf/FziRDyqQ9f3ZfqjIHKUmq utUu/uuKC19jAyz6aq0eOYJJHrRcOPHQNGieQQPC2Bg/Jgo7zQ71E4gQmdrwWPr+ 10MIrBuokzaCYG7dIPeUu4sivI/eq/Ys0ih81uOczMJYkqo+wTEd9qQu+aEAGHld vyy0+5n330BbbP+jM+7Zy3ooO7m45A== =qBaT -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- From owner-freebsd-current@freebsd.org Sun May 20 12:36: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 4CC86EDE906; Sun, 20 May 2018 12:36:50 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7D517D8A0; Sun, 20 May 2018 12:36:49 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback13g.mail.yandex.net (mxback13g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:92]) by forward100j.mail.yandex.net (Yandex) with ESMTP id EE10F5D81FA9; Sun, 20 May 2018 15:36:42 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback13g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id WWyTJP5ofw-agh4UuYV; Sun, 20 May 2018 15:36:42 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526819802; bh=y4l9JrYf6hq8/MahW8ILlvfHLSKYyOC6kJmhin7CrV8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=VWZnH196LZei4XXzlJbxwCJQOGNY0k0alraGDDz8/66g8ThYs92i2U1fl5B0wLpm6 S81caGnOTfv2qQivP7igCZhbKe8jGHV7vLTNKQsv+mCFU3SjaP8HZBSRYVssL1Dzmd sh/A6hq9PGcLbG8vX+awqiQGOA5AFuLoh3G14x4c= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id cpHsX1Ms25-ag1i5Y4g; Sun, 20 May 2018 15:36:42 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526819802; bh=y4l9JrYf6hq8/MahW8ILlvfHLSKYyOC6kJmhin7CrV8=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=VWZnH196LZei4XXzlJbxwCJQOGNY0k0alraGDDz8/66g8ThYs92i2U1fl5B0wLpm6 S81caGnOTfv2qQivP7igCZhbKe8jGHV7vLTNKQsv+mCFU3SjaP8HZBSRYVssL1Dzmd sh/A6hq9PGcLbG8vX+awqiQGOA5AFuLoh3G14x4c= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: freebsd-x11@freebsd.org, freebsd-current@freebsd.org References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> From: Boris Samorodov Openpgp: preference=signencrypt Autocrypt: addr=bsam@passap.ru; prefer-encrypt=mutual; keydata= xsFNBFKPjHIBEACwdrpPbV9pGnP/MFO0lsubC1ruUr7y79tnT/gWKlI3i8gPPS3GG5FVFwjM 9YsSv7H5wxKlHa7ufFa8BETQQF+tBWlOy5lGh0a55M9qNCY+jlnAbmRRNdrIpr8ywHHd3eIr DBafMB6CG5GIgEMJ1OBcHmNuIUOd1A8Esi4eGpd6NFRcT3O58dC8wHfEqpdCVVX+mrPEWAno Q72i0q+j6NtsyTNTFEiACiuXeW+h2xl4zj09rr1CXlCcBV4SQ20uxJ4gegGapAMXzXDUpvCD X1M8wcjlUVa44PtTvGj5OxhGypKZJnz1CQcIQJ4qjPxvg6p8PsGnAaEWfdXPL5CH5GUmuaUt qMRbzyR/Bo/K8bYMYl5o/YcAjXopkn4ij1H3KACqE5YWvEwcfiNKX++uhuVhtja34sOTWJl9 ilboFJ9C9RDq/zE6oxF4vBGMVWjF4qm88P2PXWULLPPyhg98NxFMbH0XXWnOUt0x8yqY2v0t kz2sWn1ft/o09gQ0aaUtzYvG+cLg3FeU0EeXYum+jdTKdA27uKtTmgRuwQ135XIf0+4M5hrX pw2dBh/JljkQiv1lhKiCQrVBdS52nRvRXaCo7t0OiRR4y7268LYPr7ellCq3Ywykdj8bWvmt szYcnYBi7wiftHCid8wR0bQdyGRUcuc4IH4fCf7hS8trSjukWQARAQABzSJCb3JpcyBTYW1v cm9kb3YgPGJzYW1ARnJlZUJTRC5vcmc+wsF9BBMBCAAnBQJSj4yzAhsDBQkJZgGABQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAAoJEJYOILA6P20ooagP/3r6OfyiGW5B3Fv1ylBWp8lzHZVD mI8pGW7J4ubizPsz6t+CHBofNvCkrxjW7C1WDq7qRDfgqL6rYBV6D6GMtdUm5oKmnyJNNET5 hXRP7/ljzYDaLbBaVY5Oidu7OBS4k6RRwlypo5vFaI7/YJp6iIm80eIC6MCmPJpsRqdsY6pj ng5/F8obspP+HfrORHYLYRg8mt0PLG6UwkkiOdP48z2X0Arhjbt2v5QCDwOzwerE7JfN3/P6 Knf1Soiki9vWw6CAaC5K/oo/tdbvfiUzrzxSAaV8K7HQ4dVqaKFxI5xQ2GnafnEfyPLBZQQR WdmYJcL1qwCk4D76VrN2whR94+ZczPFji6jGCxOUo4mM/hqwq44KF9xi7asZmZC7/LHZ11ac j8NMEPHQJ4nmB7q9of4Wwu9XeJUrTt7oY+AQKpmewRxab5K0EJDd9IyfQusNgHHVpF2Jpa7U MAxClPtWdoXfRSk3esxeLhu33WJOpVpAUVeLIXF9g6EokOflV/0rb0onjuSeisVihvX/eG20 8eiSomt3xYgM+2ijGWugm5ie6eHkv5o34fcG9oanG71t9QIb7IgJ36UnLYGUcOyrpByUGEfg bYQgSEgSiDBbZBZVdM+aT2kJgbqRRYeqaqjmIXvSzL4c7zSRqQXv6h0L/P11CbMjycVNQ6uo iiP0eu5vzsFNBFKPjHIBEADUsIZuXuLo8baU85CU+Mv4gdyHwXzgIeNEG28O7Iu9bssY+Gt+ NiLI+4ZpBeQDbFzBGvyA/UoYDfURdY3KT6lXl2qamRaFz7SDtXuGpN9jDVgU048bbMjN4nk/ vV5ioqWw3V0x7eOiBtUbb17P1CVnnl249KyjdtMDu8jf7KRe2KgiFXgoL5ZeiGuN4g4n17VT H9DQCXJhIYPl5d7NEeGaUVKtPTEE1mClNt048dF/euduFRomxpwgXsg+tkSdZb1ffinYuFa7 mSMLg96LubVaels2rqQu097OO9GFqxyoBFzXtRwCOl2LbRJpG2ktJisin1zEshHx8slMC0km veXQv4S/LL33TNFPhfrbTJddMQhcrjwe4kDtdGY3XtBV2VEjUGRs63BSjtHPAQWx/JQTaBwx 5IPwuJAs0H0eJwjNtq+ZunzM1Dgbbtq4rQPsgrPIrtjHSv+u6ORW2wmd5uHxGyvADB8YyYRj R6scSLzLp7KrcFmkGq3RJcB3aDYi9r4TXr/gSZk4P0swhEXqo9oiddwRo7tv6JboRwltLG1F o91W5H8pwV5iG/R0EsM2k/aIAMOTBiZ2Lkk0bBH62hd/mp4p08z0E12QL/IYbH7VuXtz9ToA KiMtAAKg4nDe58ILAkfEAhNNsStSMOEjlXMz/6n7gsRrLljS16nmgd+8FQARAQABwsFlBBgB CAAPBQJSj4xyAhsMBQkJZgGAAAoJEJYOILA6P20odvEP/0KAbaBFAyJqhwXmj4ta1i55rkd+ 6vc46Az4trNZ6H/0XOJK5v9JGW1mz5aOURzSaSCitqS9uQa1qMssggn7a2pDRYA6LPKd0xgF 9KT68QMApN3KOtpFgn1D8rV6wywovntl3CpubiaDEmBD/fD7wrHiG+KsFzR48Dqzoth94D82 zIlCzfhbKDUzPwgc5ipds48MuP150WTwyKvOytwZbH/0RBGlqw/jkA6z3P86We4TuD0RFHZl /hpuSNadbUkfAOYI0LUfSFz/uYds08Rjf/YIawjA34mZFsDsWuoHhHqjl/x9uHA/o553LSw7 TmW/oR1xja/sWBaub/9WG9ZwuhPFE25DIG2eFQdv9d7XR7dyF+SIIkhiq4TuhD8hYYWPnvfN nzI9pfq3b9ag31P1ZHjpy9WxDplW7nTQq1yGLYOsd8Hoeh+QCY7PC/Ws8N566kW0bcUM1d12 2ZXA5XS0EBabmaAccuFtrIMt86XXgPYUqDOW4N/qKdF1dG+bhPPlFN3Lx9Sf3fbbNvJaI1DY bPgGUnCzctuLLfiARaFdgACXVhJ8ZhB6h7zPBOK8SB/bVSOqxcZh9elnusnkelNg57Up1qX3 pgkTpbOtvicdN2gogQQvtV40Nljrxmu2o0MoMcyqAxVG7KhKUih38fFqqrWEpFsVaLJeFk1u 4YL+0DfP Message-ID: Date: Sun, 20 May 2018 15:36:41 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 12:36:50 -0000 18.05.2018 20:58, Niclas Zeising пишет: > Is there anyone still using the drm2 driver on 12-CURRENT?  If so, what > is preventing you from switching to the port? I use base packages and can not use port: https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069329.html -- WBR, bsam From owner-freebsd-current@freebsd.org Sun May 20 13:04: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 422C4EE01AC; Sun, 20 May 2018 13:04:24 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 859C77E3F8; Sun, 20 May 2018 13:04:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id j5-v6so22266464wme.5; Sun, 20 May 2018 06:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7whA64froBUqx/W98VZux3UXYZZozvHrR1QSlyVSXm4=; b=ToJqiPy1j3X/9yTZulmvHZzQYXw/sQ7L4cIr+pH8pkW6GoMAdFlk6pdAbHo/z+zMhN HJ5HLK4AqOw7WwatWQsjzAJrt5VIq1M2pwomg87qsdJXw+z0D5m5B31KcVebqK+Ma2aJ redaC3qpkZvmH+z6cZewWRzYWn/4zN1J45nStED4QZaw5uzkzxTTX/sulayPpDuc8yL9 lXCrM4l35WZ2tOT/mHecYAgle+lwwI8aFmXBf8JjP/ZnhYoEccppG9K0z2M+abrYSjkM TL9cgCAFsWTEiAsmZzuitNf4/JcKORSaLfT7PfqtUUrTEYd62v+ANtstCw+592iksANd FI/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7whA64froBUqx/W98VZux3UXYZZozvHrR1QSlyVSXm4=; b=a1+d/lElQBEaZQDZv3kUebPgDwM86P04dCARO+roiFkxr5SHbCHfjBg1hm22D2EE4w J7eGNpDhZVAs/vB9snY+d2wqnOEITvU0dbFGnGmDh/W56I/q3jaheoBv+c7k9Vi++Tv0 NQw0EMVLFQ6SH5t3iQOCquOHrlnOZs9puObDZ787dI9wqqWpIWnckYR3jE5NcmD9hA6f WfmRWI0xd/PFy7dkzgeBiB0ZXoAMA3gHDtFKxUUUNl64qcSDBUaRF/Z88NCDxWtZiwS0 UPDHrLlVkYe1yTT0xGU4g5RAYyPLdqx9L3ZwYI5HtxA6OLdjhHR9HGCwp9zY+ENHe5Bw QzYg== X-Gm-Message-State: ALKqPwfL2zBCf+Kf+w7j8rDVXd+c/Am37hI3WN+kg/FWCJHvcT+1RGPC FFoHQAAyRLpOS2qQr5IY7/kqNIULqBCwlbYc04P4rw== X-Google-Smtp-Source: AB8JxZrluRjgCKgSWI4YSZjuUVFth1pmX8FTFzeN2kMtReJNtF73h6UqLCOBABiLaqgXZSRJ4WN5yoOG0gqJBbmZTCI= X-Received: by 2002:a1c:e54a:: with SMTP id c71-v6mr8022208wmh.55.1526821462525; Sun, 20 May 2018 06:04:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.167.137 with HTTP; Sun, 20 May 2018 06:03:42 -0700 (PDT) In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> From: Johannes Lundberg Date: Sun, 20 May 2018 14:03:42 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Boris Samorodov Cc: x11-list freebsd , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 13:04:24 -0000 On Sun, May 20, 2018 at 1:36 PM, Boris Samorodov wrote: > 18.05.2018 20:58, Niclas Zeising =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > Is there anyone still using the drm2 driver on 12-CURRENT? If so, what > > is preventing you from switching to the port? > > I use base packages and can not use port: > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069329.html If we remove drm.ko from base (which is suggested) you would be able to install the drm-stable/next-kmod packages without conflict. > > > -- > WBR, bsam > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Sun May 20 13:06: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 21EBCEE02CD; Sun, 20 May 2018 13:06:01 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FE877E51C; Sun, 20 May 2018 13:06:00 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback20j.mail.yandex.net (mxback20j.mail.yandex.net [IPv6:2a02:6b8:0:1619::114]) by forward105j.mail.yandex.net (Yandex) with ESMTP id B58091844CF; Sun, 20 May 2018 16:05:58 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback20j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id rTfpo8Bt15-5wv0u1ML; Sun, 20 May 2018 16:05:58 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526821558; bh=DwFJ9+7k0xnpIpnDdT13O2ipbNGP/svwjcEruimb+3c=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=cGn4W/6/j77EhOqkLddFjhjeTfUdMIFJcu/8BKY6G9HprSeadw4M5hdgdkFL2qxdm X7wxMTAPbtmwuYkkK/NOELSwyCUcbITGuX8olX4tvlMVLOH+/eaPaS4eIVqEu4T6qH KC9aGLMkRXUVq9+HWQnJPsuUa15W2KRhbA2laa9U= Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 33oUHZIv30-5vDeNqdk; Sun, 20 May 2018 16:05:58 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526821558; bh=DwFJ9+7k0xnpIpnDdT13O2ipbNGP/svwjcEruimb+3c=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=cGn4W/6/j77EhOqkLddFjhjeTfUdMIFJcu/8BKY6G9HprSeadw4M5hdgdkFL2qxdm X7wxMTAPbtmwuYkkK/NOELSwyCUcbITGuX8olX4tvlMVLOH+/eaPaS4eIVqEu4T6qH KC9aGLMkRXUVq9+HWQnJPsuUa15W2KRhbA2laa9U= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: x11-list freebsd , freebsd-current References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> From: Boris Samorodov Openpgp: preference=signencrypt Autocrypt: addr=bsam@passap.ru; prefer-encrypt=mutual; keydata= xsFNBFKPjHIBEACwdrpPbV9pGnP/MFO0lsubC1ruUr7y79tnT/gWKlI3i8gPPS3GG5FVFwjM 9YsSv7H5wxKlHa7ufFa8BETQQF+tBWlOy5lGh0a55M9qNCY+jlnAbmRRNdrIpr8ywHHd3eIr DBafMB6CG5GIgEMJ1OBcHmNuIUOd1A8Esi4eGpd6NFRcT3O58dC8wHfEqpdCVVX+mrPEWAno Q72i0q+j6NtsyTNTFEiACiuXeW+h2xl4zj09rr1CXlCcBV4SQ20uxJ4gegGapAMXzXDUpvCD X1M8wcjlUVa44PtTvGj5OxhGypKZJnz1CQcIQJ4qjPxvg6p8PsGnAaEWfdXPL5CH5GUmuaUt qMRbzyR/Bo/K8bYMYl5o/YcAjXopkn4ij1H3KACqE5YWvEwcfiNKX++uhuVhtja34sOTWJl9 ilboFJ9C9RDq/zE6oxF4vBGMVWjF4qm88P2PXWULLPPyhg98NxFMbH0XXWnOUt0x8yqY2v0t kz2sWn1ft/o09gQ0aaUtzYvG+cLg3FeU0EeXYum+jdTKdA27uKtTmgRuwQ135XIf0+4M5hrX pw2dBh/JljkQiv1lhKiCQrVBdS52nRvRXaCo7t0OiRR4y7268LYPr7ellCq3Ywykdj8bWvmt szYcnYBi7wiftHCid8wR0bQdyGRUcuc4IH4fCf7hS8trSjukWQARAQABzSJCb3JpcyBTYW1v cm9kb3YgPGJzYW1ARnJlZUJTRC5vcmc+wsF9BBMBCAAnBQJSj4yzAhsDBQkJZgGABQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAAoJEJYOILA6P20ooagP/3r6OfyiGW5B3Fv1ylBWp8lzHZVD mI8pGW7J4ubizPsz6t+CHBofNvCkrxjW7C1WDq7qRDfgqL6rYBV6D6GMtdUm5oKmnyJNNET5 hXRP7/ljzYDaLbBaVY5Oidu7OBS4k6RRwlypo5vFaI7/YJp6iIm80eIC6MCmPJpsRqdsY6pj ng5/F8obspP+HfrORHYLYRg8mt0PLG6UwkkiOdP48z2X0Arhjbt2v5QCDwOzwerE7JfN3/P6 Knf1Soiki9vWw6CAaC5K/oo/tdbvfiUzrzxSAaV8K7HQ4dVqaKFxI5xQ2GnafnEfyPLBZQQR WdmYJcL1qwCk4D76VrN2whR94+ZczPFji6jGCxOUo4mM/hqwq44KF9xi7asZmZC7/LHZ11ac j8NMEPHQJ4nmB7q9of4Wwu9XeJUrTt7oY+AQKpmewRxab5K0EJDd9IyfQusNgHHVpF2Jpa7U MAxClPtWdoXfRSk3esxeLhu33WJOpVpAUVeLIXF9g6EokOflV/0rb0onjuSeisVihvX/eG20 8eiSomt3xYgM+2ijGWugm5ie6eHkv5o34fcG9oanG71t9QIb7IgJ36UnLYGUcOyrpByUGEfg bYQgSEgSiDBbZBZVdM+aT2kJgbqRRYeqaqjmIXvSzL4c7zSRqQXv6h0L/P11CbMjycVNQ6uo iiP0eu5vzsFNBFKPjHIBEADUsIZuXuLo8baU85CU+Mv4gdyHwXzgIeNEG28O7Iu9bssY+Gt+ NiLI+4ZpBeQDbFzBGvyA/UoYDfURdY3KT6lXl2qamRaFz7SDtXuGpN9jDVgU048bbMjN4nk/ vV5ioqWw3V0x7eOiBtUbb17P1CVnnl249KyjdtMDu8jf7KRe2KgiFXgoL5ZeiGuN4g4n17VT H9DQCXJhIYPl5d7NEeGaUVKtPTEE1mClNt048dF/euduFRomxpwgXsg+tkSdZb1ffinYuFa7 mSMLg96LubVaels2rqQu097OO9GFqxyoBFzXtRwCOl2LbRJpG2ktJisin1zEshHx8slMC0km veXQv4S/LL33TNFPhfrbTJddMQhcrjwe4kDtdGY3XtBV2VEjUGRs63BSjtHPAQWx/JQTaBwx 5IPwuJAs0H0eJwjNtq+ZunzM1Dgbbtq4rQPsgrPIrtjHSv+u6ORW2wmd5uHxGyvADB8YyYRj R6scSLzLp7KrcFmkGq3RJcB3aDYi9r4TXr/gSZk4P0swhEXqo9oiddwRo7tv6JboRwltLG1F o91W5H8pwV5iG/R0EsM2k/aIAMOTBiZ2Lkk0bBH62hd/mp4p08z0E12QL/IYbH7VuXtz9ToA KiMtAAKg4nDe58ILAkfEAhNNsStSMOEjlXMz/6n7gsRrLljS16nmgd+8FQARAQABwsFlBBgB CAAPBQJSj4xyAhsMBQkJZgGAAAoJEJYOILA6P20odvEP/0KAbaBFAyJqhwXmj4ta1i55rkd+ 6vc46Az4trNZ6H/0XOJK5v9JGW1mz5aOURzSaSCitqS9uQa1qMssggn7a2pDRYA6LPKd0xgF 9KT68QMApN3KOtpFgn1D8rV6wywovntl3CpubiaDEmBD/fD7wrHiG+KsFzR48Dqzoth94D82 zIlCzfhbKDUzPwgc5ipds48MuP150WTwyKvOytwZbH/0RBGlqw/jkA6z3P86We4TuD0RFHZl /hpuSNadbUkfAOYI0LUfSFz/uYds08Rjf/YIawjA34mZFsDsWuoHhHqjl/x9uHA/o553LSw7 TmW/oR1xja/sWBaub/9WG9ZwuhPFE25DIG2eFQdv9d7XR7dyF+SIIkhiq4TuhD8hYYWPnvfN nzI9pfq3b9ag31P1ZHjpy9WxDplW7nTQq1yGLYOsd8Hoeh+QCY7PC/Ws8N566kW0bcUM1d12 2ZXA5XS0EBabmaAccuFtrIMt86XXgPYUqDOW4N/qKdF1dG+bhPPlFN3Lx9Sf3fbbNvJaI1DY bPgGUnCzctuLLfiARaFdgACXVhJ8ZhB6h7zPBOK8SB/bVSOqxcZh9elnusnkelNg57Up1qX3 pgkTpbOtvicdN2gogQQvtV40Nljrxmu2o0MoMcyqAxVG7KhKUih38fFqqrWEpFsVaLJeFk1u 4YL+0DfP Message-ID: Date: Sun, 20 May 2018 16:05:57 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 13:06:01 -0000 20.05.2018 16:03, Johannes Lundberg пишет: > On Sun, May 20, 2018 at 1:36 PM, Boris Samorodov wrote: > >> 18.05.2018 20:58, Niclas Zeising пишет: >> >>> Is there anyone still using the drm2 driver on 12-CURRENT? If so, what >>> is preventing you from switching to the port? >> >> I use base packages and can not use port: >> https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069329.html > > If we remove drm.ko from base (which is suggested) you would be able to > install the drm-stable/next-kmod packages without conflict. Great, thanks. -- WBR, bsam From owner-freebsd-current@freebsd.org Sun May 20 13:53: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 D7AC9EE1AE7; Sun, 20 May 2018 13:53:43 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay114.isp.belgacom.be (mailrelay114.isp.belgacom.be [195.238.20.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 10AA880172; Sun, 20 May 2018 13:53:42 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3A3fV8gB13iqDe2FdPsmDT+DRfVm0co7zxezQtwd8Z?= =?us-ascii?q?se0QK/ad9pjvdHbS+e9qxAeQG9mDsLQc06L/iOPJYSQ4+5GPsXQPItRndiQuro?= =?us-ascii?q?EopTEmG9OPEkbhLfTnPGQQFcVGU0J5rTngaRAGUMnxaEfPrXKs8DUcBgvwNRZv?= =?us-ascii?q?JuTyB4Xek9m72/q99pHPbQhEniaxba9vJxiqsAvdsdUbj5F/Iagr0BvJpXVIe+?= =?us-ascii?q?VSxWx2IF+Yggjx6MSt8pN96ipco/0u+dJOXqX8ZKQ4UKdXDC86PGAv5c3krgfM?= =?us-ascii?q?QA2S7XYBSGoWkx5IAw/Y7BHmW5r6ryX3uvZh1CScIMb7Vq4/Vyi84Kh3SR/okC?= =?us-ascii?q?YHOCA/8GHLkcx7kaZXrAu8qxBj34LYZYeYP+d8cKzAZ9MXXWRPUMZPWSJcAY2z?= =?us-ascii?q?bYUPAOUdMuhXtIT9u1kDoQeiCQWwGO/j1DlFjWL2060g1OQhFBnL0hIhH9IMtH?= =?us-ascii?q?Tfscv4NKAVUeCu0qbIyC/Mb/VN2Tzg74XIbhEhofOIXb9rccTR01cgGB3Yg1uN?= =?us-ascii?q?p4LpJTSV1v4Cs2WC6edrSOGhi3Y/pgxyvzSj3Nkgh4bUio4P1FzI6Tt1zJwoKd?= =?us-ascii?q?C4RkN2Z8OvHoFKuCGALYR2R9svQ2RvuCkn1LILoYW7fC0WyJQ/wB7fduCHf5CI?= =?us-ascii?q?4h39UOaRJi91hHF/d7K7hhay9Favyvf7VsWuzFZKryhFkt3Wun8R0BzT7dOHRe?= =?us-ascii?q?V4/ki73zaPzBrf6uZeIUA7jabbKpghzaAslpcLsknPAzX6lFv5gaOLbEko5PSk?= =?us-ascii?q?5/r9brn7ppKROZd4igTkPaQvnsy/D/44Mg8LX2WD5eS81b/j/UniTbVElP05jL?= =?us-ascii?q?fWv4vBJcsGvKK5BBVV0ok75xalEzimyMgYnWUALF9dYh2HiZXmO0vIIPD5Cfe/?= =?us-ascii?q?mE+hkDhux//cP73hBo/BIWTEkLfkLv5B7BtjwRA1wMoXw5VPCvlVIffrckXquN?= =?us-ascii?q?3dFlkyNAnikMj9D9Ao6oIcXSqkBaiCPabbt0TAsv4uIe2kSpUYtRzGB74i/fG4?= =?us-ascii?q?3ixxokMUYaT8hchfU3u/BPkzZhzBOXc=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2CKFQCCfAFb/5nK8VFbHgEGDINDU4ELK?= =?us-ascii?q?IxXjBgBAYF4MQFdkzaBeIRxBAICghAiNhYBAgEBAQEBAQIBayiCNSQBgk8BBTo?= =?us-ascii?q?cIxALDgoJJQ8qHgYThSeoJIg9gg+KSINtLopHAocrkSEJjkxpSwGLU5IcIwMug?= =?us-ascii?q?VJNMAiCfpBQPTCPaAEB?= X-IPAS-Result: =?us-ascii?q?A2CKFQCCfAFb/5nK8VFbHgEGDINDU4ELKIxXjBgBAYF4MQF?= =?us-ascii?q?dkzaBeIRxBAICghAiNhYBAgEBAQEBAQIBayiCNSQBgk8BBTocIxALDgoJJQ8qH?= =?us-ascii?q?gYThSeoJIg9gg+KSINtLopHAocrkSEJjkxpSwGLU5IcIwMugVJNMAiCfpBQPTC?= =?us-ascii?q?PaAEB?= Received: from 153.202-241-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.241.202.153]) by relay.skynet.be with ESMTP; 20 May 2018 15:52:33 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id w4KDqUiU002509; Sun, 20 May 2018 15:52:30 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Sun, 20 May 2018 15:52:29 +0200 From: Tijl Coosemans To: Warner Losh Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180520155229.73447c1c@kalimero.tijl.coosemans.org> In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> 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.26 Precedence: 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, 20 May 2018 13:53:44 -0000 On Fri, 18 May 2018 14:03:32 -0600 Warner Losh wrote: > So do people use i386 for desktop? And need the latest KMS stuff? I use radeonkms on i386. But what about other architectures like powerpc? If it's getting in the way, can't it be turned into a port instead of removing it? (All parts of FreeBSD should be available as ports imho.) From owner-freebsd-current@freebsd.org Sun May 20 14:13: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 2D39CEE223D for ; Sun, 20 May 2018 14:13:37 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 52C2D809F6; Sun, 20 May 2018 14:13:36 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id KP5XfmbNL5wO5KP5YfPHap; Sun, 20 May 2018 08:13:34 -0600 X-Authority-Analysis: v=2.3 cv=SJtsqtnH c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=VUJBJC2UJ8kA:10 a=CjxXgO3LAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=eiRvUTW0Q9AkiptHmVsA:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id CDC17D16; Sun, 20 May 2018 07:13:30 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4KEDUgg022224; Sun, 20 May 2018 07:13:30 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4KEDTPR022221; Sun, 20 May 2018 07:13:30 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805201413.w4KEDTPR022221@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Mark Millard cc: Eitan Adler , FreeBSD Current Subject: Re: head -r333919 seems to have broken the builds In-Reply-To: Message from Mark Millard of "Sat, 19 May 2018 22:35:23 -0700." <24CC317E-3083-4E38-8497-AEAAF4F887C6@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 May 2018 07:13:29 -0700 X-CMAE-Envelope: MS4wfFJsJzzb09n3uXERLLouKv02+Zze3i9HOi5qMWP4Wq/FISSfXNAwOD6t8jS0QFdlM0+rpKjx1vJHwsaQLeceM3QzcRRnGK584fBov5cekoMMOnoptHmA hp0JhjPBPh6h9AP0+4f7qiMfDkyxf58fjRVFukxvEPYP4cBakW+ZXxaM11mg56oBYCcTESODmGHADxOja8UB8VdZEmYlnMcuL//BGPRdP/3yfZbnfCNSjSMj qQHy3ZqABAusXHeJKxr0NauFrJfGC8q0uFwmWTp4usY= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 14:13:37 -0000 In message <24CC317E-3083-4E38-8497-AEAAF4F887C6@yahoo.com>, Mark Millard write s: > After -r333913 (by mmacy) fixed the builds, > -r333919 seems to have broken them again > (in a different way). > > On ci.freebsd.org various TARGET_ARCH's (mips, mips64, > powerpc64, sparc64) are getting things like: > > --- all_subdir_lib/libmagic --- > softmagic.pico: In function `msetoffset': > /usr/src/contrib/file/src/softmagic.c:1442: undefined reference to `buffer_in > it' > /usr/src/contrib/file/src/softmagic.c:1426: undefined reference to `buffer_fi > ll' > /usr/src/contrib/file/src/softmagic.c:1436: undefined reference to `buffer_in > it' > funcs.pico: In function `file_buffer': > /usr/src/contrib/file/src/funcs.c:188: undefined reference to `buffer_init' > /usr/src/contrib/file/src/funcs.c:321: undefined reference to `buffer_fini' > ascmagic.pico: In function `file_ascmagic_with_encoding': > /usr/src/contrib/file/src/ascmagic.c:147: undefined reference to `buffer_init > ' > /usr/src/contrib/file/src/ascmagic.c:153: undefined reference to `buffer_fini > ' > /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: libmagic.so.4.full: hidden s > ymbol `buffer_fini' isn't defined > /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: final link failed: Nonrepres > entable section on output > > The other TARGET_ARCH's have not progressed to > -r333919 yet. (I ignore riscv64 that has been > broken for a long time.) It's been fixed. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun May 20 14:22: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 3A1B0EE2693; Sun, 20 May 2018 14:22:34 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95DBF810F7; Sun, 20 May 2018 14:22:33 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id t22-v6so1085512lff.13; Sun, 20 May 2018 07:22:33 -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=9fxliUeI4MpwFU4yYdIi4Z0gNwej+9RSl46Axf1Ut94=; b=Cj/wUiIEe97+4BTTNHcfBhiwVMFkBbHNAjdbV58FT7QQWU66pA0PtFnt3o2sauD2eC wk1Zbjdu68rXXUfMjbcRIrk8sGe0IonMnq3UlFfNCwQfIOvwWFm4goiWPMRMf4LYrIR3 OWgyqJWCgQbGvc3vNU3bNKRFU/KPXaZ0S1Nl1LaT7gySCQ1eyPM0gy67ePbMr8AbqBro f55l76SdQbj60PkiT1qzjeDVvE0Rx62SPNTGT2NqV+Fq5R+C9dD04NXUMaHqvMK/HUEy 0xyXpdxpGPiJPyKPtoD1eiGwKOPwFI3TtucIKR7Wzl/qS+rWykAD+8IeFMLlx8RIHw+R oYzQ== 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=9fxliUeI4MpwFU4yYdIi4Z0gNwej+9RSl46Axf1Ut94=; b=JcF7pdodz9e3lctsVbH381jH76cEyVaESTIoWzTcPapCfQZbwuo07y5tSRdN6ZQVre GrhQNfZvQCxCatjHp9xz80Tj0nr4da8RM6xNd+3a1CqdRu6TqLiOkbb07ZRGK5CTsMvw 2ESa5XQ8vTzz7xGQ8oz/J5inGoO+y31q8KqZo4alK7XzmYAc1B4ro0Yf+MA4k3rzMUis a+Y0Z54Cyvsnr+tRxCwBHUQz23wNeARZESn6wt3Zsnodh422ySSSxqt15J8+4q5wVdXj z9zyTVtPIznoyKGP0zn0NdhiBlDLCDhXBvBaXkRpZSgrcRmhId63vufPxa96cJpWrS0e K7cA== X-Gm-Message-State: ALKqPwc2kpmvQs0Jq4TpTP9FYRNtJCAr2o4czB7SVQln0ywB2GMsEmn/ xrfs4fixSHHgFLL9zvqbAB4= X-Google-Smtp-Source: AB8JxZqhDCcG/7YrEA5PRKCjCG2RXBEMd/zLUuo2RRxY1D6YUEWLmCKPkZ80RI8V0A2SnTofffEBbQ== X-Received: by 2002:a2e:9ac3:: with SMTP id p3-v6mr9952637ljj.60.1526826152158; Sun, 20 May 2018 07:22:32 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id a81-v6sm635382lfe.79.2018.05.20.07.22.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 20 May 2018 07:22:31 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sun, 20 May 2018 17:22:29 +0300 To: Johannes Lundberg Cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180520172229.074a7004@gmail.com> In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.26 Precedence: 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, 20 May 2018 14:22:34 -0000 On Fri, 18 May 2018 21:12:26 +0100 Johannes Lundberg wrote: Is Ryzen 2200G integrated graphic supported? From owner-freebsd-current@freebsd.org Sun May 20 14:36: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 44C79EE2C88; Sun, 20 May 2018 14:36:32 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (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 8ED06818E3; Sun, 20 May 2018 14:36:31 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id KPRjfmibuuYopKPRkfa7Wu; Sun, 20 May 2018 08:36:30 -0600 X-Authority-Analysis: v=2.3 cv=GopsBH9C c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=8nJEP1OIZ-IA:10 a=VUJBJC2UJ8kA:10 a=6I5d2MoRAAAA:8 a=KawIFhhbAAAA:8 a=YxBL1-UpAAAA:8 a=RUNfwU-bpJRdli9djJwA:9 a=wPNLvfGTeEIA:10 a=7G_cc3ZGiqMA:10 a=IjZwj45LgO3ly-622nXo:22 a=sDZbbUVwIjaXAAecbMhh:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 5E668D7C; Sun, 20 May 2018 07:36:27 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4KEaR5K003855; Sun, 20 May 2018 07:36:27 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4KEaPmq003852; Sun, 20 May 2018 07:36:25 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805201436.w4KEaPmq003852@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Jan Beich cc: Slawa Olhovchenkov , freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Jan Beich of "Sat, 19 May 2018 20:38:20 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Sun, 20 May 2018 07:36:25 -0700 X-CMAE-Envelope: MS4wfIvZUT6F+KvAv8TJXl3z9r5XEBsR2vM+SdEcNt//MZPqF10QTl0kykoYP6o3F0mgm6rCSC1E3Wa3t0EMdNeHMg65uJFvyAq+pEtbrrIEuABRhzo0G9WX QOK1OfLdEZJZUKBKzlhLimdSS0W0Qouu5ecHG0VMxJzk8Up1UX4okkiJDoCv32gIq+ck9AUq47XZAp34MyNxNAOUsTDkrPmOTBsh+Lmbd3Cy5MUYp9+Oo/GP Lxd7XxgxqGFv50HwLeMlfw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 14:36:32 -0000 In message , Jan Beich writes: > Slawa Olhovchenkov writes: > > > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > > > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > >> reply-to and send all replies to freebsd-x11@. Thanks! ] > >> > >> > >> Hi! > >> I propose that we remove the old drm2 driver (sys/dev/drm2) from > >> FreeBSD. I suggest the driver is marked as deprecated in 11.x and > >> removed from 12.0, as was done for other drivers recently. Some > >> background and rationale: > >> > >> The drm2 driver was the original port of a KMS driver to FreeBSD. It > >> was done by Konstantin Belousov to support Intel graphics cards, and > >> later extended by Jean-Sébastien Pédron as well as Konstantin to match > >> what's in Linux 3.8. This included unstable support from Haswell, but > >> nothing newer than that. > >> > >> For quite some time now we have had the graphics/drm-stable-kmod and > >> graphics/drm-next-kmods which provides support for modern AMD and Intel > >> graphics cards. These ports, together with the linuxkpi, or lkpi, has > > > > What about old graphics card? I am have notebook w/ i945 chipset, is > > this supported by graphics/drm-*? > > > > And what about nvidia? > > (sorry, I am not developer this drivers, I am just user, I am don't > > know what need for nvidia work etc) > > NVIDIA dropped 32bit driver since 396.* series. None of x11/nvidia-driver* > currently depend on either drm.ko or drm2.ko. However, Linux driver > appears to depend on DRM/KMS since 364.12. I think that if we want to still keep i386 viable, maybe some effort needs to be put into 915resolution to help VESA look somewhat reasonable. IIRC, as it's been a long time since I've looked at this, a person will need a custom xorg.conf. However IIRC that model breaks if person switches between a laptop monitor and an external monitor. The problem is fixable however I didn't have a open evening to look at it when I did. The 915resolution option isn't exactly available to those unwilling or unable to tinker a little. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun May 20 15:14: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 88F55EE43CD; Sun, 20 May 2018 15:14:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB38A83180; Sun, 20 May 2018 15:14:01 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id KQ1xfmt1huYopKQ1yfaBtY; Sun, 20 May 2018 09:13:55 -0600 X-Authority-Analysis: v=2.3 cv=GopsBH9C c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=VUJBJC2UJ8kA:10 a=YqRfAJJkAAAA:8 a=7Qk2ozbKAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=jO70F6GEUZp9jOOeJw0A:9 a=CjuIK1q_8ugA:10 a=EZxYlxVqKW1-bC4Rwo9g:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 013D8E36; Sun, 20 May 2018 08:13:52 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4KFDqpA009180; Sun, 20 May 2018 08:13:52 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4KFDq1v009177; Sun, 20 May 2018 08:13:52 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805201513.w4KFDq1v009177@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Tijl Coosemans cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Tijl Coosemans of "Sun, 20 May 2018 15:52:29 +0200." <20180520155229.73447c1c@kalimero.tijl.coosemans.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 May 2018 08:13:52 -0700 X-CMAE-Envelope: MS4wfAJKU1vLlygmnv5DjtnstNm4M/xNpeee2JS2ezvHSY9RHL/+EDgGQ6LEh0DZ5IOoIka32e6iH5fFxURfNEsdi0hL+3OON88WPdXYVjx+pOZuKugMy1Pd I7TBucXBite/GN39YljF2bBC5+KsZilWWtr8MuxfxGfCp/wIfpkuWH8upTnxvoXUC67ykdJoDVZ5cOBUsrqfj1bmwFA21daKkkVklTx1pGv08FqfsZtU6HXS WUc5EU0NS5nCbvtstIRApto91xIoTIUX8FO0H/psb1juUiCVijrRub7STQtEK9ary11vkbl4eYnjbOFhwFmFz/niDd4b3jrz6wL6JJwF7iXbr+UOOENVPa00 4crxZ1saqsVS8GMOMbrb8IKzyfI4p1chs/8Q8R3myz00WLvv9UiAFna8paQfyZ1S0RuaVeroQjwznHwo4ehrvKBcUT6Nlw== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 15:14:02 -0000 In message <20180520155229.73447c1c@kalimero.tijl.coosemans.org>, Tijl Cooseman s writes: > On Fri, 18 May 2018 14:03:32 -0600 Warner Losh wrote: > > So do people use i386 for desktop? And need the latest KMS stuff? > > I use radeonkms on i386. But what about other architectures like powerpc? > > If it's getting in the way, can't it be turned into a port instead of > removing it? (All parts of FreeBSD should be available as ports imho.) Yes, I think this is the way out. First create a port while implementing a knob in base to disable drm2 build, with deprecation notice for those who choose to. After a month or two remove drm2. That should give enough time for those on -CURRENT who choose, to make the switch. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun May 20 15:33: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 C6A3BEE4BC4; Sun, 20 May 2018 15:33:32 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2309583BB8; Sun, 20 May 2018 15:33:32 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id i12-v6so444279wrc.4; Sun, 20 May 2018 08:33:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dAV6jWzwKK/rl16+ficUvbLb5UwtWAOnccnwUEKUIPE=; b=Q2tpoRstsdkhoXEBKBcRph2+e6XACqPGjuMvL/hAhqzJePmynIfvP6ahIXOTvtqHv8 VW1aYpQfx6o+cudhk9H3DaEwpQMQnMUjloZ3stvyB51RlrTYr15za16QgJLpSeyDxBNe n6NgT6MHkhJ/smMmbYr4cWOC0UJkuQnV3hctcj29FEP97gp9ui46k1Ww2lTztG/6EUQy yws96Aat7BuphfL2l5to7XGBONXG9wP2t7y2NsJQ9N2J0wBZG9FaEhSP2TfSVmz1fbUB tHU/ZQ78apxVfyvbX3UtRy1UM7M8nuYi2Q/q+a3FF+HNhClM9iQNB5LVtzeZ9aKIyKqY DnMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dAV6jWzwKK/rl16+ficUvbLb5UwtWAOnccnwUEKUIPE=; b=q0jCAUnucccghOUhwN2feQlFyJz2kUxdhZNvyDLXpdFWv7CB3xq7GqzVvjtKgy7qVB tOJiHUgOIJyd57rNVRnpWTi9+f2KJMOc3Qp0vETWM6btWwo+dVqWO69TpvKq+Mk4Z4tX 9HFoxbXZ+Rxwn1Zt+aiUf1AEn2Cspt2FuPEvRK8sN4outF6Omaywb7vR72pFZj7nGzfC bm+725g50hZ+j1gErLBQUSLEQOS9txQE+EjNHY8bjtvdFbycsGecqpBbltgGzWp8BSLd 42R8LcKnZjpchTcTnpGar7Ag+BHLIbYRFKlcxmZFMv6VGxrcCYwf90lEjRZy1tnzsR3X KLkw== X-Gm-Message-State: ALKqPwfZcFD0hHGTtwW/zQzjLCo+5CSqJSgfnmN4REQIQ/4E9ETmp1v+ EjyaD0pb7qDHX33jkBpvv6rMgW6TC1uyVrE3yaWRKg== X-Google-Smtp-Source: AB8JxZoLogTaSFBoWarGjIVO/G6XULZ7tLWM0ymxBLToYT8/gAXtfYD1SnqU2/Ig8bXD6AeRpHnqZYw1jg9kb7Btp58= X-Received: by 2002:a5d:408a:: with SMTP id o10-v6mr3746312wrp.133.1526830410584; Sun, 20 May 2018 08:33:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.167.137 with HTTP; Sun, 20 May 2018 08:32:50 -0700 (PDT) In-Reply-To: <20180520172229.074a7004@gmail.com> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520172229.074a7004@gmail.com> From: Johannes Lundberg Date: Sun, 20 May 2018 16:32:50 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Rozhuk Ivan Cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 15:33:33 -0000 On Sun, May 20, 2018 at 3:22 PM, Rozhuk Ivan wrote: > On Fri, 18 May 2018 21:12:26 +0100 > Johannes Lundberg wrote: > > Is Ryzen 2200G integrated graphic supported? > > Not in the current port. I think it should be usable in 4.15 but need some more tweaking and updated firmware modules before we can update the port. Active development going on here https://github.com/FreeBSDDesktop/kms-drm/issues From owner-freebsd-current@freebsd.org Sun May 20 16:40: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 87A22EE62EA; Sun, 20 May 2018 16:40:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1967C8584A; Sun, 20 May 2018 16:40:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4KGeBQf006363 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 20 May 2018 09:40:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4KGeBQ7006362; Sun, 20 May 2018 09:40:11 -0700 (PDT) (envelope-from sgk) Date: Sun, 20 May 2018 09:40:11 -0700 From: Steve Kargl To: Warner Losh Cc: Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180520164011.GA6276@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 16:40:20 -0000 On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: > > > > > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > > > removed from 12.0, as was done for other drivers recently. Some > > > > background and rationale: > > > > > > > > > > Sounds good ( deprecate resp remove ). It causes more confusion and > > > problems and it solves nothing. > > > > > > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ONLY_FOR_ARCHS= amd64 > > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > > > > Not to ia32 friendly. > > > > So do people use i386 for desktop? And need the latest KMS stuff? > Just a data point. I had to replace the dead disk in my laptop, and after 2 days of doing a re-install and update of -current on a shiny new SSD. Before loading Xorg. % kldstat Id Refs Address Size Name 1 7 0x800000 1ac31d4 kernel 2 1 0x1e9ae000 5000 ums.ko 3 1 0x1e9b9000 4000 uhid.ko After starting Xorg without an xorg.conf in /etc/X11. Id Refs Address Size Name 1 27 0x800000 1ac31d4 kernel 2 1 0x1e9ae000 5000 ums.ko 3 1 0x1e9b9000 4000 uhid.ko 4 1 0x1eaa9000 96000 i915kms.ko 5 1 0x1eb40000 4a000 drm2.ko 6 4 0x1eb8b000 5000 iicbus.ko 7 1 0x1ebc9000 3000 iic.ko 8 1 0x1ebcf000 4000 iicbb.ko So, drm2.ko and i915kms.ko are loaded automatically. It is unclear why functionality that works should be removed. xwininfo shows Width: 1400 Height: 1050 Depth: 24 Visual: 0x21 -- Steve From owner-freebsd-current@freebsd.org Sun May 20 16:47: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 58809EE65F8; Sun, 20 May 2018 16:47:12 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 58EAE85C7B; Sun, 20 May 2018 16:47:11 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40pnrF1hgQzDhTS; Sun, 20 May 2018 16:47:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1526834828; bh=VcpQVMXl3nfYtDqLVqrZliFV bq9yCReryi9eRHf0CJ8=; b=VHRdz0i34h2DjXsntoflHuEdWgozD/dEDz4qiKYQ 3HKDiupyur5Y9FS090pjjryZ5jjpg9WIZas3sajZkEm7iRdnK9A5AkpIKBDu+rzu xlXo0QRmvZiS3TjLV1PI/NU13JeEjveczfP3QhB4w8cNsseVKYBXXOgVDhbZ0ws9 hjs= 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 v5jKtVtkolw1; Sun, 20 May 2018 16:47:08 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40pnrD2CYvzDhBg; Sun, 20 May 2018 16:47:08 +0000 (UTC) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu, Warner Losh Cc: FreeBSD X11 mailing list , Current FreeBSD References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> From: Niclas Zeising Message-ID: <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> Date: Sun, 20 May 2018 18:47:07 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20180520164011.GA6276@troutmask.apl.washington.edu> 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.26 Precedence: 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, 20 May 2018 16:47:12 -0000 On 05/20/18 18:40, Steve Kargl wrote: > On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >>> On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: >>>> On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: >>>> >>>>> I propose that we remove the old drm2 driver (sys/dev/drm2) from >>>>> FreeBSD. I suggest the driver is marked as deprecated in 11.x and >>>>> removed from 12.0, as was done for other drivers recently. Some >>>>> background and rationale: >>>>> >>>> >>>> Sounds good ( deprecate resp remove ). It causes more confusion and >>>> problems and it solves nothing. >>>> >>> >>> Check the Makefiles >>> >>> % more /usr/ports/graphics/drm-next-kmod/Makefile >>> >>> ONLY_FOR_ARCHS= amd64 >>> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 >>> >>> Not to ia32 friendly. >>> >> >> So do people use i386 for desktop? And need the latest KMS stuff? >> > > Just a data point. I had to replace the dead disk in my laptop, > and after 2 days of doing a re-install and update of -current > on a shiny new SSD. > > Before loading Xorg. > > % kldstat > Id Refs Address Size Name > 1 7 0x800000 1ac31d4 kernel > 2 1 0x1e9ae000 5000 ums.ko > 3 1 0x1e9b9000 4000 uhid.ko > > After starting Xorg without an xorg.conf in /etc/X11. > > Id Refs Address Size Name > 1 27 0x800000 1ac31d4 kernel > 2 1 0x1e9ae000 5000 ums.ko > 3 1 0x1e9b9000 4000 uhid.ko > 4 1 0x1eaa9000 96000 i915kms.ko > 5 1 0x1eb40000 4a000 drm2.ko > 6 4 0x1eb8b000 5000 iicbus.ko > 7 1 0x1ebc9000 3000 iic.ko > 8 1 0x1ebcf000 4000 iicbb.ko > > So, drm2.ko and i915kms.ko are loaded automatically. It is > unclear why functionality that works should be removed. > > xwininfo shows > > Width: 1400 > Height: 1050 > Depth: 24 > Visual: 0x21 > One of the reasons for the deprecation and removal of the drm2 bits is that they prevent us from automatically loading the drm-next/stable-kmod kernel modules, since the two collide. Regards -- Niclas From owner-freebsd-current@freebsd.org Sun May 20 16:51: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 13FB0EE678B; Sun, 20 May 2018 16:51:45 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CBB285FF1; Sun, 20 May 2018 16:51:44 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id m17-v6so20567217lfj.8; Sun, 20 May 2018 09:51:44 -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=fFZ1lrnIC1JmwIZP3NQOFfiIh7wr6X/hNQwTOeCNyDU=; b=dhNdvJj+OEyFTCA9pnQGsWb/Dz11ULKpfEzikWqngoYf4HPlSp+I4qQdL9ZniP8Coj nNY1xtQaPaliqngTIkq4I6FVfIo5om4bWPcyt6sWc+/sFpfT7jectKxEVH6wktRqP5M9 cOMG704yRpZ6qhvDs2AuJgN0PaPjHZWy/6mUwYeaBbu5opPbT14Fk8B4PKZjkDp/KsaZ GfMoVGWZxlWYLX/8MRojoAa28zv+pvzJ1qBmywNvbsuIk0hMBOhFrff2AjuEQ6m2776X ANay5mPFPYizuq7sZbq/ny7wrCMPW92WeBqlmiirNN2hAXIrpmxGCenAsUazhYyJcmSj whlw== 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=fFZ1lrnIC1JmwIZP3NQOFfiIh7wr6X/hNQwTOeCNyDU=; b=MfA+GS40N7xqO4PBPFprlIPmGMYR7Iy5qbXR5rMHVpYNNOjtdmjKuZcgKVgTPwhI1y 6eiWfHqJBvN9iH0bthMoVP/ut3cVOA2MGbFbyM2f0RhDiSV4ffoRijmNLh5nvkNutB4n SPCa8W3R2IZg3nkCWOEF38GvFpMrFhwhvOPpgHi/IH+6AgpY0NVvELaKofKWAcQT3Chq uSccUD7hgLCZa/zEsaREUzYpUe+wQoP+CCrOAUSONYOXLomjO011zPBy2wh8XCc4+KzQ G927hmOlm05ZcODh77oCfrVTjoxD3KuSxsBcszE+lv8KEI5XsT6EET01S3mBUpAoaoh1 uM8A== X-Gm-Message-State: ALKqPwfvmzD6T+W0Ks61cO8yMtNxAMes2pj8GFXkUDvyBKpNpktCvHnW GHaI9ceA2l6CmLd63Qw4fwE= X-Google-Smtp-Source: AB8JxZooyBrt7c/i2s2STnRWSIvg4pN5AuabYg+q7RAVXkRkqRdhO2ZnpdN+vp+2/wGNlttf7emQxA== X-Received: by 2002:a19:c9d1:: with SMTP id z200-v6mr7541717lff.0.1526835102367; Sun, 20 May 2018 09:51:42 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id u8-v6sm2163804ljg.40.2018.05.20.09.51.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 20 May 2018 09:51:41 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sun, 20 May 2018 19:51:39 +0300 To: Johannes Lundberg Cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180520195139.2f981883@gmail.com> In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520172229.074a7004@gmail.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.26 Precedence: 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, 20 May 2018 16:51:45 -0000 On Sun, 20 May 2018 16:32:50 +0100 Johannes Lundberg wrote: > Not in the current port. > I think it should be usable in 4.15 but need some more tweaking and > updated firmware modules before we can update the port. > Active development going on here > https://github.com/FreeBSDDesktop/kms-drm/issues Thanks! What futures will avaible in 4.15 - 4.16? Video decoding acceleration? 3d acceleration? From owner-freebsd-current@freebsd.org Sun May 20 17:01: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 C50BEEE6D43; Sun, 20 May 2018 17:01:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FEDD86345; Sun, 20 May 2018 17:01:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4KH19lY006607 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 20 May 2018 10:01:09 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4KH19Mw006606; Sun, 20 May 2018 10:01:09 -0700 (PDT) (envelope-from sgk) Date: Sun, 20 May 2018 10:01:09 -0700 From: Steve Kargl To: Niclas Zeising Cc: Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180520170109.GA6488@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 17:01:21 -0000 On Sun, May 20, 2018 at 06:47:07PM +0200, Niclas Zeising wrote: > On 05/20/18 18:40, Steve Kargl wrote: > > On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >>> > >>> % more /usr/ports/graphics/drm-next-kmod/Makefile > >>> > >>> ONLY_FOR_ARCHS= amd64 > >>> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > >>> > >>> Not to ia32 friendly. > >>> > >> > >> So do people use i386 for desktop? And need the latest KMS stuff? > >> > > > > Just a data point. I had to replace the dead disk in my laptop, > > and after 2 days of doing a re-install and update of -current > > on a shiny new SSD. > > > > Before loading Xorg. > > > > % kldstat > > Id Refs Address Size Name > > 1 7 0x800000 1ac31d4 kernel > > 2 1 0x1e9ae000 5000 ums.ko > > 3 1 0x1e9b9000 4000 uhid.ko > > > > After starting Xorg without an xorg.conf in /etc/X11. > > > > Id Refs Address Size Name > > 1 27 0x800000 1ac31d4 kernel > > 2 1 0x1e9ae000 5000 ums.ko > > 3 1 0x1e9b9000 4000 uhid.ko > > 4 1 0x1eaa9000 96000 i915kms.ko > > 5 1 0x1eb40000 4a000 drm2.ko > > 6 4 0x1eb8b000 5000 iicbus.ko > > 7 1 0x1ebc9000 3000 iic.ko > > 8 1 0x1ebcf000 4000 iicbb.ko > > > > So, drm2.ko and i915kms.ko are loaded automatically. It is > > unclear why functionality that works should be removed. > > One of the reasons for the deprecation and removal of the drm2 bits is > that they prevent us from automatically loading the drm-next/stable-kmod > kernel modules, since the two collide. > Regards They do not collide on non-AMD64 architectures. Is is possible to do svn diff sys/modules/Makefile Index: sys/modules/Makefile =================================================================== --- sys/modules/Makefile (revision 333815) +++ sys/modules/Makefile (working copy) @@ -113,7 +113,9 @@ ${_dpms} \ ${_dpt} \ ${_drm} \ +.if ${MACHINE_ARCH} != AMD64 ${_drm2} \ +.endif dummynet \ ${_ed} \ ${_efirt} \ -- Steve From owner-freebsd-current@freebsd.org Sun May 20 19:10: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 0EFF3EECAA1 for ; Sun, 20 May 2018 19:10:30 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 966AC6BFFD for ; Sun, 20 May 2018 19:10:29 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw0-x233.google.com with SMTP id y123-v6so3907670ywa.5 for ; Sun, 20 May 2018 12:10:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pQDB7yEDy1e7vBYVbc692HnYBMdq3Z4OR+mPXH6Mnic=; b=mN+Rokj+OtNe65hUYqTLpJX0em9yiFPlzToNoLwtf8oQlDRhaEfFLS+PR72jsqufdt WaK8e10Z3PRr4i7hCxONeLCs99hMCRZhjjA7Ysibr7bu9VpB/Cudd5zfitE1iDKT88WH 6v5NjJ1Z8FOYpY0BI3rnhUXG+pPPOhqzE43g89lpRCpTOLp5A4B/hUvCoTri77lzkGJ0 2bukIzqPVocnNjVNSYaUgiAz2qFy+r0cn+sVu63Ap35v5lrKO/XiIgJQ0jjP7DF0xj88 1folF8ZYbLVjVlo34dMVaD33cWuYi6ZgPRxZ7Zc1jiDGsfyS6aZ89LCYdG7JzKqgVQ21 IMVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pQDB7yEDy1e7vBYVbc692HnYBMdq3Z4OR+mPXH6Mnic=; b=fA5q3NzLuC/AqOWops4ZocCnHpzzbk4G/N2FBMTcqsOHbSTIhUkt0gmv/6H79rJes9 ygruxkDU4HvCv50NGbOnpTYo738GX5lTOX1vKFlkd9UOtPZTMxrmwt3zKVCuBbMzy3ae 3NOSUfz7iORbFxHdwv+M6m8sTAx/21cIBavWz9+mjumhK6sKsvGUKa99JJ3Xyj9Snnz2 fNBGXEZuDlzj+T+tKnrZBNXaUBcys4pwQw7tVjxKTV+2ExnEb6k3ugFkoFM94k/V0bKs aClip3Wl41Tkz73uoZZ0DfWpYmpO2qOiSXmnfsZv/DgXhmk+hpg0+FXPucAGh/xym8c/ Slgg== X-Gm-Message-State: ALKqPwdHO9LJiN2JfrWY0jQIKoiZaWcvIWrAs2vkQ/ett5SA4F84xMnI P+IsUTWTMovTttfA0PAM6fLiA0spFxHm6sBCrAKkYg== X-Google-Smtp-Source: AB8JxZq4Xj6jjI9LbFnetHrT4Np9cZc3POo2176K/0Isoq0Rc+aphia5yfL0xBsPGVeGAOaMMdOFmH+Mer1AhPtjEqo= X-Received: by 2002:a81:6905:: with SMTP id e5-v6mr8710791ywc.265.1526843428889; Sun, 20 May 2018 12:10:28 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Sun, 20 May 2018 12:10:28 -0700 (PDT) In-Reply-To: <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> From: Oliver Pinter Date: Sun, 20 May 2018 21:10:28 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Niclas Zeising Cc: "sgk@troutmask.apl.washington.edu" , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 20 May 2018 19:10:30 -0000 On Sunday, May 20, 2018, Niclas Zeising wrote: > On 05/20/18 18:40, Steve Kargl wrote: > >> On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: >> >>> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >>> sgk@troutmask.apl.washington.edu> wrote: >>> >>> On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: >>>> >>>>> On Fri, May 18, 2018, 20:00 Niclas Zeising >>>>> wrote: >>>>> >>>>> I propose that we remove the old drm2 driver (sys/dev/drm2) from >>>>>> FreeBSD. I suggest the driver is marked as deprecated in 11.x and >>>>>> removed from 12.0, as was done for other drivers recently. Some >>>>>> background and rationale: >>>>>> >>>>>> >>>>> Sounds good ( deprecate resp remove ). It causes more confusion and >>>>> problems and it solves nothing. >>>>> >>>>> >>>> Check the Makefiles >>>> >>>> % more /usr/ports/graphics/drm-next-kmod/Makefile >>>> >>>> ONLY_FOR_ARCHS= amd64 >>>> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on >>>> amd64 >>>> >>>> Not to ia32 friendly. >>>> >>>> >>> So do people use i386 for desktop? And need the latest KMS stuff? >>> >>> >> Just a data point. I had to replace the dead disk in my laptop, >> and after 2 days of doing a re-install and update of -current >> on a shiny new SSD. >> >> Before loading Xorg. >> >> % kldstat >> Id Refs Address Size Name >> 1 7 0x800000 1ac31d4 kernel >> 2 1 0x1e9ae000 5000 ums.ko >> 3 1 0x1e9b9000 4000 uhid.ko >> >> After starting Xorg without an xorg.conf in /etc/X11. >> >> Id Refs Address Size Name >> 1 27 0x800000 1ac31d4 kernel >> 2 1 0x1e9ae000 5000 ums.ko >> 3 1 0x1e9b9000 4000 uhid.ko >> 4 1 0x1eaa9000 96000 i915kms.ko >> 5 1 0x1eb40000 4a000 drm2.ko >> 6 4 0x1eb8b000 5000 iicbus.ko >> 7 1 0x1ebc9000 3000 iic.ko >> 8 1 0x1ebcf000 4000 iicbb.ko >> >> So, drm2.ko and i915kms.ko are loaded automatically. It is >> unclear why functionality that works should be removed. >> >> xwininfo shows >> >> Width: 1400 >> Height: 1050 >> Depth: 24 >> Visual: 0x21 >> >> > One of the reasons for the deprecation and removal of the drm2 bits is > that they prevent us from automatically loading the drm-next/stable-kmod > kernel modules, since the two collide. > Regards Then it wold be better to resolve this problem, rather then removing a working solution. What's about module versioning what in other cases works? > -- > Niclas > _______________________________________________ > 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 May 20 23:40: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 42CAAEF3FA2; Sun, 20 May 2018 23:40:55 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96F1E76C71; Sun, 20 May 2018 23:40:54 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id b18-v6so21302365lfa.9; Sun, 20 May 2018 16:40:54 -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=a2FOG+co3eiWqi55TC0EONZtQltFKpuCmvkZzjkoZIs=; b=WY1w8U8Xa3HP4rOOLEPmd/6LEOoQrAwqj619+7v6WFp8ly1j8EvMYqjByaweSyW+gE J5DSQMX1LopG9qmxv6ZiAuURRMzEWJBKHXPS/oEzodfRTCPTD+vU4EfDlDno1kbKEVDK tBRTzIaPbBr5GEwxLcqi2VT8FujjLk6VMuvSyvHx/rxCqlHpsO3/bUVTNvu9KB9zozLD Q0a4p7RA1CovL0LwOTEqP0gsXC57Yrqab7dGBC494daqfD09DAStigrSaltI36tR2rFL nlrT51OabgGmhcxlPXDJWlyGNJ8lwNqa1jANP2tcxNYm5RVoiIdK3yCPi/EIdN59zo9/ hdjw== 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=a2FOG+co3eiWqi55TC0EONZtQltFKpuCmvkZzjkoZIs=; b=ECNjyDsHHB9/LQEbUmy/beWAjUVmr2jD5VIE/XLwMsJ3FbO/yn1LJDICZuKbuKE4kk 1JTpkxuSQM4QDILk35NhInp7qazFZ1UrNUrMa6nFuHBZx5R1OVyop2nBkOcIAA4LjEGb 1JvtVzPFYRqg+fF50qCaPHtPkMzTrOfrIK75WNkJFJcEmPUkClE80jBdUrWPXMveXcB0 uVN4yYYOEFz5TMfalU988o/xyxjKnUgMGLtTZNC8+FuAmNCfxDLBbnSDtF8DbDpcDTuK 8sR9N0l3xX9R63ihX+Sl9emg7AGZMPAYab/472d2fFkwTn6mAJJJcgYP19hRsiXfF2o0 ZMiQ== X-Gm-Message-State: ALKqPwdUezho7t2fJjh/mSgfgGJB2wcnVrEPgGtEepS5TqNll3SnPiSz J/6tkswxHAGQr5s1zVWVZjvs2NCY X-Google-Smtp-Source: AB8JxZp/pN/fgNl2e4vRPhGqpF5xdTS/J1SwT/vl61mm4/AWcLx+1mr7M2/ODMILel5WgQEWCkaSKA== X-Received: by 2002:a2e:81d0:: with SMTP id s16-v6mr11223919ljg.115.1526859652976; Sun, 20 May 2018 16:40:52 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id s16-v6sm546460lfg.74.2018.05.20.16.40.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 20 May 2018 16:40:52 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Mon, 21 May 2018 02:40:50 +0300 To: Oliver Pinter Cc: Niclas Zeising , "sgk@troutmask.apl.washington.edu" , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521024050.0857a787@gmail.com> In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.26 Precedence: 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, 20 May 2018 23:40:55 -0000 On Sun, 20 May 2018 21:10:28 +0200 Oliver Pinter wrote: > > One of the reasons for the deprecation and removal of the drm2 bits > > is that they prevent us from automatically loading the > > drm-next/stable-kmod kernel modules, since the two collide. > > Regards > > > Then it wold be better to resolve this problem, rather then removing a > working solution. What's about module versioning what in other cases > works? > May be just move old drm2 to ports? From owner-freebsd-current@freebsd.org Mon May 21 02:36: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 02584EB0653 for ; Mon, 21 May 2018 02:36:11 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic303-2.consmr.mail.bf2.yahoo.com (sonic303-2.consmr.mail.bf2.yahoo.com [74.6.131.41]) (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 9F684682E8 for ; Mon, 21 May 2018 02:36:10 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: evcxcVEVM1kzBZ3kVH5bdlEEvSBEjLTs9f2.wAP9zBT0MXTzqpE4KZ2LDbdZ_RO WmmzQ5q3pSTw4_1RgXknrkd_tMGabVBPMSW3qIbeKFremflVNBqOOuQzTNuC_E5Du1apsIsDZ_Dz 6mc8IkpSpZcBfiij3B1DOPXjdg5oEpOTlDWaC3rSpcyPmP6a3KJSS2TTybDcVyd4WLgEVkBwCvpX 3OG79uBC56688RnNF5K.5PqMDCOJhovmmK.Df90u4Hfr3zsxhojbedJATkNIfizQq6nHn35CJ55B 5W.3j.vmxJdrTjPJ5q9P2vw_HBJLFyOLSE8glRjU_xRztVBgohrTBRcb0Xx7vcBCFvUsQvwKEF2K iJhe7IqniRayU7YP1cb6tUqGC3R2316pdIIdQ_7U_GlOtH7GtChzjboIuXLUtYHZXPrmVOPULn8F c66v2_JDNgcZ1l.u._Q31.ACa6QlUCEp_2WwVA23MYnsAulAM95Ec83iQwtgac2U2ykw4KUavy6V Kulr3_0XvX5h2UZ_KA.5PoQ4q9qqh2tMu5VAR8bzB1V.IgQDJ_UmhmJ9Qm0cdOa671atbeFBa5sr vRdHjRWE0IivxOqMYRLwy4.VyXxJmcISj2HIWwR_tBN3pjjJOCqaAVufpkt0wag_QIwAU95SEsHZ MLQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.bf2.yahoo.com with HTTP; Mon, 21 May 2018 02:36:04 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp418.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8068c5af76baad787dd8d5e03236a84c; Mon, 21 May 2018 02:36:00 +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.3 \(3445.6.18\)) Subject: head -r333946(?) broke many builds Message-Id: <3987ED2D-39CA-42F8-87EF-A776F91D2931@yahoo.com> Date: Sun, 20 May 2018 19:35:58 -0700 To: Eitan Adler , FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 02:36:11 -0000 ci.freebsd.org shows -r333945 built okay (ignoring riscv64) but later not ( -r333947 and later for most). --- all_subdir_usr.bin/top --- make[4]: make[4]: don't know how to make top.local.h. Stop make[4]: stopped in /usr/src/usr.bin/top *** [all_subdir_usr.bin/top] Error code 2 > Author: eadler > Date: Sun May 20 23:37:30 2018 > New Revision: 333946 > URL: > https://svnweb.freebsd.org/changeset/base/333946 > > > Log: > top(1): pull configuration directly into header files > > . . . Interestingly FreeBSD-head-aarch64-build is not broken at -r333947 but is later at -r333949 --for the same error: --- all_subdir_usr.bin --- make[4]: make[4]: don't know how to make top.local.h. Stop make[4]: stopped in /usr/src/usr.bin/top *** [all_subdir_usr.bin/top] Error code 2 === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon May 21 03:31: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 C97ABEB1B20 for ; Mon, 21 May 2018 03:31:53 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic315-15.consmr.mail.bf2.yahoo.com (sonic315-15.consmr.mail.bf2.yahoo.com [74.6.134.125]) (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 6FED76A083 for ; Mon, 21 May 2018 03:31:53 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: FnQsX9YVM1lSu4p29Ht0GOWTdI7VOYfSNgJmpCjB0r4.uInZHhvkmOlXY4J44ux 2kZ3CGH.IEsavFrog.SSx.HxKfKQoAWcP2mFEBY1znjJNBNk1Fsn8wxDJ_uEFyYnLBfcXReRpCLq xS8D6VCEWh.jPmZ17uvXN2I8JIaKw2QwgHqpYBVPz2V1bIkKe041vauBQBOiCYDJHhM1q359vbkA k0JRpnPX9jniJ7AM6BR0PAth65RqaOSulRkyLRluXqKiMb6w1fx2gVE2vg3j5aNDhgPRuLnMBn5w WlHEZOQy8chozYI1d5t2T504ZMZZu1QKaS3pc789C_9GM.vrxS5AOSNjjn_jbIkF_q35Gs6VwxcL n0WL5Up.Ajv.7Th24p9dsSLF_gO_gVWNfMzTkX2bxh3CsDCh5Ti14Pu_nz0BZrnh9eI0OoeU85Di dDQcoI6.JGgr53gBlLsX4Y7l3qm402er9zgvFb2wQKlyh5Co6oJZNdP_r_etQak9.gVZGSh3qG5I cV6kbiHlxFJgk2ZSDPRrnlZY8LQPqer3iZo2c8_crPWzhiskS3Kll1XZ34KWNSxUpOQ3dxEGsgoh JgE.pKOtaFJSj0ugc3WROUIwNRj53O9wgv1MQrECkV92.cSBCelTuvrSFE0fFqnb_c1vJJXuiDOH pFQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Mon, 21 May 2018 03:31:51 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp425.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 57b737587faea3341e4aa7d35376e9fc; Mon, 21 May 2018 03:31:44 +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.3 \(3445.6.18\)) Subject: Re: head -r333946(?) broke many builds Date: Sun, 20 May 2018 20:31:42 -0700 References: <3987ED2D-39CA-42F8-87EF-A776F91D2931@yahoo.com> To: Eitan Adler , FreeBSD Current In-Reply-To: <3987ED2D-39CA-42F8-87EF-A776F91D2931@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 03:31:54 -0000 On 2018-May-20, at 7:35 PM, Mark Millard = wrote: > ci.freebsd.org shows -r333945 built okay (ignoring riscv64) but > later not ( -r333947 and later for most). >=20 > --- all_subdir_usr.bin/top --- > make[4]: make[4]: don't know how to make top.local.h. Stop >=20 > make[4]: stopped in /usr/src/usr.bin/top > *** [all_subdir_usr.bin/top] Error code 2 >=20 >=20 >> Author: eadler >> Date: Sun May 20 23:37:30 2018 >> New Revision: 333946 >> URL:=20 >> https://svnweb.freebsd.org/changeset/base/333946 >>=20 >>=20 >> Log: >> top(1): pull configuration directly into header files >>=20 >> . . . >=20 >=20 >=20 > Interestingly FreeBSD-head-aarch64-build is not broken > at -r333947 but is later at -r333949 --for the same > error: >=20 > --- all_subdir_usr.bin --- > make[4]: make[4]: don't know how to make top.local.h. Stop >=20 > make[4]: stopped in /usr/src/usr.bin/top > *** [all_subdir_usr.bin/top] Error code 2 >=20 In my own builds it looks like WITH_META_MODE=3D does not deal with top having moved. The builds did not fail because they found and used an old top.local.h in my /usr/obj/ areas for the various build targets that I tried. For example: # ls -lTt = /usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/usr.bin/top/ total 928 . . . -rw-r--r-- 1 root wheel 1017 Nov 3 00:11:28 2017 top.local.h.meta -rw-r--r-- 1 root wheel 2418 Nov 3 00:11:28 2017 top.local.h FBSDFSSD# more = /usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/usr.bin/top/top.local= .h.meta # Meta data file = /usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/usr.bin/top/top.local= .h.meta CMD @echo Making top.local.h from /usr/src/contrib/top/top.local.hs CMD @sed -e's,%LoadMax%,5.0,g' -e's,%TableSize%,20011,g' = -e's,%NominalTopn%,18,g' -e's,%topn%,-1,g' -e's,%delay%,2,g' = -e's,%random%,1,g' /usr/src/contrib/top/top.local.hs > top.local.h CWD /usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/usr.bin/top TARGET top.local.h -- command output -- Making top.local.h from /usr/src/contrib/top/top.local.hs -- filemon acquired metadata -- # filemon version 5 # Target pid 10130 # Start 1509693088.899769 V 5 E 10133 /bin/sh R 10133 /etc/libmap.conf R 10133 /var/run/ld-elf.so.hints R 10133 /lib/libedit.so.7 R 10133 /lib/libc.so.7 R 10133 /lib/libncursesw.so.8 F 10133 10134 W 10134 top.local.h E 10134 /usr/bin/sed R 10134 /etc/libmap.conf R 10134 /var/run/ld-elf.so.hints R 10134 /lib/libc.so.7 R 10134 /usr/src/contrib/top/top.local.hs X 10134 0 0 X 10133 0 0 # Stop 1509693088.899769 # Bye bye was still around for the #include's to find. May be something like this explains FreeBSD-head-aarch64-build initially not failing. After a move (such as happened for top) forcing a full rebuild "form scratch" seems to be required for testing if the build process is working. =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 May 21 08:44: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 CFF57EE88B3 for ; Mon, 21 May 2018 08:44:14 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CDDE74304 for ; Mon, 21 May 2018 08:44:14 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f45.google.com with SMTP id h197-v6so22707202lfg.11 for ; Mon, 21 May 2018 01:44:14 -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=FS8rzNWQ6w3WJCvAr1uHckcchBrp54nmcZNg+zh1tyo=; b=Vrcq76Yx5H30wh5/GBWOayclwJJm9k7ajKiXtyntG6yMYxOc8LnFpTB4YXcvL50Fxi 79Y0lXrcnVeNh1rvLWzGiUyWqfDzVyY7/jK5cAbwEECD6UjolJyTVNGm+Jn19uY+IqkC OwWluWhyYR+0CwuprmO1lfNnQCN1iMXdf8CaS8nco2a2mDVvUOwach7hyi7z4GCuJx6+ LzX+CtcVJ543Dmc1wAT7tCs5tdu0ia7eEWJi4PTOIMUCVeTsEMT+1vijy5oxQDIBiNDI r5BI5GXVhe3TxN8kHEwQJqEEt7g8CQd6YRWyXt4SQsOvyYAYUPPZgUck+jAxtxdcZCTW VZiA== X-Gm-Message-State: ALKqPwcAcay3HVY4SqGCzWQ8GV+kN5V3fk2OWup/v9i6aE0rPaj63cRe H+/hZBbEMnu2BHf8WNMV50ympfUS X-Google-Smtp-Source: AB8JxZpjzJga+Vl6u5eYxUB5AcwG/fPBQg70VW897634+eQYQ/uauinLBQphv26fiB04CYHP7HrVcA== X-Received: by 2002:a2e:3503:: with SMTP id z3-v6mr11924110ljz.95.1526892247324; Mon, 21 May 2018 01:44:07 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id k5-v6sm2415571lji.39.2018.05.21.01.44.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 May 2018 01:44:06 -0700 (PDT) To: FreeBSD Current From: Andriy Gapon Subject: panic: vm_phys_free_pages: page 0x... has unexpected order 0 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: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> Date: Mon, 21 May 2018 11:44:05 +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.26 Precedence: 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, 21 May 2018 08:44:15 -0000 FreeBSD 12.0-CURRENT amd64 r332472 Does this panic ring a bell to anyone? Has it already been fixed? Thank you! panic: vm_phys_free_pages: page 0xfffff80cbfb71958 has unexpected order 0 cpuid = 3 time = 1526822662 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe017547c340 vpanic() at vpanic+0x18d/frame 0xfffffe017547c3a0 doadump() at doadump/frame 0xfffffe017547c420 vm_phys_free_pages() at vm_phys_free_pages+0x253/frame 0xfffffe017547c450 vm_page_free_phys_pglist() at vm_page_free_phys_pglist+0x37/frame 0xfffffe017547c470 vm_object_terminate() at vm_object_terminate+0x405/frame 0xfffffe017547c4d0 vm_object_deallocate() at vm_object_deallocate+0x45c/frame 0xfffffe017547c530 vm_map_process_deferred() at vm_map_process_deferred+0x99/frame 0xfffffe017547c560 vm_map_remove() at vm_map_remove+0xc6/frame 0xfffffe017547c590 exec_new_vmspace() at exec_new_vmspace+0x185/frame 0xfffffe017547c5f0 exec_elf64_imgact() at exec_elf64_imgact+0x907/frame 0xfffffe017547c6e0 kern_execve() at kern_execve+0x82c/frame 0xfffffe017547ca40 sys_execve() at sys_execve+0x4c/frame 0xfffffe017547cac0 amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe017547cbf0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe017547cbf0 -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon May 21 17:07: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 F2578EF8F50; Mon, 21 May 2018 17:07:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8126587467; Mon, 21 May 2018 17:07:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4LH7TRL014115 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 21 May 2018 10:07:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4LH7StF014114; Mon, 21 May 2018 10:07:28 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 May 2018 10:07:28 -0700 From: Steve Kargl To: Rozhuk Ivan Cc: Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521170728.GA14025@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180521024050.0857a787@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 17:07:48 -0000 On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > On Sun, 20 May 2018 21:10:28 +0200 > Oliver Pinter wrote: > > > > One of the reasons for the deprecation and removal of the drm2 bits > > > is that they prevent us from automatically loading the > > > drm-next/stable-kmod kernel modules, since the two collide. > > > Regards > > > > > > Then it wold be better to resolve this problem, rather then removing a > > working solution. What's about module versioning what in other cases > > works? > > > > May be just move old drm2 to ports? Why? "If it isn't broken, why fix it?" The conflict affects x86_64-*-freebsd aka amd64. The conflict does not affect any other architecture. The Makefile infrastructure can use MACHINE_ARCH to exclude drm2 from build of amd64. I don't use netgraph or any of the if_*.ko modules. Can we put all of that into ports? I don't use any scsi controllers, so those can go too. Why make it insanely fun for users to configure a FreeBSD system. -- Steve From owner-freebsd-current@freebsd.org Mon May 21 17:29: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 67C05EFA530; Mon, 21 May 2018 17:29:57 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::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 CCB9168AC9; Mon, 21 May 2018 17:29:56 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.187] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e7e814d4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 21 May 2018 10:29:55 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu, Rozhuk Ivan Cc: Niclas Zeising , FreeBSD X11 mailing list , Current FreeBSD , Warner Losh , Oliver Pinter References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> From: Pete Wright Message-ID: Date: Mon, 21 May 2018 10:29:54 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> 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.26 Precedence: 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, 21 May 2018 17:29:57 -0000 On 05/21/2018 10:07, Steve Kargl wrote: > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> On Sun, 20 May 2018 21:10:28 +0200 >> Oliver Pinter wrote: >> >>>> One of the reasons for the deprecation and removal of the drm2 bits >>>> is that they prevent us from automatically loading the >>>> drm-next/stable-kmod kernel modules, since the two collide. >>>> Regards >>> >>> Then it wold be better to resolve this problem, rather then removing a >>> working solution. What's about module versioning what in other cases >>> works? >>> >> May be just move old drm2 to ports? > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to exclude > drm2 from build of amd64. > > I don't use netgraph or any of the if_*.ko modules. > Can we put all of that into ports? I don't use any > scsi controllers, so those can go too. Why make it > insanely fun for users to configure a FreeBSD system. to play devils advocate - why include a kernel module that causes conflicts for a vast majority of the laptop devices that you can purchase today (as well as for the foreseeable future), while forcing the up to date and actively developed driver to not work out of the box? IMHO it is issues like this (having out of date code that supports some edge cases) which makes it harder for developers to dog-food the actual OS they are developing on.  Having things work on modern hardware by default seems like a great way to get more people on the platform testing and bugfixing things. The suggestion seems like a pretty good middle ground, people with older devices will still have workable code while also making it easier to continue to follow the state of the art in terms of hardware support. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Mon May 21 18:09: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 46C43EFB22E; Mon, 21 May 2018 18:09:21 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 E00806A2CB; Mon, 21 May 2018 18:09:19 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w4LI5oDk090972; Mon, 21 May 2018 11:05:56 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "Niclas Zeising" , "FreeBSD X11 mailing list" , " Current FreeBSD" , " Warner Losh" , " Oliver Pinter" , , "Rozhuk Ivan" In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Pete Wright" Subject: Re: [RFC] Deprecation and removal of the drm2 driver Date: Mon, 21 May 2018 11:05:56 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 18:09:21 -0000 On Mon, 21 May 2018 10:29:54 -0700 "Pete Wright" said > On 05/21/2018 10:07, Steve Kargl wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter wrote: > >> > >>>> One of the reasons for the deprecation and removal of the drm2 bits > >>>> is that they prevent us from automatically loading the > >>>> drm-next/stable-kmod kernel modules, since the two collide=2E > >>>> Regards > >>> > >>> Then it wold be better to resolve this problem, rather then removing = a > >>> working solution=2E What's about module versioning what in other cases > >>> works? > >>> > >> May be just move old drm2 to ports? > > Why? "If it isn't broken, why fix it?" > > > > The conflict affects x86_64-*-freebsd aka amd64=2E The > > conflict does not affect any other architecture=2E The > > Makefile infrastructure can use MACHINE_ARCH to exclude > > drm2 from build of amd64=2E > > > > I don't use netgraph or any of the if_*=2Eko modules=2E > > Can we put all of that into ports? I don't use any > > scsi controllers, so those can go too=2E Why make it > > insanely fun for users to configure a FreeBSD system=2E > to play devils advocate - why include a kernel module that causes=20 > conflicts for a vast majority of the laptop devices that you can=20 > purchase today (as well as for the foreseeable future), while forcing=20 > the up to date and actively developed driver to not work out of the box? >=20 > IMHO it is issues like this (having out of date code that supports some= =20 > edge cases) which makes it harder for developers to dog-food the actual= =20 > OS they are developing on=2E=C2=A0 Having things work on modern hardware by= =20 > default seems like a great way to get more people on the platform=20 > testing and bugfixing things=2E >=20 > The suggestion seems like a pretty good middle ground, people with older= =20 > devices will still have workable code while also making it easier to=20 > continue to follow the state of the art in terms of hardware support=2E >=20 > -pete Along the lines of Devils advocate; Why do *any* get "special" attention? Why does Intel get all the love? None of my nVidia cards get this; granted they're blobs=2E But I've been waiting ~1yr=2E for support for my AMD GPU to be supported=2E IOW why not make all of them a port? IMHO vt(4) , while a nice *initial* ef= fort=2E Still falls *far* short of sc(ons)=2E It's no big deal to whip up a custom ke= rnel with support for your chosen video card/APU/GPU=2E Then there can be less complaints about "favoritism" -- everyone is treated equally=2E Why must the stock (GENERIC) kernel support "graphics mode" out-of-the-box? It appears to me; at this stage; or the *proposed* stage; that Intel will b= e the only _well supported_ hardware out-of-the-box=2E tl;dr; Make all video cards/APU/GPU support come from ports/kernel OPTIONS_KNOBS Thanks for your indulgence=2E --Chris >=20 > --=20 > Pete Wright > pete@nomadlogic=2Eorg > @nomadlogicLA >=20 > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= " From owner-freebsd-current@freebsd.org Mon May 21 18:11: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 C363BEFB331 for ; Mon, 21 May 2018 18:11:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 50E866A4B3 for ; Mon, 21 May 2018 18:11:02 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4LIAvv5000455 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 21 May 2018 11:10:57 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4LIAvlR000454; Mon, 21 May 2018 11:10:57 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 May 2018 11:10:57 -0700 From: Steve Kargl To: Pete Wright Cc: Rozhuk Ivan , Niclas Zeising , FreeBSD X11 mailing list , Current FreeBSD , Warner Losh , Oliver Pinter Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521181057.GA86707@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 18:11:03 -0000 On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: > > On 05/21/2018 10:07, Steve Kargl wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter wrote: > >> > >>>> One of the reasons for the deprecation and removal of the drm2 bits > >>>> is that they prevent us from automatically loading the > >>>> drm-next/stable-kmod kernel modules, since the two collide. > >>>> Regards > >>> > >>> Then it wold be better to resolve this problem, rather then removing a > >>> working solution. What's about module versioning what in other cases > >>> works? > >>> > >> May be just move old drm2 to ports? > > Why? "If it isn't broken, why fix it?" > > > > The conflict affects x86_64-*-freebsd aka amd64. The > > conflict does not affect any other architecture. The > > Makefile infrastructure can use MACHINE_ARCH to exclude > > drm2 from build of amd64. > > > > I don't use netgraph or any of the if_*.ko modules. > > Can we put all of that into ports? I don't use any > > scsi controllers, so those can go too. Why make it > > insanely fun for users to configure a FreeBSD system. > to play devils advocate - why include a kernel module that causes > conflicts for a vast majority of the laptop devices that you can > purchase today (as well as for the foreseeable future), while forcing > the up to date and actively developed driver to not work out of the box? Poor advocacy. I stated old drm2 can be excluded by the Makefile infrastructure and I've already provided a barebones patch. Index: sys/modules/Makefile =================================================================== --- sys/modules/Makefile (revision 333609) +++ sys/modules/Makefile (working copy) @@ -112,7 +112,9 @@ ${_dpms} \ ${_dpt} \ ${_drm} \ +.if ${MACHINE_ARCH} != amd64 ${_drm2} \ +.endif dummynet \ ${_ed} \ ${_efirt} \ Those interested in killing old drm2 on amd64 can add the requisite .if ... .endif to remove obsolscent *.ko. > IMHO it is issues like this (having out of date code that supports some > edge cases) which makes it harder for developers to dog-food the actual > OS they are developing on. You're talking to 1 of the 3 contributors that has tried over the last 2 decades to improve libm (both its quality and conformance to standards). The development and testing is done on my old i386 laptop (which happily uses drm2), my amd64 systems, and at one time sparc64 (flame.freebsd.org). So, yeah, i386 and sparc64 allowed me to dog-food my code. BTW, there are uncountable many integers. How about avoiding the conflict by using, say, '3' as in drm3. -- Steve From owner-freebsd-current@freebsd.org Mon May 21 18:25: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 43DF6EFBA00 for ; Mon, 21 May 2018 18:25:43 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x244.google.com (mail-yb0-x244.google.com [IPv6:2607:f8b0:4002:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE5F76AFDF for ; Mon, 21 May 2018 18:25:42 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x244.google.com with SMTP id y3-v6so1249480ybb.2 for ; Mon, 21 May 2018 11:25:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Akr6cKl8A/LFaHB1TaE6UwlVKhvTpBE3ZjNeYqRH2jo=; b=ouONIihlSFFSWlmlNO2Pj08rHw6glqLvCTA3f3ybdjgs9hTPM4qZnLLSskWKpmn9WY wmr0iNWJweO6vPw04pPKWyjntN6O5uAO+/qXpvFCnrAsiSklPJIi6Vub7U9mTyo4X0dV GaE3Fy48jqTXQmRQVk3h0GzgbpzUY5o2aR6tEPBqF6uAv9mhHOf420xGAUo3ZlgqY1dK ppVAJjNECejOTeuXfGkMzrvfQCNERANgJ3PU5Jndo1j5FMq8WOGO/wEGI5pLmHC9sShY Ofj5KN+91Fg5NWKWdS7ami4ekhg6fedxkaqk0ZczCSedtULhdgOYuE/Dqa/5IHwfRSYb aofw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Akr6cKl8A/LFaHB1TaE6UwlVKhvTpBE3ZjNeYqRH2jo=; b=J2eHXXBxDqaK5uDTD5UOfMKn79VESHKdQiR9ui9LhJmSVGVUNzpEld74gyLsO3zSEM TPcRjJ0V2GCiJyDcox9YkFdUS6q4HnLgBUN3QuHhkxIyLEjsO6QDacQnauo51gbwGFFf r6xjDBc1tmVU8TSwuQqHl3W+VL1wTSlbjegdXHcyPJo0gCT/Zq+mVC/bHlc/JDPwlY96 ZECoa/huW/C1RKDmnnGNVF0KACPjlMADAA9QrWAv9IdSmIF+nLeRt9Me86INvSmr6Hlb Tyh8ffcNqtZycWX7Ub9sbpU09aL+w37m6xx/ejHKoQ4k8bgFOBxfYsQK6IZ9ElMeECbG PRmA== X-Gm-Message-State: ALKqPwcWy+Y5L/s9djsb1PuUlZPZLAVBhaTYRs1ZPBeoiSrAXFOrUS3Z QjwS3B1VVec7N3BorcBi4YR7MAQ6V4UDHqZhv9AJ9A== X-Google-Smtp-Source: AB8JxZooYVENYujBJ5n3dVKZRDUaNXBt47I6K1ui6gegrL6FwUnl6FLsVgDsvV/cUy+NqLGzaeqHNQa14EdirVldSe0= X-Received: by 2002:a25:bc06:: with SMTP id i6-v6mr3567180ybh.348.1526927142108; Mon, 21 May 2018 11:25:42 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Mon, 21 May 2018 11:25:41 -0700 (PDT) In-Reply-To: <20180521181057.GA86707@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180521181057.GA86707@troutmask.apl.washington.edu> From: Oliver Pinter Date: Mon, 21 May 2018 20:25:41 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Pete Wright , Rozhuk Ivan , Niclas Zeising , FreeBSD X11 mailing list , Current FreeBSD , Warner Losh Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 18:25:43 -0000 On 5/21/18, Steve Kargl wrote: > On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: >> >> On 05/21/2018 10:07, Steve Kargl wrote: >> > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> >> On Sun, 20 May 2018 21:10:28 +0200 >> >> Oliver Pinter wrote: >> >> >> >>>> One of the reasons for the deprecation and removal of the drm2 bits >> >>>> is that they prevent us from automatically loading the >> >>>> drm-next/stable-kmod kernel modules, since the two collide. >> >>>> Regards >> >>> >> >>> Then it wold be better to resolve this problem, rather then removing >> >>> a >> >>> working solution. What's about module versioning what in other cases >> >>> works? >> >>> >> >> May be just move old drm2 to ports? >> > Why? "If it isn't broken, why fix it?" >> > >> > The conflict affects x86_64-*-freebsd aka amd64. The >> > conflict does not affect any other architecture. The >> > Makefile infrastructure can use MACHINE_ARCH to exclude >> > drm2 from build of amd64. >> > >> > I don't use netgraph or any of the if_*.ko modules. >> > Can we put all of that into ports? I don't use any >> > scsi controllers, so those can go too. Why make it >> > insanely fun for users to configure a FreeBSD system. >> to play devils advocate - why include a kernel module that causes >> conflicts for a vast majority of the laptop devices that you can >> purchase today (as well as for the foreseeable future), while forcing >> the up to date and actively developed driver to not work out of the box? > > Poor advocacy. I stated old drm2 can be excluded by the > Makefile infrastructure and I've already provided a barebones > patch. > > Index: sys/modules/Makefile > =================================================================== > --- sys/modules/Makefile (revision 333609) > +++ sys/modules/Makefile (working copy) > @@ -112,7 +112,9 @@ > ${_dpms} \ > ${_dpt} \ > ${_drm} \ > +.if ${MACHINE_ARCH} != amd64 > ${_drm2} \ > +.endif > dummynet \ > ${_ed} \ > ${_efirt} \ I prefer something like this: op@opn src# git diff diff --git a/sys/amd64/conf/GENERIC b/sys/amd64/conf/GENERIC index 195b66daab51..034e2f8126fd 100644 --- a/sys/amd64/conf/GENERIC +++ b/sys/amd64/conf/GENERIC @@ -23,6 +23,7 @@ ident GENERIC makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols makeoptions WITH_CTF=1 # Run ctfconvert(1) for DTrace support +makeoptions WITHOUT_MODULES="drm drm2" # by default disable the building of DRM* for GENERIC options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption > > Those interested in killing old drm2 on amd64 can add the > requisite .if ... .endif to remove obsolscent *.ko. > >> IMHO it is issues like this (having out of date code that supports some >> edge cases) which makes it harder for developers to dog-food the actual >> OS they are developing on. > > You're talking to 1 of the 3 contributors that has tried over > the last 2 decades to improve libm (both its quality and > conformance to standards). The development and testing is > done on my old i386 laptop (which happily uses drm2), my > amd64 systems, and at one time sparc64 (flame.freebsd.org). > So, yeah, i386 and sparc64 allowed me to dog-food my code. > > BTW, there are uncountable many integers. How about avoiding > the conflict by using, say, '3' as in drm3. > > -- > Steve > From owner-freebsd-current@freebsd.org Mon May 21 18:40: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 777FBEFBD8C for ; Mon, 21 May 2018 18:40:52 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x241.google.com (mail-yb0-x241.google.com [IPv6:2607:f8b0:4002:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A3396B5C8 for ; Mon, 21 May 2018 18:40:52 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x241.google.com with SMTP id o80-v6so5418540ybc.7 for ; Mon, 21 May 2018 11:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AqRTCduI3tY+BUD7f0M3xRzYIk9La4KdB4ohmtbi2Sg=; b=UiHCZlJcM5HsmEuHU9SAS0RBOPuoxoaDLZdIgWj2OdifEDKewSttIgji3odrKGaeZV Ct0sbNESGyGW+yE+ZtJjHDxzTC0Tzs5teB/dHZnWNVVD8MKdJHY+dN9v0dg9rUq3R9Aa EnAUdRrfumJiMsNK5t8TIAtnrSzMtAUiKKRfpwT3bxTdMXN8dySjvNpHEm6mQCEpV0Gw fYJGHKCUszG1lwfOR2rX+YqbtMQMjgZvdgof3W3sWGdUXXHikIU6JScRIxqFpA7/LloH sy3YO6YLPbraA4mgar92FX9hBy42XW0fbV0M23ECmHW6sMERwaLymIgC58FGSo+xzbkF Hb1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AqRTCduI3tY+BUD7f0M3xRzYIk9La4KdB4ohmtbi2Sg=; b=CeJJIt4QNewv6D+IdtGkva480HcEsUGMld/a43u9Mme8Mfs36CNUXt8a0uvJPHUiEo SXPcfK5qb2Qm6fkS2Hl08QZV6Q5FFwwKv5E0BRUn+LqxXazYCpfVoAq+5MolC4kScr6l U9wfd5lVpTvyc+vN39Kdv7mi7kQj/c3nfO+WG2aEGq+kqIFM3rOpb7aRN0p1XZq1YXsH C7zwJ2/0SxB5ujZoRX3kdhJpkcAiLmCZTH4dJ6y9w50CmykkO9Xcxe/tck477zyqmtnQ BgeWMoMr19dq5+BD0AbTHQrgpZcRLpl6zFNizZR9msR0QRScs4/SHKAL2nIoVgHD3/0k MJMg== X-Gm-Message-State: ALKqPwc8zC5967w1uG+N2peNEtKO4P0pSdqWseM/01WCLGEvt3/HOehC +Xe3q3LHhanREa2E4UwcrzyZg/8VYRnsZjPPPc3fmw== X-Google-Smtp-Source: AB8JxZopEbS2qRdPQqDREH9h9fAZxQt5IxICCuCT4IU5kg9KgxJtyAFaP1DYg6sUhdaOEj2Vi2h0XT1GSCV8ucxV5LA= X-Received: by 2002:a25:2a8c:: with SMTP id q134-v6mr6479716ybq.29.1526928051307; Mon, 21 May 2018 11:40:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Mon, 21 May 2018 11:40:50 -0700 (PDT) In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180521181057.GA86707@troutmask.apl.washington.edu> From: Oliver Pinter Date: Mon, 21 May 2018 20:40:50 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Pete Wright , Rozhuk Ivan , Niclas Zeising , FreeBSD X11 mailing list , Current FreeBSD , Warner Losh Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 18:40:52 -0000 On 5/21/18, Oliver Pinter wrote: > On 5/21/18, Steve Kargl wrote: >> On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: >>> >>> On 05/21/2018 10:07, Steve Kargl wrote: >>> > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >>> >> On Sun, 20 May 2018 21:10:28 +0200 >>> >> Oliver Pinter wrote: >>> >> >>> >>>> One of the reasons for the deprecation and removal of the drm2 bits >>> >>>> is that they prevent us from automatically loading the >>> >>>> drm-next/stable-kmod kernel modules, since the two collide. >>> >>>> Regards >>> >>> >>> >>> Then it wold be better to resolve this problem, rather then removing >>> >>> a >>> >>> working solution. What's about module versioning what in other cases >>> >>> works? >>> >>> >>> >> May be just move old drm2 to ports? >>> > Why? "If it isn't broken, why fix it?" >>> > >>> > The conflict affects x86_64-*-freebsd aka amd64. The >>> > conflict does not affect any other architecture. The >>> > Makefile infrastructure can use MACHINE_ARCH to exclude >>> > drm2 from build of amd64. >>> > >>> > I don't use netgraph or any of the if_*.ko modules. >>> > Can we put all of that into ports? I don't use any >>> > scsi controllers, so those can go too. Why make it >>> > insanely fun for users to configure a FreeBSD system. >>> to play devils advocate - why include a kernel module that causes >>> conflicts for a vast majority of the laptop devices that you can >>> purchase today (as well as for the foreseeable future), while forcing >>> the up to date and actively developed driver to not work out of the box? >> >> Poor advocacy. I stated old drm2 can be excluded by the >> Makefile infrastructure and I've already provided a barebones >> patch. >> >> Index: sys/modules/Makefile >> =================================================================== >> --- sys/modules/Makefile (revision 333609) >> +++ sys/modules/Makefile (working copy) >> @@ -112,7 +112,9 @@ >> ${_dpms} \ >> ${_dpt} \ >> ${_drm} \ >> +.if ${MACHINE_ARCH} != amd64 >> ${_drm2} \ >> +.endif >> dummynet \ >> ${_ed} \ >> ${_efirt} \ > > I prefer something like this: > > op@opn src# git diff > diff --git a/sys/amd64/conf/GENERIC b/sys/amd64/conf/GENERIC > index 195b66daab51..034e2f8126fd 100644 > --- a/sys/amd64/conf/GENERIC > +++ b/sys/amd64/conf/GENERIC > @@ -23,6 +23,7 @@ ident GENERIC > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug > symbols > makeoptions WITH_CTF=1 # Run ctfconvert(1) for DTrace > support > +makeoptions WITHOUT_MODULES="drm drm2" # by default disable the > building of DRM* for GENERIC > > options SCHED_ULE # ULE scheduler > options PREEMPTION # Enable kernel thread preemption > Or make the function in this file smarter: "./hw/xfree86/os-support/bsd/bsd_kmod.c" #ifdef HAVE_XORG_CONFIG_H #include #endif #include #include #include #include #include #include "xf86_OSproc.h" /* * Load a FreeBSD kernel module. * This is used by the DRI/DRM to load a DRM kernel module when * the X server starts. It could be used for other purposes in the future. * Input: * modName - name of the kernel module (Ex: "tdfx") * Return: * 0 for failure, 1 for success */ int xf86LoadKernelModule(const char *modName) { if (kldload(modName) != -1) return 1; else return 0; } > >> >> Those interested in killing old drm2 on amd64 can add the >> requisite .if ... .endif to remove obsolscent *.ko. >> >>> IMHO it is issues like this (having out of date code that supports some >>> edge cases) which makes it harder for developers to dog-food the actual >>> OS they are developing on. >> >> You're talking to 1 of the 3 contributors that has tried over >> the last 2 decades to improve libm (both its quality and >> conformance to standards). The development and testing is >> done on my old i386 laptop (which happily uses drm2), my >> amd64 systems, and at one time sparc64 (flame.freebsd.org). >> So, yeah, i386 and sparc64 allowed me to dog-food my code. >> >> BTW, there are uncountable many integers. How about avoiding >> the conflict by using, say, '3' as in drm3. >> >> -- >> Steve >> > From owner-freebsd-current@freebsd.org Mon May 21 20:16: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 CE400EFD51E; Mon, 21 May 2018 20:16:13 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 602536E5BC; Mon, 21 May 2018 20:16:13 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x243.google.com with SMTP id m11-v6so18308576otf.3; Mon, 21 May 2018 13:16:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rhybfzuGjA9IXalKlmn62EtLiE9B87lqvq3xGzEjrOI=; b=Pww4mHFQ0f5fPI7ISxJwSskhyeUbAFy/bvT29Rs8JqPE1Z6sCcrRs8e5XbpDa07M55 lI2iTISb4KUlFDy6YRQpjqmK7OXiLZdd+5krF3vzJQgFP+vUwUWEtuJnc/zU7rrttpUF WTKO0TGvqTNZYyAGHEajHuwEugZ96ZLnhHPTBKw3CDo3cEfOpGpWvi+h8twalDySDPT0 p2YE+2gW8GRhsDn6SD2OA3ZRJ7BscRszlHmTs8cfRKSNNzDQiy6gJwggr66Tv788Z3Qc 4YdARlpH3207j2H0s6PZ7oDnQfpvPkSJdj4uPY7k7gBsK0sp9CZmNwHM6h9VtgM/pZWz C1ew== 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=rhybfzuGjA9IXalKlmn62EtLiE9B87lqvq3xGzEjrOI=; b=EDPWty9h8jTQ9D+6Hb8sKFVCedcRJHTspQiHuTRp5ktX5N79/ui7KlgSCrr2su9/YL kVvNsVIYDLlpWfTomBtS50oo69dnKopD9/VCeqsnWoao/iWerER2NPeTic7Jk9grSlRN NZMcworTaVSHpNkBZgldW/8CIphidCEM3OKijj8rH5CoXlI6YR6lQGVkSTybCzwxzGR/ mIYJR2cEh2aTpHwOe5SKZYesCa79BlXqcmUzVJP9BD9XL/KoUtzJ9eC9o6jXMVG+wN9S KZArDYmOIfiPgYP/QUmOueQIi6WA5tmCoaemB2lUfAL9CzX2mlOVc5WRttocFWQduAEl ONpw== X-Gm-Message-State: ALKqPwcAgZbGNTHepGXcFC2H+BSNiWam5veOhhEVN4SCPf+U1ggSLhFk 1i0XSnu1gzQI1bBs/j95znDsFZaFz4d5dFMfi/Y= X-Google-Smtp-Source: AB8JxZrky9lAmpO9SUnxHeu13kx3MQBNGT4AxyI1M1NsDYcEqkU+liz+ErfJYqN1ovLsqAOGitse7TXTJuXEJkPT5xg= X-Received: by 2002:a9d:3e07:: with SMTP id a7-v6mr13704799otd.150.1526933772656; Mon, 21 May 2018 13:16:12 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Mon, 21 May 2018 13:16:12 -0700 (PDT) In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> From: "K. Macy" Date: Mon, 21 May 2018 13:16:12 -0700 X-Google-Sender-Auth: jGQH2dskTTygnTaOFv0T5HnU3Lc Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Rozhuk Ivan , Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 20:16:14 -0000 On Mon, May 21, 2018 at 10:07 AM, Steve Kargl wrote: > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: >> On Sun, 20 May 2018 21:10:28 +0200 >> Oliver Pinter wrote: >> >> > > One of the reasons for the deprecation and removal of the drm2 bits >> > > is that they prevent us from automatically loading the >> > > drm-next/stable-kmod kernel modules, since the two collide. >> > > Regards >> > >> > >> > Then it wold be better to resolve this problem, rather then removing a >> > working solution. What's about module versioning what in other cases >> > works? >> > >> >> May be just move old drm2 to ports? > > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to exclude > drm2 from build of amd64. > Having it as a port puts the burden squarely on those using it and not on the majority who are running hardware from this decade. -M From owner-freebsd-current@freebsd.org Mon May 21 20:32: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 52150EFDA3F for ; Mon, 21 May 2018 20:32:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D2B1E6F0F4 for ; Mon, 21 May 2018 20:32:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4LKWA6F018041 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 21 May 2018 13:32:10 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4LKWAFT018040; Mon, 21 May 2018 13:32:10 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 May 2018 13:32:10 -0700 From: Steve Kargl To: "K. Macy" Cc: Rozhuk Ivan , Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521203210.GA17892@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 20:32:17 -0000 On Mon, May 21, 2018 at 01:16:12PM -0700, K. Macy wrote: > On Mon, May 21, 2018 at 10:07 AM, Steve Kargl > wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter wrote: >>> >>>>> One of the reasons for the deprecation and removal of the drm2 bits >>>>> is that they prevent us from automatically loading the >>>>> drm-next/stable-kmod kernel modules, since the two collide. >>>>> Regards >>>> >>>> Then it wold be better to resolve this problem, rather then removing a >>>> working solution. What's about module versioning what in other cases >>>> works? >>> >>> May be just move old drm2 to ports? >> >> Why? "If it isn't broken, why fix it?" >> >> The conflict affects x86_64-*-freebsd aka amd64. The >> conflict does not affect any other architecture. The >> Makefile infrastructure can use MACHINE_ARCH to exclude >> drm2 from build of amd64. >> > Wasn't a strawman. Is it that difficult to use the Makefile infrastructure to exclude old drm2 on amd64? -- Steve From owner-freebsd-current@freebsd.org Mon May 21 22:15: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 69812EFFA4E; Mon, 21 May 2018 22:15:47 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D0D7873ADF; Mon, 21 May 2018 22:15:46 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id w194-v6so27600776wmf.2; Mon, 21 May 2018 15:15:46 -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=NYWQpyjGlAmqhsBVj6hx9N0N+iNWWOHZZpzqDlOqYIw=; b=t2Hyu5lamtSZIi+Qcmq4bNjlFYc/wPLlvfBV0tEaDpoB8WtXqSNJrEp/RF6LwFMC1Z tTb80ek50HL7hBXp1f1aRSm4kqgcyOuqrZoIMkOxkIzslpd7G4X2Yy9vkhpmNOXlg6KR jk7D064KXa5KuhmjUYnQCqQ5Gf1HdpvsFZmgeQBIaBEjREVgi3yL5yQdlr/qhwTiLOqn 5fZjmsfAaElXQRApxQh8Gwx9Zv1yuHkCrF28eZUAP5vDooQDtP3eCC/CM5wbYsfIAhhS Fm/9YcuVXSXGO3TSUfQ/zgQ0VTyk9e33maKfI8zyg4WGRPUZ17xhe7HraYoN4QccOGnd nnTg== 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=NYWQpyjGlAmqhsBVj6hx9N0N+iNWWOHZZpzqDlOqYIw=; b=Yn1bKpafJpL52RURycGQ9BHRQq4wK9slwvIDImi8afo1Mb3+IAqSxD3ckSZGAC3YBa pVB1iVV0KPV/lZho3UuChhHcuNu0231VUge+s1NrOIhjFk/kZcKPpEIuqwTG8uMDmxoq IJ6CAVKHyH8JwbWeeTvJUnKID2ty5vod+j/baGjSKrGfGCFe87gGPxSiloyIX2CmnKkO P5pMwOvHhNYZWHbKsjkfiwFYDkjdX7zHa9FMdvQj5hZHs1s3xBLBOVuPesQCtsC2tLys +OSMfi7e10fdDf3Jfz3I0bB8f8WxLc/iSag34Vsy6o0Cm0ou2Sme52Zprj0rSqwrf0T1 GBdA== X-Gm-Message-State: ALKqPwcMk1/3HFKOWoOzJTe4PxvwftrW3/ETj1fxECcaxZJ6QSJNOETk RpUMpQDpbehgIx7U05nCwspd4P7o X-Google-Smtp-Source: AB8JxZoBHZxy/QbWtc8zrxD9PJcRiMnmPXy/Tx+9T7n5hNHHGtI7an1y1cQYOswHHqQafp4qRE2C7Q== X-Received: by 2002:a50:8f21:: with SMTP id 30-v6mr25361016edy.265.1526940945837; Mon, 21 May 2018 15:15:45 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id i22-v6sm7579457eds.28.2018.05.21.15.15.44 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 21 May 2018 15:15:44 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Tue, 22 May 2018 01:15:43 +0300 To: Steve Kargl Cc: Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522011543.3f621882@gmail.com> In-Reply-To: <20180521170728.GA14025@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) 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.26 Precedence: 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, 21 May 2018 22:15:47 -0000 On Mon, 21 May 2018 10:07:28 -0700 Steve Kargl wrote: > Why? "If it isn't broken, why fix it?" > > The conflict affects x86_64-*-freebsd aka amd64. The > conflict does not affect any other architecture. The > Makefile infrastructure can use MACHINE_ARCH to exclude > drm2 from build of amd64. > > I don't use netgraph or any of the if_*.ko modules. > Can we put all of that into ports? I don't use any > scsi controllers, so those can go too. Why make it > insanely fun for users to configure a FreeBSD system. > I just ask. Or why not include drm-next to base svn repo and add some option to make.conf to swith drm2/dem-next ? From owner-freebsd-current@freebsd.org Mon May 21 22:20: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 2801AEFFC0E; Mon, 21 May 2018 22:20:51 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AEAE073E50; Mon, 21 May 2018 22:20:50 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x229.google.com with SMTP id l13-v6so18636281otk.9; Mon, 21 May 2018 15:20:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3Vxxd4yyd5BgFK+InBIVd2e1ALFIEWmiimxe7oc+jtw=; b=V0fdxEWJsoUQpxD4wvV2iH4Tx2HMZwAKKslS5NuGG1RJq32b4vruZaZBjAd381aVAF 5z/skmyURm9p+rQn+ApuOzmGqqizTDZlIFHtRmjg5ozQ4eF0JbMi6JJ2gsFYH4GzGN3o bCOT0hLKZrtEuevgxCwENIErwHc+BjiyhBqxhIs+8ZkCtOW/Fbk4UiBG/NCIV3iPAbcZ lzYYIfkC7gVTA9w45dmEE2z8/y0IvedeDB0X1MiZNU958IhsAwlmNkdfs9pSi4+yEpq/ sHXwPzIqyrjCyolD3hg6uqmqQVbMtARI6VsC05a/HUBrnURSTstANTi4KLEdsBekfISe kYMA== 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=3Vxxd4yyd5BgFK+InBIVd2e1ALFIEWmiimxe7oc+jtw=; b=K/UFYcSNTw0BO9F7By5i3zK+UfWPgimxqSOw85XAe2ovU+o9JqEsnDFbcwaqDgjATj 8op+IUjY+X4Wkj0aV5inJfUSdJLsRt7Io0FjAM5t/tk7qPxBNj6CQBg2fzeHmtje7dAE S0i55BcuUbhWcQNZv39HIe1DvmjN9aojGNLoJnn+cCf19aRkVUcNC/leJ5GDIV4Oguzi hsCaPkZZaqC1XQVdh2I6T1gnZHakQ1ljRT9vOLHmPDH8zzAGt5coJCdUJQBDUay/SjwC NgSIMqhA1Iv6dVFmGgpDEsHEInoYcy57R7CZFuAEq1eIyQN5BEkzh+eHZbC636Q6HdUq DuYA== X-Gm-Message-State: ALKqPweNFgPtm8qydb2TvSiJjW7cABbRYP7CPL02Lv7M9dXnLug4sw4d GcgSYaOUkV/KTh9UGkqcZ9RJ7UzVJVRFOU/OoTE= X-Google-Smtp-Source: AB8JxZru3qo3cX+7nmsSpdUmE2eVKD4CkEF6RcUhEM27+Fejb1Kj/arsCzJDZ0Fx3hHnixF2BxtPWL2uIWdK2b5LCwA= X-Received: by 2002:a9d:3116:: with SMTP id e22-v6mr13957762otc.29.1526941249983; Mon, 21 May 2018 15:20:49 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Mon, 21 May 2018 15:20:49 -0700 (PDT) In-Reply-To: <20180522011543.3f621882@gmail.com> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> From: "K. Macy" Date: Mon, 21 May 2018 15:20:49 -0700 X-Google-Sender-Auth: LOWLGlvv8dWnNMA3lXHedtiA7tM Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Rozhuk Ivan Cc: Steve Kargl , Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 22:20:51 -0000 > > I just ask. > Or why not include drm-next to base svn repo and add some > option to make.conf to swith drm2/dem-next ? Even if it's not being built on amd64 we're still responsible for keeping it building on !amd64 so long as it's in base. This makes changing APIs and universe runs more burdensome. The graphics developers have given you notice that it will now be your collective responsibility to keep it up to date. Cheers. -M From owner-freebsd-current@freebsd.org Mon May 21 22:49: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 AFDE0EA8402 for ; Mon, 21 May 2018 22:49:33 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AB1B74A37 for ; Mon, 21 May 2018 22:49:33 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4LMnSdX028261 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 21 May 2018 15:49:28 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4LMnR8D028213; Mon, 21 May 2018 15:49:27 -0700 (PDT) (envelope-from sgk) Date: Mon, 21 May 2018 15:49:27 -0700 From: Steve Kargl To: "K. Macy" Cc: Rozhuk Ivan , Oliver Pinter , Niclas Zeising , Warner Losh , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180521224927.GA9925@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 21 May 2018 22:49:33 -0000 On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > I just ask. > > Or why not include drm-next to base svn repo and add some > > option to make.conf to swith drm2/dem-next ? > > Even if it's not being built on amd64 we're still responsible for > keeping it building on !amd64 so long as it's in base. This makes > changing APIs and universe runs more burdensome. The graphics > developers have given you notice that it will now be your collective > responsibility to keep it up to date. > Not quite. One graphics developer has indicated a desire to remove working code, because it interferes with the graphics developers' port on a single architecture. There is no indication by that graphics developer that drm2 will be available in ports. You can go read the original post here: https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html The last paragraph is What does the community think? Is there anyone still using the drm2 driver on 12-CURRENT? If so, what is preventing you from switching to the port? The answer to the last two questions are "yes" and "the port does not work on i386". Yes, I recognize that you're clever enough to purposefully break the API so that you can thumb your nose at those of us who have older hardware. What is wrong with using .if ${MACHINE_ARCH} != amd64 ... .endif to enable/disable drm2? -- Steve From owner-freebsd-current@freebsd.org Tue May 22 00:47: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 94C73EAAD2D for ; Tue, 22 May 2018 00:47:05 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic302-22.consmr.mail.ne1.yahoo.com (sonic302-22.consmr.mail.ne1.yahoo.com [66.163.186.148]) (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 35A8A78097 for ; Tue, 22 May 2018 00:47:04 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: DIWTxrMVM1mJg95o_psWBc.tMAM5ONvIsQWLTw6d6uXey9xSMoxHKq4bpgx9mjE KQ.xygXI82k_3j7dKt0zSVt_hD2rLnM74E5v3SGrdUHcA72taR__CsXcZRrltHPVNdkOVxGvdsYU uLxTjXlT4cafLhwCI8MLXdDOjiwesxwCo0N1NcW1m16qev4wn9CH2UBsSYzndXUmRYB2mbgLqIxN rcrP3YVjo39KtGmdjH5SYjwDMfDRW_n5oBOc3aMUkImhcNQ0VInXxsBBCpq87Qsjc8PhyE7lSxgn TP6IW9tKL_mRS6vbyF40JW6HuQnExXU9E0sz6UUaDGekMOKQijtTcq6Pc3sGwc8aPXppijMxZNw4 oOJaGywsl970aj8Wyorha68unHhANVa5ygv7wzN8yjrXc3SnkMJF6KQ10lotKIRB5KGcvc66B.wp tHc5BkCpItZSMaci_pqQZx0yUoIuvIYhvTP59ZNql33ZoZrm21OBOsLLcAq6kXohtC0.BrILsJwb ML6GxckMq.geh6aUgCSqlFV6tBL4jU87T_l5w1F1e2OATbIF_h8TQjDQQ11jZxSc5gRAzcOM8WM0 MNqKYD6Lh5hCwaRolbVZShvaPEGndiY99VK33Y4mwmgJFJ2PzU4FGOXAFC82BGXmmzZivRnwjCBW mMM8rA0eR Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ne1.yahoo.com with HTTP; Tue, 22 May 2018 00:47:03 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp401.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c563ca6dca150942fb15e8ccc1449bb7; Tue, 22 May 2018 00:46:59 +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.3 \(3445.6.18\)) Subject: head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds) Message-Id: Date: Mon, 21 May 2018 17:46:57 -0700 To: Eitan Adler , FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 00:47:05 -0000 FreeBSD-head-amd64-gcc (based on a more modern gcc) reports a more explicit error for -r333974 and later: --- all_subdir_usr.bin --- /workspace/src/usr.bin/top/commands.c:132:1: error: function declaration = isn't a prototype [-Werror=3Dstrict-prototypes] scanint(str, intp) ^~~~~~~ The older gcc 4.2.1 builds report: --- all_subdir_usr.bin/top --- cc1: warnings being treated as errors /usr/src/usr.bin/top/commands.c:134: warning: function declaration isn't = a prototype *** [commands.o] Error code 1 make[4]: stopped in /usr/src/usr.bin/top 1 error =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 May 22 01:06: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 E6F0DEAB784 for ; Tue, 22 May 2018 01:06:52 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic307-4.consmr.mail.bf2.yahoo.com (sonic307-4.consmr.mail.bf2.yahoo.com [74.6.134.43]) (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 8813878AD6 for ; Tue, 22 May 2018 01:06:52 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 4mnzugUVM1kjHUkapgPYBPb7xIBqsJVKw0Nnr49td1GZEPTk9GecXxFRxheX1pY XWpR_jyGdd8end9grCCLrd_Y1OVF715RTZDIK9xTdN.oRPoiqetELlt.J7MthsDJEFnS83z1gQs2 XSXJH8C9wo8jOebaOpftHFYIpbX1plTMQ1h6iJ5Z3xDgjoa9HjLQbHmIpbYWHxrEbmszO5.NKIOS I0XRLPus01yKrT8b8FSPx00MB3OV_5lycsYrThRxsD7xKozdTg27W4wLSsULmhz8JCEjAReis2cr EH6Ode4EzQMxv2jC0WdVwL7rCj.DENgRjnxVKdu5ebEljeQVY4KA.38tmUAVaZQvKNHuJois8cBa k3g9LVmrhBzYuvMzCBpxW4LyTl5_LM2jk0EYxYN_W4ELgMCbMyoOP2rTxP1RciPhCeJL69PRB12C zO1JOvv_2DkpT2mP5nydTZNSVIheEExZrd429p3VaSAUoFwT6JAk3vjbskYN7p0Z1ZwVlKA9VEJ1 f_8ty7JT4mG..ukAJ9mY4synXmD3ai5MloZ6Qd1eiPzMf6RlyxfHLLx6MpXzLSDmEhjsx1bIq9IC tLVDrj7ss1YivQxwkN_kqg1yH8G15Oz0nTXdn3fymnyBdIPZW7702t43UXUdmVdYZXimopMEE8os KPQ-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Tue, 22 May 2018 01:06:45 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp424.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 84c71deded0c94870d9fe35c8de97c7e; Tue, 22 May 2018 01:06:43 +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.3 \(3445.6.18\)) Subject: Re: head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds) Date: Mon, 21 May 2018 18:06:41 -0700 References: To: Eitan Adler , FreeBSD Current In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 01:06:53 -0000 On 2018-May-21, at 5:46 PM, Mark Millard = wrote: > FreeBSD-head-amd64-gcc (based on a more modern gcc) reports a > more explicit error for -r333974 and later: >=20 > --- all_subdir_usr.bin --- > /workspace/src/usr.bin/top/commands.c:132:1: error: function = declaration isn't a prototype [-Werror=3Dstrict-prototypes] > scanint(str, intp) > ^~~~~~~ >=20 > The older gcc 4.2.1 builds report: >=20 > --- all_subdir_usr.bin/top --- > cc1: warnings being treated as errors > /usr/src/usr.bin/top/commands.c:134: warning: function declaration = isn't a prototype > *** [commands.o] Error code 1 >=20 > make[4]: stopped in /usr/src/usr.bin/top > 1 error I should have been explicit that the material is from ci.freebsd.org . For reference, the gcc based builds seem to be: (all but the last being gcc 4.2.1 based if I undertand right) FreeBSD-head-mips-build FreeBSD-head-mips64-build FreeBSD-head-powerpc-build FreeBSD-head-powerpc64-build FreeBSD-head-powerpcspe-build FreeBSD-head-sparc64-build FreeBSD-head-amd64-gcc So those are what I'm reporting as having broken builds for the specific issue. =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue May 22 05:17: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 65AB8EE6FC3 for ; Tue, 22 May 2018 05:17:08 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic304-21.consmr.mail.gq1.yahoo.com (sonic304-21.consmr.mail.gq1.yahoo.com [98.137.68.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 E551D835DC for ; Tue, 22 May 2018 05:17:07 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: zDMu_BsVM1nm6THBp9_Drh28GdR7f1jKchL6z.hLaNFdH0ByrBuwbpUqSnLXsur .Ep_f3o3YVAdteKOTZYCAXJqCwm63KqxKEbgdwB4nXjmNrySXc3HdxB.FvYcbB7sQxtK.zEQnx9D HYttNrlPbFlPvb2k9PruArzaHxstXtt_c5JTOEnpnTRnvMrdsF8.ebvJxJ38eiUKZq1cUODcsnNa 4a0nfQW0KPRuEy.6AZD__lA4ueVxrWEyKSPmywYIPjR.jUPq5U_TFS2kVJ.3YmrHSClUyUTxsmjS PO74N.C9pdT2gNy_IDZh_gVCwFccaUQoeDWH4IcoP5uKO6IHEr_zgAFr1m0bGrmNMv1Zp8ucvizi YNqH8WB4_03WpodpWo4wHFkUNRhm0f1lcgudSYTMqagk2Qnyr6ZCK51fhbuzLZnd9UUSxBD.dx9Q oPUlerVeG9nhPKukgqGQhFpz0eMfNg3hnHHWQ72.qLeuXPVwAnk39Sr3XD1BQUyYc6XIVhF_2V4V rGGEJjiMn.LxH72OFfKZhuGP8BJ48cmBbUTst3BLTSERvr8Wj2vB2CeAMV_b5rM1Iz0tsZF_skD2 .xynhndQpzeGytY49zNtC1TKxXc9ZtJbr2SnQUUCAgW5IjCYBzGOr8jLZiEbok.GVykLNd67oWFY yuWMXm1MM Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Tue, 22 May 2018 05:17:05 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp413.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID d16900a77143060ea21749374a1ceefe; Tue, 22 May 2018 05:17:04 +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.3 \(3445.6.18\)) Subject: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh Message-Id: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> Date: Mon, 21 May 2018 22:17:03 -0700 Cc: Cy.Schubert@cschubert.com, "O. Hartmann" To: FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 05:17:08 -0000 Attempting to build head -r334014 from -r333947 includes the code from = -r334008, and for which I get: --- parser.o --- /usr/src/bin/sh/parser.c:1440:9: error: use of undeclared identifier = 'CQNL' case CQNL: ^ 1 error generated. for what was added in -r334008. # grep -r CQNL /usr/src/* | more /usr/src/bin/sh/mksyntax.c: { "CQNL", "newline character in = quotes" }, /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); /usr/src/bin/sh/parser.c: case CQNL: = /usr/src/contrib/libarchive/libarchive/test/test_read_format_rar_binary_da= ta.rar.uu:M+M7)?9;.A%CQNL-+4::&_UJQ*P"PPW:>)I5*8)7^>6(\]!Q"^9YCE>>`9OG8 Apparently this is something WITH_META_MODE=3D does not deal with. Rebuilding after: rm -fr /usr/obj/amd64_clang/* (here I normally have the build materials) built fine. (The "Making top.local.h from /usr/src/contrib/top/top.local.hs" change to no longer have top.local.h or top.local.hs was another example: for a while top.local.h was still referenced and old ones would still be used if present.) =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Tue May 22 06:50: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 AEAB5EE8C6F; Tue, 22 May 2018 06:50:51 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E55D86395; Tue, 22 May 2018 06:50:51 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id f6-v6so29054397wmc.4; Mon, 21 May 2018 23:50:51 -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=OsVzucqZ1ZiqjXY0naWFOG0g3/ihFYREOxDXrs7+Jdk=; b=QZsypmxMJyWeOB7Hr/snoWDAbeXNTvo/7u6W4N14MpUWeiKesIfjbSvBrTruq9fQ8g uaXmVwaqu2ZfDsA3osinkOAXm9iZsZCObls5rg8f/aAVC8I+akwwx9MIfYJlCorpfOKM whY15DHPZJsP9719WmOQX8Qf8l2SU2F4zmE5/adgdw6lzSntTxDUvy1pz64EVxs4qyDs /L965gNc+uQrRkbcOqijCeR34UbUXktXMwOXF0BMe6sOdgqUQ9TRG+xoz/epSwhKNPBB RyGEnJL6SpF9qOPrEfH7kyVD45MKgJHE9BEEpKF++wI+V4wZLp4yB3igU5XqYl565kPb Fw7A== 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=OsVzucqZ1ZiqjXY0naWFOG0g3/ihFYREOxDXrs7+Jdk=; b=qVse5wAfO2uy6JEpBt6MsOpeC6D4OxCCvrPJL48Xy7MRKBCPcplZo1/LLaxT73il6I dnWhM3oPbzgfITNpjTk+2XD39n6ww9MeItU49d6gtxMgJ21opHc+Mtsv7Az4+jHL31Kr Lxv/dc5gv0leW72tFTJhXZ2bJNQDke3xzNFGjiEGb+HuTu3zVXU35fhEVROZwID0UyCS afmePmiGlmzCUAPHVPOQOl4/IKs6ebYT5VhPz8FOk3ddEmSAIDntOfUMErxen+qD+qTQ UbGfQI4e227hPGjbDQLU5jHZTan2GwcagHX5aWWK6m/xDMqHCm6WPTecKK6ZlUY1kWCs Gdgw== X-Gm-Message-State: ALKqPwdeFnuYg9ApzZLs4mGrdrjToUpk1qfebuTMaXG3qbajtij3DSD5 Nf/y2hRdFzVOIxM+bj21l/mzU2fO+hvfIMXjVP4= X-Google-Smtp-Source: AB8JxZplDUrTcUwFnprohKKyl2Fpu6GvbWRzTwWZqn8hgX3os+BmM4xR22wCgVY0Awf0qXys1bqx5DLe3rH6PCHnQoY= X-Received: by 2002:a1c:be0f:: with SMTP id o15-v6mr174210wmf.104.1526971849587; Mon, 21 May 2018 23:50:49 -0700 (PDT) MIME-Version: 1.0 References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> In-Reply-To: <20180521224927.GA9925@troutmask.apl.washington.edu> From: Johannes Lundberg Date: Tue, 22 May 2018 07:50:39 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: sgk@troutmask.apl.washington.edu Cc: Current FreeBSD , FreeBSD X11 mailing list , "K. Macy" , Niclas Zeising , Oliver Pinter , Rozhuk Ivan , Warner Losh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 06:50:52 -0000 On Mon, May 21, 2018 at 23:50 Steve Kargl wrote: > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > I just ask. > > > Or why not include drm-next to base svn repo and add some > > > option to make.conf to swith drm2/dem-next ? > > > > Even if it's not being built on amd64 we're still responsible for > > keeping it building on !amd64 so long as it's in base. This makes > > changing APIs and universe runs more burdensome. The graphics > > developers have given you notice that it will now be your collective > > responsibility to keep it up to date. > > > > Not quite. One graphics developer has indicated a desire > to remove working code, because it interferes with the > graphics developers' port on a single architecture. There > is no indication by that graphics developer that drm2 will > be available in ports. You can go read the original post > here: > > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html > > The last paragraph is > > What does the community think? Is there anyone still using > the drm2 driver on 12-CURRENT? If so, what is preventing > you from switching to the port? > > The answer to the last two questions are "yes" and "the port > does not work on i386". > > Yes, I recognize that you're clever enough to purposefully > break the API so that you can thumb your nose at those of > us who have older hardware. > > What is wrong with using > > .if ${MACHINE_ARCH} !=3D amd64 > ... > .endif > > to enable/disable drm2? The answer to the first question is that the consensus seem to be that moving to a port is best for the _majority_. Let me ask you, what=E2=80=99s wrong with this one-liner after base install pkg install drm2 ? > > -- > Steve > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue May 22 07:51: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 EAC1EEEB7F7; Tue, 22 May 2018 07:51:03 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4549068329; Tue, 22 May 2018 07:51:03 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id w202-v6so27671038lff.12; Tue, 22 May 2018 00:51:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aqt6n30qACMbJvYVMiY6iCDzTMNIeXRhgpNcdyu/bqs=; b=EZDO9tkngW6MGzrg2vv8yk74EHuNyO84SfijAK7qeum/zh4dWtlyGM363zlQNkwzXx jp1gp833jTgEHluzqzj0OqMmEikTRVEzh21cBlgmlX19qCv1cnj6QHEtmetRolS2sMbE 8C/7pXSyyTZO52em4WAoyBBHJoPsIeMT7AmPwCtfxiM+Eu1iv1BolPfPOG3vuwJuAp7G /GrVFYsynjj3h7EfyLW4/vw4FexzC2wND2c5M+fPTPuq5M9q4eQGK9f9P+KEW0h1wPcy SLYWKNuDe5mDytWWtBY00ggpyfMjqbpT2NYMC2H3bzrMUZHbG5WsxF50w1EqqbUmNvoY ty7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aqt6n30qACMbJvYVMiY6iCDzTMNIeXRhgpNcdyu/bqs=; b=jvg66RPpRUdAhnsdEBxNBJFwsRFlgoTlyVkaEeMkZS1RgAvXKX0LIYx1E2chUKVK55 is4bOKA9ppDuTAxuUmBuQaidlPIv6VmvnJJRVny1HWtyafZsNjO9mfUFiZ3auei1RG1H 3ERni4IZ2ZqTRsxGfY+rU2OYhariv5SzTGOcoQvE/eVqo6bY+oixqJn/IR60KRvZcnj2 J+heUZSxHGPmw9+9yXLpj2ZydFmZt4aLFY4jbE+T/yK/fI0aOD8UajDHNx2/rMMYRI9d 2Bjmesa1oIC1zYBVObHrxwFjGuVIZ5XyDiGVntkwG+1Rd89SeEBoB4be05QbHOtvCuBN Ihdw== X-Gm-Message-State: ALKqPwf5jGkq1UqoC05tlPunkxtFI5iKyzNz5/Ub+DTNu/n49KGWP0hd v5E+koSfaARBza7xpKnrWh+kietiLYMaQAnVdbA= X-Google-Smtp-Source: AB8JxZoegVS10ty/u2uKXuQpqWaqG3B3qMW/ubuk78GwVpwetuGPm4eBW1GqzijJCk1qisxsHthicOtWfE+W14IDUpY= X-Received: by 2002:a19:9855:: with SMTP id a82-v6mr24170860lfe.87.1526975461861; Tue, 22 May 2018 00:51:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.131.76 with HTTP; Tue, 22 May 2018 00:51:01 -0700 (PDT) In-Reply-To: References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> From: Andreas Nilsson Date: Tue, 22 May 2018 09:51:01 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: Steve Kargl , Current FreeBSD , FreeBSD X11 mailing list , "K. Macy" , Niclas Zeising , Oliver Pinter , Rozhuk Ivan , Warner Losh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 07:51:04 -0000 On Tue, May 22, 2018 at 8:50 AM, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl edu> > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. > > > > Or why not include drm-next to base svn repo and add some > > > > option to make.conf to swith drm2/dem-next ? > > > > > > Even if it's not being built on amd64 we're still responsible for > > > keeping it building on !amd64 so long as it's in base. This makes > > > changing APIs and universe runs more burdensome. The graphics > > > developers have given you notice that it will now be your collective > > > responsibility to keep it up to date. > > > > > > > Not quite. One graphics developer has indicated a desire > > to remove working code, because it interferes with the > > graphics developers' port on a single architecture. There > > is no indication by that graphics developer that drm2 will > > be available in ports. You can go read the original post > > here: > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.htm= l > > > > The last paragraph is > > > > What does the community think? Is there anyone still using > > the drm2 driver on 12-CURRENT? If so, what is preventing > > you from switching to the port? > > > > The answer to the last two questions are "yes" and "the port > > does not work on i386". > > > > Yes, I recognize that you're clever enough to purposefully > > break the API so that you can thumb your nose at those of > > us who have older hardware. > > > > What is wrong with using > > > > .if ${MACHINE_ARCH} !=3D amd64 > > ... > > .endif > > > > to enable/disable drm2? > > > > The answer to the first question is that the consensus seem to be that > moving to a port is best for the _majority_. > > Let me ask you, what=E2=80=99s wrong with this one-liner after base insta= ll > pkg install drm2 > ? > > > > > > -- > > Steve Hello, If you were running GNU/Linux, you would be using the equivalent of drm-stable-kmod or drm-next-kmod. Why do you want to run older code on FreeBSD? Hardware and software moves on. One does not expect to run the latest hardware with old software, old hardware and new software might work, if someone is willing to maintain old code. Since the proposal was to keep drm2 in 11, you're looking at support until 2021, will you still run that old hardware then? With such long-time support offered by 11- branch, why hamper development of 12 by lugging around old, hard to maintain code that is relevant for only legacy hardware? Best regards Andreas From owner-freebsd-current@freebsd.org Tue May 22 11:52: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 0D56EEF28BF for ; Tue, 22 May 2018 11:52:10 +0000 (UTC) (envelope-from Alexander@leidinger.net) 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 817377095B for ; Tue, 22 May 2018 11:52:09 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: by mailman.ysv.freebsd.org (Postfix) id 410FEEF28BE; Tue, 22 May 2018 11:52: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 19793EF28BD for ; Tue, 22 May 2018 11:52:09 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9790470952 for ; Tue, 22 May 2018 11:52:07 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 22 May 2018 10:12:22 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1526989920; bh=WU9TZfXctqAagUEWAuYiTxfkgaZt2ywrwls69JRDCdE=; h=Date:From:To:Subject; b=YxIFxfxMLsC+1ShvvkMe1DBOZgz/XFHnLjZhP71eIWwaryMVD/VT8ytr8ofc9ap/C n9gh+zMdjpJx12sWyWwqZ14MK6+6+bKZJhZTt94YkSKO++2iIpc/cSqQ1IaJqdIDNb ItwIwkTV/K7CaZos/Sw94LeZbHH6K6wCa9WUu8ZLEicp+VWsnd0wxbFKMsYsa+l5DZ NStNTKQpm35zpTqQ/5BCzuHZL5EKHj7PsxfJNQCc2CdQNutkc53t7V6/j5Z9EF27IN l+JvEVtRjxDdkcisfdXhRvSKUp0F8O3Vjz+qnIM+YaKJBmBGsDDrsRb/I9sba8mhno UwpMjpwRenCeA== Message-ID: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org Subject: Recent changes in routing or IPv6 related parts? User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_k8eHYbkqlkqmDMHKlZ3_Yev"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 11:52:10 -0000 This message is in MIME format and has been PGP signed. --=_k8eHYbkqlkqmDMHKlZ3_Yev Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've updated 2 machines to r333966 and I see a change in the behavior=20=20 in=20the network area on one of the systems. To begin with, the "original" behavior was not OK either, the em NIC=20=20 fails=20to "do proper network communication"=20=20 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220997). A=20=20 workaround=20for me was so far to do an IPv4 ping to the router from=20=20 time=20to time, and if it fails do some ifconfig down/up. If the ping=20=20 doesn't=20work afterwards, reboot. Most of the time this worked. Now I see a change in behavior, the scripts kicks in, all is ok for=20=20 the=20script afterwards, but internally (inside the machine) I can't=20=20 reach=20ipv6 jails. The system is reachable externally (only tested so=20= =20 far=20is the main host-IP). The setup is vimage based, several jails (via iocage) on epairs=20=20 connected=20via bridge to the NIC. One bridge for IPv6, one for IPv4.=20=20 rc.conf=20has prefer IPv4 setting after encountering another issue. One IPv4 address (/32) for the host where a nginx is running to proxy=20=20 port=2080 and 443 requests on IPv4 to the IPv6 addresses of the jails=20=20 (IPv6=20access is going directly to the jails). After a reboot, the nginx on the main IPv4 address delivers data from=20=20 the=20ipv6 addresses of the jails (rev-proxy setup). After a while this=20= =20 stops=20working. The workaround-script mentioned above doesn't change=20=20 this=20behavior. Restarting nginx doesn't help. A reboot helps. Has someone an idea of recent changes in a related area which may be=20=20 able=20to cause such an issue? Any rev I could try to revert to check if=20= =20 it=20is related? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_k8eHYbkqlkqmDMHKlZ3_Yev Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbA9DlAAoJEKrxQhqFIICESiwQAI841duaYjJPyAvSnYgoXsVd 1uv82HFCQsV2/1zENVqREV4EpqxqOqSJnTZT5udAfnRj4728oaOQUOxwtRNwVLRO o89WrY9WpwLoLh9RjxTA01dZqSZfjSoMjyP+QX0TDckmy0RCWjbSExsPEiYaGvwZ gMZYPKHCiheiJMCdz+RU0wm2FQzbP5UQIoD+oE3ym4Kf0OxGRHaMg8eGOUZKYtkX ttPnzNgesInW4LKx0fFPp46ZUo/LufV6GCjR1UQjk0+iWCbW2PaUb8HbXpEMv0Fr C3wBcvF76r6UeLT9FcaYUsmLGDewGVnxmK+3NR+fShoRJWlIR3HsxbnlXYDd4BnX tYh/0Xbo2AoAUc5qwS6W+gP5Cl3Yw0DIfcmC6/Fryt7Ou+phPiK51njNYWtEzHEu 21qhBqV9IwL0lqHufPi8bQ6V2tyOuwCrxwSLFUGLCVro9wD7j0CCXwwpe/8/3S+y UuCgCjlaW2iMzi/Lm2KMm9uofRfdlUQe5/W8rtTFUVrvQyXzuq/ZssvGaP4Nkuih rqhfBKC5M+/Qm8UJKxhJq8lMrmEQ6KHBOuGVq/0RETZlxVqOFRfwSujww5ro0yCA MAKvDhOo7t9z859xdfHZts0MwoOuUJSU5/nzRPXDaiZPeeZxWgNewWcNHkXGRVaQ FiHe4wJRIegarHH+pt2t =GAZ+ -----END PGP SIGNATURE----- --=_k8eHYbkqlkqmDMHKlZ3_Yev-- From owner-freebsd-current@freebsd.org Tue May 22 11:56: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 A3379EF2AE9 for ; Tue, 22 May 2018 11:56:45 +0000 (UTC) (envelope-from Alexander@leidinger.net) 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 454CE70D3A for ; Tue, 22 May 2018 11:56:45 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: by mailman.ysv.freebsd.org (Postfix) id 061E7EF2AE6; Tue, 22 May 2018 11:56:45 +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 E7A5DEF2AE5 for ; Tue, 22 May 2018 11:56:44 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83B3B70D37 for ; Tue, 22 May 2018 11:56:44 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 22 May 2018 10:17:49 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1526990203; bh=bXfdMZhyHo2R0CWyWlH0O8wI7DTmOMLtB9v4oOYq43w=; h=Date:From:To:Subject; b=tQmNPKjUz9MPYsgTe2oEewTFRpLpiyjkIr9A3xNtYvF8X3ZGUkQETV7SrDkTVOrD0 ERw0kl8NG5cluVgJMUMH718WPEo8+cbfC3kfEfOgv+PTejnolF7maWcKum+lvlS161 BQV7GshqtC1lQHpCXW1B6I7HbUNRCi2IlExexwFMea1mFFjjsdOd6OkOt+GDdRJsWP ebpeM7LscbcZQrDo0pbpUIidcK5DDvYnV5sIVkDCQ083ToUkwXnu5N5USapp/La1ej 2aqfnaKH6Zyjqv+BaM4YmdIj0d1vfm67zXUozQJEoLmapMFVJJ4QIrx/FbH6mpGL9s CNflbWxKqqLIQ== Message-ID: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org Subject: Deadlocks / hangs in ZFS User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_6bXUgezYygiaoPWbEBPKOjp"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 11:56:45 -0000 This message is in MIME format and has been PGP signed. --=_6bXUgezYygiaoPWbEBPKOjp Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, does someone else experience deadlocks / hangs in ZFS? What I see is that if on a 2 socket / 4 cores -> 16 threads system I=20=20 do=20a lot in parallel (e.g. updating ports in several jails), then the=20= =20 system=20may get into a state were I can login, but any exit (e.g. from=20= =20 top)=20or logout of shell blocks somewhere. Sometimes it helps to CTRL-C=20= =20 all=20updates to get the system into a good shape again, but most of the=20= =20 times=20it doesn't. On another system at the same rev (333966) with a lot less CPUs (and=20=20 AMD=20instead of Intel), I don't see such a behavior. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_6bXUgezYygiaoPWbEBPKOjp Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbA9ItAAoJEKrxQhqFIICEshQP/j9QUdRHfuw9RmAecXXRG40c wy/J1s6I2r1Dzd11HzYSSUo+mWSO+vpPVoIGnI1XBzwDL1HE2LdaJbqB8vT+Spe0 4V6zu8w1ww/52PgWZikzckSGXMsu7/SYnWhVH+RSuzXHVqig7UpR9C+H/4P+/8FM LpqkgHG5T9EHzLc2f3Sun+I8mb+BKJOnW/zlXTt0P7We/cyshFIRfA9fBNTiJKqC hGtDPqp4HJGE5C9u8acmMYNEyNZodSG6F+Najni8j3VZi7fFjF0KZUAKxL+Jvkzn fcoDpvfosoZ5XjxKMMR3jc9W3QemAYKgT77ok893yIr4/9f7e+Nqy2xnrPJIUh39 JKuP8Lmu1hMA3A4xFCgyiAd/IRlo9C2L55QtblPbqKnTf/OyDezAID8L3HUmCLu2 +egklTp3xpt/tAwMnB6of7R3+eFrYmnpzeESnTHT07qrMlysheUpozpC5o6HhsSH lHfAoT/9jWEAvo358OjrGYw9PMuFtA3g+7xemVEevbKah27hBMOWMbMJI6Z1LP4R NVnlFXRyQ5Q/zSP2lgM4rh7Xg5RvadycE+S4srMCjMcYfBVA2isBG3gf4NTre+Kd g7Q837sseQUgYc7wnKu2ASCr5ZKi+rBKiU1ODkeMDaF1b5AlXvG3oKfexQdq7nSh SkErY4XSidwqOGgxkWC9 =87QI -----END PGP SIGNATURE----- --=_6bXUgezYygiaoPWbEBPKOjp-- From owner-freebsd-current@freebsd.org Tue May 22 12:17:15 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 157E8EF3D07 for ; Tue, 22 May 2018 12:17:15 +0000 (UTC) (envelope-from swills@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 995EA71ADA for ; Tue, 22 May 2018 12:17:14 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 59502EF3D06; Tue, 22 May 2018 12:17:14 +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 43764EF3D05 for ; Tue, 22 May 2018 12:17:14 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BC98B71AD9 for ; Tue, 22 May 2018 12:17:13 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-2606-A000-4102-2500-6245-CBFF-FE5F-6C74.dyn6.twc.com [IPv6:2606:a000:4102:2500:6245:cbff:fe5f:6c74]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w4MCH5UF008662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 22 May 2018 12:17:11 GMT (envelope-from swills@FreeBSD.org) Subject: Re: Deadlocks / hangs in ZFS To: Alexander Leidinger , current@freebsd.org References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> From: Steve Wills Message-ID: Date: Tue, 22 May 2018 08:17:00 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Tue, 22 May 2018 12:17:11 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 12:17:15 -0000 I may be seeing similar issues. Have you tried leaving top -SHa running and seeing what threads are using CPU when it hangs? I did and saw pid 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity happening. Do you see similar? Steve On 05/22/18 04:17, Alexander Leidinger wrote: > Hi, > > does someone else experience deadlocks / hangs in ZFS? > > What I see is that if on a 2 socket / 4 cores -> 16 threads system I do > a lot in parallel (e.g. updating ports in several jails), then the > system may get into a state were I can login, but any exit (e.g. from > top) or logout of shell blocks somewhere. Sometimes it helps to CTRL-C > all updates to get the system into a good shape again, but most of the > times it doesn't. > > On another system at the same rev (333966) with a lot less CPUs (and AMD > instead of Intel), I don't see such a behavior. > > Bye, > Alexander. > From owner-freebsd-current@freebsd.org Tue May 22 12:29: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 4DBC3EF447D for ; Tue, 22 May 2018 12:29:35 +0000 (UTC) (envelope-from slw@zxy.spb.ru) 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 D9E5D7212F for ; Tue, 22 May 2018 12:29:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 9600AEF447C; Tue, 22 May 2018 12:29:34 +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 84575EF447B for ; Tue, 22 May 2018 12:29:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CB707212D; Tue, 22 May 2018 12:29:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fL6Ps-000H0p-QA; Tue, 22 May 2018 15:29:24 +0300 Date: Tue, 22 May 2018 15:29:24 +0300 From: Slawa Olhovchenkov To: Steve Wills Cc: Alexander Leidinger , current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180522122924.GC1954@zxy.spb.ru> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 12:29:35 -0000 On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote: > I may be seeing similar issues. Have you tried leaving top -SHa running > and seeing what threads are using CPU when it hangs? I did and saw pid > 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity > happening. Do you see similar? Can you try https://reviews.freebsd.org/D7538 and report? > On 05/22/18 04:17, Alexander Leidinger wrote: > > Hi, > > > > does someone else experience deadlocks / hangs in ZFS? > > > > What I see is that if on a 2 socket / 4 cores -> 16 threads system I do > > a lot in parallel (e.g. updating ports in several jails), then the > > system may get into a state were I can login, but any exit (e.g. from > > top) or logout of shell blocks somewhere. Sometimes it helps to CTRL-C > > all updates to get the system into a good shape again, but most of the > > times it doesn't. > > > > On another system at the same rev (333966) with a lot less CPUs (and AMD > > instead of Intel), I don't see such a behavior. > > > > Bye, > > Alexander. > > > _______________________________________________ > 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 May 22 12:38: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 D88F7EF47C2 for ; Tue, 22 May 2018 12:38:44 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 750C572694 for ; Tue, 22 May 2018 12:38:43 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 40qwDY0vLXz5DvY for ; Tue, 22 May 2018 14:38:37 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 40qwDY04nmz5DvX for ; Tue, 22 May 2018 14:38:37 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id DE2D52B05B for ; Tue, 22 May 2018 14:38:36 +0200 (CEST) Date: Tue, 22 May 2018 14:38:36 +0200 From: Luciano Mannucci To: freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS In-Reply-To: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <40qwDY04nmz5DvX@baobab.bilink.it> X-Virus-Scanned: PippoLillo, ClamAV using ClamSMTP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 12:38:45 -0000 On Tue, 22 May 2018 10:17:49 +0200 Alexander Leidinger wrote: > does someone else experience deadlocks / hangs in ZFS? I did experience ZFS hangs on heavy load on relatively big iron (using rsync, in my case). Theh was cured by reducing the amount of available RAM to the zfs caching mechanism. Parameters in /boot/loader.conf vfs.zfs.vdev.cache.size and vfs.zfs.arc_max may be your friends. On a 16G machine not showing the syptoms anymore I have set: kern.maxusers="4096" vfs.zfs.vdev.cache.size="5G" vfs.zfs.arc_min="1228800000" vfs.zfs.arc_max="9830400000" hope it helps, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-current@freebsd.org Tue May 22 13:44: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 02044EF63AC; Tue, 22 May 2018 13:44:19 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 458427505B; Tue, 22 May 2018 13:44:17 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wm0-f42.google.com with SMTP id l1-v6so33850012wmb.2; Tue, 22 May 2018 06:44: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:to:reply-to:from:subject:openpgp:autocrypt:cc :message-id:date:user-agent:mime-version:content-language :content-transfer-encoding; bh=zwfISNsCc/wX3uhpTD1zXYY/6E7f7UfHzJIvblWTd3o=; b=Yy+yHj/V2LC/J5XHTJ9oLNA6Yw5eGqefZICp8auINz+UCr0pTFnpaq/UBtMp1R4rnU YVSbAGSKMFmB/Xr+70xQ3wmIGv1OmTrsjeejuVORQ4AKOyJogDhdJ8VBXG22C3mkOY9K dI1eRA4qKT2QOXj3CKpYkZ/fBtH+H1iDwHIV6zCEDcI2RjC9PeDg9LhlHuXWt+TmC1r+ yAIW4qAzRK27VYKZ+tfU7letM5rA9E+BIvwTp3tUlCu+zy/9fddFxSm2+uLHUMJEqflI Y+nWhFdHbg40Mg8Lnt/AiA5tgD2o9TfPHFdHWcIEmadabiuvxHxXBX4sv21zN/sWcBzc TXRQ== X-Gm-Message-State: ALKqPwclAeUtOGSPz/UwNaIMzhvvYcUPanuTWe/4SGRjIszB1i6mBInk fG4eRYY83Q5tacAnfwL1o6CQtVfQ X-Google-Smtp-Source: AB8JxZrxSdGvdGYQM/+4LAyIB1k9c2/Axtwliao78CkggBvL0+FlUhYqV5+ST1/dDwO7DWKciWXHvw== X-Received: by 2002:a2e:6c10:: with SMTP id h16-v6mr14657725ljc.81.1526996651002; Tue, 22 May 2018 06:44:11 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id 23-v6sm3988652lfw.64.2018.05.22.06.44.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 May 2018 06:44:10 -0700 (PDT) To: FreeBSD Current , freebsd-usb@freebsd.org Reply-To: freebsd-usb@freebsd.org From: Andriy Gapon Subject: uchcom update 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 Cc: freebsd-stable List Message-ID: Date: Tue, 22 May 2018 16:44:09 +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.26 Precedence: 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, 22 May 2018 13:44:19 -0000 Yesterday I committed some changes to uchcom (so far, only in CURRENT). Commits are r333997 - r334002. If you have a CH340/341 based USB<->RS232 adapter and it works for you, could you please test that it still does? If you tried your adapter in the past and it did not work, there is a chance it might start working now. Could you please test that as well? Thanks! -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 22 13:57: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 8D6B0EF6D50 for ; Tue, 22 May 2018 13:57:53 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE61D75E86 for ; Tue, 22 May 2018 13:57:52 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22a.google.com with SMTP id t16-v6so17214257wrm.9 for ; Tue, 22 May 2018 06:57:52 -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=rsxdsKTK1mEoWmqgB8YMaUSt0+BkmxYviuuHIqu3OgM=; b=n+PoqPjb5oM7wLfNQR2uPvcYGm9yXDcXAReEMgnqkqYKxCFzr88yy9EqioDtB23RuH nwKOhwRgPzQXjGpe06sRDmoVva9tRUQxjDoni4pGQtSXGh7pDBA1ctD8kJdHB0oXpPoX VZIcQ5lSSOLeCPkNMicAYzY0VcHRWPstfEm4QtNgd3F3IKiC+/jVoxkvAvtQx99GWlEG 6MyKL9TfZBaUuCRYYM37YdWOywjULAuBa/wVvmlDm1SA9kbfbF+yiyKiLPZjnDYajkFo oqn3X8uwcx2n/QsFwB1f/xwI5RxJnUczINg5fwvugfEccyOpv+JbOkKV42z+YxiEOIiL FMOw== 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=rsxdsKTK1mEoWmqgB8YMaUSt0+BkmxYviuuHIqu3OgM=; b=r6zLeGd56iWGYd7Xn0DclBV23IoW8T2K4boTJWABbGsxzfh2EXg4LRgdzGoW2xvL2V 8ilaxUPTvtY7fMgN00v0WLEhb1A/80IC+fKyF5hc+LaDr74wDXNTwvNRlkj7iU5diHMP i5uX9NdWj1fDMJigUZTmSx/GsOS1xZVasCnHUjqlGp5BhkMnBggTonOXOWE0p33PlG+7 8i3R1QrZ73CmYFdVT5Y/ouakz2GbQaHmVYZCxtoKom5nwiIvy5nnczdL1EI4GPM9Cr9c hCHbIFIPTzLgKmV1dWGgK9WJgHXj3icy2U21G1i3BPff0a5ieqfWALx8sSYF9kgRFePp PQhA== X-Gm-Message-State: ALKqPwdxQlCtD9AZ4SIZKynDSw1nRO+63G8+zg9sko0uvcjOr81qAtJx 5hxRpue1StyB484yg7iuO5gX3GbWh+DZn59NowtGahcd X-Google-Smtp-Source: AB8JxZqnS8L/aVwsGHwD6Y2kp3X4V08mgZ6Y6IdFJI5QrsUaYlIgdpKWObEnX6Za72q7zY100b0xoRkF2xSwg1iTCj0= X-Received: by 2002:adf:f74c:: with SMTP id z12-v6mr14396449wrp.165.1526997471521; Tue, 22 May 2018 06:57:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.167.137 with HTTP; Tue, 22 May 2018 06:57:11 -0700 (PDT) From: Johannes Lundberg Date: Tue, 22 May 2018 14:57:11 +0100 Message-ID: Subject: How to check if not clean shutdown? To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 13:57:53 -0000 Hi In the boot process on my test machines I'd like to do different things depending on the last run was a clean shutdown or kernel panic. Where/How can I get this information? Thanks! From owner-freebsd-current@freebsd.org Tue May 22 14:05: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 3A9BDEF7241 for ; Tue, 22 May 2018 14:05:11 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it [2.44.121.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mailserver.netfence.it", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 834A376889 for ; Tue, 22 May 2018 14:05:09 +0000 (UTC) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w4ME4xC0072293 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 22 May 2018 16:05:05 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Deadlocks / hangs in ZFS To: freebsd-current@freebsd.org References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> From: Andrea Venturoli Message-ID: <830847c6-a580-10d7-5335-effb51c1e986@netfence.it> Date: Tue, 22 May 2018 16:04:59 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.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.26 Precedence: 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, 22 May 2018 14:05:11 -0000 On 05/22/18 10:17, Alexander Leidinger wrote: > Hi, > > does someone else experience deadlocks / hangs in ZFS? Yes, in conjunction with Poudriere, probably when it builds/activates jails. Not sure this is the same problem you are seeing. bye av. From owner-freebsd-current@freebsd.org Tue May 22 14:16: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 E9CCFEF791D for ; Tue, 22 May 2018 14:16:54 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 729387724F for ; Tue, 22 May 2018 14:16:54 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 22 May 2018 16:16:32 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1526998612; bh=OjusJRjp2YD6XVIsYGb92G8G7leU5ygPPf3lyw5oBnM=; h=Date:From:To:Subject:References:In-Reply-To; b=x9trMiPeA/8/zMsvqCUQ0EI9zfI98lm+r0rJedvc889yMvjw9H42LmHDcdhhpwUHA xLl3w+Rt54rHIbyH25hn4HHraHHnKTZ3ww4e+vm/Wa6NMbbeajY05cysYbzO2bUsPW d3nE9nB2fYkP/1atTAFpVyR/cyX+vcMeKehnfwCUVqKMerOn16+KvQ9IoAG3tsXPOI 4QnPMRmXXkNJn+05WMDg2i9bcqealAXBrErQXzRUiVN1ckHONIs3XIR/gha7vr7vGT w9ww+jSh6093r+UY7lNaZUebL7IXFTDlOuoE7+TV2UdGSdsc3ITyUbMYkeQAtNW0Sv ziS/IrH5/z91w== Message-ID: <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> In-Reply-To: <20180522122924.GC1954@zxy.spb.ru> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_rjOwuw2j622I-0AAa6_QmXX"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 14:16:55 -0000 This message is in MIME format and has been PGP signed. --=_rjOwuw2j622I-0AAa6_QmXX Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Slawa Olhovchenkov (from Tue, 22 May 2018=20=20 15:29:24=20+0300): > On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote: > >> I may be seeing similar issues. Have you tried leaving top -SHa running >> and seeing what threads are using CPU when it hangs? I did and saw pid >> 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity >> happening. Do you see similar? I will try and report back. > Can you try https://reviews.freebsd.org/D7538 and report? The patch tells it is against -STABLE, we're talking -current here. It has been a while since I tried Karl's patch the last time, and I=20=20 stopped=20because it didn't apply to -current anymore at some point. Will what is provided right now in the patch work on -current? As a data point, the system I talk about in the start of the thread=20=20 has=2064 GB RAM and the ARC is not limited via sysctl. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_rjOwuw2j622I-0AAa6_QmXX Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbBCZAAAoJEKrxQhqFIICEoowP/jn/YCWofMjRfGDtaFcFToCO 1fTOEuKZ1zKf7OTUXQgHQSGi+io4i9hclwN2n0ok7WSsEtMdBYXKAbRJVvllhjku 4jrYsxnI3CSt5Yuu3pnxGj7QUwb+VWD80cCpOc4XE1KyB5+hztbxC45GDCsQB6xv pZnJVr6ImHZNqjx8LmXComwATNn9ke+VXtQ9gCT78YxBkhXd4oE4qm6cHZJSRsGN WO44PSbJwTRgLc09ctVz8zUdWYF9ehKkqBDvJHIGwCAyO47sfFqXW5AtWoQI7JG1 AREZBNzrp4iByoBwIAzzEKAripnK5NpGiat2Y4c20B1KTKax7LA9K1qVAtE1FPZ+ TF84MS2/Z7IUCqQxxLguoCrnImp0SV7sy/RFREyzc2W+IhIn/0RzWCmW7VefcEur iaqR9/5gM4/6u20pizPmMd7qBxR2JK5nQuSMArPiowihr0/1FS+0rLJFBWbQlrtw K53u9zfmSP5mAUqYXMNZ9CfF/0Dv/Ruwlrf8D/KZbbKqWjvMO81Bpm9AeBn4y5qC slfgMs/zZB87e8tL1KJfHlcFwBXRs8GZ97h+5zMLXxAWiYk9L05AHZg3XMUA9UQh W/m7pjjtgoeyWDoNQsZhonUk6MaxrtE9G9r153j0JNZp48dMJqHVD2paJanPXEI5 aMUJAYsz8ssIPbSoVYKw =hJyi -----END PGP SIGNATURE----- --=_rjOwuw2j622I-0AAa6_QmXX-- From owner-freebsd-current@freebsd.org Tue May 22 14:30: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 97B90EF7F91 for ; Tue, 22 May 2018 14:30:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B40377D27 for ; Tue, 22 May 2018 14:30:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22c.google.com with SMTP id q72-v6so199339itc.0 for ; Tue, 22 May 2018 07:30:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=uu90DQHvkrlDcEHgRjzYD2kEVvKMMJb2CyXVP5weo1M=; b=S3CK0+TlpQsTew/e4HKKRDlTQgnCpBYjDiu3iTrdT0IA8S+OLJeAiT2E8l4M5fSAS1 STgLGR18gfeMLRc6uZZUXlaqHopLSFm0Ex+DWmt+XrAwKw21UIQR4vueTg0CR6hPplD3 tvjoF9JmiFUZSrCTAAQa4CT4Vl1nLeqr5QtGqsitgS7XNydlaZ1O5WGEq5QkpRBs+n+n 4tKYiMlGeNi3pUM8gRqUvJPSt3oq9fwOrNYjGHG4O4y9K3XxPIiUFu5qTmVEzE98JgBj +4xjOyqwvPBcSWzxJ6QV1n6G2+SWwDStWiqqG5Yn6398//hw1tBkNcixTUPsTZ69UMpl Vhfg== 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=uu90DQHvkrlDcEHgRjzYD2kEVvKMMJb2CyXVP5weo1M=; b=YxziXdTQSk+dgXDQZo3QRKg0+zBz1G5gP7S0eQvBTVWHfGnCM8XO/nHfL8qmMAoeN0 jw1HlTfLZgfUxIzU22fpuAnYDrS6Fo2Ymq6bL0Xw7zGFzPtZHuWYkFxMxFP2oAoFzOgV 02LauyhvWvI0JSeQT9i4L4LF4UcNzH2y5cE2i+5s+V7lVyMPcnv2Cv05xUUM8a/QM1xV FoENfYaGms8YfuuimiCfFwsMGoV9hSOQf9m0fvlzQFg9WTyZZP4qynygq/zYy92NuMo6 pIL5AN08vYsvv3bJG9pB4PzkuMb6WqgS80PT82aRsBq/TIO+llpKES7D2RL0vlN6bXzl xyCQ== X-Gm-Message-State: ALKqPwcyZQXOvHgyi9M7D/C7kSaVzUhEocyVgFmG4LiVggkTmyDZ3uxi rB/Q2oYnpyLsrXPPTBLn9KRzzAMcbckaPkWKI33Iyg== X-Google-Smtp-Source: ADUXVKKRSVx3mu9i4nudFYKnw40jDXQ+bR8ErJBaHHXLpRCYvRHbkD1zYb5Q1tC0TuOHYvT8Rr5G7Vf6EU1nu0u0+PA= X-Received: by 2002:a24:42c6:: with SMTP id i189-v6mr1480015itb.73.1526999433357; Tue, 22 May 2018 07:30:33 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Tue, 22 May 2018 07:30:32 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Tue, 22 May 2018 08:30:32 -0600 X-Google-Sender-Auth: zLP6fccwiyMmajW7kPNTMgQIF5U Message-ID: Subject: Re: How to check if not clean shutdown? To: Johannes Lundberg Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 14:30:34 -0000 You can't, in general. By the time the boot loader starts, all knowledge of past boots is gone, unless specific counter-measures were put in place. However, if root is UFS and read/write in your box, it will be unclean on anything but a clean shutdown/reboot. If it's read-only, ZFS or NFS mounted, then you can't use this method. If you have UEFI, you can set a UEFI variable on shutdown and clear it on boot. If it's not there on boot, you had an unclean shutdown. You could do the same with a file in a r/w filesystem that doesn't record clean/unclean (like ZFS or NFS). Locally, we have hacks to IPMI to record kernel crashes in the IPMI log, but that's kinda specific to the BMC we have on our boards... Warner On Tue, May 22, 2018 at 7:57 AM, Johannes Lundberg wrote: > Hi > > In the boot process on my test machines I'd like to do different things > depending on the last run was a clean shutdown or kernel panic. Where/How > can I get this information? > > Thanks! > _______________________________________________ > 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 May 22 14:36: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 F3A70EF8395 for ; Tue, 22 May 2018 14:36:18 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7095A784B7 for ; Tue, 22 May 2018 14:36:18 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id o78-v6so465317wmg.0 for ; Tue, 22 May 2018 07:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=T7WfPU0bXzNIOD/M3+bCCnuY7XxRpDiLbG9nB73YXPw=; b=Ffwa5HQb74qq5YicnOkceJa3ge983n/suX5sYoPRAASZ+e6HHKlQWcrRL6x8yNWEzI WS2VSzd3KUv+liMhZrLzpQWswtsg2IWVNsgPXseXXzl+9KzSmwudmqOdKRVNbv9tCUoX HQze+pXnx7ktNdKwXLh28AWI65cfGHMnGSIX1xkBCgGYevS11/T74TXY7i7tbv6kTC3s holFK0tur3K2KhRc0bfgxtcuFsBSJfb102edifV7ZnWTor4iEvQ4U8qDxSz6ANJMwIij ZGY4fJyVcc03ewj07/5yCzuCTqyRe/wrc4EsjwD1qojFx/mzsNQbH+hbC/KMIKgF4y1M S/oQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=T7WfPU0bXzNIOD/M3+bCCnuY7XxRpDiLbG9nB73YXPw=; b=ujDNIcxPRHhgYdPpizqBxj+O/Mx0cT/XoF2AGdn/K/Wc3QRDcohE8QjOoT+wcH5TUX hTKURZsNfqRlD+Oi57H73pbNy+En9bovIEQQKx5k74w8OICuMMHvQU4ilKtF90Hill12 AkLCbemf/R0YDuHzz+/nQLZM9fmCVUbiawfBtHd+ZgX11km5/QqbFIGfRjoGG/iZjywa eyguF05UhQrQe9c710fVi3NK3sYSMFKIKpPZ0Rj90bQqzuiNQ74V3nsyh3Te0zfIUOt5 OdhLIGIzaVwR4GQjE4aFY3K22IcHOxUuL3lqwanuCZBJLY8lMpP+EHnPSHHegbnc+eQR rR6Q== X-Gm-Message-State: ALKqPwfW0BhLqN9ubQGcaLXYJF9miWVAffj4lluUOiTbjmt0l8+HZWKo +58X8yffNMD1Nk10S6+cfZN7EKG/r/NHSABgoEu/Rg== X-Google-Smtp-Source: AB8JxZoD88da1kNco4GHqfBV79p1JpI0F3Vy1VvJRU6aHwEkNCiK2ZTYhB8bQmAKi7t0GjgzjguPG/lRtpOz2uMkUHI= X-Received: by 2002:a1c:be0f:: with SMTP id o15-v6mr1529927wmf.104.1526999777422; Tue, 22 May 2018 07:36:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.167.137 with HTTP; Tue, 22 May 2018 07:35:37 -0700 (PDT) In-Reply-To: References: From: Johannes Lundberg Date: Tue, 22 May 2018 15:35:37 +0100 Message-ID: Subject: Re: How to check if not clean shutdown? To: Warner Losh Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 14:36:19 -0000 On Tue, May 22, 2018 at 3:30 PM, Warner Losh wrote: > You can't, in general. By the time the boot loader starts, all knowledge > of past boots is gone, unless specific counter-measures were put in place. > > However, if root is UFS and read/write in your box, it will be unclean on > anything but a clean shutdown/reboot. If it's read-only, ZFS or NFS > mounted, then you can't use this method. > > If you have UEFI, you can set a UEFI variable on shutdown and clear it on > boot. If it's not there on boot, you had an unclean shutdown. You could do > the same with a file in a r/w filesystem that doesn't record clean/unclean > (like ZFS or NFS). > > Locally, we have hacks to IPMI to record kernel crashes in the IPMI log, > but that's kinda specific to the BMC we have on our boards... > > Warner > I see. Thanks for the quick reply. I guess I can add a dummy file somewhere that I delete in a shutdown hook. > > > On Tue, May 22, 2018 at 7:57 AM, Johannes Lundberg > wrote: > >> Hi >> >> In the boot process on my test machines I'd like to do different things >> depending on the last run was a clean shutdown or kernel panic. Where/How >> can I get this information? >> >> Thanks! >> _______________________________________________ >> 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 May 22 14:40: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 C4B0BEF87B0 for ; Tue, 22 May 2018 14:40:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5DED778A22 for ; Tue, 22 May 2018 14:40:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fL8TA-000Hky-0P; Tue, 22 May 2018 17:40:56 +0300 Date: Tue, 22 May 2018 17:40:55 +0300 From: Slawa Olhovchenkov To: Alexander Leidinger Cc: freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180522144055.GD1954@zxy.spb.ru> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 14:40:57 -0000 On Tue, May 22, 2018 at 04:16:32PM +0200, Alexander Leidinger wrote: > > Quoting Slawa Olhovchenkov (from Tue, 22 May 2018 > 15:29:24 +0300): > > > On Tue, May 22, 2018 at 08:17:00AM -0400, Steve Wills wrote: > > > >> I may be seeing similar issues. Have you tried leaving top -SHa running > >> and seeing what threads are using CPU when it hangs? I did and saw pid > >> 17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity > >> happening. Do you see similar? > > I will try and report back. > > > Can you try https://reviews.freebsd.org/D7538 and report? > > The patch tells it is against -STABLE, we're talking -current here. ZFS don't changes this. > It has been a while since I tried Karl's patch the last time, and I > stopped because it didn't apply to -current anymore at some point. > Will what is provided right now in the patch work on -current? I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g I am don't know how to have two distinct patch (for stable and current) in one review. > As a data point, the system I talk about in the start of the thread > has 64 GB RAM and the ARC is not limited via sysctl. Currently vanlia ARC poorly limited via sysctl. After abd extra. May be interesting test ./sys/cddl/contrib/opensolaris/uts/common/fs/zfs/abd.c:boolean_t zfs_abd_scatter_enabled = B_FALSE; (no sysctl for change this exist) From owner-freebsd-current@freebsd.org Tue May 22 14:48: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 8EFF6EF8BE5 for ; Tue, 22 May 2018 14:48:14 +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 E3D1378F18 for ; Tue, 22 May 2018 14:48:13 +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 w4MEm9fr030595; Tue, 22 May 2018 07:48:09 -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 w4MEm9ra030594; Tue, 22 May 2018 07:48:09 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805221448.w4MEm9ra030594@pdx.rh.CN85.dnsmgr.net> Subject: Re: How to check if not clean shutdown? In-Reply-To: To: Johannes Lundberg Date: Tue, 22 May 2018 07:48:09 -0700 (PDT) CC: Warner Losh , 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.26 Precedence: 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, 22 May 2018 14:48:14 -0000 > On Tue, May 22, 2018 at 3:30 PM, Warner Losh wrote: > > > You can't, in general. By the time the boot loader starts, all knowledge > > of past boots is gone, unless specific counter-measures were put in place. > > > > However, if root is UFS and read/write in your box, it will be unclean on > > anything but a clean shutdown/reboot. If it's read-only, ZFS or NFS > > mounted, then you can't use this method. > > > > If you have UEFI, you can set a UEFI variable on shutdown and clear it on > > boot. If it's not there on boot, you had an unclean shutdown. You could do > > the same with a file in a r/w filesystem that doesn't record clean/unclean > > (like ZFS or NFS). > > > > Locally, we have hacks to IPMI to record kernel crashes in the IPMI log, > > but that's kinda specific to the BMC we have on our boards... > > > > Warner > > > > I see. Thanks for the quick reply. > I guess I can add a dummy file somewhere that I delete in a shutdown hook. utmp has one attempt at keeping track of this by recording a shutdown record. > > On Tue, May 22, 2018 at 7:57 AM, Johannes Lundberg > > wrote: > > > >> Hi > >> > >> In the boot process on my test machines I'd like to do different things > >> depending on the last run was a clean shutdown or kernel panic. Where/How > >> can I get this information? > >> > >> Thanks! > >> _______________________________________________ > >> 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" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue May 22 11:59:15 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 BBD3BEF2C16; Tue, 22 May 2018 11:59:15 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) 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 529AE70F64; Tue, 22 May 2018 11:59:15 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40qvM454B4zDhTS; Tue, 22 May 2018 11:59:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1526990351; bh=jSXMn4UhJ+IXPvImwO+zvUOI YJFozcM7it9qT19nyos=; b=KQQnrmkScV+mOOX2Wo/lIYeHE7swFU3pYmAv1Cnd Q7x+DcOXVwKagt2+gUEV+rqUmw4t8W9Xh2ZzFRvGAf2FW3HLWE3Hj5gN9nIjMH/A x5xJeFS2VlX7uB8S4KKfCdeEZJXjK29c3eK0fjuT/dsu0eBOe4Y3MgbCWFE58k10 kvI= 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 s3CxXKxMHyWB; Tue, 22 May 2018 11:59:11 +0000 (UTC) Received: from garnet.daemonic.se (host-90-233-150-251.mobileonline.telia.com [90.233.150.251]) by mail.daemonic.se (Postfix) with ESMTPSA id 40qvM22R3wzDhBg; Tue, 22 May 2018 11:59:10 +0000 (UTC) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: dpolyg , Andreas Nilsson , Johannes Lundberg Cc: FreeBSD X11 mailing list , "K. Macy" , Rozhuk Ivan , Oliver Pinter , Current FreeBSD , Steve Kargl , Warner Losh References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <368b7106-d9c9-c860-cc00-54a45a07d34c@gmail.com> From: Niclas Zeising Message-ID: Date: Tue, 22 May 2018 13:58:54 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <368b7106-d9c9-c860-cc00-54a45a07d34c@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 22 May 2018 15:10:40 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 11:59:16 -0000 On 05/22/18 13:47, dpolyg wrote: > I have one comment regarding usage of the drm2 on a "legacy" hardware. > Excuse me in advance if I misunderstand something. > For the last 2-3 years I'm playing with devices such as small form=20 > factor PCs from Shuttle: > http://global.shuttle.com/products/productsList?categoryId=3D69 > or from Gigabyte: > https://www.gigabyte.com/us/Mini-PcBarebone > or Intel "NUC"s. > To my experience drm-next doesn't work on lower price (Celeron/Atom)=20 > models. Do I missing something? > Here is concrete example: > I have a Shuttle DS47:=20 > http://global.shuttle.com/main/productsDetail?productId=3D1718 > running FreeBSD 11.1-RELEASE and drm2.ko loaded + Xorg + compton. > Having that I made a box with a voice control and ability to make a SIP= =20 > video call to it from a smartphone (WebRTC) (imagine "Amazon Show"=20 > powered by stock FeeBSD) but I never install any drm-next on it. Stock=20 > amd64 kernel used. No ports compiled. Only "pkg install ..." + custom=20 > code as the most front end. > After reading this thread I tried to compile drm-next on my DS47 box: >=20 > root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # uname -a > FreeBSD ShuttleD47 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue Ma= y=20 > =C2=A08 05:21:56 UTC 2018=20 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC=C2=A0 a= md64 > root@ShuttleD47:/usr/ports/graphics/drm-next-kmod # make > =3D=3D=3D>=C2=A0 drm-next-kmod-4.11.g20180505_1 not supported on 10.x o= r older, no=20 > kernel > support. > *** Error code 1 >=20 > Stop. > make: stopped in /usr/ports/graphics/drm-next-kmod >=20 > Why drm-next thinks it lives on a 10.x kernel or older? > Is such usage case already considered as legacy? > Is this hardware supported by drm-next? > https://www.amazon.com/Best-Sellers-Electronics-Mini-Computers/zgbs/ele= ctronics/13896591011=20 >=20 That is most likely a typo, or at least not as good as it should be.=20 drm-stable-kmod and drm-next-kmod are supported on CURRENT and will be=20 supported on FreeBSD 11.2 (it's supported in stable right now). Older=20 releases will, however, not be supported. But they still have drm2, I=20 will not remove any drivers from releases or from STABLE. Regards --=20 Niclas From owner-freebsd-current@freebsd.org Tue May 22 16:56: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 2B0EBEFC85F for ; Tue, 22 May 2018 16:56:14 +0000 (UTC) (envelope-from bsd-lists@BSDforge.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 B267A7FE5C for ; Tue, 22 May 2018 16:56:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: by mailman.ysv.freebsd.org (Postfix) id 72F70EFC85A; Tue, 22 May 2018 16:56:13 +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 5EB8CEFC859 for ; Tue, 22 May 2018 16:56:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 D769B7FE5B for ; Tue, 22 May 2018 16:56:12 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w4MGwwcs056947; Tue, 22 May 2018 09:59:04 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Alexander Leidinger" Subject: Re: Recent changes in routing or IPv6 related parts? Date: Tue, 22 May 2018 09:59:04 -0700 Message-Id: <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 16:56:14 -0000 On Tue, 22 May 2018 10:12:22 +0200 "Alexander Leidinger" said > Hi, >=20 > I've updated 2 machines to r333966 and I see a change in the behavior =20 > in the network area on one of the systems=2E >=20 > To begin with, the "original" behavior was not OK either, the em NIC =20 > fails to "do proper network communication" =20 > (https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D220997)=2E A =20 > workaround for me was so far to do an IPv4 ping to the router from =20 > time to time, and if it fails do some ifconfig down/up=2E If the ping =20 > doesn't work afterwards, reboot=2E Most of the time this worked=2E >=20 > Now I see a change in behavior, the scripts kicks in, all is ok for =20 > the script afterwards, but internally (inside the machine) I can't =20 > reach ipv6 jails=2E The system is reachable externally (only tested so =20 > far is the main host-IP)=2E >=20 > The setup is vimage based, several jails (via iocage) on epairs =20 > connected via bridge to the NIC=2E One bridge for IPv6, one for IPv4=2E =20 > rc=2Econf has prefer IPv4 setting after encountering another issue=2E >=20 > One IPv4 address (/32) for the host where a nginx is running to proxy =20 > port 80 and 443 requests on IPv4 to the IPv6 addresses of the jails =20 > (IPv6 access is going directly to the jails)=2E >=20 > After a reboot, the nginx on the main IPv4 address delivers data from =20 > the ipv6 addresses of the jails (rev-proxy setup)=2E After a while this =20 > stops working=2E The workaround-script mentioned above doesn't change =20 > this behavior=2E Restarting nginx doesn't help=2E A reboot helps=2E >=20 > Has someone an idea of recent changes in a related area which may be =20 > able to cause such an issue? Any rev I could try to revert to check if = =20 > it is related? Hello, Alexander=2E I'm not sure if this landed in -CURRENT=2E I only know it landed in 11=2E But your trouble might be related to pr #224247 : https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D224247 Hope this helps=2E --Chris >=20 > Bye, > Alexander=2E >=20 > --=20 > http://www=2ELeidinger=2Enet Alexander@Leidinger=2Enet: PGP 0x8F31830F9F2772BF > http://www=2EFreeBSD=2Eorg netchild@FreeBSD=2Eorg : PGP 0x8F31830F9F2772BF From owner-freebsd-current@freebsd.org Tue May 22 21:49: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 801C2EB0B42 for ; Tue, 22 May 2018 21:49:23 +0000 (UTC) (envelope-from AWilcox@Wilcox-Tech.com) Received: from mail.wilcox-tech.com (mail.wilcox-tech.com [45.32.83.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.wilcox-tech.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB4926A990 for ; Tue, 22 May 2018 21:49:22 +0000 (UTC) (envelope-from AWilcox@Wilcox-Tech.com) Received: (qmail 9706 invoked from network); 22 May 2018 21:49:13 -0000 Received: from 99-50-40-94.lightspeed.tulsok.sbcglobal.net (HELO ?192.168.1.65?) (awilcox@wilcox-tech.com@99.50.40.94) by mail.wilcox-tech.com with ESMTPA; 22 May 2018 21:49:13 -0000 Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: freebsd-current@freebsd.org References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> From: "A. Wilcox" Openpgp: preference=signencrypt Autocrypt: addr=AWilcox@Wilcox-Tech.com; prefer-encrypt=mutual; keydata= xsFNBE+DjPIBEADTQ1H/e/avDUhgt8+T3TJpjGYoY9Y47EMfHqWMm9LjR9aiZSG6GWRbpjWS 4V0DqzIhNQw7HLkPws9CVqQkmpIeltQyGDV2qcR5AXxJ4lCRWHxwRzWE0cCzhLUR9BBWOO0U NINQY+2IqmzRAqXZ9zL+mGTles/qeheXmaWLKf/T0kqJFihoM+ItQvUWOkWUdVv0prhzXr9Q QUdt0NTIW8n4sPwtuSvQgqwSzCJQArh1myugVSGiIIN38pCU8g41Vh35mHHhbHjbn0o1mhrX B/gbsndGo7QQBKz4CPaSel+Fl92dCvVWTp1XYyjqeZx2xlx1zfDrXOTuzY1WmNHi7BgHYuem tG7Zyp7u9MR6FvLKgQhmvCQZXaa+9oNtwKckxoP/I5R8ede9YRb6pLyG5JC0pTTk7kpUZCX2 tm8pLKy899zomm8BBm71aEJHE44ABEl/PbM7tA7XhSPiWsdBmVCxH4bqpUgGMx0ztqhNsUul SDDhiAWgtYFHATynhmeKBDKthkO7lj4CzwI54dn1uiwDtvUFVyVsPMjJcCxFnONbOPcvm1R9 sDg5sn57dv0f+EtaU3ppZdotutjM9X7OEC93d1flO3k1LO20qn2ZcI24f3tEOLAjn5xZ1GdV 3BYBwrtuaaiO8tMdp0uAtILzkkrcr0vOi2/SngxtXFw+44X+WQARAQABzTNBLiBXaWxjb3gg KEFkw6lsaWUgTGludXgpIDxhd2lsZm94QGFkZWxpZWxpbnV4Lm9yZz7CwXoEEwEIACQCGwMF CwkIBwIGFQgJCgsCBBYCAwECHgECF4AFAlhEpGYCGQEACgkQyynLUZIrnRQu5RAAqxHJdNIQ ucYYUaYX4EHJte4OAZbxXeGgMi4fe4m2qkMrd8U6VDfRbjsqETK7fOJdrIjvp+xrMTMvj36C LZ5YuBVmvTd4+Qn54y+8doMUtZppjW9Njwols3zCeaZR/4Iid2GjS7+avgVEhMuxlo5apygb n84VhdLRPAs2BtyqUWUhlLs2nXg6kzI/yT8frGGCN36Xewe35jrhl7h4d54t7h+wYcYw52Yt GHs/R+yPlCGPrlzh8IGwjDWDaUrQAqWdU3B2UG4g/yn/JYZrkvfbm7AhpBP5trY2jbm7sfTM NoClDDwgf0K8Kfj0LeBUzOLqGgQNBdaJ2x7f1xq5tJjAPmVL6oMElqyDz9ycUXvelLMnxgXI sjndF+K1aKjg6Ok68BfTo+tnUqmEjqAhjLBCSphQJavww8pU9KSPmxOr0GfjoiYELeoCdTe2 U44bhFwCcf5tG1qdu8l4pes1YPRVAVyr4J/BlS2e3FyU3MsYlma9toYghJZ0k9dVOqx5YXj9 B2keDpX1D7uEJUHpoRSPylLYKJCcNuzrsaK0gvczkgUvhaiij8qnlLEmDsv7KMdsv+qxknNC vdCBgoiYn01ZJZJrlllOEXpVAXfQDKcqGnIJ4GX87TIu3hR94tw4LOCayfRpN2Y4zlACPLaZ KiSon4ySDo+ooYQ8WgwH1y1ESsbOwU0ET4OM8gEQAOI/n9h9v2TBOiLUt/nL+HOdxqvkfrKp mDHXx6ctJSm0VBHhHCxKN6Tk2B0BsUXcgR+BD76Tw4kTQvuj3E87m13xHRtASdCmnkvGhU4c JJ9ZbJbJhPLNr9qPUxwCQxFyMrFri/9GnE0Kbv5FfxsLQy9Slubnyg3CfI/wIP5pOoVFA2qI UmsQS155DmhbV2m0FDf0san01ZRMFYVcUUktcmFo0Xmr6PAxZ0FTaxSF8+921lKrvShcsnMv Osrf5toJGEdQw/IMO5rKH1m+q3qWQAOw4uF4WQJrGvhEsVK8G4mC6EBDTbxFVDtyBTMAGUVS t+Yb5i0iIYiMAP2MEJ+twg58PV+5RglheTGP9iPW0xReI1sOD9jfIrQbwqWpOchDGBUpQx4q DFYzzcbjvAP1k2o0mwMby5DJlVwktUiXXtOWZXKZXfTnCA65x1bC6gbtMrXN1CWkyjKT9xj9 Z5WlpZaeqe2SZkLG3/N7r4bSbw/Z6NsYeJ8CpSe6SfoWSsjebD6kbXlF5dsQf8aMUjaZAHp0 UpinfgWNh+58128yddsRMsidjU/MmwhzcRFsvn3rkgtnK4IwpLEfssChNPa26qwfcsvQ+AQU CCRd/GIZ8AkOVySQ30J8Assa/T3nc6VNKRVgsAiSClkeqVevAZmUMUbvH8f3cTe1VFn6kR3q pvfTABEBAAHCwV8EGAECAAkFAk+DjPICGwwACgkQyynLUZIrnRQifQ//f++reIP4el9Un1w4 11boSy1iBALnv58YSQQHPIZ4dq5hr8P1Hp3GDz+o6JFKeIHq5RYw2ornumS9waDbz7dRD1nc N5sMoVfR2g2P7honq59r3velxX36PmifHMmxb8MTqbCSJJRisqjWTMg7CZxH0NQ28qMtpiAw kvoEb+l2Uc/gKnvcpPfVJ/X0b3go0xAe9GA7Os9thjtl1v+I7c2+xjPUtvv+pDGRb9To2+Sw zOGwogbTrVw7KgAFhktx6i8tenXZRf36O0GTACRY//qHNoNNy5H4LYmfyHj6VU2ehwNJTlkK H/8oYV7fkOdcs6DZAnxeiOXUKpHC6ck0D0sWQ42GTeEraospQevGTrp1FZdYnfXznUFXuC6W jHR9piQehutMJ1vCP+DIRLGOMzV1TFWflpo71lb4AFLU3UOS/N7Cd8F+w1nG3WPn7UjFCMrc Xf268AEe0xwakXgNtwo2MTbtQSAO5AKYyGm/hnoLZg4YQ2eBPU95jUV+GMoEM/8Q0BJgsyF0 66NfhBXtuo50AipcARmnoqi6NDOKpC6mqiEYGsVuyQ9cRtkk9Jl98tXmnjxQlSL2nb4ErwJJ SyJq3hwiKMUJcw88IRNtYBe+dXaW4kDBTRha1k+brWZbu4tUlRWLVcSGjtP1pVukXA/SQ6a1 N7qhRF0UHQZkMW1rGbU= Message-ID: <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> Date: Tue, 22 May 2018 16:49:19 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 21:49:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC Content-Type: multipart/mixed; boundary="jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP"; protected-headers="v1" From: "A. Wilcox" To: freebsd-current@freebsd.org Message-ID: <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> Subject: Re: [RFC] Deprecation and removal of the drm2 driver References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> In-Reply-To: --jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable >>>>> I just ask. >>>>> Or why not include drm-next to base svn repo and add some >>>>> option to make.conf to swith drm2/dem-next ? >>>> >>>> Even if it's not being built on amd64 we're still responsible for >>>> keeping it building on !amd64 so long as it's in base. This makes >>>> changing APIs and universe runs more burdensome. The graphics >>>> developers have given you notice that it will now be your collective= >>>> responsibility to keep it up to date. >>>> >>> >>> Not quite. One graphics developer has indicated a desire >>> to remove working code, because it interferes with the >>> graphics developers' port on a single architecture. There >>> is no indication by that graphics developer that drm2 will >>> be available in ports. You can go read the original post >>> here: >>> >>> https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.h= tml >>> >>> The last paragraph is >>> >>> What does the community think? Is there anyone still using >>> the drm2 driver on 12-CURRENT? If so, what is preventing >>> you from switching to the port? >>> >>> The answer to the last two questions are "yes" and "the port >>> does not work on i386". >>> >>> Yes, I recognize that you're clever enough to purposefully >>> break the API so that you can thumb your nose at those of >>> us who have older hardware. >>> >>> What is wrong with using >>> >>> .if ${MACHINE_ARCH} !=3D amd64 >>> ... >>> .endif >>> >>> to enable/disable drm2? >=20 > With such long-time support offered by 11- branch, why hamper developme= nt > of 12 by lugging around old, hard to maintain code that is relevant for= > only legacy hardware? >=20 it makes me giggle that people still think non-amd64 is "legacy". i386 is alive and well - new chips are being fabbed based on the 586 design with pci-e slots; not to mention things like the Talos and AmigaOne for PowerPC. --arw --=20 A. Wilcox (awilfox) Open-source programmer (C, C++, Python) https://code.foxkit.us/u/awilfox/ --jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP-- --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjNyWOYPU1SaTSMHHyynLUZIrnRQFAlsEkF8ACgkQyynLUZIr nRQzBRAAqqcbCiOTfahzcXLwcv0iiEjTyAo9qItXI8fQRxQDJNGTF5NwVkdBbQ19 4WjsGRg7hvvV8D3jH5XTfnM8IWJbKiSi6M+Kxw12pkbxFdf5bknGnNkMI7bv5HkH MowXf6+0+Bi0lbrOTBJSktOIGt5W5cBZbGroCzUrnsFrpE/JYMTVPghuteQm0+b4 Fhtw2DYSRBxocAuC9zUHQLsT6CTq5JDhcQxKd46niXjztAMH4rU6z6Y1ftjBjhHk 34EOjJL4Vt/+S8CqgdmU19Kuh6hN1T57H3zDEjpBfjXIJ96sGbDNudiWrFJebg3L 2Ws+vIrVNq/MvsSxn4Gv1aMbHle+UedsNFbe1fv/mDY2OXjyksvaXN1NDRodAHvW R/KGCfeGaZhgWFGYt9N/H0IhF8/pd2Qrpa4LsYlJo9AGaK3g6Sc0sQdMHR3X2LSL W5B03BKVX9t07qL1w0mHzS4umk2Zx5JkHixxSgaBlGk0Mrv1AeV6WDFBkR/YzZSY OnVPbsSIl/UzpIF3TXMmf7Q0tgmJihP5vlBSFWI7MpgtEIfL9RUB9Qy8wA43zSXh 6l/y/aIBReJ4sUWiG/5J+6HsqSVLSOwwlJn1x+ouO7cWiy2xtOAd0WlI3EqCL0Xh xwsbKhnpxKz0bEK/a8u6kkDHPf/sqOBINYIZOvsVhtsCBg0JO+c= =bHE3 -----END PGP SIGNATURE----- --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC-- From owner-freebsd-current@freebsd.org Tue May 22 21:56: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 8D4C4EB0EE1 for ; Tue, 22 May 2018 21:56:57 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14E816AE3D for ; Tue, 22 May 2018 21:56:57 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x230.google.com with SMTP id m11-v6so22831916otf.3 for ; Tue, 22 May 2018 14:56:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0ADfEpFrvpNvElngdUC6D2oXESmtlgXTiAc/PhLd4A4=; b=glYDdav634A7WARuVTW/jLu4fStNuC9cstPn42x1Fv43Nb21vgEN/y8K/i9WEAdYH+ c0m3GYoscuABgFmQdrDYa+BdpxwBsxg0LcSSMVodiok+lU7IDppl/jKPX26jUokCEdJd Ts0p8gXEBcXSLuzuuwu/JRQIFcWtMY1MotWrGcN7aVmIf8bEr0KpW5lZxUlEXH1rVT2J 5Oqe98Xb+cPDPt4/Pv3eXu8E4hUIB2MUIBDzi78+B8QBMXBeqfi5zi/DVjjAhOPD9ctl kEfUky8A/SIdhv8BBL2/4B9ratE7g1705HEPoAlbhU0vwyr5U4qANXCXQopUGC9aA46B 7WoA== 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=0ADfEpFrvpNvElngdUC6D2oXESmtlgXTiAc/PhLd4A4=; b=qxoMr+l6SnFKnFI0Mhhi/E014Vxc1da8fd5/nWsLUXPPWWMKiQ3KnoDtkt9Zrv25iW Att70s1PzAX8azD5NrnH/kKCAFFdpbo8Dev6fsmAZwG/YrhT3cFN0ipMzPtG8d5gKFRH 6QQGHFw017+j9zyfXlXe3oQ5llb+VLoULlJBYxzFegg7tejB7oSl9HjpJjaSPqzB8flR 6VJhM0q7Uluhdn8SNqBVGkW7p8dKLAqEDoXzQJEnwOWcK47IPULAcsvRj/K0eY0Sfsyh QHXugUkh1SErV/V0nSjMnxtvWvwEtYIU9BF9VdBPmCf7zLDSgHmDUji+4AS4BEN0QL/Z xAWQ== X-Gm-Message-State: ALKqPwf068RRPevGPuVlHMVsIvbI6s2pZvHlBNv4ApaiGgDNWrvesk3a cqx4oiYV0nrg23qZ7pFtVCcj4Bv9HhlUz2wCyPaLog== X-Google-Smtp-Source: AB8JxZovo/Gu5SBMzLyY5Oi5xXlJSYCEuUmFRX1Ei/TLlnbQR3C+CvgjSWNpeS2TiJNpg9I88iv51Ce2b2/r+uPG9E0= X-Received: by 2002:a9d:3116:: with SMTP id e22-v6mr163194otc.29.1527026216146; Tue, 22 May 2018 14:56:56 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Tue, 22 May 2018 14:56:55 -0700 (PDT) In-Reply-To: <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> References: <20180518193009.GA88432@troutmask.apl.washington.edu> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> From: "K. Macy" Date: Tue, 22 May 2018 14:56:55 -0700 X-Google-Sender-Auth: 1E_u30mVjHiTQCMexOMJdmIeZc0 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: "A. Wilcox" Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 21:56:57 -0000 > > > it makes me giggle that people still think non-amd64 is "legacy". > > i386 is alive and well - new chips are being fabbed based on the 586 > design with pci-e slots; not to mention things like the Talos and > AmigaOne for PowerPC. DRM2 doesn't support anything later than mid-Haswell. The chips in question all pre-date 2007. Users of low-volume hardware on chips from that period are welcome to continue to sustain themselves on the drm2 port just as the other 95+% of the user base will use what is now referred to as drm-next. Even by powerpc maintainers' admission DRM2 also only barely works there. I've promised Justin that I'll make drm-next work on Talos once POWER9 support is solid enough. Cheers. -M From owner-freebsd-current@freebsd.org Tue May 22 22:12: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 ADA60EB167B for ; Tue, 22 May 2018 22:12:43 +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 083046B73C; Tue, 22 May 2018 22:12:42 +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 w4MMCdd1031938; Tue, 22 May 2018 15:12: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 w4MMCdA9031937; Tue, 22 May 2018 15:12:39 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: To: "K. Macy" Date: Tue, 22 May 2018 15:12:39 -0700 (PDT) CC: "A. Wilcox" , 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.26 Precedence: 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, 22 May 2018 22:12:43 -0000 > > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for PowerPC. Yes, some how we need to shake off the idea that all the world is going to be 64 bit, and stop talking about EOL for 32 bit x86, IMHO that would be a serious mistake. For one any VM that does not need >4G of address space is a waste to run in 64 bit mode. > DRM2 doesn't support anything later than mid-Haswell. The chips in > question all pre-date 2007. Users of low-volume hardware on chips from Um, haswell announced in 2011, started shipping in mid 2013, and last product started to ship in 2015, so if "mid-haswell" is the supported chip arrena that would be pre date 2012? Also as the Moore's law curve flattens expect the life of these older, but not so old, machines to live quiet some time. I believe we are talking sandy bridge and earlier? If that is corret Sandy bridge is still a very viable system. > that period are welcome to continue to sustain themselves on the drm2 > port just as the other 95+% of the user base will use what is now > referred to as drm-next. Even by powerpc maintainers' admission DRM2 > also only barely works there. I've promised Justin that I'll make > drm-next work on Talos once POWER9 support is solid enough. I think the original RFC has been answer, yes there are people still using DRM2, and they wish to continue to use it into the 12.x time frame. Lets find a technically agreeable solution to that, and move forward. I am concerned about just disabling the compile on amd64, that typically leads to bit rot of the i386 code. I am concerned about just shoving it out to ports, as that makes it rot even faster. I am still very concerned that our in base i9xx code is like 4 years old and everyone is told to go to kmod-next from ports as well. No, I do not have a solution, but I have not tried hard to find one. I am sure if we try hard to find one it can be done. Regards, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue May 22 22: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 BF110EB1B93 for ; Tue, 22 May 2018 22:19:45 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x234.google.com (mail-ot0-x234.google.com [IPv6:2607:f8b0:4003:c0f::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53F2C6BB0F for ; Tue, 22 May 2018 22:19:45 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x234.google.com with SMTP id l13-v6so22867834otk.9 for ; Tue, 22 May 2018 15:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NqEcYGmGQPy6IDwRjn00d0ad7C/+afDa3rnoEDGWjtk=; b=kUGEOg4Sk0JcvO3Sr2IJiN5uty/VZ/LXtJ+ZQ4nBT2X6WFUCeh8Ykwp7fIxf8f2sOq 8XIjKPqpW/Mxv0l/kTOvwFg5Ic0gPpcEl3I3QAoJqLMAiOlDfDE58zW1SrMZ2DBjWdtA o9Pa6G9U7k/ymfmPD3XSq4LVizdVMWZ+Dfo1xLH4PQqxGZU0m5RB6We856Lw1ufrkm65 +xS4jY+H90CG2oFMVp0Qz968Ui9cAeKqoNag/5Plr8+cvJngfetS8r1caBBzmKfK+I9u qy/OwI7vJ+NtDBnP+SHam58a4HVyy6o5upiNDLxS1x0xni+U514rOA8tytpn1vNqUq5S 4xVA== 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=NqEcYGmGQPy6IDwRjn00d0ad7C/+afDa3rnoEDGWjtk=; b=l1yQCBWuMye0RBCF6MLWI1zHHIOdwPmiFd8kd9yfPTq2W/svakE9LQSYuSjy4YyDxh d+98RxDgdJNR24URlu0mUWzOGnsCVs1UjH4OsDvqm+LOO6IJPbL6nC+hIIWKn58SepMY MJrWwppzWeGEGmQGGzWPuKevXk9LYN/HgMU/I+qpEZTd591k3LK1Sdn11bLVBR9fJZon jv9j/cbRE+okIkX9IOLweUNJ+McOWK57kNeiaCT4+p9HmOi7+EUQIPJ0tjFNigtDNkBD EPOZuel/RKqq9LYB9Pmv5nTxZcPIJHTuTN1VIqdslVNQg57+bhWL72j1GajSqE7WRVMx bTAw== X-Gm-Message-State: ALKqPwdit5BopSHBLdX8wWAaNyASAkePoBF5QUxSHKJmcdY4XmUGU+of 6qCI6AfCOfJmn2YQio7zg6Vhe+xFJnYZ0RYQFhBRxg== X-Google-Smtp-Source: AB8JxZoPFJ7FF31bGrhjh1ZHVW4xh1A+Hkk1i/yrdUubF1Eff5Y2dNwgu11MvGqZKSb0wF52huZaMFZL5mqYcAV7cI0= X-Received: by 2002:a9d:2bec:: with SMTP id u99-v6mr204681ota.355.1527027584592; Tue, 22 May 2018 15:19:44 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Tue, 22 May 2018 15:19:44 -0700 (PDT) In-Reply-To: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> From: "K. Macy" Date: Tue, 22 May 2018 15:19:44 -0700 X-Google-Sender-Auth: H__e_xSXVagkjqoAwS6BHW9CL_E Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: "Rodney W. Grimes" Cc: "A. Wilcox" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 22:19:45 -0000 > I am concerned about just shoving it out to ports, as that makes > it rot even faster. > > I am still very concerned that our in base i9xx code is like 4 > years old and everyone is told to go to kmod-next from ports > as well. > > No, I do not have a solution, but I have not tried hard to find > one. I am sure if we try hard to find one it can be done. drm-next is a port and it's what most everyone will be using going forward. You're asking us to make a special case for a small vocal group of i386 users. If i386 is sufficiently important, its user base can support it. Cheers. -M From owner-freebsd-current@freebsd.org Tue May 22 22:47: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 4387BEE4713 for ; Tue, 22 May 2018 22:47:18 +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 A4DE76C881; Tue, 22 May 2018 22:47:17 +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 w4MMlFHe032111; Tue, 22 May 2018 15:47:15 -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 w4MMlFxm032110; Tue, 22 May 2018 15:47:15 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805222247.w4MMlFxm032110@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: To: "K. Macy" Date: Tue, 22 May 2018 15:47:15 -0700 (PDT) CC: "A. Wilcox" , 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.26 Precedence: 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, 22 May 2018 22:47:18 -0000 > > I am concerned about just shoving it out to ports, as that makes > > it rot even faster. > > > > I am still very concerned that our in base i9xx code is like 4 > > years old and everyone is told to go to kmod-next from ports > > as well. > > > > No, I do not have a solution, but I have not tried hard to find > > one. I am sure if we try hard to find one it can be done. > > drm-next is a port and it's what most everyone will be using going > forward. You're asking us to make a special case for a small vocal > group of i386 users. If i386 is sufficiently important, its user base > can support it. Are you saying there is only one way forward? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue May 22 23:26: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 B5416EE570E for ; Tue, 22 May 2018 23:26:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0206D9CE; Tue, 22 May 2018 23:26:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4MNQ4mq097758 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 May 2018 16:26:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4MNQ4SZ097757; Tue, 22 May 2018 16:26:04 -0700 (PDT) (envelope-from sgk) Date: Tue, 22 May 2018 16:26:03 -0700 From: Steve Kargl To: "K. Macy" Cc: "A. Wilcox" , FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522232603.GA97708@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 23:26:11 -0000 On Tue, May 22, 2018 at 02:56:55PM -0700, K. Macy wrote: > > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for PowerPC. > > > DRM2 doesn't support anything later than mid-Haswell. The chips in > question all pre-date 2007. Users of low-volume hardware on chips from > that period are welcome to continue to sustain themselves on the drm2 > port just as the other 95+% of the user base will use what is now > referred to as drm-next. Even by powerpc maintainers' admission DRM2 > also only barely works there. I've promised Justin that I'll make > drm-next work on Talos once POWER9 support is solid enough. % dmesg | CPU CPU: AMD FX(tm)-8350 Eight-Core Processor (4018.34-MHz K8-class CPU) % kldstat troutmask:sgk[205] kldstat Id Refs Address Size Name 9 1 0xffffffff8141e000 db148 radeonkms.ko 10 1 0xffffffff814fa000 3f7d0 drm2.ko 11 2 0xffffffff8153a000 acf8 agp.ko 12 1 0xffffffff81545000 12f9 radeonkmsfw_CAICOS_pfp.ko 13 1 0xffffffff81547000 16f7 radeonkmsfw_CAICOS_me.ko 14 1 0xffffffff81549000 d73 radeonkmsfw_BTC_rlc.ko 15 1 0xffffffff8154a000 5f97 radeonkmsfw_CAICOS_mc.ko Mid-Haswell? -- Steve From owner-freebsd-current@freebsd.org Tue May 22 23:32: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 AC9BEEE5B45 for ; Tue, 22 May 2018 23:32:41 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x234.google.com (mail-ot0-x234.google.com [IPv6:2607:f8b0:4003:c0f::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 44F456DE50 for ; Tue, 22 May 2018 23:32:41 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x234.google.com with SMTP id t1-v6so23015770ott.13 for ; Tue, 22 May 2018 16:32:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bmkblFGtlKw5OMvvGHANpk+e21wX9BBcP3+JEH1+keI=; b=IxFfR4FJD4oIFXxKfdNcNXs5QuGJSu6N/F43jrCa67okVgWVpj035o+gylG2QFSQKT lmFnRqtEuA5XCIBE1PZJFRi9jWUPYD4XlrFvWvkzMkPn5wTU6zESwKGyuZYziOB8v29w 4vXnSABm0X18RfbRDNkreGF2dpbGb+5LMu8fNdMOfaIzSAKhzBny8LljRaJDNDshmg5w 90Vpp0Oo7hB2+b2OSW4oLEQlc1ZBXXGxJjMAr1hTOZv82uCSWF2NugKEw5S3DbgMc0A2 ZJEbN4C64plRQ4pgGQE9fh5UHOZ8eWFRR091MlBxi0t2+CH0rjIktx2BFnezUVTwc+qx TyTg== 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=bmkblFGtlKw5OMvvGHANpk+e21wX9BBcP3+JEH1+keI=; b=R4CMI+W/bKt37/UStXXhDCa27POE+/gSLJdeY46AMCVVWHQZwT2+jaIsYlNNECyKaV BIF805gxvSownZdSulE9cGmH0Twew3v4Nv6CFNI8+GbSuUF1yWUFo5h1rkJt4HmE/Wl5 f2IrEFkkwoDzykmPcBln4p+vI+BlVb4/g4eYBLLhOurJQipc6NXXYCdi9J1a1KYEvcJA WsskySnoG6oUlpfTF/xJ2GS/GfetTsePc+Bk72vTp8yypEkLe9IRfKRUnvQuVtPQP1b1 fweFEg79NZWs/O3Teotj+iwT2qQJZ0dM0+vZDmhIRPPo3ARavv0TXKwG16BqTWpUvSQI BvBA== X-Gm-Message-State: ALKqPwdLI661z4nPMGYDRO7zwNp60yrsS6mVnvEvffLR4U7M3HKTsbDX By0XWpXq2ZA/55xeC3NfVFkuGKR9PMr0EOIgIZ+KBQ== X-Google-Smtp-Source: AB8JxZrZ9iTgCi1DmeR1hMixcpTf0/Vl53qsqefNUp86Oc+fj1lB0RPqqRaC0RS1hjC+ct5w3UhMXzoz/mBa2gRlF2k= X-Received: by 2002:a9d:3c0a:: with SMTP id q10-v6mr312085otc.39.1527031960224; Tue, 22 May 2018 16:32:40 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Tue, 22 May 2018 16:32:39 -0700 (PDT) In-Reply-To: <20180522232603.GA97708@troutmask.apl.washington.edu> References: <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> <20180522232603.GA97708@troutmask.apl.washington.edu> From: "K. Macy" Date: Tue, 22 May 2018 16:32:39 -0700 X-Google-Sender-Auth: ajz8dMCTHCLCjO99xU6vT8Im0KI Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Steve Kargl Cc: "A. Wilcox" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 23:32:41 -0000 Why are you running i386 on that? On Tue, May 22, 2018 at 4:26 PM, Steve Kargl wrote: > On Tue, May 22, 2018 at 02:56:55PM -0700, K. Macy wrote: >> > >> > >> > it makes me giggle that people still think non-amd64 is "legacy". >> > >> > i386 is alive and well - new chips are being fabbed based on the 586 >> > design with pci-e slots; not to mention things like the Talos and >> > AmigaOne for PowerPC. >> >> >> DRM2 doesn't support anything later than mid-Haswell. The chips in >> question all pre-date 2007. Users of low-volume hardware on chips from >> that period are welcome to continue to sustain themselves on the drm2 >> port just as the other 95+% of the user base will use what is now >> referred to as drm-next. Even by powerpc maintainers' admission DRM2 >> also only barely works there. I've promised Justin that I'll make >> drm-next work on Talos once POWER9 support is solid enough. > > % dmesg | CPU > CPU: AMD FX(tm)-8350 Eight-Core Processor (4018.34-MHz K8-class CPU) > % kldstat > troutmask:sgk[205] kldstat > Id Refs Address Size Name > 9 1 0xffffffff8141e000 db148 radeonkms.ko > 10 1 0xffffffff814fa000 3f7d0 drm2.ko > 11 2 0xffffffff8153a000 acf8 agp.ko > 12 1 0xffffffff81545000 12f9 radeonkmsfw_CAICOS_pfp.ko > 13 1 0xffffffff81547000 16f7 radeonkmsfw_CAICOS_me.ko > 14 1 0xffffffff81549000 d73 radeonkmsfw_BTC_rlc.ko > 15 1 0xffffffff8154a000 5f97 radeonkmsfw_CAICOS_mc.ko > > Mid-Haswell? > > -- > Steve From owner-freebsd-current@freebsd.org Tue May 22 23:36: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 92BCDEE5D65; Tue, 22 May 2018 23:36:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 324726E06A; Tue, 22 May 2018 23:36:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4MNZwTh097841 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 May 2018 16:35:58 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4MNZwPn097840; Tue, 22 May 2018 16:35:58 -0700 (PDT) (envelope-from sgk) Date: Tue, 22 May 2018 16:35:58 -0700 From: Steve Kargl To: Johannes Lundberg Cc: Current FreeBSD , FreeBSD X11 mailing list , "K. Macy" , Niclas Zeising , Oliver Pinter , Rozhuk Ivan , Warner Losh Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522233558.GB97708@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> 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.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 23:36:10 -0000 On Tue, May 22, 2018 at 07:50:39AM +0100, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. > > > > Or why not include drm-next to base svn repo and add some > > > > option to make.conf to swith drm2/dem-next ? > > > > > > Even if it's not being built on amd64 we're still responsible for > > > keeping it building on !amd64 so long as it's in base. This makes > > > changing APIs and universe runs more burdensome. The graphics > > > developers have given you notice that it will now be your collective > > > responsibility to keep it up to date. > > > > > > > Not quite. One graphics developer has indicated a desire > > to remove working code, because it interferes with the > > graphics developers' port on a single architecture. There > > is no indication by that graphics developer that drm2 will > > be available in ports. You can go read the original post > > here: > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html > > > > The last paragraph is > > > > What does the community think? Is there anyone still using > > the drm2 driver on 12-CURRENT? If so, what is preventing > > you from switching to the port? > > > > The answer to the last two questions are "yes" and "the port > > does not work on i386". > > > > What is wrong with using > > > > .if ${MACHINE_ARCH} != amd64 > > ... > > .endif > > > > to enable/disable drm2? > > The answer to the first question is that the consensus seem to be that > moving to a port is best for the _majority_. Best for amd64. For the majority, if one starts X, it automatically loads drm2 if one allows X to configure itself and drm2 applies. It's automatically loaded on both by i386 laptop and amd64 desktop. > Let me ask you, what’s wrong with this one-liner after base install > pkg install drm2 > ? 1) The original email did not indicate the code would be moved to a port. It simply said removed. 2) Nothing wrong if you know where to go looking for drm2. FreeBSD goes from having drm2 automatically loaded for a user to hoping that a user knows about a port. 3) I've already posted a 2-line patch for amd64 (twice actually). How many lines are needed to make the port? -- Steve From owner-freebsd-current@freebsd.org Tue May 22 23:42: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 850DAEE6313 for ; Tue, 22 May 2018 23:42:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 158996E5E1; Tue, 22 May 2018 23:42:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4MNgPik097907 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 May 2018 16:42:25 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4MNgPuJ097906; Tue, 22 May 2018 16:42:25 -0700 (PDT) (envelope-from sgk) Date: Tue, 22 May 2018 16:42:25 -0700 From: Steve Kargl To: "K. Macy" Cc: "A. Wilcox" , FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180522234225.GC97708@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> <20180522232603.GA97708@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 22 May 2018 23:42:27 -0000 On Tue, May 22, 2018 at 04:32:39PM -0700, K. Macy wrote: > Why are you running i386 on that? > I'm not. Just pointing out that drm2 runs on amd64 as well as i386. Also need to correct the dis-information that drm2 only applies to mid-Haswell and older. In the end, src committers will do what they want, so this is my last post. -- Steve From owner-freebsd-current@freebsd.org Wed May 23 01:29: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 73845EE8EEE for ; Wed, 23 May 2018 01:29:24 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 0D8AB714A8 for ; Wed, 23 May 2018 01:29:23 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (cpe-75-82-218-62.socal.res.rr.com [75.82.218.62]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w4N1TFKX008843 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 22 May 2018 18:29:15 -0700 Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: freebsd-current@freebsd.org References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> From: Nathan Whitehorn Message-ID: <3e261ac2-4be0-7105-277a-92cf63511cb4@freebsd.org> Date: Tue, 22 May 2018 21:29:14 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVbk+Lb7mpskeO26/bg7apa4WRnmgz9Tvex6fzes0CVqFrh46roLMFxwwG81g/gx54h3uG1xIg8XfWWiSLCLPooodowIYsrPHtY= X-Sonic-ID: C;/kRCtChe6BGhEMURjESG/g== M;sDGotChe6BGhEMURjESG/g== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 01:29:24 -0000 On 05/22/18 18:12, Rodney W. Grimes wrote: >>> >>> it makes me giggle that people still think non-amd64 is "legacy". >>> >>> i386 is alive and well - new chips are being fabbed based on the 586 >>> design with pci-e slots; not to mention things like the Talos and >>> AmigaOne for PowerPC. > Yes, some how we need to shake off the idea that all the world > is going to be 64 bit, and stop talking about EOL for 32 bit > x86, IMHO that would be a serious mistake. For one any VM > that does not need >4G of address space is a waste to run > in 64 bit mode. > >> DRM2 doesn't support anything later than mid-Haswell. The chips in >> question all pre-date 2007. Users of low-volume hardware on chips from > Um, haswell announced in 2011, started shipping in mid 2013, and last > product started to ship in 2015, so if "mid-haswell" is the supported > chip arrena that would be pre date 2012? > > Also as the Moore's law curve flattens expect the life of these > older, but not so old, machines to live quiet some time. I > believe we are talking sandy bridge and earlier? If that is > corret Sandy bridge is still a very viable system. > >> that period are welcome to continue to sustain themselves on the drm2 >> port just as the other 95+% of the user base will use what is now >> referred to as drm-next. Even by powerpc maintainers' admission DRM2 >> also only barely works there. I've promised Justin that I'll make >> drm-next work on Talos once POWER9 support is solid enough. > I think the original RFC has been answer, yes there are people still > using DRM2, and they wish to continue to use it into the 12.x time > frame. > > Lets find a technically agreeable solution to that, and move forward. > > I am concerned about just disabling the compile on amd64, > that typically leads to bit rot of the i386 code. > > I am concerned about just shoving it out to ports, as that makes > it rot even faster. > > I am still very concerned that our in base i9xx code is like 4 > years old and everyone is told to go to kmod-next from ports > as well. > > No, I do not have a solution, but I have not tried hard to find > one. I am sure if we try hard to find one it can be done. > > Regards, The real question in this thread is, I think: Do we want to co-version the drm kernel modules with kernel/OS releases or with the graphics drivers that use them (which are in ports)? I use the base modules (on 2014-era amd64 hardware), but would be perfectly happy with modules in ports and it seems like there is a compelling argument for co-versioning the things in x11-drivers with the kernel modules. I would like to make a proposal here: - Rename drm-next to drm-kmod - Move sys/dev/drm2 to a new port drm-kmod-legacy - Have one of the two, by default drm-kmod (amd64) or drm-kmod-legacy (i386), pulled in as a dependency by the relevant X11 drivers - Garbage-collect dev/drm, which supports 3DFX and Rage 128 and such archaic things I think this keeps the user experience intact and lets the graphics developers update in the way that works best for them. -Nathan From owner-freebsd-current@freebsd.org Wed May 23 03:52: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 E801BEEDB1A for ; Wed, 23 May 2018 03:52:36 +0000 (UTC) (envelope-from eadler@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 96DD675873 for ; Wed, 23 May 2018 03:52:36 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: from mail-yw0-f180.google.com (mail-yw0-f180.google.com [209.85.161.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: eadler) by smtp.freebsd.org (Postfix) with ESMTPSA id 6568524740 for ; Wed, 23 May 2018 03:52:36 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: by mail-yw0-f180.google.com with SMTP id p14-v6so258234ywe.10 for ; Tue, 22 May 2018 20:52:36 -0700 (PDT) X-Gm-Message-State: ALKqPwdyUvkhOtIhM03EVgefHUg6CP1NbMgEP8g2hWOTCQ6lbO3PSbSv sAAsCpaMH07iKJ4wPxHerFBOKI/fgJYkpz03EBZozA== X-Google-Smtp-Source: AB8JxZqNz+AFJL+jT4/pvqv5VHbkHH10xm/KJxwMfmegCe8paxvX5XoqzISfjWgRwiL1NDOvB+EpHNrXhm0XKQyQ6kg= X-Received: by 2002:a81:8605:: with SMTP id w5-v6mr575190ywf.162.1527047555780; Tue, 22 May 2018 20:52:35 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:c709:0:0:0:0:0 with HTTP; Tue, 22 May 2018 20:52:05 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Tue, 22 May 2018 20:52:05 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds) To: Mark Millard Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 03:52:37 -0000 On 21 May 2018 at 18:06, Mark Millard wrote: > On 2018-May-21, at 5:46 PM, Mark Millard wrote: > I should have been explicit that the material is from > ci.freebsd.org . Your email seems to always be marked as spam by my MUA even though SPF, DKIM, and DMARC pass. Apologies if you've sent me other mail I've missed. > For reference, the gcc based builds seem to be: > (all but the last being gcc 4.2.1 based if I > undertand right) FWIW believe these are fixed now. At least, they do not fail locally on "make universe" on top(1). -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-freebsd-current@freebsd.org Wed May 23 09:48: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 407AFEF6FE7 for ; Wed, 23 May 2018 09:48:43 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 898838119B; Wed, 23 May 2018 09:48:42 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fLQNs-0000G0C; Wed, 23 May 2018 11:48:40 +0200 Message-Id: To: "Rodney W. Grimes" Cc: "K. Macy" , "A. Wilcox" , FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com In-reply-to: Your message of "Tue, 22 May 2018 15:12:39 -0700 (PDT) ." <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> Date: Wed, 23 May 2018 11:48:38 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 09:48:43 -0000 >Also as the Moore's law curve flattens expect the life of these >older, but not so old, machines to live quiet some time. I >believe we are talking sandy bridge and earlier? If that is >corret Sandy bridge is still a very viable system. I noticed this lack of love for older systems recently. I wanted to use an older Dell server to test the 11.2 BETAs and RCs. Turns out, you can't install FreeBSD using a USB stick image because the BIOS only support MBR. No idea why MBR support was dropped for the USB images. In the end I had to find a CD burner, and after a couple of tries managed to install from CD. After that, my ansible playbooks started failing because /boot/loader.conf is absent if you boot from zfs in combination with MBR. Pity. This older server hardware is great for trying out new releases, play with zfs, etc. From owner-freebsd-current@freebsd.org Wed May 23 10:29: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 C36B6EF85C6 for ; Wed, 23 May 2018 10:29:29 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6096982D2D for ; Wed, 23 May 2018 10:29:29 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 90C7CE6077 for ; Wed, 23 May 2018 12:29:21 +0200 (CEST) Date: Wed, 23 May 2018 12:29:21 +0200 (CEST) Message-Id: <20180523.122921.74726348.sthaug@nethelp.no> To: freebsd-current@freebsd.org Subject: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver) From: sthaug@nethelp.no In-Reply-To: References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) 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.26 Precedence: 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, 23 May 2018 10:29:29 -0000 Hijacking a thread here, > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB images. > > In the end I had to find a CD burner, and after a couple of tries managed to > install from CD. On a somewhat related note - I recently installed 11.1-STABLE on a box with support for both UEFI and "good old fashioned BIOS". I initially used UEFI and GPT, but ended up switching to BIOS and MBR because I needed boot.config to enable booting from an alternate partition. Despite lots of Googling I couldn't find a simple way to do this using config stored on the disk itself (e.g. having "0:ad(0,f)/boot/loader" in /boot.config) with UEFI. Does anybody know if this can be done using UEFI? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current@freebsd.org Wed May 23 11:14: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 71C5BEFA2E9 for ; Wed, 23 May 2018 11:14:09 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAC4C85A00; Wed, 23 May 2018 11:14:08 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id q4-v6so2188465wmq.1; Wed, 23 May 2018 04:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JqS7pXGYCZ0fmFsDjqUAHCYyD+d+ArN+/iz5SA81m7w=; b=jnDxxfugLWDy0gkkizys/8vEzBpnsie1Y7A3f0j7xvcH/4Bti9qvJml6Sa0f066i5E Kiz4EtQ8DLS7BTHo/SGJ4i5ZBvz4KSFl6rOnV+Uu6o+UWOzMumK1/ztqFvjFZv6xJF9z 2EHB9xu0Ym1etaIVnwk0ZwBbCeLElGf3cGNyY4/ecgOgY01GDOYa+LsBBVlTjJe3C+3o Y9kWUsLK7JcpCJGuhVqsreoBZD3VF+fndtbDmJKueiUAfxTT1/xcfJ9Ur1uJhY/q2bsR iGIqTRySYy6tDpUwf8JxCjaA9xUQIrt58zv4ajUGfcLMjlHV5t7WylNImSKtuQxcYLOI UzFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JqS7pXGYCZ0fmFsDjqUAHCYyD+d+ArN+/iz5SA81m7w=; b=ZyYoCw5qQjxvkZsIXcFovZ8whFsm/+ZMSQhwk/jcAjCNi7R2T+2DdOhP3zzOrbrL/u joQdYuEGVH5J4lf7Ju50V+ht35hw0kbZGT/Gsa4+QbbfmlP3U3CYz6kDcJeFH+673fOE qUsrDJHnUjHQyt+YYfq588YzO5ALAKT7oOgl/Ja5mjLIrZeBsZeJtTjWfKMZKHXqWdmc +hQ9uPT4b6+UztdQJsswsb4R+B4tdKsvHwni+HQy8ialXU17rnu9LeR4q6Hsdye+jn2j NR1kgobhjhVjLM/cIK/tv9o/U0cOgHfjMEFYf80FOlqzTqr6S6nktZ51u9A5sqk3egqL EunA== X-Gm-Message-State: ALKqPwcZSxw2mmJigWXLn2IFSaiaDjKIT5nbE0AcORBWSulA94qSR2lZ bsTodsis1UKsgjBApNvoYT/qsY3cQGlCUDrPhUs= X-Google-Smtp-Source: AB8JxZr0scFmAxnlsLj2XbQEP7t0mk2qcvLLTKXf+RxjEQcoqmQ23I0F9ZzktApoQqMDet9f3yhM4sphD3IcMgj6DYc= X-Received: by 2002:a2e:404d:: with SMTP id n74-v6mr1516623lja.6.1527074047799; Wed, 23 May 2018 04:14:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:834c:0:0:0:0:0 with HTTP; Wed, 23 May 2018 04:14:07 -0700 (PDT) In-Reply-To: References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> From: Andreas Nilsson Date: Wed, 23 May 2018 13:14:07 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Philip Homburg Cc: "Rodney W. Grimes" , "K. Macy" , "A. Wilcox" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 11:14:09 -0000 On Wed, May 23, 2018 at 11:48 AM, Philip Homburg wrote: > >Also as the Moore's law curve flattens expect the life of these > >older, but not so old, machines to live quiet some time. I > >believe we are talking sandy bridge and earlier? If that is > >corret Sandy bridge is still a very viable system. > > I noticed this lack of love for older systems recently. > > I wanted to use an older Dell server to test the 11.2 BETAs and RCs. > > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB > images. > It's not that hard create a mbr based usb-stick. Far easier than to find a CD burner. > > In the end I had to find a CD burner, and after a couple of tries managed > to > install from CD. > > After that, my ansible playbooks started failing because /boot/loader.conf > is absent if you boot from zfs in combination with MBR. > I believe boot/loader.conf is something you have to create, it is not there by default. > > Pity. This older server hardware is great for trying out new releases, > play > with zfs, etc. > _______________________________________________ > 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 May 23 11:41: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 A3F3BEFADED for ; Wed, 23 May 2018 11:41:19 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 17B16867F1 for ; Wed, 23 May 2018 11:41:18 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fLS8p-0000HBC; Wed, 23 May 2018 13:41:15 +0200 Message-Id: To: Andreas Nilsson Cc: FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> In-reply-to: Your message of "Wed, 23 May 2018 13:14:07 +0200 ." Date: Wed, 23 May 2018 13:41:15 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 11:41:19 -0000 >It's not that hard create a mbr based usb-stick. Far easier than to find a >CD burner. 'Not hard' means - undocumented. Or at least, if you start with release notes and install instructions you won't find it. - Probably only works if you already have a FreeBSD system. And if it is indeed 'not hard', why not just generate such an image as part of the release build? >I believe boot/loader.conf is something you have to create, it is not there >by default. That's not the problem. The problem is that it lives on a separate zpool that is lost at every reboot. From owner-freebsd-current@freebsd.org Wed May 23 11: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 2E85FEFB0F1 for ; Wed, 23 May 2018 11:49:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (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 C51E686D98 for ; Wed, 23 May 2018 11:49:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P9600H00GM1AU00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 23 May 2018 10:49:03 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1527072543; bh=G8FZpYf4gy0n4BBCKI17wuuV1h7nd/BTscYmzHxh4gk=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=NV+nr/B8f/AirSaaNPsmp7osW5f+ljIVtfrl7JtgIvhG2zfIXlnuAe0LJI8BQWciJ 8JFXBZZTpawOgIytzH1bLfRC2y7Nm5DilGhVzDgoBrFRoKwDf74h+EkzxV5CTmogCt rC72m5OQA7JYuU6TtBHVL04lt2CcQnMzl4iEUBnfihKoAf2j1ptAg6PfXxluxmOqt4 VsuR0tE/nbB0qOuJMUlhzMiuqC1qOlUgbKUTGpYg2kC9w87U7R8Gl+zmC0LJgzJDlL 0LpgAUhvv4IOmKw1gdHwKilCWBDa+zYj+cvUO3VWIHooT6x1Am+4v4LnHr3j322cpE vO9uUSnJuFxxg== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P9600BWFGPNY550@st13p35im-asmtp001.me.com>; Wed, 23 May 2018 10:49:02 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-05-23_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1805230109 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver) From: Toomas Soome In-reply-to: <20180523.122921.74726348.sthaug@nethelp.no> Date: Wed, 23 May 2018 13:48:58 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <22882C48-69E4-4571-9C6A-F25D6E9CC7B3@me.com> References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> <20180523.122921.74726348.sthaug@nethelp.no> To: sthaug@nethelp.no X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 11:49:18 -0000 > On 23 May 2018, at 13:29, sthaug@nethelp.no wrote: >=20 > Hijacking a thread here, >=20 >> Turns out, you can't install FreeBSD using a USB stick image because = the >> BIOS only support MBR. No idea why MBR support was dropped for the = USB images. >>=20 >> In the end I had to find a CD burner, and after a couple of tries = managed to >> install from CD. >=20 > On a somewhat related note - I recently installed 11.1-STABLE on a box > with support for both UEFI and "good old fashioned BIOS". I initially > used UEFI and GPT, but ended up switching to BIOS and MBR because I > needed boot.config to enable booting from an alternate partition. >=20 > Despite lots of Googling I couldn't find a simple way to do this using > config stored on the disk itself (e.g. having "0:ad(0,f)/boot/loader" > in /boot.config) with UEFI. >=20 > Does anybody know if this can be done using UEFI? >=20 > Steinar Haug, Nethelp consulting, sthaug@nethelp.no it can but it a bit different situation there. you can not start bios = boot loader from UEFI loader or vice versa, you only can use the same = platform binaries. for UEFI case, the boot1.efi does not process boot.config, so you have = total 3 options - you switch boot disk in UEFI boot manager, or you use = chain command to load either bootx64.efi from target disk ESP partition = or you use chain command to load /boot/loader.efi from target disk = freebsd root file system. You also can set currdev to point to new root, = but usually you want a bit more (read in the configuration etc) so the = chainload may be a bit easier. Once you have figured out the proper file name to use with chain = command, you can set chain_disk to have it as value and you will have = chain menu entry=E2=80=A6 like = chain_disk=3Dzfs:zroot/ROOT/default:/boot/loader.efi rgds, toomas From owner-freebsd-current@freebsd.org Wed May 23 07:41: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 E4B2DEF3598 for ; Wed, 23 May 2018 07:41:36 +0000 (UTC) (envelope-from dp_pan@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 7867F7C72C for ; Wed, 23 May 2018 07:41:36 +0000 (UTC) (envelope-from dp_pan@yahoo.com) X-YMail-OSG: Abn20HQVM1nLVYPpJOT2MpefQWsZrspq2FWZ4upv1jwDeEOpr05i1bHVNnyS9CV 4vdGGpHGXh5OEJvnF3JZE9wino_RCCTP4VXiuIS4s9RdcVV514Sh533aNFIFSdIElQNG30HSVkd. f1XHuk_Xe_LGC0xjDTu3yPpLGp5th2aywZiHvuUyxsVxkUfG9Q8jyathDAN_eW7cFpD4fcIz_5go YAAJMUDLiWp3oinDnJEtKFOsGkZpB.hNEvAf20rczX_usNx8gfOJWWS7w1MNkil_KKHK.jcB3ZTI cHuc2ULDa.Ka7QWya7mSO1uh7nrlEWl.8LzIP3w.068i34PCUpSVGxWeJUNrvq7olJ91RPH2qfq1 v0VOCHmLdpX5Y5LgEkbYADrkS_MY3uDfBDosmcVWXQAgI9EPZmuRGObOV9jy7yYIyVb_Al_0RTjP MBaz1nQi.kpEMXjp0BBBI4..1WP5jHEa2OhR0q1X1DDI3JyWPkfN8KLtjHPDxAAlB7VmRXeY7ren NDrFRFPWoeeqwn7sIl_9k4xarZVJyepwwsziDvmlWCuWpkojwG4LANhGjm6hafG2T_qds0J_AX6j hOy66qEfo4UcrwSjzhjJdHkqSdsS0kcPSN3hs5TIq413rbh7CGNG53yDwDYUrf4upvoHwcaA- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.ne1.yahoo.com with HTTP; Wed, 23 May 2018 07:41:30 +0000 Date: Wed, 23 May 2018 07:41:25 +0000 (UTC) From: David Pan To: freebsd-current@freebsd.org Message-ID: <1366699076.177914.1527061285836@mail.yahoo.com> Subject: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 MIME-Version: 1.0 References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> X-Mailer: WebService/1.1.11897 YMailNorrin Mozilla/5.0 (X11; FreeBSD amd64; rv:59.0) Gecko/20100101 Firefox/59.0 X-Mailman-Approved-At: Wed, 23 May 2018 12:19:33 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 07:41:37 -0000 Hi: how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not drive the Intel Wireless Card. please help me fix that, thx David Pan From owner-freebsd-current@freebsd.org Wed May 23 12:21: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 2D750EFC822 for ; Wed, 23 May 2018 12:21:25 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A0FE668705 for ; Wed, 23 May 2018 12:21:24 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x234.google.com with SMTP id i12-v6so12958494wrc.4 for ; Wed, 23 May 2018 05:21:24 -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:cc; bh=giqRSS3PhjibfOSM/PburZOQRXcgq3U5vHasL9tC5EA=; b=VC+S77nvuOB3njU2W6Bd5G+0bgJXG3YNhkvzX8h36Tg6vpDSzQ6ZZNT6V8GO1G9A7F zja0bjif+J22+sVdntOJLIWeLIYGCdGdgyT96YWuuHWNsfcDfJtIw8QBIxBVTCHI6TAN 7c+YGQ3jLUUwzO+58hVE7Kiii7yfhZm0XzPvY6Fkk1pRtVtNp9VcJBXxkje/FXZNLH/M vq898CdTGCcwCytavdxOO4QXFiy+P+mHUwW5gkeCgv7yqUrm81UGOtgl/KVTcSrDRZ1m fUqjm85EXVbhpxUEjbrm9r0vOCP6q68dZWLrpH5H/x0wt4qk/qZNWt/MyyTbvuM2EEmk o7cw== 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:cc; bh=giqRSS3PhjibfOSM/PburZOQRXcgq3U5vHasL9tC5EA=; b=EOgnZgExcvA8SX9auojN4KIw9G8kkyLnSCqyE5crjLR/jsEGuBjLOz30rrsbo8UXNK MeGyo+B7hYKGZiLlhLYR2nRHUyfI3WeQ2idX2udoksF5c/G/JuOYEBMP1En2Z1ZRB2Lv MWEbq/z4X3E4XTTWi5IZh0qOb/UpnYtlRFqtzm2hLRtVMwm/WrPHYxlPdRA8hHbmSZLj fY5xtfb9VRQ3KU7mRNOgFsRBtfZWUESsbz9n+9u0J8rQDXE7+2uiM/m0NCBH84EJQc0q sT0NzfiD17xBegLu/nvr/vh+xTbFiWxnw7ne0y8g0nEz1SqnBK1+GEASImd/qBOJ1mN7 Ls0w== X-Gm-Message-State: ALKqPwdyv4XssG+Dv+hYDfdPPOBgqWPQDDdcz80y7R0OUQytZd03OtkM 3NMVBkqd78fnqOfE3v4mPo5NKMMXJ5TB4GBQP1Uw2A== X-Google-Smtp-Source: AB8JxZrHcQWG0PrCWeqVLzf8ylvjuN+OPEvgtz7ICllV6FmjGWX99VY6C6uJxLArC10Ef0vEepG94g3l4M5lwNUmzYA= X-Received: by 2002:adf:f74c:: with SMTP id z12-v6mr2430178wrp.165.1527078083384; Wed, 23 May 2018 05:21:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:a789:0:0:0:0:0 with HTTP; Wed, 23 May 2018 05:20:42 -0700 (PDT) From: Johannes Lundberg Date: Wed, 23 May 2018 13:20:42 +0100 Message-ID: Subject: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) To: FreeBSD Current Cc: Andreas Nilsson , Philip Homburg Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 12:21:25 -0000 On Wed, May 23, 2018 at 12:41 PM, Philip Homburg wrote: > >It's not that hard create a mbr based usb-stick. Far easier than to find a > >CD burner. > > 'Not hard' means > - undocumented. Or at least, if you start with release notes and install > instructions you won't find it. > - Probably only works if you already have a FreeBSD system. > > And if it is indeed 'not hard', why not just generate such an image as > part > of the release build? > As someone who burn memsticks weekly and don't own a cd r/w, I agree. It seems there's no way to download an .iso or .img image that will boot from usb on legacy bios. This is bad and should be fixed. We shouldn't expect people that want to experiment with FreeBSD on non-UEFI hardware to already have a FreeBSD installation where they can prepare boot media... They shouldn't have to. File a bug report in bugzilla and try to poke the right people (I don't know who is working in this area). I guess the options are, either we make a hybrid .img that'll boot off both (maybe not that easy if it requires changes to boot assembly code) or just add a -legacy-bios.img to the image generation scripts. This is important since it's about lowering the threshold of bringing people to FreeBSD and giving a good (i.e. working) first impression. > > >I believe boot/loader.conf is something you have to create, it is not > there > >by default. > > That's not the problem. The problem is that it lives on a separate zpool > that > is lost at every reboot. > > > _______________________________________________ > 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 May 23 15:23: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 4444EF0C23E for ; Wed, 23 May 2018 15:23:22 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C85D16FA03 for ; Wed, 23 May 2018 15:23:21 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x243.google.com with SMTP id y189-v6so4905944itb.2 for ; Wed, 23 May 2018 08:23:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3Ouimw0i2W61MnefbkUj5skAbRcHih6UB+jbjYO43r4=; b=elaLK3UU1z/EMS69/UaQxkj6ZnARxLeUEzcKmzoGrVjiTVBMCp3spP0ldLrWsuxz0V DSNCub1RXB8wsIrlIthoY5zk/vvOcKe5pMANrOrRyl11OqB9xiTrUv5eryfA91NS24C9 5VdoNIWGuF1+H9lYun5LMM5odk2/SdAWCieSutasrtZW5DshMWUMrILe6kHaSaHQFQP1 tSlhwbPRc67kWA+5OMbv3Sto2PZEdFDKlIQWJXSRe2r332BDqCnbrRNpOUkNf9tVLMYm L7eqb8h9Z5H4UVRQ1OMKyik1GKwOAyc4gidLvA/i35JTGzsJ0UvO1nRMvz9fAR5NRjOZ 4W1Q== 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=3Ouimw0i2W61MnefbkUj5skAbRcHih6UB+jbjYO43r4=; b=AOoo+VUC8stq0jeA5heCPNVF2wo1wPY/FMYRzOpr2yRVURUgIuoA3GbHp6V0D3lRFv hD2asWKhLy5jbUqbLxFJ0ibcEFHWUF6UTiM4YC/XvmkEYHECeI8Up2EBaxXWRk+16uL1 8k+rBA+XVrrwP8NDq8QRDz9BBCHnfA8gekZJoTKrpDWPS1tZ8YlS7j1+bVAUlzNUiMhT C+spXhBAKl2kxRjY8X1hDuPjKCOgjU2WzFezwAJHPa59WjdDJfXV3bHeQWu4vcdiU/NF xvln7gJmmdNQSirWB/FsFw69r3TjzzencSZgQnd7z97ZiyIgxn1uYJv8rnlSfEFRxR5/ 7Mbg== X-Gm-Message-State: ALKqPwclFJMYF/Qv2fmftWDYV4rB2/YRTzXAb0Ne7YGXWJe95DLaLiH+ tLfaNiOA0qo9ZBmqf53rgKgAAwQ2GV2h2tbmgDvMxxIj X-Google-Smtp-Source: ADUXVKIuyWLHLLbRLPg5roUE4uzmzPkOkdZy8hb2OTmKl0keqWsAOdQDzNC52LoPIRNhssGyQmcsWoqCDDRfBVSdVZU= X-Received: by 2002:a24:3555:: with SMTP id k82-v6mr5423398ita.49.1527088999626; Wed, 23 May 2018 08:23:19 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:82a7:0:0:0:0:0 with HTTP; Wed, 23 May 2018 08:22:59 -0700 (PDT) In-Reply-To: References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> From: Ed Maste Date: Wed, 23 May 2018 11:22:59 -0400 X-Google-Sender-Auth: dHDqLzXM2sBZGDyxf-qp8EWQGkw Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Philip Homburg Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 15:23:22 -0000 On 23 May 2018 at 05:48, Philip Homburg wrote: > > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB images. We haven't "dropped" MBR support, and our amd64 memstick images are a combined hybrid format and do in general boot on legacy systems. That said, there are a number of firmware implementations that refuse to boot from the hybrid format - this has been a problem with Lenovo firmware in particular. Those of you with a system unable to boot from our MBR images, can you reply to the "Boot USB memstick with MBR" fork of this thread with details about the system and firmware version? From owner-freebsd-current@freebsd.org Wed May 23 15:52: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 77240F105C1 for ; Wed, 23 May 2018 15:52:57 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.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 CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 280D57108C; Wed, 23 May 2018 15:52:57 +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 CE51C739B; Wed, 23 May 2018 15:52:56 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 23 May 2018 15:52:55 +0000 From: Glen Barber To: Philip Homburg Cc: "Rodney W. Grimes" , "K. Macy" , "A. Wilcox" , FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180523155255.GF24664@FreeBSD.org> References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ChQOR20MqfxkMJg9" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 15:52:57 -0000 --ChQOR20MqfxkMJg9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > >Also as the Moore's law curve flattens expect the life of these > >older, but not so old, machines to live quiet some time. I > >believe we are talking sandy bridge and earlier? If that is > >corret Sandy bridge is still a very viable system. >=20 > I noticed this lack of love for older systems recently.=20 >=20 > I wanted to use an older Dell server to test the 11.2 BETAs and RCs. >=20 > Turns out, you can't install FreeBSD using a USB stick image because the > BIOS only support MBR. No idea why MBR support was dropped for the USB im= ages. >=20 > In the end I had to find a CD burner, and after a couple of tries managed= to > install from CD. >=20 > After that, my ansible playbooks started failing because /boot/loader.con= f=20 > is absent if you boot from zfs in combination with MBR. >=20 > Pity. This older server hardware is great for trying out new releases, pl= ay=20 > with zfs, etc. The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now built as hybrid images, supporting both MBR and GPT, as well as being written to a flash drive (like memstick.img) as well as a CD. MBR support was initially removed from the memstick installer, as it is not compatible with some UEFI implementations. (Or, at least that is my understanding, based on my limited intimate knowledge of UEFI.) Glen --ChQOR20MqfxkMJg9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlsFjlYACgkQAxRYpUeP 4pN1iw/+JP5hVJglzq6xldtGrRbOHhhhce74/X15Vjg52/WkgCRLMoGedVNCK3xm KUmVRudZERzB+CT/At6Bbr65Nps96fmb85npAZbibv3e/rMhKV1+FSOSh79xbE+W wQjQH69hfyHZHZ5ak16X695+BaGbC5bVUiF2Nzl+SShKMqHhWl8UAUVVQRLWq7/9 M7kK3Jf/N/pRptImerRcAIpV0XJ8iCqezr6MbxB+WM4PKMFdJ0/9YE2vgWJhJMRC VnfZ1L+xcRTqniqxV7A6qP+gHXHclNckYTejn2kUHlZwZy3W8yb/y6XxdXmzSQBo Ew+EYG/H0TQFESjoqEe6N8UdkQqiWoHXaEGG+sBUF4/aULFgkKI7xsnLJf9Kylwj aTwzdckCUKC8mPcChtYU4ecwc1/O3YSiipAdnm1CID4Jt8jnZcc+5M9jUm2+TupK q9fRx8LjSL9keVC08Nce5VaOmEqp43nFdF7yL2aFAO9UdgDXg7o8JwoDcAqgx5xd lqhXTLYirXccyMhcQoRImZLkIvTnYAxeFHiCU6i7OfPrMft251dU78ZXm+RFZKSQ yrzsxkxZbhGn4XShdl+0Kzpl0Gps9a5ivTV4i+XEG2BNcuDSrHkHitm2237auVnX T2egQW7b73Wt1w7bpP5fFDd5mOyrcH6N+aJMdWVFBAt59PeqkC0= =rlUp -----END PGP SIGNATURE----- --ChQOR20MqfxkMJg9-- From owner-freebsd-current@freebsd.org Wed May 23 16:45: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 7A29CF1E764 for ; Wed, 23 May 2018 16:45:10 +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 0850272EC7 for ; Wed, 23 May 2018 16:45:09 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-185-240.albq.qwest.net [97.123.185.240]) (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 33ECE192888; Wed, 23 May 2018 08:52:20 +0000 (UTC) Subject: Re: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 To: freebsd-current@freebsd.org, dp_pan@yahoo.com References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> <1366699076.177914.1527061285836@mail.yahoo.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: Date: Wed, 23 May 2018 10:45:08 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <1366699076.177914.1527061285836@mail.yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ns6alA0EWYatOFUiFoUxgmMcdGwLKisaF" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 16:45:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ns6alA0EWYatOFUiFoUxgmMcdGwLKisaF Content-Type: multipart/mixed; boundary="yt9VL8ogyD61snvd8JeIHwiqxntui1Xvu"; protected-headers="v1" From: Sean Bruno To: freebsd-current@freebsd.org, dp_pan@yahoo.com Message-ID: Subject: Re: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> <1366699076.177914.1527061285836@mail.yahoo.com> In-Reply-To: <1366699076.177914.1527061285836@mail.yahoo.com> --yt9VL8ogyD61snvd8JeIHwiqxntui1Xvu Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/23/18 01:41, David Pan wrote: > Hi: > how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeB= SD 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not drive the = Intel Wireless Card. > please help me fix that, >=20 > thx > David Pan >=20 This seems to be a "iwm(4)" device. Try loading this driver in loader.co= nf. https://www.freebsd.org/doc/handbook/network-wireless.html sean --yt9VL8ogyD61snvd8JeIHwiqxntui1Xvu-- --Ns6alA0EWYatOFUiFoUxgmMcdGwLKisaF 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/LYFAlsFmpRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LZc0QgAufPJwZiGPLCPwc1xhNPUNhDbNR26nHvyGf85doxZIpe15bjhmgfUkUMc aeNYDia/y0vyAX1LvC1Mdr9CE2oPQPFH08HOKYbfG7eEVUUguipZveccxkHJMvMG 71PnViHjmBZcpp0O81UapPXr9bTALdJcFJiSsWMz4Lo8G5Cl3NwzS8v73v4aM2cM BY/9+7rEl2WnOAS9/6n/vHd5AKeX0PxM1TVuE2E3Bo6lfiQqoWDVsDyEoKE3hjLe PB5EjPHeOHAljXi+RVkePYzpTuBExbpnTLS8srmpdaSko3CocLuBOITGDvuOtc+t EKbYRJWrUVpW8ypgjAQnje9wwDclEw== =Pr5j -----END PGP SIGNATURE----- --Ns6alA0EWYatOFUiFoUxgmMcdGwLKisaF-- From owner-freebsd-current@freebsd.org Wed May 23 16:46: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 EA6D3F1E82F for ; Wed, 23 May 2018 16:46:16 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::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 732BC730CC for ; Wed, 23 May 2018 16:46:16 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id b453b907 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 23 May 2018 09:46:14 -0700 (PDT) Subject: Re: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 To: David Pan , freebsd-current@freebsd.org References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> <1366699076.177914.1527061285836@mail.yahoo.com> From: Pete Wright Message-ID: <99b881e0-9915-e859-070c-df40673400f1@nomadlogic.org> Date: Wed, 23 May 2018 09:46:13 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <1366699076.177914.1527061285836@mail.yahoo.com> 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.26 Precedence: 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, 23 May 2018 16:46:17 -0000 On 05/23/2018 00:41, David Pan wrote: > Hi: > how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not drive the Intel Wireless Card. > please help me fix that, I have this working on my end under both 12-current and 11-stable. here's my configuration: output from "pciconf -lv" iwm0@pci0:3:0:0:    class=0x028000 card=0x10108086 chip=0x24fd8086 rev=0x78 hdr=0x00     vendor     = 'Intel Corporation'     device     = 'Wireless 8265 / 8275'     class      = network to bring up the card i have added this entry to /etc/rc.conf: kld_list="if_iwm" then configuring the interface is the same as any other wifi as per the handbook, the device will be available as "iwm0". hope this helps, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed May 23 21:51: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 0D5DAEE8C1C for ; Wed, 23 May 2018 21:51:40 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 5135881030 for ; Wed, 23 May 2018 21:51:38 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fLbfT-0000H1C; Wed, 23 May 2018 23:51:35 +0200 Message-Id: To: Johannes Lundberg Cc: FreeBSD Current , Andreas Nilsson Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com In-reply-to: Your message of "Wed, 23 May 2018 13:20:42 +0100 ." Date: Wed, 23 May 2018 23:51:35 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 23 May 2018 21:51:40 -0000 I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 BIOS version 2.7.0. With both images, the USB stick is not recognized. For reference I tried an image for a random other OS and in that case the USB stick is recognized. I'll try to experiment a bit to see if I can find what causes the issue. From owner-freebsd-current@freebsd.org Wed May 23 23:21: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 D9B45EED148 for ; Wed, 23 May 2018 23:21:24 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EC21845A6 for ; Wed, 23 May 2018 23:21:24 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1527117676; bh=b1BmTTa7KUaeLHsq/D+6TF2SWLqdrObSwiswZ7C pCYk=; b=Jl1xy08/7ehQZvZInaPuv5cWSwzOfLxEGYm/faEjaPcVZaZY0nmRjSw /2Nb6cTT2f99HpKo4fZ/0P0HCM8bsKFgFUe/9aqv7PCpMoipmi0ZJ+h3ffkbiT/Y JqvuMeMICVFFoDGKwR66cfBXgXl9NBbi8yP2cZcGaccgJNahI5r4= Received: from toshi.auburn.protected-networks.net (unknown [IPv6:2001:470:1f07:4e1::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id E8A2521C35 for ; Wed, 23 May 2018 19:21:15 -0400 (EDT) To: freebsd-current From: Michael Butler Subject: kernel -current build failures Openpgp: preference=signencrypt Message-ID: Date: Wed, 23 May 2018 19:21:14 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 23 May 2018 23:21:25 -0000 On a device with bluetooth (as in GENERIC modules) .. --- ng_ether.o --- /usr/src/sys/netgraph/ng_ether.c:871:2: error: no member named 'tqh_first' in 'struct ifnethead'; did you mean 'stqh_first'? TAILQ_FOREACH(ifp, &V_ifnet, if_link) { ^ /usr/src/sys/sys/queue.h:724:15: note: expanded from macro 'TAILQ_FOREACH' for ((var) = TAILQ_FIRST((head)); \ ^ /usr/src/sys/sys/queue.h:721:36: note: expanded from macro 'TAILQ_FIRST' #define TAILQ_FIRST(head) ((head)->tqh_first) ^ On a system without IPSEC .. --- kernel --- linking kernel ld: error: undefined symbol: vnet_entry_ipsec4stat >>> referenced by key.c >>> key.o:(key_allocsp) ld: error: undefined symbol: vnet_entry_ipsec4stat >>> referenced by key.c >>> key.o:(key_allocsp) *** [kernel] Error code 1 Michael From owner-freebsd-current@freebsd.org Thu May 24 01:33: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 1266FEF1828 for ; Thu, 24 May 2018 01:33:38 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 AFE006A335 for ; Thu, 24 May 2018 01:33:37 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 0A09E21B00 for ; Wed, 23 May 2018 21:33:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 23 May 2018 21:33:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=KAbyOKyvipi89B25b L0Sv8dkA5ZCVV3QCKaKci7mj68=; b=Yd9p+PEAn6BjkNARPU/cGZw/fpansWSBB YkyCI6n3tgyCRDvQzR4rHW4iiR6cChgof71bDhlV1rLFAivRPncAJ1YbJGDBcTPp aoMVmVSp5o8+kFXFE8ALCF6VyGurw9VZ655LPlD4kSoSkiJgLiIjQ94FOENKANCx Fp3pJcD/gRmvpLYve5/5zOzjcF95GrqdJb0gJM4cbMTmKHaei9T4D8361m2Xik6b EkzfTsqOAAImB7ehhDaHFiFTz18Tenh4SpKk00DSkNNdKyOxeT1Bd4Ozx/lhixLp BzxmiDg3WeRxvXUda3DX4+Oa90CM5kxu4IiQaMudO3c3HFYnHG4rw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=KAbyOKyvipi89B25bL0Sv8dkA5ZCVV3QCKaKci7mj68=; b=Bz+32a0u XqVugfQ6Bj7FqcVwX3FXfbaLIlr4kj2JdDLbKb4ZIZAoB+Bw75TfawRu8mSRnB9L vhBb9mtdfuaDL+bBpmXrx0QvYzuaGlFsQw0mMc5oH+sXJQVF/FSW13C5SIgeXtxS NgH/cZFaC6zcDeEf//4XL8ANYnJ5tRPz66TOG60KnRRH+aiI9I3RFHlx3NvyEeSE iwy0wmJlP45KSFNw8b2AFTsEe1FgDboKBwvvexNZebM/xLgRTwZgO7wtnljVRdEm 3HvEVZwSRpHyxmH3fk0xrD/8KCp/a034GkAjix/dxAJAXTnF4QZKQOGMfrzeorO7 i2nsExMUlCd4kQ== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.2] (unknown [94.233.224.193]) by mail.messagingengine.com (Postfix) with ESMTPA id 7E857E4F0B for ; Wed, 23 May 2018 21:33:35 -0400 (EDT) To: freebsd-current From: Yuri Pankov Subject: pciconf -l doesn't show any devices on Hyper-V VM Message-ID: <140b87e9-8e37-e4b8-4adb-e881a1843408@yuripv.net> Date: Thu, 24 May 2018 04:33:35 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------B95AF418080004A458E313CB" Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 01:33:38 -0000 This is a multi-part message in MIME format. --------------B95AF418080004A458E313CB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606 snapshot as a VM on Hyper-V, `pciconf -l` (and `lspci`, expected) doesn't return any information. Hyper-V Version: 10.0.14393 [SP2] (that's Windows 2016 with Hyper-V role). dmesg.boot is attached in case it's useful. --------------B95AF418080004A458E313CB Content-Type: text/plain; charset=UTF-8; name="dmesg.boot" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.boot" Q29weXJpZ2h0IChjKSAxOTkyLTIwMTggVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0 IChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAx OTkzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1h cmsgb2YgVGhlIEZyZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCAxMi4wLUNVUlJFTlQgIzAg cjMzMzYwNjogTW9uIE1heSAxNCAxOTo1OTowOCBVVEMgMjAxOAogICAgcm9vdEByZWxlbmcz Lm55aS5mcmVlYnNkLm9yZzovdXNyL29iai91c3Ivc3JjL2FtZDY0LmFtZDY0L3N5cy9HRU5F UklDIGFtZDY0CkZyZWVCU0QgY2xhbmcgdmVyc2lvbiA2LjAuMCAodGFncy9SRUxFQVNFXzYw MC9maW5hbCAzMjY1NjUpIChiYXNlZCBvbiBMTFZNIDYuMC4wKQpXQVJOSU5HOiBXSVRORVNT IG9wdGlvbiBlbmFibGVkLCBleHBlY3QgcmVkdWNlZCBwZXJmb3JtYW5jZS4KU1JBVDogSWdu b3JpbmcgbWVtb3J5IGF0IGFkZHIgMHgxMDgyMDAwMDAKU1JBVDogSWdub3JpbmcgbWVtb3J5 IGF0IGFkZHIgMHgxMDAwMDAwMDAwClNSQVQ6IElnbm9yaW5nIG1lbW9yeSBhdCBhZGRyIDB4 MTAwMDAyMDAwMDAKU1JBVDogSWdub3JpbmcgbWVtb3J5IGF0IGFkZHIgMHgyMDAwMDIwMDAw MApTUkFUOiBJZ25vcmluZyBtZW1vcnkgYXQgYWRkciAweDQwMDAwMjAwMDAwClNSQVQ6IEln bm9yaW5nIG1lbW9yeSBhdCBhZGRyIDB4ODAwMDAyMDAwMDAKVlQoZWZpZmIpOiByZXNvbHV0 aW9uIDEwMjR4NzY4Ckh5cGVyLVYgVmVyc2lvbjogMTAuMC4xNDM5MyBbU1AyXQogIEZlYXR1 cmVzPTB4MmU3ZjxWUFJVTlRJTUUsVE1SRUZDTlQsU1lOSUMsU1lOVE0sQVBJQyxIWVBFUkNB TEwsVlBJTkRFWCxSRUZUU0MsSURMRSxUTUZSRVE+CiAgUE0gRmVhdHVyZXM9MHgwIFtDMl0K ICBGZWF0dXJlczM9MHhlZDdiMjxERUJVRyxYTU1IQyxJRExFLE5VTUEsVE1GUkVRLFNZTkNN QyxDUkFTSCxOUElFUD4KVGltZWNvdW50ZXIgIkh5cGVyLVYiIGZyZXF1ZW5jeSAxMDAwMDAw MCBIeiBxdWFsaXR5IDIwMDAKQ1BVOiBBTUQgT3B0ZXJvbih0bSkgUHJvY2Vzc29yIDYyNjIg SEUgICAgICAgICAgICAgICAoMTYwMC4wMS1NSHogSzgtY2xhc3MgQ1BVKQogIE9yaWdpbj0i QXV0aGVudGljQU1EIiAgSWQ9MHg2MDBmMTIgIEZhbWlseT0weDE1ICBNb2RlbD0weDEgIFN0 ZXBwaW5nPTIKICBGZWF0dXJlcz0weDE3ODNmYmZmPEZQVSxWTUUsREUsUFNFLFRTQyxNU1Is UEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQR0UsTUNBLENNT1YsUEFULFBTRTM2LE1NWCxG WFNSLFNTRSxTU0UyLEhUVD4KICBGZWF0dXJlczI9MHg5ZTk4MjIwMzxTU0UzLFBDTE1VTFFE USxTU1NFMyxDWDE2LFNTRTQuMSxTU0U0LjIsUE9QQ05ULEFFU05JLFhTQVZFLE9TWFNBVkUs QVZYLEhWPgogIEFNRCBGZWF0dXJlcz0weDJlNTAwODAwPFNZU0NBTEwsTlgsTU1YKyxGRlhT UixQYWdlMUdCLFJEVFNDUCxMTT4KICBBTUQgRmVhdHVyZXMyPTB4MTBiZjM8TEFIRixDTVAs Q1I4LEFCTSxTU0U0QSxNQVMsUHJlZmV0Y2gsT1NWVyxYT1AsRk1BND4KSHlwZXJ2aXNvcjog T3JpZ2luID0gIk1pY3Jvc29mdCBIdiIKcmVhbCBtZW1vcnkgID0gNDI5NDk2NzI5NiAoNDA5 NiBNQikKYXZhaWwgbWVtb3J5ID0gNDEwMDcxMDQwMCAoMzkxMCBNQikKRXZlbnQgdGltZXIg IkxBUElDIiBxdWFsaXR5IDYwMApBQ1BJIEFQSUMgVGFibGU6IDxWUlRVQUwgTUlDUk9TRlQ+ CkZyZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBTeXN0ZW0gRGV0ZWN0ZWQ6IDggQ1BVcwpG cmVlQlNEL1NNUDogMSBwYWNrYWdlKHMpIHggOCBjb3JlKHMpCnJhbmRvbTogdW5ibG9ja2lu ZyBkZXZpY2UuCmlvYXBpYzAgPFZlcnNpb24gMS4xPiBpcnFzIDAtMjMgb24gbW90aGVyYm9h cmQKTGF1bmNoaW5nIEFQczogNyAyIDEgMyA2IDUgNApyYW5kb206IGVudHJvcHkgZGV2aWNl IGV4dGVybmFsIGludGVyZmFjZQpUaW1lY291bnRlciAiSHlwZXItVi1UU0MiIGZyZXF1ZW5j eSAxMDAwMDAwMCBIeiBxdWFsaXR5IDMwMDAKW2F0aF9oYWxdIGxvYWRlZAprYmQwIGF0IGti ZG11eDAKbW9kdWxlX3JlZ2lzdGVyX2luaXQ6IE1PRF9MT0FEICh2ZXNhLCAweGZmZmZmZmZm ODEwYjg2MTAsIDApIGVycm9yIDE5Cm5ldG1hcDogbG9hZGVkIG1vZHVsZQpuZXh1czAKY3J5 cHRvc29mdDA6IDxzb2Z0d2FyZSBjcnlwdG8+IG9uIG1vdGhlcmJvYXJkCmFjcGkwOiA8VlJU VUFMIE1JQ1JPU0ZUPiBvbiBtb3RoZXJib2FyZApjcHUwOiA8QUNQSSBDUFU+IG9uIGFjcGkw CmF0cnRjMDogPEFUIHJlYWx0aW1lIGNsb2NrPiBwb3J0IDB4NzAtMHg3MSBpcnEgOCBvbiBh Y3BpMAphdHJ0YzA6IHJlZ2lzdGVyZWQgYXMgYSB0aW1lLW9mLWRheSBjbG9jaywgcmVzb2x1 dGlvbiAxLjAwMDAwMHMKRXZlbnQgdGltZXIgIlJUQyIgZnJlcXVlbmN5IDMyNzY4IEh6IHF1 YWxpdHkgMApUaW1lY291bnRlciAiQUNQSS1mYXN0IiBmcmVxdWVuY3kgMzU3OTU0NSBIeiBx dWFsaXR5IDkwMAphY3BpX3RpbWVyMDogPDMyLWJpdCB0aW1lciBhdCAzLjU3OTU0NU1Iej4g cG9ydCAweDQwOC0weDQwYiBvbiBhY3BpMAphY3BpX3N5c2NvbnRhaW5lcjA6IDxTeXN0ZW0g Q29udGFpbmVyPiBpb21lbSAweGZlMDAwMDAwMC0weGZmZmZmZmZmZiwweGY4MDAwMDAwLTB4 ZmZkZmZmZmYgb24gYWNwaTAKdm1idXMwOiA8SHlwZXItViBWbWJ1cz4gb24gYWNwaV9zeXNj b250YWluZXIwCnZtYnVzX3JlczA6IDxIeXBlci1WIFZtYnVzIFJlc291cmNlPiBpcnEgNSBv biBhY3BpMApaRlMgTk9USUNFOiBQcmVmZXRjaCBpcyBkaXNhYmxlZCBieSBkZWZhdWx0IGlm IGxlc3MgdGhhbiA0R0Igb2YgUkFNIGlzIHByZXNlbnQ7CiAgICAgICAgICAgIHRvIGVuYWJs ZSwgYWRkICJ2ZnMuemZzLnByZWZldGNoX2Rpc2FibGU9MCIgdG8gL2Jvb3QvbG9hZGVyLmNv bmYuClpGUyBmaWxlc3lzdGVtIHZlcnNpb246IDUKWkZTIHN0b3JhZ2UgcG9vbCB2ZXJzaW9u OiBmZWF0dXJlcyBzdXBwb3J0ICg1MDAwKQpUaW1lY291bnRlcnMgdGljayBldmVyeSAxMC4w MDAgbXNlYwp1c2JfbmVlZHNfZXhwbG9yZV9hbGw6IG5vIGRldmNsYXNzCnZtYnVzMDogdmVy c2lvbiAzLjAKaHZldDA6IDxIeXBlci1WIGV2ZW50IHRpbWVyPiBvbiB2bWJ1czAKRXZlbnQg dGltZXIgIkh5cGVyLVYiIGZyZXF1ZW5jeSAxMDAwMDAwMCBIeiBxdWFsaXR5IDEwMDAKaHZr YmQwOiA8SHlwZXItViBLQkQ+IG9uIHZtYnVzMApodmhlYXJ0YmVhdDA6IDxIeXBlci1WIEhl YXJ0YmVhdD4gb24gdm1idXMwCmh2a3ZwMDogPEh5cGVyLVYgS1ZQPiBvbiB2bWJ1czAKaHZz aHV0ZG93bjA6IDxIeXBlci1WIFNodXRkb3duPiBvbiB2bWJ1czAKaHZ0aW1lc3luYzA6IDxI eXBlci1WIFRpbWVzeW5jPiBvbiB2bWJ1czAKaHZ0aW1lc3luYzA6IFJUVApodnZzczA6IDxI eXBlci1WIFZTUz4gb24gdm1idXMwCmhuMDogPEh5cGVyLVYgTmV0d29yayBJbnRlcmZhY2U+ IG9uIHZtYnVzMApobjA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOjE1OjVkOjAxOjA0OjAwCmhu MDogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIFVQCnN0b3J2c2MwOiA8SHlwZXItViBTQ1NJPiBv biB2bWJ1czAKaG4xOiA8SHlwZXItViBOZXR3b3JrIEludGVyZmFjZT4gb24gdm1idXMwCmRh MCBhdCBzdG9ydnNjMCBidXMgMCBzY2J1czAgdGFyZ2V0IDAgbHVuIDAKZGEwOiA8TXNmdCBW aXJ0dWFsIERpc2sgMS4wPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNQQy0zIFNDU0kgZGV2aWNl CmRhMDogMzAwLjAwME1CL3MgdHJhbnNmZXJzCmRhMDogQ29tbWFuZCBRdWV1ZWluZyBlbmFi bGVkCmRhMDogNjU1MzZNQiAoMTM0MjE3NzI4IDUxMiBieXRlIHNlY3RvcnMpCmNkMCBhdCBz dG9ydnNjMCBidXMgMCBzY2J1czAgdGFyZ2V0IDAgbHVuIDEKY2QwOiA8TXNmdCBWaXJ0dWFs IERWRC1ST00gMS4wPiBSZW1vdmFibGUgQ0QtUk9NIFNQQy0zIFNDU0kgZGV2aWNlCmNkMDog MzAwLjAwME1CL3MgdHJhbnNmZXJzCmNkMDogODI4TUIgKDQyNDAzMyAyMDQ4IGJ5dGUgc2Vj dG9ycykKaG4xOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDoxNTo1ZDowMTowNDowMQpobjE6IGxp bmsgc3RhdGUgY2hhbmdlZCB0byBET1dOClRyeWluZyB0byBtb3VudCByb290IGZyb20gemZz Onpyb290L1JPT1QvZGVmYXVsdCBbXS4uLgpXQVJOSU5HOiBXSVRORVNTIG9wdGlvbiBlbmFi bGVkLCBleHBlY3QgcmVkdWNlZCBwZXJmb3JtYW5jZS4KbG8wOiBsaW5rIHN0YXRlIGNoYW5n ZWQgdG8gVVAK --------------B95AF418080004A458E313CB-- From owner-freebsd-current@freebsd.org Thu May 24 01:35: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 07548EF19D6 for ; Thu, 24 May 2018 01:35:53 +0000 (UTC) (envelope-from eadler@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 ACB446A4BB for ; Thu, 24 May 2018 01:35:52 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.161.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: eadler) by smtp.freebsd.org (Postfix) with ESMTPSA id 77486C9CB for ; Thu, 24 May 2018 01:35:52 +0000 (UTC) (envelope-from eadler@freebsd.org) Received: by mail-yw0-f178.google.com with SMTP id u83-v6so4668ywc.4 for ; Wed, 23 May 2018 18:35:52 -0700 (PDT) X-Gm-Message-State: ALKqPwcqGDc1bbWBT0UBsx8Hqd4FjgPXeBjXTUbZWvimQ2LVXn3/zjiJ KBcBVR6q/4/BV57hI9MjPyijHrHgbCI/xGVGCQUxGA== X-Google-Smtp-Source: AB8JxZq8RYQc9ZnatJanZRX4UJbpBkJfStFD25gbyzjCxtvpFxUS9d6pxQsXsmM7rxBCKxF2mwovIM5D+xP/S048lC0= X-Received: by 2002:a81:3e1f:: with SMTP id l31-v6mr2775735ywa.37.1527125752027; Wed, 23 May 2018 18:35:52 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:c709:0:0:0:0:0 with HTTP; Wed, 23 May 2018 18:35:21 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Wed, 23 May 2018 18:35:21 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org To: Mark Millard 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.26 Precedence: 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, 24 May 2018 01:35:53 -0000 I got this. not marked as spam On 23 May 2018 at 18:34, Mark Millard wrote: > [This submittal is in part an experiment with how Eitan's > MUA classifies the Email using an alternate yahoo.com > address. Eitan: the subject and this note are all unique > to this message.] > > I've reported to Eitan that the gcc/g++ 4.2.1 architectures > are failing for devd build failures. > > Examples include: > > --- all_subdir_sbin --- > cc1plus: warnings being treated as errors > /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_strin= g.h: In member function 'std::basic_string<_CharT, _Traits, _Alloc>::_Rep* = std::basic_string<_CharT, _Traits, _Alloc>::_M_rep() const [with _CharT =3D= char, _Traits =3D std::char_traits, _Alloc =3D std::allocator]= ': > /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_strin= g.h:493: instantiated from 'std::basic_string<_CharT, _Traits, _Alloc>::~= basic_string() [with _CharT =3D char, _Traits =3D std::char_traits, _= Alloc =3D std::allocator]' > /usr/src/sbin/devd/devd.hh:149: instantiated from here > /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_strin= g.h:288: warning: cast from 'char*' to 'std::basic_string, std::allocator >::_Rep*' increases required alignment of= target type > > mips64 and mips and sparc64 agree, for example. > > powerpc and powerpc64 report: > > --- all_subdir_sbin --- > cc1plus: warnings being treated as errors > /usr/src/sbin/devd/devd.hh: In function 'void __tcf_0(void*)': > /usr/src/sbin/devd/devd.hh:150: warning: inlining failed in call to 'virt= ual config::~config()': --param max-inline-insns-single limit reached > /usr/src/sbin/devd/devd.cc:175: warning: called from here > > but I expect the two sets of types of error message are related > somehow and the "fix" fixes both types. > > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > --=20 Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-freebsd-current@freebsd.org Thu May 24 03:05: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 B1882EF7AD9 for ; Thu, 24 May 2018 03:05:46 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28D556EA14 for ; Thu, 24 May 2018 03:05:46 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-wr0-x234.google.com with SMTP id w3-v6so223715wrl.12 for ; Wed, 23 May 2018 20:05:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EqNI562YJJ27BFx9H4D4nqBKmEgD8iJF0k2PJrabi6g=; b=kztxYMcemh7FN3EblS2vkP6uQ987Q0j9Xd5cduVMdZpFKLcWNvLJher5+5wcqVOUgp uHATFXiRcQ9cTuQ+OftIF9Wz6NVQ0tt44nfSNVZM+CYjOJ2xCTxJ57heUuWCZDWUG6ng 1rnmg6L2N7uz8XkdYyc0ynGcGSPvTE1CUyYsh8rW6dYfV6thAUq5aU1OFcwRezWhjK8P 81EgzELhgQLMHlorof1aC4Pok3t/BUw3qtWORGE1Ju+Bz8Wl6OwqZXsukgraFpF0A4Wz WJPhKm3/DjLcfiqMIJx/XeHP0NiE5KvOkl7VGbfzqVhLqkfgcS6JLvj1AFPTg7j63UM3 Vi7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EqNI562YJJ27BFx9H4D4nqBKmEgD8iJF0k2PJrabi6g=; b=eKauXyVX4vDeA2FHxYpbInloEDSdVk4+jppqvjGASD+kjFARyrHKgp6FVar+DUtTiY N5YytOvT4r+HeHvh2ANHupgQmNBZVmKeu2uten+ojbCGerRljVVHdC8JHMOe8IO1XUPN 21Yaqt8FVHh1DLnsEIV2hC7df9igbQdAS5cYtBDxCEVNBqz/uUmi7V19SV/X9VEx7Kt9 lNDkr7P0ohtfzj8qR11sXWoV3m/zvl99EZiDFvr/AXpzm/ngKtiLLnx02kmlFkWoQ2Mc hp0ZUi7S4PNZbKUsCu/a2tlCBRkCG4QkhgFgWuSmMMeCBbb8QwAGh7pRw25aH3qpNyXm RfOQ== X-Gm-Message-State: ALKqPwcWhqulpXunHEIRAbtrBmiusgSdhT5uiaPubGUtt1vIXKhLv3R9 Wretec0Jot99HGwEKIoLskS62ZgAriiq8scqSA== X-Google-Smtp-Source: AB8JxZrgCchBSNi4zbnEsGFrHZsRLfnAd/wx2LJZE8lIJrfpHTS3LehNwLScHLaH0de7qEf/WIhmJzV/69wLo1fTk3s= X-Received: by 2002:a19:e585:: with SMTP id i5-v6mr3037992lfk.63.1527131144825; Wed, 23 May 2018 20:05:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:415d:0:0:0:0:0 with HTTP; Wed, 23 May 2018 20:05:44 -0700 (PDT) In-Reply-To: <140b87e9-8e37-e4b8-4adb-e881a1843408@yuripv.net> References: <140b87e9-8e37-e4b8-4adb-e881a1843408@yuripv.net> From: Sepherosa Ziehau Date: Thu, 24 May 2018 11:05:44 +0800 Message-ID: Subject: Re: pciconf -l doesn't show any devices on Hyper-V VM To: Yuri Pankov Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 03:05:46 -0000 Gen1 or Gen2? On Gen2 Hyper-V, there is _no_ pcib0 and pci0 at all; unless you uses pci-e pass-through or SR-IOV. Why do you care about the existence of pci bus? On Thu, May 24, 2018 at 9:33 AM, Yuri Pankov wrote: > Hi, > > Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606 snapshot as a VM on > Hyper-V, `pciconf -l` (and `lspci`, expected) doesn't return any > information. > > Hyper-V Version: 10.0.14393 [SP2] (that's Windows 2016 with Hyper-V role). > > dmesg.boot is attached in case it's useful. > > _______________________________________________ > 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" > -- Tomorrow Will Never Die From owner-freebsd-current@freebsd.org Thu May 24 02:46: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 53AE8EF6623 for ; Thu, 24 May 2018 02:46:51 +0000 (UTC) (envelope-from ml@vishwin.info) 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 C7D966D95B for ; Thu, 24 May 2018 02:46:50 +0000 (UTC) (envelope-from ml@vishwin.info) Received: by mailman.ysv.freebsd.org (Postfix) id 8B66AEF6620; Thu, 24 May 2018 02:46: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 68FA8EF661E for ; Thu, 24 May 2018 02:46:50 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (varun.vishwin.info [46.101.93.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "varun.vishwin.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3A8B6D959 for ; Thu, 24 May 2018 02:46:49 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (fd35:9eae:7575::2 [IPv6:fd35:9eae:7575::2]) by varun.vishwin.info (OpenSMTPD) with ESMTP id 67adeef8 for ; Wed, 23 May 2018 22:40:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=vishwin.info; h=subject :references:to:from:message-id:date:mime-version:in-reply-to :content-type; s=fuccboi12; bh=lzW2pMMm9mlOkSQW31XKpHZ990KhNMacb nlAm7qDJwg=; b=ZhZvRFO7+GCc9Zpa7UeFlJg86h82/Lb0oiutdhBrJC+e3iv8T qEPd9alIAMUL1gVvAeanR/qxRxl6wmKuDKnO044ktGmkI/P7q1DsGI+le8LA5h+p fwqALdEDqrWD2Gi6037WCwAV2Sl4Vx/PeoQAX3SExrAbwN7EOoW2DRb5SDhIAptr KVK98aAZjXiPFXfGlvfCx23Iy598eb8ejmFVw+c2Vjd5FdbH/b/ZdERX7G5Nm3wu BrqlFxbYgUFqn1epghzIf/i2ney5JWIAz6krmZTOpXTKWGXkp46jVpqqK/BXFd16 gK0Q7BTlr5l24jBZiejxLCidhYO6B6ftmogpA== Received: from [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d] (2001:470:8:6ca:cad7:19ff:fec0:a06d [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d]) by varun.vishwin.info (OpenSMTPD) with ESMTPSA id ad8f1d8c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Wed, 23 May 2018 22:40:04 -0400 (EDT) Subject: Re: kernel -current build failures References: To: current@freebsd.org From: Charlie Li Openpgp: preference=signencrypt Autocrypt: addr=ml@vishwin.info; keydata= xsFNBFe4p7sBEADHSqa7WkWYRhRiAYsECn4Ek29AkNS7SF4YAbZTzg+3xkPL5cM5zbNCR4U4 o99wC0Y5wQn9y9X9wM16k1AxBkeQ7Dgh+AjxYGnwDjyrVdx9fcId8dQvLV/xw4V2b5CtU0Et M9IE3MDOkgLtWJamTWIL/MfrNgWk5nRZDBhDcygkTO87t0Pi4WC/QQ3TrrDya6FbBPI7I5Y2 0arX2LAeXqJ6pF7uPfjqogKy3UL+t++9nTG6FNR2oftlts1AB+kGHXJf1GiewXLpPEJTGlXx P+XGhjALqJkFw6azELYKjZcd9zGEOWiKJKp2c2RUDdEJHy+cm6cJ8g7dabVA4ZXs5O7NzeMr on7xFbBx/l/0qHux+d7gS4Z+GJ9WGvzvuj4L8MLgA0eaNzn564RJ5FCtPpaulMhcSc78LhZs NCN3rq8VxsxNrIFTlvnLdLsTNITZOKXnyalE9WlM3cK6UlQaagShhO3FliI2hIOW7j4QWJZC Thynnnj5wIAOgKv1WKFwnKJsMfsohIME6uqmt5AcH5okXGZCcBJx30+enqsoEYOvg0pi5oY7 6F/bQdvHzY2prjeujo0oJhVSeRpv5tjEUBDjX525SPNqvr4uddHiavrFBkesOh7nnOjsEMZ1 i5Q6iZrQpteoafFZTld7tfLw8gMwyiSleKN+x7tJG1H3d1Bd7QARAQABzSFDaGFybGllIExp IDx2aXNod2luQHZpc2h3aW4uaW5mbz7CwYAEEwEIACoCGwMFCQPCZwAFCwkIBwIGFQgJCgsC BBYCAwECHgECF4AFAlfq/VYCGQEACgkQtQ4IJhNZSS0i+g//fRJwTJHY/sjK0T0Mh0PzwSnm OSYEcscxTuMR9BQaXPMFjEPpArtms0Wd9S29BgzLB+F7To9MCFGiDB6yvF5fba4Zz+oJ9hB8 lJ3lvY1Hr/hxdxK6Etzl/oXM8LN08Hi9XrHDWm1yuLLJvpaynoOGotZYDLoh0hPomPp3j1w/ BcVK6cRCUArAhXwH0HWTKYlZcRsL/paTXvVgi0TKqF29u2ADhjukQh7qAwcZebC+FfxV9On4 1gCkco144JJX77Ak7g/IWeJy7MJCzbwH41PNyn/X5lwv5N+4cKcGlSOi1ndJuySY2G2Pr1Wu rRyUQ/BF70/laaQOsd5Eg4QimzhOJ3G7QqtYOCZdFBvRs4i3ht0tyKgh4NIr9Zl6FaX/AsDJ d1PBdaWdUaY3NHEDFHtntL9xWxdc+UM21fMqAh+TK4zY+FhaudZO1MdBjrMd8ukjpveaoWZJ NgFageX28AWqxFpOhcPDchkUnydqmEEnl87zuZ8OS+HilDH4JzVGAnYrCG4+/h0b9V4QGevS Jp5lnmSXv2/YFkTDHSXmyBTXrVCjfZM3zH9I+3unYxwio0iAhj8sE4gD2Mx53fmBzoS/3ckf dbG0rZ2lecEFiWez4wn7YTHWLl2ujmeBbhjoyY5JPjvOCkn2Gbcy7tJZqTW7ajkWzZQcexyW 7lLoCkCXz9zOwU0EV7inuwEQAOaRmAfkM3cDXbGYr+8QZ08T037xFyTx3pPtfg74BaL1DF5o 4nr7XG410rHT3biOUxH3Gk7NILQibA746zm/TKjj8m/S4xc+aGA8l/Wx34C/6UO+zUNg0Cpz Vynmwtvj6oh/guoPuO2mELf0tQTXEP8vo4nRVcuYlDm0VKHS5OFadlZuYc8vlCx3jOC0vXyC DUKSZu5HdcP3a75OUrHFa7fS6A6n4J8/OKyiXXO9+tUielafHv0zF4Enl7pJgRXLPoJm5FZk RQWNdltVXtfPeOvhM8Plwk5XXjkNShGhsCzTF56f2DUlHCXJQAVDHAbYuscifUY+2HrA41SY SMM1nS5YpQXRWOMuxeh1xwia1GNvgaJdaucCKZ4Fff1F6YuTPKGCOEOifRPoLfO6Te93o2Fs NvNWutiCO0jJj1rlLLdV44chMbiOIsdMtsMpj5/T/Jrm7aD2NvWXJy5+aDyqjmE529oVBYha ouX9XEeWzUL5MxdqgT2LlmBv/y6XbXhXTOUHBBQyCBbqDqiQOWPtOkusiCajTyY0lsM3gR24 +igkJEMND+kJmMdn7G8pSKy7LgRlW4haGmz+80xfMf593APbzlnGB8gD0aH7/ejYCMkGaYz+ ZwFopkl0I4QQxSc3tvVljDhWNyGZxz2Dw4DNALHiG6xmESX00itf2zMPABMrABEBAAHCwWUE GAEIAA8FAle4p7sCGwwFCQPCZwAACgkQtQ4IJhNZSS3BIxAAsXD7PgkrQWu1DunaiPlL0MbR gv2evjY+2cLdpMt8Je3+e25r8JTbPKIV1QY3q0ju0yXgWLW0dM1hWSVpsQURLNyFYnivXt4q rLuDv4T/xTUo/xuV0rUOXp+oTDVKQ7KhpvKtaZFkP0a1z0pVFJbk7AI5UkQ4+lcuyTqzawxd vxn41s/FNKIxXTtj0PAgthzE0ZivAIj4USRaULC20ZvOYFW6rc10UPmrkLsrfXepakGBc0KJ EajF8LiOUqPE4c4BH2CoeEFu+e5OJAAl4kjj/CuNvtlko1Qjd31HPpMaha4l/WAd4kKPmMeW WuRxFkOwkkJFKW2ycH837Njl8Jn6dFSpgZ5/DPBvRdBXjAgDhySr2h9Zn5b6svtnh1ByKJKv ovzp+64IRqfotlLK3J9X1eKHlq10SyprH6IlxsGyXi987ZeV6/04UUAdmPXio/Enxbtna7D2 Cvo+aXTGM9Yu/YwxfmkWRJvEUUzqCOq63Z0Aa5ckOi+8FLUj3ZryS3ctmph/x/flN+ab4R22 pDL8LW1kwMH4Y4krv7l4GBgJPzkBGmonMclGf19i9zwC3TV8oSQ26cyi5d6QmuE3KN9NuLrD CJo3QQ3fpqQrnJbtd0M6fjuKWN0o7UTVEkcOXWWRF85d33VXG8XTDXEJmAJsELG7txDPNZ9o FqGGsWKHymE= Message-ID: <5440d5c9-e7a9-5ec7-7e9a-9d426afa5d6f@vishwin.info> Date: Wed, 23 May 2018 22:39:56 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oaSPDx2gEeS4iXiP3xE9gaEkLcLe7H2Fq" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 02:46:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oaSPDx2gEeS4iXiP3xE9gaEkLcLe7H2Fq Content-Type: multipart/mixed; boundary="gMHAWkordSscGJT2TmXifWS6M8t6xDcuJ"; protected-headers="v1" From: Charlie Li To: current@freebsd.org Message-ID: <5440d5c9-e7a9-5ec7-7e9a-9d426afa5d6f@vishwin.info> Subject: Re: kernel -current build failures References: In-Reply-To: --gMHAWkordSscGJT2TmXifWS6M8t6xDcuJ Content-Type: text/plain; charset=utf-8 Content-Language: en-GB-large Content-Transfer-Encoding: quoted-printable On 23/05/2018 19:21, Michael Butler wrote: > On a device with bluetooth (as in GENERIC modules) .. >=20 > --- ng_ether.o --- > /usr/src/sys/netgraph/ng_ether.c:871:2: error: no member named > 'tqh_first' in 'struct ifnethead'; did you mean 'stqh_first'? > TAILQ_FOREACH(ifp, &V_ifnet, if_link) { > ^ > /usr/src/sys/sys/queue.h:724:15: note: expanded from macro 'TAILQ_FOREA= CH' > for ((var) =3D TAILQ_FIRST((head)); = \ > ^ > /usr/src/sys/sys/queue.h:721:36: note: expanded from macro 'TAILQ_FIRST= ' > #define TAILQ_FIRST(head) ((head)->tqh_first) > ^ >=20 Looks like this is fixed in r334123. --=20 Charlie Li Can't think of a witty .sigline today=E2=80=A6 (This email address is for mailing list use only; replace local-part with vishwin for off-list communication) --gMHAWkordSscGJT2TmXifWS6M8t6xDcuJ-- --oaSPDx2gEeS4iXiP3xE9gaEkLcLe7H2Fq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE/RdyC3Asy49czZEGtQ4IJhNZSS0FAlsGJgIACgkQtQ4IJhNZ SS0XyhAAxwYuiv7LnvETcwRAqpY97UoD3XA/3qm0oqTr9dW7GjnG2Bxtq9nPsBy/ WT2kOb3a+3YWyTQdgQXT/8tmkWXxkeQb2flsHyQRQRlHCN3bUELl47zMzQlTZYF/ IJEONKJ6w9SKbxx/xtx8vmNVDUpSomtyurZv4PyRCPow7Dd/tPpsdSGmzVe+J+80 PnfgDHMLdqaOr5MUzro0o6anJ8AdNoRB4BFPTTYvc+OHH/Yn6OlSyFDTKLHdjXjc Cj5CLqshfSR2PMKpkRDGvsiGu6ThlNVj1i184Q7UcesCu9ExNdKD25k7mG/4NEav vQ/tqVFKHUZzWlwsDIZBzhDcAFhJdX5bXdKiQm4jIRNGPSSSY35Cnu0/0gB0GlIF eJJ0ROexbX/OJaVCbPzBaL+wOcwyrtqQn61gHpqChtzRw14M/pNACwDOvWrdH7nn P8zlVNAWnzS2SJcMWl4m4d+uZII64J8VhLosp1eq6p6JyXlrGDf/ngSzufgCcpHr zZtxFBaIlDDYAdL3PiFiLFMA9QqaAMqBD/Oq6rrzhMoldWE0B9QqRdfHvQmuWG4D iep0Zdy4SGBKwK8ZVA/XMym8NR90dxLQgsufu9VcMkz9BOX+pKGDuYaOl7idJr8d BwNgsltLqV0usK9XnQ82y5xu+DachsqjI6oClpGyXTpWvmHiGfw= =TNCH -----END PGP SIGNATURE----- --oaSPDx2gEeS4iXiP3xE9gaEkLcLe7H2Fq-- From owner-freebsd-current@freebsd.org Thu May 24 06:31: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 6D0ECF54B21 for ; Thu, 24 May 2018 06:31:19 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DE3AB78573; Thu, 24 May 2018 06:31:18 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?iso-8859-2?Q?M=26S_-_Krasznai_Andr=E1s?= To: Philip Homburg , "Rodney W. Grimes" CC: "K. Macy" , "A. Wilcox" , FreeBSD Current Subject: RE: [RFC] Deprecation and removal of the drm2 driver Thread-Topic: [RFC] Deprecation and removal of the drm2 driver Thread-Index: AQHT8nvBZj/+QvBhCUWGzQbbkIm19aQ9EtVg Date: Thu, 24 May 2018 06:16:06 +0000 Message-ID: <54561d2004f34b3eb1e394d940aaf1ee@MSEXCH13.mands.hu> References: Your message of "Tue, 22 May 2018 15:12:39 -0700 (PDT) ." <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> In-Reply-To: Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.6.59] Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 06:31:19 -0000 hi I am using a Lenovo T510 laptop with FreeBSD-CURRENT. It contains Intel I5 processor and integrated Intel graphics adapter. I tried to set it to drm-stable-kmod as well as to drm-next-kmod, none was = working, I got a fatal trap, kernel panic during boot. Compiling the packages on my system did not help. The graphics adapter can = be old for drm-xxxx-kmod packages. Drm2 from the base works correctly on my laptop. rgds Andras Krasznai -----Eredeti =FCzenet----- Felad=F3: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@f= reebsd.org] Meghatalmaz=F3 Philip Homburg K=FCldve: 2018. m=E1jus 23. 11:49 C=EDmzett: Rodney W. Grimes M=E1solatot kap: K. Macy; A. Wilcox; FreeBSD Current T=E1rgy: Re: [RFC] Deprecation and removal of the drm2 driver=20 >Also as the Moore's law curve flattens expect the life of these >older, but not so old, machines to live quiet some time. I >believe we are talking sandy bridge and earlier? If that is >corret Sandy bridge is still a very viable system. I noticed this lack of love for older systems recently.=20 I wanted to use an older Dell server to test the 11.2 BETAs and RCs. Turns out, you can't install FreeBSD using a USB stick image because the BIOS only support MBR. No idea why MBR support was dropped for the USB imag= es. In the end I had to find a CD burner, and after a couple of tries managed t= o install from CD. After that, my ansible playbooks started failing because /boot/loader.conf= =20 is absent if you boot from zfs in combination with MBR. Pity. This older server hardware is great for trying out new releases, play= =20 with zfs, etc. _______________________________________________ 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 May 24 06:35: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 49CD5F59204 for ; Thu, 24 May 2018 06:35:55 +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 DFA1578A06; Thu, 24 May 2018 06:35:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 8046E2600D5; Thu, 24 May 2018 08:35:52 +0200 (CEST) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: =?UTF-8?Q?M&S_-_Krasznai_Andr=c3=a1s?= , Philip Homburg , "Rodney W. Grimes" Cc: "K. Macy" , "A. Wilcox" , FreeBSD Current References: <201805222212.w4MMCdA9031937@pdx.rh.CN85.dnsmgr.net> <54561d2004f34b3eb1e394d940aaf1ee@MSEXCH13.mands.hu> From: Hans Petter Selasky Message-ID: Date: Thu, 24 May 2018 08:35:41 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <54561d2004f34b3eb1e394d940aaf1ee@MSEXCH13.mands.hu> Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 06:35:55 -0000 On 05/24/18 08:16, M&S - Krasznai András wrote: > I tried to set it to drm-stable-kmod as well as to drm-next-kmod, none was working, I got a fatal trap, kernel panic during boot. Did you build from source? Can you show the panic? drm-next-kmod should be loaded by /etc/rc.conf like this, can you try again? kld_list="/boot/modules/i915kms.ko" --HPS From owner-freebsd-current@freebsd.org Thu May 24 01: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 AE90EEF18DA for ; Thu, 24 May 2018 01:34:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-21.consmr.mail.gq1.yahoo.com (sonic317-21.consmr.mail.gq1.yahoo.com [98.137.66.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 338A16A3A2 for ; Thu, 24 May 2018 01:34:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 2dzWItwVM1lBVm0TqnOsZvQLPmKe9DiQJy.VVqsYCfBMMeNY63JbDYz0Bm0sBzF y2xvXUboMVatrRQ9pLaErANMAls5R1531jakRVFQc593yQsj.J1wWhnpq4MFsi9gT8ZAAp1J8SWO elvsS1kBySiivAsOslXUbg._95Lil08I_RV7cjImrr2xV5yeQ107Kr3MG9XGpZ2FFtKwGEy1HerI AevYMNuQqwPe.LldzXOx1FdgooL3bHdvQqwsvCh2QCQnXH1WJB2QBM1lGccW9grdQPaYF6A1ZVaM l9iooeg_3F5hsBjZV6pndVA.0TzoAB9Z_wtrUgm40Aj1X5uvciusNh5FrDwfDJYTAnKDBQLVozNw 5NW5OxWp3OiSVIhpJhIP_A2dx5q9JRPzEHCxC3sKU79SKGXRX1RuWsiMprckxwjW9gl3TbX7HPqn 6g34XG.ZRL3RWjyxZpIPxAC86uuDJUornjswEeqi__50WRfFIv.NavzSf_IDz9TIVHph6LsU6zrW i20bAWZm2gZSDp3IaO.ZC1rqMJCO6cTrhdzjV1ZNpmF0io9pnLBcQQnvft73Y.lTIvmBTTTEukV6 dgAlAzwo45gLFLy4Zh.etVyyWyiU1wjSWD9cNKo0KqRnYHEhx90V.RDyyw5wo5q0.unjqyns6o0Q NvuJDIDy8VgOMh801Jf2lVzvfqByozg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Thu, 24 May 2018 01:34:31 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp414.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4c4add10b19158ef99393bee0f570f5e; Thu, 24 May 2018 01:34:28 +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.3 \(3445.6.18\)) Subject: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org Message-Id: Date: Wed, 23 May 2018 18:34:27 -0700 To: Eitan Adler , FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-Mailman-Approved-At: Thu, 24 May 2018 10:39:44 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 01:34:33 -0000 [This submittal is in part an experiment with how Eitan's MUA classifies the Email using an alternate yahoo.com address. Eitan: the subject and this note are all unique to this message.] I've reported to Eitan that the gcc/g++ 4.2.1 architectures are failing for devd build failures. Examples include: --- all_subdir_sbin --- cc1plus: warnings being treated as errors = /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string= .h: In member function 'std::basic_string<_CharT, _Traits, = _Alloc>::_Rep* std::basic_string<_CharT, _Traits, _Alloc>::_M_rep() = const [with _CharT =3D char, _Traits =3D std::char_traits, _Alloc = =3D std::allocator]': = /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string= .h:493: instantiated from 'std::basic_string<_CharT, _Traits, = _Alloc>::~basic_string() [with _CharT =3D char, _Traits =3D = std::char_traits, _Alloc =3D std::allocator]' /usr/src/sbin/devd/devd.hh:149: instantiated from here = /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bits/basic_string= .h:288: warning: cast from 'char*' to 'std::basic_string, std::allocator >::_Rep*' increases = required alignment of target type mips64 and mips and sparc64 agree, for example. powerpc and powerpc64 report: --- all_subdir_sbin --- cc1plus: warnings being treated as errors /usr/src/sbin/devd/devd.hh: In function 'void __tcf_0(void*)': /usr/src/sbin/devd/devd.hh:150: warning: inlining failed in call to = 'virtual config::~config()': --param max-inline-insns-single limit = reached /usr/src/sbin/devd/devd.cc:175: warning: called from here but I expect the two sets of types of error message are related somehow and the "fix" fixes both types. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Thu May 24 12:46: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 73871EEF777 for ; Thu, 24 May 2018 12:46:41 +0000 (UTC) (envelope-from timur@bat.ru) Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0995969A1B for ; Thu, 24 May 2018 12:46:40 +0000 (UTC) (envelope-from timur@bat.ru) Received: by mail-ot0-x232.google.com with SMTP id l13-v6so1739958otk.9 for ; Thu, 24 May 2018 05:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bat-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=gYlrEqtsOckL7n4WHpstMMAXnzcG5j/DHFSBNTsjNsw=; b=MRwu19HaPq0d51FfnIoNT3EiGUmeuHD40sV6kUZCdXZlXy8nhD4u9ColEMigkuu+3B 8DqSpusx9cFD617OMDplnx37N77tZ/0cVM+SaqLpwuAHnYP8rRrRDiK8ONaz7kercq0Z pQnxj1p/V4Ra/1fso7Llg+mV28mAuYivzwhfXZ+bS3g6ar+VgIg839Vwna7vcQW0Chtk 3kgkr9vTqS91dWQBV73z2rVTiaHLqqfCYufdTAShDN/j3S/ZltsFakDWWSvsat9bONQL PTSeEc2Jcjoay60NYwn9hkExzv06Y/dX9EH9/zd0vX15E6WGPaY0zI50MLi07ByYoWD6 N2/A== 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=gYlrEqtsOckL7n4WHpstMMAXnzcG5j/DHFSBNTsjNsw=; b=Ag2GZ7qePvWS7Ry74KM8Tkrf9snCbTzqEsiyOOEf+49AHPHkpUD4xtdYAuVttRIcoL aAs+XX3y68pGcCnuzORS9u8fBn6MrqUgVtbPxDgHD9oddvmmqFkQ+3nkFLQDOHEL09DB GxOkgf1PZ79xLXqNWcDGXQ/gtAg0hUBMzXlyw9MQ6I5ak98Frbbu17CshAYe0lFRGt03 ocWW/pC/Y9f9hp5v/Gmoa/OaxhkixkUQFnGl7BFEkXCimHQCz+IsSp0b+kALE7Hnoi73 EiG6fUzBPZ/CZxw9edkytrH9MrLBfdghkCPaAjgLmRh97GnOkw46Hv2OzHe8AnTKgp+Z hFPw== X-Gm-Message-State: ALKqPwcJ0WlpmePK73CGnp3wsbU6TJbTdf0cSxfa3P7aYB3fEHwzO4bu E2p5iG9yzr9CdECOUwd1f+zfm9SrqoJz85Q8g2T9ZA== X-Google-Smtp-Source: ADUXVKLVeNoUrKvVh+CLVjBtOBFeIOerzypSGMACf/JelOd+G29KYrrpHwWku+0wJEuU7DaD3l0X6gOjRjxNduFKESw= X-Received: by 2002:a9d:49a8:: with SMTP id g40-v6mr207906otf.223.1527166000124; Thu, 24 May 2018 05:46:40 -0700 (PDT) MIME-Version: 1.0 Sender: timur@bat.ru Received: by 2002:a4a:1c2:0:0:0:0:0 with HTTP; Thu, 24 May 2018 05:46:09 -0700 (PDT) In-Reply-To: References: From: "Timur I. Bakeyev" Date: Thu, 24 May 2018 14:46:09 +0200 X-Google-Sender-Auth: VmKgHHZf-FDl_68aVCYc8enEd88 Message-ID: Subject: Re: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org To: Mark Millard Cc: Eitan Adler , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 12:46:41 -0000 On 24 May 2018 at 03:34, Mark Millard wrote: > [This submittal is in part an experiment with how Eitan's > MUA classifies the Email using an alternate yahoo.com > address. Eitan: the subject and this note are all unique > to this message.] > > Gmail still considers all your mails as spam :( > This message has a from address in yahoo.com but has failed yahoo.com's required tests for authentication. WBR, Timur Bakeyev From owner-freebsd-current@freebsd.org Thu May 24 13:02: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 DC6C0EF04BD for ; Thu, 24 May 2018 13:02:37 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B76D6A9F4 for ; Thu, 24 May 2018 13:02:37 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-wm0-f45.google.com with SMTP id w194-v6so4870704wmf.2 for ; Thu, 24 May 2018 06:02:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=PRGINP/M7jrqgRXVFupP4T0fOTmcP4c018RB4ZoKB8E=; b=XB+kRGABUikqYuiN94rL5Nj1cwbS8aL4W72Wy45KjA305HXfl6dHknrDuOu4ylZ9uJ 7fhjGnhIk+SSrOFt2RjswYYKpzOE10LXWl0dfGKIh+9aoVr2ztFAD0BQfh+MhaWNhXob 9X2XXEtyicX9ag2KMybzRVc2VmelWbs7BXO8+zhN+Q2JvO+k+GvpaYw/0cVjkofZVZKz YhCTSvH1zwCtsjaoCAnHm0E3www5Mb27N7CiasZFLIj839Z4bTynZKVDSNnpFUWpDoBk t6D13iicP8TMZ7fz/Wg+egjB2dlp1emcDRoUn5hfwAUUOqp0z86f1t54UqOfWeQ24VLF rvvA== X-Gm-Message-State: ALKqPwcezhMqdgyVWzDy2HUXEU/RuIJNboHViygnzouxnGVtlbbXRONo nej5K21tl/QV7q0O/jd/fXDxeMBZ X-Google-Smtp-Source: AB8JxZp4zwIabgNmK9UNBfZuFTvO4JyMJ87AdcTrQVl9aftIteuiy6QpO0hO2k7Cyd/oJFTgCnRhWA== X-Received: by 2002:a2e:3503:: with SMTP id z3-v6mr4546289ljz.95.1527166484481; Thu, 24 May 2018 05:54:44 -0700 (PDT) Received: from oxy (89-76-8-18.dynamic.chello.pl. [89.76.8.18]) by smtp.gmail.com with ESMTPSA id f64-v6sm4994273lfg.63.2018.05.24.05.54.43 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 24 May 2018 05:54:44 -0700 (PDT) Date: Thu, 24 May 2018 14:55:48 +0200 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 Message-ID: <20180524145548.09f061ad@oxy> In-Reply-To: <99b881e0-9915-e859-070c-df40673400f1@nomadlogic.org> References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> <1366699076.177914.1527061285836@mail.yahoo.com> <99b881e0-9915-e859-070c-df40673400f1@nomadlogic.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) 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.26 Precedence: 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, 24 May 2018 13:02:38 -0000 On Wed, 23 May 2018 09:46:13 -0700 Pete Wright wrote: >On 05/23/2018 00:41, David Pan wrote: >> how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on >> FreeBSD 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not >> drive the Intel Wireless Card. >> please help me fix that, > >I have this working on my end under both 12-current and 11-stable. >here's my configuration: > >output from "pciconf -lv" >iwm0@pci0:3:0:0:=C2=A0=C2=A0=C2=A0 class=3D0x028000 card=3D0x10108086 chip= =3D0x24fd8086 >rev=3D0x78 hdr=3D0x00 > =C2=A0=C2=A0=C2=A0 vendor=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Intel Corporation' > =C2=A0=C2=A0=C2=A0 device=C2=A0=C2=A0=C2=A0=C2=A0 =3D 'Wireless 8265 / 82= 75' > =C2=A0=C2=A0=C2=A0 class=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D network > > >to bring up the card i have added this entry to /etc/rc.conf: > >kld_list=3D"if_iwm" > >then configuring the interface is the same as any other wifi as per the >handbook, the device will be available as "iwm0". Shouldn't you load some firmware as well? That's what the iwm(4) manual and WiFi/FAQ wiki page[1] say. [1]: https://wiki.freebsd.org/WiFi/FAQ#I.27ve_got_some_problems_with_the_iw= m.284.29_driver From owner-freebsd-current@freebsd.org Thu May 24 13:11: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 7BA1EEF0ABB for ; Thu, 24 May 2018 13:11:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FFEB6B04A for ; Thu, 24 May 2018 13:11:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id e20-v6so2271654itc.1 for ; Thu, 24 May 2018 06:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rCyES4EWUPjXIFGMI5w/KXtw3EBvxLQIt3J5EzYY9MY=; b=pZLu6G1u+u+AJ/cpsT1k8NLNJ/BzF+ix7WrxRuKV55alWhRVCaRxt2qmexAmzdgKTE mbZbxNbAPyzOOmpRb509Nl+RxaTSXOf53l9l9ZKGWxuRz7tKQE6ArlZOrA9Ei5l5+L7Q WjJNSeRmLhKk4GMYpzKbx7uL0W5fpW/7oSz+wCnMom5CYarURWtr0qXQi4xQkGKZRIpN O1hpqNdHUM/ttrg9ienTf4EO9K0skQELubYtPTOR9IVTFEYp5n92ITRyremKIHEcU3JE QkjLbIi0s3UoUMiOS4xE/Q6c4HAjG40vRADz4zVLABQwEVKQpBZqjkC8gcNugmk9QWEJ Y8jA== 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=rCyES4EWUPjXIFGMI5w/KXtw3EBvxLQIt3J5EzYY9MY=; b=iEK/9epD6H6xHhDOlPrCVyfOp131whBIPd/mtsBJ/Xh/HG5QC1AyHCBvF3PWuyglmh R69xyB5wB9uXc8HUFU9FDWv3Zb4lPGl3uJCj6/kaoQUsAU9sPsRONxLlPSMgyPNS+ICW CbXWpG6R0Ldfcq9JsWLVY7F7jG96IVI6HBiP0LXbgZMcpU9eNy5tOdjJTpcAerFd3H46 3m3Cm9qxnBRa8yRb4hnpNGuyMI3CnTVlJWrmUyJoQqu2GuJrzFJ6GQgDItIzoJM6z7fn LNkQjdIU7gwcdCjHryaMV5QHbMyagG478hH4LjMtqfm77yLml3k6Qja5EpUM79QMb143 w4lQ== X-Gm-Message-State: ALKqPweBQKcY5vacLWLKHqstlm4c3JtJQLsPg6fLkDsrkfneB5n6NFGw GpBs+CMotYKYR09WzNbGHtZOZPEycVynWfJlpII= X-Google-Smtp-Source: AB8JxZoMySlFRo911PGjFXob37RTHGkHKiMShufomys1ExzSfP956EcTeXefWnCwaXe4foqsQ9wgaWo2yxeM+GAZwVU= X-Received: by 2002:a24:2fce:: with SMTP id j197-v6mr8641955itj.52.1527167506525; Thu, 24 May 2018 06:11:46 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:82a7:0:0:0:0:0 with HTTP; Thu, 24 May 2018 06:11:25 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Thu, 24 May 2018 09:11:25 -0400 X-Google-Sender-Auth: ZxInHGThB4PmYxtYm2HnGO_RO8Q Message-ID: Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) To: Philip Homburg Cc: Johannes Lundberg , FreeBSD Current , Andreas Nilsson Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 13:11:47 -0000 On 23 May 2018 at 17:51, Philip Homburg wrote: > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > BIOS version 2.7.0. With both images, the USB stick is not recognized. Can you download the image from https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and write it to a USB stick and try on this system? This is a MBR-partitioned dual-mode test image. It's not an installer - it should just boot to a login prompt - but can be used to test this scheme. From owner-freebsd-current@freebsd.org Thu May 24 15:21: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 9FC69EF4902 for ; Thu, 24 May 2018 15:21:56 +0000 (UTC) (envelope-from imb@protected-networks.net) 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 B200571F03 for ; Thu, 24 May 2018 15:21:54 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 436E0EF48F1; Thu, 24 May 2018 15:21:54 +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 30835EF48F0 for ; Thu, 24 May 2018 15:21:54 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CC3771EB9 for ; Thu, 24 May 2018 15:21:52 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1527175311; bh=FThiZ1Q6 /z2MSIYnB2Z6guTvpudppkxGkxSa4HqnS5g=; b=BLPxJWIV2MJqxSMd/wewXtln XPpyzPYqNfxgzINCMF+tDo04jaZplvP3BM40Z9ztd7vMuYafhrEF7mZQND6Xu6bu 81h+SoTv4VCcm16sTr8cvBYm/yssGjkY/iXXZxkvPvBQ3GslnGoFCvJzIQ7jYaaT vOv1mjjh699n5cPWRDA= Received: from toshi.auburn.protected-networks.net (unknown [IPv6:2001:470:1f07:4e1::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id CE260BB6B; Thu, 24 May 2018 11:21:50 -0400 (EDT) Subject: Re: kernel -current build failures To: Charlie Li , current@freebsd.org References: <5440d5c9-e7a9-5ec7-7e9a-9d426afa5d6f@vishwin.info> From: Michael Butler Openpgp: preference=signencrypt Message-ID: <713be1b9-3d14-12e3-269c-8013bb7a094a@protected-networks.net> Date: Thu, 24 May 2018 11:21:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <5440d5c9-e7a9-5ec7-7e9a-9d426afa5d6f@vishwin.info> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 15:21:56 -0000 On 05/23/18 22:39, Charlie Li wrote: > On 23/05/2018 19:21, Michael Butler wrote: >> On a device with bluetooth (as in GENERIC modules) .. >> >> --- ng_ether.o --- >> /usr/src/sys/netgraph/ng_ether.c:871:2: error: no member named >> 'tqh_first' in 'struct ifnethead'; did you mean 'stqh_first'? >> TAILQ_FOREACH(ifp, &V_ifnet, if_link) { >> ^ >> /usr/src/sys/sys/queue.h:724:15: note: expanded from macro 'TAILQ_FOREACH' >> for ((var) = TAILQ_FIRST((head)); \ >> ^ >> /usr/src/sys/sys/queue.h:721:36: note: expanded from macro 'TAILQ_FIRST' >> #define TAILQ_FIRST(head) ((head)->tqh_first) >> ^ >> > Looks like this is fixed in r334123. Yes but this one isn't .. On a system without IPSEC .. --- kernel --- linking kernel ld: error: undefined symbol: vnet_entry_ipsec4stat >>> referenced by key.c >>> key.o:(key_allocsp) ld: error: undefined symbol: vnet_entry_ipsec4stat >>> referenced by key.c >>> key.o:(key_allocsp) *** [kernel] Error code 1 Michael From owner-freebsd-current@freebsd.org Thu May 24 15:22: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 B60DBEF4967 for ; Thu, 24 May 2018 15:22:16 +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 0D7C7720F7; Thu, 24 May 2018 15:22:15 +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 w4OFMEVI041052; Thu, 24 May 2018 08:22:14 -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 w4OFMCeK041051; Thu, 24 May 2018 08:22:12 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805241522.w4OFMCeK041051@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: <20180523155255.GF24664@FreeBSD.org> To: Glen Barber Date: Thu, 24 May 2018 08:22:12 -0700 (PDT) CC: Philip Homburg , "K. Macy" , "A. Wilcox" , 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.26 Precedence: 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, 24 May 2018 15:22:16 -0000 > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > >Also as the Moore's law curve flattens expect the life of these > > >older, but not so old, machines to live quiet some time. I > > >believe we are talking sandy bridge and earlier? If that is > > >corret Sandy bridge is still a very viable system. > > > > I noticed this lack of love for older systems recently. > > > > I wanted to use an older Dell server to test the 11.2 BETAs and RCs. > > > > Turns out, you can't install FreeBSD using a USB stick image because the > > BIOS only support MBR. No idea why MBR support was dropped for the USB images. > > > > In the end I had to find a CD burner, and after a couple of tries managed to > > install from CD. > > > > After that, my ansible playbooks started failing because /boot/loader.conf > > is absent if you boot from zfs in combination with MBR. > > > > Pity. This older server hardware is great for trying out new releases, play > > with zfs, etc. > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now > built as hybrid images, supporting both MBR and GPT, as well as being > written to a flash drive (like memstick.img) as well as a CD. To clarify a minor point here, are the amd64 disc1.iso images or both the amd64 and i386 disk1.iso images being built as "hybrid"? As this is what I see on my system: root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 sectors FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data '11_2_BETA2_I386_CD' (bootable) > MBR support was initially removed from the memstick installer, as it is > not compatible with some UEFI implementations. (Or, at least that is my > understanding, based on my limited intimate knowledge of UEFI.) > > Glen > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu May 24 16:02: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 DD2F6EF66FE for ; Thu, 24 May 2018 16:02:36 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.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 CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E7F174F8C; Thu, 24 May 2018 16:02:36 +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 34ABDAD03; Thu, 24 May 2018 16:02:36 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Thu, 24 May 2018 16:02:34 +0000 From: Glen Barber To: "Rodney W. Grimes" Cc: Philip Homburg , "K. Macy" , "A. Wilcox" , FreeBSD Current Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180524160234.GD68014@FreeBSD.org> References: <20180523155255.GF24664@FreeBSD.org> <201805241522.w4OFMCeK041051@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Q0rSlbzrZN6k9QnT" Content-Disposition: inline In-Reply-To: <201805241522.w4OFMCeK041051@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 16:02:37 -0000 --Q0rSlbzrZN6k9QnT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > >Also as the Moore's law curve flattens expect the life of these > > > >older, but not so old, machines to live quiet some time. I > > > >believe we are talking sandy bridge and earlier? If that is > > > >corret Sandy bridge is still a very viable system. > > >=20 > > > I noticed this lack of love for older systems recently.=20 > > >=20 > > > I wanted to use an older Dell server to test the 11.2 BETAs and RCs. > > >=20 > > > Turns out, you can't install FreeBSD using a USB stick image because = the > > > BIOS only support MBR. No idea why MBR support was dropped for the US= B images. > > >=20 > > > In the end I had to find a CD burner, and after a couple of tries man= aged to > > > install from CD. > > >=20 > > > After that, my ansible playbooks started failing because /boot/loader= =2Econf=20 > > > is absent if you boot from zfs in combination with MBR. > > >=20 > > > Pity. This older server hardware is great for trying out new releases= , play=20 > > > with zfs, etc. > >=20 > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now > > built as hybrid images, supporting both MBR and GPT, as well as being > > written to a flash drive (like memstick.img) as well as a CD. >=20 > To clarify a minor point here, are the amd64 disc1.iso images or > both the amd64 and i386 disk1.iso images being built as "hybrid"? >=20 Only amd64. i386 does not have UEFI-/GPT-related boot issues. > As this is what I see on my system: > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition 1 : ID= =3D0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 147269= 5 sectors > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data '11_2= _BETA2_I386_CD' (bootable) >=20 > > MBR support was initially removed from the memstick installer, as it is > > not compatible with some UEFI implementations. (Or, at least that is my > > understanding, based on my limited intimate knowledge of UEFI.) > >=20 Glen --Q0rSlbzrZN6k9QnT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlsG4hUACgkQAxRYpUeP 4pPLbxAAjnNxQLimvBDcjp3zbAR6oKI4q4ZsQs4CBL7F4zE4FmcYojan0cy4vIRS rcimj8Rgq3iOA9up8jGUbd9bC2MUs+gkJ7Cnl5hIS8MZK4CkxtreHPng6V10Nnih PKjTjulnRO3/AjvY+Rog4Xqwskkrz5gvnEL9PDKOMnok7QfOxY657Gjy/e78YxZJ Bh4KikHh/stYUpfDZ+eaIF3HzJY1pr2s7gY10WZTbUoBPhkGGhOjDJHFDTLuXuqt VO3641qn6lktMgxK0RfKV22coB78EaaA5YXIcFHMsKa3dp3My+qY9YRGNWGjhF/v 2MJ2B8LvaGHcxx9yN89q3s+zX+IE0SU2F2rQTZ7o7OeTDWm8mVot8SOzsqrNudIg NSzLmYNZJvkOZRgrdkEmFtwJD6TAUthxHDb2jRZvn0iDa1cLZc5IecGmHYCTwJHo GWoUqxAZ/UvNiZ48p7p1QEG74S2pC/wSdkS/Gh0n/8vQJtnmE/N3dhGH1KtvAN0z j93ZKVDUB6XIsGDwXZ/UZAFynFW4ATma5mSJP9iz7uFTn0Pt0WqcFY4W33fIu5Ht D+M6h5XVpmoFW6jqNWv571dFtfCAVWQP7etBg+CwsgkK0whSBCJrEGrjAXXXH9GP w+dnP7yVfH4jEQWMbW/l9ZS2Qa0yrXVRygPZx6ivaRn7/25W+tI= =gzDj -----END PGP SIGNATURE----- --Q0rSlbzrZN6k9QnT-- From owner-freebsd-current@freebsd.org Thu May 24 16:10: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 193E2EF6C37 for ; Thu, 24 May 2018 16:10:14 +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 6F78775706; Thu, 24 May 2018 16:10:13 +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 w4OGAAxP041281; Thu, 24 May 2018 09:10:10 -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 w4OGAAGY041280; Thu, 24 May 2018 09:10:10 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: <20180524160234.GD68014@FreeBSD.org> To: Glen Barber Date: Thu, 24 May 2018 09:10:10 -0700 (PDT) CC: Philip Homburg , "K. Macy" , "A. Wilcox" , 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.26 Precedence: 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, 24 May 2018 16:10:14 -0000 -- Start of PGP signed section. > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > >Also as the Moore's law curve flattens expect the life of these > > > > >older, but not so old, machines to live quiet some time. I > > > > >believe we are talking sandy bridge and earlier? If that is > > > > >corret Sandy bridge is still a very viable system. > > > > > > > > I noticed this lack of love for older systems recently. > > > > > > > > I wanted to use an older Dell server to test the 11.2 BETAs and RCs. > > > > > > > > Turns out, you can't install FreeBSD using a USB stick image because the > > > > BIOS only support MBR. No idea why MBR support was dropped for the USB images. > > > > > > > > In the end I had to find a CD burner, and after a couple of tries managed to > > > > install from CD. > > > > > > > > After that, my ansible playbooks started failing because /boot/loader.conf > > > > is absent if you boot from zfs in combination with MBR. > > > > > > > > Pity. This older server hardware is great for trying out new releases, play > > > > with zfs, etc. > > > > > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now > > > built as hybrid images, supporting both MBR and GPT, as well as being > > > written to a flash drive (like memstick.img) as well as a CD. > > > > To clarify a minor point here, are the amd64 disc1.iso images or > > both the amd64 and i386 disk1.iso images being built as "hybrid"? > > > > Only amd64. i386 does not have UEFI-/GPT-related boot issues. Here is a data point: Test system is Dell R710, First attempt is with BIOS in Boot mode: Bios Second attempt is with BIOS in Boot mode: UEFI Attemtped to boot amd64 version: Screen goes white background, text appears (yes, way indented) BTX version is 1.02 Consoles: internal video/keyboard _ That last _ is a blinking cursor, system is hung, does repsond to C-A-del Second attempt: Works properly I am going after Ed Maste's posted build image in the other thread now... > > > As this is what I see on my system: > > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 sectors > > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data '11_2_BETA2_I386_CD' (bootable) > > > > > MBR support was initially removed from the memstick installer, as it is > > > not compatible with some UEFI implementations. (Or, at least that is my > > > understanding, based on my limited intimate knowledge of UEFI.) > > > > > Glen > -- End of PGP section, PGP failed! -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu May 24 16:42: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 B4590EF7C0E for ; Thu, 24 May 2018 16:42:30 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26E2677408; Thu, 24 May 2018 16:42:30 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id l41-v6so4325625wre.7; Thu, 24 May 2018 09:42:30 -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=X0ykyR7Orss/1Cp0e8Gdl2PTA7NMN/SYazF6lVmFaDM=; b=uROy3jRLiW2pcqdgU21M2JiOmhIPBkg1EnPMIflBti4l0yoAMYWJJyn1vjhr8wMtd0 A3ifYMbaNdcTrLXYxYCW46PfE9+mEC20lFYmyhNb/q7QZmCLEDmWSXSFm/Yeere8xDkK Y/yHRmRCHbQnFmq8B52WjVwgFJGbV8tjGJwlHG/U4gFaTRemBicb5b32vEe00nk7PhTG n8qZmr5Qo1EKCQbtKoOvuCmMOfMydqMXgCGn4sTJN/Pf3fxLlUKSB3LE3yBrHtBLiI0D K1chc5ZAzB+vBD4966uzhyOj7cQi2nVndDT2QnNvXwGYqs1zd77lDUdfs/SOZTSIBUGQ zzeg== 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=X0ykyR7Orss/1Cp0e8Gdl2PTA7NMN/SYazF6lVmFaDM=; b=reNktye5xO1/4IoJi/k1OZGzQEVCyzFD2wZc/4KbA80toZDQoe3w3FVZIU7aQX2IXW X53PCKPGD4oCB5e26iyMTKCm6J0VbeCT+FqJfdLioRvOF9KujzLNjcBAJZuc4vBkkFt8 d12UkejwjY7XdPp0W7kCvNsNCBA+DYHLv4TBuC2E5m6/ehOXayHzApGkWVRuXJSEYwpJ 3AWFKbs371tmfXRYRIj4vXOJ0L5eeZ3PgS35PmuHu3FsX+X6/vIN3qVzNbZGm+oAQwnf C2QogcZGZ9OKkDXIXGVKj4SXShVIpMlf3X0bPJkFDYP4HGgdReTdI+jLY8plFhsD7esN R2mg== X-Gm-Message-State: ALKqPweGcQ+DTjKz9tzwVeASHAnq+SPvDNIZ5rH3UGcDd1E38IgHMCA+ z8ONvJj2v+cmoycz6Lv6XMUodht6woxkVgYZmqYCTg== X-Google-Smtp-Source: AB8JxZqh1mqWbSOTKLc9Lor/vnSoH/r8wCY6RChg5wzpRpZdvfPM21jdQkmj5FMksBwqGAnwtWqI+/zNHv+wnrR4IBU= X-Received: by 2002:adf:a0b9:: with SMTP id m54-v6mr6712710wrm.76.1527180149046; Thu, 24 May 2018 09:42:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Thu, 24 May 2018 17:41:51 +0100 Message-ID: Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) To: Ed Maste Cc: Philip Homburg , freebsd-current , Andreas Nilsson Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 16:42:31 -0000 On Thu, May 24, 2018 at 2:11 PM Ed Maste wrote: > On 23 May 2018 at 17:51, Philip Homburg wrote: > > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > > BIOS version 2.7.0. With both images, the USB stick is not recognized. > > Can you download the image from > https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and > write it to a USB stick and try on this system? This is a > MBR-partitioned dual-mode test image. It's not an installer - it > should just boot to a login prompt - but can be used to test this > scheme. > Tested successfully on Dell Latitude E7450 for both legacy BIOS and UEFI boot mode. From owner-freebsd-current@freebsd.org Thu May 24 16:49: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 54ACCEF80AA for ; Thu, 24 May 2018 16:49:43 +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 AC15277857; Thu, 24 May 2018 16:49:42 +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 w4OGncGS041472; Thu, 24 May 2018 09:49:38 -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 w4OGnblp041471; Thu, 24 May 2018 09:49:37 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805241649.w4OGnblp041471@pdx.rh.CN85.dnsmgr.net> Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) In-Reply-To: To: Ed Maste Date: Thu, 24 May 2018 09:49:37 -0700 (PDT) CC: Philip Homburg , Johannes Lundberg , FreeBSD Current , Andreas Nilsson , re@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.26 Precedence: 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, 24 May 2018 16:49:43 -0000 > On 23 May 2018 at 17:51, Philip Homburg wrote: > > I tried both FreeBSD-11.2-BETA2-amd64-bootonly.iso.xz and > > FreeBSD-11.2-BETA2-amd64-mini-memstick.img.xz on a Dell PowerEdge 2950 > > BIOS version 2.7.0. With both images, the USB stick is not recognized. > > Can you download the image from > https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and > write it to a USB stick and try on this system? This is a > MBR-partitioned dual-mode test image. It's not an installer - it > should just boot to a login prompt - but can be used to test this > scheme. Ed, I tested this here on my R710 that was failing to boot in Bios mode with the amd64-11.2-Beta2 disc1.iso, your mini-image boots fine in either Bios or UEFI mode on my Dell R710, so what ever you did fixed at least my one data point. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu May 24 17:26: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 9C04DEF93D0 for ; Thu, 24 May 2018 17:26:53 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::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 07E2779BF3; Thu, 24 May 2018 17:26:52 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 734212e5 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 24 May 2018 10:26:50 -0700 (PDT) Subject: Re: Intel Corporation Wireless 8265 / 8275 (rev 78) on FreeBSD 12 To: Mateusz Piotrowski <0mp@FreeBSD.org>, freebsd-current@freebsd.org References: <1366699076.177914.1527061285836.ref@mail.yahoo.com> <1366699076.177914.1527061285836@mail.yahoo.com> <99b881e0-9915-e859-070c-df40673400f1@nomadlogic.org> <20180524145548.09f061ad@oxy> From: Pete Wright Message-ID: Date: Thu, 24 May 2018 10:26:49 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180524145548.09f061ad@oxy> 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.26 Precedence: 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, 24 May 2018 17:26:53 -0000 On 05/24/2018 05:55, Mateusz Piotrowski wrote: > On Wed, 23 May 2018 09:46:13 -0700 > Pete Wright wrote: > >> On 05/23/2018 00:41, David Pan wrote: >>> how config the Intel Corporation Wireless 8265 / 8275 (rev 78) on >>> FreeBSD 12?I installed FreeBSD 12 on my thinkpad t470p ,and can not >>> drive the Intel Wireless Card. >>> please help me fix that, >> I have this working on my end under both 12-current and 11-stable. >> here's my configuration: >> >> output from "pciconf -lv" >> iwm0@pci0:3:0:0:    class=0x028000 card=0x10108086 chip=0x24fd8086 >> rev=0x78 hdr=0x00 >>     vendor     = 'Intel Corporation' >>     device     = 'Wireless 8265 / 8275' >>     class      = network >> >> >> to bring up the card i have added this entry to /etc/rc.conf: >> >> kld_list="if_iwm" >> >> then configuring the interface is the same as any other wifi as per the >> handbook, the device will be available as "iwm0". > Shouldn't you load some firmware as well? That's what the iwm(4) manual > and WiFi/FAQ wiki page[1] say. on my system loading if_iwm via the above rc.conf entry pulls in the appropriate firmware kld: $ kldstat|grep iwm  6    1 0xffffffff82c21000 14af0    if_iwm.ko  7    1 0xffffffff82c36000 1ba76f   iwm8265fw.ko -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Thu May 24 18:50: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 62472EFB2FA for ; Thu, 24 May 2018 18:50:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.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 CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 000847D6D2; Thu, 24 May 2018 18:50:01 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (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 C3A62F721; Thu, 24 May 2018 18:50:01 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 81F2DF5A; Thu, 24 May 2018 18:50:00 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 4jWJmYBEq-C9; Thu, 24 May 2018 18:49:58 +0000 (UTC) Subject: Re: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com CAE3CF55 To: Mark Millard , FreeBSD Current Cc: Cy.Schubert@cschubert.com, "O. Hartmann" References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8CGwwF AlrozigFCQpgez0ACgkQNddxu25Gl8+m5Af/R3VEdxNMAcDIes9ADhQyofj20SPV3eCJ3HYR OebTSuNdOudGt4AAyA8Ks94u9hiIp5IGsc6RDsT9W7O2vgXhd6eV3eiY5Oif5xLIYrIDVu1Y 1GyRxRrPEn/QOqDN6uFZCPwK1aOapGcYCrO9lB0gMuTVfgHanU61rgC9tMX0OoAOyRd+V3/M 8lDNhjJdF/IpO3SdYzKfkwduy4qamw4Gphcx/RfYQvYLq/eDkP8d50PphWdboqWBwNRHayro W/07OGzfxM5fJ5mBsXPQcO2QcRjkyHf6xCM6Hi1qQL4OnXMNE/ZTX0lnOj1/pH93TlzSHZMP TaiiA/MBD3vGsXBmBg== Organization: FreeBSD Message-ID: <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> Date: Thu, 24 May 2018 11:49:59 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vy9WVSTv6BtQPvM2Zvg1ni8BO74Hqqmxl" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 18:50:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vy9WVSTv6BtQPvM2Zvg1ni8BO74Hqqmxl Content-Type: multipart/mixed; boundary="95OKvJKNoQ8TvcwuMENU8NEfDPOAW9JA5"; protected-headers="v1" From: Bryan Drewery To: Mark Millard , FreeBSD Current Cc: Cy.Schubert@cschubert.com, "O. Hartmann" Message-ID: <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> Subject: Re: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> In-Reply-To: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> --95OKvJKNoQ8TvcwuMENU8NEfDPOAW9JA5 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/21/2018 10:17 PM, Mark Millard wrote: > Attempting to build head -r334014 from -r333947 includes the code from = -r334008, > and for which I get: >=20 > --- parser.o --- > /usr/src/bin/sh/parser.c:1440:9: error: use of undeclared identifier 'C= QNL' > case CQNL: > ^ > 1 error generated. >=20 > for what was added in -r334008. >=20 > # grep -r CQNL /usr/src/* | more > /usr/src/bin/sh/mksyntax.c: { "CQNL", "newline character in q= uotes" }, > /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); > /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); > /usr/src/bin/sh/mksyntax.c: add("\n", "CQNL"); > /usr/src/bin/sh/parser.c: case CQNL: > /usr/src/contrib/libarchive/libarchive/test/test_read_format_rar_binary= _data.rar.uu:M+M7)?9;.A%CQNL-+4::&_UJQ*P"PPW:>)I5*8)7^>6(\]!Q"^9YCE>>`9OG= 8 >=20 > Apparently this is something WITH_META_MODE=3D does not deal with. > Rebuilding after: >=20 > rm -fr /usr/obj/amd64_clang/* >=20 > (here I normally have the build materials) built fine. >=20 > (The "Making top.local.h from /usr/src/contrib/top/top.local.hs" > change to no longer have top.local.h or top.local.hs was another > example: for a while top.local.h was still referenced and old ones > would still be used if present.) >=20 It was a bug with the rescue build with dependency handling. I've fixed it in r334177. --=20 Regards, Bryan Drewery --95OKvJKNoQ8TvcwuMENU8NEfDPOAW9JA5-- --vy9WVSTv6BtQPvM2Zvg1ni8BO74Hqqmxl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJbBwlYAAoJEDXXcbtuRpfPlqIIAIIT4X3VyUIQ/FfHXOPuEj/5 S3GJrkl49uQrpz6/zFxWzKwwv142/zku3NVilXcQfExEgZjM3FXTbmgbSpJvslbu RdVjgzeAL+q5VPzdgqxkbbunMrWHumRqJWm9MYm3YPVdr72H+8HPyphfheC9UZ25 P8sO4j5o63m4LL5632k2hMatcLCgcyI5M3Kht76BtyGEYV+Z/lDHLs9agAxgcYf6 lPa8OWAwirAc6i7qBBwdSm/MIK3mKuJLEuxHf0WUDzVJEoevZ+9ymoY+DRv4qJCg e+J09rkDqloCAnVKHeHmJucm76ts2sSFiDupgnqTjf5YA/1x2WDNAOCfwmIMb84= =BC6L -----END PGP SIGNATURE----- --vy9WVSTv6BtQPvM2Zvg1ni8BO74Hqqmxl-- From owner-freebsd-current@freebsd.org Thu May 24 22:45: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 9C3D9F6B637 for ; Thu, 24 May 2018 22:45:54 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FCFC680FB; Thu, 24 May 2018 22:45:54 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1527201952; bh=vxwBGgNNQaUclF7ow7u1t/gnT1blcUoyP4qpbMb 116w=; b=njBh1DQ6jR8/d5cUncLEGSZg3BaV+W0mUFa3AM1QZomJI/UuU9uLUco pfAxVqFh0ebS1sae4oj/q4dYey7OtDd7WjNdCcUI6/1A/ZX6p2yHBs0Bd9IgH3Kl +7ecZZE4lMleSCFz+JdTX8QH/hnAhDbphqvqiBRNIIgBnazWMvTM= Received: from toshi.auburn.protected-networks.net (unknown [IPv6:2001:470:1f07:4e1::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 41B801C5F9; Thu, 24 May 2018 18:45:52 -0400 (EDT) To: freebsd-current , cognet@freebsd.org From: Michael Butler Subject: SVN - r334189 breaks build Openpgp: preference=signencrypt Message-ID: Date: Thu, 24 May 2018 18:45:50 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 24 May 2018 22:45:54 -0000 On a GENERIC box .. --- bridgestp.o --- /usr/src/sys/net/bridgestp.c:2046:2: error: no member named 'cstqe_next' in 'struct ifnet::(anonymous at /usr/src/sys/net/if_var.h:241:2)'; did you mean 'stqe_next'? CK_STAILQ_FOREACH(ifp, &V_ifnet, if_link) { ^ /usr/src/sys/contrib/ck/include/ck_queue.h:253:13: note: expanded from macro 'CK_STAILQ_FOREACH' (var) = CK_STAILQ_NEXT((var), field)) ^ /usr/src/sys/contrib/ck/include/ck_queue.h:291:32: note: expanded from macro 'CK_STAILQ_NEXT' (ck_pr_load_ptr(&(elm)->field.cstqe_next)) ^ /usr/src/sys/net/if_var.h:241:2: note: 'stqe_next' declared here STAILQ_ENTRY(ifnet) if_link; /* all struct ifnets are chained (CK_) */ And on a custom kernel .. --- hwpmc_mod.o --- /usr/src/sys/dev/hwpmc/hwpmc_mod.c:1727:2: error: no member named 'clh_first' in 'struct (anonymous at /usr/src/sys/dev/hwpmc/hwpmc_mod.c:178:8)'; did you mean 'lh_first'? CK_LIST_FOREACH(po, &pmc_ss_owners, po_ssnext) ^ /usr/src/sys/contrib/ck/include/ck_queue.h:363:15: note: expanded from macro 'CK_LIST_FOREACH' for ((var) = CK_LIST_FIRST((head)); \ ^ /usr/src/sys/contrib/ck/include/ck_queue.h:358:54: note: expanded from macro 'CK_LIST_FIRST' #define CK_LIST_FIRST(head) ck_pr_load_ptr(&(head)->clh_first) ^ /usr/src/sys/dev/hwpmc/hwpmc_mod.c:178:8: note: 'lh_first' declared here static LIST_HEAD(, pmc_owner) pmc_ss_owners; ^ From owner-freebsd-current@freebsd.org Thu May 24 22:46: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 07426F6B688 for ; Thu, 24 May 2018 22:46:54 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89852681AF; Thu, 24 May 2018 22:46:53 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x22f.google.com with SMTP id g7-v6so3911727otj.11; Thu, 24 May 2018 15:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2TioQ3mLePT/JQ7I7ld49FMAPhDZ3vqnLlxwm6x/bsI=; b=iA4QNlIXtcwlaMTjZJE60ejTVTYy/GDghy8KNPe2y23KIUbuiM016mPmOROAvj6pnM ZsFL+68p6hp3pmjKAcNQYNPr4DkLhsE5eRAG1gqx7l6bGophzzTCkF9WoMDe//UlcNZP EZ/wtKSt+0PM3HaxxeyaYTeU/oKuybPScpFXniTkcqCpGZMDfXfVAR6CPs0e8tINWG8b UBbLOohRhO4HsDkx7bx6lM7sx/jjOf/WiPCVIsyyG88LwKI7xw0PrUzBQX5iocRGQIcT B+gn6Nrhd5P2eha/SYPfbnDwMBR0kFvRyNyEJn/zjZNpZguTWqCrRXNgdOLrukEPURpk 7QVQ== 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=2TioQ3mLePT/JQ7I7ld49FMAPhDZ3vqnLlxwm6x/bsI=; b=JV5Zt5IPMN8IacFaaOsvUUc8fnq/5SeTbo6UaHFvtBE95fRDEU1cfGlF0lFBSZIhnv dwgtHBs5j5Tz4/loodkAl/mHCsaf1MvRVGEcL4InhGCkz9uRV6E4IRCCZYxwaqAlr4ga IS5cnaRr/2oGwR0Y2KI0wkDvxy48c2Id0xgF4E9rAnHHJHRYdfvcDBhfmmIOSR1kt6Fl a+zl+nDn3omAd0zAkN+wJn3vzYOjUXlp4sAMIEoloZrB9KP4eqQD36w7X6K+hQi8Qk+W FHIAhLgBj/gTGQdlBe2pUM+yHg//PqKXgeVf06cNOO618V+cxeHHh8w6sS8eWa4YedLE Ljpg== X-Gm-Message-State: ALKqPwf/HpXb4+hA4KOy7nITRj/o68DLiwviPTikjEdBD7493+quJL7f HvXOISaDIqh5DbNR+58PGMHBPhKUps78T0FoBb8wrw== X-Google-Smtp-Source: AB8JxZq+4WaJXsiwk+HJSuTeIBwzrEQK+lSnHxTcMTIE9IvrgumRW0aUdvVABcAkG3wyI6qEaUMLKdXYIgNNS2ZVhao= X-Received: by 2002:a9d:3e07:: with SMTP id a7-v6mr5681211otd.150.1527202012833; Thu, 24 May 2018 15:46:52 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Thu, 24 May 2018 15:46:52 -0700 (PDT) In-Reply-To: References: From: "K. Macy" Date: Thu, 24 May 2018 15:46:52 -0700 X-Google-Sender-Auth: yWpW1sWEXownrxLss2r2mW7FyXE Message-ID: Subject: Re: SVN - r334189 breaks build To: Michael Butler Cc: freebsd-current , cognet@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 24 May 2018 22:46:54 -0000 Fix going in in about 10 On Thu, May 24, 2018 at 3:45 PM, Michael Butler wrote: > On a GENERIC box .. > > --- bridgestp.o --- > /usr/src/sys/net/bridgestp.c:2046:2: error: no member named 'cstqe_next' > in 'struct ifnet::(anonymous at /usr/src/sys/net/if_var.h:241:2)'; did > you mean 'stqe_next'? > CK_STAILQ_FOREACH(ifp, &V_ifnet, if_link) { > ^ > /usr/src/sys/contrib/ck/include/ck_queue.h:253:13: note: expanded from > macro 'CK_STAILQ_FOREACH' > (var) = CK_STAILQ_NEXT((var), field)) > ^ > /usr/src/sys/contrib/ck/include/ck_queue.h:291:32: note: expanded from > macro 'CK_STAILQ_NEXT' > (ck_pr_load_ptr(&(elm)->field.cstqe_next)) > ^ > /usr/src/sys/net/if_var.h:241:2: note: 'stqe_next' declared here > STAILQ_ENTRY(ifnet) if_link; /* all struct ifnets are chained > (CK_) */ > > And on a custom kernel .. > > --- hwpmc_mod.o --- > /usr/src/sys/dev/hwpmc/hwpmc_mod.c:1727:2: error: no member named > 'clh_first' in 'struct (anonymous at > /usr/src/sys/dev/hwpmc/hwpmc_mod.c:178:8)'; did you mean 'lh_first'? > CK_LIST_FOREACH(po, &pmc_ss_owners, po_ssnext) > ^ > /usr/src/sys/contrib/ck/include/ck_queue.h:363:15: note: expanded from > macro 'CK_LIST_FOREACH' > for ((var) = CK_LIST_FIRST((head)); > \ > ^ > /usr/src/sys/contrib/ck/include/ck_queue.h:358:54: note: expanded from > macro 'CK_LIST_FIRST' > #define CK_LIST_FIRST(head) ck_pr_load_ptr(&(head)->clh_first) > ^ > /usr/src/sys/dev/hwpmc/hwpmc_mod.c:178:8: note: 'lh_first' declared here > static LIST_HEAD(, pmc_owner) pmc_ss_owners; > ^ > _______________________________________________ > 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 May 25 08:51:15 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 9D715F7668D for ; Fri, 25 May 2018 08:51:15 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 0E944786FF; Fri, 25 May 2018 08:51:14 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fM8RL-0000H5C; Fri, 25 May 2018 10:51:11 +0200 Message-Id: To: Ed Maste Cc: Johannes Lundberg , FreeBSD Current , Andreas Nilsson Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com References: In-reply-to: Your message of "Thu, 24 May 2018 09:11:25 -0400 ." Date: Fri, 25 May 2018 10:51:10 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 25 May 2018 08:51:15 -0000 >Can you download the image from >https://people.freebsd.org/~emaste/mini-image.amd64.xz, uncompress and >write it to a USB stick and try on this system? This is a >MBR-partitioned dual-mode test image. It's not an installer - it >should just boot to a login prompt - but can be used to test this >scheme. I have bad news and some good news. The bad news is that with this image the USB stick doesn't get recognized as a boot device. Same as with the 11.2-BETA2 images. The good news is that if I completely recreate the MBR, keeping the layout of the partitions the same, then the USB stick is recognized. The weird news is that it then proceeds to boot from harddisk. But that may be an issue with the boot code I put on. So the issue is limited to the MBR. I'll try to figure out what exactly makes the difference. From owner-freebsd-current@freebsd.org Fri May 25 09:49: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 75C14F778B3 for ; Fri, 25 May 2018 09:49:24 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DBBCA7A344; Fri, 25 May 2018 09:49:23 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?utf-8?B?TSZTIC0gS3Jhc3puYWkgQW5kcsOhcw==?= To: Bryan Drewery , Mark Millard , FreeBSD Current CC: "Cy.Schubert@cschubert.com" , "O. Hartmann" Subject: RE: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh Thread-Topic: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh Thread-Index: AQHT85CWy0NxEI2nikGrjACNHS43+qRAMcmg Date: Fri, 25 May 2018 09:49:21 +0000 Message-ID: References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> In-Reply-To: <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.4.90] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 25 May 2018 09:49:24 -0000 SGkNCg0KSSBmb3VuZCBhbm90aGVyIHByb2JsZW0gd2l0aCBjb21waWxpbmcgRnJlZUJTRC1DVVJS RU5UDQoNCndoZW4gSSB0cmllZCB0byBjb21waWxlIEdFTkVSSUMgaW5zdGVhZCBvZiBteSBjdXN0 b20gSSBydW4gaW50byB0aGUgZm9sbG93aW5nOg0KDQptYWtlIGluc3RhbGx3b3JsZCBmYWlscyB3 aXRoIA0KDQovYmluL3NoOiAvdXNyL29iai91c3Ivc3JjL2FtZDY0LmFtZDY0L3Jlc2N1ZS9yZXNj dWUvcmVzY3VlOiBub3QgZm91bmQNCnJlc2N1ZS9zaCBjaGVjayBmYWlsZWQsIGluc3RhbGxhdGlv biBhYm9ydGVkLiANCg0KSSB1c2VkIG9yaWdpbmFsbHkgYSBjdXN0b21pemVkIHNyYy5jb25mIHdo aWNoIC0gYW1vbmcgb3RoZXJzIC0gc3BlY2lmaWVzIFdJVEhPVVRfUkVTQ1VFLg0KV2hlbiB0cnlp bmcgdG8gY29tcGlsZSBHRU5FUklDIEkgcmVtb3ZlZCBzcmMuY29uZiBhbmQgSSB0aG91Z2h0IEkg d291bGQgZ2V0IGEgY29tcGxldGUgRnJlZUJTRC1DVVJSRU5UIHdpdGggR0VORVJJQywgd2l0aCBy ZXNjdWUgZmlsZXMsIGV0Yy4gDQoNClRoZSBzb3VyY2UgdHJlZSBpcyBhdCByMzM0MjAwDQoNCg0K YmVzdCByZWdhcmRzDQoNCkFuZHLDoXMgS3Jhc3puYWkNCg0KDQotLS0tLUVyZWRldGkgw7x6ZW5l dC0tLS0tDQpGZWxhZMOzOiBvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmcgW21haWx0 bzpvd25lci1mcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmddIE1lZ2hhdGFsbWF6w7MgQnJ5YW4g RHJld2VyeQ0KS8O8bGR2ZTogMjAxOC4gbcOhanVzIDI0LiAyMDo1MA0KQ8OtbXpldHQ6IE1hcmsg TWlsbGFyZDsgRnJlZUJTRCBDdXJyZW50DQpNw6Fzb2xhdG90IGthcDogQ3kuU2NodWJlcnRAY3Nj aHViZXJ0LmNvbTsgTy4gSGFydG1hbm4NClTDoXJneTogUmU6IEFub3RoZXIgcmVjZW50IFdJVEhf TUVUQV9NT0RFPSBnb3RjaGEgIjogaGFuZGxpbmcgc3ZuIGNvbW1pdDogcjMzNDAwOCAtIGhlYWQv YmluL3NoDQoNCk9uIDUvMjEvMjAxOCAxMDoxNyBQTSwgTWFyayBNaWxsYXJkIHdyb3RlOg0KPiBB dHRlbXB0aW5nIHRvIGJ1aWxkIGhlYWQgLXIzMzQwMTQgZnJvbSAtcjMzMzk0NyBpbmNsdWRlcyB0 aGUgY29kZSBmcm9tIA0KPiAtcjMzNDAwOCwgYW5kIGZvciB3aGljaCBJIGdldDoNCj4gDQo+IC0t LSBwYXJzZXIubyAtLS0NCj4gL3Vzci9zcmMvYmluL3NoL3BhcnNlci5jOjE0NDA6OTogZXJyb3I6 IHVzZSBvZiB1bmRlY2xhcmVkIGlkZW50aWZpZXIgJ0NRTkwnDQo+ICAgICAgICAgICAgICAgICAg ICAgICAgIGNhc2UgQ1FOTDoNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeDQo+IDEg ZXJyb3IgZ2VuZXJhdGVkLg0KPiANCj4gZm9yIHdoYXQgd2FzIGFkZGVkIGluIC1yMzM0MDA4Lg0K PiANCj4gIyBncmVwIC1yIENRTkwgL3Vzci9zcmMvKiB8IG1vcmUNCj4gL3Vzci9zcmMvYmluL3No L21rc3ludGF4LmM6ICAgICB7ICJDUU5MIiwgICAgICAgIm5ld2xpbmUgY2hhcmFjdGVyIGluIHF1 b3RlcyIgfSwNCj4gL3Vzci9zcmMvYmluL3NoL21rc3ludGF4LmM6ICAgICBhZGQoIlxuIiwgIkNR TkwiKTsNCj4gL3Vzci9zcmMvYmluL3NoL21rc3ludGF4LmM6ICAgICBhZGQoIlxuIiwgIkNRTkwi KTsNCj4gL3Vzci9zcmMvYmluL3NoL21rc3ludGF4LmM6ICAgICBhZGQoIlxuIiwgIkNRTkwiKTsN Cj4gL3Vzci9zcmMvYmluL3NoL3BhcnNlci5jOiAgICAgICAgICAgICAgICAgICAgICAgY2FzZSBD UU5MOg0KPiAvdXNyL3NyYy9jb250cmliL2xpYmFyY2hpdmUvbGliYXJjaGl2ZS90ZXN0L3Rlc3Rf cmVhZF9mb3JtYXRfcmFyX2JpbmFyDQo+IHlfZGF0YS5yYXIudXU6TStNNyk/OTsuQSVDUU5MLSs0 OjomX1VKUSpQIlBQVzo+KUk1KjgpN14+NihcXSFRIl45WUNFPj4NCj4gYDlPRzgNCj4gDQo+IEFw cGFyZW50bHkgdGhpcyBpcyBzb21ldGhpbmcgV0lUSF9NRVRBX01PREU9IGRvZXMgbm90IGRlYWwg d2l0aC4NCj4gUmVidWlsZGluZyBhZnRlcjoNCj4gDQo+IHJtIC1mciAvdXNyL29iai9hbWQ2NF9j bGFuZy8qDQo+IA0KPiAoaGVyZSBJIG5vcm1hbGx5IGhhdmUgdGhlIGJ1aWxkIG1hdGVyaWFscykg YnVpbHQgZmluZS4NCj4gDQo+IChUaGUgIk1ha2luZyB0b3AubG9jYWwuaCBmcm9tIC91c3Ivc3Jj L2NvbnRyaWIvdG9wL3RvcC5sb2NhbC5ocyINCj4gY2hhbmdlIHRvIG5vIGxvbmdlciBoYXZlIHRv cC5sb2NhbC5oIG9yIHRvcC5sb2NhbC5ocyB3YXMgYW5vdGhlcg0KPiBleGFtcGxlOiBmb3IgYSB3 aGlsZSB0b3AubG9jYWwuaCB3YXMgc3RpbGwgcmVmZXJlbmNlZCBhbmQgb2xkIG9uZXMgDQo+IHdv dWxkIHN0aWxsIGJlIHVzZWQgaWYgcHJlc2VudC4pDQo+IA0KDQpJdCB3YXMgYSBidWcgd2l0aCB0 aGUgcmVzY3VlIGJ1aWxkIHdpdGggZGVwZW5kZW5jeSBoYW5kbGluZy4gSSd2ZSBmaXhlZCBpdCBp biByMzM0MTc3Lg0KDQoNCi0tDQpSZWdhcmRzLA0KQnJ5YW4gRHJld2VyeQ0KDQo= From owner-freebsd-current@freebsd.org Fri May 25 12:14:15 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 DD7F7EAB57A for ; Fri, 25 May 2018 12:14:15 +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 78F8F7F2F9 for ; Fri, 25 May 2018 12:14:15 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3459CEAB575; Fri, 25 May 2018 12:14:15 +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 22B43EAB571 for ; Fri, 25 May 2018 12:14:15 +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 87B7E7F2F8 for ; Fri, 25 May 2018 12:14:14 +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 w4PCE5Bu095474 for ; Fri, 25 May 2018 12:14:05 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w4PCE53c095473 for current@freebsd.org; Fri, 25 May 2018 05:14:05 -0700 (PDT) (envelope-from david) Date: Fri, 25 May 2018 05:14:05 -0700 From: David Wolfskill To: current@freebsd.org Subject: You might want to be careful around r334147... Message-ID: <20180525121405.GL1132@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SPlM+hXbTX1U6Tnd" Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 25 May 2018 12:14:16 -0000 --SPlM+hXbTX1U6Tnd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I had no issues on my build machine (head/amd64; GENERIC kernel) performing src-based upgrades from r333974 -> r334147 -> r334205 (first step yesterday; second today). On my laptop (also head/amd64; lightly-customize kernel that includes GENERIC), I was able to go from r333974 -> r334147, booted r334147 OK and did a quick smoke-test (login via xdm; stuff seemed to work). Today, however, after updating source to r334205, the laptop locked up hard (only way out I could find was power-cycle) twice, and performed a spontaneous reboot -- each during "make buildworld." As things presently stand, I have reverted to the r333974 kernel (built the day before yesterday) and have started the build for r334205 over with an empty /usr/obj. Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump's EPA excludes reporters from a meeting on contaminants -- why? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --SPlM+hXbTX1U6Tnd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlsH/g1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7heujAf+PeMyETeH9xIKIXg+LyNHqE44HA0OPJCgz1A3zXc0L88lVBhFRtZ4/78Z RemNyouZ8MRh3QWsn0VIgHeRBFvec60uCiOkVav6TfLINk5fR3pM/LXhpBhOLcnt NEk0eBbicPZiwYrIoyAYKWQJzs7pvFyYX4Jq81RwNHM6wsN0Ma1An8jpgeuWITcl EiWJRDuJVWAFbZOMRBevqj8PupQQetLgw4tgXr86nnDdu3OcBC8DxgnH+2sB5yUl GRarb+3zSrENbSuk03Z5sJirJoPXVhd9nmk2NIgcWfJD2ZJkFMmBJdtw4Z/w9jHw XxTKxR1DdZigvy2B9ERB1FTB27HXpA== =Gqfc -----END PGP SIGNATURE----- --SPlM+hXbTX1U6Tnd-- From owner-freebsd-current@freebsd.org Fri May 25 16:33: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 360A4EED58A for ; Fri, 25 May 2018 16:33:00 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-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 C792A688F7; Fri, 25 May 2018 16:32:59 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (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 982412B15; Fri, 25 May 2018 16:32:59 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 590127BE9; Fri, 25 May 2018 16:32:58 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id POlGRHhKK35b; Fri, 25 May 2018 16:32:56 +0000 (UTC) Subject: Re: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com CD9277BE3 To: =?UTF-8?Q?M&S_-_Krasznai_Andr=c3=a1s?= , Mark Millard , FreeBSD Current Cc: "Cy.Schubert@cschubert.com" , "O. Hartmann" References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8CGwwF AlrozigFCQpgez0ACgkQNddxu25Gl8+m5Af/R3VEdxNMAcDIes9ADhQyofj20SPV3eCJ3HYR OebTSuNdOudGt4AAyA8Ks94u9hiIp5IGsc6RDsT9W7O2vgXhd6eV3eiY5Oif5xLIYrIDVu1Y 1GyRxRrPEn/QOqDN6uFZCPwK1aOapGcYCrO9lB0gMuTVfgHanU61rgC9tMX0OoAOyRd+V3/M 8lDNhjJdF/IpO3SdYzKfkwduy4qamw4Gphcx/RfYQvYLq/eDkP8d50PphWdboqWBwNRHayro W/07OGzfxM5fJ5mBsXPQcO2QcRjkyHf6xCM6Hi1qQL4OnXMNE/ZTX0lnOj1/pH93TlzSHZMP TaiiA/MBD3vGsXBmBg== Organization: FreeBSD Message-ID: Date: Fri, 25 May 2018 09:32:55 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nIAWtFmgaGl7W6M5TyqnyjE5KCa0LnRgH" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 25 May 2018 16:33:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nIAWtFmgaGl7W6M5TyqnyjE5KCa0LnRgH Content-Type: multipart/mixed; boundary="fVyUCHn9KnWgJUaSoOvKMCCRoY0J1vDdb"; protected-headers="v1" From: Bryan Drewery To: =?UTF-8?Q?M&S_-_Krasznai_Andr=c3=a1s?= , Mark Millard , FreeBSD Current Cc: "Cy.Schubert@cschubert.com" , "O. Hartmann" Message-ID: Subject: Re: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> In-Reply-To: --fVyUCHn9KnWgJUaSoOvKMCCRoY0J1vDdb Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/25/2018 2:49 AM, M&S - Krasznai Andr=C3=A1s wrote: > Hi >=20 > I found another problem with compiling FreeBSD-CURRENT >=20 > when I tried to compile GENERIC instead of my custom I run into the fol= lowing: >=20 > make installworld fails with=20 >=20 > /bin/sh: /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue: not found > rescue/sh check failed, installation aborted.=20 >=20 > I used originally a customized src.conf which - among others - specifie= s WITHOUT_RESCUE. > When trying to compile GENERIC I removed src.conf and I thought I would= get a complete FreeBSD-CURRENT with GENERIC, with rescue files, etc.=20 >=20 Unclear to me. You did buildworld with WITHOUT_RESCUE=3Dyes set and then removed 'WITHOUT_RESCUE' from your src.conf (by removing src.conf), and then did buildworld and then installworld and hit this issue? All with WITH_META_MODE=3Dyes? Or did you disable META_MODE at some point? > The source tree is at r334200 >=20 >=20 > best regards >=20 > Andr=C3=A1s Krasznai --=20 Regards, Bryan Drewery --fVyUCHn9KnWgJUaSoOvKMCCRoY0J1vDdb-- --nIAWtFmgaGl7W6M5TyqnyjE5KCa0LnRgH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJbCDq4AAoJEDXXcbtuRpfPFEMH/A5DQ0BVVyANlWxyZK3cPYY9 quhWc4XF6whWXCTQGZqlYXi61r0e49ckLyLeZC6rOVZJDElJIQ9ihTLwfkd0DOux CyttyM0HXvPWTVSD/qOzyrzwCLjzMi66IFGjd8KcNu2C8cMPJY2DyDK90U6m3pz3 Wtvk+U4nwvXwIqScScITxQCnh6gpPyKKJccGt6hc9lQgX8z1qNF79bbQbD05/XE3 NPiVXIm2K+m2tzf5N/YE/NDso6ZXf0EbAbPu/Aba4re0yycRLB4RVe977fvPrsFm x7TgU4d+nH5dQROecPG/6CxEl8KCzdQ/tVfPQDSKz9sVpB/Gs7UWnfsP2z/zsWM= =HtPl -----END PGP SIGNATURE----- --nIAWtFmgaGl7W6M5TyqnyjE5KCa0LnRgH-- From owner-freebsd-current@freebsd.org Sat May 26 10:00: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 8AD61F6FCC3 for ; Sat, 26 May 2018 10:00:28 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7A3169A6C for ; Sat, 26 May 2018 10:00:27 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22a.google.com with SMTP id y15-v6so12976835wrg.11 for ; Sat, 26 May 2018 03:00:27 -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=+3W3ss+PMKtxOkLQYeTpuYw166OxKBEgS6rXhX7tn9o=; b=WdV4ZR03/e78FBvUpxKNLs4TTnYM5OwC1zFZyjXUFh/NopCrHioDhuZ3s2bPRRWpY6 B1unA6YqtSaJSFI8W26oUn8HLAIHSufvdeqm/SnwfG/1Dcm2+vHrnRH7tS3dmIpKJX/U 1KGpKDe+u2TYZnZ0Dwtug4qye0rEN49psYmWPRO1yoWPN+03r3SiXKnyKMLatVh5CKTK 9ZqdGPXxBDYqQSOkdONLR0oszZAVc7Gn4kAEIvnYxl/wCAPVWgbIA6ru0wHfdlGSquwr NnW6CK85SJifY8xxZJY3yp63ExQaelnREBfELdaVmWQitlyC9Gf/5WjQVQMBsJY35DCz QTug== 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=+3W3ss+PMKtxOkLQYeTpuYw166OxKBEgS6rXhX7tn9o=; b=FoCguvjkVb8zcW8NxUjx+go+80WpHf2Q/VCk/sQPiHoeuLpe2ChnkoMdISoWJGRyts xWRq701BkooCu5Hw/yPfCVjnuBEDFSA5euSR7QCt+9gPZwz0RfGOBQxDlIsnTBebh7p9 PS6irl0LtT4w9zjVQ70kJdiFyyjYjepyHJZepMhjJeu86rjs1qLLJ0uA1RQVOGDbTN8A uF0UFkO6Qak9aZwvzCzTjCsCopRP8o1mIzxX3YfG5FnXvoxpd9mBh1v39hBuzR8puuFs UT4n0RwDTWwsvOoCCruY6Iodqe7qniMR9/hzFWhRZz9y5vu3tTBSrEyz+Ram9Wm5KcfE ZL3w== X-Gm-Message-State: ALKqPwfa8yMt1kqyRTk4zjGEwRU7rPUbAkSjQHlLWd2FcGd7sM4AnoMd Fi4BBzRfVtpshvS0A599VA6W53bqfoqb2GOANS3mlw== X-Google-Smtp-Source: AB8JxZpkxy8DC4uic4fdPAhZKq9TU3X35Iq3mOeYsZJ8f9NKYLgS+nKeBAz9IWN9qjt/YfsWizNKOCQ+yNqWugHv5Qg= X-Received: by 2002:adf:aa08:: with SMTP id p8-v6mr4501759wrd.140.1527328826457; Sat, 26 May 2018 03:00:26 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Sat, 26 May 2018 10:59:50 +0100 Message-ID: Subject: Floating point in kernel? To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 10:00:28 -0000 Hi The new AMD graphics drivers use floats in kernel space. Upstream Linux code has something like: kernel_fpu_begin(); ... kernel_fpu_end(); Do we have similar functions to save/restore FPU registers? Cheers From owner-freebsd-current@freebsd.org Sat May 26 10:11: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 9C227F7038E for ; Sat, 26 May 2018 10:11:10 +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 1A6FF6A0AD for ; Sat, 26 May 2018 10:11:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w4QAAxnC034995 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 26 May 2018 13:11:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w4QAAxnC034995 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w4QAAx2Q034994; Sat, 26 May 2018 13:10:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 26 May 2018 13:10:59 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: freebsd-current Subject: Re: Floating point in kernel? Message-ID: <20180526101059.GM88128@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 10:11:10 -0000 On Sat, May 26, 2018 at 10:59:50AM +0100, Johannes Lundberg wrote: > Hi > > The new AMD graphics drivers use floats in kernel space. > Upstream Linux code has something like: > kernel_fpu_begin(); > ... > kernel_fpu_end(); > > Do we have similar functions to save/restore FPU registers? Read fpu_kern(9). From owner-freebsd-current@freebsd.org Sat May 26 10:15: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 8E737F70501 for ; Sat, 26 May 2018 10:15:19 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04A5A6A317 for ; Sat, 26 May 2018 10:15:19 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id f6-v6so20302834wmc.4 for ; Sat, 26 May 2018 03:15:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=liDqVzeuNm+9t3j5hWISSjy3ipu7zkPuDkEYX7ny1VQ=; b=Nz9I9kGnMK4xWpr4NW08MlspPWptJYlcrnc7fJLp1S+1vyi4G0nJHs0IhnoRs+30Yp UtfPngQKGxEiwyPvMYOIgmK9X80PV3rBxBs1J4dvZ281OKqvQVkvaJtrGmN0I8uassgC tmbFXoBpULA7JufnQqU8FJE3yO0heD7Bs1RijeP3HHfFiiSEcpvbWZfzMBKBN2LYuOgg ND9LFKgoyAK3S6ztPg2CFaZTR50jpZ006Jj/XYPbw3vENf6zJrQ9hop4Cw+hi+mmN08n aG3TR9ZiwHcqKbVThDmLUYlpRtOdDstjB3H+ztkANoGLn+L1o4iAc1YDZQbEYWje25K3 a0IA== 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=liDqVzeuNm+9t3j5hWISSjy3ipu7zkPuDkEYX7ny1VQ=; b=C/evMds/YlE7SFKcC3cbOLVvF/CO+EGgOqLhOfKGU3fDkjDUP2QWd/XateWev1tZ89 G7vK18kojalXD+cqRq/owkVoU0VwXH0Tsd56eSxn7+Zb17CBUqGkLpnQvUUE2cRvBeaz BZcn+vVUSINAaUvSbrDpOTSMAFATZXliSQ+XULPGbZ8whs+EoIYmHi5vg3kC5Dt0JSJp I5I6/dphlx3LTqPCVP3DYhi2ElpYMnUpeteceP5Cxi2m5scXSTUtU9SMRnZqUQ7fIxWI qdNVlYbqpqKsrhB4STFsqtALMHXXnURq2BGnOcWcMZEFdcpDIjc4L0kG4xqXa209ge1D cmPA== X-Gm-Message-State: ALKqPwepomtHj6KtmB9IOLgicBpH8swz5UOft9w8PzmtumSzxw/Ijw00 lonAbxS7j8DIbNCmszdADEH1m8tWpXyszC29Rsw= X-Google-Smtp-Source: AB8JxZpkVMAARuwf4/neNk24HxPkF7tQSzMh/RER5rzo8RNHhXTPPbwEoADIbJGvh964P263KFr8b9ch7B3eGTHrD1s= X-Received: by 2002:a1c:f714:: with SMTP id v20-v6mr4555657wmh.73.1527329717888; Sat, 26 May 2018 03:15:17 -0700 (PDT) MIME-Version: 1.0 References: <20180526101059.GM88128@kib.kiev.ua> In-Reply-To: <20180526101059.GM88128@kib.kiev.ua> From: Johannes Lundberg Date: Sat, 26 May 2018 11:14:41 +0100 Message-ID: Subject: Re: Floating point in kernel? To: Konstantin Belousov Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 10:15:19 -0000 On Sat, May 26, 2018 at 11:11 AM Konstantin Belousov wrote: > On Sat, May 26, 2018 at 10:59:50AM +0100, Johannes Lundberg wrote: > > Hi > > > > The new AMD graphics drivers use floats in kernel space. > > Upstream Linux code has something like: > > kernel_fpu_begin(); > > ... > > kernel_fpu_end(); > > > > Do we have similar functions to save/restore FPU registers? > Read fpu_kern(9). > Thanks! Actually I found that just after hitting the send button :) From owner-freebsd-current@freebsd.org Sat May 26 11:23: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 D2CFFF71E65 for ; Sat, 26 May 2018 11:23:03 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 208726C073 for ; Sat, 26 May 2018 11:23:03 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-wr0-x234.google.com with SMTP id a15-v6so13190211wrm.0 for ; Sat, 26 May 2018 04:23:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:autocrypt:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=ptkn/bc2l8PEq21IoLwrQjYlcfr2vKX0gZVcmzeOOhw=; b=DHN7wRnHhfIvGK7D8NfrUI32BKQmKOn0z4I4NZC7g4veW5R42HpM5Ies5uYMXciucC I/lixnx8xtelQUY75ZNeCAZvDG4qNphCVlCKkOgSexBFWU86lKNJ92ENhjt+36WqR1S8 hRrIdjBAnE1cAKJoNjil4ciwk3Xr4ATs3BYc128+bggFriucHvK6OjarFx2DbswO/o/8 Lg0taxTbpmpQ4i7wmJf+ZzmiBfCKgVX5N00PvE2dZPSa1vR79GWa9x4yCjht2FT4Rirh R/aOfz0r9MKj/2Aq14mPKJ+qmwArNswbbUco4nfAQ6Fkf8VoBwzKoll3Kxhyu86V6K7m HpLw== 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=ptkn/bc2l8PEq21IoLwrQjYlcfr2vKX0gZVcmzeOOhw=; b=KuqWUV4iNXu8ZtwKl9if8dL8woNhVXJOLOCdC6d5re4/xjWFMv3aZVkJr5wC82IDsf HOOu7EmNQFYMHUO472ar1gMkRZAdidQTxkIh5423Kq+eAkYKAWJ02sCOd5d2DwcDl9GE Ek/2Ot2j5XNdTOE65MXaRz7pKV4xMbf8fjRJUIK6howMjgPAZ90WT8sMtIKt1Cb4WuJn r9pYfEe+zG2J9k7HOX/vRzPkgMs9pF/05Y0Xfv2sYjQ9Iuy91nvOGJy5psZj/qzd0JB8 ayhThBfY6qIyb+M5y/4CL0hNs5VopVmpICKKRVrZmpy+KbVTKun0bsvPBd7bZ+czRPV+ I8LA== X-Gm-Message-State: ALKqPwcd9POfBtZvegaH0cuBZxuWbS/s8VkSOReiZ5s59D+2uGPAA60t xNhN+e3teWie+SdbMyMbS72gug== X-Google-Smtp-Source: ADUXVKJaOKp3IWAbkoEqxzm4XxxENErMEwgrd4RNTSqmsPEwDfvHArFxqNTGPYGs/sZy1cKloP03Vg== X-Received: by 2002:a19:4dc5:: with SMTP id a188-v6mr3430705lfb.99.1527333781840; Sat, 26 May 2018 04:23:01 -0700 (PDT) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id h13-v6sm5949078lfg.20.2018.05.26.04.23.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 May 2018 04:23:00 -0700 (PDT) To: freebsd-current From: "Alex V. Petrov" Subject: r334236 error installkernel (i386) Openpgp: preference=signencrypt Autocrypt: addr=alexvpetrov@gmail.com; prefer-encrypt=mutual; keydata= xsFNBFr3oA0BEADMSXiVd/IwYhJPMQ6LXbZ7jTA/RXuzrGYaR++UENx5QJ6/HJ/3myTeMnZE nNa0Zme+oKw/9s5x7rBTP6mL5ta7VSYpnPX932mAjT9J4nS7iW/wWNBqcXn7wDCog2TV8Ww3 13SUP2YaKoJKJLxddiZD6AJrkafB9EE/AycMQ8XxMao1lVS+/KAo0yciOsnSlIJCWhF00b3j xDlHLvehrDa4S3EB13bF6uE0XU5nFfMNHtBav2mwD9t01hNioCNTV1hXwmsS/L1n5PR5FyJJ yYtjeohrAUiGKGJU9lJJ6tROBhzV/k3OsOGPyajFOVsW0vUueYfgw+IAPYdOZIAONgNdxkvs tRLQxYPCBMN1FvQ7GlIhq7ob+mxuA1imXx3xzlYy5tu4QzB383qZtLqQnZpysjYooAbHl+eN vB2ldvH9TZxm3fxxNL6zgYAXE/pNgFoqg/ILmhDwvvHzApHqVCKU3g6yii0KPxD7susaUWcL JYgrmt2BIE0RuiQRGWyS0L277D/YGmVnPNHxPi58DBs2iexDm7jw7PhlmfOw44N9w+O09D2S gqmBHySAtsq9Z5LoM81F+LrOoVmpYczZWErS917Gua1X7K3wrXoqQC8qcSiHZpEcBl/Uohii QWzjQJot5LT7rvfFHpnSOXAKgN7enVM7KxTJAYK1U343GGdepQARAQABzTZBbGV4VlBldHJv diAoZmlyc3QgZ2xvYmFsIGtleSkgPGFsZXh2cGV0cm92QGdtYWlsLmNvbT7CwY4EEwEIADgW IQRvKPTT2TJuh37ANx313p8aVpVkcAUCWvegDQIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIX gAAKCRD13p8aVpVkcLLeEADClYAElEInGGjtLfH4jdjvTDaQTsrwT5/1E5/h8yxI4yn7hCt1 Dh+iCSUNLdPO88nZV2jP8bMQXFBKSbC0nAJXd8O+8t9AfSWoUC6IMzncxKTK/jZuJTCToCUR XZ+47+uJaBp51rpw3pFX8UrFlYSF6Dz97dI2cGHfx3xAOnowKxyHfthxS8waKWgbMOceds78 BP2+Q0iLCpoC9rO4KDc+w+h8z21eHIE9VHadTHpnKVF82voPH8XWvznTOCpYrdBwUtIyD/DV XRb0xcFsOSkvmReYX7u4QuOPLSc86sEWh4hXTFLAOdfeTjrDTDmBcmFpltmW1j+5t4mI1dK8 gptREM8gMJVJw3jjcO6jADeXX9q5C8/lX0sEGz9uC4oU5nkOMyfzd9Anb+9bCs7pMxhqAKjA 8tqJPPkmJU8WzMCs+uudIiQ8W9qIETwUJWxizQ3kvlzLfWRz5n93Y9kzSmjw81aiIJK/HFY8 wsW5zNo6JBn57cMPx8nBC4E2zM09ffmqSpjDwXfvZF2IIR8L4VTiKi3ovwLglJP+Qbs5HXNn 6K40cPNqfnHzPLwXwd/co04B/VVr+cKZuE58kYGty9Xs9q/SEpObDnxnLxMNHUNJJuRgOiti TKDkteHuKm6NA8v05o3TDQ5HU9szEoE5uoi/3pQ1ktfA/K3LkDwbotXL+87BTQRa96ANARAA w5+/xcaCP6iwsi2CFQ4pAWksdmPBEHA2VPn1ym3C6opjbyWUp6sn25eTWppdhA9rUqbM/zV/ hAFRT67oZJKBYNRaMoDdO8BsVZsg/u76QF/GuhbUjIk0tFFdpddMXl0zKAJJMCfDRxURRWv7 NW6sY/EZ4Dal5s4xOT+UrWGag3qoaIRdzw5bJRP+o75L90cE8pd7+Pd9cVJOOtTAwx0E4bPq dPSa6CPDSvzd9D3mw37dPzXysyQkQTy0OM7255E2wjYz3RbJxB3utybPVN3XJBD5EyA8IYeS ic1/03UrkRNv4XrLnlg7xLv96ZeCrf/BDNQW23iVwbISUAk4TXL7xs2TGYOmowZ89mMEcbfW ChX3YLAuAeWzgpMcrDC00izOxG0spkkrHL7/i1iSu2MKhv5qMTVgchlSktdd+KTba5keleHv ULQ3feGUKf9eTkKgES6q4rKrae0tIwByTLhhDVbkXqR6v8zrpJSscrvJ3tMNgquJKy5ATIUB nvUE2hMkSwtnJ2vQ/Z0zGt6c5KxI57/hsb148tXp1v3gAq9d6i8c8ChxSR/kUlqAvzl2QGcn CFVN6nfOzyNfBPZ61abNzkzjzyhOK4Gq4gQvx4QXhDp3jEME7rPM0Tqf0venb1Dp7SIHwggV yJglGApwoUvD4kKNIC7KDr+s/UjbBp4ExFMAEQEAAcLBdgQYAQgAIBYhBG8o9NPZMm6HfsA3 HfXenxpWlWRwBQJa96ANAhsMAAoJEPXenxpWlWRwAaEQAKm0imG5Fm37JZi+5faXJv/ZLZGl r4TVg4u1kMktdTQRrTXa3Qs0i3wTtOZe1p3xCCzPx+97iYETHragDTdAFUO+v+Llin26L1Zl z4huyIqgGSuTuekQfn6eoMZbcF+wzah4j/mvXQVpJBF2qQi1YdHSapWDlweuiuk01y8C3eHv 3qfFB/OJwXhwj0HKhkGkB2dLXuLtIk4GCXh4/g22tWz/SB0gsSXU7WhJFb0CyxETGR9YKxM8 CNl5tVRLqsBC6yQLvcAJgJci73PfMiHKnjxrz//+0xQO1TPeruWsd8nLYvziT38CyX42Mbaj 01WpvB0qOeTGtwGFmyyrnE8fYpd3CE0uAl9BnHqafAabl9+09x3wf+lEkkO2bK59akZz3BPU 8Lz2BAgskyS81WZCthQYUrUozFEx/31x8JJ95EQFNW9t8HBa51r4QhedSNKxLbT3Sx8hH0iq Z8wYkGw0og9U1DqgFzxE2HSGZSDG3I1DrPDqhcM/6Y0V98wS+XreuS88DYYck37+L7bTGiyZ WYFNZk1ChcIBk8hgKn5nFOCWO2rX06RI9zorzSpEg6lB2STae1Up5oEj8QqfYmfO3cp2Qhvj F3c2/i8KpWkJQkAgNrv428FIlx9SiPu9gvNTTYuLIOdZLQvInTmKs2uCoB6JDAW75axDhBbR FvM3Vpv/ Message-ID: Date: Sat, 26 May 2018 18:22:59 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 26 May 2018 11:23:04 -0000 ===> usb/muge (install) install -T release -o root -g wheel -m 555 if_muge.ko /boot/kernel/ install: if_muge.ko: No such file or directory *** Error code 71 Stop. make[5]: stopped in /usr/src/sys/modules/usb/muge *** Error code 1 Stop. make[4]: stopped in /usr/src/sys/modules/usb *** Error code 1 Stop. make[3]: stopped in /usr/src/sys/modules *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/i386.i386/sys/ALEX *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src kernel: include GENERIC-NODEBUG ident ALEX -- ----- Alex. From owner-freebsd-current@freebsd.org Sat May 26 11:48: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 A1AE9F72888 for ; Sat, 26 May 2018 11:48:49 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 284086CC97 for ; Sat, 26 May 2018 11:48:49 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fMXgk-0006gX-Jy for freebsd-current@freebsd.org; Sat, 26 May 2018 13:48:46 +0200 Received: from [::1] (port=59688 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fMXgk-0002nz-G6 for freebsd-current@freebsd.org; Sat, 26 May 2018 13:48:46 +0200 Received: from mx10.freenet.de ([195.4.92.20]:53970) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fMXem-0000by-6y for freebsd-current@freebsd.org; Sat, 26 May 2018 13:46:44 +0200 Received: from p5b22a0c3.dip0.t-ipconnect.de ([91.34.160.195]:46651 helo=freebsd-t450.fritz.box) by mx10.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1fMXem-0004NY-0b for freebsd-current@freebsd.org; Sat, 26 May 2018 13:46:44 +0200 Date: Sat, 26 May 2018 13:46:42 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Fatal trap 12 Message-ID: <20180526114642.GA17171@freebsd-t450.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-score: 1.2 X-Spamreport: Action: no action Symbol: RCPT_COUNT_ONE(0.00) Symbol: MIME_GOOD(-0.10) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: RCVD_COUNT_ONE(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: NEURAL_SPAM(1.34) Symbol: ASN(0.00) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: FREEMAIL_ENVFROM(0.00) Symbol: RCVD_TLS_ALL(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: FREEMAIL_FROM(0.00) Symbol: TO_DN_NONE(0.00) Message-ID: 20180526114642.GA17171@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 91.34.160.195!46651 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 11:48:49 -0000 Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing several "Fatal traps 12". Before the update i did not have any of those. In all cases the traps occured some time after resume. Below there is some output found in /var/crash/core.txt __curthread () at ./machine/pcpu.h:231 231 ./machine/pcpu.h: No such file or directory. (kgdb) #0 __curthread () at ./machine/pcpu.h:231 #1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80b9a6f0 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:446 #3 0xffffffff80b9ab83 in vpanic (fmt=, ap=0xfffffe0056507e50) at /usr/src/sys/kern/kern_shutdown.c:863 #4 0xffffffff80b9a973 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:790 #5 0xffffffff80ba5c3b in kdb_switch () at /usr/src/sys/kern/kern_synch.c:377 #6 0xffffffff80ba5bb9 in mi_switch (flags=, newtd=0x0) at /usr/src/sys/kern/kern_synch.c:406 #7 0xffffffff80bf3f5f in sleepq_timedwait (wchan=, pri=) at /usr/src/sys/kern/subr_sleepqueue.c:727 #8 0xffffffff833c7bed in linux_add_to_sleepqueue (wchan=0xfffff8000bf6ad80, task=0xfffff8000bf6ad80, wmesg=, timeout=50, state=) at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:70 #9 0xffffffff833c7a58 in linux_wait_event_common (wqh=, wq=, timeout=50, state=2, lock=0x0) at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:270 #10 0xffffffff83458de6 in ?? () #11 0x000000061d026200 in ?? () #12 0x0000000600000000 in ?? () #13 0xfffff8000bf6ad80 in ?? () #14 0xffffffff833c7540 in ?? () at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:167 from /boot/kernel/linuxkpi.ko #15 0xfffff80007804828 in ?? () #16 0xfffff80007804828 in ?? () #17 0x0000000000000030 in ?? () #18 0x0000000000000000 in ?? () (kgdb) Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x3 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80cc60cb stack pointer = 0x28:0xfffffe0056508560 frame pointer = 0x28:0xfffffe0056508760 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 = 10218 (nextcloud) -- Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x300000011 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80cc60cb stack pointer = 0x28:0xfffffe005e4d1560 frame pointer = 0x28:0xfffffe005e4d1760 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 = 17918 (DNS Resolver #16) -- Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x3 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80cc60cb stack pointer = 0x28:0xfffffe0056508560 frame pointer = 0x28:0xfffffe0056508760 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 = 10218 (nextcloud) If there is any other information i can provide for solving this, please let me know. -- Manuel From owner-freebsd-current@freebsd.org Sat May 26 12:32: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 F2450F74669 for ; Sat, 26 May 2018 12:32:15 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 87DF96E2F9 for ; Sat, 26 May 2018 12:32:15 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x241.google.com with SMTP id 144-v6so9916552iti.5 for ; Sat, 26 May 2018 05:32: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=UdVLjeulb7CirdacNLEqvigJ3zQK2gZQMYuCAXkWpiQ=; b=vWoEMqRPrYh4giQk5cBTEk9OzXU7DJHF//y3bi78IS5c+RchhK+11dY9VQCvAAIwvu GbCx/WbbR70REjJdrCanbXP6jdDPNEU3dE5dVQ+/DocAHukudrEBGJBEHTzS+G9f1c1q /8/6LIkDt3QAI8us5/baCkYOiNvVp9toaZGoP4ucuQivvA/I/VqugccPVa19lTRRN8Pq MgwrWovFGcx07AWwGTEcN9/2FyUKmLXBZF7jIyS7RByCDA5AaAh6z58SCyw23oCeHkL6 cp9Uu4Rppp0Bai2AAuin3x/+i974htOvNs0ECHZHBQNKrazmnnUF1Ns01HYLGtuf4P+u /hEQ== 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=UdVLjeulb7CirdacNLEqvigJ3zQK2gZQMYuCAXkWpiQ=; b=nEtDmXhSo3frdxbEXNfG8ZfGz19noCeomN5atNWAmTn5LC+iW9qZjdY3luhAliSWp1 k6wSE+Rsky5D5JUujpTXsV6iTRLT6OPBIlSdCcR0cqhMKudmYOzRhObisDR4sL1yVKh1 vL7b0CwTz1jpseboxkaJkd6/p81pSnbKMPHbKMV4jS9vh1TbXPv/BABQI2ve/M0OxdaG hCfvdnF7uNgTS/MW8l+Cr3TOVrtmboIDx234yyoRYvU0YBuZC9aBSojHRiuQ+GdW7heM lMZB8T7k1l9JN6AN/9LHh06Vowa9rR0qLlmqHX/nIDGWn8Ycp3Qslqb4HswZSebbI43k 8ZzA== X-Gm-Message-State: ALKqPwdFiDZok9iK7Gh036QGKl7tP7LOnOa4rMG0n44/g/VzFeBk3GjE cMXKuS5wSYKWcMi7YJHghjtIzjuFKE1aUKXuEmA= X-Google-Smtp-Source: ADUXVKLJ+Xn+Cievyz96gzOoCwfu6XHp/7m1GPb3Jb8yVjF6VhO4spqyXRh1qrFqR18aiYUZy2eaH2z53yZl7H4cl+o= X-Received: by 2002:a24:d886:: with SMTP id b128-v6mr5462007itg.39.1527337934926; Sat, 26 May 2018 05:32:14 -0700 (PDT) MIME-Version: 1.0 References: <20180526114642.GA17171@freebsd-t450.fritz.box> In-Reply-To: <20180526114642.GA17171@freebsd-t450.fritz.box> From: blubee blubeeme Date: Sat, 26 May 2018 20:32:17 +0800 Message-ID: Subject: Re: Fatal trap 12 To: =?UTF-8?Q?Manuel_St=C3=BChn?= Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 12:32:16 -0000 On Sat, May 26, 2018, 19:52 Manuel St=C3=BChn wr= ote: > Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing > several "Fatal traps 12". Before the update i did not have any of those. > In all cases the traps occured some time after resume. > > Below there is some output found in /var/crash/core.txt > > __curthread () at ./machine/pcpu.h:231 > 231 ./machine/pcpu.h: No such file or directory. > (kgdb) #0 __curthread () at ./machine/pcpu.h:231 > #1 doadump (textdump=3D1) at /usr/src/sys/kern/kern_shutdown.c:366 > #2 0xffffffff80b9a6f0 in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:446 > #3 0xffffffff80b9ab83 in vpanic (fmt=3D, > ap=3D0xfffffe0056507e50) > at /usr/src/sys/kern/kern_shutdown.c:863 > #4 0xffffffff80b9a973 in panic (fmt=3D) > at /usr/src/sys/kern/kern_shutdown.c:790 > #5 0xffffffff80ba5c3b in kdb_switch () at > /usr/src/sys/kern/kern_synch.c:377 > #6 0xffffffff80ba5bb9 in mi_switch (flags=3D, newtd=3D0x0) > at /usr/src/sys/kern/kern_synch.c:406 > #7 0xffffffff80bf3f5f in sleepq_timedwait (wchan=3D, > pri=3D) at /usr/src/sys/kern/subr_sleepqueue.c:727 > #8 0xffffffff833c7bed in linux_add_to_sleepqueue > (wchan=3D0xfffff8000bf6ad80, task=3D0xfffff8000bf6ad80, wmesg=3D out>, timeout=3D50, state=3D) > at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:70 > #9 0xffffffff833c7a58 in linux_wait_event_common (wqh=3D, > wq=3D, timeout=3D50, state=3D2, lock=3D0x0) > at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:270 > #10 0xffffffff83458de6 in ?? () > #11 0x000000061d026200 in ?? () > #12 0x0000000600000000 in ?? () > #13 0xfffff8000bf6ad80 in ?? () > #14 0xffffffff833c7540 in ?? () > at /usr/src/sys/compat/linuxkpi/common/src/linux_schedule.c:167 > from /boot/kernel/linuxkpi.ko > #15 0xfffff80007804828 in ?? () > #16 0xfffff80007804828 in ?? () > #17 0x0000000000000030 in ?? () > #18 0x0000000000000000 in ?? () > (kgdb) > > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 3; apic id =3D 03 > fault virtual address =3D 0x3 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x20:0xffffffff80cc60cb > stack pointer =3D 0x28:0xfffffe0056508560 > frame pointer =3D 0x28:0xfffffe0056508760 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 10218 (nextcloud) > -- > Fatal trap 12: page fault while in kernel mode > cpuid =3D 1; apic id =3D 01 > fault virtual address =3D 0x300000011 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x20:0xffffffff80cc60cb > stack pointer =3D 0x28:0xfffffe005e4d1560 > frame pointer =3D 0x28:0xfffffe005e4d1760 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 17918 (DNS Resolver #16) > -- > Fatal trap 12: page fault while in kernel mode > cpuid =3D 3; apic id =3D 03 > fault virtual address =3D 0x3 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x20:0xffffffff80cc60cb > stack pointer =3D 0x28:0xfffffe0056508560 > frame pointer =3D 0x28:0xfffffe0056508760 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 10218 (nextcloud) > > If there is any other information i can provide for solving this, please > let me know. > > -- > Manuel > _______________________________________________ > 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= " > Aren't you the guy using the drm-kmod if yes, your custom complied kernel and not the default kernel causing those issues. Best, Owen > From owner-freebsd-current@freebsd.org Sat May 26 13:31: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 68432F75FCF; Sat, 26 May 2018 13:31:33 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03F686FCE6; Sat, 26 May 2018 13:31:32 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-io0-x229.google.com with SMTP id g14-v6so9410230ioc.7; Sat, 26 May 2018 06:31:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=w1J6Kuq406sC9XFhEHyiDYppd10F7EiQv2ge4NcSzqI=; b=N5/FMgy+LNnYS8tZGbGXty8AGcQ1xioJX3CaLcYqA55Hw7DAXhd9togiy3tSSgOceD TZtv6xwJ09+AkAGciwqAJYkx/QxMc4YUbm+LpUR6K2hSoKFJwKNxavk0/478HwvRqdHL 00gxEv8hANELIu/gWQLzcDJXwhJrbKbMIPS41Ih02lJG8dm5xjIkosY2HPYDj7qdvMAm +psewwqvpnGVf8mjaLHDXfUxm0U4/bDNSI8KfWsolnj2RM4lWxlvhRFDaQ6HCSk9Rc6m zMNGYfEGqIqz4IfSitJQGGpcC+wX19Mj0a80Gq1Y02yyvgMwZhFx+59YtelbKmXbQQCR AdHA== 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=w1J6Kuq406sC9XFhEHyiDYppd10F7EiQv2ge4NcSzqI=; b=ZLWsyr7esXcQPXeyqtp8Fsl42e2ErRah5FmRJvK2QYKTcAXMnKf0eyp6M67wWO/1ri 1AOhQGWm825spqxE4c+MvdSvkRxam3H41UXwmGLKYYwAZe3DjfY2R69glUBRcHS4zz3O +X6QWxHzuz3G4tZaGQfwDITp3q3OXmmkDKz8PCB2Da6NoWHlQjlRidl6PFfHcWKZrNw+ miGrfqfitPnHaLII7FlsXqxGx16YR40xowcK22ASfy5QBSU0HWx3uP/ZWkHToTcCvuxD QsXvB3F+VE+87f6vxYErU5xSyJgbY++8zM4NFs6lA+fUXhjpYHKUWw8eodFciDIldbTF PIqg== X-Gm-Message-State: ALKqPwes3o/LPwvO6lPxDRaq5PjFSOnOAGZSaKpZ2lKmGr6OohJ9K9gF VWmLLBwT48N5d4X2va84P4kzs+ABdqRtBabHcOQ= X-Google-Smtp-Source: ADUXVKKh+M9wNDYEENEm9Aui4iC4JNEE2TKv8swtcWs8FwhkWTYrvQC98zzsDXodADZgdyJiYOG+1kvo/ODKXyibgUs= X-Received: by 2002:a6b:d90e:: with SMTP id r14-v6mr5760213ioc.240.1527341492357; Sat, 26 May 2018 06:31:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:c68a:0:0:0:0:0 with HTTP; Sat, 26 May 2018 06:31:31 -0700 (PDT) From: blubee blubeeme Date: Sat, 26 May 2018 21:31:31 +0800 Message-ID: Subject: OSS loopback device To: FreeBSD , freebsd-multimedia@freebsd.org, FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 13:31:33 -0000 Cross post; FreeBSD-[questions | current | ultimedia] Where's the midi loopback device in the FreeBSD OSS implementation? Best, Owen From owner-freebsd-current@freebsd.org Sat May 26 14:58: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 1FAA9F78263 for ; Sat, 26 May 2018 14:58:36 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADC6B72B64 for ; Sat, 26 May 2018 14:58:35 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.140] (helo=mjail0.freenet.de) by mout1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fMaeP-0006Ar-E0 for freebsd-current@freebsd.org; Sat, 26 May 2018 16:58:33 +0200 Received: from [::1] (port=32858 helo=mjail0.freenet.de) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fMaeP-0005TP-85 for freebsd-current@freebsd.org; Sat, 26 May 2018 16:58:33 +0200 Received: from mx7.freenet.de ([195.4.92.17]:50488) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fMacE-00039P-OX for freebsd-current@freebsd.org; Sat, 26 May 2018 16:56:18 +0200 Received: from p5b22a0c3.dip0.t-ipconnect.de ([91.34.160.195]:17582 helo=freebsd-t450.fritz.box) by mx7.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1fMacE-0006dl-Jo for freebsd-current@freebsd.org; Sat, 26 May 2018 16:56:18 +0200 Date: Sat, 26 May 2018 16:56:17 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Re: Fatal trap 12 Message-ID: <20180526145617.GA93980@freebsd-t450.fritz.box> References: <20180526114642.GA17171@freebsd-t450.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-score: -3.1 X-Spamreport: Action: no action Symbol: RCVD_COUNT_ONE(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: MIME_GOOD(-0.10) Symbol: RCVD_TLS_ALL(0.00) Symbol: BAYES_HAM(-0.00) Symbol: FREEMAIL_ENVFROM(0.00) Symbol: TO_DN_NONE(0.00) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: ASN(0.00) Symbol: RCPT_COUNT_ONE(0.00) Symbol: FREEMAIL_FROM(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: NEURAL_HAM(-3.00) Message-ID: 20180526145617.GA93980@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 91.34.160.195!17582 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 14:58:36 -0000 On Sat, May 26, 2018 at 08:32:17PM +0800, blubee blubeeme wrote: > > Aren't you the guy using the drm-kmod if yes, your custom complied kernel > and not the default kernel causing those issues. > Best, > Owen I'm indeed using graphics/drm-stable-kmod, but i do not use a custom kernel: uname -rsmv FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #8 r334167: Thu May 24 20:06:20 CEST 2018 root@valinor:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 The drm-stable-kmod was installed from ports with the corresponding src-tree. -- Manuel From owner-freebsd-current@freebsd.org Sat May 26 19:54: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 E9CACEF46D3 for ; Sat, 26 May 2018 19:54:38 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 773507F16E for ; Sat, 26 May 2018 19:54:37 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Sat, 26 May 2018 21:54:10 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1527364469; bh=w+DFwPyoPCBM0By5Jbj14WN/ZZ1nOaoAAWnWZrmnpfw=; h=Date:From:To:Subject:References:In-Reply-To; b=Q4njxMnzVVpO7Lethv76JohUXQoxm5ekd2l7eZv7nwXdQDA0v2dHIcfIgcy6POwrH EwS+X3ESp9du6Avp+EpxPr9w2DfzzhhViqtDVxmncd8mUYJ+Z5iZXSRfo512M0Ys2R RfXrtvtkqUQUZ9cVGlmc8UR7nPe0D0KhZxjjaJm6V1yki0YOeBOFZA1W5x3cAPdZgY ssOd7enw6Vfkq31f76Qzhni1suR27/nCfBnrMPLMxEymtIcCIXO/ubAoEzdmYXkQqt 21Wy0gN0PDGV0wTxgWJEdz40veCoSBTI5Wo3smYxW+wEyh/5ijJJs/3TWTbd0M68/N VffZqdOrD/+dA== Message-ID: <20180526215410.Horde.TLpIgePvctlYUqw9QcqlgGR@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_qYusH3OX4idVmNdR4PqZf1V"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 26 May 2018 19:54:39 -0000 This message is in MIME format and has been PGP signed. --=_qYusH3OX4idVmNdR4PqZf1V Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Steve Wills (from Tue, 22 May 2018=20=20 08:17:00=20-0400): > I may be seeing similar issues. Have you tried leaving top -SHa=20=20 >=20running and seeing what threads are using CPU when it hangs? I did=20= =20 >=20and saw pid 17 [zfskern{txg_thread_enter}] using lots of CPU but no=20= =20 >=20disk activity happening. Do you see similar? For me it is a different zfs process/kthread, l2arc_feed_thread.=20=20 Please=20note that there is still 31 GB free, so it doesn't look lie=20=20 resource=20exhaustion. What I consider strange is the swap usage. I=20=20 watched=20the system and it started to use swap while there were >30 GB=20= =20 listed=20as free (in/out rates visible from time to time, and plenty of=20= =20 RAM=20free... ???). last pid: 93392; load averages: 0.16, 0.44, 1.03=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 =20 up 1+15:36:34 22:35:45 1509 processes:17 running, 1392 sleeping, 3 zombie, 97 waiting CPU: 0.1% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.9% idle Mem: 597M Active, 1849M Inact, 6736K Laundry, 25G Wired, 31G Free ARC: 20G Total, 9028M MFU, 6646M MRU, 2162M Anon, 337M Header, 1935M Other 14G Compressed, 21G Uncompressed, 1.53:1 Ratio Swap: 4096M Total, 1640M Used, 2455M Free, 40% Inuse PID JID USERNAME PRI NICE SIZE RES STATE C TIME=20=20= =20=20 =20 WCPU COMMAND 10 0 root 155 ki31 0K 256K CPU1 1 35.4H=20=20 100.00%=20[idle{idle: cpu1}] 10 0 root 155 ki31 0K 256K CPU11 11 35.2H=20=20 100.00%=20[idle{idle: cpu11}] 10 0 root 155 ki31 0K 256K CPU3 3 35.2H=20=20 100.00%=20[idle{idle: cpu3}] 10 0 root 155 ki31 0K 256K CPU15 15 35.1H=20=20 100.00%=20[idle{idle: cpu15}] 10 0 root 155 ki31 0K 256K RUN 9 35.1H=20=20 100.00%=20[idle{idle: cpu9}] 10 0 root 155 ki31 0K 256K CPU5 5 35.0H=20=20 100.00%=20[idle{idle: cpu5}] 10 0 root 155 ki31 0K 256K CPU14 14 35.0H=20=20 100.00%=20[idle{idle: cpu14}] 10 0 root 155 ki31 0K 256K CPU0 0 35.8H=20=20= =20 99.12%=20[idle{idle: cpu0}] 10 0 root 155 ki31 0K 256K CPU6 6 35.3H=20=20= =20 98.79%=20[idle{idle: cpu6}] 10 0 root 155 ki31 0K 256K CPU8 8 35.1H=20=20= =20 98.31%=20[idle{idle: cpu8}] 10 0 root 155 ki31 0K 256K CPU12 12 35.0H=20=20= =20 97.24%=20[idle{idle: cpu12}] 10 0 root 155 ki31 0K 256K CPU4 4 35.4H=20=20= =20 96.71%=20[idle{idle: cpu4}] 10 0 root 155 ki31 0K 256K CPU10 10 35.0H=20=20= =20 92.37%=20[idle{idle: cpu10}] 10 0 root 155 ki31 0K 256K CPU7 7 35.2H=20=20= =20 92.20%=20[idle{idle: cpu7}] 10 0 root 155 ki31 0K 256K CPU13 13 35.1H=20=20= =20 91.90%=20[idle{idle: cpu13}] 10 0 root 155 ki31 0K 256K CPU2 2 35.4H=20=20= =20 90.97%=20[idle{idle: cpu2}] 11 0 root -60 - 0K 816K WAIT 0 15:08=20=20= =20=20 0.82%=20[intr{swi4: clock (0)}] 31 0 root -16 - 0K 80K pwait 0 44:54=20=20= =20=20 0.60%=20[pagedaemon{dom0}] 45453 0 root 20 0 16932K 7056K CPU9 9 4:12=20=20= =20=20 0.24%=20top -SHaj 24 0 root -8 - 0K 256K l2arc_ 0 4:12=20=20= =20=20 0.21%=20[zfskern{l2arc_feed_thread}] 2375 0 root 20 0 16872K 6868K select 11 3:52=20=20= =20=20 0.20%=20top -SHua 7007 12 235 20 0 18017M 881M uwait 12 0:00=20=20= =20=20 0.19%=20[java{ESH-thingHandler-35}] 32 0 root -16 - 0K 16K psleep 15 5:03=20=20= =20=20 0.11%=20[vmdaemon] 41037 0 netchild 27 0 18036K 9136K select 4 2:20=20=20= =20=20 0.09%=20tmux: server (/tmp/tmux-1001/default) (t 36 0 root -16 - 0K 16K - 6 2:02=20=20= =20=20 0.09%=20[racctd] 7007 12 235 20 0 18017M 881M uwait 9 1:24=20=20= =20=20 0.07%=20[java{java}] 4746 0 root 20 0 13020K 3792K nanslp 8 0:52=20=20= =20=20 0.05%=20zpool iostat space 1 0 0 root -76 - 0K 10304K - 4 0:16=20=20= =20=20 0.05%=20[kernel{if_io_tqg_4}] 5550 8 933 20 0 2448M 607M uwait 8 0:41=20=20= =20=20 0.03%=20[java{java}] 5550 8 933 20 0 2448M 607M uwait 13 0:03=20=20= =20=20 0.03%=20[java{Timer-1}] 7007 12 235 20 0 18017M 881M uwait 0 0:39=20=20= =20=20 0.02%=20[java{java}] 5655 8 560 20 0 21524K 4840K select 6 0:21=20=20= =20=20 0.02%=20/usr/local/sbin/hald{hald} 30 0 root -16 - 0K 16K - 4 0:25=20=20= =20=20 0.01%=20[rand_harvestq] 1259 0 root 20 0 18780K 18860K select 14 0:19=20=20= =20=20 0.01%=20/usr/sbin/ntpd -c /etc/ntp.conf -p /var/ 0 0 root -76 - 0K 10304K - 12 0:19=20=20= =20=20 0.01%=20[kernel{if_config_tqg_0}] 31 0 root -16 - 0K 80K psleep 0 0:38=20=20= =20=20 0.01%=20[pagedaemon{dom1}] 0 0 root -76 - 0K 10304K - 5 0:04=20=20= =20=20 0.01%=20[kernel{if_io_tqg_5}] 7007 12 235 20 0 18017M 881M uwait 1 0:16=20=20= =20=20 0.01%=20[java{Karaf Lock Monitor }] 12622 2 88 20 0 1963M 247M uwait 7 0:13=20=20= =20=20 0.01%=20[mysqld{mysqld}] 27043 0 netchild 20 0 18964K 9124K select 6 0:01=20=20= =20=20 0.01%=20sshd: netchild@pts/0 (sshd) 7007 12 235 20 0 18017M 881M uwait 8 0:10=20=20= =20=20 0.01%=20[java{openHAB-job-schedul}] 7007 12 235 20 0 18017M 881M uwait 6 0:10=20=20= =20=20 0.01%=20[java{openHAB-job-schedul}] > On 05/22/18 04:17, Alexander Leidinger wrote: >> Hi, >> >> does someone else experience deadlocks / hangs in ZFS? >> >> What I see is that if on a 2 socket / 4 cores -> 16 threads system=20=20 >>=20I do a lot in parallel (e.g. updating ports in several jails), then=20= =20 >>=20the system may get into a state were I can login, but any exit=20=20 >>=20(e.g. from top) or logout of shell blocks somewhere. Sometimes it=20= =20 >>=20helps to CTRL-C all updates to get the system into a good shape=20=20 >>=20again, but most of the times it doesn't. >> >> On another system at the same rev (333966) with a lot less CPUs=20=20 >>=20(and AMD instead of Intel), I don't see such a behavior. >> >> Bye, >> Alexander. >> > _______________________________________________ > 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 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_qYusH3OX4idVmNdR4PqZf1V Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbCbtiAAoJEKrxQhqFIICEHsMP/3tDHv4Om5O5TalIvB2sItP3 G7xt1pHfOgCEnMwhbnXkKu5NlcN8FH0k8tdFHkJqE8w9j8GyrXkS6n69SFaaohCF wryx9ASeTFVvShPKCM84wy/Xeke25E2AHNf28m7fkBM9GDOOSoFnL+vkvPJ3Wv7W +oYVSwahuRC5yUY0mfQJdqwyfyA57UJBpa5tOCfoinNm+jDtxV9batg5a9Ph81Qw XaGpZCQ/SY0RTrSospQrzHa6Y6dqPJffsQrfntYS+iaZRs/0my9OOaTbrJ4K0FVw IoOoy1wS4Bp6Sikf5j5TEnpaTsdfX7UK2TODpY4oz6vw/iREzlxVhCNgvn4xAqhG N7Ubp/ZNxwLrWgBvEc+aXRF9HxapCLC0dyLqzzGio3z29Zb4XGOFCpcENsSbJh5k JPsZqua+KH5j7poZ2f3wC0+OS7dqBGhb9ot7eCXE7cvUbGpwAXSUaOC3DmE7PLto zgNIx1u8n6OvPPiayyw9AWNE8fpr5A82G8np7ThIKeMqX+TKFvx5ugbJEiu2X7rT 25cAQREa3+rZNZLhpV2HHggXCUK/Qo2NXIEeVNkOCzyy8Ev/3VRbpLoU8btpvMWr L8bG7cYGrFk+Dt+DEjr8j3fVImjgd5yFSrL6Vlcfm7lBpnVRA+yNXNWHzHXnMEt1 Wk8vLWkIqgsQRmJTv8xI =u3NS -----END PGP SIGNATURE----- --=_qYusH3OX4idVmNdR4PqZf1V--