From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 02:52:49 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6A61106568C for ; Sun, 23 Aug 2009 02:52:49 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 8F5CF8FC14 for ; Sun, 23 Aug 2009 02:52:49 +0000 (UTC) Received: from cauchy.math.missouri.edu (localhost [127.0.0.1]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id n7N2qkDm000654; Sat, 22 Aug 2009 21:52:46 -0500 (CDT) (envelope-from stephen@missouri.edu) Received: from localhost (redmail@localhost) by cauchy.math.missouri.edu (8.14.3/8.14.3/Submit) with ESMTP id n7N2qjYn000651; Sat, 22 Aug 2009 21:52:46 -0500 (CDT) (envelope-from stephen@missouri.edu) X-Authentication-Warning: cauchy.math.missouri.edu: redmail owned process doing -bs Date: Sat, 22 Aug 2009 21:52:45 -0500 (CDT) From: Stephen Montgomery-Smith X-X-Sender: redmail@cauchy.math.missouri.edu To: Julian Elischer In-Reply-To: <4A904E32.2010609@elischer.org> Message-ID: References: <4A8F986A.3040405@elischer.org> <20090822183105.00007262@unknown> <20090822184858.GC21946@elvis.mu.org> <4A903F8A.3010303@missouri.edu> <4A904E32.2010609@elischer.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 02:52:49 -0000 On Sat, 22 Aug 2009, Julian Elischer wrote: > Stephen Montgomery-Smith wrote: >> Alfred Perlstein wrote: >>> * Alexander Leidinger [090822 10:44] wrote: >>>> On Sat, 22 Aug 2009 00:04:10 -0700 Julian Elischer >>>> wrote: >>>> >>>>> The purists won out in that one by shouting loudly and screaming >>>>> about socialized healthware. Consequently we have 47 million >>>>> unsupported devices. >>>> You forgot to tell that now nobody wants to touch this subject anymore, >>>> as he may be the target of similar shouting then. >>> >>> I say good riddence, if someone wants thier hardware not to melt >>> then each machine should be personally responsible and enroll in >>> a private monitoring service we don't need project sponsored health >>> monitoring. >>> >>> (ron paul!) >>> >> >> I think that this kind of talk calls for boycotting certain device drivers! > > In OpenBSD they have project sponsored healthware and sometimes you have to > wait in a queue to get you notifications, and sometimes > the queue is so long events have to get merged! Not for me! > I want all my individual events to be lost After I get them. > It's my right! Perhaps you are getting too much information through the cable network. Your system might be getting all "wee weed." From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 04:12:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3CF7106564A for ; Sun, 23 Aug 2009 04:12:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 358F18FC13 for ; Sun, 23 Aug 2009 04:12:06 +0000 (UTC) Received: (qmail 11704 invoked by uid 399); 23 Aug 2009 04:12:02 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 23 Aug 2009 04:12:02 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A90C18C.7040907@FreeBSD.org> Date: Sat, 22 Aug 2009 21:11:56 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 CC: freebsd-hackers@freebsd.org References: <4A8F986A.3040405@elischer.org> <20090822183105.00007262@unknown> <20090822184858.GC21946@elvis.mu.org> <4A903F8A.3010303@missouri.edu> <4A904E32.2010609@elischer.org> In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 04:12:07 -0000 As terribly clever as you all are, can you please restrict the political commentary/humor/whatever to -chat? Thanks, Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 15:15:07 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A62F0106568D for ; Sun, 23 Aug 2009 15:15:07 +0000 (UTC) (envelope-from marc@msys.ch) Received: from sleipnir.msys.ch (smtp.msys.ch [157.161.101.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1423B8FC12 for ; Sun, 23 Aug 2009 15:15:06 +0000 (UTC) Received: from mail.msys.ch (smtp.msys.ch [157.161.101.10]) by sleipnir.msys.ch (8.14.3/8.14.1) with ESMTP id n7NFDhBZ016781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Aug 2009 17:13:43 +0200 (CEST) Received: from [192.168.17.107] (gw.vnode.ch [62.12.170.129]) (authenticated bits=0) by mail.msys.ch (8.14.3/8.14.1) with ESMTP id n7NFDg7x016208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 23 Aug 2009 17:13:42 +0200 (CEST) Message-Id: <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> From: Marc Balmer To: Alexander Leidinger In-Reply-To: <20090823170849.00000fdb@unknown> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 23 Aug 2009 17:13:42 +0200 References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> X-Mailer: Apple Mail (2.936) X-SMTP-Vilter-Version: 1.3.6 X-Spamd-Symbols: AWL Cc: =?ISO-8859-1?Q?=22Aur=E9lien_M=E9r=E9=22?= , Oliver Pinter , Gonzalo Nemmi , freebsd-hackers@FreeBSD.org Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 15:15:07 -0000 Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: > On Sat, 22 Aug 2009 21:02:32 +0200 "Aur=E9lien M=E9r=E9" > wrote: > >> I'm just afraid by reading your email that the situation doesn't seem >> to have evolved since the discussion regarding the SoC, maybe even >> more taboo, and that I'll have to keep writing my own software and >> drivers to get the data I want in the future if I want to get this >> data under FreeBSD.. Is it the case ? > > It is not "taboo", it is just that nobody wants to spend his spare =20 > time > with something like this now. > > And yes, as far as I know you have to keep writting our own stuff. But > maybe we can set up a wiki page where people can share their > FreeBSD specific stuff. Someone just has to be willing to invest some > time to add stuff. I have a little script which adds 24 values to > ganglia, and it's extensible (4 lines for wach value), e.g.: > ---snip--- > metrics=3D"${metrics} HD3_Temp" > HD3_Temp_value=3D"$(smartctl -A ad3 |awk '/Temperature_Celsius/ { = print > $10 }')" HD3_Temp_type=3D"uint8" > HD3_Temp_unit=3D"Celsius" > > metrics=3D"${metrics} logins" > logins_value=3D"$(who -q | grep users | cut -d ' ' -f 4)" > logins_type=3D"uint8" > logins_unit=3D"Users" > > metrics=3D"${metrics} SwapIn" > SwapIn_value=3D"$(sysctl vm.stats.vm.v_swapin | cut -d ' ' -f 2)" > SwapIn_type=3D"uint32" > SwapIn_unit=3D"Units" > ---snip--- > > I would add my script to such a wiki page, if some else is willing to > start such a page. such a script would indeed be much nicer than a well crafted framework =20= for the job. > If someone not @FreeBSD.org wants to maintain such a page, feel free =20= > to > register in the wiki and tell me (or another committer), I will hand =20= > out > write permission then. I hope people spend their time on thinking what was bad with the =20 sensor framework last time and improve on that, instead. > > Bye, > Alexander. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 16:39:36 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0FA7106568B for ; Sun, 23 Aug 2009 16:39:36 +0000 (UTC) (envelope-from marc@msys.ch) Received: from sleipnir.msys.ch (smtp.msys.ch [157.161.101.10]) by mx1.freebsd.org (Postfix) with ESMTP id 63DAE8FC13 for ; Sun, 23 Aug 2009 16:39:35 +0000 (UTC) Received: from mail.msys.ch (smtp.msys.ch [157.161.101.10]) by sleipnir.msys.ch (8.14.3/8.14.1) with ESMTP id n7NGcDrW012518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Aug 2009 18:38:13 +0200 (CEST) Received: from [192.168.17.107] (gw.vnode.ch [62.12.170.129]) (authenticated bits=0) by mail.msys.ch (8.14.3/8.14.1) with ESMTP id n7NGcC0n027562 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 23 Aug 2009 18:38:13 +0200 (CEST) Message-Id: <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> From: Marc Balmer To: Alexander Leidinger In-Reply-To: <20090823182454.00006387@unknown> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v936) Date: Sun, 23 Aug 2009 18:38:12 +0200 References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> <20090823182454.00006387@unknown> X-Mailer: Apple Mail (2.936) X-SMTP-Vilter-Version: 1.3.6 X-Spamd-Symbols: AWL Cc: =?ISO-8859-1?Q?=22Aur=E9lien_M=E9r=E9=22?= , Oliver Pinter , Gonzalo Nemmi , freebsd-hackers@FreeBSD.org Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 16:39:36 -0000 Am 23.08.2009 um 18:24 schrieb Alexander Leidinger: > On Sun, 23 Aug 2009 17:13:42 +0200 Marc Balmer wrote: > > >> >> Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: >> >>> On Sat, 22 Aug 2009 21:02:32 +0200 "Aur=E9lien M=E9r=E9" >>> wrote: >>> >>>> I'm just afraid by reading your email that the situation doesn't >>>> seem to have evolved since the discussion regarding the SoC, maybe >>>> even more taboo, and that I'll have to keep writing my own >>>> software and drivers to get the data I want in the future if I >>>> want to get this data under FreeBSD.. Is it the case ? >>> >>> It is not "taboo", it is just that nobody wants to spend his spare >>> time >>> with something like this now. >>> >>> And yes, as far as I know you have to keep writting our own stuff. >>> But maybe we can set up a wiki page where people can share their >>> FreeBSD specific stuff. Someone just has to be willing to invest >>> some time to add stuff. I have a little script which adds 24 values >>> to ganglia, and it's extensible (4 lines for wach value), e.g.: >>> ---snip--- >>> metrics=3D"${metrics} HD3_Temp" >>> HD3_Temp_value=3D"$(smartctl -A ad3 |awk '/Temperature_Celsius/ >>> { print $10 }')" HD3_Temp_type=3D"uint8" >>> HD3_Temp_unit=3D"Celsius" >>> >>> metrics=3D"${metrics} logins" >>> logins_value=3D"$(who -q | grep users | cut -d ' ' -f 4)" >>> logins_type=3D"uint8" >>> logins_unit=3D"Users" >>> >>> metrics=3D"${metrics} SwapIn" >>> SwapIn_value=3D"$(sysctl vm.stats.vm.v_swapin | cut -d ' ' -f 2)" >>> SwapIn_type=3D"uint32" >>> SwapIn_unit=3D"Units" >>> ---snip--- >>> >>> I would add my script to such a wiki page, if some else is willing >>> to start such a page. >> >> >> such a script would indeed be much nicer than a well crafted >> framework for the job. >> > > Indeed... > >>> If someone not @FreeBSD.org wants to maintain such a page, feel >>> free to >>> register in the wiki and tell me (or another committer), I will >>> hand out >>> write permission then. >> >> I hope people spend their time on thinking what was bad with the >> sensor framework last time and improve on that, instead. > > Go and read in the archives about it, maybe you understand why > there's not much motivation to spend spare time on such a topic. Everyone should have the right to come back with a subject, if work is =20= put into it. Or is the stanza that once there has been a heated =20 discussion about a topic, there is no possibility to come back to it, =20= maybe making it better a seccond time? And no, I have no plans to do =20= so... I am just a bit astonished about the attitude... From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 15:09:01 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB349106568B for ; Sun, 23 Aug 2009 15:09:01 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 8F5EE8FC08 for ; Sun, 23 Aug 2009 15:09:01 +0000 (UTC) Received: from outgoing.leidinger.net (pD954F4BC.dip.t-dialin.net [217.84.244.188]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 0F4B7844877; Sun, 23 Aug 2009 17:08:55 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.103]) by outgoing.leidinger.net (Postfix) with ESMTP id B711D88A50; Sun, 23 Aug 2009 17:08:51 +0200 (CEST) Date: Sun, 23 Aug 2009 17:08:49 +0200 From: Alexander Leidinger To: "=?ISO-8859-1?Q?Aur=E9lien_M=E9r=E9?=" Message-ID: <20090823170849.00000fdb@unknown> In-Reply-To: References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> X-Mailer: Claws Mail 3.7.2cvs15 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 0F4B7844877.371B4 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1.44, required 6, autolearn=disabled, ALL_TRUSTED -1.44) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1251644936.52941@Ec3rXq+oL5h4zcV2esaE3g X-EBL-Spam-Status: No X-Mailman-Approved-At: Sun, 23 Aug 2009 16:47:28 +0000 Cc: Gonzalo Nemmi , Oliver Pinter , Marc Balmer , freebsd-hackers@FreeBSD.org Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 15:09:01 -0000 On Sat, 22 Aug 2009 21:02:32 +0200 "Aur=E9lien M=E9r=E9" wrote: > I'm just afraid by reading your email that the situation doesn't seem > to have evolved since the discussion regarding the SoC, maybe even > more taboo, and that I'll have to keep writing my own software and > drivers to get the data I want in the future if I want to get this > data under FreeBSD.. Is it the case ? It is not "taboo", it is just that nobody wants to spend his spare time with something like this now. And yes, as far as I know you have to keep writting our own stuff. But maybe we can set up a wiki page where people can share their FreeBSD specific stuff. Someone just has to be willing to invest some time to add stuff. I have a little script which adds 24 values to ganglia, and it's extensible (4 lines for wach value), e.g.: ---snip--- metrics=3D"${metrics} HD3_Temp" HD3_Temp_value=3D"$(smartctl -A ad3 |awk '/Temperature_Celsius/ { print $10 }')" HD3_Temp_type=3D"uint8" HD3_Temp_unit=3D"Celsius" metrics=3D"${metrics} logins" logins_value=3D"$(who -q | grep users | cut -d ' ' -f 4)" logins_type=3D"uint8" logins_unit=3D"Users" metrics=3D"${metrics} SwapIn" SwapIn_value=3D"$(sysctl vm.stats.vm.v_swapin | cut -d ' ' -f 2)" SwapIn_type=3D"uint32" SwapIn_unit=3D"Units" ---snip--- I would add my script to such a wiki page, if some else is willing to start such a page. If someone not @FreeBSD.org wants to maintain such a page, feel free to register in the wiki and tell me (or another committer), I will hand out write permission then. Bye, Alexander. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 16:25:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AAFD1065672 for ; Sun, 23 Aug 2009 16:25:07 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id C3EE58FC0A for ; Sun, 23 Aug 2009 16:25:06 +0000 (UTC) Received: from outgoing.leidinger.net (pD954F4BC.dip.t-dialin.net [217.84.244.188]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id AEB85844877; Sun, 23 Aug 2009 18:24:59 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.103]) by outgoing.leidinger.net (Postfix) with ESMTP id A6D8768466; Sun, 23 Aug 2009 18:24:56 +0200 (CEST) Date: Sun, 23 Aug 2009 18:24:54 +0200 From: Alexander Leidinger To: Marc Balmer Message-ID: <20090823182454.00006387@unknown> In-Reply-To: <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> X-Mailer: Claws Mail 3.7.2cvs15 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: AEB85844877.CAD9B X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1.44, required 6, autolearn=disabled, ALL_TRUSTED -1.44) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1251649501.789@+eRXTBgs+5QQo1mqKuL+IA X-EBL-Spam-Status: No X-Mailman-Approved-At: Sun, 23 Aug 2009 16:47:39 +0000 Cc: =?ISO-8859-1?Q?Aur=E9lien_M=E9r=E9?= , Oliver Pinter , Gonzalo Nemmi , freebsd-hackers@FreeBSD.org Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 16:25:07 -0000 On Sun, 23 Aug 2009 17:13:42 +0200 Marc Balmer wrote: >=20 > Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: >=20 > > On Sat, 22 Aug 2009 21:02:32 +0200 "Aur=E9lien M=E9r=E9" > > wrote: > > > >> I'm just afraid by reading your email that the situation doesn't > >> seem to have evolved since the discussion regarding the SoC, maybe > >> even more taboo, and that I'll have to keep writing my own > >> software and drivers to get the data I want in the future if I > >> want to get this data under FreeBSD.. Is it the case ? > > > > It is not "taboo", it is just that nobody wants to spend his spare =20 > > time > > with something like this now. > > > > And yes, as far as I know you have to keep writting our own stuff. > > But maybe we can set up a wiki page where people can share their > > FreeBSD specific stuff. Someone just has to be willing to invest > > some time to add stuff. I have a little script which adds 24 values > > to ganglia, and it's extensible (4 lines for wach value), e.g.: > > ---snip--- > > metrics=3D"${metrics} HD3_Temp" > > HD3_Temp_value=3D"$(smartctl -A ad3 |awk '/Temperature_Celsius/ > > { print $10 }')" HD3_Temp_type=3D"uint8" > > HD3_Temp_unit=3D"Celsius" > > > > metrics=3D"${metrics} logins" > > logins_value=3D"$(who -q | grep users | cut -d ' ' -f 4)" > > logins_type=3D"uint8" > > logins_unit=3D"Users" > > > > metrics=3D"${metrics} SwapIn" > > SwapIn_value=3D"$(sysctl vm.stats.vm.v_swapin | cut -d ' ' -f 2)" > > SwapIn_type=3D"uint32" > > SwapIn_unit=3D"Units" > > ---snip--- > > > > I would add my script to such a wiki page, if some else is willing > > to start such a page. >=20 > > such a script would indeed be much nicer than a well crafted > framework for the job. > Indeed... > > If someone not @FreeBSD.org wants to maintain such a page, feel > > free to > > register in the wiki and tell me (or another committer), I will > > hand out > > write permission then. >=20 > I hope people spend their time on thinking what was bad with the =20 > sensor framework last time and improve on that, instead. Go and read in the archives about it, maybe you understand why there's not much motivation to spend spare time on such a topic. Bye, Alexander. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 23 17:11:16 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F767106564A for ; Sun, 23 Aug 2009 17:11:16 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id D88B88FC0C for ; Sun, 23 Aug 2009 17:11:15 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 22so384367eye.7 for ; Sun, 23 Aug 2009 10:11:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=w8dRWnsziCCTuzsLo5hWxg6QgEvusALDtyKXsMxrB40=; b=h8g1Uk0oXZW1Y9nVk+jtGIQGq0T/r3mVmmE8tZ7b5Y+CRoOnHqL6U+RI37qWUqIkNw KcyJh7sKejgYuTcFVAoUn9N8XkwoZ1z54hMNyB40Ti1kYbarw/Fen+XbzSAuqm8pVRLC dP3V/XdaNQMjIV04NGtiJt9IreXi5s+qmO2+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=o9Y1CoZYKkiwq1+pDaOrk0PTPvfHHxdBiQyQW2Pyt0rtqIMtoKJiqzywoRvaELlHUr yN2NwJvoAhRPU+OYSI7mW4yDpoXKaR8hw4ZjNfWFwRO2Than0ncN0tx11VQzidLlrkN2 LA2lDo6gNKDEySEQHUQI4uU9Zc01W7LEijmUA= Received: by 10.210.140.18 with SMTP id n18mr3806741ebd.13.1251047474867; Sun, 23 Aug 2009 10:11:14 -0700 (PDT) Received: from localhost (bl6-144-173.dsl.telepac.pt [82.155.144.173]) by mx.google.com with ESMTPS id 10sm6962409eyd.14.2009.08.23.10.11.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Aug 2009 10:11:14 -0700 (PDT) Sender: Rui Paulo Date: Sun, 23 Aug 2009 18:11:12 +0100 From: Rui Paulo To: Marc Balmer Message-ID: <20090823171112.GB2390@mac-mini.lan> References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> <20090823182454.00006387@unknown> <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Alexander Leidinger , Oliver Pinter , Gonzalo Nemmi , freebsd-hackers@FreeBSD.org, =?iso-8859-1?B?IkF1culsaWVuIE3pcuki?= Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 17:11:16 -0000 On Sun, Aug 23, 2009 at 06:38:12PM +0200, Marc Balmer wrote: > Everyone should have the right to come back with a subject, if work > is put into it. Or is the stanza that once there has been a heated > discussion about a topic, there is no possibility to come back to > it, maybe making it better a seccond time? And no, I have no plans > to do so... I am just a bit astonished about the attitude... I think what Alexander was trying to say was that, given the heated discussion last time, people are now reluctant to restart another discussion. From what I remember, it was very hard to understand why such a large number of messages was being created for such a small detail. Topics, such as these, pose a high risk of making your FreeBSD developer experience more painful than it should be. And since I believe a lot of people here like to work on FreeBSD, sometimes these types of discussions are avoided for a long time just because the developer(s) doesn't(don't) want to make their FreeBSD development experience any more painful. I believe that if we keep insisting on the same bikesheds for a long time, developers will defintely go away. So, there's no ``stanza'' or whatever, just human nature. Regardless of what I just said, the topic keeps coming back and that's a clear sign that a framework should be developed and, possibly, in a way that appeals to both parties. -- Rui Paulo From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 01:01:12 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B24F10656B0 for ; Mon, 24 Aug 2009 01:01:12 +0000 (UTC) (envelope-from lists@mawer.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id C3D498FC3E for ; Mon, 24 Aug 2009 01:01:09 +0000 (UTC) Received: by rv-out-0506.google.com with SMTP id l9so796148rvb.3 for ; Sun, 23 Aug 2009 18:01:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.135.20 with SMTP id i20mr1930264rvd.145.1251074086845; Sun, 23 Aug 2009 17:34:46 -0700 (PDT) In-Reply-To: <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> <20090823182454.00006387@unknown> <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> Date: Mon, 24 Aug 2009 10:34:46 +1000 Message-ID: From: Antony Mawer To: Marc Balmer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Alexander Leidinger , Oliver Pinter , Gonzalo Nemmi , freebsd-hackers@freebsd.org, =?ISO-8859-1?B?IkF1culsaWVuIE3pcuki?= Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 01:01:15 -0000 On Mon, Aug 24, 2009 at 2:38 AM, Marc Balmer wrote: > Am 23.08.2009 um 18:24 schrieb Alexander Leidinger: >> On Sun, 23 Aug 2009 17:13:42 +0200 Marc Balmer wrote: >>> Am 23.08.2009 um 17:08 schrieb Alexander Leidinger: >>>> On Sat, 22 Aug 2009 21:02:32 +0200 "Aur=E9lien M=E9r=E9" >>>> wrote: >>>> >>>>> I'm just afraid by reading your email that the situation doesn't >>>>> seem to have evolved since the discussion regarding the SoC, maybe >>>>> even more taboo, and that I'll have to keep writing my own >>>>> software and drivers to get the data I want in the future if I >>>>> want to get this data under FreeBSD.. Is it the case ? >>>> >>>> It is not "taboo", it is just that nobody wants to spend his spare >>>> time >>>> with something like this now. >>>> >>> >>> I hope people spend their time on thinking what was bad with the >>> sensor framework last time and improve on that, instead. >> >> Go and read in the archives about it, maybe you understand why >> there's not much motivation to spend spare time on such a topic. > > Everyone should have the right to come back with a subject, if work is pu= t > into it. =A0Or is the stanza that once there has been a heated discussion > about a topic, there is no possibility to come back to it, maybe making i= t > better a seccond time? =A0And no, I have no plans to do so... I am just a= bit > astonished about the attitude... I for one would be quite happy to contribute towards such an effort. I would much rather contribute towards a project-wide monitoring solution rather than continuing to extend/maintain my own ad-hoc monitoring scripts. I am sure many others are in a similar position... it seems crazy that we are all re-inventing the wheel instead of contributing to a common effort. Is there a summary (perhaps something suitable to go on the Project Ideas page) that outlines: - An outline of what such a system should provide - What it should NOT provide (ie. what would be "out of scope") - What lessons should be learned from the SoC effort (ie. both good points and what NOT to do) - Suggested starting points Maybe that would go a long way to ensuring anyone wanting to start such an effort without getting to the end and having their efforts rejected... Yes, bits of this can be found in the past mailing list posts, but it would nice to have an clear "official" summary of this so that any volunteer effort has the best chance of being accepted... -- Antony From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 07:46:04 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39C57106568B for ; Mon, 24 Aug 2009 07:46:04 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id B3B738FC08 for ; Mon, 24 Aug 2009 07:46:03 +0000 (UTC) Received: by fxm6 with SMTP id 6so1234545fxm.43 for ; Mon, 24 Aug 2009 00:46:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:to:subject:organization:from :date:message-id:user-agent:mime-version:content-type; bh=bSJcLjO1HDDeyq3AwVwjgGplKB/eBLIqgHmCMTQxNbk=; b=vstv0+4a86/MwhWXv5hGFqJI85u/nkG7zcHNMEcI9vbYeAf4nBcuFGYyUNLAgMOlPx in1yEA7ZRJc3Szq2TnXuHj0Dv+Abx8yZTs8caeJjS3BimFKZJr//lDVx0xiFcIMUcLDD +j6UK8EP4kPosxbWebd8oZtBiP4o36WLailsE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:subject:organization:from:date:message-id:user-agent :mime-version:content-type; b=RUEyBBOV3DxsNwyAkEOpQpokTSITiYW20rjNRMDGy8qOOEpKFoa55em9h/08RreKSN cGKBzGkDTGW2Ef/lycjv7nUJ2A6OI/l7je/mlX+TeajtvAB734kh7KW48rAgr4jFYrKb u9Ffbcfo9rZy5EM4J3a/Yca4B3PQ5/s8nwx30= Received: by 10.103.81.21 with SMTP id i21mr1725863mul.57.1251099962563; Mon, 24 Aug 2009 00:46:02 -0700 (PDT) Received: from localhost ([95.69.167.4]) by mx.google.com with ESMTPS id e9sm20133124muf.2.2009.08.24.00.46.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Aug 2009 00:46:01 -0700 (PDT) To: freebsd-hackers@freebsd.org Organization: TOA Ukraine From: Mikolaj Golub Date: Mon, 24 Aug 2009 10:45:58 +0300 Message-ID: <86ws4tejt5.fsf@kopusha.onet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Partial kvm dumps X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 07:46:04 -0000 Hi, I would like to discuss the idea of partial kvm dumps -- the possibility of creating dumps of some parts of the kernel memory from the live system, which later could be read via KVM interface. Why this could be useful. I suppose many people here happened to set up scripts to run utilies like ps, vmstat, top etc periodically to collect system statistics and analyse system behaviour when problems happened. I did this so often that eventually wrote perl script -- wrapper around these utilities to make the setup and later data analysis easier. http://code.google.com/p/gatherit/wiki/README Currently I run this script on most of my servers collecting various statistics about a system. But I feel some discomfort from the fact that this is rather inefficient. Here is typical list of commands I use to collect data: $ ./gather show utils -------------------------------------------------------------------------------- name cmd desc -------------------------------------------------------------------------------- devstat /usr/local/bin/devstat devstat output df /bin/df df output fstat /usr/bin/fstat fstat output netstat-La /usr/bin/netstat -nLa netstat listening socket statistics netstat-a /usr/bin/netstat -na netstat socket statistics netstat-i /usr/bin/netstat -ni netstat interface statistics netstat-m /usr/bin/netstat -m netstat mbuf statistics netstat-r /usr/bin/netstat -nr netstat routing tables netstat-rs /usr/bin/netstat -rs netstat routing statistics netstat-s /usr/bin/netstat -s netstat system wide statistics nfsstat /usr/bin/nfsstat nfsstat output ps /bin/ps auxww processes statistics (-u flag) ps-l /bin/ps alxww processes statistics (-l flag) sockstat /usr/bin/sockstat sockstat output sysctl /sbin/sysctl -a sysctl variables top /usr/bin/top -d1 -S -b 1000 top output (cpu mode) top-mio /usr/bin/top -d1 -S -mio -b 1000 top output (io mode) uptime /usr/bin/uptime system uptime vmstat /usr/bin/vmstat vmstat output vmstat-i /usr/bin/vmstat -ai vmstat interupts statistics Note, many utilities are run several times but with different parameters, also there are comands that do almost the same (e.g. netstat -a and sockstat), processing the same kernel structures. I want them all to run because I don't know in advance what output will turn out more usefull in certain circumstances. It would be more efficient to have some one utility that whould traverse kernel structures extracting all necessary data and later on need this data would be converted to human readable output. And actually we have almost everything for this to work. Many of the system utilities can output data not only from live system but from core dumps too. So if we created dumps from live systems periodically then later we would use them to extract system statistics. Of course there is a little sense in dumping the whole kernel memory. We could extend our KVM interface to have the possibility of creating and then later reading dumps that would contain only necessary parts of kernel memory. As proof of the concept I have written pkvmdump utility that creates partial dumps with some kernel statistics, which can be later exctracted by vmstat and ps utilities. The details of the current implementation: Generated dump has simple format: dump header (struct minidumphdr is used with PKVMDUMP_MAGIC) and data entries. Each data entry has header (address of extracted data in kvm and its lenth) + data itself. So the generation of a dump is very simple -- kvm_open(3) /dev/mem, read necessary regions of memory and write to dump prepending with [addr, len] header. To read the dump the libkvm interface has been extended. The following trick (hack? :-) is used: On kvm_open(): 1) create temporary (unlinked) file; 2) for every data entry from the dump do in tempfile: lseek(addr, SEEK_SET), write(data, len); 3) close dump file and set kd->pmfd to point to tempfile. On kvm_read() the request is translated to direct read from the tempfile. This format/algorithm has been chosen becase of simplicity of implementation, just to start experimenting with this. You can find the source here: http://code.google.com/p/trociny/downloads/list I would like to hear what other people think about this. It looks very useful for me. At least as a first step it would be nice to extend KVM to work with partial dumps so the users could try this and see if it turned out to be useful. P.S. The final goal I would like to achive is to make snapshots of system state, which could be used for later analysis if necessary. May be the approach I try here is wrong. E.g. SNMP looks like more proper alternative solution -- this is standard, also snmpd is actually that program which "traverse kernel structures extracting all necessary data". But SNMP has its own limitations, statistics provided via SNMP are rather limited and currently I don't see how I could use it effectively to echieve my goal, althogh I haven't think much in this direction yet... -- Mikolaj Golub From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 08:23:14 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13837106568B; Mon, 24 Aug 2009 08:23:14 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id ABFE98FC16; Mon, 24 Aug 2009 08:23:13 +0000 (UTC) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 939961CECF; Mon, 24 Aug 2009 10:23:12 +0200 (CEST) Date: Mon, 24 Aug 2009 10:23:12 +0200 From: Ed Schouten To: freebsd-hackers@FreeBSD.org Message-ID: <20090824082312.GD2829@hoeg.nl> References: <20090822191207.GP1292@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d9ADC0YsG2v16Js0" Content-Disposition: inline In-Reply-To: <20090822191207.GP1292@hoeg.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: kmacy@FreeBSD.org Subject: Re: CFT: Patch for the Xen console driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 08:23:14 -0000 --d9ADC0YsG2v16Js0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Ed Schouten wrote: > Are there any (8.0-)users here who can test the attached patch for me? No, there aren't. Well, I'll commit it to HEAD. If it turns out that it breaks stuff, I'll give the person who reports it a glass of beer if we ever meet in person. ;-) --=20 Ed Schouten WWW: http://80386.nl/ --d9ADC0YsG2v16Js0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqSTfAACgkQ52SDGA2eCwXkJgCcCyUTt7gVZ9se/jDZwewxwzyK 4gIAnjz1Ougxw6Neczi8P647rULsd3T3 =t//g -----END PGP SIGNATURE----- --d9ADC0YsG2v16Js0-- From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 08:54:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76494106568C for ; Mon, 24 Aug 2009 08:54:41 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4C8C98FC16 for ; Mon, 24 Aug 2009 08:54:41 +0000 (UTC) Received: from eagle.syrec.org (c-24-6-221-126.hsd1.ca.comcast.net [24.6.221.126]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n7O8seDW093751 for ; Mon, 24 Aug 2009 01:54:40 -0700 (PDT) Message-ID: <4A92554F.1040506@rawbw.com> Date: Mon, 24 Aug 2009 01:54:39 -0700 From: Yuri User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ral0 interface hangs with the message "No buffer space available" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 08:54:41 -0000 Almost every time when I leave system to download a large file I get ral device inoperable after a while. Pinging the other peer causes these messages: > ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available I don't believe that TCP buffer is legitimately filled up to the max because after I bring it down and back up it works fine for a long while. So why didn't this data go through before down/up? If TCP connections are slow buffers shouldn't just fill up: system can and should be preventing this letting apps to hold data streams. Something isn't quite right. Why would network device hang in a steady download scenaio? 7.2-STABLE Yuri From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 11:08:01 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDBE810656A8 for ; Mon, 24 Aug 2009 11:08:01 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout3.freenet.de (mout3.freenet.de [IPv6:2001:748:100:40::2:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0788FC24 for ; Mon, 24 Aug 2009 11:08:01 +0000 (UTC) Received: from [195.4.92.13] (helo=3.mx.freenet.de) by mout3.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #92) id 1MfXP5-0004uW-MP; Mon, 24 Aug 2009 13:07:59 +0200 Received: from td106.t.pppool.de ([89.55.209.6]:33080 helo=ernst.jennejohn.org) by 3.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1MfXP5-0004Ce-4K; Mon, 24 Aug 2009 13:07:59 +0200 Date: Mon, 24 Aug 2009 13:07:57 +0200 From: Gary Jennejohn To: yuri@rawbw.com Message-ID: <20090824130757.560757fa@ernst.jennejohn.org> In-Reply-To: <4A92554F.1040506@rawbw.com> References: <4A92554F.1040506@rawbw.com> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-purgate-ID: 149285::1251112079-00002DCE-ECFCB365/0-0/0-0 Cc: freebsd-hackers@freebsd.org Subject: Re: ral0 interface hangs with the message "No buffer space available" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 11:08:01 -0000 On Mon, 24 Aug 2009 01:54:39 -0700 Yuri wrote: > Almost every time when I leave system to download a large file I get ral > device inoperable after a while. > Pinging the other peer causes these messages: > > > ping 192.168.0.1 > PING 192.168.0.1 (192.168.0.1): 56 data bytes > ping: sendto: No buffer space available > ping: sendto: No buffer space available > > I don't believe that TCP buffer is legitimately filled up to the max > because after I bring it down and back up it works fine for a long > while. So why didn't this data go through before down/up? > > If TCP connections are slow buffers shouldn't just fill up: system can > and should be preventing this letting apps to hold data streams. > > Something isn't quite right. > > Why would network device hang in a steady download scenaio? > > 7.2-STABLE > The buffers aren't full, it's the send queue used by whichever driver it is which you are using. The down/up frees it up because all queued transmits are discarded. This should never happen in normal operation. You haven't really provided any useful information to allow further analysis. --- Gary Jennejohn From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 05:35:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55FED106568D for ; Mon, 24 Aug 2009 05:35:34 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id D783B8FC19 for ; Mon, 24 Aug 2009 05:35:33 +0000 (UTC) Received: from outgoing.leidinger.net (pD9E2CBB6.dip.t-dialin.net [217.226.203.182]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 02D4084403A; Mon, 24 Aug 2009 07:35:26 +0200 (CEST) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id A7CC1686AA; Mon, 24 Aug 2009 07:35:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1251092122; bh=kCTV/F+uSwjbiGFKZrIyvyCp5bRnNywuw/5mmMYOeYM=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=F+fEv5278iAJtvwfhkVHO1IamH0pmx3ccKIwHUed0WJT7v4t1hnrnr+dpzYiGSmi9 pxYRlu29SK+yYAhb7oMezgcWDqksTEL0QGnhFoOCdkUJDHLOvUnlGkfGyk8qMhQew0 TpoNO9FI+3YR7GtiYlG7yKpXHyEWZfzAPknprX0A1Sy0YBcbXC8keCRVdbnRZtZCPB TKaSzL4CXD/uJm/F+vS80gl2nu2xc+jGuJJijbkbt0vSyCOmxFUZcp+Ss8eit9pMJk uAZIoWSAYcWarrzLDUQKN0piaTlKJjzP4QfATM1BkrY+IPfAgHLx7ZuUcNm6ifPqtQ 4BHxMEEg+m1NA== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n7O5ZLUc062898; Mon, 24 Aug 2009 07:35:21 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Mon, 24 Aug 2009 07:35:20 +0200 Message-ID: <20090824073520.642366ipfkqbers4@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 24 Aug 2009 07:35:20 +0200 From: Alexander Leidinger To: Antony Mawer References: <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> <20090822182923.000064e0@unknown> <20090823170849.00000fdb@unknown> <7306B4ED-D9AF-4946-9FCE-BD1CE7685AC2@msys.ch> <20090823182454.00006387@unknown> <843B14C2-D6D0-4910-B1B4-C7A8CB37635D@msys.ch> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.3.3 / FreeBSD-8.0 X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 02D4084403A.79111 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1.44, required 6, autolearn=disabled, ALL_TRUSTED -1.44, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1251696926.44805@AnmUMzkSWVQJ6bfuziWu4w X-EBL-Spam-Status: No X-Mailman-Approved-At: Mon, 24 Aug 2009 11:39:00 +0000 Cc: =?utf-8?b?TcOpcsOp?= , Marc Balmer , =?utf-8?b?QXVyw6lsaWVuIA==?=, Oliver Pinter , freebsd-hackers@freebsd.org, Gonzalo Nemmi Subject: Re: Common interface for sensors/health monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 05:35:34 -0000 Quoting Antony Mawer (from Mon, 24 Aug 2009 10:34:46 +1000): > On Mon, Aug 24, 2009 at 2:38 AM, Marc Balmer wrote: > Is there a summary (perhaps something suitable to go on the Project > Ideas page) that outlines: > > - An outline of what such a system should provide > - What it should NOT provide (ie. what would be "out of scope") > - What lessons should be learned from the SoC effort (ie. both good > points and what NOT to do) > - Suggested starting points There's nothing like this. The big controversy in the discussion is, that one party wants to put a lot of processing and logic into the kernel (IMO over-engineered), and the GSoC-party wants to keep this complexity out of the kernel (why doing stuff in the kernel when it can be done in the userland, there's no need to get the last few % of performance out of this). Other things discussed there (providing the data via sysctl or via a binary interface in /dev/) are minor implementation details which do not really matter that much (the argument of the GSoC-party was that we already have the sysctl interface and use it already for similar things like process monitoring (kern.proc.*), and it also usable in single-user mode without the need to write another decoding utility for this new binary data). Bye, Alexander. -- Computers are not intelligent. They only think they are. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 12:30:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1F111065695 for ; Mon, 24 Aug 2009 12:30:43 +0000 (UTC) (envelope-from cwf-ml@arcor.de) Received: from mail.arcor.net (mail.arcor.net [145.253.32.2]) by mx1.freebsd.org (Postfix) with ESMTP id 60C7F8FC1C for ; Mon, 24 Aug 2009 12:30:42 +0000 (UTC) Received: from mail-gw.arcor.net (sunmaildns01.arcor.net [10.128.4.73]) by mail.arcor.net (8.13.8/8.13.8) with ESMTP id n7OCBORi025422 for ; Mon, 24 Aug 2009 14:11:24 +0200 (MEST) Received: from agvvodmail01.arcor.net (esbanl-1ug-1-p2.arcor.net [10.128.5.69]) by mail-gw.arcor.net (8.13.8/8.13.8) with ESMTP id n7OCBOJd009039 for ; Mon, 24 Aug 2009 14:11:24 +0200 (MEST) Received: from sky.tnd.arcor.net (esbanl-1ug-1-p2.arcor.net [10.128.5.69]) by agvvodmail01.arcor.net (Postfix) with ESMTP id 98EB8CDA for ; Mon, 24 Aug 2009 14:11:24 +0200 (MEST) Received: from [10.128.19.15] (unknown [10.128.19.15]) by sky.tnd.arcor.net (Postfix) with ESMTP id 63CBB2F31 for ; Mon, 24 Aug 2009 14:11:24 +0200 (MEST) Message-ID: <4A92836B.2010206@arcor.de> Date: Mon, 24 Aug 2009 14:11:23 +0200 From: Christoph Weber-Fahr User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4A92554F.1040506@rawbw.com> In-Reply-To: <4A92554F.1040506@rawbw.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: is there any chance to get HP blade servers supported again? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 12:30:43 -0000 Hello, is there any chance to get HP blade servers (BL460, BL465) supported again? They used to be supported until G5, but the most recent generation doesn't work with FrreeBSD (no support for the network controllers). Does anbody have more information on this? (I asked on .hardware a few weeks ago, but got no information). Regards Christoph Weber-Fahr From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 12:43:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF098106568C for ; Mon, 24 Aug 2009 12:43:50 +0000 (UTC) (envelope-from marc@msys.ch) Received: from sleipnir.msys.ch (unknown [IPv6:2001:4060:c0de:f000::3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6E68FC14 for ; Mon, 24 Aug 2009 12:43:50 +0000 (UTC) Received: from mail.msys.ch (smtp.msys.ch [157.161.101.10]) by sleipnir.msys.ch (8.14.3/8.14.1) with ESMTP id n7OChgt0019557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Aug 2009 14:43:42 +0200 (CEST) Received: from dhcp-168.msys.ch (dhcp-168.msys.ch [157.161.101.168]) (authenticated bits=0) by mail.msys.ch (8.14.3/8.14.1) with ESMTP id n7OChgq3006445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 24 Aug 2009 14:43:42 +0200 (CEST) Message-Id: From: Marc Balmer To: Christoph Weber-Fahr In-Reply-To: <4A92836B.2010206@arcor.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 24 Aug 2009 14:43:42 +0200 References: <4A92554F.1040506@rawbw.com> <4A92836B.2010206@arcor.de> X-Mailer: Apple Mail (2.936) X-SMTP-Vilter-Version: 1.3.6 X-Spamd-Symbols: AWL Cc: freebsd-hackers@freebsd.org Subject: Re: is there any chance to get HP blade servers supported again? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 12:43:51 -0000 > is there any chance to get HP blade servers (BL460, BL465) supported > again? > > They used to be supported until G5, but the most recent generation > doesn't work with FrreeBSD (no support for the network controllers). > > Does anbody have more information on this? > > (I asked on .hardware a few weeks ago, but got no information). We just installed FreeBSD 8.0BETA3 (i386) on two HP BL460C, quad Xeon, with HP smart Array200i and QLogic QMH2462 4Gb FC HBA and networking works. At least that's what my colleague, who is onsite, just told me on the phone. - Marc Balmer From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 13:37:24 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB6C0106568D for ; Mon, 24 Aug 2009 13:37:24 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5F4AF8FC0A for ; Mon, 24 Aug 2009 13:37:23 +0000 (UTC) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id n7ODJmxN087660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Aug 2009 15:19:48 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id n7ODJguY009843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Aug 2009 15:19:42 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id n7ODJgC2025224; Mon, 24 Aug 2009 15:19:42 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id n7ODJgm9025223; Mon, 24 Aug 2009 15:19:42 +0200 (CEST) (envelope-from ticso) Date: Mon, 24 Aug 2009 15:19:42 +0200 From: Bernd Walter To: Christoph Weber-Fahr Message-ID: <20090824131941.GL20020@cicely7.cicely.de> References: <4A92554F.1040506@rawbw.com> <4A92836B.2010206@arcor.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A92836B.2010206@arcor.de> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.043, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-hackers@freebsd.org Subject: Re: is there any chance to get HP blade servers supported again? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 13:37:24 -0000 On Mon, Aug 24, 2009 at 02:11:23PM +0200, Christoph Weber-Fahr wrote: > Hello, > > is there any chance to get HP blade servers (BL460, BL465) supported again? > > They used to be supported until G5, but the most recent generation > doesn't work with FrreeBSD (no support for the network controllers). So they've never worked and there is no regression at all. This is always the problem with new hardware - someone needs to write the drivers and before doing that someone need to beg vendors for specs. Unless someone with time and hardwarespecs come up there is no chance. Use another NIC as temporary workaround. > Does anbody have more information on this? > > (I asked on .hardware a few weeks ago, but got no information). Probably because noone has informations? -network list would be an option to get in touch with network people. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 18:46:59 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17F22106568B for ; Mon, 24 Aug 2009 18:46:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id E0C0F8FC1A for ; Mon, 24 Aug 2009 18:46:58 +0000 (UTC) Received: from eagle.syrec.org (c-24-6-221-126.hsd1.ca.comcast.net [24.6.221.126]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n7OIkvrZ018280; Mon, 24 Aug 2009 11:46:57 -0700 (PDT) Message-ID: <4A92E020.9020502@rawbw.com> Date: Mon, 24 Aug 2009 11:46:56 -0700 From: Yuri User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <4A92554F.1040506@rawbw.com> <20090824130757.560757fa@ernst.jennejohn.org> In-Reply-To: <20090824130757.560757fa@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: ral0 interface hangs with the message "No buffer space available" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 18:46:59 -0000 Gary Jennejohn wrote: > You haven't really provided any useful information to allow further analysis What would be "useful information"? 'netstat -m' is one. Anything else? Yuri From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 24 21:27:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 933731065690 for ; Mon, 24 Aug 2009 21:27:42 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4CAE38FC0C for ; Mon, 24 Aug 2009 21:27:42 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mfh4m-00075t-Pr for freebsd-hackers@freebsd.org; Mon, 24 Aug 2009 23:27:40 +0200 Received: from 93-138-250-165.adsl.net.t-com.hr ([93.138.250.165]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Aug 2009 23:27:40 +0200 Received: from ivoras by 93-138-250-165.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Aug 2009 23:27:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Mon, 24 Aug 2009 23:27:07 +0200 Lines: 35 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFCAE28F21D739F83D169C535" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-138-250-165.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) X-Enigmail-Version: 0.96.0 Sender: news Subject: Parallel port headers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 21:27:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFCAE28F21D739F83D169C535 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, At least one on-line tutorial about parallel port hacking (http://www.excamera.com/articles/21/parallel.html) uses these header fil= es: #include #include They are actually present in /sys, but not in the normal userland include paths. Is this intentional, or was it removed sometimes in the pa= st? --------------enigFCAE28F21D739F83D169C535 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqTBawACgkQldnAQVacBci5TQCfZxONyRvPsvgAmZ1NnP5yDinl pQYAoKrF+8HkwTbE6yDHHnJnTVXJyAL6 =kmDw -----END PGP SIGNATURE----- --------------enigFCAE28F21D739F83D169C535-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 03:22:05 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56153106568B for ; Tue, 25 Aug 2009 03:22:05 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 43D098FC23 for ; Tue, 25 Aug 2009 03:22:04 +0000 (UTC) Received: from eagle.syrec.org (c-24-6-221-126.hsd1.ca.comcast.net [24.6.221.126]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n7P3M3HP019335 for ; Mon, 24 Aug 2009 20:22:03 -0700 (PDT) Message-ID: <4A9358DA.9080509@rawbw.com> Date: Mon, 24 Aug 2009 20:22:02 -0700 From: Yuri User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4A92554F.1040506@rawbw.com> In-Reply-To: <4A92554F.1040506@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ral0 interface hangs with the message "No buffer space available" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 03:22:05 -0000 Here's additional information: 'netstat -m' output: 174/2931/3105 mbufs in use (current/cache/total) 68/1892/1960/25600 mbuf clusters in use (current/cache/total/max) 68/1114 mbuf+clusters out of packet secondary zone in use (current/cache) 0/1327/1327/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 179K/9824K/10004K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/14/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 25 requests for I/O initiated by sendfile 0 calls to protocol drain routines ifconfig ral0: ral0: flags=8c43 metric 0 mtu 1500 ether 00:18:f8:2e:40:25 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/48Mbps) status: associated ssid "xxx xxx xxx" channel 6 (2437 Mhz 11g) bssid 00:0c:41:53:e6:71 authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpower 50 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 03:41:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B9ED106568D; Tue, 25 Aug 2009 03:41:21 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id A44B98FC13; Tue, 25 Aug 2009 03:41:20 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n7P3fITi012268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 25 Aug 2009 13:11:18 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 25 Aug 2009 13:11:04 +0930 User-Agent: KMail/1.9.10 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1386211.b6zfeR6ZaB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200908251311.12503.doconnor@gsoft.com.au> X-Spam-Score: -3.603 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Ivan Voras Subject: Re: Parallel port headers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 03:41:21 -0000 --nextPart1386211.b6zfeR6ZaB Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 25 Aug 2009, Ivan Voras wrote: > Hi, > > At least one on-line tutorial about parallel port hacking > (http://www.excamera.com/articles/21/parallel.html) uses these header > files: > > #include > #include > > They are actually present in /sys, but not in the normal userland > include paths. Is this intentional, or was it removed sometimes in > the past? According to the ppi man page it's.. #include #include #include #include #include int main(int argc, char **argv) { int fd; if ((fd =3D open("/dev/ppi0", O_RDWR)) =3D=3D -1) { printf("Can't open /dev/ppi0\n"); exit(1); } exit(0); } Those includes are present on my 7.2 box (upgraded with the last week)=20 and my (oldish) -current box. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1386211.b6zfeR6ZaB Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKk11Y5ZPcIHs/zowRAqzWAJ9FJXUiBtx3oi6MT1alA06/caB8CgCeOab4 yNmVHb5n5Svm9lWcIHMbZLY= =4e/m -----END PGP SIGNATURE----- --nextPart1386211.b6zfeR6ZaB-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 11:09:36 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F242B106568C for ; Tue, 25 Aug 2009 11:09:36 +0000 (UTC) (envelope-from prvs=1481e02895=brian@FreeBSD.org) Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id BE0D18FC19 for ; Tue, 25 Aug 2009 11:09:36 +0000 (UTC) Received: from pd2ml1so-ssvc.prod.shaw.ca ([10.0.141.139]) by pd2mo1so-svcs.prod.shaw.ca with ESMTP; 25 Aug 2009 04:41:12 -0600 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=1 a=MJPcHhXccCG8eBs0us8XwA==:17 a=MMwg4So0AAAA:8 a=6I5d2MoRAAAA:8 a=ZT4lUwVGkln9Y6YlvXUA:9 a=5KIN3r7MZbznHzk0cTgA:7 a=bi9cJamc7Ty9TRVrEJfptvO_Tn4A:4 a=WJ3hkfHDukgA:10 a=SV7veod9ZcQA:10 a=T588jcPp3brV9v73k90A:9 a=NEyOCEzHxeufVKYfehLGO14h8jcA:4 Received: from unknown (HELO store.lan.Awfulhak.org) ([70.79.162.198]) by pd2ml1so-dmz.prod.shaw.ca with ESMTP; 25 Aug 2009 04:41:09 -0600 Received: from store.lan.Awfulhak.org (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 70F91C43518_A93BFC3B; Tue, 25 Aug 2009 10:41:07 +0000 (GMT) Received: from gw.Awfulhak.org (gw.lan.Awfulhak.org [172.16.0.1]) by store.lan.Awfulhak.org (Sophos Email Appliance) with ESMTP id 24EE5C460F3_A93BFC1F; Tue, 25 Aug 2009 10:41:05 +0000 (GMT) Received: from dev.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by gw.Awfulhak.org (8.14.3/8.14.3) with ESMTP id n7PAf4cd090785; Tue, 25 Aug 2009 03:41:04 -0700 (PDT) (envelope-from brian@FreeBSD.org) Date: Tue, 25 Aug 2009 03:40:54 -0700 From: Brian Somers To: freebsd-hackers@FreeBSD.org Message-ID: <20090825034054.2d57e733@dev.lan.Awfulhak.org> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.5; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/5Xee_40azWQyT3XMHoTDzh_"; protocol="application/pgp-signature" Cc: Ivan Radovanovic Subject: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 11:09:37 -0000 --Sig_/5Xee_40azWQyT3XMHoTDzh_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I recently closed bin/137647 and had second thoughts after Ivan (the originator) challenged my reason for closing it. The suggestion is that ps's -w switch is a strange artifact that can be safely deprecated. ps goes to great lengths to implement width limitations, and any time I've seen people not using -ww has either been a mistake or doesn't matter. Using 'cut -c1-N' is also a great way of limiting widths if people really want that... I'd like to propose changing ps so that width limits are removed and '-w' is deprecated - ignored for now with a note in the man page saying that it will be removed in a future release. Does anyone have any objections to doing this? I don't propose merging this back into stable/8. --=20 Brian Somers Don't _EVER_ lose your sense of humour ! --Sig_/5Xee_40azWQyT3XMHoTDzh_ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iQCVAwUBSpO/wA7tvOdmanQhAQKOgQP/f4zpizwkdzq08feUhZnZYBsgDg6F1FQ2 0aX1MqG5tMo1P6xNbagZfZJi79/nx7IiAr6Q0YisCtzF+DpK91Pmi1gciTSSPSdz RWr/qYwhAATj5q4r9SrqokV8EuNxkpnMAaJvQ2Twq1gXwpQ3OpVWb5PrW8H2UQaD KB/fZbyC1xA= =vJHH -----END PGP SIGNATURE----- --Sig_/5Xee_40azWQyT3XMHoTDzh_-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 11:23:49 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA7A7106568D for ; Tue, 25 Aug 2009 11:23:49 +0000 (UTC) (envelope-from marc@msys.ch) Received: from sleipnir.msys.ch (unknown [IPv6:2001:4060:c0de:f000::3]) by mx1.freebsd.org (Postfix) with ESMTP id 6B4108FC0C for ; Tue, 25 Aug 2009 11:23:49 +0000 (UTC) Received: from mail.msys.ch (smtp.msys.ch [157.161.101.10]) by sleipnir.msys.ch (8.14.3/8.14.1) with ESMTP id n7PBNgJe025869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 25 Aug 2009 13:23:42 +0200 (CEST) Received: from dhcp-168.msys.ch (dhcp-168.msys.ch [157.161.101.168]) (authenticated bits=0) by mail.msys.ch (8.14.3/8.14.1) with ESMTP id n7PBNgGf007506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Tue, 25 Aug 2009 13:23:42 +0200 (CEST) Message-Id: <131A8E29-4A35-4CA7-9297-5360B5A8DB19@msys.ch> From: Marc Balmer To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 25 Aug 2009 13:23:41 +0200 X-Mailer: Apple Mail (2.936) X-SMTP-Vilter-Version: 1.3.6 X-Spamd-Symbols: AWL Subject: tree doesnt compile X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 11:23:49 -0000 /usr/src/sys/modules/vesa/../../i386/isa/vesa.c: In function 'vesa_set_mode': /usr/src/sys/modules/vesa/../../i386/isa/vesa.c:1117: error: duplicate case value anyone seeing this as well or is this a local f***up ? From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 12:18:33 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F4AC106568C for ; Tue, 25 Aug 2009 12:18:33 +0000 (UTC) (envelope-from marc@msys.ch) Received: from sleipnir.msys.ch (unknown [IPv6:2001:4060:c0de:f000::3]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9958FC22 for ; Tue, 25 Aug 2009 12:18:33 +0000 (UTC) Received: from mail.msys.ch (smtp.msys.ch [157.161.101.10]) by sleipnir.msys.ch (8.14.3/8.14.1) with ESMTP id n7PCIQ6R015185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Aug 2009 14:18:26 +0200 (CEST) Received: from dhcp-168.msys.ch (dhcp-168.msys.ch [157.161.101.168]) (authenticated bits=0) by mail.msys.ch (8.14.3/8.14.1) with ESMTP id n7PCIQlX003446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 25 Aug 2009 14:18:26 +0200 (CEST) Message-Id: <3BF61938-F1E7-43ED-BC9E-C1A180595E90@msys.ch> From: Marc Balmer To: Marc Balmer In-Reply-To: <131A8E29-4A35-4CA7-9297-5360B5A8DB19@msys.ch> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 25 Aug 2009 14:18:26 +0200 References: <131A8E29-4A35-4CA7-9297-5360B5A8DB19@msys.ch> X-Mailer: Apple Mail (2.936) X-SMTP-Vilter-Version: 1.3.6 X-Spamd-Symbols: AWL Cc: freebsd-hackers@freebsd.org Subject: Re: tree doesnt compile X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 12:18:33 -0000 Am 25.08.2009 um 13:23 schrieb Marc Balmer: > /usr/src/sys/modules/vesa/../../i386/isa/vesa.c: In function > 'vesa_set_mode': > /usr/src/sys/modules/vesa/../../i386/isa/vesa.c:1117: error: > duplicate case value > > anyone seeing this as well or is this a local f***up ? fwiw, problem is still there after 'make clean && make kernel' From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 12:42:21 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31FA01065693 for ; Tue, 25 Aug 2009 12:42:21 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id A5F098FC28 for ; Tue, 25 Aug 2009 12:42:20 +0000 (UTC) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 04814199A4B; Tue, 25 Aug 2009 14:42:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id EC10A199A49; Tue, 25 Aug 2009 14:42:15 +0200 (CEST) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id D7B83199A32; Tue, 25 Aug 2009 14:42:15 +0200 (CEST) Received: from wep4035 ([132.187.37.35]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.2FP1HF244) with ESMTP id 2009082514421500-2230 ; Tue, 25 Aug 2009 14:42:15 +0200 Received: by wep4035 (sSMTP sendmail emulation); Tue, 25 Aug 2009 14:42:15 +0200 Date: Tue, 25 Aug 2009 14:42:15 +0200 From: Alexey Shuvaev To: Brian Somers Message-ID: <20090825124215.GA80035@wep4035.physik.uni-wuerzburg.de> Mail-Followup-To: Brian Somers , freebsd-hackers@FreeBSD.org, Ivan Radovanovic References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> Mime-Version: 1.0 In-Reply-To: <20090825034054.2d57e733@dev.lan.Awfulhak.org> User-Agent: Mutt/1.4.2.3i Organization: Universitaet Wuerzburg X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 08/25/2009 02:42:15 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 08/25/2009 02:42:15 PM, Serialize complete at 08/25/2009 02:42:15 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 12:42:21 -0000 On Tue, Aug 25, 2009 at 03:40:54AM -0700, Brian Somers wrote: > I recently closed bin/137647 and had second thoughts after Ivan (the > originator) challenged my reason for closing it. > > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... > > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. > Do you want to remove '-w' switch preserving '-ww' one? IMO this seems awkward. Also, by ignoring it for now do you mean that behavior of ps with '-w' switch would be the same as without it? I would prefer that '-w' == '-ww'. One can remove all references to multiple 'w' switches from the man page but leave ps itself insensitive to any number of 'w' switches (so '-w' == '-ww' == '-www' == ...). This also would be consistent with (for example) http://www.freebsd.org/cgi/man.cgi?query=ps&apropos=0&sektion=0&manpath=Red+Hat+Linux%2Fi386+9&format=html > Does anyone have any objections to doing this? I don't propose > merging this back into stable/8. > 0.02$, Alexey. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 13:44:48 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32ECA106568B; Tue, 25 Aug 2009 13:44:48 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id EC14D8FC26; Tue, 25 Aug 2009 13:44:47 +0000 (UTC) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 5C1BC1CD58; Tue, 25 Aug 2009 15:44:47 +0200 (CEST) Date: Tue, 25 Aug 2009 15:44:47 +0200 From: Ed Schouten To: Brian Somers Message-ID: <20090825134447.GM2829@hoeg.nl> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hdhkc9EpVJoq6PQ6" Content-Disposition: inline In-Reply-To: <20090825034054.2d57e733@dev.lan.Awfulhak.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 13:44:48 -0000 --hdhkc9EpVJoq6PQ6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Brian Somers wrote: > I recently closed bin/137647 and had second thoughts after Ivan (the > originator) challenged my reason for closing it. >=20 > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... >=20 > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. >=20 > Does anyone have any objections to doing this? I don't propose > merging this back into stable/8. So ps(1) output can never be limited to the screen width? --=20 Ed Schouten WWW: http://80386.nl/ --hdhkc9EpVJoq6PQ6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqT6s8ACgkQ52SDGA2eCwXfvwCdHEjIDmvn72ntNblALRmQ2nqc hBwAnizukr+XSXeZQgqYTekUXQEnVBxa =N1TT -----END PGP SIGNATURE----- --hdhkc9EpVJoq6PQ6-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 14:09:12 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18D3F106568C for ; Tue, 25 Aug 2009 14:09:12 +0000 (UTC) (envelope-from j.mckeown@ru.ac.za) Received: from f.mail.ru.ac.za (f.mail.ru.ac.za [IPv6:2001:4200:1010::25:6]) by mx1.freebsd.org (Postfix) with ESMTP id 4B53E8FC24 for ; Tue, 25 Aug 2009 14:09:11 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ru-msa; d=ru.ac.za; h=Received:From:Organization:To:Subject:Date:User-Agent:References:In-Reply-To:X-Face:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-Virus-Scanned:X-Authenticated-User; b=DrSzfdq61JOGofqVLOjMO/RuSa+xnyjfPsyalGMRQS52+yXlD8sAZEoRhJdVJ1cEJc0HHf+rRvihNQmEiw8pul+Xxp+PfkUQhxNKumFBBAmrHs+sbkSYo0Z2yKLXkGjb; Received: from vorkosigan.ru.ac.za ([2001:4200:1010:1058:219:d1ff:fe9f:a932]:53851) by f.mail.ru.ac.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mfwhx-000DgS-FJ for freebsd-hackers@freebsd.org; Tue, 25 Aug 2009 16:09:09 +0200 From: Jonathan McKeown Organization: Rhodes University To: freebsd-hackers@freebsd.org Date: Tue, 25 Aug 2009 16:09:09 +0200 User-Agent: KMail/1.9.10 References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> In-Reply-To: <20090825134447.GM2829@hoeg.nl> X-Face: $@VrUx^RHy/}yu]jKf/<4T%/d|F+$j-Ol2"2J$q+%OK1]&/G_S9(=?utf-8?q?HkaQ*=60!=3FYOK=3FY!=27M=60C=0A=09aP=5C9nVPF8Q=7DCilHH8l=3B=7E!4?= =?utf-8?q?2HK6=273lg4J=7Daz?=@1Dqqh:J]M^"YPn*2IWrZON$1+G?oX3@ =?utf-8?q?k=230=0A=0954XDRg=3DYn=5FF-etwot4U=24b?=dTS{i X-Virus-Scanned: f.mail.ru.ac.za (2001:4200:1010::25:6) X-Authenticated-User: s0900137 from vorkosigan.ru.ac.za (2001:4200:1010:1058:219:d1ff:fe9f:a932) using auth_plaintext Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 14:09:12 -0000 On Tuesday 25 August 2009 15:44:47 Ed Schouten wrote: > * Brian Somers wrote: > > I recently closed bin/137647 and had second thoughts after Ivan (the > > originator) challenged my reason for closing it. > > > > The suggestion is that ps's -w switch is a strange artifact that can > > be safely deprecated. ps goes to great lengths to implement width > > limitations, and any time I've seen people not using -ww has either > > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > > way of limiting widths if people really want that... > > > > I'd like to propose changing ps so that width limits are removed and > > '-w' is deprecated - ignored for now with a note in the man page > > saying that it will be removed in a future release. > > > > Does anyone have any objections to doing this? I don't propose > > merging this back into stable/8. > > So ps(1) output can never be limited to the screen width? I usually want to see ps(1) output in easily-read columns. Without width limits, this can't be guaranteed. I would strongly object to the complete removal of any option to limit the output width of ps(1) and make it easily human-readable. I'm also astonished at the suggestion that not using -ww is ``a mistake''. I very seldom need to see the whole commandline for every process. Jonathan From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 14:10:44 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 423201065692 for ; Tue, 25 Aug 2009 14:10:44 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 08AF38FC0C for ; Tue, 25 Aug 2009 14:10:44 +0000 (UTC) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 1FB011CD9F; Tue, 25 Aug 2009 16:10:43 +0200 (CEST) Date: Tue, 25 Aug 2009 16:10:42 +0200 From: Ed Schouten To: Marc Balmer Message-ID: <20090825141042.GN2829@hoeg.nl> References: <131A8E29-4A35-4CA7-9297-5360B5A8DB19@msys.ch> <3BF61938-F1E7-43ED-BC9E-C1A180595E90@msys.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="57SHPaztv6dlLu/a" Content-Disposition: inline In-Reply-To: <3BF61938-F1E7-43ED-BC9E-C1A180595E90@msys.ch> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-hackers@freebsd.org Subject: Re: tree doesnt compile X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 14:10:44 -0000 --57SHPaztv6dlLu/a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Marc Balmer wrote: >=20 > Am 25.08.2009 um 13:23 schrieb Marc Balmer: >=20 > >/usr/src/sys/modules/vesa/../../i386/isa/vesa.c: In function > >'vesa_set_mode': > >/usr/src/sys/modules/vesa/../../i386/isa/vesa.c:1117: error: > >duplicate case value > > > >anyone seeing this as well or is this a local f***up ? >=20 > fwiw, problem is still there after 'make clean && make kernel' svn up ;-) --=20 Ed Schouten WWW: http://80386.nl/ --57SHPaztv6dlLu/a Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqT8OIACgkQ52SDGA2eCwUDJQCdHITlvB27RAJ//ShqSUfF9XNY kcUAn0pVPHb6yBIP8EoBXOQibe+4vdGY =nGbh -----END PGP SIGNATURE----- --57SHPaztv6dlLu/a-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 14:24:31 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AADEE106568C for ; Tue, 25 Aug 2009 14:24:31 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 398438FC28 for ; Tue, 25 Aug 2009 14:24:30 +0000 (UTC) Received: by fxm6 with SMTP id 6so2015833fxm.43 for ; Tue, 25 Aug 2009 07:24:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=QjuZtsv/+rVW2CxgD2AiDlkcIfrymz1H/wIldy5THlA=; b=mPXYf1BwCxQ5bzf+mFh3Yj33dvALWkheTvDOOyDGgzwF4HAzoUtirRsKKYtF8peeDV tL+5m9eAuBuUkQC4+YJpqVc4cPezYmVzuovIjXWOIaXSxwHeDvzarVquLrEyGa18QgjG WncBPHTSGfa2wCgFiEkrJBjTt/9IIk9ejZAWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=pwLjbna1cHFcEPt7ZlejY2GIL6iRLbI7zlYF3mPswhKK97Zsw+yHhNuM+BxZ7DiJah v8NmFh9SjIHPLr0kqxZwnrtHaRttrUaBzQUoxcZ0XVliEOLMjXe2CMVXyBrWJsA9DQAW p2LOm8cqmXhYAcZJ6WhAw1MKxGzRds8jP6r/w= Received: by 10.103.37.38 with SMTP id p38mr2599129muj.134.1251208798080; Tue, 25 Aug 2009 06:59:58 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id t10sm104956muh.30.2009.08.25.06.59.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 Aug 2009 06:59:57 -0700 (PDT) Message-ID: <4A93EE5B.8000300@gmail.com> Date: Tue, 25 Aug 2009 15:59:55 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: Ed Schouten References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> In-Reply-To: <20090825134447.GM2829@hoeg.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 14:24:31 -0000 Ed Schouten napisa: > * Brian Somers wrote: > >> I recently closed bin/137647 and had second thoughts after Ivan (the >> originator) challenged my reason for closing it. >> >> The suggestion is that ps's -w switch is a strange artifact that can >> be safely deprecated. ps goes to great lengths to implement width >> limitations, and any time I've seen people not using -ww has either >> been a mistake or doesn't matter. Using 'cut -c1-N' is also a great >> way of limiting widths if people really want that... >> >> I'd like to propose changing ps so that width limits are removed and >> '-w' is deprecated - ignored for now with a note in the man page >> saying that it will be removed in a future release. >> >> Does anyone have any objections to doing this? I don't propose >> merging this back into stable/8. >> > > So ps(1) output can never be limited to the screen width? > I think it would be smart not to limit width by default (ie default behavior to be like with -ww), but to have some switch (like -w) to limit width if someone really needs to do that, although with "cut -c 1-80" could be achieved limiting... From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 14:43:46 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44E07106568F; Tue, 25 Aug 2009 14:43:46 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6DA8FC20; Tue, 25 Aug 2009 14:43:46 +0000 (UTC) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 01F721CDC3; Tue, 25 Aug 2009 16:43:44 +0200 (CEST) Date: Tue, 25 Aug 2009 16:43:44 +0200 From: Ed Schouten To: Adrian Penisoara Message-ID: <20090825144344.GO2829@hoeg.nl> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <4A93EE5B.8000300@gmail.com> <78cb3d3f0908250736g2ef52068pb84896eac5a2c45d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BuBclajtnfx5hylj" Content-Disposition: inline In-Reply-To: <78cb3d3f0908250736g2ef52068pb84896eac5a2c45d@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-hackers@freebsd.org, Brian Somers , Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 14:43:46 -0000 --BuBclajtnfx5hylj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Adrian Penisoara wrote: > Maybe we should also think about compatibility with System V Unix / Linux > -- I have encountered quite a lot of scripts expecting "ps -ef" to give an > "all processes" output. It would not hurt to review what the Linux folks = did > with their ps(1) -- it supports 3 kinds of options for UNIX/BSD/GNU flavo= rs. In my opinion we should just implement ps(1) as documented in the POSIX Onlinepubs. If it turns out it lacks certain features we want, we could consider adding this to procstat(1) instead. I am of course too lazy to work on this. ;-) --=20 Ed Schouten WWW: http://80386.nl/ --BuBclajtnfx5hylj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqT+KAACgkQ52SDGA2eCwWzGACePbRe6ZEmjWncFUc4XYWfZTow BOwAnijcbMM7rF/w/fS/689RFYf82SPJ =671z -----END PGP SIGNATURE----- --BuBclajtnfx5hylj-- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 15:03:32 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3BE71065693; Tue, 25 Aug 2009 15:03:32 +0000 (UTC) (envelope-from ady@ady.ro) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id 13BE58FC29; Tue, 25 Aug 2009 15:03:31 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so699380eyf.9 for ; Tue, 25 Aug 2009 08:03:31 -0700 (PDT) MIME-Version: 1.0 Sender: ady@ady.ro Received: by 10.210.27.20 with SMTP id a20mr2455073eba.28.1251211014149; Tue, 25 Aug 2009 07:36:54 -0700 (PDT) In-Reply-To: <4A93EE5B.8000300@gmail.com> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <4A93EE5B.8000300@gmail.com> Date: Tue, 25 Aug 2009 16:36:54 +0200 X-Google-Sender-Auth: daa6e7c2e131e48a Message-ID: <78cb3d3f0908250736g2ef52068pb84896eac5a2c45d@mail.gmail.com> From: Adrian Penisoara To: Ivan Radovanovic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Ed Schouten , Brian Somers , freebsd-hackers@freebsd.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 15:03:32 -0000 Hi, On Tue, Aug 25, 2009 at 3:59 PM, Ivan Radovanovic wrote: > Ed Schouten napisa: > > * Brian Somers wrote: >> >> >>> I recently closed bin/137647 and had second thoughts after Ivan (the >>> originator) challenged my reason for closing it. >>> >>> The suggestion is that ps's -w switch is a strange artifact that can >>> be safely deprecated. ps goes to great lengths to implement width >>> limitations, and any time I've seen people not using -ww has either >>> been a mistake or doesn't matter. Using 'cut -c1-N' is also a great >>> way of limiting widths if people really want that... >>> >>> I'd like to propose changing ps so that width limits are removed and >>> '-w' is deprecated - ignored for now with a note in the man page >>> saying that it will be removed in a future release. >>> >>> Does anyone have any objections to doing this? I don't propose >>> merging this back into stable/8. >>> >>> >> >> So ps(1) output can never be limited to the screen width? >> >> > I think it would be smart not to limit width by default (ie default > behavior to be like with -ww), but to have some switch (like -w) to limit > width if someone really needs to do that, although with "cut -c 1-80" could > be achieved limiting... Let's not reverse the meaning of switches, for the sake of compatibility with (older) existent scripts... Maybe we should also think about compatibility with System V Unix / Linux -- I have encountered quite a lot of scripts expecting "ps -ef" to give an "all processes" output. It would not hurt to review what the Linux folks did with their ps(1) -- it supports 3 kinds of options for UNIX/BSD/GNU flavors. Regards, Adrian Penisoara EnterpriseBSD From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 16:11:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 507BB1065690 for ; Tue, 25 Aug 2009 16:11:15 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 25FC48FC15 for ; Tue, 25 Aug 2009 16:11:15 +0000 (UTC) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n7PFmZOD096920 for freebsd-hackers@freebsd.org; Tue, 25 Aug 2009 08:48:35 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id a8vznym8w54skedf4c8r7bfxvw; for freebsd-hackers@freebsd.org; Tue, 25 Aug 2009 08:48:35 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4A9407D3.60006@freebsd.org> Date: Tue, 25 Aug 2009 08:48:35 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <200908251609.09302.j.mckeown@ru.ac.za> In-Reply-To: <200908251609.09302.j.mckeown@ru.ac.za> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 16:11:15 -0000 Jonathan McKeown wrote: > On Tuesday 25 August 2009 15:44:47 Ed Schouten wrote: >> * Brian Somers wrote: >>> I recently closed bin/137647 and had second thoughts after Ivan (the >>> originator) challenged my reason for closing it. >>> >>> The suggestion is that ps's -w switch is a strange artifact that can >>> be safely deprecated. ps goes to great lengths to implement width >>> limitations, and any time I've seen people not using -ww has either >>> been a mistake or doesn't matter. The difference between "ps", "ps -w", and "ps -ww" is pretty significant for Java, in particular. Java command lines are typically enormous (thank you, CLASSPATH) which makes "ps -ww" often more annoying than it's worth. I concur with another poster that the GNU ps approach for supporting multiple argument styles deserves consideration. Tim From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 16:23:18 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95FC5106568E; Tue, 25 Aug 2009 16:23:18 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id 43C9B8FC14; Tue, 25 Aug 2009 16:23:18 +0000 (UTC) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:80f4:0:2e0:81ff:fe33:7e9a]) by tinker.exit.com (8.14.3/8.14.3) with ESMTP id n7PGNHm2059508; Tue, 25 Aug 2009 09:23:17 -0700 (PDT) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1251217397; bh=bCv/y55y7ac1RMo0NOe5F9MrLXrOi3BLNpdVeK/dhuQ=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type: Content-Transfer-Encoding:Date:Message-Id:Mime-Version; b=mipnlJxI 0rhDylBcaZCPB0KmjtPeSyZXp2YFoRhgLHJ9IF/+6IafQLcwI4PaENb8JHuR0VLopCZ rg6UdoraawS29ooXNsjhP38XhOQmbkKN7u1JdJtgC/rybHGzGNa8lxOCcKf+UjmNz4q Oy0mSvq0o+HuUO3l1uErVdDZfWEE8= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.3/8.14.2) with ESMTP id n7PGNHHt083340; Tue, 25 Aug 2009 09:23:17 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.3/8.14.3/Submit) id n7PGNHWE083339; Tue, 25 Aug 2009 09:23:17 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: Tim Kientzle In-Reply-To: <4A9407D3.60006@freebsd.org> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <200908251609.09302.j.mckeown@ru.ac.za> <4A9407D3.60006@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Tue, 25 Aug 2009 09:23:15 -0700 Message-Id: <1251217395.83189.1.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.93.3/9739/Tue Aug 25 06:38:07 2009 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 16:23:18 -0000 On Tue, 2009-08-25 at 08:48 -0700, Tim Kientzle wrote: > Jonathan McKeown wrote: > > On Tuesday 25 August 2009 15:44:47 Ed Schouten wrote: > >> * Brian Somers wrote: > >>> I recently closed bin/137647 and had second thoughts after Ivan (the > >>> originator) challenged my reason for closing it. > >>> > >>> The suggestion is that ps's -w switch is a strange artifact that can > >>> be safely deprecated. ps goes to great lengths to implement width > >>> limitations, and any time I've seen people not using -ww has either > >>> been a mistake or doesn't matter. > > The difference between "ps", "ps -w", and "ps -ww" is pretty > significant for Java, in particular. Java command lines > are typically enormous (thank you, CLASSPATH) which makes > "ps -ww" often more annoying than it's worth. > > I concur with another poster that the GNU ps approach for > supporting multiple argument styles deserves consideration. I realized that nobody asked me, but IMHO it ain't broke so don't fix it. I use -w and -ww a lot, and yes, I do distinguish them. Sometimes -w is enough; if it isn't, then I'll use -ww but otherwise I avoid it because it gives just too much output in many cases. -- Frank Mayhar frank@exit.com http://www.exit.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 16:54:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31B4D106568B; Tue, 25 Aug 2009 16:54:42 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 08C348FC21; Tue, 25 Aug 2009 16:54:40 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA07103; Tue, 25 Aug 2009 19:35:57 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4A9412ED.6080309@freebsd.org> Date: Tue, 25 Aug 2009 19:35:57 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hackers@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 16:54:42 -0000 I have become to own Gigabyte GA-MA780G-UD3H motherboard: http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on AMD 780G + SB700. BTW, CPU I am using is Athlon II X2 250. Sorry for the broadcast announcement, but this is my first AMD-based system in many years, so I eagerly started exploring it and hacking for it. For this reason please expect a number of questions from me as well as some reports and hopefully code related to this motherboard. I am going to post them as follow-ups to this email. Meanwhile, if you interested in any information about this motherboard - data dumps, outputs from tools, etc - please let me know, I will try my best to provide that. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 17:34:12 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7411E106568E for ; Tue, 25 Aug 2009 17:34:12 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A38128FC21 for ; Tue, 25 Aug 2009 17:34:11 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA08277 for ; Tue, 25 Aug 2009 20:34:10 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4A942091.6000909@freebsd.org> Date: Tue, 25 Aug 2009 20:34:09 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4A9412ED.6080309@freebsd.org> In-Reply-To: <4A9412ED.6080309@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: AMD SB700 watchdog driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 17:34:12 -0000 Anybody has any code for AMD SB700 watchdog driver? I see that there is none in FreeBSD and I'd like to write one. So I could re-use anything that you have for a faster start. In any case, I expect the driver to be rather simple. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 17:49:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27D18106568B; Tue, 25 Aug 2009 17:49:34 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3B6DF8FC1A; Tue, 25 Aug 2009 17:49:32 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA08587; Tue, 25 Aug 2009 20:49:31 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4A94242B.7090806@freebsd.org> Date: Tue, 25 Aug 2009 20:49:31 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org, freebsd-hackers@freebsd.org References: <4A9412ED.6080309@freebsd.org> In-Reply-To: <4A9412ED.6080309@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: AMD SB700 SMBus controller driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 17:49:34 -0000 According to SB700 specifications its SMBus controller is very similar to one in PIIX4. The differences that I see so far: 1. Interrupt Line/Interrupt Pin PCI configuration registers (0x3c, 0x3d) do not specify interrupt number that the controller could use: > This register specifies which interrupt pin the device issue > This module does not generate interrupt but contains the > actual interrupt controller. This register is hardcoded to 0. 2. I2CbusConfig register (0xd2) uses bit #1 to indicate whether SMI or regular interrupt is used in interrupt mode; PIIX4 uses bit 3. I couldn't get our intpm driver to work with this hardware by simply adding PCI id and tweaking 0xd2 bits meaning. I could get it to work by forcing polling mode. It appears that Linux driver for this HW always uses polling mode, and OpenBSD and NetBSD drivers would use it with this HW too. I am still trying to get interrupt mode to work. I set 0xd2 to enable regular interrupt generation (it is set to SMI after boot). SB700 specifications say at one place that SMB interrupt is connected to INTIN20 pin of IO-APIC in APIC mode. I tried setting up IRQ20 in the driver but no interrupts are generated. And there are no stray interrupts either. So I am not sure - either this HW doesn't generate normal interrupts at all, or they to a different pin, or additional setup is required, or I am doing something wrong. Anyway, I plan to produce an updated version of intpm driver with possibility of forced or auto-detected polling mode and support for PCI id of SB700 SMBus controller and its peculiarities. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 18:00:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4169106568C; Tue, 25 Aug 2009 18:00:50 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D87288FC2B; Tue, 25 Aug 2009 18:00:49 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA08763; Tue, 25 Aug 2009 21:00:48 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4A9426CF.1030205@freebsd.org> Date: Tue, 25 Aug 2009 21:00:47 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org, freebsd-hackers@freebsd.org References: <4A9412ED.6080309@freebsd.org> In-Reply-To: <4A9412ED.6080309@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: GA-MA780G-UD3H hardware monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 18:00:50 -0000 Does anybody know if Gigabyte provides special ACPI interfaces for HWM on their motherboards? Maybe something like ASUS does (acpi_aiboost)? Or do they access HWM chip directly? They have this EasyTune software, so they must be doing something. DSDT of GA-MA780G-UD3H doesn't even provide TZ. This motherboard has iTE IT8718 Super I/O + HWM chip. Thanks to superiotool from coreboot project I determined that base address (port actually) for HWM logical device is at 0x228 (as opposed to more typical 0x290). Slightly modified version of mbmon is even able to recognize the chip and get some data. I am not sure if the data is entirely correct, but it looks sane/reasonable. Still I would like to not only monitor temperatures, voltages and fan speeds, but even to be able to control fan speed. Any links, pointers, ideas, code would be very appreciated! -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 18:06:57 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18BE91065690 for ; Tue, 25 Aug 2009 18:06:57 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outt.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 028E68FC32 for ; Tue, 25 Aug 2009 18:06:56 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 12F4B2442; Tue, 25 Aug 2009 10:53:55 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 781A92D601F; Tue, 25 Aug 2009 10:53:54 -0700 (PDT) Message-ID: <4A942531.6000702@elischer.org> Date: Tue, 25 Aug 2009 10:53:53 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Brian Somers , hackers@freebsd.org References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> In-Reply-To: <20090825034054.2d57e733@dev.lan.Awfulhak.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 18:06:57 -0000 Brian Somers wrote: > I recently closed bin/137647 and had second thoughts after Ivan (the > originator) challenged my reason for closing it. > > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... > > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. > > Does anyone have any objections to doing this? I don't propose > merging this back into stable/8. > my fingers would object as ps auxw is my standard command. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 18:50:16 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E263106568D for ; Tue, 25 Aug 2009 18:50:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 95D878FC14 for ; Tue, 25 Aug 2009 18:50:15 +0000 (UTC) Received: (qmail 11328 invoked by uid 399); 25 Aug 2009 18:50:11 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 25 Aug 2009 18:50:11 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A94325D.6070201@FreeBSD.org> Date: Tue, 25 Aug 2009 11:50:05 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Brian Somers References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> In-Reply-To: <20090825034054.2d57e733@dev.lan.Awfulhak.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 18:50:16 -0000 Brian Somers wrote: > I recently closed bin/137647 and had second thoughts after Ivan (the > originator) challenged my reason for closing it. > > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... > > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. > > Does anyone have any objections to doing this? I don't propose > merging this back into stable/8. Short version, yes, I object to changing the defaults. Longer version, I don't see anything wrong with the defaults the way that they are, and the fact that there is a teeny-tiny learning curve for people who need to see the full output isn't really an issue that deserves the time already spent on it. Bruce pointed out in the PR that most users would be surprised if 'ps -ax | grep foo' suddenly sprouted a lot more stuff that 'ps -ax' didn't have, and I agree. As a matter of personal preference I find the current defaults to be just lovely, and occasionally use -w or -ww if I need to see more. If you want the default to be something different, that's what aliases are for. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:00:38 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DCA0106568E; Tue, 25 Aug 2009 19:00:38 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-yw0-f202.google.com (mail-yw0-f202.google.com [209.85.211.202]) by mx1.freebsd.org (Postfix) with ESMTP id D035D8FC1D; Tue, 25 Aug 2009 19:00:37 +0000 (UTC) Received: by ywh40 with SMTP id 40so5099146ywh.14 for ; Tue, 25 Aug 2009 12:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ysJGjQkEFWG71DX0Qg1546yjxxIdGRBjLc5reyWdTrk=; b=obtPZy+hMFSaxgwzu+ImzkRWe2Ww56upihFW4eotGAJXQ8tJPc0LsL6a7qGBcupzFi AX3l6LyvhbKT3t8jAI8ErPy3zz2Qr+G5g8cfyKyN3iMmzyva+tAo66eeHvVVPa0DqJDp RNdRs1GAkC+6TaTaPHbQCpLN4+GfZTdp6HNuo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=HQpWsL1La2OsbPLxcDN04cQhZ6VI7grUP5FqxCFU0ZltOG3gN3qfnIoWAnNYnHgsrb CXMcfhTDS3da5v8QZOGT6Hci1t3x2C2Mb1Lq4XcBMU1O5VhAYiXrbcldIzv8mWsjaolo m2UsATbSJFG9Rxpt/YNsbIJsUqHBLW/EpHJHk= MIME-Version: 1.0 Received: by 10.150.129.27 with SMTP id b27mr11225837ybd.29.1251225280343; Tue, 25 Aug 2009 11:34:40 -0700 (PDT) In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Date: Tue, 25 Aug 2009 13:34:40 -0500 Message-ID: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> From: "Sam Fourman Jr." To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:00:38 -0000 > Meanwhile, if you interested in any information about this motherboard - data > dumps, outputs from tools, etc - please let me know, I will try my best to provide > that. it would be interesting to see a dmesg as a starting point. Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:08:27 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C440106564A; Tue, 25 Aug 2009 19:08:27 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 930968FC15; Tue, 25 Aug 2009 19:08:25 +0000 (UTC) Received: by fxm6 with SMTP id 6so2265752fxm.43 for ; Tue, 25 Aug 2009 12:08:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=VcZXN0YC5QFgI/pPtILH48P7NxkSp29jQLBMqkkkCEY=; b=SfDxUW6CA6YNIx36zkBzEPj/sR+BoQ4egGpGWU1DnSiau++sXz+QNgWpGXJfbO4cDe uOBJdZJbf4E41yGfdancDkJOv0T48LPQ33j6LcKAxFLXTgQxIY/kpNIUgEeieFN7W3yX S/vxsVW7VtFMmPvJHGpWWa6ZNN+g0YURqApT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=s2ZABwe1MI2ZB2fffwWT89UuZfR/bKuBhyhK9pxN80ggea4Vd0/ER5ULbp3a900n06 4+DR+SAi20rOKRCiqHmo8LTZpbT2Hqs1dWUu9kNcvo+BlFPZhkHb9MZhIIkWJMLrsyra I7gAJA6qBcDqRtsvv4vNgGBkqj3M0ZR4b73gs= Received: by 10.103.48.17 with SMTP id a17mr2894559muk.82.1251227305277; Tue, 25 Aug 2009 12:08:25 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id u9sm1353967muf.7.2009.08.25.12.08.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 Aug 2009 12:08:24 -0700 (PDT) Message-ID: <4A9436A7.2020108@gmail.com> Date: Tue, 25 Aug 2009 21:08:23 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: Doug Barton References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> In-Reply-To: <4A94325D.6070201@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:08:27 -0000 Doug Barton napisa: > Brian Somers wrote: > >> I recently closed bin/137647 and had second thoughts after Ivan (the >> originator) challenged my reason for closing it. >> >> The suggestion is that ps's -w switch is a strange artifact that can >> be safely deprecated. ps goes to great lengths to implement width >> limitations, and any time I've seen people not using -ww has either >> been a mistake or doesn't matter. Using 'cut -c1-N' is also a great >> way of limiting widths if people really want that... >> >> I'd like to propose changing ps so that width limits are removed and >> '-w' is deprecated - ignored for now with a note in the man page >> saying that it will be removed in a future release. >> >> Does anyone have any objections to doing this? I don't propose >> merging this back into stable/8. >> > > Short version, yes, I object to changing the defaults. > > Longer version, I don't see anything wrong with the defaults the way > that they are, and the fact that there is a teeny-tiny learning curve > for people who need to see the full output isn't really an issue that > deserves the time already spent on it. Bruce pointed out in the PR > that most users would be surprised if 'ps -ax | grep foo' suddenly > sprouted a lot more stuff that 'ps -ax' didn't have, and I agree. As a > matter of personal preference I find the current defaults to be just > lovely, and occasionally use -w or -ww if I need to see more. If you > want the default to be something different, that's what aliases are for. > > > Doug > So, if the developer is presented with a task of developing utility to list running processes on the machine the right way to solve this problem is to implement it exactly the way the ps is implemented (ie, to please some aesthetic criteria (ie to format output to some width) rather than to focus on functionality)? I think software should evolve to be better rather then to stick with something done the wrong way, even that has been done maybe 30 years ago - that is why behavior should be changed. It is never too late to do the right thing ;-) Best regards, Ivan From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:15:47 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 426F1106568D for ; Tue, 25 Aug 2009 19:15:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id CA0778FC28 for ; Tue, 25 Aug 2009 19:15:46 +0000 (UTC) Received: (qmail 30009 invoked by uid 399); 25 Aug 2009 19:15:44 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 25 Aug 2009 19:15:44 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A94385A.1000405@FreeBSD.org> Date: Tue, 25 Aug 2009 12:15:38 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Ivan Radovanovic References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> In-Reply-To: <4A9436A7.2020108@gmail.com> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:15:47 -0000 Ivan Radovanovic wrote: > So, if the developer is presented with a task of developing utility to > list running processes on the machine the right way to solve this > problem is to implement it exactly the way the ps is implemented (ie, to > please some aesthetic criteria (ie to format output to some width) > rather than to focus on functionality)? If you're developing your own app to display running processes implement it any way you wish. That's totally unrelated to the question at hand. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:31:40 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 209C5106568C; Tue, 25 Aug 2009 19:31:40 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 45A1F8FC20; Tue, 25 Aug 2009 19:31:38 +0000 (UTC) Received: by bwz2 with SMTP id 2so2004079bwz.43 for ; Tue, 25 Aug 2009 12:31:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=uNhwHaPusyurmIKC15ADUHe1TW59vcsSuGgMk8uzk1Q=; b=XlnrJj1fWpm906ewXrFQOnxNdvKVgMpshCe1xSq+zw8gvzjFiDKa4nlnsWIJ5Xul/H IGiS1lK2l0Rp9+ksZPv048wtdQwqzUeTqm24rf3Nox+Y2P/397x+9rGhjh2Hvdoh0L/O lyzh7uRNIL6W/vZmdxZw+MdVK37WlXHlhupdE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=dVBkC7inYImwC/OJh/MNbEpHmwB2qRRRJz83tV3X9u+CY6alvaPx9bIP3Eb664NIbl vi04NMMH6csrnrgry0IhAdGKKg228uvi1qQtnJbUd/Us8vreYBJa98+rrs3m4pixS/mG C+0rJkNl64oDZzQbVCrRn3wEcI6BdH3l57TkM= Received: by 10.102.178.11 with SMTP id a11mr2858959muf.129.1251228698066; Tue, 25 Aug 2009 12:31:38 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id u9sm1495217muf.7.2009.08.25.12.31.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 Aug 2009 12:31:37 -0700 (PDT) Message-ID: <4A943C18.2050103@gmail.com> Date: Tue, 25 Aug 2009 21:31:36 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: Doug Barton References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> In-Reply-To: <4A94385A.1000405@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:31:40 -0000 Doug Barton napisa: > If you're developing your own app to display running processes > implement it any way you wish. That's totally unrelated to the > question at hand. > > Doug > I totally disagree with you - being against change means that you believe it is done the best way it could be done. Although there is another way to solve this "problem" - manual can be changed to state in the first row "process status formated for terminal output" instead of "process status" which is now title for ps. That way it would be obvious at the first look that ps is tightly coupled with terminal it is running on and nobody would need to learn this harder way. Regards, Ivan From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:35:47 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47F0F106568E for ; Tue, 25 Aug 2009 19:35:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id D7FC38FC19 for ; Tue, 25 Aug 2009 19:35:46 +0000 (UTC) Received: (qmail 3153 invoked by uid 399); 25 Aug 2009 19:35:40 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 25 Aug 2009 19:35:40 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A943D06.405@FreeBSD.org> Date: Tue, 25 Aug 2009 12:35:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Ivan Radovanovic References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> <4A943C18.2050103@gmail.com> In-Reply-To: <4A943C18.2050103@gmail.com> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:35:47 -0000 Ivan Radovanovic wrote: > Doug Barton napisa: >> If you're developing your own app to display running processes >> implement it any way you wish. That's totally unrelated to the >> question at hand. >> >> Doug >> > I totally disagree with you - being against change means that you > believe it is done the best way it could be done. This argument is so non-sequitur that I'm tempted not to respond, but no, that's not what I'm saying at all. What I'm saying is that there are valid reasons to leave the defaults as they are, AND if you don't like the defaults there are easy ways to manipulate that in your own environment. > Although there is another way to solve this "problem" - manual can be > changed to state in the first row "process status formated for terminal > output" instead of "process status" which is now title for ps. That way > it would be obvious at the first look that ps is tightly coupled with > terminal it is running on and nobody would need to learn this harder way. Feel free to take a crack at this and send the results to the list for review. Improving the documentation is always a worthy goal. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:03:01 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CFCB1065693; Tue, 25 Aug 2009 20:03:01 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 6342B8FC28; Tue, 25 Aug 2009 20:03:00 +0000 (UTC) Received: by bwz2 with SMTP id 2so2021757bwz.43 for ; Tue, 25 Aug 2009 13:02:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Klu4S2qyV1rJpMUmZVqLOmAtDi4BSxQy75ATa0VoKpI=; b=Ay7Qz4Tt0hLkyINzzokJeBczmebQF6OiGykNi+rcQ1AeYu19rdeuw3vfXtwWmBfOT+ J/0f/Pmb0/Hk2m7Jc4MFfykDzkZQQzqTvcbMjET+x7KqTmCWP6nXbK56SHa2k8/lOeZe 94dqc8LiDFzLkYquG4R9qw3rf1GjVX40no+fE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=uZ8Q1JXxc6vOdLLyBbCbqmCIgKyC01zzFTZePx6V3tMleFpbAApKOc6lzREpIAz8TL KUqD6pkxqoT+lx15KjI9Y2eljfXMGCN1ySWoms7188HgE8GihRkQqIzbgQXLt6WL4egs xp0YaIhHz80pa62cispYC9ra5S77sOqFo+dlQ= Received: by 10.103.78.35 with SMTP id f35mr2926385mul.89.1251230579193; Tue, 25 Aug 2009 13:02:59 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id n10sm1210924mue.19.2009.08.25.13.02.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 Aug 2009 13:02:58 -0700 (PDT) Message-ID: <4A944370.2000306@gmail.com> Date: Tue, 25 Aug 2009 22:02:56 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: Doug Barton References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> <4A943C18.2050103@gmail.com> <4A943D06.405@FreeBSD.org> In-Reply-To: <4A943D06.405@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:03:01 -0000 Doug Barton napisa: > Ivan Radovanovic wrote: > >> I totally disagree with you - being against change means that you >> believe it is done the best way it could be done. >> > This argument is so non-sequitur that I'm tempted not to respond, but > no, that's not what I'm saying at all. What I'm saying is that there > are valid reasons to leave the defaults as they are, AND if you don't > like the defaults there are easy ways to manipulate that in your own > environment. > You wrote : Longer version, I don't see anything wrong with the defaults the way that they are, and the fact that there is a teeny-tiny learning curve for people who need to see the full output isn't really an issue that deserves the time already spent on it. Bruce pointed out in the PR that most users would be surprised if 'ps -ax | grep foo' suddenly sprouted a lot more stuff that 'ps -ax' didn't have, and I agree. As a matter of personal preference I find the current defaults to be just lovely, and occasionally use -w or -ww if I need to see more. If you want the default to be something different, that's what aliases are for. So, valid arguments against change should be: 1. users will be surprised if ps starts displaying more stuff no matter if that stuff is correct and less stuff (current state) is incorrect 2. your personal preference is that current defaults are lovely Sorry, I don't find these arguments valid >> Although there is another way to solve this "problem" - manual can be >> changed to state in the first row "process status formated for terminal >> output" instead of "process status" which is now title for ps. That way >> it would be obvious at the first look that ps is tightly coupled with >> terminal it is running on and nobody would need to learn this harder way. >> > Feel free to take a crack at this and send the results to the list for > review. Improving the documentation is always a worthy goal. > I would do that for sure if everyone thinks this ps behavior is something that should be kept at current state even if it could be made better Ivan From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:08:54 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82665106568C; Tue, 25 Aug 2009 20:08:54 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 1A7318FC0C; Tue, 25 Aug 2009 20:08:53 +0000 (UTC) Received: from [192.168.1.4] (adsl-154-198-91.ard.bellsouth.net [72.154.198.91]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n7PJrowD023880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Aug 2009 15:53:51 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Thierry Herbelot In-Reply-To: <200908252127.48214.thierry.herbelot@free.fr> References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> <200908252127.48214.thierry.herbelot@free.fr> Content-Type: text/plain; charset="ISO-8859-1" Organization: FreeBSD Date: Tue, 25 Aug 2009 14:53:45 -0500 Message-Id: <1251230025.45706.280.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:08:54 -0000 On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit : > > > Meanwhile, if you interested in any information about this motherboard - > > > data dumps, outputs from tools, etc - please let me know, I will try my > > > best to provide that. > > > > it would be interesting to see a dmesg as a starting point. > > > here you are ;-) > > I have plugged a PCI sound board in the machine, but it does seem to be > detected (there could be some issue with PCI bus enumeration : I also include > a pciconf log) I'm curious why you would plug in a pci sound card? You already have both a standard hda codec as well as the hda codec for the hdmi port of the video. If you are discovering that it isn't working... set hw.snd.default_unit=1 which is typcially your normal analog audio port. The hdmi port on radeon chips tends to be enumerated before the normal system codecs, so people tend to think that sound isn't working. robert. > TfH > > > > Sam Fourman Jr. > > _______________________________________________ > > 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" > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.2-STABLE #12: Mon Jul 6 09:37:34 CEST 2009 > XXX@YYY:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3106.64-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 > > Features=0x178bfbff > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x11f > TSC: P-state invariant > Cores per package: 2 > usable memory = 4008947712 (3823 MB) > avail memory = 3836862464 (3659 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > This module (opensolaris) contains code covered by the > Common Development and Distribution License (CDDL) > see http://opensolaris.org/os/licensing/opensolaris_license/ > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bfce0000 (3) failed > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xee00-0xeeff mem > 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq 18 at > device 5.0 on pci1 > hdac0: mem 0xfdffc000-0xfdffffff > irq 19 at device 5.1 on pci1 > hdac0: HDA Driver Revision: 20090329_0131 > hdac0: [ITHREAD] > pcib2: irq 18 at device 10.0 on pci0 > pci2: on pcib2 > re0: Ethernet> port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff,0xfdae0000-0xfdaeffff > irq 18 at device 0.0 on pci2 > re0: Using 1 MSI messages > re0: Chip rev. 0x3c000000 > re0: MAC rev. 0x00400000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > re0: Ethernet address: 00:1f:d0:56:75:23 > re0: [FILTER] > atapci0: port > 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem > 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0 > atapci0: [ITHREAD] > atapci0: AHCI Version 01.10 controller with 6 ports detected > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > ata4: on atapci0 > ata4: [ITHREAD] > ata5: on atapci0 > ata5: [ITHREAD] > ata6: on atapci0 > ata6: [ITHREAD] > ata7: on atapci0 > ata7: [ITHREAD] > ohci0: mem 0xfe02e000-0xfe02efff irq 16 at > device 18.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem 0xfe02d000-0xfe02dfff irq 16 at > device 18.1 on pci0 > ohci1: [GIANT-LOCKED] > ohci1: [ITHREAD] > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 3 ports with 3 removable, self powered > ehci0: mem 0xfe02c000-0xfe02c0ff irq 17 at > device 18.2 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb2: EHCI version 1.0 > usb2: companion controllers, 3 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > uhub2: on usb2 > uhub2: 6 ports with 6 removable, self powered > ohci2: mem 0xfe02b000-0xfe02bfff irq 18 at > device 19.0 on pci0 > ohci2: [GIANT-LOCKED] > ohci2: [ITHREAD] > usb3: OHCI version 1.0, legacy support > usb3: on ohci2 > usb3: USB revision 1.0 > uhub3: on usb3 > uhub3: 3 ports with 3 removable, self powered > ohci3: mem 0xfe02a000-0xfe02afff irq 18 at > device 19.1 on pci0 > ohci3: [GIANT-LOCKED] > ohci3: [ITHREAD] > usb4: OHCI version 1.0, legacy support > usb4: SMM does not respond, resetting > usb4: on ohci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 3 ports with 3 removable, self powered > ehci1: mem 0xfe029000-0xfe0290ff irq 19 at > device 19.2 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb5: EHCI version 1.0 > usb5: companion controllers, 3 ports each: usb3 usb4 > usb5: on ehci1 > usb5: USB revision 2.0 > uhub5: on usb5 > uhub5: 6 ports with 6 removable, self powered > pci0: at device 20.0 (no driver attached) > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 > ata0: on atapci1 > ata0: [ITHREAD] > hdac1: mem 0xfe024000-0xfe027fff > irq 16 at device 20.2 on pci0 > hdac1: HDA Driver Revision: 20090329_0131 > hdac1: [ITHREAD] > isab0: at device 20.3 on pci0 > isa0: on isab0 > pcib3: at device 20.4 on pci0 > pci3: on pcib3 > fwohci0: mem > 0xfdcff000-0xfdcff7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci3 > fwohci0: [FILTER] > fwohci0: OHCI version 1.10 (ROM=0) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:70:c0:59:00:00:1f:d0 > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:70:c0:00:1f:d0 > fwe0: Ethernet address: 02:70:c0:00:1f:d0 > fwip0: on firewire0 > fwip0: Firewire address: 00:70:c0:59:00:00:1f:d0 @ 0xfffe00000000, S400, > maxrec 2048 > sbp0: on firewire0 > dcons_crom0: on firewire0 > dcons_crom0: bus_addr 0xb6e80000 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode > ohci4: mem 0xfe028000-0xfe028fff irq 18 at > device 20.5 on pci0 > ohci4: [GIANT-LOCKED] > ohci4: [ITHREAD] > usb6: OHCI version 1.0, legacy support > usb6: SMM does not respond, resetting > usb6: on ohci4 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > amdtemp0: on hostb4 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio0: [FILTER] > ppc0: port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > cpu0: on acpi0 > powernow0: on cpu0 > cpu1: on acpi0 > powernow1: on cpu1 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio2: configured irq 5 not in bitmap of probed irqs 0 > sio2: port may not be enabled > sio3: configured irq 9 not in bitmap of probed irqs 0 > sio3: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > WARNING: ZFS is considered to be an experimental feature in FreeBSD. > Timecounters tick every 1.000 msec > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > ad4: 238474MB at ata2-master SATA150 > ZFS filesystem version 13 > ZFS storage pool version 13 > ad6: 238475MB at ata3-master SATA150 > ad8: 238475MB at ata4-master SATA150 > acd0: DVDR at ata7-master SATA150 > hdac0: HDA Codec #0: ATI RS690/780 HDMI > pcm0: at cad 0 nid 1 on hdac0 > hdac1: HDA Codec #0: Realtek ALC885 > pcm1: at cad 0 nid 1 on hdac1 > pcm2: at cad 0 nid 1 on hdac1 > pcm3: at cad 0 nid 1 on hdac1 > GEOM_LABEL: Label for provider ad4s1a is ufsid/4895a4a721182022. > GEOM_LABEL: Label for provider ad4s1d is ufsid/4895a4b3b6d4e02e. > GEOM_LABEL: Label for provider ad4s1e is ufsid/4895a4b54799f68b. > GEOM_LABEL: Label for provider ad4s1f is ufsid/4895a4b724bcb48f. > GEOM_LABEL: Label for provider ad4s2a is ufsid/49185b60bbfa4d50. > GEOM_LABEL: Label for provider ad6s1 is ext2fs//. > GEOM_LABEL: Label for provider ad6s2 is ext2fs//1. > GEOM_LABEL: Label for provider ad8s1a is ufsid/4895a498589c3d5f. > GEOM_LABEL: Label for provider ad8s1d is ufsid/4895a48d5fd2f14b. > GEOM_LABEL: Label for provider ad8s1e is ufsid/4895a48489eb6120. > GEOM_LABEL: Label for provider ad8s1f is ufsid/4895a48a019d7151. > GEOM_LABEL: Label for provider ad8s2a is ufsid/4729b57b020c7526. > GEOM_LABEL: Label for provider ad8s2d is ufsid/4729b587458f5554. > GEOM_LABEL: Label for provider ad8s2e is ufsid/4729b58af29c6330. > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s2a > GEOM_LABEL: Label ufsid/49185b60bbfa4d50 removed. > > > > machine# pciconf -lv > hostb0@pci0:0:0:0: class=0x060000 card=0x96001022 chip=0x96001022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = HOST-PCI > pcib1@pci0:0:1:0: class=0x060400 card=0x96021022 chip=0x96021022 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:10:0: class=0x060400 card=0x96001022 chip=0x96091022 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = PCI-PCI > atapci0@pci0:0:17:0: class=0x010601 card=0xb0021458 chip=0x43911002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 SATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > ohci0@pci0:0:18:0: class=0x0c0310 card=0x50041458 chip=0x43971002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI0 Controller' > class = serial bus > subclass = USB > ohci1@pci0:0:18:1: class=0x0c0310 card=0x50041458 chip=0x43981002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI1 Controller' > class = serial bus > subclass = USB > ehci0@pci0:0:18:2: class=0x0c0320 card=0x50041458 chip=0x43961002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB EHCI Controller' > class = serial bus > subclass = USB > ohci2@pci0:0:19:0: class=0x0c0310 card=0x50041458 chip=0x43971002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI0 Controller' > class = serial bus > subclass = USB > ohci3@pci0:0:19:1: class=0x0c0310 card=0x50041458 chip=0x43981002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI1 Controller' > class = serial bus > subclass = USB > ehci1@pci0:0:19:2: class=0x0c0320 card=0x50041458 chip=0x43961002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB EHCI Controller' > class = serial bus > subclass = USB > none0@pci0:0:20:0: class=0x0c0500 card=0x43851458 chip=0x43851002 > rev=0x3a hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'ATI SMBus (ATI RD600/RS600)' > class = serial bus > subclass = SMBus > atapci1@pci0:0:20:1: class=0x01018a card=0x50021458 chip=0x439c1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'PATA 133 Controller (SB7xx)' > class = mass storage > subclass = ATA > hdac1@pci0:0:20:2: class=0x040300 card=0xa0021458 chip=0x43831002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'IXP SB600 High Definition Audio Controller' > class = multimedia > subclass = HDA > isab0@pci0:0:20:3: class=0x060100 card=0x43831002 chip=0x439d1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 LPC host controller' > class = bridge > subclass = PCI-ISA > pcib3@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 > rev=0x00 hdr=0x01 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'IXP SB600 PCI to PCI Bridge' > class = bridge > subclass = PCI-PCI > ohci4@pci0:0:20:5: class=0x0c0310 card=0x50041458 chip=0x43991002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI2 Controller' > class = serial bus > subclass = USB > hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport > Technology Configuration' > class = bridge > subclass = HOST-PCI > hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) Address Map' > class = bridge > subclass = HOST-PCI > hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller' > class = bridge > subclass = HOST-PCI > hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' > class = bridge > subclass = HOST-PCI > vgapci0@pci0:1:5:0: class=0x030000 card=0xd0001458 chip=0x96101002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'Radeon HD 3200 Integrated Graphics Processor (780G)' > class = display > subclass = VGA > hdac0@pci0:1:5:1: class=0x040300 card=0x960f1002 chip=0x960f1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > class = multimedia > subclass = HDA > re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' > class = network > subclass = ethernet > fwohci0@pci0:3:14:0: class=0x0c0010 card=0x10001458 chip=0x8024104c > rev=0x00 hdr=0x00 > vendor = 'Texas Instruments (TI)' > device = 'TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller' > class = serial bus > subclass = FireWire > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" -- Robert Noland FreeBSD From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:39:37 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 132A61065690 for ; Tue, 25 Aug 2009 20:39:37 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 9C6808FC24 for ; Tue, 25 Aug 2009 20:39:36 +0000 (UTC) Received: from OMTA23.westchester.pa.mail.comcast.net ([76.96.62.74]) by QMTA13.westchester.pa.mail.comcast.net with comcast id YfR51c0011c6gX85DkSNZz; Tue, 25 Aug 2009 20:26:22 +0000 Received: from daland.home ([24.34.211.11]) by OMTA23.westchester.pa.mail.comcast.net with comcast id YkW61c00H0FJTGg3jkW7q8; Tue, 25 Aug 2009 20:30:07 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mg2ay-000Pd1-8W; Tue, 25 Aug 2009 16:26:20 -0400 From: Alex Goncharov To: Ivan Radovanovic In-reply-to: <4A944370.2000306@gmail.com> (message from Ivan Radovanovic on Tue, 25 Aug 2009 22:02:56 +0200) References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> <4A943C18.2050103@gmail.com> <4A943D06.405@FreeBSD.org> <4A944370.2000306@gmail.com> Message-Id: Sender: Alex Goncharov Date: Tue, 25 Aug 2009 16:26:20 -0400 Cc: freebsd-hackers@FreeBSD.org, dougb@FreeBSD.org, brian@FreeBSD.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:39:37 -0000 ,--- You/Ivan (Tue, 25 Aug 2009 22:02:56 +0200) ----* | > Feel free to take a crack at this and send the results to the list for | > review. Improving the documentation is always a worthy goal. | > | I would do that for sure if everyone thinks this ps behavior is | something that should be kept at current state even if it could be made | better `---------------------------------------------------* Don't know how you are going to find about "everyone", but I, for one, think that modifying the established tool's behavior in the proposed manner is an utterly bad idea. Use shell aliases, functions and scripts wrapped around the primary tool to get the behavior you like -- let others stick with their established habits and wrappers. Improving the documentation would be good, OTOH. Thanks, -- Alex -- alex-goncharov@comcast.net -- From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:48:55 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB7B8106568F; Tue, 25 Aug 2009 20:48:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0738FC19; Tue, 25 Aug 2009 20:48:55 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2A72646B58; Tue, 25 Aug 2009 16:48:55 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 7E5998A029; Tue, 25 Aug 2009 16:48:54 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 25 Aug 2009 16:47:36 -0400 User-Agent: KMail/1.9.7 References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A943D06.405@FreeBSD.org> <4A944370.2000306@gmail.com> In-Reply-To: <4A944370.2000306@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908251647.36679.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 25 Aug 2009 16:48:54 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Doug Barton , Brian Somers , Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:48:55 -0000 On Tuesday 25 August 2009 4:02:56 pm Ivan Radovanovic wrote: > Doug Barton napisa: > > Ivan Radovanovic wrote: > > > >> I totally disagree with you - being against change means that you > >> believe it is done the best way it could be done. > >> > > This argument is so non-sequitur that I'm tempted not to respond, but > > no, that's not what I'm saying at all. What I'm saying is that there > > are valid reasons to leave the defaults as they are, AND if you don't > > like the defaults there are easy ways to manipulate that in your own > > environment. > > > You wrote : > > Longer version, I don't see anything wrong with the defaults the way > that they are, and the fact that there is a teeny-tiny learning curve > for people who need to see the full output isn't really an issue that > deserves the time already spent on it. Bruce pointed out in the PR > that most users would be surprised if 'ps -ax | grep foo' suddenly > sprouted a lot more stuff that 'ps -ax' didn't have, and I agree. As a > matter of personal preference I find the current defaults to be just > lovely, and occasionally use -w or -ww if I need to see more. If you > want the default to be something different, that's what aliases are for. > > So, valid arguments against change should be: > 1. users will be surprised if ps starts displaying more stuff no matter if that stuff is correct and less stuff (current state) is incorrect > 2. your personal preference is that current defaults are lovely POLA -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:51:46 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63C80106568D for ; Tue, 25 Aug 2009 20:51:46 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from hamlet.setfilepointer.com (hamlet.SetFilePointer.com [63.224.10.2]) by mx1.freebsd.org (Postfix) with SMTP id 0AE788FC19 for ; Tue, 25 Aug 2009 20:51:45 +0000 (UTC) Received: (qmail 14274 invoked from network); 25 Aug 2009 15:51:44 -0500 Received: from keira.kiwi-computer.com (HELO kiwi-computer.com) (63.224.10.3) by hamlet.setfilepointer.com with SMTP; 25 Aug 2009 15:51:44 -0500 Received: (qmail 47017 invoked by uid 2001); 25 Aug 2009 20:51:43 -0000 Date: Tue, 25 Aug 2009 15:51:43 -0500 From: "Rick C. Petty" To: Jonathan McKeown Message-ID: <20090825205143.GA46753@keira.kiwi-computer.com> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <200908251609.09302.j.mckeown@ru.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908251609.09302.j.mckeown@ru.ac.za> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2008@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:51:46 -0000 On Tue, Aug 25, 2009 at 04:09:09PM +0200, Jonathan McKeown wrote: > > I usually want to see ps(1) output in easily-read columns. Without width > limits, this can't be guaranteed. > > I would strongly object to the complete removal of any option to limit the > output width of ps(1) and make it easily human-readable. > > I'm also astonished at the suggestion that not using -ww is ``a mistake''. I > very seldom need to see the whole commandline for every process. Then you must not use Java much. I almost always need the -ww option. I'm fine with the default being "fit into my terminal width", but I'd be for one option to specify limited width and another option (-w) to specify "as wide as possible". -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 19:46:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8343B1065743; Tue, 25 Aug 2009 19:46:21 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtpfb1-g21.free.fr (smtpfb1-g21.free.fr [212.27.42.9]) by mx1.freebsd.org (Postfix) with ESMTP id 943A88FC1A; Tue, 25 Aug 2009 19:46:17 +0000 (UTC) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by smtpfb1-g21.free.fr (Postfix) with ESMTP id 8294F77CB3E; Tue, 25 Aug 2009 21:28:12 +0200 (CEST) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id 1C5484C810F; Tue, 25 Aug 2009 21:28:03 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id E2DB14C8182; Tue, 25 Aug 2009 21:28:00 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n7PJRrst009804; Tue, 25 Aug 2009 21:27:54 +0200 (CEST) From: Thierry Herbelot To: freebsd-hackers@freebsd.org Date: Tue, 25 Aug 2009 21:27:47 +0200 User-Agent: KMail/1.9.10 References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> In-Reply-To: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200908252127.48214.thierry.herbelot@free.fr> X-Mailman-Approved-At: Tue, 25 Aug 2009 21:02:49 +0000 Cc: "Sam Fourman Jr." , freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 19:46:21 -0000 Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit : > > Meanwhile, if you interested in any information about this motherboard - > > data dumps, outputs from tools, etc - please let me know, I will try my > > best to provide that. > > it would be interesting to see a dmesg as a starting point. > here you are ;-) I have plugged a PCI sound board in the machine, but it does seem to be detected (there could be some issue with PCI bus enumeration : I also include a pciconf log) TfH > > Sam Fourman Jr. > _______________________________________________ > 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" Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #12: Mon Jul 6 09:37:34 CEST 2009 XXX@YYY:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3106.64-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f TSC: P-state invariant Cores per package: 2 usable memory = 4008947712 (3823 MB) avail memory = 3836862464 (3659 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bfce0000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq 18 at device 5.0 on pci1 hdac0: mem 0xfdffc000-0xfdffffff irq 19 at device 5.1 on pci1 hdac0: HDA Driver Revision: 20090329_0131 hdac0: [ITHREAD] pcib2: irq 18 at device 10.0 on pci0 pci2: on pcib2 re0: port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff,0xfdae0000-0xfdaeffff irq 18 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1f:d0:56:75:23 re0: [FILTER] atapci0: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 6 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: [ITHREAD] ohci0: mem 0xfe02e000-0xfe02efff irq 16 at device 18.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe02d000-0xfe02dfff irq 16 at device 18.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfe02c000-0xfe02c0ff irq 17 at device 18.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered ohci2: mem 0xfe02b000-0xfe02bfff irq 18 at device 19.0 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: on ohci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 3 ports with 3 removable, self powered ohci3: mem 0xfe02a000-0xfe02afff irq 18 at device 19.1 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 3 ports with 3 removable, self powered ehci1: mem 0xfe029000-0xfe0290ff irq 19 at device 19.2 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 3 ports each: usb3 usb4 usb5: on ehci1 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 6 ports with 6 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] hdac1: mem 0xfe024000-0xfe027fff irq 16 at device 20.2 on pci0 hdac1: HDA Driver Revision: 20090329_0131 hdac1: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 fwohci0: mem 0xfdcff000-0xfdcff7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci3 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:70:c0:59:00:00:1f:d0 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:70:c0:00:1f:d0 fwe0: Ethernet address: 02:70:c0:00:1f:d0 fwip0: on firewire0 fwip0: Firewire address: 00:70:c0:59:00:00:1f:d0 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xb6e80000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ohci4: mem 0xfe028000-0xfe028fff irq 18 at device 20.5 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb6: OHCI version 1.0, legacy support usb6: SMM does not respond, resetting usb6: on ohci4 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered amdtemp0: on hostb4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio2: configured irq 5 not in bitmap of probed irqs 0 sio2: port may not be enabled sio3: configured irq 9 not in bitmap of probed irqs 0 sio3: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad4: 238474MB at ata2-master SATA150 ZFS filesystem version 13 ZFS storage pool version 13 ad6: 238475MB at ata3-master SATA150 ad8: 238475MB at ata4-master SATA150 acd0: DVDR at ata7-master SATA150 hdac0: HDA Codec #0: ATI RS690/780 HDMI pcm0: at cad 0 nid 1 on hdac0 hdac1: HDA Codec #0: Realtek ALC885 pcm1: at cad 0 nid 1 on hdac1 pcm2: at cad 0 nid 1 on hdac1 pcm3: at cad 0 nid 1 on hdac1 GEOM_LABEL: Label for provider ad4s1a is ufsid/4895a4a721182022. GEOM_LABEL: Label for provider ad4s1d is ufsid/4895a4b3b6d4e02e. GEOM_LABEL: Label for provider ad4s1e is ufsid/4895a4b54799f68b. GEOM_LABEL: Label for provider ad4s1f is ufsid/4895a4b724bcb48f. GEOM_LABEL: Label for provider ad4s2a is ufsid/49185b60bbfa4d50. GEOM_LABEL: Label for provider ad6s1 is ext2fs//. GEOM_LABEL: Label for provider ad6s2 is ext2fs//1. GEOM_LABEL: Label for provider ad8s1a is ufsid/4895a498589c3d5f. GEOM_LABEL: Label for provider ad8s1d is ufsid/4895a48d5fd2f14b. GEOM_LABEL: Label for provider ad8s1e is ufsid/4895a48489eb6120. GEOM_LABEL: Label for provider ad8s1f is ufsid/4895a48a019d7151. GEOM_LABEL: Label for provider ad8s2a is ufsid/4729b57b020c7526. GEOM_LABEL: Label for provider ad8s2d is ufsid/4729b587458f5554. GEOM_LABEL: Label for provider ad8s2e is ufsid/4729b58af29c6330. SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s2a GEOM_LABEL: Label ufsid/49185b60bbfa4d50 removed. machine# pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x96001022 chip=0x96001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x96021022 chip=0x96021022 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = PCI-PCI pcib2@pci0:0:10:0: class=0x060400 card=0x96001022 chip=0x96091022 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = PCI-PCI atapci0@pci0:0:17:0: class=0x010601 card=0xb0021458 chip=0x43911002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 SATA Controller [AHCI mode]' class = mass storage subclass = SATA ohci0@pci0:0:18:0: class=0x0c0310 card=0x50041458 chip=0x43971002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI0 Controller' class = serial bus subclass = USB ohci1@pci0:0:18:1: class=0x0c0310 card=0x50041458 chip=0x43981002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI1 Controller' class = serial bus subclass = USB ehci0@pci0:0:18:2: class=0x0c0320 card=0x50041458 chip=0x43961002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB EHCI Controller' class = serial bus subclass = USB ohci2@pci0:0:19:0: class=0x0c0310 card=0x50041458 chip=0x43971002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI0 Controller' class = serial bus subclass = USB ohci3@pci0:0:19:1: class=0x0c0310 card=0x50041458 chip=0x43981002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI1 Controller' class = serial bus subclass = USB ehci1@pci0:0:19:2: class=0x0c0320 card=0x50041458 chip=0x43961002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB EHCI Controller' class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x43851458 chip=0x43851002 rev=0x3a hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI SMBus (ATI RD600/RS600)' class = serial bus subclass = SMBus atapci1@pci0:0:20:1: class=0x01018a card=0x50021458 chip=0x439c1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'PATA 133 Controller (SB7xx)' class = mass storage subclass = ATA hdac1@pci0:0:20:2: class=0x040300 card=0xa0021458 chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'IXP SB600 High Definition Audio Controller' class = multimedia subclass = HDA isab0@pci0:0:20:3: class=0x060100 card=0x43831002 chip=0x439d1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 LPC host controller' class = bridge subclass = PCI-ISA pcib3@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'IXP SB600 PCI to PCI Bridge' class = bridge subclass = PCI-PCI ohci4@pci0:0:20:5: class=0x0c0310 card=0x50041458 chip=0x43991002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI2 Controller' class = serial bus subclass = USB hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' class = bridge subclass = HOST-PCI vgapci0@pci0:1:5:0: class=0x030000 card=0xd0001458 chip=0x96101002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'Radeon HD 3200 Integrated Graphics Processor (780G)' class = display subclass = VGA hdac0@pci0:1:5:1: class=0x040300 card=0x960f1002 chip=0x960f1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' class = multimedia subclass = HDA re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' class = network subclass = ethernet fwohci0@pci0:3:14:0: class=0x0c0010 card=0x10001458 chip=0x8024104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller' class = serial bus subclass = FireWire From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 20:31:19 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F6701065691; Tue, 25 Aug 2009 20:31:19 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtpfb1-g21.free.fr (smtpfb1-g21.free.fr [212.27.42.9]) by mx1.freebsd.org (Postfix) with ESMTP id E984C8FC1C; Tue, 25 Aug 2009 20:31:15 +0000 (UTC) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by smtpfb1-g21.free.fr (Postfix) with ESMTP id D53D32DA47; Tue, 25 Aug 2009 22:14:41 +0200 (CEST) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id 9C5C54C807F; Tue, 25 Aug 2009 22:14:32 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id 9FBAD4C816D; Tue, 25 Aug 2009 22:14:29 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n7PKESAT002345; Tue, 25 Aug 2009 22:14:28 +0200 (CEST) From: Thierry Herbelot To: Robert Noland Date: Tue, 25 Aug 2009 22:14:22 +0200 User-Agent: KMail/1.9.10 References: <4A9412ED.6080309@freebsd.org> <200908252127.48214.thierry.herbelot@free.fr> <1251230025.45706.280.camel@balrog.2hip.net> In-Reply-To: <1251230025.45706.280.camel@balrog.2hip.net> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200908252214.22667.thierry@herbelot.com> X-Mailman-Approved-At: Tue, 25 Aug 2009 21:16:11 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 20:31:19 -0000 Le Tuesday 25 August 2009, Robert Noland a écrit : > On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > > Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit : > > > > Meanwhile, if you interested in any information about this > > > > motherboard - data dumps, outputs from tools, etc - please let me > > > > know, I will try my best to provide that. > > > > > > it would be interesting to see a dmesg as a starting point. > > > > here you are ;-) > > > > I have plugged a PCI sound board in the machine, but it does seem to be > > detected (there could be some issue with PCI bus enumeration : I also > > include a pciconf log) > > I'm curious why you would plug in a pci sound card? You already have > both a standard hda codec as well as the hda codec for the hdmi port of > the video. If you are discovering that it isn't working... set Initially, this was the issue, before other people sent various howtos around the probe of the hdmi hda port (which by the way sounds *much* better than my previous cmi board). Afterwards, the PCI board remained in the machine (leftover from a previous box), but it is still *not* seen by the PCI enumeration (I'm a bit too lazy to find another spare PCI board and plug it in see what happens : is it also ignored by the BIOS/ACPI/whatever and/or the kernel ?). It seems that it is not either detected by a Linux kernel. TfH > hw.snd.default_unit=1 which is typcially your normal analog audio port. > The hdmi port on radeon chips tends to be enumerated before the normal > system codecs, so people tend to think that sound isn't working. > > robert. > From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 21:24:06 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001151065701; Tue, 25 Aug 2009 21:24:05 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 2DCDD8FC22; Tue, 25 Aug 2009 21:24:04 +0000 (UTC) Received: by fxm6 with SMTP id 6so2339106fxm.43 for ; Tue, 25 Aug 2009 14:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=FKfJuebSGv9QRRCRgixShzruHosCURtgZJNydM5U4eg=; b=R7/ZaI/QQ8VBhQwQDgyKNdcB5VXw4Ohb1Sr+0QGWZ0ev8bFiesmcRJuszVaSuhpma6 7CBAj7whQyjVszuqgzGEa55Sz3fIQGRAtVghNs6Z4tv10M7/42Ly1yS+RyjWEdZx8FlI PCWX5RwgSyVlK4WVqB6PAytzy3igDkYhPhafI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Elq0aQnGkBi5/EioRRyZ8XR4g/EtAcI08R0cDwc/IMAwAGoMW6vOpR81Q99/6kY0XK IzpLNXqqxXAD5cu7fYusN3RFfnoGu5b2ngoHmh70vsBAvQdjhhFABzhyIIiDm/aJvXEd AXXE5X9595azj4kam1zqf5AuaCHwNyAbq1uOA= Received: by 10.103.85.28 with SMTP id n28mr3034262mul.66.1251235444198; Tue, 25 Aug 2009 14:24:04 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id j2sm425638mue.50.2009.08.25.14.24.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 Aug 2009 14:24:03 -0700 (PDT) Message-ID: <4A945672.6010901@gmail.com> Date: Tue, 25 Aug 2009 23:24:02 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: Alex Goncharov References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> <4A943C18.2050103@gmail.com> <4A943D06.405@FreeBSD.org> <4A944370.2000306@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, dougb@FreeBSD.org, brian@FreeBSD.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 21:24:06 -0000 Alex Goncharov napisa: > ,--- You/Ivan (Tue, 25 Aug 2009 22:02:56 +0200) ----* > | > Feel free to take a crack at this and send the results to the list for > | > review. Improving the documentation is always a worthy goal. > | > > | I would do that for sure if everyone thinks this ps behavior is > | something that should be kept at current state even if it could be made > | better > `---------------------------------------------------* > > Don't know how you are going to find about "everyone", but I, for one, > think that modifying the established tool's behavior in the proposed > manner is an utterly bad idea. > > Use shell aliases, functions and scripts wrapped around the primary > tool to get the behavior you like -- let others stick with their > established habits and wrappers. > > Improving the documentation would be good, OTOH. > > Thanks, > > -- Alex -- alex-goncharov@comcast.net -- > I guess voting is going against me, so I would probably need to update that documentation :-) Please understand that my idea is to make tool behave as expected from its description - for example ls also formats its output according to terminal, but when you redirect it then it doesn't care about terminal (try "ls" and "ls | less"), that is what in the first place made me think that ps would behave in the same way (and btw, I still think that all non-interactive tools behave that way). And I also think that if we can make learning FreeBSD even little less difficult then we should do that. My point is if you are making tool for listing processes what you want is to LIST process (first, and most important), and later (if at all) to make that pretty formatted, after all it is unix philosophy to have small programs that do exactly one thing and that do it right - I think that philosophy is broken (because of historical reasons) with current implementation of ps On the other hand fixing ps's behavior in the proposed manner will for sure brake some scripts that depend on it, but if scripts depend on formatting behavior then those scripts are used only to display some information on the terminal and they would be easily spotted and corrected (are there scripts like that in the system - can someone point out and say "Hey XXX will be broken, and that will further brake YYY and so on"? Because I am beginning to think that maybe there is far less things depending on this behavior than expected... ) Ivan P.S. I am giving up of trying to explain my reasoning any more, I think I gave enough reasons for everyone to understand my motivation (although of course everyone has the right not to agree with me). I didn't want to offend anyone in this short discussion and if someone feels that way then I am truly sorry. Any pointers on how to update manual page for ps would be greatly appreciated, as well as some mail agreeing with my standpoint :-) From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 21:28:23 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B65C3106568B; Tue, 25 Aug 2009 21:28:23 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0A88FC18; Tue, 25 Aug 2009 21:28:23 +0000 (UTC) Received: from [192.168.1.4] (adsl-154-198-91.ard.bellsouth.net [72.154.198.91]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n7PLSK8a024393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Aug 2009 17:28:21 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Thierry Herbelot In-Reply-To: <200908252214.22667.thierry@herbelot.com> References: <4A9412ED.6080309@freebsd.org> <200908252127.48214.thierry.herbelot@free.fr> <1251230025.45706.280.camel@balrog.2hip.net> <200908252214.22667.thierry@herbelot.com> Content-Type: text/plain; charset="ISO-8859-1" Organization: FreeBSD Date: Tue, 25 Aug 2009 16:28:15 -0500 Message-Id: <1251235695.45706.375.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 21:28:23 -0000 On Tue, 2009-08-25 at 22:14 +0200, Thierry Herbelot wrote: > Le Tuesday 25 August 2009, Robert Noland a écrit : > > On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > > > Le Tuesday 25 August 2009, Sam Fourman Jr. a écrit : > > > > > Meanwhile, if you interested in any information about this > > > > > motherboard - data dumps, outputs from tools, etc - please let me > > > > > know, I will try my best to provide that. > > > > > > > > it would be interesting to see a dmesg as a starting point. > > > > > > here you are ;-) > > > > > > I have plugged a PCI sound board in the machine, but it does seem to be > > > detected (there could be some issue with PCI bus enumeration : I also > > > include a pciconf log) > > > > I'm curious why you would plug in a pci sound card? You already have > > both a standard hda codec as well as the hda codec for the hdmi port of > > the video. If you are discovering that it isn't working... set > > Initially, this was the issue, before other people sent various howtos around > the probe of the hdmi hda port (which by the way sounds *much* better than my > previous cmi board). > > Afterwards, the PCI board remained in the machine (leftover from a previous > box), but it is still *not* seen by the PCI enumeration (I'm a bit too lazy > to find another spare PCI board and plug it in see what happens : is it also > ignored by the BIOS/ACPI/whatever and/or the kernel ?). > > It seems that it is not either detected by a Linux kernel. Perhaps it isn't seated properly? Or possibly a different slot might help. robert. > TfH > > > hw.snd.default_unit=1 which is typcially your normal analog audio port. > > The hdmi port on radeon chips tends to be enumerated before the normal > > system codecs, so people tend to think that sound isn't working. > > > > robert. > > -- Robert Noland FreeBSD From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 21:59:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 333F1106564A; Tue, 25 Aug 2009 21:59:20 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-gx0-f227.google.com (mail-gx0-f227.google.com [209.85.217.227]) by mx1.freebsd.org (Postfix) with ESMTP id A4E868FC14; Tue, 25 Aug 2009 21:59:19 +0000 (UTC) Received: by gxk27 with SMTP id 27so4438011gxk.12 for ; Tue, 25 Aug 2009 14:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OhSce9O6R5irC/ay9Bx/LnrxMU4rfrdKZShTCwzGyd0=; b=dNU0ph98OoBU78lLNsqjB3G+vYNGB/YzIZR3d/F/s8+6UeZ5pR+pn6Jh3FQP4cDKnP BfwJWE6Q57PpTChlw2xpEBKF0pKmWTMyCACFg0dQtPdQvG2bYoeGreTOxWw+zme4Bgkm Sx9oAT2gkKAcjuSUnmY8/pAJIQIG+OrIpBzjw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mbN87wuDa8ElM3NXb/HU/WAud6JFevj+O/W6KSUnMMo8OW8A6GsQwKdk/lUXsGcfvX /ZWVjUxyUQ5KCiAtU30r9JPOMD5Tf/4GnKjQjafFVpgYnbW/irLW4vtwzcQW7avBpT10 ssIAk+e2rPJvzaPWrsFjvuMOIxUCdDfHoPj40= MIME-Version: 1.0 Received: by 10.150.88.35 with SMTP id l35mr10029637ybb.274.1251237558683; Tue, 25 Aug 2009 14:59:18 -0700 (PDT) In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Date: Tue, 25 Aug 2009 16:59:18 -0500 Message-ID: <11167f520908251459r7477fac3kdf3ff6e603a313dd@mail.gmail.com> From: "Sam Fourman Jr." To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 21:59:20 -0000 On Tue, Aug 25, 2009 at 11:35 AM, Andriy Gapon wrote: > > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H > It is based on AMD 780G + SB700. > BTW, CPU I am using is Athlon II X2 250. are you using a i386 or AMD64 kernel? maybe I am blind but I didnt see it in your dmesg Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 22:06:14 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0091106568E; Tue, 25 Aug 2009 22:06:14 +0000 (UTC) (envelope-from bernt@bah.homeip.net) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) by mx1.freebsd.org (Postfix) with ESMTP id 5F09B8FC19; Tue, 25 Aug 2009 22:06:14 +0000 (UTC) Received: from kw.homeip.net (c80-217-74-129.bredband.comhem.se [80.217.74.129]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id n7PLtQUC095670; Tue, 25 Aug 2009 23:55:29 +0200 (CEST) (envelope-from bernt@bah.homeip.net) Message-ID: <4A945DC1.8070202@bah.homeip.net> Date: Tue, 25 Aug 2009 23:55:13 +0200 From: Bernt Hansson User-Agent: slrn/1.0.8 (FreeBSD) MIME-Version: 1.0 To: Andriy Gapon References: <4A9412ED.6080309@freebsd.org> In-Reply-To: <4A9412ED.6080309@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 25 Aug 2009 22:08:48 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 22:06:15 -0000 Andriy Gapon said the following on 2009-08-25 18:35: > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H > It is based on AMD 780G + SB700. > BTW, CPU I am using is Athlon II X2 250. > > Sorry for the broadcast announcement, but this is my first AMD-based system in > many years, so I eagerly started exploring it and hacking for it. > > For this reason please expect a number of questions from me as well as some > reports and hopefully code related to this motherboard. I am going to post them as > follow-ups to this email. > > Meanwhile, if you interested in any information about this motherboard - data > dumps, outputs from tools, etc - please let me know, I will try my best to provide > that. > It would be interesting to know if you can have usb devices connected and detected during boot. With SB600 you can not. From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 25 22:27:58 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8349B10656A3 for ; Tue, 25 Aug 2009 22:27:58 +0000 (UTC) (envelope-from kindman@amc-os.com) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE5D8FC2C for ; Tue, 25 Aug 2009 22:27:55 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id 19DE94C8090; Wed, 26 Aug 2009 00:27:50 +0200 (CEST) Received: from kindman (blackforest.amc-os.net [88.174.102.207]) by smtp4-g21.free.fr (Postfix) with SMTP id E7C894C8072; Wed, 26 Aug 2009 00:27:47 +0200 (CEST) Message-ID: <604B96C6CF22447EACE5BD9719DDE1F5@kindman> From: "Aurélien Méré" To: "Andriy Gapon" , , References: <4A9412ED.6080309@freebsd.org> <4A94242B.7090806@freebsd.org> Date: Wed, 26 Aug 2009 00:27:41 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-RFC2646: Format=Flowed; Original Cc: Subject: Re: AMD SB700 SMBus controller driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 22:27:58 -0000 Could you please forward me the patch to make it work in polling mode ? I'd like to test it as I've been trying to make intpm work with a SB400 (which should be quite the same as yours) but system hangs when I try to force polling mode (didn't have the specs nor all the differences you just presented). And btw, I didn't find any implementation using interrupt neither but I'm ready to test your updated version. Thanks, Aurélien ----- Original Message ----- From: "Andriy Gapon" To: ; Sent: Tuesday, August 25, 2009 7:49 PM Subject: AMD SB700 SMBus controller driver > > According to SB700 specifications its SMBus controller is very similar to > one in > PIIX4. > The differences that I see so far: > > 1. Interrupt Line/Interrupt Pin PCI configuration registers (0x3c, 0x3d) > do not > specify interrupt number that the controller could use: >> This register specifies which interrupt pin the device issue >> This module does not generate interrupt but contains the >> actual interrupt controller. This register is hardcoded to 0. > > 2. I2CbusConfig register (0xd2) uses bit #1 to indicate whether SMI or > regular > interrupt is used in interrupt mode; PIIX4 uses bit 3. > > I couldn't get our intpm driver to work with this hardware by simply > adding PCI id > and tweaking 0xd2 bits meaning. > > I could get it to work by forcing polling mode. It appears that Linux > driver for > this HW always uses polling mode, and OpenBSD and NetBSD drivers would use > it with > this HW too. > > I am still trying to get interrupt mode to work. > I set 0xd2 to enable regular interrupt generation (it is set to SMI after > boot). > SB700 specifications say at one place that SMB interrupt is connected to > INTIN20 > pin of IO-APIC in APIC mode. I tried setting up IRQ20 in the driver but no > interrupts are generated. And there are no stray interrupts either. > So I am not sure - either this HW doesn't generate normal interrupts at > all, or > they to a different pin, or additional setup is required, or I am doing > something > wrong. > > Anyway, I plan to produce an updated version of intpm driver with > possibility of > forced or auto-detected polling mode and support for PCI id of SB700 SMBus > controller and its peculiarities. > > -- > Andriy Gapon > _______________________________________________ > 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 Aug 25 22:57:46 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15C1D106568D for ; Tue, 25 Aug 2009 22:57:46 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id EEC718FC1A for ; Tue, 25 Aug 2009 22:57:45 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 95DB5BABB; Tue, 25 Aug 2009 15:58:15 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id D8A432D6006; Tue, 25 Aug 2009 15:57:44 -0700 (PDT) Message-ID: <4A946C68.40302@elischer.org> Date: Tue, 25 Aug 2009 15:57:44 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Ivan Radovanovic References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> <4A94385A.1000405@FreeBSD.org> <4A943C18.2050103@gmail.com> <4A943D06.405@FreeBSD.org> <4A944370.2000306@gmail.com> In-Reply-To: <4A944370.2000306@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Doug Barton , Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 22:57:46 -0000 Ivan Radovanovic wrote: > Doug Barton napisa: >> Ivan Radovanovic wrote: >> >>> I totally disagree with you - being against change means that you >>> believe it is done the best way it could be done. >>> >> This argument is so non-sequitur that I'm tempted not to respond, but >> no, that's not what I'm saying at all. What I'm saying is that there >> are valid reasons to leave the defaults as they are, AND if you don't >> like the defaults there are easy ways to manipulate that in your own >> environment. >> > > I would do that for sure if everyone thinks this ps behavior is > something that should be kept at current state even if it could be made > better -w was added to show more information, and -ww for "all" information. I find no problem understanding this and see no reason to change it. "blue please" p.s. -ww can get "big" > > Ivan > _______________________________________________ > 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 Aug 26 04:11:08 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA879106568E; Wed, 26 Aug 2009 04:11:08 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id EF8D28FC22; Wed, 26 Aug 2009 04:11:04 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id A9D8D4C8099; Wed, 26 Aug 2009 06:11:00 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id 820594C8066; Wed, 26 Aug 2009 06:10:57 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n7Q4AppB022458; Wed, 26 Aug 2009 06:10:52 +0200 (CEST) From: Thierry Herbelot To: freebsd-hackers@freebsd.org Date: Wed, 26 Aug 2009 06:10:45 +0200 User-Agent: KMail/1.9.10 References: <4A9412ED.6080309@freebsd.org> <4A945DC1.8070202@bah.homeip.net> In-Reply-To: <4A945DC1.8070202@bah.homeip.net> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200908260610.45849.thierry@herbelot.com> X-Mailman-Approved-At: Wed, 26 Aug 2009 05:01:45 +0000 Cc: freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org, Bernt Hansson Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 04:11:08 -0000 Le Tuesday 25 August 2009, Bernt Hansson a écrit : > Andriy Gapon said the following on 2009-08-25 18:35: > > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassV > >alue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on > > AMD 780G + SB700. > > BTW, CPU I am using is Athlon II X2 250. > > > > Sorry for the broadcast announcement, but this is my first AMD-based > > system in many years, so I eagerly started exploring it and hacking for > > it. > > > > For this reason please expect a number of questions from me as well as > > some reports and hopefully code related to this motherboard. I am going > > to post them as follow-ups to this email. > > > > Meanwhile, if you interested in any information about this motherboard - > > data dumps, outputs from tools, etc - please let me know, I will try my > > best to provide that. > > It would be interesting to know if you can have usb devices connected > and detected during boot. With SB600 you can not. This maybe the explanation why I have to re-plug the USB mouse each time the machine is restarted ;-) (with an SB700) TfH From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 05:26:45 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6525A106568F; Wed, 26 Aug 2009 05:26:45 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by mx1.freebsd.org (Postfix) with ESMTP id 2C8DB8FC21; Wed, 26 Aug 2009 05:26:44 +0000 (UTC) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id n7Q4Dc46031796; Wed, 26 Aug 2009 00:13:39 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <4A94325D.6070201@FreeBSD.org> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> Date: Wed, 26 Aug 2009 00:13:37 -0400 To: Doug Barton , Brian Somers From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 0.10 () [Hold at 20.00] COMBINED_FROM X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225 Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 05:26:45 -0000 At 11:50 AM -0700 8/25/09, Doug Barton wrote: >Brian Somers wrote: >> I recently closed bin/137647 and had second thoughts after Ivan (the >> originator) challenged my reason for closing it. >> >> The suggestion is that ps's -w switch is a strange artifact that can >> be safely deprecated. ps goes to great lengths to implement width >> limitations, and any time I've seen people not using -ww has either >> been a mistake or doesn't matter. Using 'cut -c1-N' is also a great >> way of limiting widths if people really want that... >> >> I'd like to propose changing ps so that width limits are removed and >> '-w' is deprecated - ignored for now with a note in the man page >> saying that it will be removed in a future release. >> >> Does anyone have any objections to doing this? I don't propose >> merging this back into stable/8. > >Short version, yes, I object to changing the defaults. Speaking as someone who has worked on 'ps' in the past, I recommend that you go slow in making arbitrary changes. 'ps' is already a minefield of craziness between various versions of unix, and adding this new variant will just make matters worse. You certainly can not go back to older releases and change the formatting there, so all programmers who write for a variety of machines/platforms will just end up with one extra way for things to break. -- Garance Alistair Drosehn = drosehn@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 07:06:31 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D341106568E for ; Wed, 26 Aug 2009 07:06:31 +0000 (UTC) (envelope-from j.mckeown@ru.ac.za) Received: from f.mail.ru.ac.za (f.mail.ru.ac.za [IPv6:2001:4200:1010::25:6]) by mx1.freebsd.org (Postfix) with ESMTP id 750608FC21 for ; Wed, 26 Aug 2009 07:06:30 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ru-msa; d=ru.ac.za; h=Received:From:Organization:To:Subject:Date:User-Agent:References:In-Reply-To:X-Face:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-Virus-Scanned:X-Authenticated-User; b=c7rCssn9wuQ2ig1G7nVzUljkb13hEAO9OTkVTY6Y3zxVPX1JPAYDEdWksBuE020g6aDvREiNjVkNc3lXitAlwMrlzEiE8IKA3cuDbq+YVd4R3wWQ7zyTKYaJraxExozB; Received: from vorkosigan.ru.ac.za ([2001:4200:1010:1058:219:d1ff:fe9f:a932]:64105) by f.mail.ru.ac.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgCaL-0005rN-Iv; Wed, 26 Aug 2009 09:06:21 +0200 From: Jonathan McKeown Organization: Rhodes University To: freebsd-hackers@freebsd.org, rick-freebsd2008@kiwi-computer.com Date: Wed, 26 Aug 2009 09:06:21 +0200 User-Agent: KMail/1.9.10 References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <200908251609.09302.j.mckeown@ru.ac.za> <20090825205143.GA46753@keira.kiwi-computer.com> In-Reply-To: <20090825205143.GA46753@keira.kiwi-computer.com> X-Face: $@VrUx^RHy/}yu]jKf/<4T%/d|F+$j-Ol2"2J$q+%OK1]&/G_S9(=?utf-8?q?HkaQ*=60!=3FYOK=3FY!=27M=60C=0A=09aP=5C9nVPF8Q=7DCilHH8l=3B=7E!4?= =?utf-8?q?2HK6=273lg4J=7Daz?=@1Dqqh:J]M^"YPn*2IWrZON$1+G?oX3@ =?utf-8?q?k=230=0A=0954XDRg=3DYn=5FF-etwot4U=24b?=dTS{i X-Virus-Scanned: f.mail.ru.ac.za (2001:4200:1010::25:6) X-Authenticated-User: s0900137 from vorkosigan.ru.ac.za (2001:4200:1010:1058:219:d1ff:fe9f:a932) using auth_plaintext Cc: Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 07:06:31 -0000 On Tuesday 25 August 2009 22:51:43 Rick C. Petty wrote: > On Tue, Aug 25, 2009 at 04:09:09PM +0200, Jonathan McKeown wrote: > > I usually want to see ps(1) output in easily-read columns. Without width > > limits, this can't be guaranteed. > > > > I would strongly object to the complete removal of any option to limit > > the output width of ps(1) and make it easily human-readable. > > > > I'm also astonished at the suggestion that not using -ww is ``a > > mistake''. I very seldom need to see the whole commandline for every > > process. > > Then you must not use Java much. I almost always need the -ww option. > I'm fine with the default being "fit into my terminal width", but I'd be > for one option to specify limited width and another option (-w) to > specify "as wide as possible". As it happens, you're right: I don't use Java at all. Neither do I object=20 (much) to a change in the default behaviour such that wide output is the no= rm=20 and restricted-width an option. In the original message, Brian Somers wrote: > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. =A0ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. =A0Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... > > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. The suggestion seems to be to remove the width-limiting code altogether, an= d=20 make people who want width-restricted output (for example to keep it in=20 columns which are easily scanned by eye) pipe the output through another=20 command. That I do object to. From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 07:59:33 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97FA8106568D for ; Wed, 26 Aug 2009 07:59:33 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153]) by mx1.freebsd.org (Postfix) with ESMTP id 7398C8FC24 for ; Wed, 26 Aug 2009 07:59:33 +0000 (UTC) Received: from gluon.draftnet (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 337588465; Wed, 26 Aug 2009 07:43:16 +0000 (UTC) Date: Wed, 26 Aug 2009 08:43:00 +0100 From: Bruce Cran To: Mikolaj Golub Message-ID: <20090826084300.484c4b6e@gluon.draftnet> In-Reply-To: <86ws4tejt5.fsf@kopusha.onet> References: <86ws4tejt5.fsf@kopusha.onet> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.4; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Partial kvm dumps X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 07:59:33 -0000 On Mon, 24 Aug 2009 10:45:58 +0300 Mikolaj Golub wrote: > http://code.google.com/p/trociny/downloads/list > > I would like to hear what other people think about this. It looks > very useful for me. At least as a first step it would be nice to > extend KVM to work with partial dumps so the users could try this and > see if it turned out to be useful. Having recently been debugging core dump support in the base system utilities I spotted what looks like a bug in your code: the 'execfile' parameter to kvm_open or kvm_openfiles should be NULL if you want to use the kernel from the running system; some people may not be running a kernel from "/boot/kernel/kernel" by default. -- Bruce From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 08:53:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91624106568E; Wed, 26 Aug 2009 08:53:42 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6B13D8FC20; Wed, 26 Aug 2009 08:53:41 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA27442; Wed, 26 Aug 2009 11:53:38 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1] helo=edge.pp.kiev.ua) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1MgEGA-000NYu-Cm; Wed, 26 Aug 2009 11:53:38 +0300 Message-ID: <4A94F811.8020705@freebsd.org> Date: Wed, 26 Aug 2009 11:53:37 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090723) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> In-Reply-To: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: GA-MA780G-UD3H motherboard X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 08:53:42 -0000 on 25/08/2009 21:34 Sam Fourman Jr. said the following: >> Meanwhile, if you interested in any information about this motherboard - data >> dumps, outputs from tools, etc - please let me know, I will try my best to provide >> that. > > it would be interesting to see a dmesg as a starting point. Please see http://people.freebsd.org/~avg/ga-ma780g-ud3h/ Replying to the other email - I use amd64 arch. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 09:00:51 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E1C9106568E; Wed, 26 Aug 2009 09:00:51 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 7AD788FC26; Wed, 26 Aug 2009 09:00:50 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA27703; Wed, 26 Aug 2009 12:00:47 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1] helo=edge.pp.kiev.ua) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1MgEN4-000Na1-6K; Wed, 26 Aug 2009 12:00:46 +0300 Message-ID: <4A94F9BD.70907@freebsd.org> Date: Wed, 26 Aug 2009 12:00:45 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090723) MIME-Version: 1.0 To: kindman@amc-os.com References: <4A9412ED.6080309@freebsd.org> <4A94242B.7090806@freebsd.org> <604B96C6CF22447EACE5BD9719DDE1F5@kindman> In-Reply-To: <604B96C6CF22447EACE5BD9719DDE1F5@kindman> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org Subject: Re: AMD SB700 SMBus controller driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 09:00:51 -0000 on 26/08/2009 01:27 said the following: > Could you please forward me the patch to make it work in polling mode ? I'd > like to test it as I've been trying to make intpm work with a SB400 (which > should be quite the same as yours) but system hangs when I try to force > polling mode (didn't have the specs nor all the differences you just > presented). And btw, I didn't find any implementation using interrupt > neither but I'm ready to test your updated version. [what charset/encoding was your email?] Please see: http://people.freebsd.org/~avg/ga-ma780g-ud3h/intpm.diff The patch is work-in-progress and is not clean for this reason (style violations, experimental hacks) What the patch does: 1. redefine PCI_INTR_SMB_IRQ9 to 2 (bit 1) 2. disable writing to PCIR_INTLINE 3. add PCI id of my hardware 4. attempt to use IRQ mode with interrupt 20 - doesn't work 5. force polling mode - seems to work -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 12:00:53 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B08FD10656CF for ; Wed, 26 Aug 2009 12:00:53 +0000 (UTC) (envelope-from ivan.anyukov@googlemail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 2BDEB8FC3F for ; Wed, 26 Aug 2009 12:00:52 +0000 (UTC) Received: by bwz2 with SMTP id 2so57727bwz.43 for ; Wed, 26 Aug 2009 05:00:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=tJ6TYFQh0Gqevp3Pr2f/qo+SnYLBoHzxgGGV+9l2npQ=; b=v7z0LAV4sAasMOzvrwXtKjI1kbLzSX5FrR3YKI4kwqPrV9Yf6UD18KCOjME8A9TOIP 7q0qo0j55LQRrSbwwz7TENMgPfg8bm4+lS5gR3jeJ0ZeSylzcvMCBUVv++WzjlNg4RCY gIG+W3XpvP52M39qCxW6FLtrLS3Jif0zB4SKs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cqnc+dm9ZQuHJh6vsLoOrHinUnNuITY2zAZWA6KZCYdywTB+RRb4C8ZIiOtfCMdf6p Is0XADzBOvwgj0ctaXJlqk1eqtjqXfQfdZ6GDEUgQ7EjLYenje+0+U1H35oMnEgXn5Kh UFUZ8hZ3IXuZKsHa2BloDczDnUjj+QS4pua+Q= MIME-Version: 1.0 Received: by 10.223.7.90 with SMTP id c26mr5926791fac.73.1251286311186; Wed, 26 Aug 2009 04:31:51 -0700 (PDT) Date: Wed, 26 Aug 2009 13:31:51 +0200 Message-ID: <962bea8e0908260431j7f683cf4tcb3806cbcb723ae7@mail.gmail.com> From: ivan anyukov To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Wed, 26 Aug 2009 12:04:06 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: NMI running X with dual-monitor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 12:00:53 -0000 Hi guys, I'm running 7.2-STABLE on a Thinkpad T60. When connecting a second monitor to my docking station sometimes my FreeBSD freezes. kgdb on the vmcore-file says "non-maskable interrupt trap" Some details: X.Org 1.5.3 using the radeon-Driver I think the problem appears when moving xterms from the first to the second monitor (or back). The mouse cursor looks _very_ strange then and after some minutes the whole system freezes. Does anyone know about the problem? Is it a hardware-failure for sure? Thanks a lot! From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 13:56:53 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BB9C106568E for ; Wed, 26 Aug 2009 13:56:53 +0000 (UTC) (envelope-from bertwiley@gmail.com) Received: from mail-gx0-f227.google.com (mail-gx0-f227.google.com [209.85.217.227]) by mx1.freebsd.org (Postfix) with ESMTP id DC5588FC39 for ; Wed, 26 Aug 2009 13:56:52 +0000 (UTC) Received: by gxk27 with SMTP id 27so195478gxk.12 for ; Wed, 26 Aug 2009 06:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=3bz1XQgsKHbA7c7ceJzi284kyl/oGFEPYsZBHK5itwk=; b=FRLimwwDQxnkVgK2xCJGH6P7glIjvRqqFWL3J92oiUeyei8Gsb1JkblLr8Ozu8hyVH VkLGku57rWlY3XBHEaELHR3oWybsBnQU9DvyP5kzkcxHC0lA+IC63fa08UQ2oQPBsVTO XU31h2fhZL0g0AiE2lWklAm8a5m02bS/FGMXQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fgQ/2AJTs0dobtd3T9fiQ1vd/3ty/+OfXuYTMfucsUXlomDII2jnF/rSTnjd7jDMRP rZ5U7Xsx/fwVSSeAAJVFG9WNUFBT7kDXt3RFYoihPO5FFtPrcMPUAUgY3VfPZOToCg3A 3DPezSCkv0YxSdGHFGXnJesvn2IMMBqfKbhhc= MIME-Version: 1.0 Received: by 10.91.26.7 with SMTP id d7mr6088667agj.1.1251295010826; Wed, 26 Aug 2009 06:56:50 -0700 (PDT) Date: Wed, 26 Aug 2009 09:56:50 -0400 Message-ID: <9527461a0908260656w570f6cdha72e92b267e5354f@mail.gmail.com> From: bert wiley To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Need some help understanding a jail system call. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 13:56:53 -0000 Hello I found this code under a project called jailNG which has some system calls for doing jail stuff. Im still new to freebsd and im stumped on what this code is actually doing. In the source from the project there are few function calls that look like it creates and access the jail layer. Here is an example #define JAIL_CREATE 1 #define JAIL_DESTROY 2 #define JAIL_JOIN 3 extern char *environ[]; static void usage(void) { fprintf(stderr, "usage:\n"); fprintf(stderr, " jailctl create [jailname]\n"); fprintf(stderr, " jailctl destroy [jailname]\n"); fprintf(stderr, " jailctl join [jailname] [-c chrootpath] [path] " "[cmd] [args...]\n"); exit(-1); } static int jail_create(int argc, char *argv[]) { int error; if (argc < 2) usage(); error = syscall(375, JAIL_CREATE, argv[1]); if (error) perror("jailconf().create"); return (error); } No where in the code do i ever see any access to the jail.h type systems calls, so does the syscall(375, JAIL_CREATE, argv[1]); actually access the jail subsystem and create a jail? Here is the link i used to find this code http://www.watson.org/~robert/freebsd/jailng/ Any help on this question is appreciated thanks. From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 14:21:01 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D82E410656C3; Wed, 26 Aug 2009 14:21:01 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 97F718FC23; Wed, 26 Aug 2009 14:21:01 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id A01286D44C; Wed, 26 Aug 2009 14:21:00 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 96135844A3; Wed, 26 Aug 2009 16:20:59 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Tim Kientzle References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <200908251609.09302.j.mckeown@ru.ac.za> <4A9407D3.60006@freebsd.org> Date: Wed, 26 Aug 2009 16:20:59 +0200 Message-ID: <86hbvu64hg.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 14:21:01 -0000 Tim Kientzle writes: > The difference between "ps", "ps -w", and "ps -ww" is pretty > significant for Java, in particular. Java command lines > are typically enormous (thank you, CLASSPATH) which makes > "ps -ww" often more annoying than it's worth. Java command lines aren't necessarily enormous. If they are, it is because whoever invoked Java didn't know that it respects the CLASSPATH environment variable, and that setting -classpath on the command line f*s up the user's preferences (e.g. the user may want to replace a particular set of classes with an alternative implementation). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 14:23:16 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2DE2106568D; Wed, 26 Aug 2009 14:23:16 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 802268FC22; Wed, 26 Aug 2009 14:23:16 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 995B16D44E; Wed, 26 Aug 2009 14:23:15 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id D1D2D844A3; Wed, 26 Aug 2009 16:23:13 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ivan Radovanovic References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <4A94325D.6070201@FreeBSD.org> <4A9436A7.2020108@gmail.com> Date: Wed, 26 Aug 2009 16:23:13 +0200 In-Reply-To: <4A9436A7.2020108@gmail.com> (Ivan Radovanovic's message of "Tue, 25 Aug 2009 21:08:23 +0200") Message-ID: <86d46i64dq.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@FreeBSD.org, Doug Barton , Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 14:23:16 -0000 Ivan Radovanovic writes: > I think software should evolve to be better rather then to stick with > something done the wrong way, even that has been done maybe 30 years > ago - that is why behavior should be changed. It is never too late to > do the right thing ;-) Are you also going to rewrite 30 years' worth of scripts that expect ps(1) to have a -w option which behaves in a particular manner? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 14:34:10 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2B30106568E for ; Wed, 26 Aug 2009 14:34:10 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id B4F958FC24 for ; Wed, 26 Aug 2009 14:34:10 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id A99316D44C; Wed, 26 Aug 2009 14:34:09 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 8C49D844A3; Wed, 26 Aug 2009 16:34:09 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: bert wiley References: <9527461a0908260656w570f6cdha72e92b267e5354f@mail.gmail.com> Date: Wed, 26 Aug 2009 16:34:09 +0200 In-Reply-To: <9527461a0908260656w570f6cdha72e92b267e5354f@mail.gmail.com> (bert wiley's message of "Wed, 26 Aug 2009 09:56:50 -0400") Message-ID: <868wh663vi.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Need some help understanding a jail system call. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 14:34:11 -0000 bert wiley writes: > No where in the code do i ever see any access to the jail.h type systems > calls Because at that stage in the development process, the system calls in belong to the old implementation. > so does the syscall(375, JAIL_CREATE, argv[1]); actually access the > jail subsystem and create a jail? It calls the new system call, which at that stage hasn't been added to libc yet, because it would conflict with the existing system calls. > Here is the link i used to find this code > http://www.watson.org/~robert/freebsd/jailng/ You realize that this is eight years old, right? And that the jail infrastructure has been extensively modified since then, and is currently being rewritten again? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 14:44:08 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B8C1065882 for ; Wed, 26 Aug 2009 14:44:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 800308FC18 for ; Wed, 26 Aug 2009 14:44:07 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA06413 for ; Wed, 26 Aug 2009 17:44:06 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A954A35.4030207@icyb.net.ua> Date: Wed, 26 Aug 2009 17:44:05 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 14:44:08 -0000 Here is a question that I am afraid I know an answer for. I have some ECC capable hardware: 1) Athlon II with embedded memory controller that can do ECC 2) DRAM modules with ECC Assuming that ECC data lanes are connected between the two on motherboard, and given that BIOS doesn't perform any ECC setup (nor there is any option to control that) - would it be possible to turn on ECC from OS code? Or is it too late in the game already? -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 16:24:11 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF46E106568C for ; Wed, 26 Aug 2009 16:24:11 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 8B25D8FC27 for ; Wed, 26 Aug 2009 16:24:11 +0000 (UTC) Received: from OMTA19.westchester.pa.mail.comcast.net ([76.96.62.98]) by QMTA07.westchester.pa.mail.comcast.net with comcast id Yyr91c00227AodY574QBVG; Wed, 26 Aug 2009 16:24:11 +0000 Received: from daland.home ([24.34.211.11]) by OMTA19.westchester.pa.mail.comcast.net with comcast id Z4Tp1c0030FJTGg3f4U0l8; Wed, 26 Aug 2009 16:28:00 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MgLHz-0001CG-Go; Wed, 26 Aug 2009 12:23:59 -0400 From: Alex Goncharov To: Dag-Erling Smørgrav In-reply-to: <86hbvu64hg.fsf@ds4.des.no> (message from Dag-Erling Smørgrav on Wed, 26 Aug 2009 16:20:59 +0200) References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090825134447.GM2829@hoeg.nl> <200908251609.09302.j.mckeown@ru.ac.za> <4A9407D3.60006@freebsd.org> <86hbvu64hg.fsf@ds4.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: Sender: Alex Goncharov Date: Wed, 26 Aug 2009 12:23:59 -0400 Cc: freebsd-hackers@freebsd.org, kientzle@freebsd.org Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 16:24:12 -0000 ,--- You/Dag-Erling (Wed, 26 Aug 2009 16:20:59 +0200) ----* | Tim Kientzle writes: | > The difference between "ps", "ps -w", and "ps -ww" is pretty | > significant for Java, in particular. Java command lines | > are typically enormous (thank you, CLASSPATH) which makes | > "ps -ww" often more annoying than it's worth. | | Java command lines aren't necessarily enormous. If they are, it is | because whoever invoked Java didn't know that it respects the CLASSPATH | environment variable, and that setting -classpath on the command line | f*s up the user's preferences (e.g. the user may want to replace a | particular set of classes with an alternative implementation). Using either the `-classpath' option to `java' or `CLASSPATH' environment variable is a pretty obsolete practice (whoever does either these days, should stop and re-think, IMHO.) The deficiency of the above, in either variation, is the need to list every `jar' file used, which gets ugly with more than a few files. A persons who keeps up with modern Java will call it with one or several of the options: -Djava.ext.dirs -Djava.library.path -Djava.endorsed.dirs Java Virtual Machine will internally list the files in each of the directories (specified on the command line or default ones), saving a user the effort to mention them explicitly in `CLASSPATH'. This cuts on the length of the command line dramatically, but still `java' processes' command lines are typically enormously long: even the lists of the directories, with their absolute paths are significant; on top of it, `java' is usually invoked with a gazillion of options modifying JVM's runtime behaviour. It's a fact of life that for real-life applications, `java' command lines are *long* -- you can't change that by moving from `-classpath' to `CLASSPATH'. (This said, I am not in favor of modifying `ps' in the manner proposed, as my previous message indicated.) -- Alex -- alex-goncharov@comcast.net -- From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 19:03:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13F8B106568C for ; Wed, 26 Aug 2009 19:03:15 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from mail-yw0-f202.google.com (mail-yw0-f202.google.com [209.85.211.202]) by mx1.freebsd.org (Postfix) with ESMTP id C3FDE8FC2E for ; Wed, 26 Aug 2009 19:03:14 +0000 (UTC) Received: by ywh40 with SMTP id 40so542389ywh.14 for ; Wed, 26 Aug 2009 12:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=hwFgM8HBSHoFY98REzrJlmD5UGwPxY1m5PByh2+7C5w=; b=ZTrID4qiaouxGtCg78pDoG26/QEhbddZ+RZ6nm5t4bBNzWgAAkhlYkmsrHSLH8VHsh F7N38bVxkt2iDuU/tmK1n4UJGOADvTCgtpM6xBObVhzsSsO+1EsBzDW9CC2yTf/tIt/N Tqgp8PCfb6K3Yvg3v+bpoidRh66QJ0IYb1lGg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=fSADFWRzZuTYCOY6POA89A+uh3sc0idF5jIYFovz8IJuCnWhTkUE8m33oAHKkJh8vF m0siK+RTQNGAfIkCtAtWH5JEUK4XGc5G9FwuyMtTcX914ABYdQJ5faI3P4rS9oBWE+sc xPR/ak19O9GixvbP1bt3+iDBFLNSDDk12JHuA= MIME-Version: 1.0 Received: by 10.100.56.26 with SMTP id e26mr8159037ana.162.1251313393868; Wed, 26 Aug 2009 12:03:13 -0700 (PDT) Date: Wed, 26 Aug 2009 15:03:13 -0400 Message-ID: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> From: Linda Messerschmidt To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Intermittent system hangs on 7.2-RELEASE-p1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 19:03:15 -0000 I'm trying to troubleshoot an intermittent Apache performance problem, and I've narrowed it down using to what appears to be a brief whole-system hang that last from 0.5 - 3 seconds. They occur every few minutes. I took the rather extreme step of doing "ktrace -t cnisuwt -i -d -p 1" and then I waited for the hang. This is what I got: 54937 httpd 1251302859.375313 CALL shutdown(0x3,) 54937 httpd 1251302859.375333 RET shutdown 0 54937 httpd 1251302859.375348 CALL select(0x4,0xbfbfe92c,0,0,0xbfbfe9ac) 54937 httpd 1251302859.375363 CSW stop kernel 54937 httpd 1251302859.376402 CSW resume kernel 54937 httpd 1251302859.376439 RET select 1 54937 httpd 1251302859.376453 CALL read(0x3,0xbfbfe9b4,0x200) 54937 httpd 1251302859.376470 GIO fd 3 read 0 bytes 54937 httpd 1251302859.376482 RET read 0 54937 httpd 1251302859.376495 CALL close(0x3) 54937 httpd 1251302859.376511 RET close 0 54937 httpd 1251302859.376525 CALL sigaction(SIGUSR1,0xbfbfebb0,0xbfbfeb98) 54937 httpd 1251302859.376538 RET sigaction 0 54937 httpd 1251302859.376552 CALL munmap(0x282ff000,0x11) 54937 httpd 1251302859.376607 RET munmap 0 54937 httpd 1251302859.376633 CALL accept(0x11,0xbfbfebf0,0xbfbfec10) 54937 httpd 1251302859.376649 CSW stop kernel 796 svscan 1251302859.481064 CSW resume kernel 54937 httpd 1251302859.489374 CSW resume kernel 54937 httpd 1251302859.489391 STRU struct sockaddr { AF_INET, 172.17.0.143:61610 } 98229 httpd 1251302859.601850 CSW resume kernel 46517 httpd 1251302859.601900 CSW resume kernel 98202 httpd 1251302859.611661 CSW resume kernel 837 nrpe2 1251302859.622681 CSW resume kernel 54454 httpd 1251302859.655422 CSW resume kernel 54454 httpd 1251302859.655443 STRU struct sockaddr { AF_INET, 172.17.0.131:59011 } 7182 httpd 1251302859.722381 CSW resume kernel 98178 httpd 1251302859.722438 CSW resume kernel 858 gmond 1251302859.794996 CSW resume kernel 858 gmond 1251302859.794998 GIO fd 5 wrote 0 bytes 770 ntpd 1251302860.076501 CSW resume kernel 98346 httpd 1251302860.086261 CSW resume kernel 65277 httpd 1251302860.086300 CSW resume kernel 98514 httpd 1251302860.106849 CSW resume kernel 7191 httpd 1251302860.106894 CSW resume kernel 796 svscan 1251302861.403335 RET nanosleep 0 796 svscan 1251302861.403370 CALL wait4(0xffffffff,0xbfbfee18,WNOHANG,0) 796 svscan 1251302861.403405 RET wait4 0 54454 httpd 1251302861.403481 RET accept 3 98229 httpd 1251302861.403532 RET select 0 796 svscan 1251302861.403553 CALL stat(0x804a3bb,0xbfbfed6c) 858 gmond 1251302861.403601 GIO fd 5 read 20 bytes 54454 httpd 1251302861.403619 CSW stop user 46517 httpd 1251302861.403647 RET select 0 858 gmond 1251302861.403674 RET kevent 1 858 gmond 1251302861.403710 CALL socket(PF_INET,SOCK_DGRAM,IPPROTO_IP) 98202 httpd 1251302861.403714 RET select 0 858 gmond 1251302861.403752 RET socket 9 837 nrpe2 1251302861.403756 RET select 0 There is a gap between 1251302860.106894 and 1251302861.403335 of over one second, and the "effective gap" starts around 1251302859.376649 and thus lasts for about two seconds. This machine runs Apache and during this sample it was being hit every 0.1 seconds with a test request for a simple static file (in addition to production traffic). It is a 2-processor machine that is 85-95% idle; there's nothing in userspace that runs that long without yielding. According to systat, it handles 5000+ syscalls every second. But according to ktrace, nothing happens at all during the hang. This matches user experience. (The static file request, which usually completes in <0.01s suddenly takes 2 seconds as observed from the remote machine issuing the requests.) Here's the relevant snip from the httpd process handling that static file at the time of the hang: 54937 httpd 1251302859.376633 CALL accept(0x11,0xbfbfebf0,0xbfbfec10) 54937 httpd 1251302859.376649 CSW stop kernel 54937 httpd 1251302859.489374 CSW resume kernel 54937 httpd 1251302859.489391 STRU struct sockaddr { AF_INET, 172.17.0.143:61610 } 54937 httpd 1251302861.403862 RET accept 3 It's stuck in accept, but does *not* get context-switched away from during the delay. (The earlier context switch corresponds to the 0.1 seconds between requests; there is an Apache instance configured to handle just the test requests with one child process; that process has nothing else to do or block on.) I'll include some other processes below. I think it's weird that all these processes get context-switched-into before/during the hang, and I wonder if it's a clue. The kernel is obviously still running, since it wakes these processes up, but nothing is happening. That and the fact that it happens on multiple machines (though we've only tested this one) leads me away from suspecting the hardware. Are we out of a kernel resource or is something getting garbage collected / stuck / temporarily locked inside the kernel somewhere? This is a production server, so our debugging options are very limited. We also can't recreate the problem on a test server. So KTR and/or the kernel debugger are probably out. There's nothing in syslog or dmesg or on the console. Could anyone suggest away to gather more information about this, given our constraints? More samples: Here's an Apache "parent" process; its hang is in select(). The immediately following select() call demonstrates what the middle one should also have done: 98178 httpd 1251302858.703733 CALL select(0,0,0,0,0xbfbfed3c) 98178 httpd 1251302858.703789 CSW stop kernel 98178 httpd 1251302859.722438 CSW resume kernel 98178 httpd 1251302861.403908 RET select 0 98178 httpd 1251302861.404118 CALL gettimeofday(0xbfbfec58,0) 98178 httpd 1251302861.404453 RET gettimeofday 0 98178 httpd 1251302861.404478 CALL wait4(0xffffffff,0xbfbfed80,WNOHANG,0) 98178 httpd 1251302861.405288 RET wait4 0 98178 httpd 1251302861.405576 CALL select(0,0,0,0,0xbfbfed3c) 98178 httpd 1251302861.405603 CSW stop kernel 98178 httpd 1251302862.417549 CSW resume kernel 98178 httpd 1251302862.417581 RET select 0 Same behavior from nrpe2: 837 nrpe2 1251302859.107587 CALL select(0x5,0xbfbfe16c,0,0xbfbfe16c,0xbfbfe20c) 837 nrpe2 1251302859.107607 CSW stop kernel 837 nrpe2 1251302859.622681 CSW resume kernel 837 nrpe2 1251302861.403756 RET select 0 Here's a production Apache child process. Also hangs in accept(), but the delay does happen inside the context switch: 55062 httpd 1251302859.044661 CALL accept(0x12,0xbfbfec00,0xbfbfec20) 55062 httpd 1251302859.044681 CSW stop kernel 55062 httpd 1251302861.792647 CSW resume kernel 55062 httpd 1251302861.792662 STRU struct sockaddr { AF_INET, 172.17.0.131:59093 } 55062 httpd 1251302861.792880 RET accept 3 gmond hangs in kevent() on some kind of I/O: 858 gmond 1251302859.233805 CALL kevent(0x5,0,0,0x2833d960,0x2,0xbfbfe344) 858 gmond 1251302859.233820 CSW stop kernel 858 gmond 1251302859.794996 CSW resume kernel 858 gmond 1251302859.794998 GIO fd 5 wrote 0 bytes 858 gmond 1251302861.403601 GIO fd 5 read 20 bytes 858 gmond 1251302861.403674 RET kevent 1 svscan hangs in nanosleep(). It sleeps for 5 seconds, not 7. 796 svscan 1251302854.429189 CALL lseek(0x3,0,SEEK_SET,0) 796 svscan 1251302854.429269 RET lseek 0 796 svscan 1251302854.429346 CALL close(0x3) 796 svscan 1251302854.429709 RET close 0 796 svscan 1251302854.429894 CALL nanosleep(0xbfbfee18,0xbfbfee10) 796 svscan 1251302854.430033 CSW stop kernel 796 svscan 1251302859.481064 CSW resume kernel 796 svscan 1251302861.403335 RET nanosleep 0 796 svscan 1251302861.403370 CALL wait4(0xffffffff,0xbfbfee18,WNOHANG,0) 796 svscan 1251302861.403405 RET wait4 0 796 svscan 1251302861.403553 CALL stat(0x804a3bb,0xbfbfed6c) 796 svscan 1251302861.404027 NAMI "." ntpd shows the same behavior, except it wakes up by alarm. Again, the normal behavior (no gap between CSW and RET) is shown right after: 770 ntpd 1251302859.078305 CALL select(0x3b,0xbfbfed7c,0,0,0) 770 ntpd 1251302859.078312 CSW stop kernel 770 ntpd 1251302860.076501 CSW resume kernel 770 ntpd 1251302861.403952 RET select -1 errno 4 Interrupted system call 770 ntpd 1251302861.404168 PSIG SIGALRM caught handler=0x806ad90 mask=0x0 code=0x0 770 ntpd 1251302861.404191 CALL sigreturn(0xbfbfea50) 770 ntpd 1251302861.404553 RET sigreturn JUSTRETURN 770 ntpd 1251302861.404890 CALL select(0x3b,0xbfbfed7c,0,0,0) 770 ntpd 1251302861.405955 CSW stop kernel 770 ntpd 1251302862.077114 CSW resume kernel 770 ntpd 1251302862.077171 RET select -1 errno 4 Interrupted system call There were other processes running, mainly more httpds, but I went through each and every one of them and I don't see anything that I haven't already shown an example of. Thanks very much for any advice! From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 20:43:54 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 888BF106568B for ; Wed, 26 Aug 2009 20:43:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 59F0B8FC25 for ; Wed, 26 Aug 2009 20:43:54 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id ED01E46B58; Wed, 26 Aug 2009 16:43:53 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 495C68A02A; Wed, 26 Aug 2009 16:43:53 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 26 Aug 2009 16:42:59 -0400 User-Agent: KMail/1.9.7 References: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> In-Reply-To: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908261642.59419.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 26 Aug 2009 16:43:53 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Linda Messerschmidt Subject: Re: Intermittent system hangs on 7.2-RELEASE-p1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 20:43:54 -0000 On Wednesday 26 August 2009 3:03:13 pm Linda Messerschmidt wrote: > I'm trying to troubleshoot an intermittent Apache performance problem, > and I've narrowed it down using to what appears to be a brief > whole-system hang that last from 0.5 - 3 seconds. They occur every > few minutes. One thing to note is that ktrace only logs voluntary context switches (i.e. call to tsleep or waiting on a condition variable). It specifically does not log preemptions or blocking on a mutex, so in theory if your machine was livelocked temporarily that might explain this. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 21:16:59 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E42C106568F for ; Wed, 26 Aug 2009 21:16:59 +0000 (UTC) (envelope-from remodeler@alentogroup.org) Received: from courriel.marmotmail.com (courriel.marmotmail.com [85.17.36.172]) by mx1.freebsd.org (Postfix) with ESMTP id 3441D8FC25 for ; Wed, 26 Aug 2009 21:16:58 +0000 (UTC) Received: from bruce.epifora.com (localhost.local [127.0.0.1]) by courriel.marmotmail.com (Postfix) with ESMTP id 73B1F2395E3 for ; Thu, 27 Aug 2009 00:06:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 723494761F9 for ; Wed, 26 Aug 2009 17:07:18 -0400 (EDT) Received: from bruce.epifora.com ([127.0.0.1]) by localhost (bruce.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28105-08 for ; Wed, 26 Aug 2009 17:07:16 -0400 (EDT) Received: from alentogroup.org (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id A9B674761F8 for ; Wed, 26 Aug 2009 17:07:16 -0400 (EDT) From: "remodeler" To: freebsd-hackers@freebsd.org Date: Wed, 26 Aug 2009 17:07:16 -0400 Message-Id: <20090826204513.M28384@alentogroup.org> X-OriginatingIP: 127.0.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: MBR hack for serial console X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 21:16:59 -0000 I am hoping for input on a patch I want to apply to the MBR of a FreeBSD 8-BETA3 AMD64 server. I need a serial console on this server. The ASUS motherboard (amibios) has PCI and PCI-e expansion slots, and a Moschip MCS9820 UART (serial board) is installed at pci0:3:5:0. The amibios can be configured to do the plug-and-play enumeration, or this feature turned off, but there is no way to assign a particular i/o port to a PCI device in the BIOS, and I cannot get source for the BIOS to change this behavior. The serial board has a single Base Address Register at 10h in its pci configuration space. Whether the PCI bus is probed by the BIOS or FreeBSD, the UART BAR is assigned the i386 I/O port address of 0xe800. It must be COM1-COM4 (i.e. 0x3F8) to work in the boot sequence. I need access to the serial console before loader. I do not expect the hardware configuration to change so a hack is ok. My plan is to patch the MBR to override the serial card's BAR with 0x3F8. My reasoning is that the CPU is still in Real mode (allowing direct hardware access) until loader executes, and the serial console would work for the boot0 and boot2 calls to the terminal. I have experimented with using pciconf to change the BAR from a command line; curiously the command: pciconf -w pci0:3:5:0 16 1016 loads 0x3F9 into the serial card's PCI configuration space instead of 0x3F8, and I don't understand why. I've worked up this patch and hope someone can tell me why this would or wouldn't work: /usr/src/sys/boot/i386/mbr/mbr.s 41,57d40 < # Patch to reconfigure PCI UART's Base Address to COM1 < # I count 40 bytes in opcode < # < startcon: .set PCIADD_PORT,0xcf8 # Load pci config port addy < .set PCIDATA_PORT,0xcfc # Load pci data port addy < .set PCIADD,0x8003e810 # Load pci register identifier < .set PCIDATA,0x3f8 # Load pci register data < < pushad # save double registers < mov %ax,$PCIADD # put pci reg to access in ax < mov %dx,$PCIADD_PORT # put pci config port in dx < out %dx,%ax # send to cpu i/o space < mov %ax,$PCIDATA # put pci data in ax < mov %dx,$PCIDATA_PORT # put pci data port in dx < out %dx,%ax # send data to cpu i/o space < popad # pop saved registers < # 166,171c149,151 < # < # Instruction messages reduced to numbers, saves 60 bytes < # < msg_pt: .asciz "1" # "Invalid partition table" < msg_rd: .asciz "2" # "Error loading operating system" < msg_os: .asciz "3" # "Missing operating system" --- > msg_pt: .asciz "Invalid partition table" > msg_rd: .asciz "Error loading operating system" > msg_os: .asciz "Missing operating system" Thanks in advance for any help. I am not an assembly coder so am really uncertain about my patch. From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 21:36:58 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 053EE106568F for ; Wed, 26 Aug 2009 21:36:58 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id DB46E8FC30 for ; Wed, 26 Aug 2009 21:36:57 +0000 (UTC) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n7QLavo02287; Wed, 26 Aug 2009 14:36:57 -0700 (PDT) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n7QLavZ15046; Wed, 26 Aug 2009 14:36:57 -0700 (PDT) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Wed, 26 Aug 2009 14:36:57 -0700 (PDT) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: Linda Messerschmidt In-Reply-To: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> Message-ID: References: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Intermittent system hangs on 7.2-RELEASE-p1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 21:36:58 -0000 On Wed, 26 Aug 2009, Linda Messerschmidt wrote: > I'm trying to troubleshoot an intermittent Apache performance problem, > and I've narrowed it down using to what appears to be a brief > whole-system hang that last from 0.5 - 3 seconds. They occur every > few minutes. One thought would be to use "ps" to try to determine which process, if any, is charged with CPU time during the hang. If you could afford a little downtime, it would be worth seeing if the hang occurs in single-user mode (perhaps with a simple program that loops calling gettimeofday() and warns when the time between successive iterations is large). I once had a problem like this that I eventually traced to a power management problem. (Specifically, the machine had a modem, and would hang for a few seconds whenever the line would ring. It was apparently related to the Wake-On-Ring feature.) If I remember correctly, disabling ACPI made it go away. So that might be something to try, if rebooting is an option. What are the similarities and differences in hardware and software among the affected machines (you mentioned there were several)? -- Nate Eldredge neldredge@math.ucsd.edu From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 26 23:20:44 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9901D1065690 for ; Wed, 26 Aug 2009 23:20:44 +0000 (UTC) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.freebsd.org (Postfix) with ESMTP id 7B0178FC21 for ; Wed, 26 Aug 2009 23:20:44 +0000 (UTC) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.14.3/8.14.3) with ESMTP id n7QMraAn063684 for ; Wed, 26 Aug 2009 15:53:36 -0700 (PDT) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.14.3/8.14.3/Submit) id n7QMrauP063683 for hackers@freebsd.org; Wed, 26 Aug 2009 15:53:36 -0700 (PDT) (envelope-from steve) Message-Id: <200908262253.n7QMrauP063683@wattres.watt.com> In-Reply-To: <4A954A35.4030207@icyb.net.ua> From: steve@Watt.COM (Steve Watt) Organization: Watt Consultants, San Jose, CA, USA Date: Wed, 26 Aug 2009 15:53:36 -0700 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: hackers@freebsd.org X-Archived: 1251327216.828595188@wattres.Watt.COM X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (wattres.watt.com [127.0.0.1]); Wed, 26 Aug 2009 15:53:36 -0700 (PDT) Cc: Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 23:20:44 -0000 In <4A954A35.4030207@icyb.net.ua>, avg@icyb.net.ua wrote: > >Here is a question that I am afraid I know an answer for. >I have some ECC capable hardware: >1) Athlon II with embedded memory controller that can do ECC >2) DRAM modules with ECC >Assuming that ECC data lanes are connected between the two on motherboard, and >given that BIOS doesn't perform any ECC setup (nor there is any option to control >that) - would it be possible to turn on ECC from OS code? >Or is it too late in the game already? It's about 100 times easier to have the BIOS do this. First off, it's usually quite specific to the chip set exactly how to do it. Next, if ECC wasn't enabled previously, the ECC bytes will all be wrong, which means that you'll have to rewrite all of memory after you've turned it on. Oh, and you have to fetch the code that rewrites the ECC from the memory with incorrect ECC to do that. If the BIOS is broken to the extent that it doesn't enable ECC on a system that it should be available, whine at the vendor. -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.5" / 37N 20' 15.3" Internet: steve @ Watt.COM Whois: SW32-ARIN Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 07:09:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2B8106568B; Thu, 27 Aug 2009 07:09:15 +0000 (UTC) (envelope-from prvs=14836b82ff=brian@FreeBSD.org) Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id E81B68FC1C; Thu, 27 Aug 2009 07:09:14 +0000 (UTC) Received: from pd3ml1so-ssvc.prod.shaw.ca ([10.0.141.140]) by pd2mo1so-svcs.prod.shaw.ca with ESMTP; 27 Aug 2009 00:40:21 -0600 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=1 a=MJPcHhXccCG8eBs0us8XwA==:17 a=6I5d2MoRAAAA:8 a=MMwg4So0AAAA:8 a=rrxcYoe_TmSxUakYs3IA:9 a=W2Vh8_yiTJ6VnWxprLUA:7 a=rVTwtgZgkWwnu82VMncLQtreuDgA:4 a=SV7veod9ZcQA:10 a=WJ3hkfHDukgA:10 a=Q8kfNSWlL1dofc25vHwA:9 a=IMQyv7S60G0m8Sjpa4D7xI35sB8A:4 Received: from unknown (HELO store.lan.Awfulhak.org) ([70.79.162.198]) by pd3ml1so-dmz.prod.shaw.ca with ESMTP; 27 Aug 2009 00:40:20 -0600 Received: from store.lan.Awfulhak.org (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 2955CC440AB_A962A56B; Thu, 27 Aug 2009 06:40:22 +0000 (GMT) Received: from gw.Awfulhak.org (gw.lan.Awfulhak.org [172.16.0.1]) by store.lan.Awfulhak.org (Sophos Email Appliance) with ESMTP id B06CBC460F4_A962A51F; Thu, 27 Aug 2009 06:40:17 +0000 (GMT) Received: from dev.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5]) by gw.Awfulhak.org (8.14.3/8.14.3) with ESMTP id n7R6eFlZ097230; Wed, 26 Aug 2009 23:40:15 -0700 (PDT) (envelope-from brian@FreeBSD.org) Date: Wed, 26 Aug 2009 23:40:09 -0700 From: Brian Somers To: freebsd-hackers@FreeBSD.org Message-ID: <20090826234009.13b90734@dev.lan.Awfulhak.org> In-Reply-To: <20090825034054.2d57e733@dev.lan.Awfulhak.org> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.5; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/AXOUNzMX3Zufpwd.bjry.2J"; protocol="application/pgp-signature" Cc: Brian Somers , Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 07:09:15 -0000 --Sig_/AXOUNzMX3Zufpwd.bjry.2J Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 25 Aug 2009 03:40:54 -0700 Brian Somers wrote: > I recently closed bin/137647 and had second thoughts after Ivan (the > originator) challenged my reason for closing it. >=20 > The suggestion is that ps's -w switch is a strange artifact that can > be safely deprecated. ps goes to great lengths to implement width > limitations, and any time I've seen people not using -ww has either > been a mistake or doesn't matter. Using 'cut -c1-N' is also a great > way of limiting widths if people really want that... >=20 > I'd like to propose changing ps so that width limits are removed and > '-w' is deprecated - ignored for now with a note in the man page > saying that it will be removed in a future release. >=20 > Does anyone have any objections to doing this? I don't propose > merging this back into stable/8. To clarify, my proposal is to silently ignore the -w switch (any/all of the= m) and to remove the code that reads the terminal width and truncates some columns based on the result (or based on "132"). The pros: - ps's code becomes simpler. It was mentioned that the ps code is a minefield. This would remove a few mines. - ps IMHO has no business knowing about terminal widths (and where did the 132 column -w idea come from again?). Some programs such as iostat have similar (but way more broken) behaviour however whilst others such as ls do not. - We remove the sizing bugs (only some columns are truncation victims). The cons: - people with visual expectations would have to learn to use less -S or some similar tool. This breaks POLA. - Scripts may exist that depend on the behaviour without -w. Furthermore having to handle ps from both before and after such a change in one script can be painful. It was also suggested that rather than changing the behaviour of one flavour of ps it would be better to adopt an approach more like linux's or even implementing POSIXs suggestions. AFAIK the linux suggestion has been on the table for more time than I care to remember (wasn't Brett Glass going to provide a patch soon?). Although I haven't read the linux code, I'm pretty sure it's a scary place - perhaps this is the reason that we don't have those patches yet. Unless others have more to say on the subject, I think it's clear that the most popular vote is to do nothing. I think this is a shame as I find the pros more compelling than the cons, and I'm sure there are more than a few supporters out there on hackers@ that will stay silent. --=20 Brian Somers Don't _EVER_ lose your sense of humour ! --Sig_/AXOUNzMX3Zufpwd.bjry.2J Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iQCVAwUBSpYqTw7tvOdmanQhAQK5/wQAkuW3oq9q6IRChno5MdwFDKSUI33hj8R4 ZwffH/7SglEk8vQFnPk9awS3MqaHCQoFNxO1j+/qi7xiNE4yXXzQkFsaqkY8us1V 3CTYA9Tjrvx+J7LOQ8pDEtCwTYLvw0r/Y/e/wPhDP/iun3pziDSlu7Uvv/s7HuNM URCdiZzTCSk= =b6np -----END PGP SIGNATURE----- --Sig_/AXOUNzMX3Zufpwd.bjry.2J-- From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 07:18:18 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 734BF106568D for ; Thu, 27 Aug 2009 07:18:18 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outJ.internet-mail-service.net (outj.internet-mail-service.net [216.240.47.233]) by mx1.freebsd.org (Postfix) with ESMTP id 5844F8FC2F for ; Thu, 27 Aug 2009 07:18:18 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id DF5DFAE083; Thu, 27 Aug 2009 00:18:17 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 8A9D12D6011; Thu, 27 Aug 2009 00:18:17 -0700 (PDT) Message-ID: <4A963338.7080908@elischer.org> Date: Thu, 27 Aug 2009 00:18:16 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Brian Somers References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> In-Reply-To: <20090826234009.13b90734@dev.lan.Awfulhak.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 07:18:18 -0000 Brian Somers wrote: > On Tue, 25 Aug 2009 03:40:54 -0700 Brian Somers wrote: >> I recently closed bin/137647 and had second thoughts after Ivan (the >> originator) challenged my reason for closing it. >> >> The suggestion is that ps's -w switch is a strange artifact that can >> be safely deprecated. ps goes to great lengths to implement width >> limitations, and any time I've seen people not using -ww has either >> been a mistake or doesn't matter. Using 'cut -c1-N' is also a great >> way of limiting widths if people really want that... >> >> I'd like to propose changing ps so that width limits are removed and >> '-w' is deprecated - ignored for now with a note in the man page >> saying that it will be removed in a future release. >> >> Does anyone have any objections to doing this? I don't propose >> merging this back into stable/8. > > To clarify, my proposal is to silently ignore the -w switch (any/all of them) > and to remove the code that reads the terminal width and truncates some > columns based on the result (or based on "132"). > > The pros: > > - ps's code becomes simpler. It was mentioned that the ps code is > a minefield. This would remove a few mines. > - ps IMHO has no business knowing about terminal widths (and where > did the 132 column -w idea come from again?). back in the day terminals came in two widths... 80 and 132. the teletype printers were 132 and the few video terminals there were were 80. later some of the video terminals had a wide 132 mode you could switch to. Some programs such > as iostat have similar (but way more broken) behaviour however whilst > others such as ls do not. > - We remove the sizing bugs (only some columns are truncation victims). > > The cons: > > - people with visual expectations would have to learn to use less -S or some > similar tool. This breaks POLA. > - Scripts may exist that depend on the behaviour without -w. Furthermore > having to handle ps from both before and after such a change in one > script can be painful. > > It was also suggested that rather than changing the behaviour of one > flavour of ps it would be better to adopt an approach more like linux's > or even implementing POSIXs suggestions. AFAIK the linux suggestion > has been on the table for more time than I care to remember (wasn't > Brett Glass going to provide a patch soon?). Although I haven't read > the linux code, I'm pretty sure it's a scary place - perhaps this is the > reason that we don't have those patches yet. > > > Unless others have more to say on the subject, I think it's clear that > the most popular vote is to do nothing. I think this is a shame as I > find the pros more compelling than the cons, and I'm sure there are > more than a few supporters out there on hackers@ that will stay > silent. > From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 10:28:32 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C379D106564A; Thu, 27 Aug 2009 10:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 86C1A8FC41; Thu, 27 Aug 2009 10:28:32 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 42AD56D418; Thu, 27 Aug 2009 10:28:31 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 1C309844C4; Thu, 27 Aug 2009 12:28:31 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Brian Somers References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> Date: Thu, 27 Aug 2009 12:28:30 +0200 In-Reply-To: <20090826234009.13b90734@dev.lan.Awfulhak.org> (Brian Somers's message of "Wed, 26 Aug 2009 23:40:09 -0700") Message-ID: <86fxbd1rg1.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 10:28:32 -0000 Brian Somers writes: > To clarify, my proposal is to silently ignore the -w switch (any/all of t= hem) > and to remove the code that reads the terminal width and truncates some > columns based on the result (or based on "132"). > > The pros: > > - ps's code becomes simpler. It was mentioned that the ps code is > a minefield. This would remove a few mines. Frankly, the width limiting code is the least of ps's problems. > - ps IMHO has no business knowing about terminal widths (and where > did the 132 column -w idea come from again?). Some programs such > as iostat have similar (but way more broken) behaviour however whilst > others such as ls do not. Actually, ls does pretty much the same thing (use a different layout when run on a tty), and it's far from the only Unix utility to do so. Usually, the tty layout is "pretty" while the non-tty layout is easier to work with in scripts. > The cons: > [...] > - Scripts may exist that depend on the behaviour without -w. Furthermore > having to handle ps from both before and after such a change in one > script can be painful. Breaking existing scripts would be an *extremely* unwise and unpopular move. The only part of your proposal I support is removing the 132-column limit on 'ps -w' (which I believe would make the output from 'ps -w' identical to that from 'ps -ww') DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 10:29:13 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41105106568E; Thu, 27 Aug 2009 10:29:13 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id 16FB18FC48; Thu, 27 Aug 2009 10:29:13 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-240-232.hsd1.ms.comcast.net [75.65.240.232]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id EE58237B62C; Thu, 27 Aug 2009 05:12:04 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 179B261C41; Thu, 27 Aug 2009 05:12:04 -0500 (CDT) Date: Thu, 27 Aug 2009 05:12:04 -0500 From: "Matthew D. Fuller" To: Brian Somers Message-ID: <20090827101204.GI10667@over-yonder.net> References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090826234009.13b90734@dev.lan.Awfulhak.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.20-fullermd.4 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.2 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-hackers@FreeBSD.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 10:29:13 -0000 On Wed, Aug 26, 2009 at 11:40:09PM -0700 I heard the voice of Brian Somers, and lo! it spake thus: > > I think this is a shame as I find the pros more compelling than the > cons, and I'm sure there are more than a few supporters out there on > hackers@ that will stay silent. FWIW, I'm in favor of at least carefully examining whether the cons really disqualify the change. My uses of ps pretty well fall into three categories: 1) The times I use -ww 2) The times it doesn't matter whether I did or not 3) The times I wish I'd used -ww, sometimes way later in the game when a script *DOESN'T* do what it's supposed to because ps isn't actually giving me the command. Thanks, ps. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 10:36:38 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C55E1106568D; Thu, 27 Aug 2009 10:36:38 +0000 (UTC) (envelope-from rivanr@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 283968FC41; Thu, 27 Aug 2009 10:36:37 +0000 (UTC) Received: by fxm6 with SMTP id 6so796710fxm.43 for ; Thu, 27 Aug 2009 03:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EVk4wxfSrrdCPc9rumIl6lpIoqE8boq4VMJ0Q/rhACs=; b=N8oJA8ykcbjHVwW0GuKsAgNnBEqCl0nQE7TydKRovbDCQFapK+rc31CweET8MCrPLm FnamAbItw21hL88CPkTDx/3p85eAMuP3y3t6qrRVXiaHbxiKpcO6P6S9PpGuhr/CKWvV g5Mbtr/6E4gigufugn4uMVv+O6JtuQw7l91I0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Md0iz2vJkmQnHYl0egN7+opHHnkiYa53iMR802grMskyjYCtCiw7aoazG2GTwpaiOz 10mHh1OP0YY1SAjkI96qbzGjp7ne/YTE899sHBhS+VBdwLjEe4oa7Vp8XxkFQ6gvzoRX CNOdIEviZJ1Zrq6+DLBA5FW88KBWy1EDoqjcs= Received: by 10.102.149.23 with SMTP id w23mr4202954mud.38.1251369393499; Thu, 27 Aug 2009 03:36:33 -0700 (PDT) Received: from azdaja.softwarehood.com ([95.180.33.218]) by mx.google.com with ESMTPS id n7sm7262629mue.25.2009.08.27.03.36.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 Aug 2009 03:36:33 -0700 (PDT) Message-ID: <4A9661AF.3040800@gmail.com> Date: Thu, 27 Aug 2009 12:36:31 +0200 From: Ivan Radovanovic User-Agent: Thunderbird 2.0.0.22 (X11/20090708) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> <86fxbd1rg1.fsf@ds4.des.no> In-Reply-To: <86fxbd1rg1.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@FreeBSD.org, Brian Somers Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 10:36:38 -0000 Dag-Erling Smørgrav napisa: > Actually, ls does pretty much the same thing (use a different layout > when run on a tty), and it's far from the only Unix utility to do so. > Usually, the tty layout is "pretty" while the non-tty layout is easier > to work with in scripts. > Actually ls doesn't work the same - ls tries to format its output according to terminal but if it can't it won't just chop off any piece of information, and if you pipe ls into other command's input ls behaves as not running on tty - ps behaves in the opposite way in both cases From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 10:45:19 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90C3F106568B; Thu, 27 Aug 2009 10:45:19 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 526388FC46; Thu, 27 Aug 2009 10:45:19 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 5FE796D418; Thu, 27 Aug 2009 10:45:18 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 42F4A844C4; Thu, 27 Aug 2009 12:45:18 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Matthew D. Fuller" References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> <20090827101204.GI10667@over-yonder.net> Date: Thu, 27 Aug 2009 12:45:18 +0200 In-Reply-To: <20090827101204.GI10667@over-yonder.net> (Matthew D. Fuller's message of "Thu, 27 Aug 2009 05:12:04 -0500") Message-ID: <868wh51qo1.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@FreeBSD.org, Brian Somers , Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 10:45:19 -0000 "Matthew D. Fuller" writes: > FWIW, I'm in favor of at least carefully examining whether the cons > really disqualify the change. They do. Breaking scripts is not acceptable under any circumstances. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 05:35:25 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 058E4106568F; Thu, 27 Aug 2009 05:35:25 +0000 (UTC) (envelope-from erich@apsara.com.sg) Received: from babylon.webvis.net (babylon.webvis.net [202.157.163.226]) by mx1.freebsd.org (Postfix) with ESMTP id 0B44E8FC20; Thu, 27 Aug 2009 05:35:23 +0000 (UTC) Received: from [10.0.1.240] ([119.73.191.194]) by apsara.com.sg ; Thu, 27 Aug 2009 11:30:21 +0800 SGT From: Erich Dollansky Organization: apsara green technology pte ltd To: freebsd-hackers@freebsd.org Date: Thu, 27 Aug 2009 11:30:15 +0800 User-Agent: KMail/1.9.10 References: <200908262253.n7QMrauP063683@wattres.watt.com> In-Reply-To: <200908262253.n7QMrauP063683@wattres.watt.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908271130.18073.erich@apsara.com.sg> X-Mailman-Approved-At: Thu, 27 Aug 2009 11:14:59 +0000 Cc: Steve Watt , hackers@freebsd.org Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 05:35:25 -0000 Hi, On 27 August 2009 am 06:53:36 Steve Watt wrote: > In <4A954A35.4030207@icyb.net.ua>, avg@icyb.net.ua wrote: > >Assuming that ECC data lanes are connected between the two on > > motherboard, and given that BIOS doesn't perform any ECC > > setup (nor there is any option to control that) - would it be > > possible to turn on ECC from OS code? Or is it too late in > > the game already? > > It's about 100 times easier to have the BIOS do this. First > off, it's usually quite specific to the chip set exactly how to how should it be done at OS level at all when the OS is loaded into RAM? I do not thing that normal PC hardware is capable of handling this. Only code running in a ROM can do this. Erich From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 05:35:25 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 058E4106568F; Thu, 27 Aug 2009 05:35:25 +0000 (UTC) (envelope-from erich@apsara.com.sg) Received: from babylon.webvis.net (babylon.webvis.net [202.157.163.226]) by mx1.freebsd.org (Postfix) with ESMTP id 0B44E8FC20; Thu, 27 Aug 2009 05:35:23 +0000 (UTC) Received: from [10.0.1.240] ([119.73.191.194]) by apsara.com.sg ; Thu, 27 Aug 2009 11:30:21 +0800 SGT From: Erich Dollansky Organization: apsara green technology pte ltd To: freebsd-hackers@freebsd.org Date: Thu, 27 Aug 2009 11:30:15 +0800 User-Agent: KMail/1.9.10 References: <200908262253.n7QMrauP063683@wattres.watt.com> In-Reply-To: <200908262253.n7QMrauP063683@wattres.watt.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908271130.18073.erich@apsara.com.sg> X-Mailman-Approved-At: Thu, 27 Aug 2009 11:15:08 +0000 Cc: Steve Watt , hackers@freebsd.org Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 05:35:25 -0000 Hi, On 27 August 2009 am 06:53:36 Steve Watt wrote: > In <4A954A35.4030207@icyb.net.ua>, avg@icyb.net.ua wrote: > >Assuming that ECC data lanes are connected between the two on > > motherboard, and given that BIOS doesn't perform any ECC > > setup (nor there is any option to control that) - would it be > > possible to turn on ECC from OS code? Or is it too late in > > the game already? > > It's about 100 times easier to have the BIOS do this. First > off, it's usually quite specific to the chip set exactly how to how should it be done at OS level at all when the OS is loaded into RAM? I do not thing that normal PC hardware is capable of handling this. Only code running in a ROM can do this. Erich From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 11:42:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14102106568C; Thu, 27 Aug 2009 11:42:15 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.sonnenberger.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id BF6F88FC2D; Thu, 27 Aug 2009 11:42:14 +0000 (UTC) Received: from britannica.bec.de (www.sonnenberger.org [192.168.1.10]) by www.sonnenberger.org (Postfix) with ESMTP id 9B9E96676F; Thu, 27 Aug 2009 13:23:19 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id EF3251BDD0C; Thu, 27 Aug 2009 13:22:29 +0200 (CEST) Date: Thu, 27 Aug 2009 13:22:29 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20090827112229.GB14987@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <200908262253.n7QMrauP063683@wattres.watt.com> <200908271130.18073.erich@apsara.com.sg> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908271130.18073.erich@apsara.com.sg> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 11:42:15 -0000 On Thu, Aug 27, 2009 at 11:30:15AM +0800, Erich Dollansky wrote: > how should it be done at OS level at all when the OS is loaded > into RAM? Copy the kernel to the video RAM, jump to it, enable ECC, copy back. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 11:42:15 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14102106568C; Thu, 27 Aug 2009 11:42:15 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.sonnenberger.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id BF6F88FC2D; Thu, 27 Aug 2009 11:42:14 +0000 (UTC) Received: from britannica.bec.de (www.sonnenberger.org [192.168.1.10]) by www.sonnenberger.org (Postfix) with ESMTP id 9B9E96676F; Thu, 27 Aug 2009 13:23:19 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id EF3251BDD0C; Thu, 27 Aug 2009 13:22:29 +0200 (CEST) Date: Thu, 27 Aug 2009 13:22:29 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20090827112229.GB14987@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <200908262253.n7QMrauP063683@wattres.watt.com> <200908271130.18073.erich@apsara.com.sg> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908271130.18073.erich@apsara.com.sg> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 11:42:15 -0000 On Thu, Aug 27, 2009 at 11:30:15AM +0800, Erich Dollansky wrote: > how should it be done at OS level at all when the OS is loaded > into RAM? Copy the kernel to the video RAM, jump to it, enable ECC, copy back. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 12:28:32 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE880106568B for ; Thu, 27 Aug 2009 12:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id B2EFD8FC2C for ; Thu, 27 Aug 2009 12:28:32 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id C1D826D418 for ; Thu, 27 Aug 2009 12:28:31 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 9C31F844C4; Thu, 27 Aug 2009 14:28:31 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: freebsd-hackers@freebsd.org References: <200908262253.n7QMrauP063683@wattres.watt.com> <200908271130.18073.erich@apsara.com.sg> <20090827112229.GB14987@britannica.bec.de> Date: Thu, 27 Aug 2009 14:28:31 +0200 In-Reply-To: <20090827112229.GB14987@britannica.bec.de> (Joerg Sonnenberger's message of "Thu, 27 Aug 2009 13:22:29 +0200") Message-ID: <864ort1lw0.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 12:28:33 -0000 Joerg Sonnenberger writes: > Erich Dollansky writes: > > how should it be done at OS level at all when the OS is loaded=20 > > into RAM? > Copy the kernel to the video RAM, jump to it, enable ECC, copy back. Not just the kernel - you have to copy all the memory that is currently in use, including interrupt tables, the BIOS configuration space, shadow copies of various ROMs... The CPU will probably not look too kindly on having interrupt descriptors, segment descriptors, page tables etc. in memory accessed through the I/O controller instead of the memory controller. The machine might not even have video RAM! On systems that support ECC, I suspect that the BIOS enables it at the same time as it configures the memory controller, which is one of the very first things it does - literally within a few dozen (or perhaps a few hundred) instructions from CPU reset - using only CPU registers, ROM code, and configuration variables loaded from NVRAM. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 14:16:44 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92C4F106568B for ; Thu, 27 Aug 2009 14:16:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 659B28FC2C for ; Thu, 27 Aug 2009 14:16:44 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E1E0046B03; Thu, 27 Aug 2009 10:16:43 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 500DD8A02E; Thu, 27 Aug 2009 10:16:43 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Aug 2009 08:08:09 -0400 User-Agent: KMail/1.9.7 References: <20090826204513.M28384@alentogroup.org> In-Reply-To: <20090826204513.M28384@alentogroup.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908270808.09790.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 27 Aug 2009 10:16:43 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: remodeler Subject: Re: MBR hack for serial console X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 14:16:44 -0000 On Wednesday 26 August 2009 5:07:16 pm remodeler wrote: > I am hoping for input on a patch I want to apply to the MBR of a FreeBSD > 8-BETA3 AMD64 server. I need a serial console on this server. The ASUS > motherboard (amibios) has PCI and PCI-e expansion slots, and a Moschip MCS9820 > UART (serial board) is installed at pci0:3:5:0. The amibios can be configured > to do the plug-and-play enumeration, or this feature turned off, but there is > no way to assign a particular i/o port to a PCI device in the BIOS, and I > cannot get source for the BIOS to change this behavior. The serial board has a > single Base Address Register at 10h in its pci configuration space. Whether > the PCI bus is probed by the BIOS or FreeBSD, the UART BAR is assigned the > i386 I/O port address of 0xe800. It must be COM1-COM4 (i.e. 0x3F8) to work in > the boot sequence. I need access to the serial console before loader. Hmm, is 60 bytes enough to read the current value of the BAR instead and use that address? Writing 0x3f8 will not work if the BAR has a length > 8, though it sounds like that isn't the case. Still, if the device is behind a PCI-PCI bridge (which it probably is if it is on bus 3) you have the problem that 0x3f8 is probably not in the IO range decoded by the parent bridge. Given that I really think reading the current value and using that instead of 0x3f8 is probably more reliable. > I do not expect the hardware configuration to change so a hack is ok. My plan > is to patch the MBR to override the serial card's BAR with 0x3F8. My reasoning > is that the CPU is still in Real mode (allowing direct hardware access) until > loader executes, and the serial console would work for the boot0 and boot2 > calls to the terminal. I have experimented with using pciconf to change the > BAR from a command line; curiously the command: > > pciconf -w pci0:3:5:0 16 1016 > > loads 0x3F9 into the serial card's PCI configuration space instead of 0x3F8, > and I don't understand why. I've worked up this patch and hope someone can > tell me why this would or wouldn't work: You would read back 0x3f9 because the lower 3 bits of a BAR are various flags. bit 0 indicates if a BAR is for I/O (1) or memory (0) hence why you read back 0x3f8 | 0x1. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 17:45:28 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CF811065694 for ; Thu, 27 Aug 2009 17:45:28 +0000 (UTC) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.freebsd.org (Postfix) with ESMTP id 5D5AB8FC39 for ; Thu, 27 Aug 2009 17:45:28 +0000 (UTC) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.14.3/8.14.3) with ESMTP id n7RHjRSu036946 for ; Thu, 27 Aug 2009 10:45:27 -0700 (PDT) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.14.3/8.14.3/Submit) id n7RHjR7J036945 for hackers@freebsd.org; Thu, 27 Aug 2009 10:45:27 -0700 (PDT) (envelope-from steve) Message-Id: <200908271745.n7RHjR7J036945@wattres.watt.com> X-Newsgroups: local.freebsd-hackers In-Reply-To: <200908271130.18073.erich@apsara.com.sg> From: steve@Watt.COM (Steve Watt) References: <200908262253.n7QMrauP063683@wattres.watt.com> Organization: Watt Consultants, San Jose, CA, USA Date: Thu, 27 Aug 2009 10:45:27 -0700 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: hackers@freebsd.org X-Archived: 1251395127.824430372@wattres.Watt.COM X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (wattres.watt.com [127.0.0.1]); Thu, 27 Aug 2009 10:45:27 -0700 (PDT) Cc: Subject: Re: enable ECC in OS code? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 17:45:28 -0000 In <200908271130.18073.erich@apsara.com.sg>, erich@apsara.com.sg wrote: >Hi, > >On 27 August 2009 am 06:53:36 Steve Watt wrote: >> In <4A954A35.4030207@icyb.net.ua>, avg@icyb.net.ua wrote: >> >Assuming that ECC data lanes are connected between the two on >> > motherboard, and given that BIOS doesn't perform any ECC >> > setup (nor there is any option to control that) - would it be >> > possible to turn on ECC from OS code? Or is it too late in >> > the game already? >> >> It's about 100 times easier to have the BIOS do this. First >> off, it's usually quite specific to the chip set exactly how to > >how should it be done at OS level at all when the OS is loaded >into RAM? > >I do not thing that normal PC hardware is capable of handling >this. > >Only code running in a ROM can do this. Disable the ECC error reporting and copy memory back to itself? Again, quite controller-specific. That said, the BIOS should do it, and any that doesn't is broken. -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.5" / 37N 20' 15.3" Internet: steve @ Watt.COM Whois: SW32-ARIN Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 20:14:40 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AA37106568E for ; Thu, 27 Aug 2009 20:14:40 +0000 (UTC) (envelope-from linda.messerschmidt@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5578F8FC3D for ; Thu, 27 Aug 2009 20:14:40 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 3so311842qwe.7 for ; Thu, 27 Aug 2009 13:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=MOG30b9mAkpXtPXFXxkGxwMda0hctps7yuICHuU0QT4=; b=APeTYGJuPL52cvyCQ3iqVo5UrF32151okVvMROC3FQQxzWPUZX/GlkRWCmLAENmIAc qzwgQ2ksWs4hMBP+rW8YftO50VUUrbTy+oNsMnZhQrGK+YOae5uGntv19YdxEbLdh+HG jhzLhOnGVlOxlkOKTHgylX1ecMhfCGV8UBtbE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tIxHVpXHzZtP3pt1AaZGjUdjC8sV7l02/wopkuqCoX/FzzUtU3cP1wUFGy5F3mhcmN OA++xQCw/K+5s1trgieG4cqNAIHtz+PQ0zBkg5MVhG77WDsL11KrFNUT1UYnhhA1VSXR 4TrkcAP63ogBJszuxk5ScaqtjXAA8938g8CG8= MIME-Version: 1.0 Received: by 10.229.93.4 with SMTP id t4mr206829qcm.93.1251404079506; Thu, 27 Aug 2009 13:14:39 -0700 (PDT) In-Reply-To: <200908261642.59419.jhb@freebsd.org> References: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> <200908261642.59419.jhb@freebsd.org> Date: Thu, 27 Aug 2009 16:14:39 -0400 Message-ID: <237c27100908271314v28e6c710s8a278064333d1d20@mail.gmail.com> From: Linda Messerschmidt To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Intermittent system hangs on 7.2-RELEASE-p1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 20:14:40 -0000 On Wed, Aug 26, 2009 at 4:42 PM, John Baldwin wrote: > One thing to note is that ktrace only logs voluntary context switches (i.e. > call to tsleep or waiting on a condition variable). It specifically does not > log preemptions or blocking on a mutex, I was not aware, thanks. > so in theory if your machine was > livelocked temporarily that might explain this. How would we determine that? We are now able to reproduce this on a test machine, even after slipping in a 7.2-STABLE kernel with KTR enabled. So we have a lot more options now. Unfortunately, I don't really "get" KTR yet. It looks like it has relevant info, but I was unable to correlate its huge timestamps (e.g. 6795522404430562) to ktrace output times (e.g. 1251387606.225544) showing problem areas. What's my best bet from here? From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 27 20:20:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 773CC106568E for ; Thu, 27 Aug 2009 20:20:07 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id C95C18FC39 for ; Thu, 27 Aug 2009 20:20:06 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n7RKK0B3070882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Aug 2009 23:20:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n7RKK03q091570; Thu, 27 Aug 2009 23:20:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n7RKK0b6091569; Thu, 27 Aug 2009 23:20:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 27 Aug 2009 23:20:00 +0300 From: Kostik Belousov To: Linda Messerschmidt Message-ID: <20090827202000.GQ9623@deviant.kiev.zoral.com.ua> References: <237c27100908261203g7e771400o2d9603220d1f1e0b@mail.gmail.com> <200908261642.59419.jhb@freebsd.org> <237c27100908271314v28e6c710s8a278064333d1d20@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vgR9NaMwtk/oK4d5" Content-Disposition: inline In-Reply-To: <237c27100908271314v28e6c710s8a278064333d1d20@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Intermittent system hangs on 7.2-RELEASE-p1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 20:20:07 -0000 --vgR9NaMwtk/oK4d5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 27, 2009 at 04:14:39PM -0400, Linda Messerschmidt wrote: > On Wed, Aug 26, 2009 at 4:42 PM, John Baldwin wrote: > > One thing to note is that ktrace only logs voluntary context switches (= i.e. > > call to tsleep or waiting on a condition variable). It specifically do= es not > > log preemptions or blocking on a mutex, >=20 > I was not aware, thanks. >=20 > > so in theory if your machine was > > livelocked temporarily that might explain this. >=20 > How would we determine that? >=20 > We are now able to reproduce this on a test machine, even after > slipping in a 7.2-STABLE kernel with KTR enabled. So we have a lot > more options now. >=20 > Unfortunately, I don't really "get" KTR yet. It looks like it has > relevant info, but I was unable to correlate its huge timestamps (e.g. > 6795522404430562) to ktrace output times (e.g. 1251387606.225544) > showing problem areas. >=20 > What's my best bet from here? How much memory is installed ? --vgR9NaMwtk/oK4d5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkqW6nAACgkQC3+MBN1Mb4jSAwCgkAqNs76fjgjU8lxUzJkslk/e qmEAn3nPACrDtWMffwx47nUEAS1EtI7X =lY55 -----END PGP SIGNATURE----- --vgR9NaMwtk/oK4d5-- From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 28 07:33:29 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F60C1069A10 for ; Fri, 28 Aug 2009 07:33:29 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 93004900ED for ; Fri, 28 Aug 2009 01:45:02 +0000 (UTC) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n7S1iiML033503; Thu, 27 Aug 2009 18:44:44 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id zj6g6gykxyuxwu6vbnu4fx9nz2; Thu, 27 Aug 2009 18:44:44 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4A97368C.9000405@freebsd.org> Date: Thu, 27 Aug 2009 18:44:44 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16 MIME-Version: 1.0 To: Brian Somers References: <20090825034054.2d57e733@dev.lan.Awfulhak.org> <20090826234009.13b90734@dev.lan.Awfulhak.org> In-Reply-To: <20090826234009.13b90734@dev.lan.Awfulhak.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Ivan Radovanovic Subject: Re: Deprecating ps(1)s -w switch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:33:34 -0000 Brian Somers wrote: > > To clarify, my proposal is to silently ignore the -w switch (any/all of them) > and to remove the code that reads the terminal width and truncates some > columns based on the result (or based on "132"). If you're going to change something that, whether you agree with it or not, a lot of other code depends on, you may as well change the name at the same time and call it "myps". Tim From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 28 07:33:55 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ED0A1065A74 for ; Fri, 28 Aug 2009 07:33:55 +0000 (UTC) (envelope-from remodeler@alentogroup.org) Received: from courriel.marmotmail.com (courriel.marmotmail.com [85.17.36.172]) by mx1.freebsd.org (Postfix) with ESMTP id 9E75190256 for ; Fri, 28 Aug 2009 03:25:16 +0000 (UTC) Received: from bruce.epifora.com (localhost.local [127.0.0.1]) by courriel.marmotmail.com (Postfix) with ESMTP id 47DCF239625 for ; Fri, 28 Aug 2009 06:35:12 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 2C9AD4761F9 for ; Thu, 27 Aug 2009 23:36:11 -0400 (EDT) Received: from bruce.epifora.com ([127.0.0.1]) by localhost (bruce.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29974-10 for ; Thu, 27 Aug 2009 23:36:09 -0400 (EDT) Received: from alentogroup.org (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 308A94761F8 for ; Thu, 27 Aug 2009 23:36:09 -0400 (EDT) From: "remodeler" To: freebsd-hackers@freebsd.org Date: Thu, 27 Aug 2009 23:36:09 -0400 Message-Id: <20090828033609.M34898@alentogroup.org> In-Reply-To: <200908270808.09790.jhb@freebsd.org> References: <20090826204513.M28384@alentogroup.org> <200908270808.09790.jhb@freebsd.org> X-OriginatingIP: 127.0.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Re: MBR hack for serial console X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:33:56 -0000 This is in response to John Baldwin's response to my question about using a non-legacy IO port for an i386 serial console. I notice that src/sys/boot/i386/boot0/boot0.S uses a call to the PC BIOS int 14h routine to access the serial console, if SIO is defined. I believe SIO is defined if make.conf specifies a port for BOOT_COMCONSOLE_PORT (though I'm probably wrong), in which case the boot0 executable would be made from src/sys/boot/i386/boot0/boot0sio when recompiling the boot blocks with: # cd /sys/boot # make clean # make # make install The 14h pc bios routine is definitely limited to 0x3F8, 0x2F8, 0x3E8, or 0x2E8 because it is called with the DX register set to specify COM1-COM4 (dx set to 0, 1, 2, or 3). boot2 looks like I might be able to specify the 0xe800 address for the serial console. src/sys/boot/i386/boot2/sio.S has this definition: .set SIO_PRT,SIOPRT but I am not sure where SIOPRT is set. I don't see if in any makefile. I would guess it is being set by BOOT_COMCONSOLE_PORT also? > if the device is behind a PCI-PCI bridge (which it probably is > if it is on bus 3) you have the problem that 0x3f8 is probably not > in the IO range decoded by the parent bridge The device is behind a bridge: pcib0 --> pci0 --> pcib3 --> pci3, but AMD doesn't have a data sheet available on the 'net to tell me what IO range is decoded by the parent bridge (750SB southbridge chip). I also notice in the PCI specification this ("I/O Space Address Decoding for Legacy Devices"): A function that supports a PC legacy function (IDE, VGA, etc.) is allowed to claim those addresses associated with the specific function when the I/O Space (see Figure 6-2) [the configuration space's Command Register layout, bit 0] enable bit is set. These addresses are not requested using a Base Address register but are assigned by initialization software. If a device identifies itself as a legacy function (class code), the initialization software grants the device permission to claim the I/O legacy addresses by setting the device’s I/O Space enable bit. > read the current value of the BAR instead and use that address? If I can set the serial console to a non-legacy port in boot2, that would be ideal. I don't think the boot0 routine would cause problems; it is just looking for keystrokes AFAIK. In this approach, I would guess it would make sense to read the value and set SIOPRT to it in boot2? I think from this point on, the serial console calls use sio.S, and these functions (sio_init, etc.) access the hardware directly with assembler out commands rather than using the PC BIOS routines like boot0. Would something as simple as: .set SIO_PRT,0xe800 in src/sys/boot/i386/boot2/sio.S work? If it does, I can develop code to read and set it to the current port instead of hard-coding it. Thanks again for your help. From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 28 13:44:29 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75B16106566C for ; Fri, 28 Aug 2009 13:44:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 30A508FC23 for ; Fri, 28 Aug 2009 13:44:29 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BB94C46B09; Fri, 28 Aug 2009 09:44:28 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A48548A02B; Fri, 28 Aug 2009 09:44:27 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 28 Aug 2009 08:32:19 -0400 User-Agent: KMail/1.9.7 References: <20090826204513.M28384@alentogroup.org> <200908270808.09790.jhb@freebsd.org> <20090828033609.M34898@alentogroup.org> In-Reply-To: <20090828033609.M34898@alentogroup.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200908280832.19782.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 28 Aug 2009 09:44:27 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: remodeler Subject: Re: MBR hack for serial console X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 13:44:29 -0000 On Thursday 27 August 2009 11:36:09 pm remodeler wrote: > This is in response to John Baldwin's response to my question about using= a > non-legacy IO port for an i386 serial console. >=20 > I notice that src/sys/boot/i386/boot0/boot0.S uses a call to the PC BIOS = int > 14h routine to access the serial console, if SIO is defined. I believe SI= O is > defined if make.conf specifies a port for BOOT_COMCONSOLE_PORT (though I'm > probably wrong), in which case the boot0 executable would be made from > src/sys/boot/i386/boot0/boot0sio when recompiling the boot blocks with: >=20 > # cd /sys/boot > # make clean > # make > # make install >=20 > The 14h pc bios routine is definitely limited to 0x3F8, 0x2F8, 0x3E8, or = 0x2E8 > because it is called with the DX register set to specify COM1-COM4 (dx se= t to > 0, 1, 2, or 3). That's probably true that the BIOS routines likely do not handle a serial p= ort in an add-on card. However, just setting the I/O address to 03xf8 may not = make the BIOS routines work either since the BIOS may know that there isn't a CO= M1 on the motherboard so it may just fail I/O w/o trying. > boot2 looks like I might be able to specify the 0xe800 address for the se= rial > console. src/sys/boot/i386/boot2/sio.S has this definition: .set > SIO_PRT,SIOPRT but I am not sure where SIOPRT is set. I don't see if in a= ny > makefile. I would guess it is being set by BOOT_COMCONSOLE_PORT also? Correct. It's set via 'CFLAGS' in boot2's Makefile. > > if the device is behind a PCI-PCI bridge (which it probably is=20 > > if it is on bus 3) you have the problem that 0x3f8 is probably not > > in the IO range decoded by the parent bridge >=20 > The device is behind a bridge: pcib0 --> pci0 --> pcib3 --> pci3, but AMD > doesn't have a data sheet available on the 'net to tell me what IO range = is > decoded by the parent bridge (750SB southbridge chip). A verbose dmesg will tell you as it isn't a fixed range but it assigned by = the BIOS just like a BAR. > I also notice in the PCI specification this ("I/O Space Address Decoding = for > Legacy Devices"): >=20 > A function that supports a PC legacy function (IDE, VGA, etc.) is allowed= to > claim those addresses associated with the specific function when the I/O = Space > (see Figure 6-2) [the configuration space's Command Register layout, bit = 0] > enable bit is set. >=20 > These addresses are not requested using a Base Address register but are > assigned by initialization software. If a device identifies itself as a l= egacy > function (class code), the initialization software grants the device > permission to claim the I/O legacy addresses by setting the device=92s I/= O Space > enable bit. Note the 'not requested using a BAR' part of the quote. :-/ The way these transactions are handled by PCI-PCI bridges is there is a bit that effectiv= ely instructs the bridge to claim legacy I/O or VGA ranges. However, the PCI-I= SA/LPC bridge device probably is already setup that way so that I/O accesses to th= e RTC, keyboard controller, etc. all work. > > read the current value of the BAR instead and use that address? >=20 > If I can set the serial console to a non-legacy port in boot2, that would= be > ideal. I don't think the boot0 routine would cause problems; it is just > looking for keystrokes AFAIK. In this approach, I would guess it would ma= ke > sense to read the value and set SIOPRT to it in boot2? I think from this = point > on, the serial console calls use sio.S, and these functions (sio_init, et= c.) > access the hardware directly with assembler out commands rather than usin= g the > PC BIOS routines like boot0. Would something as simple as: >=20 > .set SIO_PRT,0xe800 >=20 > in src/sys/boot/i386/boot2/sio.S work? If it does, I can develop code to = read > and set it to the current port instead of hard-coding it. Yes, I would try that. You can also just do 'BOOT_COMCONSOLE_PORT=3D0xe800= ' to see if that will work as a test w/o having to modify any of the boot2 code directly. =2D-=20 John Baldwin