From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 14 16:03:00 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 2B5DDE1; Sun, 14 Dec 2014 16:03:00 +0000 (UTC) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailhost.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E4B69DF9; Sun, 14 Dec 2014 16:02:59 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id EF7E1B806E; Sun, 14 Dec 2014 17:02:56 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id DCE7828494; Sun, 14 Dec 2014 17:02:56 +0100 (CET) Date: Sun, 14 Dec 2014 17:02:56 +0100 From: Jilles Tjoelker To: Stefan Esser Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) Message-ID: <20141214160256.GB84077@stack.nl> References: <201412101931.sBAJV7uk076028@idle.juniper.net> <548BF6EF.2090504@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <548BF6EF.2090504@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) 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: Sun, 14 Dec 2014 16:03:00 -0000 On Sat, Dec 13, 2014 at 09:21:03AM +0100, Stefan Esser wrote: > Am 10.12.2014 um 20:31 schrieb Phil Shafer: > > Stefan Esser writes: > >> 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 ...) It depends on which JSON parser. Each parser and language has its own rules about type conversion. Some examples: When using JavaScript JSON.parse, JavaScript's type conversion rules will apply when using the deserialized data. These will never implicitly convert a string "true" or "false" to a boolean true or false (both of them will convert to true because they are non-empty). A boolean will be converted to a string "true" or "false" when appropriate. Likewise, when using Python json module, Python's type conversion rules will apply when using the deserialized data. These will generally allow few implicit conversions, but as in JavaScript any non-empty string will be considered true by control flow statements. Explicit conversion of a boolean to a string gives "True" or "False"; something like "true" if v else "false" is needed to get the lowercase values. Jansson (C library) and Android's JsonReader do not convert any types at all. If multiple types are acceptable, the caller will have to handle it. JSONObject (Java, from json.org or in Android) will convert a string "true" or "false" from and to a boolean true or false when it is requested as such type. Summarizing, a boolean will be easiest to use if it is serialized as a JSON boolean. If you do not want to use a JSON boolean for some reason, a number 0 (false) or 1 (true) will still be easier and safer than a string "false" or "true". -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 14 19:13: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 5EF06842; Sun, 14 Dec 2014 19:13:06 +0000 (UTC) Received: from mailout01.t-online.de (mailout01.t-online.de [194.25.134.80]) (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 E4B8C25A; Sun, 14 Dec 2014 19:13:05 +0000 (UTC) Received: from fwd16.aul.t-online.de (fwd16.aul.t-online.de [172.20.26.243]) by mailout01.t-online.de (Postfix) with SMTP id 2857D1728C4; Sun, 14 Dec 2014 20:12:57 +0100 (CET) Received: from [192.168.119.26] (XjoVo0Z68h2UYTIRtz+2kcX5R979xjCQ71FsMNmArv97RdCeGIl3Mnlf1OWiHRNgYp@[84.154.99.91]) by fwd16.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1Y0Eb9-1KhJvU0; Sun, 14 Dec 2014 20:12:55 +0100 Message-ID: <548DE134.8040501@freebsd.org> Date: Sun, 14 Dec 2014 20:12:52 +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: Jilles Tjoelker , Stefan Esser Subject: Re: [Patch] updated: Add JSON and XML output to pciconf (libxo support - D1206) References: <201412101931.sBAJV7uk076028@idle.juniper.net> <548BF6EF.2090504@freebsd.org> <20141214160256.GB84077@stack.nl> In-Reply-To: <20141214160256.GB84077@stack.nl> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: XjoVo0Z68h2UYTIRtz+2kcX5R979xjCQ71FsMNmArv97RdCeGIl3Mnlf1OWiHRNgYp X-TOI-MSGID: fd8699b8-e9a6-4c85-913c-2787072bc14d 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: Sun, 14 Dec 2014 19:13:06 -0000 Am 14.12.2014 um 17:02 schrieb Jilles Tjoelker: > On Sat, Dec 13, 2014 at 09:21:03AM +0100, Stefan Esser wrote: >> Am 10.12.2014 um 20:31 schrieb Phil Shafer: >>> Stefan Esser writes: >>>> 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 ...) > > It depends on which JSON parser. Each parser and language has its own > rules about type conversion. Some examples: > > When using JavaScript JSON.parse, JavaScript's type conversion rules > will apply when using the deserialized data. These will never implicitly > convert a string "true" or "false" to a boolean true or false (both of > them will convert to true because they are non-empty). A boolean will be > converted to a string "true" or "false" when appropriate. > > Likewise, when using Python json module, Python's type conversion rules > will apply when using the deserialized data. These will generally allow > few implicit conversions, but as in JavaScript any non-empty string will > be considered true by control flow statements. Explicit conversion of a > boolean to a string gives "True" or "False"; something like > "true" if v else "false" > is needed to get the lowercase values. > > Jansson (C library) and Android's JsonReader do not convert any types at > all. If multiple types are acceptable, the caller will have to handle > it. > > JSONObject (Java, from json.org or in Android) will convert a string > "true" or "false" from and to a boolean true or false when it is > requested as such type. > > Summarizing, a boolean will be easiest to use if it is serialized as a > JSON boolean. If you do not want to use a JSON boolean for some reason, > a number 0 (false) or 1 (true) will still be easier and safer than a > string "false" or "true". Hi Jilles, thanks a lot for the explanation! I'll change all pciconf output to use true/false without quotes, then. This seems to be the best compromise (looks good in XML and JSON when directly reading the output, can be parsed as XML and JSON). @Phil: I think this information makes a good candidate for the libxo documentation (at least I did not see, that it is already mentioned). Best regards, Stefan From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 15 19:05:20 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 1E5F3F25 for ; Mon, 15 Dec 2014 19:05:20 +0000 (UTC) Received: from caprica.ketralnis.com (caprica.ketralnis.com [184.73.185.184]) (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 E75BC9D2 for ; Mon, 15 Dec 2014 19:05:19 +0000 (UTC) Received: from [10.0.15.252] (108-60-121-46.static.wiline.com [108.60.121.46]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: dking) by caprica.ketralnis.com (Postfix) with ESMTPSA id EA5C11BACEF; Mon, 15 Dec 2014 10:57:41 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_5E55121A-A4A8-4C52-BC50-86D914C3FBEE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: latest wireshark core dumps From: David King In-Reply-To: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> Date: Mon, 15 Dec 2014 10:57:37 -0800 Message-Id: <7926BAAA-EA43-447C-B3EE-A3130695E05F@ketralnis.com> References: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> To: Daniel Braniss X-Mailer: Apple Mail (2.1878.6) 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, 15 Dec 2014 19:05:20 -0000 --Apple-Mail=_5E55121A-A4A8-4C52-BC50-86D914C3FBEE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 What does the backtrace say? Something like this: $ gdb $(which wireshark) ... it prints run some stuff ... type "run" ... it prints run some stuff, then dies where it would normally dump = core ... type "bt" On 13 Dec 2014, at 03:11, Daniel Braniss wrote: > hi all, > I just compiled from ports wireshark et.all on a virgin 10.1-stable, > and it=92c coredumping on startup, any hints? >=20 > thanks, > danny >=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" --Apple-Mail=_5E55121A-A4A8-4C52-BC50-86D914C3FBEE 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----- iQIcBAEBAgAGBQJUjy8jAAoJEFrLaEb73Smz2DIP/jIVMw6Z7M+qcFAB/E+D8yt3 IvJkS3Pv/sEtmtM9y2q/sJCK8TIgZ6tHGQxX4pM+Ris6GZRj2EcjuzL9Ds88wT6P Lv4LvhB3BFQvRvq7euBre/kI3jHkzSSUUopzT1o31q7VjiLzC6wY5ZmN3BRt+84X dBeCf8R03DpWdiHwOLytWlwSpt/ngRr3Qwv4Ygx91W1WyUAWUQJAiJxS8+mJGMzR 3PI/Uy/zxRQMieQ1z2CZev4xP0D65hiznjD8dVPDeM/3o55gzag/zmwaZCEDRhQM tQJp9ibA7RprlwZPjNuFE7+pA/ntsPK6u5L49r/eSDhM7pkFy33bcC3BHx5pjB27 OdfQaMEvxFxnv97bJ5CFdsed7dDChwPib1Jbc1yZWVtdwcIoS7Lq1Tpx17sxmD+v 9Q44Sda6k0yZ3JhXB5qCldZyFGXwmRdEq4vUOUzjuG4jm7h6SikUw1GA5y8T6iCw TM0Ho0jEqXo6gL9A8WhadWIU/FG5zTes+s+KWO3eQJwTclzs3KGALZvXUKZrTk/P yOOw10hpCO4KNLK1J+5XTa5xyz0RAH73il66it3LRVvDtjUk2x6+2kvrdZqKILR6 zPEh/KViLaEIwy5jflgPtc6vKNGu3Kar3J9UYDKP3UmXzLVqGLEYNuwRkCsjibKN sK1S8eMYdjNRCfylP3el =7mSK -----END PGP SIGNATURE----- --Apple-Mail=_5E55121A-A4A8-4C52-BC50-86D914C3FBEE-- From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 15 23:49:58 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 D9D59253 for ; Mon, 15 Dec 2014 23:49:58 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.201]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6CC8E78 for ; Mon, 15 Dec 2014 23:49:58 +0000 (UTC) Received: from stoa.freebsd.net ([172.15.184.248]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0LjISX-1XNUUS37y3-00dZzd for ; Tue, 16 Dec 2014 00:49:51 +0100 Message-ID: <548F74B5.9050108@gmx.us> Date: Mon, 15 Dec 2014 18:54:29 -0500 From: Dutch Ingraham User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: latest wireshark core dumps References: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> In-Reply-To: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:BQzZOH/c967PwljKagVAedHo/fBEHyNJqfx3qJQaX5tKUan4tPW UBsaQishYVVtqVtyCGIwu3WzzLYw1ARqf4Frtmgl+xGTNydFZr1u+siH/fDoRF3631rPttV gdOJAIlHtExnLdNw1G4XKGM02FkVuSI+Drh9x3Pfd1BWwIkylCjwfmJP4dWVN1NJGhW+Uy9 7XShqfMropuSddOKfDKBg== X-UI-Out-Filterresults: notjunk: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: Mon, 15 Dec 2014 23:49:58 -0000 On 12/13/14 06:11, Daniel Braniss wrote: > hi all, > I just compiled from ports wireshark et.all on a virgin 10.1-stable, > and it’c coredumping on startup, any hints? > > thanks, > danny > > _______________________________________________ > 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" > A few of us are having the same problem.[1],[2],[3] Working on it. [1]https://forums.freebsd.org/threads/wireshark-install.49487/ [2]http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+current/freebsd-questions [3]bug #195980 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 16 06:56:39 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 CA71EE9F for ; Tue, 16 Dec 2014 06:56:39 +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 7AA92F5F for ; Tue, 16 Dec 2014 06:56:39 +0000 (UTC) Received: from th-04.cs.huji.ac.il ([132.65.80.125]) by kabab.cs.huji.ac.il with esmtp id 1Y0m3Z-000HSX-0J; Tue, 16 Dec 2014 08:56:29 +0200 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: latest wireshark core dumps From: Daniel Braniss In-Reply-To: <548F74B5.9050108@gmx.us> Date: Tue, 16 Dec 2014 08:56:28 +0200 Message-Id: <47B5C4FD-6B17-4D4E-A821-6BCA4B3CDEE0@cs.huji.ac.il> References: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> <548F74B5.9050108@gmx.us> To: Dutch Ingraham 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: 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, 16 Dec 2014 06:56:40 -0000 good to know it=E2=80=99s not a local issue! thanks! if it=E2=80=99s of any help: (gdb) bt #0 0x0000000809cff6d2 in g_type_check_instance_is_fundamentally_a ( type_instance=3D0x109e1860, fundamental_type=3D80) at gtype.c:3979 #1 0x0000000809cdb43a in g_object_ref (_object=3D0x109e1860) at = gobject.c:3041 #2 0x0000000809f8523f in g_list_foreach (list=3D0x810aa3b80,=20 func=3D0x809cdb410 , user_data=3D0x0) at glist.c:993 #3 0x00000008082cd60d in gtk_window_set_icon_list (window=3D0x810946230,=20= list=3D0x810aa3b80) at gtkwindow.c:4456 #4 0x00000000004445b6 in _start () #5 0x0000000809cd548c in g_cclosure_marshal_VOID__VOID = (closure=3D0x810962300,=20 return_value=3D0x0, n_param_values=3D1, param_values=3D0x7fffffffdcd0,= =20 invocation_hint=3D0x7fffffffdc70, marshal_data=3D0x0) at = gmarshal.c:85 #6 0x0000000809cd107a in g_closure_invoke (closure=3D0x810962300,=20 return_value=3D0x0, n_param_values=3D1, param_values=3D0x7fffffffdcd0,= =20 invocation_hint=3D0x7fffffffdc70) at gclosure.c:768 #7 0x0000000809cf4a3c in signal_emit_unlocked_R (node=3D0x81084ea60, = detail=3D0,=20 instance=3D0x810946230, emission_return=3D0x0,=20 instance_and_params=3D0x7fffffffdcd0) at gsignal.c:3553 #8 0x0000000809cf66b9 in g_signal_emit_valist (instance=3D0x810946230,=20= signal_id=3D8, detail=3D0, var_args=3D0x7fffffffe410) at = gsignal.c:3309 #9 0x0000000809cf700f in g_signal_emit (instance=3D0x810946230, = signal_id=3D8,=20 detail=3D0) at gsignal.c:3365 #10 0x00000008082a2b86 in gtk_widget_realize (widget=3D0x810946230) at gtkwidget.c:5508 ---Type to continue, or q to quit--- #11 0x00000000004c1e55 in _start () #12 0x00000000004478e2 in _start () #13 0x000000000042463f in _start () #14 0x0000000800811000 in ?? () #15 0x0000000000000000 in ?? () > On Dec 16, 2014, at 1:54 AM, Dutch Ingraham wrote: >=20 > On 12/13/14 06:11, Daniel Braniss wrote: >> 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? >>=20 >> thanks, >> danny >>=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 > A few of us are having the same problem.[1],[2],[3] Working on it. >=20 > [1]https://forums.freebsd.org/threads/wireshark-install.49487/ > = [2]http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D0+0+current/freebsd-ques= tions > [3]bug #195980 > _______________________________________________ > 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 Tue Dec 16 17:07: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 3F49A3AA for ; Tue, 16 Dec 2014 17:07:56 +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 1832BD53 for ; Tue, 16 Dec 2014 17:07:56 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 03E26B93C; Tue, 16 Dec 2014 12:07:55 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: freebsd crash under I/O - got error messages part 4 Date: Tue, 16 Dec 2014 11:54:47 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201412161154.47153.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 16 Dec 2014 12:07:55 -0500 (EST) Cc: Wojciech Puchar 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, 16 Dec 2014 17:07:56 -0000 On Sunday, December 07, 2014 3:57:25 pm Wojciech Puchar wrote: > 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 --- The LORs are known false positives (certainly the dirhash one is and is documented as such in the source). They are unrelated to the hard I/O errors you had in your first mail. I'm not sure how to track those down further however. :( -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 16 17:07:58 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 9B041410; Tue, 16 Dec 2014 17:07:58 +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 72C34D54; Tue, 16 Dec 2014 17:07:58 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 69846B97B; Tue, 16 Dec 2014 12:07:57 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: top -d1 behavior Date: Tue, 16 Dec 2014 12:03:44 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <54723E7E.8080509@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201412161203.44257.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 16 Dec 2014 12:07:57 -0500 (EST) Cc: Allan Jude , Fernando =?utf-8?q?Apestegu=C3=ADa?= 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, 16 Dec 2014 17:07:58 -0000 On Sunday, November 23, 2014 4:57:33 pm Fernando Apestegu=C3=ADa wrote: > > Neither seem like what the user would expect. >=20 > Agreed. But this is mostly unexpected (and can lead scripts to fail): Actually, I think having it output the states since boot would be more consistent with other tools like iostat/vmstat/etc. They report states on the first iteration that are states since boot. For example: % iostat 1 tty ada0 ada1 cd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 8 225 20.41 12 0.24 20.56 12 0.24 2.79 0 0.00 3 0 2 0 95 0 6230 60.00 6 0.35 64.80 10 0.62 0.00 0 0.00 9 0 91 0 0 0 6195 64.00 5 0.31 51.43 7 0.35 0.00 0 0.00 11 0 89 0 1 Can you test this test patch to see if it gives you what you expect from top -d1? Index: contrib/top/top.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =2D-- top.c (revision 275828) +++ top.c (working copy) @@ -176,7 +176,7 @@ char *argv[]; int preset_argc =3D 0; char **av; int ac; =2D char dostates =3D No; + char dostates =3D Yes; char do_unames =3D Yes; char interactive =3D Maybe; char warnings =3D 0; =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 16 18:36: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 B9F75E67 for ; Tue, 16 Dec 2014 18:36:34 +0000 (UTC) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::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 811C79D8 for ; Tue, 16 Dec 2014 18:36:34 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id h15so7553839igd.7 for ; Tue, 16 Dec 2014 10:36:34 -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:from:date:message-id :subject:to:cc:content-type; bh=dPds0BXHbk4VP/AsXXaA4pULKvPQuBmBJKvjoRJLx1c=; b=l7G76CpkGof9+/qljAxeps0eZHcDCbj+eBKQ8vEYJNJAgFUDFUIhejhOo8lSmSJ2HP ye4O8osfGd1E8m1Z1PpfldUMJf6+RSUgkpaXE0MIrqFTTGyMQ5XfnBzxDKZ11WAijG9Q OLfYcr0fOfj1vp3FOrzTeMUE7OPamSqSZVF4d8jybJjRI4kMsg7XK51UEtzRkpPJD+Mp PL9oqYbsLxrPXKt60OBgLnioofx+bEbH6MoxKAlLWwt3QIxFpfniUT6fZLYJqzesKTpQ G4Pv0XABAn+ZteRZmDh3gVEKBsAhT+m1nCzhMiCNZmYbUnn0lSRFx7YclzxXJcmRrvdB hOpA== X-Received: by 10.43.120.69 with SMTP id fx5mr33416183icc.45.1418754993953; Tue, 16 Dec 2014 10:36:33 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.0.85 with HTTP; Tue, 16 Dec 2014 10:36:13 -0800 (PST) In-Reply-To: <20141209125029.GA1568@schlappy> References: <20141209125029.GA1568@schlappy> From: Ed Maste Date: Tue, 16 Dec 2014 13:36:13 -0500 X-Google-Sender-Auth: O5WC1Y0L33Zd9ujfG_P_ud8fmW4 Message-ID: Subject: Re: [Patch] Bring back ALT_BREAK_TO_DEBUGGER functionality to vt(4) To: Andre Albsmeier Content-Type: text/plain; charset=UTF-8 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, 16 Dec 2014 18:36:34 -0000 On 9 December 2014 at 07:50, Andre Albsmeier wrote: > This is what I use to bring back ALT_BREAK_TO_DEBUGGER > functionality to vt(4). The patch is against STABLE-9.3. Thanks Andre, I'll add this to my queue and get it committed. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 16 19:50:13 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 7AB6A7E2; Tue, 16 Dec 2014 19:50:13 +0000 (UTC) Received: from mail.myota.org (mail.myota.org [85.10.206.105]) by mx1.freebsd.org (Postfix) with ESMTP id 07DAB212; Tue, 16 Dec 2014 19:50:12 +0000 (UTC) Received: from mobile.client (135.198.80.190.m.sta.codetel.net.do [190.80.198.135] (may be forged)) (authenticated bits=128) by mail.myota.org (8.14.9/8.14.9) with ESMTP id sBGJnpeO081085; Tue, 16 Dec 2014 20:49:58 +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 sBGJnOGN001562; Tue, 16 Dec 2014 20:49:25 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: (from user@localhost) by schlappy.local (8.14.9/8.14.9/Submit) id sBGJnOvN001561; Tue, 16 Dec 2014 20:49:24 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Date: Tue, 16 Dec 2014 20:49:24 +0100 From: Andre Albsmeier To: Ed Maste Subject: Re: [Patch] Bring back ALT_BREAK_TO_DEBUGGER functionality to vt(4) Message-ID: <20141216194924.GA1485@schlappy> References: <20141209125029.GA1568@schlappy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Echelon: VHF, TWA, Delta, Surveillance, Passwords 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 Cc: Andre Albsmeier , "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, 16 Dec 2014 19:50:13 -0000 On Tue, 16-Dec-2014 at 13:36:13 -0500, Ed Maste wrote: > On 9 December 2014 at 07:50, Andre Albsmeier wrote: > > This is what I use to bring back ALT_BREAK_TO_DEBUGGER > > functionality to vt(4). The patch is against STABLE-9.3. > > Thanks Andre, I'll add this to my queue and get it committed. Cool, thanks. If possible, please take also care of 273973, see https://groups.google.com/forum/#!topic/bsdmailinglist/PVE8ORrxLD8 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 16 20:21:26 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 E80CE3C1 for ; Tue, 16 Dec 2014 20:21:26 +0000 (UTC) Received: from mail-yh0-f52.google.com (mail-yh0-f52.google.com [209.85.213.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 AACBB91B for ; Tue, 16 Dec 2014 20:21:26 +0000 (UTC) Received: by mail-yh0-f52.google.com with SMTP id z6so6414059yhz.39 for ; Tue, 16 Dec 2014 12:21:20 -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=k6uxKkf4pLKN7Y8UGTyoMy2UP2VDr47UAdsBndlBwa4=; b=X38L1VPUFh4KCNpodscrKinknAbrJXmAKyWJBOmNTgKHfAjwuBHBK6kETqVMM43V1o LmvEA5z9KnDkCILrZ/yoDnuuDJzz2R/FqJMKS0OLq5plMFZWSyvvO0U4r/ri3v9cIqsb 87nksvhK2bFXVEZNMkTEl6ilqf2de92tf2owGNt/+Ei44+gM3ZuJBLs4mIyBk1NgaEJC f4UecdqE6Sk1fSen7czfPZBv1YEKAmewBsAzreEVVny1MfPlKX9wryWwOlDP8k8BvwOg CWLH6RungOWirtQ5MhhtMYyTK+E54iPq7KiW6E4Hf8uwavKSWHMJ2iI14Bnht7JBEJ9F lgHA== X-Gm-Message-State: ALoCoQnMmyTdUyBXG7MAnq5HvP0GoqeWx1EBf3USa6/rEvDCA4Fw9z6nnkiX+OR5BKMNTAV2oXUi MIME-Version: 1.0 X-Received: by 10.236.34.166 with SMTP id s26mr27624054yha.31.1418761280427; Tue, 16 Dec 2014 12:21:20 -0800 (PST) Received: by 10.170.46.213 with HTTP; Tue, 16 Dec 2014 12:21:20 -0800 (PST) In-Reply-To: <20141216194924.GA1485@schlappy> References: <20141209125029.GA1568@schlappy> <20141216194924.GA1485@schlappy> Date: Tue, 16 Dec 2014 21:21:20 +0100 Message-ID: Subject: Re: [Patch] Bring back ALT_BREAK_TO_DEBUGGER functionality to vt(4) From: Oliver Pinter To: Ed Maste Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , thierry@FreeBSD.org, Andre Albsmeier , bugzilla.freebsd@omnilan.de 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, 16 Dec 2014 20:21:27 -0000 Hi Ed! Could you please review and commit these patches too: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194744 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193817 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193865 On Tue, Dec 16, 2014 at 8:49 PM, Andre Albsmeier wrote: > On Tue, 16-Dec-2014 at 13:36:13 -0500, Ed Maste wrote: >> On 9 December 2014 at 07:50, Andre Albsmeier wrote: >> > This is what I use to bring back ALT_BREAK_TO_DEBUGGER >> > functionality to vt(4). The patch is against STABLE-9.3. >> >> Thanks Andre, I'll add this to my queue and get it committed. > > Cool, thanks. If possible, please take also care of 273973, see > > https://groups.google.com/forum/#!topic/bsdmailinglist/PVE8ORrxLD8 > _______________________________________________ > 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 Wed Dec 17 20:14: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 6043ED0F for ; Wed, 17 Dec 2014 20:14:22 +0000 (UTC) Received: from host203.r-bonomi.com (host203.r-bonomi.com [204.87.227.203]) by mx1.freebsd.org (Postfix) with ESMTP id 37BFE158A for ; Wed, 17 Dec 2014 20:14:21 +0000 (UTC) Received: (from bonomi@localhost) by host203.r-bonomi.com (8.14.9/8.14.7) id sBHK6Q5E031660; Wed, 17 Dec 2014 14:06:26 -0600 (CST) (envelope-from bonomi) Date: Wed, 17 Dec 2014 14:06:26 -0600 (CST) From: Robert Bonomi Message-Id: <201412172006.sBHK6Q5E031660@host203.r-bonomi.com> To: freebsd-hackers@freebsd.org Subject: getting 'load average' info from inside a kernel module X-Mailman-Approved-At: Wed, 17 Dec 2014 20:35:52 +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: Wed, 17 Dec 2014 20:14:22 -0000 originally sent to -questions, where it was suggested that -hackers was more likely to produce some useful info. > Subject: getting 'load averages' (or something similar) from inside a _kernel_ > > I'm trying to get the current 'runnable processes' count from inside a > kernel loadable module for BSD 8.4, so I can tweak it's behavior depending > on the current activity level. All I've found so far is what's in 'man 9 > runqueue', and it is *badly* out-of-sync with the 8.4 kernel code. > e.g., the external arrays at the beginning of the synopisis > are shown as being of type 'struct rq' -- but there *ISN"T* any defined > struct 'rq'; it seems to be named 'runq', at least in /usr/include/sys/runq.h > > Then the cr*p gets deeper -- trying to make heads or tails out of how to > get a count of runnable processes from the _arrays_ (of unknown size) > described on the 'man 9 runqueue' page info has me defeated. > Looking at '/usr/include/sys/runq.h', it appears that 'struct runq' is > a single item with an array of queues (by 'nice' level), and a bitmap of > which array elements have non-zero length queues. > > I'm perfectly willing to brute-force the data out of the queue lists, *IF* > there's some reasonable, _current_, descriptive info of the format/usage > of those kernel structures. if 'man 9 runqueue' is 'mostly' correct -- reality just being 'runq' instead of 'rq' -- then 'how to find out' how mamy elements are in those 'unknown size' arrays is the missing element. *OR* if those four items are _not_ arrays, but simple structs -- given the array of queueheads in the 'runq' struct, I can probably decipher the rest. > > Alternatively, is there a way to directly access the 'sysctl' MIB data in > kernel memory. sysctl(3) is out -- it's in 'libc', and not available to > kernel modules. Pointers to descriptions of the kernel in-memory data for > that MIB would be a big help. Or 'where to ask', if there's a better place. I'm willing to 'count processes' in the run queues each time I query -- an 'instantenous' value is fine for my purposes, I can derive whatever 'avrage over time' I need. :)) From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 17 22:27:42 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 41098CBC; Wed, 17 Dec 2014 22:27:42 +0000 (UTC) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (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 C669F936; Wed, 17 Dec 2014 22:27:41 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id l18so25372wgh.2; Wed, 17 Dec 2014 14:27:40 -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:content-transfer-encoding; bh=+6+beEliBdFzvVkKeiWBR1dMZzDoHqB5cHWOskQI7sc=; b=tH4Ym7zW0UV8XfhLh5PxWnV0KaNtCTeK+lYMXiYIudlZjpTDdEgb2RfTxh7LEDxteH Y8qqrW920pLI7hxtESidyWZE4nxlKhVTfz1POX+B7k1AUqCBSVwH8+Y1K6rvueBFDvIW qaLkDJft5k4dApVw1ohqMCZDTmkAGKqGuxL3rByTAgVs4h1Of44ETl8Cf3YlaHfc8PQt 3PYMa+ZzJNJOth043XuYcdUPujw6uw4Ql5/WBH3Id/eGTlHxShRZA3NM4NozS/D4kNTe qvlE0U3wNEMY5iWUCWgKO4SDQAWa0/+w6I0leJTHFicypkzWpnpD2+5DhQE8LqUWBsqW 6KSA== MIME-Version: 1.0 X-Received: by 10.194.234.40 with SMTP id ub8mr78734209wjc.100.1418855260241; Wed, 17 Dec 2014 14:27:40 -0800 (PST) Received: by 10.180.198.52 with HTTP; Wed, 17 Dec 2014 14:27:40 -0800 (PST) In-Reply-To: <201412161203.44257.jhb@freebsd.org> References: <54723E7E.8080509@freebsd.org> <201412161203.44257.jhb@freebsd.org> Date: Wed, 17 Dec 2014 23:27:40 +0100 Message-ID: Subject: Re: top -d1 behavior From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= To: John Baldwin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers , Allan Jude 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, 17 Dec 2014 22:27:42 -0000 On Tue, Dec 16, 2014 at 6:03 PM, John Baldwin wrote: > On Sunday, November 23, 2014 4:57:33 pm Fernando Apestegu=C3=ADa wrote: >> > Neither seem like what the user would expect. >> >> Agreed. But this is mostly unexpected (and can lead scripts to fail): > > Actually, I think having it output the states since boot would be more > consistent with other tools like iostat/vmstat/etc. They report states > on the first iteration that are states since boot. For example: > > % iostat 1 > tty ada0 ada1 cd0 = cpu > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in= id > 8 225 20.41 12 0.24 20.56 12 0.24 2.79 0 0.00 3 0 2 0= 95 > 0 6230 60.00 6 0.35 64.80 10 0.62 0.00 0 0.00 9 0 91 0= 0 > 0 6195 64.00 5 0.31 51.43 7 0.35 0.00 0 0.00 11 0 89 0= 1 > > Can you test this test patch to see if it gives you what you expect from > top -d1? Yes it does. I thought however that the discussion was over :) so I filed a PR[1] to at least warn in the man page about the special behavior for this case. I would rather fix top and leave the man page as it is. Cheers. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195717 > > Index: contrib/top/top.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- top.c (revision 275828) > +++ top.c (working copy) > @@ -176,7 +176,7 @@ char *argv[]; > int preset_argc =3D 0; > char **av; > int ac; > - char dostates =3D No; > + char dostates =3D Yes; > char do_unames =3D Yes; > char interactive =3D Maybe; > char warnings =3D 0; > > -- > John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 18 08:48:15 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 E190150F for ; Thu, 18 Dec 2014 08:48:14 +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 83C2C1A75 for ; Thu, 18 Dec 2014 08:48:14 +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 sBI8m4h2034397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Dec 2014 10:48:04 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua sBI8m4h2034397 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id sBI8m3eN034396; Thu, 18 Dec 2014 10:48:03 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 18 Dec 2014 10:48:03 +0200 From: Konstantin Belousov To: Robert Bonomi Subject: Re: getting 'load average' info from inside a kernel module Message-ID: <20141218084803.GP2148@kib.kiev.ua> References: <201412172006.sBHK6Q5E031660@host203.r-bonomi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201412172006.sBHK6Q5E031660@host203.r-bonomi.com> 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 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: Thu, 18 Dec 2014 08:48:15 -0000 On Wed, Dec 17, 2014 at 02:06:26PM -0600, Robert Bonomi wrote: > > originally sent to -questions, where it was suggested that -hackers was more > likely to produce some useful info. > > > Subject: getting 'load averages' (or something similar) from inside a _kernel_ > > > > I'm trying to get the current 'runnable processes' count from inside a > > kernel loadable module for BSD 8.4, so I can tweak it's behavior depending > > on the current activity level. All I've found so far is what's in 'man 9 > > runqueue', and it is *badly* out-of-sync with the 8.4 kernel code. > > e.g., the external arrays at the beginning of the synopisis > > are shown as being of type 'struct rq' -- but there *ISN"T* any defined > > struct 'rq'; it seems to be named 'runq', at least in /usr/include/sys/runq.h > > > > Then the cr*p gets deeper -- trying to make heads or tails out of how to > > get a count of runnable processes from the _arrays_ (of unknown size) > > described on the 'man 9 runqueue' page info has me defeated. > > Looking at '/usr/include/sys/runq.h', it appears that 'struct runq' is > > a single item with an array of queues (by 'nice' level), and a bitmap of > > which array elements have non-zero length queues. > > > > I'm perfectly willing to brute-force the data out of the queue lists, *IF* > > there's some reasonable, _current_, descriptive info of the format/usage > > of those kernel structures. > > if 'man 9 runqueue' is 'mostly' correct -- reality just being 'runq' instead > of 'rq' -- then 'how to find out' how mamy elements are in those 'unknown size' > arrays is the missing element. *OR* if those four items are _not_ arrays, > but simple structs -- given the array of queueheads in the 'runq' struct, > I can probably decipher the rest. > > > > Alternatively, is there a way to directly access the 'sysctl' MIB data in > > kernel memory. sysctl(3) is out -- it's in 'libc', and not available to > > kernel modules. Pointers to descriptions of the kernel in-memory data for > > that MIB would be a big help. Or 'where to ask', if there's a better place. > > I'm willing to 'count processes' in the run queues each time I query -- an > 'instantenous' value is fine for my purposes, I can derive whatever 'avrage > over time' I need. :)) You are writing a kernel module, so why did not you looked at the kernel sources ? Look at the implementation of the sysctl for which you want the kernel analog, and do the same. AFAIU, you want vm.loadavg, which is floating-point recoded representation of the fixed-point values from averunnable array. Look at sys/kern/kern_synch.c and sys/vm/vm_meter.c (honestly, I only checked HEAD). From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 18 10:12:25 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 1DF7F7E4; Thu, 18 Dec 2014 10:12:25 +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 C110B18EC; Thu, 18 Dec 2014 10:12:23 +0000 (UTC) Received: from th-04.cs.huji.ac.il ([132.65.80.125]) by kabab.cs.huji.ac.il with esmtp id 1Y1Y45-0006wL-LZ; Thu, 18 Dec 2014 12:12:13 +0200 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: latest wireshark core dumps From: Daniel Braniss In-Reply-To: <47B5C4FD-6B17-4D4E-A821-6BCA4B3CDEE0@cs.huji.ac.il> Date: Thu, 18 Dec 2014 12:12:12 +0200 Message-Id: References: <2BF919F0-ADB3-44DD-B2A7-F21F909DC46F@cs.huji.ac.il> <548F74B5.9050108@gmx.us> <47B5C4FD-6B17-4D4E-A821-6BCA4B3CDEE0@cs.huji.ac.il> To: Dutch Ingraham , marcus@FreeBSD.org 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: 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: Thu, 18 Dec 2014 10:12:25 -0000 just a wild guess, but wireshark is also complaining about: ** (wireshark:79448): WARNING **: Couldn't connect to accessibility bus: = Failed to connect to socket /tmp/dbus-H8OvE4zmWb: No such file or = directory after many tries, there is a /var/tmp/dbus-xxxx but not the one = requested, does any one know how does this dbus-xxx appear? I ran dbus-launch, and that seems to be reading correctly /var/db/dbus/machine-id I am mentioning dbus, because last time there were issues, i did some = magics with dbus and wireshark stooped core-dumping=E2=80=A6 [the magic no longer = works :-( danny > On Dec 16, 2014, at 8:56 AM, Daniel Braniss = wrote: >=20 > good to know it=E2=80=99s not a local issue! > thanks! > if it=E2=80=99s of any help: > (gdb) bt > #0 0x0000000809cff6d2 in g_type_check_instance_is_fundamentally_a ( > type_instance=3D0x109e1860, fundamental_type=3D80) at gtype.c:3979 > #1 0x0000000809cdb43a in g_object_ref (_object=3D0x109e1860) at = gobject.c:3041 > #2 0x0000000809f8523f in g_list_foreach (list=3D0x810aa3b80,=20 > func=3D0x809cdb410 , user_data=3D0x0) at glist.c:993 > #3 0x00000008082cd60d in gtk_window_set_icon_list = (window=3D0x810946230,=20 > list=3D0x810aa3b80) at gtkwindow.c:4456 > #4 0x00000000004445b6 in _start () > #5 0x0000000809cd548c in g_cclosure_marshal_VOID__VOID = (closure=3D0x810962300,=20 > return_value=3D0x0, n_param_values=3D1, = param_values=3D0x7fffffffdcd0,=20 > invocation_hint=3D0x7fffffffdc70, marshal_data=3D0x0) at = gmarshal.c:85 > #6 0x0000000809cd107a in g_closure_invoke (closure=3D0x810962300,=20 > return_value=3D0x0, n_param_values=3D1, = param_values=3D0x7fffffffdcd0,=20 > invocation_hint=3D0x7fffffffdc70) at gclosure.c:768 > #7 0x0000000809cf4a3c in signal_emit_unlocked_R (node=3D0x81084ea60, = detail=3D0,=20 > instance=3D0x810946230, emission_return=3D0x0,=20 > instance_and_params=3D0x7fffffffdcd0) at gsignal.c:3553 > #8 0x0000000809cf66b9 in g_signal_emit_valist (instance=3D0x810946230,=20= > signal_id=3D8, detail=3D0, var_args=3D0x7fffffffe410) at = gsignal.c:3309 > #9 0x0000000809cf700f in g_signal_emit (instance=3D0x810946230, = signal_id=3D8,=20 > detail=3D0) at gsignal.c:3365 > #10 0x00000008082a2b86 in gtk_widget_realize (widget=3D0x810946230) > at gtkwidget.c:5508 > ---Type to continue, or q to quit--- > #11 0x00000000004c1e55 in _start () > #12 0x00000000004478e2 in _start () > #13 0x000000000042463f in _start () > #14 0x0000000800811000 in ?? () > #15 0x0000000000000000 in ?? () >=20 >> On Dec 16, 2014, at 1:54 AM, Dutch Ingraham wrote: >>=20 >> On 12/13/14 06:11, Daniel Braniss wrote: >>> 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? >>>=20 >>> thanks, >>> danny >>>=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 >> A few of us are having the same problem.[1],[2],[3] Working on it. >>=20 >> [1]https://forums.freebsd.org/threads/wireshark-install.49487/ >> = [2]http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D0+0+current/freebsd-ques= tions >> [3]bug #195980 >> _______________________________________________ >> 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 > _______________________________________________ > 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 Thu Dec 18 19:49: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 AADD15E7; Thu, 18 Dec 2014 19:49:34 +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 8268A16AD; Thu, 18 Dec 2014 19:49:34 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 73715B97A; Thu, 18 Dec 2014 14:49:33 -0500 (EST) From: John Baldwin To: Fernando =?utf-8?q?Apestegu=C3=ADa?= Subject: Re: top -d1 behavior Date: Thu, 18 Dec 2014 14:49:16 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201412161203.44257.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201412181449.16974.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 18 Dec 2014 14:49:33 -0500 (EST) Cc: FreeBSD Hackers , Allan Jude 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: Thu, 18 Dec 2014 19:49:34 -0000 On Wednesday, December 17, 2014 5:27:40 pm Fernando Apestegu=C3=ADa wrote: > On Tue, Dec 16, 2014 at 6:03 PM, John Baldwin wrote: > > On Sunday, November 23, 2014 4:57:33 pm Fernando Apestegu=C3=ADa wrote: > >> > Neither seem like what the user would expect. > >> > >> Agreed. But this is mostly unexpected (and can lead scripts to fail): > > > > Actually, I think having it output the states since boot would be more > > consistent with other tools like iostat/vmstat/etc. They report states > > on the first iteration that are states since boot. For example: > > > > % iostat 1 > > tty ada0 ada1 cd0 = cpu > > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy = in id > > 8 225 20.41 12 0.24 20.56 12 0.24 2.79 0 0.00 3 0 2 = 0 95 > > 0 6230 60.00 6 0.35 64.80 10 0.62 0.00 0 0.00 9 0 91 = 0 0 > > 0 6195 64.00 5 0.31 51.43 7 0.35 0.00 0 0.00 11 0 89 = 0 1 > > > > Can you test this test patch to see if it gives you what you expect from > > top -d1? >=20 > Yes it does. >=20 > I thought however that the discussion was over :) so I filed a PR[1] > to at least warn in the man page about the special behavior for this > case. >=20 > I would rather fix top and leave the man page as it is. I think fixing top makes the most sense. I saw this thread a while ago but just hadn't replied until I sent the previous message. Here's a real versi= on of the patch if you would like to test it. Index: contrib/top/display.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =2D-- contrib/top/display.c (revision 275828) +++ contrib/top/display.c (working copy) @@ -557,46 +557,6 @@ } } =20 =2Dz_cpustates() =2D =2D{ =2D register int i =3D 0; =2D register char **names; =2D register char *thisname; =2D register int *lp; =2D int cpu, value; =2D =2Dfor (cpu =3D 0; cpu < num_cpus; cpu++) { =2D names =3D cpustate_names; =2D =2D /* show tag and bump lastline */ =2D if (num_cpus =3D=3D 1) =2D printf("\nCPU: "); =2D else { =2D value =3D printf("\nCPU %d: ", cpu); =2D while (value++ <=3D cpustates_column) =2D printf(" "); =2D } =2D lastline++; =2D =2D while ((thisname =3D *names++) !=3D NULL) =2D { =2D if (*thisname !=3D '\0') =2D { =2D printf("%s %% %s", (i++ % num_cpustates) =3D=3D 0 ? "" : ", ", t= hisname); =2D } =2D } =2D} =2D =2D /* fill the "last" array with all -1s, to insure correct updating */ =2D lp =3D lcpustates; =2D i =3D num_cpustates * num_cpus; =2D while (--i >=3D 0) =2D { =2D *lp++ =3D -1; =2D } =2D} =2D /* * *_memory(stats) - print "Memory: " followed by the memory summary stri= ng * Index: contrib/top/top.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =2D-- contrib/top/top.c (revision 275828) +++ contrib/top/top.c (working copy) @@ -176,7 +176,6 @@ int preset_argc =3D 0; char **av; int ac; =2D char dostates =3D No; char do_unames =3D Yes; char interactive =3D Maybe; char warnings =3D 0; @@ -643,23 +642,7 @@ system_info.procstates); =20 /* display the cpu state percentage breakdown */ =2D if (dostates) /* but not the first time */ =2D { =2D (*d_cpustates)(system_info.cpustates); =2D } =2D else =2D { =2D /* we'll do it next time */ =2D if (smart_terminal) =2D { =2D z_cpustates(); =2D } =2D else =2D { =2D putchar('\n'); =2D } =2D dostates =3D Yes; =2D } + (*d_cpustates)(system_info.cpustates); =20 /* display memory stats */ (*d_memory)(system_info.memory); =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 10:27:48 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 78317153; Fri, 19 Dec 2014 10:27:48 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (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 0CFFC188D; Fri, 19 Dec 2014 10:27:48 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id y19so902146wgg.21; Fri, 19 Dec 2014 02:27:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7eRs6seN1xdZEcgZGiX45l97/qQ7ojVsIqu0DriEVpk=; b=YhV9Z3X7HhxBAhjB3hk5JT1uPz5cgg3w6Aj8ixkv7V5R2xVSmPpBqCclw0ZfQKV93s rKEdu6n+ARugUD4G9dMea1+ikToMG2VAl9O0J4SPGTFPLFd7QnX0ELX+SSR6qUtlhV+/ lFUUXZ8inA3i5fsraDMsWEQ+2zeLFMjhsx11I3GEZ14OXMkALkT3AtbXNpMavIq4bF6M /Z0uSCpOzmbIOQxIHPb16Ooh+R4MFFuR+ReofBlyPOh8qsrfWIkwrBZBMI62rFhN5Z0u kxCPAPF3AvqTLXx19+2AucSA8bGQ1rbJ6ZjZoLkbhNjjK1q5ZrZ2z2S9siP62Y7Gawc1 zw9Q== MIME-Version: 1.0 X-Received: by 10.180.198.211 with SMTP id je19mr4262327wic.27.1418984866346; Fri, 19 Dec 2014 02:27:46 -0800 (PST) Received: by 10.194.216.226 with HTTP; Fri, 19 Dec 2014 02:27:46 -0800 (PST) Date: Fri, 19 Dec 2014 14:27:46 +0400 Message-ID: Subject: lighttpd crush the system after r274463 From: Andrey Fesenko To: freebsd-current , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 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, 19 Dec 2014 10:27:48 -0000 Hello, I'm use lighttpd+SPAWNFCGI for moinmoin wiki. Before r274463 work fine, after update r275317 and CURRENT system crushed after start any python CGI script. For test i'm install py27-flup and start simple #!/usr/local/bin/python2.7 def myapp(environ, start_response): start_response('200 OK', [('Content-Type', 'text/plain')]) return ['Hello World!\n'] if __name__ == '__main__': from flup.server.fcgi import WSGIServer WSGIServer(myapp).run() Perl CGI test script work fine. Workaround FreeBSD-r275317 and later lighttpd-1.4.35_5 Options : BZIP2 : on DOCS : on FAM : on GDBM : off IPV6 : on LDAP : off LIBEV : on LUA : on MEMCACHE : off MYSQL : off MYSQLAUTH : off NODELAY : on OPENSSL : on SPAWNFCGI : on VALGRIND : off WEBDAV : off Shared Libs required: libpcre.so.1 liblua-5.1.so libfam.so.0 libev.so.4 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff809d44bd stack pointer = 0x28:0xfffffe00f77df700 frame pointer = 0x28:0xfffffe00f77df730 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 658 (lighttpd) [ thread pid 658 tid 100067 ] Stopped at sbappendstream_locked+0x2d: cmpq $0,0x8(%r14) db> bt Tracing pid 658 tid 100067 td 0xfffff8000ba3e940 sbappendstream_locked() at sbappendstream_locked+0x2d/frame 0xfffffe00f77df730 sbappendstream() at sbappendstream+0x3c/frame 0xfffffe00f77df760 tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfffffe00f77df7e0 sosend_generic() at sosend_generic+0x40b/frame 0xfffffe00f77df8a0 soo_write() at soo_write+0x42/frame 0xfffffe00f77df8d0 dofilewrite() at dofilewrite+0x88/frame 0xfffffe00f77df920 kern_writev() at kern_writev+0x68/frame 0xfffffe00f77df970 sys_writev() at sys_writev+0x36/frame 0xfffffe00f77df9a0 amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe00f77dfab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00f77dfab0 --- syscall (121, FreeBSD ELF64, sys_writev), rip = 0x80164cb8a, rsp = 0x7fffffffa658, rbp = 0x7fffffffe6 c0 --- From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 13:52: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 25D48B40 for ; Fri, 19 Dec 2014 13:52:28 +0000 (UTC) Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::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 D27AF1CD5 for ; Fri, 19 Dec 2014 13:52:27 +0000 (UTC) Received: by mail-qa0-f52.google.com with SMTP id x12so607934qac.25 for ; Fri, 19 Dec 2014 05:52:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=yBGbvXKhOBXli99Se/qjUGNfac5PfwYnVtPnF/DZ+s0=; b=ftxQLTEGNMLqPzQRVbtWFXNxlv9Cr8nRP0lc05JC84D9vihWp6fZiJ2fmQ6DeLbz0c Tskm/fTYkfp5AV4M1d7lA6KBzOd2Qp85MpUSIMNa6cyrYpoeLudA+5mRdNiPSsALj7AJ tiT1i0jqE8Y4EZ4O1i1mZEmR/d3P/6xfoLQtAVJBzzK+xONKo9LG3jVFRTYI8oqlt+3A 16camf/vnwsGYsSgBQkcb0EqEccvvVkx7AcVvwCSTznmhEFOHMPOjjjGfXVEIeqZwHdR yrCpHGi313x6sSVzQaZXOMAGO8A7f+DQNhp36r0c0nsk3PawPkaHo/T7d32amV+nBstM 98ug== MIME-Version: 1.0 X-Received: by 10.224.45.69 with SMTP id d5mr14087027qaf.56.1418997147001; Fri, 19 Dec 2014 05:52:27 -0800 (PST) Received: by 10.140.27.145 with HTTP; Fri, 19 Dec 2014 05:52:26 -0800 (PST) Date: Fri, 19 Dec 2014 11:52:26 -0200 Message-ID: Subject: [OFF-TOPIC] A real programmer would not stoop to wasting machine capacity to do the assembly as said Richard Hamming? From: =?UTF-8?Q?fran=C3=A7ai_s?= To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Fri, 19 Dec 2014 13:52:28 -0000 [quote="http://worrydream.com/dbx/"] Reactions to SOAP and Fortran Richard Hamming -- The Art of Doing Science and Engineering, p25 (pdf book) In the beginning we programmed in absolute binary... Finally, a Symbolic Assembly Program was devised -- after more years than you are apt to believe during which most programmers continued their heroic absolute binary programming. At the time [the assembler] first appeared I would guess about 1% of the older programmers were interested in it -- using [assembly] was "sissy stuff", and a real programmer would not stoop to wasting machine capacity to do the assembly. Yes! Programmers wanted no part of it, though when pressed they had to admit their old methods used more machine time in locating and fixing up errors than the [assembler] ever used. One of the main complaints was when using a symbolic system you do not know where anything was in storage -- though in the early days we supplied a mapping of symbolic to actual storage, and believe it or not they later lovingly pored over such sheets rather than realize they did not need to know that information if they stuck to operating within the system -- no! When correcting errors they preferred to do it in absolute binary. FORTRAN was proposed by Backus and friends, and again was opposed by almost all programmers. First, it was said it could not be done. Second, if it could be done, it would be too wasteful of machine time and capacity. Third, even if it did work, no respectable programmer would use it -- it was only for sissies! John von Neumann's reaction to assembly language and Fortran John A.N. Lee, Virginia Polytechnical Institute John von Neumann, when he first heard about FORTRAN in 1954, was unimpressed and asked "why would you want more than machine language?" One of von Neumann's students at Princeton recalled that graduate students were being used to hand assemble programs into binary for their early machine. This student took time out to build an assembler, but when von Neumann found out about it he was very angry, saying that it was a waste of a valuable scientific computing instrument to use it to do clerical work.[/quote] If is true that a real programmer would not stoop to wasting machine capacity to do the assembly, is an unfortunate fact the real programmers do use to wasting machine capacity to do the assembly, compilers... From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 14:21:44 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 6B1E0A9 for ; Fri, 19 Dec 2014 14:21:44 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::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 20B812097 for ; Fri, 19 Dec 2014 14:21:44 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id dc16so649112qab.23 for ; Fri, 19 Dec 2014 06:21:43 -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 :content-type; bh=KCQYBaEGwmZLZuT8NJonk8KTupT6JhHKFOpuB0d3bLk=; b=ROMbuJOpk5GOCH09ja4m+eZLJHvcHKDs3asn3BvjO/bh0E4AECYs9FpjT4Ole7pgpx 3RfqUic2b0gGhdGa2/1XEm9Taiz18Yn2eMYBO/Hlk0IExW29mNVghGHrzIl0u/zZFtQ6 FQ0W32IfocsRBPhIAlKOLjDvUAjdr6h3UZxvJaGCGrCIMwXAPMMwDYW17xblC1bKI4Mx eaHzO3bx948Bg9nUZTm+SqZMngHwdNgAd245od5FUKrbEWBDXUr78mgHlMUqn7IwiVXX dw+Yr+zXQmI/dWZ9lJpAY1ZD9pZMYX6QDRZmTYs0GgjLByvE75F9A4cnY0lx8vLhkvkQ S8hw== MIME-Version: 1.0 X-Received: by 10.140.101.145 with SMTP id u17mr13269810qge.84.1418998903087; Fri, 19 Dec 2014 06:21:43 -0800 (PST) Received: by 10.140.27.145 with HTTP; Fri, 19 Dec 2014 06:21:43 -0800 (PST) In-Reply-To: References: Date: Fri, 19 Dec 2014 12:21:43 -0200 Message-ID: Subject: Re: [OFF-TOPIC] A real programmer would not stoop to wasting machine capacity to do the assembly as said Richard Hamming? From: =?UTF-8?Q?fran=C3=A7ai_s?= To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-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, 19 Dec 2014 14:21:44 -0000 Is true that a real programmer would not stoop to wasting machine capacity to do the assembly? 2014-12-19 11:52 GMT-02:00 fran=C3=A7ai s : > > [quote=3D"http://worrydream.com/dbx/"] > Reactions to SOAP and Fortran > Richard Hamming -- The Art of Doing Science and Engineering, p25 (pdf boo= k) > > In the beginning we programmed in absolute binary... Finally, a Symbolic > Assembly Program was devised -- after more years than you are apt to > believe during which most programmers continued their heroic absolute > binary programming. At the time [the assembler] first appeared I would > guess about 1% of the older programmers were interested in it -- using > [assembly] was "sissy stuff", and a real programmer would not stoop to > wasting machine capacity to do the assembly. > > Yes! Programmers wanted no part of it, though when pressed they had to > admit their old methods used more machine time in locating and fixing up > errors than the [assembler] ever used. One of the main complaints was whe= n > using a symbolic system you do not know where anything was in storage -- > though in the early days we supplied a mapping of symbolic to actual > storage, and believe it or not they later lovingly pored over such sheets > rather than realize they did not need to know that information if they > stuck to operating within the system -- no! When correcting errors they > preferred to do it in absolute binary. > > FORTRAN was proposed by Backus and friends, and again was opposed by > almost all programmers. First, it was said it could not be done. Second, = if > it could be done, it would be too wasteful of machine time and capacity. > Third, even if it did work, no respectable programmer would use it -- it > was only for sissies! > > > John von Neumann's reaction to assembly language and Fortran > John A.N. Lee, Virginia Polytechnical Institute > > John von Neumann, when he first heard about FORTRAN in 1954, was > unimpressed and asked "why would you want more than machine language?" On= e > of von Neumann's students at Princeton recalled that graduate students we= re > being used to hand assemble programs into binary for their early machine. > This student took time out to build an assembler, but when von Neumann > found out about it he was very angry, saying that it was a waste of a > valuable scientific computing instrument to use it to do clerical > work.[/quote] > > If is true that a real programmer would not stoop to wasting machine > capacity to do the assembly, is an unfortunate fact the real programmers = do > use to wasting machine capacity to do the assembly, compilers... > > From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 17:22:44 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 A42258B6; Fri, 19 Dec 2014 17:22:44 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::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 3F7B4222A; Fri, 19 Dec 2014 17:22:44 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id bs8so5371310wib.3; Fri, 19 Dec 2014 09:22:42 -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:content-transfer-encoding; bh=GY7qMuy4j8NSO+ywNbnfC5UKMTPJ32Zntx2qf1EQQbE=; b=reEe3Glw137nKoyqiZf27Uf/Ag1DVN1LoK+Tw10TV4wv4kfIvpIR+e7IQnm52lTZIN cS8wdFpAAFHt9scwU7uI+e3DEJfGmB9knTg5C3gL8lDiZVcLMeSeGoAhcjGX7BPR1Coh BwkUHzJ3WMgmIOLJBWMQXcWwl0SVH/D7Gvkr10NlN3jRse4atrPVzAXeJUD6VIKKHDId oWw61nlgAtUhXR07wIef88C6mvfbF6SoZsRgKU5ODgCbpVTptXllBh4yukG16XtwMtqc WmT5df3aLs8h4zXN1wbfCvyAX9mO1G/W5pkBu+QRTXA6rnrG9rWay7upkBW2l6nhg1GF lQ8Q== MIME-Version: 1.0 X-Received: by 10.181.13.106 with SMTP id ex10mr7788002wid.36.1419009762340; Fri, 19 Dec 2014 09:22:42 -0800 (PST) Received: by 10.180.198.52 with HTTP; Fri, 19 Dec 2014 09:22:42 -0800 (PST) In-Reply-To: <201412181449.16974.jhb@freebsd.org> References: <201412161203.44257.jhb@freebsd.org> <201412181449.16974.jhb@freebsd.org> Date: Fri, 19 Dec 2014 18:22:42 +0100 Message-ID: Subject: Re: top -d1 behavior From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= To: John Baldwin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers , Allan Jude 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, 19 Dec 2014 17:22:44 -0000 On Thu, Dec 18, 2014 at 8:49 PM, John Baldwin wrote: > On Wednesday, December 17, 2014 5:27:40 pm Fernando Apestegu=C3=ADa wrote= : >> On Tue, Dec 16, 2014 at 6:03 PM, John Baldwin wrote: >> > On Sunday, November 23, 2014 4:57:33 pm Fernando Apestegu=C3=ADa wrote= : >> >> > Neither seem like what the user would expect. >> >> >> >> Agreed. But this is mostly unexpected (and can lead scripts to fail): >> > >> > Actually, I think having it output the states since boot would be more >> > consistent with other tools like iostat/vmstat/etc. They report state= s >> > on the first iteration that are states since boot. For example: >> > >> > % iostat 1 >> > tty ada0 ada1 cd0 = cpu >> > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy= in id >> > 8 225 20.41 12 0.24 20.56 12 0.24 2.79 0 0.00 3 0 2= 0 95 >> > 0 6230 60.00 6 0.35 64.80 10 0.62 0.00 0 0.00 9 0 91= 0 0 >> > 0 6195 64.00 5 0.31 51.43 7 0.35 0.00 0 0.00 11 0 89= 0 1 >> > >> > Can you test this test patch to see if it gives you what you expect fr= om >> > top -d1? >> >> Yes it does. >> >> I thought however that the discussion was over :) so I filed a PR[1] >> to at least warn in the man page about the special behavior for this >> case. >> >> I would rather fix top and leave the man page as it is. > > I think fixing top makes the most sense. I saw this thread a while ago b= ut > just hadn't replied until I sent the previous message. Here's a real ver= sion > of the patch if you would like to test it. I don't know what I was doing wrong, but I couldn't apply your patch cleanly, sorry (patch -p0 < /path/to/patch). Anyway, I translated the changes to the code and it worked for me. Sample output: last pid: 8084; load averages: 0.36, 0.26, 0.23 up 1+00:47:24 16:38:10 47 processes: 1 running, 46 sleeping CPU: 32.0% user, 0.0% nice, 8.1% system, 0.1% interrupt, 59.8% idle Mem: 361M Active, 1024M Inact, 630M Wired, 528K Cache, 361M Buf, 1931M Free Swap: 128M Total, 40M Used, 88M Free, 31% Inuse ... [snip] If you are to commit this, could you please close PR 195717? > > Index: contrib/top/display.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- contrib/top/display.c (revision 275828) > +++ contrib/top/display.c (working copy) > @@ -557,46 +557,6 @@ > } > } > > -z_cpustates() > - > -{ > - register int i =3D 0; > - register char **names; > - register char *thisname; > - register int *lp; > - int cpu, value; > - > -for (cpu =3D 0; cpu < num_cpus; cpu++) { > - names =3D cpustate_names; > - > - /* show tag and bump lastline */ > - if (num_cpus =3D=3D 1) > - printf("\nCPU: "); > - else { > - value =3D printf("\nCPU %d: ", cpu); > - while (value++ <=3D cpustates_column) > - printf(" "); > - } > - lastline++; > - > - while ((thisname =3D *names++) !=3D NULL) > - { > - if (*thisname !=3D '\0') > - { > - printf("%s %% %s", (i++ % num_cpustates) =3D=3D 0 ? "" : "= , ", thisname); > - } > - } > -} > - > - /* fill the "last" array with all -1s, to insure correct updating */ > - lp =3D lcpustates; > - i =3D num_cpustates * num_cpus; > - while (--i >=3D 0) > - { > - *lp++ =3D -1; > - } > -} > - > /* > * *_memory(stats) - print "Memory: " followed by the memory summary st= ring > * > Index: contrib/top/top.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- contrib/top/top.c (revision 275828) > +++ contrib/top/top.c (working copy) > @@ -176,7 +176,6 @@ > int preset_argc =3D 0; > char **av; > int ac; > - char dostates =3D No; > char do_unames =3D Yes; > char interactive =3D Maybe; > char warnings =3D 0; > @@ -643,23 +642,7 @@ > system_info.procstates); > > /* display the cpu state percentage breakdown */ > - if (dostates) /* but not the first time */ > - { > - (*d_cpustates)(system_info.cpustates); > - } > - else > - { > - /* we'll do it next time */ > - if (smart_terminal) > - { > - z_cpustates(); > - } > - else > - { > - putchar('\n'); > - } > - dostates =3D Yes; > - } > + (*d_cpustates)(system_info.cpustates); > > /* display memory stats */ > (*d_memory)(system_info.memory); > > -- > John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 18:27: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 05DE6BB1 for ; Fri, 19 Dec 2014 18:27:55 +0000 (UTC) Received: from tds-solutions.net (tds-solutions.net [192.99.32.153]) by mx1.freebsd.org (Postfix) with ESMTP id BABFF2DD1 for ; Fri, 19 Dec 2014 18:27:54 +0000 (UTC) Received: from tds-solutions.net (localhost [127.0.0.1]) by tds-solutions.net (Postfix) with ESMTP id D4DDF75EC3; Fri, 19 Dec 2014 13:18:33 -0500 (EST) X-Virus-Scanned: amavisd-new at tds-solutions.net Received: from tds-solutions.net ([127.0.0.1]) by tds-solutions.net (tds-solutions.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVSS-W6w4s6D; Fri, 19 Dec 2014 13:18:29 -0500 (EST) Received: from [192.168.1.102] (host-184-166-24-185.gdj-co.client.bresnan.net [184.166.24.185]) (Authenticated sender: sorressean) by tds-solutions.net (Postfix) with ESMTPSA id F1C2975E77; Fri, 19 Dec 2014 13:18:28 -0500 (EST) Message-ID: <54946BF6.7000900@tysdomain.com> Date: Fri, 19 Dec 2014 13:18:30 -0500 From: "Littlefield, Tyler" Reply-To: tyler@tysdomain.com User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: =?UTF-8?B?ZnJhbsOnYWkgcw==?= , freebsd-hackers@freebsd.org Subject: Re: [OFF-TOPIC] A real programmer would not stoop to wasting machine capacity to do the assembly as said Richard Hamming? 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: Fri, 19 Dec 2014 18:27:55 -0000 On 12/19/2014 9:21 AM, françai s wrote: > Is true that a real programmer would not stoop to wasting machine capacity > to do the assembly? Is true that a real troll wouldn't stoop to waste bandwidth but to do the real work? 2014-12-19 11:52 GMT-02:00 françai s : >> [quote="http://worrydream.com/dbx/"] >> Reactions to SOAP and Fortran >> Richard Hamming -- The Art of Doing Science and Engineering, p25 (pdf book) >> >> In the beginning we programmed in absolute binary... Finally, a Symbolic >> Assembly Program was devised -- after more years than you are apt to >> believe during which most programmers continued their heroic absolute >> binary programming. At the time [the assembler] first appeared I would >> guess about 1% of the older programmers were interested in it -- using >> [assembly] was "sissy stuff", and a real programmer would not stoop to >> wasting machine capacity to do the assembly. >> >> Yes! Programmers wanted no part of it, though when pressed they had to >> admit their old methods used more machine time in locating and fixing up >> errors than the [assembler] ever used. One of the main complaints was when >> using a symbolic system you do not know where anything was in storage -- >> though in the early days we supplied a mapping of symbolic to actual >> storage, and believe it or not they later lovingly pored over such sheets >> rather than realize they did not need to know that information if they >> stuck to operating within the system -- no! When correcting errors they >> preferred to do it in absolute binary. >> >> FORTRAN was proposed by Backus and friends, and again was opposed by >> almost all programmers. First, it was said it could not be done. Second, if >> it could be done, it would be too wasteful of machine time and capacity. >> Third, even if it did work, no respectable programmer would use it -- it >> was only for sissies! >> >> >> John von Neumann's reaction to assembly language and Fortran >> John A.N. Lee, Virginia Polytechnical Institute >> >> John von Neumann, when he first heard about FORTRAN in 1954, was >> unimpressed and asked "why would you want more than machine language?" One >> of von Neumann's students at Princeton recalled that graduate students were >> being used to hand assemble programs into binary for their early machine. >> This student took time out to build an assembler, but when von Neumann >> found out about it he was very angry, saying that it was a waste of a >> valuable scientific computing instrument to use it to do clerical >> work.[/quote] >> >> If is true that a real programmer would not stoop to wasting machine >> capacity to do the assembly, is an unfortunate fact the real programmers do >> use to wasting machine capacity to do the assembly, compilers... >> >> > _______________________________________________ > 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" -- Take care, Ty http://tds-solutions.net He that will not reason is a bigot; he that cannot reason is a fool; he that dares not reason is a slave. From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 18:28:59 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 919DFCA3; Fri, 19 Dec 2014 18:28:59 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::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 3501B2DEF; Fri, 19 Dec 2014 18:28:59 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so2772856wiv.11; Fri, 19 Dec 2014 10:28:57 -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=nImUziS9qEt8SBPgHRPHdtTagFGX7VNCIpitH2rhrZM=; b=GvUiuNiLj7Zw/igycdbJQHPmUPa0wmxDqoi5fdAg66xKpRLPio8NlO6XuJI8zWzPAm oEpHAHb8sGXMt7H3ZqyI2BHgFlti7PuLV+9egCZg4aAOecMjF+i3I1hgz7oCtq4QSs3Y 2HxPeBcn2ffmqV/2rhAyIorRr1AS8E32h5c6nWvudndeV/qcw3sK6c5Q+0VgQgN7F9T9 iVy5/RQzsH6p7ETlDGi8qqjHAZ5nRHQyzIoMyhNkNvyj4Bi6fUFGhPDJSVGCVwRLRN+q kUG4YrV9M42Lz1kCIwadk1KuKfsay5JJaTMqvVfTHVM9l0OLKIrWgZ3J5c32xiauLjDD OHXA== MIME-Version: 1.0 X-Received: by 10.194.85.83 with SMTP id f19mr17965185wjz.20.1419013737536; Fri, 19 Dec 2014 10:28:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Fri, 19 Dec 2014 10:28:57 -0800 (PST) In-Reply-To: References: Date: Fri, 19 Dec 2014 10:28:57 -0800 X-Google-Sender-Auth: L8YLXbR2yNwOpR8u3u3ghNW6Nxk Message-ID: Subject: Re: lighttpd crush the system after r274463 From: Adrian Chadd To: Andrey Fesenko , Gleb Smirnoff Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , freebsd-current 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, 19 Dec 2014 18:28:59 -0000 Hm, glebius? Any ideas? -adrian On 19 December 2014 at 02:27, Andrey Fesenko wrote: > Hello, > I'm use lighttpd+SPAWNFCGI for moinmoin wiki. > Before r274463 work fine, after update r275317 and CURRENT system > crushed after start any python CGI script. > > For test i'm install py27-flup and start simple > > #!/usr/local/bin/python2.7 > def myapp(environ, start_response): > start_response('200 OK', [('Content-Type', 'text/plain')]) > return ['Hello World!\n'] > > if __name__ == '__main__': > from flup.server.fcgi import WSGIServer > WSGIServer(myapp).run() > > Perl CGI test script work fine. > > Workaround FreeBSD-r275317 and later > > lighttpd-1.4.35_5 > Options : > BZIP2 : on > DOCS : on > FAM : on > GDBM : off > IPV6 : on > LDAP : off > LIBEV : on > LUA : on > MEMCACHE : off > MYSQL : off > MYSQLAUTH : off > NODELAY : on > OPENSSL : on > SPAWNFCGI : on > VALGRIND : off > WEBDAV : off > Shared Libs required: > libpcre.so.1 > liblua-5.1.so > libfam.so.0 > libev.so.4 > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x8 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff809d44bd > stack pointer = 0x28:0xfffffe00f77df700 > frame pointer = 0x28:0xfffffe00f77df730 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 658 (lighttpd) > [ thread pid 658 tid 100067 ] > Stopped at sbappendstream_locked+0x2d: cmpq $0,0x8(%r14) > db> bt > Tracing pid 658 tid 100067 td 0xfffff8000ba3e940 > sbappendstream_locked() at sbappendstream_locked+0x2d/frame 0xfffffe00f77df730 > sbappendstream() at sbappendstream+0x3c/frame 0xfffffe00f77df760 > tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfffffe00f77df7e0 > sosend_generic() at sosend_generic+0x40b/frame 0xfffffe00f77df8a0 > soo_write() at soo_write+0x42/frame 0xfffffe00f77df8d0 > dofilewrite() at dofilewrite+0x88/frame 0xfffffe00f77df920 > kern_writev() at kern_writev+0x68/frame 0xfffffe00f77df970 > sys_writev() at sys_writev+0x36/frame 0xfffffe00f77df9a0 > amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe00f77dfab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00f77dfab0 > --- syscall (121, FreeBSD ELF64, sys_writev), rip = 0x80164cb8a, rsp = > 0x7fffffffa658, rbp = 0x7fffffffe6 > c0 --- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 19:42:17 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 45D6E124; Fri, 19 Dec 2014 19:42:17 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (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 EE2161BF6; Fri, 19 Dec 2014 19:42:15 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3k40nx2j4SzZrR; Fri, 19 Dec 2014 20:41:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1419018115; x=1420832516; bh=edwPiOcvg4YBsAi8A8HixkUo3rQiAXDl7JGr7fNNC8g=; b= rbnpRJLgqyq+/bF07wvS7Q/GTFY3jAq3n/HtGiqpSzFcCe58mHlvWOs7pqsH0x+u QG5o6lLHcdeHwunAbDop7j6XVy2uwovNv14sRmCB+2gIdVaOvdhqwUk+1BHeongN q7rLWtw7PzYnddtcqkoCqmtkq1GynNjmELDVGgOrqMc= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 0CxCF4IWULzJ; Fri, 19 Dec 2014 20:41:55 +0100 (CET) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Fri, 19 Dec 2014 20:41:55 +0100 (CET) Message-ID: <54947F82.3090603@madpilot.net> Date: Fri, 19 Dec 2014 20:41:54 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Adrian Chadd , Andrey Fesenko , Gleb Smirnoff Subject: Re: lighttpd crush the system after r274463 References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" , freebsd-current 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, 19 Dec 2014 19:42:17 -0000 On 12/19/14 19:28, Adrian Chadd wrote: > Hm, glebius? Any ideas? > [...] >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0x8 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff809d44bd >> stack pointer = 0x28:0xfffffe00f77df700 >> frame pointer = 0x28:0xfffffe00f77df730 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 658 (lighttpd) >> [ thread pid 658 tid 100067 ] >> Stopped at sbappendstream_locked+0x2d: cmpq $0,0x8(%r14) >> db> bt >> Tracing pid 658 tid 100067 td 0xfffff8000ba3e940 >> sbappendstream_locked() at sbappendstream_locked+0x2d/frame 0xfffffe00f77df730 >> sbappendstream() at sbappendstream+0x3c/frame 0xfffffe00f77df760 >> tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfffffe00f77df7e0 >> sosend_generic() at sosend_generic+0x40b/frame 0xfffffe00f77df8a0 >> soo_write() at soo_write+0x42/frame 0xfffffe00f77df8d0 >> dofilewrite() at dofilewrite+0x88/frame 0xfffffe00f77df920 >> kern_writev() at kern_writev+0x68/frame 0xfffffe00f77df970 >> sys_writev() at sys_writev+0x36/frame 0xfffffe00f77df9a0 >> amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe00f77dfab0 >> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00f77dfab0 >> --- syscall (121, FreeBSD ELF64, sys_writev), rip = 0x80164cb8a, rsp = >> 0x7fffffffa658, rbp = 0x7fffffffe6 >> c0 --- Maybe I'm wrong but I see some similarities with what I reported with virtualbox. Bug 195822 has been filed about that. All information I have is there. Glebius already knows. -- Guido Falsi From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 19 20:46:12 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 030387C8; Fri, 19 Dec 2014 20:46:12 +0000 (UTC) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebius.int.ru", Issuer "cell.glebius.int.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FE4E29E7; Fri, 19 Dec 2014 20:46:10 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.9/8.14.9) with ESMTP id sBJKk6XY060519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 19 Dec 2014 23:46:06 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.9/8.14.9/Submit) id sBJKk64u060518; Fri, 19 Dec 2014 23:46:06 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 19 Dec 2014 23:46:06 +0300 From: Gleb Smirnoff To: Guido Falsi Subject: Re: lighttpd crush the system after r274463 Message-ID: <20141219204606.GD47144@glebius.int.ru> References: <54947F82.3090603@madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54947F82.3090603@madpilot.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , freebsd-current , Andrey Fesenko 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, 19 Dec 2014 20:46:12 -0000 On Fri, Dec 19, 2014 at 08:41:54PM +0100, Guido Falsi wrote: G> On 12/19/14 19:28, Adrian Chadd wrote: G> > Hm, glebius? Any ideas? I was quite busy last week, doing defense of my thesis. Now it is done, and I will look at the problem ASAP. -- Totus tuus, Glebius. From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 20 02:31:38 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 AED2FBB; Sat, 20 Dec 2014 02:31:38 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::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 3E2462D15; Sat, 20 Dec 2014 02:31:38 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id bs8so6289352wib.3; Fri, 19 Dec 2014 18:31:36 -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=uYe/1NUYGKbyF5Q3+Tbr/N5MLaSbHD8RBLXO9xZXcI8=; b=kVieJ0AQ5FJOWk4BEV719r93N5T7P3v5T50mwm5aebjJ8SkrOmzsrkI2wgkrF5Krwb T/Q4c5vWtu84n+lT8mu462KMQMLxZWtMhJupIlfEYDnJ/B9vaeDSqcl26IQ3SDxhP6Ny EtlioJiFy4lgyWql9LCaFKKAXn8hKF2elBaC1ePxM8pOiQW4U5Gpi7dEm6MHT+V6Z04F cszg48pKZu1WQ+jOfgqWc3a5NCrSptyH84DZcrUGq4VtBR1VM6ZM+dt/eorGKZD102QN vL2TzeUu9WI5QCJk/BzfkRtcHWvblEh+SQ86IW6R1bvYEdJZos8LDD5/j25oNr4+8L5V hc+w== MIME-Version: 1.0 X-Received: by 10.180.9.241 with SMTP id d17mr11057937wib.13.1419042696625; Fri, 19 Dec 2014 18:31:36 -0800 (PST) Received: by 10.194.216.226 with HTTP; Fri, 19 Dec 2014 18:31:36 -0800 (PST) In-Reply-To: <20141219204606.GD47144@glebius.int.ru> References: <54947F82.3090603@madpilot.net> <20141219204606.GD47144@glebius.int.ru> Date: Sat, 20 Dec 2014 06:31:36 +0400 Message-ID: Subject: Re: lighttpd crush the system after r274463 From: Andrey Fesenko To: Gleb Smirnoff Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , freebsd-current , Guido Falsi 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, 20 Dec 2014 02:31:38 -0000 On Fri, Dec 19, 2014 at 11:46 PM, Gleb Smirnoff wrote: > On Fri, Dec 19, 2014 at 08:41:54PM +0100, Guido Falsi wrote: > G> On 12/19/14 19:28, Adrian Chadd wrote: > G> > Hm, glebius? Any ideas? > > I was quite busy last week, doing defense of my thesis. Now it is > done, and I will look at the problem ASAP. > > -- > Totus tuus, Glebius. I found the problem seems to commit https://svnweb.freebsd.org/base/head/sys/kern/uipc_socket.c?r1=274712&r2=274711&pathrev=274712 if revert this, and rebuild kernel, system work fine.