From owner-freebsd-stable@freebsd.org Sun Jun 24 08:04:04 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10CD3101DC46; Sun, 24 Jun 2018 08:04:04 +0000 (UTC) (envelope-from SRS0=8X+v=JK=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 8ED097E488; Sun, 24 Jun 2018 08:04:03 +0000 (UTC) (envelope-from SRS0=8X+v=JK=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2360928411; Sun, 24 Jun 2018 10:03:55 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A144828422; Sun, 24 Jun 2018 10:03:46 +0200 (CEST) Subject: Re: jail related inconsistencies in FreeBSD tools parameters To: James Gritton , bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <47728073-93d3-325c-d90f-6235a4d548e7@quip.cz> Date: Sun, 24 Jun 2018 10:03:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <18000a3b93085c91aeffbca937862786@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 24 Jun 2018 08:04:04 -0000 James Gritton wrote on 2018/06/23 17:30: > On 2018-06-22 16:03, Miroslav Lachman wrote: >> Chris H wrote on 2018/06/22 23:46: >>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >>> <000.fbsd@quip.cz> said >>> >>>> I don't know if it is better to discuss it in jail@ or stable@ list >>>> so a do cross-post. >>>> >>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>> taking JID as parameter. >>>> >>>> For example "sockstat" takes -j JID "Show only sockets belonging to >>>> the specified jail ID" and it means numeric ID only. >>>> On the other hand "ps" takes -J JID "This may be either the jid or >>>> name of the jail.  Use -J 0 to display only host processes." >>>> The same apply for "top", it understands jid as a number or name of >>>> the jail too. >>>> Then again "cpuset" takes only numerical ID of the jail... >>>> >>>> Shouldn't it be consistent across all FreeBSD base utilities so all >>>> of them can use numerical ID and name? >>> Good idea! Are you offering to create a patch? ;-) >>> It'd be my guess that given they weren't all created at the same >>> time, nor >>> the same individual; that (quite probably?) the "jail" additions were >>> also >>> added at different times, and by different people. So I'd imagine that >>> unless someone with a commit bit decides one day they'd like to take >>> that >>> on. Someone(tm) maybe you? will need to propose a patch. :-) >> >> If I can understand C sources I will create the patch by myself >> instead of just posting here. Unfortunately I am able to code in sh, >> php and a bit of javascript and perl but no C. :) >> >> Miroslav Lachman > > Sure, a PR would be handy for this - it's a pretty simple thing to add, > and consistency would indeed be a good move. PR 229266 created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 Kind regards Miroslav Lachman From owner-freebsd-stable@freebsd.org Sun Jun 24 17:53:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 966E01006D7B for ; Sun, 24 Jun 2018 17:53:51 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AC35711E8 for ; Sun, 24 Jun 2018 17:53:50 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 41DKfv3bxmzDhGj for ; Sun, 24 Jun 2018 17:53:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1529862823; bh=L/y7BWEK2aLWgbmKAalrJTi7 u2PxD8lbdMmXqa62lEA=; b=RMwqHJsiqYwnz2TIYhelB7eGkPVjtm9o9P72ulCx EgNfhmrxSq5hTfiF2MH4tjq6ZZnUxZ/V+G74zvCI5FyWUmDC31yfqeVajTEgIwx3 GqWj9EoHNlaBTDu9PmTLLJhLDiNonguRFlYRdhqg9gDI5HfL1CJc8/JZakqyQnJF qxk= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id 5uNMlvj67qrH for ; Sun, 24 Jun 2018 17:53:43 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:201:9eda:3eff:fe70:24c0]) by mail.daemonic.se (Postfix) with ESMTPSA id 41DKfv0V3kzDhFd for ; Sun, 24 Jun 2018 17:53:43 +0000 (UTC) Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] To: freebsd-stable@freebsd.org References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> <20180622015757.GA52468@quark.hightek.org> <86zhznbi8u.fsf@elm.localnet> From: Niclas Zeising Message-ID: Date: Sun, 24 Jun 2018 19:53:42 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 24 Jun 2018 17:53:51 -0000 On 06/23/18 00:40, Mark Saad wrote: > Vincent > I used the scfb driver in openbsd land for a work project . Currentl= y I am using 11-STABLE with the Radeon driver but at one point I had a di= fferent card under 11.0 that didn=E2=80=99t work unless I used the scfb d= river . Hi! If you are using FreeBSD 11.2 or later (stable or current) you should be=20 able to use graphics/drm-stable-kmod and get acceleration with your ATI=20 video cards. Please try it out! Regards --=20 Niclas From owner-freebsd-stable@freebsd.org Sun Jun 24 21:01:36 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6157C100FFFA for ; Sun, 24 Jun 2018 21:01:36 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F38717ABED for ; Sun, 24 Jun 2018 21:01:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B42A6100FFEF; Sun, 24 Jun 2018 21:01:35 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1B26100FFEC for ; Sun, 24 Jun 2018 21:01:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DB4C7ABDD for ; Sun, 24 Jun 2018 21:01:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6473D99D8 for ; Sun, 24 Jun 2018 21:01:34 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5OL1YRk077733 for ; Sun, 24 Jun 2018 21:01:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5OL1Ybn077727 for stable@FreeBSD.org; Sun, 24 Jun 2018 21:01:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201806242101.w5OL1Ybn077727@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: stable@FreeBSD.org Subject: Problem reports for stable@FreeBSD.org that need special attention Date: Sun, 24 Jun 2018 21:01:34 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 24 Jun 2018 21:01:36 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock 1 problems total for which you should take action. From owner-freebsd-stable@freebsd.org Mon Jun 25 00:30:57 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9440D101B6D2 for ; Mon, 25 Jun 2018 00:30:57 +0000 (UTC) (envelope-from lists@pingle.org) Received: from luna.pingle.org (luna.pingle.org [68.76.213.30]) by mx1.freebsd.org (Postfix) with ESMTP id 3E44B83171 for ; Mon, 25 Jun 2018 00:30:56 +0000 (UTC) (envelope-from lists@pingle.org) Received: from luna.pingle.org (unknown [127.0.0.1]) by luna.pingle.org (Postfix) with ESMTP id 82E30DDA927; Sun, 24 Jun 2018 20:30:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at pingle.org Received: from luna.pingle.org ([127.0.0.1]) by luna.pingle.org (luna.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3SGHGkk-mDN; Sun, 24 Jun 2018 20:30:49 -0400 (EDT) Received: from [172.21.32.115] (hpcw.hpcisp.com [68.76.213.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by luna.pingle.org (Postfix) with ESMTPSA id 6758FDDA920; Sun, 24 Jun 2018 20:30:49 -0400 (EDT) Subject: Re: 11.2-RC3 regression - networking igb driver To: David Samms <2yt@gmx.com>, freebsd-stable@freebsd.org References: <2b154303-35f8-df8e-5d2f-ea93b8fdad1d@gmx.com> From: Jim Pingle Message-ID: <2c4e2c6c-ef7a-66a3-e21d-222026c9e88c@pingle.org> Date: Sun, 24 Jun 2018 20:30:47 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <2b154303-35f8-df8e-5d2f-ea93b8fdad1d@gmx.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 00:30:57 -0000 On 6/23/2018 1:27 PM, David Samms wrote: > There is a regression in 11.2-RC3 that effects the igb driver for Intels > C2000 SoC I354 Quad GbE Controller > > Supermicro A1SRi-2558F > http://www.supermicro.com/products/motherboard/Atom/X10/A1SRi-2558F.cfm > > This server has run 10.x and 11.x fine up till 11.2-RC3. > > PROBLEM: > with 11.2-RC3 the server boots and gets a network connection to the > cable modem, but the interface (igb0) resets every 4-8 second. The reset > time appears to be related to network load, but reset withing 10s with > next to no traffic. I did try swapping cables, but with no effect. With > each reset the interface successfully obtains an IP address via DHCP, > works for a few seconds and resets. > > Restoring the server to 11.1-RELEASE-p10 resolves the problem. > > Any suggestions? Does your DHCP server send you an MTU, perhaps? Before the interface resets, what does its MTU show? You might try creating a dhclient.conf that sets "supersede interface-mtu 0;" and see if that helps. The MTU from DHCP feature is new (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 ) and e1000 interfaces will reset when applying the MTU. Jim P. From owner-freebsd-stable@freebsd.org Mon Jun 25 04:13:04 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 046901022D6B for ; Mon, 25 Jun 2018 04:13:04 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from fish.ish.com.au (ip-2.ish.com.au [203.29.62.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C10C89969 for ; Mon, 25 Jun 2018 04:13:02 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from ip-145.ish.com.au ([203.29.62.145]:60974) by fish.ish.com.au with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1fXIrr-0007cv-1A for freebsd-stable@freebsd.org; Mon, 25 Jun 2018 14:12:43 +1000 X-CTCH-RefID: str=0001.0A150202.5B306BBB.00B1:SCFSTAT42589845, ss=1, re=-4.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 To: freebsd-stable From: Aristedes Maniatis Subject: pf best practices: in or out Message-ID: <1a730ca1-8c9e-9a9b-72e5-696fb92c8e49@ish.com.au> Date: Mon, 25 Jun 2018 14:12:43 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 04:13:04 -0000 Hi all pf has rules that can operate either 'in' or 'out'. That is, on traffic entering or leaving an interface. I'm trying to consolidate my rules to make them easier to understand and update, so it seems a bit pointless to have the same rules twice. Are there any best practices on whether it makes more sense to put rules on the in or out side? I could bind all the rules to the internet facing interface and then use "in" for inbound traffic and "out" for outbound. Does that makes sense? Does it make any difference from a performance point of view? Secondly, where do DNAT rules execute in the sequence? Do they change the destination IP in between the in and out pass pf rules? I'm not currently subscribed here, so please cc me on replies. Thanks Ari From owner-freebsd-stable@freebsd.org Mon Jun 25 04:16:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9291F10232AE for ; Mon, 25 Jun 2018 04:16:52 +0000 (UTC) (envelope-from 2yt@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 039CE89BB2 for ; Mon, 25 Jun 2018 04:16:51 +0000 (UTC) (envelope-from 2yt@gmx.com) Received: from xeon.localdomain ([98.127.45.240]) by mail.gmx.com (mrgmx002 [212.227.17.184]) with ESMTPSA (Nemesis) id 0ML72n-1fXa2r3vwf-000Hjg; Mon, 25 Jun 2018 06:16:41 +0200 Subject: Re: 11.2-RC3 regression - networking igb driver To: Jim Pingle , freebsd-stable@freebsd.org References: <2b154303-35f8-df8e-5d2f-ea93b8fdad1d@gmx.com> <2c4e2c6c-ef7a-66a3-e21d-222026c9e88c@pingle.org> From: David Samms <2yt@gmx.com> Message-ID: Date: Sun, 24 Jun 2018 22:16:38 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <2c4e2c6c-ef7a-66a3-e21d-222026c9e88c@pingle.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:S0XuBIZPoKCuO0ZKqrNrfBkI59OT+FLwNhwKtWSUwCc1VQ+XJ1a 54ldofGzHnmkLvWfwirtksT7Ug7P7GPqVFAKzTSUby+zm6WFOFRQuQNa3/3mYf+5p9kCJJt hhoo7YIJoO4qSSpTOeezrTT0lN5DfexCOgqKz00oFIZxgKR9S5Gu8mucrsvbj+FgKPeizn3 cOpzaLoq+D0zC00ImwpjA== X-UI-Out-Filterresults: notjunk:1;V01:K0:O3PGyRwKsAI=:PSlKdKnM/wtFD7AaH1oYX/ dmauDbZVms1jJtoBgiIdzxlWHMXf0YdVpZSvEols2TCUa8vOV+ztOJ2FQKb9z51ILjNy/GwZk f9zlVC4kFYDAgScoPDHrW5KRLKy9uRPSpivm+0PUEjsoPqTShuxvav7Il231AJLd8UpxMpPwF V4HGGiI6vo8gLbl+PvzsmskYFaAb2TqMMr6rm99HdVjQtUEBaeSvNghtiQ8W2QAOtjbbIxkRE NwCxTKRU6nFwMUEom3WlLs4PDHW7kItmFT6CRUVBb0A9JutNDEX4lUXPnC04h8HAcIp/WwYvT 26JgIqA28G1AvEe7/Lt/EmkZVikbQD79Q+0Z6YSdWiMJuMZdeTmsaJ7wl1S9fnci4tkwiAEKI aW3kKW/WezFTIop7fmw9hD4R8dp0uBVbrSIYR9Tp4Wu5P3r/OS1MvZSzvsHWsMEXgAG5Q/a7X FHWyjjf+8YhVXz/JgoF2550P5BWmcvWwqOmvoBygBrAoLJL7t0JBN79+mG0TYB6Q5wpW/Jnqg mDgUsjj9Y9tjNohWXu0FPjchA+Y7JqrUg/I6GK18Mfrtobbg/dld2QKvYAjyQeM14OsxjSHGH nChTNPVmrrX2Ngo7/wGHe68pcI+YRdCfuH9YuJIGgg/z+o13uW2ZLrtGdw3bN6KpCBocmW9rq 23Zr5W0snxh8CnWiamSnCr2DszRhFTdnlR2NTKAnju6HexiZSfWmmqyqhGYJJOaViB6EYOFli sEmS8VPQr4AC4AaTxaqyIcJNhb1d9DXjedWS5/tFrvwRpNI/00x5zw45HjrjCiCmofss5KhGW YXWP7SY X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 04:16:52 -0000 On 06/24/18 18:30, Jim Pingle wrote: > On 6/23/2018 1:27 PM, David Samms wrote: >> There is a regression in 11.2-RC3 that effects the igb driver for Intels >> C2000 SoC I354 Quad GbE Controller >> >> Supermicro A1SRi-2558F >> http://www.supermicro.com/products/motherboard/Atom/X10/A1SRi-2558F.cfm >> >> This server has run 10.x and 11.x fine up till 11.2-RC3. >> >> PROBLEM: >> with 11.2-RC3 the server boots and gets a network connection to the >> cable modem, but the interface (igb0) resets every 4-8 second. The reset >> time appears to be related to network load, but reset withing 10s with >> next to no traffic. I did try swapping cables, but with no effect. With >> each reset the interface successfully obtains an IP address via DHCP, >> works for a few seconds and resets. >> >> Restoring the server to 11.1-RELEASE-p10 resolves the problem. >> >> Any suggestions? > > Does your DHCP server send you an MTU, perhaps? Before the interface > resets, what does its MTU show? > > You might try creating a dhclient.conf that sets "supersede > interface-mtu 0;" and see if that helps. > > The MTU from DHCP feature is new (see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 ) and e1000 > interfaces will reset when applying the MTU. > > Jim P. > Jim, Thank you for your kind reply. I believe you have correctly identified my issue. My ISP is Charter and the modem is a Arris TM822. Running off a live CD of both 11.2-RC3 and 12-CURRENT, I can see that DHCP receives a MTU of 576. In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 they mention that this is an invalid value, and running dhclient -d, I can see that dhclient considers the value invalid and does reset the interface and makes another request. Interestingly, the interface doesn't appear to actually reset until the new address is received. Manually setting the interface with ifconfig/route, I can ping 8.8.8.8 with MTU of 576, but I didn't try any data transfers. Using ifconfig to set MTU 1500 works fine too. All said, I think we have a rather poor DHCP client in 11.2 and a BREAKING change for many casual users. At the very least, dhclient should be complaining of invalid values being received, that would help the user recover quickly. As of now, all you see in the log is that the interface reset. Ideally dhclient would log the invalid MTU as an error but continue as it did in 11.1 with a valid MTU. Again, thank you for taking the time to help me figure out this puzzle. I am on holiday for the next 5 days and will not be on the internet so won't be able to reply for a while. -- David Samms From owner-freebsd-stable@freebsd.org Mon Jun 25 06:56:18 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94FF51027933 for ; Mon, 25 Jun 2018 06:56:18 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 1ED298E023 for ; Mon, 25 Jun 2018 06:56:18 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-oi0-x236.google.com with SMTP id n84-v6so3848945oib.9 for ; Sun, 24 Jun 2018 23:56:18 -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=jO+FtLpdZpf91TXU2+9n5rcJhNoMq9DQdy4zv8vpxh8=; b=uVZcvBlrIhC8MkpK4Cdd/TffYLhP7d4laDjb3psWPanU7bWfI7ZypcTxW3s0ZVpfC6 Dj5QJV6LLEdXBLbX4mdH+UDx8T7SuvhIhHoB7UxNmwZUBrRMTGwaDmKS9+D4uiENOb1o JRx1t0qRlXp+jqY3evl8BtkoT63ktIG3F2pwb33VoMeV6WQEaXjgGYc/3sCAAfolAYUV YjB9t2sIXSyk6YKpjjwJdzTMxalK+yDfj1n2dLOgA3+b43HBUYxD1/uPH2ACxnhdllse N6CS6qJD8YEZ8ZbcI2jaCLhm7m+AOOqT72rroFM3givnoUlfvgtaLN5jI4eW6O11mNzo UoTw== 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=jO+FtLpdZpf91TXU2+9n5rcJhNoMq9DQdy4zv8vpxh8=; b=L0Yy1u63wPoulaBH71dl2Rfilz6bdfjkv6kL8ogRsPHCgkdmiBmObQuupyzGb/z1Hn eE7URqBcC/1VMYmWaXiAtY3alwf8jbfleP+SVJYXZlmLkJwSHoWRkVvKPV/NE6WeUk8+ gTAeDWusTGZfNDBQ+JTYEw5WuCSq7l1tGVrvsmVZGlyjDBIEsVLLXOhTNnh2porOWff+ WaW1ezcHnBLWJrdMN0yOoKgsT03xUwPk/QTHFNhzitPM1woNAK46u1wQFBQiy38AeF3s McypOwXph/v0HKawPxMnHBGAKgEd/t8Haa0rwCWPP9HBFuxFSVwFTDv9VhxRo1uHMPWG uoAg== X-Gm-Message-State: APt69E2yr2y0ONVKr1r6hskgtUlnZEAiWyaStidlau9laCERO8Degsj4 B8Ww0G51jyH4zWV7o9CnCu9nn1YOFrcQZc92e0SL9Q== X-Google-Smtp-Source: AAOMgpeP1YMaLLO9xKtA1i/Gt+Sd8Hu5XAhy3B6NsCq+1zVRZkkTSJ6OcaajORQLdBVzC/nGScHlaUr17Zo49WWj++I= X-Received: by 2002:aca:61d5:: with SMTP id v204-v6mr2067787oib.137.1529909777380; Sun, 24 Jun 2018 23:56:17 -0700 (PDT) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 2002:ac9:2fc3:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 23:55:57 -0700 (PDT) In-Reply-To: <1a730ca1-8c9e-9a9b-72e5-696fb92c8e49@ish.com.au> References: <1a730ca1-8c9e-9a9b-72e5-696fb92c8e49@ish.com.au> From: Jason Tubnor Date: Mon, 25 Jun 2018 16:55:57 +1000 X-Google-Sender-Auth: N15OqpxS0tQoi4VQ0szc3dqEFtE Message-ID: Subject: Re: pf best practices: in or out To: Aristedes Maniatis Cc: freebsd-stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 06:56:18 -0000 Hi Ari, In most cases, block all and then perform conditional pass in on traffic. Depending on your requirements you would conclude your rules with explicit pass out or just a general pass out 'all' (the former in the newer syntax of PF allows you to control queues, operational tags etc - but that won't help you with the current implementation of PF in FreeBSD). DNAT isn't a thing in PF (I assume you were looking how you'd do it if you were coming from Linux). Incoming will manipulate where required when rdr etc. Only outbound needs NAT binding. Cheers, Jason. On 25 June 2018 at 14:12, Aristedes Maniatis wrote: > Hi all > > pf has rules that can operate either 'in' or 'out'. That is, on traffic > entering or leaving an interface. I'm trying to consolidate my rules to > make them easier to understand and update, so it seems a bit pointless to > have the same rules twice. > > Are there any best practices on whether it makes more sense to put rules > on the in or out side? I could bind all the rules to the internet facing > interface and then use "in" for inbound traffic and "out" for outbound. > Does that makes sense? Does it make any difference from a performance point > of view? > > Secondly, where do DNAT rules execute in the sequence? Do they change the > destination IP in between the in and out pass pf rules? > > > I'm not currently subscribed here, so please cc me on replies. > > Thanks > > Ari > > _______________________________________________ > 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" > -- "If my calculations are correct, when this baby hits 88MPH, you're gonna to see some serious shit" - Emmett "Doc" Brown From owner-freebsd-stable@freebsd.org Mon Jun 25 07:19:36 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2584102857D for ; Mon, 25 Jun 2018 07:19:35 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from fish.ish.com.au (ip-2.ish.com.au [203.29.62.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55C098EDA3 for ; Mon, 25 Jun 2018 07:19:34 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from ip-145.ish.com.au ([203.29.62.145]:63238) by fish.ish.com.au with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1fXLmZ-0003hh-0S; Mon, 25 Jun 2018 17:19:27 +1000 X-CTCH-RefID: str=0001.0A150203.5B30977F.0064:SCFSTAT42589845, ss=1, re=-4.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 Subject: Re: pf best practices: in or out To: Jason Tubnor Cc: freebsd-stable References: <1a730ca1-8c9e-9a9b-72e5-696fb92c8e49@ish.com.au> From: Aristedes Maniatis Message-ID: Date: Mon, 25 Jun 2018 17:19:26 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 07:19:36 -0000 Thanks Jason, So in essence, you'd just control everything on the 'pass in'. I'm assuming all traffic originating from the local machine is still hitting a pass in rule on some interface corresponding to the source IP address? DNAT is working fine for me in pf, although I understand it is named rdr. What is the use case for using pass out rules instead of pass in rules? Cheers Ari On 25/6/18 4:55pm, Jason Tubnor wrote: > Hi Ari, > > In most cases, block all and then perform conditional pass in on > traffic.  Depending on your requirements you would conclude your rules > with explicit pass out or just a general pass out 'all' (the former in > the newer syntax of PF allows you to control queues, operational tags > etc - but that won't help you with the current implementation of PF in > FreeBSD). > > DNAT isn't a thing in PF (I assume you were looking how you'd do it if > you were coming from Linux).  Incoming will manipulate where required > when rdr etc. Only outbound needs NAT binding. > > Cheers, > > Jason. > > On 25 June 2018 at 14:12, Aristedes Maniatis > wrote: > > Hi all > > pf has rules that can operate either 'in' or 'out'. That is, on > traffic entering or leaving an interface. I'm trying to > consolidate my rules to make them easier to understand and update, > so it seems a bit pointless to have the same rules twice. > > Are there any best practices on whether it makes more sense to put > rules on the in or out side? I could bind all the rules to the > internet facing interface and then use "in" for inbound traffic > and "out" for outbound. Does that makes sense? Does it make any > difference from a performance point of view? > > Secondly, where do DNAT rules execute in the sequence? Do they > change the destination IP in between the in and out pass pf rules? > > > I'm not currently subscribed here, so please cc me on replies. > > Thanks > > Ari > > _______________________________________________ > 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 > " > > > > > -- > "If my calculations are correct, when this baby hits 88MPH, you're > gonna to see some serious shit" - Emmett "Doc" Brown From owner-freebsd-stable@freebsd.org Mon Jun 25 07:44:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C45F1029582 for ; Mon, 25 Jun 2018 07:44:23 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from fish.ish.com.au (ip-2.ish.com.au [203.29.62.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0521470049 for ; Mon, 25 Jun 2018 07:44:22 +0000 (UTC) (envelope-from prvs=071478b283=ari@ish.com.au) Received: from ip-145.ish.com.au ([203.29.62.145]:63504) by fish.ish.com.au with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1fXMAb-00058N-2A; Mon, 25 Jun 2018 17:44:17 +1000 X-CTCH-RefID: str=0001.0A150209.5B309D51.00EE:SCFSTAT42589845, ss=1, re=-4.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 Subject: Re: pf best practices: in or out To: Walter Parker , freebsd-stable References: <1a730ca1-8c9e-9a9b-72e5-696fb92c8e49@ish.com.au> From: Aristedes Maniatis Message-ID: Date: Mon, 25 Jun 2018 17:44:17 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 25 Jun 2018 07:44:23 -0000 On 25/6/18 5:30pm, Walter Parker wrote: > The use case for pass out rules would be to block local processes on > the box from making external connections to other servers. > This is useful if you don't fully trust users or software running on > your equipment. Also, this would useful to preemptively block ports > that would be useful in DDOS attacks. Ah, then I misunderstood what pass-in and pass-out meant. I thought those words referred to the interface, so it would hit pass-in to the interface even if coming from a local process. In that case I'm better writing all my outbound rules as pass-out so as to equally filter traffic from the internal network and local firewall machine. Ari From owner-freebsd-stable@freebsd.org Mon Jun 25 17:28:21 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F49D1017CBA for ; Mon, 25 Jun 2018 17:28:21 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFBF385CEA for ; Mon, 25 Jun 2018 17:28:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1B5DC21ACE; Mon, 25 Jun 2018 13:28:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 25 Jun 2018 13:28:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=vbK48Bq7Mwe4vcv95G49FnY0pPJA7 NVNBHPlfNs9MCw=; b=OmH+R8qGqrJUzcRBCW1h2PcYYMChbJ9rHKGNfv5bYnWgQ RY+BClDSdWVB0LekH6hFxbMbVW27ftT5nGuPE+44/NfX3cNRHyXXMH1A5u8/gp7l ljpgZHftdz7La/pB8mA9sspxgXgNjorY5tvL4bjAtJIU216DJOfvu8aDz5eOvQ9v Icr0NvOLpBKVG0edSdzrdhFBgN0HMff731HAcvubEDpLk67QqLFeLsvZimAa3QjB DQwZURi1K8NLott7ZblxRB2NpFzqxSK1JgLgAkfmMXtPRlac/QFlUkX9OzXKMXzL HeQRDI1u4O87ez6/MFzfsj0gRRCU7MYPcSk3swcFA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=vbK48B q7Mwe4vcv95G49FnY0pPJA7NVNBHPlfNs9MCw=; b=To4TITyxNt+D2fsWIZKYO+ rMT6Hz1GGSOsmiuDYIJLwOX9xbeB5bTE1Z4YDCh91cPQsCSAQMJ2vprbzTSSWOW9 ixeufVWVP8fZ84YLeg9qehIYpDDmML+ys3D3NENpVJF+n2TFivlHQuwpLMSe3xs0 QLpq1t1xXy65PQdzor53+nbLiJaG48Ehzyt4MKs/uRwL3rnHu0Ukw99H9qJb8fuq SNyRO1IO8P50ocEo7wnrbjyZpEmnk7ygtbRVvqR+ZZvBHbZdvWZJ5ILChlbZuuuH x6o0GXAUQOPV9vHE1yTsELzxV6vX4+ioedJB7o4IovRq7WaBij2DWi52ovewGHPw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 4DE1D10261; Mon, 25 Jun 2018 13:28:19 -0400 (EDT) Subject: Re: lightly loaded system eats swap space To: Shane Ambler , Jeremy Chadwick , freebsd-stable@freebsd.org References: <20180619172936.GA24967@icarus.home.lan> <95c74868-7ba6-9077-4e24-6d685078aee6@ShaneWare.Biz> From: tech-lists Organization: none Message-ID: Date: Mon, 25 Jun 2018 18:28:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <95c74868-7ba6-9077-4e24-6d685078aee6@ShaneWare.Biz> 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.26 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, 25 Jun 2018 17:28:21 -0000 On 20/06/2018 06:08, Shane Ambler wrote: > This review is aiming to fix this - > https://reviews.freebsd.org/D7538 > > I have been running the patch on stable/11 and after eight days uptime I > still have zero swap in use, I can't recall a time in the last few years > that I have had no swap usage past the first hour or two uptime. will this work on a recent 12-current? thanks, -- J. From owner-freebsd-stable@freebsd.org Tue Jun 26 09:25:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BD62101DC5F for ; Tue, 26 Jun 2018 09:25:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A4C908915A for ; Tue, 26 Jun 2018 09:25:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6918D101DC57; Tue, 26 Jun 2018 09:25:31 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 534D8101DC56 for ; Tue, 26 Jun 2018 09:25:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDE1D89151 for ; Tue, 26 Jun 2018 09:25:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 15D881CD1D for ; Tue, 26 Jun 2018 09:25:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5Q9PTba073052 for ; Tue, 26 Jun 2018 09:25:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5Q9PTv0073051 for stable@FreeBSD.org; Tue, 26 Jun 2018 09:25:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic Date: Tue, 26 Jun 2018 09:25:28 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: me@janh.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 09:25:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228535 me@janh.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me@janh.de --- Comment #9 from me@janh.de --- I have hit this problem, too. For me, it is different than previous problems with kernel modules from por= ts after minor FreeBSD version updates: There were modules that would not load, but very rarely an old module would lead to a panic. I have vboxdrv_load=3D"YES" in /boot/loader.conf and I could not immediatel= y tell what caused the panic. Obviously, single user mode would not work, either, = but loading the old kernel did. Having freebsd-update print a warning in the end to update ports with kernel modules would not help in this case, either: The panic already happens after installing the kernel and rebooting and you cannot even install the userlan= d. If there was such a warning, it would have to be with the first prompt for a reboot. Rebuilding ports at that time would not be the best idea, either, s= ince the userland is still old. The message would have to tell you to disable everything from ports in /boot/loader.conf, /etc/rc.conf|kld_list, and simi= lar places. Besides emulators/virtualbox-ose-kmod, I also had to rebuild x11/nvidia-dri= ver, but it was nicer: There was no crash, xorg simply would not start. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Tue Jun 26 10:31:29 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89F94101FF3C for ; Tue, 26 Jun 2018 10:31:29 +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 276E18B14A; Tue, 26 Jun 2018 10:31:29 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fXlFu-0009Fr-8P; Tue, 26 Jun 2018 10:31:26 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fXlFu-0000rF-3y; Tue, 26 Jun 2018 11:31:26 +0100 To: eric@vangyzen.net, mike@sentex.net, petefrench@ingresso.co.uk, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, freebsd-stable@freebsd.org, freebsd@hda3.com, kostikbel@gmail.com In-Reply-To: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> Message-Id: From: Pete French Date: Tue, 26 Jun 2018 11:31:26 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 10:31:29 -0000 > On 06/18/2018 09:34, Pete French wrote: > > Preseumably in the slightly longer term these workarounds go into the > > actual kernel if it detects Ryzen ? > > Yes, Kostik said he would code this into the kernel after he gets enough > feedback. So, I've been running with the sysctl and cputl fixes from https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html for a couple of weeks now, with all the default settings back on (including SMT) and it now completely stable, so consider this one more point of feedback for incorporating thois in the the kernel :-) cheers, -pete. From owner-freebsd-stable@freebsd.org Tue Jun 26 11:29:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6B0C1021CFF for ; Tue, 26 Jun 2018 11:29:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DB618C8F1; Tue, 26 Jun 2018 11:29:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5QBTJqw017102; Tue, 26 Jun 2018 14:29:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5QBTJqw017102 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5QBTJXF017101; Tue, 26 Jun 2018 14:29:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 26 Jun 2018 14:29:19 +0300 From: Konstantin Belousov To: Pete French Cc: eric@vangyzen.net, mike@sentex.net, truckman@FreeBSD.org, avg@freebsd.org, freebsd-stable@freebsd.org, freebsd@hda3.com Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <20180626112919.GK2430@kib.kiev.ua> References: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 11:29:33 -0000 On Tue, Jun 26, 2018 at 11:31:26AM +0100, Pete French wrote: > > On 06/18/2018 09:34, Pete French wrote: > > > Preseumably in the slightly longer term these workarounds go into the > > > actual kernel if it detects Ryzen ? > > > > Yes, Kostik said he would code this into the kernel after he gets enough > > feedback. > > So, I've been running with the sysctl and cputl fixes from > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > for a couple of weeks now, with all the default settings back on (including > SMT) and it now completely stable, so consider this one more point of feedback If you run without the script, with the same settings, do you experience problems ? Also, please show the 100 first lines of the verbose boot dmesg on this machine. From owner-freebsd-stable@freebsd.org Tue Jun 26 12:32:05 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42FA010247CA for ; Tue, 26 Jun 2018 12:32:05 +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 D1F808E8F0; Tue, 26 Jun 2018 12:32:04 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fXn8b-000BGG-4Q; Tue, 26 Jun 2018 12:32:01 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fXn8b-0000se-1B; Tue, 26 Jun 2018 13:32:01 +0100 To: kostikbel@gmail.com, petefrench@ingresso.co.uk Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org In-Reply-To: <20180626112919.GK2430@kib.kiev.ua> Message-Id: From: Pete French Date: Tue, 26 Jun 2018 13:32:01 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 12:32:05 -0000 > If you run without the script, with the same settings, do you experience > problems ? I have not tried this since the last BIOPS update which brought with it the latest AEGSA version. Previously the machine would lock uop if I enabled SMT though which is why looking at those settings and cross referencing them to the erata was very interesting. I just rebooted the machine to get you the log, and am going to run without applyingthose fixes for the rest of the week to see how it goes though. Will let you know one way or the other on Friday, and will do my best to lock it up before then. > Also, please show the 100 first lines of the verbose boot dmesg on this > machine. the dmesg wraps around if I boot verbosely, but heres the contnets of /var/log/messages from the time it starts to where it stops talking about CPU specific stuff... if you need something else then let me know - this is an easy machine to reboot and play about with. -pete. Jun 26 13:13:26 dilbert kernel: Table 'FACP' at 0xdd0fb6b8 Jun 26 13:13:26 dilbert kernel: Table 'APIC' at 0xdd0fb7d0 Jun 26 13:13:26 dilbert kernel: APIC: Found table at 0xdd0fb7d0 Jun 26 13:13:26 dilbert kernel: APIC: Using the MADT enumerator. Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 0 ACPI ID 1: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 0 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 1 ACPI ID 2: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 1 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 2 ACPI ID 3: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 2 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 3 ACPI ID 4: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 3 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 4 ACPI ID 5: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 4 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 5 ACPI ID 6: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 5 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 6 ACPI ID 7: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 6 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 7 ACPI ID 8: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 7 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 8 ACPI ID 9: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 8 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 9 ACPI ID 10: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 9 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 10 ACPI ID 11: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 10 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 11 ACPI ID 12: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 11 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 12 ACPI ID 13: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 12 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 13 ACPI ID 14: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 13 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 14 ACPI ID 15: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 14 (AP) Jun 26 13:13:26 dilbert kernel: MADT: Found CPU APIC ID 15 ACPI ID 16: enabled Jun 26 13:13:26 dilbert kernel: SMP: Added CPU 15 (AP) Jun 26 13:13:26 dilbert kernel: Copyright (c) 1992-2018 The FreeBSD Project. Jun 26 13:13:26 dilbert kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jun 26 13:13:26 dilbert kernel: The Regents of the University of California. All rights reserved. Jun 26 13:13:26 dilbert kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jun 26 13:13:26 dilbert kernel: FreeBSD 11.2-STABLE #0 r335659: Tue Jun 26 10:47:47 BST 2018 Jun 26 13:13:26 dilbert kernel: petefrench@dilbert.london-internal.ingresso.co.uk:/usr/obj/usr/src/sys/GENERIC amd64 Jun 26 13:13:26 dilbert kernel: FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) Jun 26 13:13:26 dilbert kernel: Table 'FACP' at 0xdd0fb6b8 Jun 26 13:13:26 dilbert kernel: Table 'APIC' at 0xdd0fb7d0 Jun 26 13:13:26 dilbert kernel: Table 'FPDT' at 0xdd0fb8b0 Jun 26 13:13:26 dilbert kernel: Table 'FIDT' at 0xdd0fb8f8 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd0fb998 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd104630 Jun 26 13:13:26 dilbert kernel: Table 'CRAT' at 0xdd106948 Jun 26 13:13:26 dilbert kernel: Table 'CDIT' at 0xdd107898 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd1078c8 Jun 26 13:13:26 dilbert kernel: Table 'MCFG' at 0xdd10a660 Jun 26 13:13:26 dilbert kernel: Table 'HPET' at 0xdd10a6a0 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd10a6d8 Jun 26 13:13:26 dilbert kernel: Table 'UEFI' at 0xdd10a700 Jun 26 13:13:26 dilbert kernel: Table 'IVRS' at 0xdd10a748 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd10a818 Jun 26 13:13:26 dilbert kernel: Table 'SSDT' at 0xdd10a910 Jun 26 13:13:26 dilbert kernel: Table 'WSMT' at 0xdd10c358 Jun 26 13:13:26 dilbert kernel: ACPI: No SRAT table found Jun 26 13:13:26 dilbert kernel: PPIM 0: PA=0xa0000, VA=0xffffffff82810000, size=0x10000, mode=0 Jun 26 13:13:26 dilbert kernel: VT(vga): resolution 640x480 Jun 26 13:13:26 dilbert kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff826bd000. Jun 26 13:13:26 dilbert kernel: Preloaded boot_entropy_cache "/boot/entropy" at 0xffffffff826c6148. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/aesni.ko" at 0xffffffff826c61a0. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/cryptodev.ko" at 0xffffffff826c6888. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/geom_eli.ko" at 0xffffffff826c6f38. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/fuse.ko" at 0xffffffff826c75e8. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/sem.ko" at 0xffffffff826c7c90. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/amdtemp.ko" at 0xffffffff826c82b8. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/amdsmn.ko" at 0xffffffff826c8860. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/linux.ko" at 0xffffffff826c8e08. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/linux_common.ko" at 0xffffffff826c96f0. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/zfs.ko" at 0xffffffff826c9e20. Jun 26 13:13:26 dilbert kernel: Preloaded elf obj module "/boot/kernel/opensolaris.ko" at 0xffffffff826ca648. Jun 26 13:13:26 dilbert kernel: Calibrating TSC clock ... TSC clock: 3000069750 Hz Jun 26 13:13:26 dilbert kernel: CPU: AMD Ryzen 7 1700 Eight-Core Processor (3000.07-MHz K8-class CPU) Jun 26 13:13:26 dilbert kernel: Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Jun 26 13:13:26 dilbert kernel: Features=0x178bfbff Jun 26 13:13:26 dilbert kernel: Features2=0x7ed8320b Jun 26 13:13:26 dilbert kernel: AMD Features=0x2e500800 Jun 26 13:13:26 dilbert kernel: AMD Features2=0x35c233ff Jun 26 13:13:26 dilbert kernel: Structured Extended Features=0x209c01a9 Jun 26 13:13:26 dilbert kernel: XSAVE Features=0xf Jun 26 13:13:26 dilbert kernel: AMD Extended Feature Extensions ID EBX=0x1007 Jun 26 13:13:26 dilbert kernel: SVM: Features=0x1bcff,PauseFilterThreshold,AVIC> Jun 26 13:13:26 dilbert kernel: Revision=1, ASIDs=32768 Jun 26 13:13:26 dilbert kernel: TSC: P-state invariant, performance statistics Jun 26 13:13:26 dilbert kernel: L1 2MB data TLB: 64 entries, fully associative Jun 26 13:13:26 dilbert kernel: L1 2MB instruction TLB: 64 entries, fully associative Jun 26 13:13:26 dilbert kernel: L1 4KB data TLB: 64 entries, fully associative Jun 26 13:13:26 dilbert kernel: L1 4KB instruction TLB: 64 entries, fully associative Jun 26 13:13:26 dilbert kernel: L1 data cache: 32 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative Jun 26 13:13:26 dilbert kernel: L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 4-way associative Jun 26 13:13:26 dilbert kernel: L2 2MB data TLB: 1536 entries, 2-way associative Jun 26 13:13:26 dilbert kernel: L2 2MB instruction TLB: 1024 entries, 2-way associative Jun 26 13:13:26 dilbert kernel: L2 4KB data TLB: 1536 entries, 8-way associative Jun 26 13:13:26 dilbert kernel: L2 4KB instruction TLB: 1536 entries, 8-way associative Jun 26 13:13:26 dilbert kernel: L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative Jun 26 13:13:26 dilbert kernel: real memory = 8589934592 (8192 MB) Jun 26 13:13:26 dilbert kernel: Physical memory chunk(s): Jun 26 13:13:26 dilbert kernel: 0x0000000000010000 - 0x0000000000099fff, 565248 bytes (138 pages) Jun 26 13:13:26 dilbert kernel: 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) Jun 26 13:13:26 dilbert kernel: 0x0000000002800000 - 0x0000000003ffffff, 25165824 bytes (6144 pages) Jun 26 13:13:26 dilbert kernel: 0x000000000400a000 - 0x0000000009d7ffff, 98000896 bytes (23926 pages) Jun 26 13:13:26 dilbert kernel: 0x000000000a000000 - 0x000000000affffff, 16777216 bytes (4096 pages) Jun 26 13:13:26 dilbert kernel: 0x000000000b020000 - 0x00000000dce94fff, 3521597440 bytes (859765 pages) Jun 26 13:13:26 dilbert kernel: 0x00000000dcffd000 - 0x00000000dd0f3fff, 1011712 bytes (247 pages) Jun 26 13:13:26 dilbert kernel: 0x00000000de665000 - 0x00000000deffffff, 10072064 bytes (2459 pages) Jun 26 13:13:26 dilbert kernel: 0x0000000100000000 - 0x0000000211b2afff, 4591890432 bytes (1121067 pages) Jun 26 13:13:26 dilbert kernel: avail memory = 8208781312 (7828 MB) Jun 26 13:13:26 dilbert kernel: Event timer "LAPIC" quality 600 Jun 26 13:13:26 dilbert kernel: LAPIC: ipi_wait() us multiplier 13 (r 22217700 tsc 3000069750) Jun 26 13:13:26 dilbert kernel: ACPI APIC Table: Jun 26 13:13:26 dilbert kernel: Package ID shift: 4 Jun 26 13:13:26 dilbert kernel: L3 cache ID shift: 3 Jun 26 13:13:26 dilbert kernel: L2 cache ID shift: 1 Jun 26 13:13:26 dilbert kernel: L1 cache ID shift: 1 Jun 26 13:13:26 dilbert kernel: Core ID shift: 1 Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 2 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 4 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 6 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 8 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 10 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 12 as a target Jun 26 13:13:26 dilbert kernel: INTR: Adding local APIC 14 as a target Jun 26 13:13:26 dilbert kernel: FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs Jun 26 13:13:26 dilbert kernel: FreeBSD/SMP: 1 package(s) x 8 core(s) x 2 hardware threads Jun 26 13:13:26 dilbert kernel: Package HW ID = 0 (0) Jun 26 13:13:26 dilbert kernel: Core HW ID = 0 (0) Jun 26 13:13:26 dilbert kernel: CPU0 (BSP): APIC ID: 0 (0) Jun 26 13:13:26 dilbert kernel: CPU1 (AP/HT): APIC ID: 1 (0x1) Jun 26 13:13:26 dilbert kernel: Core HW ID = 1 (0x1) Jun 26 13:13:26 dilbert kernel: CPU2 (AP): APIC ID: 2 (0x2) Jun 26 13:13:26 dilbert kernel: CPU3 (AP/HT): APIC ID: 3 (0x3) Jun 26 13:13:26 dilbert kernel: Core HW ID = 2 (0x2) Jun 26 13:13:26 dilbert kernel: CPU4 (AP): APIC ID: 4 (0x4) Jun 26 13:13:26 dilbert kernel: CPU5 (AP/HT): APIC ID: 5 (0x5) Jun 26 13:13:26 dilbert kernel: Core HW ID = 3 (0x3) Jun 26 13:13:26 dilbert kernel: CPU6 (AP): APIC ID: 6 (0x6) Jun 26 13:13:26 dilbert kernel: CPU7 (AP/HT): APIC ID: 7 (0x7) Jun 26 13:13:26 dilbert kernel: Core HW ID = 4 (0x4) Jun 26 13:13:26 dilbert kernel: CPU8 (AP): APIC ID: 8 (0x8) Jun 26 13:13:26 dilbert kernel: CPU9 (AP/HT): APIC ID: 9 (0x9) Jun 26 13:13:26 dilbert kernel: Core HW ID = 5 (0x5) Jun 26 13:13:26 dilbert kernel: CPU10 (AP): APIC ID: 10 (0xa) Jun 26 13:13:26 dilbert kernel: CPU11 (AP/HT): APIC ID: 11 (0xb) Jun 26 13:13:26 dilbert kernel: Core HW ID = 6 (0x6) Jun 26 13:13:26 dilbert kernel: CPU12 (AP): APIC ID: 12 (0xc) Jun 26 13:13:26 dilbert kernel: CPU13 (AP/HT): APIC ID: 13 (0xd) Jun 26 13:13:26 dilbert kernel: Core HW ID = 7 (0x7) Jun 26 13:13:26 dilbert kernel: CPU14 (AP): APIC ID: 14 (0xe) Jun 26 13:13:26 dilbert kernel: CPU15 (AP/HT): APIC ID: 15 (0xf) Jun 26 13:13:26 dilbert kernel: APIC: CPU 0 has ACPI ID 1 Jun 26 13:13:26 dilbert kernel: APIC: CPU 1 has ACPI ID 2 Jun 26 13:13:26 dilbert kernel: APIC: CPU 2 has ACPI ID 3 Jun 26 13:13:26 dilbert kernel: APIC: CPU 3 has ACPI ID 4 Jun 26 13:13:26 dilbert kernel: APIC: CPU 4 has ACPI ID 5 Jun 26 13:13:26 dilbert kernel: APIC: CPU 5 has ACPI ID 6 Jun 26 13:13:26 dilbert kernel: APIC: CPU 6 has ACPI ID 7 Jun 26 13:13:26 dilbert kernel: APIC: CPU 7 has ACPI ID 8 Jun 26 13:13:26 dilbert kernel: APIC: CPU 8 has ACPI ID 9 Jun 26 13:13:26 dilbert kernel: APIC: CPU 9 has ACPI ID 10 Jun 26 13:13:26 dilbert kernel: APIC: CPU 10 has ACPI ID 11 Jun 26 13:13:26 dilbert kernel: APIC: CPU 11 has ACPI ID 12 Jun 26 13:13:26 dilbert kernel: APIC: CPU 12 has ACPI ID 13 Jun 26 13:13:26 dilbert kernel: APIC: CPU 13 has ACPI ID 14 Jun 26 13:13:26 dilbert kernel: APIC: CPU 14 has ACPI ID 15 Jun 26 13:13:26 dilbert kernel: APIC: CPU 15 has ACPI ID 16 Jun 26 13:13:26 dilbert kernel: x86bios: IVT 0x000000-0x0004ff at 0xfffff80000000000 Jun 26 13:13:26 dilbert kernel: x86bios: SSEG 0x098000-0x098fff at 0xfffffe01ecfe8000 Jun 26 13:13:26 dilbert kernel: x86bios: EBDA 0x09d000-0x09ffff at 0xfffff8000009d000 Jun 26 13:13:26 dilbert kernel: x86bios: ROM 0x0a0000-0x0fefff at 0xfffff800000a0000 Jun 26 13:13:26 dilbert kernel: Pentium Pro MTRR support enabled Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 0 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 1 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 2 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 3 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 4 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 5 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 6 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 7 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 8 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 9 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 10 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 11 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 12 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 13 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 14 Jun 26 13:13:26 dilbert kernel: ULE: setup cpu 15 Jun 26 13:13:26 dilbert kernel: ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA) Jun 26 13:13:26 dilbert kernel: ACPI: XSDT 0x00000000DD0F4098 0000AC (v01 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: ACPI: FACP 0x00000000DD0FB6B8 000114 (v06 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) Jun 26 13:13:26 dilbert kernel: ACPI: DSDT 0x00000000DD0F41D8 0074DC (v02 ALASKA A M I 01072009 INTL 20120913) Jun 26 13:13:26 dilbert kernel: ACPI: FACS 0x00000000DD4BCE00 000040 Jun 26 13:13:26 dilbert kernel: ACPI: APIC 0x00000000DD0FB7D0 0000DE (v03 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: ACPI: FPDT 0x00000000DD0FB8B0 000044 (v01 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: ACPI: FIDT 0x00000000DD0FB8F8 00009C (v01 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD0FB998 008C98 (v02 AMD AMD ALIB 00000002 MSFT 04000000) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD104630 002314 (v01 AMD AMD CPU 00000001 AMD 00000001) Jun 26 13:13:26 dilbert kernel: ACPI: CRAT 0x00000000DD106948 000F50 (v01 AMD AMD CRAT 00000001 AMD 00000001) Jun 26 13:13:26 dilbert kernel: ACPI: CDIT 0x00000000DD107898 000029 (v01 AMD AMD CDIT 00000001 AMD 00000001) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD1078C8 002D94 (v01 AMD AMD AOD 00000001 INTL 20120913) Jun 26 13:13:26 dilbert kernel: ACPI: MCFG 0x00000000DD10A660 00003C (v01 ALASKA A M I 01072009 MSFT 00010013) Jun 26 13:13:26 dilbert kernel: ACPI: HPET 0x00000000DD10A6A0 000038 (v01 ALASKA A M I 01072009 AMI 00000005) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD10A6D8 000024 (v01 AMDFCH FCHZP 00001000 INTL 20120913) Jun 26 13:13:26 dilbert kernel: ACPI: UEFI 0x00000000DD10A700 000042 (v01 00000000 00000000) Jun 26 13:13:26 dilbert kernel: ACPI: IVRS 0x00000000DD10A748 0000D0 (v02 AMD AMD IVRS 00000001 AMD 00000000) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD10A818 0000F8 (v01 AMD AMD PT 00001000 INTL 20120913) Jun 26 13:13:26 dilbert kernel: ACPI: SSDT 0x00000000DD10A910 001A41 (v01 AMD AmdTable 00000001 INTL 20120913) Jun 26 13:13:26 dilbert kernel: ACPI: WSMT 0x00000000DD10C358 000028 (v01 ALASKA A M I 01072009 AMI 00010013) Jun 26 13:13:26 dilbert kernel: MADT: Found IO APIC ID 17, Interrupt 0 at 0xfec00000 Jun 26 13:13:26 dilbert kernel: ioapic0: Changing APIC ID to 17 Jun 26 13:13:26 dilbert kernel: ioapic0: ver 0x21 maxredir 0x17 Jun 26 13:13:26 dilbert kernel: ioapic0: Routing external 8259A's -> intpin 0 Jun 26 13:13:26 dilbert kernel: MADT: Found IO APIC ID 18, Interrupt 24 at 0xfec01000 Jun 26 13:13:26 dilbert kernel: ioapic1: Changing APIC ID to 18 Jun 26 13:13:26 dilbert kernel: ioapic1: ver 0x21 maxredir 0x1f Jun 26 13:13:26 dilbert kernel: lapic: Routing NMI -> LINT1 Jun 26 13:13:26 dilbert kernel: lapic: LINT1 trigger: edge Jun 26 13:13:26 dilbert kernel: lapic: LINT1 polarity: high Jun 26 13:13:26 dilbert kernel: MADT: Interrupt override: source 0, irq 2 Jun 26 13:13:26 dilbert kernel: ioapic0: Routing IRQ 0 -> intpin 2 Jun 26 13:13:26 dilbert kernel: MADT: Interrupt override: source 9, irq 9 Jun 26 13:13:26 dilbert kernel: ioapic0: intpin 9 trigger: level Jun 26 13:13:26 dilbert kernel: ioapic0: intpin 9 polarity: low Jun 26 13:13:26 dilbert kernel: ioapic0 irqs 0-23 on motherboard Jun 26 13:13:26 dilbert kernel: ioapic1 irqs 24-55 on motherboard Jun 26 13:13:26 dilbert kernel: lapic: Divisor 2, Frequency 50001164 Hz Jun 26 13:13:26 dilbert kernel: cpu0 BSP: Jun 26 13:13:26 dilbert kernel: ID: 0x00000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #15 Launched! Jun 26 13:13:26 dilbert kernel: cpu15 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0f000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #13 Launched! Jun 26 13:13:26 dilbert kernel: cpu13 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0d000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #9 Launched! Jun 26 13:13:26 dilbert kernel: cpu9 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x09000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #7 Launched! Jun 26 13:13:26 dilbert kernel: cpu7 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x07000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #3 Launched! Jun 26 13:13:26 dilbert kernel: cpu3 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x03000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #8 Launched! Jun 26 13:13:26 dilbert kernel: cpu8 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x08000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #11 Launched! Jun 26 13:13:26 dilbert kernel: cpu11 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0b000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #4 Launched! Jun 26 13:13:26 dilbert kernel: cpu4 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x04000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #2 Launched! Jun 26 13:13:26 dilbert kernel: cpu2 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x02000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #5 Launched! Jun 26 13:13:26 dilbert kernel: cpu5 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x05000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #1 Launched! Jun 26 13:13:26 dilbert kernel: cpu1 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #12 Launched! Jun 26 13:13:26 dilbert kernel: cpu12 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0c000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #14 Launched! Jun 26 13:13:26 dilbert kernel: cpu14 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0e000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #10 Launched! Jun 26 13:13:26 dilbert kernel: cpu10 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x0a000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: AP CPU #6 Launched! Jun 26 13:13:26 dilbert kernel: cpu6 AP: Jun 26 13:13:26 dilbert kernel: ID: 0x06000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Jun 26 13:13:26 dilbert kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Jun 26 13:13:26 dilbert kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 Jun 26 13:13:26 dilbert kernel: AMD ext features: 0x00040007 Jun 26 13:13:26 dilbert kernel: AMD elvt0: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt1: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt2: 0x00010000 Jun 26 13:13:26 dilbert kernel: AMD elvt3: 0x00010000 Jun 26 13:13:26 dilbert kernel: SMP: passed TSC synchronization test Jun 26 13:13:26 dilbert kernel: TSC timecounter discards lower 1 bit(s) Jun 26 13:13:26 dilbert kernel: Timecounter "TSC-low" frequency 1500034875 Hz quality 1000 Jun 26 13:13:26 dilbert kernel: snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] Jun 26 13:13:26 dilbert kernel: feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 Jun 26 13:13:26 dilbert kernel: random: entropy device external interface From owner-freebsd-stable@freebsd.org Tue Jun 26 14:23:09 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24AB01028D54 for ; Tue, 26 Jun 2018 14:23:09 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CC2372874 for ; Tue, 26 Jun 2018 14:23:08 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lj1-x233.google.com with SMTP id t22-v6so1757477ljc.11 for ; Tue, 26 Jun 2018 07:23:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=23OOY63LRpyMFNwg1nFwTfID2ZsxQMsK8Ev1UWcVQ+o=; b=P/rY6EnrgW6D8oUa5OkCVyF24KdW2PjPiPGaBIYoYgn7Gao9ZdcWxOHMSFuQjfRYPH Gk9Pa9D4xkPWwjQT3kuKMGkzRJtM+gMqqW9iE1u/E82jUuErUfef5jnA2Zqw9iO/LfN+ mO/WdoU/nDzOGgnm3dpJnL6Y7RC4cXo9Gpj/SZ54jkdH+u3TNlhKFAqEjKWWMRKA2Zma H6PoodVem3l172Os5JpYax0GlpFzkdzi1kosnTcWAlrVyQMMb0AXWXFF85lH1+qgRtlT mH096/WG9Glt7E0l87EVw5Y3A2r8aEvbCrDmrq7Fz2HHU+7As5myRZXCu3J905Hvgzj5 KVwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=23OOY63LRpyMFNwg1nFwTfID2ZsxQMsK8Ev1UWcVQ+o=; b=RPFW1DjcINGjDh1ohn3O/HbHDCKxkciMYGMhMivbARATbPlIOpOkdUHj991a+bRgI5 BPU/Lo1xUp63YgWXyNU6Qv9D12VzsfZToEORHIjSIza8V82ZCw87ftIw8UA0+JunRAAE R7u4hBnvsmkQCwIsJuD4Itb3LpXqy9pL4uG/UEkGLO8fxG9TPsI9iG/K5rgXQP8nGeRU G9GLG2d2bDarbW0zuWBaLy835axOAd2Qboh4i3FRNaPq+OzjDiH6YnqM/glIm2DIh3NH MSkQPiCcBvj3SRrn4iEQPRtx8lE4ndEZ9YIN4aJa02PPayQsoSHteIioRLSVePqas4XE QAVQ== X-Gm-Message-State: APt69E05b9b+L7Lk/5Wy3+qZjpaqr9DCEiiQNgA10N8o6e0uWjIKboOd ajK5A+KYNaOGOv/PS8FuVovfho9fdblzOMRxSg+hyg== X-Google-Smtp-Source: ADUXVKLgtFjDd7BUSVQdsRzRfxDGxDZqqJccFip459usLwWFSsm/dM7cjHNahoY3bqYk6+WGhXIrKa5jj4B5KcSW0so= X-Received: by 2002:a2e:560d:: with SMTP id k13-v6mr1305477ljb.124.1530022987152; Tue, 26 Jun 2018 07:23:07 -0700 (PDT) MIME-Version: 1.0 References: <20180626112919.GK2430@kib.kiev.ua> In-Reply-To: From: Freddie Cash Date: Tue, 26 Jun 2018 07:22:55 -0700 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French Cc: FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 14:23:09 -0000 On Tue, Jun 26, 2018, 5:33 AM Pete French, wrote: > > > Also, please show the 100 first lines of the verbose boot dmesg on this > > machine. > > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU specific stuff... if you need something else then > let me know - this is an easy machine to reboot and play about with. > /var/run/dmesg.boot is there for this various reason (dmesg buffer rolling over). :) It's the dmesg output for the current boot. Cheers, Freddie > From owner-freebsd-stable@freebsd.org Tue Jun 26 14:42:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4857D102979A for ; Tue, 26 Jun 2018 14:42:32 +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 E330C73600 for ; Tue, 26 Jun 2018 14:42:31 +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.89 (FreeBSD)) (envelope-from ) id 1fXpAr-000Cgk-0L; Tue, 26 Jun 2018 14:42:29 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Freddie Cash Cc: FreeBSD Stable References: <20180626112919.GK2430@kib.kiev.ua> From: Pete French Message-ID: Date: Tue, 26 Jun 2018 15:42:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 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, 26 Jun 2018 14:42:32 -0000 Gah! I my memory said it was /var/boot - so close :-) Thanks! On 26/06/2018 15:22, Freddie Cash wrote: > > > On Tue, Jun 26, 2018, 5:33 AM Pete French, > wrote: > > > > Also, please show the 100 first lines of the verbose boot dmesg > on this > > machine. > > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU specific stuff... if you need something else then > let me know - this is an easy machine to reboot and play about with. > > > /var/run/dmesg.boot is there for this various reason (dmesg buffer > rolling over). :) It's the dmesg output for the current boot. > > Cheers, > Freddie > From owner-freebsd-stable@freebsd.org Tue Jun 26 18:05:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F083F100787F for ; Tue, 26 Jun 2018 18:05:31 +0000 (UTC) (envelope-from bounce@ims3.isendservice.com.br) Received: from ims3.isendservice.com.br (ims3.isendservice.com.br [54.232.186.7]) by mx1.freebsd.org (Postfix) with ESMTP id 6D01A7BD93 for ; Tue, 26 Jun 2018 18:05:31 +0000 (UTC) (envelope-from bounce@ims3.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims3.isendservice.com.br (Postfix) with ESMTP id 195C942B2C for ; Tue, 26 Jun 2018 15:05:19 -0300 (BRT) Date: Tue, 26 Jun 2018 15:05:19 -0300 (BRT) From: SENAI | FATEC - Faculdade SENAI Reply-To: posgraduacao@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <388091599.459823.1530036319853.JavaMail.root@ims3> Subject: =?ISO-8859-1?Q?P=F3s-Gradua=E7=E3o_SENAI_|_FATEC?= =?ISO-8859-1?Q?_-_MBA_em_Gest=E3o_de_Projetos?= bounce-key: <2420-22522874-2174889> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 18:05:32 -0000 From owner-freebsd-stable@freebsd.org Tue Jun 26 18:43:08 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6623A1010F1C; Tue, 26 Jun 2018 18:43:08 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org (gritton.org [199.192.165.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gritton.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 05BBA7DD09; Tue, 26 Jun 2018 18:43:07 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org ([127.0.0.131]) by gritton.org (8.15.2/8.15.2) with ESMTP id w5QIgqIK007004; Tue, 26 Jun 2018 12:42:52 -0600 (MDT) (envelope-from jamie@freebsd.org) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Jun 2018 12:42:52 -0600 From: James Gritton To: Eitan Adler Cc: bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable Subject: Re: jail related inconsistencies in FreeBSD tools parameters In-Reply-To: References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> <51718e96f63175e997cb8268381d1070@freebsd.org> Message-ID: <8b11953ce292aff0bc60298e2e7613d6@freebsd.org> X-Sender: jamie@freebsd.org User-Agent: Roundcube Webmail/1.3.6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 18:43:08 -0000 On 2018-06-23 12:58, Eitan Adler wrote: > On 23 June 2018 at 08:50, James Gritton wrote: >> On 2018-06-23 09:45, Eitan Adler wrote: >>> >>> On 23 June 2018 at 08:30, James Gritton wrote: >>>> >>>> On 2018-06-22 16:03, Miroslav Lachman wrote: >>>>> >>>>> >>>>> Chris H wrote on 2018/06/22 23:46: >>>>>> >>>>>> >>>>>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >>>>>> <000.fbsd@quip.cz> >>>>>> said >>>>>> >>>>>>> I don't know if it is better to discuss it in jail@ or stable@ >>>>>>> list so >>>>>>> a >>>>>>> do cross-post. >>>>>>> >>>>>>> FreeBSD has many jail aware utilities but they are inconsistent >>>>>>> in >>>>>>> taking JID as parameter. >>>>>>> >>>>>>> For example "sockstat" takes -j JID "Show only sockets belonging >>>>>>> to >>>>>>> the >>>>>>> specified jail ID" and it means numeric ID only. >>>>>>> On the other hand "ps" takes -J JID "This may be either the jid >>>>>>> or >>>>>>> name >>>>>>> of the jail. Use -J 0 to display only host processes." >>>>>>> The same apply for "top", it understands jid as a number or name >>>>>>> of >>>>>>> the >>>>>>> jail too. >>>>>>> Then again "cpuset" takes only numerical ID of the jail... >>>>>>> >>>>>>> Shouldn't it be consistent across all FreeBSD base utilities so >>>>>>> all of >>>>>>> them can use numerical ID and name? >>>>>> >>>>>> >>>>>> Good idea! Are you offering to create a patch? ;-) >>>>>> It'd be my guess that given they weren't all created at the same >>>>>> time, >>>>>> nor >>>>>> the same individual; that (quite probably?) the "jail" additions >>>>>> were >>>>>> also >>>>>> added at different times, and by different people. So I'd imagine >>>>>> that >>>>>> unless someone with a commit bit decides one day they'd like to >>>>>> take >>>>>> that >>>>>> on. Someone(tm) maybe you? will need to propose a patch. :-) >>>>> >>>>> >>>>> >>>>> If I can understand C sources I will create the patch by myself >>>>> instead of just posting here. Unfortunately I am able to code in >>>>> sh, >>>>> php and a bit of javascript and perl but no C. :) >>>>> >>>>> Miroslav Lachman >>>> >>>> >>>> >>>> Sure, a PR would be handy for this - it's a pretty simple thing to >>>> add, >>>> and >>>> consistency would indeed be a good move. >>> >>> >>> Agreed. I'll review and commit such patches. I'd like to see a single >>> function for taking a "id or name". Ideally it would live in a >>> library, perhaps libjail? >> >> >> It already lives there: jail_getid(3) > > I was thinking of a more generic one that does id or name. Now that I > think about it a bit more, C makes this kind of thing impossible to do > usefully. > > That said, I'll still review and commit any patches to existing tools > to make them behave consistently. Yes, jail_getid(3) works with either a numeric ID or a name. I've added a patch to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 for the four programs I've found that need help. I've tested the easy ones (cpuset and sockstat). - Jamie From owner-freebsd-stable@freebsd.org Tue Jun 26 19:14:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17FFA1012974; Tue, 26 Jun 2018 19:14:28 +0000 (UTC) (envelope-from SRS0=Ta0Z=JM=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 A3CCB7F964; Tue, 26 Jun 2018 19:14:27 +0000 (UTC) (envelope-from SRS0=Ta0Z=JM=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2166928416; Tue, 26 Jun 2018 21:14:26 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id D530728412; Tue, 26 Jun 2018 21:14:24 +0200 (CEST) Subject: Re: jail related inconsistencies in FreeBSD tools parameters To: James Gritton , Eitan Adler Cc: freebsd-jail@freebsd.org, freebsd-stable Stable , bsd-lists@bsdforge.com References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> <51718e96f63175e997cb8268381d1070@freebsd.org> <8b11953ce292aff0bc60298e2e7613d6@freebsd.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <383af6fa-ae18-9126-de99-d642fe8407ae@quip.cz> Date: Tue, 26 Jun 2018 21:14:24 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <8b11953ce292aff0bc60298e2e7613d6@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 26 Jun 2018 19:14:28 -0000 James Gritton wrote on 2018/06/26 20:42: > On 2018-06-23 12:58, Eitan Adler wrote: [...] >> I was thinking of a more generic one that does id or name. Now that I >> think about it a bit more, C makes this kind of thing impossible to do >> usefully. >> >> That said, I'll still review and commit any patches to existing tools >> to make them behave consistently. > > Yes, jail_getid(3) works with either a numeric ID or a name. > > I've added a patch to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229266 for the four > programs I've found that need help.  I've tested the easy ones (cpuset > and sockstat). Thank you very much. I really appreciate your neverending work on jails! I hope it will be committed soon. Kind regards Miroslav Lachman From owner-freebsd-stable@freebsd.org Wed Jun 27 15:25:06 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DF4B1029564 for ; Wed, 27 Jun 2018 15:25:06 +0000 (UTC) (envelope-from vince@hightek.org) Received: from mail.ngtek.org (ngtek.org [IPv6:2001:19f0:6400:8963:5400:ff:fe09:9585]) (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 11D728281A for ; Wed, 27 Jun 2018 15:25:05 +0000 (UTC) (envelope-from vince@hightek.org) Received: from ip68-227-103-24.ok.ok.cox.net ([68.227.103.24] helo=hightek.org) by mail.ngtek.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fYCJc-0009A8-QX for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:25:04 -0500 Received: from localhost ([127.0.0.1] helo=quark.hightek.org) by hightek.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fYCJa-000AHO-GI for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:25:02 -0500 Received: (from vince@localhost) by quark.hightek.org (8.15.2/8.15.2/Submit) id w5RFP2OQ039517 for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:25:02 -0500 (CDT) (envelope-from vince) Date: Wed, 27 Jun 2018 10:25:02 -0500 From: Vincent Stemen To: freebsd-stable@freebsd.org Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] Message-ID: <20180627152502.GA39126@quark.hightek.org> References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> <20180622015757.GA52468@quark.hightek.org> <86zhznbi8u.fsf@elm.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 27 Jun 2018 15:25:06 -0000 On Sun, Jun 24, 2018 at 07:53:42PM +0200, Niclas Zeising wrote: > On 06/23/18 00:40, Mark Saad wrote: > > Vincent > > I used the scfb driver in openbsd land for a work project > > . Currently I am using 11-STABLE with the Radeon driver but at > > one point I had a different card under 11.0 that didn???t work > > unless I used the scfb driver . > > Hi! > If you are using FreeBSD 11.2 or later (stable or current) you should be > able to use graphics/drm-stable-kmod and get acceleration with your ATI > video cards. Please try it out! > Regards > -- > Niclas Thanks for the info. I'll make note of it for when I get a chance to upgrade. Right now, I am still running 11.1. Vince From owner-freebsd-stable@freebsd.org Wed Jun 27 15:34:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2726B1029C72 for ; Wed, 27 Jun 2018 15:34:01 +0000 (UTC) (envelope-from vince@hightek.org) Received: from mail.ngtek.org (ngtek.org [IPv6:2001:19f0:6400:8963:5400:ff:fe09:9585]) (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 C3B4682F9B for ; Wed, 27 Jun 2018 15:34:00 +0000 (UTC) (envelope-from vince@hightek.org) Received: from ip68-227-103-24.ok.ok.cox.net ([68.227.103.24] helo=hightek.org) by mail.ngtek.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fYCSF-0009BE-TU for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:33:59 -0500 Received: from localhost ([127.0.0.1] helo=quark.hightek.org) by hightek.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fYCSF-000AME-7r for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:33:59 -0500 Received: (from vince@localhost) by quark.hightek.org (8.15.2/8.15.2/Submit) id w5RFXxbJ039817 for freebsd-stable@freebsd.org; Wed, 27 Jun 2018 10:33:59 -0500 (CDT) (envelope-from vince) Date: Wed, 27 Jun 2018 10:33:59 -0500 From: Vincent Stemen To: freebsd-stable@freebsd.org Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] Message-ID: <20180627153359.GB39126@quark.hightek.org> References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> <20180622015757.GA52468@quark.hightek.org> <86zhznbi8u.fsf@elm.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86zhznbi8u.fsf@elm.localnet> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 27 Jun 2018 15:34:01 -0000 On Thu, Jun 21, 2018 at 08:41:21PM -0700, Carl Johnson wrote: > Vincent Stemen writes: > > > You must load radeonkms.ko after the system is fully booted. > > > > # kldload radeonkms > > > > That automatically loads the other 3 modules and initializes the console where > > the console text goes into higher resolution mode. Then X and the desktop > > environments work and seem to be fully functional, including transparency, etc. > > > > So I can either put it in /etc/rc.local, to be run at boot time, or put it in > > an X startup script wrapper. Note that it must be run prior to startx because > > it must be loaded before launching the X server. So it cannot be put in > > ~/.xinitrc. > > Have you tried loading it with kld_list in /etc/rc.conf? Those get > loaded during boot, but it might be late enough to work. That would be > automated, so it might be a little more convenient. > -- > Carl Johnson carlj@peak.org Thanks Carl. Yes, that also worked. So, in summary, you can load the radeonkms.ko module from $kld_list in /etc/rc.conf or put "kldload radeonkms" in /etc/rc.local. I find it to be about the same convenience either way. Vince From owner-freebsd-stable@freebsd.org Thu Jun 28 09:54:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2A1D1028714 for ; Thu, 28 Jun 2018 09:54:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6CE73FED for ; Thu, 28 Jun 2018 09:54:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 404131028712; Thu, 28 Jun 2018 09:54:00 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EC271028710 for ; Thu, 28 Jun 2018 09:54:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C2CCE73FE8 for ; Thu, 28 Jun 2018 09:53:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 119EA16220 for ; Thu, 28 Jun 2018 09:53:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5S9rw1T098397 for ; Thu, 28 Jun 2018 09:53:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5S9rwDs098396 for stable@FreeBSD.org; Thu, 28 Jun 2018 09:53:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly Date: Thu, 28 Jun 2018 09:53:58 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: freebsd.bugs@jmdavisprog.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 09:54:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228536 Jonathan M Davis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd.bugs@jmdavisprog.co | |m --- Comment #3 from Jonathan M Davis --- This is still broken in the released version of 11.2. The nvidia-driver pac= kage that's available for 11.2 is built for 11.1, not 11.2, and it doesn't work.= The module loads, but when X tries to start, it barfs, complaining: nvidia0: NVRM: rm_init_adapter() failed! Building the port and installing it fixes the problem, but the package does= n't work, which means that everyone using an nvidia card on 11.2 right now is g= oing to need to build the port themselves. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu Jun 28 15:31:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DA941012A1C for ; Thu, 28 Jun 2018 15:31:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 007BB80D3F for ; Thu, 28 Jun 2018 15:31:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AE7681012A13; Thu, 28 Jun 2018 15:31:38 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C3191012A12 for ; Thu, 28 Jun 2018 15:31:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2618D80D2F for ; Thu, 28 Jun 2018 15:31:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2CB3D19126 for ; Thu, 28 Jun 2018 15:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5SFVbIU006556 for ; Thu, 28 Jun 2018 15:31:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5SFVbAb006555 for stable@FreeBSD.org; Thu, 28 Jun 2018 15:31:37 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly Date: Thu, 28 Jun 2018 15:31:36 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 15:31:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228536 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: gjb Date: Thu Jun 28 15:30:52 UTC 2018 New revision: 335764 URL: https://svnweb.freebsd.org/changeset/base/335764 Log: Add an errata entry regarding Bugzilla 228536. PR: 228536 Sponsored by: The FreeBSD Foundation Changes: stable/11/release/doc/en_US.ISO8859-1/errata/article.xml --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu Jun 28 22:03:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A21171028DB1 for ; Thu, 28 Jun 2018 22:03:10 +0000 (UTC) (envelope-from ann.morris@laytheon.com) Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 20DD570A75 for ; Thu, 28 Jun 2018 22:03:10 +0000 (UTC) (envelope-from ann.morris@laytheon.com) Received: by mail-pg0-x242.google.com with SMTP id e11-v6so3055343pgq.0 for ; Thu, 28 Jun 2018 15:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=laytheon.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=yIkcpu4ofLaQ6S0jFRlLe7dJoOX0dTbHSAkoX5qu/BM=; b=cj+dGQ4VzyhwHokqT4cXlxk0Cwx87dl2plcFchu/jsvV7Vq0LcPl6T5ybTjYM08VFP PEzOdAD+lOnwDsxvWNF3khYrscTsgI28a0EiowHjbddnoixf/oKMRCbNUwYPYyt4FibZ ndQBb+7P2GsQ5zgZE1WV4QZBqkP+0i4HHZdnM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=yIkcpu4ofLaQ6S0jFRlLe7dJoOX0dTbHSAkoX5qu/BM=; b=i1QV1iPrk1KemZRVYydmMG4vr8b7tSnTKZpQHr9fw4kiRBLj7/9FRM7uz0qroiSKV9 qojLyoVvMHO8RFgv70cbfFj9lpnZ9R88Y6LBWjPc0kt6sxmSXcrxrisJGuXNV2+9NKWI GDhXH8BhO4OZV7/BcZ4pQlUPYzTKTGIhajbxMyar9HJ4xgPTr2A4liKqfwlWZma6aNnH nJpnCWQVMscpgSuxaosevV8DC/LmNhZw2tJdscStEMQhB5OKqMy+OdKroeKePyLDPRmq XiZ5h2VZTZ9ZNxIe8mQTOh5CcxBlWex5ierGqP6PJ6mm0n+FB26wXQnhNzoU1Gk7QPm7 JxcQ== X-Gm-Message-State: APt69E2mGYpIh59RqxxcLw6hBFfymfYKGNpjZb4/OShZbHy2rlcETepE c8rN6CAUsxZvxQl19m9RpJjyZ5B59PyYEzqu5p+JxA== X-Google-Smtp-Source: AAOMgpciyOUX94GyB083AeIFx6NEquAnd8HhvkuhLM7sJetBeqluC1UNYRD0WBUyQSXwSHsKFyrg0K7PoV810Zf6rf0= X-Received: by 2002:a63:d518:: with SMTP id c24-v6mr1426080pgg.357.1530223388984; Thu, 28 Jun 2018 15:03:08 -0700 (PDT) Received: from 369520428376 named unknown by gmailapi.google.com with HTTPREST; Thu, 28 Jun 2018 15:03:08 -0700 MIME-Version: 1.0 Sender: ann.morris@laytheon.com From: ann.morris@laytheon.com Date: Thu, 28 Jun 2018 15:03:08 -0700 X-Google-Sender-Auth: 5g7Qe4K2bKBHJ5TYZ8yH5M7Uu3k Message-ID: Subject: Targeted Global B2B Companies Emails List To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 22:03:10 -0000 Hello, Hope all is well! We are a database organization. We provide business executives' contact information. Below, I've included a few examples: Industry-Specific Lists: Agriculture, Business Services, Chambers of Commerce, Cities, Towns & Municipalities, Construction, Consumer Services, Cultural, Education, Energy, Utilities & Waste Treatment, Finance, Government, Healthcare, Hospitality, Insurance, Law Firms & Legal Services, Manufacturing, Media & Internet, Metals & Mining, Organizations, Real Estate, Retail, Software, Telecommunications, Transportation, and more! Technology-Specific Lists: SAP users, PeopleSoft users, SIEBEL customers, Oracle Application customers, Microsoft Dynamic users, Sales force users, Microsoft Exchange users, QuickBooks, Lawson users, Act users, JD Edward users, ASP users, Microsoft GP Applications users, Net Suite users, IBM DBMS Application users, McAfee users, MS Dynamics GP (Great Plains), and many more. Title-Specific Lists: C-level executives: CEO, CFO, CIO, CTO, CMO, CISO, CSO, COO Key decision-makers: All C-level, VP-level, and Director-level executives HR Executives: VP of HR, HR Director & HR Manager, etc. Marketi= ng Executives: CMO, VP of Marketing, Director of Marketing, Marketing Managers IT Executives: CIO, CTO, CISO, IT-VP, IT-Director, IT Manager, MIS Manager, etc. Please keep me informed for any additional details. I look forward to hearing from you. Kind Regards, Ann Marketing Executive If you don't want to include yourself in our mailing list, please reply back =E2=80=9CLeave Out" in a subject line From owner-freebsd-stable@freebsd.org Fri Jun 29 11:30:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 994AE1037F18 for ; Fri, 29 Jun 2018 11:30:32 +0000 (UTC) (envelope-from lists@searchy.net) Received: from mx.searchy.nl (mx.searchy.nl [IPv6:2a00:1280:8000:4::9]) (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 340E186EBF for ; Fri, 29 Jun 2018 11:30:32 +0000 (UTC) (envelope-from lists@searchy.net) Received: from mx.searchy.nl (mx.searchy.nl [79.143.214.224]) by mx.searchy.nl (Postfix) with ESMTP id ECA5613980A for ; Fri, 29 Jun 2018 11:30:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at mx.searchy.nl X-Spam-Flag: NO X-Spam-Score: -2.79 X-Spam-Level: X-Spam-Status: No, score=-2.79 tagged_above=-99 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no Authentication-Results: mx.searchy.nl (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=searchy.net Received: from mx.searchy.nl ([79.143.214.224]) by mx.searchy.nl (mx.searchy.nl [79.143.214.224]) (amavisd-new, port 10026) with ESMTP id LAKAM72ni8kK for ; Fri, 29 Jun 2018 11:30:27 +0000 (UTC) Received: from [IPv6:2001:470:79dd:3:d8e5:c16c:1b10:f5a3] (unknown [IPv6:2001:470:79dd:3:d8e5:c16c:1b10:f5a3]) by mx.searchy.nl (Postfix) with ESMTPSA id 18BD5139808 for ; Fri, 29 Jun 2018 11:30:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=searchy.net; s=default; t=1530271827; bh=2ZfndvifgImNsp/6gy1Qf4WEO/MTUtDxMn7DFQ11XA8=; h=To:From:Subject:Date; b=EUsIOXEyK7lgWV1NztgU6g9To71hW3OStwMKFGZRF1HpUuMXwhqVdUScN19oxE6Yu hEYEtwUWmRA3qlY7RbGYnHvWJlQUqHIZ5A2nr1OmWxVORY7HE1RFLxQ0PDF0PBto88 LlPyZGafi7dj0FwtP6pg3TT5T50FkTer+ijcRUek= To: FreeBSD Stable From: "Frank (lists)" Subject: iSCSI initiator multipath Message-ID: Date: Fri, 29 Jun 2018 13:30:25 +0200 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 29 Jun 2018 11:30:32 -0000 Hi, I have a=C2=A0 HA setup with LIO on linux. The exact set up is can be fou= nd=20 here: http://docs.ceph.com/docs/mimic/rbd/iscsi-target-cli/ I'm trying to use FreeBSD as initiator for this, but I can't manage to=20 get it working. Is this kind of setup supported by the FreeBSD=20 initiator? From another mailinglist a response=C2=A0 was about multipath=20 probably not enabling ALUA. Regards, Frank de Bot From owner-freebsd-stable@freebsd.org Fri Jun 29 14:32:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7F10EF92FC for ; Fri, 29 Jun 2018 14:32:30 +0000 (UTC) (envelope-from rene@reckschwardt.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 76F428D603 for ; Fri, 29 Jun 2018 14:32:30 +0000 (UTC) (envelope-from rene@reckschwardt.de) Received: by mailman.ysv.freebsd.org (Postfix) id 2FE5CEF92FB; Fri, 29 Jun 2018 14:32:30 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1976CEF92FA for ; Fri, 29 Jun 2018 14:32:30 +0000 (UTC) (envelope-from rene@reckschwardt.de) Received: from www.menny.de (reckschwardt.de [148.251.127.230]) (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 A60348D602 for ; Fri, 29 Jun 2018 14:32:28 +0000 (UTC) (envelope-from rene@reckschwardt.de) Received: from renes-iMac.local (p578ECB50.dip0.t-ipconnect.de [87.142.203.80]) by www.menny.de (Postfix) with ESMTPSA id E270327C13CA for ; Fri, 29 Jun 2018 16:31:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=reckschwardt.de; s=default; t=1530282710; bh=VtKWuAKgvy+VJPmIDnJ8J0LllXxx8yMzY12ya7FPOIA=; l=240; h=To:From:Subject; b=sRiGWr7XiyRD0hU0Xv65EnKkdFFHyMUs5UQXrqBC+IwlTHIDQMFPkjMfCUwX3t8R6 G2k9ShsDTLxvtGgg3Q5A3ENxi0cC4zH7+bHpO9pXz8bKH0xybo55Y1wh2zacDhzqE9 K0blyvy4AdcbQK3i6S9cV4xOSUbg7qKkimntaO7A= To: stable@FreeBSD.org From: rene reckschwardt Subject: link_elf_obj: symbol linux_flush_fn undefined Message-ID: <1b335375-0abd-9b98-3464-8d5e699459de@reckschwardt.de> Date: Fri, 29 Jun 2018 16:31:49 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: de-DE X-PPP-Message-ID: <20180629143150.22987.74849@www.menny.de> X-PPP-Vhost: reckschwardt.de X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 29 Jun 2018 14:32:31 -0000 Hello all, i updated yesterdays from 11.1-RELEASE to  11.2-RELEASE and the mlx4 NIC need the linuxkpi Kernelmodule but /var/log/message say: link_elf_obj: symbol linux_flush_fn undefined is this Problem known? best regards ré From owner-freebsd-stable@freebsd.org Fri Jun 29 17:18:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6312CEFFB60 for ; Fri, 29 Jun 2018 17:18:38 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 C70AC732D9 for ; Fri, 29 Jun 2018 17:18:37 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id v25-v6so1954563wmc.0 for ; Fri, 29 Jun 2018 10:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=zlFTPlEK1kv20H+ev84Yn8gI22PvNekdMdpAHe+uYgg=; b=FjTs/hB2QG9p/lim/EXOxxOUZt4lmX8nyT9G+wS6MjxqlxJXO4e748I7eH3B/OoeBy tY5EYERqBf9CUvlsbGPQcI7cLshz+CxiIBXvTOuX+nk6lONbAmAA0MufF2KaxTITKWS3 l5VignMDZ5vwWYb8gbuEM+a5YoI9lycs2idOpTkDsL50POVw2KqPeh6sI/nIadCRdtkr DV99imUptG33+tnS5gYe0DZKpHe68UChW9DADmhNbrbS+rHaH9CXCl6KhcDGogB9vLir bxweT2w9lf4VxcBwGFee+sIgon3a9/xR+AeW33v3oIYmUsSxtzAvZM6BBY2++7ffpfYn MeSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=zlFTPlEK1kv20H+ev84Yn8gI22PvNekdMdpAHe+uYgg=; b=e5nHXLs9wuq6VCdmevyXXzX9EgsXRfQaoy9lTFOMJFlqb4OK1kZGFguL86RQ6Ag7cm 9opC8peeXY5G36VODTQqkk257RDjJR1JKA2TFzL8t6s8nanZhXW5lFvdg2pYqcmy3U2C OWuEkE1mf16TLEg2QPPtF39sH4llsNXVlY89a4w8QYBAzByGHhr/WSAYNTtd3HHa4e+M tMAu2uR08mmBGI3ZpdMCkSkubheZskUVChtKKkOiEQvn0n4AZ9DMjCO7BxVCLBM4HQNF lD7YjbEImyrSVNb2FezzloAC89VJ+sN9T1KkAww/u6s5GylDmLXjqtHdipNidIzLiqJs IfvA== X-Gm-Message-State: APt69E1hRUMbJDln+UWS/+1svGAmJ+x4M40PPQdnzj71w0wPgcMGcRXV l5SqS8Du0ZjFJLwzWmwCUb/1lQ== X-Google-Smtp-Source: AAOMgpeRC9fb9Wpn0VVMN3ezOqBf/J8ET07XJdKF1LZRhNwB6xWNwJYHX4cFer73oixtKa8ESnDDRg== X-Received: by 2002:a1c:58d1:: with SMTP id m200-v6mr2517314wmb.160.1530292716155; Fri, 29 Jun 2018 10:18:36 -0700 (PDT) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id j10-v6sm13549610wrr.47.2018.06.29.10.18.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jun 2018 10:18:35 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 29 Jun 2018 18:18:33 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: "Frank (lists)" Cc: FreeBSD Stable Subject: Re: iSCSI initiator multipath Message-ID: <20180629171833.GA1503@brick> Mail-Followup-To: "Frank (lists)" , FreeBSD Stable References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 29 Jun 2018 17:18:38 -0000 On 0629T1330, Frank (lists) wrote: > Hi, > > I have a  HA setup with LIO on linux. The exact set up is can be found > here: http://docs.ceph.com/docs/mimic/rbd/iscsi-target-cli/ > > I'm trying to use FreeBSD as initiator for this, but I can't manage to > get it working. Is this kind of setup supported by the FreeBSD > initiator? From another mailinglist a response  was about multipath > probably not enabling ALUA. FreeBSD doesn't support ALUA. You can do multipathing in two ways: 1. Export your LUNs via two (or more) different paths (for example via two different target portal IP addresses), on the initiator side set up both iSCSI sessions in the usual way (like without multipathing), add kern.iscsi.fail_on_disconnection=1 to /etc/sysctl.conf, and set up gmultipath on top of LUNs reachable via those sessions 2. Set up the target so it redirects (sends "Target moved temporarily" login responses) to the target portal it considers active. Then set up the initiator (single session) to either one; the target will "bounce it" to the right place. You don't need gmultipath in this case, because from the initiator point of view there's only one iSCSI session at any time. From owner-freebsd-stable@freebsd.org Fri Jun 29 23:28:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28BECFD30CA for ; Fri, 29 Jun 2018 23:28:43 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) (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 7E0A180EF0 for ; Fri, 29 Jun 2018 23:28:42 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: by mail-ed1-x541.google.com with SMTP id w14-v6so8090849eds.6 for ; Fri, 29 Jun 2018 16:28:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cordula-ws.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to; bh=qrbAkyD6o1tY0lyvk36yR0c5Y6t04ssxZ1DgnPNIYjE=; b=OP6Xr0mB6kdaTuVeUgvdNOtYeZI1+m0lQ2pSn63g5cGQF45In8K8PYYTnmZ7t/SZUn AsZ/h3a+Jh50m2t7BUWruFjSYjuQOXI0mvuqGbg4FNKgfYeXhhccYr2FgvCtPp6BWZGe 51QZCFcJTGKmysn4/95vXUXlHyPywF8VkvM/AwzWVU7rNvOrmyOl0WYHsZ3ql5uwb6an l6yjMmvz+3Ndl90JykBhwzq/x5FzOhFPmX6D0a+/+1Osi1KHYHnaZiMhDFUkS8C+wdqK OSW8pP8Z0AQLZenqYhAvrZvazMmemfdKAZaFG38dDntVOSN8F0j25R0uH4G9emhDzpii wCHQ== 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; bh=qrbAkyD6o1tY0lyvk36yR0c5Y6t04ssxZ1DgnPNIYjE=; b=muUbAFwwBgAONeQI2WFaEJsh3dN0mlMnUmPLxAr1s1vtXEnZHvgi92BPZQo+/YWVW1 qotPwWnKdfiu9ldO6N/onoxTxmF1AXamY9ItWSRRIKrpZYFgp6PlzP3C8+/0E6vcwzMm RhBQQLq8GdBx7QZ84+ygKR2y/yz8AoUgrk2z4wzJDv0b00jMro3TqqMZyTXv6edZlt7p DMCFslbkGbZYnZtajZEuobP9cXJxqj3DH/GdgZDqk3nMO/5UN6eZ6XY0mJKlM22IkVa4 20uGQcqHsh5x7Ipxk+CMCrub/UZsLl8F3BZp3V4Wn6EBxtpxP62tZNVGvsWPpK5Br6rQ lnYQ== X-Gm-Message-State: APt69E2VgcjafdRhAoCOqzXg6+ntwV81ed+S6oKwEnY6egwXNmfoGwsu zr+kYSE06Ps81RaDYnkvQQi+RQ== X-Google-Smtp-Source: AAOMgpeQNztg1V9a/POC1AsmxrreBqL1ndr/66QqKaJZuuBteQCBizJTS4gEF14iFL6qpPZsLr4POg== X-Received: by 2002:aa7:c803:: with SMTP id a3-v6mr10412690edt.124.1530314920828; Fri, 29 Jun 2018 16:28:40 -0700 (PDT) Received: from ?IPv6:2a02:908:960:c43e:2efd:a1ff:fe57:abb8? ([2a02:908:960:c43e:2efd:a1ff:fe57:abb8]) by smtp.gmail.com with ESMTPSA id p30-v6sm5717605edc.5.2018.06.29.16.28.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jun 2018 16:28:39 -0700 (PDT) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: freebsd-stable@freebsd.org References: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> <20180626112919.GK2430@kib.kiev.ua> From: cpghost Cc: Konstantin Belousov Message-ID: <70feb5c9-4755-ebe7-f802-c36ea21288e4@cordula.ws> Date: Sat, 30 Jun 2018 01:28:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180626112919.GK2430@kib.kiev.ua> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms090409010704030104030100" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 29 Jun 2018 23:28:43 -0000 This is a cryptographically signed message in MIME format. --------------ms090409010704030104030100 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/26/18 13:29, Konstantin Belousov wrote: > On Tue, Jun 26, 2018 at 11:31:26AM +0100, Pete French wrote: >>> On 06/18/2018 09:34, Pete French wrote: >>>> Preseumably in the slightly longer term these workarounds go into th= e >>>> actual kernel if it detects Ryzen ? >>> >>> Yes, Kostik said he would code this into the kernel after he gets eno= ugh >>> feedback. >> >> So, I've been running with the sysctl and cputl fixes from >> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.h= tml >> for a couple of weeks now, with all the default settings back on (incl= uding >> SMT) and it now completely stable, so consider this one more point of = feedback Same here on FreeBSD monster 11.2-BETA2 FreeBSD 11.2-BETA2 #1 r334062: Tue May 22 23:4= 6:29 CEST 2018 root@monster:/usr/obj/usr/src/sys/GENERIC amd64 with a Threadripper 1950X and % sudo x86info -a | grep Microcode Microcode patch level: 0x8001136 Without that script, the system would lockup up to 5-6 times a day. Now running without any lockup at all for 3 days, with all kinds of workload from idle to torture tests. Too early to tell, but it looks good for now. CPU: AMD Ryzen Threadripper 1950X 16-Core Processor (3393.71-MHz K8-clas= s CPU) Origin=3D"AuthenticAMD" Id=3D0x800f11 Family=3D0x17 Model=3D0x1 Ste= pping=3D1 Features=3D0x178bfbff Features2=3D0x7ed8320b AMD Features=3D0x2e500800 AMD Features2=3D0x35c233ff Structured Extended Features=3D0x209c01a9 XSAVE Features=3D0xf AMD Extended Feature Extensions ID EBX=3D0x1007= SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 TSC: P-state invariant, performance statistics Thanks, -cpghost. --------------ms090409010704030104030100 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC Cx4wggUwMIIEGKADAgECAhEAxi8czu5BfArXx+KbCt8qNjANBgkqhkiG9w0BAQsFADCBlzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0Eg Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTcxMjIwMDAw MDAwWhcNMTgxMjIwMjM1OTU5WjAjMSEwHwYJKoZIhvcNAQkBFhJjcGdob3N0QGNvcmR1bGEu d3MwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCuV3EBb8py/1yrTdT8cb8h5Ocl h5XDYOn2HNcGCENONWU7Rrz9X+suOufiGCwUzrj+ysDLzM/jfB8EQMFH+uZrt9hi1gb9QvXh jzHvHqrb0P6Bj/HV8VvWyywa+BbuHNxuvOHB+ECpQYs4/Itfyhr4F/08FhweUpP7W+NKK/m8 VvLyY3kT5T58DYN0AvxgN6LK0ejbKD44wOrjK4EwuZpRmKewuWi+VquqRS04vo6xVE+h2tqq BUmVv4q9S6fHnvDcDCg3Gs4NTc6eujsHK6O9SLcgKB3CkHm5mxMkqGWNvtLb9p3/y9A+/v3n 2GRE07mmRkeJ43ntSytkz5xCiYmpAgMBAAGjggHoMIIB5DAfBgNVHSMEGDAWgBSCr2yM+MX+ lmF86B89K3FIXsSLwDAdBgNVHQ4EFgQUJVBhgnBvX0Bb+4bCJ8KLFjYJ4powDgYDVR0PAQH/ BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUC MBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsG AQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBaBgNVHR8EUzBRME+gTaBL hklodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9SU0FDbGllbnRBdXRoZW50aWNhdGlv bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGLBggrBgEFBQcBAQR/MH0wVQYIKwYBBQUHMAKGSWh0 dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET1JTQUNsaWVudEF1dGhlbnRpY2F0aW9uYW5k U2VjdXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNv bTAdBgNVHREEFjAUgRJjcGdob3N0QGNvcmR1bGEud3MwDQYJKoZIhvcNAQELBQADggEBAAZ0 otdXgClU/ijwGvnOdARI7LVDD4pPg6BD1kTbMywUE6ti082zAvujveH4DkleGZaVByv1VHGV HAdB8S7P21bm2uGCxwJNdRGl2R8USNmE7OP0EXYlQLTXDQbpBBPoB8k5Tv8WGJfguxIrPpS6 L729xb5d75NoKFMYn8JHTlujcfYt5TZCir0tO5/B9BgfB01tokFQ814wpUWmXplnD+tfRLaJ OChKmyUnOi5qpBntd/PHpUDNFIUJy0QZ3sYt1PyW7ejhtMvGvI/cQLZdDOUXv432nu0dgy2K 8PDGRfhp/NZhW8He7ililwDIu4B229OfiKI3fpPCDtm+xz7V900wggXmMIIDzqADAgECAhBq m+E4O/8ra58B1dm4p1JWMA0GCSqGSIb3DQEBDAUAMIGFMQswCQYDVQQGEwJHQjEbMBkGA1UE CBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P RE8gQ0EgTGltaXRlZDErMCkGA1UEAxMiQ09NT0RPIFJTQSBDZXJ0aWZpY2F0aW9uIEF1dGhv cml0eTAeFw0xMzAxMTAwMDAwMDBaFw0yODAxMDkyMzU5NTlaMIGXMQswCQYDVQQGEwJHQjEb MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK ExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAL6znlesKHZ1QBbHOAOY08YYdiFQ8yV5C0y1oNF9Olg+nKcxLqf2NHbZhGra0D00 SOTq9bus3/mxgUsg/Wh/eXQ0pnp8tZ8XZWAnlyKMpjL+qUByRjXCA6RQyDMqVaVUkbIr5SU0 RDX/kSsKwer3H1pT/HUrBN0X8sKtPTdGX8XAWt/VdMLBrZBlgvnkCos+KQWWCo63OTTqRvaq 8aWccm+KOMjTcE6s2mj6RkalweyDI7X+7U5lNo6jzC8RTXtVV4/Vwdax720YpMPJQaDaElmO upyTf1Qib+cpukNJnQmwygjD8m046DQkLnpXNCAGjuJy1F5NATksUsbfJAr7FLUCAwEAAaOC ATwwggE4MB8GA1UdIwQYMBaAFLuvfgI9+qbxPISOre44mOzZMjLUMB0GA1UdDgQWBBSCr2yM +MX+lmF86B89K3FIXsSLwDAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAR BgNVHSAECjAIMAYGBFUdIAAwTAYDVR0fBEUwQzBBoD+gPYY7aHR0cDovL2NybC5jb21vZG9j YS5jb20vQ09NT0RPUlNBQ2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcmwwcQYIKwYBBQUHAQEE ZTBjMDsGCCsGAQUFBzAChi9odHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9SU0FBZGRU cnVzdENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMA0GCSqG SIb3DQEBDAUAA4ICAQB4XLKBKDRPPO5fVs6fl1bsj6JrF/bz9kkIBtTYLzXN30D+03Hj6OxC DBEaIeNmsBhrJmuubvyE7HtoSmR809AgcYboW+rcTNZ/8u/Hv+GTrNI/AhqX2/kiQNxmgUPt /eJPs92Qclj0HnVyy9TnSvGkSDU7I5Px+TbO+88G4zipA2psZaWeEykgzClZlPz1FjTCkk77 ZXp5cQYYexE6zeeN4/0OqqoAloFrjAF4o50YJafX8mnahjp3I2Y2mkjhk0xQfhNqbzlLWPoT 3m7j7U26u7zg6swjOq8hITYc3/np5tM5aVyu6t99p17bTbY7+1RTWBviN9YJzK8HxzObXYWB f/L+VGOYNsQDTxAk0Hbvb1j6KjUhg7fO294F29QIhhmiNOr84JHoy+fNLpfvYc/Q9EtFOI5I SYgOxLk3nD/whbUe9rmEQXLp8MB933Ij474gwwCPUpwv9mj2PMnXoc7mbrS22XUSeTwxCTP9 bcmUdp4jmIoWfhQm7X9w/Zgddg+JZ/YnIHOwsGsaTUgj7fIvxqith7DoJC91WJ8Lce3CVJqb 1XWeKIJ84F7YLXZN0oa7TktYgDdmQVxYkZo1c5noaDKH9Oq9cbm/vOYRUM1cWcef20Wkyk5S /GFyyPJwG0fR1nRas3DqAf4cXxMiEKcff7PNa4M3RGTqH0pWR8p6EjGCBDgwggQ0AgEBMIGt MIGXMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQH EwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RP IFJTQSBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAMYvHM7u QXwK18fimwrfKjYwDQYJYIZIAWUDBAIBBQCgggJbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE4MDYyOTIzMjgzOFowLwYJKoZIhvcNAQkEMSIEIBrsojPL 3Xr/A8l4CV8k5qkg7PL6SZQbER8TqwA7hZQJMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUD BAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgb4GCSsGAQQBgjcQBDGBsDCBrTCBlzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0Eg Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDGLxzO7kF8CtfH 4psK3yo2MIHABgsqhkiG9w0BCRACCzGBsKCBrTCBlzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RP IENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhlbnRpY2F0aW9u IGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDGLxzO7kF8CtfH4psK3yo2MA0GCSqGSIb3DQEBAQUA BIIBAGGJLvXq+4KV+HnfCGXRG1fjlMTT4HN4PxGPAA0IVBgAZiH0gI6k/tkDyBfetx2UoUNh dpcihwtK06QsgSIE6C5VxERtyKPf0XzrQqFhMMkCt/X1JLVwY1ScVqCx65L5aR3fX9ztoSjA /Co09HH97YDDvA2f0rVssmx2kBGfqYZGYQ4flE6aXxG0roO2T09z97KAm+mX5z89RBZQNUZc cboqI5bqL0HNVw1RVGXkAS9IACFbiWD6+qUwZLwsSpb/1woGAFC9yVlu0alPiDpTOVKVCgks HfsIHbve/4GnxkpOPib3eQiNKLIrYFWcUAPdGzC/wXOb5qLoBgzoQHWL34wAAAAAAAA= --------------ms090409010704030104030100-- From owner-freebsd-stable@freebsd.org Sat Jun 30 04:08:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14E3E100184A for ; Sat, 30 Jun 2018 04:08:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6BB8C394 for ; Sat, 30 Jun 2018 04:08:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 545F41001848; Sat, 30 Jun 2018 04:08:01 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 420AC1001847 for ; Sat, 30 Jun 2018 04:08:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD64C8C380 for ; Sat, 30 Jun 2018 04:08:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EECFEC41A for ; Sat, 30 Jun 2018 04:07:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5U47xkD059728 for ; Sat, 30 Jun 2018 04:07:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5U47xLd059727 for stable@FreeBSD.org; Sat, 30 Jun 2018 04:07:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly Date: Sat, 30 Jun 2018 04:07:58 +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: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: khng300@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2018 04:08:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228536 --- Comment #5 from Ka Ho Ng --- (In reply to Jonathan M Davis from comment #3) kld built for FreeBSD 11.1 is supposed to work on FreeBSD 11.2 and so on. However due to a KBI bug exposed by r328469 the KBI of vm_map becomes incompatible between 11.1 and 11.2. r332091 was committed to rectify the is= sue but it only takes effect when nvidia kmod in ports/pkg start to be built against FreeBSD 11.2 kernel. So you currently either need to workaround the issue by rebuilding the ports yourself or waiting till FreeBSD 11.1 is deprecated. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Sat Jun 30 16:55:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D3B04AA for ; Sat, 30 Jun 2018 16:55:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 631AB84715; Sat, 30 Jun 2018 16:55:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w5UGtAXv093128 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Jun 2018 19:55:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5UGtAXv093128 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5UGt8Ln093107; Sat, 30 Jun 2018 19:55:08 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 30 Jun 2018 19:55:08 +0300 From: Konstantin Belousov To: Pete French Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, mike@sentex.net, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <20180630165508.GT2430@kib.kiev.ua> References: <20180626112919.GK2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2018 16:55:23 -0000 On Tue, Jun 26, 2018 at 01:32:01PM +0100, Pete French wrote: > the dmesg wraps around if I boot verbosely, but heres the contnets of > /var/log/messages from the time it starts to where it stops > talking about CPU specific stuff... if you need something else then > let me know - this is an easy machine to reboot and play about with. This should be the kernel patch equivalent to the script. According to the revision document, some of the erratas are applicable to the Ryzen 2, but I do not want to do the bit tweaking without a confirmation. diff --git a/sys/amd64/amd64/initcpu.c b/sys/amd64/amd64/initcpu.c index ccc5e64d0c4..aac3ccb7c73 100644 --- a/sys/amd64/amd64/initcpu.c +++ b/sys/amd64/amd64/initcpu.c @@ -130,6 +130,29 @@ init_amd(void) } } + /* Ryzen erratas. */ + if (CPUID_TO_FAMILY(cpu_id) == 0x17 && CPUID_TO_MODEL(cpu_id) == 0x1) { + /* 1021 */ + msr = rdmsr(0xc0011029); + msr |= 0x2000; + wrmsr(0xc0011029, msr); + + /* 1033 */ + msr = rdmsr(0xc0011020); + msr |= 0x10; + wrmsr(0xc0011020, msr); + + /* 1049 */ + msr = rdmsr(0xc0011028); + msr |= 0x10; + wrmsr(0xc0011028, msr); + + /* 1095 */ + msr = rdmsr(0xc0011020); + msr |= 0x200000000000000; + wrmsr(0xc0011020, msr); + } + /* * Work around a problem on Ryzen that is triggered by executing * code near the top of user memory, in our case the signal diff --git a/sys/x86/include/specialreg.h b/sys/x86/include/specialreg.h index 0ea6e61e652..c3900dadf05 100644 --- a/sys/x86/include/specialreg.h +++ b/sys/x86/include/specialreg.h @@ -998,18 +998,18 @@ #define MSR_TOP_MEM 0xc001001a /* boundary for ram below 4G */ #define MSR_TOP_MEM2 0xc001001d /* boundary for ram above 4G */ #define MSR_NB_CFG1 0xc001001f /* NB configuration 1 */ +#define MSR_K8_UCODE_UPDATE 0xc0010020 /* update microcode */ +#define MSR_MC0_CTL_MASK 0xc0010044 #define MSR_P_STATE_LIMIT 0xc0010061 /* P-state Current Limit Register */ #define MSR_P_STATE_CONTROL 0xc0010062 /* P-state Control Register */ #define MSR_P_STATE_STATUS 0xc0010063 /* P-state Status Register */ #define MSR_P_STATE_CONFIG(n) (0xc0010064 + (n)) /* P-state Config */ #define MSR_SMM_ADDR 0xc0010112 /* SMM TSEG base address */ #define MSR_SMM_MASK 0xc0010113 /* SMM TSEG address mask */ +#define MSR_VM_CR 0xc0010114 /* SVM: feature control */ +#define MSR_VM_HSAVE_PA 0xc0010117 /* SVM: host save area address */ #define MSR_EXTFEATURES 0xc0011005 /* Extended CPUID Features override */ #define MSR_IC_CFG 0xc0011021 /* Instruction Cache Configuration */ -#define MSR_K8_UCODE_UPDATE 0xc0010020 /* update microcode */ -#define MSR_MC0_CTL_MASK 0xc0010044 -#define MSR_VM_CR 0xc0010114 /* SVM: feature control */ -#define MSR_VM_HSAVE_PA 0xc0010117 /* SVM: host save area address */ /* MSR_VM_CR related */ #define VM_CR_SVMDIS 0x10 /* SVM: disabled by BIOS */ diff --git a/sys/x86/x86/cpu_machdep.c b/sys/x86/x86/cpu_machdep.c index d897d518cbc..3416f949686 100644 --- a/sys/x86/x86/cpu_machdep.c +++ b/sys/x86/x86/cpu_machdep.c @@ -709,6 +709,13 @@ cpu_idle_tun(void *unused __unused) if (TUNABLE_STR_FETCH("machdep.idle", tunvar, sizeof(tunvar))) cpu_idle_selector(tunvar); + else if (cpu_vendor_id == CPU_VENDOR_AMD && + CPUID_TO_FAMILY(cpu_id) == 0x17 && CPUID_TO_MODEL(cpu_id) == 0x1) { + /* Ryzen erratas 1057, 1109. */ + cpu_idle_selector("hlt"); + idle_mwait = 0; + } + if (cpu_vendor_id == CPU_VENDOR_INTEL && cpu_id == 0x506c9) { /* * Apollo Lake errata APL31 (public errata APL30).