From owner-freebsd-stable@freebsd.org Sun Mar 26 08:31:04 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A8EDD1E5FC for ; Sun, 26 Mar 2017 08:31:04 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 105A1153D for ; Sun, 26 Mar 2017 08:31:04 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0FC20D1E5FA; Sun, 26 Mar 2017 08:31:04 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F6A4D1E5F9 for ; Sun, 26 Mar 2017 08:31:04 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8408A153A for ; Sun, 26 Mar 2017 08:31:03 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id v2Q8Uleb056831 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 26 Mar 2017 19:30:53 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id v2Q8UfnS046887 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 26 Mar 2017 19:30:41 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id v2Q8Ue8g046886 for stable@freebsd.org; Sun, 26 Mar 2017 19:30:40 +1100 (AEDT) (envelope-from peter) Date: Sun, 26 Mar 2017 19:30:40 +1100 From: Peter Jeremy To: stable@freebsd.org Subject: Re: Unable to boot 11.0-release on Unisurf Notebook Message-ID: <20170326083040.GA98076@server.rulingia.com> References: <20170324231957.GA94855@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20170324231957.GA94855@server.rulingia.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 08:31:04 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2017-Mar-25 10:19:57 +1100, Peter Jeremy wrote: >I've just bought a Unisurf Notebook[1] and am trying to boot it from a >FreeBSD-11.0-RELEASE-amd64-memstick.img. The boot starts OK but hangs >whilst probing devices. With safe and verbose enabled, it hangs after >complaining about ppc0 (see https://goo.gl/photos/3e7tLWygjsQ6ayBT9). >At this point neither Ctrl-Alt-Del nor Ctrl-Alt-Esc have any effect and >the only option is to hold the power button down until it powers off. For the record, I have both good and bad news: The good news is that setting hint.uart.1.disabled=3D"1" let it boot. The bad news is that FreeBSD-11 (I didn't try head) can't see the eMMC flash. The worse news is that the WiFi adapter is attached to the SDIO. I've given up and returned it. If anyone's interested, I've posted dmesg and similar information from both FreeBSD-11 and xubuntu 16.04.2 at https://www.rulingia.com/~peter/unisurf/ --=20 Peter Jeremy --17pEHd4RhPHOinZp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY13wwXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0ISkP/2RSNrddxUBuEirecsfr4mb2 VhvOorfL4dLx76PU+VXwYTem/VSj3nY/Yj4FcnRs97O+w0/NF8i50JvYIO7Tslw7 LUAZcMD99jT/RXuM5X0DwtAZEZA9AiETH1F48m1GX6sbu0+JqrPaOBQkbYP76hV4 wvnCWF7Wfu/RZyjNHxKqxDdyFlCwR954aPLgkcO2peRWsrL96HF7R4atnmT+3B1j 6+pFn/KBEh4IfsUj+OtYF1qvcjjYxBNenWHWicoj+4DFmodq4pxNpoAclj6O13H0 TZqjSXAhcyljCodYTUCzin9aCZdQxgrvZSrbsvzIjOfRNY16ru9R6/EsleNTdAwu AAw7i7T3kcgCXSCS6hxVUuPcwwc+qhCtYZHcTcu4VIsh6aayGQEnDmAdmDFSD/mk 7daYvby0ow1W69IVQDJYNdr2HSJeg0UFW8Gw38op1dfIH/SxwSaMZJrNRQ1S8z7R oqs5CcY1hJxEXi8yqqq5+Jqo9Nyx3U8aZxoFrapDCsD4u1GSpnw2TkfZZyjkzsXO bty9JMZA/eKMnbfH64nU6bZGPwJRl4nI+jPKpNRXExoUuh7dO9Ube+ee/2K02mmI IIH8/Gpf9aKMZEA1D5VPunzpA59XWuy9w84lwfHewsF9fG2jL08WzzutUO2aa/Rj yZcbRd0voZS0mhhAGPmH =4Kc/ -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@freebsd.org Sun Mar 26 13:39:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32A7ED1D17D for ; Sun, 26 Mar 2017 13:39:48 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) 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 217931D1C for ; Sun, 26 Mar 2017 13:39:48 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: by mailman.ysv.freebsd.org (Postfix) id 1D897D1D17B; Sun, 26 Mar 2017 13:39:48 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D364D1D17A for ; Sun, 26 Mar 2017 13:39:48 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (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 90A901D1B for ; Sun, 26 Mar 2017 13:39:45 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v2QDdWCB059914; Mon, 27 Mar 2017 00:39:32 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 27 Mar 2017 00:39:32 +1100 (EST) From: Ian Smith To: Peter Jeremy cc: stable@freebsd.org Subject: Re: Unable to boot 11.0-release on Unisurf Notebook In-Reply-To: <20170326083040.GA98076@server.rulingia.com> Message-ID: <20170327001246.A42565@sola.nimnet.asn.au> References: <20170324231957.GA94855@server.rulingia.com> <20170326083040.GA98076@server.rulingia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 13:39:48 -0000 On Sun, 26 Mar 2017 19:30:40 +1100, Peter Jeremy wrote: > On 2017-Mar-25 10:19:57 +1100, Peter Jeremy wrote: > >I've just bought a Unisurf Notebook[1] and am trying to boot it from a > >FreeBSD-11.0-RELEASE-amd64-memstick.img. The boot starts OK but hangs > >whilst probing devices. With safe and verbose enabled, it hangs after > >complaining about ppc0 (see https://goo.gl/photos/3e7tLWygjsQ6ayBT9). > >At this point neither Ctrl-Alt-Del nor Ctrl-Alt-Esc have any effect and > >the only option is to hold the power button down until it powers off. I did have a look at [1] http://unisurf.com.au/unisurf-14-Notebook.html and wondered who really made them. INSYDE Corp., I see. Cutely, their ACPI tables are mostly listed as 'INTEL INSYDE' :) and it's called a 'CherryTrail'; all news to me. Looks pretty well locked in to Windows. > For the record, I have both good and bad news: > The good news is that setting hint.uart.1.disabled="1" let it boot. > The bad news is that FreeBSD-11 (I didn't try head) can't see the eMMC > flash. The worse news is that the WiFi adapter is attached to the SDIO. > I've given up and returned it. I wondered what possessed you to buy it, going on specs and 'manual'? and what the '32GB Storage' might denote. Good thing you could return it. For reference, just how cheap are they in AU? > If anyone's interested, I've posted dmesg and similar information from both > FreeBSD-11 and xubuntu 16.04.2 at https://www.rulingia.com/~peter/unisurf/ I noticed: CPUs max speed/power 1.44GHz/2W, min 480MHz/600mW so it's low powered enough. but no Li-ion capacity info and it doesn't support S3 suspend! No thermal zone passive control, still, at 8W for 4 CPUs flat out that might be ok. You'd likely want to force HPET event timer (to get C3 idle state), and get that MMC to show up for it to be any use. cheers, Ian From owner-freebsd-stable@freebsd.org Sun Mar 26 16:22:40 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CFAAD1E0F6 for ; Sun, 26 Mar 2017 16:22:40 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id EB7C810B3 for ; Sun, 26 Mar 2017 16:22:39 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EAEB8D1E0F5; Sun, 26 Mar 2017 16:22:39 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA8D4D1E0F2 for ; Sun, 26 Mar 2017 16:22:39 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 CEDDA10B0 for ; Sun, 26 Mar 2017 16:22:39 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 63dcbe35-1240-11e7-8c45-c35e37f62db1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 63dcbe35-1240-11e7-8c45-c35e37f62db1; Sun, 26 Mar 2017 16:22:22 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v2QGMUSQ001373; Sun, 26 Mar 2017 10:22:31 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1490545350.58015.133.camel@freebsd.org> Subject: Re: Unable to boot 11.0-release on Unisurf Notebook From: Ian Lepore To: Peter Jeremy , stable@freebsd.org Date: Sun, 26 Mar 2017 10:22:30 -0600 In-Reply-To: <20170326083040.GA98076@server.rulingia.com> References: <20170324231957.GA94855@server.rulingia.com> <20170326083040.GA98076@server.rulingia.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 16:22:40 -0000 On Sun, 2017-03-26 at 19:30 +1100, Peter Jeremy wrote: > On 2017-Mar-25 10:19:57 +1100, Peter Jeremy > wrote: > > > > I've just bought a Unisurf Notebook[1] and am trying to boot it > > from a > > FreeBSD-11.0-RELEASE-amd64-memstick.img.  The boot starts OK but > > hangs > > whilst probing devices.  With safe and verbose enabled, it hangs > > after > > complaining about ppc0 (see https://goo.gl/photos/3e7tLWygjsQ6ayBT9 > > ). > > At this point neither Ctrl-Alt-Del nor Ctrl-Alt-Esc have any effect > > and > > the only option is to hold the power button down until it powers > > off. > For the record, I have both good and bad news: > The good news is that setting hint.uart.1.disabled="1" let it boot. > The bad news is that FreeBSD-11 (I didn't try head) can't see the > eMMC > flash.  The worse news is that the WiFi adapter is attached to the > SDIO. > I've given up and returned it. > > If anyone's interested, I've posted dmesg and similar information > from both > FreeBSD-11 and xubuntu 16.04.2 at https://www.rulingia.com/~peter/uni > surf/ > Marius is currently updating our mmc/sd stack for better support of modern emmc, there's a good chance that support will hit 11-stable in a while. There is also work in progress on sdio, but that's still focused on the lower level support.  Once that infrastructure is in place, another round of work will be needed to create the wifi drivers. -- Ian From owner-freebsd-stable@freebsd.org Sun Mar 26 20:13:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F6E0D1EE3F for ; Sun, 26 Mar 2017 20:13:25 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 74CA1116E for ; Sun, 26 Mar 2017 20:13:25 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7411FD1EE3E; Sun, 26 Mar 2017 20:13:25 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73B88D1EE3C for ; Sun, 26 Mar 2017 20:13:25 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2162F116D for ; Sun, 26 Mar 2017 20:13:24 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id v2QKDFOR060907 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 27 Mar 2017 07:13:21 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id v2QKD9pc093567 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Mar 2017 07:13:09 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id v2QKD9hC093566; Mon, 27 Mar 2017 07:13:09 +1100 (AEDT) (envelope-from peter) Date: Mon, 27 Mar 2017 07:13:09 +1100 From: Peter Jeremy To: Ian Smith Cc: stable@freebsd.org Subject: Re: Unable to boot 11.0-release on Unisurf Notebook Message-ID: <20170326201309.GB98076@server.rulingia.com> References: <20170324231957.GA94855@server.rulingia.com> <20170326083040.GA98076@server.rulingia.com> <20170327001246.A42565@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <20170327001246.A42565@sola.nimnet.asn.au> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Mar 2017 20:13:25 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2017-Mar-27 00:39:32 +1100, Ian Smith wrote: >I did have a look at [1] http://unisurf.com.au/unisurf-14-Notebook.html=20 >and wondered who really made them. INSYDE Corp., I see. Cutely, their=20 >ACPI tables are mostly listed as 'INTEL INSYDE' :) and it's called a=20 >'CherryTrail'; all news to me. Looks pretty well locked in to Windows. Well, ark.intel.com lists the Atom x5-Z8350 as "products formerly Cherry Trail". >I wondered what possessed you to buy it, going on specs and 'manual'?=20 >and what the '32GB Storage' might denote. Good thing you could return=20 >it. For reference, just how cheap are they in AU? Something cheap and cheerful as a portable to play on - there wasn't enough information available online to determine whether it would be usable outside Windows. Aldi's "no questions" returns policy was one of the things that swayed me to try it. It was AUD249 but I've found something by "Pendo" for AUD229 that looks like it came off the same production line. I hadn't realised just how weird the insides of some "PC compatible" computers had become. --=20 Peter Jeremy --K8nIJk4ghYZn606h Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY2CDVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0xvcP/2IpffJKR4BXg+QRH9ljGAvV CvCFWDgGA40RqTDHnAQV12jmyxjsNvwhN9QzEuDvFNt/HwA2re0AK265mzY+MKXt LmYsbh+W0GJdB1yBlnGeFdYADyFCW+dNwaji1+zNGuxHE596UsHDEKcWAwwNc5Mc 4ZxsAiXO7DYPn19RT2Ed9wRbz2jiOFo3bqupGJNRivMq+C78X1a1y5Q4+7A6f9XZ prjtMfqqGT8AuL6hX5tBhGNSIgXabhbSYt+Cb3tmZR/COMLASYD872TQfGXcx9Y7 ocqAxa+5ZOKaKOeU/z7OzMuIF67Mu9i0aBuulhSS6SN2rPnxE59nqQxalQwKQUQB JRRHReYfFYxkbtOmDtTpNhhiwmRMJlqbVxIofP1doZcqcWLUmJVssfb75dRvjcSj EjoiyUO0Ct/MHMimPtd6D7zVewlV8O41wjNiAcb6k7qOrBnnoJ9Fe/UaN6KLydH5 86SOgshF1A/B9NvKft1/9U/EBkP9aPnU0YO9FYiM1hZEJkIdsAH7YfaB7QPW15wF VX1CZwm/4wjrts7KXsiQvbl/oCdYIW4AbsUkblMCBJ4hKBGP7xjU9o80KyHNYvwI UI7rOuem7YYqu1Qaa6RlPg3l4CctWnXjPmgRqStQS09UxLYZPXg1hEfSdIOuiNfU 3ZbjDgt6DG4fGwyU+yZY =awyR -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- From owner-freebsd-stable@freebsd.org Mon Mar 27 09:49:35 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01945D1FF82; Mon, 27 Mar 2017 09:49:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 26AF11CB7; Mon, 27 Mar 2017 09:49:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA13325; Mon, 27 Mar 2017 12:49:32 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1csRHI-000GUk-5d; Mon, 27 Mar 2017 12:49:32 +0300 Subject: Re: Opteron 6100-series "Magny-Cours" To: "Jack L." References: <6C0CE842-C900-4914-B362-8DD88C1BDB2E@gmail.com> Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org From: Andriy Gapon Message-ID: <0ff0e9ab-524f-cb0d-87c9-bfec9aa44a4e@FreeBSD.org> Date: Mon, 27 Mar 2017 12:48:10 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <6C0CE842-C900-4914-B362-8DD88C1BDB2E@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 09:49:35 -0000 On 03/25/2017 23:26, Jack L. wrote: > I have a few still sitting in a corner with FreeBSD 7 or 8 on them. Someday i might put them back on with FreeBSD but not anytime soon Apologies for not qualifying my question. I would like to obtain some information from such a system and possibly to ask to test a patch. Looks like you won't be able to help with that. At least, until that some day :-). >> On Mar 25, 2017, at 11:02 AM, Andriy Gapon wrote: >> >> >> Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with FreeBSD? -- Andriy Gapon From owner-freebsd-stable@freebsd.org Mon Mar 27 10:09:45 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CCB4D1F6FD; Mon, 27 Mar 2017 10:09:45 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp208.alice.it (smtp208.alice.it [82.57.200.104]) by mx1.freebsd.org (Postfix) with ESMTP id E8E461A20; Mon, 27 Mar 2017 10:09:44 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (82.52.25.226) by smtp208.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 588F42930A8B18FF; Mon, 27 Mar 2017 12:09:33 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v2RA9X3T063176; Mon, 27 Mar 2017 12:09:36 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Opteron 6100-series "Magny-Cours" To: Andriy Gapon , freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org References: From: Andrea Venturoli Message-ID: Date: Mon, 27 Mar 2017 12:09:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 10:09:45 -0000 On 03/25/17 19:02, Andriy Gapon wrote: > > Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with FreeBSD? Will an equivalent Athlon do or is this Opteron specific? What would that Athlon be? bye av. From owner-freebsd-stable@freebsd.org Mon Mar 27 11:33:39 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30606CA2CC6 for ; Mon, 27 Mar 2017 11:33:39 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 F0A3CF4A for ; Mon, 27 Mar 2017 11:33:38 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1csSu0-000DuN-Bn for freebsd-stable@freebsd.org; Mon, 27 Mar 2017 11:33:36 +0000 Subject: Re: Opteron 6100-series "Magny-Cours" To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: Date: Mon, 27 Mar 2017 12:33:36 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 11:33:39 -0000 On 03/27/17 11:09, Andrea Venturoli wrote: > On 03/25/17 19:02, Andriy Gapon wrote: >> >> Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors >> with FreeBSD? > > Will an equivalent Athlon do or is this Opteron specific? > > What would that Athlon be? Opteron 6100 was a K10 core, like the Phenom II, but they were 8 core, so I would hazzard a guess that the FX-8350 or similar is the same. But its usually a good idea to test on the exact CPU exhibiting the issue. -pete. (FWIW, this is being types on a K10 machine and it works fine.) From owner-freebsd-stable@freebsd.org Mon Mar 27 13:44:48 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECD6BD1F86A for ; Mon, 27 Mar 2017 13:44:48 +0000 (UTC) (envelope-from bounce-mc.us15_71311470.70265-stable=freebsd.org@mail117.suw13.rsgsv.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CD8B9FC8 for ; Mon, 27 Mar 2017 13:44:48 +0000 (UTC) (envelope-from bounce-mc.us15_71311470.70265-stable=freebsd.org@mail117.suw13.rsgsv.net) Received: by mailman.ysv.freebsd.org (Postfix) id CCC08D1F869; Mon, 27 Mar 2017 13:44:48 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC463D1F868 for ; Mon, 27 Mar 2017 13:44:48 +0000 (UTC) (envelope-from bounce-mc.us15_71311470.70265-stable=freebsd.org@mail117.suw13.rsgsv.net) Received: from mail117.suw13.rsgsv.net (mail117.suw13.rsgsv.net [198.2.183.117]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE72FC7 for ; Mon, 27 Mar 2017 13:44:48 +0000 (UTC) (envelope-from bounce-mc.us15_71311470.70265-stable=freebsd.org@mail117.suw13.rsgsv.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=k1; d=mail117.suw13.rsgsv.net; h=Subject:From:Reply-To:To:Date:Message-ID:List-ID:List-Unsubscribe:Sender:Content-Type:MIME-Version; i=recruiting=3Dteamcmp.com@mail117.suw13.rsgsv.net; bh=EI+1+F+plnnGekk42UJQnNcArSU=; b=wum4NfcPu3+OXXe0OB6kXm6RsSag3YdNXOHvk/VvVCC81SiHweqMbotzQEnqznBVmGTrS1lfgW47 XW18R5QKAjUyYlmZzIprXu1G9IIki6kq68D0JBvMxqjqMSS70kStEgdqLoqGO+kkJHy8tpkzDRQ/ 71av/DoDlAa8LWDRRAI= Received: from (127.0.0.1) by mail117.suw13.rsgsv.net id hr4bl022s7gr for ; Mon, 27 Mar 2017 13:29:41 +0000 (envelope-from ) Subject: =?utf-8?Q?Open=20positions=20at=20CMP=20Group?= From: =?utf-8?Q?HR=20Department?= Reply-To: =?utf-8?Q?HR=20Department?= To: Date: Mon, 27 Mar 2017 13:29:41 +0000 Message-ID: <5ca1791377601525c05daeb69.0d42462541.20170327132909.54b28644fc.c655b911@mail117.suw13.rsgsv.net> X-Mailer: MailChimp Mailer - **CID54b28644fc0d42462541** X-Campaign: mailchimp5ca1791377601525c05daeb69.54b28644fc X-campaignid: mailchimp5ca1791377601525c05daeb69.54b28644fc X-Report-Abuse: Please report abuse for this campaign here: http://www.mailchimp.com/abuse/abuse.phtml?u=5ca1791377601525c05daeb69&id=54b28644fc&e=0d42462541 X-MC-User: 5ca1791377601525c05daeb69 X-Feedback-ID: 71311470:71311470.70265:us15:mc X-Accounttype: pd Sender: "HR Department" x-mcda: FALSE MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format="fixed" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 13:44:49 -0000 http://www.teamcmp.com ** CMP Group is hiring! ------------------------------------------------------------ We're a digital entertainment business (leader in the industry=2C with ove= r 10M unique requests/day) with headquarters in Barcelona and an office in= New York. We are hiring talents across the business to help us with creative product= solutions and to design new applications from scratch=2C using cutting ed= ge technologies. Our Referral Program : Get your friend a new job and we will give you 500=E2=82=AC! * We have lots of open positions=2C here are a few examples: * PHP Developer (https://cmp-group.workable.com/jobs/431564) - Webpack=2C= Web Push Notifications * QA Engineer (https://cmp-group.workable.com/jobs/438991) - Selenium=2C= Jenkins=2C Java * DevOps Engineer (https://cmp-group.workable.com/jobs/440239) - Terrafo= rm=2C Go=2C Elastic Search Check out all our open positions! (http://teamcmp.com/jobs/) We're CMP Group (http://www.teamcmp.com) . Want to know more about our tec= hnical philosophies? Check out the tech team's manifesto (http://teamcmp.c= om/manifesto/) . *Terms & Conditions 1. Candidates must be placed and employed within 15 weeks of a referral be= ing submitted 2. The payment will be done through a Paypal transfer 3. CMP group reserves the right to amend or withdraw the referral scheme w= ithout further notice 4. To receive credit=2C your friend must enter your email address when the= y apply for the role so we know who should be paid for the referral =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ** (https://www.linkedin.com/company-beta/3008891/) ** (http://www.teamcmp.com) Copyright =C2=A9 2017 CMP Group=2C All rights reserved. ** www.teamcmp.com (http://www.teamcmp.com) Want to change how you receive these emails? You can ** update your preferences (http://teamcmp.us15.list-manage.com/profile?u= =3D5ca1791377601525c05daeb69&id=3Dfd13787516&e=3D0d42462541) or ** unsubscribe from this list (http://teamcmp.us15.list-manage.com/unsu= bscribe?u=3D5ca1791377601525c05daeb69&id=3Dfd13787516&e=3D0d42462541&c=3D54b= 28644fc) From owner-freebsd-stable@freebsd.org Mon Mar 27 18:13:01 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00DE1D2065B for ; Mon, 27 Mar 2017 18:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E47F1E83 for ; Mon, 27 Mar 2017 18:13:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2RID0dm006764 for ; Mon, 27 Mar 2017 18:13:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837) Date: Mon, 27 Mar 2017 18:13:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 18:13:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213903 --- Comment #22 from Cassiano Peixoto --- (In reply to Franco Fichtner from comment #21) Hi Franco, i agree with you. Now it's 6 days with no crashing anymore. Mate= usz, can you take a look please? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Mon Mar 27 18:20:01 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9DDCD209D5 for ; Mon, 27 Mar 2017 18:20:01 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from smtp.smtpout.orange.fr (smtp09.smtpout.orange.fr [80.12.242.131]) by mx1.freebsd.org (Postfix) with ESMTP id 4825B77D for ; Mon, 27 Mar 2017 18:20:00 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from [192.168.1.14] ([90.16.85.102]) by mwinf5d85 with ME id 16CL1v00N2CUNze036CLc2; Mon, 27 Mar 2017 20:12:22 +0200 X-ME-Helo: [192.168.1.14] X-ME-Date: Mon, 27 Mar 2017 20:12:22 +0200 X-ME-IP: 90.16.85.102 To: freebsd-stable From: David Marec Subject: Panic in nvidia module Message-ID: <5d1e3b4d-9548-d047-3b37-734ba7390158@davenulle.org> Date: Mon, 27 Mar 2017 20:12:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr-classic Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 18:20:01 -0000 greeting, Tracking 11-Stable, - now : 316014, - kernel panics on 'page fault' within nvidia module. The system boots and works well ( 'vt' in graphic mode) until xorg starts. - I had to rollback to a r315900 kernel to make xorg run again. Here is a dump: === kgdb kernel.debug /var/crash/vmcore.last ========================== GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x4 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff82c76964 stack pointer = 0x28:0xfffffe0235b8e4b0 frame pointer = 0x28:0xfffffe0235b8e4b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 3 current process = 876 (Xorg) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff80a8c397 at kdb_backtrace+0x67 #1 0xffffffff80a496c6 at vpanic+0x186 #2 0xffffffff80a49533 at panic+0x43 #3 0xffffffff80eadf52 at trap_fatal+0x322 #4 0xffffffff80eae11c at trap_pfault+0x1bc #5 0xffffffff80ead7d0 at trap+0x280 #6 0xffffffff80e92681 at calltrap+0x8 #7 0xffffffff82c434ef at _nv017563rm+0x1f Uptime: 1h3m54s Dumping 489 out of 8082 MB:..4%..14%..23%..33%..43%..53%..63%..72%..82%..92% Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/zfs.ko.debug...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /usr/lib/debug//boot/kernel/opensolaris.ko.debug...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /usr/lib/debug//boot/kernel/linux.ko.debug...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/linux_common.ko...Reading symbols from /usr/lib/debug//boot/kernel/linux_common.ko.debug...done. done. Loaded symbols for /boot/kernel/linux_common.ko Reading symbols from /boot/kernel/linux64.ko...Reading symbols from /usr/lib/debug//boot/kernel/linux64.ko.debug...done. done. Loaded symbols for /boot/kernel/linux64.ko Reading symbols from /boot/modules/nvidia-modeset.ko...done. Loaded symbols for /boot/modules/nvidia-modeset.ko Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=) at pcpu.h:222 222 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) backtrace #0 doadump (textdump=) at pcpu.h:222 #1 0xffffffff80a49256 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80a49700 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80a49533 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80eadf52 in trap_fatal (frame=0xfffffe0235b8e3f0, eva=4) at /usr/src/sys/amd64/amd64/trap.c:801 #5 0xffffffff80eae11c in trap_pfault (frame=0xfffffe0235b8e3f0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:658 #6 0xffffffff80ead7d0 in trap (frame=0xfffffe0235b8e3f0) at /usr/src/sys/amd64/amd64/trap.c:421 #7 0xffffffff80e92681 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff82c76964 in os_get_euid () from /boot/modules/nvidia.ko #9 0xffffffff82c434ef in _nv017563rm () from /boot/modules/nvidia.ko #10 0xfffff80021881400 in ?? () #11 0xffffffff82ba3330 in _nv004904rm () from /boot/modules/nvidia.ko #12 0x0000000000000000 in ?? () Current language: auto; currently minimal === kgdb kernel.debug /var/crash/vmcore.last ========================== Thanks -- David Marec https://lapinbilly.eu/ From owner-freebsd-stable@freebsd.org Mon Mar 27 18:34:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0587ED20634 for ; Mon, 27 Mar 2017 18:34:29 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 C47707D4 for ; Mon, 27 Mar 2017 18:34:28 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-it0-x22b.google.com with SMTP id 190so64012533itm.0 for ; Mon, 27 Mar 2017 11:34:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KcoemAZLpWDUytBRM2AA8g3hjQx9gzUGhgq6X4o3hQc=; b=QBHohj5Ckca4KYysuKq9LtNlo7apSNJlo5WZL8ngJWX+WjZGFsdilDbcEuywfrBeFN hm9a2NPglPQYU6uN0Q1cTr1yqTN1p6zGO8GxaIjdZcF0ItXAX/XecahjUz26GhR8/eZf zZxn2me0g1EDszAZ4MlMlt6/qhLCLBL3IoC8gisdyYNUYrahtDe8mp65E+if1o3enaZQ HFrsugRl9l2LQ8sEJu5S5zM/OQ+znT0KnNOZOzRpJfo0dSBxeJSDo/RYtKRMB8Qau3qS m45gjieCCAs2zOl45L296Y8Fvw+t+V9JP12rOmEovzqX8p5HqCy7XHcVcAjTW4LlWWag zBRA== 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=KcoemAZLpWDUytBRM2AA8g3hjQx9gzUGhgq6X4o3hQc=; b=kOmF3QgQFvacbNtmEqcchdoSEQQcMB1zMK3IsZru9Yufdip4KIGzvKTJWRlFjxGl3X Hrca0WpHoz5YwnMgeQ9HviWwTQ8nFtrKNc+nGMm2YapEqwMUsJarVeW/XiWHVoOHa1Ui rp6JmpqxIo0H3+EOQ/dvJZTiRkoWpBXrfu+aMl42JPn96VjY0AJdVgLXelbp54Khuf6d VprHL8Y2j+S37h61/5P8ZNDkooEKI/agnl7QR2Ht7SutNXvHyLFsZTpmAuDeyYPlzO55 apkAAlPteMdM4HkTFcGx7nDXQ1YFvz+GvVhSrIozzYNmrtdRugOw348OiVBPRdKlpq6u 4JKg== X-Gm-Message-State: AFeK/H30EKuAJgpsnFG6fqvHyO0AjYqQXv/gQa96rOuuPZDSotnInYsiKeC4UlFrCufaLJ8fYccFIBbrR1wvJw== X-Received: by 10.36.3.129 with SMTP id e123mr10969149ite.94.1490639668170; Mon, 27 Mar 2017 11:34:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.195.65 with HTTP; Mon, 27 Mar 2017 11:34:27 -0700 (PDT) X-Originating-IP: [203.99.129.1] In-Reply-To: <5d1e3b4d-9548-d047-3b37-734ba7390158@davenulle.org> References: <5d1e3b4d-9548-d047-3b37-734ba7390158@davenulle.org> From: Jonathan Chen Date: Tue, 28 Mar 2017 07:34:27 +1300 Message-ID: Subject: Re: Panic in nvidia module To: David Marec Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 18:34:29 -0000 On 28 March 2017 at 07:12, David Marec wrote: > greeting, > > Tracking 11-Stable, > - now : 316014, - > kernel panics on 'page fault' within nvidia module. > The system boots and works well ( 'vt' in graphic mode) until xorg starts. Everytime you sync up STABLE, you have to rebuild your nvidia-driver port, as it produces kernel modules that are tied closely the current kernel. I also had a panic when I moved up my STABLE-11/amd installation yesterday, but after a de-install and rebuild of the nvidia-driver port, I'm up and running again. Cheers. -- Jonathan Chen From owner-freebsd-stable@freebsd.org Mon Mar 27 18:40:02 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79244D20931 for ; Mon, 27 Mar 2017 18:40:02 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 593C7BFC for ; Mon, 27 Mar 2017 18:40:02 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=LBEMhr/1A1E87aFnmBSipRYPi/U6xtxIG5BYqN/+5w0=; b=NrjQzxUQCzWVv7pzv+dxUA8IBG sqyX7mGTz0WUm89n+lEN193qw7LrRX2vhViFXRE9rGCLsSNQ6EKR5TdokZ9R5KSmxYZSeQ9jw3rCK 4i/822yVKsp5RBzwc7Rz4H3wZtF+Xr4Y1cjEsKaPzr2JxkyMLiBfV8kBPBcRRBPX+194=; Received: from [198.61.62.10] (port=44846 helo=[10.11.82.81]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1csZYe-0006AJ-Gb; Mon, 27 Mar 2017 13:40:00 -0500 User-Agent: Microsoft-MacOutlook/f.20.0.170309 Date: Mon, 27 Mar 2017 11:39:28 -0700 Subject: Re: Panic in nvidia module From: Larry Rosenman To: Jonathan Chen , David Marec CC: freebsd-stable Message-ID: Thread-Topic: Panic in nvidia module References: <5d1e3b4d-9548-d047-3b37-734ba7390158@davenulle.org> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 18:40:02 -0000 On 3/27/17, 11:34 AM, "Jonathan Chen" wrote: On 28 March 2017 at 07:12, David Marec wrote: > greeting, > > Tracking 11-Stable, > - now : 316014, - > kernel panics on 'page fault' within nvidia module. > The system boots and works well ( 'vt' in graphic mode) until xorg starts. Everytime you sync up STABLE, you have to rebuild your nvidia-driver port, as it produces kernel modules that are tied closely the current kernel. I also had a panic when I moved up my STABLE-11/amd installation yesterday, but after a de-install and rebuild of the nvidia-driver port, I'm up and running again. Cheers. -- Jonathan Chen I fixed the issue by adding: PORTS_MODULES+=x11/nvidia-driver To my /etc/make.conf so it gets rebuilt on every kernel build. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-stable@freebsd.org Mon Mar 27 19:42:08 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85D1CD2050C for ; Mon, 27 Mar 2017 19:42:08 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) by mx1.freebsd.org (Postfix) with ESMTP id 2A478418 for ; Mon, 27 Mar 2017 19:42:07 +0000 (UTC) (envelope-from david.marec@davenulle.org) Received: from localhost ([90.16.85.102]) by mwinf5d77 with ME id 17aR1v00X2CUNze037aR3B; Mon, 27 Mar 2017 21:34:27 +0200 X-ME-Helo: localhost X-ME-Date: Mon, 27 Mar 2017 21:34:27 +0200 X-ME-IP: 90.16.85.102 Date: Mon, 27 Mar 2017 21:34:25 +0200 From: David Marec To: freebsd-stable@freebsd.org Subject: Re: Panic in nvidia module Message-ID: <20170327193424.GA46363@llanura> References: <5d1e3b4d-9548-d047-3b37-734ba7390158@davenulle.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 19:42:08 -0000 On Mon, Mar 27, 2017 at 11:39:28AM -0700, Larry Rosenman wrote: > On 3/27/17, 11:34 AM, "Jonathan Chen" wrote: Thanks Larry & Jonathan, rebuidling the nvidia driver against the new kernel solved the issue. -- David Marec https://lapinbilly.eu From owner-freebsd-stable@freebsd.org Mon Mar 27 22:28:14 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F392CD20199 for ; Mon, 27 Mar 2017 22:28:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0E7FDA6 for ; Mon, 27 Mar 2017 22:28:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2RMSC6M057552 for ; Mon, 27 Mar 2017 22:28:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837) Date: Mon, 27 Mar 2017 22:28:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: woodsb02@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 22:28:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213903 --- Comment #23 from Ben Woods --- I have also been running a week with this patch, with no more crashes. It appears to have solved it - thank you! --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Tue Mar 28 03:59:10 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 906F4D2155F for ; Tue, 28 Mar 2017 03:59:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-181.reflexion.net [208.70.211.181]) (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 4C8F57C2 for ; Tue, 28 Mar 2017 03:59:09 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29651 invoked from network); 28 Mar 2017 03:59:03 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 28 Mar 2017 03:59:03 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.2) with SMTP; Mon, 27 Mar 2017 23:59:03 -0400 (EDT) Received: (qmail 27894 invoked from network); 28 Mar 2017 03:59:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 28 Mar 2017 03:59:02 -0000 Received: from [192.168.1.119] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 27966EC8257; Mon, 27 Mar 2017 20:59:02 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: arm64 fork/swap data corruptions: A ~110 line C program demonstrating an example (Pine64+ 2GB context) [Corrected subject: arm64!] From: Mark Millard In-Reply-To: <1C595969-C6E0-44A2-9086-E48C237263BC@dsl-only.net> Date: Mon, 27 Mar 2017 20:59:01 -0700 Cc: FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: 7bit Message-Id: References: <01735A68-FED6-4E63-964F-0820FE5C446C@dsl-only.net> <16B3D614-62E1-4E58-B409-8DB9DBB35BCB@dsl-only.net> <5BEAFC6C-DA80-4D7B-AB55-977E585D1ACC@dsl-only.net> <10F50F1C-FD26-4142-9350-966312822438@dsl-only.net> <76DD9882-B4BD-4A16-A8E1-5A5FBB5A21F5@dsl-only.net> <1C595969-C6E0-44A2-9086-E48C237263BC@dsl-only.net> To: Andrew Turner , freebsd-arm X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 03:59:10 -0000 On 2017-Mar-21, at 7:21 PM, Mark Millard wrote: > On 2017-Mar-18, at 9:10 PM, Mark Millard wrote: > >> >> On 2017-Mar-18, at 5:53 PM, Mark Millard wrote: >> >>> A new, significant discovery follows. . . >>> >>> While checking out use of procstat -v I ran >>> into the following common property for the 3 >>> programs that I looked at: >>> >>> A) My small test program that fails for >>> a dynamically allocated space. >>> >>> B) sh reporting Failed assertion: "tsd_booted". >>> >>> C) su reporting Failed assertion: "tsd_booted". >>> >>> Here are example addresses from the area of >>> incorrectly zeroed memory (A then B then C): >>> >>> (lldb) print dyn_region >>> (region *volatile) $0 = 0x0000000040616000 >>> >>> (lldb) print &__je_tsd_booted >>> (bool *) $0 = 0x0000000040618520 >>> >>> (lldb) print &__je_tsd_booted >>> (bool *) $0 = 0x0000000040618520 >> >> That last above was a copy/paste error. Correction: >> >> (lldb) print &__je_tsd_booted >> (bool *) $0 = 0x000000004061d520 >> >>> The first is from dynamic allocation ending up >>> in the area. The other two are from libc.so.7 >>> globals/statics ending up in the general area. >>> >>> It looks like something is trashing a specific >>> memory area for some reason, rather independently >>> of what the program specifics are. > > I probably should have noted that the processes > involved were: child/parent then grandparent > and then great grandparent. The grandparent > was sh and the great grandparent was su. > > The ancestors in the process tree are being > damaged, not just the instances of the > program that demonstrates the problem. > >>> Other notes: >>> >>> At least for my small program showing failure: >>> >>> Being explicit about the combined conditions for failure >>> for my test program. . . >>> >>> Both tcache enabled and allocations fitting in SMALL_MAXCLASS >>> are required in order to make the program fail. >>> >>> Note: >>> >>> lldb) print __je_tcache_maxclass >>> (size_t) $0 = 32768 >>> >>> which is larger than SMALL_MAXCLASS. I've not observed >>> failures for sizes above SMALL_MAXCLASS but not exceeding >>> __je_tcache_maxclass. >>> >>> Thus tcache use by itself does not seen sufficient for >>> my program to get corruption of its dynamically allocated >>> memory: the small allocation size also matters. >>> >>> >>> Be warned that I can not eliminate the possibility that >>> the trashing changed what region of memory it trashed >>> for larger allocations or when tcache is disabled. >> >> The pine64+ 2GB eventually got into a state where: >> >> /etc/malloc.conf -> tcache:false >> >> made no difference and the failure kept occurring >> with that symbolic link in place. >> >> But after a reboot of the pin46+ 2GB >> /etc/malloc.conf -> tcache:false was again effective >> for my test program. (It was still present from >> before the reboot.) >> >> I checked the .core files and the allocated address >> assigned to dyn_region was the same in the tries >> before and after the reboot. (I had put in an >> additional raise(SIGABRT) so I'd always have >> a core file to look at.) >> >> Apparently /etc/malloc.conf -> tcache:false was >> being ignored before the reboot for some reason? > > I have also discovered that if the child process > in an example like my program does a: > > (void) posix_madvise(dyn_region, region_size, POSIX_MADV_WILLNEED); > > after the fork but before the sleep/swap-out/wait > then the problem does not happen. This is without > any read or write access to the memory between the > fork and sleep/swap-out/wait. > > By contrast such POSIX_MADV_WILLNEED use in the parent > process does not change the failure behavior. I've added another test program to bugzilla 217239 and 217138, one with thousands of 14 KiByte allocations. The test program usually ends up with them all being zeroed in the parent and child of the fork. But I've had a couple of runs where a much smaller prefix was messed up and then there were normal, expected values. #define region_size (14u*1024u) . . . #define num_regions (256u*1024u*1024u/region_size) So num_regions==18724, using up most of 256 MiBytes. Note: each region has its own 14 KiByte allocation. But dyn_regions[1296].array[0] in one example was the first normal value. In another example dyn_regions[2180].array[4096] was the first normal value. The last is interesting for being part way through an allocation's space. That but aligning with a 4 KiByte page size would seem odd for a pure-jemalloc issue. === Mark Millard markmi at dsl-only.net From owner-freebsd-stable@freebsd.org Tue Mar 28 14:25:22 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 194CCD2299B for ; Tue, 28 Mar 2017 14:25:22 +0000 (UTC) (envelope-from ml@ft-c.de) 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 067627BA for ; Tue, 28 Mar 2017 14:25:22 +0000 (UTC) (envelope-from ml@ft-c.de) Received: by mailman.ysv.freebsd.org (Postfix) id 02C77D2299A; Tue, 28 Mar 2017 14:25:22 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02647D22999 for ; Tue, 28 Mar 2017 14:25:22 +0000 (UTC) (envelope-from ml@ft-c.de) Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [IPv6:2001:67c:1400:1010::20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.in-berlin.de", Issuer "StartCom Class 3 OV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D8097B9 for ; Tue, 28 Mar 2017 14:25:21 +0000 (UTC) (envelope-from ml@ft-c.de) X-Envelope-From: ml@ft-c.de X-Envelope-To: Received: from [192.168.43.250] (x59cc8bcd.dyn.telefonica.de [89.204.139.205]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id v2SEPHgG019057 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 28 Mar 2017 16:25:17 +0200 To: stable@freebsd.org Reply-To: ml@ft-c.de From: ml@ft-c.de Subject: pkg problem Message-ID: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> Date: Tue, 28 Mar 2017 16:25:16 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 14:25:22 -0000 Hello, when I update/upgrade freebsd with pkg, pkg would install the postgresql93-client, but postgresql* version 9.6 is installed. What's going wrong? Have someoen a solution? I get the following messages: % pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. postgresql96-plpython-9.6.0_1 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgtcl-postgresql96-2.0.0_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgtcl-postgresql96-2.0.0_1 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-plperl-9.6.0_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-plpython-9.6.0_1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-server-9.6.1_1 is locked and may not be modified postgresql96-contrib-9.6.1 is locked and may not be modified pgadmin3-1.22.1_3 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified postgresql96-client-9.6.1 is locked and may not be modified The following 32 package(s) will be affected (of 0 checked): New packages to be INSTALLED: postgresql93-client: 9.3.15_1 Installed packages to be UPGRADED: php70-zlib: 7.0.16 -> 7.0.17 ... (more) php70-pgsql: 7.0.16 -> 7.0.17 php70-pdo_sqlite: 7.0.16 -> 7.0.17 php70-pdo_pgsql: 7.0.16 -> 7.0.17 php70-pdo: 7.0.16 -> 7.0.17 ... (more) nspr: 4.13.1 -> 4.14 mod_php70: 7.0.16 -> 7.0.17 git: 2.11.0_3 -> 2.12.1 Installed packages to be REINSTALLED: apache24-2.4.25_1 (options changed) Number of packages to be installed: 1 Number of packages to be upgraded: 30 Number of packages to be reinstalled: 1 The process will require 10 MiB more space. 234 KiB to be downloaded. % pkg upgrade git Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. pgtcl-postgresql96-2.0.0_1 is locked and may not be modified ... (more: see above) Checking integrity... Assertion failed: (cun != NULL), function pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. Child process pid=2230 terminated abnormally: Abort trap % uname -a FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 From owner-freebsd-stable@freebsd.org Tue Mar 28 17:36:45 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 888E4D22318 for ; Tue, 28 Mar 2017 17:36:45 +0000 (UTC) (envelope-from lsxvdqe@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 672D2FCF for ; Tue, 28 Mar 2017 17:36:45 +0000 (UTC) (envelope-from lsxvdqe@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 666D3D22317; Tue, 28 Mar 2017 17:36:45 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 661BAD22316 for ; Tue, 28 Mar 2017 17:36:45 +0000 (UTC) (envelope-from lsxvdqe@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 ECE20FCD for ; Tue, 28 Mar 2017 17:36:44 +0000 (UTC) (envelope-from lsxvdqe@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id u132so45619158wmg.0 for ; Tue, 28 Mar 2017 10:36:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=ozV7JF+nk/hcQPwXUpTyyKfmc045JI8v0MSmi7MEkAc=; b=glh6w7ccsRzIEUmS/Uomd5q6oH1Ohymk3BYfaymvCU0Sl8KG7Qi+u+oMe1lRqC5L8U OXjAJ4RXt0wR7p6sNqN+bUS52gXD8LvdEKifbg2VS5t1xFG+sXN9PfJRTKaXUHrQU/B/ byWsQiLLftBg1iPOAC+AAZsRh81AS8vi+QQ8wpI3lcxDv7rXF6aykyEp65K4hBtcmSqy wv0nTIK+WcclWETcpIp863qO4xp5hReuc3pObTcctlh0n7jeVoYi+v1V009FFLgF/6+W SMtTHv6lMkNbnux62rxr6n8elqpWSuKImQaCc9ALs7/UlCb2tQh7dazE7MlksqPv0mwP TSwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=ozV7JF+nk/hcQPwXUpTyyKfmc045JI8v0MSmi7MEkAc=; b=tGeU7MSd3G7SI1E+KAzIS8NAGyusSBtVXuXqzFeF4CwLcDF2U2iEfaohZBUCBT0rfR GTkIi+SM2O7cgdNLpgRpUc0QIdPbqwdRoE9ICDPX1lqdgPN2FFSdOhIj4DxFx9BO85OA yUgFttwCRMcbSojOurI6e8WNeIrVgp2jAtxMmStm8YJ24ztIuZ9cDZcthEPJEotSzpir yXUQGbo8s13NDZz5za7URoQpJako2Gcg4B3j5gsLnNWwnazTQ4+9Y+kXsJk0/bxlBxoJ sl1tSzEuBBre1lh5itXifY/rRCwWdglK6LWE/3nQH6lr8HTeZgJA8IinQw++vHELvA0G s6UQ== X-Gm-Message-State: AFeK/H2PHkn/ElIJA3aCZDXqzKBTj9SjYYaY9e9C4Wrh7sO1PzKN3hPSrpQuFRVIkw3ELQ== X-Received: by 10.28.28.69 with SMTP id c66mr16058732wmc.28.1490722603164; Tue, 28 Mar 2017 10:36:43 -0700 (PDT) Received: from 127.0.0.1 (3.tor.exit.babylon.network. [149.56.229.17]) by smtp.gmail.com with ESMTPSA id y190sm4467722wmy.15.2017.03.28.10.36.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 10:36:42 -0700 (PDT) Date: Tue, 28 Mar 2017 17:36:34 +0000 (UTC) From: lsxvdqe X-X-Sender: xaos@foo.bar To: ml@ft-c.de cc: stable@freebsd.org Subject: Re: pkg problem In-Reply-To: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> Message-ID: References: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 17:36:45 -0000 On Tue, 28 Mar 2017, ml@ft-c.de wrote: > Hello, > > when I update/upgrade freebsd with pkg, > pkg would install the postgresql93-client, > but postgresql* version 9.6 is installed. > > What's going wrong? > Have someoen a solution? > > I get the following messages: > > % pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > > postgresql96-plpython-9.6.0_1 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgtcl-postgresql96-2.0.0_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgtcl-postgresql96-2.0.0_1 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-plpython-9.6.0_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > > The following 32 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > postgresql93-client: 9.3.15_1 > > Installed packages to be UPGRADED: > php70-zlib: 7.0.16 -> 7.0.17 > ... (more) > php70-pgsql: 7.0.16 -> 7.0.17 > php70-pdo_sqlite: 7.0.16 -> 7.0.17 > php70-pdo_pgsql: 7.0.16 -> 7.0.17 > php70-pdo: 7.0.16 -> 7.0.17 > ... (more) > nspr: 4.13.1 -> 4.14 > mod_php70: 7.0.16 -> 7.0.17 > git: 2.11.0_3 -> 2.12.1 > > Installed packages to be REINSTALLED: > apache24-2.4.25_1 (options changed) > > Number of packages to be installed: 1 > Number of packages to be upgraded: 30 > Number of packages to be reinstalled: 1 > > The process will require 10 MiB more space. > 234 KiB to be downloaded. > Seems like locking is the problem. It's often a bad idea to use it. Try to upgrade with packages unlocked. From owner-freebsd-stable@freebsd.org Tue Mar 28 18:24:42 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C21DD22ADA for ; Tue, 28 Mar 2017 18:24:42 +0000 (UTC) (envelope-from jim@ohlste.in) 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 59058CC1 for ; Tue, 28 Mar 2017 18:24:42 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mailman.ysv.freebsd.org (Postfix) id 556B5D22AD7; Tue, 28 Mar 2017 18:24:42 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5360CD22AD6 for ; Tue, 28 Mar 2017 18:24:42 +0000 (UTC) (envelope-from jim@ohlste.in) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 1523CCBF for ; Tue, 28 Mar 2017 18:24:41 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mail-qk0-x234.google.com with SMTP id f11so73091539qkb.0 for ; Tue, 28 Mar 2017 11:24:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ohlste-in.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=y7Hi6bXh2IMRRlJs++vTzN2Fq6mFeD6zKi5F1mAgIdw=; b=pKUOEV4dolJc+EEqoRRMQeSGpkWgXKXuz3O6bHOPgYJCdvqg0yQ++wyFsK6uzm1jJj e6o81/D7pydLK8a+xJ/QVBuk8mzywiJaEoMlWR0rwCDlDnP+04JptSyQDifQeMYXAXT4 dq6FFQ03j5aCdr3WaWkVYktlwI6a5BO4Z1YpuMe3fQ6t+FPiLelnUAlz945fMn4Ta09h X4AMp0ENGM/vlgtkGLBhALukaOMgVcvsTfMgRI3sdqwgvg8tF5+QkvOAHMJFXCfbuV0C ZSWpiku+eSm1jXvsPralXZuQeeXZOPyNk4MKJCBgEI3S9DACBGAu01vcRjnrUbwEYkb+ MnnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=y7Hi6bXh2IMRRlJs++vTzN2Fq6mFeD6zKi5F1mAgIdw=; b=R2FqmofRJ3I42JJ43FeW6cBpDIWQ19fz74i2PgwSKeB7T6ed4TCE78dHSPzTHM4RP2 cRMl6/90ObY7qOq2jBG6oMKWR4uE5gcs30ZMeWUoWBLQIsCJWgDscjdfNfaCwSH76IDn W6qk2KYwtB5EmwlO99tt6nDHQtvefKXuKInWtmRLbPamHmij3Miuayyspcj3eIUo79Z6 yWI0aN5iEDLcmGQS/K72Igi7oXfxs8CdKiDWSnd+kl8laNgv84dNxuP0aZCEizevpeVv XPeMATGfygMRGPS/zMdqRsCzvNWrTLKlc3nZIgjeu2cC0GWJ41I5HwDwUhhkF5ks5B5w fyZQ== X-Gm-Message-State: AFeK/H3gLHv8egqDQmM29b5MFgcW72je4TiEwA0ielBqb4TiYv7idIWADvQ3xXWBhbC2hQ== X-Received: by 10.55.10.1 with SMTP id 1mr23934721qkk.48.1490725480747; Tue, 28 Mar 2017 11:24:40 -0700 (PDT) Received: from [192.168.1.10] (pool-108-39-64-29.nrflva.fios.verizon.net. [108.39.64.29]) by smtp.googlemail.com with ESMTPSA id 1sm3160164qty.69.2017.03.28.11.24.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 11:24:39 -0700 (PDT) Subject: Re: pkg problem To: ml@ft-c.de, stable@freebsd.org References: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> From: Jim Ohlstein Cc: freebsd-ports@freebsd.org Message-ID: <433208bf-3922-ab6b-dc57-902a1a0ad4eb@ohlste.in> Date: Tue, 28 Mar 2017 14:24:51 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 18:24:42 -0000 Hello, [cc'ing to ports mailing list since it seems more appropriate there] On 3/28/17 10:25 AM, ml@ft-c.de wrote: > Hello, > > when I update/upgrade freebsd with pkg, > pkg would install the postgresql93-client, > but postgresql* version 9.6 is installed. It appears as though $something that you are trying to upgrade has a dependency on postgresql-client. Since postgresql93 is the default version for FreeBSD packages, $something is built against postgresql93-client, and is trying to pull it in as a dependency. That would cause postgresql96-client to be deinstalled, which would then cause pretty much anything postgresql96 related to be removed. Those packages are locked, hence the failure. > > What's going wrong? > Have someoen a solution? > > I get the following messages: > > % pkg upgrade > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > > postgresql96-plpython-9.6.0_1 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgtcl-postgresql96-2.0.0_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgtcl-postgresql96-2.0.0_1 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-plperl-9.6.0_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-plpython-9.6.0_1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-server-9.6.1_1 is locked and may not be modified > postgresql96-contrib-9.6.1 is locked and may not be modified > pgadmin3-1.22.1_3 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > postgresql96-client-9.6.1 is locked and may not be modified > > The following 32 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > postgresql93-client: 9.3.15_1 > > Installed packages to be UPGRADED: > php70-zlib: 7.0.16 -> 7.0.17 > ... (more) > php70-pgsql: 7.0.16 -> 7.0.17 > php70-pdo_sqlite: 7.0.16 -> 7.0.17 > php70-pdo_pgsql: 7.0.16 -> 7.0.17 > php70-pdo: 7.0.16 -> 7.0.17 > ... (more) > nspr: 4.13.1 -> 4.14 > mod_php70: 7.0.16 -> 7.0.17 > git: 2.11.0_3 -> 2.12.1 > > Installed packages to be REINSTALLED: > apache24-2.4.25_1 (options changed) > > Number of packages to be installed: 1 > Number of packages to be upgraded: 30 > Number of packages to be reinstalled: 1 > > The process will require 10 MiB more space. > 234 KiB to be downloaded. > > > > % pkg upgrade git > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > pgtcl-postgresql96-2.0.0_1 is locked and may not be modified > ... (more: see above) > > Checking integrity... > Assertion failed: (cun != NULL), function > pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. > Child process pid=2230 terminated abnormally: Abort trap > > > > % uname -a > FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 > 06:55:27 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain From owner-freebsd-stable@freebsd.org Tue Mar 28 18:48:46 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91D27D232D2 for ; Tue, 28 Mar 2017 18:48:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7231BCB0 for ; Tue, 28 Mar 2017 18:48:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6E5E4D232D0; Tue, 28 Mar 2017 18:48:46 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A8B4D232CF; Tue, 28 Mar 2017 18:48:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 1EB07CAF; Tue, 28 Mar 2017 18:48:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yw0-x230.google.com with SMTP id v76so59964664ywg.0; Tue, 28 Mar 2017 11:48:46 -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=wSSSP4HoCBlACBM6Ov5L6cNgeYxoUdWJTtImKxZTLoc=; b=VRPj3KAyexwt9nJQoEnP/mQpJFz0KBLbnOBOW7O/IypFG4TH5jf5xUAik5G97Po5TJ 2xKpyNiVm7tMYEVb32gZIMuOeGhh+kw7xTVqwJEojQBOyq++gwc9bJyg5p7soVtiJVbn q0gJxjpv/itcJhknpY1AExuzy2Ih1dtfn8Rd1dJXNwsGLeLrpta1CmP7yojnXr/PzhLs 6scP97FjmPzvsOoQU9YuNoHiD1nyx1AyHg7vD/h2KyhHv4xVpso5iZnNs69x+8X6v7V/ XIzGaBXQctDIcTtX6pnSFxNfHgCaqGQ759K1sgFnJldeJofabig/SXzlVstsFLA6gg9C rwzQ== 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=wSSSP4HoCBlACBM6Ov5L6cNgeYxoUdWJTtImKxZTLoc=; b=k1/IQK5ytgTn9YlNRy3Fbi4xDvFIJIbGMjLDzKnEYgVC2JLObCJIgHl1ilOJhvXuWL JVdO43ko16Z1na7r0zkVHY3NkaZSL7GFuqmj+OhTAZeB6aonIRb4DkfhsnXbvjGOt1bm VXY+lQBoTKAA6E17VGaiF5MF70Pcw6iTMDrQSfSYxDorkvllyrYM8J24aINij41/yrIm 36Jl5JCQZQ3wdg+4B9YT21UzlR+wm4eSQ1tE1dwlYvFLyDOSQOeU3PGlC5dE+npQReVU kncgnMtvCFsOMNbVMJEtJlKP1N7w8LKLHHhQTvFGjvGhdQzLZIpqHZvxBPr9lWq3oxVe czyA== X-Gm-Message-State: AFeK/H0sM4Pgi7YcV3/u1N7k8mdgubS6JrDba3A6ujuMUpykX5d7laJLQ3C80YYSE6fUWi0kQqiXhFnUoOLN+Q== X-Received: by 10.129.68.31 with SMTP id r31mr4815368ywa.307.1490726925179; Tue, 28 Mar 2017 11:48:45 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.129.20.214 with HTTP; Tue, 28 Mar 2017 11:48:44 -0700 (PDT) In-Reply-To: <433208bf-3922-ab6b-dc57-902a1a0ad4eb@ohlste.in> References: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> <433208bf-3922-ab6b-dc57-902a1a0ad4eb@ohlste.in> From: Alan Somers Date: Tue, 28 Mar 2017 12:48:44 -0600 X-Google-Sender-Auth: 0EqWN_Wvmrxn9MDa66Ms8RjVab4 Message-ID: Subject: Re: pkg problem To: Jim Ohlstein Cc: ml@ft-c.de, FreeBSD Stable ML , freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 18:48:46 -0000 Try setting DEFAULT_VERSIONS=pgsql=9.6 in /etc/make.conf. Then any ports that use postgres will have to be rebuilt from ports instead of installed through pkg. -Alan On Tue, Mar 28, 2017 at 12:24 PM, Jim Ohlstein wrote: > Hello, > > [cc'ing to ports mailing list since it seems more appropriate there] > > On 3/28/17 10:25 AM, ml@ft-c.de wrote: >> >> Hello, >> >> when I update/upgrade freebsd with pkg, >> pkg would install the postgresql93-client, >> but postgresql* version 9.6 is installed. > > > > It appears as though $something that you are trying to upgrade has a > dependency on postgresql-client. Since postgresql93 is the default version > for FreeBSD packages, $something is built against postgresql93-client, and > is trying to pull it in as a dependency. That would cause > postgresql96-client to be deinstalled, which would then cause pretty much > anything postgresql96 related to be removed. Those packages are locked, > hence the failure. > > >> >> What's going wrong? >> Have someoen a solution? >> >> I get the following messages: >> >> % pkg upgrade >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> >> postgresql96-plpython-9.6.0_1 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-plperl-9.6.0_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-plpython-9.6.0_1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-server-9.6.1_1 is locked and may not be modified >> postgresql96-contrib-9.6.1 is locked and may not be modified >> pgadmin3-1.22.1_3 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> postgresql96-client-9.6.1 is locked and may not be modified >> >> The following 32 package(s) will be affected (of 0 checked): >> >> New packages to be INSTALLED: >> postgresql93-client: 9.3.15_1 >> >> Installed packages to be UPGRADED: >> php70-zlib: 7.0.16 -> 7.0.17 >> ... (more) >> php70-pgsql: 7.0.16 -> 7.0.17 >> php70-pdo_sqlite: 7.0.16 -> 7.0.17 >> php70-pdo_pgsql: 7.0.16 -> 7.0.17 >> php70-pdo: 7.0.16 -> 7.0.17 >> ... (more) >> nspr: 4.13.1 -> 4.14 >> mod_php70: 7.0.16 -> 7.0.17 >> git: 2.11.0_3 -> 2.12.1 >> >> Installed packages to be REINSTALLED: >> apache24-2.4.25_1 (options changed) >> >> Number of packages to be installed: 1 >> Number of packages to be upgraded: 30 >> Number of packages to be reinstalled: 1 >> >> The process will require 10 MiB more space. >> 234 KiB to be downloaded. >> >> >> >> % pkg upgrade git >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >> ... (more: see above) >> >> Checking integrity... >> Assertion failed: (cun != NULL), function >> pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499. >> Child process pid=2230 terminated abnormally: Abort trap >> >> >> >> % uname -a >> FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 >> 06:55:27 UTC 2016 >> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >> >> > > -- > Jim Ohlstein > > > "Never argue with a fool, onlookers may not be able to tell the difference." > - Mark Twain > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Tue Mar 28 19:27:24 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72073D2254B for ; Tue, 28 Mar 2017 19:27:24 +0000 (UTC) (envelope-from jim@ohlste.in) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4E7DCECC for ; Tue, 28 Mar 2017 19:27:24 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mailman.ysv.freebsd.org (Postfix) id 4DE5DD22549; Tue, 28 Mar 2017 19:27:24 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D922D22548 for ; Tue, 28 Mar 2017 19:27:24 +0000 (UTC) (envelope-from jim@ohlste.in) Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 068A6EC8 for ; Tue, 28 Mar 2017 19:27:24 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mail-qt0-x231.google.com with SMTP id i34so73343005qtc.0 for ; Tue, 28 Mar 2017 12:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ohlste-in.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bhgLlddquBIRg8RS2uPObYKGGpofBLq5lU3AQ+RRInk=; b=lioYe4KAF535ErVWNC9D0Erogq6oaDTZbLzPyHMNzSHl7u0YzYw6pQqRo0XBX1nd9R 0ms+dcMkKWE2NVrfTvClOPuy5/EWle8UiJ67A/rMFK5Ol27828AkENcbb4yTcbJMk85i nT2U8AT8Waby1yriOUxYL1CE51kaIo90ylM4JHUh0sqLOyl3MlmhK9MLyw6a0Hr1XyWw aXcJstoXjPU75H7ucX3KnFB06urdqR5UiKkPRXessun2AL4uNA+rERLFkJzQgJhmMulo fkvPY6LSAsDFMOcRcJdjK3Pn7f5UiflPEfw6fgN9nDN2BS2EwlWIrMlXDUIiNm/WJVsP QQVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bhgLlddquBIRg8RS2uPObYKGGpofBLq5lU3AQ+RRInk=; b=O2VvgwJrre5IRp3zw22AZkEbXKYRqXRd+iWkKRO9ajIgvs2PEJ0ss2yFQOiimgfgZU 72eAyHvFCX2/wmxiTGknYCtAbyE4i93NRC3dTBgtlh6fCeEs+Oc8MbCTUf0zEWh8uAJh qE6sPe3AYTBxH08HLAi4Try5AhVAGBiVa3AVWHpnXuDNKTM+52dN/rWWZXFml51p1uAB RF994wsW9PvK7hZHXosRWN5aWc4a3WWso0o1HC0qSlpoMnLeA32Pa//CP5XUeaBTsE/s x0kkr9k7djxga7JxzUD2OONMQ06C2IkSIO493fJAAL0UhroNRLbCOP/g8X0U9Iyl8ccY G0iw== X-Gm-Message-State: AFeK/H10WQ971ppm1ItykkC/yf4ivTHAI9jjMDOcVzfdUdXtNzHoXxPox7z3V2BNsRcHsw== X-Received: by 10.200.46.208 with SMTP id i16mr28047799qta.13.1490729243165; Tue, 28 Mar 2017 12:27:23 -0700 (PDT) Received: from [192.168.1.9] (pool-108-39-64-29.nrflva.fios.verizon.net. [108.39.64.29]) by smtp.gmail.com with ESMTPSA id a21sm2126411qkc.12.2017.03.28.12.27.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 12:27:22 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: pkg problem From: Jim Ohlstein X-Mailer: iPhone Mail (14E277) In-Reply-To: Date: Tue, 28 Mar 2017 15:27:21 -0400 Cc: ml@ft-c.de, FreeBSD Stable ML , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <51e401b5-d951-1edb-5146-676f25812d4d@ft-c.de> <433208bf-3922-ab6b-dc57-902a1a0ad4eb@ohlste.in> To: Alan Somers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 19:27:24 -0000 Hello, > On Mar 28, 2017, at 2:48 PM, Alan Somers wrote: >=20 > Try setting DEFAULT_VERSIONS=3Dpgsql=3D9.6 in /etc/make.conf. Then any > ports that use postgres will have to be rebuilt from ports instead of > installed through pkg. > -Alan I believe he's using packages.=20 >=20 >> On Tue, Mar 28, 2017 at 12:24 PM, Jim Ohlstein wrote: >> Hello, >>=20 >> [cc'ing to ports mailing list since it seems more appropriate there] >>=20 >>> On 3/28/17 10:25 AM, ml@ft-c.de wrote: >>>=20 >>> Hello, >>>=20 >>> when I update/upgrade freebsd with pkg, >>> pkg would install the postgresql93-client, >>> but postgresql* version 9.6 is installed. >>=20 >>=20 >>=20 >> It appears as though $something that you are trying to upgrade has a >> dependency on postgresql-client. Since postgresql93 is the default versio= n >> for FreeBSD packages, $something is built against postgresql93-client, an= d >> is trying to pull it in as a dependency. That would cause >> postgresql96-client to be deinstalled, which would then cause pretty much= >> anything postgresql96 related to be removed. Those packages are locked, >> hence the failure. >>=20 >>=20 >>>=20 >>> What's going wrong? >>> Have someoen a solution? >>>=20 >>> I get the following messages: >>>=20 >>> % pkg upgrade >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>>=20 >>> postgresql96-plpython-9.6.0_1 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-plperl-9.6.0_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-plpython-9.6.0_1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-server-9.6.1_1 is locked and may not be modified >>> postgresql96-contrib-9.6.1 is locked and may not be modified >>> pgadmin3-1.22.1_3 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>> postgresql96-client-9.6.1 is locked and may not be modified >>>=20 >>> The following 32 package(s) will be affected (of 0 checked): >>>=20 >>> New packages to be INSTALLED: >>> postgresql93-client: 9.3.15_1 >>>=20 >>> Installed packages to be UPGRADED: >>> php70-zlib: 7.0.16 -> 7.0.17 >>> ... (more) >>> php70-pgsql: 7.0.16 -> 7.0.17 >>> php70-pdo_sqlite: 7.0.16 -> 7.0.17 >>> php70-pdo_pgsql: 7.0.16 -> 7.0.17 >>> php70-pdo: 7.0.16 -> 7.0.17 >>> ... (more) >>> nspr: 4.13.1 -> 4.14 >>> mod_php70: 7.0.16 -> 7.0.17 >>> git: 2.11.0_3 -> 2.12.1 >>>=20 >>> Installed packages to be REINSTALLED: >>> apache24-2.4.25_1 (options changed) >>>=20 >>> Number of packages to be installed: 1 >>> Number of packages to be upgraded: 30 >>> Number of packages to be reinstalled: 1 >>>=20 >>> The process will require 10 MiB more space. >>> 234 KiB to be downloaded. >>>=20 >>>=20 >>>=20 >>> % pkg upgrade git >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>> pgtcl-postgresql96-2.0.0_1 is locked and may not be modified >>> ... (more: see above) >>>=20 >>> Checking integrity... >>> Assertion failed: (cun !=3D NULL), function >>> pkg_conflicts_check_chain_conflict, file pkg_jobs_conflicts.c, line 499.= >>> Child process pid=3D2230 terminated abnormally: Abort trap >>>=20 >>>=20 >>>=20 >>> % uname -a >>> FreeBSD ftc2 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 >>> 06:55:27 UTC 2016 >>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >>>=20 >>>=20 >>=20 >> -- >> Jim Ohlstein >>=20 >>=20 >> "Never argue with a fool, onlookers may not be able to tell the differenc= e." >> - Mark Twain >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"= From owner-freebsd-stable@freebsd.org Wed Mar 29 18:34:18 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FA23D24B52 for ; Wed, 29 Mar 2017 18:34:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F1871349 for ; Wed, 29 Mar 2017 18:34:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2TIYHfV002854 for ; Wed, 29 Mar 2017 18:34:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837) Date: Wed, 29 Mar 2017 18:34:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2017 18:34:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213903 --- Comment #24 from Cassiano Peixoto --- So guys, any committer available to commit this fix? It's really important. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Wed Mar 29 20:06:43 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BA33D242F8 for ; Wed, 29 Mar 2017 20:06:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0B5D61A33 for ; Wed, 29 Mar 2017 20:06:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2TK6eC7036430 for ; Wed, 29 Mar 2017 20:06:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837) Date: Wed, 29 Mar 2017 20:06:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mjg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2017 20:06:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213903 --- Comment #25 from Mateusz Guzik --- I'm working on an update on this, likely will be ready tomorrow. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Mar 31 11:13:31 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 422DDD27763 for ; Fri, 31 Mar 2017 11:13:31 +0000 (UTC) (envelope-from harrier@seiryu.id.hkg.ac.jp) Received: from seiryu.id.hkg.ac.jp (seiryu.id.hkg.ac.jp [202.25.192.41]) by mx1.freebsd.org (Postfix) with ESMTP id 0949DC30 for ; Fri, 31 Mar 2017 11:13:31 +0000 (UTC) (envelope-from harrier@seiryu.id.hkg.ac.jp) Received: from shinnou.localhost (localhost [127.0.0.1]) by seiryu.id.hkg.ac.jp (Postfix) with SMTP id B4CB515BA4; Fri, 31 Mar 2017 20:07:57 +0900 (JST) Date: Fri, 31 Mar 2017 20:07:57 +0900 From: Hiroyuki Une To: freebsd-stable@freebsd.org Subject: VirtualBox-ose kernel module crashes 10-stable Message-Id: <20170331200757.233b3826797acd61c66f03e7@seiryu.id.hkg.ac.jp> Organization: Hiroshima Kokusai Gakuin University X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 11:13:31 -0000 Kernel Panic was caused on My 10.3-STABLE r316132 by VirtualBox-ose created by poudriere(8) on my box with DEBUG option. However, when I was using 10.3-STABLE r315187, VirtualBox-ose worked without any problem. Here is the output by kgdb: ------ start here (output by kgdb) GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: !!Assertion Failed!! Expression: RTThreadPreemptIsEnabled(NIL_RTTHREAD) Location : /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/r0drv/freebsd/spinlock-r0drv-freebsd.c(78) int RTSpinlockCreate(PRTSPINLOCK, uint32_t, const char *) Fatal trap 3: breakpoint instruction fault while in kernel mode cpuid = 3; apic id = 06 instruction pointer = 0x20:0xffffffff81dbb3de stack pointer = 0x28:0xfffffe0464bfd490 frame pointer = 0x28:0xfffffe0464bfd4c0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 46465 (VBoxSVC) trap number = 3 panic: breakpoint instruction fault cpuid = 3 KDB: stack backtrace: #0 0xffffffff809bb360 at kdb_backtrace+0x60 #1 0xffffffff8097c1e6 at vpanic+0x126 #2 0xffffffff8097c0b3 at panic+0x43 #3 0xffffffff80d9ce2d at trap_fatal+0x35d #4 0xffffffff80d9caaf at trap+0x79f #5 0xffffffff80d81d4c at calltrap+0x8 #6 0xffffffff81d7d591 at supdrvCreateSession+0x91 #7 0xffffffff81d9355b at vboxdrvFreeBSDOpenCommon+0x2b #8 0xffffffff80855a32 at devfs_open+0x122 #9 0xffffffff80ed8671 at VOP_OPEN_APV+0xa1 #10 0xffffffff80a3bc34 at vn_open_vnode+0x234 #11 0xffffffff80a3b803 at vn_open_cred+0x373 #12 0xffffffff80a348cf at kern_openat+0x26f #13 0xffffffff80d9d862 at amd64_syscall+0x452 #14 0xffffffff80d8203b at Xfast_syscall+0xfb Uptime: 16h16m43s Dumping 3881 out of 16259 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. Loaded symbols for /boot/kernel/linprocfs.ko.symbols Reading symbols from /boot/kernel/linux_common.ko.symbols...done. Loaded symbols for /boot/kernel/linux_common.ko.symbols Reading symbols from /boot/kernel/linsysfs.ko.symbols...done. Loaded symbols for /boot/kernel/linsysfs.ko.symbols Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols Reading symbols from /boot/kernel/tmpfs.ko.symbols...done. Loaded symbols for /boot/kernel/tmpfs.ko.symbols Reading symbols from /boot/modules/vboxdrv.ko.symbols...done. Loaded symbols for /boot/modules/vboxdrv.ko.symbols Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. Loaded symbols for /boot/kernel/fdescfs.ko.symbols Reading symbols from /boot/kernel/i915kms.ko.symbols...done. Loaded symbols for /boot/kernel/i915kms.ko.symbols Reading symbols from /boot/kernel/drm2.ko.symbols...done. Loaded symbols for /boot/kernel/drm2.ko.symbols Reading symbols from /boot/kernel/iicbus.ko.symbols...done. Loaded symbols for /boot/kernel/iicbus.ko.symbols Reading symbols from /boot/kernel/iic.ko.symbols...done. Loaded symbols for /boot/kernel/iic.ko.symbols Reading symbols from /boot/kernel/iicbb.ko.symbols...done. Loaded symbols for /boot/kernel/iicbb.ko.symbols Reading symbols from /boot/kernel/ulpt.ko.symbols...done. Loaded symbols for /boot/kernel/ulpt.ko.symbols Reading symbols from /boot/kernel/ipfw.ko.symbols...done. Loaded symbols for /boot/kernel/ipfw.ko.symbols Reading symbols from /boot/kernel/linux.ko.symbols...done. Loaded symbols for /boot/kernel/linux.ko.symbols Reading symbols from /boot/kernel/linux64.ko.symbols...done. Loaded symbols for /boot/kernel/linux64.ko.symbols Reading symbols from /boot/kernel/i915.ko.symbols...done. Loaded symbols for /boot/kernel/i915.ko.symbols Reading symbols from /boot/kernel/drm.ko.symbols...done. Loaded symbols for /boot/kernel/drm.ko.symbols Reading symbols from /boot/kernel/nullfs.ko.symbols...done. Loaded symbols for /boot/kernel/nullfs.ko.symbols #0 doadump (textdump=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=) at pcpu.h:219 #1 0xffffffff8097be03 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:486 #2 0xffffffff8097c225 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:889 #3 0xffffffff8097c0b3 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:818 #4 0xffffffff80d9ce2d in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:858 #5 0xffffffff80d9caaf in trap (frame=) at /usr/src/sys/amd64/amd64/trap.c:203 #6 0xffffffff80d81d4c in calltrap () at /usr/src/sys/amd64/amd64/exception.S:238 #7 0xffffffff81dbb3de in RTSpinlockCreate (pSpinlock=0xfffff80233354860, fFlags=4, pszName=0xfffffe0464bfd310 "") at /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/r0drv/freebsd/spinlock-r0drv-freebsd.c:78 #8 0xffffffff81d7d591 in supdrvCreateSession (pDevExt=0xffffffff81ddc510, fUser=true, fUnrestricted=false, ppSession=0xfffffe0464bfd518) at SUPDrv.c:772 #9 0xffffffff81d9355b in vboxdrvFreeBSDOpenCommon () at /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c:250 #10 0xffffffff80855a32 in devfs_open (ap=) at /usr/src/sys/fs/devfs/devfs_vnops.c:1116 #11 0xffffffff80ed8671 in VOP_OPEN_APV (vop=, a=) at vnode_if.c:469 ---Type to continue, or q to quit--- #12 0xffffffff80a3bc34 in vn_open_vnode (vp=0xfffff802d807b3b0, fmode=3, cred=0xfffff8031f06f100, td=0xfffff802aad3b4c0, fp=0xfffff80020b39320) at vnode_if.h:196 #13 0xffffffff80a3b803 in vn_open_cred (ndp=0xfffffe0464bfd870, flagp=0xfffffe0464bfd94c, cmode=, vn_open_flags=, cred=0xfffffe0464bfd310, fp=0xfffff80020b39320) at /usr/src/sys/kern/vfs_vnops.c:268 #14 0xffffffff80a348cf in kern_openat (td=0xfffff802aad3b4c0, fd=-100, path=0x80182c1ec
, pathseg=UIO_USERSPACE, flags=3, mode=) at /usr/src/sys/kern/vfs_syscalls.c:1067 #15 0xffffffff80d9d862 in amd64_syscall (td=0xfffff802aad3b4c0, traced=0) at subr_syscall.c:141 #16 0xffffffff80d8203b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:398 #17 0x0000000802cdf8fa in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal ------ end here (output by kgdb) As shown in the above, kernel panic was caused by assertion RTThreadPreemptIsEnabled(NIL_RTTHREAD) which tests the following expressions: 1. curthread->td_critnest is equal to 0, and 2. IF (interrupt flag) on eflag (or rflag ?) is equal to 1. This assertion will be successful only if both of above are true. As I read the source of VirtualBox, RTThreadPreemptIsEnabled is a part of test for preemtiveness which is used to create a spinlock. However, I'm not sure why assertion RTThreadPreemptIsEnabled is required, and this was failed on 10.3-STABLE r316132. I would appreciate any information. Thanks. -- Hiroyuki Une: Hiroshima Kokusai Gakuin University une@hkg.ac.jp / harrier@seiryu.id.hkg.ac.jp From owner-freebsd-stable@freebsd.org Fri Mar 31 11:57:17 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65D0AD26083 for ; Fri, 31 Mar 2017 11:57:17 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 01EC47F1 for ; Fri, 31 Mar 2017 11:57:16 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id v2VBusUx062602 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 31 Mar 2017 13:56:55 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id v2VBusIB062599; Fri, 31 Mar 2017 13:56:54 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 31 Mar 2017 13:56:54 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Hiroyuki Une cc: freebsd-stable@freebsd.org Subject: Re: VirtualBox-ose kernel module crashes 10-stable In-Reply-To: <20170331200757.233b3826797acd61c66f03e7@seiryu.id.hkg.ac.jp> Message-ID: References: <20170331200757.233b3826797acd61c66f03e7@seiryu.id.hkg.ac.jp> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 11:57:17 -0000 On Fri, 31 Mar 2017 20:07+0900, Hiroyuki Une wrote: > Kernel Panic was caused on My 10.3-STABLE r316132 > by VirtualBox-ose created by poudriere(8) on my box with DEBUG option. > However, when I was using 10.3-STABLE r315187, > VirtualBox-ose worked without any problem. > > Here is the output by kgdb: > > ------ start here (output by kgdb) > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > !!Assertion Failed!! > Expression: RTThreadPreemptIsEnabled(NIL_RTTHREAD) > Location : /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/r0drv/freebsd/spinlock-r0drv-freebsd.c(78) int RTSpinlockCreate(PRTSPINLOCK, uint32_t, const char *) > > > Fatal trap 3: breakpoint instruction fault while in kernel mode > cpuid = 3; apic id = 06 > instruction pointer = 0x20:0xffffffff81dbb3de > stack pointer = 0x28:0xfffffe0464bfd490 > frame pointer = 0x28:0xfffffe0464bfd4c0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 46465 (VBoxSVC) > trap number = 3 > panic: breakpoint instruction fault > cpuid = 3 > KDB: stack backtrace: > #0 0xffffffff809bb360 at kdb_backtrace+0x60 > #1 0xffffffff8097c1e6 at vpanic+0x126 > #2 0xffffffff8097c0b3 at panic+0x43 > #3 0xffffffff80d9ce2d at trap_fatal+0x35d > #4 0xffffffff80d9caaf at trap+0x79f > #5 0xffffffff80d81d4c at calltrap+0x8 > #6 0xffffffff81d7d591 at supdrvCreateSession+0x91 > #7 0xffffffff81d9355b at vboxdrvFreeBSDOpenCommon+0x2b > #8 0xffffffff80855a32 at devfs_open+0x122 > #9 0xffffffff80ed8671 at VOP_OPEN_APV+0xa1 > #10 0xffffffff80a3bc34 at vn_open_vnode+0x234 > #11 0xffffffff80a3b803 at vn_open_cred+0x373 > #12 0xffffffff80a348cf at kern_openat+0x26f > #13 0xffffffff80d9d862 at amd64_syscall+0x452 > #14 0xffffffff80d8203b at Xfast_syscall+0xfb > Uptime: 16h16m43s > Dumping 3881 out of 16259 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% > > Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. > Loaded symbols for /boot/kernel/linprocfs.ko.symbols > Reading symbols from /boot/kernel/linux_common.ko.symbols...done. > Loaded symbols for /boot/kernel/linux_common.ko.symbols > Reading symbols from /boot/kernel/linsysfs.ko.symbols...done. > Loaded symbols for /boot/kernel/linsysfs.ko.symbols > Reading symbols from /boot/kernel/zfs.ko.symbols...done. > Loaded symbols for /boot/kernel/zfs.ko.symbols > Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. > Loaded symbols for /boot/kernel/opensolaris.ko.symbols > Reading symbols from /boot/kernel/tmpfs.ko.symbols...done. > Loaded symbols for /boot/kernel/tmpfs.ko.symbols > Reading symbols from /boot/modules/vboxdrv.ko.symbols...done. > Loaded symbols for /boot/modules/vboxdrv.ko.symbols > Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. > Loaded symbols for /boot/kernel/fdescfs.ko.symbols > Reading symbols from /boot/kernel/i915kms.ko.symbols...done. > Loaded symbols for /boot/kernel/i915kms.ko.symbols > Reading symbols from /boot/kernel/drm2.ko.symbols...done. > Loaded symbols for /boot/kernel/drm2.ko.symbols > Reading symbols from /boot/kernel/iicbus.ko.symbols...done. > Loaded symbols for /boot/kernel/iicbus.ko.symbols > Reading symbols from /boot/kernel/iic.ko.symbols...done. > Loaded symbols for /boot/kernel/iic.ko.symbols > Reading symbols from /boot/kernel/iicbb.ko.symbols...done. > Loaded symbols for /boot/kernel/iicbb.ko.symbols > Reading symbols from /boot/kernel/ulpt.ko.symbols...done. > Loaded symbols for /boot/kernel/ulpt.ko.symbols > Reading symbols from /boot/kernel/ipfw.ko.symbols...done. > Loaded symbols for /boot/kernel/ipfw.ko.symbols > Reading symbols from /boot/kernel/linux.ko.symbols...done. > Loaded symbols for /boot/kernel/linux.ko.symbols > Reading symbols from /boot/kernel/linux64.ko.symbols...done. > Loaded symbols for /boot/kernel/linux64.ko.symbols > Reading symbols from /boot/kernel/i915.ko.symbols...done. > Loaded symbols for /boot/kernel/i915.ko.symbols > Reading symbols from /boot/kernel/drm.ko.symbols...done. > Loaded symbols for /boot/kernel/drm.ko.symbols > Reading symbols from /boot/kernel/nullfs.ko.symbols...done. > Loaded symbols for /boot/kernel/nullfs.ko.symbols > #0 doadump (textdump=) at pcpu.h:219 > 219 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:219 > #1 0xffffffff8097be03 in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:486 > #2 0xffffffff8097c225 in vpanic (fmt=, > ap=) at /usr/src/sys/kern/kern_shutdown.c:889 > #3 0xffffffff8097c0b3 in panic (fmt=0x0) > at /usr/src/sys/kern/kern_shutdown.c:818 > #4 0xffffffff80d9ce2d in trap_fatal (frame=, > eva=) at /usr/src/sys/amd64/amd64/trap.c:858 > #5 0xffffffff80d9caaf in trap (frame=) > at /usr/src/sys/amd64/amd64/trap.c:203 > #6 0xffffffff80d81d4c in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:238 > #7 0xffffffff81dbb3de in RTSpinlockCreate (pSpinlock=0xfffff80233354860, > fFlags=4, pszName=0xfffffe0464bfd310 "") > at /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/r0drv/freebsd/spinlock-r0drv-freebsd.c:78 > #8 0xffffffff81d7d591 in supdrvCreateSession (pDevExt=0xffffffff81ddc510, > fUser=true, fUnrestricted=false, ppSession=0xfffffe0464bfd518) > at SUPDrv.c:772 > #9 0xffffffff81d9355b in vboxdrvFreeBSDOpenCommon () > at /wrkdirs/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.1.18/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c:250 > #10 0xffffffff80855a32 in devfs_open (ap=) > at /usr/src/sys/fs/devfs/devfs_vnops.c:1116 > #11 0xffffffff80ed8671 in VOP_OPEN_APV (vop=, > a=) at vnode_if.c:469 > ---Type to continue, or q to quit--- > #12 0xffffffff80a3bc34 in vn_open_vnode (vp=0xfffff802d807b3b0, fmode=3, > cred=0xfffff8031f06f100, td=0xfffff802aad3b4c0, fp=0xfffff80020b39320) > at vnode_if.h:196 > #13 0xffffffff80a3b803 in vn_open_cred (ndp=0xfffffe0464bfd870, > flagp=0xfffffe0464bfd94c, cmode=, > vn_open_flags=, cred=0xfffffe0464bfd310, > fp=0xfffff80020b39320) at /usr/src/sys/kern/vfs_vnops.c:268 > #14 0xffffffff80a348cf in kern_openat (td=0xfffff802aad3b4c0, fd=-100, > path=0x80182c1ec
, > pathseg=UIO_USERSPACE, flags=3, mode=) > at /usr/src/sys/kern/vfs_syscalls.c:1067 > #15 0xffffffff80d9d862 in amd64_syscall (td=0xfffff802aad3b4c0, traced=0) > at subr_syscall.c:141 > #16 0xffffffff80d8203b in Xfast_syscall () > at /usr/src/sys/amd64/amd64/exception.S:398 > #17 0x0000000802cdf8fa in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > > ------ end here (output by kgdb) > > As shown in the above, kernel panic was caused by > assertion RTThreadPreemptIsEnabled(NIL_RTTHREAD) > which tests the following expressions: > > 1. curthread->td_critnest is equal to 0, and > 2. IF (interrupt flag) on eflag (or rflag ?) is equal to 1. > > This assertion will be successful only if both of above are true. > > As I read the source of VirtualBox, RTThreadPreemptIsEnabled is > a part of test for preemtiveness which is used to create a spinlock. > However, I'm not sure why assertion RTThreadPreemptIsEnabled is required, > and this was failed on 10.3-STABLE r316132. > > I would appreciate any information. Thanks. emulators/virtualbox-ose needs access to the kernel sources during build. Maybe you should rebuild emulators/virtualbox-ose to match your current source tree. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+