From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 00:44:15 2014 Return-Path: Delivered-To: hackers@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 2C4DC491 for ; Sun, 7 Dec 2014 00:44:15 +0000 (UTC) Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F33ED83D for ; Sun, 7 Dec 2014 00:44:14 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id ft15so2930960pdb.18 for ; Sat, 06 Dec 2014 16:44:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=WpN4ZaDE2yhyHuPAFj4vNfvXo9UCVppu457iDorgg/w=; b=g4dCQkWTkRLHTvEQGNA0rooWNDo2fZD8KuKPtx+d5rhvzfv+AGv2ANYNlvQCYsWy0y 6CAswQ2sd1BQcC5PA6rrUylrN3BK8UuKd8hNC4jt9uVHBt+Cf1UULZMQhun42myD+oQv bCjCbhz9oXe6+y0y+ADB7qfgsk4Yv14TSE30jGBKuQSaK5Pl23XtJjLbglgbp1o8Q03B CxftR/hlsLmjw+Hpui5l1RKX10pEn389qEzHatiblWdNmvhOMqc6ot9LzZ36tstyDWma xnzC7p1fu0aNdg6EF6lUb5BWp7DiJ4/WbdbS3gzVNDv49Htw7/0onCJi3PcIS0vzXNnd Sjbg== X-Gm-Message-State: ALoCoQmHocIEAHwx/aQ0oFNkKrsaR31aDQCby+GLxEdA9lpuOUml31alM7TbJ0lIV6fr3qJ8oy8v X-Received: by 10.70.89.174 with SMTP id bp14mr8405018pdb.136.1417913048179; Sat, 06 Dec 2014 16:44:08 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id tm3sm32852578pac.12.2014.12.06.16.44.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Dec 2014 16:44:07 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <5482B805.3020602@optusnet.com.au> Date: Sat, 6 Dec 2014 16:44:04 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <5482B805.3020602@optusnet.com.au> To: Tony Maher X-Mailer: Apple Mail (2.1993) Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 00:44:15 -0000 > On Dec 6, 2014, at 12:02 AM, Tony Maher = wrote: >=20 > I finally got a chance to try USB memstick with 10.1. > It failed with BTX halted. I tried various BIOS options > related to USB booting but same result everytime. > I could Ctrl-Alt-Del to reboot. > Not much help I am afraid. >=20 > cheers > --=20 > Tony Maher email: tonymaher@optusnet.com.au Tony, Considering that we both have the same board and BIOS and very similar = processors, how very odd that mine will happily boot from a USB stick = and yours won=E2=80=99t, but mine hangs during the probing and yours = doesn=E2=80=99t. Christopher From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 01:32:44 2014 Return-Path: Delivered-To: freebsd-hackers@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 DF33E892 for ; Sun, 7 Dec 2014 01:32:44 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id CCA4BBD0 for ; Sun, 7 Dec 2014 01:32:44 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 83C2D341F867 for ; Sat, 6 Dec 2014 17:32:44 -0800 (PST) Message-ID: <5483AE21.8090306@freebsd.org> Date: Sat, 06 Dec 2014 17:32:17 -0800 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: FreeBSD Hackers Subject: cross installing freebsd? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 01:32:45 -0000 Hey folks, In order to make installation of a new world/kernel on my i386 soekris a LOT faster/easier I've taken to doing builds on an amd64 host and then "cross-installing" Steps are as follows: On amd64 host: /usr/trees/freebsd.git % env TARGET=i386 make -j8 buildworld && env TARGET=i386 make -j8 buildkernel On i386 host: mount spigot:/usr/trees /usr/trees mount spigot:/usr/obj /usr/obj cd /usr/trees/freebsd.git # install kernel: env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ INSTALL=/usr/bin/install \ make installkernel # install world: env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ INSTALL=/usr/bin/install STRIPBIN=/usr/bin/strip \ MAKEWHATIS=/usr/bin/makewhatis \ make installworld Seems to work nicely. Any objections if I add something like this target as "cross-installworld" and "cross-installkernel" to top level Makefile? -Alfred From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 03:09:04 2014 Return-Path: Delivered-To: hackers@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 76200CFC for ; Sun, 7 Dec 2014 03:09:04 +0000 (UTC) Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F522608 for ; Sun, 7 Dec 2014 03:09:04 +0000 (UTC) Received: by mail-yh0-f44.google.com with SMTP id c41so1422186yho.31 for ; Sat, 06 Dec 2014 19:09:03 -0800 (PST) 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=kKsSIPem+eBkeTGq/7Jr36k/QMUFLsDqsTOAEpYriy0=; b=FR4DVTjNu/coP7niJZTj1Zvks/NN1/ZWgXpZLOzgMRiYjiJtek12YTzXNGSTrbR8x2 LI3QYbKxZ0e/YGdPpzc7LP/IydOjcGFxh0RwppXbY45R5acOazcQjdjkmDeB3XvvH8tl s+EFqnXvJkmNfwPGsxXoDmewOewEIHoxETvkOpkjEZhESSedJudHZpVuU4yGpNMjQFeu xOl0d/EmzMr0KLZ3/7NDZdKRXZXg1zBnccmjqg7gwjd5QWDYZyyOmTI6InzVBEU7F67T AsbMGwl2n4p6vjHaufr/rheku3LYY2niqKMde7V+gqdR44eUqZdNVXV+/JGWtPADYIGG v/cQ== MIME-Version: 1.0 X-Received: by 10.170.124.16 with SMTP id q16mr27729845ykb.107.1417921743132; Sat, 06 Dec 2014 19:09:03 -0800 (PST) Received: by 10.170.90.131 with HTTP; Sat, 6 Dec 2014 19:09:03 -0800 (PST) In-Reply-To: <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <5482B805.3020602@optusnet.com.au> <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> Date: Sat, 6 Dec 2014 19:09:03 -0800 Message-ID: Subject: Re: 10.1 hangs during boot on Intel DP35DP board From: Mehmet Erol Sanliturk To: "Christopher R. Bowman" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tony Maher , "hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 03:09:04 -0000 On Sat, Dec 6, 2014 at 4:44 PM, Christopher R. Bowman wrote: > > On Dec 6, 2014, at 12:02 AM, Tony Maher > wrote: > > > > I finally got a chance to try USB memstick with 10.1. > > It failed with BTX halted. I tried various BIOS options > > related to USB booting but same result everytime. > > I could Ctrl-Alt-Del to reboot. > > Not much help I am afraid. > > > > cheers > > -- > > Tony Maher email: tonymaher@optusnet.com.au > > Tony, > Considering that we both have the same board and BIOS and very similar > processors, how very odd that mine will happily boot from a USB stick and > yours won=E2=80=99t, but mine hangs during the probing and yours doesn=E2= =80=99t. > Christopher > _______________________________________________ > > Impedance mismatch : http://en.wikipedia.org/wiki/Impedance_matching Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 03:10:23 2014 Return-Path: Delivered-To: hackers@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 2A9ACDE0 for ; Sun, 7 Dec 2014 03:10:23 +0000 (UTC) Received: from mail105.syd.optusnet.com.au (mail105.syd.optusnet.com.au [211.29.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id E113C618 for ; Sun, 7 Dec 2014 03:10:22 +0000 (UTC) Received: from zen.home (c211-30-203-218.thorn2.nsw.optusnet.com.au [211.30.203.218]) (Authenticated sender: tonymaher@optusnet.com.au) by mail105.syd.optusnet.com.au (Postfix) with ESMTPA id A39AA1040EB9; Sun, 7 Dec 2014 14:10:20 +1100 (AEDT) Message-ID: <5483C51C.8000906@optusnet.com.au> Date: Sun, 07 Dec 2014 14:10:20 +1100 From: Tony Maher User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "Christopher R. Bowman" Subject: Re: 10.1 hangs during boot on Intel DP35DP board References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <5482B805.3020602@optusnet.com.au> <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> In-Reply-To: <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=dMCfxopb c=1 sm=1 tr=0 a=MQ6uhdTv3FoGARDo7fdH2w==:117 a=MQ6uhdTv3FoGARDo7fdH2w==:17 a=PO7r1zJSAAAA:8 a=_M8H_RHeOCMA:10 a=IkcTkHD0fZMA:10 a=s16sUXrb-bPV8nI6xL8A:9 a=QEXdDO2ut3YA:10 a=dvg4hahemeQA:10 a=xXYpSUSE7EsA:10 a=Zt_YgOI5I4gA:10 a=k6Yqosr5OAQA:10 a=XLPQ4plS_DgA:10 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 03:10:23 -0000 Hello, I tried a CDROM with FreeBSD-10.1-RELEASE-amd64-bootonly.iso and it booted fine and entered Live CD shell. All looked ok. cheers -- Tony Maher email: tonymaher@optusnet.com.au From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 03:26:18 2014 Return-Path: Delivered-To: freebsd-hackers@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 BCFF2429; Sun, 7 Dec 2014 03:26:18 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E2967FD; Sun, 7 Dec 2014 03:26:18 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id gm9so2413621lab.40 for ; Sat, 06 Dec 2014 19:26:16 -0800 (PST) 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=NGRMTsGp6fVuhxTDIfL9m5tIJVTPGYz0iRwcti1YVjM=; b=aCDSyd3FxEl2ftluD1DWe+EpGyVkskF8+UKR8Wa1CH0DgeSIsEThbAmNwfvuRurd/Y l9CWmI5OMUk0AczdKRz4LjVsoRN7c29XH4jceOwh5Di3SjdA30dgGNenzh5YBG+27K/q cxZT9ueFEhHio3d3WULYexBEl9CO8Lhx+3tlYtMnvmhBKzbFH5re/cH7gItWXrsvr+Zw 88tAk6vlu6DxIX0ZZkNQnlqXAYMW+kFMe946MvuYPX46diqaLzp8PqJMtMfflplf7R/6 t8IiEXV6I06lBPMftFd8KbU7eXPivG21dSJrgrh4XF8Ctw8mZkCr5g3xcaAo+dBMZwmd sXEg== MIME-Version: 1.0 X-Received: by 10.152.87.100 with SMTP id w4mr9944308laz.71.1417922776241; Sat, 06 Dec 2014 19:26:16 -0800 (PST) Sender: rizzo.unipi@gmail.com Received: by 10.114.174.169 with HTTP; Sat, 6 Dec 2014 19:26:16 -0800 (PST) In-Reply-To: <5483AE21.8090306@freebsd.org> References: <5483AE21.8090306@freebsd.org> Date: Sun, 7 Dec 2014 14:26:16 +1100 X-Google-Sender-Auth: 854xnX2H2NKZ0Pyd2LIxa3cKVNY Message-ID: Subject: Re: cross installing freebsd? From: Luigi Rizzo To: Alfred Perlstein Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 03:26:18 -0000 On Sunday, December 7, 2014, Alfred Perlstein wrote: > Hey folks, > > In order to make installation of a new world/kernel on my i386 soekris a > LOT faster/easier I've taken to doing builds on an amd64 host and then > "cross-installing" > > Steps are as follows: > > On amd64 host: > /usr/trees/freebsd.git % env TARGET=i386 make -j8 buildworld && env > TARGET=i386 make -j8 buildkernel > > On i386 host: > mount spigot:/usr/trees /usr/trees > mount spigot:/usr/obj /usr/obj > cd /usr/trees/freebsd.git > # install kernel: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install \ > make installkernel > # install world: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install STRIPBIN=/usr/bin/strip \ > MAKEWHATIS=/usr/bin/makewhatis \ > make installworld > > Seems to work nicely. > > Any objections if I add something like this target as "cross-installworld" > and "cross-installkernel" to top level Makefile? > > If you do so please put the extra targets into an additional make file that is included by the main one so people can easily exclude or modify it. Or perhaps put something in tools/tools . The master makefule is way too complex for humans, and i suspect very fragile too. I also have my own makefile that I use for custom cross builds and wouldn't mind seeing some better example than what I could come up with. As an example from time to time I read good advice from people to cross build kernel modules or individual binaries which I always forget. They would fit well in this extra make file. Cheers Luigi -Alfred > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2211611 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 10:00:43 2014 Return-Path: Delivered-To: freebsd-hackers@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 1A0AD629 for ; Sun, 7 Dec 2014 10:00:43 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A0742C12 for ; Sun, 7 Dec 2014 10:00:42 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB79e9NP063141 for ; Sun, 7 Dec 2014 10:40:09 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 10:40:05 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: FreeBSD Hackers Subject: 10.1-STABLE one week old from svn - random hangs Message-ID: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 10:40:10 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 10:00:43 -0000 i have a problem with FreeBSD-10. To make it more probable one have to 1) reduce maxbcache. eg kern.maxbcache=50000000 in loader.conf but NOT doing this doesn't make problem disappear. it is just more rare. 2) use swap. But you don't need system that swaps heavily. Probably - it may not swap at all. 3) do lots of I/O 4) it is more often if you use virtualbox, but still - it is not required, just make problem more common. The problem. At random moment system I/O stops. If you are running top at this moment, there are lots of prosesses stalled in vnread or biord. network keeps running, processes that doesn't need I/O still runs. top often reports at least 10MB free memory. seems like a deadlock. Anyone know that problem. How to trace it down? From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 11:36:33 2014 Return-Path: Delivered-To: freebsd-hackers@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 0D096BBC for ; Sun, 7 Dec 2014 11:36:33 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id C5D8F74E for ; Sun, 7 Dec 2014 11:36:32 +0000 (UTC) Received: from [192.168.135.70] (unknown [94.19.235.70]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 8181A5C002; Sun, 7 Dec 2014 14:36:21 +0300 (MSK) Message-ID: <54843BB3.2000602@FreeBSD.org> Date: Sun, 07 Dec 2014 14:36:19 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Wojciech Puchar , FreeBSD Hackers Subject: Re: 10.1-STABLE one week old from svn - random hangs References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 11:36:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07.12.2014 12:40, Wojciech Puchar wrote: > The problem. At random moment system I/O stops. If you are running > top at this moment, there are lots of prosesses stalled in vnread > or biord. network keeps running, processes that doesn't need I/O > still runs. > > top often reports at least 10MB free memory. > > seems like a deadlock. Anyone know that problem. How to trace it > down? Looks like I have same problem sometimes. And you could not run any new process, you could not login on console, but you could switch virtual consoles & if "top" is running on one of them, it doesn't hang itself, right? I get this typically when "svnsync" synchronize my local FreeBSD repo mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged. - -- // Lev Serebryakov AKA Black Lion -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ oeXgB3qxqhPtvfDmUm+X =R88v -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 12:32:14 2014 Return-Path: Delivered-To: freebsd-hackers@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 A695C5CF; Sun, 7 Dec 2014 12:32:14 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 933FDC35; Sun, 7 Dec 2014 12:32:14 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id DAD64341F84E; Sun, 7 Dec 2014 04:32:13 -0800 (PST) Message-ID: <548448B1.20907@freebsd.org> Date: Sun, 07 Dec 2014 04:31:45 -0800 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: lev@FreeBSD.org, Wojciech Puchar , FreeBSD Hackers Subject: Re: 10.1-STABLE one week old from svn - random hangs References: <54843BB3.2000602@FreeBSD.org> In-Reply-To: <54843BB3.2000602@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 12:32:14 -0000 Can you enable crashdumps please and then send a traceback? https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html These two are most helpful: https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html On 12/7/14, 3:36 AM, Lev Serebryakov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 07.12.2014 12:40, Wojciech Puchar wrote: > >> The problem. At random moment system I/O stops. If you are running >> top at this moment, there are lots of prosesses stalled in vnread >> or biord. network keeps running, processes that doesn't need I/O >> still runs. >> >> top often reports at least 10MB free memory. >> >> seems like a deadlock. Anyone know that problem. How to trace it >> down? > Looks like I have same problem sometimes. And you could not run any > new process, you could not login on console, but you could switch > virtual consoles & if "top" is running on one of them, it doesn't hang > itself, right? > > I get this typically when "svnsync" synchronize my local FreeBSD repo > mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged. > > - -- > // Lev Serebryakov AKA Black Lion > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF > QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo > NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk > +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG > ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx > XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc > VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP > CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX > kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC > ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 > 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf > a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ > oeXgB3qxqhPtvfDmUm+X > =R88v > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 12:58:30 2014 Return-Path: Delivered-To: hackers@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 2F448A14 for ; Sun, 7 Dec 2014 12:58:30 +0000 (UTC) Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3007E01 for ; Sun, 7 Dec 2014 12:58:29 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id eu11so3542689pac.39 for ; Sun, 07 Dec 2014 04:58:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:message-id:references:to; bh=qB87H2l9YPw75S0BsNi9n5lm9eOIill1sYreKzj7Brg=; b=RlDZ4FHtP+4rdt49yLcPSLtulrPgY/loZMJDDFw5SisM4rFK+rOfC+prJQuUwWoF8U O/aApCj6PPOQxE/AaYYGHNbuH7js1G1mGmGgF2IhB+w0nS1hNQqfFwbQMyurtVehY/xH qV4yhoFHt0OPfR0pmQFBschxjJB5L9of8BmrVjDSOab5vjTLYkZ1bQM+zAkIIwP6iXbZ s7LQty5zyPKKc0+ySmBldR3zizZdQf05qKeqXP4z+aJdfMzDBhM/TCjVstOVeDkVp9ds 2rfXobADsVyFA+mmgVLaww8Tx/hEmvDh46rD4SCLaWkKlbp3VuglDuR19ReoK/0O8ZU7 Z3jQ== X-Gm-Message-State: ALoCoQluDa8yNVqHETAZ6ksntBdw0PGCHphbCoEWPGylzMMGWNFDCCrjl6NeSSO3fQIg3zibzZkd X-Received: by 10.70.94.73 with SMTP id da9mr12094416pdb.51.1417957103065; Sun, 07 Dec 2014 04:58:23 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id ni9sm25150744pdb.36.2014.12.07.04.58.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 07 Dec 2014 04:58:22 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <5483C51C.8000906@optusnet.com.au> Date: Sun, 7 Dec 2014 04:58:20 -0800 Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <5482B805.3020602@optusnet.com.au> <8EEF631D-AC58-4BE8-9244-459A3D97B992@ChrisBowman.com> <5483C51C.8000906@optusnet.com.au> To: Tony Maher X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 12:58:30 -0000 > On Dec 6, 2014, at 7:10 PM, Tony Maher = wrote: >=20 > Hello, >=20 > I tried a CDROM with FreeBSD-10.1-RELEASE-amd64-bootonly.iso > and it booted fine and entered Live CD shell. All looked ok. > cheers > --=20 > Tony Maher email: tonymaher@optusnet.com.au Tony, Well, again, thank you. It=E2=80=99s helpful to at least know = that board can boot 10.1. I wish I knew what to ask you to figure out = why mine won=E2=80=99t. Christopher From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 13:25:20 2014 Return-Path: Delivered-To: freebsd-hackers@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 8CBF314A; Sun, 7 Dec 2014 13:25:20 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9EF131; Sun, 7 Dec 2014 13:25:19 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7DPFH0068337; Sun, 7 Dec 2014 14:25:15 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 14:25:11 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Lev Serebryakov Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: <54843BB3.2000602@FreeBSD.org> Message-ID: References: <54843BB3.2000602@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 14:25:15 +0100 (CET) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 13:25:20 -0000 >> >> seems like a deadlock. Anyone know that problem. How to trace it >> down? > Looks like I have same problem sometimes. And you could not run any > new process, you could not login on console, but you could switch > virtual consoles & if "top" is running on one of them, it doesn't hang > itself, right? yes. ping works. all hanged process waits for I/O infinitely. no I/O is going. strange sometimes it does not happen WHILE performing heavy I/O, but after. some kind of deadlock. From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 13:25:50 2014 Return-Path: Delivered-To: freebsd-hackers@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 3AFA9226; Sun, 7 Dec 2014 13:25:50 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B64E5138; Sun, 7 Dec 2014 13:25:49 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7DPklG068354; Sun, 7 Dec 2014 14:25:47 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 14:25:43 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Alfred Perlstein Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: <548448B1.20907@freebsd.org> Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 14:25:47 +0100 (CET) Cc: FreeBSD Hackers , lev@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 13:25:50 -0000 no crashdump. system does not panic so i cannot do this On Sun, 7 Dec 2014, Alfred Perlstein wrote: > Can you enable crashdumps please and then send a traceback? > > > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > > These two are most helpful: > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html > > > On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> On 07.12.2014 12:40, Wojciech Puchar wrote: >> >>> The problem. At random moment system I/O stops. If you are running >>> top at this moment, there are lots of prosesses stalled in vnread >>> or biord. network keeps running, processes that doesn't need I/O >>> still runs. >>> >>> top often reports at least 10MB free memory. >>> >>> seems like a deadlock. Anyone know that problem. How to trace it >>> down? >> Looks like I have same problem sometimes. And you could not run any >> new process, you could not login on console, but you could switch >> virtual consoles & if "top" is running on one of them, it doesn't hang >> itself, right? >> >> I get this typically when "svnsync" synchronize my local FreeBSD repo >> mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged. >> >> - -- // Lev Serebryakov AKA Black Lion >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.22 (MingW32) >> >> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >> oeXgB3qxqhPtvfDmUm+X >> =R88v >> -----END PGP SIGNATURE----- >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 13:38:06 2014 Return-Path: Delivered-To: freebsd-hackers@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 E06D6D6A; Sun, 7 Dec 2014 13:38:05 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 84004243; Sun, 7 Dec 2014 13:38:05 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7Dc221068937; Sun, 7 Dec 2014 14:38:03 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 14:37:59 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Alfred Perlstein Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 14:38:03 +0100 (CET) Cc: FreeBSD Hackers , lev@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 13:38:06 -0000 how to get via svn or other means sources of 10*-STABLE from 18.06.2014? to get back to working system. On Sun, 7 Dec 2014, Wojciech Puchar wrote: > no crashdump. system does not panic > so i cannot do this > > On Sun, 7 Dec 2014, Alfred Perlstein wrote: > >> Can you enable crashdumps please and then send a traceback? >> >> >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >> >> These two are most helpful: >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html >> >> >> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>> >>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>> >>>> The problem. At random moment system I/O stops. If you are running >>>> top at this moment, there are lots of prosesses stalled in vnread >>>> or biord. network keeps running, processes that doesn't need I/O >>>> still runs. >>>> >>>> top often reports at least 10MB free memory. >>>> >>>> seems like a deadlock. Anyone know that problem. How to trace it >>>> down? >>> Looks like I have same problem sometimes. And you could not run any >>> new process, you could not login on console, but you could switch >>> virtual consoles & if "top" is running on one of them, it doesn't hang >>> itself, right? >>> >>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged. >>> >>> - -- // Lev Serebryakov AKA Black Lion >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.22 (MingW32) >>> >>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>> oeXgB3qxqhPtvfDmUm+X >>> =R88v >>> -----END PGP SIGNATURE----- >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >>> >> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 14:38:26 2014 Return-Path: Delivered-To: freebsd-hackers@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 80D029FA for ; Sun, 7 Dec 2014 14:38:26 +0000 (UTC) Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 43DA69DF for ; Sun, 7 Dec 2014 14:38:25 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 10so1601682ykt.5 for ; Sun, 07 Dec 2014 06:38:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jBHpmXTvxO+CHEQUL/QrnCgmLlPbRICGK0I3Y/8ODWY=; b=B6AIdMXW3jT0O5vftcfPNTKWKf90pjdajWWYiGW4wZtvAUopAzRKDdgEB2aHcc8gKk usPXuiHOkQWswlTt4NnJ91tP+rVJBOJwqKYMklZ/ELA/uuzYoyoXhQ1NAiVdTe51loYH UnHe4PT/mLJBhdE01YqR6hsswJXBZIzyedwS02BVQE5r86XyOugO5YRkMxMwa8FG66Ye FOZ8P3tX+XT7HTtKd1VVS99pB0ntS/WEpkeJvrLHs387wjOHOtBP2odLgtl0TAy4jIAP WOrQvNQDJrT8SvQHzl4OPCseLS7O8Pt9/X6g6NKgRlqef8OO3cphd9F5Ww6egyu7yK85 R3Ig== X-Gm-Message-State: ALoCoQlCZ9zl68JgCzXZV8ZZcTxI/olr8odm+gR7b/+L46YnCHc/LfmGGhGz8vgAA/tUQr4bkoYk MIME-Version: 1.0 X-Received: by 10.170.170.87 with SMTP id m84mr29607316ykd.106.1417961470253; Sun, 07 Dec 2014 06:11:10 -0800 (PST) Received: by 10.170.46.213 with HTTP; Sun, 7 Dec 2014 06:11:10 -0800 (PST) In-Reply-To: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> Date: Sun, 7 Dec 2014 15:11:10 +0100 Message-ID: Subject: Re: 10.1-STABLE one week old from svn - random hangs From: Oliver Pinter To: Wojciech Puchar Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Hackers , Alfred Perlstein , lev@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 14:38:26 -0000 Guys, do you have enabled GELI or encrypted partition? On Sun, Dec 7, 2014 at 2:37 PM, Wojciech Puchar wrote: > how to get via svn or other means sources of 10*-STABLE from 18.06.2014? > > to get back to working system. > > > On Sun, 7 Dec 2014, Wojciech Puchar wrote: > >> no crashdump. system does not panic >> so i cannot do this >> >> On Sun, 7 Dec 2014, Alfred Perlstein wrote: >> >>> Can you enable crashdumps please and then send a traceback? >>> >>> >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >>> >>> These two are most helpful: >>> >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain >>> >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html >>> >>> >>> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA512 >>>> >>>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>>> >>>>> The problem. At random moment system I/O stops. If you are running >>>>> top at this moment, there are lots of prosesses stalled in vnread >>>>> or biord. network keeps running, processes that doesn't need I/O >>>>> still runs. >>>>> >>>>> top often reports at least 10MB free memory. >>>>> >>>>> seems like a deadlock. Anyone know that problem. How to trace it >>>>> down? >>>> >>>> Looks like I have same problem sometimes. And you could not run any >>>> new process, you could not login on console, but you could switch >>>> virtual consoles & if "top" is running on one of them, it doesn't hang >>>> itself, right? >>>> >>>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily >>>> damaged. >>>> >>>> - -- // Lev Serebryakov AKA Black Lion >>>> -----BEGIN PGP SIGNATURE----- >>>> Version: GnuPG v2.0.22 (MingW32) >>>> >>>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>>> oeXgB3qxqhPtvfDmUm+X >>>> =R88v >>>> -----END PGP SIGNATURE----- >>>> _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to >>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>> >>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to >>> "freebsd-hackers-unsubscribe@freebsd.org" >>> >>> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 14:43:53 2014 Return-Path: Delivered-To: freebsd-hackers@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 2BBE1B41; Sun, 7 Dec 2014 14:43:53 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BDE90A92; Sun, 7 Dec 2014 14:43:52 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7Ehnig070413; Sun, 7 Dec 2014 15:43:50 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 15:43:45 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Oliver Pinter Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 15:43:50 +0100 (CET) Cc: FreeBSD Hackers , Alfred Perlstein , lev@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 14:43:53 -0000 yes i do use geli. On Sun, 7 Dec 2014, Oliver Pinter wrote: > Guys, do you have enabled GELI or encrypted partition? > > On Sun, Dec 7, 2014 at 2:37 PM, Wojciech Puchar wrote: >> how to get via svn or other means sources of 10*-STABLE from 18.06.2014? >> >> to get back to working system. >> >> >> On Sun, 7 Dec 2014, Wojciech Puchar wrote: >> >>> no crashdump. system does not panic >>> so i cannot do this >>> >>> On Sun, 7 Dec 2014, Alfred Perlstein wrote: >>> >>>> Can you enable crashdumps please and then send a traceback? >>>> >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >>>> >>>> These two are most helpful: >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html >>>> >>>> >>>> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>>>> >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA512 >>>>> >>>>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>>>> >>>>>> The problem. At random moment system I/O stops. If you are running >>>>>> top at this moment, there are lots of prosesses stalled in vnread >>>>>> or biord. network keeps running, processes that doesn't need I/O >>>>>> still runs. >>>>>> >>>>>> top often reports at least 10MB free memory. >>>>>> >>>>>> seems like a deadlock. Anyone know that problem. How to trace it >>>>>> down? >>>>> >>>>> Looks like I have same problem sometimes. And you could not run any >>>>> new process, you could not login on console, but you could switch >>>>> virtual consoles & if "top" is running on one of them, it doesn't hang >>>>> itself, right? >>>>> >>>>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>>>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily >>>>> damaged. >>>>> >>>>> - -- // Lev Serebryakov AKA Black Lion >>>>> -----BEGIN PGP SIGNATURE----- >>>>> Version: GnuPG v2.0.22 (MingW32) >>>>> >>>>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>>>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>>>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>>>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>>>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>>>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>>>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>>>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>>>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>>>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>>>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>>>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>>>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>>>> oeXgB3qxqhPtvfDmUm+X >>>>> =R88v >>>>> -----END PGP SIGNATURE----- >>>>> _______________________________________________ >>>>> freebsd-hackers@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>>> To unsubscribe, send any mail to >>>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>>> >>>> >>>> _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to >>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>> >>>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >>> >>> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 15:49:53 2014 Return-Path: Delivered-To: freebsd-hackers@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 0DDB47DC for ; Sun, 7 Dec 2014 15:49:53 +0000 (UTC) Received: from server1.xenet.de (server1.xenet.de [213.221.94.201]) by mx1.freebsd.org (Postfix) with ESMTP id 92A2EF85 for ; Sun, 7 Dec 2014 15:49:51 +0000 (UTC) Received: from [10.1.0.50] (tubercel-gate.xenet.de [213.221.94.54]) (authenticated bits=0) by server1.xenet.de (8.12.5/8.12.5) with ESMTP id sB7FOv0Y009444 for ; Sun, 7 Dec 2014 16:25:01 +0100 (CET) (envelope-from Meyser@xenet.de) Message-ID: <54847206.8070107@xenet.de> Date: Sun, 07 Dec 2014 16:28:06 +0100 From: Matthias Meyser User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: cross installing freebsd? References: <5483AE21.8090306@freebsd.org> In-Reply-To: <5483AE21.8090306@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.38 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 15:49:53 -0000 Hi all Am 07.12.2014 um 02:32 schrieb Alfred Perlstein: > Hey folks, > > In order to make installation of a new world/kernel on my i386 soekris > a LOT faster/easier I've taken to doing builds on an amd64 host and > then "cross-installing" > > Steps are as follows: > > On amd64 host: > /usr/trees/freebsd.git % env TARGET=i386 make -j8 buildworld && env > TARGET=i386 make -j8 buildkernel > > On i386 host: > mount spigot:/usr/trees /usr/trees > mount spigot:/usr/obj /usr/obj > cd /usr/trees/freebsd.git > # install kernel: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install \ > make installkernel > # install world: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install STRIPBIN=/usr/bin/strip \ > MAKEWHATIS=/usr/bin/makewhatis \ > make installworld Thank you! You are my hero. This bothers me a long time. Even on arm. > Seems to work nicely. > Any objections if I add something like this target as > "cross-installworld" and "cross-installkernel" to top level Makefile? It would be much nicer if the normal install* would handle this automatically. Someone should teach the Makesystem to build the installboottrapbinaries not only for the HOST system but also for the Targetsystem. Then normal install would just work. - Matthias -- Matthias Meyser | XeNET GmbH Tel.: +49-5323-9489050 | 38678 Clausthal-Zellerfeld, Marktstrasse 40 Fax: +49-5323-9489059 | Registergericht: Amtsgericht Braunschweig HRB 110823 Email: Meyser@xenet.de | Geschaeftsfuehrer: Matthias Meyser From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 16:35:53 2014 Return-Path: Delivered-To: freebsd-hackers@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 71D0280A; Sun, 7 Dec 2014 16:35:53 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 3415D6DD; Sun, 7 Dec 2014 16:35:53 +0000 (UTC) Received: from [192.168.135.70] (unknown [94.19.235.70]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 8258E5C003; Sun, 7 Dec 2014 19:35:37 +0300 (MSK) Message-ID: <548481D8.5030604@FreeBSD.org> Date: Sun, 07 Dec 2014 19:35:36 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Alfred Perlstein , Wojciech Puchar , FreeBSD Hackers Subject: Re: 10.1-STABLE one week old from svn - random hangs References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> In-Reply-To: <548448B1.20907@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 16:35:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07.12.2014 15:31, Alfred Perlstein wrote: > Can you enable crashdumps please and then send a traceback? > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > > These two are most helpful: > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain > > > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html > No panic for me :) Also, I'm leaving to vacation right now, so I could not provide any additional info till January. - -- // Lev Serebryakov AKA Black Lion -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJUhIHXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePLBsP/RiomeRDs1RSvYF9JN5WT1H6 hK/d07HzzwhnIG93hHXRT/rB4t3DPUGG7Bm5M/Ckh72OgzEaFdX1pTeR1aFgijJe JlTAVOC7bZOulxutHsogQp4mpZ+rIdOcoy7SYCQuN+89/aIh68DlZwysrChBILOz VvOz22uedTXSndyKy8fYwIih487hLluBnQqW9V87b3S0zWc9xZuV2brYaiAjU9DW 9JxGXpF0pY2firIPbogJNYaC288yVzyTkW4T/rJYrnaedgD2D0QgDz37DVjA36Ou cYNZpCYR56XlViXU7tU5roXiHT92ffrOhlD0v0+ggxzcAi6LAVzAdSsea6qAWQ9F zjrOvoGwXb0U98zk4U4diXh3MSPyx9rFbZ2er0cSzj8pEQOSmm110QnsHxzvx9rg D604d5/c3q6PQr92MFQ79bXrNJRqSdPAf6OL1c8c5vafw1HB72qgXm7sHjG5Cu3C VlmHvoBxE6ZofmewbRTai8Aln2Uvmy1fQgTVrPl4NwFCxaJfkPREnSxiz3NGIRM0 gR3e9ayYcqU7x3rSpeqZvU7JFiekHb4YavJ22TVYaK+GFPNOgNdMoWpqatZcD6iz RtCp3j2Fdiy0I0wVwYd/EJjiYvv+SjXN2wR12DjZOvPWdAOGh2oiNcrggjonpqvo MtHbUm1/ElwBo12ZHgDm =KQbr -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 16:36:13 2014 Return-Path: Delivered-To: freebsd-hackers@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 572E78E9; Sun, 7 Dec 2014 16:36:13 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 158BA6E4; Sun, 7 Dec 2014 16:36:13 +0000 (UTC) Received: from [192.168.135.70] (unknown [94.19.235.70]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 2E0E85C004; Sun, 7 Dec 2014 19:36:12 +0300 (MSK) Message-ID: <548481FB.9010400@FreeBSD.org> Date: Sun, 07 Dec 2014 19:36:11 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Oliver Pinter , Wojciech Puchar Subject: Re: 10.1-STABLE one week old from svn - random hangs References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , Alfred Perlstein X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 16:36:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07.12.2014 17:11, Oliver Pinter wrote: > Guys, do you have enabled GELI or encrypted partition? I don't. - -- // Lev Serebryakov AKA Black Lion -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQJ8BAEBCgBmBQJUhIH7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePHoYQAJfgrCj2vsqkIbbU4XHeeVbt cCelblUGGvnlRDPhPo5D7JJxh9oP5YgT3exnZdjBiVVQcNRm8YMYCdliDe0xPIb1 id39jMq2KNYgtp+jQ16bfwc5exaBxuXEsxMwNJnjCLh2jq1VQpv7IMC1WXMhmr71 hfdQf3B7sG5qqykA7CrRGItHTxuSwexN63PdHBsfkaroE4B1kDLgNaq695XUqAf7 E0kDtztnE7nW0OioDKKFAL9a56dhDSNiaF/yjatQfZpU5+vG4fZ2IwVuO4jXN9pf JQP/6bOGj3S+JOVyx/24cVqlbIq/IvrH/7RNgJozGhSXqAkeOE6WDH5Y4xMkc1YL c3/e+bPusSwCngSs5oqqyl5wUUlNwWatOOgthefbbrj1hxgGXFFLyYjjG13Fp3kt bHWFbmYZvLB5V4JYHcqeoqVU67E1PfDr4XH8FPJPDfOcHJRFtftkhuKnGBHofVTr ElTLcCx554j1dkcfRt4PLB3+XutMzDWlCjGIlikg4BFhCAGdv391cU1IH9HvBzS5 LbK77oNN/Q8V9WU6MUHISaG3Yufsr7E8DDrIYtky9xu0FIFQAc2lOpiSK1qwhfzE IF1kSiyKLNZ8vJq/CrQU4f5ge1b62Ip3KWSDhmVG4HkYeKfXlGzwbYLQKPZO6UpO BiCuUSwOrv/mr3EjjT5K =2CqF -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 17:36:52 2014 Return-Path: Delivered-To: freebsd-hackers@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 78115504 for ; Sun, 7 Dec 2014 17:36:52 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 66A17C59 for ; Sun, 7 Dec 2014 17:36:52 +0000 (UTC) Received: from [10.0.1.20] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id D1681341F84E; Sun, 7 Dec 2014 09:36:51 -0800 (PST) Subject: Re: cross installing freebsd? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Alfred Perlstein In-Reply-To: <54847206.8070107@xenet.de> Date: Sun, 7 Dec 2014 09:36:50 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <73D1FFAD-4E79-4561-B383-5D1F794C4688@mu.org> References: <5483AE21.8090306@freebsd.org> <54847206.8070107@xenet.de> To: Matthias Meyser X-Mailer: Apple Mail (2.1283) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 17:36:52 -0000 On Dec 7, 2014, at 7:28 AM, Matthias Meyser wrote: > Hi all >=20 > Am 07.12.2014 um 02:32 schrieb Alfred Perlstein: >> Hey folks, >>=20 >> In order to make installation of a new world/kernel on my i386 = soekris a LOT faster/easier I've taken to doing builds on an amd64 host = and then "cross-installing" >>=20 >> Steps are as follows: >>=20 >> On amd64 host: >> /usr/trees/freebsd.git % env TARGET=3Di386 make -j8 buildworld && env = TARGET=3Di386 make -j8 buildkernel >>=20 >> On i386 host: >> mount spigot:/usr/trees /usr/trees >> mount spigot:/usr/obj /usr/obj >> cd /usr/trees/freebsd.git >> # install kernel: >> env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ >> INSTALL=3D/usr/bin/install \ >> make installkernel >> # install world: >> env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ >> INSTALL=3D/usr/bin/install STRIPBIN=3D/usr/bin/strip \ >> MAKEWHATIS=3D/usr/bin/makewhatis \ >> make installworld > Thank you! You are my hero. > This bothers me a long time. Even on arm. >=20 >=20 >> Seems to work nicely. >> Any objections if I add something like this target as = "cross-installworld" and "cross-installkernel" to top level Makefile? >=20 > It would be much nicer if the normal install* would handle this = automatically. > Someone should teach the Makesystem to build the = installboottrapbinaries > not only for the HOST system but also for the Targetsystem. >=20 > Then normal install would just work. I wish I had time to do that, but I really do not have time to sort how = to determine that reliably, also people have been pretty upset if = anything in the build changes lately and anything breaks. So I am very = afraid to touch any defaults. Due to time and the pressure to not break anything I can do one of two = things: 1) clean up the two targets I've submitted and put them in a = Makefile.cross-install, then document them in the main Makefile. 2) Keep this code in my own repo. Sorry. Let me know if there is a way forward with 1 for the time being? -Alfred >=20 >=20 >=20 > - Matthias >=20 > --=20 > Matthias Meyser | XeNET GmbH > Tel.: +49-5323-9489050 | 38678 Clausthal-Zellerfeld, Marktstrasse = 40 > Fax: +49-5323-9489059 | Registergericht: Amtsgericht Braunschweig = HRB 110823 > Email: Meyser@xenet.de | Geschaeftsfuehrer: Matthias Meyser >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 19:26:57 2014 Return-Path: Delivered-To: freebsd-hackers@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 4C9F2DC9; Sun, 7 Dec 2014 19:26:57 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9580394E; Sun, 7 Dec 2014 19:26:56 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7JQpdL081752; Sun, 7 Dec 2014 20:26:51 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 20:26:47 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Lev Serebryakov Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: <548481FB.9010400@FreeBSD.org> Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> <548481FB.9010400@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 20:26:52 +0100 (CET) Cc: FreeBSD Hackers , Alfred Perlstein , Oliver Pinter X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 19:26:57 -0000 just tried to svn checkout 10-stable from 2014.06.06 (that last that worked without hangs). while doing this on my laptop it rebooted hard, no crashdump, no messages On Sun, 7 Dec 2014, Lev Serebryakov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 07.12.2014 17:11, Oliver Pinter wrote: > >> Guys, do you have enabled GELI or encrypted partition? > I don't. > > - -- > // Lev Serebryakov AKA Black Lion > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQJ8BAEBCgBmBQJUhIH7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF > QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePHoYQAJfgrCj2vsqkIbbU4XHeeVbt > cCelblUGGvnlRDPhPo5D7JJxh9oP5YgT3exnZdjBiVVQcNRm8YMYCdliDe0xPIb1 > id39jMq2KNYgtp+jQ16bfwc5exaBxuXEsxMwNJnjCLh2jq1VQpv7IMC1WXMhmr71 > hfdQf3B7sG5qqykA7CrRGItHTxuSwexN63PdHBsfkaroE4B1kDLgNaq695XUqAf7 > E0kDtztnE7nW0OioDKKFAL9a56dhDSNiaF/yjatQfZpU5+vG4fZ2IwVuO4jXN9pf > JQP/6bOGj3S+JOVyx/24cVqlbIq/IvrH/7RNgJozGhSXqAkeOE6WDH5Y4xMkc1YL > c3/e+bPusSwCngSs5oqqyl5wUUlNwWatOOgthefbbrj1hxgGXFFLyYjjG13Fp3kt > bHWFbmYZvLB5V4JYHcqeoqVU67E1PfDr4XH8FPJPDfOcHJRFtftkhuKnGBHofVTr > ElTLcCx554j1dkcfRt4PLB3+XutMzDWlCjGIlikg4BFhCAGdv391cU1IH9HvBzS5 > LbK77oNN/Q8V9WU6MUHISaG3Yufsr7E8DDrIYtky9xu0FIFQAc2lOpiSK1qwhfzE > IF1kSiyKLNZ8vJq/CrQU4f5ge1b62Ip3KWSDhmVG4HkYeKfXlGzwbYLQKPZO6UpO > BiCuUSwOrv/mr3EjjT5K > =2CqF > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 20:21:57 2014 Return-Path: Delivered-To: freebsd-hackers@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 5BAA3702 for ; Sun, 7 Dec 2014 20:21:57 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EDB65E7B for ; Sun, 7 Dec 2014 20:21:56 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7KLrXp085400 for ; Sun, 7 Dec 2014 21:21:54 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 21:21:49 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: FreeBSD Hackers Subject: freebsd crash under I/O - got error messages Message-ID: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 21:21:54 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 20:21:57 -0000 after enabling debug, WITNESS, INVARIANTS, DIAGNOSTICS etc. just after virtualbox starting VM with windows XP, i've got what to do next to trace down a problem? Dec 7 21:15:26 laptop kernel: vboxdrv: fAsync=0 offMin=0x356 offMax=0xe62 Dec 7 21:15:41 laptop kernel: lock order reversal: Dec 7 21:15:41 laptop kernel: 1st 0xfffff800603305f0 ufs (ufs) @ kern/vfs_syscalls.c:3459 Dec 7 21:15:41 laptop kernel: 2nd 0xfffffe0060df5ad0 bufwait (bufwait) @ ufs/ffs/ffs_vnops.c:262 Dec 7 21:15:41 laptop kernel: 3rd 0xfffff8006037dd50 ufs (ufs) @ kern/vfs_subr.c:2137 Dec 7 21:15:41 laptop kernel: KDB: stack backtrace: Dec 7 21:15:41 laptop kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00787923e0 Dec 7 21:15:41 laptop kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0078792490 Dec 7 21:15:41 laptop kernel: witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe0078792520 Dec 7 21:15:41 laptop kernel: __lockmgr_args() at __lockmgr_args+0x9ea/frame 0xfffffe0078792660 Dec 7 21:15:41 laptop kernel: ffs_lock() at ffs_lock+0x84/frame 0xfffffe00787926b0 Dec 7 21:15:41 laptop kernel: VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfffffe00787926e0 Dec 7 21:15:41 laptop kernel: _vn_lock() at _vn_lock+0xaa/frame 0xfffffe0078792750 Dec 7 21:15:41 laptop kernel: vget() at vget+0x67/frame 0xfffffe0078792790 Dec 7 21:15:41 laptop kernel: vfs_hash_get() at vfs_hash_get+0xe1/frame 0xfffffe00787927e0 Dec 7 21:15:41 laptop kernel: ffs_vgetf() at ffs_vgetf+0x40/frame 0xfffffe0078792870 Dec 7 21:15:41 laptop kernel: softdep_sync_buf() at softdep_sync_buf+0xac0/frame 0xfffffe0078792950 Dec 7 21:15:41 laptop kernel: ffs_syncvnode() at ffs_syncvnode+0x286/frame 0xfffffe00787929d0 Dec 7 21:15:41 laptop kernel: ffs_fsync() at ffs_fsync+0x20/frame 0xfffffe0078792a00 Dec 7 21:15:41 laptop kernel: VOP_FSYNC_APV() at VOP_FSYNC_APV+0xd1/frame 0xfffffe0078792a30 Dec 7 21:15:41 laptop kernel: sys_fsync() at sys_fsync+0x144/frame 0xfffffe0078792aa0 Dec 7 21:15:41 laptop kernel: amd64_syscall() at amd64_syscall+0x216/frame 0xfffffe0078792bb0 Dec 7 21:15:41 laptop kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0078792bb0 Dec 7 21:15:41 laptop kernel: --- syscall (95, FreeBSD ELF64, sys_fsync), rip = 0x80128e66a, rsp = 0x7fffffffb4d8, rbp = 0x7fffffffb4f0 --- Dec 7 21:16:30 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207473672192, length=262144)]error = 11 Dec 7 21:16:31 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207474262016, length=950272)]error = 11 Dec 7 21:16:32 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207475507200, length=65536)]error = 11 Dec 7 21:16:33 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207475671040, length=98304)]error = 11 Dec 7 21:16:34 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207709601792, length=32768)]error = 11 Dec 7 21:16:35 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207709667328, length=98304)]error = 11 Dec 7 21:16:36 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207709798400, length=65536)]error = 11 Dec 7 21:16:37 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207709962240, length=32768)]error = 11 Dec 7 21:16:38 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207710650368, length=32768)]error = 11 Dec 7 21:16:39 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207714942976, length=32768)]error = 11 Dec 7 21:16:40 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715041280, length=32768)]error = 11 Dec 7 21:16:41 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715106816, length=32768)]error = 11 Dec 7 21:16:42 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715237888, length=32768)]error = 11 Dec 7 21:16:43 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715467264, length=65536)]error = 11 Dec 7 21:16:44 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715565568, length=131072)]error = 11 Dec 7 21:16:45 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715729408, length=65536)]error = 11 Dec 7 21:16:46 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715827712, length=98304)]error = 11 Dec 7 21:16:47 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207715958784, length=65536)]error = 11 Dec 7 21:16:48 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207716188160, length=65536)]error = 11 Dec 7 21:16:49 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207716548608, length=65536)]error = 11 Dec 7 21:16:50 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207719825408, length=32768)]error = 11 Dec 7 21:16:51 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207719989248, length=65536)]error = 11 Dec 7 21:16:52 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207720087552, length=131072)]error = 11 Dec 7 21:16:53 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207720775680, length=131072)]error = 11 Dec 7 21:16:54 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207720939520, length=32768)]error = 11 Dec 7 21:16:55 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207721005056, length=393216)]error = 11 Dec 7 21:16:56 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207721463808, length=163840)]error = 11 Dec 7 21:16:57 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207721758720, length=65536)]error = 11 Dec 7 21:16:58 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207721857024, length=98304)]error = 11 Dec 7 21:16:59 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207722184704, length=32768)]error = 11 Dec 7 21:17:00 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207722512384, length=32768)]error = 11 Dec 7 21:17:01 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723167744, length=65536)]error = 11 Dec 7 21:17:02 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723266048, length=32768)]error = 11 Dec 7 21:17:03 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723364352, length=65536)]error = 11 Dec 7 21:17:04 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723495424, length=131072)]error = 11 Dec 7 21:17:05 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723659264, length=32768)]error = 11 Dec 7 21:17:06 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207723921408, length=32768)]error = 11 Dec 7 21:17:07 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208111108096, length=32768)]error = 11 Dec 7 21:17:08 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208111206400, length=32768)]error = 11 Dec 7 21:17:09 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208111271936, length=32768)]error = 11 Dec 7 21:17:10 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208223830016, length=32768)]error = 11 Dec 7 21:17:11 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208233758720, length=32768)]error = 11 Dec 7 21:17:12 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208233824256, length=98304)]error = 11 Dec 7 21:17:13 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208234250240, length=65536)]error = 11 Dec 7 21:17:14 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208234545152, length=65536)]error = 11 Dec 7 21:17:15 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=231380746240, length=32768)]error = 11 Dec 7 21:17:16 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=231366688768, length=32768)]error = 11 Dec 7 21:17:17 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=231368425472, length=32768)]error = 11 Dec 7 21:17:18 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=262973521920, length=32768)]error = 11 Dec 7 21:17:19 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=233904668672, length=32768)]error = 11 Dec 7 21:17:20 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=233911713792, length=32768)]error = 11 Dec 7 21:17:21 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=233914073088, length=32768)]error = 11 Dec 7 21:17:22 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=233946447872, length=32768)]error = 11 Dec 7 21:17:23 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=234820861952, length=32768)]error = 11 Dec 7 21:17:24 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=234776231936, length=32768)]error = 11 Dec 7 21:17:25 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=235616010240, length=32768)]error = 11 Dec 7 21:17:26 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=235633606656, length=32768)]error = 11 Dec 7 21:17:27 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207441526784, length=65536)]error = 11 Dec 7 21:17:28 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=285122953216, length=32768)]error = 11 Dec 7 21:17:29 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=280897093632, length=32768)]error = 11 Dec 7 21:17:30 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=199790362624, length=4096)]error = 11 Dec 7 21:17:31 laptop kernel: g_vfs_done():ada0d.eli[READ(offset=269781565440, length=32768)]error = 11 Dec 7 21:17:32 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=270651752448, length=32768)]error = 11 Dec 7 21:17:33 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=270652309504, length=32768)]error = 11 Dec 7 21:17:34 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207724150784, length=32768)]error = 11 Dec 7 21:17:35 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=207725461504, length=393216)]error = 11 Dec 7 21:17:36 laptop kernel: g_vfs_done():ada0d.eli[WRITE(offset=208111370240, length=393216)]error = 11 Dec 7 21:17:37 laptop kernel: g_vfs_done():ada0d.eli[READ(offset=228004618240, length=49152)]error = 11 Dec 7 21:17:37 laptop kernel: vnode_pager_getpages: I/O read error Dec 7 21:17:37 laptop kernel: vm_fault: pager read error, pid 673 (VirtualBox) From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 20:24:41 2014 Return-Path: Delivered-To: freebsd-hackers@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 4FB7E801 for ; Sun, 7 Dec 2014 20:24:41 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D4C75E95 for ; Sun, 7 Dec 2014 20:24:40 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7KOa3v085679 for ; Sun, 7 Dec 2014 21:24:37 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 21:24:33 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: FreeBSD Hackers Subject: freebsd crash under I/O - got error messages part 2 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 21:24:37 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 20:24:41 -0000 after rebooting, without even loading vboxdrv.ko, quickly after running svnlite checkout Dec 7 21:23:21 laptop kernel: lock order reversal: Dec 7 21:23:21 laptop kernel: 1st 0xfffffe0060f7fdd8 bufwait (bufwait) @ kern/vfs_bio.c:3061 Dec 7 21:23:21 laptop kernel: 2nd 0xfffff8001a555600 dirhash (dirhash) @ ufs/ufs/ufs_dirhash.c:284 Dec 7 21:23:21 laptop kernel: KDB: stack backtrace: Dec 7 21:23:21 laptop kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0078702440 Dec 7 21:23:21 laptop kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00787024f0 Dec 7 21:23:21 laptop kernel: witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe0078702580 Dec 7 21:23:21 laptop kernel: _sx_xlock() at _sx_xlock+0x71/frame 0xfffffe00787025c0 Dec 7 21:23:21 laptop kernel: ufsdirhash_add() at ufsdirhash_add+0x3a/frame 0xfffffe0078702600 Dec 7 21:23:21 laptop kernel: ufs_direnter() at ufs_direnter+0x6b3/frame 0xfffffe00787026c0 Dec 7 21:23:21 laptop kernel: ufs_mkdir() at ufs_mkdir+0x4d0/frame 0xfffffe0078702850 Dec 7 21:23:21 laptop kernel: VOP_MKDIR_APV() at VOP_MKDIR_APV+0xd1/frame 0xfffffe0078702880 Dec 7 21:23:21 laptop kernel: kern_mkdirat() at kern_mkdirat+0x1be/frame 0xfffffe0078702aa0 Dec 7 21:23:21 laptop kernel: amd64_syscall() at amd64_syscall+0x216/frame 0xfffffe0078702bb0 Dec 7 21:23:21 laptop kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0078702bb0 Dec 7 21:23:21 laptop kernel: --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x801d4e93a, rsp = 0x7fffffffde68, rbp = 0x7fffffffde8 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 20:37:19 2014 Return-Path: Delivered-To: freebsd-hackers@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 67005AC9 for ; Sun, 7 Dec 2014 20:37:19 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E72D4F85 for ; Sun, 7 Dec 2014 20:37:18 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7KbFLH086634 for ; Sun, 7 Dec 2014 21:37:15 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 21:37:12 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: FreeBSD Hackers Subject: freebsd crash under I/O - got error messages part 3 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 21:37:15 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 20:37:19 -0000 after disabling UFS_DIRHASH in kernel config the following disappers but error generated by virtualbox is still active. On Sun, 7 Dec 2014, Wojciech Puchar wrote: > after rebooting, without even loading vboxdrv.ko, quickly after running > svnlite checkout > > Dec 7 21:23:21 laptop kernel: lock order reversal: > Dec 7 21:23:21 laptop kernel: 1st 0xfffffe0060f7fdd8 bufwait (bufwait) @ > kern/vfs_bio.c:3061 > Dec 7 21:23:21 laptop kernel: 2nd 0xfffff8001a555600 dirhash (dirhash) @ > ufs/ufs/ufs_dirhash.c:284 > Dec 7 21:23:21 laptop kernel: KDB: stack backtrace: > Dec 7 21:23:21 laptop kernel: db_trace_self_wrapper() at > db_trace_self_wrapper+0x2b/frame 0xfffffe0078702440 > Dec 7 21:23:21 laptop kernel: kdb_backtrace() at kdb_backtrace+0x39/frame > 0xfffffe00787024f0 > Dec 7 21:23:21 laptop kernel: witness_checkorder() at > witness_checkorder+0xdc2/frame 0xfffffe0078702580 > Dec 7 21:23:21 laptop kernel: _sx_xlock() at _sx_xlock+0x71/frame > 0xfffffe00787025c0 > Dec 7 21:23:21 laptop kernel: ufsdirhash_add() at ufsdirhash_add+0x3a/frame > 0xfffffe0078702600 > Dec 7 21:23:21 laptop kernel: ufs_direnter() at ufs_direnter+0x6b3/frame > 0xfffffe00787026c0 > Dec 7 21:23:21 laptop kernel: ufs_mkdir() at ufs_mkdir+0x4d0/frame > 0xfffffe0078702850 > Dec 7 21:23:21 laptop kernel: VOP_MKDIR_APV() at VOP_MKDIR_APV+0xd1/frame > 0xfffffe0078702880 > Dec 7 21:23:21 laptop kernel: kern_mkdirat() at kern_mkdirat+0x1be/frame > 0xfffffe0078702aa0 > Dec 7 21:23:21 laptop kernel: amd64_syscall() at amd64_syscall+0x216/frame > 0xfffffe0078702bb0 > Dec 7 21:23:21 laptop kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame > 0xfffffe0078702bb0 > Dec 7 21:23:21 laptop kernel: --- syscall (136, FreeBSD ELF64, sys_mkdir), > rip = 0x801d4e93a, rsp = 0x7fffffffde68, rbp = 0x7fffffffde8 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 20:57:31 2014 Return-Path: Delivered-To: freebsd-hackers@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 AD2C7D35 for ; Sun, 7 Dec 2014 20:57:31 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A2F2176 for ; Sun, 7 Dec 2014 20:57:31 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7KvSf9088141 for ; Sun, 7 Dec 2014 21:57:28 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 21:57:25 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: FreeBSD Hackers Subject: Re: freebsd crash under I/O - got error messages part 4 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 21:57:29 +0100 (CET) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 20:57:31 -0000 even without UFS_DIRHASH there are still errors under heavier I/O load. lock order reversal: 1st 0xfffff800182c9068 ufs (ufs) @ kern/vfs_subr.c:2137 2nd 0xfffffe00612443d0 bufwait (bufwait) @ ufs/ffs/ffs_vnops.c:262 3rd 0xfffff8004a877418 ufs (ufs) @ kern/vfs_subr.c:2137 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe007870ae20 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe007870aed0 witness_checkorder() at witness_checkorder+0xdc2/frame 0xfffffe007870af60 __lockmgr_args() at __lockmgr_args+0x9ea/frame 0xfffffe007870b0a0 ffs_lock() at ffs_lock+0x84/frame 0xfffffe007870b0f0 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfffffe007870b120 _vn_lock() at _vn_lock+0xaa/frame 0xfffffe007870b190 vget() at vget+0x67/frame 0xfffffe007870b1d0 vfs_hash_get() at vfs_hash_get+0xe1/frame 0xfffffe007870b220 ffs_vgetf() at ffs_vgetf+0x40/frame 0xfffffe007870b2b0 softdep_sync_buf() at softdep_sync_buf+0x3b3/frame 0xfffffe007870b390 ffs_syncvnode() at ffs_syncvnode+0x286/frame 0xfffffe007870b410 ffs_truncate() at ffs_truncate+0x614/frame 0xfffffe007870b600 ufs_direnter() at ufs_direnter+0x722/frame 0xfffffe007870b6c0 ufs_mkdir() at ufs_mkdir+0x4d0/frame 0xfffffe007870b850 VOP_MKDIR_APV() at VOP_MKDIR_APV+0xd1/frame 0xfffffe007870b880 kern_mkdirat() at kern_mkdirat+0x1be/frame 0xfffffe007870baa0 amd64_syscall() at amd64_syscall+0x216/frame 0xfffffe007870bbb0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe007870bbb0 --- syscall (136, FreeBSD ELF64, sys_mkdir), rip = 0x800c0e93a, rsp = 0x7fffffffd3f8, rbp = 0x7fffffffd520 --- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 22:43:34 2014 Return-Path: Delivered-To: freebsd-hackers@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 760C221A; Sun, 7 Dec 2014 22:43:34 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 62054DC1; Sun, 7 Dec 2014 22:43:34 +0000 (UTC) Received: from [100.89.165.221] (220.sub-70-197-14.myvzw.com [70.197.14.220]) by elvis.mu.org (Postfix) with ESMTPSA id BC7FA341F87B; Sun, 7 Dec 2014 14:43:33 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 10.1-STABLE one week old from svn - random hangs From: Alfred Perlstein X-Mailer: iPhone Mail (12B436) In-Reply-To: Date: Sun, 7 Dec 2014 14:43:31 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> To: Wojciech Puchar Cc: FreeBSD Hackers , Alfred Perlstein , "lev@FreeBSD.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 22:43:34 -0000 > On Dec 7, 2014, at 5:25 AM, Wojciech Puchar wrote: >=20 > no crashdump. system does not panic > so i cannot do this That is actually better as you can run ddb scripts or if you what you can fo= rce a crash.=20 Do sysctl -a |grep panic Then set the sysctl node to panic.=20 >=20 >> On Sun, 7 Dec 2014, Alfred Perlstein wrote: >>=20 >> Can you enable crashdumps please and then send a traceback? >>=20 >>=20 >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html= >>=20 >> These two are most helpful: >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html= #kerneldebug-obtain >> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.= html >>=20 >>=20 >>> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>>> The problem. At random moment system I/O stops. If you are running >>>> top at this moment, there are lots of prosesses stalled in vnread >>>> or biord. network keeps running, processes that doesn't need I/O >>>> still runs. >>>> top often reports at least 10MB free memory. >>>> seems like a deadlock. Anyone know that problem. How to trace it >>>> down? >>> Looks like I have same problem sometimes. And you could not run any >>> new process, you could not login on console, but you could switch >>> virtual consoles & if "top" is running on one of them, it doesn't hang >>> itself, right? >>>=20 >>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged= . >>> - -- // Lev Serebryakov AKA Black Lion >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.22 (MingW32) >>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>> oeXgB3qxqhPtvfDmUm+X >>> =3DR88v >>> -----END PGP SIGNATURE----- >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g" >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >=20 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 04:35:04 2014 Return-Path: Delivered-To: freebsd-hackers@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 09994C19; Mon, 8 Dec 2014 04:35:04 +0000 (UTC) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7281100; Mon, 8 Dec 2014 04:35:03 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id v10so4392110pde.12 for ; Sun, 07 Dec 2014 20:35:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=Isj+dHQyCiA7fwR1g7HygDTN/JiuScE8m+92EWcFIxU=; b=GzA/A0HAoeXjECQGcULOc9jM7AF24yO9phFmDQHH9P00w9OucV9sawnL7MTvM/6ct0 wzkoZ+z/brLTn6sJqu9PPRyP6/ib28JEHgYzFJvfKbl0uD6EgVw1Ix3KT5wh0wPopmDf wmZ+TP2FWbOvdpQ20mqex6/r8RFu7WPe8Vg3oTwSq76gX0G3zFvvqTAuvCbXdqyxBwZa EMk323+dLPge2Yb7lKR3DugykIU886HXuShh2RCVpfVyxv5aIjsblrYOiyL4DDBE0atR Ur8MXtxtka0QERmlLDdezj1ACrPHNQbQPOMhx4K9JamkcfjmSSY8RFYy40sgHqwuuiqe E3ig== X-Received: by 10.69.16.69 with SMTP id fu5mr57224293pbd.159.1418013303109; Sun, 07 Dec 2014 20:35:03 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:f855:3c8d:38d3:b94b? ([2601:8:ab80:7d6:f855:3c8d:38d3:b94b]) by mx.google.com with ESMTPSA id qd2sm19225016pdb.0.2014.12.07.20.35.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 07 Dec 2014 20:35:02 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_B907E66C-64C4-4F6D-B2F9-AC94CE64169D"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: cross installing freebsd? From: Garrett Cooper In-Reply-To: <5483AE21.8090306@freebsd.org> Date: Sun, 7 Dec 2014 20:35:01 -0800 Message-Id: References: <5483AE21.8090306@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 04:35:04 -0000 --Apple-Mail=_B907E66C-64C4-4F6D-B2F9-AC94CE64169D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 6, 2014, at 17:32, Alfred Perlstein wrote: > Hey folks, >=20 > In order to make installation of a new world/kernel on my i386 soekris = a LOT faster/easier I've taken to doing builds on an amd64 host and then = "cross-installing" >=20 > Steps are as follows: >=20 > On amd64 host: > /usr/trees/freebsd.git % env TARGET=3Di386 make -j8 buildworld && env = TARGET=3Di386 make -j8 buildkernel >=20 > On i386 host: > mount spigot:/usr/trees /usr/trees > mount spigot:/usr/obj /usr/obj > cd /usr/trees/freebsd.git > # install kernel: > env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ > INSTALL=3D/usr/bin/install \ > make installkernel > # install world: > env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ > INSTALL=3D/usr/bin/install STRIPBIN=3D/usr/bin/strip \ > MAKEWHATIS=3D/usr/bin/makewhatis \ > make installworld >=20 > Seems to work nicely. >=20 > Any objections if I add something like this target as = "cross-installworld" and "cross-installkernel" to top level Makefile? Hi Alfred, Reading your examples... 1. I=92m wondering if we should formalize CROSS_BUILD_TESTING in = Makefile.inc1: 188 .if ${MACHINE} =3D=3D ${TARGET} && ${MACHINE_ARCH} =3D=3D = ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING) 189 OBJTREE=3D ${MAKEOBJDIRPREFIX} 190 .else 191 OBJTREE=3D ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH} 192 .endif 2. MAKEWHATIS seems like it should be added to ITOOLS. Do you = agree? 3. Seems like strip should be added to ITOOLS if = CROSS_BUILD_TESTING is defined (or at the very least LOCAL_ITOOLS). 4. Why did you need to explicitly define the path to INSTALL? Thanks! --Apple-Mail=_B907E66C-64C4-4F6D-B2F9-AC94CE64169D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhSp1AAoJEMZr5QU6S73ekdYH/3DFuLOzZTm9ewc9/512iB6F BCPYoM9Q3bO/59qaN92PBUsSToq+EZVIJSA8F+6mTL+NYt8uWmUyuyYpCZHU1m5/ TuiBSiVU1w+IWmvh6M7Ufp7pnkbnjn3skVp53mV1k+Iv0gWYREtXS8JX3+aKUDF3 PBJeQ0c6jTh3UetxWeDuetwX/TTZ15X7Cgu8xrv/E9CHoDJI1U6itpRoa5pvzlv1 tLWN4Yq4CrFuKYhcO4oxROeCbBxHQUtOIrvZTv6vRhp+bg872KVNhOrvDyzyTTZ0 cAod70Ddxu+70XU6yRF5N3hipdA79VCw4wegR1FG4IGTKubhE38iOkfDCLJsJjE= =HLld -----END PGP SIGNATURE----- --Apple-Mail=_B907E66C-64C4-4F6D-B2F9-AC94CE64169D-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 05:48:54 2014 Return-Path: Delivered-To: freebsd-hackers@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 AFF756EA for ; Mon, 8 Dec 2014 05:48:54 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 9DAB19B4 for ; Mon, 8 Dec 2014 05:48:54 +0000 (UTC) Received: from [10.0.1.20] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 63133341F850; Sun, 7 Dec 2014 21:48:54 -0800 (PST) Subject: Re: cross installing freebsd? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Alfred Perlstein In-Reply-To: Date: Sun, 7 Dec 2014 21:48:53 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> References: <5483AE21.8090306@freebsd.org> To: Garrett Cooper X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 05:48:54 -0000 On Dec 7, 2014, at 8:35 PM, Garrett Cooper wrote: > On Dec 6, 2014, at 17:32, Alfred Perlstein wrote: >=20 >> Hey folks, >>=20 >> In order to make installation of a new world/kernel on my i386 = soekris a LOT faster/easier I've taken to doing builds on an amd64 host = and then "cross-installing" >>=20 >> Steps are as follows: >>=20 >> On amd64 host: >> /usr/trees/freebsd.git % env TARGET=3Di386 make -j8 buildworld && env = TARGET=3Di386 make -j8 buildkernel >>=20 >> On i386 host: >> mount spigot:/usr/trees /usr/trees >> mount spigot:/usr/obj /usr/obj >> cd /usr/trees/freebsd.git >> # install kernel: >> env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ >> INSTALL=3D/usr/bin/install \ >> make installkernel >> # install world: >> env MAKEOBJDIRPREFIX=3D/usr/obj/i386.i386 CC=3D/usr/bin/cc \ >> INSTALL=3D/usr/bin/install STRIPBIN=3D/usr/bin/strip \ >> MAKEWHATIS=3D/usr/bin/makewhatis \ >> make installworld >>=20 >> Seems to work nicely. >>=20 >> Any objections if I add something like this target as = "cross-installworld" and "cross-installkernel" to top level Makefile? >=20 > Hi Alfred, > Reading your examples... > 1. I=92m wondering if we should formalize CROSS_BUILD_TESTING in = Makefile.inc1: >=20 > 188 .if ${MACHINE} =3D=3D ${TARGET} && ${MACHINE_ARCH} =3D=3D = ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING) > 189 OBJTREE=3D ${MAKEOBJDIRPREFIX} > 190 .else > 191 OBJTREE=3D ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH} > 192 .endif >=20 > 2. MAKEWHATIS seems like it should be added to ITOOLS. Do you = agree? > 3. Seems like strip should be added to ITOOLS if = CROSS_BUILD_TESTING is defined (or at the very least LOCAL_ITOOLS). > 4. Why did you need to explicitly define the path to INSTALL? > Thanks! To be honest I have a gist as to what you're saying but I think the = build is suffering from shibboleth-itis. Meaning it's not serviceable = unless you're intimately familiar with it=85 I *guess* that ITOOLS or maybe LOCAL_ITOOLS means programs needed to = installworld/installkernel? If so, then yes, makewhatis needs to be added to that. As far as everything else written: no idea what "CROSS_BUILD_TESTING" means, it's not documented anywhere I = can see in the makefile. I can't decode if there will be a target that "just works" for doing a = cross-install, will there be? What will it be named and how will people = invoke it? Can we have cross-installworld and cross-installkernel targets please? -Alfred= From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 07:38:18 2014 Return-Path: Delivered-To: freebsd-hackers@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 5431E101; Mon, 8 Dec 2014 07:38:18 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E7F1479A; Mon, 8 Dec 2014 07:38:17 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB87cBcd034577; Mon, 8 Dec 2014 08:38:12 +0100 (CET) (envelope-from wojtek@puchar.net) X-Authentication-Warning: puchar.net: Host laptop.wojtek.intra [10.1.0.2] claimed to be [10.1.0.2] Date: Mon, 8 Dec 2014 08:38:08 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Alfred Perlstein Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Mon, 08 Dec 2014 08:38:13 +0100 (CET) Cc: FreeBSD Hackers , Alfred Perlstein , "lev@FreeBSD.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 07:38:18 -0000 already sent you kernel messages with debugging diags etc. enabled. lots of them and crashes easily repeatable. got back to 10-STABLE from 2014.06.06 + manually applied patched from security advisories after. NONE of errors happens, no crashes so far. On Sun, 7 Dec 2014, Alfred Perlstein wrote: > > >> On Dec 7, 2014, at 5:25 AM, Wojciech Puchar wrote: >> >> no crashdump. system does not panic >> so i cannot do this > > That is actually better as you can run ddb scripts or if you what you can force a crash. > > Do sysctl -a |grep panic > > > Then set the sysctl node to panic. > > >> >>> On Sun, 7 Dec 2014, Alfred Perlstein wrote: >>> >>> Can you enable crashdumps please and then send a traceback? >>> >>> >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >>> >>> These two are most helpful: >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain >>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html >>> >>> >>>> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA512 >>>>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>>>> The problem. At random moment system I/O stops. If you are running >>>>> top at this moment, there are lots of prosesses stalled in vnread >>>>> or biord. network keeps running, processes that doesn't need I/O >>>>> still runs. >>>>> top often reports at least 10MB free memory. >>>>> seems like a deadlock. Anyone know that problem. How to trace it >>>>> down? >>>> Looks like I have same problem sometimes. And you could not run any >>>> new process, you could not login on console, but you could switch >>>> virtual consoles & if "top" is running on one of them, it doesn't hang >>>> itself, right? >>>> >>>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily damaged. >>>> - -- // Lev Serebryakov AKA Black Lion >>>> -----BEGIN PGP SIGNATURE----- >>>> Version: GnuPG v2.0.22 (MingW32) >>>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>>> oeXgB3qxqhPtvfDmUm+X >>>> =R88v >>>> -----END PGP SIGNATURE----- >>>> _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 10:04:09 2014 Return-Path: Delivered-To: freebsd-hackers@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 C052494C; Mon, 8 Dec 2014 10:04:09 +0000 (UTC) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 872469F6; Mon, 8 Dec 2014 10:04:09 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id et14so4976401pad.1 for ; Mon, 08 Dec 2014 02:04:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=wh7HwlJj1sWKymiKz/edDr5vXH6FsUh7seRw2p8cCpE=; b=h5p7sucfhxJcy3wZL4TA6c6MQTE1Xn3Vo6H6eT5pyVeR5Dh7cp4NyobapWdAtrZLQz Wt768DmeULn4nA9e56GTM5qwa5y9HzTOJ6EgSy7H11KZv4/GssVUC8cKknz9UR3tihtc Se6pPt8KZmIhWcXNr/7D+IqjR2Lgl00iVmNpNZA4gS+CPQUS1Yh2k5xpIrwgdU5s197D 6ovs4zfYgR7HMyzTuTXiYAllD6msQkLVII+qrKTiGvL/rZBz40WLCklU2QXICyYNHUNH fkQ0zjixQXjkyJdC9ttjJ4vTNmBlvl3ONZbeVXa77maA2Cq4WHc7nQS8JrQg09x24Zu/ k8/w== X-Received: by 10.66.138.41 with SMTP id qn9mr52198646pab.82.1418033049056; Mon, 08 Dec 2014 02:04:09 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:f855:3c8d:38d3:b94b? ([2601:8:ab80:7d6:f855:3c8d:38d3:b94b]) by mx.google.com with ESMTPSA id fb7sm36205665pab.10.2014.12.08.02.04.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 02:04:08 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_01A83CEE-0155-488F-8325-AE4CF7676EB6"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: cross installing freebsd? From: Garrett Cooper In-Reply-To: <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> Date: Mon, 8 Dec 2014 02:04:06 -0800 Message-Id: <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> References: <5483AE21.8090306@freebsd.org> <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 10:04:09 -0000 --Apple-Mail=_01A83CEE-0155-488F-8325-AE4CF7676EB6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 7, 2014, at 21:48, Alfred Perlstein wrote: >> Hi Alfred, >> Reading your examples... >> 1. I=92m wondering if we should formalize CROSS_BUILD_TESTING in = Makefile.inc1: >>=20 >> 188 .if ${MACHINE} =3D=3D ${TARGET} && ${MACHINE_ARCH} =3D=3D = ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING) >> 189 OBJTREE=3D ${MAKEOBJDIRPREFIX} >> 190 .else >> 191 OBJTREE=3D ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH} >> 192 .endif >>=20 >> 2. MAKEWHATIS seems like it should be added to ITOOLS. Do you = agree? >> 3. Seems like strip should be added to ITOOLS if = CROSS_BUILD_TESTING is defined (or at the very least LOCAL_ITOOLS). >> 4. Why did you need to explicitly define the path to INSTALL? >> Thanks! >=20 > To be honest I have a gist as to what you're saying but I think the = build is suffering from shibboleth-itis. Meaning it's not serviceable = unless you're intimately familiar with it=85 Right. I didn=92t know about all of these magic things until I started = reading the Makefiles :). > I *guess* that ITOOLS or maybe LOCAL_ITOOLS means programs needed to = installworld/installkernel? Yes. Basically for things that can be replaced while make installworld = is run, or as Makefile.inc1 says=85 "# Required install tools to be saved in a scratch dir for safety.=94 All the libraries for the tools are backed up so if the tools get = replaced while make distributeworld/installworld is running, your system = won=92t be hosed (that=92s why make installworld works for me the = majority of the time, if cp gets replaced and ABI changes =97 not = always, but oftentimes). > If so, then yes, makewhatis needs to be added to that. Review opened for that issue: https://reviews.freebsd.org/D1280 > As far as everything else written: > no idea what "CROSS_BUILD_TESTING" means, it's not documented anywhere = I can see in the makefile. It=92s something that ru@ introduced (probably to do comparisons between = architectures). I haven=92t quite tracked down why make tinderbox works = with TARGET_ARCH/TARGET set to the host values, but I=92ll probably = figure it out soon. > I can't decode if there will be a target that "just works" for doing a = cross-install, will there be? What will it be named and how will people = invoke it? >=20 > Can we have cross-installworld and cross-installkernel targets please? Setting TARGET/TARGET_ARCH should be sufficient in an ideal world. = Jumping through hoops to do this with a myriad of variables which should = be automatically determined via sane defaults seems wrong/unusable=85 = there shouldn=92t be a reason for why we need to introduce autoconf = variable style hell for building/installing world, unless someone is = intentionally skating around sane defaults. I think that creating more custom targets will only complicate/muddle = the build process, and create more potential for bugs like the one that = I just addressed with xdev. Thanks! --Apple-Mail=_01A83CEE-0155-488F-8325-AE4CF7676EB6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhXeWAAoJEMZr5QU6S73edM0H/iuNhF/ZGdu8+NvVzr6krQ3s rkzNWELvsL/mDDgs6ItZqGW3gbE0y9sej3tsKjFmkn/d3AZNygZDSyaIjjLRla6d iSi1dc8uhE1oDEAZuChr7qhudEQ2IEcb0WbGhPoHgdO4Ts0KK6PWku6ZikdhJKoI KVtsm56cO0UjpqCoLoviBdEyloecpbYYGFkGl5zexuHgAbMmM4jB4KHtsLUX3uH0 Zih2K89MxBrE5kxaBpSAawylDo2TEz8W6Bp6v0Hcn7E+QlTDS8HOhJ9OYWLz7r14 ibtVUiBGKOA1D7jWDm/y9zdyZOe0xzurbrDteiMeyxQcDaZNygQ7Cfxelhpy+vo= =HtXj -----END PGP SIGNATURE----- --Apple-Mail=_01A83CEE-0155-488F-8325-AE4CF7676EB6-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 10:22:43 2014 Return-Path: Delivered-To: freebsd-hackers@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 B00CECCA; Mon, 8 Dec 2014 10:22:43 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7931BC2C; Mon, 8 Dec 2014 10:22:43 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id w10so1813311pde.39 for ; Mon, 08 Dec 2014 02:22:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=/7hrOkKp2Cq3va9l9A3+M9sIWOFK2mWzYpmL8BAw07Q=; b=QURQuJcYzZieRbcuGgsBr3sCJvT4LQVktAGK4TpdG0Eyn5Dcun/RdiDSHJ2v6T/YZp U53CTEMD3KwTHSml3yAoJh84SoKliPiLWikdXw9nlJjmozVj1phg6Z7+dCxliy6+wYZD K5r/qacfNhvrjPewZHC/TfyYwzZ55BOfk/xo8c3POtG6f+QAg/VbxafLwAs0KTI6uNmb UXgHyWSDBTpnqt+PdnbbhSGY8T9I1D+1KrgEITOE1fsV15tETMOb/qHvjNVzMlEYzt7v eaqz4yVR2+DNJQccb06YAe/8yJNrzRgF5RUQkG9+pdcvgvMxLQJpxwBiPM1P+dAo1UmG ehZw== X-Received: by 10.70.47.195 with SMTP id f3mr19265969pdn.156.1418034163056; Mon, 08 Dec 2014 02:22:43 -0800 (PST) Received: from [192.168.20.5] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id y9sm36115567pdj.29.2014.12.08.02.22.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 02:22:41 -0800 (PST) From: Garrett Cooper Content-Type: multipart/signed; boundary="Apple-Mail=_7082F75A-42E3-4556-A993-2B1F96CF3852"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? Date: Mon, 8 Dec 2014 02:22:39 -0800 Message-Id: <44119C94-0459-4942-B79B-11450C8B5664@gmail.com> To: FreeBSD Hackers Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Cc: Kirk McKusick , jkh@FreeBSD.org, dickey@his.com X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 10:22:43 -0000 --Apple-Mail=_7082F75A-42E3-4556-A993-2B1F96CF3852 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi all, I=92m trying to resolve an issue where usr.bin/vi is needed to = preprocess share/termcap every time make buildworld is invoked on = FreeBSD. The termcap file reordering seems to have been done since the = BSD 4.4 Lite sources were imported into FreeBSD: = https://svnweb.freebsd.org/base/projects/building-blocks/share/termcap/Mak= efile?view=3Dmarkup#l15 , = https://svnweb.freebsd.org/base?view=3Drevision&revision=3D1638 . I = don=92t have history behind why this should be done (it=92s unfortunate = because it appears to mangle the comment <-> entry mappings, and = ultimately this gets put into termcap.db), and I was hoping that someone = with additional history could fill in why this is being done. Thank you! --Apple-Mail=_7082F75A-42E3-4556-A993-2B1F96CF3852 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhXvvAAoJEMZr5QU6S73ebQAH/1AHCkXDT7rpHm0w7g5l3d0P CAsKYkD1/HXgBo7agts+hT5g08obkFfkD/gsVNY/n9TDj9P/DJX/s6I4V1zl0qZQ /jdJIrmF6wB8ny9zpEQxVp70jk1/Wk0Dz+M+ti8KsmVGJa8E+dK42DPsssOIxUIC UkN3+/ZpPe6wDyk3USQcQ89D2OZoib2iz+kAnySCbthniDmOq7sx2rwd0FXzXtHy n2IJlRGtKIw8lNLnwH61u1vnIBPUchDzWjbkdK0gxcQeZyRABDX9RMkL1UDZGJ4n GeSM2nndJWTnQuMiLw52OaQOT7ioyqBEi0LMQyK4rAMKumUfRbvgTBMqoTmw89M= =qLtn -----END PGP SIGNATURE----- --Apple-Mail=_7082F75A-42E3-4556-A993-2B1F96CF3852-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 10:26:30 2014 Return-Path: Delivered-To: freebsd-hackers@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 ACBDFE2E; Mon, 8 Dec 2014 10:26:30 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 73C4CC6B; Mon, 8 Dec 2014 10:26:30 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id bj1so4980359pad.37 for ; Mon, 08 Dec 2014 02:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=etIGBn/nA7MzXd61wyS2Zs52VQaa0Eht2Dy9ilZM2QU=; b=r2/NvIlxqFRVMdohwyA7xLb+8ZtYgixXmkepAH1weBevVaXiBnhxWvqg0jIXBKEE46 sMsmHFbX8laCIiCXGSnjl2tlFRGJ6xSRWqOJBe+tuP0RJc+som9isYZWFswsze89c9hC rTriGs9pxA66qDXTee/a/tuU+GklWslFxlem/a2fHSsy9HjUqms2P+uFqnhdELuA8qZi 5T+X20a9RZBAeAkif1V+V1jZGR2b2auLSryepl52+cGJaLx+8d89oBlmH4au70qPTjx6 +oqwJahRRVxmvagvGf8rzjnCjdT3PCiDtsRlijK+VANYZbnDUJ9SaKQIlFVuUYfvpRZW rDaw== X-Received: by 10.66.122.69 with SMTP id lq5mr52612807pab.52.1418034390050; Mon, 08 Dec 2014 02:26:30 -0800 (PST) Received: from [192.168.20.5] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id ty7sm29906755pac.1.2014.12.08.02.26.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 02:26:29 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_44C80FCC-8F44-4086-AFA5-5574366DB358"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: cross installing freebsd? From: Garrett Cooper In-Reply-To: <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> Date: Mon, 8 Dec 2014 02:26:28 -0800 Message-Id: <75A452B0-5E16-47C1-8D1C-F1DC95BA6F50@gmail.com> References: <5483AE21.8090306@freebsd.org> <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> To: Alfred Perlstein X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 10:26:30 -0000 --Apple-Mail=_44C80FCC-8F44-4086-AFA5-5574366DB358 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 8, 2014, at 2:04, Garrett Cooper wrote: > On Dec 7, 2014, at 21:48, Alfred Perlstein wrote: =85 >> As far as everything else written: >> no idea what "CROSS_BUILD_TESTING" means, it's not documented = anywhere I can see in the makefile. >=20 > It=92s something that ru@ introduced (probably to do comparisons = between architectures). I haven=92t quite tracked down why make = tinderbox works with TARGET_ARCH/TARGET set to the host values, but I=92ll= probably figure it out soon. It is documented in build(7): buildworld Build everything but the kernel, configure = files in etc, and release. The actual build location = prefix used is ${MAKEOBJDIRPREFIX}${.CURDIR} for = native builds, and = ${MAKEOBJDIRPREFIX}/${TARGET}${.CURDIR} for cross builds and native builds with = variable CROSS_BUILD_TESTING set. It might have been used in older releases for something more meaningful, = but again=85 not sure why/how tinderbox does the right thing by = MAKEOBJDIRPREFIX. Cheers, --Apple-Mail=_44C80FCC-8F44-4086-AFA5-5574366DB358 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhXzUAAoJEMZr5QU6S73e97YH/24hUeBo55velL83XTm7CjT9 h6SCgfiFXYibyLZ3zgiUyCFhQgUI/ek/z/nehEQLdSXxedPApfuVQ+0VQpDEh2py BWPJUl676hTMUbKk9oO7bXMTPNhsb4AeAIsUshOvVoSjk5rT+OzAY78Odo/tobK7 JUTEfmcE1gwYPPxU/Z9oIAfyJ03SUPAjrZNg5H9dxMrV5EXFi2N/iiR7sC44bEQ9 0LutsyxP85O3/PTp8ocA85J53bccMR1YlUTlvInXk8sNCBOKIDFE4wB402XJ2DHP 0lVteYQkHedUbYeWut87DxoPVFQkK8eBZMxznwd8CDMx37SU0VXI4Ch+sGql4ew= =sP4m -----END PGP SIGNATURE----- --Apple-Mail=_44C80FCC-8F44-4086-AFA5-5574366DB358-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 12:21:20 2014 Return-Path: Delivered-To: freebsd-hackers@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 42A36A58; Mon, 8 Dec 2014 12:21:20 +0000 (UTC) Received: from cursor.its.uu.se (smtp-out1.uu.se [130.238.7.172]) (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 AAD4DAFF; Mon, 8 Dec 2014 12:21:18 +0000 (UTC) Received: from e-mailfilter01.sunet.se (e-mailfilter01.sunet.se [192.36.171.201]) by cursor.its.uu.se (Postfix) with ESMTP id 7A67D2B1; Mon, 8 Dec 2014 13:13:45 +0100 (CET) Received: from lyra.its.uu.se (lyra.its.uu.se [130.238.7.73]) by e-mailfilter01.sunet.se (8.14.4/8.14.4/Debian-4) with ESMTP id sB8CDjcs016871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Dec 2014 13:13:45 +0100 Received: from virgata.its.uu.se (virgata.its.uu.se [130.238.7.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lyra.its.uu.se (Postfix) with ESMTPS id 078E839083; Mon, 8 Dec 2014 13:13:43 +0100 (CET) X-DKIM: Sendmail DKIM Filter v2.8.3 lyra.its.uu.se 078E839083 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uu.se; s=centralsmtp; t=1418040824; i=@uu.se; bh=oKpNJRrxjcBHNYt/IPDxUf98CmSNoq/6vzfur5jp23s=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=CjK1M2JfLC4vvwjTuWbkqM67QQbSWow9BVAGSaIfoZgeKEdFxE4xTQQ2APDB2imCZ OL8RaXviC3ihn69flofKunTFPKidMkDXKZVsVJtk0wpeFxG1UQ0PRby7Ehad4yBE5t 1A6RDYyhb/QWVeqRzJTmbMfwWRP6rTnayt0xxh8Y= Received: from jubula (localhost.localdomain [127.0.0.1]) by virgata.its.uu.se (8.13.8/8.13.8) with ESMTP id sB8CDeTC031707; Mon, 8 Dec 2014 13:13:40 +0100 Received: from h-197-74.a213.corp.bahnhof.se (h-197-74.a213.corp.bahnhof.se [85.24.197.74]) by webmail.uu.se (Horde Framework) with HTTP; Mon, 08 Dec 2014 13:13:40 +0100 Message-ID: <20141208131340.16934twbkxmadd6c@webmail.uu.se> Date: Mon, 08 Dec 2014 13:13:40 +0100 From: Erik Trulsson To: Garrett Cooper Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? References: <44119C94-0459-4942-B79B-11450C8B5664@gmail.com> In-Reply-To: <44119C94-0459-4942-B79B-11450C8B5664@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, outbound-uu-se:default, uu-se:default, base:default, @@RPTN) X-Spam-Score: -0.10 () [Tag at 15.00] T_RP_MATCHES_RCVD:-0.1 X-p0f-Info: os=Linux 2.6.x, link=Ethernet or modem X-CanIt-Geo: ip=130.238.7.55; country=SE; region=Uppsala; city=Uppsala; latitude=59.8500; longitude=17.6333; http://maps.google.com/maps?q=59.8500,17.6333&z=6 X-CanItPRO-Stream: outbound-uu-se:outbound (inherits from outbound-uu-se:default, uu-se:default, base:default) X-Canit-Stats-ID: 09Np0dJAB - afa91b7f1b04 - 20141208 X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?i=09Np0dJAB&m=afa91b7f1b04&t=20141208&c=f X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?i=09Np0dJAB&m=afa91b7f1b04&t=20141208&c=n X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?i=09Np0dJAB&m=afa91b7f1b04&t=20141208&c=s X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.36.171.201 X-Mailman-Approved-At: Mon, 08 Dec 2014 12:32:32 +0000 Cc: Kirk McKusick , FreeBSD Hackers , dickey@his.com, jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 12:21:20 -0000 Quoting Garrett Cooper : > Hi all, > I'm trying to resolve an issue where usr.bin/vi is needed to > preprocess share/termcap every time make buildworld is invoked on > FreeBSD. The termcap file reordering seems to have been done since > the BSD 4.4 Lite sources were imported into FreeBSD: > https://svnweb.freebsd.org/base/projects/building-blocks/share/termcap/Makefile?view=markup#l15 , https://svnweb.freebsd.org/base?view=revision&revision=1638 . I don't have history behind why this should be done (it's unfortunate because it appears to mangle the comment <-> entry mappings, and ultimately this gets put into termcap.db), and I was hoping that someone with additional history could fill in why this is being > done. > Thank you! > It looks like it is done to put the most common (at the time it was written) terminal types early in the reordered termcap file. This presumably so that programs reading termcap would be more likely to find the entry they wanted as quickly as possible. That would have been useful when termcap was just a plain text file, but if you are using termcap.db to look up terminal capabilities then there doesn't seem to be much point to doing such reordering beforehand. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 13:11:16 2014 Return-Path: Delivered-To: hackers@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 085B3686; Mon, 8 Dec 2014 13:11:16 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCC06FC6; Mon, 8 Dec 2014 13:11:12 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id DE4AE6A601C; Mon, 8 Dec 2014 14:11:07 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id sB8DB7Za075070; Mon, 8 Dec 2014 14:11:07 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id sB8DB7tN075049; Mon, 8 Dec 2014 14:11:07 +0100 (CET) (envelope-from lars) Date: Mon, 8 Dec 2014 14:11:07 +0100 From: Lars Engels To: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= Subject: Re: fstyp(8) Message-ID: <20141208131107.GD68024@e-new.0x20.net> References: <20141205114635.GA12557@brick.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oZv4yqUxWy6Z3hn+" Content-Disposition: inline In-Reply-To: <20141205114635.GA12557@brick.home> X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p16 User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Mon, 08 Dec 2014 13:18:51 +0000 Cc: hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 13:11:16 -0000 --oZv4yqUxWy6Z3hn+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 05, 2014 at 12:46:35PM +0100, Edward Tomasz Napiera=C5=82a wrot= e: > I'm slowly working on making autofs suitable for mounting removable > media, and one of the things required is filesystem detection. It's > kind of possible to use file(1), but it's, well, "suboptimal" for this > task. So, I went and wrote fstyp(8). >=20 > This utility, named after SVR4 command with same weird name, detects > filesystems. It's mostly based on glabel code. The output is machine > parseable, it can print out filesystem labels, and runs capsicated. >=20 > You can join the review at https://reviews.freebsd.org/D1255. Will it be possible to run "mount /dev/da$foo" without specifying a file system type? --oZv4yqUxWy6Z3hn+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJUhaNrXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tmToIAMEHK+x+Jm+ezLb8B7Yj6dT0 sSdGwTfmiR5CnDbFIylpYot6kWSIqrs0f/oUXfM3/njhiB99X12iPQix7eYoF9Zi ENbAHCWGKmmrH0wC9x6tAcqvDBQ60cvNgAVk/0zE1igZzw6V9eq61pZtTdpUKByi cnjgZAtkOCucvxs7Mj5FTbh04gx+mtWe3QsZLAPJcC72YCOhw8Daqa1a7Y+VLOs1 7yWZtBkZXqpntdLn7mqoDrE6sYwc3ghfZ7OfMiLn5bdk0Xry1QKbougup8zU9Nbg kirRSpPlXRrdbip28/2UWLJ1sVkwWF7Cjq5qdUgYQRLbq9T28sdI+jL9jft+kSg= =8JqU -----END PGP SIGNATURE----- --oZv4yqUxWy6Z3hn+-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 13:20:54 2014 Return-Path: Delivered-To: freebsd-hackers@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 EE209ABB for ; Mon, 8 Dec 2014 13:20:54 +0000 (UTC) Received: from server1.xenet.de (server1.xenet.de [213.221.94.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5631611F for ; Mon, 8 Dec 2014 13:20:53 +0000 (UTC) Received: from [10.0.0.32] (intern.xenet.de [213.221.94.50]) (authenticated bits=0) by server1.xenet.de (8.12.5/8.12.5) with ESMTP id sB8DHE3q044202; Mon, 8 Dec 2014 14:17:17 +0100 (CET) (envelope-from meyser@xenet.de) Message-ID: <5485A5AE.1080602@xenet.de> Date: Mon, 08 Dec 2014 14:20:46 +0100 From: Matthias Meyser Organization: XeNET GmbH, Clausthal-Zellerfeld User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: cross installing freebsd? References: <5483AE21.8090306@freebsd.org> <54847206.8070107@xenet.de> <73D1FFAD-4E79-4561-B383-5D1F794C4688@mu.org> In-Reply-To: <73D1FFAD-4E79-4561-B383-5D1F794C4688@mu.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.38 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 13:20:55 -0000 Hi Am 07.12.2014 um 18:36 schrieb Alfred Perlstein: > > On Dec 7, 2014, at 7:28 AM, Matthias Meyser wrote: [...] >> >> It would be much nicer if the normal install* would handle this automatically. >> Someone should teach the Makesystem to build the installboottrapbinaries >> not only for the HOST system but also for the Targetsystem. >> >> Then normal install would just work. > > I wish I had time to do that, but I really do not have time to sort how to determine that reliably, also people have been pretty upset if anything in the build changes lately and anything breaks. So I am very afraid to touch any defaults. > > Due to time and the pressure to not break anything I can do one of two things: > 1) clean up the two targets I've submitted and put them in a Makefile.cross-install, then document them in the main Makefile. > 2) Keep this code in my own repo. > > Sorry. Let me know if there is a way forward with 1 for the time being? 1 ist better than nothing. ;) Go and submit. But someone with more buildsystemfoo than me and more time than both of us should fix this "the right way" in the future. Because 1) may cause trouble when incompatible changes to the programs used during install are introduced between the installed OS Version and the to be installed OS Version. This is why a separate set of binaries used to install is created during building an used during install. The show stopper is that those binaries are build for the HOST arch not the TARGET arch. (This is fine if you want to run install on the HOST for e.g. to an image) Hmmm. Now even the new target name "cross-install" seems wrong. ;) Its really a "native-install" (on i386 install a i386 system) I hope this grieve get fixed some day. - Matthias -- Matthias Meyser | XeNET GmbH Tel.: +49-5323-9489050 | 38678 Clausthal-Zellerfeld, Marktstrasse 40 Fax: +49-5323-9489059 | Registergericht: Amtsgericht Braunschweig HRB 110823 Email: Meyser@xenet.de | Geschaeftsfuehrer: Matthias Meyser From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 13:38:22 2014 Return-Path: Delivered-To: freebsd-hackers@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 A585ADF3; Mon, 8 Dec 2014 13:38:22 +0000 (UTC) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) (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 292D426E; Mon, 8 Dec 2014 13:38:22 +0000 (UTC) Received: by gremlin.foo.is (Postfix, from userid 1000) id CCF39DA848; Mon, 8 Dec 2014 13:30:23 +0000 (GMT) Date: Mon, 8 Dec 2014 13:30:23 +0000 From: Baldur Gislason To: Alfred Perlstein Subject: Re: cross installing freebsd? Message-ID: <20141208133023.GX2775@gremlin.foo.is> References: <5483AE21.8090306@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5483AE21.8090306@freebsd.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 13:38:22 -0000 I used to install my Soekris by mounting its hard drive on my desktop machine and doing a make kernel/world with the soekris hard drive as a target directory. Granted this was on an i386 host, I guess I never tried it on amd64. Baldur On Sat, Dec 06, 2014 at 05:32:17PM -0800, Alfred Perlstein wrote: > Hey folks, > > In order to make installation of a new world/kernel on my i386 soekris a > LOT faster/easier I've taken to doing builds on an amd64 host and then > "cross-installing" > > Steps are as follows: > > On amd64 host: > /usr/trees/freebsd.git % env TARGET=i386 make -j8 buildworld && env > TARGET=i386 make -j8 buildkernel > > On i386 host: > mount spigot:/usr/trees /usr/trees > mount spigot:/usr/obj /usr/obj > cd /usr/trees/freebsd.git > # install kernel: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install \ > make installkernel > # install world: > env MAKEOBJDIRPREFIX=/usr/obj/i386.i386 CC=/usr/bin/cc \ > INSTALL=/usr/bin/install STRIPBIN=/usr/bin/strip \ > MAKEWHATIS=/usr/bin/makewhatis \ > make installworld > > Seems to work nicely. > > Any objections if I add something like this target as > "cross-installworld" and "cross-installkernel" to top level Makefile? > > -Alfred > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 13:39:22 2014 Return-Path: Delivered-To: hackers@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 10253EE8 for ; Mon, 8 Dec 2014 13:39:22 +0000 (UTC) Received: from nm38.bullet.mail.ir2.yahoo.com (nm38.bullet.mail.ir2.yahoo.com [212.82.96.63]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 753FC280 for ; Mon, 8 Dec 2014 13:39:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1418045953; bh=tnQ2+/O6b6NRI/3r8f46BDaiU1/x7AxUUFviAvab4Xo=; h=Date:From:Resent-From:Resent-Date:Resent-To:From:Subject; b=VPhu3fAei+G6QJUf5YyGH0FHzfbG0rcCpMxf21rqggIw05VwWPVN5JFW+vJIRMsLhw2dQigNh8vN6Y8i9kR4+VvIaHOxyNqO3aFEOpyuMV5RK6y8qTdtbPlPUimBeCeicbLpn2nbp1dG0Z2138rwo27wWlnYeOpN5+ZAmmsYZO1PoPLhOR1eH/ulENkG+HZ25LUeAMizsLDKdSMQMrVWdbY4viTEDKyn3pz3FmQDnGDdNZJ5SUaEp8+7aEg5ei7iWrXW4zdmwd4RY/ww57Rd3VfYDfE5sS2pjXWHkx6lrUj1UzVnpVLY1aflf9tSeXwmunkRHYvfIdtZTt4rrsg6yg== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=Xe+vawyTDNPZna6Q9/PSsVJ44KhJYsF/MbYYNCK4OKdyIAmwjv8XC85lyrKv+lriiNp4LmpGIvSHgMRoze74I3320muvf/5dAQ3B5AyJ4tAPV96xSrWsCX6ynGsG19wjeLy08nYDIrZSImi24Clzf2020uglTMQ/0WAdP8QaX0NpGytc3aWj9q4jciRaV7K4nUY7jDbMojkcLWrhDC++L4qAqWWr+c4JjYUjoIBW0Q8Qird6RA1BfibebN7f2Di25WTqMBAVILgBcIak80zSvI5yAHeFowGGzGTTB8DP0KOyPuwVfdFu0S6S4Ltov/SIXYA9N3e7Qm7Wdsp5s+wuZA==; Received: from [212.82.98.55] by nm38.bullet.mail.ir2.yahoo.com with NNFMP; 08 Dec 2014 13:39:13 -0000 Received: from [46.228.39.88] by tm8.bullet.mail.ir2.yahoo.com with NNFMP; 08 Dec 2014 13:39:13 -0000 Received: from [127.0.0.1] by smtp125.mail.ir2.yahoo.com with NNFMP; 08 Dec 2014 13:39:13 -0000 X-Yahoo-Newman-Id: 133375.35515.bm@smtp125.mail.ir2.yahoo.com Message-ID: <133375.35515.bm@smtp125.mail.ir2.yahoo.com> Date: Mon, 8 Dec 2014 13:39:13 +0000 (UTC) X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: eTJCHWEVM1lRH79meJAmxg_1Mrcnlo0mhnBSuHVSw6aWe2j Fmi5B0dCbYViwYcjs0ClqyGBDohBMGKVAVj7uLem2v6GYnJhALE57YEzfEk5 Je4c.41_wn59HZeaDi5lSFenXc1IZT54ueY2WaIfeeZu.LmwAVzWVJBFaIPM 7Hdo.DtfqbMmAmInb3Z8aTNreJyjLThCj4VTfHpbf3RvJmyXf_NS3oKydlc7 .DzN2NQRs8ToeR8XHojsDVnEmvMNBaoqETb991wHcxB_moWfgG6bZc0C_pvf ZvWTtJTAMycNveSMbc6PZ31HUimkt.JNKf8wWsMg1CSoxImP2tOOgwvzQB6q iyAiEK.pJRpNRkMAfjuPGUwO9AuKLzlLjvmZKcaOM6JKjOlHj2dX7eqddAET _6OVFwtL2bicaRQz.fkMxtp822Uhh_asikIkVzUk_NKDVCrNlaE251vK420x tn297ipxbBTKlCMcUMoO6UIAH1n_oi9Ji7us4ReVbABO2Q75Ui9kNO6nCctG L3S_m8wa4BlPGfwyyO9O7ITuPr8pAsIs- X-Yahoo-SMTP: iDf2N9.swBDAhYEh7VHfpgq0lnq. From: se@freebsd.org Received: by StefanEsser.freebsd.org (Postfix, from userid 200) id 174C8701; Mon, 8 Dec 2014 14:39:12 +0100 (CET) Resent-From: Stefan Esser Resent-Date: Mon, 8 Dec 2014 14:39:12 +0100 Resent-Message-ID: <20141208133912.GA21370@StefanEsser.freebsd.org> Resent-To: hackers@freebsd.org, phil@juniper.net X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 13:39:22 -0000 >From se@FreeBSD.org Mon Dec 8 14:34:01 2014 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on StefanEsser.freebsd.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=7.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,RDNS_NONE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 X-Original-To: se@localhost Received: from StefanEsser.freebsd.org (localhost [IPv6:::1]) by StefanEsser.freebsd.org (Postfix) with ESMTP id 814C66FF for ; Mon, 8 Dec 2014 14:34:01 +0100 (CET) Received: from sfwdallmx.t-online.de [194.25.134.46] by StefanEsser.freebsd.org with POP3 (fetchmail-6.3.26) for (single-drop); Mon, 08 Dec 2014 14:34:01 +0100 (CET) Received: from mailin58.aul.t-online.de ([172.20.27.247]) by ehead603.aul.t-online.de (Dovecot) with LMTP id DS1GDYOmhVQ+LAAAPh7MgA; Mon, 08 Dec 2014 14:24:19 +0100 Received: from mx2.freebsd.org ([8.8.178.116]) by mailin58.aul.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1XxyIT-2JxvX60; Mon, 8 Dec 2014 14:24:17 +0100 Received: from hub.freebsd.org (hub.freebsd.org [8.8.178.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.freebsd.org (Postfix) with ESMTPS id 37D5B373A for ; Mon, 8 Dec 2014 13:24:15 +0000 (UTC) Received: by hub.freebsd.org (Postfix) id 35023C52; Mon, 8 Dec 2014 13:24:15 +0000 (UTC) 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 34387C50 for ; Mon, 8 Dec 2014 13:24:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2034146 for ; Mon, 8 Dec 2014 13:24:14 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id sB8DOEcg056293 for ; Mon, 8 Dec 2014 13:24:14 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id sB8DOE39056292; Mon, 8 Dec 2014 13:24:14 GMT (envelope-from root) Date: Mon, 8 Dec 2014 13:24:14 +0000 To: se@localhost.FreeBSD.org From: =?utf-8?Q?se_=28Stefan_E=C3=9Fer=29?= Subject: [Differential] [Updated, 639 lines] D1206: Add libxo support to pciconf Message-ID: <75337b9bc584b5c3795df4e0b12641ad@localhost.localdomain> X-Priority: 3 Thread-Topic: D1206: Add libxo support to pciconf X-Herald-Rules: none X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: NmM1NGY4YmRhNzU1ODBkMDBiYjdjMTRhYWQ3IFSFpn4= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-TOI-SPAM: u;0;2014-12-08T13:24:19Z X-TOI-VIRUSSCAN: unchecked X-TOI-MSGID: abfdb5d0-3bcc-4171-8a83-0d818bff93ab X-Seen: false X-ENVELOPE-TO: X-UID: 182952 X-Keywords: NonJunk se updated this revision to Diff 2680. se added a comment. Update after review by Phil Shafer and extend to cover errors and capabilities Summary: This version contains many fixes to issues pointed out by Phil and a number of further enhancements: - Use of XO lists and instances to structure the information - Descriptive identifiers instead of abbreviations - Addition of XO support to PCI/PCIe error reporting - Addition of XO support to PCI/PCIe capability information printing I do not have access to a PCI or PCI-Express Spec. with information on the capabilities and their specified names, but have only used publicly available information to select XML/JSON labels. A pointer to a freely available specification of PCI/PCIe capabilities (just the path that might help chose good names for data fields) would be highly appreciated. Test Plan: This version of pciconf should generate 100% identical output, except when one of the structured XO formats is requested. Please test with: pciconf -lbecv I do not know whether the labels used for XML amd JSON output of PCI/PCIe capabilities are well chosen. Several names are very long, but I wanted to avoid cryptic abbreviations. Suggestions for better or more correct names are welcome. I could not test output of Intel or AMD (Hyper Transport) specific capabilities (my Intel system uses SATA AHCI, but I do not see that in the reported capabilities; I do not have any FreeBSD systems on AMD hardware, currently). I'm adding a few reviewers (jhb because he did the initial commit of cap.c and kib because of the HT specific information that I cannot test). I hope you don't mind being selected as potential reviewers. Reviewers: phil@juniper.net hackers@freebsd.org jhb@freebsd.org kib@freebsd.org Subscribers: CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D1206?vs=2617&id=2680 REVISION DETAIL https://reviews.freebsd.org/D1206 AFFECTED FILES Makefile cap.c err.c pciconf.c To: se Cc: emaste From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 16:59:23 2014 Return-Path: Delivered-To: hackers@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 51E3757D for ; Mon, 8 Dec 2014 16:59:23 +0000 (UTC) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D521AD73 for ; Mon, 8 Dec 2014 16:59:22 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id x13so4195359wgg.33 for ; Mon, 08 Dec 2014 08:59:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tRsaPZk7kZiD7tw1Jq63yD7xP9wtGsMjHENnBtoHQXA=; b=0AGZDqQhU5ubQ6iOHQM0gG1ZLC2dayIwGyLeZ/yhNcJQPcGZ4fRPMtPvcMK3KD/lEz gX3RCCEwn+g8Q5jWl2ON5dsQH9RB0HuXuPvzTknePsi8aCyXYOdU7hBjrWuApZJ5cyCH BPBM2vF9i3xxVNuVyumwUIhuLKnMhBrT1Yp3fhLOH63EMMxUM7sTI0njG3feHeby4GOj LLPAUnwIINV8UaBRurT8NjPQAXUt8Nfl9h/gfHC6DeRWeb68xtA0dqJiIUoJLkfG0YRG ApakEtq8TsyZs0f2j287XC0AtUQAOV2OX9ZqX3VmtKfBi6t0kIjURw8K9Cjemx9Eukcp InQQ== X-Received: by 10.180.73.235 with SMTP id o11mr25410403wiv.51.1418057961181; Mon, 08 Dec 2014 08:59:21 -0800 (PST) Received: from [77.113.95.134] (apn-77-113-95-134.dynamic.gprs.plus.pl. [77.113.95.134]) by mx.google.com with ESMTPSA id eu8sm10464043wib.21.2014.12.08.08.59.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 08:59:20 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: fstyp(8) From: =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Mailer: iPhone Mail (12B435) In-Reply-To: <20141208131107.GD68024@e-new.0x20.net> Date: Mon, 8 Dec 2014 17:59:17 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <02915D00-6415-4C9C-B841-7351B0886BC0@FreeBSD.org> References: <20141205114635.GA12557@brick.home> <20141208131107.GD68024@e-new.0x20.net> To: Lars Engels Cc: "hackers@FreeBSD.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 16:59:23 -0000 Dnia 8 gru 2014 o godz. 14:11 Lars Engels napisa=C5=82= (a): >> On Fri, Dec 05, 2014 at 12:46:35PM +0100, Edward Tomasz Napiera=C5=82a wr= ote: >> I'm slowly working on making autofs suitable for mounting removable >> media, and one of the things required is filesystem detection. It's >> kind of possible to use file(1), but it's, well, "suboptimal" for this >> task. So, I went and wrote fstyp(8). >>=20 >> This utility, named after SVR4 command with same weird name, detects >> filesystems. It's mostly based on glabel code. The output is machine >> parseable, it can print out filesystem labels, and runs capsicated. >>=20 >> You can join the review at https://reviews.freebsd.org/D1255. >=20 > Will it be possible to run "mount /dev/da$foo" without specifying a file > system type? No, but it's possible to run "mount -t `fstyp /dev/da$foo` /dev/da$foo /mnt"= . Or, with upcoming "-media" autofs map, just "cd /media/da$foo". From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 17:00:18 2014 Return-Path: Delivered-To: freebsd-hackers@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 A5F2766D; Mon, 8 Dec 2014 17:00:18 +0000 (UTC) Received: from mailout05.t-online.de (mailout05.t-online.de [194.25.134.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65E4FD8F; Mon, 8 Dec 2014 17:00:18 +0000 (UTC) Received: from fwd27.aul.t-online.de (fwd27.aul.t-online.de [172.20.26.132]) by mailout05.t-online.de (Postfix) with SMTP id 442CB5C4233; Mon, 8 Dec 2014 18:00:10 +0100 (CET) Received: from [192.168.119.11] (GW0+x-ZC8hL9woRE6nB1RewrIJq6BNXdqElO2R7LXAJaJOU6c7oe4k6j2e9Aq3BwrC@[84.154.99.91]) by fwd27.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1Xy1fM-0upLeK0; Mon, 8 Dec 2014 18:00:08 +0100 Message-ID: <5485D915.5060609@freebsd.org> Date: Mon, 08 Dec 2014 18:00:05 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Subject: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) References: <133375.35515.bm@smtp125.mail.ir2.yahoo.com> In-Reply-To: <133375.35515.bm@smtp125.mail.ir2.yahoo.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: GW0+x-ZC8hL9woRE6nB1RewrIJq6BNXdqElO2R7LXAJaJOU6c7oe4k6j2e9Aq3BwrC X-TOI-MSGID: 9ba29516-ed72-44aa-8c96-8e31f3a29034 Cc: Phil Shafer X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 17:00:18 -0000 Am 08.12.2014 um 14:39 schrieb se@freebsd.org: >> >From se@FreeBSD.org Mon Dec 8 14:34:01 2014 > Return-Path: > X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on [...] Sorry for the malformed message, I have no idea why the mail header became part of the message body. (The message was sent as a "bounce" by "mutt", and that used to work for decades ...) Content of this message should just have been my update on the patch that adds XO support to pciconf and which is available for review as D1206 on reviews.freebsd.org (https://reviews.freebsd.org/D1206). Regards, STefan And here is just the relevant text from that mal-formatted message: > Update after review by Phil Shafer and extend to cover errors and capabilities > > Summary: > > This version contains many fixes to issues pointed out by Phil and > a number of further enhancements: > - Use of XO lists and instances to structure the information > - Descriptive identifiers instead of abbreviations > - Addition of XO support to PCI/PCIe error reporting > - Addition of XO support to PCI/PCIe capability information printing > > I do not have access to a PCI or PCI-Express Spec. with information on > the capabilities and their specified names, but have only used publicly > available information to select XML/JSON labels. A pointer to a freely > available specification of PCI/PCIe capabilities (just the path that > might help chose good names for data fields) would be highly appreciated. > > Test Plan: > > This version of pciconf should generate 100% identical output, except > when one of the structured XO formats is requested. > > Please test with: > pciconf -lbecv > > I do not know whether the labels used for XML amd JSON output of PCI/PCIe > capabilities are well chosen. Several names are very long, but I wanted to > avoid cryptic abbreviations. Suggestions for better or more correct names > are welcome. > > I could not test output of Intel or AMD (Hyper Transport) specific > capabilities (my Intel system uses SATA AHCI, but I do not see that in > the reported capabilities; I do not have any FreeBSD systems on AMD > hardware, currently). > > I'm adding a few reviewers (jhb because he did the initial commit of cap.c > and kib because of the HT specific information that I cannot test). I hope > you don't mind being selected as potential reviewers. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 16:51:48 2014 Return-Path: Delivered-To: freebsd-hackers@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 AFE7A3E9; Mon, 8 Dec 2014 16:51:48 +0000 (UTC) Received: from chez.mckusick.com (chez.mckusick.com [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) (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 8FA1AD1D; Mon, 8 Dec 2014 16:51:48 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id sB8GpbpO088722; Mon, 8 Dec 2014 08:51:37 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201412081651.sB8GpbpO088722@chez.mckusick.com> To: Garrett Cooper Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? In-reply-to: <20141208131340.16934twbkxmadd6c@webmail.uu.se> Date: Mon, 08 Dec 2014 08:51:37 -0800 From: Kirk McKusick X-Mailman-Approved-At: Mon, 08 Dec 2014 17:31:14 +0000 Cc: FreeBSD Hackers , Erik Trulsson , dickey@his.com, jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 16:51:48 -0000 > Date: Mon, 08 Dec 2014 13:13:40 +0100 > From: Erik Trulsson > To: Garrett Cooper > Cc: FreeBSD Hackers , > Kirk McKusick , jkh@freebsd.org, > dickey@his.com > Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? > X-ASK-Info: Message Queued (2014/12/08 04:13:49) > X-ASK-Info: Confirmed by User (2014/12/08 08:34:35) > > Quoting Garrett Cooper : > >> Hi all, >> I'm trying to resolve an issue where usr.bin/vi is needed to >> preprocess share/termcap every time make buildworld is invoked on >> FreeBSD. The termcap file reordering seems to have been done since >> the BSD 4.4 Lite sources were imported into FreeBSD: >> https://svnweb.freebsd.org/base/projects/building-blocks/share/termcap/Makefile?view=markup#l15, >> https://svnweb.freebsd.org/base?view=revision&revision=1638. >> I don't have history behind why this should be done (it's unfortunate >> because it appears to mangle the comment <-> entry mappings, and >> ultimately this gets put into termcap.db), and I was hoping that >> someone with additional history could fill in why this is being done. >> Thank you! > > It looks like it is done to put the most common (at the time it was > written) terminal types early in the reordered termcap file. This > presumably so that programs reading termcap would be more likely to > find the entry they wanted as quickly as possible. > > That would have been useful when termcap was just a plain text file, > but if you are using termcap.db to look up terminal capabilities then > there doesn't seem to be much point to doing such reordering beforehand. I believe Erik Trulsson's answer is correct. Termcap had grown very large and on sub-1-MIP computers took a noticable delay to read on every startup of programs using it. So, it was reordered to reduce the startup time on common terminals. As Erik points out this optimization is no longer necessary as termcap is now placed in a database. Not to mention that there are far fewer entries in it today than there were at the peak of its existence. Kirk McKusick From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 17:47:16 2014 Return-Path: Delivered-To: freebsd-hackers@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 A7B28E83 for ; Mon, 8 Dec 2014 17:47:16 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 93C4389E for ; Mon, 8 Dec 2014 17:47:16 +0000 (UTC) Received: from [10.0.1.20] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 4D9C8341F872; Mon, 8 Dec 2014 09:47:16 -0800 (PST) Subject: Re: cross installing freebsd? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Alfred Perlstein In-Reply-To: <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> Date: Mon, 8 Dec 2014 09:47:17 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5483AE21.8090306@freebsd.org> <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> To: Garrett Cooper X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 17:47:16 -0000 On Dec 8, 2014, at 2:04 AM, Garrett Cooper wrote: > On Dec 7, 2014, at 21:48, Alfred Perlstein wrote: >=20 >>> Hi Alfred, >>> Reading your examples... >>> 1. I=92m wondering if we should formalize CROSS_BUILD_TESTING in = Makefile.inc1: >>>=20 >>> 188 .if ${MACHINE} =3D=3D ${TARGET} && ${MACHINE_ARCH} =3D=3D = ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING) >>> 189 OBJTREE=3D ${MAKEOBJDIRPREFIX} >>> 190 .else >>> 191 OBJTREE=3D ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH} >>> 192 .endif >>>=20 >>> 2. MAKEWHATIS seems like it should be added to ITOOLS. Do you = agree? >>> 3. Seems like strip should be added to ITOOLS if = CROSS_BUILD_TESTING is defined (or at the very least LOCAL_ITOOLS). >>> 4. Why did you need to explicitly define the path to INSTALL? >>> Thanks! >>=20 >> To be honest I have a gist as to what you're saying but I think the = build is suffering from shibboleth-itis. Meaning it's not serviceable = unless you're intimately familiar with it=85 >=20 > Right. I didn=92t know about all of these magic things until I started = reading the Makefiles :). >=20 >> I *guess* that ITOOLS or maybe LOCAL_ITOOLS means programs needed to = installworld/installkernel? >=20 > Yes. Basically for things that can be replaced while make installworld = is run, or as Makefile.inc1 says=85 >=20 > "# Required install tools to be saved in a scratch dir for safety.=94 >=20 > All the libraries for the tools are backed up so if the tools get = replaced while make distributeworld/installworld is running, your system = won=92t be hosed (that=92s why make installworld works for me the = majority of the time, if cp gets replaced and ABI changes =97 not = always, but oftentimes). >=20 >> If so, then yes, makewhatis needs to be added to that. >=20 > Review opened for that issue: https://reviews.freebsd.org/D1280 >=20 >> As far as everything else written: >> no idea what "CROSS_BUILD_TESTING" means, it's not documented = anywhere I can see in the makefile. >=20 > It=92s something that ru@ introduced (probably to do comparisons = between architectures). I haven=92t quite tracked down why make = tinderbox works with TARGET_ARCH/TARGET set to the host values, but I=92ll= probably figure it out soon. >=20 >> I can't decode if there will be a target that "just works" for doing = a cross-install, will there be? What will it be named and how will = people invoke it? >>=20 >=20 >> Can we have cross-installworld and cross-installkernel targets = please? >=20 > Setting TARGET/TARGET_ARCH should be sufficient in an ideal world. = Jumping through hoops to do this with a myriad of variables which should = be automatically determined via sane defaults seems wrong/unusable=85 = there shouldn=92t be a reason for why we need to introduce autoconf = variable style hell for building/installing world, unless someone is = intentionally skating around sane defaults. >=20 > I think that creating more custom targets will only complicate/muddle = the build process, and create more potential for bugs like the one that = I just addressed with xdev. I still don't see how I am supposed to do this: ssh amd64_machine export TARGET=3Di386 cd /usr/trees/freebsd make -j8 build world && make -j8 buildkernel ssh i386box mount amd64_machine:/usr/trees/freebsd /usr/trees/freebsd mount amd64_machine:/usr/obj /usr/obj cd /usr/trees/freebsd make installkernel installworld That last step "make installkernel installworld" will bomb out unless I = set those vars CC=3D/usr/bin/cc, MAKEWHATIS=3D/usr/bin/makewhatis, = STRIPBIN=3D/usr/bin/strip, INSTALL=3D/usr/bin/install all over the = place. Why is there not a target for this that just knows the right = things to set? -Alfred= From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 17:49:35 2014 Return-Path: Delivered-To: freebsd-hackers@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 4662AFD3 for ; Mon, 8 Dec 2014 17:49:35 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 31DE48C9 for ; Mon, 8 Dec 2014 17:49:35 +0000 (UTC) Received: from [10.0.1.20] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id EE256341F850; Mon, 8 Dec 2014 09:49:34 -0800 (PST) Subject: Re: cross installing freebsd? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Alfred Perlstein In-Reply-To: Date: Mon, 8 Dec 2014 09:49:37 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5483AE21.8090306@freebsd.org> <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> To: Garrett Cooper X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 17:49:35 -0000 On Dec 8, 2014, at 9:47 AM, Alfred Perlstein wrote: >=20 > On Dec 8, 2014, at 2:04 AM, Garrett Cooper wrote: >=20 >> On Dec 7, 2014, at 21:48, Alfred Perlstein = wrote: >>=20 >>>> Hi Alfred, >>>> Reading your examples... >>>> 1. I=92m wondering if we should formalize CROSS_BUILD_TESTING in = Makefile.inc1: >>>>=20 >>>> 188 .if ${MACHINE} =3D=3D ${TARGET} && ${MACHINE_ARCH} =3D=3D = ${TARGET_ARCH} && !defined(CROSS_BUILD_TESTING) >>>> 189 OBJTREE=3D ${MAKEOBJDIRPREFIX} >>>> 190 .else >>>> 191 OBJTREE=3D ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH} >>>> 192 .endif >>>>=20 >>>> 2. MAKEWHATIS seems like it should be added to ITOOLS. Do you = agree? >>>> 3. Seems like strip should be added to ITOOLS if = CROSS_BUILD_TESTING is defined (or at the very least LOCAL_ITOOLS). >>>> 4. Why did you need to explicitly define the path to INSTALL? >>>> Thanks! >>>=20 >>> To be honest I have a gist as to what you're saying but I think the = build is suffering from shibboleth-itis. Meaning it's not serviceable = unless you're intimately familiar with it=85 >>=20 >> Right. I didn=92t know about all of these magic things until I = started reading the Makefiles :). >>=20 >>> I *guess* that ITOOLS or maybe LOCAL_ITOOLS means programs needed to = installworld/installkernel? >>=20 >> Yes. Basically for things that can be replaced while make = installworld is run, or as Makefile.inc1 says=85 >>=20 >> "# Required install tools to be saved in a scratch dir for safety.=94 >>=20 >> All the libraries for the tools are backed up so if the tools get = replaced while make distributeworld/installworld is running, your system = won=92t be hosed (that=92s why make installworld works for me the = majority of the time, if cp gets replaced and ABI changes =97 not = always, but oftentimes). >>=20 >>> If so, then yes, makewhatis needs to be added to that. >>=20 >> Review opened for that issue: https://reviews.freebsd.org/D1280 >>=20 >>> As far as everything else written: >>> no idea what "CROSS_BUILD_TESTING" means, it's not documented = anywhere I can see in the makefile. >>=20 >> It=92s something that ru@ introduced (probably to do comparisons = between architectures). I haven=92t quite tracked down why make = tinderbox works with TARGET_ARCH/TARGET set to the host values, but I=92ll= probably figure it out soon. >>=20 >>> I can't decode if there will be a target that "just works" for doing = a cross-install, will there be? What will it be named and how will = people invoke it? >>>=20 >>=20 >>> Can we have cross-installworld and cross-installkernel targets = please? >>=20 >> Setting TARGET/TARGET_ARCH should be sufficient in an ideal world. = Jumping through hoops to do this with a myriad of variables which should = be automatically determined via sane defaults seems wrong/unusable=85 = there shouldn=92t be a reason for why we need to introduce autoconf = variable style hell for building/installing world, unless someone is = intentionally skating around sane defaults. >>=20 >> I think that creating more custom targets will only complicate/muddle = the build process, and create more potential for bugs like the one that = I just addressed with xdev. >=20 >=20 > I still don't see how I am supposed to do this: >=20 > ssh amd64_machine > export TARGET=3Di386 > cd /usr/trees/freebsd > make -j8 build world && make -j8 buildkernel >=20 > ssh i386box > mount amd64_machine:/usr/trees/freebsd /usr/trees/freebsd > mount amd64_machine:/usr/obj /usr/obj > cd /usr/trees/freebsd > make installkernel installworld >=20 > That last step "make installkernel installworld" will bomb out unless = I set those vars CC=3D/usr/bin/cc, MAKEWHATIS=3D/usr/bin/makewhatis, = STRIPBIN=3D/usr/bin/strip, INSTALL=3D/usr/bin/install all over the = place. Why is there not a target for this that just knows the right = things to set? >=20 I just re-read your original mail, if what you're saying is that on the = i386 box I need to set "TARGET_ARCH" or "TARGET" or "I_AM_A_DERP" vars = to something, then just say what those magic vars are so I can document = it please. gah! -Alfred= From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 18:24:02 2014 Return-Path: Delivered-To: freebsd-hackers@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 84C17A67; Mon, 8 Dec 2014 18:24:02 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A7C9CA8; Mon, 8 Dec 2014 18:24:02 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id w10so2498591pde.11 for ; Mon, 08 Dec 2014 10:24:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=xrpxhD4GgojXRU/uISXHvMM40lhraGNYYIPU1gfXYkI=; b=Mwk4N1mquubj+YulG3Cz+w53LDNkf4KdfmMxCdKLJxESp6zCTq1ewgp4/bG9CmGzNR VvE/rvYL4p1Y6yJsKZHkwwQS8I/I931bHgZFXS6KAO/UuZ7DzEcqDcIU/8Sy7I2z7cVG RWljU6B8/4atmjow08LWFLpIDkRJhrUj8ngpljGZz11AQc8cjOL7zl/BBjOb8vCXrOG9 FQJ741jdBKzeQalKzqLI6De0/aSlQb2onMOjgBoLuca6FnkmVSIJ+Dh4eXxumqCMLQo1 hJXyFzvOuE7WDD5k1bnHV3lAjHBC7SkN04tFhFCt0dgMmZWQoKqR2Pc05FoJQ4m7JEOR iZpA== X-Received: by 10.70.131.78 with SMTP id ok14mr23530820pdb.112.1418063041801; Mon, 08 Dec 2014 10:24:01 -0800 (PST) Received: from ?IPv6:2601:8:ab80:7d6:819d:7b8f:c98b:9d2c? ([2601:8:ab80:7d6:819d:7b8f:c98b:9d2c]) by mx.google.com with ESMTPSA id xq16sm28027433pac.31.2014.12.08.10.24.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 10:24:01 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_A7597229-6A59-4733-B08D-A0F633B016D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? From: Garrett Cooper In-Reply-To: <201412081651.sB8GpbpO088722@chez.mckusick.com> Date: Mon, 8 Dec 2014 10:23:59 -0800 Message-Id: <745168FD-F296-427D-9AEB-79FD42038324@gmail.com> References: <201412081651.sB8GpbpO088722@chez.mckusick.com> To: Kirk McKusick X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Hackers , Erik Trulsson , dickey@his.com, jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 18:24:02 -0000 --Apple-Mail=_A7597229-6A59-4733-B08D-A0F633B016D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 8, 2014, at 8:51, Kirk McKusick wrote: >> Date: Mon, 08 Dec 2014 13:13:40 +0100 >> From: Erik Trulsson >> To: Garrett Cooper >> Cc: FreeBSD Hackers , >> Kirk McKusick , jkh@freebsd.org, >> dickey@his.com >> Subject: Re: Reason for reordering /usr/share/misc/termcap.src for = /usr/share/misc/termcap ? >> X-ASK-Info: Message Queued (2014/12/08 04:13:49) >> X-ASK-Info: Confirmed by User (2014/12/08 08:34:35) >>=20 >> Quoting Garrett Cooper : >>=20 >>> Hi all, >>> I'm trying to resolve an issue where usr.bin/vi is needed to =20 >>> preprocess share/termcap every time make buildworld is invoked on =20= >>> FreeBSD. The termcap file reordering seems to have been done since =20= >>> the BSD 4.4 Lite sources were imported into FreeBSD: =20 >>> = https://svnweb.freebsd.org/base/projects/building-blocks/share/termcap/Mak= efile?view=3Dmarkup#l15, >>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D1638. >>> I don't have history behind why this should be done (it's = unfortunate >>> because it appears to mangle the comment <-> entry mappings, and >>> ultimately this gets put into termcap.db), and I was hoping that >>> someone with additional history could fill in why this is being = done. >>> Thank you! >>=20 >> It looks like it is done to put the most common (at the time it was =20= >> written) terminal types early in the reordered termcap file. This =20= >> presumably so that programs reading termcap would be more likely to =20= >> find the entry they wanted as quickly as possible. >>=20 >> That would have been useful when termcap was just a plain text file, =20= >> but if you are using termcap.db to look up terminal capabilities then = =20 >> there doesn't seem to be much point to doing such reordering = beforehand. >=20 > I believe Erik Trulsson's answer is correct. Termcap had grown very > large and on sub-1-MIP computers took a noticable delay to read on > every startup of programs using it. So, it was reordered to reduce > the startup time on common terminals. As Erik points out this = optimization > is no longer necessary as termcap is now placed in a database. Not to > mention that there are far fewer entries in it today than there were > at the peak of its existence. Ok. I=92ll do some double-checking to see whether or not something=92s = accessing the plaintext termcap file directly, but it helps to know the = history behind this (especially when the history in the installed file = gets muddled when ex is run on the file at build time). Thanks! --Apple-Mail=_A7597229-6A59-4733-B08D-A0F633B016D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUhey/AAoJEMZr5QU6S73eofgH/RqLchH2T9aiym3Bctx8y1I7 xOLMfcVm8hJjAiSjFkW0HDLVdWV+3uP3Y3CdI7tRF6oRKETMjRfS5/vykQHN0MkU 1SRwiNtpczPb+j25zkjHcJQW9Zi0NPJpTHzjqJ4FLJU90Uat3XyN4CjZlBXI3lBI kLb+cbYGbnJ7LvaXcDIDvMi62+WpI4Ct9+qNWfH8om611p7YNx9zEizbegabkzaL EgkTRKtQAFDXkzQf77puip3xW96XTNVuX7uFXu2/SwN/C7whuPegREdcvdCmmwen 2TfJYvCK+SP5++4+ndqYC+RSG8SHcj/iLTngCG+DTfMCFsGeeMbn9+kVDDuj5gg= =fjKD -----END PGP SIGNATURE----- --Apple-Mail=_A7597229-6A59-4733-B08D-A0F633B016D3-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 18:32:23 2014 Return-Path: Delivered-To: freebsd-hackers@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 6DDCCE4D; Mon, 8 Dec 2014 18:32:23 +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 4579FD92; Mon, 8 Dec 2014 18:32:23 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D2A5AB93E; Mon, 8 Dec 2014 13:32:21 -0500 (EST) From: John Baldwin To: "Christopher R. Bowman" Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Mon, 08 Dec 2014 13:32:20 -0500 Message-ID: <3125619.Pmuf3ojzUs@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <4750778.kghJ8KRE21@ralph.baldwin.cx> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 08 Dec 2014 13:32:21 -0500 (EST) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 18:32:23 -0000 On Saturday, December 06, 2014 01:37:09 PM Christopher R. Bowman wrote:= > John, > Its still sitting but I turned on verbose output and it's been sittin= g for > 10 minutes so far without any further output. Christopher. Grrr, then it might be stuck elsewhere than the interrupt config hooks.= =20 Unfortunately we'd really need to find a way to get into DDB. I think = GENERIC=20 doesn't include BREAK_TO_DEBUGGER by default, so Ctrl-Alt-Esc doesn't w= ork out=20 of the box. Can you break into the loader prompt and type 'set=20 debug.kdb.break_to_debugger=3D1' before booting? Ctrl-Alt-Esc should t= hen work=20 when it hangs. Once that happens, please get the output of 'ps' from D= DB. > -- > Christopher R. Bowman >=20 > > On Dec 5, 2014, at 7:20 AM, John Baldwin wrote: > >=20 > > On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman wr= ote: > >>> On Dec 4, 2014, at 8:39 AM, John Baldwin wrote:= > >>>> On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: > >>>> Hi, > >>>>=20 > >>>> I'm not sure - it may be that the timekeeping stuff is a bit con= fused. > >>>> Maybe it's now time to file a bug and see if we can loop the > >>>> timekeeping folk into it. > >>>=20 > >>> This is probably not timekeeping. That message is just the last = thing > >>> printed before the interrupt-driven hooks are run. If you booted= a HEAD > >>> snapshot the kernel should have DDB compiled in. Please drop int= o DDB > >>> using Ctrl-Alt-Esc and then run 'show conifhk' and reply here wit= h the > >>> output please. > >>=20 > >> John, > >>=20 > >> Thank you for responding. I tried that but the machine seemed = wedged > >> at > >>=20 > >> that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc nor = can I do > >> Ctrl-Alt-Del to reboot. All I can do it push the reset button. > >> Christopher > >=20 > > If you let it sit for 60 seconds it should print out a message tell= ing you > > what it is waiting on. --=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 21:29:29 2014 Return-Path: Delivered-To: freebsd-hackers@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 AEB21EE6; Mon, 8 Dec 2014 21:29:29 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0118.outbound.protection.outlook.com [65.55.169.118]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1CBB21F; Mon, 8 Dec 2014 21:29:28 +0000 (UTC) Received: from CO2PR05CA023.namprd05.prod.outlook.com (10.141.241.151) by BN1PR05MB440.namprd05.prod.outlook.com (10.141.58.26) with Microsoft SMTP Server (TLS) id 15.1.31.17; Mon, 8 Dec 2014 21:14:36 +0000 Received: from BN1AFFO11FD038.protection.gbl (2a01:111:f400:7c10::149) by CO2PR05CA023.outlook.office365.com (2a01:111:e400:1429::23) with Microsoft SMTP Server (TLS) id 15.1.31.17 via Frontend Transport; Mon, 8 Dec 2014 21:14:35 +0000 Received: from P-EMF03-SAC.jnpr.net (66.129.239.17) by BN1AFFO11FD038.mail.protection.outlook.com (10.58.52.242) with Microsoft SMTP Server (TLS) id 15.1.26.17 via Frontend Transport; Mon, 8 Dec 2014 21:14:34 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF03-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Mon, 8 Dec 2014 13:14:33 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id sB8LEWR41410; Mon, 8 Dec 2014 13:14:32 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.4/8.14.3) with ESMTP id sB8LEJnR056654; Mon, 8 Dec 2014 16:14:19 -0500 (EST) (envelope-from phil@idle.juniper.net) Message-ID: <201412082114.sB8LEJnR056654@idle.juniper.net> To: Stefan Esser Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) In-Reply-To: <5485D915.5060609@freebsd.org> Date: Mon, 8 Dec 2014 16:14:19 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:66.129.239.17; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(189002)(164054003)(199003)(21056001)(31966008)(77156002)(62966003)(450100001)(48376002)(110136001)(120916001)(68736005)(46102003)(4396001)(77096005)(107046002)(15975445007)(99396003)(97736003)(19580395003)(50466002)(69596002)(76506005)(53416004)(103666002)(84676001)(106466001)(81156004)(105596002)(6806004)(50986999)(20776003)(87936001)(64706001)(47776003)(92566001)(86362001)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB440; H:P-EMF03-SAC.jnpr.net; FPR:; SPF:SoftFail; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB440; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601002); SRVR:BN1PR05MB440; X-Forefront-PRVS: 041963B986 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.17 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.17) smtp.mailfrom=phil@juniper.net; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB440; X-OriginatorOrg: juniper.net X-Mailman-Approved-At: Mon, 08 Dec 2014 21:40:54 +0000 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 21:29:29 -0000 Stefan Esser writes: >D1206 on reviews.freebsd.org (https://reviews.freebsd.org/D1206). Patch looks good. Some nits: The names for xo_open_list and xo_open_instance need to be identical, so: >@@ -554,9 +698,14 @@ > /* Walk the capability list. */ > express = 0; > ptr = read_config(fd, &p->pc_sel, ptr, 1); >+ xo_open_list("capabilities"); should be: xo_open_list("capability"); to match: >+ xo_open_instance("capability"); Similar for: >+ xo_open_list("extended-capabilities"); >... >+ xo_open_list("error-categories"); >... >+ xo_open_list("base-addresses"); If you turn on the warn flag, you should get these issues reported (--libox=warn). >+ xo_emit("{:name/unknown}"); Should "name" be "capibility-name", to be consistent? Add some point the printf calls need to be removed. It would be great to see some example xml, json, and html output for this command, pretty printed of course. Thanks, Phil From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 22:15:34 2014 Return-Path: Delivered-To: freebsd-hackers@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 6D5EED84 for ; Mon, 8 Dec 2014 22:15:34 +0000 (UTC) Received: from smtp-nf-201.his.com (smtp-nf-201.his.com [216.194.251.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2F71C974 for ; Mon, 8 Dec 2014 22:15:33 +0000 (UTC) Received: from cuda201.his.com (cuda201.his.com [216.194.248.226]) by smtp-nf-201.his.com (Postfix) with ESMTPS id 7321462593 for ; Mon, 8 Dec 2014 17:06:48 -0500 (EST) X-ASG-Debug-ID: 1418076407-061c414fbe1ada5c0001-P5m3U7 Received: from smtp-nf-202.his.com (smtp-nf-202.his.com [216.194.248.252]) by cuda201.his.com with ESMTP id CWqFmaxvqzEAdNY0; Mon, 08 Dec 2014 17:06:47 -0500 (EST) X-Barracuda-Envelope-From: dickey@his.com X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.252 Received: from mail-sterling.his.com (mail-sterling.his.com [216.194.248.141]) by smtp-nf-202.his.com (Postfix) with ESMTP id 73EFA60171; Mon, 8 Dec 2014 17:06:47 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail-sterling.his.com (Postfix) with ESMTP id 4D6A73FB0008; Mon, 8 Dec 2014 17:06:46 -0500 (EST) X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.141 X-Virus-Scanned: amavisd-new at mail-sterling.his.com Received: from mail-sterling.his.com ([127.0.0.1]) by localhost (mail-sterling.his.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2ssyJrl0HCe; Mon, 8 Dec 2014 17:06:42 -0500 (EST) Received: from mail-sterling.his.com (mail-sterling.his.com [216.194.248.141]) by mail-sterling.his.com (Postfix) with ESMTP id 3A75F3FF0001; Mon, 8 Dec 2014 17:06:42 -0500 (EST) Date: Mon, 8 Dec 2014 17:06:42 -0500 (EST) From: Thomas Dickey To: Kirk McKusick Message-ID: <1479779318.56241253.1418076402148.JavaMail.root@his.com> In-Reply-To: <201412081651.sB8GpbpO088722@chez.mckusick.com> Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? MIME-Version: 1.0 X-ASG-Orig-Subj: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [71.178.218.187] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Mac)/7.2.6_GA_2926) X-Barracuda-Connect: smtp-nf-202.his.com[216.194.248.252] X-Barracuda-Start-Time: 1418076407 X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi Received-SPF: pass (his.com: domain of dickey@his.com designates 216.194.248.141 as permitted sender) X-Virus-Scanned: by bsmtpd at his.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.12627 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Mailman-Approved-At: Mon, 08 Dec 2014 23:16:03 +0000 Cc: FreeBSD Hackers , Erik Trulsson , Garrett Cooper , jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 22:15:34 -0000 ----- Original Message ----- | From: "Kirk McKusick" | To: "Garrett Cooper" | Cc: "Erik Trulsson" , "FreeBSD Hackers" , | jkh@freebsd.org, dickey@his.com | Sent: Monday, December 8, 2014 11:51:37 AM | Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? ... | | I believe Erik Trulsson's answer is correct. Termcap had grown very | large and on sub-1-MIP computers took a noticable delay to read on | every startup of programs using it. So, it was reordered to reduce | the startup time on common terminals. As Erik points out this | optimization | is no longer necessary as termcap is now placed in a database. Not to | mention that there are far fewer entries in it today than there were | at the peak of its existence. Actually, the current file in the repository is 10% longer (4667 lines vs 4007) than the first check-in. Where might I find a larger example (of BSD termcap) such as you are referring to? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 22:41:00 2014 Return-Path: Delivered-To: freebsd-hackers@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 53F0B49F; Mon, 8 Dec 2014 22:41:00 +0000 (UTC) Received: from chez.mckusick.com (chez.mckusick.com [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) (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 35518C1A; Mon, 8 Dec 2014 22:41:00 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id sB8Mek7a065468; Mon, 8 Dec 2014 14:40:46 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201412082240.sB8Mek7a065468@chez.mckusick.com> To: Thomas Dickey Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? In-reply-to: <1479779318.56241253.1418076402148.JavaMail.root@his.com> Date: Mon, 08 Dec 2014 14:40:46 -0800 From: Kirk McKusick X-Mailman-Approved-At: Mon, 08 Dec 2014 23:33:28 +0000 Cc: FreeBSD Hackers , Erik Trulsson , Garrett Cooper , jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 22:41:00 -0000 > Date: Mon, 8 Dec 2014 17:06:42 -0500 (EST) > From: Thomas Dickey > To: Kirk McKusick > Cc: Erik Trulsson , > FreeBSD Hackers , jkh@freebsd.org, > Garrett Cooper > Subject: Re: Reason for reordering /usr/share/misc/termcap.src for > /usr/share/misc/termcap ? > X-ASK-Info: Message Queued (2014/12/08 14:06:59) > X-ASK-Info: Confirmed by User (2014/12/08 14:07:49) > > ----- Original Message ----- > | From: "Kirk McKusick" > | To: "Garrett Cooper" > | Cc: "Erik Trulsson" , "FreeBSD Hackers" , > | jkh@freebsd.org, dickey@his.com > | Sent: Monday, December 8, 2014 11:51:37 AM > | Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? > ... > | > | I believe Erik Trulsson's answer is correct. Termcap had grown very > | large and on sub-1-MIP computers took a noticable delay to read on > | every startup of programs using it. So, it was reordered to reduce > | the startup time on common terminals. As Erik points out this > | optimization > | is no longer necessary as termcap is now placed in a database. Not to > | mention that there are far fewer entries in it today than there were > | at the peak of its existence. > > Actually, the current file in the repository is 10% longer (4667 > lines vs 4007) than the first check-in. Where might I find a larger > example (of BSD termcap) such as you are referring to? > > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net You are correct that it is now longer that it used to be. I (mistakenly) thought that the old cruft had been dropped. We can probbly do without Kaypro and Radio Shack trs-80 and trs100 support to name just three :-) Kirk McKusick From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 04:32:55 2014 Return-Path: Delivered-To: freebsd-hackers@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 AAD9FCD5; Tue, 9 Dec 2014 04:32:55 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 4B488798; Tue, 9 Dec 2014 04:32:55 +0000 (UTC) X-AuditID: 1209190f-f79716d000000d1a-ed-54867b7080ea Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 2C.6E.03354.07B76845; Mon, 8 Dec 2014 23:32:48 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id sB94WlSF025658; Mon, 8 Dec 2014 23:32:47 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id sB94Wjeu008747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 8 Dec 2014 23:32:47 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id sB94Wi3e013798; Mon, 8 Dec 2014 23:32:44 -0500 (EST) Date: Mon, 8 Dec 2014 23:32:44 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org Subject: Call for FreeBSD 2014Q4 (October-December) Status Reports Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNIsWRmVeSWpSXmKPExsUixG6nrltQ3RZi8LuX12LOmw9MFts3/2N0 YPKY8Wk+SwBjFJdNSmpOZllqkb5dAlfGzT37WQoucVX0X1rF2sD4mqOLkZNDQsBEYkfrOjYI W0ziwr31QDYXh5DAYiaJ59N2MUI4Gxglvt9/COUcZJKYtfguaxcjB5BTL3G8Sx2km0VAS2JV 9zxWEJtNQE1i/YprzBBTFSU2n5oEZosIyEvsa3rPDmIzA9lbVk8G2yws4CSx/NRyFhCbV8BR 4vPP5WD1ogI6Eqv3T4GKC0qcnPmEBaJXS2L59G0sExgFZiFJzUKSWsDItIpRNiW3Sjc3MTOn ODVZtzg5MS8vtUjXRC83s0QvNaV0EyMoDDkl+XcwfjuodIhRgINRiYdXw7ItRIg1say4MvcQ oyQHk5Iob4cOUIgvKT+lMiOxOCO+qDQntfgQowQHs5II7/KdrSFCvCmJlVWpRfkwKWkOFiVx 3k0/+EKEBNITS1KzU1MLUotgsjIcHEoSvJVVQEMFi1LTUyvSMnNKENJMHJwgw3mAhj8BqeEt LkjMLc5Mh8ifYlSUEuc9ApIQAElklObB9cLSxCtGcaBXhHnlQKp4gCkGrvsV0GAmoMEvEkGu Li5JREhJNTDWGlzbtK/AWTba1PR95/53U97tXLNsiv/dWZvszjkuKjh64MWEJobFkxXyWz6f F4oPnv3+uezEpOM7XwiennBI8cqauwevT8zj6Dh76dtHl+8McbO7vjkdk3y9OuXIs51/0zZk fS7UXxrcfT38+OFmv+vPnosset0/93zfvNOLL0+8futhgC3XskIlluKMREMt5qLiRADRufnY 7gIAAA== Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 04:32:55 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2015, for work done in October through December. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at freebsd.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2014Q4 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2014-04-2014-06.html [5] http://www.freebsd.org/news/status/report-2014-07-2014-09.html From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 10:17:56 2014 Return-Path: Delivered-To: freebsd-hackers@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 97D7DDC8 for ; Tue, 9 Dec 2014 10:17:56 +0000 (UTC) Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D031D3E for ; Tue, 9 Dec 2014 10:17:56 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id eu11so295940pac.8 for ; Tue, 09 Dec 2014 02:17:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=tSOMnUL9Yeufg+mh03PK2OE//iuNbwwy8ghJX1Adtz4=; b=KPlXKS0be28LEl7w8dhGgnBIW/tML5odLXc9T+GwPvAJPz7klDceygcsQ0YlSUXF2L 4x4M+ZcnstDxxQMBCLx606F8vlR4oWRC9eDeiVtgDM/lE9MQkXYlFC5HsEAHdLJxs3sX Luhv+0/u0ckCNRZ2ArUQ/MRuCF0L0mntX0Jd7Cq1BGe1JfdjLrzSdhOFdVzyRc+4J4UM aurziRwtfvmcwenGj+DztYH+O5SPnAI1wjhZ/z5yOMe2ImIflo1Pyd5RTu1fMl9IaEtF 6qZyBB3LNoSxS4vi7C1JzbSW6gie05x8T3kSDBWsS+EA6iabGJMOJeY+6tlXHi/LoHKu GZRQ== X-Gm-Message-State: ALoCoQkFb4LFdyPAsp6eOJzEXWFjhOMSD8OWic8mQ75w0UjZ+3CK45+kLn4Q36EQ5xMBTw3yabl7 X-Received: by 10.70.134.197 with SMTP id pm5mr29180980pdb.72.1418120270669; Tue, 09 Dec 2014 02:17:50 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id pb6sm1082799pbb.13.2014.12.09.02.17.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Dec 2014 02:17:49 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <3125619.Pmuf3ojzUs@ralph.baldwin.cx> Date: Tue, 9 Dec 2014 02:17:47 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <4750778.kghJ8KRE21@ralph.baldwin.cx> <3125619.Pmuf3ojzUs@ralph.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.1993) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 10:17:56 -0000 > On Dec 8, 2014, at 10:32 AM, John Baldwin wrote: >=20 > On Saturday, December 06, 2014 01:37:09 PM Christopher R. Bowman = wrote: >> John, >> Its still sitting but I turned on verbose output and it's been = sitting for >> 10 minutes so far without any further output. Christopher. >=20 > Grrr, then it might be stuck elsewhere than the interrupt config = hooks. =20 > Unfortunately we'd really need to find a way to get into DDB. I think = GENERIC=20 > doesn't include BREAK_TO_DEBUGGER by default, so Ctrl-Alt-Esc doesn't = work out=20 > of the box. Can you break into the loader prompt and type 'set=20 > debug.kdb.break_to_debugger=3D1' before booting? Ctrl-Alt-Esc should = then work=20 > when it hangs. Once that happens, please get the output of 'ps' from = DDB. >=20 >> -- >> Christopher R. Bowman >>=20 >>> On Dec 5, 2014, at 7:20 AM, John Baldwin wrote: >>>=20 >>> On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman = wrote: >>>>> On Dec 4, 2014, at 8:39 AM, John Baldwin wrote: >>>>>> On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: >>>>>> Hi, >>>>>>=20 >>>>>> I'm not sure - it may be that the timekeeping stuff is a bit = confused. >>>>>> Maybe it's now time to file a bug and see if we can loop the >>>>>> timekeeping folk into it. >>>>>=20 >>>>> This is probably not timekeeping. That message is just the last = thing >>>>> printed before the interrupt-driven hooks are run. If you booted = a HEAD >>>>> snapshot the kernel should have DDB compiled in. Please drop into = DDB >>>>> using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with = the >>>>> output please. >>>>=20 >>>> John, >>>>=20 >>>> Thank you for responding. I tried that but the machine seemed = wedged >>>> at >>>>=20 >>>> that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc nor = can I do >>>> Ctrl-Alt-Del to reboot. All I can do it push the reset button. >>>> Christopher >>>=20 >>> If you let it sit for 60 seconds it should print out a message = telling you >>> what it is waiting on. >=20 >=20 > --=20 > John Baldwin John, I tried this twice on the off chance I typed it wrong once. = This had no effect. After letting the machine sit for 5 minutes there = was no further output or prompt. Doesn=E2=80=99t look like it dropped = into the debugger. Any more suggestion? Christopher From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 11:51:24 2014 Return-Path: Delivered-To: freebsd-hackers@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 61667E99 for ; Tue, 9 Dec 2014 11:51:24 +0000 (UTC) Received: from nm7-vm8.bullet.mail.ir2.yahoo.com (nm7-vm8.bullet.mail.ir2.yahoo.com [212.82.96.133]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A71C3998 for ; Tue, 9 Dec 2014 11:51:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1418125880; bh=xQVzJ2wIIkt6OupUArvt5VJ2PgG7MyC/QS+aRG5WU64=; h=Date:From:To:Subject:In-Reply-To:References:From:Subject; b=qCmhhI96xYmOWUfygPu7imMjME/Xulx6//UpFj0aihpFkMpzQFi2Ix5GR91O85v0ey7SxrKWMV2Gf0YPw2X/5OEw1/gNv1aJd4By6koGaXpcEKPyWs3V9mK0dDkrO9+CpFZ6aNgda5jZrq/Nx/K6cAyujFkfioA5idKvXDi+n2FXdvn73sB924JsixyMudhmMsCk8oO9TDojh0IGJHzvBVtk3mAJ5LuNJPQAGhIpKAJCQO7G4dORtvQzy+/hflZuR27p3ZCc/AYBhANkOvT4K0OM2Ksp/j4fWzXYQMoUzvLBMpma9peHHxUfLOJaKBgsjioK4neQ6YujeUm2uO1ibQ== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.es; b=MvaHbWOQbuy3mf03SXtKdCHpeoPlXVDtmUO0IemJTbz5xx9BIRDo4QzE/6CoYd/exlncM6yuYrONAwZyP/YzmXUL+URg6eHPa/qb/qid74kJWzag5Q/SjR6Bgh4d0zHT8iRsK0hJxp8I+iG9eRPaN2tcu7HkQ00XSmWLnHGgNT+JssQRv35+p/fyFS0cGqG8xU0gjrIbxB6OKeL1bRFDa4xvMdE4f3Agt3jQTBOE/JqnrXZcAViZIKg6WlJn5ZIPyUmKv9mAtG61yFlHf+LI5zX18A3VjHdxGRcixyJHBdRxrOfrucRPiSJ01OPi5Lal2tDEStWVEi0N0qXVqwmRlA==; Received: from [212.82.98.49] by nm7.bullet.mail.ir2.yahoo.com with NNFMP; 09 Dec 2014 11:51:20 -0000 Received: from [46.228.39.109] by tm2.bullet.mail.ir2.yahoo.com with NNFMP; 09 Dec 2014 11:51:20 -0000 Received: from [127.0.0.1] by smtp146.mail.ir2.yahoo.com with NNFMP; 09 Dec 2014 11:51:20 -0000 X-Yahoo-Newman-Id: 921707.18614.bm@smtp146.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Cac6wuIVM1nByitPZD_5P5dqASvPZArIKT.3rAJUfSpSRQD wJ5y_tYFCVe7MqV7ArMjbwucoDy_rqFgKP2m90ivOkWGBtr08J7r8PXYp1Bk ntotvAJIVoJGTjH0I1pn7T5mwZV_wC0IxQdoI0HI774GdfkqESimTnn6OUu6 LtMcUIfy0QW.YqY8mjT15M2XpGe50dfCWwS0tMbs3LeDXEMscOlJbOYVYsXS 37JxF_PDeKUjlZkXy.j_XhfwypwDMZIERJ7S2t7ax3eaJ_zEqfCFatCnSFht rRKYshOGWavLWqnpU7zKejaCejp1syb3isenkqIQdNUwPv9.Pm.Rzew.dLeu J2l5U8T3FR.Kx8vto3Bu.HwQeOtJdNaDSmFEuQWtrQhLMLw9iokRPT3T_kn_ n1Er_W3iYySIYAtrc9.aJxBwWbfJIXCuw0e9EjEAanMUGFR4610WVobLkRKp BmxQrg40t42Ve_tsxXAI_FqqFy_iIG9issbxEW83p901s6MtDb_DeMtPEDmg - X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Tue, 9 Dec 2014 12:51:27 +0100 From: Eduardo Morras To: freebsd-hackers@freebsd.org Subject: Re: 10.1 hangs during boot on Intel DP35DP board Message-Id: <20141209125127.eb6b7ce640d0d3d89cd8e1bb@yahoo.es> In-Reply-To: References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <4750778.kghJ8KRE21@ralph.baldwin.cx> <3125619.Pmuf3ojzUs@ralph.baldwin.cx> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 11:51:24 -0000 On Tue, 9 Dec 2014 02:17:47 -0800 "Christopher R. Bowman" wrote: > > John, > I tried this twice on the off chance I typed it wrong once. > This had no effect. After letting the machine sit for 5 minutes > there was no further output or prompt. Doesn’t look like it dropped > into the debugger. Any more suggestion? Christopher I'm not sure, please John or other developer confirm this, but 10.1 BETA or RC isos had all debug on. If this is true, you use them to investigate esasier this issue/bug. HTH --- --- Eduardo Morras From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 12:00:02 2014 Return-Path: Delivered-To: freebsd-hackers@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 C967830A; Tue, 9 Dec 2014 12:00:02 +0000 (UTC) Received: from server1.xenet.de (server1.xenet.de [213.221.94.201]) by mx1.freebsd.org (Postfix) with ESMTP id BB6F79E4; Tue, 9 Dec 2014 12:00:01 +0000 (UTC) Received: from [10.0.0.32] (intern.xenet.de [213.221.94.50]) (authenticated bits=0) by server1.xenet.de (8.12.5/8.12.5) with ESMTP id sB9BuC3q079363; Tue, 9 Dec 2014 12:56:14 +0100 (CET) (envelope-from meyser@xenet.de) Message-ID: <5486E432.2030809@xenet.de> Date: Tue, 09 Dec 2014 12:59:46 +0100 From: Matthias Meyser Organization: XeNET GmbH, Clausthal-Zellerfeld User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Garrett Cooper , Alfred Perlstein Subject: Re: Re: cross installing freebsd? References: <5483AE21.8090306@freebsd.org> <613884DA-F978-4D9F-9E37-D39581EFEA61@freebsd.org> <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> In-Reply-To: <26F569E9-3E70-4CE7-810F-5427FF1C7EA0@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.38 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 12:00:02 -0000 Hi Am 08.12.2014 um 11:04 schrieb Garrett Cooper: > On Dec 7, 2014, at 21:48, Alfred Perlstein wrote: [..] >> To be honest I have a gist as to what you're saying but I think the build is suffering from shibboleth-itis. Meaning it's not serviceable unless you're intimately familiar with it… > > Right. I didn’t know about all of these magic things until I started reading the Makefiles :). > >> I *guess* that ITOOLS or maybe LOCAL_ITOOLS means programs needed to installworld/installkernel? > > Yes. Basically for things that can be replaced while make installworld is run, or as Makefile.inc1 says… > > "# Required install tools to be saved in a scratch dir for safety.” > > All the libraries for the tools are backed up so if the tools get replaced while make distributeworld/installworld is running, your system won’t be hosed (that’s why make installworld works for me the majority of the time, if cp gets replaced and ABI changes — not always, but oftentimes). > >> If so, then yes, makewhatis needs to be added to that. The problem is that those tools are build for the HOST arch during crossbuilding. I don`t know if a version for TARGET arch is build also. The "right way" would be to to build these tools also for the TARGET arch (if not done already) and to teach the normal "install" to use them. - Matthias -- Matthias Meyser | XeNET GmbH Tel.: +49-5323-9489050 | 38678 Clausthal-Zellerfeld, Marktstrasse 40 Fax: +49-5323-9489059 | Registergericht: Amtsgericht Braunschweig HRB 110823 Email: Meyser@xenet.de | Geschaeftsfuehrer: Matthias Meyser From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 8 23:41:40 2014 Return-Path: Delivered-To: freebsd-hackers@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 BC6FE1D8; Mon, 8 Dec 2014 23:41:40 +0000 (UTC) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9C877214; Mon, 8 Dec 2014 23:41:40 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 6E5E75607B; Mon, 8 Dec 2014 17:41:39 -0600 (CST) Date: Mon, 8 Dec 2014 17:41:39 -0600 From: Mark Linimon To: Kirk McKusick Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? Message-ID: <20141208234139.GA13682@lonesome.com> References: <1479779318.56241253.1418076402148.JavaMail.root@his.com> <201412082240.sB8Mek7a065468@chez.mckusick.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201412082240.sB8Mek7a065468@chez.mckusick.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Tue, 09 Dec 2014 12:42:10 +0000 Cc: Garrett Cooper , FreeBSD Hackers , Erik Trulsson , Thomas Dickey , jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 23:41:40 -0000 On Mon, Dec 08, 2014 at 02:40:46PM -0800, Kirk McKusick wrote: > We can probably do without Kaypro and Radio Shack trs-80 and trs100 > support to name just three :-) POLA! mcl (do I _have_ to put the smiley?) From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 08:39:29 2014 Return-Path: Delivered-To: freebsd-hackers@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 4BF6B6A7; Tue, 9 Dec 2014 08:39:29 +0000 (UTC) Received: from cursor.its.uu.se (smtp-out1.uu.se [130.238.7.172]) (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 C9DF7BA; Tue, 9 Dec 2014 08:39:28 +0000 (UTC) Received: from e-mailfilter01.sunet.se (e-mailfilter01.sunet.se [192.36.171.201]) by cursor.its.uu.se (Postfix) with ESMTP id 4896845C; Tue, 9 Dec 2014 09:39:25 +0100 (CET) Received: from lyra.its.uu.se (lyra.its.uu.se [130.238.7.73]) by e-mailfilter01.sunet.se (8.14.4/8.14.4/Debian-4) with ESMTP id sB98dOR1012686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2014 09:39:25 +0100 Received: from virgata.its.uu.se (virgata.its.uu.se [130.238.7.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lyra.its.uu.se (Postfix) with ESMTPS id A4D3739116; Tue, 9 Dec 2014 09:39:24 +0100 (CET) X-DKIM: Sendmail DKIM Filter v2.8.3 lyra.its.uu.se A4D3739116 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uu.se; s=centralsmtp; t=1418114364; i=@uu.se; bh=hG6YEAl9jP5eQsQ8Yxcbkku65dBYAva41IBDo1+qs6g=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Ooqw8x/SXk8GIcKZm+bncTuUjSnqI+Su2lpTjM7I1t6p1xmlv1joQ6ccMo2Ci1dkk NwvQ0D9rkVND8kPB7iw6MHJQxF03KSH76M9VG3HUCTtEy0PALJCkxxMr0b0b/95Szs DDrPXs3MxYYx/EcKz247oVBj9BrmsNfS+4zIHHpY= Received: from jubula (localhost.localdomain [127.0.0.1]) by virgata.its.uu.se (8.13.8/8.13.8) with ESMTP id sB98dLhL029754; Tue, 9 Dec 2014 09:39:22 +0100 Received: from h-197-74.a213.corp.bahnhof.se (h-197-74.a213.corp.bahnhof.se [85.24.197.74]) by webmail.uu.se (Horde Framework) with HTTP; Tue, 09 Dec 2014 09:39:21 +0100 Message-ID: <20141209093921.10896xgn8zvjhbuh@webmail.uu.se> Date: Tue, 09 Dec 2014 09:39:21 +0100 From: Erik Trulsson To: Thomas Dickey Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? References: <1479779318.56241253.1418076402148.JavaMail.root@his.com> In-Reply-To: <1479779318.56241253.1418076402148.JavaMail.root@his.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, outbound-uu-se:default, uu-se:default, base:default, @@RPTN) X-Spam-Score: -0.10 () [Tag at 15.00] T_RP_MATCHES_RCVD:-0.1 X-p0f-Info: os=Linux 2.6.x, link=Ethernet or modem X-CanIt-Geo: ip=130.238.7.55; country=SE; region=Uppsala; city=Uppsala; latitude=59.8500; longitude=17.6333; http://maps.google.com/maps?q=59.8500,17.6333&z=6 X-CanItPRO-Stream: outbound-uu-se:outbound (inherits from outbound-uu-se:default, uu-se:default, base:default) X-Canit-Stats-ID: 09NpkDpgc - d16425ede68e - 20141209 X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?i=09NpkDpgc&m=d16425ede68e&t=20141209&c=f X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?i=09NpkDpgc&m=d16425ede68e&t=20141209&c=n X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?i=09NpkDpgc&m=d16425ede68e&t=20141209&c=s X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.36.171.201 X-Mailman-Approved-At: Tue, 09 Dec 2014 12:48:21 +0000 Cc: Kirk McKusick , FreeBSD Hackers , Garrett Cooper , jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 08:39:29 -0000 Quoting Thomas Dickey : > ----- Original Message ----- > | From: "Kirk McKusick" > | To: "Garrett Cooper" > | Cc: "Erik Trulsson" , "FreeBSD > Hackers" , > | jkh@freebsd.org, dickey@his.com > | Sent: Monday, December 8, 2014 11:51:37 AM > | Subject: Re: Reason for reordering /usr/share/misc/termcap.src for > /usr/share/misc/termcap ? > ... > | > | I believe Erik Trulsson's answer is correct. Termcap had grown very > | large and on sub-1-MIP computers took a noticable delay to read on > | every startup of programs using it. So, it was reordered to reduce > | the startup time on common terminals. As Erik points out this > | optimization > | is no longer necessary as termcap is now placed in a database. Not to > | mention that there are far fewer entries in it today than there were > | at the peak of its existence. > > Actually, the current file in the repository is 10% longer (4667 > lines vs 4007) than the first check-in. > Where might I find a larger example (of BSD termcap) such as you are > referring to? If you want to see an absolutely enormous version of termcap.src you can look at the one found inside https://ftp.gnu.org/gnu/termcap/termcap-1.3.1.tar.gz From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 09:04:52 2014 Return-Path: Delivered-To: hackers@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 E55BEF33; Tue, 9 Dec 2014 09:04:52 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (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 A2FFE3EF; Tue, 9 Dec 2014 09:04:52 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 6A4C66A6008; Tue, 9 Dec 2014 10:04:49 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id sB994ngG027516; Tue, 9 Dec 2014 10:04:49 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id sB994mip027265; Tue, 9 Dec 2014 10:04:48 +0100 (CET) (envelope-from lars) Date: Tue, 9 Dec 2014 10:04:48 +0100 From: Lars Engels To: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= Subject: Re: fstyp(8) Message-ID: <20141209090448.GF68024@e-new.0x20.net> References: <20141205114635.GA12557@brick.home> <20141208131107.GD68024@e-new.0x20.net> <02915D00-6415-4C9C-B841-7351B0886BC0@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pZtAG9wM4xcPQMtr" Content-Disposition: inline In-Reply-To: <02915D00-6415-4C9C-B841-7351B0886BC0@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p16 User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Tue, 09 Dec 2014 12:48:35 +0000 Cc: "hackers@FreeBSD.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 09:04:53 -0000 --pZtAG9wM4xcPQMtr Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 08, 2014 at 05:59:17PM +0100, Edward Tomasz Napiera=C5=82a wrot= e: > Dnia 8 gru 2014 o godz. 14:11 Lars Engels napisa= =C5=82(a): >=20 > >> On Fri, Dec 05, 2014 at 12:46:35PM +0100, Edward Tomasz Napiera=C5=82a= wrote: > >> I'm slowly working on making autofs suitable for mounting removable > >> media, and one of the things required is filesystem detection. It's > >> kind of possible to use file(1), but it's, well, "suboptimal" for this > >> task. So, I went and wrote fstyp(8). > >>=20 > >> This utility, named after SVR4 command with same weird name, detects > >> filesystems. It's mostly based on glabel code. The output is machine > >> parseable, it can print out filesystem labels, and runs capsicated. > >>=20 > >> You can join the review at https://reviews.freebsd.org/D1255. > >=20 > > Will it be possible to run "mount /dev/da$foo" without specifying a file > > system type? >=20 > No, but it's possible to run "mount -t `fstyp /dev/da$foo` /dev/da$foo > /mnt". Or, with upcoming "-media" autofs map, just "cd > /media/da$foo". Okay, that's a candidate for some shell alias then :) --pZtAG9wM4xcPQMtr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJUhrswXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tFFAH/ApFaVtA3K/PTrIHrzDHQZhZ HIPruEGyRb2VEH+LkznZrxSKiWLluHcbB9cW0ojdd21wNOQ3ms08d0TKhc34q9KF gz7L3tQnI4FU0jj63DVJAwJNVmxlJX84zvIAsjxOrfZ4yFNuRUWgcU/TaT6IDGm8 yzIsP8f7ru8Z4lcKW/cat7W0hFwyfItFrDbishE8drKOd8vPiDuhwADmzkL65e+1 mP0ynw8G231wo48C2b0PxetLGgdXTDiNgz6njVjQrx+x6192tpQAVaBG+038dnGZ lGt0TBv97WsSx7RyRLl4zg86o0CqiP/g/9S2bJsPVtUr+Gi0KosvZfrzJNyOKS8= =ftXf -----END PGP SIGNATURE----- --pZtAG9wM4xcPQMtr-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 09:10:18 2014 Return-Path: Delivered-To: freebsd-hackers@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 5C1F0153 for ; Tue, 9 Dec 2014 09:10:18 +0000 (UTC) Received: from smtp-nf-201.his.com (smtp-nf-201.his.com [216.194.251.34]) by mx1.freebsd.org (Postfix) with ESMTP id 1BABE622 for ; Tue, 9 Dec 2014 09:10:17 +0000 (UTC) Received: from cuda201.his.com (cuda201.his.com [216.194.248.226]) by smtp-nf-201.his.com (Postfix) with ESMTPS id E310962545 for ; Tue, 9 Dec 2014 04:10:15 -0500 (EST) X-ASG-Debug-ID: 1418116214-061c414fbe1b10f20001-P5m3U7 Received: from smtp-nf-202.his.com (smtp-nf-202.his.com [216.194.248.252]) by cuda201.his.com with ESMTP id fj3dIvbznEgnfzrG; Tue, 09 Dec 2014 04:10:14 -0500 (EST) X-Barracuda-Envelope-From: dickey@his.com X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.252 Received: from mail-sterling.his.com (mail-sterling.his.com [216.194.248.141]) by smtp-nf-202.his.com (Postfix) with ESMTP id C900F60081; Tue, 9 Dec 2014 04:10:14 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail-sterling.his.com (Postfix) with ESMTP id A7FD73F80004; Tue, 9 Dec 2014 04:10:13 -0500 (EST) X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.141 X-Virus-Scanned: amavisd-new at mail-sterling.his.com Received: from mail-sterling.his.com ([127.0.0.1]) by localhost (mail-sterling.his.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2zQtC4awZbs; Tue, 9 Dec 2014 04:10:10 -0500 (EST) Received: from mail-sterling.his.com (mail-sterling.his.com [216.194.248.141]) by mail-sterling.his.com (Postfix) with ESMTP id 1B1F03F80003; Tue, 9 Dec 2014 04:10:10 -0500 (EST) Date: Tue, 9 Dec 2014 04:10:09 -0500 (EST) From: Thomas Dickey To: Erik Trulsson Message-ID: <7932144.56345245.1418116209332.JavaMail.root@his.com> In-Reply-To: <20141209093921.10896xgn8zvjhbuh@webmail.uu.se> Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? MIME-Version: 1.0 X-ASG-Orig-Subj: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [71.178.218.187] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Mac)/7.2.6_GA_2926) X-Barracuda-Connect: smtp-nf-202.his.com[216.194.248.252] X-Barracuda-Start-Time: 1418116214 X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi Received-SPF: pass (his.com: domain of dickey@his.com designates 216.194.248.141 as permitted sender) X-Virus-Scanned: by bsmtpd at his.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.12649 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Mailman-Approved-At: Tue, 09 Dec 2014 12:48:52 +0000 Cc: Kirk McKusick , FreeBSD Hackers , Garrett Cooper , jkh@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 09:10:18 -0000 ----- Original Message ----- | From: "Erik Trulsson" | To: "Thomas Dickey" | Cc: "Kirk McKusick" , "FreeBSD Hackers" , jkh@freebsd.org, | "Garrett Cooper" | Sent: Tuesday, December 9, 2014 3:39:21 AM | Subject: Re: Reason for reordering /usr/share/misc/termcap.src for /usr/share/misc/termcap ? | | Quoting Thomas Dickey : | | > ----- Original Message ----- | > | From: "Kirk McKusick" | > | To: "Garrett Cooper" | > | Cc: "Erik Trulsson" , "FreeBSD | > Hackers" , | > | jkh@freebsd.org, dickey@his.com | > | Sent: Monday, December 8, 2014 11:51:37 AM | > | Subject: Re: Reason for reordering /usr/share/misc/termcap.src | > | for | > /usr/share/misc/termcap ? | > ... | > | | > | I believe Erik Trulsson's answer is correct. Termcap had grown | > | very | > | large and on sub-1-MIP computers took a noticable delay to read | > | on | > | every startup of programs using it. So, it was reordered to | > | reduce | > | the startup time on common terminals. As Erik points out this | > | optimization | > | is no longer necessary as termcap is now placed in a database. | > | Not to | > | mention that there are far fewer entries in it today than there | > | were | > | at the peak of its existence. | > | > Actually, the current file in the repository is 10% longer (4667 | > lines vs 4007) than the first check-in. | > Where might I find a larger example (of BSD termcap) such as you | > are | > referring to? | | If you want to see an absolutely enormous version of termcap.src you | can look at the one found inside | https://ftp.gnu.org/gnu/termcap/termcap-1.3.1.tar.gz | That's generated from ncurses (using the option to avoid multiple "tc=" clauses. It's also rather old, unmaintained and as such a nuisance on occasion. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 12:51:06 2014 Return-Path: Delivered-To: freebsd-hackers@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 0C3F5147 for ; Tue, 9 Dec 2014 12:51:06 +0000 (UTC) Received: from mail.myota.org (mail.myota.org [85.10.206.105]) by mx1.freebsd.org (Postfix) with ESMTP id 91704ED2 for ; Tue, 9 Dec 2014 12:51:05 +0000 (UTC) Received: from mobile.client (144.93.167.190.d.dyn.codetel.net.do [190.167.93.144] (may be forged)) (authenticated bits=128) by mail.myota.org (8.14.9/8.14.9) with ESMTP id sB9ComAc048832 for ; Tue, 9 Dec 2014 13:50:52 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: from submit.client ([127.0.0.1]) by schlappy.local (8.14.9/8.14.9) with ESMTP id sB9CoTE6001634; Tue, 9 Dec 2014 13:50:30 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: (from user@localhost) by schlappy.local (8.14.9/8.14.9/Submit) id sB9CoTPd001633; Tue, 9 Dec 2014 13:50:29 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Date: Tue, 9 Dec 2014 13:50:29 +0100 From: Andre Albsmeier To: freebsd-hackers@freebsd.org Subject: [Patch] Bring back ALT_BREAK_TO_DEBUGGER functionality to vt(4) Message-ID: <20141209125029.GA1568@schlappy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Echelon: Ortega, Secret, Compsec, 767, BND X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Not delayed on 85.10.206.105, ACL: AUTH(59), Origin: DO, OS: FreeBSD 9.x X-Virus-Scanned: clamav-milter 0.98.5 at colo X-Virus-Status: Clean X-Mailman-Approved-At: Tue, 09 Dec 2014 13:31:54 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 12:51:06 -0000 This is what I use to bring back ALT_BREAK_TO_DEBUGGER functionality to vt(4). The patch is against STABLE-9.3. --- ./vt_core.c.ORI 2014-07-22 17:29:27.000000000 +0200 +++ ./vt_core.c 2014-12-08 20:51:24.000000000 +0100 @@ -517,6 +517,9 @@ } #endif +#if defined(KDB) + kdb_alt_break( c, &vd->vd_altbrk ); +#endif terminal_input_char(vw->vw_terminal, KEYCHAR(c)); } else terminal_input_raw(vw->vw_terminal, c); --- ./vt.h.ORI 2014-04-07 19:06:41.000000000 +0200 +++ ./vt.h 2014-12-08 20:46:55.000000000 +0100 @@ -139,6 +139,7 @@ int vd_keyboard; /* (G) Keyboard index. */ unsigned int vd_kbstate; /* (?) Device unit. */ unsigned int vd_unit; /* (c) Device unit. */ + int vd_altbrk; /* (?) State for alt break sequence. */ }; /* Any comments? Something missing in order to get it committed? -Andre From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 16:31:25 2014 Return-Path: Delivered-To: freebsd-hackers@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 97C89893; Tue, 9 Dec 2014 16:31:25 +0000 (UTC) Received: from mailout08.t-online.de (mailout08.t-online.de [194.25.134.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45544C78; Tue, 9 Dec 2014 16:31:24 +0000 (UTC) Received: from fwd29.aul.t-online.de (fwd29.aul.t-online.de [172.20.26.134]) by mailout08.t-online.de (Postfix) with SMTP id 366C63D201F; Tue, 9 Dec 2014 17:31:17 +0100 (CET) Received: from [192.168.119.11] (rPv-QZZFohFrW2lVF9EQdwKGDKmp44SiBVF+wnD91hvzlBlFY3fBSSmhQ3FFpfgw9D@[84.154.99.91]) by fwd29.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XyNgv-1lgaWm0; Tue, 9 Dec 2014 17:31:13 +0100 Message-ID: <548723D0.1000402@freebsd.org> Date: Tue, 09 Dec 2014 17:31:12 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Phil Shafer Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) References: <201412082114.sB8LEJnR056654@idle.juniper.net> In-Reply-To: <201412082114.sB8LEJnR056654@idle.juniper.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-ID: rPv-QZZFohFrW2lVF9EQdwKGDKmp44SiBVF+wnD91hvzlBlFY3fBSSmhQ3FFpfgw9D X-TOI-MSGID: 2f660d45-0b17-4d14-8393-93d0ac8c343c Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 16:31:25 -0000 Am 08.12.2014 um 22:14 schrieb Phil Shafer: > Stefan Esser writes: >> D1206 on reviews.freebsd.org (https://reviews.freebsd.org/D1206). > > Patch looks good. Some nits: Hi Phil, thanks again for your effort to help me understand libxo! > The names for xo_open_list and xo_open_instance need to be > identical, so: > >> @@ -554,9 +698,14 @@ >> /* Walk the capability list. */ >> express = 0; >> ptr = read_config(fd, &p->pc_sel, ptr, 1); >> + xo_open_list("capabilities"); > > should be: > > xo_open_list("capability"); > > to match: > >> + xo_open_instance("capability"); I just re-read the man-page for xo_list_open() and it clearly says: "The name given to all calls must be identical, and it is strong suggested that the name be singular, not plural, [...]", which I had wrongly understood to only relate to opening and closing of elements. I had noticed, that the parameter of xo_open_list() is printed as the array name in JSON, while the parameter of xo_open_instance() is used as the element name in XML - it seemed more natural to use the plural for the array name ... (and I had not noticed the sentence I quoted above). > Similar for: > >> + xo_open_list("extended-capabilities"); >> ... >> + xo_open_list("error-categories"); >> ... >> + xo_open_list("base-addresses"); Yes, there were even more, I have fixed them in my local version (not yet uploaded to the reviews site). > If you turn on the warn flag, you should get these issues reported > (--libox=warn). This did not work for me - --libxo=warn generates no output at all for these examples. >> + xo_emit("{:name/unknown}"); > > Should "name" be "capibility-name", to be consistent? Fixed, thanks. > Add some point the printf calls need to be removed. Sure, I just wanted to keep them around in the sources until those capabilities that I do not know and cannot test have received a review (especially Hyper threading specific information). I'm afraid that there will be requests to change quite a number of field labels, once this patch is committed to -CURRENT and I really hope for other interested parties to > It would be great to see some example xml, json, and html output for this > command, pretty printed of course. I have uploaded sample output (with the link/instance names fixed according to your review): https://people.freebsd.org/~se/pciconf-lbcevV.tar.bz2 I'm afraid that the verboseness is quite high and that some fields are poorly named. OTOH, I'd love to see the output generated on an AMD64 system with HyperThreading information. (Offätopic: is it possible to attach such information to the review on Phabricator? I noticed that due to the markup language used, it is hard to put structured information into comments. Marking as text that should not be interpreted as markup did not work when I tried it ...). BTW, a few remarks and questions regarding libxo: It seems, that libxo/xo.h depends on stdio.h (or at least stdarg.h) for functions that use FILE or varargs. This is not mentioned in the respective man-pages for the affected functions (and I think it should be ...). Is there a description of the rules, which decide whether quotes are put around JSON formatted information elements. It seems, for example, that use of %d in format strings suppresses quotes, which was unexpected, if the format is e.g. "xyz%d" (which is a string, despite the %d ...). And formatted output that contains blanks within the field is probably also a string (even "%d %d", hmmm, but "%d.%d" might be a number ...). But I have to admit, that I do not really know the rules for quotes around data fields in JSON. (E.g. must I write "true" to represent a string value of "true", or could I also use true without quotes to represent a truth value? What do parsers do if there are unquoted words or words separated by blanks?) Are there any plans for a versioning scheme for XO extended programs. E.g. if I need to change some of the elements or labels in pciconf, how do I include the information about the file schema being the old or the new one in an output file. I could f.i. just add an xo_emit(":e/schema-version/1") at the head of the file, to make the file format version explicit in the generated output ... (Or rather: is there a concept how to let a parser know which XML schema to expect when looking at some input file, if the schema has been changed over time?) Thank you for the time to review my attempt to grok libxo! When pciconf is ready, I'll have a look at other tools that could be improved by adding XO support ... (and I hope I'll be fluent in XO and will not require as much support ;-) ) Best regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 16:45:28 2014 Return-Path: Delivered-To: freebsd-hackers@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 CE0DE1AE; Tue, 9 Dec 2014 16:45:28 +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 714F4DDD; Tue, 9 Dec 2014 16:45:28 +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 sB9GjGW4030174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2014 18:45:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua sB9GjGW4030174 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id sB9GjGha030172; Tue, 9 Dec 2014 18:45:16 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 9 Dec 2014 18:45:16 +0200 From: Konstantin Belousov To: Stefan Esser Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) Message-ID: <20141209164516.GB97072@kib.kiev.ua> References: <201412082114.sB8LEJnR056654@idle.juniper.net> <548723D0.1000402@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <548723D0.1000402@freebsd.org> 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-hackers@freebsd.org" , Phil Shafer X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 16:45:29 -0000 On Tue, Dec 09, 2014 at 05:31:12PM +0100, Stefan Esser wrote: > Am 08.12.2014 um 22:14 schrieb Phil Shafer: > > Stefan Esser writes: > >> D1206 on reviews.freebsd.org (https://reviews.freebsd.org/D1206). > > > > Patch looks good. Some nits: > > Hi Phil, > > thanks again for your effort to help me understand libxo! > > > The names for xo_open_list and xo_open_instance need to be > > identical, so: > > > >> @@ -554,9 +698,14 @@ > >> /* Walk the capability list. */ > >> express = 0; > >> ptr = read_config(fd, &p->pc_sel, ptr, 1); > >> + xo_open_list("capabilities"); > > > > should be: > > > > xo_open_list("capability"); > > > > to match: > > > >> + xo_open_instance("capability"); > > I just re-read the man-page for xo_list_open() and it clearly says: > > "The name given to all calls must be identical, and it is strong > suggested that the name be singular, not plural, [...]", which I had > wrongly understood to only relate to opening and closing of elements. If it is required that the name be identical, it makes more sense to require some handle to be passed to functions instead of the string. I.e. either there should be some atom-like calls which convert string to identifier, or first call should return handle passed to consequent calls. This is obviously a note WRT libxo interface, not your patch. > > I had noticed, that the parameter of xo_open_list() is printed as > the array name in JSON, while the parameter of xo_open_instance() is > used as the element name in XML - it seemed more natural to use the > plural for the array name ... (and I had not noticed the sentence I > quoted above). > > > Similar for: > > > >> + xo_open_list("extended-capabilities"); > >> ... > >> + xo_open_list("error-categories"); > >> ... > >> + xo_open_list("base-addresses"); > > Yes, there were even more, I have fixed them in my local version > (not yet uploaded to the reviews site). .... > OTOH, I'd love to see the output generated on an AMD64 system > with HyperThreading information. There are no AMD processors which support HyperThreading. I suspect you mean HyperTransport there. Any relatively modern AMD CPU, in particular, all chips capable of running amd64, use hypertransport for northbridge. Look at netperf cluster for available resources, there are several AMD machines there https://wiki.freebsd.org/TestClusterOneReservations From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 9 20:29:47 2014 Return-Path: Delivered-To: freebsd-hackers@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 39284D6A; Tue, 9 Dec 2014 20:29:47 +0000 (UTC) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF8F0F25; Tue, 9 Dec 2014 20:29:46 +0000 (UTC) Received: from fwd00.aul.t-online.de (fwd00.aul.t-online.de [172.20.26.147]) by mailout07.t-online.de (Postfix) with SMTP id CB6623B3233; Tue, 9 Dec 2014 21:29:37 +0100 (CET) Received: from [192.168.119.11] (XRjRnYZcYhd0ZAadUUwtDsdVFx3UeKYoLa-KkFq-FLnP25S5r3VUwjEPqQvWDX2ZLv@[84.154.99.91]) by fwd00.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XyRPV-0s1Yjw0; Tue, 9 Dec 2014 21:29:29 +0100 Message-ID: <54875BA8.1040600@freebsd.org> Date: Tue, 09 Dec 2014 21:29:28 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) References: <201412082114.sB8LEJnR056654@idle.juniper.net> <548723D0.1000402@freebsd.org> <20141209164516.GB97072@kib.kiev.ua> In-Reply-To: <20141209164516.GB97072@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: XRjRnYZcYhd0ZAadUUwtDsdVFx3UeKYoLa-KkFq-FLnP25S5r3VUwjEPqQvWDX2ZLv X-TOI-MSGID: 581de69a-ff26-4f42-b43b-b788b0caea44 Cc: "freebsd-hackers@freebsd.org" , Phil Shafer X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 20:29:47 -0000 Am 09.12.2014 um 17:45 schrieb Konstantin Belousov: > On Tue, Dec 09, 2014 at 05:31:12PM +0100, Stefan Esser wrote: >> Am 08.12.2014 um 22:14 schrieb Phil Shafer: >>> Stefan Esser writes: >>>> D1206 on reviews.freebsd.org (https://reviews.freebsd.org/D1206). >>> >>> Patch looks good. Some nits: >> >> Hi Phil, >> >> thanks again for your effort to help me understand libxo! >> >>> The names for xo_open_list and xo_open_instance need to be >>> identical, so: >>> >>>> @@ -554,9 +698,14 @@ >>>> /* Walk the capability list. */ >>>> express = 0; >>>> ptr = read_config(fd, &p->pc_sel, ptr, 1); >>>> + xo_open_list("capabilities"); >>> >>> should be: >>> >>> xo_open_list("capability"); >>> >>> to match: >>> >>>> + xo_open_instance("capability"); >> >> I just re-read the man-page for xo_list_open() and it clearly says: >> >> "The name given to all calls must be identical, and it is strong >> suggested that the name be singular, not plural, [...]", which I had >> wrongly understood to only relate to opening and closing of elements. > If it is required that the name be identical, it makes more sense > to require some handle to be passed to functions instead of the string. > I.e. either there should be some atom-like calls which convert string > to identifier, or first call should return handle passed to consequent > calls. > > This is obviously a note WRT libxo interface, not your patch. Use of handles could help with other aspects of the conversion, too. (E.g. to build several trees of information in parallel and then flush them to output as several lists in some specified order - I have, there is one loop in pciconf that prints 3 kinds of data as text that need to be separated for structured output, for example). Such sub-tree handles could also simplify the task of converting for libxo (modelled after DOM based XML generators, instead of the current SAX like style). The "handles" that exist in libxo serve a different purpose and allow e.g. several independent output streams to be written to by a single program. But the current interface "as is" is very regular with regard to the parameters passed and the xolint tool really helps to identify bad format strings and other mistakes that are hard to spot, otherwise. [...] >> OTOH, I'd love to see the output generated on an AMD64 system >> with HyperThreading information. > There are no AMD processors which support HyperThreading. I suspect you > mean HyperTransport there. Any relatively modern AMD CPU, in particular, > all chips capable of running amd64, use hypertransport for northbridge. Yes, sure, I meant HyperTransport (and spelled it that way in the patch). I do not have any AMD systems to test on (but I have an old nForce 630a/7050 mainboard and all parts to reconstruct a working AMD64 X2 (AM2) system, ... but not this week). > Look at netperf cluster for available resources, there are several > AMD machines there > https://wiki.freebsd.org/TestClusterOneReservations Thank you for the pointer - I'll ask for test access (I'll need root access, albeit only for a few minutes) to a suitable machine in the cluster, next week. Best regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 10 03:16:42 2014 Return-Path: Delivered-To: freebsd-hackers@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 39B679CD for ; Wed, 10 Dec 2014 03:16:42 +0000 (UTC) Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09064170 for ; Wed, 10 Dec 2014 03:16:41 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id rd3so1899109pab.0 for ; Tue, 09 Dec 2014 19:16:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:mime-version:subject :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=i3UJxS96ZZ5+YIQJKb04Tz2xGpL7fumBH271pJw8HYE=; b=ZnjYbHl9iSnYogSRn0LCK9XyLpsqhAMoICXzOLX9vp3tIU8vBjmndERRHrTmDqjjWa Rz5IK7Ds8oRTvtaGdpnTIbKl3HcBxxIrynyAzRj6OgxnPcMTEvVdngW5ftxfBI++0D80 udAudaXULFou/bRoUDC3M19gQR1f1cpSNk0ryOnG1z/N2cx43PWMZJ18fOHMTENGyBda ovOq1xFO0NDXmyyxD0jjr2zIyz8XR/+EXfu92/WrubFtDqE9h3od1R5mxpYTuLLknnhe PkJDDSjb/qqNMHYG9A5xT/lj6Jc34B9FaovmhCz0GTkot1UP7SkR20H0ZjnjOdKUh2BD oNzg== X-Gm-Message-State: ALoCoQldnc4EXHs0uvlurFbZHhcDPk+EKxt9bwQK2av1rSGPoL6x85MuhZNHs/FcJZ3HhMvK2dKV X-Received: by 10.68.202.1 with SMTP id ke1mr2714402pbc.139.1418181394778; Tue, 09 Dec 2014 19:16:34 -0800 (PST) Received: from macbookpro.chrisbowman.com (c-67-180-23-235.hsd1.ca.comcast.net. [67.180.23.235]) by mx.google.com with ESMTPSA id xq4sm2718786pbb.21.2014.12.09.19.16.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Dec 2014 19:16:34 -0800 (PST) From: "Christopher R. Bowman" X-Google-Original-From: "Christopher R. Bowman" Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: 10.1 hangs during boot on Intel DP35DP board In-Reply-To: <20141209125127.eb6b7ce640d0d3d89cd8e1bb@yahoo.es> Date: Tue, 9 Dec 2014 19:16:31 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <37E85A4C-0755-4655-8DA2-F65B9769D44D@ChrisBowman.com> References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <4750778.kghJ8KRE21@ralph.baldwin.cx> <3125619.Pmuf3ojzUs@ralph.baldwin.cx> <20141209125127.eb6b7ce640d0d3d89cd8e1bb@yahoo.es> To: Eduardo Morras X-Mailer: Apple Mail (2.1993) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 03:16:42 -0000 > On Dec 9, 2014, at 3:51 AM, Eduardo Morras wrote: >=20 > On Tue, 9 Dec 2014 02:17:47 -0800 > "Christopher R. Bowman" wrote: >=20 >>=20 >> John, >> I tried this twice on the off chance I typed it wrong once. >> This had no effect. After letting the machine sit for 5 minutes >> there was no further output or prompt. Doesn=E2=80=99t look like it = dropped >> into the debugger. Any more suggestion? Christopher >=20 > I'm not sure, please John or other developer confirm this, but 10.1 = BETA or RC isos had all debug on. If this is true, you use them to = investigate esasier this issue/bug. >=20 > HTH >=20 > --- --- > Eduardo Morras > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" Eduardo, I=E2=80=99ll try this, but where can I download a 10.1 RC image. = I couldn=E2=80=99t find one any more now that 10.1 is out. Christopher From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 10 09:07:33 2014 Return-Path: Delivered-To: freebsd-hackers@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 AA8BB432; Wed, 10 Dec 2014 09:07:33 +0000 (UTC) Received: from work.netasq.com (gwlille.netasq.com [91.212.116.1]) by mx1.freebsd.org (Postfix) with ESMTP id 4224EF28; Wed, 10 Dec 2014 09:07:32 +0000 (UTC) Received: from work.netasq.com (localhost.localdomain [127.0.0.1]) by work.netasq.com (Postfix) with ESMTP id EF92E270061A; Wed, 10 Dec 2014 10:01:23 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by work.netasq.com (Postfix) with ESMTP id AE22D2700619; Wed, 10 Dec 2014 10:01:23 +0100 (CET) Received: from work.netasq.com ([127.0.0.1]) by localhost (work.netasq.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YOa_3iliha_N; Wed, 10 Dec 2014 10:01:23 +0100 (CET) Received: from work.netasq.com (localhost.localdomain [127.0.0.1]) by work.netasq.com (Postfix) with ESMTP id 02C24270058F; Wed, 10 Dec 2014 10:01:23 +0100 (CET) Date: Wed, 10 Dec 2014 10:01:22 +0100 (CET) From: Arnaud YSMAL To: freebsd-hackers@FreeBSD.org, freebsd-net@FreeBSD.org Message-ID: <536944673.989749.1418202082741.JavaMail.zimbra@stormshield.eu> In-Reply-To: <940402442.797031.1418139811947.JavaMail.zimbra@stormshield.eu> Subject: Issue with the number of jumbo frames after tweaking MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_989747_1238867947.1418202082738" Thread-Topic: Issue with the number of jumbo frames after tweaking Thread-Index: VHAByctDNs4/l+fzuLMGJ731D9+uYw== Cc: damien.deville@stormshield.eu, andre@FreeBSD.org, Fabien THOMAS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 09:07:33 -0000 ------=_Part_989747_1238867947.1418202082738 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, Using sysctl to set a new value to kern.ipc.nmbjumbo9 or kern.ipc.nmbjumbo16 leads to a wrong value. This appears in FreeBSD 9.3 with the revision 254515 (https://svnweb.freebsd.org/base?view=revision&revision=254515) which MFC the revision 243631. The values are respectively 3 and 4 times bigger than expected. Example on a FreeBSD 9.3 (amd64): # sysctl kern.ipc.nmbjumbo9=224000 kern.ipc.nmbjumbo9: 223263 -> 672000 The sysctls functions in sys/kern/kern_mbuf.c got the new value from the uma_zone_set_max (sys/vm/uma_core.c) function. It looks like the formula used in uma_core.c to compute the number of items based on the number of pages is not always the same (uk_ppera is sometimes missing). In the enclosed patch I assumed that the correct formula to compute the number of items is: (pages / uk_ppera) * uk_ipers Is it normal that in these sysctls the comparison between nmbufs and the sum of jumbos + clusters (added in the same revision) does not use the new value requested by the user? Arnaud ------=_Part_989747_1238867947.1418202082738 Content-Type: text/x-patch; name=uma_core.patch Content-Disposition: attachment; filename=uma_core.patch Content-Transfer-Encoding: base64 LS0tIHN5cy92bS91bWFfY29yZS5jLm9yaWcJMjAxNC0xMi0wOSAxNDoxODoyNy4wMDAwMDAwMDAg KzAwMDAKKysrIHN5cy92bS91bWFfY29yZS5jCTIwMTQtMTItMDkgMTQ6NDc6NTMuMDAwMDAwMDAw ICswMDAwCkBAIC0xNDE2LDcgKzE0MTYsNyBAQAogCXByaW50ZigiVU1BOiAlcyglcCkgc2l6ZSAl ZCglZCkgZmxhZ3MgJSN4IGlwZXJzICVkIHBwZXJhICVkIG91dCAlZCBmcmVlICVkXG4iLAogCSAg ICB6b25lLT51el9uYW1lLCB6b25lLCBrZWctPnVrX3NpemUsIGtlZy0+dWtfcnNpemUsIGtlZy0+ dWtfZmxhZ3MsCiAJICAgIGtlZy0+dWtfaXBlcnMsIGtlZy0+dWtfcHBlcmEsCi0JICAgIChrZWct PnVrX2lwZXJzICoga2VnLT51a19wYWdlcykgLSBrZWctPnVrX2ZyZWUsIGtlZy0+dWtfZnJlZSk7 CisJICAgIChrZWctPnVrX3BhZ2VzIC8ga2VnLT51a19wcGVyYSkgKiBrZWctPnVrX2lwZXJzICAt IGtlZy0+dWtfZnJlZSwga2VnLT51a19mcmVlKTsKICNlbmRpZgogCiAJTElTVF9JTlNFUlRfSEVB RCgma2VnLT51a196b25lcywgem9uZSwgdXpfbGluayk7CkBAIC0yODQ3LDE2ICsyODQ3LDE5IEBA CiB1bWFfem9uZV9zZXRfbWF4KHVtYV96b25lX3Qgem9uZSwgaW50IG5pdGVtcykKIHsKIAl1bWFf a2VnX3Qga2VnOworCWludCBybml0ZW1zOwogCiAJWk9ORV9MT0NLKHpvbmUpOwogCWtlZyA9IHpv bmVfZmlyc3Rfa2VnKHpvbmUpOwogCWtlZy0+dWtfbWF4cGFnZXMgPSAobml0ZW1zIC8ga2VnLT51 a19pcGVycykgKiBrZWctPnVrX3BwZXJhOwotCWlmIChrZWctPnVrX21heHBhZ2VzICoga2VnLT51 a19pcGVycyA8IG5pdGVtcykKKwlybml0ZW1zID0gKGtlZy0+dWtfbWF4cGFnZXMgLyBrZWctPnVr X3BwZXJhKSAqIGtlZy0+dWtfaXBlcnM7CisJaWYgKHJuaXRlbXMgPCBuaXRlbXMpIHsKIAkJa2Vn LT51a19tYXhwYWdlcyArPSBrZWctPnVrX3BwZXJhOwotCW5pdGVtcyA9IGtlZy0+dWtfbWF4cGFn ZXMgKiBrZWctPnVrX2lwZXJzOworCQlybml0ZW1zKys7CisJfQogCVpPTkVfVU5MT0NLKHpvbmUp OwogCi0JcmV0dXJuIChuaXRlbXMpOworCXJldHVybiAocm5pdGVtcyk7CiB9CiAKIC8qIFNlZSB1 bWEuaCAqLwpAQCAtMjg2OCw3ICsyODcxLDcgQEAKIAogCVpPTkVfTE9DSyh6b25lKTsKIAlrZWcg PSB6b25lX2ZpcnN0X2tlZyh6b25lKTsKLQluaXRlbXMgPSBrZWctPnVrX21heHBhZ2VzICoga2Vn LT51a19pcGVyczsKKwluaXRlbXMgPSAoa2VnLT51a19tYXhwYWdlcyAvIGtlZy0+dWtfcHBlcmEp ICoga2VnLT51a19pcGVyczsKIAlaT05FX1VOTE9DSyh6b25lKTsKIAogCXJldHVybiAobml0ZW1z KTsKQEAgLTMxNTYsNyArMzE1OSw3IEBACiAJICAgICJvdXQgJWQgZnJlZSAlZCBsaW1pdCAlZFxu IiwKIAkgICAga2VnLT51a19uYW1lLCBrZWcsIGtlZy0+dWtfc2l6ZSwga2VnLT51a19yc2l6ZSwg a2VnLT51a19mbGFncywKIAkgICAga2VnLT51a19pcGVycywga2VnLT51a19wcGVyYSwKLQkgICAg KGtlZy0+dWtfaXBlcnMgKiBrZWctPnVrX3BhZ2VzKSAtIGtlZy0+dWtfZnJlZSwga2VnLT51a19m cmVlLAorCSAgICAoa2VnLT51a19wYWdlcyAvIGtlZy0+dWtfcHBlcmEpICoga2VnLT51a19pcGVy cyAtIGtlZy0+dWtfZnJlZSwga2VnLT51a19mcmVlLAogCSAgICAoa2VnLT51a19tYXhwYWdlcyAv IGtlZy0+dWtfcHBlcmEpICoga2VnLT51a19pcGVycyk7CiAJcHJpbnRmKCJQYXJ0IHNsYWJzOlxu Iik7CiAJTElTVF9GT1JFQUNIKHNsYWIsICZrZWctPnVrX3BhcnRfc2xhYiwgdXNfbGluaykK ------=_Part_989747_1238867947.1418202082738-- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 10 19:36:01 2014 Return-Path: Delivered-To: freebsd-hackers@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 8E6B7C1C; Wed, 10 Dec 2014 19:36:01 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0112.outbound.protection.outlook.com [65.55.169.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2B87907; Wed, 10 Dec 2014 19:36:00 +0000 (UTC) Received: from CO2PR05CA031.namprd05.prod.outlook.com (10.141.241.159) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 19:35:58 +0000 Received: from BN1BFFO11FD054.protection.gbl (2a01:111:f400:7c10::1:113) by CO2PR05CA031.outlook.office365.com (2a01:111:e400:1429::31) with Microsoft SMTP Server (TLS) id 15.1.31.17 via Frontend Transport; Wed, 10 Dec 2014 19:35:58 +0000 Received: from P-EMF03-SAC.jnpr.net (66.129.239.17) by BN1BFFO11FD054.mail.protection.outlook.com (10.58.145.9) with Microsoft SMTP Server (TLS) id 15.1.26.17 via Frontend Transport; Wed, 10 Dec 2014 19:35:57 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF03-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 10 Dec 2014 11:35:37 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id sBAJZZR16670; Wed, 10 Dec 2014 11:35:35 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.4/8.14.3) with ESMTP id sBAJZL5I076079; Wed, 10 Dec 2014 14:35:21 -0500 (EST) (envelope-from phil@idle.juniper.net) Message-ID: <201412101935.sBAJZL5I076079@idle.juniper.net> To: Konstantin Belousov Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) In-Reply-To: <20141209164516.GB97072@kib.kiev.ua> Date: Wed, 10 Dec 2014 14:35:21 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:66.129.239.17; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(164054003)(64706001)(47776003)(120916001)(87936001)(20776003)(103666002)(97736003)(21056001)(105596002)(69596002)(84676001)(48376002)(50466002)(46102003)(6806004)(107046002)(53416004)(92566001)(86362001)(76506005)(110136001)(1411001)(4396001)(31966008)(50986999)(54356999)(81156004)(106466001)(99396003)(62966003)(77156002)(68736005)(77096005)(15975445007); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB443; H:P-EMF03-SAC.jnpr.net; FPR:; SPF:SoftFail; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601002); SRVR:CO1PR05MB443; X-Forefront-PRVS: 0421BF7135 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.17 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.17) smtp.mailfrom=phil@juniper.net; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:CO1PR05MB443; X-OriginatorOrg: juniper.net X-Mailman-Approved-At: Wed, 10 Dec 2014 19:56:12 +0000 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 19:36:01 -0000 Konstantin Belousov writes: >If it is required that the name be identical, it makes more sense >to require some handle to be passed to functions instead of the string. >I.e. either there should be some atom-like calls which convert string >to identifier, or first call should return handle passed to consequent >calls. The library supports "do the right thing" mode, where it records the open tag value and doesn't need the user to provide it: http://juniper.github.io/libxo/libxo-manual.html#dtrt-mode I could enable this by default and use it when NULL is passed for an instance name. Thanks, Phil From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 10 20:33:44 2014 Return-Path: Delivered-To: freebsd-hackers@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 10F35D05; Wed, 10 Dec 2014 20:33:44 +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 DB59AEF8; Wed, 10 Dec 2014 20:33:43 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D9F6EB91E; Wed, 10 Dec 2014 15:33:42 -0500 (EST) From: John Baldwin To: "Christopher R. Bowman" Subject: Re: 10.1 hangs during boot on Intel DP35DP board Date: Wed, 10 Dec 2014 15:33:25 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <1dbd10028e6466adac4d5c10cf7e099d4fe035c1@webmailnew.optuszoo.com.au> <3125619.Pmuf3ojzUs@ralph.baldwin.cx> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201412101533.25855.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 10 Dec 2014 15:33:42 -0500 (EST) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Tony Maher X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 20:33:44 -0000 On Tuesday, December 09, 2014 5:17:47 am Christopher R. Bowman wrote: >=20 > > On Dec 8, 2014, at 10:32 AM, John Baldwin wrote: > >=20 > > On Saturday, December 06, 2014 01:37:09 PM Christopher R. Bowman wrote: > >> John, > >> Its still sitting but I turned on verbose output and it's been sitting= =20 for > >> 10 minutes so far without any further output. Christopher. > >=20 > > Grrr, then it might be stuck elsewhere than the interrupt config hooks.= =20 > > Unfortunately we'd really need to find a way to get into DDB. I think= =20 GENERIC=20 > > doesn't include BREAK_TO_DEBUGGER by default, so Ctrl-Alt-Esc doesn't w= ork=20 out=20 > > of the box. Can you break into the loader prompt and type 'set=20 > > debug.kdb.break_to_debugger=3D1' before booting? Ctrl-Alt-Esc should t= hen=20 work=20 > > when it hangs. Once that happens, please get the output of 'ps' from D= DB. > >=20 > >> -- > >> Christopher R. Bowman > >>=20 > >>> On Dec 5, 2014, at 7:20 AM, John Baldwin wrote: > >>>=20 > >>> On Thursday, December 04, 2014 07:42:48 PM Christopher R. Bowman wrot= e: > >>>>> On Dec 4, 2014, at 8:39 AM, John Baldwin wrote: > >>>>>> On Wednesday, December 03, 2014 9:36:01 am Adrian Chadd wrote: > >>>>>> Hi, > >>>>>>=20 > >>>>>> I'm not sure - it may be that the timekeeping stuff is a bit=20 confused. > >>>>>> Maybe it's now time to file a bug and see if we can loop the > >>>>>> timekeeping folk into it. > >>>>>=20 > >>>>> This is probably not timekeeping. That message is just the last th= ing > >>>>> printed before the interrupt-driven hooks are run. If you booted a= =20 HEAD > >>>>> snapshot the kernel should have DDB compiled in. Please drop into = DDB > >>>>> using Ctrl-Alt-Esc and then run 'show conifhk' and reply here with = the > >>>>> output please. > >>>>=20 > >>>> John, > >>>>=20 > >>>> Thank you for responding. I tried that but the machine seemed wed= ged > >>>> at > >>>>=20 > >>>> that point. I can=E2=80=99t drop into DDB using Ctrl-Alt-Esc nor ca= n I do > >>>> Ctrl-Alt-Del to reboot. All I can do it push the reset button. > >>>> Christopher > >>>=20 > >>> If you let it sit for 60 seconds it should print out a message tellin= g=20 you > >>> what it is waiting on. > >=20 > >=20 > > --=20 > > John Baldwin >=20 >=20 > John, > I tried this twice on the off chance I typed it wrong once. This had no= =20 effect. After letting the machine sit for 5 minutes there was no further=20 output or prompt. Doesn=E2=80=99t look like it dropped into the debugger. = Any more=20 suggestion? Can you trigger an NMI? Perhaps remotely via IPMI? (I'm not sure if that'= s=20 even feasible in the IPMI spec.) Barring break_to_debugger, that's the onl= y=20 other thing I'm aware of. Another option might be to compile a custom kern= el=20 with 'options KTR', 'options KTR_VERBOSE', 'options KTR_COMPILE=3DKTR_PROC'= and=20 'options KTR_MASK=3DKTR_PROC' and boot that. If the machine is truly hung = it=20 will still hang. If you can point the machine at a serial console and log = the=20 output, that would be good if it doesn't really hang but is sitting idle. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 10 20:36:52 2014 Return-Path: Delivered-To: freebsd-hackers@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 2F48EE0F; Wed, 10 Dec 2014 20:36:52 +0000 (UTC) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0113.outbound.protection.outlook.com [157.56.110.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D227FF24; Wed, 10 Dec 2014 20:36:51 +0000 (UTC) Received: from BN1PR05MB437.namprd05.prod.outlook.com (10.141.58.11) by BN1PR05MB278.namprd05.prod.outlook.com (10.141.64.147) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 20:36:49 +0000 Received: from BY2PR05CA033.namprd05.prod.outlook.com (10.141.250.23) by BN1PR05MB437.namprd05.prod.outlook.com (10.141.58.11) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 20:36:48 +0000 Received: from BY2FFO11FD016.protection.gbl (2a01:111:f400:7c0c::110) by BY2PR05CA033.outlook.office365.com (2a01:111:e400:2c5f::23) with Microsoft SMTP Server (TLS) id 15.1.31.17 via Frontend Transport; Wed, 10 Dec 2014 20:36:47 +0000 Received: from P-EMF03-SAC.jnpr.net (66.129.239.17) by BY2FFO11FD016.mail.protection.outlook.com (10.1.14.148) with Microsoft SMTP Server (TLS) id 15.1.26.17 via Frontend Transport; Wed, 10 Dec 2014 20:36:47 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF03-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 10 Dec 2014 12:36:45 -0800 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id sBAJVKR14747; Wed, 10 Dec 2014 11:31:21 -0800 (PST) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.4/8.14.3) with ESMTP id sBAJV7uk076028; Wed, 10 Dec 2014 14:31:07 -0500 (EST) (envelope-from phil@idle.juniper.net) Message-ID: <201412101931.sBAJV7uk076028@idle.juniper.net> To: Stefan Esser Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) In-Reply-To: <548723D0.1000402@freebsd.org> Date: Wed, 10 Dec 2014 14:31:07 -0500 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:66.129.239.17; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(164054003)(199003)(189002)(87936001)(110136001)(50466002)(86362001)(50986999)(54356999)(69596002)(103666002)(62966003)(450100001)(77156002)(6806004)(48376002)(31966008)(4396001)(92566001)(84676001)(46102003)(68736005)(64706001)(47776003)(20776003)(97736003)(77096005)(120916001)(99396003)(76506005)(53416004)(105596002)(15975445007)(106466001)(21056001)(81156004)(107046002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR05MB437; H:P-EMF03-SAC.jnpr.net; FPR:; SPF:SoftFail; MLV:sfv; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en; X-Microsoft-Antispam: UriScan:;UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB437; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(9)(10); SRVR:BN1PR05MB437; X-Forefront-PRVS: 0421BF7135 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.17 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.17) smtp.mailfrom=phil@juniper.net; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB437; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1PR05MB278; X-OriginatorOrg: juniper.net X-Mailman-Approved-At: Wed, 10 Dec 2014 21:47:41 +0000 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2014 20:36:52 -0000 Stefan Esser writes: >It seems, that libxo/xo.h depends on stdio.h (or at least >stdarg.h) for functions that use FILE or varargs. This is >not mentioned in the respective man-pages for the affected >functions (and I think it should be ...). I'll fix that. >Is there a description of the rules, which decide whether >quotes are put around JSON formatted information elements. >It seems, for example, that use of %d in format strings >suppresses quotes, which was unexpected, if the format is >e.g. "xyz%d" (which is a string, despite the %d ...). >And formatted output that contains blanks within the field >is probably also a string (even "%d %d", hmmm, but "%d.%d" >might be a number ...). http://juniper.github.io/libxo/libxo-manual.html#the-quotes-modifier-q Quotes default to on for strings, off for others. >But I have to admit, that I do not really know the rules for >quotes around data fields in JSON. (E.g. must I write "true" >to represent a string value of "true", or could I also use >true without quotes to represent a truth value? What do >parsers do if there are unquoted words or words separated >by blanks?) JSON uses "true", "false", and "null" (without quotes) as unquoted tokens. If you want a boolean, you'll need: xo_emit("{n:valid/%s}", valid ? "true" : "false"); >Are there any plans for a versioning scheme for XO extended >programs. E.g. if I need to change some of the elements or >labels in pciconf, how do I include the information about the >file schema being the old or the new one in an output file. >I could f.i. just add an xo_emit(":e/schema-version/1") at >the head of the file, to make the file format version explicit >in the generated output ... No plans. In practice, your tags become an API, and changes to that API require an attitude of "don't break your users". Most users won't check versioning information. Please let me know what's unclear from the docs and I'll try to improve them. Thanks, Phil From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 12 15:34:32 2014 Return-Path: Delivered-To: freebsd-hackers@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 1A33F374 for ; Fri, 12 Dec 2014 15:34:32 +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 E5688988 for ; Fri, 12 Dec 2014 15:34:31 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4CDF4B98C; Fri, 12 Dec 2014 10:34:30 -0500 (EST) From: John Baldwin To: Mike Gelfand Subject: Re: [BUG] Getting path to program binary sometimes fails Date: Fri, 12 Dec 2014 10:33:59 -0500 Message-ID: <3715296.8JkIjC2VMR@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <27C465FC-E8C7-44CB-A812-65213BB8AC9F@logicnow.com> References: <91809230-5E81-4A6E-BFD6-BE8815A06BB2@logicnow.com> <2066750.N3TZpYSHCy@ralph.baldwin.cx> <27C465FC-E8C7-44CB-A812-65213BB8AC9F@logicnow.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); Fri, 12 Dec 2014 10:34:30 -0500 (EST) Cc: Konstantin Belousov , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 15:34:32 -0000 On Friday, December 05, 2014 03:52:41 PM Mike Gelfand wrote: > On Dec 5, 2014, at 6:19 PM, John Baldwin wrote: > >> No, not NFS but ZFS. Could that be an issue? The FreeBSD 8 machine I > >> mentioned before has UFS. > >> > >> Also, as you can see from the video I recorded (and from the code I > >> provided), path resolution succeeds and fails within fractions of a > >> second > >> after process startup. > > > > Are you seeing vnodes being actively recycled? In particular, do you see > > vfs.numvnodes close to kern.maxvnodes? You can try raising > > kern.maxvnodes. > > If vfs.numvnodes grows up to the limit then as long as you can stomach the > > RAM of having more vnodes around that would increase the changes of your > > paths remaining valid. > > When the call works, sysctl returns: > vfs.numvnodes: 59638 > kern.maxvnodes: 204723 > The times it doesn't, the output is: > vfs.numvnodes: 60017 > kern.maxvnodes: 204723 > I've selected maximum numbers. Monitoring was made with > while sysctl vfs.numvnodes kern.maxvnodes; do sleep 0.1; done > > So it seems that's not related, correct? 60K is much less than 200K. Yes. Unfortunately, we don't expose a raw counter for vnode recycling (I should really add one). I think we might also purge unused vnodes if we have too many "free" vnodes. However, directories that aren't currently open by a process (meaning via opendir()) count as "unused", so are subject to purging. You can try increasing "vfs.wantfreevnodes". Also, please try this patch. It just adds a counter for recycled vnodes. If this value increases during your test then it does show that recycling is occurring. If it doesn't, then that rules it out. Index: vfs_subr.c =================================================================== --- vfs_subr.c (revision 275512) +++ vfs_subr.c (working copy) @@ -156,6 +156,10 @@ static int vlru_allow_cache_src; SYSCTL_INT(_vfs, OID_AUTO, vlru_allow_cache_src, CTLFLAG_RW, &vlru_allow_cache_src, 0, "Allow vlru to reclaim source vnode"); +static u_long recycles_count; +SYSCTL_ULONG(_vfs, OID_AUTO, recycles, CTLFLAG_RW, &recycles_count, 0, + "Number of vnodes recycled"); + /* * Various variables used for debugging the new implementation of * reassignbuf(). @@ -988,6 +992,7 @@ vtryrecycle(struct vnode *vp) __func__, vp); return (EBUSY); } + atomic_add_long(&recycles_count, 1); if ((vp->v_iflag & VI_DOOMED) == 0) vgonel(vp); VOP_UNLOCK(vp, LK_INTERLOCK); -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 13 08:21:22 2014 Return-Path: Delivered-To: freebsd-hackers@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 69B248BD; Sat, 13 Dec 2014 08:21:22 +0000 (UTC) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1711D9DB; Sat, 13 Dec 2014 08:21:21 +0000 (UTC) Received: from fwd13.aul.t-online.de (fwd13.aul.t-online.de [172.20.27.62]) by mailout12.t-online.de (Postfix) with SMTP id AB8F0304128; Sat, 13 Dec 2014 09:21:12 +0100 (CET) Received: from [192.168.119.11] (bN6MtsZBoh6Q6GsrbZ6uWxSB3eEUB6U8OCBeTQAP+gkr6ZSYVtW8SFYTlYPusdWZvX@[84.154.99.91]) by fwd13.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1Xzhwr-2ogjJY0; Sat, 13 Dec 2014 09:21:09 +0100 Message-ID: <548BF6EF.2090504@freebsd.org> Date: Sat, 13 Dec 2014 09:21:03 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Phil Shafer Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) References: <201412101931.sBAJV7uk076028@idle.juniper.net> In-Reply-To: <201412101931.sBAJV7uk076028@idle.juniper.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-ID: bN6MtsZBoh6Q6GsrbZ6uWxSB3eEUB6U8OCBeTQAP+gkr6ZSYVtW8SFYTlYPusdWZvX X-TOI-MSGID: 0778b85e-33ee-4700-be1a-149277f48d12 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 08:21:22 -0000 Am 10.12.2014 um 20:31 schrieb Phil Shafer: > Stefan Esser writes: >> It seems, that libxo/xo.h depends on stdio.h (or at least >> stdarg.h) for functions that use FILE or varargs. This is >> not mentioned in the respective man-pages for the affected >> functions (and I think it should be ...). > > I'll fix that. Hi Phil, one more nit: The man page for xo_open_container seems to be truncated (no "ADDITIONAL DOCUMENTATION", "SEE ALSO", ...). And I did not find any documenation of DTRT in the man pages, but only in the HTML docs (in a somewhat hidden place, since you need to know it is below "Representing Hierarchy" ...). >> Is there a description of the rules, which decide whether >> quotes are put around JSON formatted information elements. >> It seems, for example, that use of %d in format strings >> suppresses quotes, which was unexpected, if the format is >> e.g. "xyz%d" (which is a string, despite the %d ...). >> And formatted output that contains blanks within the field >> is probably also a string (even "%d %d", hmmm, but "%d.%d" >> might be a number ...). > > http://juniper.github.io/libxo/libxo-manual.html#the-quotes-modifier-q > > Quotes default to on for strings, off for others. Yes, that's what I had expected. But in fact I needed to put quite a few "q:" or "n:" to get the JSON output correctly quoted. I'll see that I create a file with a few test cases. >> But I have to admit, that I do not really know the rules for >> quotes around data fields in JSON. (E.g. must I write "true" >> to represent a string value of "true", or could I also use >> true without quotes to represent a truth value? What do >> parsers do if there are unquoted words or words separated >> by blanks?) > > JSON uses "true", "false", and "null" (without quotes) > as unquoted tokens. If you want a boolean, you'll need: > > xo_emit("{n:valid/%s}", valid ? "true" : "false"); Hmmm, but what will the "reader" of the JSON file expect? Is it good practice to have libxo output booleans instead of strings, if these are the only possible values? Will a JSON parser automatically convert them to strings, if an unquoted true or false is read and a strings is expected? (Sorry, I have bno experience with JSON parsers ...) >> Are there any plans for a versioning scheme for XO extended >> programs. E.g. if I need to change some of the elements or >> labels in pciconf, how do I include the information about the >> file schema being the old or the new one in an output file. >> I could f.i. just add an xo_emit(":e/schema-version/1") at >> the head of the file, to make the file format version explicit >> in the generated output ... > > No plans. In practice, your tags become an API, and changes > to that API require an attitude of "don't break your users". > Most users won't check versioning information. While it is probably true, that most users do not want to check for different format versions, I think there should be a canonical way to provide such information. I have thought about putting around the pciconf output, just to let people know, that the format is expected to change until I understand the semantics of all fields (e.g. in the PCIe (extended) capabilities section). > Please let me know what's unclear from the docs and I'll > try to improve them. Thanks, I'll do. Best regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 13 11:18:53 2014 Return-Path: Delivered-To: hackers@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 2D509911 for ; Sat, 13 Dec 2014 11:18:53 +0000 (UTC) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.12]) (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 D8574B5B for ; Sat, 13 Dec 2014 11:18:52 +0000 (UTC) Received: from mbpro2-w.bs.cs.huji.ac.il ([132.65.179.21]) by kabab.cs.huji.ac.il with esmtp id 1XzkbE-0001AR-7u for hackers@freebsd.org; Sat, 13 Dec 2014 13:11:00 +0200 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: latest wireshark core dumps Message-Id: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> Date: Sat, 13 Dec 2014 13:11:00 +0200 To: hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 11:18:53 -0000 hi all, I just compiled from ports wireshark et.all on a virgin 10.1-stable, and it=E2=80=99c coredumping on startup, any hints? thanks, danny From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 13 11:59:29 2014 Return-Path: Delivered-To: freebsd-hackers@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 A57C1C9; Sat, 13 Dec 2014 11:59:29 +0000 (UTC) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51E28EA0; Sat, 13 Dec 2014 11:59:28 +0000 (UTC) Received: from fwd27.aul.t-online.de (fwd27.aul.t-online.de [172.20.26.132]) by mailout06.t-online.de (Postfix) with SMTP id 9EE0328E1F6; Sat, 13 Dec 2014 12:59:19 +0100 (CET) Received: from [192.168.119.11] (Vah5x2ZHZhYwE2r1G1Zlgi2jNilRoZpwoMcQ-NlpPxvFl8dz7B1f0YKKLXUvT-kQ7H@[84.154.99.91]) by fwd27.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XzlLs-4GWDsu0; Sat, 13 Dec 2014 12:59:12 +0100 Message-ID: <548C2A0A.8090908@freebsd.org> Date: Sat, 13 Dec 2014 12:59:06 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Phil Shafer , Konstantin Belousov Subject: Suggestion of higher level libxo API (in addition to current one) References: <201412101935.sBAJZL5I076079@idle.juniper.net> In-Reply-To: <201412101935.sBAJZL5I076079@idle.juniper.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit X-ID: Vah5x2ZHZhYwE2r1G1Zlgi2jNilRoZpwoMcQ-NlpPxvFl8dz7B1f0YKKLXUvT-kQ7H X-TOI-MSGID: 67f0a246-b9f8-4e52-bd02-a70aaffbe872 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2014 11:59:29 -0000 Am 10.12.2014 um 20:35 schrieb Phil Shafer: > Konstantin Belousov writes: >> If it is required that the name be identical, it makes more sense >> to require some handle to be passed to functions instead of the string. >> I.e. either there should be some atom-like calls which convert string >> to identifier, or first call should return handle passed to consequent >> calls. > > The library supports "do the right thing" mode, where it records > the open tag value and doesn't need the user to provide it: > > http://juniper.github.io/libxo/libxo-manual.html#dtrt-mode > > I could enable this by default and use it when NULL is passed for > an instance name. Hi Phil, I've thought a lot about this over the last days. Based on my experience with the conversion of pciconf, which was not written with XML or JSON output in mind and which outputs quite complex data structures, I have started to wonder whether a different concept might be easier to use for the programmer. I think it is possible to provide a different API that can co-exist with the current functions. First what I think the current libxo API provides: The API is very low-level in the sense, that every call generates (at most) one XML or JSON element, and it generates it the moment the call is made. xo_open_list: writes JSON label and starts array with "[{", no output for XML xo_open_instance: ignored for JSON, starts sub-tree within given element for XML xo_open_container: writes label and opening "{", starts sub-tree within given element for XML xo_emit: writes label and value for XML, creates element with given value I'm not describing the xo_close_* functions, but they just emit the syntactically required closing tags or brackets/braces. Use of this API leads to the following code to print error information (which is suppressed in the output, if there are no errors to report, which is the normal case). --------------------------------------------------------------------- static int errors; static void print_header(const char *header) { if (errors++ == 0) xo_open_list("error-category"); xo_open_instance("error-category"); xo_emit("{:category/%14s} = ", header); } static void print_bits(const char *header, struct bit_table *table, uint32_t mask) { int first; first = 1; for (; table->desc != NULL; table++) if (mask & table->mask) { if (first) { print_header(header); xo_open_list("detected-error"); first = 0; } else xo_emit(" "); xo_open_instance("detected-error"); xo_emit("{:description/%s}\n", table->desc); xo_close_instance("error"); mask &= ~table->mask; } if (!first) xo_close_list("detected-error"); if (mask != 0) { if (first) { print_header(header); first = 0; } else xo_emit(" "); xo_emit("Unknown: {:unknown-errors-bitmask/0x%08x}\n", mask); } if (!first) xo_close_instance("error-category"); if (errors != 0) xo_close_list("error-category"); } --------------------------------------------------------------------- Maybe I'm doing things wrong, but I had to use two state variables to control the correct printing of opening and closing tags ("first" was in the non-libxo version, "errors" was added just for libxo). I have to be careful to explicitly record state and to close any of the containers/lists that I open. This could have been much easier to write, if the libxo API was more abstract ("higher level") and printing of XML elements was decoupled from xo_XXX calls. The semantics of xo_open_{list,instance,container} is, that a new level in the tree structure is created, and everything following that call is in the new level, until the corresponding xo_close_*() is called. I'd rather want to describe the structure in a different way, for which I'm using an example syntax: xo_start_instance(instance_name): Creates a new instance *at the same level* as the previous one, the previous one is automatically closed (if any is open). If this is the first list/array item, an xo_open_list with the same name as that of the instance is implied. This call is thus equivalent to (pseudo-code using Python style indenting): if IN_SOME_CONTAINER() xo_close_container_d() if NOT_IN_LIST(instance_name) if IN_SOME_LIST() xo_close_list_d() xo_open_list(instance_name) if INSTANCE_IS_OPEN(instance_name) xo_close_instance(instance_name) xo_open_instance(instance_name) xo_start_container(container_name): Starts a new container at the same level as the previous one, closing any currently open container or list. if IN_SOME_LIST() if IN_SOME_INSTANCE() xo_close_instance_d() xo_close_list_d() if IN_SOME_CONTAINER() xo_close_container_d() xo_open_container() xo_start_level(debug_name): Starts a new sub-tree (which is implicitly done by xo_open_*). No output is generated, except that a previously open container or instance is implicitly closed. The previous state is kept on a stack and will become visible after the corresponding xo_end_level() is called. The debug_name is optional and just there to be checked to match the one passed to a corresponding xo_finish_level(debug_name). if IN_SOME_LIST() or IN_SOME_CONTAINER() close_* xo_push_state() xo_finish_level(): Close all open instances and containers and finish the sub-tree, restore the state before the previous xo_start_level(). if IN_SOME_LIST() or IN_SOME_CONTAINER() close_* xo_pop_state() The following call sequences should generate identical output, with indentation reflecting "pretty" XML: xo_open_container("group1"); xo_open_container("subgroup1"); xo_emit("{:label1/value}"); xo_emit("{:label2/value}"); xo_close_container("subgroup1"); xo_open_list("array1") xo_open_instance("array1"); xo_emit("{:array1-label1/value}"); xo_emit("{:array1-label2/value}"); xo_close_instance("array1"); xo_open_instance("array1"); xo_emit("{:array1-label1/value}"); xo_emit("{:array1-label2/value}"); xo_close_instance("array1"); xo_close_list("array1"); xo_emit("{:label3/value}"); xo_close_container("group1"); value value value value value value value With the xo_start_* functions I'd use the following for the same output: xo_start_container("group1"); xo_start_group(""); // (*1*) xo_start_container("subgroup1"); xo_emit("{:label1/value}"); xo_emit("{:label2/value}"); xo_start_instance("array1"); xo_emit("{:array1-label1/value}"); xo_emit("{:array1-label2/value}"); xo_start_instance("array1"); xo_emit("{:array1-label1/value}"); xo_emit("{:array1-label2/value}"); xo_finish_group(""); xo_emit("{:label3/value}"); (*1*) If no new "group" was started, then the next container would be at the same level in the tree, i.e. would be closed before is opened. All the xo_close can be implied, and I do not have to remember, if an opening tag has been written. The closing tags ore braces are always generated as required. This syntax can express everything that is formally correct with the xo_open/xo_close calls. E.g. it automatically places xo_open_list() around instances - and the names are required to match for the well formed cases anyway. The only "complication" is, that I'd need to put xo_start_group() and xo_finish_group() calls around the output for a sub-tree, else the generated data structure will be "flat". There is also no risk of run-away data structures, due to the omitting of closing tags. This can easily be taken care of by start/finish_group. If there is a subroutine that emits XML/JSON data into a sub-tree, then just wrap the commands in this sub-routine in xo_start_group(func_name) and xo_stop_group(func_name) - the arguments are not used to generate any output, just to generate debug output if XOF_WARN is set. The calls I suggest are more similar to the JSON output generated than to the XML output (which is similar structured to xo_open/close_*). I am convinced, that the libxo API that I propose simplifies use of libxo. It is higher level in the sense, that it is more decoupled from the generated output. In fact, it allows for semantic extensions, that could further simplify use of libxo: 1) If there is no call to xo_emit() within a container or instance, the tags for the container/instance could be omitted. That would allow to always call xo_start_container, before testing for any data to actually put into that container. In the example code from pciconf that I quoted above, that could remove the need for the helper function, if xo_optional_emit() was introduced as a variant of xo_emit(), that is only written if any regular xo_emit() is also printed into the same container. 2) I have seen cases, where list instances are created out of order by the non-libxo code, and to adapt that code to libxo, the loop has to be completely rewritten (leading to different output than before for the XO_TEXT case). This could be fixed with xo_start_instance(), if all the instances were collected between xo_start_group() to xo_finish_group() and all the JSON array structures were only written with all collected instances when the xo_close_container() implied by xo_finish_group() is called. This would allow the following code: xo_start_instance("array1"); xo_emit(array1-label/value1); xo_start_instance("array2"); xo_emit(array2-label/value2); xo_start_instance("array1"); xo_emit(array1-label/value3); leading to the following JSON output: array1 [ { array1-label: value1 } { array1-label: value3 } ], array2 [ { array2-label: value2 } ] This is of course also possible with xo_open/xo_close, but as soon you start to dissociate these calls from the output (by delaying the output), you could as well use the xo_start_* variants I suggest ... Anyway, except for the badly chosen name "xo_optional_emit()" (which as described above is for data, that should be omitted if there is no xo_emit() within the same container/instance, I think this is a workable API for libxo, which just spares the programmer from working as if he was directly writing XML output (with the addition of xo_open_list(), which in fact is ignored for XML and just required for JSON). The two APIs could be mixed with each other, if the semantics of xo_open_* and xo_start_* were aligned. E.g. any xo_open_list() after a xo_start_container/instance would just be interpreted as xo_start_group(); xo_start_list(); xo_finish_group(); and similar for containers (instances are only allowed inside lists and are thus covered by the wrapping of xo_start_list() shown above). It is obvious that it is not possible to specify xo_open*() via xo_start and xo_start via xo_open without generating cyclic dependencies, but the real implementation could be either way (with emulation of xo_open via xo_start being the simpler case, since it only requires the wrapping with xo_start_group). Here is the example code from above with the xo_start API: --------------------------------------------------------------------- static void print_bits(const char *header, struct bit_table *table, uint32_t mask) { int first; xo_start_group("print_bits1"); // just a debug label xo_start_instance("error-category"); first = 1; for (; table->desc != NULL; table++) if (mask & table->mask) { if (first) { xo_emit("{:category/%14s} = ", header); xo_start_group("print_bits2"); first = 0; } else xo_emit(" "); xo_start_instance("detected-error"); xo_emit("{:description/%s}\n", table->desc); mask &= ~table->mask; } if (mask != 0) { if (first) { xo_emit("{:category/%14s} = ", header); xo_start_group("print_bits2"); first = 0; } else xo_emit(" "); xo_emit("Unknown: {:unknown-errors-bitmask/0x%08x}\n", mask); } if (!first) xo_finish_group("print_bits2"); xo_finish_group("print_bits1"); } --------------------------------------------------------------------- (While doing the conversion, I noticed that there might be a bug in the call sequence of my code quoted in the first example with xo_open API, which I had not spotted before.) The above example is not only shorter, the diff against the non-libxo version is also significantly smaller and easier to understand and review. I'm open to further discussion and I understand, that it is important to not void effort put in code that uses xo_open*(). But I'd really love to be able to use a higher-level API and I think what I suggested fits the bill ;-) Best regards, STefan