From owner-freebsd-stable@FreeBSD.ORG Sun Mar 8 17:47:06 2015 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE597E2 for ; Sun, 8 Mar 2015 17:47:06 +0000 (UTC) Received: from s17151775.onlinehome-server.info (s17151775.onlinehome-server.info [IPv6:2001:8d8:86b:9300::29:494f]) (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 77944AA0 for ; Sun, 8 Mar 2015 17:47:06 +0000 (UTC) Received: by s17151775.onlinehome-server.info (Postfix, from userid 502) id 53D30440732; Sun, 8 Mar 2015 18:21:09 +0100 (CET) To: stable@freebsd.org Subject: Quote products details X-PHP-Originating-Script: 502:a.php From: Grace Reply-To: gracemacf@yahoo.com MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: <20150308172644.53D30440732@s17151775.onlinehome-server.info> Date: Sun, 8 Mar 2015 18:21:09 +0100 (CET) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 17:47:06 -0000 Dear Sales Manager, This is Grace, the Sales Manager of Stock Pile LTD, Thailand. We are an US based B2B Platform. We are in the process of gathering various types of trade-able goods for various international markets like USA, UK, India, Germany, Australia and various other Asian & European countries. We offer great interest to do a purchase agreement with your company. Please get back to us with the following information 1,Minimum Order 2,Payment Terms 3,Product Specification 4,Delivery Time 5,Country Of Origin 6,Sample Availability 7,Is Your Price Negotiable? We would need a quick reply. Brst Regards, Grace Macfede Amata Nakorn Industrial Estate 700/553, Moo 7, T.Don Hua Roh, A.Maung, Chonburi, 20000, Thailand From owner-freebsd-stable@FreeBSD.ORG Sun Mar 8 18:15:04 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E384BB7 for ; Sun, 8 Mar 2015 18:15:04 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 044B2E76 for ; Sun, 8 Mar 2015 18:15:03 +0000 (UTC) Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 947524109F; Sun, 8 Mar 2015 18:14:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1425838497; bh=mw2jGY2VA7S+sHGdkcgsggzk595YMGJC3YP1uDOn1OU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ZeYwUmPbfBE013q0q5konZ1Jf4B8rLyuw10P+tuXjukgbmyizHtAQoe3IasBNFXiS iKYWZL7OiHrGH4UG1xhZtVahZcozZTyVF0LPyG8i2K9WYyUKTE244Fux6FKcIiewId 46vuUUNQoS/E9V2mylm8L3dMi/pbYXPqxQhFS6bM= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: pkubaj) with ESMTPSA id 1D40022C8F Message-ID: <54FC9197.9040406@riseup.net> Date: Sun, 08 Mar 2015 19:14:47 +0100 From: Piotr Kubaj User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Chris H , freebsd-stable@freebsd.org Subject: Re: No sound on 10.1-RELEASE References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net> In-Reply-To: <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.6 at mx1 X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 18:15:04 -0000 On 03/07/15 01:55, Chris H wrote: > On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote > >> I've got MSI X99 motherboard and am using it with UEFI installation of >> 10.1 (BIOS mode doesn't work with FreeBSD). At first, sound worked >> properly (even in KDE), but now it doesn't. I'm not sure what happened, >> since snd_hda is in kernel (I use GENERIC). I've checked all possible >> values of hw.snd.default_unit and turned off KDE to check what happens >> when doing cat /dev/random > /dev/dsp (it does nothing). >> Attached below is dmesg and /dev/sndstat. >> > -----8<------- > >> Installed devices: >> pcm0: (play) >> pcm1: (play) >> pcm2: (play) >> pcm3: (play) >> pcm4: (play/rec) default >> pcm5: (play/rec) >> pcm6: (play) >> pcm7: (rec) > Honestly, this could potentially go a lot of different directions; > software/driver(s)/setup... > It might be helpful to get the pinouts. The kernel > (dmesg(8)) will provide it for you. You can see them by; > loader.conf(5) > adding the following to /boot/loader.conf: > > boot_verbose="YES" > > or by simply selecting boot verbose on the loader menu > 6 --> boot verbose > > and then getting the results from dmesg(8) > /var/run/dmesg.boot > > If everything looks as anticipated, you might check that > your software is using the right sound system (OSS). > I've had very good experiences on these sound systems by > installing > audio/xfce4-mixer > doing so, always seems to get the correct settings for > everything on these boards -- even if you never use > the application. > Because these boards can be so troublesome where sound > is concerned; I used to have a script that would both > check, as well as set everything up. But I can't seem > to locate it ATM. > > HTH > > --Chris >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: http://pastebin.com/pP0KXp4v KDE is definitely using OSS as chosen in its settings (I also use its own mixer which can do the same as Xfce's). I also use VLC's Phonon backend because Gstreamer is said to cause problems, but that also works on 3 other computers. From owner-freebsd-stable@FreeBSD.ORG Sun Mar 8 21:14:33 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0F48233 for ; Sun, 8 Mar 2015 21:14:33 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BC018FF for ; Sun, 8 Mar 2015 21:14:33 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t28LFwMi070089; Sun, 8 Mar 2015 14:15:58 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@freebsd.org, Piotr Kubaj In-Reply-To: <54FC9197.9040406@riseup.net> References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> From: "Chris H" Subject: Re: No sound on 10.1-RELEASE Date: Sun, 08 Mar 2015 14:15:59 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Mar 2015 21:14:33 -0000 On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote > On 03/07/15 01:55, Chris H wrote: > > On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote > > > >> I've got MSI X99 motherboard and am using it with UEFI installation of > >> 10.1 (BIOS mode doesn't work with FreeBSD). At first, sound worked > >> properly (even in KDE), but now it doesn't. I'm not sure what happened, > >> since snd_hda is in kernel (I use GENERIC). I've checked all possible > >> values of hw.snd.default_unit and turned off KDE to check what happens > >> when doing cat /dev/random > /dev/dsp (it does nothing). > >> Attached below is dmesg and /dev/sndstat. > >> > > -----8<------- > > > >> Installed devices: > >> pcm0: (play) > >> pcm1: (play) > >> pcm2: (play) > >> pcm3: (play) > >> pcm4: (play/rec) default > >> pcm5: (play/rec) > >> pcm6: (play) > >> pcm7: (rec) > > Honestly, this could potentially go a lot of different directions; > > software/driver(s)/setup... > > It might be helpful to get the pinouts. The kernel > > (dmesg(8)) will provide it for you. You can see them by; > > loader.conf(5) > > adding the following to /boot/loader.conf: > > > > boot_verbose="YES" > > > > or by simply selecting boot verbose on the loader menu > > 6 --> boot verbose > > > > and then getting the results from dmesg(8) > > /var/run/dmesg.boot > > > > If everything looks as anticipated, you might check that > > your software is using the right sound system (OSS). > > I've had very good experiences on these sound systems by > > installing > > audio/xfce4-mixer > > doing so, always seems to get the correct settings for > > everything on these boards -- even if you never use > > the application. > > Because these boards can be so troublesome where sound > > is concerned; I used to have a script that would both > > check, as well as set everything up. But I can't seem > > to locate it ATM. > > > > HTH > > > > --Chris > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: > http://pastebin.com/pP0KXp4v Out of the 4 MSI boards I that I have; 3 run the same Realtek ALC893 HDA CODEC that yours does. The other, the Realtek ALC1200 HDA CODEC. All four of them work. But I notice 1 notable difference; that yours reports 2 HDA interfaces: hdac0: and hdac1: I see hdac0 is disregarded (unused) whereas hdac1 is enabled, and functioning. I think your problems quite possibly lies in your (sound) system attempting to use the first HDA device in the list, which is effectively disabled. If you can determine a way to tell KDE, and friends to use the 2nd HDA. Things may well go as intended. None of the 4 MSI boards I have display 2 HDA's, as yours does. If you have any additional questions, you may well find the FreeBSD forums already have answers to your issue. This is where I originally found answers to my issues, when I first started using these boards. HTH > > KDE is definitely using OSS as chosen in its settings (I also use its > own mixer which can do the same as Xfce's). I also use VLC's Phonon > backend because Gstreamer is said to cause problems, but that also works > on 3 other computers. --Chris -- From owner-freebsd-stable@FreeBSD.ORG Mon Mar 9 16:19:39 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21A91F10 for ; Mon, 9 Mar 2015 16:19:39 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 83EB4F2A for ; Mon, 9 Mar 2015 16:19:38 +0000 (UTC) Received: by lamq1 with SMTP id q1so8202379lam.12 for ; Mon, 09 Mar 2015 09:19:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=AeWs1qyfRRFAfQG7ekWb1snENt3WPIV1cVqkfsquqVo=; b=irI3RLCW8Z73anRIil+qqbZ3t+hPk2veyLj1mZ62S5FR7kpynzZ805QZszoeY3QrIx nso3iSuNcDa2QHYcVqjlLE7lI3ilzsLgMGLRYMjQNPiQE+iFlclQvBxIPfgpAadOs3lT rZ2hgzgzsNNSh4gc0dv1gCKV4xXCfHAmWzf0SpEKri749fKIKRcqz0X5SbdXqzk3iyju IuobCeIVL4SFkpfFssjHEQP12JOPTF+5w5Bx/8VYRIqk5yFWWqAhsVxuVuwP69CKY870 swnu1M3dyYb2PX4wo3Guu53ZQoJ11plY+ZcQtl6206L9/84fR4prgXE8xsxVyFQiza8x eQ0g== MIME-Version: 1.0 X-Received: by 10.112.98.201 with SMTP id ek9mr26760588lbb.68.1425917976487; Mon, 09 Mar 2015 09:19:36 -0700 (PDT) Received: by 10.25.90.131 with HTTP; Mon, 9 Mar 2015 09:19:36 -0700 (PDT) In-Reply-To: References: <2F9DC176-912C-40C0-BAB7-DB66BD572ABA@vnode.se> <54D8E341.101@pix.net> <1423501720.16794.18.camel@freebsd.org> Date: Mon, 9 Mar 2015 09:19:36 -0700 Message-ID: Subject: Re: freebsd-update and hang during reboot From: Nick Rogers Cc: FreeBSD STABLE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Mar 2015 16:19:39 -0000 On Tue, Feb 10, 2015 at 1:37 PM, Nick Rogers wrote: > > > On Mon, Feb 9, 2015 at 9:08 AM, Ian Lepore wrote: > >> On Mon, 2015-02-09 at 11:41 -0500, Kurt Lidl wrote: >> > Joel wrote: >> > > Hi, >> > > >> > > Just about every machine I have seems to hang after running >> freebsd-update and doing a reboot. The last message on the screen is "Al= l >> buffers synced=E2=80=9D and it just freezes. >> > > >> > > This happens when doing a freebsd-update and going from 10.0 to 10.1= , >> but also when doing a fresh 10.1 install and using freebsd-update to get >> the latest -pX security patches. As soon as I reboot the machine, it han= gs. >> > > >> > > I=E2=80=99ve tried it on several different HP ProLiant models, on In= tel NUCs >> and on VMware virtual machines. Same phenomenon everywhere. It=E2=80=99s= really >> easy to trigger: just install 10.1, use default settings everywhere, >> freebsd-update fetch/install, shutdown -r now and BOOM. It hangs. I thin= k >> I=E2=80=99ve seen it on >> > > >> > > >> > > >> > > >> > > 30 servers or so now. >> > > >> > > Everything works like it should after the initial hang tough - no >> matter how many times I reboot it completes the reboot cycle just fine. >> > > >> > > I=E2=80=99ve seen several people (mostly on IRC) mention this proble= m, but no >> solution. >> > > >> > > Is anyone working on fixing this? >> > >> > I ran into this problem in spades when upgrading a set of servers from >> > FreeBSD 9.0 to 9.1. I happened consistently. Normal reboots worked, >> > but when going from 9.0 to 9.1, it *ALWAYS* hung, and it always hung >> > at the same place, after printing the "All buffers synced" message. >> > >> > I ultimately determined that if I did the following, rather than >> > just a "reboot" or "shutdown -r now 'FreeBSD 9.1-RELEASE upgrade'", >> > it would consistently AVOID the hang: >> > >> > sync ; sync ; sync ; shutdown -o -n -r now "FreeBSD 9.1 install" >> > >> > Your mileage may vary, but you don't have a lot to lose by trying it. >> > >> > -Kurt >> > >> >> That is just bad advice. sync(1) does not g'tee that all data has been >> written, no matter how many times you type it. shutdown -n tells the >> system to abandon unwritten data. All in all, this is a recipe for >> silent filesystem corruption. Using it after an update is just asking >> to have a mix of old and new files on the system after the reboot. >> >> A more robust workaround would be to "mount -r" on all filesystems >> before invoking the shutdown (even a shutdown -n should be safe after >> everything has been remounted readonly). If the mount -r hangs on one >> of the filesystems, then you've probably got a clue as to where a normal >> shutdown is hanging. >> > > FWIW mount -r on the root filesystem hangs for me. If I disable > softupdates-journaling on the root filesystem before the upgrade process, > the system no longer hangs on the last reboot after userland upgrade. > However, the root filesystem still comes up dirty with an incorrect free > block count during fsck. > Is anyone working on fixing this problem? It seems like this should have some kind of "full court press" as it is obviously affecting plenty of people, some of which have spoken up in the following PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195458 I realize its a tough problem to track down, and if I had the appropriate skills I would help. But so far all I've been able to do, like others, is replicate and complain about the problem. Its still affecting upgrading to 10.1-RELEASE-p6 from the official 10.1-RELEASE distribution, and from 10.1-RELEASE-p5. I just had another production server hang during reboot after updating to p6, and I don't see this changing for the inevitable p7 unless this problem gets more attention. Can someone with the right skill-set please help figure this out? Thank you. >> -- Ian >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org= " >> > > From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 00:24:43 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96991782 for ; Tue, 10 Mar 2015 00:24:43 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 82EFEABC for ; Tue, 10 Mar 2015 00:24:42 +0000 (UTC) Received: from [10.1.8.7] (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id 460C3284E1 for ; Tue, 10 Mar 2015 10:17:10 +1000 (EST) Message-ID: <54FE3803.2000307@akips.com> Date: Tue, 10 Mar 2015 10:17:07 +1000 From: Nick Frampton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Suspected libkvm infinite loop Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 00:24:43 -0000 Hi, For the past several months, we have had an intermittent problem where a process calling kvm_openfiles(3) or kvm_getprocs(3) (not sure which) gets stuck in an infinite loop and goes to 100% cpu. We have just observed "fstat -m" do the same thing and suspect it may be the same problem. Our environment is a 10.1-RELEASE-p6 amd64 guest running in VirtualBox, with ufs root and zfs /home. Has anyone else experienced this? Is there anything we can do to investigate the problem further? Thanks, Nick -- Founder, CTO www.akips.com From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 00:43:25 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6842F9BB for ; Tue, 10 Mar 2015 00:43:25 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41687CC7 for ; Tue, 10 Mar 2015 00:43:25 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2A0itQ4002839 for ; Mon, 9 Mar 2015 17:44:55 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: "FreeBSD STABLE" From: "Chris H" Subject: Is there a linux_base available for RELENG_9? Date: Mon, 09 Mar 2015 17:44:55 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 00:43:25 -0000 I performed av svn update for both src (r279796), and ports (r380829) last night. building/installing world/kernel, went as one would hope. Upgrading ports was a different story. Given this box has an nVidia card. I usually start by upgrading emulators/linux_base; which according to UPDATING; meant linux_base-f10 --> linux_base-c6. I deinstalled x11/nvidia-driver, followed by emulators/linux_base-f10. I then attempted to make install emulators/linux_base-c6, which resulted in a message that it wasn't supported. So I simply cd'd to emulators/linux_base-f10, followed by make install. Which resulted in a CVE message; indicating it was vulnerable to glib issues. I'm now stuck w/o hardware support for my video card, and unable to effectively follow a safe port upgrade path, that enables me to keep the options I have chosen for my currently installed ports. Is there a *safe* linux_base available? Thank you for all your time, and consideration. --Chris -- From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 00:45:14 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C124EAC4 for ; Tue, 10 Mar 2015 00:45:14 +0000 (UTC) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.167]) by mx1.freebsd.org (Postfix) with ESMTP id 98A3ECE1 for ; Tue, 10 Mar 2015 00:45:13 +0000 (UTC) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 6EE1D3E9DF for ; Mon, 9 Mar 2015 20:45:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2dH5paqo18Ho for ; Mon, 9 Mar 2015 20:45:12 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <54FE3E97.3040508@egr.msu.edu> Date: Mon, 09 Mar 2015 20:45:11 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Is there a linux_base available for RELENG_9? References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> In-Reply-To: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 00:45:14 -0000 On 03/09/2015 20:44, Chris H wrote: > I performed av svn update for both src (r279796), > and ports (r380829) last night. building/installing > world/kernel, went as one would hope. Upgrading ports > was a different story. Given this box has an nVidia card. > I usually start by upgrading emulators/linux_base; which > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > I deinstalled x11/nvidia-driver, followed by > emulators/linux_base-f10. I then attempted to make install > emulators/linux_base-c6, which resulted in a message > that it wasn't supported. What was the exact error? From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 00:50:13 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC0F5BEA for ; Tue, 10 Mar 2015 00:50:13 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 94752D9A for ; Tue, 10 Mar 2015 00:50:13 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2A0pgwu003238; Mon, 9 Mar 2015 17:51:42 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@freebsd.org, Adam McDougall In-Reply-To: <54FE3E97.3040508@egr.msu.edu> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net>, <54FE3E97.3040508@egr.msu.edu> From: "Chris H" Subject: Re: Is there a linux_base available for RELENG_9? Date: Mon, 09 Mar 2015 17:51:42 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <956f4c591a372887250288b5e37d30f5@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 00:50:13 -0000 On Mon, 09 Mar 2015 20:45:11 -0400 Adam McDougall wrote > On 03/09/2015 20:44, Chris H wrote: > > I performed av svn update for both src (r279796), > > and ports (r380829) last night. building/installing > > world/kernel, went as one would hope. Upgrading ports > > was a different story. Given this box has an nVidia card. > > I usually start by upgrading emulators/linux_base; which > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > I deinstalled x11/nvidia-driver, followed by > > emulators/linux_base-f10. I then attempted to make install > > emulators/linux_base-c6, which resulted in a message > > that it wasn't supported. > > What was the exact error? Thank you very much for the reply, Adam. It was: ===> linux_base-f10-10_9 has known vulnerabilities: linux_base-f10-10_9 is vulnerable: glibc -- gethostbyname buffer overflow CVE: CVE-2015-0235 WWW: http://portaudit.FreeBSD.org/0765de84-a6c1-11e4-a0c1-c485083ca99c.html Thanks, again! --Chris > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 00:51:13 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E588FCDA for ; Tue, 10 Mar 2015 00:51:13 +0000 (UTC) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6C4BDAE for ; Tue, 10 Mar 2015 00:51:13 +0000 (UTC) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YV8O2-000BuO-Hk; Tue, 10 Mar 2015 00:51:06 +0000 Date: Tue, 10 Mar 2015 00:51:06 +0000 From: Gary Palmer To: Chris H Subject: Re: Is there a linux_base available for RELENG_9? Message-ID: <20150310005106.GA59888@in-addr.com> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false Cc: FreeBSD STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 00:51:14 -0000 On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > I performed av svn update for both src (r279796), > and ports (r380829) last night. building/installing > world/kernel, went as one would hope. Upgrading ports > was a different story. Given this box has an nVidia card. > I usually start by upgrading emulators/linux_base; which > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > I deinstalled x11/nvidia-driver, followed by > emulators/linux_base-f10. I then attempted to make install > emulators/linux_base-c6, which resulted in a message > that it wasn't supported. So I simply cd'd to > emulators/linux_base-f10, followed by make install. Which > resulted in a CVE message; indicating it was vulnerable > to glib issues. I'm now stuck w/o hardware support for > my video card, and unable to effectively follow > a safe port upgrade path, that enables me to keep the > options I have chosen for my currently installed ports. > Is there a *safe* linux_base available? > > Thank you for all your time, and consideration. If you set sysctl compat.linux.osrelease=2.6.18 you can install linux_base-c6 on RELENG_9 It works well enough at least for nvidia-driver, as my main desktop is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 installed Remember to put compat.linux.osrelease=2.6.18 into /etc/sysctl.conf so it's preserved on startup I believe if you read the message from linux_base-c6 that's basically what it told you to do. Regards, Gary From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 01:07:33 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7475AE86; Tue, 10 Mar 2015 01:07:33 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1EC61EB2; Tue, 10 Mar 2015 01:07:33 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2A193WK004591; Mon, 9 Mar 2015 18:09:04 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Gary Palmer In-Reply-To: <20150310005106.GA59888@in-addr.com> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net>, <20150310005106.GA59888@in-addr.com> From: "Chris H" Subject: Re: Is there a linux_base available for RELENG_9? Date: Mon, 09 Mar 2015 18:09:04 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <08c23a03a843632af2f105057de45713@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: FreeBSD STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:07:33 -0000 On Tue, 10 Mar 2015 00:51:06 +0000 Gary Palmer wrote > On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > > I performed av svn update for both src (r279796), > > and ports (r380829) last night. building/installing > > world/kernel, went as one would hope. Upgrading ports > > was a different story. Given this box has an nVidia card. > > I usually start by upgrading emulators/linux_base; which > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > I deinstalled x11/nvidia-driver, followed by > > emulators/linux_base-f10. I then attempted to make install > > emulators/linux_base-c6, which resulted in a message > > that it wasn't supported. So I simply cd'd to > > emulators/linux_base-f10, followed by make install. Which > > resulted in a CVE message; indicating it was vulnerable > > to glib issues. I'm now stuck w/o hardware support for > > my video card, and unable to effectively follow > > a safe port upgrade path, that enables me to keep the > > options I have chosen for my currently installed ports. > > Is there a *safe* linux_base available? > > > > Thank you for all your time, and consideration. > > If you set > > sysctl compat.linux.osrelease=2.6.18 > > you can install linux_base-c6 on RELENG_9 > > It works well enough at least for nvidia-driver, as my main desktop > is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 > installed > > Remember to put > > compat.linux.osrelease=2.6.18 > > into /etc/sysctl.conf so it's preserved on startup > > I believe if you read the message from linux_base-c6 that's basically > what it told you to do. Thanks for the reply, Gary. Right you are. That's exactly what I did to stage for the upgrade; entered 'compat.linux.osrelease=2.6.18' into etc/sysctl.conf rebooted, deinstalled x11/nvidia-driver, emulators/linux_base-f10, cd emulators/linux_base-c6; make install which led to: ===> linux_base-c6-6.6_3 compat.linux.osrelease: 2.6.16 is not supported, please use 2.6.18, BEWARE this is highly experimental. *** [all] Error code 1 Stop in /usr/ports/emulators/linux_base-c6. Thanks! and sorry for not being more detailed in the first place. --Chris > > Regards, > > Gary > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 01:11:12 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69168F98; Tue, 10 Mar 2015 01:11:12 +0000 (UTC) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD18ED4; Tue, 10 Mar 2015 01:11:12 +0000 (UTC) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YV8hS-000BxP-BR; Tue, 10 Mar 2015 01:11:10 +0000 Date: Tue, 10 Mar 2015 01:11:10 +0000 From: Gary Palmer To: Chris H Subject: Re: Is there a linux_base available for RELENG_9? Message-ID: <20150310011110.GA45784@in-addr.com> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> <20150310005106.GA59888@in-addr.com> <08c23a03a843632af2f105057de45713@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <08c23a03a843632af2f105057de45713@ultimatedns.net> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false Cc: FreeBSD STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:11:12 -0000 On Mon, Mar 09, 2015 at 06:09:04PM -0700, Chris H wrote: > On Tue, 10 Mar 2015 00:51:06 +0000 Gary Palmer wrote > > > On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > > > I performed av svn update for both src (r279796), > > > and ports (r380829) last night. building/installing > > > world/kernel, went as one would hope. Upgrading ports > > > was a different story. Given this box has an nVidia card. > > > I usually start by upgrading emulators/linux_base; which > > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > > I deinstalled x11/nvidia-driver, followed by > > > emulators/linux_base-f10. I then attempted to make install > > > emulators/linux_base-c6, which resulted in a message > > > that it wasn't supported. So I simply cd'd to > > > emulators/linux_base-f10, followed by make install. Which > > > resulted in a CVE message; indicating it was vulnerable > > > to glib issues. I'm now stuck w/o hardware support for > > > my video card, and unable to effectively follow > > > a safe port upgrade path, that enables me to keep the > > > options I have chosen for my currently installed ports. > > > Is there a *safe* linux_base available? > > > > > > Thank you for all your time, and consideration. > > > > If you set > > > > sysctl compat.linux.osrelease=2.6.18 > > > > you can install linux_base-c6 on RELENG_9 > > > > It works well enough at least for nvidia-driver, as my main desktop > > is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 > > installed > > > > Remember to put > > > > compat.linux.osrelease=2.6.18 > > > > into /etc/sysctl.conf so it's preserved on startup > > > > I believe if you read the message from linux_base-c6 that's basically > > what it told you to do. > Thanks for the reply, Gary. > Right you are. That's exactly what I did to stage for the upgrade; > entered 'compat.linux.osrelease=2.6.18' into etc/sysctl.conf > rebooted, deinstalled x11/nvidia-driver, emulators/linux_base-f10, > cd emulators/linux_base-c6; make install > which led to: > ===> linux_base-c6-6.6_3 compat.linux.osrelease: 2.6.16 is not supported, > please use 2.6.18, BEWARE this is highly experimental. > *** [all] Error code 1 > > Stop in /usr/ports/emulators/linux_base-c6. > > Thanks! and sorry for not being more detailed in the first place. For some reason your sysctl.conf setting didn't take. You should investigate why and resolve that and then the port should work. A temporary work around would be to run sysctl compat.linux.osrelease=2.6.18 from a root shell, but it won't last past reboot. Regards, Gary From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 01:19:22 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11A3E33A; Tue, 10 Mar 2015 01:19:22 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D5E52FB3; Tue, 10 Mar 2015 01:19:21 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2A1KqjW005304; Mon, 9 Mar 2015 18:20:52 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Gary Palmer In-Reply-To: <20150310011110.GA45784@in-addr.com> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> <20150310005106.GA59888@in-addr.com> <08c23a03a843632af2f105057de45713@ultimatedns.net>, <20150310011110.GA45784@in-addr.com> From: "Chris H" Subject: Re: Is there a linux_base available for RELENG_9? Date: Mon, 09 Mar 2015 18:20:52 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit Cc: FreeBSD STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:19:22 -0000 On Tue, 10 Mar 2015 01:11:10 +0000 Gary Palmer wrote > On Mon, Mar 09, 2015 at 06:09:04PM -0700, Chris H wrote: > > On Tue, 10 Mar 2015 00:51:06 +0000 Gary Palmer wrote > > > > > On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > > > > I performed av svn update for both src (r279796), > > > > and ports (r380829) last night. building/installing > > > > world/kernel, went as one would hope. Upgrading ports > > > > was a different story. Given this box has an nVidia card. > > > > I usually start by upgrading emulators/linux_base; which > > > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > > > I deinstalled x11/nvidia-driver, followed by > > > > emulators/linux_base-f10. I then attempted to make install > > > > emulators/linux_base-c6, which resulted in a message > > > > that it wasn't supported. So I simply cd'd to > > > > emulators/linux_base-f10, followed by make install. Which > > > > resulted in a CVE message; indicating it was vulnerable > > > > to glib issues. I'm now stuck w/o hardware support for > > > > my video card, and unable to effectively follow > > > > a safe port upgrade path, that enables me to keep the > > > > options I have chosen for my currently installed ports. > > > > Is there a *safe* linux_base available? > > > > > > > > Thank you for all your time, and consideration. > > > > > > If you set > > > > > > sysctl compat.linux.osrelease=2.6.18 > > > > > > you can install linux_base-c6 on RELENG_9 > > > > > > It works well enough at least for nvidia-driver, as my main desktop > > > is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 > > > installed > > > > > > Remember to put > > > > > > compat.linux.osrelease=2.6.18 > > > > > > into /etc/sysctl.conf so it's preserved on startup > > > > > > I believe if you read the message from linux_base-c6 that's basically > > > what it told you to do. > > Thanks for the reply, Gary. > > Right you are. That's exactly what I did to stage for the upgrade; > > entered 'compat.linux.osrelease=2.6.18' into etc/sysctl.conf > > rebooted, deinstalled x11/nvidia-driver, emulators/linux_base-f10, > > cd emulators/linux_base-c6; make install > > which led to: > > ===> linux_base-c6-6.6_3 compat.linux.osrelease: 2.6.16 is not supported, > > please use 2.6.18, BEWARE this is highly experimental. > > *** [all] Error code 1 > > > > Stop in /usr/ports/emulators/linux_base-c6. > > > > Thanks! and sorry for not being more detailed in the first place. > > For some reason your sysctl.conf setting didn't take. You should > investigate why and resolve that and then the port should work. > > A temporary work around would be to run > > sysctl compat.linux.osrelease=2.6.18 > > from a root shell, but it won't last past reboot. LOL right you are *again*. Immediately after replying to your last response, I checked the current status of 'compat.linux.osrelease' which, as you might have guessed, returned 2.18. So I simply entered it manually, followed by cd'ing to emulators/linux_base-c6;make install. Which went beautifully. SO. In my humble defense; UPDATING indicated sysctl.conf(5), when it *actually* meant sysctl(8). :-) Thank you very much, for taking the time to respond, Gary! --Chris > > Regards, > > Gary From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 01:42:00 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B8B3E6; Tue, 10 Mar 2015 01:42:00 +0000 (UTC) Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (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 57E5D303; Tue, 10 Mar 2015 01:42:00 +0000 (UTC) Received: by yhoa41 with SMTP id a41so38115538yho.4; Mon, 09 Mar 2015 18:41:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PhHTg1Pg6d29FL2o3V4FfJLBGZBAAZmI3AIDKlMpvt4=; b=pUKr73vYs1Zzw1ek1CemRZ8AM2gBtg1gsGVxNoVXtl3xtpsf1Ag7qoGzow/4MW8NEx PLm7M8cQrBk8A2kKx0vBKC/0lKAO6wzlNUJnKsJijWTVBl0h5e5eTjSlAvEkEjd1A+aZ yOt2xGFCw1RqKkWK6gSsCTye5Lt1bT+f0lHBd7l5dhbVyoWSai0vpstio57WuI+a+UZg LljBnlL7AvOkPRN2QHNz8gtsjSg/3BdJOsXLN4zlVU93aJonawdLtdqD2eKBv5Qg5q5p AzTkHaPwbFVZbrEWXc8dCCcF9JKOGlZe3lLxk4S+8uTWDe4RaOX3GmHGTfHXlK5tZtkx 7Mnw== MIME-Version: 1.0 X-Received: by 10.170.198.211 with SMTP id p202mr9474266yke.60.1425951719402; Mon, 09 Mar 2015 18:41:59 -0700 (PDT) Received: by 10.170.79.87 with HTTP; Mon, 9 Mar 2015 18:41:59 -0700 (PDT) Received: by 10.170.79.87 with HTTP; Mon, 9 Mar 2015 18:41:59 -0700 (PDT) In-Reply-To: <08c23a03a843632af2f105057de45713@ultimatedns.net> References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> <20150310005106.GA59888@in-addr.com> <08c23a03a843632af2f105057de45713@ultimatedns.net> Date: Mon, 9 Mar 2015 18:41:59 -0700 Message-ID: Subject: Re: Is there a linux_base available for RELENG_9? From: Freddie Cash To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 01:42:00 -0000 Re-read the error message you pasted into the email. Pay particular attention to the part after "2.6", the last two digits. :) 2.6.16 != 2.6.18 The latter is what needs to be in sysctl.conf, or (as you discovered) entered via sysctl(8). You will need to put the correct values into sysctl.conf, though, for it to be set correctly at boot. Cheers, Freddie On Mar 9, 2015 6:07 PM, "Chris H" wrote: > On Tue, 10 Mar 2015 00:51:06 +0000 Gary Palmer wrote > > > On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > > > I performed av svn update for both src (r279796), > > > and ports (r380829) last night. building/installing > > > world/kernel, went as one would hope. Upgrading ports > > > was a different story. Given this box has an nVidia card. > > > I usually start by upgrading emulators/linux_base; which > > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > > I deinstalled x11/nvidia-driver, followed by > > > emulators/linux_base-f10. I then attempted to make install > > > emulators/linux_base-c6, which resulted in a message > > > that it wasn't supported. So I simply cd'd to > > > emulators/linux_base-f10, followed by make install. Which > > > resulted in a CVE message; indicating it was vulnerable > > > to glib issues. I'm now stuck w/o hardware support for > > > my video card, and unable to effectively follow > > > a safe port upgrade path, that enables me to keep the > > > options I have chosen for my currently installed ports. > > > Is there a *safe* linux_base available? > > > > > > Thank you for all your time, and consideration. > > > > If you set > > > > sysctl compat.linux.osrelease=2.6.18 > > > > you can install linux_base-c6 on RELENG_9 > > > > It works well enough at least for nvidia-driver, as my main desktop > > is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 > > installed > > > > Remember to put > > > > compat.linux.osrelease=2.6.18 > > > > into /etc/sysctl.conf so it's preserved on startup > > > > I believe if you read the message from linux_base-c6 that's basically > > what it told you to do. > Thanks for the reply, Gary. > Right you are. That's exactly what I did to stage for the upgrade; > entered 'compat.linux.osrelease=2.6.18' into etc/sysctl.conf > rebooted, deinstalled x11/nvidia-driver, emulators/linux_base-f10, > cd emulators/linux_base-c6; make install > which led to: > ===> linux_base-c6-6.6_3 compat.linux.osrelease: 2.6.16 is not supported, > please use 2.6.18, BEWARE this is highly experimental. > *** [all] Error code 1 > > Stop in /usr/ports/emulators/linux_base-c6. > > Thanks! and sorry for not being more detailed in the first place. > > --Chris > > > > Regards, > > > > Gary > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 04:45:05 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 784DD232 for ; Tue, 10 Mar 2015 04:45:05 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 453A5ACE for ; Tue, 10 Mar 2015 04:45:05 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2A4kZsw017908; Mon, 9 Mar 2015 21:46:36 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Freddie Cash In-Reply-To: References: <8b870ff7de0d308b93b9ffb5edc21fce@ultimatedns.net> <20150310005106.GA59888@in-addr.com> <08c23a03a843632af2f105057de45713@ultimatedns.net>, From: "Chris H" Subject: Re: Is there a linux_base available for RELENG_9? Date: Mon, 09 Mar 2015 21:46:36 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <88e79f73155978f7c2c31e8a5ed94a54@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 04:45:05 -0000 On Mon, 9 Mar 2015 18:41:59 -0700 Freddie Cash wrote > Re-read the error message you pasted into the email. Pay particular > attention to the part after "2.6", the last two digits. :) > > 2.6.16 != 2.6.18 > > The latter is what needs to be in sysctl.conf, or (as you discovered) > entered via sysctl(8). You will need to put the correct values into > sysctl.conf, though, for it to be set correctly at boot. Indeed. Having read UPDATING prior to the attempted upgrade, I followed the advise to add 'compat.linux.osrelease=2.6.18' to sysctl.conf(5). And rebooted. But what turned out to be the *actual* solution, was to use sysctl(8). Applying it directly fixed it. :-) Maybe update UPDATING? ;-) --Chris > > Cheers, > Freddie > On Mar 9, 2015 6:07 PM, "Chris H" wrote: > > > On Tue, 10 Mar 2015 00:51:06 +0000 Gary Palmer wrote > > > > > On Mon, Mar 09, 2015 at 05:44:55PM -0700, Chris H wrote: > > > > I performed av svn update for both src (r279796), > > > > and ports (r380829) last night. building/installing > > > > world/kernel, went as one would hope. Upgrading ports > > > > was a different story. Given this box has an nVidia card. > > > > I usually start by upgrading emulators/linux_base; which > > > > according to UPDATING; meant linux_base-f10 --> linux_base-c6. > > > > I deinstalled x11/nvidia-driver, followed by > > > > emulators/linux_base-f10. I then attempted to make install > > > > emulators/linux_base-c6, which resulted in a message > > > > that it wasn't supported. So I simply cd'd to > > > > emulators/linux_base-f10, followed by make install. Which > > > > resulted in a CVE message; indicating it was vulnerable > > > > to glib issues. I'm now stuck w/o hardware support for > > > > my video card, and unable to effectively follow > > > > a safe port upgrade path, that enables me to keep the > > > > options I have chosen for my currently installed ports. > > > > Is there a *safe* linux_base available? > > > > > > > > Thank you for all your time, and consideration. > > > > > > If you set > > > > > > sysctl compat.linux.osrelease=2.6.18 > > > > > > you can install linux_base-c6 on RELENG_9 > > > > > > It works well enough at least for nvidia-driver, as my main desktop > > > is 9.3-RELEASE-p9 and has nvidia-driver and linux_base-c6-6.6_3 > > > installed > > > > > > Remember to put > > > > > > compat.linux.osrelease=2.6.18 > > > > > > into /etc/sysctl.conf so it's preserved on startup > > > > > > I believe if you read the message from linux_base-c6 that's basically > > > what it told you to do. > > Thanks for the reply, Gary. > > Right you are. That's exactly what I did to stage for the upgrade; > > entered 'compat.linux.osrelease=2.6.18' into etc/sysctl.conf > > rebooted, deinstalled x11/nvidia-driver, emulators/linux_base-f10, > > cd emulators/linux_base-c6; make install > > which led to: > > ===> linux_base-c6-6.6_3 compat.linux.osrelease: 2.6.16 is not supported, > > please use 2.6.18, BEWARE this is highly experimental. > > *** [all] Error code 1 > > > > Stop in /usr/ports/emulators/linux_base-c6. > > > > Thanks! and sorry for not being more detailed in the first place. > > > > --Chris > > > > > > Regards, > > > > > > Gary > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > > " > > > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 11:15:35 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F0098E84 for ; Tue, 10 Mar 2015 11:15:35 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB823993 for ; Tue, 10 Mar 2015 11:15:35 +0000 (UTC) Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 4AF8A40F17; Tue, 10 Mar 2015 11:15:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1425986129; bh=t5mE5rPdv4PSr49XhewtkEIra9VDmwUofkUShRyUIO0=; h=Date:From:To:Subject:References:In-Reply-To:From; b=iHLaGz7oO33OxXUw4yRV5yYwxdADIoT5mAhMBuYYUQyvmQsheNFJI69/Tmn8lzvaR Lk5h46Yzii0pPM2GtdMG37EnMbtw3Oyv1pl7FB++UuE0Fjqjlw8Lbglmp0Hd2RTOe+ qy1acLrO2BMfA6igSJIpcy7jWnO74yw1B/9xOzyY= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: pkubaj) with ESMTPSA id E1E44439F8 Message-ID: <54FED24A.9040503@riseup.net> Date: Tue, 10 Mar 2015 12:15:22 +0100 From: Piotr Kubaj User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Chris H , freebsd-stable@freebsd.org Subject: Re: No sound on 10.1-RELEASE References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.6 at mx1 X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 11:15:36 -0000 On 03/08/15 22:15, Chris H wrote: > On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote > >> On 03/07/15 01:55, Chris H wrote: >>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote >>> >>>> I've got MSI X99 motherboard and am using it with UEFI installation of >>>> 10.1 (BIOS mode doesn't work with FreeBSD). At first, sound worked >>>> properly (even in KDE), but now it doesn't. I'm not sure what happened, >>>> since snd_hda is in kernel (I use GENERIC). I've checked all possible >>>> values of hw.snd.default_unit and turned off KDE to check what happens >>>> when doing cat /dev/random > /dev/dsp (it does nothing). >>>> Attached below is dmesg and /dev/sndstat. >>>> >>> -----8<------- >>> >>>> Installed devices: >>>> pcm0: (play) >>>> pcm1: (play) >>>> pcm2: (play) >>>> pcm3: (play) >>>> pcm4: (play/rec) default >>>> pcm5: (play/rec) >>>> pcm6: (play) >>>> pcm7: (rec) >>> Honestly, this could potentially go a lot of different directions; >>> software/driver(s)/setup... >>> It might be helpful to get the pinouts. The kernel >>> (dmesg(8)) will provide it for you. You can see them by; >>> loader.conf(5) >>> adding the following to /boot/loader.conf: >>> >>> boot_verbose="YES" >>> >>> or by simply selecting boot verbose on the loader menu >>> 6 --> boot verbose >>> >>> and then getting the results from dmesg(8) >>> /var/run/dmesg.boot >>> >>> If everything looks as anticipated, you might check that >>> your software is using the right sound system (OSS). >>> I've had very good experiences on these sound systems by >>> installing >>> audio/xfce4-mixer >>> doing so, always seems to get the correct settings for >>> everything on these boards -- even if you never use >>> the application. >>> Because these boards can be so troublesome where sound >>> is concerned; I used to have a script that would both >>> check, as well as set everything up. But I can't seem >>> to locate it ATM. >>> >>> HTH >>> >>> --Chris >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>> >>> >> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: >> http://pastebin.com/pP0KXp4v > Out of the 4 MSI boards I that I have; 3 run the same > Realtek ALC893 HDA CODEC that yours does. The other, the > Realtek ALC1200 HDA CODEC. All four of them work. But I > notice 1 notable difference; that yours reports 2 > HDA interfaces: > hdac0: > and > hdac1: > I see hdac0 is disregarded (unused) whereas > hdac1 is enabled, and functioning. I think your problems > quite possibly lies in your (sound) system attempting to > use the first HDA device in the list, which is effectively > disabled. If you can determine a way to tell KDE, and friends > to use the 2nd HDA. Things may well go as intended. > None of the 4 MSI boards I have display 2 HDA's, as yours > does. > If you have any additional questions, you may well find > the FreeBSD forums already have answers to your issue. This > is where I originally found answers to my issues, when I > first started using these boards. > > HTH >> >> KDE is definitely using OSS as chosen in its settings (I also use its >> own mixer which can do the same as Xfce's). I also use VLC's Phonon >> backend because Gstreamer is said to cause problems, but that also works >> on 3 other computers. > > > --Chris > > -- > > I don't think it's KDE's fault, as it also happens when I kill KDE (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have vol and pcm maxed out. From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 11:29:21 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 537AF213 for ; Tue, 10 Mar 2015 11:29:21 +0000 (UTC) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F3B8ADF for ; Tue, 10 Mar 2015 11:29:21 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YVILY-0002dP-5s; Tue, 10 Mar 2015 11:29:12 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YVILY-000PiO-3q; Tue, 10 Mar 2015 11:29:12 +0000 To: bsd-lists@bsdforge.com, fjwcash@gmail.com Subject: Re: Is there a linux_base available for RELENG_9? In-Reply-To: <88e79f73155978f7c2c31e8a5ed94a54@ultimatedns.net> Message-Id: From: Pete French Date: Tue, 10 Mar 2015 11:29:12 +0000 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 11:29:21 -0000 > Indeed. Having read UPDATING prior to the attempted upgrade, I > followed the advise to add 'compat.linux.osrelease=2.6.18' > to sysctl.conf(5). And rebooted. If you rebooted then it should have been set - and you should not have needed to do it manually. > But what turned out to be the *actual* solution, was to use > sysctl(8). Applying it directly fixed it. :-) This should not have been necessary if you rebooted. I think you should try and find out what went wrong, as otherwise this will not work when you reboot next time and you will have to set it by hand on each reboot. It sounds like you did all the right things - nt sure why it didnt work for you. Have you rebooted since ? What is the value after rebooting now ? -pete. From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 12:28:26 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3985638 for ; Tue, 10 Mar 2015 12:28:26 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 6481622C for ; Tue, 10 Mar 2015 12:28:25 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2AC5ioZ015423 for ; Tue, 10 Mar 2015 13:05:44 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2AC5iY2015420 for ; Tue, 10 Mar 2015 13:05:44 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdg3JKKP; Tue Mar 10 13:05:40 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 8c452fef; for ; Tue, 10 Mar 2015 13:05:40 +0100 (CET) Date: Tue, 10 Mar 2015 13:05:40 +0100 From: Peter Olsson To: freebsd-stable@FreeBSD.org Subject: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310120540.GN8223@pol-server.leissner.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 12:28:26 -0000 This flag to mergemaster saved a lot of work when I did upgrades the old way, with cvsup and the make steps and then mergemaster: " # Install the new file if it differs only by VCS Id ($FreeBSD) FREEBSD_ID=yes " Is there some equivalent to this flag in freebsd-update/merge? I just did my first major upgrade (8.4-RELEASE-p24 -> 9.3-RELEASE-p10) with freebsd-update. It took more than an hour of manual keyboard activity, most of which could probably be done automatically. (And here I thought that computers were supposed to free us from tedious routine work...) First robotically pressing dd..j.ZZ in a lot of files. Occasionally combined with /<<< to find more places that needed changing in files that didn't fit in the screen. Eg sendmail.cf. Of all these files that needed manual editing I had made my own changes in only one file (/etc/hosts), the rest of them just had this kind of change: The following file could not be merged automatically: /etc/rc.d/nisdomain Press Enter to edit this file in vi and resolve the conflicts manually... <<<<<<< current version # $FreeBSD: src/etc/rc.d/nisdomain,v 1.5.2.2 2013/03/28 13:02:44 svnexp Exp $ ======= # $FreeBSD: releng/9.3/etc/rc.d/nisdomain 193197 2009-06-01 04:55:13Z dougb $ >>>>>>> 9.3-RELEASE And then, after all these edits, I had to wade through entering y to "Does this look reasonable (y/n)?" for all these files! This is of course a necessary step to avoid being bitten by any <<< === >>> lines left behind by mistake (easy to do when you lose your concentration after more than a hundred files), but most of this step could be entirely avoided by automatically accepting the ID changes. (I amused myself by counting all files during this stage. I had to answer y to about 320 files, most of which only had changes in the ID.) This was my first upgrade from 8.4 to 9.3. I have 30 more to go before the 8.4 EoL this summer. I see 30 completely unnecessarily wasted hours in my future... And think of the combined lost man hours worldwide in these upgrades! Merge seems to be a really stupid choice for major upgrades. (Unless of course there is some flag to freebsd-update which makes this kind of change automatically accepted. But I see no such flag in man freebsd-update in 8.4, 9.3 or 10.1.) And yes, I could maybe copy most of /etc from the first upgraded server to the rest of them before upgrading, but that seems error-prone and not really a good solution for every FreeBSD user. -- Peter Olsson From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 13:10:14 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0537C12C for ; Tue, 10 Mar 2015 13:10:14 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B68C18EF for ; Tue, 10 Mar 2015 13:10:13 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1YVJvH-000LMP-92; Tue, 10 Mar 2015 14:10:11 +0100 Date: Tue, 10 Mar 2015 14:10:11 +0100 From: Kurt Jaeger To: Peter Olsson Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310131011.GN62590@home.opsec.eu> References: <20150310120540.GN8223@pol-server.leissner.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150310120540.GN8223@pol-server.leissner.se> Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 13:10:14 -0000 Hi! > This flag to mergemaster saved a lot of work when I did > upgrades the old way, with cvsup and the make steps and > then mergemaster: > " > # Install the new file if it differs only by VCS Id ($FreeBSD) > FREEBSD_ID=yes > " > Is there some equivalent to this flag in freebsd-update/merge? > > I just did my first major upgrade (8.4-RELEASE-p24 -> > 9.3-RELEASE-p10) with freebsd-update. It took more than > an hour of manual keyboard activity, most of which could > probably be done automatically. (And here I thought that > computers were supposed to free us from tedious routine > work...) Well, I've been through this in the past as well. If it helps, it gets much better with more recent versions of FreeBSD (9.3 -> 10.x). So, yes, it's a drag, but it will not repeat in future updates. -- pi@opsec.eu +49 171 3101372 5 years to go ! From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 13:12:41 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 556442EC for ; Tue, 10 Mar 2015 13:12:41 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 100349AF for ; Tue, 10 Mar 2015 13:12:40 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E206A28429; Tue, 10 Mar 2015 14:03:00 +0100 (CET) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 0638C28423; Tue, 10 Mar 2015 14:02:59 +0100 (CET) Message-ID: <54FEEB9A.3020407@quip.cz> Date: Tue, 10 Mar 2015 14:03:22 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Peter Olsson , freebsd-stable@FreeBSD.org Subject: Re: There has to be a better way of merging /etc during a major freebsd-update References: <20150310120540.GN8223@pol-server.leissner.se> In-Reply-To: <20150310120540.GN8223@pol-server.leissner.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 13:12:41 -0000 Peter Olsson wrote on 03/10/2015 13:05: [...] > (I amused myself by counting all files during this stage. > I had to answer y to about 320 files, most of which only > had changes in the ID.) > > This was my first upgrade from 8.4 to 9.3. I have 30 more to go > before the 8.4 EoL this summer. I see 30 completely unnecessarily > wasted hours in my future... > And think of the combined lost man hours worldwide in these upgrades! > Merge seems to be a really stupid choice for major upgrades. [...] This and some other problems with freebsd-update (hanging on the reboot after update) turns me back to using source compiled upgrades. I am compiling 10.1 right now to do the upgrades from 8.4 to 10.1 on 15 machines. Once compiled, I will NFS mount /usr/src and /usr/obj to all machines and will run installkernel, installworld and mergemaster with customized .mergemasterrc. It is more reliable and predictable upgrade, than freebsd-update. (I used freebsd-update for many years, but enough is enough) Miroslav Lachman PS: on PC-BSD there is etcupdate for merging changed files in /etc From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 13:56:35 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EEF2F7A for ; Tue, 10 Mar 2015 13:56:35 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D9FCE64 for ; Tue, 10 Mar 2015 13:56:34 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2ADw6Kk069979; Tue, 10 Mar 2015 06:58:07 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@FreeBSD.org, Peter Olsson In-Reply-To: <20150310120540.GN8223@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> From: "Chris H" Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Date: Tue, 10 Mar 2015 06:58:07 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 13:56:35 -0000 On Tue, 10 Mar 2015 13:05:40 +0100 Peter Olsson wrote > This flag to mergemaster saved a lot of work when I did > upgrades the old way, with cvsup and the make steps and > then mergemaster: > " > # Install the new file if it differs only by VCS Id ($FreeBSD) > FREEBSD_ID=yes > " > Is there some equivalent to this flag in freebsd-update/merge? Hello, Peter. This has probably been answered by now. But just in case. I believe what you're looking for is: mergemaster -vF This is my [chosen] default. I also find it helpful, as a "safety net" to cp _Rp /etc /eetc prior to the mergemaster(8) step. On a related note. I'm not very fond of mergemaster. As a result, I recently took on maintaining sysutils/etcmerge. sysutils/etcupdate, is also a [mergemaster] related port. Hope this helps. --Chris > > I just did my first major upgrade (8.4-RELEASE-p24 -> > 9.3-RELEASE-p10) with freebsd-update. It took more than > an hour of manual keyboard activity, most of which could > probably be done automatically. (And here I thought that > computers were supposed to free us from tedious routine > work...) > > First robotically pressing dd..j.ZZ in a lot of files. > Occasionally combined with /<<< to find more places that > needed changing in files that didn't fit in the screen. > Eg sendmail.cf. > > Of all these files that needed manual editing I had made > my own changes in only one file (/etc/hosts), the rest of > them just had this kind of change: > > The following file could not be merged automatically: /etc/rc.d/nisdomain > Press Enter to edit this file in vi and resolve the conflicts > manually... > > <<<<<<< current version > # $FreeBSD: src/etc/rc.d/nisdomain,v 1.5.2.2 2013/03/28 13:02:44 svnexp Exp $ > ======= > # $FreeBSD: releng/9.3/etc/rc.d/nisdomain 193197 2009-06-01 04:55:13Z dougb $ > >>>>>>> 9.3-RELEASE > > And then, after all these edits, I had to wade through entering > y to "Does this look reasonable (y/n)?" for all these files! > This is of course a necessary step to avoid being bitten by > any <<< === >>> lines left behind by mistake (easy to do when > you lose your concentration after more than a hundred files), > but most of this step could be entirely avoided by automatically > accepting the ID changes. > (I amused myself by counting all files during this stage. > I had to answer y to about 320 files, most of which only > had changes in the ID.) > > This was my first upgrade from 8.4 to 9.3. I have 30 more to go > before the 8.4 EoL this summer. I see 30 completely unnecessarily > wasted hours in my future... > And think of the combined lost man hours worldwide in these upgrades! > Merge seems to be a really stupid choice for major upgrades. > (Unless of course there is some flag to freebsd-update which makes > this kind of change automatically accepted. But I see no such flag > in man freebsd-update in 8.4, 9.3 or 10.1.) > > And yes, I could maybe copy most of /etc from the first > upgraded server to the rest of them before upgrading, but > that seems error-prone and not really a good solution for > every FreeBSD user. > > -- > Peter Olsson > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 14:41:27 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57381C79 for ; Tue, 10 Mar 2015 14:41:27 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CBCE792 for ; Tue, 10 Mar 2015 14:41:27 +0000 (UTC) Received: by igbhn18 with SMTP id hn18so3428039igb.2 for ; Tue, 10 Mar 2015 07:41:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=2cwxa7Og80g5fsrzcSk/ER45Y5cIoOyMWuu1VE38ltU=; b=jCud8s160L2iPCta+1tHEKF+LDYyLAo0kqgxTZWu+fTiK4ADFQUghR1QyvNbhAu1jh //Cu6esY1xyR1uDswnsFbKAgDHwMcBg+fFHo/2zczcE9NYUVdHCj5U3PKYiJXINnYTdM UZDMxVv3CG5SeYB2Py3Ljkq9Ll52zAJAb3egl+cZrFVvCjZVs/KQuTs6x7iY8oZhzUn9 EROHlMtwJJck9VyrxJwair4ntFH3tvlZ2Kc/0gWzK0COj+f7WfsISlCJ/oavrITpg+Qn G7q0CvVS6CSbeKEozG26Q1lFQ7KuJo5ouFvyBsuz5tOcAqJc/7IMP6hnd4r/sEJa+ICn lDAg== MIME-Version: 1.0 X-Received: by 10.42.199.193 with SMTP id et1mt28516650icb.75.1425998486399; Tue, 10 Mar 2015 07:41:26 -0700 (PDT) Received: by 10.107.132.85 with HTTP; Tue, 10 Mar 2015 07:41:26 -0700 (PDT) In-Reply-To: <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> References: <20150310120540.GN8223@pol-server.leissner.se> <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> Date: Tue, 10 Mar 2015 14:41:26 +0000 Message-ID: Subject: Re: There has to be a better way of merging /etc during a major freebsd-update From: Tom Evans Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable , Peter Olsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 14:41:27 -0000 On Tue, Mar 10, 2015 at 1:58 PM, Chris H wrote: > Hello, Peter. > This has probably been answered by now. But just in case. > I believe what you're looking for is: > mergemaster -vF > > This is my [chosen] default. I also find it helpful, > as a "safety net" to > cp _Rp /etc /eetc > > prior to the mergemaster(8) step. I use these steps after new kernel boots OK with old world: zfs set readonly=off zroot zfs mount -a adjkerntz -i mergemaster -piF cd /usr/src make installworld mergemaster -iFPU make delete-old I get very few questions asked of me by mergemaster. Cheers Tom From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 14:46:46 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C7B3F22 for ; Tue, 10 Mar 2015 14:46:46 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0265986C for ; Tue, 10 Mar 2015 14:46:45 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2AEmJlm083837; Tue, 10 Mar 2015 07:48:19 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@FreeBSD.org, Peter Olsson In-Reply-To: <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> References: <20150310120540.GN8223@pol-server.leissner.se>, <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> From: "Chris H" Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Date: Tue, 10 Mar 2015 07:48:19 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <71c86834a9514c94c7ab74bff91a679d@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 14:46:46 -0000 On Tue, 10 Mar 2015 06:58:07 -0700 "Chris H" wrote > On Tue, 10 Mar 2015 13:05:40 +0100 Peter Olsson > wrote > > > This flag to mergemaster saved a lot of work when I did > > upgrades the old way, with cvsup and the make steps and > > then mergemaster: > > " > > # Install the new file if it differs only by VCS Id ($FreeBSD) > > FREEBSD_ID=yes > > " > > Is there some equivalent to this flag in freebsd-update/merge? > Hello, Peter. > This has probably been answered by now. But just in case. > I believe what you're looking for is: > mergemaster -vF > > This is my [chosen] default. I also find it helpful, > as a "safety net" to > cp _Rp /etc /eetc Ahem... On the off chance it wasn't obvious. The above line /should/ have read cp -Rp /etc /eetc ___^ Sorry. --Chris > > prior to the mergemaster(8) step. > > On a related note. I'm not very fond of mergemaster. As > a result, I recently took on maintaining > sysutils/etcmerge. sysutils/etcupdate, is also a > [mergemaster] related port. > > Hope this helps. > > --Chris > > > > I just did my first major upgrade (8.4-RELEASE-p24 -> > > 9.3-RELEASE-p10) with freebsd-update. It took more than .. > > > > -- > > Peter Olsson > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 15:17:19 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A7FB92A7 for ; Tue, 10 Mar 2015 15:17:19 +0000 (UTC) Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73537CD9 for ; Tue, 10 Mar 2015 15:17:19 +0000 (UTC) Received: by pdjy10 with SMTP id y10so2950324pdj.8 for ; Tue, 10 Mar 2015 08:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pUwiA5G/PSeLbC0qM4TbLGXj8WjfpfQlv2T36gVpN4I=; b=jr2Nl/woSkC8O8+3Dq+LFqA4ATKmmwPAqntngMJd/ed3+p6W8qlo0B6K1WjDtKxZcQ 6wB5SXLkXEp6pBP1CBKB1FuLEXYPEO5HIMP12J02OEpjdDhQm3KAeP3qbaMti5r9X/kG T69v0ZWv6Kgpgh+OKiBgxyjvLvXD9RMhphpwMIKVeRCGbNHBXSHPXTdeSweENWCFlxMp QSElJTvjt1I1KBFGwWEF+Ap9tH9QsaE+DFEKYD2MI9J6PjZ2f+zy+/u6fpvfxDzj5uD3 bTvbucIkRrSZjNfBPtcOusLKeNEtt2G/wiWencJRx7Rnnu2r7rAi3GinFcsL+ThSrbo8 gCHQ== MIME-Version: 1.0 X-Received: by 10.66.159.138 with SMTP id xc10mr67258821pab.141.1426000638756; Tue, 10 Mar 2015 08:17:18 -0700 (PDT) Received: by 10.70.110.134 with HTTP; Tue, 10 Mar 2015 08:17:18 -0700 (PDT) In-Reply-To: <20150310120540.GN8223@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> Date: Tue, 10 Mar 2015 10:17:18 -0500 Message-ID: Subject: Re: There has to be a better way of merging /etc during a major freebsd-update From: Adam Vande More To: Peter Olsson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 15:17:19 -0000 On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson wrote: > This flag to mergemaster saved a lot of work when I did > upgrades the old way, with cvsup and the make steps and > then mergemaster: > https://svnweb.freebsd.org/base?view=revision&revision=221780 I'd venture to guess the script will work fine on older installs, but testing should be done first. -- Adam From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 17:43:24 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 820D42D8 for ; Tue, 10 Mar 2015 17:43:24 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5B7337 for ; Tue, 10 Mar 2015 17:43:23 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2AHhJR9026970 for ; Tue, 10 Mar 2015 18:43:19 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2AHhJ3w026969 for ; Tue, 10 Mar 2015 18:43:19 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpd0yg3Dq; Tue Mar 10 18:43:09 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 0a45fbf1; Tue, 10 Mar 2015 18:43:09 +0100 (CET) Date: Tue, 10 Mar 2015 18:43:09 +0100 From: Peter Olsson To: Chris H Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310174309.GA9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2885765b7842d951d89a9712bd5ba86e@ultimatedns.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 17:43:24 -0000 On Tue, Mar 10, 2015 at 06:58:07AM -0700, Chris H wrote: > On Tue, 10 Mar 2015 13:05:40 +0100 Peter Olsson > wrote > > > This flag to mergemaster saved a lot of work when I did > > upgrades the old way, with cvsup and the make steps and > > then mergemaster: > > " > > # Install the new file if it differs only by VCS Id ($FreeBSD) > > FREEBSD_ID=yes > > " > > Is there some equivalent to this flag in freebsd-update/merge? > Hello, Peter. > This has probably been answered by now. But just in case. > I believe what you're looking for is: > mergemaster -vF Yes, that would probably solve my problem. Can I just change this line in /etc/freebsd-update.conf: MergeChanges /etc/ /var/named/etc/ /boot/device.hints to this: MergeChanges /var/named/etc/ /boot/device.hints And run mergemaster after the first freebsd-update install, before I reboot? Thanks! Peter Olsson > This is my [chosen] default. I also find it helpful, > as a "safety net" to > cp _Rp /etc /eetc > > prior to the mergemaster(8) step. > > On a related note. I'm not very fond of mergemaster. As > a result, I recently took on maintaining > sysutils/etcmerge. sysutils/etcupdate, is also a > [mergemaster] related port. > > Hope this helps. > > --Chris > > > > I just did my first major upgrade (8.4-RELEASE-p24 -> > > 9.3-RELEASE-p10) with freebsd-update. It took more than > > an hour of manual keyboard activity, most of which could > > probably be done automatically. (And here I thought that > > computers were supposed to free us from tedious routine > > work...) > > > > First robotically pressing dd..j.ZZ in a lot of files. > > Occasionally combined with /<<< to find more places that > > needed changing in files that didn't fit in the screen. > > Eg sendmail.cf. > > > > Of all these files that needed manual editing I had made > > my own changes in only one file (/etc/hosts), the rest of > > them just had this kind of change: > > > > The following file could not be merged automatically: /etc/rc.d/nisdomain > > Press Enter to edit this file in vi and resolve the conflicts > > manually... > > > > <<<<<<< current version > > # $FreeBSD: src/etc/rc.d/nisdomain,v 1.5.2.2 2013/03/28 13:02:44 svnexp Exp $ > > ======= > > # $FreeBSD: releng/9.3/etc/rc.d/nisdomain 193197 2009-06-01 04:55:13Z dougb $ > > >>>>>>> 9.3-RELEASE > > > > And then, after all these edits, I had to wade through entering > > y to "Does this look reasonable (y/n)?" for all these files! > > This is of course a necessary step to avoid being bitten by > > any <<< === >>> lines left behind by mistake (easy to do when > > you lose your concentration after more than a hundred files), > > but most of this step could be entirely avoided by automatically > > accepting the ID changes. > > (I amused myself by counting all files during this stage. > > I had to answer y to about 320 files, most of which only > > had changes in the ID.) > > > > This was my first upgrade from 8.4 to 9.3. I have 30 more to go > > before the 8.4 EoL this summer. I see 30 completely unnecessarily > > wasted hours in my future... > > And think of the combined lost man hours worldwide in these upgrades! > > Merge seems to be a really stupid choice for major upgrades. > > (Unless of course there is some flag to freebsd-update which makes > > this kind of change automatically accepted. But I see no such flag > > in man freebsd-update in 8.4, 9.3 or 10.1.) > > > > And yes, I could maybe copy most of /etc from the first > > upgraded server to the rest of them before upgrading, but > > that seems error-prone and not really a good solution for > > every FreeBSD user. > > > > -- > > Peter Olsson > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 17:46:00 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A33CB68A for ; Tue, 10 Mar 2015 17:46:00 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 32849382 for ; Tue, 10 Mar 2015 17:45:59 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2AHjxFf027147 for ; Tue, 10 Mar 2015 18:45:59 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2AHjxUd027143 for ; Tue, 10 Mar 2015 18:45:59 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdv7xeay; Tue Mar 10 18:45:55 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 9f5d7543; Tue, 10 Mar 2015 18:45:55 +0100 (CET) Date: Tue, 10 Mar 2015 18:45:54 +0100 From: Peter Olsson To: Adam Vande More Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310174554.GB9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 17:46:00 -0000 On Tue, Mar 10, 2015 at 10:17:18AM -0500, Adam Vande More wrote: > On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson > wrote: > > > This flag to mergemaster saved a lot of work when I did > > upgrades the old way, with cvsup and the make steps and > > then mergemaster: > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > I'd venture to guess the script will work fine on older installs, but > testing should be done first. > > -- > Adam This seems like an excellent addition fo freebsd-update, how come it isn't added? Possibly as a flag, so the default operation isn't changed. Peter Olsson From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 17:55:10 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04EED8E9 for ; Tue, 10 Mar 2015 17:55:10 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::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 C989566E for ; Tue, 10 Mar 2015 17:55:09 +0000 (UTC) Received: by pablj1 with SMTP id lj1so4030723pab.10 for ; Tue, 10 Mar 2015 10:55:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=l6QJ5e4Z16XFFhvaj0nHrNzi/dMx38iCUAPbiFpIe3U=; b=pHK2vkWcgd4s4+yzIX8ThExnolCA5mrX6fvKMF6zar3+MNch/gXSrFv1Fz+bkK8hab R5IQZXkZ5z5b+vbVPJHncCLgA404FXJ6t/l1RjhwtJccJ6hYEkk72dbdkyRyRaav5Bta +xKas41DQ4dC8JZwl5ldt9Pm07imbyFjsoN0x4FcPPxEBcoCXhP929a5e49A4AcLWdOJ Q4Y6s+87jJjSIdh+Yfcqnot0eA6CrfV/Cfj7J8MQuueFZGMrk9hx7UwiYAC+ZxGXX2kT bCJNAQrCh6RnX5DbLkVaapQazFb5I6HJB0DdQ3zpOFNOUXs9fZNme3QfNblyXLNxEsLM ub5w== MIME-Version: 1.0 X-Received: by 10.70.28.130 with SMTP id b2mr69574030pdh.48.1426010109245; Tue, 10 Mar 2015 10:55:09 -0700 (PDT) Received: by 10.70.79.166 with HTTP; Tue, 10 Mar 2015 10:55:09 -0700 (PDT) In-Reply-To: <20150310174554.GB9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <20150310174554.GB9442@pol-server.leissner.se> Date: Tue, 10 Mar 2015 12:55:09 -0500 Message-ID: Subject: Re: There has to be a better way of merging /etc during a major freebsd-update From: Adam Vande More To: Peter Olsson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 17:55:10 -0000 On Tue, Mar 10, 2015 at 12:45 PM, Peter Olsson < list-freebsd-stable@jyborn.se> wrote: > On Tue, Mar 10, 2015 at 10:17:18AM -0500, Adam Vande More wrote: > > On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson < > list-freebsd-stable@jyborn.se > > > wrote: > > > > > This flag to mergemaster saved a lot of work when I did > > > upgrades the old way, with cvsup and the make steps and > > > then mergemaster: > > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > > > I'd venture to guess the script will work fine on older installs, but > > testing should be done first. > > > > -- > > Adam > > This seems like an excellent addition fo freebsd-update, > how come it isn't added? > It is added, no flag needed. You are running a version of freebsd-update which didn't have the feature(8.4). -- Adam From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 17:59:51 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47082A42 for ; Tue, 10 Mar 2015 17:59:51 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id C6E7A6AA for ; Tue, 10 Mar 2015 17:59:50 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2AHxnNL027328 for ; Tue, 10 Mar 2015 18:59:49 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2AHxnr4027327 for ; Tue, 10 Mar 2015 18:59:49 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdySIUux; Tue Mar 10 18:59:46 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id eb609ca0; Tue, 10 Mar 2015 18:59:46 +0100 (CET) Date: Tue, 10 Mar 2015 18:59:46 +0100 From: Peter Olsson To: Adam Vande More Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310175946.GD9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <20150310174554.GB9442@pol-server.leissner.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 17:59:51 -0000 On Tue, Mar 10, 2015 at 12:55:09PM -0500, Adam Vande More wrote: > On Tue, Mar 10, 2015 at 12:45 PM, Peter Olsson < > list-freebsd-stable@jyborn.se> wrote: > > > On Tue, Mar 10, 2015 at 10:17:18AM -0500, Adam Vande More wrote: > > > On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson < > > list-freebsd-stable@jyborn.se > > > > wrote: > > > > > > > This flag to mergemaster saved a lot of work when I did > > > > upgrades the old way, with cvsup and the make steps and > > > > then mergemaster: > > > > > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > > > > > I'd venture to guess the script will work fine on older installs, but > > > testing should be done first. > > > > > > -- > > > Adam > > > > This seems like an excellent addition fo freebsd-update, > > how come it isn't added? > > > > It is added, no flag needed. You are running a version of freebsd-update > which didn't have the feature(8.4). > > -- > Adam Ok, I see, thanks! Peter Olsson From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 19:00:21 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C961CFA for ; Tue, 10 Mar 2015 19:00:21 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 102DADB3 for ; Tue, 10 Mar 2015 19:00:20 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2AJ1s01001255; Tue, 10 Mar 2015 12:01:54 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Peter Olsson , Adam Vande More In-Reply-To: References: <20150310120540.GN8223@pol-server.leissner.se>, From: "Chris H" Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Date: Tue, 10 Mar 2015 12:01:54 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 19:00:21 -0000 On Tue, 10 Mar 2015 10:17:18 -0500 Adam Vande More wrote > On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson > wrote: > > > This flag to mergemaster saved a lot of work when I did > > upgrades the old way, with cvsup and the make steps and > > then mergemaster: > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > I'd venture to guess the script will work fine on older installs, but > testing should be done first. Isn't that pretty much what the -F flag, I mentioned does? "-F If the files differ only by VCS Id ($FreeBSD) install the new file." In all honesty, I too got stuck answering "y" ~100 times, way back when. And decided I needed to either find a better way, or see if the mergemaster(8) had any secrets I wasn't aware of. ;-) --Chris > > -- > Adam > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 19:08:23 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04F47F2E for ; Tue, 10 Mar 2015 19:08:23 +0000 (UTC) Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C2DF4E9A for ; Tue, 10 Mar 2015 19:08:22 +0000 (UTC) Received: by pdjy10 with SMTP id y10so4413151pdj.12 for ; Tue, 10 Mar 2015 12:08:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BYqFqSzfKOU18iYnKujpU2dyNurJV7zwgw3HwtormiU=; b=O4XRcNiQVVh4p6c4XqH4mAfeG41a8nWuqpzdZ+kYeAssG6wPaDnttqoY3V30xpAXQ+ z4WJOvNuiCuH2gDeMxB3CSvdlLwf4iTs+/mq5GpeZVnKIAPwtED+PZ4hNGy0JCloqMC5 P8caacPB+IUel3ZN1DmzrUM2cSWOeYBEo2IqCtiGWSpPzLIjuUyGX/GcnLKHHnp91vuS Xy6bYpLEShQ5QejNSOGdBLVoky6qJnxMZG6g0n9sEww2pKLVszApZNUaQ8hok4Fm/XVs FirR094GK9Ao+66C4xmXLbACYG1Jr6i0lhzvh6W6gMHIZs58Kzhm5tP701FDMSFpZaj9 lnBw== MIME-Version: 1.0 X-Received: by 10.66.63.106 with SMTP id f10mr69541940pas.0.1426014501259; Tue, 10 Mar 2015 12:08:21 -0700 (PDT) Received: by 10.70.79.166 with HTTP; Tue, 10 Mar 2015 12:08:21 -0700 (PDT) In-Reply-To: <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> References: <20150310120540.GN8223@pol-server.leissner.se> <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> Date: Tue, 10 Mar 2015 14:08:21 -0500 Message-ID: Subject: Re: There has to be a better way of merging /etc during a major freebsd-update From: Adam Vande More To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" , Peter Olsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 19:08:23 -0000 On Tue, Mar 10, 2015 at 2:01 PM, Chris H wrote: > > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > > > I'd venture to guess the script will work fine on older installs, but > > testing should be done first. > Isn't that pretty much what the -F flag, I mentioned does? > "-F If the files differ only by VCS Id ($FreeBSD) install the > new file." > Op asked for a freebsd-update solution which excludes any mergemaster solution short of at least a partial rewrite. -- Adam From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 19:18:43 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5FADE3CC for ; Tue, 10 Mar 2015 19:18:43 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24530FA7 for ; Tue, 10 Mar 2015 19:18:43 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2AJKGWY002478; Tue, 10 Mar 2015 12:20:16 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Adam Vande More In-Reply-To: References: <20150310120540.GN8223@pol-server.leissner.se> <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net>, From: "Chris H" Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Date: Tue, 10 Mar 2015 12:20:16 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit Cc: "freebsd-stable@freebsd.org" , Peter Olsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 19:18:43 -0000 On Tue, 10 Mar 2015 14:08:21 -0500 Adam Vande More wrote > On Tue, Mar 10, 2015 at 2:01 PM, Chris H wrote: > > > > > > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > > > > > I'd venture to guess the script will work fine on older installs, but > > > testing should be done first. > > Isn't that pretty much what the -F flag, I mentioned does? > > "-F If the files differ only by VCS Id ($FreeBSD) install the > > new file." > > > > Op asked for a freebsd-update solution which excludes any mergemaster > solution short of at least a partial rewrite. Ahem... right you are! Speaking of reading things, it'd kill me to read more closely, before replying. :P Sorry, Adam. --Chris > > -- > Adam > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 19:18:52 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C491A4BB for ; Tue, 10 Mar 2015 19:18:52 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 50FF7FAD for ; Tue, 10 Mar 2015 19:18:51 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2AJInd0029127 for ; Tue, 10 Mar 2015 20:18:49 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2AJInAa029126 for ; Tue, 10 Mar 2015 20:18:49 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdaMfLrL; Tue Mar 10 20:18:49 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 21732571; Tue, 10 Mar 2015 20:18:49 +0100 (CET) Date: Tue, 10 Mar 2015 20:18:49 +0100 From: Peter Olsson To: Chris H Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310191849.GI9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Adam Vande More , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 19:18:52 -0000 On Tue, Mar 10, 2015 at 12:01:54PM -0700, Chris H wrote: > On Tue, 10 Mar 2015 10:17:18 -0500 Adam Vande More > wrote > > > On Tue, Mar 10, 2015 at 7:05 AM, Peter Olsson > > wrote: > > > > > This flag to mergemaster saved a lot of work when I did > > > upgrades the old way, with cvsup and the make steps and > > > then mergemaster: > > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=221780 > > > > I'd venture to guess the script will work fine on older installs, but > > testing should be done first. > Isn't that pretty much what the -F flag, I mentioned does? > "-F If the files differ only by VCS Id ($FreeBSD) install the > new file." > In all honesty, I too got stuck answering "y" ~100 times, way > back when. And decided I needed to either find a better way, > or see if the mergemaster(8) had any secrets I wasn't > aware of. ;-) I think you are mixing up mergemaster with merge. Freebsd-update uses merge, not mergemaster. (But I will try running freebsd-update without merging /etc, and use mergemaster -F instead. Should solve my problem.) Peter Olsson From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 20:34:10 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AFD1EBC2 for ; Tue, 10 Mar 2015 20:34:10 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 88FFCB89 for ; Tue, 10 Mar 2015 20:34:10 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E1078B913; Tue, 10 Mar 2015 16:34:08 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: Suspected libkvm infinite loop Date: Tue, 10 Mar 2015 14:10:09 -0400 Message-ID: <4637620.LE11f9AQj7@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <54FE3803.2000307@akips.com> References: <54FE3803.2000307@akips.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 10 Mar 2015 16:34:09 -0400 (EDT) Cc: Nick Frampton X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 20:34:10 -0000 On Tuesday, March 10, 2015 10:17:07 AM Nick Frampton wrote: > Hi, > > For the past several months, we have had an intermittent problem where a > process calling kvm_openfiles(3) or kvm_getprocs(3) (not sure which) gets > stuck in an infinite loop and goes to 100% cpu. We have just observed > "fstat -m" do the same thing and suspect it may be the same problem. > > Our environment is a 10.1-RELEASE-p6 amd64 guest running in VirtualBox, with > ufs root and zfs /home. > > Has anyone else experienced this? Is there anything we can do to investigate > the problem further? Often loops using libkvm are due to programs using libkvm are trying to read kernel data structures while they are changing. However, if you use sysctls to fetch this data instead, you should be able to get a stable snapshot of the system state without getting stuck in a possible loop. I believe for libkvm to use sysctl instead of /dev/kmem you have to pass a NULL for the kernel and "/dev/null" for the core image. fstat -m should be doing that by default however, so if it is not that, can you ktrace fstat when it is spinning to see if it is spinning userland or in the kernel? If you see no activity via ktrace, then it is spinning in one of the two places without making any system calls, etc. You can attach to it with gdb to pause it, then see where gdb thinks it is. If gdb hangs attaching to it, then it is stuck in the kernel. If gdb attaches to it ok, then it is spinning in userland. Unfortunately, for gdb to be useful, you really need debug symbols. We don't currently provide those for release binaries or binaries provided via freebsd-update (though that is being worked on for 11.0). If you build from source, then the simplest way to get this is to add 'WITH_DEBUG_FILES=yes' to /etc/src.conf and rebuild your world without NO_CLEAN. If you are building from source and are able to reproduce with those binaries, then after attaching to the process with gdb, use 'bt' to see where it is hung and reply with that. If it is hanging in the kernel, then you will need to use the kernel debugger to see where it is hanging. The simplest way to do this is probably to force a crash via the debug.kdb.panic sysctl (set it to a non-zero value). You will then need to fire up kgdb on the crash dump after it reboots, switch to the fstat process via the 'proc ' command and get a backtrace via 'bt'. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 21:59:19 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06D293B9; Tue, 10 Mar 2015 21:59:19 +0000 (UTC) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C542580B; Tue, 10 Mar 2015 21:59:18 +0000 (UTC) Received: by pabrd3 with SMTP id rd3so5637489pab.5; Tue, 10 Mar 2015 14:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Ldj8/YChVqSp8ZlnLwzi7EUGt/SA/O7Sce1XPMi5BAo=; b=kyswx/TDtzgriTz2dJ7lPy8YtiuajahW0VhpY5cM9w45bMM89GfTAC+nr2MuRIyGHS YKThOsBMu+0nF0dW+mSSqBAByLyuQQe3ONTusJGKL3V2fghHHCmI1wsYOHGmpkUE2EU4 ixAdd74q/z5/iBbNi1B0V1bmZvITK0v/yI73nPNAYzKyukih00TdKiy9q02JKnFJnE2b AQcAtAYh3pMclbEXP1GH9RklvSxYVtTyuJfqkoEz7327UnUrCzSsKMepKFi3rY/1UIBm eWMyMZxmCvk/yVC0N52o0Am+FGA0Ise/IY/mFCuAg5AqzEuNbJHJrwzuAezb6SqjLBef HRdw== X-Received: by 10.70.34.129 with SMTP id z1mr21154517pdi.113.1426024758181; Tue, 10 Mar 2015 14:59:18 -0700 (PDT) Received: from charmander.picturesperfect.net (c-67-182-131-225.hsd1.wa.comcast.net. [67.182.131.225]) by mx.google.com with ESMTPSA id ux7sm2655046pab.19.2015.03.10.14.59.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2015 14:59:17 -0700 (PDT) Sender: Mark Johnston Date: Tue, 10 Mar 2015 14:59:13 -0700 From: Mark Johnston To: John Baldwin Subject: Re: Suspected libkvm infinite loop Message-ID: <20150310215913.GB52108@charmander.picturesperfect.net> References: <54FE3803.2000307@akips.com> <4637620.LE11f9AQj7@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4637620.LE11f9AQj7@ralph.baldwin.cx> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Nick Frampton , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 21:59:19 -0000 On Tue, Mar 10, 2015 at 02:10:09PM -0400, John Baldwin wrote: > On Tuesday, March 10, 2015 10:17:07 AM Nick Frampton wrote: > > Hi, > > > > For the past several months, we have had an intermittent problem where a > > process calling kvm_openfiles(3) or kvm_getprocs(3) (not sure which) gets > > stuck in an infinite loop and goes to 100% cpu. We have just observed > > "fstat -m" do the same thing and suspect it may be the same problem. > > > > Our environment is a 10.1-RELEASE-p6 amd64 guest running in VirtualBox, with > > ufs root and zfs /home. > > > > Has anyone else experienced this? Is there anything we can do to investigate > > the problem further? > > Often loops using libkvm are due to programs using libkvm are trying to read > kernel data structures while they are changing. However, if you use sysctls > to fetch this data instead, you should be able to get a stable snapshot of the > system state without getting stuck in a possible loop. I believe for libkvm > to use sysctl instead of /dev/kmem you have to pass a NULL for the kernel and > "/dev/null" for the core image. fstat -m should be doing that by default > however, so if it is not that, can you ktrace fstat when it is spinning to see > if it is spinning userland or in the kernel? If you see no activity via > ktrace, then it is spinning in one of the two places without making any system > calls, etc. You can attach to it with gdb to pause it, then see where gdb > thinks it is. If gdb hangs attaching to it, then it is stuck in the kernel. > > If gdb attaches to it ok, then it is spinning in userland. Unfortunately, for > gdb to be useful, you really need debug symbols. We don't currently provide > those for release binaries or binaries provided via freebsd-update (though > that is being worked on for 11.0). If you build from source, then the > simplest way to get this is to add 'WITH_DEBUG_FILES=yes' to /etc/src.conf and > rebuild your world without NO_CLEAN. If you are building from source and are > able to reproduce with those binaries, then after attaching to the process > with gdb, use 'bt' to see where it is hung and reply with that. > > If it is hanging in the kernel, then you will need to use the kernel debugger > to see where it is hanging. The simplest way to do this is probably to force > a crash via the debug.kdb.panic sysctl (set it to a non-zero value). You will > then need to fire up kgdb on the crash dump after it reboots, switch to the > fstat process via the 'proc ' command and get a backtrace via 'bt'. It sounds like this issue might be the one fixed in r272566: if the KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an sbuf error return value could bubble up and be treated as ERESTART, resulting in a loop. This can be confirmed with something like dtrace -n 'syscall:::entry /pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p If the output consists solely of __sysctl, this bug is likely the culprit. -Mark From owner-freebsd-stable@FreeBSD.ORG Tue Mar 10 22:15:56 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19049677 for ; Tue, 10 Mar 2015 22:15:56 +0000 (UTC) Received: from arha.morrow.me.uk (arha.morrow.me.uk [176.58.88.145]) by mx1.freebsd.org (Postfix) with ESMTP id D379C9D3 for ; Tue, 10 Mar 2015 22:15:55 +0000 (UTC) Received: from anubis.morrow.me.uk (unknown [93.89.81.46]) (Authenticated sender: mauzo) by arha.morrow.me.uk (Postfix) with ESMTPSA id EEB28B0636; Tue, 10 Mar 2015 22:06:43 +0000 (GMT) Received: by anubis.morrow.me.uk (Postfix, from userid 5001) id 9FD5017DE5; Tue, 10 Mar 2015 22:06:39 +0000 (GMT) Date: Tue, 10 Mar 2015 22:06:37 +0000 From: Ben Morrow To: list-freebsd-stable@jyborn.se, freebsd-stable@freebsd.org Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150310220635.GA90305@anubis.morrow.me.uk> Mail-Followup-To: list-freebsd-stable@jyborn.se, freebsd-stable@freebsd.org References: <20150310120540.GN8223@pol-server.leissner.se> <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150310191849.GI9442@pol-server.leissner.se> X-Newsgroups: gmane.os.freebsd.stable User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Mar 2015 22:15:56 -0000 Quoth Peter Olsson : > > (But I will try running freebsd-update without merging /etc, > and use mergemaster -F instead. Should solve my problem.) I'm fairly sure this won't do what you want, and in fact won't work at all, unless your /etc is identical to the stock /etc installed from the ISO. (Which it isn't, of course.) installworld specifically avoids installing the files in /etc; then, when you run mergemaster, it installs the new versions of those files into a temporary directory and merges them with the existing /etc. freebsd-update works a little differently: because it doesn't have a source tree available, it has to fetch the stock versions of the files in /etc for the release you're upgrading from, so that it can patch them to the new release and then merge the changes into your current /etc. If you tell freebsd-update to install /etc without merging it will blindly update files you haven't changed (which is probably what you want) but (I think) will fail to update the files that you have changed, because it uses binary patches which won't apply to your modified versions. If you want a rather hackish solution, you could try something like this: - Rename /etc to /oldetc. - Find yourself a copy of the stock /etc for the version you are upgrading from. (tar -xpf base.txz --include /etc) - Run freebsd-update with /etc removed from the merge list. This will (should?) give you a stock /etc for the version you are upgrading to. - Rename /etc -> /tmp/etc, /oldetc -> /etc and run mergemaster with -t /tmp. Obviously I would script this if I was doing more than one or two machines. Ben From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 00:30:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5635E528 for ; Wed, 11 Mar 2015 00:30:08 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29339BED for ; Wed, 11 Mar 2015 00:30:08 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2B0Vgsd025289; Tue, 10 Mar 2015 17:31:42 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: fjwcash@gmail.com, Pete French In-Reply-To: References: From: "Chris H" Subject: Re: Is there a linux_base available for RELENG_9? Date: Tue, 10 Mar 2015 17:31:42 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <55390460cd3ce7854089fe03066ee7e0@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 00:30:08 -0000 On Tue, 10 Mar 2015 11:29:12 +0000 Pete French wrote > > Indeed. Having read UPDATING prior to the attempted upgrade, I > > followed the advise to add 'compat.linux.osrelease=2.6.18' > > to sysctl.conf(5). And rebooted. > > If you rebooted then it should have been set - and you should > not have needed to do it manually. > > > But what turned out to be the *actual* solution, was to use > > sysctl(8). Applying it directly fixed it. :-) > > This should not have been necessary if you rebooted. I think > you should try and find out what went wrong, as otherwise this > will not work when you reboot next time and you will have to set it > by hand on each reboot. > > It sounds like you did all the right things - nt sure why it didnt > work for you. > > Have you rebooted since ? What is the value after rebooting now ? Hello Peter, and thank you for the reply. I only just now got a chance to bounce the box. I first sysctl compat.linux.osrelease=2.6.16 as that's what it reported, after the [kern/world] install, and before/during my attempts to install -c6. I then confirmed the setting via sysctl, then confirmed sysctl.conf(5) had the sysctl compat.linux.osrelease=2.6.18 setting listed. Bounced the box, and the sysctl.conf settings took. I have absolutely no idea why it wouldn't work as stated in UPDATING, or after loading it in sysctl.conf, yesterday. But it *apparently* works now. I think, under the circumstances, I'd do well to continue to monitor that setting for awhile. Fortunately, given it's FreeBSD, and a server, I won't have a need to bounce it very often. Thanks again, Peter, for taking the time to reply. --Chris > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 01:05:17 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D440C39 for ; Wed, 11 Mar 2015 01:05:17 +0000 (UTC) Received: from gw.catspoiler.org (cl-1657.chi-02.us.sixxs.net [IPv6:2001:4978:f:678::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCA8CF61 for ; Wed, 11 Mar 2015 01:05:16 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t2B155sY086709; Tue, 10 Mar 2015 17:05:11 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201503110105.t2B155sY086709@gw.catspoiler.org> Date: Tue, 10 Mar 2015 18:05:05 -0700 (PDT) From: Don Lewis Subject: Re: There has to be a better way of merging /etc during a major freebsd-update To: 000.fbsd@quip.cz In-Reply-To: <54FEEB9A.3020407@quip.cz> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-stable@FreeBSD.org, list-freebsd-stable@jyborn.se X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 01:05:17 -0000 On 10 Mar, Miroslav Lachman wrote: > This and some other problems with freebsd-update (hanging on the reboot > after update) turns me back to using source compiled upgrades. > I am compiling 10.1 right now to do the upgrades from 8.4 to 10.1 on 15 > machines. I only do source upgrades, but I've still run into the hang on reboot problem with 10.1-STABLE. The problem seems to have gone away when I switched the root filesystem (there's actually only one filesystem on that machine) from SU+J to SU. From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 01:11:13 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 797AFE80 for ; Wed, 11 Mar 2015 01:11:13 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49195CD for ; Wed, 11 Mar 2015 01:11:13 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2B1Cl9m027686; Tue, 10 Mar 2015 18:12:47 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@freebsd.org, Piotr Kubaj In-Reply-To: <54FED24A.9040503@riseup.net> References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> , <54FED24A.9040503@riseup.net> From: "Chris H" Subject: Re: No sound on 10.1-RELEASE Date: Tue, 10 Mar 2015 18:12:48 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 01:11:13 -0000 On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj wrote > On 03/08/15 22:15, Chris H wrote: > > On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote > > > >> On 03/07/15 01:55, Chris H wrote: > >>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote > >>> > >>>> I've got MSI X99 motherboard and am using it with UEFI installation of ----8<---BIG-SNIP--- > >>> > >> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: > >> http://pastebin.com/pP0KXp4v > > Out of the 4 MSI boards I that I have; 3 run the same > > Realtek ALC893 HDA CODEC that yours does. The other, the > > Realtek ALC1200 HDA CODEC. All four of them work. But I > > notice 1 notable difference; that yours reports 2 > > HDA interfaces: > > hdac0: > > and > > hdac1: > > I see hdac0 is disregarded (unused) whereas > > hdac1 is enabled, and functioning. I think your problems > > quite possibly lies in your (sound) system attempting to > > use the first HDA device in the list, which is effectively > > disabled. If you can determine a way to tell KDE, and friends > > to use the 2nd HDA. Things may well go as intended. > > None of the 4 MSI boards I have display 2 HDA's, as yours > > does. > > If you have any additional questions, you may well find > > the FreeBSD forums already have answers to your issue. This > > is where I originally found answers to my issues, when I > > first started using these boards. > > > > HTH > >> > >> KDE is definitely using OSS as chosen in its settings (I also use its > >> own mixer which can do the same as Xfce's). I also use VLC's Phonon > >> backend because Gstreamer is said to cause problems, but that also works > >> on 3 other computers. > > > I don't think it's KDE's fault, as it also happens when I kill KDE > (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have > vol and pcm maxed out. If your speakers are amplified, you should hear them "pop", when the kernel finds, and creates/attaches the driver(s) to it. Same would be true, if you were wearing your headphones when bouncing your box. I'm quite sure that the sound system is defaulting the the first HDA presented. Which, in your case, is the one that is disabled/ non-operational. It's not KDE per se; but how the software decides, by default, to hook sound up. If you had a sound control panel available in KDE. You *should* be able to *choose* which sound device to use. In your case, provided it's even seen, it would be the *2nd* HDA. The sound control panel should also present the *status* of the sound device that it's using. Which, in your case, would indicate everything as being "muted", and/or "unavailable". On the box I'm writing this from, the HDA/CODEC is the Realtek ALC893, as yours is. I have it hooked up to a 700 watt external amplifier that I use as sound for my entire house. With the amplifier turned on, if I bounce the box (reboot) I hear a "pop" when the kernel detects/attaches to the sound chip. These are the relevant, and only "sound" related devices, created/listed in /dev: cd0 dsp0.0 dsp1.0 dsp2.0 dsp4.0 midistat mixer0 mixer1 mixer2 mixer4 sndstat If I'm not mistaken, you're probably running GENERIC, which has *also* loaded snd_hda, and possibly/probably, others. Which accounts for the additional HDA listing in dmesg(8). What I would do, if I were you, is build/install a custom kernel, stripped of any device not available on your MB. This is the first thing I do, after a fresh install, and, as you're discovering, for good reason. :) You should also find, by doing so, that your system performs much better, as a result. The *only* sound related listings I have in my KERNCONF file, is: speaker # PC beeper sound # geneic sound snd_hda # Realtec CODEC HDA Last, and only because I have to say it; you *are* sure that you have your headphones/speakers plugged into the *correct* jack, right? ;-) Hey! It happens. :) --Chris -- From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 02:18:59 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32101C55; Wed, 11 Mar 2015 02:18:59 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0505A1E; Wed, 11 Mar 2015 02:18:58 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 757DC28428; Wed, 11 Mar 2015 03:18:54 +0100 (CET) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 93D2D28427; Wed, 11 Mar 2015 03:18:53 +0100 (CET) Message-ID: <54FFA623.4020308@quip.cz> Date: Wed, 11 Mar 2015 03:19:15 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Don Lewis Subject: Re: There has to be a better way of merging /etc during a major freebsd-update References: <201503110105.t2B155sY086709@gw.catspoiler.org> In-Reply-To: <201503110105.t2B155sY086709@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, list-freebsd-stable@jyborn.se X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 02:18:59 -0000 Don Lewis wrote on 03/11/2015 02:05: > On 10 Mar, Miroslav Lachman wrote: > >> This and some other problems with freebsd-update (hanging on the reboot >> after update) turns me back to using source compiled upgrades. >> I am compiling 10.1 right now to do the upgrades from 8.4 to 10.1 on 15 >> machines. > > I only do source upgrades, but I've still run into the hang on reboot > problem with 10.1-STABLE. The problem seems to have gone away when I > switched the root filesystem (there's actually only one filesystem on > that machine) from SU+J to SU. It is a strange. I am not using SU+J on any machine, but some machines did hang on reboot after freebsd-update even on an older releases like 8.x or 9.x. Upgraded from 9.1 an 9.2 to 10.1 from sources and rebooted without problem. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 04:00:51 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3340A93; Wed, 11 Mar 2015 04:00:51 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 8D23E6D6; Wed, 11 Mar 2015 04:00:51 +0000 (UTC) Received: from [10.1.8.7] (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id D3B8B28029; Wed, 11 Mar 2015 14:00:43 +1000 (EST) Message-ID: <54FFBDE9.5060702@akips.com> Date: Wed, 11 Mar 2015 14:00:41 +1000 From: Nick Frampton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Mark Johnston , John Baldwin Subject: Re: Suspected libkvm infinite loop References: <54FE3803.2000307@akips.com> <4637620.LE11f9AQj7@ralph.baldwin.cx> <20150310215913.GB52108@charmander.picturesperfect.net> In-Reply-To: <20150310215913.GB52108@charmander.picturesperfect.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 04:00:51 -0000 On 11/03/15 07:59, Mark Johnston wrote: > On Tue, Mar 10, 2015 at 02:10:09PM -0400, John Baldwin wrote: >> Often loops using libkvm are due to programs using libkvm are trying to read >> kernel data structures while they are changing. However, if you use sysctls >> to fetch this data instead, you should be able to get a stable snapshot of the >> system state without getting stuck in a possible loop. I believe for libkvm >> to use sysctl instead of /dev/kmem you have to pass a NULL for the kernel and >> "/dev/null" for the core image. In our code, we're invoking kvm_openfiles as you suggest: kd = kvm_openfiles (NULL, _PATH_DEVNULL, NULL, O_RDONLY, errbuf) > It sounds like this issue might be the one fixed in r272566: if the > KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an > sbuf error return value could bubble up and be treated as ERESTART, > resulting in a loop. > > This can be confirmed with something like > > dtrace -n 'syscall:::entry /pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p > > If the output consists solely of __sysctl, this bug is likely the > culprit. Unfortunately, I accidentally killed fstat this morning before I could do any further debug. I ran truss -p on it yesterday and it was spinning solely on __sysctl. I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the problem in a reasonable time frame so it could be days or weeks before we see it happen again. -Nick From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 09:19:46 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7D674F7 for ; Wed, 11 Mar 2015 09:19:46 +0000 (UTC) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 5219CB65 for ; Wed, 11 Mar 2015 09:19:45 +0000 (UTC) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.14.9/8.14.9) with ESMTP id t2B9JgtY053657 for ; Wed, 11 Mar 2015 10:19:42 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.14.9/8.14.9/Submit) id t2B9JgXA053655 for ; Wed, 11 Mar 2015 10:19:42 +0100 (CET) (envelope-from list-freebsd-stable@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdNDZL7T; Wed Mar 11 10:19:33 2015 Received: from localhost (2968@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 6abca8f4; for ; Wed, 11 Mar 2015 10:19:33 +0100 (CET) Date: Wed, 11 Mar 2015 10:19:33 +0100 From: Peter Olsson To: freebsd-stable@freebsd.org Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Message-ID: <20150311091933.GM9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <1d4863fa5d3f1374a9fa5f9bd19d01b7@ultimatedns.net> <20150310220635.GA90305@anubis.morrow.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150310220635.GA90305@anubis.morrow.me.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 09:19:47 -0000 On Tue, Mar 10, 2015 at 10:06:37PM +0000, Ben Morrow wrote: > Quoth Peter Olsson : > > > > (But I will try running freebsd-update without merging /etc, > > and use mergemaster -F instead. Should solve my problem.) > > I'm fairly sure this won't do what you want, and in fact won't work at > all, unless your /etc is identical to the stock /etc installed from the > ISO. (Which it isn't, of course.) > > installworld specifically avoids installing the files in /etc; then, > when you run mergemaster, it installs the new versions of those files > into a temporary directory and merges them with the existing /etc. > > freebsd-update works a little differently: because it doesn't have a > source tree available, it has to fetch the stock versions of the files > in /etc for the release you're upgrading from, so that it can patch them > to the new release and then merge the changes into your current /etc. If > you tell freebsd-update to install /etc without merging it will blindly > update files you haven't changed (which is probably what you want) but > (I think) will fail to update the files that you have changed, because > it uses binary patches which won't apply to your modified versions. > > If you want a rather hackish solution, you could try something like > this: > > - Rename /etc to /oldetc. > - Find yourself a copy of the stock /etc for the version you are > upgrading from. (tar -xpf base.txz --include /etc) > - Run freebsd-update with /etc removed from the merge list. This > will (should?) give you a stock /etc for the version you are > upgrading to. > - Rename /etc -> /tmp/etc, /oldetc -> /etc and run mergemaster with > -t /tmp. > > Obviously I would script this if I was doing more than one or two > machines > > Ben I'm not really clear on what will happen if I remove /etc/ from MergeChanges in freebsd-update.conf. Will my /etc then be ignored by freebsd-update, or will my /etc be completely overwritten by freebsd-update? Anyway, your hack could be useful to me. There are no more than about ten files I usually change in /etc, so saving the current /etc, installing a stock /etc, running freebsd-update and then running diff -r to sort out my changes could work. But I'm a little worried about removing my /etc changes from a running server. Thanks! Peter Olsson From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 10:47:02 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2A29C8D for ; Wed, 11 Mar 2015 10:47:02 +0000 (UTC) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2a02:b90:3002:e550::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0BBB78B for ; Wed, 11 Mar 2015 10:47:02 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YVeAA-000DKZ-28; Wed, 11 Mar 2015 10:46:54 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YVeA9-000NbE-TY; Wed, 11 Mar 2015 10:46:53 +0000 To: bsd-lists@bsdforge.com, freebsd-stable@freebsd.org, pkubaj@riseup.net Subject: Re: No sound on 10.1-RELEASE In-Reply-To: <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> Message-Id: From: Pete French Date: Wed, 11 Mar 2015 10:46:53 +0000 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 10:47:03 -0000 I havent really followed this thread in great detail, but I just remembered that I also have an MSI motjherboard with onboard sound, pyus a graphics card with sound on it. I have to ouyht this in sysctl.conf hw.snd.default_unit=1 to make sure sound comes out of the onboard port not the graphics card, as the kernel finds them in the opposite order. Could something this work for you maybe ? -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 14:54:16 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81ADD5BD for ; Wed, 11 Mar 2015 14:54:16 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F60894F for ; Wed, 11 Mar 2015 14:54:16 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id ABA9CB918; Wed, 11 Mar 2015 10:54:14 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: There has to be a better way of merging /etc during a major freebsd-update Date: Wed, 11 Mar 2015 10:51:05 -0400 Message-ID: <6135520.eb0tS7GDFh@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <20150311091933.GM9442@pol-server.leissner.se> References: <20150310120540.GN8223@pol-server.leissner.se> <20150310220635.GA90305@anubis.morrow.me.uk> <20150311091933.GM9442@pol-server.leissner.se> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 11 Mar 2015 10:54:14 -0400 (EDT) Cc: Peter Olsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 14:54:16 -0000 On Wednesday, March 11, 2015 10:19:33 AM Peter Olsson wrote: > On Tue, Mar 10, 2015 at 10:06:37PM +0000, Ben Morrow wrote: > > Quoth Peter Olsson : > > > > > > (But I will try running freebsd-update without merging /etc, > > > and use mergemaster -F instead. Should solve my problem.) > > > > I'm fairly sure this won't do what you want, and in fact won't work at > > all, unless your /etc is identical to the stock /etc installed from the > > ISO. (Which it isn't, of course.) > > > > installworld specifically avoids installing the files in /etc; then, > > when you run mergemaster, it installs the new versions of those files > > into a temporary directory and merges them with the existing /etc. > > > > freebsd-update works a little differently: because it doesn't have a > > source tree available, it has to fetch the stock versions of the files > > in /etc for the release you're upgrading from, so that it can patch them > > to the new release and then merge the changes into your current /etc. If > > you tell freebsd-update to install /etc without merging it will blindly > > update files you haven't changed (which is probably what you want) but > > (I think) will fail to update the files that you have changed, because > > it uses binary patches which won't apply to your modified versions. > > > > If you want a rather hackish solution, you could try something like > > this: > > > > - Rename /etc to /oldetc. > > - Find yourself a copy of the stock /etc for the version you are > > upgrading from. (tar -xpf base.txz --include /etc) > > - Run freebsd-update with /etc removed from the merge list. This > > will (should?) give you a stock /etc for the version you are > > upgrading to. > > - Rename /etc -> /tmp/etc, /oldetc -> /etc and run mergemaster with > > -t /tmp. > > > > Obviously I would script this if I was doing more than one or two > > machines > > > > Ben > > I'm not really clear on what will happen if I remove /etc/ from > MergeChanges in freebsd-update.conf. Will my /etc then be ignored > by freebsd-update, or will my /etc be completely overwritten by > freebsd-update? > > Anyway, your hack could be useful to me. There are no more than > about ten files I usually change in /etc, so saving the current > /etc, installing a stock /etc, running freebsd-update and then > running diff -r to sort out my changes could work. But I'm a > little worried about removing my /etc changes from a running server. BTW, this is kind of how etcupdate works (except that it does a full 3-way merge unlike mergemaster since it keeps the previous /etc around to compare with the new /etc and apply the diffs to the real /etc). It even has a mode to allow it to generate tarballs on the build machine that can then be used in place of having a source tree during upgrades so that freebsd-update could be changed to ship the updated bundle on each update. However, I haven't had time to look at what it would take to update freebsd-update to do this (and freebsd-update would have to include building the tarballs in its upstream build process as well). OTOH, if you ask freebsd-update to update your source tree after each update, you can use etcupdate to manage /etc instead of using freebsd-update. (Note that starting with 10.1 and 9.3 etcupdate is in base now and new releases ship with an initial etcupdate database that matches the release ISOs). The (completely untested) process might go something like this: Before your next freebsd-update run, ensure etcupdate is setup: 1) See if etcupdate already works by running 'etcupdate diff' and seeing if you get a sane diff. If you get a nice diff (without lots of noise like $FreeBSD$ changes), skip to step 3. 2) Ensure you have an up-to-date source tree with your current world. Run 'etcupdate extract'. 'etcupdate diff' should now give you a reasonable diff of your changes to /etc files. (Note that it does not show "new" files like /etc/fstab, just changes to files installed by a clean install.) 3) Review the output of 'etcupdate diff'. If there are local changes that are not correct, you can edit the files in /etc to reduce the diffs. If you want to restore a file to its original state, you can use 'cp /var/db/etcupdate/current/etc/ /etc/' (I will someday add an 'etcupdate revert' command for this) 4) Ensure that freebsd-update is set to update your source tree on each update and to not do any /etc merges After your next run of 'freebsd-update', run 'etcupdate' to merge in any changes to '/etc'. It can generally cope with simple merges similar to 'svn up'. If it encounters a conflict, it saves off a copy of the file with conflict markers for you to resolve via 'etcupdate resolve' but leaves the "old" file in /etc untouched until you resolve the conflict. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 14:54:16 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD0E65BE; Wed, 11 Mar 2015 14:54:16 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85566950; Wed, 11 Mar 2015 14:54:16 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5C690B91F; Wed, 11 Mar 2015 10:54:15 -0400 (EDT) From: John Baldwin To: Nick Frampton Subject: Re: Suspected libkvm infinite loop Date: Wed, 11 Mar 2015 10:38:12 -0400 Message-ID: <1648097.s1OBMXVVbH@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <54FFBDE9.5060702@akips.com> References: <54FE3803.2000307@akips.com> <20150310215913.GB52108@charmander.picturesperfect.net> <54FFBDE9.5060702@akips.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 11 Mar 2015 10:54:15 -0400 (EDT) Cc: Mark Johnston , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 14:54:16 -0000 On Wednesday, March 11, 2015 02:00:41 PM Nick Frampton wrote: > On 11/03/15 07:59, Mark Johnston wrote: > > On Tue, Mar 10, 2015 at 02:10:09PM -0400, John Baldwin wrote: > >> Often loops using libkvm are due to programs using libkvm are trying to read > >> kernel data structures while they are changing. However, if you use sysctls > >> to fetch this data instead, you should be able to get a stable snapshot of the > >> system state without getting stuck in a possible loop. I believe for libkvm > >> to use sysctl instead of /dev/kmem you have to pass a NULL for the kernel and > >> "/dev/null" for the core image. > > In our code, we're invoking kvm_openfiles as you suggest: > kd = kvm_openfiles (NULL, _PATH_DEVNULL, NULL, O_RDONLY, errbuf) > > > > It sounds like this issue might be the one fixed in r272566: if the > > KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an > > sbuf error return value could bubble up and be treated as ERESTART, > > resulting in a loop. > > > > This can be confirmed with something like > > > > dtrace -n 'syscall:::entry /pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p > > > > If the output consists solely of __sysctl, this bug is likely the > > culprit. > > Unfortunately, I accidentally killed fstat this morning before I could do any further debug. > > I ran truss -p on it yesterday and it was spinning solely on __sysctl. > > I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the > problem in a reasonable time frame so it could be days or weeks before we see it happen again. Tha truss output is consistent with Mark's suggestion, so I would try his suggested fix of 272566. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 22:09:45 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73053BFA for ; Wed, 11 Mar 2015 22:09:45 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C8EF403 for ; Wed, 11 Mar 2015 22:09:45 +0000 (UTC) Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id A1036411B7; Wed, 11 Mar 2015 22:09:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1426111775; bh=ugzH57LGzmhwSWw6+UFExIY2XyUpsS0NDd5+mMXME4M=; h=Date:From:To:Subject:References:In-Reply-To:From; b=QCic9LmuKB0EXoNFzbHygN//EYHoSb9WUSJn4LNtKvkMSy4jJp17OPBZZ7G/6bq9W VUzWE5CtUF3/nAoNx91KBLeo5tza3xo4pPvixCYIgt2jc9LkJuvQk0edOKpJpSLmtm 70wpDzBRAPRUM557CsIl2mSvmjtbdfbsXoOugOOk= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: pkubaj) with ESMTPSA id B8DB640E3D Message-ID: <5500BD1B.5070409@riseup.net> Date: Wed, 11 Mar 2015 23:09:31 +0100 From: Piotr Kubaj User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Chris H , petefrench@ingresso.co.uk, freebsd-stable@freebsd.org Subject: Re: No sound on 10.1-RELEASE References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> , <54FED24A.9040503@riseup.net> <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> In-Reply-To: <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.6 at mx1 X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 22:09:45 -0000 On 03/11/15 02:12, Chris H wrote: > On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj wrote > >> On 03/08/15 22:15, Chris H wrote: >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote >>> >>>> On 03/07/15 01:55, Chris H wrote: >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote >>>>> >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > ----8<---BIG-SNIP--- >>>>> >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: >>>> http://pastebin.com/pP0KXp4v >>> Out of the 4 MSI boards I that I have; 3 run the same >>> Realtek ALC893 HDA CODEC that yours does. The other, the >>> Realtek ALC1200 HDA CODEC. All four of them work. But I >>> notice 1 notable difference; that yours reports 2 >>> HDA interfaces: >>> hdac0: >>> and >>> hdac1: >>> I see hdac0 is disregarded (unused) whereas >>> hdac1 is enabled, and functioning. I think your problems >>> quite possibly lies in your (sound) system attempting to >>> use the first HDA device in the list, which is effectively >>> disabled. If you can determine a way to tell KDE, and friends >>> to use the 2nd HDA. Things may well go as intended. >>> None of the 4 MSI boards I have display 2 HDA's, as yours >>> does. >>> If you have any additional questions, you may well find >>> the FreeBSD forums already have answers to your issue. This >>> is where I originally found answers to my issues, when I >>> first started using these boards. >>> >>> HTH >>>> >>>> KDE is definitely using OSS as chosen in its settings (I also use its >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon >>>> backend because Gstreamer is said to cause problems, but that also works >>>> on 3 other computers. >>> >> I don't think it's KDE's fault, as it also happens when I kill KDE >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have >> vol and pcm maxed out. > If your speakers are amplified, you should hear them "pop", > when the kernel finds, and creates/attaches the driver(s) to > it. Same would be true, if you were wearing your headphones > when bouncing your box. > I'm quite sure that the sound system is defaulting the the first > HDA presented. Which, in your case, is the one that is disabled/ > non-operational. It's not KDE per se; but how the software > decides, by default, to hook sound up. If you had a sound > control panel available in KDE. You *should* be able to > *choose* which sound device to use. In your case, provided > it's even seen, it would be the *2nd* HDA. The sound control > panel should also present the *status* of the sound device > that it's using. Which, in your case, would indicate everything > as being "muted", and/or "unavailable". > On the box I'm writing this from, the HDA/CODEC is the > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > external amplifier that I use as sound for my entire house. > With the amplifier turned on, if I bounce the box (reboot) > I hear a "pop" when the kernel detects/attaches to the > sound chip. These are the relevant, and only "sound" related > devices, created/listed in /dev: > > cd0 > > dsp0.0 > dsp1.0 > dsp2.0 > dsp4.0 > > midistat > mixer0 > mixer1 > mixer2 > mixer4 > > sndstat > > If I'm not mistaken, you're probably running GENERIC, which > has *also* loaded snd_hda, and possibly/probably, others. > Which accounts for the additional HDA listing in dmesg(8). > What I would do, if I were you, is build/install a > custom kernel, stripped of any device not available > on your MB. This is the first thing I do, after a fresh > install, and, as you're discovering, for good reason. :) > You should also find, by doing so, that your system performs > much better, as a result. > The *only* sound related listings I have in my KERNCONF file, > is: > speaker # PC beeper > sound # geneic sound > snd_hda # Realtec CODEC HDA > Last, and only because I have to say it; > you *are* sure that you have your headphones/speakers > plugged into the *correct* jack, right? ;-) > Hey! It happens. :) > > --Chris > > -- > > I've deleted all other drivers except for snd_hda and sound but NVIDIA interfaces also use snd_hda driver. Also, I have already set up hw.snd.default_unit=4, which is the analog Intel interface (included in my 1st mail). I'm not sure how I should choose the default device in KDE, since it's chosen in hw.snd.default_unit. I'm not sure how you are able to hear a "pop" when sound devices are detected because it doesn't work that way on any of my other PC's (6 in total). From owner-freebsd-stable@FreeBSD.ORG Wed Mar 11 22:34:34 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0CF05550 for ; Wed, 11 Mar 2015 22:34:34 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D95A894D for ; Wed, 11 Mar 2015 22:34:33 +0000 (UTC) Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id C2E1F41834; Wed, 11 Mar 2015 22:34:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1426113272; bh=O62hqxp82w1eZr0m7pKVhWeF2F0tKSDFFJ3hjnpV6Z8=; h=Date:From:To:Subject:References:In-Reply-To:From; b=oDVVfnmqoY6UQ+CahkD2xqMnUu13zhZEwU2HvpMiyP2fYLjnSBnH6mIbKIrVay96e lvGoh4S1YHnXfP95+av84R9Ux9mFhTVMy7B8g+MBtkZk4mVTlmekLdAjEw0Ta6EWLL QGX1W3NoJQWGoprQVRYynqUtrT5Ujct0c17M4G8c= Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: pkubaj) with ESMTPSA id C7197400BE Message-ID: <5500C2F6.5040908@riseup.net> Date: Wed, 11 Mar 2015 23:34:30 +0100 From: Piotr Kubaj User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Chris H , petefrench@ingresso.co.uk, freebsd-stable@freebsd.org Subject: Re: No sound on 10.1-RELEASE References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> , <54FED24A.9040503@riseup.net> <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> In-Reply-To: <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.6 at mx1 X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Mar 2015 22:34:34 -0000 On 03/11/15 02:12, Chris H wrote: > On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj wrote > >> On 03/08/15 22:15, Chris H wrote: >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote >>> >>>> On 03/07/15 01:55, Chris H wrote: >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj wrote >>>>> >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > ----8<---BIG-SNIP--- >>>>> >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: >>>> http://pastebin.com/pP0KXp4v >>> Out of the 4 MSI boards I that I have; 3 run the same >>> Realtek ALC893 HDA CODEC that yours does. The other, the >>> Realtek ALC1200 HDA CODEC. All four of them work. But I >>> notice 1 notable difference; that yours reports 2 >>> HDA interfaces: >>> hdac0: >>> and >>> hdac1: >>> I see hdac0 is disregarded (unused) whereas >>> hdac1 is enabled, and functioning. I think your problems >>> quite possibly lies in your (sound) system attempting to >>> use the first HDA device in the list, which is effectively >>> disabled. If you can determine a way to tell KDE, and friends >>> to use the 2nd HDA. Things may well go as intended. >>> None of the 4 MSI boards I have display 2 HDA's, as yours >>> does. >>> If you have any additional questions, you may well find >>> the FreeBSD forums already have answers to your issue. This >>> is where I originally found answers to my issues, when I >>> first started using these boards. >>> >>> HTH >>>> >>>> KDE is definitely using OSS as chosen in its settings (I also use its >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon >>>> backend because Gstreamer is said to cause problems, but that also works >>>> on 3 other computers. >>> >> I don't think it's KDE's fault, as it also happens when I kill KDE >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have >> vol and pcm maxed out. > If your speakers are amplified, you should hear them "pop", > when the kernel finds, and creates/attaches the driver(s) to > it. Same would be true, if you were wearing your headphones > when bouncing your box. > I'm quite sure that the sound system is defaulting the the first > HDA presented. Which, in your case, is the one that is disabled/ > non-operational. It's not KDE per se; but how the software > decides, by default, to hook sound up. If you had a sound > control panel available in KDE. You *should* be able to > *choose* which sound device to use. In your case, provided > it's even seen, it would be the *2nd* HDA. The sound control > panel should also present the *status* of the sound device > that it's using. Which, in your case, would indicate everything > as being "muted", and/or "unavailable". > On the box I'm writing this from, the HDA/CODEC is the > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > external amplifier that I use as sound for my entire house. > With the amplifier turned on, if I bounce the box (reboot) > I hear a "pop" when the kernel detects/attaches to the > sound chip. These are the relevant, and only "sound" related > devices, created/listed in /dev: > > cd0 > > dsp0.0 > dsp1.0 > dsp2.0 > dsp4.0 > > midistat > mixer0 > mixer1 > mixer2 > mixer4 > > sndstat > > If I'm not mistaken, you're probably running GENERIC, which > has *also* loaded snd_hda, and possibly/probably, others. > Which accounts for the additional HDA listing in dmesg(8). > What I would do, if I were you, is build/install a > custom kernel, stripped of any device not available > on your MB. This is the first thing I do, after a fresh > install, and, as you're discovering, for good reason. :) > You should also find, by doing so, that your system performs > much better, as a result. > The *only* sound related listings I have in my KERNCONF file, > is: > speaker # PC beeper > sound # geneic sound > snd_hda # Realtec CODEC HDA > Last, and only because I have to say it; > you *are* sure that you have your headphones/speakers > plugged into the *correct* jack, right? ;-) > Hey! It happens. :) > > --Chris > > -- > > A small update: I can set hw.snd.default_unit=5 and sound works through the front panel, but not so through the back panel. I have tried any other value from 0 to 7 and the sound works with the back panel on Windows so it's connected properly. From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 03:23:41 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D0E4E16 for ; Thu, 12 Mar 2015 03:23:41 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C4611AE5 for ; Thu, 12 Mar 2015 03:23:40 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2C3PIQ8056299; Wed, 11 Mar 2015 20:25:18 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: petefrench@ingresso.co.uk, freebsd-stable@freebsd.org, Piotr Kubaj In-Reply-To: <5500BD1B.5070409@riseup.net> References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> , <54FED24A.9040503@riseup.net> <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net>, <5500BD1B.5070409@riseup.net> From: "Chris H" Subject: Re: No sound on 10.1-RELEASE Date: Wed, 11 Mar 2015 20:25:19 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <1356067ef4623250bcec438c3956af46@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 03:23:41 -0000 On Wed, 11 Mar 2015 23:09:31 +0100 Piotr Kubaj wrote > On 03/11/15 02:12, Chris H wrote: > > On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj wrote > > > >> On 03/08/15 22:15, Chris H wrote: > >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote > >>> > >>>> On 03/07/15 01:55, Chris H wrote: > >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj > >>>>> wrote >>>>> > >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > > ----8<---BIG-SNIP--- > >>>>> > >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: > >>>> http://pastebin.com/pP0KXp4v > >>> Out of the 4 MSI boards I that I have; 3 run the same > >>> Realtek ALC893 HDA CODEC that yours does. The other, the > >>> Realtek ALC1200 HDA CODEC. All four of them work. But I > >>> notice 1 notable difference; that yours reports 2 > >>> HDA interfaces: > >>> hdac0: > >>> and > >>> hdac1: > >>> I see hdac0 is disregarded (unused) whereas > >>> hdac1 is enabled, and functioning. I think your problems > >>> quite possibly lies in your (sound) system attempting to > >>> use the first HDA device in the list, which is effectively > >>> disabled. If you can determine a way to tell KDE, and friends > >>> to use the 2nd HDA. Things may well go as intended. > >>> None of the 4 MSI boards I have display 2 HDA's, as yours > >>> does. > >>> If you have any additional questions, you may well find > >>> the FreeBSD forums already have answers to your issue. This > >>> is where I originally found answers to my issues, when I > >>> first started using these boards. > >>> > >>> HTH > >>>> > >>>> KDE is definitely using OSS as chosen in its settings (I also use its > >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon > >>>> backend because Gstreamer is said to cause problems, but that also works > >>>> on 3 other computers. > >>> > >> I don't think it's KDE's fault, as it also happens when I kill KDE > >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have > >> vol and pcm maxed out. > > If your speakers are amplified, you should hear them "pop", > > when the kernel finds, and creates/attaches the driver(s) to > > it. Same would be true, if you were wearing your headphones > > when bouncing your box. > > I'm quite sure that the sound system is defaulting the the first > > HDA presented. Which, in your case, is the one that is disabled/ > > non-operational. It's not KDE per se; but how the software > > decides, by default, to hook sound up. If you had a sound > > control panel available in KDE. You *should* be able to > > *choose* which sound device to use. In your case, provided > > it's even seen, it would be the *2nd* HDA. The sound control > > panel should also present the *status* of the sound device > > that it's using. Which, in your case, would indicate everything > > as being "muted", and/or "unavailable". > > On the box I'm writing this from, the HDA/CODEC is the > > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > > external amplifier that I use as sound for my entire house. > > With the amplifier turned on, if I bounce the box (reboot) > > I hear a "pop" when the kernel detects/attaches to the > > sound chip. These are the relevant, and only "sound" related > > devices, created/listed in /dev: > > > > cd0 > > > > dsp0.0 > > dsp1.0 > > dsp2.0 > > dsp4.0 > > > > midistat > > mixer0 > > mixer1 > > mixer2 > > mixer4 > > > > sndstat > > > > If I'm not mistaken, you're probably running GENERIC, which > > has *also* loaded snd_hda, and possibly/probably, others. > > Which accounts for the additional HDA listing in dmesg(8). > > What I would do, if I were you, is build/install a > > custom kernel, stripped of any device not available > > on your MB. This is the first thing I do, after a fresh > > install, and, as you're discovering, for good reason. :) > > You should also find, by doing so, that your system performs > > much better, as a result. > > The *only* sound related listings I have in my KERNCONF file, > > is: > > speaker # PC beeper > > sound # geneic sound > > snd_hda # Realtec CODEC HDA > > Last, and only because I have to say it; > > you *are* sure that you have your headphones/speakers > > plugged into the *correct* jack, right? ;-) > > Hey! It happens. :) > > > > --Chris > > > > -- > > > > > I've deleted all other drivers except for snd_hda and sound but NVIDIA > interfaces also use snd_hda driver. Also, I have already set up > hw.snd.default_unit=4, which is the analog Intel interface (included in > my 1st mail). I'm not sure how I should choose the default device in > KDE, since it's chosen in hw.snd.default_unit. I'm not sure how you are > able to hear a "pop" when sound devices are detected because it doesn't > work that way on any of my other PC's (6 in total). Well, I'm only able to share my own experiences. The 3 with Realtek chips, all make a light pop sound during boot. The one I happen to be writing this from emits the following in dmesg(8) hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 hdaa0: Subsystem ID: 0x103c2a72 pcm0: at nid 20,27 and 24,25,22 on hdaa0 pcm0: Playback: pcm0: Stream cap: 0x00000001 PCM pcm0: PCM cap: 0x000e0560 16 20 24 bits, 44 48 96 192 KHz pcm0: DAC: 2 pcm0: Soft PCM mixer ENABLED pcm0: Playback channel set is: Front Left, Front Right, pcm0: Playback channel matrix is: 2.0 (disconnected) pcm0: Recording channel set is: Front Left, Front Right, pcm0: Recording channel matrix is: 2.0 (disconnected) pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "mix": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "monitor": pcm0: Soft PCM mixer ENABLED pcm0: Playback channel set is: Front Left, Front Right, pcm0: Playback channel matrix is: 2.0 pcm1: at nid 21 on hdaa0 pcm1: Playback: pcm1: Stream cap: 0x00000001 PCM pcm1: PCM cap: 0x000e0560 16 20 24 bits, 44 48 96 192 KHz pcm1: DAC: 3 pcm1: Mixer "vol": pcm1: Mixer "pcm": pcm1: Mixer "igain": pcm1: Soft PCM mixer ENABLED pcm1: Playback channel set is: Front Left, Front Right, pcm1: Playback channel matrix is: 2.0 sysctl(8) reports: hw.snd.default_unit: 0 I have sound. That's as much as I can offer. All the best. --Chris -- From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 03:43:29 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9568D126 for ; Thu, 12 Mar 2015 03:43:29 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 405E1CFE for ; Thu, 12 Mar 2015 03:43:29 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2C3j8ZV057586; Wed, 11 Mar 2015 20:45:08 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@freebsd.org, Piotr Kubaj In-Reply-To: <5500C2F6.5040908@riseup.net> References: <54FA3376.4020001@riseup.net> <821bd8e3acb111667353737ec5c8eb5c@ultimatedns.net>, <54FC9197.9040406@riseup.net> , <54FED24A.9040503@riseup.net> <6bdeedc21fe40455bd8b82a60256436f@ultimatedns.net>, <5500C2F6.5040908@riseup.net> From: "Chris H" Subject: Re: No sound on 10.1-RELEASE Date: Wed, 11 Mar 2015 20:45:09 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <17a2dc2d7eb20892a300050c37c3f783@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 03:43:29 -0000 On Wed, 11 Mar 2015 23:34:30 +0100 Piotr Kubaj wrote > On 03/11/15 02:12, Chris H wrote: > > On Tue, 10 Mar 2015 12:15:22 +0100 Piotr Kubaj wrote > > > >> On 03/08/15 22:15, Chris H wrote: > >>> On Sun, 08 Mar 2015 19:14:47 +0100 Piotr Kubaj wrote > >>> > >>>> On 03/07/15 01:55, Chris H wrote: > >>>>> On Sat, 07 Mar 2015 00:08:38 +0100 Piotr Kubaj > >>>>> wrote >>>>> > >>>>>> I've got MSI X99 motherboard and am using it with UEFI installation of > > ----8<---BIG-SNIP--- > >>>>> > >>>> I'm not sure what may be wrong in dmesg.boot so I've uploaded it here: > >>>> http://pastebin.com/pP0KXp4v > >>> Out of the 4 MSI boards I that I have; 3 run the same > >>> Realtek ALC893 HDA CODEC that yours does. The other, the > >>> Realtek ALC1200 HDA CODEC. All four of them work. But I > >>> notice 1 notable difference; that yours reports 2 > >>> HDA interfaces: > >>> hdac0: > >>> and > >>> hdac1: > >>> I see hdac0 is disregarded (unused) whereas > >>> hdac1 is enabled, and functioning. I think your problems > >>> quite possibly lies in your (sound) system attempting to > >>> use the first HDA device in the list, which is effectively > >>> disabled. If you can determine a way to tell KDE, and friends > >>> to use the 2nd HDA. Things may well go as intended. > >>> None of the 4 MSI boards I have display 2 HDA's, as yours > >>> does. > >>> If you have any additional questions, you may well find > >>> the FreeBSD forums already have answers to your issue. This > >>> is where I originally found answers to my issues, when I > >>> first started using these boards. > >>> > >>> HTH > >>>> > >>>> KDE is definitely using OSS as chosen in its settings (I also use its > >>>> own mixer which can do the same as Xfce's). I also use VLC's Phonon > >>>> backend because Gstreamer is said to cause problems, but that also works > >>>> on 3 other computers. > >>> > >> I don't think it's KDE's fault, as it also happens when I kill KDE > >> (service kdm4 stop) and do cat /dev/random > /dev/dsp. Of course, I have > >> vol and pcm maxed out. > > If your speakers are amplified, you should hear them "pop", > > when the kernel finds, and creates/attaches the driver(s) to > > it. Same would be true, if you were wearing your headphones > > when bouncing your box. > > I'm quite sure that the sound system is defaulting the the first > > HDA presented. Which, in your case, is the one that is disabled/ > > non-operational. It's not KDE per se; but how the software > > decides, by default, to hook sound up. If you had a sound > > control panel available in KDE. You *should* be able to > > *choose* which sound device to use. In your case, provided > > it's even seen, it would be the *2nd* HDA. The sound control > > panel should also present the *status* of the sound device > > that it's using. Which, in your case, would indicate everything > > as being "muted", and/or "unavailable". > > On the box I'm writing this from, the HDA/CODEC is the > > Realtek ALC893, as yours is. I have it hooked up to a 700 watt > > external amplifier that I use as sound for my entire house. > > With the amplifier turned on, if I bounce the box (reboot) > > I hear a "pop" when the kernel detects/attaches to the > > sound chip. These are the relevant, and only "sound" related > > devices, created/listed in /dev: > > > > cd0 > > > > dsp0.0 > > dsp1.0 > > dsp2.0 > > dsp4.0 > > > > midistat > > mixer0 > > mixer1 > > mixer2 > > mixer4 > > > > sndstat > > > > If I'm not mistaken, you're probably running GENERIC, which > > has *also* loaded snd_hda, and possibly/probably, others. > > Which accounts for the additional HDA listing in dmesg(8). > > What I would do, if I were you, is build/install a > > custom kernel, stripped of any device not available > > on your MB. This is the first thing I do, after a fresh > > install, and, as you're discovering, for good reason. :) > > You should also find, by doing so, that your system performs > > much better, as a result. > > The *only* sound related listings I have in my KERNCONF file, > > is: > > speaker # PC beeper > > sound # geneic sound > > snd_hda # Realtec CODEC HDA > > Last, and only because I have to say it; > > you *are* sure that you have your headphones/speakers > > plugged into the *correct* jack, right? ;-) > > Hey! It happens. :) > > > > --Chris > > > > -- > > > > > A small update: I can set hw.snd.default_unit=5 and sound works through > the front panel, but not so through the back panel. I have tried any > other value from 0 to 7 and the sound works with the back panel on > Windows so it's connected properly. Good(ish) news. I just recalled something that might prove somewhat helpful in diagnosing your issue. I don't know about yours; but if I unplug the speakers, or headphones, I get a lot of noise on the console, regarding the event. It indicated what was disconnected in such a way, that you might well be able to compare the output with that of dmesg, to find out what == what. All the best. --Chris -- From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 04:05:42 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41D63740; Thu, 12 Mar 2015 04:05:42 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id 2AEC2ED8; Thu, 12 Mar 2015 04:05:41 +0000 (UTC) Received: from [10.1.8.7] (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id B83F42824E; Thu, 12 Mar 2015 14:05:34 +1000 (EST) Message-ID: <5501108C.4080303@akips.com> Date: Thu, 12 Mar 2015 14:05:32 +1000 From: Nick Frampton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: John Baldwin Subject: Re: Suspected libkvm infinite loop References: <54FE3803.2000307@akips.com> <20150310215913.GB52108@charmander.picturesperfect.net> <54FFBDE9.5060702@akips.com> <1648097.s1OBMXVVbH@ralph.baldwin.cx> In-Reply-To: <1648097.s1OBMXVVbH@ralph.baldwin.cx> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com Cc: Mark Johnston , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:05:42 -0000 On 12/03/15 00:38, John Baldwin wrote: >>> It sounds like this issue might be the one fixed in r272566: if the >>> > >KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an >>> > >sbuf error return value could bubble up and be treated as ERESTART, >>> > >resulting in a loop. >>> > > >>> > >This can be confirmed with something like >>> > > >>> > > dtrace -n 'syscall:::entry/pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p >>> > > >>> > >If the output consists solely of __sysctl, this bug is likely the >>> > >culprit. >> > >> >Unfortunately, I accidentally killed fstat this morning before I could do any further debug. >> > >> >I ran truss -p on it yesterday and it was spinning solely on __sysctl. >> > >> >I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the >> >problem in a reasonable time frame so it could be days or weeks before we see it happen again. > Tha truss output is consistent with Mark's suggestion, so I would try > his suggested fix of 272566. I patched the 10.1 kernel with r272566 and it appears to have fixed the issue. Is this patch likely to be MFCed back to 10-stable? Our RC script forks off about 200 processes when starting our software, and I wrote a small script to repeatedly stop/start the software, which fairly reliably reproduces the issue about 1 in 10 times. I've been running the script with the patched kernel for an hour now and I haven't seen the issue appear. Thanks for your help. -Nick -- Founder, CTO www.akips.com From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 04:34:14 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55F396A4; Thu, 12 Mar 2015 04:34:14 +0000 (UTC) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EADD2B5; Thu, 12 Mar 2015 04:34:14 +0000 (UTC) Received: by padet14 with SMTP id et14so17254065pad.0; Wed, 11 Mar 2015 21:34:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=f09oNAHrFPpw+L7sFwcFrr0OTbsI6YpbjEb5yiGAG4E=; b=scD2w9SA5Edm3dGO/71kgDJAr7im0MqfFngZ+vYdVcPZM8dBC8KI461aBvcVVYFhpU 6uCt0xB37i5xrbRyUC1R6+PvPWgFBRGRTs96Gzdk0K1NhRJBdAT4qb6Z3124dDUxOaKt bDK+BDumSO1vWsneMJnL+5aCjbegUeoM6u6/azpeDpGkceEM/gGaEwRYdSemnNnhzAt9 KKy33tNKttjXe5oPajxGnbl684MNk1KX1D4sulYS34NPI15hQwXblGXJqXNKX9puPH4i saO3HCTF8wapCmObcs376/JfBTJKsuVRxPljQyVnSy9DjrSf9zhaf+UiTsrU1RonEN24 JATw== X-Received: by 10.66.65.195 with SMTP id z3mr85930782pas.10.1426134853774; Wed, 11 Mar 2015 21:34:13 -0700 (PDT) Received: from raichu (216-243-33-91.users.condointernet.net. [216.243.33.91]) by mx.google.com with ESMTPSA id k5sm8348328pdf.95.2015.03.11.21.34.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Mar 2015 21:34:12 -0700 (PDT) Sender: Mark Johnston Date: Wed, 11 Mar 2015 21:34:07 -0700 From: Mark Johnston To: Nick Frampton Subject: Re: Suspected libkvm infinite loop Message-ID: <20150312043407.GA11120@raichu> References: <54FE3803.2000307@akips.com> <20150310215913.GB52108@charmander.picturesperfect.net> <54FFBDE9.5060702@akips.com> <1648097.s1OBMXVVbH@ralph.baldwin.cx> <5501108C.4080303@akips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5501108C.4080303@akips.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: kib@FreeBSD.org, freebsd-stable@freebsd.org, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 04:34:14 -0000 On Thu, Mar 12, 2015 at 02:05:32PM +1000, Nick Frampton wrote: > On 12/03/15 00:38, John Baldwin wrote: > >>> It sounds like this issue might be the one fixed in r272566: if the > >>> > >KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an > >>> > >sbuf error return value could bubble up and be treated as ERESTART, > >>> > >resulting in a loop. > >>> > > > >>> > >This can be confirmed with something like > >>> > > > >>> > > dtrace -n 'syscall:::entry/pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p > >>> > > > >>> > >If the output consists solely of __sysctl, this bug is likely the > >>> > >culprit. > >> > > >> >Unfortunately, I accidentally killed fstat this morning before I could do any further debug. > >> > > >> >I ran truss -p on it yesterday and it was spinning solely on __sysctl. > >> > > >> >I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the > >> >problem in a reasonable time frame so it could be days or weeks before we see it happen again. > > Tha truss output is consistent with Mark's suggestion, so I would try > > his suggested fix of 272566. > > I patched the 10.1 kernel with r272566 and it appears to have fixed the issue. Is this patch likely > to be MFCed back to 10-stable? I can't see any reason it shouldn't be, and there was an MFC reminder in the commit log entry for that revision. I've cc'ed kib@, who might have a reason. > > Our RC script forks off about 200 processes when starting our software, and I wrote a small script > to repeatedly stop/start the software, which fairly reliably reproduces the issue about 1 in 10 > times. I've been running the script with the patched kernel for an hour now and I haven't seen the > issue appear. From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 05:18:21 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E540C68; Thu, 12 Mar 2015 05:18:20 +0000 (UTC) Date: Thu, 12 Mar 2015 05:18:17 +0000 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: HEADS-UP: system deadlock issues when rebooting after updating or upgrading to 10.1-RELEASE Message-ID: <20150312051817.GI51985@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="+ZmrHH5cGjskQnY1" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 05:18:21 -0000 --+ZmrHH5cGjskQnY1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It has become apparent that issues reported in PR 195458 [1] do not apply to freebsd-update(8) users alone, and that the deadlock on reboot (either via reboot(8) or shutdown(8) with the '-r' flag) can be reliably reproduced under certain conditions. Specifically, the issue can be reliably reproduced on systems using UFS as the root filesystem with soft-updates and journaling enabled (a.k.a., SU+J). Systems using ZFS or UFS without SU+J appear to be unaffected at this point (noted by various people in the referenced PR, as well as my own tests). Based on the comments in the referenced PR, it is unclear if this deadlock can occur under other conditions, but it seems to be contained to UFS with SU+J. If you have experienced a deadlock after upgrading a 10.1-RELEASE system, please update the referenced PR with pertinent information (filesystem, and filesystem options, etc.). While the underlying cause, and more importantly, a resolution is being investigated, it is critical we have as much information as possible. Once the underlying issue is identified, and we have a tested fix for the problem, an EN will be issued as soon as reasonably possible. To be clear, this issue manifests as an unresponsive system after issuing a reboot(8) (or in some cases, a shutdown(8)) command, after the "All buffers synced." message is displayed, and this heads-up is addressing only those cases (or potential cases). All other filesystem related should be reported in a separate PR, as usual. Having said all of the above, I as the RE for 10.1-RELEASE, personally apologize to everyone that has run into this issue. I am still baffled why I did not run into this problem when testing 10.1-RELEASE (or any of the -BETA or -RC builds). I can only attribute this to a change in my testing environment (i.e., updated hypervisor software), but given the details and reproducibility after recent testing, am unable to explain how this was not discovered earlier. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458 Glen On behalf of: re@ --+ZmrHH5cGjskQnY1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVASGZAAoJEAMUWKVHj+KTteIP/3aRZNH0saDzHQLAncqN2UXa 5u3Y8XgP4rpdUKYUz55sawUJmHSVPslo5FhyyE8tdybbOmA2VcFT9wz9kTioL985 x9uVALergFv56q8T22ZWNpxaPLQaH5nEiI5T1tPCc5jtYoLY6OwfgsxzlhZmsuO7 InWAIfK/0TGSgkwZS2V2XsCUcgxDmN/IWQY3jwWYY+qQwuiNHLQ7zmylL7o8bnvj xWBamZylWSrYksZy+fx3FK6NHbOvoj4cfGtvGbYPJmd5sEVZ5AU6LgVZOvkAclJL vOCFdEFMrFLgesgxNYGFedysXEqCwVkuK43WXgwXAnxhH33o2xv8NhVdd10Nwrln rZZsM1w0npfLyFUaVjhtLwhp7jDujCSKaMI/fJccIg+DaT88rU43nZot+nF4YSx2 PsccjpfobAjRwib/evKV2tNzirO2MskxZHAnSfZjO4GiHr0Uv+Eq4o3xWNWW11hx xU0ssZWgsscRYhVIyLmS1ODJjyhu0Vbi6ve7j88UXdn9t1rNPpw4kyJiTffYkIJD j0GJxUtOBw7uEoWHN72EvFNHpQAGnVbgIovCEJj7bX2cj4jNRpc4Zl9BWv7ps6xn 2138dd3ChOhNF5ZtFkglGCq9JB+Qxu7EUTHXF/9EIpV74E5PqpAT3SZVumcvRgsm 2ks4U1CRmR+XYiqHK8Lu =Klgm -----END PGP SIGNATURE----- --+ZmrHH5cGjskQnY1-- From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 10:40:33 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 93BC91C8; Thu, 12 Mar 2015 10:40:33 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B89921E; Thu, 12 Mar 2015 10:40:32 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t2CAeNOX030323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Mar 2015 12:40:24 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t2CAeNOX030323 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t2CAeNCT030320; Thu, 12 Mar 2015 12:40:23 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 12 Mar 2015 12:40:23 +0200 From: Konstantin Belousov To: Mark Johnston Subject: Re: Suspected libkvm infinite loop Message-ID: <20150312104023.GL2379@kib.kiev.ua> References: <54FE3803.2000307@akips.com> <20150310215913.GB52108@charmander.picturesperfect.net> <54FFBDE9.5060702@akips.com> <1648097.s1OBMXVVbH@ralph.baldwin.cx> <5501108C.4080303@akips.com> <20150312043407.GA11120@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150312043407.GA11120@raichu> User-Agent: Mutt/1.5.23 (2014-03-12) 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.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: freebsd-stable@freebsd.org, Nick Frampton , John Baldwin , kib@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 10:40:33 -0000 On Wed, Mar 11, 2015 at 09:34:07PM -0700, Mark Johnston wrote: > On Thu, Mar 12, 2015 at 02:05:32PM +1000, Nick Frampton wrote: > > On 12/03/15 00:38, John Baldwin wrote: > > >>> It sounds like this issue might be the one fixed in r272566: if the > > >>> > >KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an > > >>> > >sbuf error return value could bubble up and be treated as ERESTART, > > >>> > >resulting in a loop. > > >>> > > > > >>> > >This can be confirmed with something like > > >>> > > > > >>> > > dtrace -n 'syscall:::entry/pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p > > >>> > > > > >>> > >If the output consists solely of __sysctl, this bug is likely the > > >>> > >culprit. > > >> > > > >> >Unfortunately, I accidentally killed fstat this morning before I could do any further debug. > > >> > > > >> >I ran truss -p on it yesterday and it was spinning solely on __sysctl. > > >> > > > >> >I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the > > >> >problem in a reasonable time frame so it could be days or weeks before we see it happen again. > > > Tha truss output is consistent with Mark's suggestion, so I would try > > > his suggested fix of 272566. > > > > I patched the 10.1 kernel with r272566 and it appears to have fixed the issue. Is this patch likely > > to be MFCed back to 10-stable? > > I can't see any reason it shouldn't be, and there was an MFC reminder in > the commit log entry for that revision. I've cc'ed kib@, who might have a > reason. The mentioned commit depends on r271976, in fact it depends on the series of commits, including r271486 and r271489. I did not merged r271976 with manual resolution of the conficts, since it means that the work done for HEAD needs to be redone for stable/10 to ensure that all cases are covered. Later, when the mentioned series is merged, the work should be redone once more. And to note, r271489 is not trivially mergeable as well, just checked. From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 15:09:37 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9B9F366; Thu, 12 Mar 2015 15:09:37 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F8B879A; Thu, 12 Mar 2015 15:09:37 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 90637B963; Thu, 12 Mar 2015 11:09:36 -0400 (EDT) From: John Baldwin To: Konstantin Belousov Subject: Re: Suspected libkvm infinite loop Date: Thu, 12 Mar 2015 10:39:10 -0400 Message-ID: <2374792.i316gF0qRo@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <20150312104023.GL2379@kib.kiev.ua> References: <54FE3803.2000307@akips.com> <20150312043407.GA11120@raichu> <20150312104023.GL2379@kib.kiev.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 12 Mar 2015 11:09:36 -0400 (EDT) Cc: freebsd-stable@freebsd.org, Mark Johnston , Nick Frampton , kib@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 15:09:37 -0000 On Thursday, March 12, 2015 12:40:23 PM Konstantin Belousov wrote: > On Wed, Mar 11, 2015 at 09:34:07PM -0700, Mark Johnston wrote: > > On Thu, Mar 12, 2015 at 02:05:32PM +1000, Nick Frampton wrote: > > > On 12/03/15 00:38, John Baldwin wrote: > > > >>> It sounds like this issue might be the one fixed in r272566: if the > > > >>> > >KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an > > > >>> > >sbuf error return value could bubble up and be treated as ERESTART, > > > >>> > >resulting in a loop. > > > >>> > > > > > >>> > >This can be confirmed with something like > > > >>> > > > > > >>> > > dtrace -n 'syscall:::entry/pid == $target/{@[probefunc] = count();} tick-3s {exit(0);}' -p > > > >>> > > > > > >>> > >If the output consists solely of __sysctl, this bug is likely the > > > >>> > >culprit. > > > >> > > > > >> >Unfortunately, I accidentally killed fstat this morning before I could do any further debug. > > > >> > > > > >> >I ran truss -p on it yesterday and it was spinning solely on __sysctl. > > > >> > > > > >> >I'll try compiling with debug symbols in case it happens again. I haven't been able to reproduce the > > > >> >problem in a reasonable time frame so it could be days or weeks before we see it happen again. > > > > Tha truss output is consistent with Mark's suggestion, so I would try > > > > his suggested fix of 272566. > > > > > > I patched the 10.1 kernel with r272566 and it appears to have fixed the issue. Is this patch likely > > > to be MFCed back to 10-stable? > > > > I can't see any reason it shouldn't be, and there was an MFC reminder in > > the commit log entry for that revision. I've cc'ed kib@, who might have a > > reason. > > The mentioned commit depends on r271976, in fact it depends on the series of > commits, including r271486 and r271489. > > I did not merged r271976 with manual resolution of the conficts, since it > means that the work done for HEAD needs to be redone for stable/10 to > ensure that all cases are covered. Later, when the mentioned series is > merged, the work should be redone once more. > > And to note, r271489 is not trivially mergeable as well, just checked. You could merge r272566 and just fixup the sbuf_bcat() in export_fd_to_sb() in kern_descrip.c instead. I hadn't really considered fo_fill_kinfo to be something that was mergeable to 10. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 19:07:57 2015 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8573807 for ; Thu, 12 Mar 2015 19:07:57 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF412A91 for ; Thu, 12 Mar 2015 19:07:57 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CJ7v8I013542 for ; Thu, 12 Mar 2015 19:07:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 198549] FreeBSD -STABLE r279935 world fail to build. Date: Thu, 12 Mar 2015 19:07:57 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sasamotikomi@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 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, 12 Mar 2015 19:07:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 sasamotikomi@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sasamotikomi@gmail.com, | |stable@FreeBSD.org -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 19:36:32 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1597D201 for ; Thu, 12 Mar 2015 19:36:32 +0000 (UTC) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFB17E2E for ; Thu, 12 Mar 2015 19:36:31 +0000 (UTC) Received: by ieclw3 with SMTP id lw3so57025203iec.2 for ; Thu, 12 Mar 2015 12:36:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=2Ei9FxHKwBAm+m592LgP0xRxMnq8ZNCUNvrCdwU0nz0=; b=Foe2JzrYcDZleHOqqkt0P1jToI+L48Lfum4qpqj0Zp0fXmkyalR6sTr8C9FZ2wNwPV 8lIMymlNtAI/zb5q3nQqN5P9IJxaLXTSxvW/JQKJwEPUtrhLvQGFkBsPYVChaSOdTfNX U8QInl7o5Z3QmjpCa1I0cca0M5gQprWeg9228OXGR74qsjpokiCGv6QJ8cgLJFzcnWqv Zjnt35NUUIuwnU/WAvKho9mWrg96v6MPvT77LAyE4y4L9TBFbWgd3bn8os/PPDpcbfQs vIlby6Iznm/2yNRu0qHafj43IFKlKniCfR64bgc4UmSJJJSBXvFpgHq7CtV6gc7hrrxY 3ZUQ== MIME-Version: 1.0 X-Received: by 10.42.119.202 with SMTP id c10mr45007080icr.4.1426188976557; Thu, 12 Mar 2015 12:36:16 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Thu, 12 Mar 2015 12:36:16 -0700 (PDT) Date: Thu, 12 Mar 2015 12:36:16 -0700 X-Google-Sender-Auth: DAC89agkkJaLwVnU1uBGNR8Kn_s Message-ID: Subject: On-going laptop brightness issues From: Kevin Oberman To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 19:36:32 -0000 I have just submitted a PR to MFC the code that will fix brightness adjustmant on may laptops with modern Intel GPUs. It has been tested by at least two people and I have been using it for at least three months with no negative issues. Th author has posted that he lacks the time to MFC but that "someone else" will have to do it. Could some committer please take a look at this one? The patch touches three files, two just to add entry points for the code. The functional code is all to /sys/dev/drm2/i915/intel_opregion.c. Other than some offsets, it applies cleanly to stable. At very least, it will fix an annoyance for some people and eliminate some messages to several mail lists (stable, questions, x1l, mobile and acpi). The patch can be found it 198551, just submitted. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 19:40:48 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC20F41B for ; Thu, 12 Mar 2015 19:40:48 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 819B1E66 for ; Thu, 12 Mar 2015 19:40:48 +0000 (UTC) Received: by igjz20 with SMTP id z20so268464igj.4 for ; Thu, 12 Mar 2015 12:40:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ArJHQCjJ6/v13GmS0OMB2ul9PX8eefL6z/4p5aY4r4o=; b=YajftEwZLp+6vVuZRuVJJG38WBCSIDLQcp1MB7Ta1A+bUJtosZH+368acqLLpzo6nc x18CwDVcL/Vi8rISnUgqT2Ue+CGvv9pjnoa+ZcQ6XLCx0WWZT9KuEXDbbwuvScS5oTnD /YbiftOWIzThJoxlgRkLSH1b/Lz+NYGbOyRjhXyGWdnJLMwEULwAvuGH3+qEsJ4z3a86 BkEg/sL1AwyevwiCUpqZrI3qak7dvMitol58tZsQHTnMSAhkLf1cyPE9AdkxLJDBiUcT X/Mzr+A08fcQ7yT3JYOHu+xVRVpY+EIIDFBug5OgIUPcc3j/+z1JX8ICluiNvI85NbHV /p/Q== MIME-Version: 1.0 X-Received: by 10.107.5.211 with SMTP id 202mr43259021iof.88.1426189247892; Thu, 12 Mar 2015 12:40:47 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Thu, 12 Mar 2015 12:40:47 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Mar 2015 12:40:47 -0700 X-Google-Sender-Auth: -m5RM6E-HMyBCehCbxwJ_2kkIwg Message-ID: Subject: Re: On-going laptop brightness issues From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 19:40:48 -0000 I thought jhb already mfc'ed it? -a On 12 March 2015 at 12:36, Kevin Oberman wrote: > I have just submitted a PR to MFC the code that will fix brightness > adjustmant on may laptops with modern Intel GPUs. It has been tested by at > least two people and I have been using it for at least three months with no > negative issues. > > Th author has posted that he lacks the time to MFC but that "someone else" > will have to do it. > > Could some committer please take a look at this one? The patch touches > three files, two just to add entry points for the code. The functional code > is all to /sys/dev/drm2/i915/intel_opregion.c. Other than some offsets, it > applies cleanly to stable. At very least, it will fix an annoyance for some > people and eliminate some messages to several mail lists (stable, > questions, x1l, mobile and acpi). > > The patch can be found it 198551, just submitted. > -- > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Mar 12 20:20:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 973D1178 for ; Thu, 12 Mar 2015 20:20:08 +0000 (UTC) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 289713B1 for ; Thu, 12 Mar 2015 20:20:08 +0000 (UTC) Received: by wggx12 with SMTP id x12so18836178wgg.13 for ; Thu, 12 Mar 2015 13:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KjdVNKpBOQK7nuf8hfmNnav1xfBPNZisALslv2xi2ko=; b=ZpsqPepMnAF0zRFUpnz9RSy12wqObYPj6e2aGK7V39sFMMmY/NCwp4cdoWNNYCvmuJ YfNS8FxrwG07oARO++IVbIyWKOpWUZIOmxAr+tE37Aj8yqCKNHZtaFSrIYv8DBFw9yzb tesxKrzFmxcqA7QjGYcjzsLJI/2tbLMehHz3OEMO2kj3r/HWNaosLU4SoM4U6YNB3g7v FofRA9IrMHHUqzC07YnElpsNqTDU8xIymQ8hAwqmZ0uzCP1isN5bRDIr1VQu1DVUL/kG GNS96SRyG6lL24agRwozyjbcaYiK+i4k+OrE2gx6emMViS4zWm2Lv3ZBSJBnZka+Wj/Z DxkA== MIME-Version: 1.0 X-Received: by 10.181.13.174 with SMTP id ez14mr134542440wid.72.1426191606580; Thu, 12 Mar 2015 13:20:06 -0700 (PDT) Sender: markjdb@gmail.com Received: by 10.194.92.229 with HTTP; Thu, 12 Mar 2015 13:20:06 -0700 (PDT) In-Reply-To: <5501108C.4080303@akips.com> References: <54FE3803.2000307@akips.com> <20150310215913.GB52108@charmander.picturesperfect.net> <54FFBDE9.5060702@akips.com> <1648097.s1OBMXVVbH@ralph.baldwin.cx> <5501108C.4080303@akips.com> Date: Thu, 12 Mar 2015 13:20:06 -0700 X-Google-Sender-Auth: 7wrwFzimb9wIYEJMQyj1YvhWL3E Message-ID: Subject: Re: Suspected libkvm infinite loop From: Mark Johnston To: Nick Frampton Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Mar 2015 20:20:08 -0000 On Wed, Mar 11, 2015 at 9:05 PM, Nick Frampton wrote: > On 12/03/15 00:38, John Baldwin wrote: >>>> >>>> It sounds like this issue might be the one fixed in r272566: if the >>>> > >KERN_PROC_ALL sysctl is read with an insufficiently large buffer, an >>>> > >sbuf error return value could bubble up and be treated as ERESTART, >>>> > >resulting in a loop. >>>> > > >>>> > >This can be confirmed with something like >>>> > > >>>> > > dtrace -n 'syscall:::entry/pid == $target/{@[probefunc] = >>>> > > count();} tick-3s {exit(0);}' -p >>>> > > >>>> > >If the output consists solely of __sysctl, this bug is likely the >>>> > >culprit. >>> >>> > >>> >Unfortunately, I accidentally killed fstat this morning before I could >>> > do any further debug. >>> > >>> >I ran truss -p on it yesterday and it was spinning solely on __sysctl. >>> > >>> >I'll try compiling with debug symbols in case it happens again. I >>> > haven't been able to reproduce the >>> >problem in a reasonable time frame so it could be days or weeks before >>> > we see it happen again. >> >> Tha truss output is consistent with Mark's suggestion, so I would try >> his suggested fix of 272566. > > > I patched the 10.1 kernel with r272566 and it appears to have fixed the > issue. Is this patch likely to be MFCed back to 10-stable? A followup to the thread: the change has been merged to stable/10 in r279926. From owner-freebsd-stable@FreeBSD.ORG Fri Mar 13 01:19:28 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CAF09A0; Fri, 13 Mar 2015 01:19:28 +0000 (UTC) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 60367C77; Fri, 13 Mar 2015 01:19:28 +0000 (UTC) Received: by iegc3 with SMTP id c3so74649241ieg.3; Thu, 12 Mar 2015 18:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=iDUvy53g+Bxi8k9mR6UldqOwNJxmBSAaT6ks+ZP+gYA=; b=RNMS82KcjRncXqz4Pp42pD05wuvnDlTdI2kLYv6NgWRQNzaTa6OVQlerHidbHR5Mhi eWoeM3aN3e7fIDTSRiCkZFkBD6vhJIh0fswz5dPEs319uXfMYcem9HDp7xmgmlYLDPxP MrQ20qXZPLqAK8ztjRJ/6Yg4ib3SYIIkdctVrWOixPySlVlRbKZy2mDap2KhTBNw0hvt 0MWvheARXJ+ST0HuGlUk4A4evaq/E/aSfRicq3ymPGuE3Y1KQiJtUAuJCJJLrtib+qXJ VPK4sUEah5eYu8SWx6CB+KnJweXRtmkXAk5otoF0+Q3lD8N732SPcEwG2p8sjJ7rUWcl FvRw== MIME-Version: 1.0 X-Received: by 10.107.25.72 with SMTP id 69mr82346940ioz.44.1426209567753; Thu, 12 Mar 2015 18:19:27 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Thu, 12 Mar 2015 18:19:27 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Mar 2015 18:19:27 -0700 X-Google-Sender-Auth: HNRvPfx3fmXw00AMllqZdzOF5XQ Message-ID: Subject: Re: On-going laptop brightness issues From: Kevin Oberman To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 01:19:28 -0000 On Thu, Mar 12, 2015 at 12:40 PM, Adrian Chadd wrote: > I thought jhb already mfc'ed it? > > > -a > > > Adrian, jhb asked that I ask you to MFC. I did so and, since you declined (as is your right and I understand that an MFC takes a fair bit of time to do correctly), I am hoping someone who has a commit bit and some spare time will take this one. I did confirm that it has not been MFCed before opening the ticket and included a patch that applies cleanly to 10-STABLE as of today. (This code in Stable has not changed for over a year.) Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Fri Mar 13 01:25:24 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 173D9B60 for ; Fri, 13 Mar 2015 01:25:24 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::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 CF5BAD7F for ; Fri, 13 Mar 2015 01:25:23 +0000 (UTC) Received: by iecvj10 with SMTP id vj10so70166419iec.0 for ; Thu, 12 Mar 2015 18:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Bf4S4XvGCevUp9bjTzW78Zk7p6Wpon3CemZxob2nRco=; b=oy34AwdqI+QH+5IqHpNFVw80j9+nKL9ouwqByOvV8uRR+XltKB3TfUInjTcSFv7Z0N tEk76FLc1zEg9S2Zg9alxzH2LMyZoeUnkGGjdlvlUNXBtiRqJHnNgvV/3TSxstn+MPSY g8P/hi3dLj1IMnnOq0p6T3i+Mzc7OtXpg1wUiIMm83pNvto+U7EMZKZFRZNO3JCQeYzG ZfKKbG+ew9Mzt3NsDx0a9Qhf1A9nhnsf68E8hULc4wzvtXVoa4vapmS2bpGY1BmyJtnP Q4Huh8MbXpDtBw6JxQEwNAG5KpAr6AWWUT2se1sPH26JkMTCvP0T9tRIArIiqS0DYSNA JJHw== MIME-Version: 1.0 X-Received: by 10.50.67.100 with SMTP id m4mr38992378igt.32.1426209922584; Thu, 12 Mar 2015 18:25:22 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Thu, 12 Mar 2015 18:25:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Mar 2015 18:25:22 -0700 X-Google-Sender-Auth: -b9XYhaa3cFgfmgF74VoSgUHO0k Message-ID: Subject: Re: On-going laptop brightness issues From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 01:25:24 -0000 On 12 March 2015 at 18:19, Kevin Oberman wrote: > On Thu, Mar 12, 2015 at 12:40 PM, Adrian Chadd wrote: >> >> I thought jhb already mfc'ed it? >> >> >> -a >> >> > > Adrian, > > jhb asked that I ask you to MFC. I did so and, since you declined (as is > your right and I understand that an MFC takes a fair bit of time to do > correctly), I am hoping someone who has a commit bit and some spare time > will take this one. > > I did confirm that it has not been MFCed before opening the ticket and > included a patch that applies cleanly to 10-STABLE as of today. (This code > in Stable has not changed for over a year.) Ah damn. :( Okay. -a From owner-freebsd-stable@FreeBSD.ORG Fri Mar 13 13:37:29 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45F3B95E; Fri, 13 Mar 2015 13:37:29 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D1F69DE; Fri, 13 Mar 2015 13:37:29 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B3013B94E; Fri, 13 Mar 2015 09:37:27 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: On-going laptop brightness issues Date: Fri, 13 Mar 2015 09:37:13 -0400 Message-ID: <1677117.BW3piSn51g@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 13 Mar 2015 09:37:27 -0400 (EDT) Cc: Kevin Oberman , Adrian Chadd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 13:37:29 -0000 On Thursday, March 12, 2015 06:19:27 PM Kevin Oberman wrote: > On Thu, Mar 12, 2015 at 12:40 PM, Adrian Chadd wrote: > > > I thought jhb already mfc'ed it? > > > > > > -a > > > > > > > Adrian, > > jhb asked that I ask you to MFC. I did so and, since you declined (as is > your right and I understand that an MFC takes a fair bit of time to do > correctly), I am hoping someone who has a commit bit and some spare time > will take this one. I was going to merge it, but there is another bug report where these changes broke a different system, see the followups here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190186 Hmm, looking at the bug report about the hang itself: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193500 it seems that there is a workaround at least, but not yet a fix. However, since there is a viable workaround the gain from merging this probably outweighs the downside. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Fri Mar 13 23:26:09 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A9E9FAD; Fri, 13 Mar 2015 23:26:09 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 883D385B; Fri, 13 Mar 2015 23:26:09 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 6A02A2BC2; Fri, 13 Mar 2015 23:26:06 +0000 (UTC) Date: Fri, 13 Mar 2015 23:25:42 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, jhb@FreeBSD.org Message-ID: <1093489915.7.1426289163797.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_stable_10 #1281 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: FAILURE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 13 Mar 2015 23:26:09 -0000 See Changes: [jhb] MFC 270516: i915 driver - enable opregion handle; program CADL. add opregion handling for drm2 - which exposes some ACPI video configuratio= n pieces that some Lenovo laptop models use to flesh out which video device to speak to. This enables the brightness control in ACPI to work these mod= els. The CADL bits are also important - it's used to figure out which ACPI events to hook the brightness buttons into. It doesn't yet seem to work for me, but it does for the OP. PR:=09=09190186, 198551 Submitted by:=09Henry Hu ------------------------------------------ [...truncated 263495 lines...] awk -f @/tools/makeobjops.awk @/dev/pccard/card_if.m -h --- depend_subdir_drm2 --- D_stable_10/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_irq.c = --- depend_subdir_drm --- --- pci_if.h --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- depend_subdir_ed --- --- pci_if.h --- --- depend_subdir_drm --- --- opt_drm.h --- --- depend_subdir_ed --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- depend_subdir_drm --- ln -sf opt_drm.h --- .depend --- --- depend_subdir_dtrace --- --- opt_compat.h --- --- depend_subdir_drm --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KE= RNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3D= iso9899:1999 --- depend_subdir_dtrace --- ln -sf opt_compat.h --- depend_subdir_ed --- --- opt_ed.h --- ln -sf opt_ed.h --- depend_subdir_dtrace --- --- opt_kstack_pages.h --- ln -sf opt_kstack_pages.h --- opt_nfs.h --- ln -sf opt_nfs.h --- depend_subdir_ed --- --- bus_if.h --- --- depend_subdir_dtrace --- --- opt_hwpmc_hooks.h --- ln -sf opt_hwpmc_hooks.h --- vnode_if.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h --- depend_subdir_ed --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- miibus_if.h --- awk -f @/tools/makeobjops.awk @/dev/mii/miibus_if.m -h --- depend_subdir_dtrace --- --- genassym.o --- cc -c -O2 -pipe -DDIS_MEM -DSMP -fno-strict-aliasing -Werror -D_KERNEL -DK= LD_MODULE -nostdinc -I -I<= https://jenkins.freebsd.org/job/FreeBSD_stable_10/ws/sys/modules/dtrace/dtr= ace/../../../cddl/dev/dtrace/x86> -I = -I -I -I<= https://jenkins.freebsd.org/job/FreeBSD_stable_10/ws/sys/modules/dtrace/dtr= ace/../../../cddl/contrib/opensolaris/uts/common> -I -I -DHAVE_KERNEL_OPTION_HEADE= RS -include -I. -I@ -I@/contrib/altq -g -= fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I = -mno-aes -mno-avx -mcmodel=3Dkernel -mno-red-zone -mno-mmx -mno-sse -msoft-= float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -gdw= arf-2 -std=3Diso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredu= ndant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoi= nter-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensio= ns -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological= -compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-u= nused-function -Wno-unknown-pragmas -Wno-parentheses -Wno-uninitialized -Wn= o-cast-qual -Wno-unused -include @/amd64/amd64/genassym.c --- depend_subdir_ed --- --- .depend --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KE= RNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3D= iso9899:1999 --- depend_subdir_drm --- =3D=3D=3D> drm/radeon (depend) --- --- @ -> --- --- machine -> --- --- x86 -> --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- bus_if.h --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- depend_subdir_dtrace --- --- assym.s --- sh @/kern/genassym.sh genassym.o > assym.s --- depend_subdir_drm --- --- pci_if.h --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- opt_drm.h --- ln -sf opt_drm.h --- .depend --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KE= RNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3D= iso9899:1999 --- agp_if.h --- awk -f -h --- modules-depend --- --- depend_subdir_em --- --- depend_subdir_dtrace --- --- .depend --- rm -f .depend --- depend_subdir_em --- =3D=3D=3D> em (depend) --- depend_subdir_dtrace --- CC=3D'cc ' mkdep -f .depend -a -nostdinc -DDIS_MEM -DSMP -D_KERNEL -DKLD_= MODULE -I -I -I -I -I -I -I -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I= @/contrib/altq -I -std=3Diso9899:1999 --- depend_subdir_em --- --- = --- @ -> --- --- machine -> --- --- x86 -> --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- bus_if.h --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- pci_if.h --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- opt_inet.h --- ln -sf opt_inet.h --- opt_inet6.h --- ln -sf opt_inet6.h --- .depend --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3Diso9899:1999 --- depend_subdir_drm --- =3D=3D=3D> drm/savage (depend) --- depend_subdir_dtrace --- =3D=3D=3D> dtrace/dtraceall (depend) --- depend_subdir_drm2 --- In file included from :37: @/dev/acpica/acpivar.h:36:10: fatal error: 'acpi_if.h' file not found #include "acpi_if.h" ^ 1 error generated. --- depend_subdir_drm --- --- --- --- depend_subdir_dtrace --- --- --- --- depend_subdir_drm --- @ -> --- --- --- depend_subdir_dtrace --- @ -> --- depend_subdir_drm --- machine -> --- depend_subdir_dtrace --- --- --- machine -> --- depend_subdir_drm --- --- --- --- depend_subdir_dtrace --- --- --- x86 -> --- depend_subdir_drm --- x86 -> --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- depend_subdir_dtrace --- --- opt_compat.h --- ln -sf opt_compat.h --- opt_nfs.h --- ln -sf opt_nfs.h --- .depend --- --- depend_subdir_drm --- --- bus_if.h --- --- depend_subdir_dtrace --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3Diso9899:1999 --- depend_subdir_drm --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- pci_if.h --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- opt_drm.h --- ln -sf opt_drm.h --- depend_subdir_dtrace --- =3D=3D=3D> dtrace/dtrace_test (depend) --- depend_subdir_drm --- --- .depend --- rm -f .depend CC=3D'cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=3Diso9899:1999 --- depend_subdir_dtrace --- --- --- @ -> --- --- machine -> --- --- x86 -> --- opt_kdtrace.h --- ln -sf opt_kdtrace.h --- vnode_if_newproto.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p --- vnode_if_typedef.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q --- vnode_if.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h --- depend_subdir_drm2 --- mkdep: compile failed *** [.depend] Error code 1 make[5]: stopped in 1 error make[5]: stopped in *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in --- depend_subdir_dtrace --- A failure has been detected in another branch of the parallel make --- depend_subdir_drm2 --- *** [depend_subdir_drm2] Error code 2 make[3]: stopped in --- depend_subdir_dtrace --- make[5]: stopped in *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [depend_subdir_dtrace] Error code 2 make[3]: stopped in --- depend_subdir_drm --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [depend_subdir_drm] Error code 2 make[3]: stopped in --- depend_subdir_em --- A failure has been detected in another branch of the parallel make make[4]: stopped in *** [depend_subdir_em] Error code 2 make[3]: stopped in 4 errors make[3]: stopped in *** [modules-depend] Error code 2 make[2]: stopped in 1 error make[2]: stopped in *** [buildkernel] Error code 2 make[1]: stopped in 1 error make[1]: stopped in *** [buildkernel] Error code 2 make: stopped in 1 error make: stopped in Build step 'Execute shell' marked build as failure From owner-freebsd-stable@FreeBSD.ORG Sat Mar 14 11:06:50 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47574B4D; Sat, 14 Mar 2015 11:06:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 2888B240; Sat, 14 Mar 2015 11:06:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id C1AEE2CBC; Sat, 14 Mar 2015 11:06:48 +0000 (UTC) Date: Sat, 14 Mar 2015 11:06:45 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, jhb@FreeBSD.org, kib@FreeBSD.org Message-ID: <1346765374.8.1426331206890.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1093489915.7.1426289163797.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1093489915.7.1426289163797.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_stable_10 #1282 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: FAILURE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 14 Mar 2015 11:06:50 -0000 See Changes: [kib] MFC r279401: Some fixes for fdescfs lookup code Do not ever return doomed vnode from. lookup. Reuse the vn_vget_ino_gen() helper to handle parallel unmounts . ------------------------------------------ [...truncated 270882 lines...] --- --- machine -> --- --- x86 -> --- depend_subdir_drm --- ===> drm/savage (depend) --- depend_subdir_dtrace --- --- opt_compat.h --- ln -sf opt_compat.h --- opt_nfs.h --- ln -sf opt_nfs.h --- .depend --- rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=iso9899:1999 --- depend_subdir_drm --- --- --- @ -> --- --- machine -> --- --- x86 -> --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- depend_subdir_dtrace --- ===> dtrace/dtrace_test (depend) --- depend_subdir_drm --- --- bus_if.h --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- pci_if.h --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- depend_subdir_dtrace --- --- --- --- depend_subdir_drm --- --- opt_drm.h --- ln -sf opt_drm.h --- .depend --- --- depend_subdir_dtrace --- @ -> --- depend_subdir_drm --- rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=iso9899:1999 --- depend_subdir_dtrace --- --- --- machine -> --- --- x86 -> --- opt_kdtrace.h --- ln -sf opt_kdtrace.h --- vnode_if_newproto.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p --- vnode_if_typedef.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q --- vnode_if.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h --- depend_subdir_drm --- ===> drm/sis (depend) --- depend_subdir_dtrace --- --- .depend --- rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -D_KERNEL -DKLD_MODULE -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=iso9899:1999 ===> dtrace/lockstat (depend) --- depend_subdir_drm2 --- In file included from :37: @/dev/acpica/acpivar.h:36:10: fatal error: 'acpi_if.h' file not found #include "acpi_if.h" ^ 1 error generated. --- depend_subdir_drm --- --- --- @ -> --- --- machine -> --- depend_subdir_dtrace --- --- --- --- depend_subdir_drm --- --- --- --- depend_subdir_dtrace --- @ -> --- depend_subdir_drm --- x86 -> --- depend_subdir_dtrace --- --- --- --- depend_subdir_drm --- --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- depend_subdir_dtrace --- machine -> --- --- --- depend_subdir_drm --- --- bus_if.h --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- depend_subdir_dtrace --- x86 -> --- vnode_if_newproto.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p --- vnode_if_typedef.h --- --- depend_subdir_drm --- --- pci_if.h --- --- depend_subdir_dtrace --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q --- depend_subdir_drm --- awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h --- depend_subdir_dtrace --- --- opt_kdtrace.h --- ln -sf opt_kdtrace.h --- depend_subdir_drm --- --- opt_drm.h --- ln -sf opt_drm.h --- .depend --- rm -f .depend --- depend_subdir_dtrace --- --- vnode_if.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h --- depend_subdir_drm --- CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=iso9899:1999 --- depend_subdir_dtrace --- --- .depend --- rm -f .depend CC='cc ' mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I -I -I -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I -std=iso9899:1999 --- mmcbr_if.h --- awk -f -h --- modules-depend --- --- depend_subdir_en --- ===> en (depend) --- depend_subdir_dtrace --- ===> dtrace/profile (depend) --- depend_subdir_drm --- ===> drm/tdfx (depend) --- depend_subdir_en --- --- --- --- depend_subdir_dtrace --- --- --- --- depend_subdir_en --- @ -> --- --- --- depend_subdir_dtrace --- @ -> --- depend_subdir_en --- machine -> --- depend_subdir_dtrace --- --- --- machine -> --- depend_subdir_en --- --- --- --- depend_subdir_dtrace --- --- --- --- depend_subdir_en --- x86 -> --- depend_subdir_dtrace --- x86 -> --- vnode_if_newproto.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p --- depend_subdir_drm --- --- --- --- depend_subdir_en --- --- device_if.h --- awk -f @/tools/makeobjops.awk @/kern/device_if.m -h --- depend_subdir_dtrace --- --- vnode_if_typedef.h --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q --- depend_subdir_drm --- @ -> --- depend_subdir_en --- --- bus_if.h --- awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h --- depend_subdir_drm2 --- mkdep: compile failed --- depend_subdir_drm --- --- --- machine -> --- --- x86 -> --- depend_subdir_dtrace --- --- vnode_if.h --- --- depend_subdir_drm2 --- *** [.depend] Error code 1 make[5]: stopped in 1 error make[5]: stopped in --- depend_subdir_dtrace --- awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h --- depend_subdir_drm2 --- *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in --- depend_subdir_drm --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [depend_subdir_drm] Error code 2 make[3]: stopped in --- depend_subdir_drm2 --- *** [depend_subdir_drm2] Error code 2 make[3]: stopped in --- depend_subdir_en --- A failure has been detected in another branch of the parallel make make[4]: stopped in *** [depend_subdir_en] Error code 2 make[3]: stopped in --- depend_subdir_dtrace --- A failure has been detected in another branch of the parallel make make[5]: stopped in *** [_sub.depend] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [depend_subdir_dtrace] Error code 2 make[3]: stopped in 4 errors make[3]: stopped in *** [modules-depend] Error code 2 make[2]: stopped in 1 error make[2]: stopped in *** [buildkernel] Error code 2 make[1]: stopped in 1 error make[1]: stopped in *** [buildkernel] Error code 2 make: stopped in 1 error make: stopped in Build step 'Execute shell' marked build as failure From owner-freebsd-stable@FreeBSD.ORG Sat Mar 14 14:37:45 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA6D2F81; Sat, 14 Mar 2015 14:37:45 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 98047970; Sat, 14 Mar 2015 14:37:45 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A124D2CF9; Sat, 14 Mar 2015 14:37:45 +0000 (UTC) Date: Sat, 14 Mar 2015 14:37:44 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, jhb@FreeBSD.org, kib@FreeBSD.org Message-ID: <584024178.9.1426343865594.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1346765374.8.1426331206890.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1346765374.8.1426331206890.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : FreeBSD_stable_10 #1283 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 14 Mar 2015 14:37:45 -0000 See From owner-freebsd-stable@FreeBSD.ORG Sat Mar 14 22:09:34 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA5067F3 for ; Sat, 14 Mar 2015 22:09:34 +0000 (UTC) Received: from roadkill.tharned.org (roadkill.tharned.org [75.145.12.185]) (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 539B3869 for ; Sat, 14 Mar 2015 22:09:34 +0000 (UTC) Received: from angus.tharned.org (angus.tharned.org [10.10.10.7]) (authenticated bits=0) by roadkill.tharned.org (8.14.9/8.14.9) with ESMTP id t2EM8wtI063474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 14 Mar 2015 17:09:04 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2014; t=1426370944; bh=ESN2R89L8KWSglrB/q2k03uYx/qLovbOFtASwCHCUTI=; h=Date:From:To:Subject; b=H7yW5jgBqe27M364VS8h3BCXMeKkGWVXU/s1ncaXEZ4efBUV3S3Mh+HQCDlzVZxCz INu4FJo/6YFW2DJtSahHIRdmEtPLSC6XACwDFbCcAYuqVpeAw7TikS7yNnx9Hq+Y7p /ZAZE0kZEUM0B+xRwOvXgnsHASNVAWBVE+4rzV2I+/Gx9ev8gDbR2XQz7CnXBkr9qB HtV6ARM2VsF3N+1EtXXJOh1U7ro4YSFLtNsTmyL1KYnaJoMCwfvlnMtXJKyJecUP/t xK6grkifIerjrCSN2IGhVKw1zOzA3k1aJEECxi0z8BL9pq2ckE4md/8Ygi1qgASLAu i4a22swxC+QKQ== Date: Sat, 14 Mar 2015 17:08:57 -0500 (CDT) From: Greg Rivers To: freebsd-stable@freebsd.org Subject: HP EliteBook EFI boot failure Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (roadkill.tharned.org [75.145.12.185]); Sat, 14 Mar 2015 17:09:04 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 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, 14 Mar 2015 22:09:34 -0000 I'm unable to boot the memstick EFI images on a HP EliteBook 850 G1 (SKU F2Q24UT#ABA). The BIOS is up to date and set to the default "UEFI Native (Without CSM)" setting. I tried the most recent 10.1-STABLE and 11.0-CURRENT snapshots with the following results (hand transcribed from the screen): FreeBSD-10.1-STABLE-amd64-20150309-r279796-uefi-memstick.img.xz: -------------------------------------------------------------------------------- >> FreeBSD EFI boot block Loader path: /boot/loader.efi Consoles: EFI console Image base: 0x9fb5e000 EFI version 2.10 EFI Firmware: HPQ (rev 4096.01) FreeBSD/amd64 EFI loader, Revision 1.1 (root@releng1.nyi.freebsd.org, Mon Mar 9 16:10:08 UTC 2015) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0xf9d8c8 data=0x125ce8 syms=[0x8+0x141318+0x8+0x15be03] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Start @ 0xffffffff802dbc90 ... -------------------------------------------------------------------------------- FreeBSD-11.0-CURRENT-amd64-20150309-r279813-memstick.img.xz: -------------------------------------------------------------------------------- >> FreeBSD EFI boot block Loader path: /boot/loader.efi Consoles: EFI console Image base: 0x9fa06000 EFI version 2.10 EFI Firmware: HPQ (rev 4096.01) FreeBSD/amd64 EFI loader, Revision 1.1 (root@releng2.nyi.freebsd.org, Mon Mar 9 16:24:01 UTC 2015) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x103a3c0 data=0x3faef0 syms=[0x8+0x148f38+0x8+0x164ae7] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Start @ 0xffffffff802e4000 ... EFI framebuffer information: addr, size 0xc0000000, 0x7e9000 dimensions 1920 x 1080 stride 1920 masks 0x0ff0000, 0x000000ff, 0xff000000 -------------------------------------------------------------------------------- In both cases the system simply hangs. How can I help debug this? -- Greg Rivers