From owner-freebsd-arch@FreeBSD.ORG Sun Aug 8 15:12:20 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF6F816A4CE; Sun, 8 Aug 2004 15:12:20 +0000 (GMT) Received: from grosbein.pp.ru (grgw.svzserv.kemerovo.su [213.184.64.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABB343D3F; Sun, 8 Aug 2004 15:12:19 +0000 (GMT) (envelope-from eugen@grosbein.pp.ru) Received: from grosbein.pp.ru (eugen@localhost [127.0.0.1]) by grosbein.pp.ru (8.12.11/8.12.11) with ESMTP id i78FCI77009865; Sun, 8 Aug 2004 23:12:18 +0800 (KRAST) (envelope-from eugen@grosbein.pp.ru) Received: (from eugen@localhost) by grosbein.pp.ru (8.12.11/8.12.11/Submit) id i78FCIXB009864; Sun, 8 Aug 2004 23:12:18 +0800 (KRAST) (envelope-from eugen) Date: Sun, 8 Aug 2004 23:12:18 +0800 From: Eugene Grosbein To: bug-followup@freebsd.org Message-ID: <20040808151218.GA9847@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: arch@freebsd.org cc: stable@freebsd.org cc: re@freebsd.org Subject: Re: bin/58951: Some problems with 4.9-RELEASE installation using comconsole X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 15:12:20 -0000 Hi! Is there anyone interested in fixing 4.x-RELEASE serial console installation? Eugene From owner-freebsd-arch@FreeBSD.ORG Sun Aug 8 15:25:11 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E68E16A4CE; Sun, 8 Aug 2004 15:25:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE46E43D45; Sun, 8 Aug 2004 15:25:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 7DA771FF9A6; Sun, 8 Aug 2004 17:25:07 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 7B7321FF92F; Sun, 8 Aug 2004 17:25:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 4846415665; Sun, 8 Aug 2004 15:21:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 4595A15329; Sun, 8 Aug 2004 15:21:41 +0000 (UTC) Date: Sun, 8 Aug 2004 15:21:41 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD arch mailing list Subject: NO_YP_LIBC patch - please test/review X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 15:25:11 -0000 Hi, I am looking for more tests and reviews of the NO_YP_LIBC patch. You can find the latest version to test on http://sources.zabbadoz.net/freebsd/patchset/10039-no-yp-libc.diff You will need to apply the whole patch in order to successfully build a world with NO_YP_LIBC=yes in make.conf and thus be able to also test the changes. Mostly things like bind, sendmail, amd, etc. that still get build will need testing. If there are any problems or if it works for you or of you have further additions please let me know. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-arch@FreeBSD.ORG Sun Aug 8 20:26:02 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC82716A4CE for ; Sun, 8 Aug 2004 20:26:02 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3738443D1F for ; Sun, 8 Aug 2004 20:26:02 +0000 (GMT) (envelope-from stormbind@gmail.com) Received: by mproxy.gmail.com with SMTP id 75so85136rnl for ; Sun, 08 Aug 2004 13:25:57 -0700 (PDT) Received: by 10.38.181.43 with SMTP id d43mr342048rnf; Sun, 08 Aug 2004 13:25:57 -0700 (PDT) Message-ID: Date: Sun, 8 Aug 2004 21:25:57 +0100 From: Glen Stormbind To: freebsd-arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Seeking information on the frame buffer X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 20:26:02 -0000 Hi people, I'm looking to create a display system but I'm stuck before beginning. I know pretty much what I'm hoping to create, and have the design concept mapped out, but it will be my first low-level project and I don't know diddly-squat about frame buffers :( Soooo... can someone please point me in the right direction to getting started with the frame buffer? Thanks for your time! --Glen :) From owner-freebsd-arch@FreeBSD.ORG Sun Aug 8 22:38:36 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 716F416A4CE for ; Sun, 8 Aug 2004 22:38:36 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4566A43D2F for ; Sun, 8 Aug 2004 22:38:36 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 16956 invoked from network); 8 Aug 2004 22:38:35 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Aug 2004 22:38:35 -0000 Received: from hydrogen.funkthat.com (dapatm@localhost.funkthat.com [127.0.0.1])i78McZuU041164; Sun, 8 Aug 2004 15:38:35 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i78McYvD041163; Sun, 8 Aug 2004 15:38:34 -0700 (PDT) Date: Sun, 8 Aug 2004 15:38:34 -0700 From: John-Mark Gurney To: Glen Stormbind Message-ID: <20040808223834.GD991@funkthat.com> Mail-Followup-To: Glen Stormbind , freebsd-arch@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-arch@freebsd.org Subject: Re: Seeking information on the frame buffer X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 22:38:36 -0000 Glen Stormbind wrote this message on Sun, Aug 08, 2004 at 21:25 +0100: > I'm looking to create a display system but I'm stuck before beginning. > > I know pretty much what I'm hoping to create, and have the design > concept mapped out, but it will be my first low-level project and I > don't know diddly-squat about frame buffers :( > > Soooo... can someone please point me in the right direction to getting > started with the frame buffer? Thanks for your time! If you want a raw frame buffer, take a look at svgalib... It has calls that will get you the linear mapped frame buffer for most svga cards on i386... If you're looking for other platforms, that might be a bit more complicated... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arch@FreeBSD.ORG Mon Aug 9 18:44:18 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A020816A4D3 for ; Mon, 9 Aug 2004 18:44:18 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B5EF43D54 for ; Mon, 9 Aug 2004 18:44:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 17366 invoked from network); 9 Aug 2004 18:44:18 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 9 Aug 2004 18:44:17 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i79IiDtH076097; Mon, 9 Aug 2004 14:44:14 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-arch@FreeBSD.org Date: Mon, 9 Aug 2004 10:21:54 -0400 User-Agent: KMail/1.6 References: <20040807153543.34382.qmail@web14828.mail.yahoo.com> In-Reply-To: <20040807153543.34382.qmail@web14828.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408091021.55568.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Rostislav Krasny Subject: Re: again question about "IRQ 2 problem" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 18:44:18 -0000 On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > --- John Baldwin wrote: > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c Please let > > me know if it is not, thanks! > > Thank you very much! The "IRQ 2 problem" is fixed now and that device > (ed1) is working. Excellent. > > The only strange thing is what I see in 'dmesg -a' output after booting > in verbose mode (the first "adv1:..." line): Given the number of adv1 lines, it sounds like the adv(4) driver probably has a bug of some sort leading to those error messages. I wouldn't worry about those though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Mon Aug 9 18:44:26 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06D5E16A4CE for ; Mon, 9 Aug 2004 18:44:26 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CEE043D48 for ; Mon, 9 Aug 2004 18:44:25 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1787 invoked from network); 9 Aug 2004 18:44:25 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 9 Aug 2004 18:44:24 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i79IiDtI076097; Mon, 9 Aug 2004 14:44:16 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-arch@FreeBSD.org, John-Mark Gurney Date: Mon, 9 Aug 2004 10:26:35 -0400 User-Agent: KMail/1.6 References: <20040806224316.GB991@funkthat.com> In-Reply-To: <20040806224316.GB991@funkthat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408091026.35755.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: valid dup lock logic for witness X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 18:44:26 -0000 On Friday 06 August 2004 06:43 pm, John-Mark Gurney wrote: > I have been working on kqueue, and to support kq in kq, I need to obtain > two kq locks (both of the same type) at the same time. Normally this can > cause a deadlock, but using a proper lock ordering strategy, it can be > avoided. In the kq case, I chose to aquire a kq global lock before > acquiring multiple kq locks. (In the proc case, jhb said you aquire > the child's before the parents.) > > Mutexs have the flag MTX_DUPOK that notify witness that duplicate locks > are ok, but this can hide other problems (and in fact would have in my > testing). > > I have created a patch that lets you inform witness the a duplicate lock > is valid as long as you hold another lock. The only run time change is > that when a duplicate lock is found, it will run through another table > to verify it's ok before printing out the back trace. > > Anyone have objections to this? As I said on IRC, my objection to this is that there are numerous ways of acquiring duplicate locks in a valid fashion. For kq there is a global lock around such cases. For proc locks child processes are locked before parents. The problem is that there is not a single way of doing this, so if you want WITNESS to check all of these, you will have to add lots of special case one-off hacks to WITNESS making it even more obtuse and slow. Perhaps something that might be feasible is to provide some sort of way for other parts of the kernel to register a duplicate check function for a given lock type. This would let you keep the code doing the duplicate check closer to the code using the locks for one thing and would avoid adding N hacks to witness for the various different dup lock checks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Mon Aug 9 20:06:08 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F0BD16A4F9 for ; Mon, 9 Aug 2004 20:06:08 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 399EB43D53 for ; Mon, 9 Aug 2004 20:06:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 12884 invoked from network); 9 Aug 2004 20:06:08 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 9 Aug 2004 20:06:07 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i79K5krc076764; Mon, 9 Aug 2004 16:06:04 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Rostislav Krasny Date: Mon, 9 Aug 2004 16:04:33 -0400 User-Agent: KMail/1.6 References: <20040807153543.34382.qmail@web14828.mail.yahoo.com> In-Reply-To: <20040807153543.34382.qmail@web14828.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408091604.33984.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: gibbs@FreeBSD.org cc: freebsd-arch@FreeBSD.org Subject: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 20:06:08 -0000 On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > --- John Baldwin wrote: > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c Please let > > me know if it is not, thanks! > > Thank you very much! The "IRQ 2 problem" is fixed now and that device > (ed1) is working. > > The only strange thing is what I see in 'dmesg -a' output after booting > in verbose mode (the first "adv1:..." line): Try this patch to the adv(4) driver to see if your messages go away: Index: dev/advansys/adv_isa.c =================================================================== RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v retrieving revision 1.26 diff -u -r1.26 adv_isa.c --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 @@ -117,6 +117,12 @@ struct resource *iores, *irqres; /* + * We don't know of any PnP ID's for these cards. + */ + if (isa_get_logicalid(dev) != 0) + return (ENXIO); + + /* * Default to scanning all possible device locations. */ port_index = 0; Whoever maintains adv(4) (gibbs@?) might want to look at adding proper PnP support if there are any known ISA PnP IDs for the PnP adv(4) cards. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 02:22:20 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6BB316A4CE for ; Tue, 10 Aug 2004 02:22:20 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D76A43D3F for ; Tue, 10 Aug 2004 02:22:20 +0000 (GMT) (envelope-from jekyllhy@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i7A2MKro001765 for ; Mon, 9 Aug 2004 19:22:20 -0700 (PDT) Received: from [150.46.156.117] ([150.46.156.117]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id i7A2MHLv029328 for ; Mon, 9 Aug 2004 19:22:19 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <17EADF32-EA74-11D8-B537-000D93C4B248@mac.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-arch@FreeBSD.org From: huang yong Date: Tue, 10 Aug 2004 11:22:14 +0900 X-Mailer: Apple Mail (2.618) Subject: can i use freebsd on my mac g5 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 02:22:20 -0000 Dear sir, Would you like to tell me that can I use freebsd on my mac g5. Thanks for your time. sincerely, huang yong From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 08:27:20 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 025B316A4CE; Tue, 10 Aug 2004 08:27:20 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A195E43D3F; Tue, 10 Aug 2004 08:27:17 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.12.10/8.12.10) with ESMTP id i7A8RGNf002675; Tue, 10 Aug 2004 10:27:16 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.12.11/8.12.11) with ESMTP id i7A8RNL5012847; Tue, 10 Aug 2004 10:27:23 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.12.11/8.12.11/Submit) id i7A8RNcG012846; Tue, 10 Aug 2004 10:27:23 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 10 Aug 2004 10:27:23 +0200 From: Francois Tigeot To: "Bjoern A. Zeeb" Message-ID: <20040810082723.GA8692@aoi.wolfpond.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: FreeBSD arch mailing list cc: FreeBSD current mailing list Subject: Re: NO_YP_LIBC patch - please test/review X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 08:27:20 -0000 On Sun, Aug 08, 2004 at 03:21:41PM +0000, Bjoern A. Zeeb wrote: > > I am looking for more tests and reviews of the NO_YP_LIBC patch. > > You can find the latest version to test on > http://sources.zabbadoz.net/freebsd/patchset/10039-no-yp-libc.diff > > You will need to apply the whole patch in order to successfully build > a world with > NO_YP_LIBC=yes > in make.conf and thus be able to also test the changes. > Mostly things like bind, sendmail, amd, etc. that still get build will > need testing. I installed it on an i386 workstation. So far so good. If there are no problems with it in a few days I will try it on an amd64/sendmail server. -- Francois Tigeot From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 11:27:44 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0B2616A4CE for ; Tue, 10 Aug 2004 11:27:44 +0000 (GMT) Received: from web53505.mail.yahoo.com (web53505.mail.yahoo.com [206.190.37.66]) by mx1.FreeBSD.org (Postfix) with SMTP id 58DD043D5F for ; Tue, 10 Aug 2004 11:27:44 +0000 (GMT) (envelope-from jm_tallet@yahoo.com) Message-ID: <20040810112743.5796.qmail@web53505.mail.yahoo.com> Received: from [81.50.183.72] by web53505.mail.yahoo.com via HTTP; Tue, 10 Aug 2004 04:27:43 PDT Date: Tue, 10 Aug 2004 04:27:43 -0700 (PDT) From: jean-marc tallet To: re-pc98@FreeBSD.org, freebsd-ppc@FreeBSD.org, freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Which platform? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 11:27:44 -0000 Hi, I have a typical pc where I run windows and wish to install FreeBSD. Which platform should I choose? My processor is x86 family 6 model 4. Sincerely, JM _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 11:31:50 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2E0B16A4CF for ; Tue, 10 Aug 2004 11:31:50 +0000 (GMT) Received: from web14103.mail.yahoo.com (web14103.mail.yahoo.com [216.136.172.133]) by mx1.FreeBSD.org (Postfix) with SMTP id 398DD43D55 for ; Tue, 10 Aug 2004 11:31:50 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040810113150.56178.qmail@web14103.mail.yahoo.com> Received: from [194.248.174.58] by web14103.mail.yahoo.com via HTTP; Tue, 10 Aug 2004 13:31:50 CEST Date: Tue, 10 Aug 2004 13:31:50 +0200 (CEST) From: =?iso-8859-1?q?Claus=20Guttesen?= To: jean-marc tallet , re-pc98@FreeBSD.org, freebsd-ppc@FreeBSD.org, freebsd-arch@FreeBSD.org In-Reply-To: <20040810112743.5796.qmail@web53505.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Which platform? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 11:31:50 -0000 > I have a typical pc where I run windows and wish to > install FreeBSD. Which platform should I choose? > My processor is x86 family 6 model 4. Try the i386-port. regards Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 11:31:50 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFC4916A4D0 for ; Tue, 10 Aug 2004 11:31:50 +0000 (GMT) Received: from web53510.mail.yahoo.com (web53510.mail.yahoo.com [206.190.37.71]) by mx1.FreeBSD.org (Postfix) with SMTP id 4107F43D5C for ; Tue, 10 Aug 2004 11:31:50 +0000 (GMT) (envelope-from jm_tallet@yahoo.com) Message-ID: <20040810113149.5498.qmail@web53510.mail.yahoo.com> Received: from [81.50.183.72] by web53510.mail.yahoo.com via HTTP; Tue, 10 Aug 2004 04:31:49 PDT Date: Tue, 10 Aug 2004 04:31:49 -0700 (PDT) From: jean-marc tallet To: re-pc98@FreeBSD.org, freebsd-ppc@FreeBSD.org, freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Which architecture X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 11:31:50 -0000 Hi, I have a typical pc where I run windows and wish to install FreeBSD. Which platform should I choose? My processor is x86 family 6 model 4. Sorry also I wanted to know which architecture to pick up on the mirror site, between pc98 and i386! Sincerely, JM __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 00:27:32 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 081FA16A4CF for ; Wed, 11 Aug 2004 00:27:32 +0000 (GMT) Received: from web14826.mail.yahoo.com (web14826.mail.yahoo.com [216.136.225.197]) by mx1.FreeBSD.org (Postfix) with SMTP id CDC7043D2F for ; Wed, 11 Aug 2004 00:27:31 +0000 (GMT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20040811002731.46210.qmail@web14826.mail.yahoo.com> Received: from [212.143.154.227] by web14826.mail.yahoo.com via HTTP; Tue, 10 Aug 2004 17:27:31 PDT Date: Tue, 10 Aug 2004 17:27:31 -0700 (PDT) From: Rostislav Krasny To: John Baldwin In-Reply-To: <200408091604.33984.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: gibbs@FreeBSD.org cc: freebsd-arch@FreeBSD.org Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 00:27:32 -0000 --- John Baldwin wrote: > On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > > --- John Baldwin wrote: > > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c Please > > > let me know if it is not, thanks! > > > > Thank you very much! The "IRQ 2 problem" is fixed now and that > > device (ed1) is working. > > > > The only strange thing is what I see in 'dmesg -a' output after > > booting in verbose mode (the first "adv1:..." line): > > Try this patch to the adv(4) driver to see if your messages go away: > > Index: dev/advansys/adv_isa.c > =================================================================== > RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v > retrieving revision 1.26 > diff -u -r1.26 adv_isa.c > --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 > +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 > @@ -117,6 +117,12 @@ > struct resource *iores, *irqres; > > /* > + * We don't know of any PnP ID's for these cards. > + */ > + if (isa_get_logicalid(dev) != 0) > + return (ENXIO); > + > + /* > * Default to scanning all possible device locations. > */ > port_index = 0; After patching the "adv_isa.c" file and rebuilding the GENERIC kernel those messages went away. Previously posted chunk of the 'dmesg -a' output looks so now: isa_probe_children: probing PnP devices ed1: at port 0x200-0x21f irq 5 on isa0 ed1: [GIANT-LOCKED] ed1: bpf attached ed1: Ethernet address: 00:00:21:82:25:03 type NE2000 (16 bit) unknown: can't assign resources (port) unknown: at port 0x60 on isa0 unknown: failed to probe at port 0x61 on isa0 unknown: can't assign resources (port) unknown: at port 0x4d0-0x4d1 on isa0 unknown: can't assign resources (port) unknown: at port 0x208-0x20f on isa0 unknown: can't assign resources (port) unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources (port) unknown: at port 0x3f2-0x3f5 on isa0 unknown: can't assign resources (port) unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources (port) unknown: at port 0x2f8-0x2ff on isa0 Device configuration finished. procfs registered P.S. What are these "unknown: ..." messages? I don't have so many PnP devices. And my speaker (port 0x61) is working properly. I even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse -p -e -w 23 I am a 5.2-CURRENT, test me.' :-) __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 02:27:54 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 910BA16A4CE; Wed, 11 Aug 2004 02:27:54 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E03943D3F; Wed, 11 Aug 2004 02:27:54 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i7B2Rrn2023321; Tue, 10 Aug 2004 21:27:53 -0500 (CDT) (envelope-from dan) Date: Tue, 10 Aug 2004 21:27:53 -0500 From: Dan Nelson To: Rostislav Krasny Message-ID: <20040811022753.GD6474@dan.emsphone.com> References: <200408091604.33984.jhb@FreeBSD.org> <20040811002731.46210.qmail@web14826.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040811002731.46210.qmail@web14826.mail.yahoo.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-arch@freebsd.org Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 02:27:54 -0000 In the last episode (Aug 10), Rostislav Krasny said: > unknown: can't assign resources (port) > unknown: at port 0x60 on isa0 > unknown: failed to probe at port 0x61 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x4d0-0x4d1 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x208-0x20f on isa0 > unknown: can't assign resources (port) > unknown: at port 0x3f8-0x3ff on isa0 > unknown: can't assign resources (port) > unknown: at port 0x3f2-0x3f5 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x378-0x37f on isa0 > unknown: can't assign resources (port) > unknown: at port 0x2f8-0x2ff on isa0 > > P.S. What are these "unknown: ..." messages? I don't have so > many PnP devices. And my speaker (port 0x61) is working properly. I > even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse -p -e > -w 23 I am a 5.2-CURRENT, test me.' :-) PNP* devices are standard motherboard resources, like the keyboard (PNP0303) and serial port (PNP0501). There's a table at http://www.plasma-online.de/english/identify/serial/pnp_id_pnp.html that lists a lot of them. My -current kernel correctly matches these up to known devices, though: $ devinfo -v | grep PNP0303 atkbdc0 pnpinfo _HID=PNP0303 _UID=0 at handle=\_SB_.PCI0.ISA_.KBC_ -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 11:04:05 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7425916A4CE for ; Wed, 11 Aug 2004 11:04:05 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB48543D4C for ; Wed, 11 Aug 2004 11:04:04 +0000 (GMT) (envelope-from stormbind@gmail.com) Received: by mproxy.gmail.com with SMTP id 75so170218rnl for ; Wed, 11 Aug 2004 04:04:04 -0700 (PDT) Received: by 10.38.181.54 with SMTP id d54mr303187rnf; Wed, 11 Aug 2004 04:04:04 -0700 (PDT) Message-ID: Date: Wed, 11 Aug 2004 12:04:04 +0100 From: Glen Stormbind To: freebsd-arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Really stupid X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 11:04:05 -0000 I appologise in advance for posting this really stupid question -- but I can't for the life of me navigate the FreeBSD site to find the sources. I have tried several times and just seem to be going in circles. Where can I download the (i386) source code? Again. Sorry. --Glen From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 11:12:42 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B77B316A4CE for ; Wed, 11 Aug 2004 11:12:42 +0000 (GMT) Received: from web90008.mail.scd.yahoo.com (web90008.mail.scd.yahoo.com [66.218.94.66]) by mx1.FreeBSD.org (Postfix) with SMTP id 9457043D2D for ; Wed, 11 Aug 2004 11:12:42 +0000 (GMT) (envelope-from yousef_ourabi@yahoo.com) Message-ID: <20040811111242.9391.qmail@web90008.mail.scd.yahoo.com> Received: from [67.180.39.195] by web90008.mail.scd.yahoo.com via HTTP; Wed, 11 Aug 2004 04:12:42 PDT Date: Wed, 11 Aug 2004 04:12:42 -0700 (PDT) From: Yousef Ourabi To: freebsd-arch@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Really stupid X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 11:12:42 -0000 Glen, If you installed the source distribution during the install the full source code would be under the /usr/src tree. If not simply sync via cvsup as if you were going to do an update, and that will place the source in /usr/src. Here are fairly detaied instructions on how to cvsup, part of Dru Lavignes FreeBSD series on onlamp.com http://www.onlamp.com/pub/a/bsd/2002/09/05/FreeBSD_Basics.html Good Luck. Best, Yousef --- Glen Stormbind wrote: > I appologise in advance for posting this really > stupid question -- but > I can't for the life of me navigate the FreeBSD site > to find the > sources. I have tried several times and just seem to > be going in > circles. > > Where can I download the (i386) source code? > > Again. Sorry. > > --Glen > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to > "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-arch@FreeBSD.ORG Tue Aug 10 16:55:58 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C7616A4CE; Tue, 10 Aug 2004 16:55:58 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A5A43D41; Tue, 10 Aug 2004 16:55:57 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id DDBB372DF2; Tue, 10 Aug 2004 09:55:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id D88BA72DB5; Tue, 10 Aug 2004 09:55:57 -0700 (PDT) Date: Tue, 10 Aug 2004 09:55:57 -0700 (PDT) From: Doug White To: huang yong In-Reply-To: <17EADF32-EA74-11D8-B537-000D93C4B248@mac.com> Message-ID: <20040810095436.I88160@carver.gumbysoft.com> References: <17EADF32-EA74-11D8-B537-000D93C4B248@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 11 Aug 2004 12:19:47 +0000 cc: freebsd-powerpc@freebsd.org Subject: Re: can i use freebsd on my mac g5 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 16:55:58 -0000 Note: The correct list to ask this on would be either questions@freebsd.org or powerpc@freebsd.org. I'm setting the followup to powerpc here. On Tue, 10 Aug 2004, huang yong wrote: > Dear sir, > Would you like to tell me that can I use freebsd on my mac g5. > Thanks for your time. Not at this time. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 16:07:22 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDF6616A4CE for ; Wed, 11 Aug 2004 16:07:22 +0000 (GMT) Received: from north-zone.net (wh1.north-zone.net [65.110.60.200]) by mx1.FreeBSD.org (Postfix) with SMTP id CEDE743D46 for ; Wed, 11 Aug 2004 16:07:17 +0000 (GMT) (envelope-from nicobn@quebecbsd.org) Received: (qmail 10572 invoked by uid 80); 11 Aug 2004 16:07:42 -0000 Received: from 69.70.227.33 (SquirrelMail authenticated user nicobn@quebecbsd.org) by webmail.north-zone.net with HTTP; Wed, 11 Aug 2004 16:07:42 -0000 (GMT) Message-ID: <3622.69.70.227.33.1092240462.squirrel@webmail.north-zone.net> In-Reply-To: References: Date: Wed, 11 Aug 2004 16:07:42 -0000 (GMT) From: Nicolas =?iso-8859-1?Q?B=E9rard_Nault?= To: "Glen Stormbind" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: freebsd-arch@freebsd.org Subject: Re: Really stupid X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: nicobn@quebecbsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 16:07:22 -0000 Glen Stormbind said: > I appologise in advance for posting this really stupid question -- but > I can't for the life of me navigate the FreeBSD site to find the > sources. I have tried several times and just seem to be going in > circles. > > Where can I download the (i386) source code? You can download the sources using cvs or cvsup. More information on cvsup can be found here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html. Also, the sources are available as a distribution package in /stand/sysinstall. Finally, ftpx.freebsd.org/pub/FreeBSD/releases/i386/[RELEASE] probably has what you need. -- Nicolas Bérard Nault (nicobn@quebecbsd.org) http://staff.xeatech.net/nicobn PGP public key: 0x64159509 From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 16:52:03 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2607A16A4CF for ; Wed, 11 Aug 2004 16:52:03 +0000 (GMT) Received: from web14822.mail.yahoo.com (web14822.mail.yahoo.com [216.136.225.172]) by mx1.FreeBSD.org (Postfix) with SMTP id CE61743D45 for ; Wed, 11 Aug 2004 16:52:02 +0000 (GMT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20040811165202.51422.qmail@web14822.mail.yahoo.com> Received: from [212.143.154.227] by web14822.mail.yahoo.com via HTTP; Wed, 11 Aug 2004 09:52:02 PDT Date: Wed, 11 Aug 2004 09:52:02 -0700 (PDT) From: Rostislav Krasny To: Dan Nelson In-Reply-To: <20040811022753.GD6474@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-arch@freebsd.org Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 16:52:03 -0000 --- Dan Nelson wrote: > In the last episode (Aug 10), Rostislav Krasny said: > > unknown: can't assign resources (port) > > unknown: at port 0x60 on isa0 > > unknown: failed to probe at port 0x61 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x4d0-0x4d1 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x208-0x20f on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x3f8-0x3ff on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x3f2-0x3f5 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x378-0x37f on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x2f8-0x2ff on isa0 > > > > P.S. What are these "unknown: ..." messages? I don't have > > so many PnP devices. And my speaker (port 0x61) is working > > properly. I even can run 'kldload -v /boot/kernel/speaker.ko' and > > then 'morse -p -e -w 23 I am a 5.2-CURRENT, test me.' :-) > > PNP* devices are standard motherboard resources, like the keyboard > (PNP0303) and serial port (PNP0501). There's a table at > http://www.plasma-online.de/english/identify/serial/pnp_id_pnp.html > that lists a lot of them. My -current kernel correctly matches these > up to known devices, though: > > $ devinfo -v | grep PNP0303 > atkbdc0 pnpinfo _HID=PNP0303 _UID=0 at handle=\_SB_.PCI0.ISA_.KBC_ After a little googling I've found that PNPXXXX strings are "Microsoft PnP Device Identification Codes". According to http://www.mclibrary.edu.mn/itbooks/repair_pcs/Chapter_35.pdf all devices in PnP compatable system should have such a code: ==== start of citation ==== For the PC to recognize and configure a PnP device, each and every device must be able to identify itself and its resource requirements to the system—even motherboard busses and devices must be able to identify themselves. Identification is accomplished through a seven-character code. Each manufacturer is assigned a three-character prefix, the following character identifies the device type, and the remaining three characters identify the particular device. For example, the PnP code PNP0907 identifies a “Western Digital VGA” device adapter. Microsoft reserves the code “PNP” for itself, but other manufacturers are assigned their own codes (e.g., Creative Labs uses the “CTL” prefix). The advantage of Microsoft’s prefixes is that they are “generic,” and you can usually identify a device adequately by utilizing the Microsoft generic equivalent. ===== end of citation ===== In my system the output of 'devinfo -v | grep PNP0303' is nothing. But output of 'devinfo -v | grep pnpinfo' is as following: # devinfo -v | grep pnpinfo hostb0 pnpinfo vendor=0x8086 device=0x7100 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=0 isab0 pnpinfo vendor=0x8086 device=0x7110 subvendor=0x0000 subdevice=0x0000 class=0x060100 at slot=7 function=0 atapci0 pnpinfo vendor=0x8086 device=0x7111 subvendor=0x0000 subdevice=0x0000 class=0x010180 at slot=7 function=1 uhci0 pnpinfo vendor=0x8086 device=0x7112 subvendor=0x0000 subdevice=0x0000 class=0x0c0300 at slot=7 function=2 piix0 pnpinfo vendor=0x8086 device=0x7113 subvendor=0x0000 subdevice=0x0000 class=0x068000 at slot=7 function=3 xl0 pnpinfo vendor=0x10b7 device=0x9200 subvendor=0x10b7 subdevice=0x1000 class=0x020000 at slot=17 function=0 unknown pnpinfo vendor=0x1002 device=0x4755 subvendor=0x1002 subdevice=0x4755 class=0x030000 at slot=19 function=0 What is the prospective behaviour of FreeBSD 5.2-CURRENT with those PNP* devices like PNP0303 and PNP0800? This is an old Pentium MMX 200MHz, based on Intel 430TX chipset, system. BTW I think I've found a bug in devinfo(8). Try following scenario on your system: 1. log in as a root and make sure that 'speaker.ko' isn't loaded automatically during boot 2. run 'kldload -v /boot/kernel/speaker.ko' 3. run 'kldunload speaker' 4. run devinfo -v After the last step I've got following on the console: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc17429b7 fault code = supervisor read, page not present instruction pointer = 0x8:0xc06597f0 stack pointer = 0x10:0x857da18 frame pointer = 0x10:0x857da24 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 492 (devinfo) [thread 100059] Stopped at strlcpy+0x1c: movb 0(%edx),%al db> trace strlcpy(c857da60,c17429b7,20) at strlcpy+0x1c sysctl_devices(c084d9c0,c857dc90,2,c857dc08,c084d9c0) at sysctl_devices()+0xb8 sysctl_root(0,c857dc84,5,c857dc08,c146e580) at sysctl_root()+0x11b userland_sysctl(c146e580,c857dc84,5,bfbfeaf0,bfbfea50) at userland_sysctl()+0xec __sysctl(c146e580,c857dd14,6,9,292) at __sysctl()+0x71 syscall(2f,2f,2f,5,bfbfea50) at syscall()+0x217 Xint80_syscall() at Xint80_syscall()+0x1f --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x280c3723, esp = 0xbfbfe9dc, ebp = 0xbfbfea18 --- db> __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 19:05:32 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA46316A4E6 for ; Wed, 11 Aug 2004 19:05:31 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CF5443D53 for ; Wed, 11 Aug 2004 19:05:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 15866 invoked from network); 11 Aug 2004 19:05:06 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 11 Aug 2004 19:05:05 -0000 Received: from [10.50.41.91] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i7BJ516R093561; Wed, 11 Aug 2004 15:05:02 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-arch@FreeBSD.org Date: Wed, 11 Aug 2004 11:11:35 -0400 User-Agent: KMail/1.6.2 References: <20040811002731.46210.qmail@web14826.mail.yahoo.com> In-Reply-To: <20040811002731.46210.qmail@web14826.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408111111.35564.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: gibbs@FreeBSD.org cc: Rostislav Krasny Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 19:05:32 -0000 On Tuesday 10 August 2004 08:27 pm, Rostislav Krasny wrote: > --- John Baldwin wrote: > > On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > > > --- John Baldwin wrote: > > > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c Please > > > > let me know if it is not, thanks! > > > > > > Thank you very much! The "IRQ 2 problem" is fixed now and that > > > device (ed1) is working. > > > > > > The only strange thing is what I see in 'dmesg -a' output after > > > booting in verbose mode (the first "adv1:..." line): > > > > Try this patch to the adv(4) driver to see if your messages go away: > > > > Index: dev/advansys/adv_isa.c > > =================================================================== > > RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v > > retrieving revision 1.26 > > diff -u -r1.26 adv_isa.c > > --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 > > +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 > > @@ -117,6 +117,12 @@ > > struct resource *iores, *irqres; > > > > /* > > + * We don't know of any PnP ID's for these cards. > > + */ > > + if (isa_get_logicalid(dev) != 0) > > + return (ENXIO); > > + > > + /* > > * Default to scanning all possible device locations. > > */ > > port_index = 0; > > After patching the "adv_isa.c" file and rebuilding the GENERIC kernel > those messages went away. Previously posted chunk of the 'dmesg -a' > output looks so now: > > isa_probe_children: probing PnP devices > ed1: at port 0x200-0x21f irq 5 on isa0 > ed1: [GIANT-LOCKED] > ed1: bpf attached > ed1: Ethernet address: 00:00:21:82:25:03 > type NE2000 (16 bit) > unknown: can't assign resources (port) > unknown: at port 0x60 on isa0 > unknown: failed to probe at port 0x61 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x4d0-0x4d1 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x208-0x20f on isa0 > unknown: can't assign resources (port) > unknown: at port 0x3f8-0x3ff on isa0 > unknown: can't assign resources (port) > unknown: at port 0x3f2-0x3f5 on isa0 > unknown: can't assign resources (port) > unknown: at port 0x378-0x37f on isa0 > unknown: can't assign resources (port) > unknown: at port 0x2f8-0x2ff on isa0 > Device configuration finished. > procfs registered > > > P.S. What are these "unknown: ..." messages? I don't have so > many PnP devices. And my speaker (port 0x61) is working properly. I > even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse -p -e > -w 23 I am a 5.2-CURRENT, test me.' :-) They are PnPBIOS entries for things like the ISA timers, AT 8259A PICs, and the speaker. FreeBSD doesn't currently use the PnPBIOS device entries to attach to these devices. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-arch@FreeBSD.ORG Wed Aug 11 21:12:42 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB1D916A4CE for ; Wed, 11 Aug 2004 21:12:41 +0000 (GMT) Received: from web14828.mail.yahoo.com (web14828.mail.yahoo.com [216.136.225.230]) by mx1.FreeBSD.org (Postfix) with SMTP id BB38F43D2F for ; Wed, 11 Aug 2004 21:12:41 +0000 (GMT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20040811211241.17442.qmail@web14828.mail.yahoo.com> Received: from [212.143.154.227] by web14828.mail.yahoo.com via HTTP; Wed, 11 Aug 2004 14:12:41 PDT Date: Wed, 11 Aug 2004 14:12:41 -0700 (PDT) From: Rostislav Krasny To: John Baldwin , freebsd-arch@FreeBSD.org In-Reply-To: <200408111111.35564.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: gibbs@FreeBSD.org cc: Rostislav Krasny Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 21:12:42 -0000 --- John Baldwin wrote: > On Tuesday 10 August 2004 08:27 pm, Rostislav Krasny wrote: > > --- John Baldwin wrote: > > > On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > > > > --- John Baldwin wrote: > > > > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c > Please > > > > > let me know if it is not, thanks! > > > > > > > > Thank you very much! The "IRQ 2 problem" is fixed now and that > > > > device (ed1) is working. > > > > > > > > The only strange thing is what I see in 'dmesg -a' output after > > > > booting in verbose mode (the first "adv1:..." line): > > > > > > Try this patch to the adv(4) driver to see if your messages go > away: > > > > > > Index: dev/advansys/adv_isa.c > > > > =================================================================== > > > RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v > > > retrieving revision 1.26 > > > diff -u -r1.26 adv_isa.c > > > --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 > > > +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 > > > @@ -117,6 +117,12 @@ > > > struct resource *iores, *irqres; > > > > > > /* > > > + * We don't know of any PnP ID's for these cards. > > > + */ > > > + if (isa_get_logicalid(dev) != 0) > > > + return (ENXIO); > > > + > > > + /* > > > * Default to scanning all possible device locations. > > > */ > > > port_index = 0; > > > > After patching the "adv_isa.c" file and rebuilding the GENERIC > kernel > > those messages went away. Previously posted chunk of the 'dmesg -a' > > output looks so now: > > > > isa_probe_children: probing PnP devices > > ed1: at port 0x200-0x21f irq 5 on > isa0 > > ed1: [GIANT-LOCKED] > > ed1: bpf attached > > ed1: Ethernet address: 00:00:21:82:25:03 > > type NE2000 (16 bit) > > unknown: can't assign resources (port) > > unknown: at port 0x60 on isa0 > > unknown: failed to probe at port 0x61 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x4d0-0x4d1 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x208-0x20f on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x3f8-0x3ff on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x3f2-0x3f5 on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x378-0x37f on isa0 > > unknown: can't assign resources (port) > > unknown: at port 0x2f8-0x2ff on isa0 > > Device configuration finished. > > procfs registered > > > > > > P.S. What are these "unknown: ..." messages? I don't have > so > > many PnP devices. And my speaker (port 0x61) is working properly. I > > even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse > -p -e > > -w 23 I am a 5.2-CURRENT, test me.' :-) > > They are PnPBIOS entries for things like the ISA timers, AT 8259A > PICs, and the speaker. FreeBSD doesn't currently use the PnPBIOS > device entries to attach to these devices. If FreeBSD doesn't currently use the PnPBIOS device entries, why FreeBSD tries assign or probe resources for those device entries anyway? Please, correct me if I misunderstood something here. Thank you __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-arch@FreeBSD.ORG Thu Aug 12 00:44:58 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDA6516A4CE for ; Thu, 12 Aug 2004 00:44:58 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8219F43D41 for ; Thu, 12 Aug 2004 00:44:58 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 3D4A07A3D2 for ; Wed, 11 Aug 2004 17:44:58 -0700 (PDT) Message-ID: <411ABD8A.70405@elischer.org> Date: Wed, 11 Aug 2004 17:44:58 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: arch@freebsd.org Content-Type: multipart/mixed; boundary="------------010209040104050607060306" Subject: [Fwd: [Fwd: RFC.. defining __rangeof() in cdefs.h]] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 00:44:59 -0000 This is a multi-part message in MIME format. --------------010209040104050607060306 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Warner suggested this should be asked here.. --------------010209040104050607060306 Content-Type: message/rfc822; name="[Fwd: RFC.. defining __rangeof() in cdefs.h]" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="[Fwd: RFC.. defining __rangeof() in cdefs.h]" Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by idiom.com (8.12.9p2/8.12.9) with ESMTP id i7BMmiOZ081610 for ; Wed, 11 Aug 2004 15:48:44 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 52DB358929 for ; Wed, 11 Aug 2004 22:47:41 +0000 (GMT) (envelope-from owner-freebsd-current@freebsd.org) Received: by hub.freebsd.org (Postfix) id F15FB16A511; Wed, 11 Aug 2004 22:47:36 +0000 (GMT) Delivered-To: julian@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E16DC16A50D; Wed, 11 Aug 2004 22:47:36 +0000 (GMT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9587D16A4CE for ; Wed, 11 Aug 2004 22:47:32 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F43143D31 for ; Wed, 11 Aug 2004 22:47:31 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 6A8E17A3D2 for ; Wed, 11 Aug 2004 15:47:31 -0700 (PDT) Message-ID: <411AA203.1020502@elischer.org> Date: Wed, 11 Aug 2004 15:47:31 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: current@freebsd.org Content-Type: multipart/mixed; boundary="------------040706030807060502090005" Subject: [Fwd: RFC.. defining __rangeof() in cdefs.h] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Accessio-Status: NO, score=0.00,none version=6.0 count=0 X-Accessio-Spam-Flag: NO X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on idiom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-ClamAV-Status: No X-Idiom-Reporting: If this was spam, please forward it to spambox@idiom.com This is a multi-part message in MIME format. --------------040706030807060502090005 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Interresting.. not a single comment.. :-/ --------------040706030807060502090005 Content-Type: message/rfc822; name="RFC.. defining __rangeof() in cdefs.h" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="RFC.. defining __rangeof() in cdefs.h" Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by idiom.com (8.12.9p2/8.12.9) with ESMTP id i79LeqOZ063959 for ; Mon, 9 Aug 2004 14:40:53 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 372F356A1D for ; Mon, 9 Aug 2004 21:40:45 +0000 (GMT) (envelope-from owner-freebsd-current@freebsd.org) Received: by hub.freebsd.org (Postfix) id 7CF5C16A4E7; Mon, 9 Aug 2004 21:40:43 +0000 (GMT) Delivered-To: julian@freebsd.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6457C16A4E4; Mon, 9 Aug 2004 21:40:43 +0000 (GMT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE71916A4CE for ; Mon, 9 Aug 2004 21:40:38 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75ED643D5A for ; Mon, 9 Aug 2004 21:40:38 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 12E377A3D2 for ; Mon, 9 Aug 2004 14:40:38 -0700 (PDT) Message-ID: <4117EF55.4090409@elischer.org> Date: Mon, 09 Aug 2004 14:40:37 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: RFC.. defining __rangeof() in cdefs.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Accessio-Status: NO, score=0.00,none version=6.0 count=0 X-Accessio-Spam-Flag: NO X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on idiom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Idiom-Reporting: If this was spam, please forward it to spambox@idiom.com I'm considdereing adding: Index: sys/cdefs.h =================================================================== RCS file: /home/ncvs/src/sys/sys/cdefs.h,v retrieving revision 1.83 diff -u -r1.83 cdefs.h --- sys/cdefs.h 28 Jul 2004 07:03:42 -0000 1.83 +++ sys/cdefs.h 9 Aug 2004 21:36:41 -0000 @@ -241,6 +241,8 @@ * require it. */ #define __offsetof(type, field) ((size_t)(&((type *)0)->field)) +#define __rangeof(type, start, end) \ + (__offsetof(type, end) - __offsetof(type, start)) /* * Compiler-dependent macros to declare that functions take printf-like it is used in several places. most importantly in fork1() and it is defined in several files (*).. we should probably just have one copy... (*) in the form RANGEOF() but if we define it in cdefs.h I'd change that to __rangeof() to match __offsetof() _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --------------040706030807060502090005 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --------------040706030807060502090005-- --------------010209040104050607060306-- From owner-freebsd-arch@FreeBSD.ORG Thu Aug 12 05:57:20 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC2DB16A4CE for ; Thu, 12 Aug 2004 05:57:19 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E6F43D54 for ; Thu, 12 Aug 2004 05:57:17 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 7565 invoked from network); 12 Aug 2004 05:57:13 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Aug 2004 05:57:13 -0000 Received: from hydrogen.funkthat.com (fybura@localhost.funkthat.com [127.0.0.1])i7C5vDuU016190; Wed, 11 Aug 2004 22:57:13 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i7C5vC4l016189; Wed, 11 Aug 2004 22:57:12 -0700 (PDT) Date: Wed, 11 Aug 2004 22:57:12 -0700 From: John-Mark Gurney To: John Baldwin Message-ID: <20040812055712.GC991@funkthat.com> Mail-Followup-To: John Baldwin , freebsd-arch@FreeBSD.org References: <20040806224316.GB991@funkthat.com> <200408091026.35755.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408091026.35755.jhb@FreeBSD.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-arch@FreeBSD.org Subject: Re: valid dup lock logic for witness X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 05:57:20 -0000 John Baldwin wrote this message on Mon, Aug 09, 2004 at 10:26 -0400: > On Friday 06 August 2004 06:43 pm, John-Mark Gurney wrote: > > I have been working on kqueue, and to support kq in kq, I need to obtain > > two kq locks (both of the same type) at the same time. Normally this can > > cause a deadlock, but using a proper lock ordering strategy, it can be > > avoided. In the kq case, I chose to aquire a kq global lock before > > acquiring multiple kq locks. (In the proc case, jhb said you aquire > > the child's before the parents.) > > > > Mutexs have the flag MTX_DUPOK that notify witness that duplicate locks > > are ok, but this can hide other problems (and in fact would have in my > > testing). > > > > I have created a patch that lets you inform witness the a duplicate lock > > is valid as long as you hold another lock. The only run time change is > > that when a duplicate lock is found, it will run through another table > > to verify it's ok before printing out the back trace. > > > > Anyone have objections to this? > > As I said on IRC, my objection to this is that there are numerous ways of > acquiring duplicate locks in a valid fashion. For kq there is a global lock > around such cases. For proc locks child processes are locked before parents. > The problem is that there is not a single way of doing this, so if you want > WITNESS to check all of these, you will have to add lots of special case > one-off hacks to WITNESS making it even more obtuse and slow. Perhaps > something that might be feasible is to provide some sort of way for other > parts of the kernel to register a duplicate check function for a given lock > type. This would let you keep the code doing the duplicate check closer to > the code using the locks for one thing and would avoid adding N hacks to > witness for the various different dup lock checks. How about that, but making the dup lock ok w/ a signle parent lock a generic function. I would imagine there are a finite number of ways to solve duplicate locks, and they will end up being shared between different subsystems. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arch@FreeBSD.ORG Thu Aug 12 13:11:43 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50F5C16A4CE for ; Thu, 12 Aug 2004 13:11:43 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id E913D43D39 for ; Thu, 12 Aug 2004 13:11:42 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21021 invoked from network); 12 Aug 2004 13:11:42 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 12 Aug 2004 13:11:42 -0000 Received: from [10.50.41.91] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i7CDBGbW099702; Thu, 12 Aug 2004 09:11:38 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Rostislav Krasny Date: Wed, 11 Aug 2004 17:30:36 -0400 User-Agent: KMail/1.6.2 References: <20040811211241.17442.qmail@web14828.mail.yahoo.com> In-Reply-To: <20040811211241.17442.qmail@web14828.mail.yahoo.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408111730.36301.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: gibbs@FreeBSD.org cc: freebsd-arch@FreeBSD.org Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 13:11:43 -0000 On Wednesday 11 August 2004 05:12 pm, Rostislav Krasny wrote: > --- John Baldwin wrote: > > On Tuesday 10 August 2004 08:27 pm, Rostislav Krasny wrote: > > > --- John Baldwin wrote: > > > > On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > > > > > --- John Baldwin wrote: > > > > > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c > > > > Please > > > > > > > > let me know if it is not, thanks! > > > > > > > > > > Thank you very much! The "IRQ 2 problem" is fixed now and that > > > > > device (ed1) is working. > > > > > > > > > > The only strange thing is what I see in 'dmesg -a' output after > > > > > booting in verbose mode (the first "adv1:..." line): > > > > > > > > Try this patch to the adv(4) driver to see if your messages go > > > > away: > > > > Index: dev/advansys/adv_isa.c > > > > =================================================================== > > > > > > RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v > > > > retrieving revision 1.26 > > > > diff -u -r1.26 adv_isa.c > > > > --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 > > > > +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 > > > > @@ -117,6 +117,12 @@ > > > > struct resource *iores, *irqres; > > > > > > > > /* > > > > + * We don't know of any PnP ID's for these cards. > > > > + */ > > > > + if (isa_get_logicalid(dev) != 0) > > > > + return (ENXIO); > > > > + > > > > + /* > > > > * Default to scanning all possible device locations. > > > > */ > > > > port_index = 0; > > > > > > After patching the "adv_isa.c" file and rebuilding the GENERIC > > > > kernel > > > > > those messages went away. Previously posted chunk of the 'dmesg -a' > > > output looks so now: > > > > > > isa_probe_children: probing PnP devices > > > ed1: at port 0x200-0x21f irq 5 on > > > > isa0 > > > > > ed1: [GIANT-LOCKED] > > > ed1: bpf attached > > > ed1: Ethernet address: 00:00:21:82:25:03 > > > type NE2000 (16 bit) > > > unknown: can't assign resources (port) > > > unknown: at port 0x60 on isa0 > > > unknown: failed to probe at port 0x61 on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x4d0-0x4d1 on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x208-0x20f on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x3f8-0x3ff on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x3f2-0x3f5 on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x378-0x37f on isa0 > > > unknown: can't assign resources (port) > > > unknown: at port 0x2f8-0x2ff on isa0 > > > Device configuration finished. > > > procfs registered > > > > > > > > > P.S. What are these "unknown: ..." messages? I don't have > > > > so > > > > > many PnP devices. And my speaker (port 0x61) is working properly. I > > > even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse > > > > -p -e > > > > > -w 23 I am a 5.2-CURRENT, test me.' :-) > > > > They are PnPBIOS entries for things like the ISA timers, AT 8259A > > PICs, and the speaker. FreeBSD doesn't currently use the PnPBIOS > > device entries to attach to these devices. > > If FreeBSD doesn't currently use the PnPBIOS device entries, why > FreeBSD tries assign or probe resources for those device entries > anyway? Please, correct me if I misunderstood something here. > > Thank you We use them for some devices like sio0. We just don't use all of them (yet). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-arch@FreeBSD.ORG Thu Aug 12 13:50:56 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F92116A4CE for ; Thu, 12 Aug 2004 13:50:56 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 440F743D31 for ; Thu, 12 Aug 2004 13:50:56 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 16265 invoked from network); 12 Aug 2004 13:50:56 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 12 Aug 2004 13:50:55 -0000 Received: from [10.50.41.91] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i7CDop20099923; Thu, 12 Aug 2004 09:50:52 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-arch@FreeBSD.org, John-Mark Gurney Date: Thu, 12 Aug 2004 09:23:42 -0400 User-Agent: KMail/1.6.2 References: <20040806224316.GB991@funkthat.com> <200408091026.35755.jhb@FreeBSD.org> <20040812055712.GC991@funkthat.com> In-Reply-To: <20040812055712.GC991@funkthat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408120923.42973.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: valid dup lock logic for witness X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 13:50:56 -0000 On Thursday 12 August 2004 01:57 am, John-Mark Gurney wrote: > John Baldwin wrote this message on Mon, Aug 09, 2004 at 10:26 -0400: > > On Friday 06 August 2004 06:43 pm, John-Mark Gurney wrote: > > > I have been working on kqueue, and to support kq in kq, I need to > > > obtain two kq locks (both of the same type) at the same time. Normally > > > this can cause a deadlock, but using a proper lock ordering strategy, > > > it can be avoided. In the kq case, I chose to aquire a kq global lock > > > before acquiring multiple kq locks. (In the proc case, jhb said you > > > aquire the child's before the parents.) > > > > > > Mutexs have the flag MTX_DUPOK that notify witness that duplicate locks > > > are ok, but this can hide other problems (and in fact would have in my > > > testing). > > > > > > I have created a patch that lets you inform witness the a duplicate > > > lock is valid as long as you hold another lock. The only run time > > > change is that when a duplicate lock is found, it will run through > > > another table to verify it's ok before printing out the back trace. > > > > > > Anyone have objections to this? > > > > As I said on IRC, my objection to this is that there are numerous ways of > > acquiring duplicate locks in a valid fashion. For kq there is a global > > lock around such cases. For proc locks child processes are locked before > > parents. The problem is that there is not a single way of doing this, so > > if you want WITNESS to check all of these, you will have to add lots of > > special case one-off hacks to WITNESS making it even more obtuse and > > slow. Perhaps something that might be feasible is to provide some sort > > of way for other parts of the kernel to register a duplicate check > > function for a given lock type. This would let you keep the code doing > > the duplicate check closer to the code using the locks for one thing and > > would avoid adding N hacks to witness for the various different dup lock > > checks. > > How about that, but making the dup lock ok w/ a signle parent lock a > generic function. I would imagine there are a finite number of ways > to solve duplicate locks, and they will end up being shared between > different subsystems. Making it a generic function will be slower. You can have the kqueue dup check function look something like: int kqueue_check_dup(struct lock_object *l1, struct lock_object *l2) { return (mtx_owned(&kqueue_master_dup_lock)); } (Where the dup function returns 1 if the dup is ok and 0 if it is not). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-arch@FreeBSD.ORG Thu Aug 12 23:08:16 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13B0616A4CE for ; Thu, 12 Aug 2004 23:08:16 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A75643D41 for ; Thu, 12 Aug 2004 23:08:14 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b147.otenet.gr [212.205.244.155]) i7CN7ciJ012185; Fri, 13 Aug 2004 02:07:50 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id i7CN6Scc007269; Fri, 13 Aug 2004 02:06:28 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id i7CN6L4R007268; Fri, 13 Aug 2004 02:06:21 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 13 Aug 2004 02:06:21 +0300 From: Giorgos Keramidas To: Julian Elischer Message-ID: <20040812230620.GA7173@gothmog.gr> References: <411ABD8A.70405@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <411ABD8A.70405@elischer.org> cc: arch@freebsd.org Subject: Re: [Fwd: [Fwd: RFC.. defining __rangeof() in cdefs.h]] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 23:08:16 -0000 On 2004-08-11 17:44, Julian Elischer wrote: > Warner suggested this should be asked here.. > Date: Wed, 11 Aug 2004 15:47:31 -0700 > To: current@freebsd.org > > Interresting.. not a single comment.. :-/ > Date: Mon, 09 Aug 2004 14:40:37 -0700 > To: current@freebsd.org > > I'm considdereing adding: > > --- sys/cdefs.h 28 Jul 2004 07:03:42 -0000 1.83 > +++ sys/cdefs.h 9 Aug 2004 21:36:41 -0000 > @@ -241,6 +241,8 @@ > * require it. > */ > #define __offsetof(type, field) ((size_t)(&((type *)0)->field)) > +#define __rangeof(type, start, end) \ > + (__offsetof(type, end) - __offsetof(type, start)) > it is used in several places. most importantly in fork1() > > and it is defined in several files (*).. we should probably just have > one copy... Bearing in mind that I'm not really very acquainted with the internals of IMHO this is ok, since __rangeof() starts with underscores, which clearly sets it into the implementation- specific part of the namespace. If it simplifies things in the source tree and the people from -standards don't object to it, I think it's fine :-) There are now 6 different places where RANGEOF() is defined: src/sys/kern/kern_fork.c src/sys/kern/kern_proc.c src/sys/kern/kern_thr.c src/sys/kern/kern_thread.c src/sys/kern/kern_kse.c src/sys/vm/vm_glue.c All these definitions are identical, if one ignores whitespace, so moving the definition to a single place is a Good Thing(TM). It might even be possible to remove some of these (re)definitions. For instance, kern_proc.c and kern_thread.c define RANGEOF() but AFAICT they never actually use this macro. - Giorgos From owner-freebsd-arch@FreeBSD.ORG Fri Aug 13 09:09:36 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E184516A4CE; Fri, 13 Aug 2004 09:09:36 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 793E643D39; Fri, 13 Aug 2004 09:09:34 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.12.10/8.12.10) with ESMTP id i7D99WNf025797; Fri, 13 Aug 2004 11:09:32 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id i7D99Xsa049646; Fri, 13 Aug 2004 11:09:33 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i7D99Xim049645; Fri, 13 Aug 2004 11:09:33 +0200 (CEST) (envelope-from ftigeot) Date: Fri, 13 Aug 2004 11:09:33 +0200 From: Francois Tigeot To: "Bjoern A. Zeeb" Message-ID: <20040813090933.GA94761@aoi.wolfpond.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: FreeBSD arch mailing list cc: FreeBSD current mailing list Subject: Re: NO_YP_LIBC patch - please test/review X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 09:09:37 -0000 On Sun, Aug 08, 2004 at 03:21:41PM +0000, Bjoern A. Zeeb wrote: > > I am looking for more tests and reviews of the NO_YP_LIBC patch. > > You can find the latest version to test on > http://sources.zabbadoz.net/freebsd/patchset/10039-no-yp-libc.diff > > You will need to apply the whole patch in order to successfully build > a world with > NO_YP_LIBC=yes > in make.conf and thus be able to also test the changes. > Mostly things like bind, sendmail, amd, etc. that still get build will > need testing. FWIW, I have been running a lightly loaded mail server for two days with this patch. I didn't find any problem whatsoever yet. -- Francois Tigeot From owner-freebsd-arch@FreeBSD.ORG Fri Aug 13 13:53:30 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9800616A4CE for ; Fri, 13 Aug 2004 13:53:30 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D812243D39 for ; Fri, 13 Aug 2004 13:53:29 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i7DDrRFi062349 for ; Fri, 13 Aug 2004 15:53:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 13 Aug 2004 13:49:36 GMT." <200408131349.i7DDnaJY086691@repoman.freebsd.org> Date: Fri, 13 Aug 2004 15:53:27 +0200 Message-ID: <62348.1092405207@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: Re: PERFORCE change 59573 for review X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 13:53:30 -0000 Can anybody shed light on this one ? In message <200408131349.i7DDnaJY086691@repoman.freebsd.org>, Poul-Henning Kamp writes: >http://perforce.freebsd.org/chv.cgi?CH=59573 > >Change 59573 by phk@phk_bang on 2004/08/13 13:48:38 > > Bring back the first chunk of ffs_getpages(). > > FFS cannot run with straight vnode_pager_generic_getpages() > and I suspect that means that the first code in ffs_getpages > really belong in vnode_pager_generic_getpages() where other > filesystems would benefit as well, rather than being private > to FFS. > >Affected files ... > >.. //depot/user/phk/phk_bufwork/sys/ufs/ffs/ffs_vnops.c#13 edit > >Differences ... > >==== //depot/user/phk/phk_bufwork/sys/ufs/ffs/ffs_vnops.c#13 (text+ko) ==== > >@@ -81,6 +81,7 @@ > extern int ffs_rawread(struct vnode *vp, struct uio *uio, int *workdone); > #endif > static int ffs_fsync(struct vop_fsync_args *); >+static int ffs_getpages(struct vop_getpages_args *); > static int ffs_read(struct vop_read_args *); > static int ffs_write(struct vop_write_args *); > static int ffs_extread(struct vnode *vp, struct uio *uio, int ioflag); >@@ -100,6 +101,7 @@ > static struct vnodeopv_entry_desc ffs_vnodeop_entries[] = { > { &vop_default_desc, (vop_t *) ufs_vnoperate }, > { &vop_fsync_desc, (vop_t *) ffs_fsync }, >+ { &vop_getpages_desc, (vop_t *) ffs_getpages }, > { &vop_read_desc, (vop_t *) ffs_read }, > { &vop_reallocblks_desc, (vop_t *) ffs_reallocblks }, > { &vop_write_desc, (vop_t *) ffs_write }, >@@ -712,6 +714,50 @@ > } > > /* >+ * get page routine >+ */ >+static int >+ffs_getpages(ap) >+ struct vop_getpages_args *ap; >+{ >+ int i; >+ vm_page_t mreq; >+ int pcount; >+ >+ GIANT_REQUIRED; >+ >+ pcount = round_page(ap->a_count) / PAGE_SIZE; >+ mreq = ap->a_m[ap->a_reqpage]; >+ >+ /* >+ * if ANY DEV_BSIZE blocks are valid on a large filesystem block, >+ * then the entire page is valid. Since the page may be mapped, >+ * user programs might reference data beyond the actual end of file >+ * occuring within the page. We have to zero that data. >+ */ >+ VM_OBJECT_LOCK(mreq->object); >+ if (mreq->valid) { >+ if (mreq->valid != VM_PAGE_BITS_ALL) >+ vm_page_zero_invalid(mreq, TRUE); >+ vm_page_lock_queues(); >+ for (i = 0; i < pcount; i++) { >+ if (i != ap->a_reqpage) { >+ vm_page_free(ap->a_m[i]); >+ } >+ } >+ vm_page_unlock_queues(); >+ VM_OBJECT_UNLOCK(mreq->object); >+ return VM_PAGER_OK; >+ } >+ VM_OBJECT_UNLOCK(mreq->object); >+ >+ return vnode_pager_generic_getpages(ap->a_vp, ap->a_m, >+ ap->a_count, >+ ap->a_reqpage); >+} >+ >+ >+/* > * Extended attribute area reading. > */ > static int > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.