From owner-freebsd-current Sun Sep 8 1:13: 1 2002 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 E7FF337B400 for ; Sun, 8 Sep 2002 01:12:58 -0700 (PDT) Received: from mail.dada.it (mail4.dada.it [195.110.100.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 3406E43E4A for ; Sun, 8 Sep 2002 01:12:46 -0700 (PDT) (envelope-from riccardo@torrini.org) Received: (qmail 23450 invoked from network); 8 Sep 2002 08:12:34 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 8 Sep 2002 08:12:34 -0000 Received: from trudy.torrini.home (localhost.torrini.home [127.0.0.1]) by torrini.org (8.12.3/8.12.3) with ESMTP id g888CVZv019873; Sun, 8 Sep 2002 10:12:31 +0200 (CEST) (envelope-from riccardo@trudy.torrini.home) Received: (from riccardo@localhost) by trudy.torrini.home (8.12.3/8.12.3/Submit) id g888CThi019872; Sun, 8 Sep 2002 10:12:29 +0200 (CEST) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020907215522.GE9987@hades.hell.gr> Date: Sun, 08 Sep 2002 10:12:29 +0200 (CEST) From: Riccardo Torrini To: Giorgos Keramidas Subject: Re: Unable to buildworld (new record, 18") Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Sep-2002 (21:55:22/GMT) Giorgos Keramidas wrote: >> /usr/include/sys/_types.h:71: declaration does not declare anything >> *** Error code 1 > Which revision of /usr/include/sys/_types.h do you have? # ident /usr/include/sys/_types.h /usr/include/sys/_types.h: $FreeBSD: src/sys/sys/_types.h,v 1.7 2002/08/25 19:26:31 mike Exp $ # ident /usr/include/stdlib.h /usr/include/stdlib.h: $FreeBSD: src/include/stdlib.h,v 1.41 2002/09/06 11:23:32 tjr Exp $ > What is at, around, and near line 71 of /usr/include/sys/_types.h ? # cat -n /usr/include/sys/_types.h | grep -C4 "71" 67 * character set plus one extra value (WEOF), and must be at least 16 bits. 68 */ 69 typedef int __ct_rune_t; 70 typedef __ct_rune_t __rune_t; 71 typedef __ct_rune_t __wchar_t; 72 typedef __ct_rune_t __wint_t; 73 74 /* 75 * mbstate_t is an opaque object to keep conversion state during multibyte After some unsuccesfull buildworld I tryed updating includes but got the same error. May be because my -CURRENT is pre-gcc_3.1 ? Can I (Must I?) upgrade to an intermediate version between May and now? Riccardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 1:32:20 2002 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 8C92B37B400 for ; Sun, 8 Sep 2002 01:32:18 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F3A943E65 for ; Sun, 8 Sep 2002 01:32:17 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Sep 2002 09:32:16 +0100 (BST) Date: Sun, 8 Sep 2002 09:32:15 +0100 From: David Malone To: Craig Rodrigues Cc: freebsd-current@freebsd.org Subject: Re: Clock runs too fast Message-ID: <20020908083215.GA45774@walton.maths.tcd.ie> References: <20020907231952.A5525@attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020907231952.A5525@attbi.com> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 07, 2002 at 11:19:52PM -0400, Craig Rodrigues wrote: > Is there a problem with the ACPI code or with my > hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). Several people (including me) have reported this problem with this motherboard. Poul had a look at it, but couldn't figure out why the clock was running fast - I'd guess the hardware is busted in some obscure way. (I may have a look at it once I have the machine running -current again. At the moment it is my NAT box, so it is running -stable). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 1:47:46 2002 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 EBC5B37B400; Sun, 8 Sep 2002 01:47:43 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA7043E42; Sun, 8 Sep 2002 01:47:42 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA23988; Sun, 8 Sep 2002 18:47:39 +1000 Date: Sun, 8 Sep 2002 18:55:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Bruce A. Mah" Cc: Poul-Henning Kamp , Subject: Re: libmd bug on -CURRENT In-Reply-To: <200209071604.g87G44pc019967@intruder.bmah.org> Message-ID: <20020908183745.X2381-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 7 Sep 2002, Bruce A. Mah wrote: > If memory serves me right, Bruce Evans wrote: > > libmd is also broken for some cases involving pipes. IIRC, this is > > caused by the bogus st_size checks in the same function. st_size is > > only valid for regular files. > > It's puzzling that the call to lseek(2) doesn't always return an error > in these cases as well (as the manpage seems to imply). Yet, one can do > md5(1) on a pipe: > > tomcat:bmah% cat /etc/motd | md5 > 9caae6eae6f9c2dfea77d6a5fae2e93c > tomcat:bmah% md5 /etc/motd > MD5 (/etc/motd) = 9caae6eae6f9c2dfea77d6a5fae2e93c I don't remember exactly which case(s) are broken. The above works, but cat /dev/motd | md5 /dev/stdin doesn't -- it gives the seek error. I think the open() in mdXFileChunk() gets used for the latter but not when stdin is used directly. This is with /dev/stdin not on devfs or fdescfs. Named pipes seem to work too: mkfifo p; md5 < p & cat /etc/motd >p # same result as md5 /etc/motd > > The loop in the function fails to to terminate if read() returns 0, > > which can probably happen if the file shrinks underneath us. > > Maybe add a check after the read(2), so that if it returns zero, we set > n = 0? It's not clear to me what result should be returned in the case > of trying to compute a checksum on a file that shrinks in the middle of > the computation. Writes that change the file underneath us will make a mess of the result. Hmm ... detecting changes is very easy, at least for regular files - just use fstat() and compare ctimes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 2: 2: 1 2002 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 4E6CB37B405 for ; Sun, 8 Sep 2002 02:01:58 -0700 (PDT) Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E1243E4A for ; Sun, 8 Sep 2002 02:01:57 -0700 (PDT) (envelope-from bartequi@neomedia.it) Received: from localhost (aragorn.neomedia.it [195.120.250.6] (may be forged)) by aragorn.neomedia.it (8.12.3/8.12.3) with ESMTP id g8891rtR032056; Sun, 8 Sep 2002 11:01:53 +0200 (CEST) Received: from 213.144.203.36 ([213.144.203.36]) by webmail.neomedia.it (IMP) with HTTP for ; Sun, 8 Sep 2002 11:01:52 +0200 Message-ID: <1031475712.3d7b1200ee5b0@webmail.neomedia.it> Date: Sun, 8 Sep 2002 11:01:52 +0200 From: Salvo Bartolotta To: Riccardo Torrini Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: Unable to buildworld (new record, 18") MIME-Version: 1.0 Content-Type: text/plain; charset=Any Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1.1-cvs X-WebMail-Company: Neomedia X-Originating-IP: 213.144.203.36 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 9/7/02, 11:20:48 PM, Riccardo Torrini wrote regarding Re: Unable to buildworld (new record, 18"): > On 07-Sep-2002 (21:00:28/GMT) Riccardo Torrini wrote: > >> Have you read through UPDATING? > > Yes, more and more ... I added -DNO_WERROR without luck > > I also found two PR speaking about wchar_t (31864 and 40084). > > I'm about to remove contrib/gcc tree and cvsuping again... > No, same error :( Any other ideas? [...] Have you tried making new includes? Ciao, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 3:19: 1 2002 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 D39E337B400; Sun, 8 Sep 2002 03:18:53 -0700 (PDT) Received: from thufir.bluecom.no (thufir.bluecom.no [217.118.32.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5505043E77; Sun, 8 Sep 2002 03:18:52 -0700 (PDT) (envelope-from eirik@eirikn.net) Received: from eirikn.net (a217-118-45-95.bluecom.no [217.118.45.95]) by thufir.bluecom.no (8.11.5/8.11.5) with ESMTP id g88AIc802870; Sun, 8 Sep 2002 12:18:42 +0200 Received: by eirikn.net (Postfix, from userid 1001) id 98098756; Sun, 8 Sep 2002 12:18:41 +0200 (CEST) Date: Sun, 8 Sep 2002 12:18:41 +0200 From: Eirik Nygaard To: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: 5.0 package build with gcc32 complete (HELP NEEDED!!) Message-ID: <20020908101841.GA34010@eirikn.net> Reply-To: eirikn@bluezone.no Mail-Followup-To: current@FreeBSD.ORG, ports@FreeBSD.ORG References: <20020906185816.GA75066@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <20020906185816.GA75066@xor.obsecurity.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I got some free time on my hands and will try to fix some ports, already fi= xed sysutils/logmon. On Fri, Sep 06, 2002 at 11:58:17AM -0700, Kris Kennaway wrote: > All ports maintainers/committers: please take a look at >=20 > http://bento.freebsd.org/errorlogs/5-latest/ >=20 > and consider fixing some ports. With the new gcc compiler we now have > over 900 packages that are failing to build (an all-time record, > AFAIK). Many of these are simple to fix and require less than 5 > minutes of your time. Thanks for any help you can provide. >=20 > Kris >=20 --=20 Eirik Nygaard Http://kverka.org/~eirik/ PGP Key: 83C55EDE --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9eyQB1JB0Z4PFXt4RAhr1AJsFSB8hBzQW2RFtmg1ErJfTmSGHKwCfXA0M 7RK8k+Lr5mmywcM6tAWwJms= =ZV6W -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 3:34:23 2002 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 85E8537B400; Sun, 8 Sep 2002 03:34:13 -0700 (PDT) Received: from maya20.nic.fr (maya20.nic.fr [192.134.4.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A72D43E65; Sun, 8 Sep 2002 03:34:12 -0700 (PDT) (envelope-from francois.tigeot@nic.fr) Received: from brazil.nic.fr (brazil.nic.fr [192.134.4.77]) by maya20.nic.fr (8.12.4/8.12.4) with ESMTP id g88ASM231322909; Sun, 8 Sep 2002 12:28:22 +0200 (CEST) Received: from brazil.nic.fr (localhost [IPv6:::1]) by brazil.nic.fr (8.12.5/8.12.5) with ESMTP id g88ASKkR035140; Sun, 8 Sep 2002 12:28:20 +0200 (CEST) (envelope-from tigeot@brazil.nic.fr) Received: (from tigeot@localhost) by brazil.nic.fr (8.12.5/8.12.5/Submit) id g88ASKto035139; Sun, 8 Sep 2002 12:28:20 +0200 (CEST) Date: Sun, 8 Sep 2002 12:28:20 +0200 From: Francois Tigeot To: current@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: ste driver broken Message-ID: <20020908102820.GA71874@brazil.nic.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4i Organization: AFNIC / NIC-France Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, I recently upgraded one machine to a recent -CURRENT, and the NIC (DLink 550 TX) fails to be properly initialized. The rest of the system is pretty vanilla : Athlon XP, with Via chipset. Here is the relevant part of dmesg: ste0: port 0x9800-0x987f mem 0xe9000000-0xe900007f irq 7 at device 11.0 on pci0 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 lock order reversal 1st 0xc25b69a4 ste0 (network driver) @ /usr/src/sys/pci/if_ste.c:937 2nd 0xc0318600 allproc (allproc) @ /usr/src/sys/kern/kern_fork.c:317 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 ste0: Ethernet address: 00:50:ba:71:be:ea ste0: MII without any phy! device_probe_and_attach: ste0 attach returned 6 By replacing the current version of /usr/src/sys/pci/if_ste.c by version 1.33 I am able to obtain a correctly working system. This is a part of the new dmesg: ste0: port 0x9800-0x987f mem 0xe9000000-0xe900007f irq 7 at device 11.0 on pci0 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:906 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:906 lock order reversal 1st 0xc26039a4 ste0 (network driver) @ /usr/src/sys/pci/if_ste.c:906 2nd 0xc0487c00 allproc (allproc) @ /usr/src/sys/kern/kern_fork.c:317 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:906 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:906 /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:906 ste0: Ethernet address: 00:50:ba:71:be:ea miibus0: on ste0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:244 The main difference between the working and current revision of if_ste.c is very small and doesn't add anything new. I think it should be removed. -- François Tigeot | AFNIC http://www.nic.fr/ | mailto:nic@nic.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 4:21:40 2002 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 89FB237B400 for ; Sun, 8 Sep 2002 04:21:37 -0700 (PDT) Received: from alfred.skaarup.org (alfred.skaarup.org [193.111.120.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 5FB2743E3B for ; Sun, 8 Sep 2002 04:21:35 -0700 (PDT) (envelope-from mfbsd@skaarup.org) Received: (qmail 11144 invoked by uid 0); 8 Sep 2002 11:21:33 -0000 Received: from localhost (HELO alfred.skaarup.org) (127.0.0.1) by localhost with SMTP; 8 Sep 2002 11:21:33 -0000 Received: (qmail 11137 invoked by uid 1039); 8 Sep 2002 11:21:33 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Sep 2002 11:21:33 -0000 Date: Sun, 8 Sep 2002 13:21:33 +0200 (CEST) From: Rasmus Skaarup To: freebsd-current@freebsd.org Subject: syscons in rcng ? Message-ID: <20020908131904.R11096-100000@alfred.skaarup.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, With the latest changes (1.8, 5th of Sep) to /etc/rc.d/syscons, syscons doesn't get initialized on my 5.0-CURRENT. Have I missed some new configuration options? Sincerely, Rasmus Skaarup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 4:42:53 2002 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 1879937B400 for ; Sun, 8 Sep 2002 04:42:50 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 502CB43E65 for ; Sun, 8 Sep 2002 04:42:48 -0700 (PDT) (envelope-from ust@cert.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g88BgfT27271 for ; Sun, 8 Sep 2002 13:42:41 +0200 (MEST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g88Bgfx18488 for ; Sun, 8 Sep 2002 13:42:41 +0200 (MEST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.12.6/8.12.6/Siemens CERT [ $Revision: 1.25 ]) with ESMTP id g88BgePA078206 for ; Sun, 8 Sep 2002 13:42:40 +0200 (CEST) (envelope-from ust@alaska.cert.siemens.de) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [127.0.0.1]) by alaska.cert.siemens.de (8.12.6/8.12.6/alaska [ $Revision: 1.14 ]) with ESMTP id g88BgeG9050959 for ; Sun, 8 Sep 2002 13:42:40 +0200 (CEST) (envelope-from ust@alaska.cert.siemens.de) Received: (from ust@localhost) by alaska.cert.siemens.de (8.12.6/8.12.6/alaska [ $Revision: 1.3 ]) id g88BgeYu050958 for freebsd-current@FreeBSD.ORG; Sun, 8 Sep 2002 13:42:40 +0200 (CEST) (envelope-from ust) Date: Sun, 8 Sep 2002 13:42:40 +0200 From: Udo Schweigert To: freebsd-current@FreeBSD.ORG Subject: Release building broken for -current Message-ID: <20020908114240.GA50562@alaska.cert.siemens.de> Mail-Followup-To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline X-Operating-System: FreeBSD 4.7-PRERELEASE User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, when bulding release on -current I get (since a couple of days): > rm -rf /R/stage/dists > mkdir -p /R/stage/dists > rolling base/base tarball > mtree: line 0: dumpdates: No such file or directory > *** Error code 1 > > Stop in /usr/src/release. Somehow dumpdates didn't get installed into /R/stage/trees/base/usr/share/examples/etc Later then I got same problems for: /R/stage/trees/base/usr/share/tmac/mm/locale /R/stage/trees/base/usr/share/tmac/mm/se_locale ... and others. All the problems seem to be with files of size 0, so maybe the problem is with mtree. Hopefully this can be get fixed so a new snapshot release with the new gcc can be built. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : udo.schweigert@siemens.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 5:18:15 2002 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 BF27B37B405 for ; Sun, 8 Sep 2002 05:18:09 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8978A43E72 for ; Sun, 8 Sep 2002 05:18:09 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g88CI9YB001966 for ; Sun, 8 Sep 2002 05:18:09 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g88CI849001964 for current@freebsd.org; Sun, 8 Sep 2002 05:18:08 -0700 (PDT) Date: Sun, 8 Sep 2002 05:18:08 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209081218.g88CI849001964@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> share/termcap script, 36: Pattern not found script, 36: Ex command failed: pending commands discarded *** Error code 1 Stop in /var/tmp/des/src/share/termcap. *** Error code 1 Stop in /var/tmp/des/src/share. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 5:55:38 2002 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 625FE37B400 for ; Sun, 8 Sep 2002 05:55:32 -0700 (PDT) Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52FC443E4A for ; Sun, 8 Sep 2002 05:55:31 -0700 (PDT) (envelope-from D.Rock@t-online.de) Received: from fwd01.sul.t-online.de by mailout04.sul.t-online.com with smtp id 17o1b7-0006Er-05; Sun, 08 Sep 2002 14:55:29 +0200 Received: from dialin.t-online.de (340029380333-0001@[80.128.214.32]) by fmrl01.sul.t-online.com with esmtp id 17o1ax-10dZiaC; Sun, 8 Sep 2002 14:55:19 +0200 Received: from t-online.de (doom [172.23.7.254]) by dialin.t-online.de (8.11.6+Sun/8.11.6/Rock) with ESMTP id g88Cidv00192; Sun, 8 Sep 2002 14:44:39 +0200 (CEST) Message-ID: <3D7B4638.1060007@t-online.de> Date: Sun, 08 Sep 2002 14:44:40 +0200 From: Daniel Rock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.1) Gecko/20020826 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Craig Rodrigues Cc: freebsd-current@freebsd.org Subject: Re: Clock runs too fast References: <20020907231952.A5525@attbi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Craig Rodrigues schrieb: >Hi, > >I have been having this problem with -current for the past 2 weeks now >(I am new to -current and just started using it 2 weeks ago). >I just did a cvsup and rebuilt the kernel and rebuilt the world. > >My clock seems to be running too fast, and I keep resetting it >with ntpdate. > >[...] > >Now the clock seems to run at a more reasonable rate. > >Is there a problem with the ACPI code or with my >hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). > >How can I default to i8254 as my default timer? Is there >something I should put in device.hints? > I had similar problems with a Gigabyte GA-5AX (also with ALi Aladdin V chipset). Without setting debug.acpi.disable = "timer" the clock runs twice as fast as it should be. This problem seems to be introduced in the ACPI update around July 2001. I didn't find any solution other than disabling ACPI timecounter. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 7:10:51 2002 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 DCCF637B400 for ; Sun, 8 Sep 2002 07:10:48 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id C00FC43E65 for ; Sun, 8 Sep 2002 07:10:47 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA12041; Mon, 9 Sep 2002 00:10:41 +1000 Date: Mon, 9 Sep 2002 00:18:19 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Craig Rodrigues Cc: freebsd-current@FreeBSD.ORG Subject: Re: make installworld cannot find files in /usr/bin In-Reply-To: <20020907230246.A535@attbi.com> Message-ID: <20020909001128.E3205-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 7 Sep 2002, Craig Rodrigues wrote: > I did a cvsup from a few hours ago, and rebuilt the world. > make buildworld worked fine. > > make installworld failed: > ===> usr.sbin/ppp^M > install -s -o root -g network -m 4554 ppp /usr/sbin > m4 /usr/src/usr.sbin/ppp/ppp.8.m4 >ppp.8 > m4: not found > > I also had similar problems in /usr/src/share/termcap, because > the Makefile there could not find /usr/bin/cap_mkdb and > /usr/bin/ex. > > I worked around the problem by replacing references > to m4, cap_mkdb, and ex > in /usr/src/usr.sbin/ppp/Makefile and /usr/src/share/termcap/Makefile > with fully qualified path names. > > Any ideas what could cause this? Some local problem with timestamps, together with a bug in bsd.files.mk (it uses a hack to create dependencies, and this results in things being rebuilt at install time if something is out of date; building things at install times is an error and the error happens to be detected because some utilities needed for building are not in $PATH). > My environment has /usr/bin in its PATH. Also, if I manually > cd to either of those directories and do: make install, then > it finds the programs in /usr/bin with no problem. The error is not detected in this case because there are too many utilities in $PATH. Building at install time would still fail if the relevant obj directories are not writable. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 7:51:56 2002 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 E08D337B400 for ; Sun, 8 Sep 2002 07:51:53 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2198843E3B for ; Sun, 8 Sep 2002 07:51:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g88AGQUc000433; Sun, 8 Sep 2002 12:16:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Craig Rodrigues Cc: freebsd-current@freebsd.org Subject: Re: Clock runs too fast In-Reply-To: Your message of "Sat, 07 Sep 2002 23:19:52 EDT." <20020907231952.A5525@attbi.com> Date: Sun, 08 Sep 2002 12:16:26 +0200 Message-ID: <432.1031480186@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020907231952.A5525@attbi.com>, Craig Rodrigues writes: >I reset my timecounter: >sysctl kern.timecounter.hardware=i8254 > >Now the clock seems to run at a more reasonable rate. > >Is there a problem with the ACPI code or with my >hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). > >How can I default to i8254 as my default timer? Is there >something I should put in device.hints? Put it in /etc/rc.early: sysctl kern.timecounterhardware=i8254 I have not been able to understand in what way this board fails :-( Does the time run uniformly fast, ie: 7 minutes every 5, all the time, or is it erratic ? -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 9:43: 2 2002 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 7684B37B401 for ; Sun, 8 Sep 2002 09:43:01 -0700 (PDT) Received: from smtp3.southeast.rr.com (smtp3.southeast.rr.com [24.93.67.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD61943E6A for ; Sun, 8 Sep 2002 09:43:00 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from mail7.sc.rr.com (fe7 [24.93.67.54]) by smtp3.southeast.rr.com (8.12.5/8.12.2) with ESMTP id g88Ggaga017540 for ; Sun, 8 Sep 2002 12:42:37 -0400 (EDT) Received: from cae57-176-076.sc.rr.com ([66.57.176.76]) by mail7.sc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Sun, 8 Sep 2002 12:42:59 -0400 Date: Sun, 8 Sep 2002 12:42:59 -0400 (EDT) From: Wesley Morgan To: current@freebsd.org Subject: sio problems? Message-ID: <20020908123948.P10884-100000@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The sio driver was touched recently for the PUC stuff... Not sure if that is the source of my problem, but suddenly I am seeing many many many of these: sio1: 22 more interrupt-level buffer overflows (total 2943) Just started recently. Seems to happen most often when I cvsup. Happens with and without ACPI, with and without using a shared interrupt. -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 9:48: 6 2002 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 A94DB37B400 for ; Sun, 8 Sep 2002 09:48:04 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C75A743E65 for ; Sun, 8 Sep 2002 09:48:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g88GldZV008526; Sun, 8 Sep 2002 18:47:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Wesley Morgan Cc: current@FreeBSD.ORG Subject: Re: sio problems? In-Reply-To: Your message of "Sun, 08 Sep 2002 12:42:59 EDT." <20020908123948.P10884-100000@volatile.chemikals.org> Date: Sun, 08 Sep 2002 18:47:39 +0200 Message-ID: <8525.1031503659@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020908123948.P10884-100000@volatile.chemikals.org>, Wesley Morgan writes: >The sio driver was touched recently for the PUC stuff... Not sure if that >is the source of my problem, but suddenly I am seeing many many many of >these: > >sio1: 22 more interrupt-level buffer overflows (total 2943) > >Just started recently. Seems to happen most often when I cvsup. Happens >with and without ACPI, with and without using a shared interrupt. The changes to the PUC driver does not have anything to do with this I think. -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 10: 5:20 2002 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 9454C37B400 for ; Sun, 8 Sep 2002 10:05:18 -0700 (PDT) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BFFA43E4A for ; Sun, 8 Sep 2002 10:05:16 -0700 (PDT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1]) by zibbi.icomtek.csir.co.za (8.12.6/8.12.6) with ESMTP id g88H5BD8057227; Sun, 8 Sep 2002 19:05:11 +0200 (SAT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.12.6/8.12.6/Submit) id g88H58Mp057226; Sun, 8 Sep 2002 19:05:08 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200209081705.g88H58Mp057226@zibbi.icomtek.csir.co.za> Subject: Re: Release building broken for -current In-Reply-To: <20020908114240.GA50562@alaska.cert.siemens.de> from Udo Schweigert at "Sep 8, 2002 01:42:40 pm" To: udo.schweigert@siemens.com (Udo Schweigert) Date: Sun, 8 Sep 2002 19:05:08 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > when bulding release on -current I get (since a couple of days): > > > rm -rf /R/stage/dists > > mkdir -p /R/stage/dists > > rolling base/base tarball > > mtree: line 0: dumpdates: No such file or directory > > *** Error code 1 > > > > Stop in /usr/src/release. > > Somehow dumpdates didn't get installed into > /R/stage/trees/base/usr/share/examples/etc md5 died on zero length files. You will have to upgrade the machine or at least do a buildworld with new source before you try a release again. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 10:14:43 2002 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 9710C37B400 for ; Sun, 8 Sep 2002 10:14:42 -0700 (PDT) Received: from smtp4.wanadoo.nl (smtp4.wanadoo.nl [194.134.35.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ACE543E3B for ; Sun, 8 Sep 2002 10:14:41 -0700 (PDT) (envelope-from plusminus@zonnet.nl) Received: from woefdram (3eea54c8.cable.wanadoo.nl [62.234.84.200]) by smtp4.wanadoo.nl (Postfix) with SMTP id 5F4A03E41C for ; Sun, 8 Sep 2002 19:14:31 +0200 (CEST) Message-ID: <001101c2575b$2ddfb030$0300a8c0@woefdram> From: "Woefdram" To: Subject: Date: Sun, 8 Sep 2002 19:14:22 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 10:29:12 2002 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 E528537B400 for ; Sun, 8 Sep 2002 10:29:09 -0700 (PDT) Received: from out012.verizon.net (out012pub.verizon.net [206.46.170.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8CA243E4A for ; Sun, 8 Sep 2002 10:29:08 -0700 (PDT) (envelope-from arlankfo@verizon.net) Received: from verizon.net ([138.88.128.204]) by out012.verizon.net (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20020908172908.XRWX18399.out012.verizon.net@verizon.net>; Sun, 8 Sep 2002 12:29:08 -0500 To: current@freebsd.org Cc: mfbsd@skaarup.org Subject: Re: syscons in rcng ? From: "Andrew Lankford" Reply-To: "Andrew Lankford" Date: Sun, 08 Sep 2002 13:29:07 -0400 Message-Id: <20020908172908.XRWX18399.out012.verizon.net@verizon.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What I've noticed is that vidcontrol refuses to change the console mode to anything other than 80x25 or 80x30. I had it set at 80x60, but CURRENT no longer likes that. I've also noticed that starting up XFree4.2.0's server switches my console from 80x30 back to 80x25. Funky. In any case, I don't know anything about problems with /etc/rc.d/syscons, but perhaps vidcontrol or the kernel is the culprit. Andrew Lankford >Hello, > >With the latest changes (1.8, 5th of Sep) to /etc/rc.d/syscons, syscons >doesn't get initialized on my 5.0-CURRENT. > >Have I missed some new configuration options? > > >Sincerely, >Rasmus Skaarup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 11:34:31 2002 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 039DC37B400; Sun, 8 Sep 2002 11:34:29 -0700 (PDT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49D0D43E4A; Sun, 8 Sep 2002 11:34:28 -0700 (PDT) (envelope-from mi@aldan.algebra.com) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.12.5/8.12.5) with ESMTP id g88IU9vC086800; Sun, 8 Sep 2002 14:30:09 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.12.6/8.12.6/Submit) id g88IU6s9086799; Sun, 8 Sep 2002 14:30:06 -0400 (EDT) Content-Type: text/plain; charset="us-ascii" From: Mikhail Teterin To: current@FreeBSD.org Subject: troubles with the new GCC -- anyone else? Date: Sun, 8 Sep 2002 14:30:06 -0400 User-Agent: KMail/1.4.2 Cc: kde@FreeBSD.org, kan@FreeBSD.org, obrien@FreeBSD.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is it just me, or do others have troubles too? I upgraded yesterday: mi@celsius:~ (101) cc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.2.1 [FreeBSD] 20020901 (prerelease) With ``-march=pentium2 -mmmx'' . there is a file or two in XFree86-4-Server, that cause an Internal Compiler Error -- fixed with ``-march=pentium2 -mno-mmx'' (same trouble existed with the previous version, AFAIR) . one file in libiconv causes ICE -- the workaround above does not work. But ``-march=pentium -mmmx'' works. . in the kdelibs3, the kdecore/kkeyserver_x11.cpp will not compile regardless of the architecture or optimization flags -- the ICE is in GCC's cp/cp-lang.c:130, due, it seems, to the initialization complexity. Can't think of a workaround :-\ Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 11:38: 3 2002 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 941BB37B400; Sun, 8 Sep 2002 11:37:59 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2039C43E6A; Sun, 8 Sep 2002 11:37:59 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.5) with ESMTP id g88Ibk4m028744; Sun, 8 Sep 2002 11:37:47 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id g88IbfBB028743; Sun, 8 Sep 2002 11:37:41 -0700 (PDT) Date: Sun, 8 Sep 2002 11:37:41 -0700 From: Steve Kargl To: Mikhail Teterin Cc: current@FreeBSD.ORG, kde@FreeBSD.ORG, kan@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: troubles with the new GCC -- anyone else? Message-ID: <20020908183741.GA28735@troutmask.apl.washington.edu> References: <200209081429.43386@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209081429.43386@aldan> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 02:30:06PM -0400, Mikhail Teterin wrote: > Is it just me, or do others have troubles too? I upgraded yesterday: > > mi@celsius:~ (101) cc -v > Using built-in specs. > Configured with: FreeBSD/i386 system compiler > Thread model: posix > gcc version 3.2.1 [FreeBSD] 20020901 (prerelease) > > With ``-march=pentium2 -mmmx'' > Do not use -march=... -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 11:46:10 2002 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 7665D37B400 for ; Sun, 8 Sep 2002 11:46:07 -0700 (PDT) Received: from thufir.bluecom.no (thufir.bluecom.no [217.118.32.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 266F243E4A for ; Sun, 8 Sep 2002 11:46:06 -0700 (PDT) (envelope-from eirik@eirikn.net) Received: from eirikn.net (a217-118-45-95.bluecom.no [217.118.45.95]) by thufir.bluecom.no (8.11.5/8.11.5) with ESMTP id g88Ijw830090 for ; Sun, 8 Sep 2002 20:45:59 +0200 Received: by eirikn.net (Postfix, from userid 1001) id 067A06FE; Sun, 8 Sep 2002 20:45:59 +0200 (CEST) Date: Sun, 8 Sep 2002 20:45:59 +0200 From: Eirik Nygaard To: current@FreeBSD.ORG Subject: Re: troubles with the new GCC -- anyone else? Message-ID: <20020908184559.GA85104@eirikn.net> Reply-To: eirikn@bluezone.no Mail-Followup-To: current@FreeBSD.ORG References: <200209081429.43386@aldan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: <200209081429.43386@aldan> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable There is problem with several ports and gcc 3.2, which ports got the proble= m is maped and is put out on the web: http://bento.freebsd.org/errorlogs/5-= latest/, some has been fixed. On Sun, Sep 08, 2002 at 02:30:06PM -0400, Mikhail Teterin wrote: > Is it just me, or do others have troubles too? I upgraded yesterday: >=20 > mi@celsius:~ (101) cc -v > Using built-in specs. > Configured with: FreeBSD/i386 system compiler > Thread model: posix > gcc version 3.2.1 [FreeBSD] 20020901 (prerelease) >=20 > With ``-march=3Dpentium2 -mmmx'' >=20 > . there is a file or two in XFree86-4-Server, that cause an Internal Com= piler > Error -- fixed with ``-march=3Dpentium2 -mno-mmx'' (same trouble existed= with > the previous version, AFAIR) >=20 > . one file in libiconv causes ICE -- the workaround above does not work.= But > ``-march=3Dpentium -mmmx'' works. >=20 > . in the kdelibs3, the kdecore/kkeyserver_x11.cpp will not compile regar= dless > of the architecture or optimization flags -- the ICE is in GCC's > cp/cp-lang.c:130, due, it seems, to the initialization complexity. Can't > think of a workaround :-\ >=20 > Yours, >=20 > -mi >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --=20 Eirik Nygaard PGP Key: 83C55EDE --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9e5rn1JB0Z4PFXt4RAgSUAKCZmm98j1CiMwb5V5qZAESeMG8X1gCfR1aP 1KDIKY2mvvj048tQfc1k14w= =Hqok -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 11:48:58 2002 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 5E04B37B400 for ; Sun, 8 Sep 2002 11:48:56 -0700 (PDT) Received: from nic.upatras.gr (nic.upatras.gr [150.140.129.30]) by mx1.FreeBSD.org (Postfix) with SMTP id 61F9D43E6E for ; Sun, 8 Sep 2002 11:48:54 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: (qmail 22976 invoked from network); 8 Sep 2002 18:42:12 -0000 Received: from upnet-dialinpool-53.upatras.gr (HELO hades.hell.gr) (150.140.128.201) by nic.upatras.gr with SMTP; 8 Sep 2002 18:42:12 -0000 Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.6/8.12.6) with ESMTP id g88ImbSJ000806 for ; Sun, 8 Sep 2002 21:48:42 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.6/8.12.6/Submit) id g88DuY2a065067; Sun, 8 Sep 2002 16:56:34 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 8 Sep 2002 16:56:34 +0300 From: Giorgos Keramidas To: Riccardo Torrini Cc: freebsd-current@FreeBSD.org Subject: Re: Unable to buildworld (new record, 18") Message-ID: <20020908135634.GA64781@hades.hell.gr> References: <20020907215522.GE9987@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: Riccardo Torrini wrote: > > After some unsuccesfull buildworld I tryed updating includes but got > the same error. May be because my -CURRENT is pre-gcc_3.1 ? > Can I (Must I?) upgrade to an intermediate version between May and now? There have been at least two gcc upgrades since then. I believe the easiest way to upgrade to today's -current would be to install a fairly recent snapshot from http://snapshots.jp.FreeBSD.org/ instead of trying to debug the many ways in which a buildworld can fail. - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 12:43: 6 2002 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 9EF4237B400; Sun, 8 Sep 2002 12:43:03 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83DFD43E3B; Sun, 8 Sep 2002 12:42:53 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.11.6/8.11.6) with ESMTP id g88JgLs45853; Sun, 8 Sep 2002 22:42:34 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.5/8.12.5) with ESMTP id g88JgQdO009954; Sun, 8 Sep 2002 22:42:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.5/8.12.5/Submit) id g88JgPdZ009953; Sun, 8 Sep 2002 22:42:25 +0300 (EEST) Date: Sun, 8 Sep 2002 22:42:25 +0300 From: Maxim Sobolev To: Mikhail Teterin Cc: current@FreeBSD.ORG, kde@FreeBSD.ORG, kan@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: troubles with the new GCC -- anyone else? Message-ID: <20020908194225.GB9892@vega.vega.com> References: <200209081429.43386@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200209081429.43386@aldan> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 02:30:06PM -0400, Mikhail Teterin wrote: > Is it just me, or do others have troubles too? I upgraded yesterday: > > mi@celsius:~ (101) cc -v > Using built-in specs. > Configured with: FreeBSD/i386 system compiler > Thread model: posix > gcc version 3.2.1 [FreeBSD] 20020901 (prerelease) > > With ``-march=pentium2 -mmmx'' > > . there is a file or two in XFree86-4-Server, that cause an Internal Compiler > Error -- fixed with ``-march=pentium2 -mno-mmx'' (same trouble existed with > the previous version, AFAIR) > > . one file in libiconv causes ICE -- the workaround above does not work. But > ``-march=pentium -mmmx'' works. > > . in the kdelibs3, the kdecore/kkeyserver_x11.cpp will not compile regardless > of the architecture or optimization flags -- the ICE is in GCC's > cp/cp-lang.c:130, due, it seems, to the initialization complexity. Can't > think of a workaround :-\ Please submit preprocessed sources which trigger ICE to GCC's problem reporting database. There is very little (if anything at all) FreeBSD developers could and should do to help you with that. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 12:54:39 2002 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 BF64437B400 for ; Sun, 8 Sep 2002 12:54:36 -0700 (PDT) Received: from mail.dada.it (mail3.dada.it [195.110.100.3]) by mx1.FreeBSD.org (Postfix) with SMTP id E0B2843E42 for ; Sun, 8 Sep 2002 12:54:30 -0700 (PDT) (envelope-from riccardo@torrini.org) Received: (qmail 1441 invoked from network); 8 Sep 2002 19:54:22 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 8 Sep 2002 19:54:22 -0000 Received: from trudy.torrini.home (localhost.torrini.home [127.0.0.1]) by torrini.org (8.12.3/8.12.3) with ESMTP id g88JsJZv073056; Sun, 8 Sep 2002 21:54:19 +0200 (CEST) (envelope-from riccardo@trudy.torrini.home) Received: (from riccardo@localhost) by trudy.torrini.home (8.12.3/8.12.3/Submit) id g88JsHjj073039; Sun, 8 Sep 2002 21:54:17 +0200 (CEST) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020908135634.GA64781@hades.hell.gr> Date: Sun, 08 Sep 2002 21:54:17 +0200 (CEST) From: Riccardo Torrini To: Giorgos Keramidas Subject: Re: Unable to buildworld (new record, 18") Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Sep-2002 (13:56:34/GMT) Giorgos Keramidas wrote: > There have been at least two gcc upgrades since then. I believe the > easiest way to upgrade to today's -current would be to install a > fairly recent snapshot from http://snapshots.jp.FreeBSD.org/ instead > of trying to debug the many ways in which a buildworld can fail. I'm obstinate :) I have tryed with a middle version (1 jul 2002) but it fails without and with make includes before build, now I'm trying with cvsup from 15 aug 2002 (as written by Munish Chopra on 1 sep: IIRC current was in good shape between August 12-15, 17, 18, 22-24) and it is still compiling (I'm crossing fingers)... If it complete (I hope it complete) is -CURRENT of 15 aug 2002 a reasonable version to install and to use to jump to today ones? Any comment? Thanks again, Riccardo. PS: It stopped on stage 4:libraries, something about crypt, now is running again with -DNO_WERROR -DNOCLEAN -DNOCRYPT ;^) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 13: 6:43 2002 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 1B56437B400 for ; Sun, 8 Sep 2002 13:06:41 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BDDF43E77 for ; Sun, 8 Sep 2002 13:06:40 -0700 (PDT) (envelope-from adam@blacktabby.org) Received: from emmenthaler.blacktabby.org ([12.240.109.159]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020908200640.SWNZ9751.sccrmhc01.attbi.com@emmenthaler.blacktabby.org> for ; Sun, 8 Sep 2002 20:06:40 +0000 Received: from cheshire.blacktabby.org (cheshire.blacktabby.org [192.168.1.198]) by emmenthaler.blacktabby.org (Postfix) with SMTP id EE1E93B23 for ; Sun, 8 Sep 2002 13:06:38 -0700 (PDT) Date: Sun, 8 Sep 2002 13:06:32 -0700 From: Adam Kranzel To: current@freebsd.org Subject: Termcap broken? Message-Id: <20020908130632.5d429828.adam@blacktabby.org> X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi... I'm getting the error "Terminal must backspace." when trying to run Slash'EM (a Nethack-derived game). I'm not sure what's gotten broken, but if I copy over the termcap and termcap.db from a 4.6-STABLE machine (of mid-August), it works again. Any suggestions on how to fix this? My TERM environment variable is set to "xterm-color" right now, but changing it to "xterm" doesn't seem to make a difference. thanks -Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 13:13:33 2002 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 2EEE937B400; Sun, 8 Sep 2002 13:13:31 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A1C443E4A; Sun, 8 Sep 2002 13:13:30 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C553466C4E; Sun, 8 Sep 2002 13:13:29 -0700 (PDT) Date: Sun, 8 Sep 2002 13:13:29 -0700 From: Kris Kennaway To: Mikhail Teterin Cc: current@FreeBSD.org, kde@FreeBSD.org, kan@FreeBSD.org, obrien@FreeBSD.org Subject: Re: troubles with the new GCC -- anyone else? Message-ID: <20020908201329.GA24581@xor.obsecurity.org> References: <200209081429.43386@aldan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <200209081429.43386@aldan> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Sep 08, 2002 at 02:30:06PM -0400, Mikhail Teterin wrote: > Is it just me, or do others have troubles too? I upgraded yesterday: Did you try the gcc patch Alexander posted the other day? Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9e69oWry0BWjoQKURAovlAJ9U78+Zekm7elpBXbDMZYf0eEpzZgCfe8uD 9AJL7NENcNi413jTKQCl7zo= =vW4l -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 13:15:47 2002 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 6FB0337B401; Sun, 8 Sep 2002 13:15:43 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 001BB43E42; Sun, 8 Sep 2002 13:15:42 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5EAEB66C4E; Sun, 8 Sep 2002 13:15:42 -0700 (PDT) Date: Sun, 8 Sep 2002 13:15:42 -0700 From: Kris Kennaway To: Eirik Nygaard Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: 5.0 package build with gcc32 complete (HELP NEEDED!!) Message-ID: <20020908201542.GB24581@xor.obsecurity.org> References: <20020906185816.GA75066@xor.obsecurity.org> <20020908101841.GA34010@eirikn.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline In-Reply-To: <20020908101841.GA34010@eirikn.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Sep 08, 2002 at 12:18:41PM +0200, Eirik Nygaard wrote: > I got some free time on my hands and will try to fix some ports, already fixed sysutils/logmon. Thanks! Kris --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9e6/tWry0BWjoQKURArlpAKC1fIozaqijSUsDxg9bvTjntH/nBgCgxXWI MSEgnwKB+9vWxTSxBWvP6SE= =D4Ld -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 14: 2:10 2002 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 2F1A737B400 for ; Sun, 8 Sep 2002 14:02:08 -0700 (PDT) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id A987A43E75 for ; Sun, 8 Sep 2002 14:02:07 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0291.cvx21-bradley.dialup.earthlink.net ([209.179.193.36] helo=mindspring.com) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17o9By-0002RD-00; Sun, 08 Sep 2002 14:02:03 -0700 Message-ID: <3D7BBA8C.4081BB77@mindspring.com> Date: Sun, 08 Sep 2002 14:01:00 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Adam Kranzel Cc: current@freebsd.org Subject: Re: Termcap broken? References: <20020908130632.5d429828.adam@blacktabby.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Adam Kranzel wrote: > I'm getting the error "Terminal must backspace." when trying to run > Slash'EM (a Nethack-derived game). I'm not sure what's gotten broken, > but if I copy over the termcap and termcap.db from a 4.6-STABLE machine > (of mid-August), it works again. Any suggestions on how to fix this? > My TERM environment variable is set to "xterm-color" right now, but > changing it to "xterm" doesn't seem to make a difference. The best thing to do would be to look at the source code for the program, and see what is making it spit out the message, and figure out how to correct that. One common issue in this are is terminals whose left arrow emits ASCII BS (^H) instead of having a seperate escape sequence (e.g. Televideo, Wyse, Hazeltine terminals). Another is people who define the PC console backspace key to send ASCII DEL instead of ASCII BS. The last is when there is no such thing as a backspace that is non-destructive (e.g. some terminals do not allow you to use ASCII BS sent to the terminal to move the curosr left, without actually erasing the character under the cursor). Like I said: look at the code, and find out what entries make it emit the error message that you are seeing. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 16:26:18 2002 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 D7C5237B401 for ; Sun, 8 Sep 2002 16:26:11 -0700 (PDT) Received: from Stalker.alfacom.net (Stalker.Alfacom.net [193.108.124.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BCDF43E42 for ; Sun, 8 Sep 2002 16:26:08 -0700 (PDT) (envelope-from vkushnir@alfacom.net) Received: from kushnir1.kiev.ua (124-137.dialup.Alfacom.net [193.108.124.137]) by Stalker.alfacom.net (8.12.5/8.12.5) with ESMTP id g88NPlZW004881; Mon, 9 Sep 2002 02:25:51 +0300 (EEST) Received: from kushnir1.kiev.ua (localhost [127.0.0.1]) by kushnir1.kiev.ua (8.12.6/8.12.2) with ESMTP id g88NPJcf055313; Mon, 9 Sep 2002 02:25:19 +0300 (EEST) (envelope-from vkushnir@alfacom.net) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.12.6/8.12.6/Submit) with ESMTP id g88NOB4E055307; Mon, 9 Sep 2002 02:24:38 +0300 (EEST) X-Authentication-Warning: kushnir1.kiev.ua: volodya owned process doing -bs Date: Mon, 9 Sep 2002 02:24:09 +0300 (EEST) From: Vladimir Kushnir X-X-Sender: volodya@kushnir1.kiev.ua To: Andrew Lankford Cc: current@FreeBSD.ORG Subject: Re: syscons in rcng ? - SOLVED In-Reply-To: <20020908172908.XRWX18399.out012.verizon.net@verizon.net> Message-ID: <20020909022140.W54490-100000@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 8 Sep 2002, Andrew Lankford wrote: > > What I've noticed is that vidcontrol refuses to change the console mode > to anything other than 80x25 or 80x30. I had it set at 80x60, but CURRENT > no longer likes that. I've also noticed that starting up XFree4.2.0's server > switches my console from 80x30 back to 80x25. Funky. > > In any case, I don't know anything about problems with /etc/rc.d/syscons, > but perhaps vidcontrol or the kernel is the culprit. > > Andrew Lankford > > >Hello, > > > >With the latest changes (1.8, 5th of Sep) to /etc/rc.d/syscons, syscons > >doesn't get initialized on my 5.0-CURRENT. > > > >Have I missed some new configuration options? > > > > > Very simple: /usr/src/etc/rc.d/syscons misses line run_rc_command "$1" Regards, Vladimir -- Vladimir Kushnir - vkushnir@Alfacom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 19:23:10 2002 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 C91A037B400 for ; Sun, 8 Sep 2002 19:23:07 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FD9B43E3B for ; Sun, 8 Sep 2002 19:23:07 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g892N7YB032613 for ; Sun, 8 Sep 2002 19:23:07 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g892N675032611 for current@freebsd.org; Sun, 8 Sep 2002 19:23:06 -0700 (PDT) Date: Sun, 8 Sep 2002 19:23:06 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209090223.g892N675032611@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Sun Sep 8 18:17:50 PDT 2002 -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Sun Sep 8 19:23:03 PDT 2002 -------------------------------------------------------------- >>> Kernel build for LINT started on Sun Sep 8 19:23:04 PDT 2002 -------------------------------------------------------------- ===> LINT config: Error: device "apm_saver" is unknown config: Error: device "cy" is unknown config: Error: device "cy" does not take a count config: 3 errors WARNING: kernel contains GPL contaminated ext2fs filesystem FYI: static unit limits for vcoda are set: NVCODA=4 FYI: static unit limits for dgb are set: NDGB=1 FYI: static unit limits for card are set: NCARD=1 FYI: static unit limits for meteor are set: NMETEOR=1 *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 19:59: 9 2002 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 C6F2937B400 for ; Sun, 8 Sep 2002 19:59:07 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E8FE43E4A for ; Sun, 8 Sep 2002 19:59:07 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g892x1fO025419; Sun, 8 Sep 2002 19:59:01 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g892x1ZU025418; Sun, 8 Sep 2002 19:59:01 -0700 (PDT) Date: Sun, 8 Sep 2002 19:59:01 -0700 From: "David O'Brien" To: Craig Rodrigues Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] C++ fix for flex Message-ID: <20020909025901.GA25313@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020907235508.A6911@attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020907235508.A6911@attbi.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 07, 2002 at 11:55:08PM -0400, Craig Rodrigues wrote: > Hi, > > As I am fixing some of the C++ ports for GCC 3.2, I found a problem with lex. > The following patch is required for lex to generate code which > can compile with GCC 3.2. It applies to /usr/src/usr.bin/lex Committed. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 20:50:29 2002 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 07E9B37B400; Sun, 8 Sep 2002 20:50:24 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73DFB43E3B; Sun, 8 Sep 2002 20:50:23 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id g893oHVo062195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 8 Sep 2002 23:50:17 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id g893oHMs062192; Sun, 8 Sep 2002 23:50:17 -0400 (EDT) (envelope-from wollman) Date: Sun, 8 Sep 2002 23:50:17 -0400 (EDT) From: Garrett Wollman Message-Id: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> To: current@FreeBSD.org Cc: kan@FreeBSD.org Subject: No way to tell when `long long' is or is not supported? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG GCC used to define a macro __STRICT_ANSI__ when `-ansi' was given on the command line. The current version does not do this, which breaks detection of whether `long long' is allowed. (For some reason this is not hit in -current builds, but I have made some fixes to which trigger it in every program which sets WARNS.) Rather than trying to deduce whether `long long' is supported from other macros, I simply modified the compiler driver to tell us. (BTW, the `-posix' flag is utterly useless and should go.) If anyone has a better way to accomplish this, I'm all ears. (I suspect that the removal of __STRICT_ANSI__ was intentional, since it's not clear what that should mean in the face of multiple C language standards. The trouble is that C89 (implied by `-ansi') is otherwise indistinguishable from C89+GCC-extensions (implied by the absence of `-ansi'), and we need to make both cases work properly.) -GAWollman Index: freebsd-spec.h =================================================================== RCS file: /home/ncvs/src/contrib/gcc/config/freebsd-spec.h,v retrieving revision 1.2 diff -u -r1.2 freebsd-spec.h --- freebsd-spec.h 10 May 2002 19:05:07 -0000 1.2 +++ freebsd-spec.h 8 Sep 2002 18:34:29 -0000 @@ -85,12 +85,13 @@ the final CPP_PREDEFINES value. */ #define FBSD_CPP_PREDEFINES \ - "-D__FreeBSD__=5 -D__FreeBSD_cc_version=500003 -Dunix -D__KPRINTF_ATTRIBUTE__ -Asystem=unix -Asystem=bsd -Asystem=FreeBSD" + "-D__FreeBSD__=5 -D__FreeBSD_cc_version=500004 -Dunix -D__KPRINTF_ATTRIBUTE__ -Asystem=unix -Asystem=bsd -Asystem=FreeBSD" #endif /* ! FREEBSD_NATIVE */ /* Provide a CPP_SPEC appropriate for FreeBSD. We just deal with the GCC - option `-posix', and PIC issues. */ + option `-posix', and PIC issues. Also deal with the problem of + detecting support for the `long long' type. */ #define FBSD_CPP_SPEC " \ %(cpp_cpu) \ @@ -98,6 +99,8 @@ %{munderscores: -D__UNDERSCORES__} \ %{maout: %{!mno-underscores: -D__UNDERSCORES__}} \ %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} \ + %{!ansi:%{!std=*:-D__LONG_LONG_SUPPORTED}%{std=gnu*:-D__LONG_LONG_SUPPORTED}}\ + %{std=c99:-D__LONG_LONG_SUPPORTED}\ %{posix:-D_POSIX_SOURCE}" /* Provide a STARTFILE_SPEC appropriate for FreeBSD. Here we add To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 21:15: 8 2002 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 E796F37B400 for ; Sun, 8 Sep 2002 21:15:05 -0700 (PDT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5FCC43E4A for ; Sun, 8 Sep 2002 21:15:04 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g894Ea311484; Mon, 9 Sep 2002 13:14:37 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200209081705.g88H58Mp057226@zibbi.icomtek.csir.co.za> References: <20020908114240.GA50562@alaska.cert.siemens.de> <200209081705.g88H58Mp057226@zibbi.icomtek.csir.co.za> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (bamboo) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 13 From: Makoto Matsushita To: jhay@icomtek.csir.co.za Subject: Re: Release building broken for -current Date: Mon, 09 Sep 2002 13:14:34 +0900 Message-Id: <20020909131434A.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG jhay> md5 died on zero length files. You will have to upgrade the machine or jhay> at least do a buildworld with new source before you try a release again. Ya, that's exactly the problem on my buildbox... Thank you for the info. But if new md5(1) doesn't used by during a release, it's yet another similar problem to be fixed, since current "make release" don't (actually, cannot) update its own chroot sandbox before starting final release procedures... -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 8 23:29: 5 2002 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 6F70E37B400; Sun, 8 Sep 2002 23:29:02 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB1043E72; Sun, 8 Sep 2002 23:29:01 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g896Spau070784; Mon, 9 Sep 2002 10:28:54 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g896Sn87070782; Mon, 9 Sep 2002 10:28:49 +0400 (MSD) (envelope-from ache) Date: Mon, 9 Sep 2002 10:28:47 +0400 From: "Andrey A. Chernov" To: current@freebsd.org, peter@freebsd.org Subject: Ncurses official patch to solve xterm ac= problem, please commit. Message-ID: <20020909062845.GA70763@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This patch comes from Thomas. Please commit it to solve missing ACS characters problem with recent XFree entries termcap spam. -------------------------------------------------------------------- This is the change I made to comp_parse.c (compare with similar logic in parse_entry.c): Index: ncurses/tinfo/comp_parse.c Prereq: 1.51 --- ncurses-5.2-20020824+/ncurses/tinfo/comp_parse.c Sat Aug 10 20:59:06 2002 +++ ncurses-5.2-20020901/ncurses/tinfo/comp_parse.c Sat Aug 31 13:14:56 2002 @@ -52,7 +52,7 @@ #include #include -MODULE_ID("$Id: comp_parse.c,v 1.51 2002/08/11 00:59:06 tom Exp $") +MODULE_ID("$Id: comp_parse.c,v 1.52 2002/08/31 17:14:56 tom Exp $") static void sanity_check(TERMTYPE *); NCURSES_IMPEXP void NCURSES_API(*_nc_check_termtype) (TERMTYPE *) = sanity_check; @@ -81,8 +81,8 @@ NCURSES_EXPORT_VAR(ENTRY *) _nc_head = 0; NCURSES_EXPORT_VAR(ENTRY *) _nc_tail = 0; - static void - enqueue(ENTRY * ep) +static void +enqueue(ENTRY * ep) /* add an entry to the in-core list */ { ENTRY *newp = _nc_copy_entry(ep); @@ -461,9 +461,17 @@ || PRESENT(enter_reverse_mode))) _nc_warning("no exit_attribute_mode"); #endif /* __UNUSED__ */ - PAIRED(enter_standout_mode, exit_standout_mode) - PAIRED(enter_underline_mode, exit_underline_mode) + PAIRED(enter_standout_mode, exit_standout_mode); + PAIRED(enter_underline_mode, exit_underline_mode); } + + /* we do this check/fix in postprocess_termcap(), but some packagers + * prefer to bypass it... + */ + if (acs_chars == 0 + && enter_alt_charset_mode != 0 + && exit_alt_charset_mode != 0) + acs_chars = strdup(VT_ACSC); /* listed in structure-member order of first argument */ PAIRED(enter_alt_charset_mode, exit_alt_charset_mode); -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------------------------------------------------------------- -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 0: 7: 4 2002 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 7291837B400; Mon, 9 Sep 2002 00:07:02 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E1243E75; Mon, 9 Sep 2002 00:07:02 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g89771fO027199; Mon, 9 Sep 2002 00:07:01 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g89770vs027183; Mon, 9 Sep 2002 00:07:00 -0700 (PDT) Date: Mon, 9 Sep 2002 00:07:00 -0700 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.org, kan@FreeBSD.org Subject: Re: No way to tell when `long long' is or is not supported? Message-ID: <20020909070700.GA26978@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Garrett Wollman , current@FreeBSD.org, kan@FreeBSD.org References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 11:50:17PM -0400, Garrett Wollman wrote: > GCC used to define a macro __STRICT_ANSI__ when `-ansi' was given on > the command line. The current version does not do this, It seems to work for me: $ cat foo.c #ifdef __STRICT_ANSI__ #error __STRICT_ANSI__ #endif $ /usr/bin/cc -ansi foo.c foo.c:2:2: #error __STRICT_ANSI__ The problem is it is also set for this: $ /usr/bin/cc -std=c99 foo.c foo.c:2:2: #error __STRICT_ANSI__ As you mentioned, this is now not a good test to decide if 'long long' is supported. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 0:51:55 2002 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 8ECCD37B401 for ; Mon, 9 Sep 2002 00:51:49 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4962C43E6A for ; Mon, 9 Sep 2002 00:51:48 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g897pWEs022740; Mon, 9 Sep 2002 09:51:32 +0200 Received: (nullmailer pid 941 invoked by uid 1000); Mon, 09 Sep 2002 06:36:16 -0000 Date: Mon, 9 Sep 2002 08:36:16 +0200 From: Mark Santcroos To: John Angelmo Cc: current@FreeBSD.ORG Subject: Re: apm support Message-ID: <20020909063616.GA887@laptop.6bone.nl> References: <20020907192910.575335e7.john@veidit.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020907192910.575335e7.john@veidit.net> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 07, 2002 at 07:29:10PM +0200, John Angelmo wrote: > Hello > > I'm trying to get some apm support on my laptop. > I have device apm in my kernelconf > and apm_enable="YES" in rc.conf > > but when I run apm I get: > $ apm > APM version: 1.2 > APM Managment: Enabled > AC Line status: on-line > Battery status: unknown > Remaining battery life: 100% > Remaining battery time: unknown > Number of batteries: 1 > Battery 0: > Battery status: unknown > Remaining battery life: 100% > Remaining battery time: 0:00:00 > APM Capabilities: > unknown > > > what could I be missing? That's a good question! What gives you the idea something is wrong here? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 1:10:49 2002 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 5138637B400; Mon, 9 Sep 2002 01:10:47 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC8543E65; Mon, 9 Sep 2002 01:10:46 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g898AkfO054921; Mon, 9 Sep 2002 01:10:46 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g898AkRf054920; Mon, 9 Sep 2002 01:10:46 -0700 (PDT) Date: Mon, 9 Sep 2002 01:10:46 -0700 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.org, kan@FreeBSD.org Subject: Re: No way to tell when `long long' is or is not supported? Message-ID: <20020909081046.GB26978@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Garrett Wollman , current@FreeBSD.org, kan@FreeBSD.org References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 11:50:17PM -0400, Garrett Wollman wrote: > Rather than trying to deduce whether `long long' is supported from > other macros, I simply modified the compiler driver to tell us. Looking at GCC on other platforms, "_LONGLONG" seems to be the most preferred symbol. How does this patch look? We can't get this 100% correct as there is no way to match "iso9899:1990" and "iso9899:199409" as ':' is a token already. The only way to do this correctly is to add it to c-common.c and c-opt.c looking at the value of the various "flag_iso*" variables. Index: freebsd-spec.h =================================================================== RCS file: /home/ncvs/src/contrib/gcc/config/freebsd-spec.h,v retrieving revision 1.3 diff -u -r1.3 freebsd-spec.h --- freebsd-spec.h 9 Sep 2002 06:56:29 -0000 1.3 +++ freebsd-spec.h 9 Sep 2002 07:23:58 -0000 @@ -98,6 +105,7 @@ %{munderscores: -D__UNDERSCORES__} \ %{maout: %{!mno-underscores: -D__UNDERSCORES__}} \ %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} \ + %{!ansi:%{!std=c89:%{!std=iso9899.1990:%{!std=iso9899.199409:-D_LONGLONG}}}}\ %{posix:-D_POSIX_SOURCE}" /* Provide a STARTFILE_SPEC appropriate for FreeBSD. Here we add To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 1:50:28 2002 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 67E5D37B400 for ; Mon, 9 Sep 2002 01:50:26 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14CEF43E3B for ; Mon, 9 Sep 2002 01:50:26 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0118.cvx22-bradley.dialup.earthlink.net ([209.179.198.118] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17oKFQ-0007Yh-00; Mon, 09 Sep 2002 01:50:20 -0700 Message-ID: <3D7C608C.118BE344@mindspring.com> Date: Mon, 09 Sep 2002 01:49:16 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Santcroos Cc: John Angelmo , current@FreeBSD.ORG Subject: Re: apm support References: <20020907192910.575335e7.john@veidit.net> <20020909063616.GA887@laptop.6bone.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Santcroos wrote: > On Sat, Sep 07, 2002 at 07:29:10PM +0200, John Angelmo wrote: > > I'm trying to get some apm support on my laptop. > > I have device apm in my kernelconf > > and apm_enable="YES" in rc.conf > > > > but when I run apm I get: [ ... ] > > what could I be missing? > > That's a good question! What gives you the idea something is wrong here? I will guess, which may save some turnaround time for the messages, that it's these specific line items: > > Battery status: unknown > > Remaining battery time: unknown > > Battery 0: > > Battery status: unknown > > Remaining battery time: 0:00:00 > > APM Capabilities: > > unknown -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 1:56:48 2002 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 1E66737B400 for ; Mon, 9 Sep 2002 01:56:47 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D24643E4A for ; Mon, 9 Sep 2002 01:56:46 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g898ujEs012516; Mon, 9 Sep 2002 10:56:45 +0200 Received: (nullmailer pid 1719 invoked by uid 1000); Mon, 09 Sep 2002 08:56:08 -0000 Date: Mon, 9 Sep 2002 10:56:07 +0200 From: Mark Santcroos To: John Angelmo Cc: current@FreeBSD.ORG Subject: Re: apm support Message-ID: <20020909085607.GA743@laptop.6bone.nl> References: <20020907192910.575335e7.john@veidit.net> <20020909063616.GA887@laptop.6bone.nl> <3D7C608C.118BE344@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D7C608C.118BE344@mindspring.com> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1034 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Battery status: unknown > > > Remaining battery time: unknown > > > Battery 0: > > > Battery status: unknown > > > Remaining battery time: 0:00:00 > > > APM Capabilities: > > > unknown What does: 'sysctl -a hw.acpi' show? And what does the 'apm' command show when you unplug your AC? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 2:15:50 2002 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 D8B9237B400 for ; Mon, 9 Sep 2002 02:15:46 -0700 (PDT) Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B60D843E65 for ; Mon, 9 Sep 2002 02:15:45 -0700 (PDT) (envelope-from john@veidit.net) Received: from d1o1000.telia.com (d1o1000.telia.com [217.208.12.241]) by maile.telia.com (8.12.5/8.12.5) with ESMTP id g899Fin1023698; Mon, 9 Sep 2002 11:15:44 +0200 (CEST) X-Original-Recipient: current@FreeBSD.ORG Received: from Sleeper (h60n2fls35o1000.telia.com [217.210.235.60]) by d1o1000.telia.com (8.10.2/8.10.1) with SMTP id g899FhR12557; Mon, 9 Sep 2002 11:15:44 +0200 (CEST) Date: Mon, 9 Sep 2002 11:15:43 +0200 From: John Angelmo To: Mark Santcroos Cc: current@FreeBSD.ORG Subject: Re: apm support Message-Id: <20020909111543.55dbac6f.john@veidit.net> In-Reply-To: <20020909085607.GA743@laptop.6bone.nl> References: <20020907192910.575335e7.john@veidit.net> <20020909063616.GA887@laptop.6bone.nl> <3D7C608C.118BE344@mindspring.com> <20020909085607.GA743@laptop.6bone.nl> X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002 10:56:07 +0200 Mark Santcroos wrote: > > > > Battery status: unknown > > > > Remaining battery time: unknown > > > > Battery 0: > > > > Battery status: unknown > > > > Remaining battery time: 0:00:00 > > > > APM Capabilities: > > > > unknown > > What does: 'sysctl -a hw.acpi' show? sysctl -a hw.acpi hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.acline: 1 hw.acpi.battery.life: 98 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 > And what does the 'apm' command show when you unplug your AC? > Plugged out and then plugged in right after that: -bash-2.05b$ apm APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: charging Remaining battery life: invalid value (0xffffffff) Remaining battery time: unknown Number of batteries: 1 Battery 0: Battery status: not present APM Capabilities: unknown -bash-2.05b$ apm APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: high Remaining battery life: 92% Remaining battery time: 3:03:00 Number of batteries: 1 Battery 0: Battery status: high Remaining battery life: 92% Remaining battery time: 3:03:00 APM Capabilities: unknown -bash-2.05b$ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 2:25: 5 2002 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 2ED8237B400 for ; Mon, 9 Sep 2002 02:25:03 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AED143E65 for ; Mon, 9 Sep 2002 02:25:02 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g899P0Es022784; Mon, 9 Sep 2002 11:25:01 +0200 Received: (nullmailer pid 2031 invoked by uid 1000); Mon, 09 Sep 2002 09:24:23 -0000 Date: Mon, 9 Sep 2002 11:24:23 +0200 From: Mark Santcroos To: John Angelmo Cc: current@FreeBSD.ORG Subject: Re: apm support Message-ID: <20020909092423.GA1962@laptop.6bone.nl> References: <20020907192910.575335e7.john@veidit.net> <20020909063616.GA887@laptop.6bone.nl> <3D7C608C.118BE344@mindspring.com> <20020909085607.GA743@laptop.6bone.nl> <20020909111543.55dbac6f.john@veidit.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020909111543.55dbac6f.john@veidit.net> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: > > > > > Battery status: unknown > > > > > Remaining battery time: unknown > > > > > Battery 0: > > > > > Battery status: unknown > > > > > Remaining battery time: 0:00:00 These were all zero because you were plugged in, as you showed the values were showed when you were unplugged. > > > > > APM Capabilities: > > > > > unknown This is explained by the fact that you run ACPI. Afaik it's either ACPI or APM that your laptop has. Yours has ACPI. The reason that you can still use the 'apm' command is that the ACPI driver 'emulates' the behaviour of /dev/apm, but the information is not actually coming from apm. (Can you remove device apm from your kernel to ack this?) What laptop do you have btw? And how is the suspending/resuming working? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 2:30: 3 2002 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 0B54737B400 for ; Mon, 9 Sep 2002 02:29:59 -0700 (PDT) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3961943E6E for ; Mon, 9 Sep 2002 02:29:58 -0700 (PDT) (envelope-from john@veidit.net) Received: from d1o1000.telia.com (d1o1000.telia.com [217.208.12.241]) by mailb.telia.com (8.12.5/8.12.5) with ESMTP id g899TuAe000824; Mon, 9 Sep 2002 11:29:56 +0200 (CEST) X-Original-Recipient: current@FreeBSD.ORG Received: from veidit.net (h60n2fls35o1000.telia.com [217.210.235.60]) by d1o1000.telia.com (8.10.2/8.10.1) with ESMTP id g899TuR15892; Mon, 9 Sep 2002 11:29:56 +0200 (CEST) Message-ID: <3D7C69E7.8030700@veidit.net> Date: Mon, 09 Sep 2002 11:29:11 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: Mark Santcroos Cc: current@FreeBSD.ORG Subject: Re: apm support References: <20020907192910.575335e7.john@veidit.net> <20020909063616.GA887@laptop.6bone.nl> <3D7C608C.118BE344@mindspring.com> <20020909085607.GA743@laptop.6bone.nl> <20020909111543.55dbac6f.john@veidit.net> <20020909092423.GA1962@laptop.6bone.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Santcroos wrote: > On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: > >>>>>>Battery status: unknown >>>>>>Remaining battery time: unknown >>>>>>Battery 0: >>>>>> Battery status: unknown >>>>>> Remaining battery time: 0:00:00 >>>>> > > These were all zero because you were plugged in, as you showed the values > were showed when you were unplugged. > > >>>>>>APM Capabilities: >>>>>> unknown >>>>> > > This is explained by the fact that you run ACPI. Afaik it's either ACPI or > APM that your laptop has. Yours has ACPI. > > The reason that you can still use the 'apm' command is that the ACPI > driver 'emulates' the behaviour of /dev/apm, but the information is not > actually coming from apm. > (Can you remove device apm from your kernel to ack this?) > > What laptop do you have btw? http://www.fujitsu-siemens.com/rl/products/notebooks/professional/lifebook/lifebookc/lifebookc.html But with an older Celeron 800Mhz > And how is the suspending/resuming working? Great in Windows, not at all in FreeBSD, well the screen goes blank but not black, (no power off to the screen) after 15 minutes. /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 2:42:46 2002 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 7736437B400; Mon, 9 Sep 2002 02:42:45 -0700 (PDT) Received: from smtp.sw.oz.au (smtp.sw.oz.au [203.31.96.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FF2343E42; Mon, 9 Sep 2002 02:42:43 -0700 (PDT) (envelope-from vance@aurema.com) Received: (from vance@localhost) by smtp.sw.oz.au (8.8.8+Sun/8.8.8) id TAA13460; Mon, 9 Sep 2002 19:42:32 +1000 (EST) Date: Mon, 9 Sep 2002 19:42:32 +1000 From: Christopher Vance To: "David O'Brien" Cc: Garrett Wollman , current@FreeBSD.ORG, kan@FreeBSD.ORG Subject: Re: No way to tell when `long long' is or is not supported? Message-ID: <20020909194232.A25660@aurema.com> References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> <20020909081046.GB26978@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020909081046.GB26978@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Sep 09, 2002 at 01:10:46AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 09, 2002 at 01:10:46AM -0700, David O'Brien wrote: : > Rather than trying to deduce whether `long long' is supported from : > other macros, I simply modified the compiler driver to tell us. What's wrong with #include #ifdef LLONG_MAX Surely we get to determine the contents of our own limits.h files? -- Christopher Vance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 3: 6:50 2002 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 6FCA137B400; Mon, 9 Sep 2002 03:06:46 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0524C43E3B; Mon, 9 Sep 2002 03:06:45 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA09758; Mon, 9 Sep 2002 20:06:39 +1000 Date: Mon, 9 Sep 2002 20:14:08 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "David O'Brien" Cc: Garrett Wollman , , Subject: Re: No way to tell when `long long' is or is not supported? In-Reply-To: <20020909070700.GA26978@dragon.nuxi.com> Message-ID: <20020909195812.E6306-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, David O'Brien wrote: > On Sun, Sep 08, 2002 at 11:50:17PM -0400, Garrett Wollman wrote: > > GCC used to define a macro __STRICT_ANSI__ when `-ansi' was given on > > the command line. The current version does not do this, > > It seems to work for me: For me too. I vaguely remember that it didn't work for all cases, but I can't find any broken case now (perhaps gcc-3.2 unbroke it). > The problem is it is also set for this: > > $ /usr/bin/cc -std=c99 foo.c > foo.c:2:2: #error __STRICT_ANSI__ > > As you mentioned, this is now not a good test to decide if 'long long' is > supported. The __STDC_VERSION__ test in the XXX comment before the __STRICT_ANSI__ ifdef works for -std=c99. A messy ifdef to handle old compilers seems to be unavoidable until we drop support for nonstandard (non-C90) features in old compilers. BTW, I'm still waiting for the bogus LONGLONG lint markup to be removed from stdlib.h. lint should warn about "long long" if and only if "ong long" is a syntax error for the compiler that lint is checking for. Lint must see the same value for __LONG_LONG_SUPPORTED as the relevant compiler would, and then the LONGLONG markup is a no-op. The markup mainly breaks detection of broken lints and/or broken setting of __LONG_LONG_SUPPORTED. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 3:45: 7 2002 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 0C3A737B400; Mon, 9 Sep 2002 03:45:05 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA14043E4A; Mon, 9 Sep 2002 03:45:03 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA13728; Mon, 9 Sep 2002 20:44:57 +1000 Date: Mon, 9 Sep 2002 20:52:38 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Christopher Vance Cc: "David O'Brien" , Garrett Wollman , , Subject: Re: No way to tell when `long long' is or is not supported? In-Reply-To: <20020909194232.A25660@aurema.com> Message-ID: <20020909204406.P6401-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Christopher Vance wrote: > On Mon, Sep 09, 2002 at 01:10:46AM -0700, David O'Brien wrote: > : > Rather than trying to deduce whether `long long' is supported from > : > other macros, I simply modified the compiler driver to tell us. > > What's wrong with > > #include > #ifdef LLONG_MAX > > Surely we get to determine the contents of our own limits.h files? 1) Namespace pollution. Standard headers other than are not permitted to define LLONG_MAX. 2) A non-broken would need much the same ifdefs as for determining whether the compiler and/or standard supports long long. is not permitted to define LLONG_MA if the standard is C90 but currently defines it unconditionally. The syntax error in the definition of LLONG_MAX doesn't cause many problems for C90 compilers because the macro is not normally used in C90 environment. A test like: #include #if LLONG_MAX > 0 would have syntax errors. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 6:47: 1 2002 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 0B4E537B400 for ; Mon, 9 Sep 2002 06:46:58 -0700 (PDT) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 648B043E42 for ; Mon, 9 Sep 2002 06:46:57 -0700 (PDT) (envelope-from ust@cert.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g89DSEt12600; Mon, 9 Sep 2002 15:28:14 +0200 (MEST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g89DSEx15002; Mon, 9 Sep 2002 15:28:14 +0200 (MEST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.12.6/8.12.6/Siemens CERT [ $Revision: 1.25 ]) with ESMTP id g89DSEPA068769; Mon, 9 Sep 2002 15:28:14 +0200 (CEST) (envelope-from ust@alaska.cert.siemens.de) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [127.0.0.1]) by alaska.cert.siemens.de (8.12.6/8.12.6/alaska [ $Revision: 1.14 ]) with ESMTP id g89DSDSL081205; Mon, 9 Sep 2002 15:28:13 +0200 (CEST) (envelope-from ust@alaska.cert.siemens.de) Received: (from ust@localhost) by alaska.cert.siemens.de (8.12.6/8.12.6/alaska [ $Revision: 1.3 ]) id g89DSA72081202; Mon, 9 Sep 2002 15:28:10 +0200 (CEST) (envelope-from ust) Date: Mon, 9 Sep 2002 15:28:10 +0200 From: Udo Schweigert To: John Hay Cc: freebsd-current@FreeBSD.ORG Subject: Re: Release building broken for -current Message-ID: <20020909132810.GA81152@alaska.cert.siemens.de> Mail-Followup-To: John Hay , freebsd-current@FreeBSD.ORG References: <20020908114240.GA50562@alaska.cert.siemens.de> <200209081705.g88H58Mp057226@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <200209081705.g88H58Mp057226@zibbi.icomtek.csir.co.za> X-Operating-System: FreeBSD 4.7-PRERELEASE User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 19:05:08 +0200, John Hay wrote: >> >> when bulding release on -current I get (since a couple of days): >> > >> rm -rf /R/stage/dists > >> mkdir -p /R/stage/dists > >> rolling base/base tarball > >> mtree: line 0: dumpdates: No such file or directory > >> *** Error code 1 > >> > >> Stop in /usr/src/release. >> >> Somehow dumpdates didn't get installed into >> /R/stage/trees/base/usr/share/examples/etc > > md5 died on zero length files. You will have to upgrade the machine or > at least do a buildworld with new source before you try a release again. > Yes, that fixed it. Thanks. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : udo.schweigert@siemens.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 6:59:18 2002 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 ACE0237B400 for ; Mon, 9 Sep 2002 06:59:14 -0700 (PDT) Received: from smtp0.adl1.internode.on.net (smtp0.adl1.internode.on.net [203.16.214.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D61743E6A for ; Mon, 9 Sep 2002 06:59:13 -0700 (PDT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp1469.qld.padsl.internode.on.net [150.101.178.188]) by smtp0.adl1.internode.on.net (8.12.4/8.12.4) with ESMTP id g89Dx9eM030069; Mon, 9 Sep 2002 23:29:09 +0930 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.11.6/8.11.6) with ESMTP id g89Dx8t12523; Mon, 9 Sep 2002 23:59:09 +1000 (EST) (envelope-from mckay) Message-Id: <200209091359.g89Dx8t12523@dungeon.home> To: Martin Blapp Cc: current@freebsd.org, Stephen McKay Subject: Re: Uncommitted dc0 fixes ... References: <20020904165819.R31964-100000@levais.imp.ch> In-Reply-To: <20020904165819.R31964-100000@levais.imp.ch> from Martin Blapp at "Wed, 04 Sep 2002 15:07:48 +0000" Date: Mon, 09 Sep 2002 23:59:08 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 4th September 2002, Martin Blapp wrote: >And this patch here together with patch III made the annoying messages (dc0: >failed to force tx and rx to idle mode) go away. And I can use now my card >without to replug the cable over again) I've been meaning to remove the annoying message for ages. Sorry about that. >+ if (DC_IS_INTEL(sc)) { >+ for (i = 0; i < DC_TIMEOUT; i++) { >+ isr = CSR_READ_4(sc, DC_ISR); >+ if (isr & DC_ISR_TX_IDLE && >+ (isr & DC_ISR_RX_STATE) >+ == DC_RXSTATE_STOPPED) >+ break; >+ DELAY(10); >+ } >+ } Conditionalising on DC_IS_INTEL() means most cards no longer wait until the TX and RX are idle. I don't have enough different if_dc cards to know if this is safe. On the other hand, every test I've done on my Intel and Macronix cards shows zero calls to DELAY() in this loop. The loop may as well not be there for those card types. Indeed, it isn't there at all in if_de and in a Linux driver I looked at. From this I'm guessing that no 21143 (real or clone) needs this check, though I've got no real proof. Out of all this fuzzy evidence, I guess the most sensible option is the patch you've proposed. If nobody else is interested, I'll commit this part of your patch cluster on the weekend. I suppose I could do the ADMtek auto tx underrun recover patch too, as it seems harmless to other cards. The other stuff I can't test at all. This driver represents a counterintuitive state of affairs. I was impressed when Bill Paul managed to support so many clone cards with one driver. But now nobody has enough hardware on hand to test any change properly. There's some sort of lesson to be learnt here. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 7:13:48 2002 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 A164137B401 for ; Mon, 9 Sep 2002 07:13:45 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EB643E6E for ; Mon, 9 Sep 2002 07:13:45 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g89EDiYB054917 for ; Mon, 9 Sep 2002 07:13:44 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g89EDilf054915 for current@freebsd.org; Mon, 9 Sep 2002 07:13:44 -0700 (PDT) Date: Mon, 9 Sep 2002 07:13:44 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209091413.g89EDilf054915@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Mon Sep 9 06:08:51 PDT 2002 -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Mon Sep 9 07:13:39 PDT 2002 -------------------------------------------------------------- >>> Kernel build for LINT started on Mon Sep 9 07:13:41 PDT 2002 -------------------------------------------------------------- ===> LINT config: Error: device "apm_saver" is unknown config: Error: device "cy" is unknown config: Error: device "cy" does not take a count config: 3 errors WARNING: kernel contains GPL contaminated ext2fs filesystem FYI: static unit limits for vcoda are set: NVCODA=4 FYI: static unit limits for dgb are set: NDGB=1 FYI: static unit limits for card are set: NCARD=1 FYI: static unit limits for meteor are set: NMETEOR=1 *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 7:40:31 2002 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 7F42937B400 for ; Mon, 9 Sep 2002 07:40:24 -0700 (PDT) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5179343E3B for ; Mon, 9 Sep 2002 07:40:22 -0700 (PDT) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.11.6/8.11.6) with ESMTP id g89EeFh26870 for ; Mon, 9 Sep 2002 16:40:17 +0200 (MEST) Date: Mon, 9 Sep 2002 16:40:15 +0200 (CEST) From: Harti Brandt To: current@freebsd.org Subject: xl_stats_update taking very long Message-ID: <20020909163158.C30835-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a system that I use for simulation purposes. I have set HZ to 10000 and everything is just fine. Except for one thing: the routine xl_stats_update has a mean execution time of 7.6 milliseconds. For my feeling this is far too long (compare to dc_tick, which takes only 1.5 usecs). If I comment out most of ukphy_status in ukphy_subr.c the problem disappears. It seems, that the READ_PHY() takes very long. If the reason for this behaviour is a hardware design bug, xl_stats_update should be called from a kernel thread rather then from a callout. Is there anybody with xl, mii, what-ever knowledge who knows what happens here? Regards, harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, brandt@fokus.fhg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 8:20: 4 2002 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 2C2FB37B401 for ; Mon, 9 Sep 2002 08:19:59 -0700 (PDT) Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id B796343E6A for ; Mon, 9 Sep 2002 08:19:58 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24]) by e31.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id g89FJuLe026542 for ; Mon, 9 Sep 2002 11:19:57 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g89FJsWm199452 for ; Mon, 9 Sep 2002 09:19:55 -0600 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id BF2F6375C; Mon, 9 Sep 2002 20:49:46 +0530 (IST) Subject: Kernel hangs during boot - latest cvsup From: Sid Carter Operating-System: Turing OS XCVIII Disclaimer: Not speaking for anyone in any way, shape, or form. Copyright: Copyright 2002 Sid Carter - All Rights Reserved To: current@freebsd.org Reply-To: sidcarter@symonds.net Organization: Sid Carter GmBH. Date: 09 Sep 2002 20:49:46 +0530 Message-ID: <86lm6b197x.fsf@calvin.in.ibm.com> Lines: 29 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I compiled the kernel last nite and I haven't been able to boot into the system with that kernel. This is where the kernel hangs ---------------------------- vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec ----------------------------------- It prints the above message and just hangs. uname -------- 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Aug 8 21:48:49 IST 2002 Anybody else experiencing this ? Regards Sid -- A computer, to print out a fact, Will divide, multiply, and subtract. But this output can be No more than debris, If the input was short of exact. -- Gigo Sid Carter - http://symonds.net/~sidcarter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 10:14:38 2002 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 7580B37B406; Mon, 9 Sep 2002 10:14:35 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9EA243E6A; Mon, 9 Sep 2002 10:14:34 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id g89HEYVo066113 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 9 Sep 2002 13:14:34 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id g89HEXop066110; Mon, 9 Sep 2002 13:14:33 -0400 (EDT) (envelope-from wollman) Date: Mon, 9 Sep 2002 13:14:33 -0400 (EDT) From: Garrett Wollman Message-Id: <200209091714.g89HEXop066110@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.org Cc: current@FreeBSD.org, kan@FreeBSD.org Subject: Re: No way to tell when `long long' is or is not supported? In-Reply-To: <20020909081046.GB26978@dragon.nuxi.com> References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> <20020909081046.GB26978@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > Looking at GCC on other platforms, "_LONGLONG" seems to be the most > preferred symbol. How does this patch look? Works for me. I'd still like to see `-posix' go away, if we're going to be changing freebsd-spec.h further. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 10:16:42 2002 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 AB7D837B401; Mon, 9 Sep 2002 10:16:33 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CD6E43E72; Mon, 9 Sep 2002 10:16:32 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.5) with ESMTP id g89HGVVo066163 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 9 Sep 2002 13:16:31 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.5/Submit) id g89HGVXK066160; Mon, 9 Sep 2002 13:16:31 -0400 (EDT) (envelope-from wollman) Date: Mon, 9 Sep 2002 13:16:31 -0400 (EDT) From: Garrett Wollman Message-Id: <200209091716.g89HGVXK066160@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.org Cc: current@FreeBSD.org, kan@FreeBSD.org Subject: Re: No way to tell when `long long' is or is not supported? In-Reply-To: <20020909070700.GA26978@dragon.nuxi.com> References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> <20020909070700.GA26978@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > It seems to work for me: > $ cat foo.c > #ifdef __STRICT_ANSI__ > #error __STRICT_ANSI__ > #endif > $ /usr/bin/cc -ansi foo.c > foo.c:2:2: #error __STRICT_ANSI__ OK, so this is now one of those magic defines that's not shown in the specs and just pulled out thin air by the preprocessor? One wishes that the GCC crowd would make up their minds already.... -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 10:18:41 2002 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 F2B2937B407 for ; Mon, 9 Sep 2002 10:18:37 -0700 (PDT) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EDB043E3B for ; Mon, 9 Sep 2002 10:18:37 -0700 (PDT) (envelope-from rodrigc@attbi.com) Received: from dibbler.ne.client2.attbi.com (localhost [127.0.0.1]) by dibbler.ne.client2.attbi.com (8.12.6/8.12.5) with ESMTP id g89HIUhF003240; Mon, 9 Sep 2002 13:18:31 -0400 (EDT) (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6/Submit) id g89HIU7k003239; Mon, 9 Sep 2002 13:18:30 -0400 (EDT) Date: Mon, 9 Sep 2002 13:18:30 -0400 From: Craig Rodrigues To: Poul-Henning Kamp Cc: freebsd-current@freebsd.org Subject: Re: Clock runs too fast Message-ID: <20020909131830.A3204@attbi.com> References: <20020907231952.A5525@attbi.com> <432.1031480186@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <432.1031480186@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sun, Sep 08, 2002 at 12:16:26PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 12:16:26PM +0200, Poul-Henning Kamp wrote: > In message <20020907231952.A5525@attbi.com>, Craig Rodrigues writes: > >Is there a problem with the ACPI code or with my > >hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). > > > >How can I default to i8254 as my default timer? Is there > >something I should put in device.hints? > > Put it in /etc/rc.early: > sysctl kern.timecounterhardware=i8254 I put the following lin in /etc/sysctl.conf and it did the job: kern.timecounter.hardware=i8254 > > I have not been able to understand in what way this board fails :-( > > Does the time run uniformly fast, ie: 7 minutes every 5, all the > time, or is it erratic ? I didn't do a very thorough analysis of the problem, but it seemed to erratic. -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 10:33:42 2002 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 4F05337B400; Mon, 9 Sep 2002 10:33:35 -0700 (PDT) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07ADB43E65; Mon, 9 Sep 2002 10:33:31 -0700 (PDT) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.4905); Mon, 9 Sep 2002 10:35:23 -0700 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.4905); Mon, 9 Sep 2002 10:35:22 -0700 Message-ID: <3D7CDB63.1E640A3F@exodus.net> Date: Mon, 09 Sep 2002 10:33:23 -0700 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org, mobile@freebsd.org Subject: Bluetooth stack for FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Sep 2002 17:35:23.0028 (UTC) FILETIME=[468B0540:01C25827] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hackers, I'm very pleased to announce that another engineering release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020909.tar.gz This release features several major changes and includes support for H4 UART and H2 USB transport layers, Host Controller Interface (HCI), Link Layer Control and Adaptation Protocol (L2CAP) and Bluetooth sockets layer. It also comes with several user space utilities that can be used to configure and test Bluetooth devices. Also there are several man pages. o HCI and L2CAP code bug fixes o Bluetooth sockets layer now supports raw HCI and L2CAP sockets and SEQPACKET L2CAP sockets. o SDP is now supported. I ported BlueZ-sdp-0.7 daemon, configuration tool and user space library. I also did basic interoperability testing with Linux (BlueZ) and Windows 2000 (3COM and Xircom stacks). It seems to work just fine. o RFCOMM is now supported. I ported old BlueZ-rfcommd-1.1 (no longer supported by BlueZ) daemon. This daemon provides RFCOMM service via pseudo ttys. It is not very useful for legacy applications, but i managed to run PPP over Bluetooth. I also did some basic interoperability testing with Linux (works) and Windows 2000 (Xircom stack - works, 3COM stack - does not work - crc errors). Note: this code isn't in very good shape and needs more cleanup and fixing. It still has some bugs. I still would like to hear from people. I'm extremely surprised that FreeBSD community seems not interested in this at all. I got very few replies from few people (Julian Elischer, Terry Lambert - thanks!) and that's it. As usual, i would like to invite any interested individuals to join the project and help me. thanks, max p.s. NetBSD folks seem to started work on Bluetooth too. http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/dev/bluetooth/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 10:37:11 2002 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 CB45237B401; Mon, 9 Sep 2002 10:37:07 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB66343E4A; Mon, 9 Sep 2002 10:37:06 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g89HapZV013009; Mon, 9 Sep 2002 19:36:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Maksim Yevmenkin Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD In-Reply-To: Your message of "Mon, 09 Sep 2002 10:33:23 PDT." <3D7CDB63.1E640A3F@exodus.net> Date: Mon, 09 Sep 2002 19:36:51 +0200 Message-ID: <13008.1031593011@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3D7CDB63.1E640A3F@exodus.net>, Maksim Yevmenkin writes: >I still would like to hear from people. I'm extremely >surprised that FreeBSD community seems not interested in >this at all. I got very few replies from few people >(Julian Elischer, Terry Lambert - thanks!) and that's it. Most of us probably doesn't have any bluetooth hardware... -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 11: 9:49 2002 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 7320337B401; Mon, 9 Sep 2002 11:09:44 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7727843E4A; Mon, 9 Sep 2002 11:09:41 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.11.6/8.11.6) with ESMTP id g89I9CS21089; Mon, 9 Sep 2002 21:09:13 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.5/8.12.5) with ESMTP id g89I9MdO013819; Mon, 9 Sep 2002 21:09:22 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.5/8.12.5/Submit) id g89I9Jan013818; Mon, 9 Sep 2002 21:09:19 +0300 (EEST) Date: Mon, 9 Sep 2002 21:09:19 +0300 From: Maxim Sobolev To: Poul-Henning Kamp Cc: Maksim Yevmenkin , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD Message-ID: <20020909180919.GB13754@vega.vega.com> References: <3D7CDB63.1E640A3F@exodus.net> <13008.1031593011@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <13008.1031593011@critter.freebsd.dk> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 09, 2002 at 07:36:51PM +0200, Poul-Henning Kamp wrote: > In message <3D7CDB63.1E640A3F@exodus.net>, Maksim Yevmenkin writes: > > >I still would like to hear from people. I'm extremely > >surprised that FreeBSD community seems not interested in > >this at all. I got very few replies from few people > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > Most of us probably doesn't have any bluetooth hardware... Yuip, at least I don't have for sure. :( -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 11:32:49 2002 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 3040037B400 for ; Mon, 9 Sep 2002 11:32:46 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E845E43E6A for ; Mon, 9 Sep 2002 11:32:42 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 15304 invoked by uid 1000); 9 Sep 2002 18:32:46 -0000 Date: Mon, 9 Sep 2002 11:32:46 -0700 (PDT) From: Nate Lawson To: current@freebsd.org Subject: Re: alpha tinderbox (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anyone else? ---------- Forwarded message ---------- Date: Mon, 9 Sep 2002 09:33:44 +0100 From: Doug Rabson To: Nate Lawson , Doug Rabson Subject: Re: alpha tinderbox On Monday 09 September 2002 7:08 am, Nate Lawson wrote: > You offered to fix the kernel LINT problems a while back. Still > interested? I don't think I will have the time for the next month but possibly after that I can get back to doing some FreeBSD stuff. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 11:54:45 2002 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 BB52537B400 for ; Mon, 9 Sep 2002 11:54:41 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFD5A43E4A for ; Mon, 9 Sep 2002 11:54:40 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g89IscO1005886; Mon, 9 Sep 2002 20:54:38 +0200 Received: (nullmailer pid 8717 invoked by uid 1000); Mon, 09 Sep 2002 18:54:01 -0000 Date: Mon, 9 Sep 2002 20:54:01 +0200 From: Mark Santcroos To: acpi-jp@jp.freebsd.org Cc: current@FreeBSD.ORG Subject: Re: acpica-unix-20020829 patches (was Re: Lots of ACPI errors when booting yesterdays CURRENT Message-ID: <20020909185401.GA8621@laptop.6bone.nl> References: <3D75BB51.4020305@gneto.com> <20020905.150630.78701116.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020905.150630.78701116.iwasaki@jp.FreeBSD.org> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1034 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 05, 2002 at 03:06:30PM +0900, Mitsuru IWASAKI wrote: > Please try the latest version acpica-unix-20020829, patches for > FreeBSD at: > http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020829-test20020905.diff Hi Mitsuru, I applied your patches today and besides the "Revision"s mismatch it applied cleanly. Running it now without new problems or new features. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 12: 4: 3 2002 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 054F037B400 for ; Mon, 9 Sep 2002 12:04:02 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161AA43E42 for ; Mon, 9 Sep 2002 12:04:01 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id FAA20383; Tue, 10 Sep 2002 05:03:57 +1000 Date: Tue, 10 Sep 2002 05:11:39 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Nate Lawson Cc: current@FreeBSD.ORG Subject: Re: alpha tinderbox (fwd) In-Reply-To: Message-ID: <20020910050815.E8209-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Nate Lawson wrote: > Anyone else? I might get around to fixing some of the cy dirver problems, but you can easily just remove references to the cy driver from alpha files (the main references have have already been moved from conf/files to conf/files.{i386,pc98}. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 13: 4:13 2002 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 4441237B400 for ; Mon, 9 Sep 2002 13:04:11 -0700 (PDT) Received: from alfred.skaarup.org (alfred.skaarup.org [193.111.120.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 1DC7E43E65 for ; Mon, 9 Sep 2002 13:04:09 -0700 (PDT) (envelope-from mfbsd@skaarup.org) Received: (qmail 31368 invoked by uid 0); 9 Sep 2002 20:04:02 -0000 Received: from localhost (HELO alfred.skaarup.org) (127.0.0.1) by localhost with SMTP; 9 Sep 2002 20:04:01 -0000 Received: (qmail 31355 invoked by uid 1039); 9 Sep 2002 20:04:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Sep 2002 20:04:01 -0000 Date: Mon, 9 Sep 2002 22:04:01 +0200 (CEST) From: Rasmus Skaarup To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Please commit syscons fix (Was: Re: syscons in rcng ? - SOLVED) In-Reply-To: <20020909022140.W54490-100000@kushnir1.kiev.ua> Message-ID: <20020909220254.O31291-100000@alfred.skaarup.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > >With the latest changes (1.8, 5th of Sep) to /etc/rc.d/syscons, syscons > > >doesn't get initialized on my 5.0-CURRENT. > > > > > >Have I missed some new configuration options? > > > > Very simple: /usr/src/etc/rc.d/syscons misses line > run_rc_command "$1" Would someone please commit this? Sincerely, Rasmus Skaarup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 13:40:50 2002 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 B906F37B400 for ; Mon, 9 Sep 2002 13:40:44 -0700 (PDT) Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4936443E3B for ; Mon, 9 Sep 2002 13:40:44 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id g89KeeP22735; Mon, 9 Sep 2002 13:40:40 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200209092040.g89KeeP22735@ambrisko.com> Subject: Re: ste driver broken In-Reply-To: <20020908102820.GA71874@brazil.nic.fr> To: Francois Tigeot Date: Mon, 9 Sep 2002 13:40:39 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Francois Tigeot writes: [ Charset ISO-8859-1 unsupported, converting... ] | Greetings, | | I recently upgraded one machine to a recent -CURRENT, and the NIC | (DLink 550 TX) fails to be properly initialized. | The rest of the system is pretty vanilla : Athlon XP, with Via chipset. | | | Here is the relevant part of dmesg: | | ste0: port 0x9800-0x987f mem 0xe9000000-0xe900007f irq 7 at device 11.0 on pci0 | /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 | /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 | lock order reversal | 1st 0xc25b69a4 ste0 (network driver) @ /usr/src/sys/pci/if_ste.c:937 | 2nd 0xc0318600 allproc (allproc) @ /usr/src/sys/kern/kern_fork.c:317 | /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 | /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 | /usr/src/sys/vm/uma_core.c:1332: could sleep with "ste0" locked from /usr/src/sys/pci/if_ste.c:937 | ste0: Ethernet address: 00:50:ba:71:be:ea | ste0: MII without any phy! | device_probe_and_attach: ste0 attach returned 6 I'd like to send you some code to test out. It looks like a 550 is different from a 580 part. I need to do some testing. Thanks, Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 13:43:46 2002 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 E144737B400; Mon, 9 Sep 2002 13:43:43 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A6AE43E4A; Mon, 9 Sep 2002 13:43:42 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Sep 2002 21:43:41 +0100 (BST) To: hsu@freebsd.org, jennifer@freebsd.org Cc: current@freebsd.org Subject: -current panic with IPv6. X-Request-Do: Date: Mon, 09 Sep 2002 21:43:41 +0100 From: David Malone Message-ID: <200209092143.aa63055@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've got the following panic a few times using IPv6 on a recent -current (while scping a file usually): panic: mutex inp not owned at ../../../netinet/tcp_output.c:131 panic: from debugger the trace back seems to involve getting an ICMP message and then calling tcp code. David. #0 0xc01f50ab in doadump () #1 0xc01f5549 in boot () #2 0xc01f5778 in panic () #3 0xc013eb12 in db_panic () #4 0xc013ea92 in db_command () #5 0xc013eba6 in db_command_loop () #6 0xc014177a in db_trap () #7 0xc02fe3f2 in kdb_trap () #8 0xc030e2a7 in trap () #9 0xc02ffb68 in calltrap () #10 0xc01f5760 in panic () #11 0xc01ebd7c in _mtx_assert () #12 0xc02751ea in tcp_output () #13 0xc0277d41 in tcp_mtudisc () #14 0xc028929b in in6_pcbnotify () #15 0xc02779ce in tcp6_ctlinput () #16 0xc0280c17 in icmp6_notify_error () #17 0xc0280629 in icmp6_input () #18 0xc028d848 in ip6_input () #19 0xc028cbc1 in ip6intr () #20 0xc01e2003 in swi_net () #21 0xc01e1c52 in ithread_loop () #22 0xc01e08ff in fork_exit () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 14: 9: 9 2002 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 5B01237B400 for ; Mon, 9 Sep 2002 14:09:06 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B25F743E6E for ; Mon, 9 Sep 2002 14:09:05 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g89L8gs31678; Mon, 9 Sep 2002 11:08:42 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 9 Sep 2002 11:08:42 -1000 (HST) From: Vincent Poy To: Sid Carter Cc: current@FreeBSD.ORG Subject: Re: Kernel hangs during boot - latest cvsup In-Reply-To: <86lm6b197x.fsf@calvin.in.ibm.com> Message-ID: <20020909110826.O2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep 2002, Sid Carter wrote: > Hi, > > I compiled the kernel last nite and I haven't been able to boot into the > system with that kernel. This is where the kernel hangs > > ---------------------------- > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 10.000 msec > ----------------------------------- > > It prints the above message and just hangs. > > uname > -------- > 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Aug 8 21:48:49 IST 2002 > > Anybody else experiencing this ? > > Regards > Sid Can you post your kernel config file? Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 14:18:12 2002 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 7EC3537B400; Mon, 9 Sep 2002 14:18:04 -0700 (PDT) Received: from mx2.alles.or.jp (mx2.alles.or.jp [210.231.151.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E0A143E42; Mon, 9 Sep 2002 14:18:03 -0700 (PDT) (envelope-from sous1@aa.alles.or.jp) Received: from B (p6044-ipad22marunouchi.tokyo.ocn.ne.jp [61.214.35.44]) by mx2.alles.or.jp (8.9.3/3.7W/allesnet) with SMTP id GAA06604; Tue, 10 Sep 2002 06:16:37 +0900 (JST) Message-Id: <200209092116.GAA06604@mx2.alles.or.jp> From: =?iso-2022-jp?B?c291czFAYWEuYWxsZXMub3IuanA=?=@mx2.alles.or.jp To: =?iso-2022-jp?B?MTIx?=@mx2.alles.or.jp Reply-To: sous1@aa.alles.or.jp Date: Tue, 10 Sep 2002 06:16:46 +0900 Subject: =?iso-2022-jp?B?GyRCJDckOCRfJEgkYiRiJE4lMyVpJVwlbCE8JTclZyVzGyhK?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ‚à‚à‚Ş‚Í‚ĥ‚Ż‚Ä‚Ô‚Ç‚¤‚Ş‚ä‚ê‚é ‚µ‚ĥ‚Ŭ‚Ĉ‚à‚à‚̃Rƒ‰ƒ{ƒŒ[ƒVƒ‡ƒ“ ƒƒŠ[ƒ^ƒrƒfƒIi‚c‚u‚cjê–ċ ‚˘‚‚܂Ċ‰c‹Ĉ‚Ċ‚Ğ‚é‚İ‚í‚İ‚è‚Ü‚ı‚ñ ‚²’•ĥ‚Í‚¨‘‚߂ɁI http://book-i.net/mutou ì•i—á ­—“`à@–ĵŒ‰’c’n9@­—‚Ì“ı‘ ‚È‚Ç‚È‚Ç132ì•iBD•]”­”„’†I (^-^)/~ƒƒŠ˜F—˜ƒ€ƒg[ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 14:40:14 2002 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 DF36537B406 for ; Mon, 9 Sep 2002 14:40:07 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 735BF43E3B for ; Mon, 9 Sep 2002 14:40:07 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020909214006.OOWL19682.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 9 Sep 2002 21:40:06 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA58676; Mon, 9 Sep 2002 14:37:46 -0700 (PDT) Date: Mon, 9 Sep 2002 14:37:45 -0700 (PDT) From: Julian Elischer To: Vincent Poy Cc: Sid Carter , current@FreeBSD.ORG Subject: Re: Kernel hangs during boot - latest cvsup In-Reply-To: <20020909110826.O2914-100000@oahu.WURLDLINK.NET> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Vincent Poy wrote: > On 9 Sep 2002, Sid Carter wrote: > > > Hi, > > > > I compiled the kernel last nite and I haven't been able to boot into the > > system with that kernel. This is where the kernel hangs > > > > ---------------------------- > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > Timecounters tick every 10.000 msec > > ----------------------------------- boot -v might be instructive.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 14:50:34 2002 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 CB83937B400 for ; Mon, 9 Sep 2002 14:50:31 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E69243E4A for ; Mon, 9 Sep 2002 14:50:31 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.111.103] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.12 $ on Novell NetWare via secured & encrypted transport (TLS); Mon, 09 Sep 2002 15:50:31 -0600 Message-ID: <3D7D176E.3010800@hotmail.com> Date: Mon, 09 Sep 2002 14:49:34 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020905 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: pkg_install broken? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/lib/version.c -o version.o building static install library ranlib libinstall.a ===> add cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/main.c cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/perform.c cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/futil.c cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/extract.c cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib -Werror -Wall -Wno-format-y2k -Wno-uninitialized -o pkg_add main.o perform.o futil.o extract.o /usr/obj/usr/src/usr.sbin/pkg_install/add/../lib/libinstall.a -lfetch -lmd -lssl -lcrypto /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x81): undefined reference to `main' *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 15: 9:31 2002 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 2404137B400 for ; Mon, 9 Sep 2002 15:09:27 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED3243E4A for ; Mon, 9 Sep 2002 15:09:26 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g89M95Y32339; Mon, 9 Sep 2002 12:09:05 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 9 Sep 2002 12:09:05 -1000 (HST) From: Vincent Poy To: Julian Elischer Cc: Sid Carter , Subject: Re: Kernel hangs during boot - latest cvsup In-Reply-To: Message-ID: <20020909120516.A2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Julian Elischer wrote: > On Mon, 9 Sep 2002, Vincent Poy wrote: > > > On 9 Sep 2002, Sid Carter wrote: > > > > > Hi, > > > > > > I compiled the kernel last nite and I haven't been able to boot into the > > > system with that kernel. This is where the kernel hangs > > > > > > ---------------------------- > > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > > Timecounters tick every 10.000 msec > > > ----------------------------------- > > > boot -v might be instructive.. It seems in the latest -CURRENT, the following in the kernel config file based on the GENERIC kernel: options MAXMEM=786432 would hang the kernel right after: Copyright (c) 1992-2002 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 5.0-CURRENT #0: Mon Sep 9 11:56:07 PDT 2002 vince@bigbang.DNALOGIC.NET:/usr/obj/usr/src/sys/BIGBANG At this point, it would just sit there and hitting the power button would turn off the machine. Tested this on two notebooks and a desktop, same results. Taking out that line in the kernel config would make a bootable kernel. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 16: 0:34 2002 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 3027937B400; Mon, 9 Sep 2002 16:00:31 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5BDE43E6A; Mon, 9 Sep 2002 16:00:29 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g89N0Hwr093398; Mon, 9 Sep 2002 16:00:21 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209092300.g89N0Hwr093398@gw.catspoiler.org> Date: Mon, 9 Sep 2002 16:00:17 -0700 (PDT) From: Don Lewis Subject: vnode lock assertion problem in nfs_link() To: current@FreeBSD.org, jeff@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG nfs_link() contains the following code: /* * Push all writes to the server, so that the attribute cache * doesn't get "out of sync" with the server. * XXX There should be a better way! */ VOP_FSYNC(vp, cnp->cn_cred, MNT_WAIT, cnp->cn_thread); The problem is that vp is not locked by the caller, but VOP_FSYNC() expects its argument to be locked. I think we can probably just lock and unlock vp around the call to VOP_FSYNC() ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 16: 2:35 2002 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 15D3037B400 for ; Mon, 9 Sep 2002 16:02:33 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 586FB43E3B for ; Mon, 9 Sep 2002 16:02:30 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.11.6/8.11.6) with ESMTP id g89N0TS31490; Tue, 10 Sep 2002 02:00:30 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.5/8.12.5) with ESMTP id g89N0edO014961; Tue, 10 Sep 2002 02:00:40 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.5/8.12.5/Submit) id g89N0dTf014960; Tue, 10 Sep 2002 02:00:39 +0300 (EEST) Date: Tue, 10 Sep 2002 02:00:39 +0300 From: Maxim Sobolev To: walt Cc: freebsd-current@FreeBSD.ORG Subject: Re: pkg_install broken? Message-ID: <20020909230039.GA14909@vega.vega.com> References: <3D7D176E.3010800@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <3D7D176E.3010800@hotmail.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OOPS, sorry, this was my fault. I've fixed it already. Thanks for reporting! -Maxim On Mon, Sep 09, 2002 at 02:49:34PM -0700, walt wrote: > cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k > -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/lib/version.c -o > version.o > building static install library > ranlib libinstall.a > ===> add > cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/usr.sbin/pkg_install/add/main.c > cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/usr.sbin/pkg_install/add/perform.c > cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/usr.sbin/pkg_install/add/futil.c > cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/usr.sbin/pkg_install/add/extract.c > cc -O -pipe -mcpu=pentiumpro -I/usr/src/usr.sbin/pkg_install/add/../lib > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -o pkg_add main.o > perform.o futil.o extract.o > /usr/obj/usr/src/usr.sbin/pkg_install/add/../lib/libinstall.a -lfetch -lmd > -lssl -lcrypto > /usr/lib/crt1.o: In function `_start': > /usr/lib/crt1.o(.text+0x81): undefined reference to `main' > *** Error code 1 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 16: 3:55 2002 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 B664837B400 for ; Mon, 9 Sep 2002 16:03:53 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3888743E65 for ; Mon, 9 Sep 2002 16:03:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g89N3qfO050313; Mon, 9 Sep 2002 16:03:52 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g89N3q5U050312; Mon, 9 Sep 2002 16:03:52 -0700 (PDT) Date: Mon, 9 Sep 2002 16:03:52 -0700 From: "David O'Brien" To: Stephen McKay Cc: Martin Blapp , current@freebsd.org Subject: Re: Uncommitted dc0 fixes ... Message-ID: <20020909230351.GA50249@dragon.nuxi.com> Reply-To: current@freebsd.org Mail-Followup-To: David O'Brien , Stephen McKay , Martin Blapp , current@freebsd.org References: <20020904165819.R31964-100000@levais.imp.ch> <200209091359.g89Dx8t12523@dungeon.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209091359.g89Dx8t12523@dungeon.home> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 09, 2002 at 11:59:08PM +1000, Stephen McKay wrote: > This driver represents a counterintuitive state of affairs. I was impressed > when Bill Paul managed to support so many clone cards with one driver. But > now nobody has enough hardware on hand to test any change properly. There's > some sort of lesson to be learnt here. If a clear capable replacement maintainer for dc(4) stepped forward, I am sure the user community could put all the various types of cards in said person's hands. I have 3 cards I could donate to the cause myself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 16: 5:28 2002 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 4DBCE37B400; Mon, 9 Sep 2002 16:05:26 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D828643E4A; Mon, 9 Sep 2002 16:05:25 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g89N5Gwr093422; Mon, 9 Sep 2002 16:05:20 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209092305.g89N5Gwr093422@gw.catspoiler.org> Date: Mon, 9 Sep 2002 16:05:16 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: current@FreeBSD.ORG, jeff@FreeBSD.ORG Cc: current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <200209092300.g89N0Hwr093398@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep, Don Lewis wrote: > nfs_link() contains the following code: > > /* > * Push all writes to the server, so that the attribute cache > * doesn't get "out of sync" with the server. > * XXX There should be a better way! > */ > VOP_FSYNC(vp, cnp->cn_cred, MNT_WAIT, cnp->cn_thread); > > The problem is that vp is not locked by the caller, but VOP_FSYNC() > expects its argument to be locked. > > I think we can probably just lock and unlock vp around the call to > VOP_FSYNC() ... Hmn, I think I just figured out this bit of code in ufs_link(): if (tdvp != vp && (error = vn_lock(vp, LK_EXCLUSIVE, td))) { goto out2; } It would probably be a bad thing to unconditionally lock vp if vp and tdvp are the same ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 17: 8:52 2002 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 D0B3D37B405; Mon, 9 Sep 2002 17:08:43 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C1BF43E65; Mon, 9 Sep 2002 17:08:43 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g8A08HOo004829; Mon, 9 Sep 2002 20:08:18 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 9 Sep 2002 20:08:17 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Don Lewis Cc: current@FreeBSD.org, jeff@FreeBSD.org Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209092300.g89N0Hwr093398@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Don Lewis wrote: > nfs_link() contains the following code: > > /* > * Push all writes to the server, so that the attribute cache > * doesn't get "out of sync" with the server. > * XXX There should be a better way! > */ > VOP_FSYNC(vp, cnp->cn_cred, MNT_WAIT, cnp->cn_thread); > > The problem is that vp is not locked by the caller, but VOP_FSYNC() > expects its argument to be locked. > > I think we can probably just lock and unlock vp around the call to > VOP_FSYNC() ... What I'd actually like to do is lock vp on going in to the VOP. I need to grab the lock in the link() code anyway to do the MAC check. UFS and others all immediately lock the vnode on entry anyway... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 17:56:42 2002 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 A65FD37B400; Mon, 9 Sep 2002 17:56:40 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3172D43E3B; Mon, 9 Sep 2002 17:56:40 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8A0uQwr093581; Mon, 9 Sep 2002 17:56:30 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209100056.g8A0uQwr093581@gw.catspoiler.org> Date: Mon, 9 Sep 2002 17:56:26 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: rwatson@FreeBSD.org Cc: current@FreeBSD.org, jeff@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep, Robert Watson wrote: > On Mon, 9 Sep 2002, Don Lewis wrote: >> I think we can probably just lock and unlock vp around the call to >> VOP_FSYNC() ... > > What I'd actually like to do is lock vp on going in to the VOP. I need to > grab the lock in the link() code anyway to do the MAC check. UFS and > others all immediately lock the vnode on entry anyway... That sounds reasonable. It looks like ufs and ext2fs are currently doing the locking and nfs and coda aren't. The only other filesystem that implements the link method is unionfs, which conditionally does the lock only in certain cases and does some complex lock manipulations that I don't fully understand. BTW, I noticed that a number of filesystems have reimplemented vop_eopnotsupp() and called it foofs_link(). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 18: 0: 9 2002 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 D2A0D37B400 for ; Mon, 9 Sep 2002 18:00:06 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D2D43E42 for ; Mon, 9 Sep 2002 18:00:06 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g8A106YB068942 for ; Mon, 9 Sep 2002 18:00:06 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g8A1059v068940 for current@freebsd.org; Mon, 9 Sep 2002 18:00:05 -0700 (PDT) Date: Mon, 9 Sep 2002 18:00:05 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209100100.g8A1059v068940@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> usr.sbin/pkg_install/add /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/lib/crt1.o: In function `_start': /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/lib/crt1.o(.text+0xec): undefined reference to `main' /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/lib/crt1.o(.text+0xf0): undefined reference to `main' *** Error code 1 Stop in /var/tmp/des/src/usr.sbin/pkg_install/add. *** Error code 1 Stop in /var/tmp/des/src/usr.sbin/pkg_install. *** Error code 1 Stop in /var/tmp/des/src/usr.sbin. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 18:25:56 2002 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 864B437B400 for ; Mon, 9 Sep 2002 18:25:39 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E181143E6A for ; Mon, 9 Sep 2002 18:25:37 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8A1P8l33879; Mon, 9 Sep 2002 15:25:08 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 9 Sep 2002 15:25:08 -1000 (HST) From: Vincent Poy To: Martin Blapp Cc: current@FreeBSD.ORG Subject: Re: Uncommitted dc0 fixes ... In-Reply-To: <20020905210537.Q31964-100000@levais.imp.ch> Message-ID: <20020909130911.U2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 5 Sep 2002, Martin Blapp wrote: > > When I tried these patches manually handpatching on 08182002 JP > > SNAPSHOT, it took away the error messages like you had mentioned except > > I can ping everything except for the gateway. Also, no other protocols > > would work at all so it seems like something else broke. I took out > > the following and it still made no difference. > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=misc/32699 > > Can you please test each patch and see which one is responsable ? > > Martin Hi Martin and everyone, I finally updated to the latest -CURRENT last night after pulling the HD from my IBM ThinkPad 770Z and putting it in a loaner Dell Inspiron 8200 P4m-1.7Ghz as I couldn't get the fans to turn on and it keeps shutting off due to overheating. I have both a Siemens/Efficient Networks SpeedStream SS1012 and a SMC Networks SMC8036TX which seems to be identical cards physically as it has the same design and same label printing information layout. As far as testing each patch, here goes: 1) dc driver uses wrong case to read MAC from eeprom. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482 This one seems to break data sending/receiving as the only thing that works is pinging and that's only on the alias/secondary IP and not the primary IP network which is completely unpingable. * $FreeBSD: src/sys/pci/if_dcreg.h,v 1.25 2002/05/06 10:55:42 iwasaki Exp *** /usr/temp/if_dcreg.h Mon May 6 03:55:42 2002 --- /usr/src/sys/pci/if_dcreg.h Mon Sep 9 15:14:08 2002 *************** *** 78,83 **** --- 78,84 ---- #define DC_TYPE_PNIC 0xA /* 82c168/82c169 PNIC I */ #define DC_TYPE_XIRCOM 0xB /* Xircom X3201 */ #define DC_TYPE_CONEXANT 0xC /* Conexant LANfinity RS7112 */ + #define DC_TYPE_EN5152B 0xD /* Accton EN5251B. Clone of ADMtek 983B? */ #define DC_IS_MACRONIX(x) \ (x->dc_type == DC_TYPE_98713 || \ *************** *** 86,91 **** --- 87,93 ---- #define DC_IS_ADMTEK(x) \ (x->dc_type == DC_TYPE_AL981 || \ + x->dc_type == DC_TYPE_EN5152B || \ x->dc_type == DC_TYPE_AN985) #define DC_IS_INTEL(x) (x->dc_type == DC_TYPE_21143) *************** *** 890,895 **** --- 892,904 ---- */ #define DC_DEVICEID_EN1217 0x1217 #define DC_DEVICEID_EN2242 0x1216 + #define DC_DEVICEID_EN5251B 0x1216 + + /* + * The Accton EN5251B is sold as the Siemens Speedstream SS1020. + * The EN5251B seems to be a clone of the ADMtek 983 or 983B + */ + #define DC_REVISION_EN5251B 0x11 /* ASSUMING that EN2242's revision differs */ /* * Xircom vendor ID * $FreeBSD: src/sys/pci/if_dc.c,v 1.77 2002/09/04 18:14:17 markm Exp $ *** /usr/temp/if_dc.c Wed Sep 4 11:14:17 2002 --- /usr/src/sys/pci/if_dc.c Mon Sep 9 15:22:09 2002 *************** *** 186,191 **** --- 186,193 ---- "Accton EN1217 10/100BaseTX" }, { DC_VENDORID_ACCTON, DC_DEVICEID_EN2242, "Accton EN2242 MiniPCI 10/100BaseTX" }, + { DC_VENDORID_ACCTON, DC_DEVICEID_EN5251B, + "Siemens SpeedStream SS1020 10/100BaseTX" }, { DC_VENDORID_XIRCOM, DC_DEVICEID_X3201, "Xircom X3201 10/100BaseTX" }, { DC_VENDORID_ABOCOM, DC_DEVICEID_FE2500, *************** *** 1579,1584 **** --- 1581,1589 ---- if (t->dc_did == DC_DEVICEID_DM9102 && rev >= DC_REVISION_DM9102A) t++; + if (t->dc_did == DC_DEVICEID_EN2242 && + rev >= DC_REVISION_EN5251B) + t++; return(t); } t++; *************** *** 1917,1925 **** sc->dc_flags |= DC_TX_ADMTEK_WAR; sc->dc_pmode = DC_PMODE_MII; break; case DC_DEVICEID_AN985: case DC_DEVICEID_FE2500: - case DC_DEVICEID_EN2242: sc->dc_type = DC_TYPE_AN985; sc->dc_flags |= DC_TX_USE_TX_INTR; sc->dc_flags |= DC_TX_ADMTEK_WAR; --- 1922,1939 ---- sc->dc_flags |= DC_TX_ADMTEK_WAR; sc->dc_pmode = DC_PMODE_MII; break; + case DC_DEVICEID_EN2242: /* and DC_DEVICEID_EN5251B: */ + if (revision < DC_REVISION_EN5251B) { + sc->dc_type = DC_TYPE_AN985; + } else { + sc->dc_type = DC_TYPE_EN5152B; + } + sc->dc_flags |= DC_TX_USE_TX_INTR; + sc->dc_flags |= DC_TX_ADMTEK_WAR; + sc->dc_pmode = DC_PMODE_MII; + break; case DC_DEVICEID_AN985: case DC_DEVICEID_FE2500: sc->dc_type = DC_TYPE_AN985; sc->dc_flags |= DC_TX_USE_TX_INTR; sc->dc_flags |= DC_TX_ADMTEK_WAR; *************** *** 2056,2061 **** --- 2070,2076 ---- break; case DC_TYPE_AL981: case DC_TYPE_AN985: + case DC_TYPE_EN5152B: dc_read_eeprom(sc, (caddr_t)&eaddr, DC_AL_EE_NODEADDR, 3, 0); break; case DC_TYPE_CONEXANT: dmesg output is as follows: cardbus1: Expecting link target, got 0x59 cardbus1: Resource not specified in CIS: id=10, size=100 cardbus1: Resource not specified in CIS: id=14, size=400 dc0: port 0x1000-0x10ff mem 0xf4002000 -0xf40023ff irq 11 at device 0.0 on cardbus1 dc0: Ethernet address: 85:84:33:a0:00:80 miibus1: on dc0 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:623 /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:623 /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:623 versus before the patch as follows: cardbus1: Expecting link target, got 0x59 cardbus1: Resource not specified in CIS: id=10, size=100 cardbus1: Resource not specified in CIS: id=14, size=400 dc0: port 0x1000-0x10ff mem 0xf4002000-0xf4 0023ff irq 11 at device 0.0 on cardbus1 dc0: Ethernet address: 00:04:e2:2e:c3:4e miibus1: on dc0 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:621 /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:621 /usr/src/sys/vm/uma_core.c:1332: could sleep with "dc0" locked from /usr/src/sys /pci/if_dc.c:621 Seems to identify everything as a Siemens SpeedStream SS1020. 2) Tulip ether card EN2242 (if_dc.c) use wrong multicast table This one works as far as I can tell. I don't have a IPv6 network to test. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=misc/32699 * $FreeBSD: src/sys/pci/if_dc.c,v 1.77 2002/09/04 18:14:17 markm Exp $ *** /usr/temp/if_dc.c Wed Sep 4 11:14:17 2002 --- /usr/src/sys/pci/if_dc.c Mon Sep 9 16:28:55 2002 *************** *** 1168,1174 **** TAILQ_FOREACH(ifma, &ifp->if_multiaddrs, ifma_link) { if (ifma->ifma_addr->sa_family != AF_LINK) continue; ! h = dc_crc_be(LLADDR((struct sockaddr_dl *)ifma->ifma_addr)); if (h < 32) hashes[0] |= (1 << h); else --- 1168,1178 ---- TAILQ_FOREACH(ifma, &ifp->if_multiaddrs, ifma_link) { if (ifma->ifma_addr->sa_family != AF_LINK) continue; ! if (DC_IS_CENTAUR(sc)) ! h = dc_crc_le(sc, ! LLADDR((struct sockaddr_dl *)ifma->ifma_addr)); ! else ! h = dc_crc_be(LLADDR((struct sockaddr_dl *)ifma->ifma_addr)); if (h < 32) hashes[0] |= (1 << h); else *************** *** 1921,1926 **** --- 1925,1931 ---- case DC_DEVICEID_FE2500: case DC_DEVICEID_EN2242: sc->dc_type = DC_TYPE_AN985; + sc->dc_flags |= DC_64BIT_HASH; sc->dc_flags |= DC_TX_USE_TX_INTR; sc->dc_flags |= DC_TX_ADMTEK_WAR; sc->dc_pmode = DC_PMODE_MII; 3) ADMtek AN98x, enable automatically TX underrun recovery This works and works combined with 2 above. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236 * $FreeBSD: src/sys/pci/if_dcreg.h,v 1.25 2002/05/06 10:55:42 iwasaki Exp $ *** /usr/temp/if_dcreg.h Mon May 6 03:55:42 2002 --- /usr/src/sys/pci/if_dcreg.h Mon Sep 9 17:08:14 2002 *************** *** 526,531 **** --- 526,532 ---- * ADMtek specific registers and constants for the AL981 and AN985. * The AN985 doesn't use the magic PHY registers. */ + #define DC_AL_CR 0x88 /* Command register */ #define DC_AL_PAR0 0xA4 /* station address */ #define DC_AL_PAR1 0xA8 /* station address */ #define DC_AL_MAR0 0xAC /* multicast hash filter */ *************** *** 540,545 **** --- 541,547 ---- #define DC_ADMTEK_PHYADDR 0x1 #define DC_AL_EE_NODEADDR 4 + #define DC_AL_CR_ATUR 0x00000001 /* Enable automatically TX underrun recovery */ /* End of ADMtek specific registers */ /* * $FreeBSD: src/sys/pci/if_dc.c,v 1.77 2002/09/04 18:14:17 markm Exp $ *** /usr/temp/if_dc.c Wed Sep 4 11:14:17 2002 --- /usr/src/sys/pci/if_dc.c Mon Sep 9 17:11:42 2002 *************** *** 1482,1487 **** --- 1486,1494 ---- } } + if (DC_IS_ADMTEK(sc)) + DC_SETBIT(sc, DC_AL_CR, DC_AL_CR_ATUR); + if ((media & IFM_GMASK) == IFM_FDX) { DC_SETBIT(sc, DC_NETCFG, DC_NETCFG_FULLDUPLEX); if (sc->dc_pmode == DC_PMODE_SYM && DC_IS_PNIC(sc)) 4) Martin's patch... This one works standalone and with 2 and 3 above. It seems to have increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec. Ofcourse, for some odd reason, if the ftp was done from a Windows XP Pro machine, it's only 6722KBytes/sec. * $FreeBSD: src/sys/pci/if_dc.c,v 1.77 2002/09/04 18:14:17 markm Exp $ *** /usr/temp/if_dc.c Wed Sep 4 11:14:17 2002 --- /usr/src/sys/pci/if_dc.c Mon Sep 9 17:55:22 2002 *************** *** 1363,1379 **** restart = 1; DC_CLRBIT(sc, DC_NETCFG, (DC_NETCFG_TX_ON|DC_NETCFG_RX_ON)); ! for (i = 0; i < DC_TIMEOUT; i++) { ! isr = CSR_READ_4(sc, DC_ISR); ! if (isr & DC_ISR_TX_IDLE && ! (isr & DC_ISR_RX_STATE) == DC_RXSTATE_STOPPED) ! break; ! DELAY(10); } - - if (i == DC_TIMEOUT) - printf("dc%d: failed to force tx and " - "rx to idle state\n", sc->dc_unit); } if (IFM_SUBTYPE(media) == IFM_100_TX) { --- 1367,1386 ---- restart = 1; DC_CLRBIT(sc, DC_NETCFG, (DC_NETCFG_TX_ON|DC_NETCFG_RX_ON)); ! if (DC_IS_INTEL(sc)) { ! for (i = 0; i < DC_TIMEOUT; i++) { ! isr = CSR_READ_4(sc, DC_ISR); ! if (isr & DC_ISR_TX_IDLE && ! (isr & DC_ISR_RX_STATE) ! == DC_RXSTATE_STOPPED) ! break; ! DELAY(10); ! } ! if (i == DC_TIMEOUT) { ! printf("dc%d: failed to force tx and " ! "rx to idle state\n", sc->dc_unit); ! } } } if (IFM_SUBTYPE(media) == IFM_100_TX) { Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 18:35:55 2002 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 1A19737B400 for ; Mon, 9 Sep 2002 18:35:47 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E43943E3B for ; Mon, 9 Sep 2002 18:35:46 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8A1ZAU33963; Mon, 9 Sep 2002 15:35:10 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 9 Sep 2002 15:35:10 -1000 (HST) From: Vincent Poy To: Mark Santcroos Cc: John Angelmo , Subject: Re: apm support In-Reply-To: <20020909092423.GA1962@laptop.6bone.nl> Message-ID: <20020909152750.Q2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Mark Santcroos wrote: > On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: > > > > > > Battery status: unknown > > > > > > Remaining battery time: unknown > > > > > > Battery 0: > > > > > > Battery status: unknown > > > > > > Remaining battery time: 0:00:00 > > These were all zero because you were plugged in, as you showed the values > were showed when you were unplugged. > > > > > > > APM Capabilities: > > > > > > unknown > > This is explained by the fact that you run ACPI. Afaik it's either ACPI or > APM that your laptop has. Yours has ACPI. Got a question about this... I have a IBM ThinkPad 770Z and I think it's APM when it was running the pre-load Win98 but with WinME and WinXP, it was running under ACPI. However, with the GENERIC kernel, the fan doesn't seem to go on. Is there a way to disable the system from suspending when the lid is closed? or would adding device apm to the kernel and then enabling apmd and apm in rc.conf cause it to read the settings in the BIOS which I used the ThinkPad PS2 utility to configure instead? When I attempt to do a make buildworld, after about 5 minutes it would display the following message and then the system shuts off by itself shortly thereafter. Sep 9 11:01:32 exabyte kernel: acpi_tz0: WARNING - current temperature (97.8C) exceeds system limits This is what my sysctl hw.acpi output looks like. Originally, all the hw.acpi.thermal.tz*.active were -1 so I changed it to 1 but it still didn't turn the fans on. root@bigbang [6:27pm][~] >> sysctl hw.acpi hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3180 hw.acpi.thermal.tz0.active: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 3130 hw.acpi.thermal.tz1.active: 1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 3442 hw.acpi.thermal.tz1._ACx: 3402 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 3090 hw.acpi.thermal.tz2.active: 1 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: -1 hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 3372 hw.acpi.thermal.tz2._ACx: 3242 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz3.temperature: 3000 hw.acpi.thermal.tz3.active: 1 hw.acpi.thermal.tz3.thermal_flags: 0 hw.acpi.thermal.tz3._PSV: -1 hw.acpi.thermal.tz3._HOT: -1 hw.acpi.thermal.tz3._CRT: 3322 hw.acpi.thermal.tz3._ACx: 3272 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz4.temperature: 3050 hw.acpi.thermal.tz4.active: 1 hw.acpi.thermal.tz4.thermal_flags: 0 hw.acpi.thermal.tz4._PSV: -1 hw.acpi.thermal.tz4._HOT: -1 hw.acpi.thermal.tz4._CRT: 3392 hw.acpi.thermal.tz4._ACx: 3037 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz5.temperature: 3060 hw.acpi.thermal.tz5.active: 1 hw.acpi.thermal.tz5.thermal_flags: 0 hw.acpi.thermal.tz5._PSV: -1 hw.acpi.thermal.tz5._HOT: -1 hw.acpi.thermal.tz5._CRT: 3432 hw.acpi.thermal.tz5._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz6.temperature: 3000 hw.acpi.thermal.tz6.active: 1 hw.acpi.thermal.tz6.thermal_flags: 0 hw.acpi.thermal.tz6._PSV: -1 hw.acpi.thermal.tz6._HOT: -1 hw.acpi.thermal.tz6._CRT: 3432 hw.acpi.thermal.tz6._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 49 hw.acpi.battery.time: -1 hw.acpi.battery.state: 4 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 > The reason that you can still use the 'apm' command is that the ACPI > driver 'emulates' the behaviour of /dev/apm, but the information is not > actually coming from apm. > (Can you remove device apm from your kernel to ack this?) > > What laptop do you have btw? > > And how is the suspending/resuming working? > > Mark Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 19:32:31 2002 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 536FD37B400 for ; Mon, 9 Sep 2002 19:32:28 -0700 (PDT) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8190C43E6A for ; Mon, 9 Sep 2002 19:32:27 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare/smtpfeed 1.14) with ESMTP/inet id g8A2WMY54506; Tue, 10 Sep 2002 11:32:22 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 10 Sep 2002 11:32:11 +0900 (JST) Message-Id: <20020910.113211.112630082.iwasaki@jp.FreeBSD.org> To: vince@oahu.WURLDLINK.NET Cc: marks@ripe.net, john@veidit.net, current@FreeBSD.ORG, acpi-jp@jp.freebsd.org Subject: ACPI support (was Re: apm support) From: Mitsuru IWASAKI In-Reply-To: <20020909152750.Q2914-100000@oahu.WURLDLINK.NET> References: <20020909092423.GA1962@laptop.6bone.nl> <20020909152750.Q2914-100000@oahu.WURLDLINK.NET> X-Mailer: Mew version 2.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [subject was changed] Hi, > WinXP, it was running under ACPI. However, with the GENERIC kernel, the > fan doesn't seem to go on. Is there a way to disable the system from > suspending when the lid is closed? or would adding device apm to the > kernel and then enabling apmd and apm in rc.conf cause it to read the > settings in the BIOS which I used the ThinkPad PS2 utility to configure > instead? When I attempt to do a make buildworld, after about 5 minutes it > would display the following message and then the system shuts off by > itself shortly thereafter. > > Sep 9 11:01:32 exabyte kernel: acpi_tz0: WARNING - current temperature > (97.8C) exceeds system limits It seems that your sysctl has wrong configuration and your kernel maybe too old. to disable sleep state transition by lid switch: hw.acpi.lid_switch_state=NONE APM BIOS is completely disabled when acpi(4) is enabled. The acpi(4) just emulates limited functions of APM by using acpi functions. Cooling system control code had serious bugs, fixed at 8/27. hw.acpi.thermal.tz0.active=-1 should be OK if you want auto-thermal management. To force thermal zones activated: hw.acpi.thermal.tz0.active=0 hw.acpi.thermal.tz1.active=0 [snip] hw.acpi.thermal.tz5.active=0 hw.acpi.thermal.tz6.active=0 Note that hw.acpi.thermal.tz0.active=1 is worng because it is not bool value, and > hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 there is no _AC1. There is only _AC0, so 0 must be specified to hw.acpi.thermal.tz0.active to force tz0 activated. ACPI for FreeBSD is still under development, the best way to obtain the most accurate info. is check /sys/dev/acpica/*.[ch] files for now :-) Documents at http://acpi.info/spec.htm would be helpful too. Of course, volunteers for development and documentation always are welcome. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 21:19:10 2002 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 3FEF437B400 for ; Mon, 9 Sep 2002 21:19:00 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A5E43E3B for ; Mon, 9 Sep 2002 21:18:58 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8A4ILl35032; Mon, 9 Sep 2002 18:18:22 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Mon, 9 Sep 2002 18:18:21 -1000 (HST) From: Vincent Poy To: Mitsuru IWASAKI Cc: marks@ripe.net, , , Subject: Re: ACPI support (was Re: apm support) In-Reply-To: <20020910.113211.112630082.iwasaki@jp.FreeBSD.org> Message-ID: <20020909175400.B2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Mitsuru IWASAKI wrote: Hi Iwasaki-san: > [subject was changed] > > Hi, > > > WinXP, it was running under ACPI. However, with the GENERIC kernel, the > > fan doesn't seem to go on. Is there a way to disable the system from > > suspending when the lid is closed? or would adding device apm to the > > kernel and then enabling apmd and apm in rc.conf cause it to read the > > settings in the BIOS which I used the ThinkPad PS2 utility to configure > > instead? When I attempt to do a make buildworld, after about 5 minutes it > > would display the following message and then the system shuts off by > > itself shortly thereafter. > > > > Sep 9 11:01:32 exabyte kernel: acpi_tz0: WARNING - current temperature > > (97.8C) exceeds system limits > > It seems that your sysctl has wrong configuration and your kernel > maybe too old. I installed FreeBSD via ISO Image from current.FreeBSD.ORG using the original kernel that came from the installed system: FreeBSD 5.0-CURRENT-20020818-JPSNAP #0: Wed Sep 4 11:55:32 PDT 2002 Sep 4 15:04:43 bigbang kernel: vince@bigbang.DNALOGIC.NET:/usr/obj/usr/src/sys/ GENERIC I wasn't able to buildworld since the machine would shutdown due to overheating so I move the HDD to my Dell Inspiron 8200 to do the buildworld and the new kernel to the latest -current code for September 8, 2002. My /etc/sysctl.conf consists of the following which is identical to the source tree without adding anything. # $FreeBSD: src/etc/sysctl.conf,v 1.6 2001/09/26 19:35:04 dillon Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # > to disable sleep state transition by lid switch: > hw.acpi.lid_switch_state=NONE Thanks. That worked. The other problem is it seems like even when it did sleep and now, the LCD doesn't actually go off at all but just remains on when the switch is pushed even though the indicator panel went off, is there a way around this? > APM BIOS is completely disabled when acpi(4) is enabled. The acpi(4) > just emulates limited functions of APM by using acpi functions. Interesting. That was where I was confused. If apm is enabled in the kernel config and rc.conf, what would actually happen. > Cooling system control code had serious bugs, fixed at 8/27. > hw.acpi.thermal.tz0.active=-1 should be OK if you want auto-thermal > management. To force thermal zones activated: > hw.acpi.thermal.tz0.active=0 > hw.acpi.thermal.tz1.active=0 > [snip] > hw.acpi.thermal.tz5.active=0 > hw.acpi.thermal.tz6.active=0 Haven't tried it yet but this is what the September 8, 2002 -current build looks like: root@bigbang [8:58pm][/var/log] >> sysctl hw.acpi hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3240 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 3200 hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 3442 hw.acpi.thermal.tz1._ACx: 3402 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 3150 hw.acpi.thermal.tz2.active: -1 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: -1 hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 3372 hw.acpi.thermal.tz2._ACx: 3242 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz3.temperature: 3000 hw.acpi.thermal.tz3.active: -1 hw.acpi.thermal.tz3.thermal_flags: 0 hw.acpi.thermal.tz3._PSV: -1 hw.acpi.thermal.tz3._HOT: -1 hw.acpi.thermal.tz3._CRT: 3322 hw.acpi.thermal.tz3._ACx: 3272 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz4.temperature: 3080 hw.acpi.thermal.tz4.active: -1 hw.acpi.thermal.tz4.thermal_flags: 0 hw.acpi.thermal.tz4._PSV: -1 hw.acpi.thermal.tz4._HOT: -1 hw.acpi.thermal.tz4._CRT: 3392 hw.acpi.thermal.tz4._ACx: 3092 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz5.temperature: 3030 hw.acpi.thermal.tz5.active: -1 hw.acpi.thermal.tz5.thermal_flags: 0 hw.acpi.thermal.tz5._PSV: -1 hw.acpi.thermal.tz5._HOT: -1 hw.acpi.thermal.tz5._CRT: 3432 hw.acpi.thermal.tz5._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz6.temperature: 3000 hw.acpi.thermal.tz6.active: -1 hw.acpi.thermal.tz6.thermal_flags: 0 hw.acpi.thermal.tz6._PSV: -1 hw.acpi.thermal.tz6._HOT: -1 hw.acpi.thermal.tz6._CRT: 3432 hw.acpi.thermal.tz6._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 99 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 > Note that hw.acpi.thermal.tz0.active=1 is worng because it is not > bool value, and I actually got the idea for that one when you and Michael Wu were discussion about the IBM s31 issue back on July 30, 2002 where you wrote: [snip] > hw.acpi.thermal.tz0.temperature: 3442 > hw.acpi.thermal.tz0.active: 0 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 3681 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3732 > hw.acpi.thermal.tz0._ACx: 3332 3352 -1 -1 -1 -1 -1 -1 -1 -1 s31 has AC0 and AC1 level cooling. Please try; # sysctl hw.acpi.thermal.tz0.active=1 to activate AC1 level cooling by manual. but automatically switching to AC1 is not functioning. I think this is bug, I'll check later on. The actual message can be found here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=54879+0+archive/2002/freebsd-mobile/20020804.freebsd-mobile > > hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 > there is no _AC1. There is only _AC0, so 0 must be specified to > hw.acpi.thermal.tz0.active to force tz0 activated. Oh okay, I think I'll leave it at -1 as long as the auto thermal management works instead of shutting down the machine :-) > ACPI for FreeBSD is still under development, the best way to obtain > the most accurate info. is check /sys/dev/acpica/*.[ch] files for now :-) > Documents at http://acpi.info/spec.htm would be helpful too. > > Of course, volunteers for development and documentation always are welcome. > > Thanks Thanks for your input. I'm still trying to figure out why I couldn't get my 3Com 3CXFEM656C Combo 10/100 Fast Ethernet + 56k Modem Cardbus card working on the IBM ThinkPad 770Z since it keeps saying xl0: watchdog timeout while the card works fine on the Dell Inspiron 8200 when I tried it. The only cards I successfully got working is the Siemens/Efficient Networks SpeedStream SS1012 and a SMC Networks SMC8036TX which both seem to be physically identical cards that runs on the dc0 driver. The NetGear FA511 and the LinkSys PCMPC200 Cardbus NICs both don't work at all. Is there a database somewhere of which models of Cardbus NIC cards actually work with -current? Since one of my friends has various Xircom's and other Cardbus cards but he has to ship one to me and it would be easier to just tell him which one I want before he sends it. Thanks. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 9 21:19:55 2002 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 D863D37B400; Mon, 9 Sep 2002 21:19:43 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B93E43E42; Mon, 9 Sep 2002 21:19:43 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8A4JTwr093971; Mon, 9 Sep 2002 21:19:33 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209100419.g8A4JTwr093971@gw.catspoiler.org> Date: Mon, 9 Sep 2002 21:19:29 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: rwatson@FreeBSD.org Cc: current@FreeBSD.org, jeff@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep, Robert Watson wrote: > What I'd actually like to do is lock vp on going in to the VOP. I need to > grab the lock in the link() code anyway to do the MAC check. UFS and > others all immediately lock the vnode on entry anyway... Here's a patch to implement this. It compiles and seems to work OK, but needs review. There are a couple of issues that definitely need a look: I believe the new vn_lock() call in kern_link() should use the LK_RETRY flag. The locking changes in union_link() need a thorough review, though the light testing of that I performed didn't turn up any glaring problems. The VOP_LINK(9) man page needs would also need to be updated. I also missed a change to the block comment before union_link() :-( Index: fs/unionfs/union_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/unionfs/union_vnops.c,v retrieving revision 1.89 diff -u -r1.89 union_vnops.c --- fs/unionfs/union_vnops.c 4 Aug 2002 10:29:31 -0000 1.89 +++ fs/unionfs/union_vnops.c 10 Sep 2002 02:45:34 -0000 @@ -1250,7 +1250,6 @@ struct union_node *tun = VTOUNION(ap->a_vp); if (tun->un_uppervp == NULLVP) { - vn_lock(ap->a_vp, LK_EXCLUSIVE | LK_RETRY, td); #if 0 if (dun->un_uppervp == tun->un_dirvp) { if (dun->un_flags & UN_ULOCK) { @@ -1267,9 +1266,9 @@ dun->un_flags |= UN_ULOCK; } #endif - VOP_UNLOCK(ap->a_vp, 0, td); } vp = tun->un_uppervp; + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td); } if (error) @@ -1288,6 +1287,8 @@ VOP_UNLOCK(ap->a_tdvp, 0, td); /* unlock calling node */ error = VOP_LINK(tdvp, vp, cnp); /* call link on upper */ + if (ap->a_tdvp->v_op == ap->a_vp->v_op) + VOP_UNLOCK(vp, 0, td); /* * We have to unlock tdvp prior to relocking our calling node in * order to avoid a deadlock. Index: gnu/ext2fs/ext2_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vnops.c,v retrieving revision 1.68 diff -u -r1.68 ext2_vnops.c --- gnu/ext2fs/ext2_vnops.c 15 Aug 2002 20:55:01 -0000 1.68 +++ gnu/ext2fs/ext2_vnops.c 10 Sep 2002 03:09:33 -0000 @@ -827,7 +827,6 @@ struct vnode *vp = ap->a_vp; struct vnode *tdvp = ap->a_tdvp; struct componentname *cnp = ap->a_cnp; - struct thread *td = cnp->cn_thread; struct inode *ip; int error; @@ -837,19 +836,16 @@ #endif if (tdvp->v_mount != vp->v_mount) { error = EXDEV; - goto out2; - } - if (tdvp != vp && (error = vn_lock(vp, LK_EXCLUSIVE, td))) { - goto out2; + goto out; } ip = VTOI(vp); if ((nlink_t)ip->i_nlink >= LINK_MAX) { error = EMLINK; - goto out1; + goto out; } if (ip->i_flags & (IMMUTABLE | APPEND)) { error = EPERM; - goto out1; + goto out; } ip->i_nlink++; ip->i_flag |= IN_CHANGE; @@ -860,10 +856,7 @@ ip->i_nlink--; ip->i_flag |= IN_CHANGE; } -out1: - if (tdvp != vp) - VOP_UNLOCK(vp, 0, td); -out2: +out: return (error); } Index: kern/vfs_syscalls.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v retrieving revision 1.285 diff -u -r1.285 vfs_syscalls.c --- kern/vfs_syscalls.c 1 Sep 2002 20:37:28 -0000 1.285 +++ kern/vfs_syscalls.c 10 Sep 2002 03:00:50 -0000 @@ -1027,10 +1027,13 @@ if (nd.ni_vp != NULL) { vrele(nd.ni_vp); error = EEXIST; - } else { + } else if (nd.ni_dvp == vp || + (error = vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td)) == 0) { VOP_LEASE(nd.ni_dvp, td, td->td_ucred, LEASE_WRITE); VOP_LEASE(vp, td, td->td_ucred, LEASE_WRITE); error = VOP_LINK(nd.ni_dvp, vp, &nd.ni_cnd); + if (nd.ni_dvp != vp) + VOP_UNLOCK(vp, 0, td); } NDFREE(&nd, NDF_ONLY_PNBUF); vput(nd.ni_dvp); Index: kern/vnode_if.src =================================================================== RCS file: /home/ncvs/src/sys/kern/vnode_if.src,v retrieving revision 1.56 diff -u -r1.56 vnode_if.src --- kern/vnode_if.src 5 Sep 2002 20:56:14 -0000 1.56 +++ kern/vnode_if.src 10 Sep 2002 02:29:56 -0000 @@ -261,7 +261,7 @@ # #% link tdvp L L L -#% link vp U U U +#% link vp L L L # vop_link { IN struct vnode *tdvp; Index: ufs/ufs/ufs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 1.204 diff -u -r1.204 ufs_vnops.c --- ufs/ufs/ufs_vnops.c 15 Aug 2002 20:55:08 -0000 1.204 +++ ufs/ufs/ufs_vnops.c 10 Sep 2002 03:08:48 -0000 @@ -814,7 +814,6 @@ struct vnode *vp = ap->a_vp; struct vnode *tdvp = ap->a_tdvp; struct componentname *cnp = ap->a_cnp; - struct thread *td = cnp->cn_thread; struct inode *ip; struct direct newdir; int error; @@ -825,19 +824,16 @@ #endif if (tdvp->v_mount != vp->v_mount) { error = EXDEV; - goto out2; - } - if (tdvp != vp && (error = vn_lock(vp, LK_EXCLUSIVE, td))) { - goto out2; + goto out; } ip = VTOI(vp); if ((nlink_t)ip->i_nlink >= LINK_MAX) { error = EMLINK; - goto out1; + goto out; } if (ip->i_flags & (IMMUTABLE | APPEND)) { error = EPERM; - goto out1; + goto out; } ip->i_effnlink++; ip->i_nlink++; @@ -859,10 +855,7 @@ if (DOINGSOFTDEP(vp)) softdep_change_linkcnt(ip); } -out1: - if (tdvp != vp) - VOP_UNLOCK(vp, 0, td); -out2: +out: VN_KNOTE(vp, NOTE_LINK); VN_KNOTE(tdvp, NOTE_WRITE); return (error); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 0:38: 5 2002 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 7158B37B400; Tue, 10 Sep 2002 00:38:01 -0700 (PDT) Received: from mail.j.dendai.ac.jp (mail.j.dendai.ac.jp [133.14.49.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFCED43E6A; Tue, 10 Sep 2002 00:38:00 -0700 (PDT) (envelope-from fujimoto@j.dendai.ac.jp) Received: from j.dendai.ac.jp (yebisu.j.dendai.ac.jp [133.14.49.224]) by mail.j.dendai.ac.jp (Postfix) with ESMTP id 6CC938039; Tue, 10 Sep 2002 13:07:28 +0900 (JST) Message-ID: <3D7D7000.AEB88A8E@j.dendai.ac.jp> Date: Tue, 10 Sep 2002 13:07:28 +0900 From: FUJIMOTO Kou Organization: Tokyo Denki University X-Mailer: Mozilla 4.78 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: current@freebsd.org, mobile@freebsd.org Subject: Re: Bluetooth stack for FreeBSD References: <13008.1031593011@critter.freebsd.dk> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <3D7CDB63.1E640A3F@exodus.net>, Maksim Yevmenkin writes: > > >I still would like to hear from people. I'm extremely > >surprised that FreeBSD community seems not interested in > >this at all. I got very few replies from few people > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > Most of us probably doesn't have any bluetooth hardware... I have a BT PCMCIA card by IBM, a BT USB adapter by MITSUMI, a C413S BT mobile phone by Sony, and a BT adapter for Sony CLIE. A communication between CLIE/C413S and PC does not work properly with Windows OS. Mobile phone and CLIE work well, because no Windows needed and it's a Sony-to-Sony connection! Sony is eager to introduce BT and there're several models of VAIO notebooks that have built-in BT interfaces. Anyway, I am willing to be a tester and you could find more ones in Japan, because there're dozens of Bluetooth PCs and devices. -- FUJIMOTO Kou, Tokyo Denki University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 0:44:30 2002 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 C536937B400 for ; Tue, 10 Sep 2002 00:44:28 -0700 (PDT) Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C8D543E4A for ; Tue, 10 Sep 2002 00:44:27 -0700 (PDT) (envelope-from mb@imp.ch) Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7]) by mail.imp.ch (8.12.3/8.12.3) with ESMTP id g8A7iKO9091275; Tue, 10 Sep 2002 09:44:21 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by nbs.imp.ch (8.12.3/8.12.3) with ESMTP id g8A7iK75539245; Tue, 10 Sep 2002 09:44:20 +0200 (MES) Date: Tue, 10 Sep 2002 09:49:33 +0200 (CEST) From: Martin Blapp To: Vincent Poy Cc: Subject: Re: Uncommitted dc0 fixes ... In-Reply-To: <20020909130911.U2914-100000@oahu.WURLDLINK.NET> Message-ID: <20020910094649.C50626-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, > 1) dc driver uses wrong case to read MAC from eeprom. > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482 > > This one seems to break data sending/receiving as the only thing that > works is pinging and that's only on the alias/secondary IP and not the > primary IP network which is completely unpingable. I expected this one to be the problem PR. I'll look at it this evening. + case DC_DEVICEID_EN2242: /* and DC_DEVICEID_EN5251B: */ + if (revision < DC_REVISION_EN5251B) { + sc->dc_type = DC_TYPE_AN985; + } else { + sc->dc_type = DC_TYPE_EN5152B; + } + sc->dc_flags |= DC_TX_USE_TX_INTR; + sc->dc_flags |= DC_TX_ADMTEK_WAR; + sc->dc_pmode = DC_PMODE_MII; + break; case DC_DEVICEID_AN985: - case DC_DEVICEID_EN2242: sc->dc_type = DC_TYPE_AN985; sc->dc_flags |= DC_TX_USE_TX_INTR; sc->dc_flags |= DC_TX_ADMTEK_WAR; This change looks wrong to me. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 0:52:37 2002 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 C89BF37B400 for ; Tue, 10 Sep 2002 00:52:34 -0700 (PDT) Received: from demos.su (mx.demos.su [194.87.0.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0107143E4A for ; Tue, 10 Sep 2002 00:52:33 -0700 (PDT) (envelope-from katty@sinbin.demos.su) Received: from [194.87.5.31] (HELO sinbin.demos.su) by demos.su (CommuniGate Pro SMTP 3.5.9/D) with ESMTP-TLS id 49999759 for current@freebsd.org; Tue, 10 Sep 2002 11:52:31 +0400 Received: from sinbin.demos.su by sinbin.demos.su with ESMTPœ id g8A7qTTb085506; (8.12.6/D) Tue, 10 Sep 2002 11:52:29 +0400 (MSD) Received: (from katty@localhost) by sinbin.demos.su (8.12.6/8.12.5/Submit) id g8A7qTdB085505 for current@freebsd.org; Tue, 10 Sep 2002 11:52:29 +0400 (MSD) Date: Tue, 10 Sep 2002 11:52:29 +0400 From: Ekaterina Kochetkova To: current@freebsd.org Subject: unsubscribe Message-ID: <20020910115229.B81008@sinbin.demos.su> Reply-To: Ekaterina Kochetkova Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: "Demos Company Ltd., Moscow, Russia" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG unsubscribe -- katty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 0:58:57 2002 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 3E3C337B400 for ; Tue, 10 Sep 2002 00:58:55 -0700 (PDT) Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56B2543E6E for ; Tue, 10 Sep 2002 00:58:54 -0700 (PDT) (envelope-from mb@imp.ch) Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7]) by mail.imp.ch (8.12.3/8.12.3) with ESMTP id g8A7wrO9095407; Tue, 10 Sep 2002 09:58:53 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by nbs.imp.ch (8.12.3/8.12.3) with ESMTP id g8A7wr75533217; Tue, 10 Sep 2002 09:58:53 +0200 (MES) Date: Tue, 10 Sep 2002 10:04:05 +0200 (CEST) From: Martin Blapp To: Vincent Poy Cc: Subject: Re: Uncommitted dc0 fixes ... In-Reply-To: <20020909130911.U2914-100000@oahu.WURLDLINK.NET> Message-ID: <20020910100124.V50626-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, > and Martins patch: > This one works standalone and with 2 and 3 above. It seems to have > increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec. Cool. > Ofcourse, for some odd reason, if the ftp was done from a Windows XP Pro > machine, it's only 6722KBytes/sec. Hmm. TCP-window size ? And did you already tried to turn on/off the sysctls ? net.inet.tcp.rfc1323 net.inet.tcp.rfc1644 Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 1:18:22 2002 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 8CA2F37B400 for ; Tue, 10 Sep 2002 01:18:19 -0700 (PDT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C60543E3B for ; Tue, 10 Sep 2002 01:18:18 -0700 (PDT) (envelope-from tanimura@axe-inc.co.jp) Received: from t-axegw.t.axe-inc.co.jp ([218.230.241.250]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with ESMTP id RAA24205; Tue, 10 Sep 2002 17:18:01 +0900 (JST) Received: from shojaku.t.axe-inc.co.jp ([192.168.6.103]) by t-axegw.t.axe-inc.co.jp (8.12.6/3.7W-Axe-Gwhost-Tokyo) with ESMTP id g8A8HV14001945 ; Tue, 10 Sep 2002 17:17:31 +0900 (JST) Received: from shojaku.t.axe-inc.co.jp (localhost [127.0.0.1]) by shojaku.t.axe-inc.co.jp (8.12.5/3.7W-Axe-Tokyo-NoARR) with ESMTP id g8A8HU59018884 ; Tue, 10 Sep 2002 17:17:30 +0900 (JST) Message-Id: <200209100817.g8A8HU59018884@shojaku.t.axe-inc.co.jp> Date: Tue, 10 Sep 2002 17:17:30 +0900 From: Seigo Tanimura To: Alexander Leidinger Cc: current@FreeBSD.ORG, tanimura@axe-inc.co.jp, tanimura@tanimura.dyndns.org Subject: Re: panic: ffs_valloc: dup alloc (with bt + contents of some structures) In-Reply-To: <20020829120525.2ef926e6.Alexander@Leidinger.net> References: <20020829120525.2ef926e6.Alexander@Leidinger.net> User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-1?Q?Kashiharajing=FE-mae?=) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: AXE, Inc. MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 29 Aug 2002 12:05:25 +0200, Alexander Leidinger said: Alexander> After booting the system up xdm didn't showed up and there was no Alexander> possibility to login on the console, so I breaked into ddb and send a Alexander> "kill 1" to xdm. Nothing happened so I again breaked into ddb and did a Alexander> "kill 1 1". Nothing happened again, so I decided to do a + Alexander> (several times) -> boom. Alexander> ---snip--- Alexander> panic: ffs_valloc: dup alloc Alexander> panic: from debugger Alexander> Uptime: 4m9s Alexander> pfs_vncache_unload(): 1 entries remaining Alexander> [...] Alexander> #7 0xc025573c in kdb_trap (type=3, code=0, regs=0xd1d707cc) Alexander> at ../../../i386/i386/db_interface.c:161 Alexander> #8 0xc0262e8a in trap (frame= Alexander> {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -1033800768, tf_esi = 256, tf_ebp = -774436848, tf_isp = -774436872, tf_ebx = 0, tf_edx = -1071016644, tf_ecx = -1070913265, tf_eax = -1070913281, tf_trapno = 3, tf_err = 0, tf_eip = -1071293992, tf_cs = 8, tf_eflags = 582, tf_esp = -1070958431, tf_ss = -774436824}) Alexander> at ../../../i386/i386/trap.c:606 Alexander> #9 0xc02569f8 in calltrap () at {standard input}:98 Alexander> #10 0xc019ae06 in panic (fmt=0x0) at ../../../kern/kern_shutdown.c:480 Alexander> #11 0xc020be9b in ffs_valloc () at ../../../ufs/ffs/ffs_alloc.c:871 (snip) I can reproduce that panic by extracting an archive of the Solaris source code (74.5MB approximately) into a filesystem on a swap-backed md(4) with softupdates. Except that the caller of ffs_valloc() is usually ufs_mkdir() in my case, ffs_nodealloccg() sometimes returns an inode with a nonzero i_mode. A filesystem without softupdates produces no panics, with or without async. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 1:19:11 2002 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 AFB5337B400; Tue, 10 Sep 2002 01:19:07 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FD9543E3B; Tue, 10 Sep 2002 01:19:06 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA05520; Tue, 10 Sep 2002 18:18:59 +1000 Date: Tue, 10 Sep 2002 18:26:42 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Don Lewis Cc: rwatson@FreeBSD.ORG, , Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209100419.g8A4JTwr093971@gw.catspoiler.org> Message-ID: <20020910182523.D367-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The locking changes in union_link() need a thorough review, > though the light testing of that I performed didn't turn up any > glaring problems. The changes are obviously just cleanups for leaf file systems, but I wonder why everything wasn't always locked at the top. Could it have been because locking all the way down is harmful? > Index: ufs/ufs/ufs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v > retrieving revision 1.204 > diff -u -r1.204 ufs_vnops.c > --- ufs/ufs/ufs_vnops.c 15 Aug 2002 20:55:08 -0000 1.204 > +++ ufs/ufs/ufs_vnops.c 10 Sep 2002 03:08:48 -0000 > ... > @@ -825,19 +824,16 @@ > #endif > if (tdvp->v_mount != vp->v_mount) { > error = EXDEV; > - goto out2; > - } > - if (tdvp != vp && (error = vn_lock(vp, LK_EXCLUSIVE, td))) { > - goto out2; > + goto out; > } > ip = VTOI(vp); > if ((nlink_t)ip->i_nlink >= LINK_MAX) { > error = EMLINK; > - goto out1; > + goto out; > } > if (ip->i_flags & (IMMUTABLE | APPEND)) { > error = EPERM; > - goto out1; > + goto out; > } > ip->i_effnlink++; > ip->i_nlink++; > @@ -859,10 +855,7 @@ > if (DOINGSOFTDEP(vp)) > softdep_change_linkcnt(ip); > } > -out1: > - if (tdvp != vp) > - VOP_UNLOCK(vp, 0, td); > -out2: > +out: > VN_KNOTE(vp, NOTE_LINK); > VN_KNOTE(tdvp, NOTE_WRITE); > return (error); The ugly gotos and uglier braces near them could be replaced by simple returns now. Some related points: (1) I think it is just a bug that null changes for failed operations are knoted. It might be useful for knote to report attempted operations and why they failed, but reporting failed operations doesn't seem very useful unless they can be distinguished from successful ones. Anyway, knote isn't told about failures before here. Doing the knoting at a higher level upon successful completion would work better in many cases including the above. This would be similar to setting file times only upon successful completion, except it is easier because knotes apply to vnodes but file times are fs-specific. In both cases, it might be useful to set flags at lower levels in some cases and back out the settings together with backing out the main effects of the operation if the operation becomes unsuccessful later. (2) The gotos seem to exist to join common code that does a vput(tdvp) as well as the things removed in the above. The vput() was removed some time ago. There also used to be VOP_ABORTOP()s, but they weren't in the common code for some reason. (3) Removing the VOP_ABORTOP() after vn_lock() failure left ugly braces. Similarly in ext2fs, except its support for kevent is missing in most places including here. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 1:49:50 2002 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 A424537B400; Tue, 10 Sep 2002 01:49:47 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1859D43E6A; Tue, 10 Sep 2002 01:49:47 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8A8nWwr094342; Tue, 10 Sep 2002 01:49:36 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209100849.g8A8nWwr094342@gw.catspoiler.org> Date: Tue, 10 Sep 2002 01:49:32 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: bde@zeta.org.au Cc: rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <20020910182523.D367-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Bruce Evans wrote: >> The locking changes in union_link() need a thorough review, >> though the light testing of that I performed didn't turn up any >> glaring problems. > > The changes are obviously just cleanups for leaf file systems, but I > wonder why everything wasn't always locked at the top. Could it have > been because locking all the way down is harmful? Judging by how the leaf filesystems were careful to only do the lock if tdvp != vp, I suspect there was the potential for a deadlock if both vnodes were automatically locked at the top. > The ugly gotos and uglier braces near them could be replaced by simple > returns now. Some related points: We can't change the gotos to returns unless we also make the change in (1). I think I agree with you about (1), but VN_KNOTE() doesn't have a man page and I didn't want to change anything that I didn't understand. I think (1) deserves a separate sweep and mega-commit. A quick look at ufs_vnops.c turns up a number of inconsistencies in the use of VN_KNOTE(). > (1) I think it is just a bug that null changes for failed operations are > knoted. It might be useful for knote to report attempted operations > and why they failed, but reporting failed operations doesn't seem > very useful unless they can be distinguished from successful ones. > Anyway, knote isn't told about failures before here. Doing the > knoting at a higher level upon successful completion would work > better in many cases including the above. This would be similar > to setting file times only upon successful completion, except it is > easier because knotes apply to vnodes but file times are fs-specific. > In both cases, it might be useful to set flags at lower levels in > some cases and back out the settings together with backing out the > main effects of the operation if the operation becomes unsuccessful > later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 2:17:48 2002 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 998F137B400 for ; Tue, 10 Sep 2002 02:17:45 -0700 (PDT) Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E2043E65 for ; Tue, 10 Sep 2002 02:17:44 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from northrelay01.pok.ibm.com (northrelay01.pok.ibm.com [9.56.224.149]) by e2.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g8A9HhIV263570 for ; Tue, 10 Sep 2002 05:17:43 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by northrelay01.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g8A9HeBP185726 for ; Tue, 10 Sep 2002 05:17:42 -0400 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id D94093750; Tue, 10 Sep 2002 14:47:28 +0530 (IST) Subject: Re: Kernel hangs during boot - latest cvsup References: <20020909120516.A2914-100000@oahu.WURLDLINK.NET> From: Sid Carter Operating-System: Turing OS XCVIII Disclaimer: Not speaking for anyone in any way, shape, or form. Copyright: Copyright 2002 Sid Carter - All Rights Reserved To: current@freebsd.org Reply-To: sidcarter@symonds.net Organization: Sid Carter GmBH. Date: 10 Sep 2002 14:47:28 +0530 In-Reply-To: <20020909120516.A2914-100000@oahu.WURLDLINK.NET> Message-ID: <86r8g2cifr.fsf@calvin.in.ibm.com> Lines: 42 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Mon, 9 Sep 2002 12:09:05 -1000 (HST), Vincent Poy said: Vincent> On Mon, 9 Sep 2002, Julian Elischer wrote: >> On Mon, 9 Sep 2002, Vincent Poy wrote: >> > > Timecounters tick every 10.000 msec >> > > ----------------------------------- >> >> >> boot -v might be instructive.. Vincent> It seems in the latest -CURRENT, the following in the kernel Vincent> config file based on the GENERIC kernel: Vincent> options MAXMEM=786432 Hi, I just did a cvsup , clean and cleandir and stuff and when I try to compile the kernel, I get this error cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -fno-common -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/cardbus/cardbus.c cc1: warnings being treated as errors /usr/src/sys/dev/cardbus/cardbus.c: In function `cardbus_driver_added': /usr/src/sys/dev/cardbus/cardbus.c:319: warning: unused variable `cardattached' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Anyone else getting this ? Regards Sid -- The [Ford Foundation] is a large body of money completely surrounded by people who want some. -- Dwight MacDonald Sid Carter - http://symonds.net/~sidcarter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 2:50:31 2002 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 0BB5237B400 for ; Tue, 10 Sep 2002 02:50:29 -0700 (PDT) Received: from e6.ny.us.ibm.com (e6.ny.us.ibm.com [32.97.182.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DA7143E3B for ; Tue, 10 Sep 2002 02:50:28 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from northrelay01.pok.ibm.com (northrelay01.pok.ibm.com [9.56.224.149]) by e6.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g8A9oRlg020900 for ; Tue, 10 Sep 2002 05:50:27 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by northrelay01.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g8A9oOBP233574 for ; Tue, 10 Sep 2002 05:50:25 -0400 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id C9B96375C; Tue, 10 Sep 2002 15:20:22 +0530 (IST) Subject: Re: Kernel hangs during boot - latest cvsup References: From: Sid Carter Operating-System: Turing OS XCVIII Disclaimer: Not speaking for anyone in any way, shape, or form. Copyright: Copyright 2002 Sid Carter - All Rights Reserved To: current@freebsd.org Reply-To: sidcarter@symonds.net Organization: Sid Carter GmBH. Date: 10 Sep 2002 15:20:22 +0530 In-Reply-To: Message-ID: <86n0qqjhr5.fsf@calvin.in.ibm.com> Lines: 33 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Mon, 9 Sep 2002 14:37:45 -0700 (PDT), Julian Elischer said: Julian> On Mon, 9 Sep 2002, Vincent Poy wrote: >> > I compiled the kernel last nite and I haven't been able to boot into the >> > system with that kernel. This is where the kernel hangs >> > >> > ---------------------------- >> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >> > Timecounters tick every 10.000 msec >> > ----------------------------------- Julian> boot -v might be instructive.. Hi, boot -v gives me this. Sep 10 15:13:34 calvin kernel: 0 accounted for Sep 10 15:13:34 calvin kernel: Device configuration finished. Sep 10 15:13:34 calvin kernel: procfs registered Sep 10 15:13:34 calvin kernel: Timecounters tick every 10.000 msec Sep 10 15:13:34 calvin kernel: bpf:lo0 attached and of course hangs at the last statement. Regards Sid -- Don't let your mind wander -- it's too little to be let out alone. Sid Carter - http://symonds.net/~sidcarter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 2:56:10 2002 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 626D037B400; Tue, 10 Sep 2002 02:56:07 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDA1343E65; Tue, 10 Sep 2002 02:56:05 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA18045; Tue, 10 Sep 2002 19:55:54 +1000 Date: Tue, 10 Sep 2002 20:03:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Don Lewis Cc: rwatson@FreeBSD.ORG, , Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209100849.g8A8nWwr094342@gw.catspoiler.org> Message-ID: <20020910194838.M876-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Don Lewis wrote: > On 10 Sep, Bruce Evans wrote: > >> The locking changes in union_link() need a thorough review, > >> though the light testing of that I performed didn't turn up any > >> glaring problems. > > > > The changes are obviously just cleanups for leaf file systems, but I > > wonder why everything wasn't always locked at the top. Could it have > > been because locking all the way down is harmful? > > Judging by how the leaf filesystems were careful to only do the lock if > tdvp != vp, I suspect there was the potential for a deadlock if both > vnodes were automatically locked at the top. I think this is because some places are still worrying about using link(2) on directories. I think there aren't any significant problems when vp is not a directory. Hard linking of directories was permitted (and perhaps even supported) until relatively recently: % RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v % Working file: vfs_syscalls.c % head: 1.285 % ... % ---------------------------- % revision 1.48 % date: 1996/05/24 16:19:23; author: peter; state: Exp; lines: +9 -7 % Dont allow directories to be link()ed or unlink()ed, even for root % (returns EPERM always, the errno is specified by POSIX). % % If you really have a desperate need to link or unlink a directory, you % can use fsdb. :-) % % This should stop any chance of ftpd, rdist, "rm -rf", etc from % bugging out and damaging the filesystem structure or loosing races % with malicious users. % % Reviewed by: davidg, bde % ---------------------------- > > The ugly gotos and uglier braces near them could be replaced by simple > > returns now. Some related points: > > We can't change the gotos to returns unless we also make the change in > (1). I think I agree with you about (1), but VN_KNOTE() doesn't have a > man page and I didn't want to change anything that I didn't understand. > I think (1) deserves a separate sweep and mega-commit. A quick look at > ufs_vnops.c turns up a number of inconsistencies in the use of > VN_KNOTE(). > > (1) I think it is just a bug that null changes for failed operations are > > knoted. It might be useful for knote to report attempted operations OK. I have fixed some of these inconsistencies in my version, but haven't done a sweep or tested kevent. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 3:46:19 2002 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 83EED37B400; Tue, 10 Sep 2002 03:46:17 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12E9C43E6A; Tue, 10 Sep 2002 03:46:17 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AAk7wr094789; Tue, 10 Sep 2002 03:46:11 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209101046.g8AAk7wr094789@gw.catspoiler.org> Date: Tue, 10 Sep 2002 03:46:07 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: bde@zeta.org.au Cc: rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <20020910194838.M876-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Bruce Evans wrote: > On Tue, 10 Sep 2002, Don Lewis wrote: > >> On 10 Sep, Bruce Evans wrote: >> > The changes are obviously just cleanups for leaf file systems, but I >> > wonder why everything wasn't always locked at the top. Could it have >> > been because locking all the way down is harmful? >> >> Judging by how the leaf filesystems were careful to only do the lock if >> tdvp != vp, I suspect there was the potential for a deadlock if both >> vnodes were automatically locked at the top. ... or panic "locking against myself" ... > I think this is because some places are still worrying about using > link(2) on directories. I think there aren't any significant problems > when vp is not a directory. Hard linking of directories was permitted > (and perhaps even supported) until relatively recently: I suspect that you are right about this. If so, it should be able to let namei() lock the first vnode since we check its type and bail out if it is a directory before the second namei() call. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 4:11: 3 2002 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 6AE9137B400; Tue, 10 Sep 2002 04:10:59 -0700 (PDT) Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 104A843E3B; Tue, 10 Sep 2002 04:10:59 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0024.cvx22-bradley.dialup.earthlink.net ([209.179.198.24] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17oiuv-00018O-00; Tue, 10 Sep 2002 04:10:50 -0700 Message-ID: <3D7DD2FC.A559730E@mindspring.com> Date: Tue, 10 Sep 2002 04:09:48 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Don Lewis , rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: vnode lock assertion problem in nfs_link() References: <20020910182523.D367-100000@gamplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > The changes are obviously just cleanups for leaf file systems, but I > wonder why everything wasn't always locked at the top. Could it have > been because locking all the way down is harmful? For a stacked local media FS, you can end up with a deadlock, if a lower vnode is exposed into the visible namespace, e.g.: o o /usr/myfs2 | /usr/myfs1 | ,------------------.------------------. | | | / | | quotafs o | / | `------------------' / | | \ / | | ffs o | `-------------------------------------' Probably, the correct thing to do is to lock at the top, and lock the lower in all intermediate layers as the top is locked. This requires that the operation from the top look the same from the top and from the bottom of the VFS stacking layer. This probably needs a veto-VOP that is a NUL operation for local media FSs that can't be stacked on something other than the VM system. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 4:14: 3 2002 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 B501137B400 for ; Tue, 10 Sep 2002 04:13:59 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF95B43E65 for ; Tue, 10 Sep 2002 04:13:58 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8ABDZ438400; Tue, 10 Sep 2002 01:13:35 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Tue, 10 Sep 2002 01:13:35 -1000 (HST) From: Vincent Poy To: Sid Carter Cc: current@FreeBSD.ORG Subject: Re: Kernel hangs during boot - latest cvsup In-Reply-To: <86r8g2cifr.fsf@calvin.in.ibm.com> Message-ID: <20020910011224.G2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep 2002, Sid Carter wrote: > >>>>> On Mon, 9 Sep 2002 12:09:05 -1000 (HST), Vincent Poy said: > > Vincent> On Mon, 9 Sep 2002, Julian Elischer wrote: > >> On Mon, 9 Sep 2002, Vincent Poy wrote: > >> > > Timecounters tick every 10.000 msec > >> > > ----------------------------------- > >> > >> > >> boot -v might be instructive.. > Vincent> It seems in the latest -CURRENT, the following in the kernel > Vincent> config file based on the GENERIC kernel: > > Vincent> options MAXMEM=786432 > > Hi, > > I just did a cvsup , clean and cleandir and stuff and when I try to > compile the kernel, I get this error > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -fno-common -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/cardbus/cardbus.c > cc1: warnings being treated as errors > /usr/src/sys/dev/cardbus/cardbus.c: In function `cardbus_driver_added': > /usr/src/sys/dev/cardbus/cardbus.c:319: warning: unused variable `cardattached' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/GENERIC. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > > Anyone else getting this ? Nope, the GENERIC I built is based on the September 8, 2002 -current and has been fine. My only problem seems to be if MAXMEM is defined in a kernel config, it hangs on bootup. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 4:23:23 2002 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 CE98737B400 for ; Tue, 10 Sep 2002 04:23:20 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF7D43E3B for ; Tue, 10 Sep 2002 04:23:20 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8ABMxe38482; Tue, 10 Sep 2002 01:23:00 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Tue, 10 Sep 2002 01:22:59 -1000 (HST) From: Vincent Poy To: Martin Blapp Cc: current@FreeBSD.ORG Subject: Re: Uncommitted dc0 fixes ... In-Reply-To: <20020910094649.C50626-100000@levais.imp.ch> Message-ID: <20020910012149.E2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Martin Blapp wrote: Hi, > > 1) dc driver uses wrong case to read MAC from eeprom. > > > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482 > > > > This one seems to break data sending/receiving as the only thing that > > works is pinging and that's only on the alias/secondary IP and not the > > primary IP network which is completely unpingable. > > I expected this one to be the problem PR. I'll look at it this evening. I guess it's probably making everything detect as a EN5152B or something. > + case DC_DEVICEID_EN2242: /* and DC_DEVICEID_EN5251B: */ > + if (revision < DC_REVISION_EN5251B) { > + sc->dc_type = DC_TYPE_AN985; > + } else { > + sc->dc_type = DC_TYPE_EN5152B; > + } > + sc->dc_flags |= DC_TX_USE_TX_INTR; > + sc->dc_flags |= DC_TX_ADMTEK_WAR; > + sc->dc_pmode = DC_PMODE_MII; > + break; > case DC_DEVICEID_AN985: > - case DC_DEVICEID_EN2242: > sc->dc_type = DC_TYPE_AN985; > sc->dc_flags |= DC_TX_USE_TX_INTR; > sc->dc_flags |= DC_TX_ADMTEK_WAR; > > This change looks wrong to me. I guess it probably works for the originator of the PR. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 4:26: 5 2002 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 F11AA37B400 for ; Tue, 10 Sep 2002 04:26:01 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 644D343E4A for ; Tue, 10 Sep 2002 04:26:01 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8ABPgW38519; Tue, 10 Sep 2002 01:25:42 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Tue, 10 Sep 2002 01:25:42 -1000 (HST) From: Vincent Poy To: Martin Blapp Cc: current@FreeBSD.ORG Subject: Re: Uncommitted dc0 fixes ... In-Reply-To: <20020910100124.V50626-100000@levais.imp.ch> Message-ID: <20020910012306.R2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Martin: On Tue, 10 Sep 2002, Martin Blapp wrote: > > and Martins patch: > > This one works standalone and with 2 and 3 above. It seems to have > > increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec. > > Cool. Seems to depend on which notebook the card is in. With the Dell Inspiron 8200, it does do the above rates and 6722Kbyte/sec if the ftp was initiated from a Windows box. On the IBM ThinkPad 770Z, the rates are 6600Kbyte/sec on the FreeBSD machine but 3085Kbyte/sec if the ftp is initiated from the Windows machine. > > Ofcourse, for some odd reason, if the ftp was done from a Windows XP Pro > > machine, it's only 6722KBytes/sec. > > Hmm. TCP-window size ? And did you already tried to > turn on/off the sysctls ? The TCP-Window size I have is 32767 on the Windows machines. > net.inet.tcp.rfc1323 > net.inet.tcp.rfc1644 Yep tried both of those already and didn't make a difference. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 4:55: 0 2002 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 5012037B400; Tue, 10 Sep 2002 04:54:55 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BB0743E4A; Tue, 10 Sep 2002 04:54:54 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8ABsdwr094898; Tue, 10 Sep 2002 04:54:43 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209101154.g8ABsdwr094898@gw.catspoiler.org> Date: Tue, 10 Sep 2002 04:54:39 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: bde@zeta.org.au Cc: rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <200209101046.g8AAk7wr094789@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Don Lewis wrote: > On 10 Sep, Bruce Evans wrote: >> On Tue, 10 Sep 2002, Don Lewis wrote: >> >>> On 10 Sep, Bruce Evans wrote: > >>> > The changes are obviously just cleanups for leaf file systems, but I >>> > wonder why everything wasn't always locked at the top. Could it have >>> > been because locking all the way down is harmful? >> I think this is because some places are still worrying about using >> link(2) on directories. I think there aren't any significant problems >> when vp is not a directory. Hard linking of directories was permitted >> (and perhaps even supported) until relatively recently: > > I suspect that you are right about this. If so, it should be able to > let namei() lock the first vnode since we check its type and bail out if > it is a directory before the second namei() call. I looked at namei() and ufs_lookup() and found a problem with telling the first namei() to grab the lock. It appears that the *_lookup() routines always lock the child vnode, and namei() later releases the lock if LOCKLEAF is not set. If we passed LOCKLEAF to the first namei(), then link("/foo/bar", "/foo/bar") would attempt to lock "bar" twice. Because we now bail out early if the first vnode turns out to be a pointer, I believe we can dispense with the vnode inequality test and always grab the lock. BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the reference has been dropped with vput() or vrele()? Here's a replacement for the kern_link() patch in my previous patch file: Index: vfs_syscalls.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v retrieving revision 1.285 diff -u -r1.285 vfs_syscalls.c --- vfs_syscalls.c 1 Sep 2002 20:37:28 -0000 1.285 +++ vfs_syscalls.c 10 Sep 2002 11:28:01 -0000 @@ -1027,10 +1027,12 @@ if (nd.ni_vp != NULL) { vrele(nd.ni_vp); error = EEXIST; - } else { + } else if ((error = vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td)) + == 0) { VOP_LEASE(nd.ni_dvp, td, td->td_ucred, LEASE_WRITE); VOP_LEASE(vp, td, td->td_ucred, LEASE_WRITE); error = VOP_LINK(nd.ni_dvp, vp, &nd.ni_cnd); + VOP_UNLOCK(vp, 0, td); } NDFREE(&nd, NDF_ONLY_PNBUF); vput(nd.ni_dvp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 5: 2:43 2002 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 C56B237B406; Tue, 10 Sep 2002 05:02:38 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B34143EA9; Tue, 10 Sep 2002 05:02:15 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AC0uwr094918; Tue, 10 Sep 2002 05:01:01 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209101201.g8AC0uwr094918@gw.catspoiler.org> Date: Tue, 10 Sep 2002 05:00:56 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: tlambert2@mindspring.com Cc: bde@zeta.org.au, rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <3D7DD2FC.A559730E@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Terry Lambert wrote: > Bruce Evans wrote: >> The changes are obviously just cleanups for leaf file systems, but I >> wonder why everything wasn't always locked at the top. Could it have >> been because locking all the way down is harmful? > > For a stacked local media FS, you can end up with a deadlock, if > a lower vnode is exposed into the visible namespace, e.g.:> > o o > /usr/myfs2 | /usr/myfs1 | > ,------------------.------------------. > | | | / | > | quotafs o | / | > `------------------' / | > | \ / | > | ffs o | > `-------------------------------------' In general you are correct. In this case I think we are safe if we look up the first vnode and leave it unlocked, verify that it is not a directory, do the second lookup and only lock the parent directory, and only then lock the first vnode. Even with stacking, we won't attempt to lock the same vnode twice because we guarantee that the vnodes are of different types before we do the second lock. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 5:26:53 2002 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 BC98637B400; Tue, 10 Sep 2002 05:26:50 -0700 (PDT) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1329243E3B; Tue, 10 Sep 2002 05:26:50 -0700 (PDT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (localhost [127.0.0.1]) by corbulon.video-collage.com (8.12.2/8.12.2) with ESMTP id g8ACQhPW063431 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Sep 2002 08:26:43 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: (from mi@localhost) by corbulon.video-collage.com (8.12.2/8.12.2/Submit) id g8ACQglQ063430; Tue, 10 Sep 2002 08:26:42 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200209101226.g8ACQglQ063430@corbulon.video-collage.com> Subject: freeze with the CardBus NIC 3CCFE575BT To: current@FreeBSD.org, mobile@FreeBSD.org Date: Tue, 10 Sep 2002 08:26:42 -0400 (EDT) Cc: imp@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL92b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Regardless of whether the xl driver is linked into the kernel or loaded as a module, the machine freezes shortly after ifconfig-ing the card. Sunday's -current. Complete freeeze -- can not go into debugger... More information available upon request... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 5:29:58 2002 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 039F137B400 for ; Tue, 10 Sep 2002 05:29:52 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA8DA43E4A for ; Tue, 10 Sep 2002 05:29:50 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g8ACTnZP010572; Tue, 10 Sep 2002 14:29:49 +0200 Received: (nullmailer pid 3310 invoked by uid 1000); Tue, 10 Sep 2002 12:29:10 -0000 Date: Tue, 10 Sep 2002 14:29:10 +0200 From: Mark Santcroos To: Mitsuru IWASAKI Cc: acpi-jp@jp.FreeBSD.org, current@FreeBSD.ORG Subject: Re: ACPI video driver (for Dell Latitude C640) Message-ID: <20020910122910.GA2338@laptop.6bone.nl> References: <20020825193459.GA725@laptop.6bone.nl> <20020826.223258.00576482.iwasaki@jp.FreeBSD.org> <20020826134202.GA1637@laptop.6bone.nl> <20020827.175855.112858711.iwasaki@jp.FreeBSD.org> <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020829211115.GB2059@laptop.6bone.nl> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 29, 2002 at 11:11:15PM +0200, Mark Santcroos wrote: > I worked around this by making the driver a child of pci instead of a > child of acpi. (Which is even more correct too) My driver is a child of acpi again and at this point it always seems to be called at resume too. I don't know whether that is due to the latest acpi patches (29/8) or other changes in the kernel. (At this point I don't want to spent time tracking that down) > However, getting my screen back doesn't work yet. So there might be more > too it. (In the worst case, the 'OFF' I do, is different than the 'OFF' > the system does, so doing my 'ON' doesn't influence the systems 'OFF') It turned out to be the 'worst case'. The 'OFF' I was doing is not the same 'OFF' as the system itself is doing. (Actually my OFF was a display switch from one to another without going to the other actually. It was a wild guess and turned to be wrong) Do you think that there is a change that this is in the direction of DPMS, or is that very unliky? I tried to find the spec for DPMS but it seems to be a closed on (at least to non-members). I'm back to where I started basicly (besides knowing more about acpi now). Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 6:46:25 2002 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 E35E837B400; Tue, 10 Sep 2002 06:46:20 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19CE043E3B; Tue, 10 Sep 2002 06:46:20 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g8ADjtOo088370; Tue, 10 Sep 2002 09:45:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 10 Sep 2002 09:45:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Don Lewis Cc: bde@zeta.org.au, current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209101154.g8ABsdwr094898@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Don Lewis wrote: > >>> > The changes are obviously just cleanups for leaf file systems, but I > >>> > wonder why everything wasn't always locked at the top. Could it have > >>> > been because locking all the way down is harmful? > > >> I think this is because some places are still worrying about using > >> link(2) on directories. I think there aren't any significant problems > >> when vp is not a directory. Hard linking of directories was permitted > >> (and perhaps even supported) until relatively recently: > > > > I suspect that you are right about this. If so, it should be able to > > let namei() lock the first vnode since we check its type and bail out if > > it is a directory before the second namei() call. > > I looked at namei() and ufs_lookup() and found a problem with telling > the first namei() to grab the lock. It appears that the *_lookup() > routines always lock the child vnode, and namei() later releases the > lock if LOCKLEAF is not set. If we passed LOCKLEAF to the first > namei(), then link("/foo/bar", "/foo/bar") would attempt to lock "bar" > twice. This also violates the "directory vnodes before file vnodes" lock order. Generally speaking, you must always lock directories before files, since files are always leaves, and directories may not be. The patch you have looks fine to me, since it grabs a reference to the file but doesn't lock it until after the directory look is held (and guarantees it's a leaf node by checking VDIR so that it's safe to do the locking later). > Because we now bail out early if the first vnode turns out to be a > pointer, I believe we can dispense with the vnode inequality test and > always grab the lock. Yeah. vp != VDIR, and dvp == VDIR due to earlier constraints, so we know that vp != dvp. > BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the > reference has been dropped with vput() or vrele()? Well, all the VFS code currently runs under Giant so a certain class of unsafe cases is avoided, but generally no: ASSERT_VOP_UNLOCKED() invokes a vnode operation to determine if the vnode is locked or not, which dereferences fields in the vnode that require a valid reference to use. Because none of the code there currently blocks, it's not an issue generally right now (as neither vnode is likely to have been deleted during the link operation, so releasing the reference is unlikely to result in chances to the vnode). It's worth fixing though. > Here's a replacement for the kern_link() patch in my previous patch > file: Looks good to me. I'm not familiar enough with unionfs and stacking to provide an effective review of that code, however. Maybe Jeff can give us some comments? (unionfs is actually the reason I stalled in making the same changes). > Index: vfs_syscalls.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_syscalls.c,v > retrieving revision 1.285 > diff -u -r1.285 vfs_syscalls.c > --- vfs_syscalls.c 1 Sep 2002 20:37:28 -0000 1.285 > +++ vfs_syscalls.c 10 Sep 2002 11:28:01 -0000 > @@ -1027,10 +1027,12 @@ > if (nd.ni_vp != NULL) { > vrele(nd.ni_vp); > error = EEXIST; > - } else { > + } else if ((error = vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td)) > + == 0) { > VOP_LEASE(nd.ni_dvp, td, td->td_ucred, LEASE_WRITE); > VOP_LEASE(vp, td, td->td_ucred, LEASE_WRITE); > error = VOP_LINK(nd.ni_dvp, vp, &nd.ni_cnd); > + VOP_UNLOCK(vp, 0, td); > } > NDFREE(&nd, NDF_ONLY_PNBUF); > vput(nd.ni_dvp); > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 7:16:32 2002 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 9142437B400 for ; Tue, 10 Sep 2002 07:16:27 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 574AC43E3B for ; Tue, 10 Sep 2002 07:16:27 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g8AEGQYB092216 for ; Tue, 10 Sep 2002 07:16:26 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g8AEGQHq092214 for current@freebsd.org; Tue, 10 Sep 2002 07:16:26 -0700 (PDT) Date: Tue, 10 Sep 2002 07:16:26 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209101416.g8AEGQHq092214@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Tue Sep 10 06:11:03 PDT 2002 -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Tue Sep 10 07:16:21 PDT 2002 -------------------------------------------------------------- >>> Kernel build for LINT started on Tue Sep 10 07:16:23 PDT 2002 -------------------------------------------------------------- ===> LINT config: Error: device "apm_saver" is unknown config: Error: device "cy" is unknown config: Error: device "cy" does not take a count config: 3 errors WARNING: kernel contains GPL contaminated ext2fs filesystem FYI: static unit limits for vcoda are set: NVCODA=4 FYI: static unit limits for dgb are set: NDGB=1 FYI: static unit limits for card are set: NCARD=1 FYI: static unit limits for meteor are set: NMETEOR=1 *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 7:21:14 2002 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 BDAB337B400; Tue, 10 Sep 2002 07:21:09 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id C560C43E4A; Tue, 10 Sep 2002 07:21:07 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA10840; Wed, 11 Sep 2002 00:21:01 +1000 Date: Wed, 11 Sep 2002 00:28:46 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Don Lewis Cc: rwatson@FreeBSD.ORG, , Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209101154.g8ABsdwr094898@gw.catspoiler.org> Message-ID: <20020911000503.L1981-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Don Lewis wrote: I have just one thing to add to Robert's reply. > BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the > reference has been dropped with vput() or vrele()? I think it is. It has some internal locking (v_interlock at least), and only asserts that the vnode is unlocked by curthread so it doesn't matter if another thread locks it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 8:22:33 2002 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 3E83E37B400 for ; Tue, 10 Sep 2002 08:22:30 -0700 (PDT) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A55143E42 for ; Tue, 10 Sep 2002 08:22:28 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g8AFMFY33137; Wed, 11 Sep 2002 00:22:15 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Wed, 11 Sep 2002 00:22:04 +0900 (JST) Message-Id: <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> To: acpi-jp@jp.FreeBSD.org, marks@ripe.net Cc: current@freebsd.org Subject: Re: [acpi-jp 1789] Re: ACPI video driver (for Dell Latitude C640) From: Mitsuru IWASAKI In-Reply-To: <20020910122910.GA2338@laptop.6bone.nl> References: <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> <20020910122910.GA2338@laptop.6bone.nl> X-Mailer: Mew version 2.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Thu, Aug 29, 2002 at 11:11:15PM +0200, Mark Santcroos wrote: > > I worked around this by making the driver a child of pci instead of a > > child of acpi. (Which is even more correct too) > > My driver is a child of acpi again and at this point it always seems to be > called at resume too. I don't know whether that is due to the latest acpi > patches (29/8) or other changes in the kernel. (At this point I don't want > to spent time tracking that down) Sorry for my late response. I've been checking your driver, and it always seems suspend/resume methods are called. It's; DRIVER_MODULE(acpi_agp, acpi, acpi_agp_driver, acpi_agp_devclass, 0, 0); version. > > However, getting my screen back doesn't work yet. So there might be more > > too it. (In the worst case, the 'OFF' I do, is different than the 'OFF' > > the system does, so doing my 'ON' doesn't influence the systems 'OFF') > > It turned out to be the 'worst case'. The 'OFF' I was doing is not the > same 'OFF' as the system itself is doing. > (Actually my OFF was a display switch from one to another without going to > the other actually. It was a wild guess and turned to be wrong) > > Do you think that there is a change that this is in the direction of DPMS, > or is that very unliky? I tried to find the spec for DPMS but it seems to > be a closed on (at least to non-members). It seems that old laptops don't have VGA specific ACPI objects, so many people will be happy if we can implement non-ACPI VGA driver w/ ATI chips hack. BTW, have you checked for XFree86 code? Hopefully we might find some hints on DPMS for ATI chips. > I'm back to where I started basicly (besides knowing more about acpi now). Never mind. I know one more guy who writing ACPI VGA driver, takawata-san(takawata@axe-inc.co.jp). Could you send him your latest code and contact him? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 8:27:30 2002 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 E820337B400 for ; Tue, 10 Sep 2002 08:27:27 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 170EF43E3B for ; Tue, 10 Sep 2002 08:27:27 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g8AFRQZP010598; Tue, 10 Sep 2002 17:27:26 +0200 Received: (nullmailer pid 5565 invoked by uid 1000); Tue, 10 Sep 2002 15:27:25 -0000 Date: Tue, 10 Sep 2002 17:27:25 +0200 From: Mark Santcroos To: Mitsuru IWASAKI Cc: acpi-jp@jp.FreeBSD.org, current@FreeBSD.ORG Subject: Re: [acpi-jp 1789] Re: ACPI video driver (for Dell Latitude C640) Message-ID: <20020910152725.GB2338@laptop.6bone.nl> References: <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> <20020910122910.GA2338@laptop.6bone.nl> <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Sep 11, 2002 at 12:22:04AM +0900, Mitsuru IWASAKI wrote: > It seems that old laptops don't have VGA specific ACPI objects, so > many people will be happy if we can implement non-ACPI VGA driver w/ > ATI chips hack. > BTW, have you checked for XFree86 code? Hopefully we might find > some hints on DPMS for ATI chips. Does this mean: "Yes, I think DPMS might have the answer" ? > Never mind. I know one more guy who writing ACPI VGA driver, > takawata-san(takawata@axe-inc.co.jp). Could you send him > your latest code and contact him? Ok, will do. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 8:36:18 2002 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 65F6037B400 for ; Tue, 10 Sep 2002 08:36:14 -0700 (PDT) Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id B744F43E72 for ; Tue, 10 Sep 2002 08:36:13 -0700 (PDT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Tue, 10 Sep 2002 08:36:13 -0700 Received: from adsl-64-173-182-155.dsl.mtry01.pacbell.net (adsl-64-173-182-155.dsl.mtry01.pacbell.net [64.173.182.155]) by Mail.EnContacto.Net (IMP) with HTTP for eculp@encontacto.net@encontacto.net; Tue, 10 Sep 2002 08:36:13 -0700 Message-ID: <1031672173.3d7e116d3a4e8@Mail.EnContacto.Net> Date: Tue, 10 Sep 2002 08:36:13 -0700 From: Edwin Culp To: current@freebsd.org Cc: "acpi-jp@jp.FreeBSD.org" Subject: acpi on compaq 1701CL with current. References: <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> <20020910122910.GA2338@laptop.6bone.nl> <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> In-Reply-To: <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Priority: 3 (Normal) X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just bought an new battery and that combined with the fact that I've seen so many recent emails about acpi that I decided to check my laptop. I've never really been able to take advantage of acpi with it and may never be able to, but previously I was able to do an acpidump and now I get: /root # acpidump /* RSD PTR: Checksum=202, OEMID=PTLTD, RsdtAddress=0x0fffbea3 */ acpidump: RSDT is corrupted with sysctl /root # sysctl hw.acpi sysctl: unknown oid 'hw.acpi' with kldstat /root # kldstat Id Refs Address Size Name 1 12 0xc0100000 349ffc kernel 2 1 0xc044a000 90b0 snd_maestro3.ko 3 1 0xc0454000 3fea8 acpi.ko 4 1 0xc241a000 5000 linprocfs.ko 5 1 0xc24d9000 14000 linux.ko I seem to have the module loaded automatically. Is this probably a configuration issue, an acpi problem or could it be a problem with the bios? Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:20:43 2002 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 AD37537B401; Tue, 10 Sep 2002 09:20:37 -0700 (PDT) Received: from duey.wolves.k12.mo.us (duey.wolves.k12.mo.us [207.160.214.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14E4643E75; Tue, 10 Sep 2002 09:20:37 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.wolves.k12.mo.us (cdillon@localhost [127.0.0.1]) by duey.wolves.k12.mo.us (8.12.5/8.12.5) with ESMTP id g8AGKUsd024421; Tue, 10 Sep 2002 11:20:30 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (cdillon@localhost) by duey.wolves.k12.mo.us (8.12.6/8.12.5/Submit) with ESMTP id g8AGKTLu024418; Tue, 10 Sep 2002 11:20:29 -0500 (CDT) X-Authentication-Warning: duey.wolves.k12.mo.us: cdillon owned process doing -bs Date: Tue, 10 Sep 2002 11:20:29 -0500 (CDT) From: Chris Dillon To: Maksim Yevmenkin Cc: current@FreeBSD.ORG, Subject: Re: Bluetooth stack for FreeBSD In-Reply-To: <3D7CDB63.1E640A3F@exodus.net> Message-ID: <20020910111741.H24092-100000@duey.wolves.k12.mo.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > I still would like to hear from people. I'm extremely surprised that > FreeBSD community seems not interested in this at all. I got very > few replies from few people (Julian Elischer, Terry Lambert - > thanks!) and that's it. I'm very interested, as are some other people I know, but we just don't have any bluetooth hardware to use yet. Don't think people don't care and thanks for the good work. :-) -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, ARM, and S/390 under development - http://www.freebsd.org No trees were harmed in the composition of this message, although some electrons were mildly inconvenienced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:21:36 2002 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 E584937B400 for ; Tue, 10 Sep 2002 09:21:33 -0700 (PDT) Received: from nebula.anchoragerescue.org (115-7-237-24-cable.anchorageak.net [24.237.7.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48C8B43E75 for ; Tue, 10 Sep 2002 09:21:33 -0700 (PDT) (envelope-from akbeech@sinbad.net) Received: from nova.anchoragerescue.org (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with ESMTP id 5DD9E728 for ; Tue, 10 Sep 2002 08:21:32 -0800 (AKDT) Content-Type: text/plain; charset="us-ascii" From: Beech Rintoul Organization: Sinbad Network Communications Inc. To: freebsd-current@freebsd.org Subject: Build failure rpm Date: Tue, 10 Sep 2002 08:21:31 -0800 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200209100821.32019.akbeech@sinbad.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was trying to update linux_base and got the following build failure: cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../build -I../misc -I/usr/local/include -I/usr/local/include -O -pipe -D_GNU_SOURCE -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -c cpio.c -fPIC -DPIC -o .libs/cpio.lo In file included from ../system.h:279, from cpio.c:1: ../misc/glob.h:51: redefinition of `__size_t' /usr/include/machine/_types.h:81: `__size_t' previously declared here gmake[2]: *** [cpio.lo] Error 1 gmake[2]: Leaving directory `/usr/ports/archivers/rpm/work/rpm-3.0.6/lib' gmake[1]: *** [all-recursive] Error 1 Running -current (yesterday). Beech -- ------------------------------------------------------------------- Beech Rintoul - SysAdmin - akbeech@sinbad.net /"\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:26:29 2002 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 AD57837B400; Tue, 10 Sep 2002 09:26:23 -0700 (PDT) Received: from scl8owa02.int.exodus.net (scl8out02.exodus.net [66.35.230.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 047B043E42; Tue, 10 Sep 2002 09:26:23 -0700 (PDT) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa02.int.exodus.net with Microsoft SMTPSVC(5.0.2195.4905); Tue, 10 Sep 2002 09:28:19 -0700 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.4905); Tue, 10 Sep 2002 09:28:18 -0700 Message-ID: <3D7E1D2E.94B61ACE@exodus.net> Date: Tue, 10 Sep 2002 09:26:22 -0700 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: FUJIMOTO Kou Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD References: <13008.1031593011@critter.freebsd.dk> <3D7D7000.AEB88A8E@j.dendai.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Sep 2002 16:28:18.0706 (UTC) FILETIME=[1245F720:01C258E7] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FUJIMOTO Kou wrote: > > Poul-Henning Kamp wrote: > > > > In message <3D7CDB63.1E640A3F@exodus.net>, Maksim Yevmenkin writes: > > > > >I still would like to hear from people. I'm extremely > > >surprised that FreeBSD community seems not interested in > > >this at all. I got very few replies from few people > > >(Julian Elischer, Terry Lambert - thanks!) and that's it. > > > > Most of us probably doesn't have any bluetooth hardware... > > I have a BT PCMCIA card by IBM, a BT USB adapter by MITSUMI, IBM PCMCIA card is not supported this time. If you can get spec. i will write a driver for it. In the mean time can you send card CIS dump to me? MITSUMI USB adapter is likely to work. I think it is a CSR/Bluecore based product (i.e. similar to 3Com USB dongle). But you will need to give me VendorID and ProductID so i can add it to the list of supported devices in "ubt.c". Just load "ugen" driver plug USB dongle and note vendor and product IDs. you also can get the same information via "usbdevs". > a C413S BT mobile phone by Sony, and a BT adapter for Sony CLIE. > A communication between CLIE/C413S and PC does not work properly > with Windows OS. Mobile phone and CLIE work well, because no > Windows needed and it's a Sony-to-Sony connection! sorry, but i have no clue about Bluetooth phones and handhelds. you've got to try it. i will try to do my best in helping you. > Anyway, I am willing to be a tester and you could find more ones > in Japan, because there're dozens of Bluetooth PCs and devices. great! thanks a lot! max. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:47:10 2002 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 6A80F37B400 for ; Tue, 10 Sep 2002 09:47:07 -0700 (PDT) Received: from ref5.freebsd.org (ref5.FreeBSD.org [216.136.204.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31EEC43E3B for ; Tue, 10 Sep 2002 09:47:07 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from ref5.freebsd.org (localhost [127.0.0.1]) by ref5.freebsd.org (8.12.6/8.12.6) with ESMTP id g8AGl6IM094819 for ; Tue, 10 Sep 2002 09:47:06 -0700 (PDT) (envelope-from des@ref5.freebsd.org) Received: (from des@localhost) by ref5.freebsd.org (8.12.6/8.12.6/Submit) id g8AGl6D9094817 for current@freebsd.org; Tue, 10 Sep 2002 09:47:06 -0700 (PDT) Date: Tue, 10 Sep 2002 09:47:06 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209101647.g8AGl6D9094817@ref5.freebsd.org> To: current@freebsd.org Subject: i386 tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Tue Sep 10 09:39:00 PDT 2002 -------------------------------------------------------------- ===> xe cc1: warnings being treated as errors /local0/scratch/des/src/sys/dev/cardbus/cardbus.c: In function `cardbus_driver_added': /local0/scratch/des/src/sys/dev/cardbus/cardbus.c:319: warning: unused variable `cardattached' *** Error code 1 Stop in /local0/scratch/des/obj/local0/scratch/des/src/sys/GENERIC. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:49:51 2002 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 AD30837B400; Tue, 10 Sep 2002 09:49:46 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF2BA43E4A; Tue, 10 Sep 2002 09:49:45 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.3/8.12.3) with ESMTP id g8AGnh9R019325; Tue, 10 Sep 2002 10:49:43 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 10 Sep 2002 10:49:34 -0600 (MDT) Message-Id: <20020910.104934.04188990.imp@bsdimp.com> To: cdillon@wolves.k12.mo.us Cc: myevmenk@exodus.net, current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD From: "M. Warner Losh" In-Reply-To: <20020910111741.H24092-100000@duey.wolves.k12.mo.us> References: <3D7CDB63.1E640A3F@exodus.net> <20020910111741.H24092-100000@duey.wolves.k12.mo.us> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <20020910111741.H24092-100000@duey.wolves.k12.mo.us> Chris Dillon writes: : On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: : : > I still would like to hear from people. I'm extremely surprised that : > FreeBSD community seems not interested in this at all. I got very : > few replies from few people (Julian Elischer, Terry Lambert - : > thanks!) and that's it. : : I'm very interested, as are some other people I know, but we just : don't have any bluetooth hardware to use yet. Don't think people : don't care and thanks for the good work. :-) I know I'm interested in bluetooth, but have no space cycles in which to help someone get something like this into the shape needed to integrate it into the tree. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:50:55 2002 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 40B2337B401; Tue, 10 Sep 2002 09:50:52 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D71D443E42; Tue, 10 Sep 2002 09:50:50 -0700 (PDT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.4/8.12.4) with ESMTP id g8AGoUOn007503; Tue, 10 Sep 2002 12:50:30 -0400 (EDT) (envelope-from arr@watson.org) Received: from localhost (arr@localhost) by fledge.watson.org (8.12.5/8.12.5/Submit) with SMTP id g8AGoTEJ007500; Tue, 10 Sep 2002 12:50:30 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Tue, 10 Sep 2002 12:50:29 -0400 (EDT) From: "Andrew R. Reiter" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: i386 tinderbox failure In-Reply-To: <200209101647.g8AGl6D9094817@ref5.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Dag-Erling Smorgrav wrote: :cc1: warnings being treated as errors :/local0/scratch/des/src/sys/dev/cardbus/cardbus.c: In function `cardbus_driver_added': :/local0/scratch/des/src/sys/dev/cardbus/cardbus.c:319: warning: unused variable `cardattached' :*** Error code 1 I just committed a fix for this, JFYI. Cheers, -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 9:57:29 2002 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 AE36537B400; Tue, 10 Sep 2002 09:57:24 -0700 (PDT) Received: from dmlb.org (pc1-cmbg2-6-cust106.cam.cable.ntl.com [80.4.4.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23FA343E65; Tue, 10 Sep 2002 09:57:24 -0700 (PDT) (envelope-from dmlb@dmlb.org) Received: from slave.my.domain ([192.168.200.39]) by dmlb.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.36 #1) id 17ooK7-000L4O-00; Tue, 10 Sep 2002 17:57:12 +0100 Received: from dmlb by slave.my.domain with local (Exim 3.36 #1) id 17ooK7-000DJ0-00; Tue, 10 Sep 2002 17:57:11 +0100 Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020910.104934.04188990.imp@bsdimp.com> Date: Tue, 10 Sep 2002 17:57:11 +0100 (BST) From: Duncan Barclay To: "M. Warner Losh" Subject: Re: Bluetooth stack for FreeBSD Cc: mobile@FreeBSD.ORG, current@FreeBSD.ORG, myevmenk@exodus.net, cdillon@wolves.k12.mo.us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10-Sep-2002 M. Warner Losh wrote: > In message: <20020910111741.H24092-100000@duey.wolves.k12.mo.us> > Chris Dillon writes: >: On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: >: >: > I still would like to hear from people. I'm extremely surprised that >: > FreeBSD community seems not interested in this at all. I got very >: > few replies from few people (Julian Elischer, Terry Lambert - >: > thanks!) and that's it. >: >: I'm very interested, as are some other people I know, but we just >: don't have any bluetooth hardware to use yet. Don't think people >: don't care and thanks for the good work. :-) > > I know I'm interested in bluetooth, but have no space cycles in which > to help someone get something like this into the shape needed to > integrate it into the tree. I contacted Maksim off list. I can get limited access to a Bluetooth qualification lab. (out of hours etc.) and will try and get his stack tested against a number of other solutions. Duncan -- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@dmlb.org | the alcoholics, and the permanently stoned. dmlb@freebsd.org| Steven King To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11: 0:24 2002 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 E3FB237B400; Tue, 10 Sep 2002 11:00:15 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45E9A43E6A; Tue, 10 Sep 2002 11:00:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020910180014.COMY16673.sccrmhc01.attbi.com@InterJet.elischer.org>; Tue, 10 Sep 2002 18:00:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA63095; Tue, 10 Sep 2002 10:48:26 -0700 (PDT) Date: Tue, 10 Sep 2002 10:48:26 -0700 (PDT) From: Julian Elischer To: Chris Dillon Cc: Maksim Yevmenkin , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD In-Reply-To: <20020910111741.H24092-100000@duey.wolves.k12.mo.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Chris Dillon wrote: > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > I still would like to hear from people. I'm extremely surprised that > > FreeBSD community seems not interested in this at all. I got very > > few replies from few people (Julian Elischer, Terry Lambert - > > thanks!) and that's it. > > I'm very interested, as are some other people I know, but we just > don't have any bluetooth hardware to use yet. Don't think people > don't care and thanks for the good work. :-) Yes. we are aware of the work and we are pleased that it is hapenning, but few of us have even SEEN any bluetooth stuff yet.. certainly in the US it's not yet being marketted a lot. Until it becomes more common all we can say is "hey FreeBSD is there ahead of the crowd" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11: 2:48 2002 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 AB52F37B400; Tue, 10 Sep 2002 11:02:41 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id F399443E42; Tue, 10 Sep 2002 11:02:40 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7A01166E36; Tue, 10 Sep 2002 11:02:40 -0700 (PDT) Date: Tue, 10 Sep 2002 11:02:39 -0700 From: Kris Kennaway To: current@FreeBSD.org Cc: fs@FreeBSD.org Subject: panic: ufs_dirbad: bad dir Message-ID: <20020910180238.GA72798@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I got this on the bento cluster this morning (-current from about 2 days ago): /x: bad dir ino 3180135 at offset 0: mangled entry panic: ufs_dirbad: bad dir Debugger("panic") Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db> trace Debugger(c03f45bc,c0473f80,c040e087,ceac4974,ffffffff) at Debugger+0x54 panic(c040e087,c25f9aac,308667,0,c040e02c) at panic+0x90 ufs_dirbad(c44b7100,0,c040e02c,0,ceac49f4) at ufs_dirbad+0x52 ufs_lookup(ceac4b20,ceac4b5c,c0286539,ceac4b20,ceac4c98) at ufs_lookup+0x317 ufs_vnoperate(ceac4b20,ceac4c98,ceac4cac,c040dfa0,52) at ufs_vnoperate+0x18 vfs_cache_lookup(ceac4bd0,ceac4bfc,c028aa22,ceac4bd0,c3d9dc00) at vfs_cache_lookup+0x3b9 ufs_vnoperate(ceac4bd0,c3d9dc00,0,c3d9dc00,c3d9dc00) at ufs_vnoperate+0x18 lookup(ceac4c84,0,c03fb880,a4,c3d9dc00) at lookup+0x302 namei(ceac4c84,c043c600,c03f80e0,bfbffb3e,0) at namei+0x24e unmount(c3d9dc00,ceac4d10,c041a960,418,2) at unmount+0x3d syscall(2f,2f,2f,8099291,80b5005) at syscall+0x2c4 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (22, FreeBSD ELF32, unmount), eip = 0x804aea3, esp = 0xbfbff46c, ebp = 0xbfbff4e8 --- An earlier console message which may be important: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done Any ideas? Kris --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9fjO+Wry0BWjoQKURAl99AJ4w0e9GulX+xnB+cznjdTTFKoPXdACdE7P/ zBw9IzrP5cvFwK6ZhN0Ia9o= =sV0Z -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11:12: 1 2002 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 E7F5E37B43C for ; Tue, 10 Sep 2002 11:11:49 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EF1843E6A for ; Tue, 10 Sep 2002 11:11:49 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1BC8666E36; Tue, 10 Sep 2002 11:11:49 -0700 (PDT) Date: Tue, 10 Sep 2002 11:11:48 -0700 From: Kris Kennaway To: Beech Rintoul Cc: freebsd-current@freebsd.org Subject: Re: Build failure rpm Message-ID: <20020910181148.GA72976@xor.obsecurity.org> References: <200209100821.32019.akbeech@sinbad.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <200209100821.32019.akbeech@sinbad.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote: > I was trying to update linux_base and got the following build failure: Known problem; see the list archives for a patch. Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9fjXjWry0BWjoQKURAlrQAKD69xnrN/YOmKeV8CYvhiur6Q2zdwCfWPja vojIRO3MDPniJt30O0zH9d8= =w4+B -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11:21:22 2002 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 8D97C37B400 for ; Tue, 10 Sep 2002 11:21:20 -0700 (PDT) Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 454E543E4A for ; Tue, 10 Sep 2002 11:21:20 -0700 (PDT) (envelope-from dmiller@sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id CA858D984; Tue, 10 Sep 2002 14:17:23 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id C25F9D983 for ; Tue, 10 Sep 2002 14:17:23 -0400 (EDT) Date: Tue, 10 Sep 2002 14:17:23 -0400 (EDT) From: current@d.sparks.net X-Sender: dmiller@search.sparks.net To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-current current@d.sparks.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11:24:51 2002 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 6549137B400; Tue, 10 Sep 2002 11:24:47 -0700 (PDT) Received: from scl8owa01.int.exodus.net (scl8out01.exodus.net [66.35.230.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C97843E42; Tue, 10 Sep 2002 11:24:47 -0700 (PDT) (envelope-from Maksim.Yevmenkin@exodus.net) Received: from scl8owa01.int.exodus.net ([66.35.230.241]) by scl8owa01.int.exodus.net with Microsoft SMTPSVC(5.0.2195.4905); Tue, 10 Sep 2002 11:26:42 -0700 Received: from exodus.net ([206.220.227.147]) by scl8owa01.int.exodus.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.4905); Tue, 10 Sep 2002 11:26:42 -0700 Message-ID: <3D7E38ED.8965E33C@exodus.net> Date: Tue, 10 Sep 2002 11:24:45 -0700 From: Maksim Yevmenkin X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Chris Dillon , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Sep 2002 18:26:42.0627 (UTC) FILETIME=[9C8A4930:01C258F7] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian, > On Tue, 10 Sep 2002, Chris Dillon wrote: > > > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > > > I still would like to hear from people. I'm extremely surprised that > > > FreeBSD community seems not interested in this at all. I got very > > > few replies from few people (Julian Elischer, Terry Lambert - > > > thanks!) and that's it. > > > > I'm very interested, as are some other people I know, but we just > > don't have any bluetooth hardware to use yet. Don't think people > > don't care and thanks for the good work. :-) > > Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. Please :-) May i suggest to look at www.compusa.com and search for Bluetooth. Then try to look for the nearest store that has it. Prices <= $100. Yes, it is more expensive then 802.11. Yes, you can not do a lot with it right now, but Microsoft and Apple already claim support for Bluetooth. Yes, i know, "claim" does not mean much :-) > Until it becomes more common all we can say is > "hey FreeBSD is there ahead of the crowd" :-) Linux had Bluetooth stuff for almost a year now. Or may be even longer. People in Europe try to use Linux with Bluetooth for all sort of stuff, access points, printers, headset, phones you name it. Some even run in on iPAQ and Sharp Zaurus. Is that common for you? :-) I'm not trying to troll. You anyone wants to discuss it further, please, please, please take it off the list. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11:27:47 2002 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 374FE37B400; Tue, 10 Sep 2002 11:27:41 -0700 (PDT) Received: from thor.wearix.com (ad96e1d2d.dsl.de.colt.net [217.110.29.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA58C43E65; Tue, 10 Sep 2002 11:27:39 -0700 (PDT) (envelope-from Harald.Schmalzbauer@wearix.com) Received: from loki.muc.wearix.com (loki.muc.wearix.com [172.18.10.3]) by thor.wearix.com (8.12.6/8.12.6) with ESMTP id g8AIRTgC005681; Tue, 10 Sep 2002 20:27:33 +0200 (CEST) (envelope-from Harald.Schmalzbauer@wearix.com) Received: from obst.test ([192.168.11.2]) (AUTH: PLAIN hsc1, ) by loki.muc.wearix.com with esmtp; Tue, 10 Sep 2002 20:27:29 +0200 Subject: Re: Bluetooth stack for FreeBSD From: Harald Schmalzbauer To: Julian Elischer Cc: Chris Dillon , Maksim Yevmenkin , current@freebsd.org, mobile@freebsd.org In-Reply-To: References: X-Mailer: Ximian Evolution 1.0.7 Date: 10 Sep 2002 20:28:03 +0200 Message-Id: <1031682484.75750.107.camel@obst> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am Di, 2002-09-10 um 19.48 schrieb Julian Elischer: > > > > On Tue, 10 Sep 2002, Chris Dillon wrote: > > > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote: > > > > > I still would like to hear from people. I'm extremely surprised that > > > FreeBSD community seems not interested in this at all. I got very > > > few replies from few people (Julian Elischer, Terry Lambert - > > > thanks!) and that's it. > > *SNIP* > > > Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. > > Until it becomes more common all we can say is > "hey FreeBSD is there ahead of the crowd" :-) > I'm very happy too, and I do have hardware (VAIO and a t68) but no time right now. I'll do some tests ASAP! Thanks, -Harry > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 11:35:28 2002 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 E2E3B37B400; Tue, 10 Sep 2002 11:35:24 -0700 (PDT) Received: from ajax.cnchost.com (ajax.cnchost.com [207.155.248.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3196043E65; Tue, 10 Sep 2002 11:35:23 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by ajax.cnchost.com id OAA22492; Tue, 10 Sep 2002 14:35:15 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200209101835.OAA22492@ajax.cnchost.com> To: Julian Elischer Cc: Chris Dillon , Maksim Yevmenkin , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: Bluetooth stack for FreeBSD In-reply-to: Your message of "Tue, 10 Sep 2002 10:48:26 PDT." Date: Tue, 10 Sep 2002 11:35:16 -0700 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Yes. we are aware of the work and we are pleased that it is hapenning, but > few of us have even SEEN any bluetooth stuff yet.. > certainly in the US it's not yet being marketted a lot. Fry's Electronics in the SF bayarea has a bunch of bluetooth gadgets. Go to www.outpost.com and search for 'bluetooth'. USB adapters, pcmcia card, printer adapter, connectors for Palm and iPAQ etc. The printer adapter looks just like a standard paraller port connector with a RJ11 or RJ45 socket on one side (you can hook up a serial cable to it too). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 12: 4: 5 2002 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 7745237B405 for ; Tue, 10 Sep 2002 12:04:01 -0700 (PDT) Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id C65CF43E3B for ; Tue, 10 Sep 2002 12:04:00 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 473D44CE31; Tue, 10 Sep 2002 15:03:55 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id PAA17125; Tue, 10 Sep 2002 15:03:54 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id MAA01290; Tue, 10 Sep 2002 12:03:53 -0700 (PDT) Message-Id: <200209101903.MAA01290@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: phk@critter.freebsd.dk Subject: Re: kern_timeout.c msg "Expensive timeout(9) function: 0xc026f3ec(0xc4067800) 0.006773207" Cc: current@FreeBSD.ORG Date: Tue, 10 Sep 2002 12:03:52 -0700 Versions: dmail (solaris) 2.5a/makemail 2.9d Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've seen the scrn_timer() one too: Expensive timeout(9) function: 0xc049b3f0(0xc0657200) 0.003659743 c049b3f0 t scrn_timer as well as uma_timeout(). Expensive timeout(9) function: 0xc047c6b0(0) 0.002146136 c047c6b0 t uma_timeout Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 12:17:11 2002 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 BAC7637B400 for ; Tue, 10 Sep 2002 12:17:09 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6C8643E42 for ; Tue, 10 Sep 2002 12:17:08 -0700 (PDT) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.5/8.11.6) with SMTP id g8AJH6ZP002700; Tue, 10 Sep 2002 21:17:06 +0200 Received: (nullmailer pid 1222 invoked by uid 1000); Tue, 10 Sep 2002 19:17:06 -0000 Date: Tue, 10 Sep 2002 21:17:05 +0200 From: Mark Santcroos To: Mitsuru IWASAKI Cc: acpi-jp@jp.FreeBSD.org, current@FreeBSD.ORG Subject: Re: [acpi-jp 1789] Re: ACPI video driver (for Dell Latitude C640) Message-ID: <20020910191705.GA765@laptop.6bone.nl> References: <20020828134307.GA892@laptop.6bone.nl> <20020829211115.GB2059@laptop.6bone.nl> <20020910122910.GA2338@laptop.6bone.nl> <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020911.002204.70226596.iwasaki@jp.FreeBSD.org> User-Agent: Mutt/1.4i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1023 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Sep 11, 2002 at 12:22:04AM +0900, Mitsuru IWASAKI wrote: > > Do you think that there is a change that this is in the direction of DPMS, > > or is that very unliky? I tried to find the spec for DPMS but it seems to > > be a closed on (at least to non-members). > > It seems that old laptops don't have VGA specific ACPI objects, so > many people will be happy if we can implement non-ACPI VGA driver w/ > ATI chips hack. > BTW, have you checked for XFree86 code? Hopefully we might find > some hints on DPMS for ATI chips. Ok, listen to this ;-) I think DPMS might be very related, because when I suspend from X and resume again everything is (almost) fine!! 1. I start up the machine 2. startx 3. I enter S1 either by acpiconf / closing the lid / ctrl-esc (sleep key) 4. Screen goes to console and stays on 5. I resume with power key / open lid 6. Screen turns black 7. Few seconds later X is in front of me again! 8. If I now go back to the console (ctrl-f1) the console is still black I also tried the scenario where I suspend on the console, then resume again, which turns the screen black. I then startx again and my screen is back again. This is a major step IMHO. I already looked at the DPMS code in X and we have to extract that basically. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 12:18:32 2002 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 CBBAA37B400; Tue, 10 Sep 2002 12:18:27 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52A7843E42; Tue, 10 Sep 2002 12:18:27 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AJIHwr095835; Tue, 10 Sep 2002 12:18:21 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209101918.g8AJIHwr095835@gw.catspoiler.org> Date: Tue, 10 Sep 2002 12:18:17 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: bde@zeta.org.au Cc: rwatson@FreeBSD.ORG, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <20020911000503.L1981-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11 Sep, Bruce Evans wrote: > On Tue, 10 Sep 2002, Don Lewis wrote: > > I have just one thing to add to Robert's reply. > >> BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the >> reference has been dropped with vput() or vrele()? > > I think it is. It has some internal locking (v_interlock at least), and > only asserts that the vnode is unlocked by curthread so it doesn't matter > if another thread locks it. I'm mostly worried about the vnode being recycled as something else after the vput() or vrele() call. I think a better approach would be to add the assertion checks to vput() and vrele(), which would mean that we could remove most of the checks in the syscall code. The only problems we would miss would be when we leak vnode references, but reference leaks are a problem anyway. I wish there was a good way to add assertion checks for detecting the leaks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 12:36: 0 2002 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 BB83D37B400; Tue, 10 Sep 2002 12:35:54 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4A1743E42; Tue, 10 Sep 2002 12:35:53 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8AJZDh43694; Tue, 10 Sep 2002 09:35:15 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Tue, 10 Sep 2002 09:35:13 -1000 (HST) From: Vincent Poy To: Mikhail Teterin Cc: current@FreeBSD.ORG, , Subject: Re: freeze with the CardBus NIC 3CCFE575BT In-Reply-To: <200209101226.g8ACQglQ063430@corbulon.video-collage.com> Message-ID: <20020910092916.J2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Mikhail Teterin wrote: > Regardless of whether the xl driver is linked into the kernel or > loaded as a module, the machine freezes shortly after ifconfig-ing > the card. Sunday's -current. Complete freeeze -- can not go into > debugger... > > More information available upon request... > > -mi This is interesting. I have the CardBus 3Com NIC 3CXFEM656C which is the type II card that takes one slot but a combo with 56k modem and the Megahertz XJack. With Sunday's -current and the 08182002-JP SNAPSHOT, the card works fine under xl0 driver with the Dell Inspiron 8200 Notebook when I moved the HDD from the IBM ThinkPad 770Z. On the 770Z however, as soon as I do the ifconfig, it'll xl0: watchdog timer all over and it will ping with latencies at 8000ms. So not sure what the problem is. Other cards which I have tried, the Siemens/Efficient Networks SpeedStream SS1012 and the SMC Networks SMC8036TX which seems to be identical cards physically as it has the same design and same label printing information layout seems to work fine on both machines. The NetGear FA511 and the LinkSys PCM200 both don't work at all since FreeBSD can't detect the device id or something. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 12:37: 8 2002 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 D248637B400; Tue, 10 Sep 2002 12:37:04 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E16B743E6E; Tue, 10 Sep 2002 12:37:03 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g8AJZKOo025607; Tue, 10 Sep 2002 15:35:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 10 Sep 2002 15:35:20 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Don Lewis Cc: bde@zeta.org.au, current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <200209101918.g8AJIHwr095835@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Don Lewis wrote: > On 11 Sep, Bruce Evans wrote: > > On Tue, 10 Sep 2002, Don Lewis wrote: > > > > I have just one thing to add to Robert's reply. > > > >> BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the > >> reference has been dropped with vput() or vrele()? > > > > I think it is. It has some internal locking (v_interlock at least), and > > only asserts that the vnode is unlocked by curthread so it doesn't matter > > if another thread locks it. > > I'm mostly worried about the vnode being recycled as something else > after the vput() or vrele() call. I think a better approach would be to > add the assertion checks to vput() and vrele(), which would mean that we > could remove most of the checks in the syscall code. The only problems > we would miss would be when we leak vnode references, but reference > leaks are a problem anyway. I wish there was a good way to add > assertion checks for detecting the leaks. Unfortunately, we can't assert not locked at the end of vput because of recursive locking of vnodes. What I would like to see is a check that, when control is returned to userland, that the thread owns no locks. It's a bit like sleeping while holding a mutex: don't do that. Also, last time I tried to use the ddb show lockedvnods command, I got the problem attached below due to locking issues, which makes it a lot harder to debug locking problems... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories db> show lockedvnods Locked vnodes panic: blockable sleep lock (sleep mutex) mountlist @ ../../../kern/vfs_subr.c:2621 Debugger("panic") Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc0423ed4 stack pointer = 0x10:0xc869b9d0 frame pointer = 0x10:0xc869b9dc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = IOPL = 0 current process = 11 (idle) Stopped at siointr1+0xf4: movl $0,brk_state1.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 13:27:44 2002 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 97B7837B406; Tue, 10 Sep 2002 13:27:41 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 634C343E9E; Tue, 10 Sep 2002 13:27:37 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AKA3wr095951; Tue, 10 Sep 2002 13:10:07 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209102010.g8AKA3wr095951@gw.catspoiler.org> Date: Tue, 10 Sep 2002 13:10:03 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: rwatson@FreeBSD.ORG Cc: bde@zeta.org.au, current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Robert Watson wrote: > On Tue, 10 Sep 2002, Don Lewis wrote: >> I'm mostly worried about the vnode being recycled as something else >> after the vput() or vrele() call. I think a better approach would be to >> add the assertion checks to vput() and vrele(), which would mean that we >> could remove most of the checks in the syscall code. The only problems >> we would miss would be when we leak vnode references, but reference >> leaks are a problem anyway. I wish there was a good way to add >> assertion checks for detecting the leaks. > > Unfortunately, we can't assert not locked at the end of vput because of > recursive locking of vnodes. I was actually thinking of adding the assertion at the beginning of vput to check that the vnode was locked. I forgot about recursive locking, so doing any checking inside vrele() wouldn't work. > What I would like to see is a check that, when control is returned to > userland, that the thread owns no locks. That sounds neat, though the obvious solution of traversing the vnode list would sure slow things down ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 13:48:26 2002 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 BCA7F37B400; Tue, 10 Sep 2002 13:48:23 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A26E43E3B; Tue, 10 Sep 2002 13:48:22 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA01539; Wed, 11 Sep 2002 06:11:02 +1000 Date: Wed, 11 Sep 2002 06:18:48 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Robert Watson Cc: Don Lewis , , Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: Message-ID: <20020911060453.C3443-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Robert Watson wrote: > ... Also, last time I tried to use the ddb > show lockedvnods command, I got the problem attached below due to locking > issues, which makes it a lot harder to debug locking problems... > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Network Associates Laboratories > > db> show lockedvnods > Locked vnodes > panic: blockable sleep lock (sleep mutex) mountlist @ > ../../../kern/vfs_subr.c:2621 > Debugger("panic") Try removing all the locking in the command. ddb commands can't use locking. I have printfs in _mtx_lock_flags(), _mtx_lock_spin_flags(), _mtx_lock_sleep() and _mtx_lock_spin() to detect locking when ddb is active. The error handling would be better if trap_fatal() were called before panic panic(), like it is for null pointer panics. ddb on i386's then notices that it shot itself and longjmps to its entry point. This handles things like reading through garbage pointers OK, but not external state changes like locking. Maybe my printfs should be trap_fatals or or direct longjmps. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 13:53:39 2002 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 EA77037B400; Tue, 10 Sep 2002 13:53:36 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2137343E3B; Tue, 10 Sep 2002 13:53:36 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g8AKrBOo034369; Tue, 10 Sep 2002 16:53:11 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 10 Sep 2002 16:53:11 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bruce Evans Cc: Don Lewis , current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: vnode lock assertion problem in nfs_link() In-Reply-To: <20020911060453.C3443-100000@gamplex.bde.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 11 Sep 2002, Bruce Evans wrote: > On Tue, 10 Sep 2002, Robert Watson wrote: > > > ... Also, last time I tried to use the ddb > > show lockedvnods command, I got the problem attached below due to locking > > issues, which makes it a lot harder to debug locking problems... > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > > robert@fledge.watson.org Network Associates Laboratories > > > > db> show lockedvnods > > Locked vnodes > > panic: blockable sleep lock (sleep mutex) mountlist @ > > ../../../kern/vfs_subr.c:2621 > > Debugger("panic") > > Try removing all the locking in the command. ddb commands can't use > locking. I have printfs in _mtx_lock_flags(), _mtx_lock_spin_flags(), > _mtx_lock_sleep() and _mtx_lock_spin() to detect locking when ddb is > active. > > The error handling would be better if trap_fatal() were called before > panic panic(), like it is for null pointer panics. ddb on i386's then > notices that it shot itself and longjmps to its entry point. This > handles things like reading through garbage pointers OK, but not > external state changes like locking. Maybe my printfs should be > trap_fatals or or direct longjmps. I'll try removing the locking tonight sometime. Yeah, the other frustrating thing about this particular panic is that there is no way to recover from it if you just broke to ddb for the purposes of checking locks, because the panic hoses the ddb state, which in this case is highly unfortunate. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 14:16:41 2002 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 F234E37B400 for ; Tue, 10 Sep 2002 14:16:38 -0700 (PDT) Received: from nebula.anchoragerescue.org (115-7-237-24-cable.anchorageak.net [24.237.7.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FFB843E75 for ; Tue, 10 Sep 2002 14:16:38 -0700 (PDT) (envelope-from akbeech@sinbad.net) Received: from nova.anchoragerescue.org (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with ESMTP id 29BEE700; Tue, 10 Sep 2002 13:16:37 -0800 (AKDT) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul Organization: Sinbad Network Communications Inc. To: Kris Kennaway Subject: Re: Build failure rpm Date: Tue, 10 Sep 2002 13:16:36 -0800 User-Agent: KMail/1.4.3 Cc: freebsd-current@freebsd.org References: <200209100821.32019.akbeech@sinbad.net> <20020910181148.GA72976@xor.obsecurity.org> In-Reply-To: <20020910181148.GA72976@xor.obsecurity.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200209101316.36580.akbeech@sinbad.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 10 September 2002 10:11 am, Kris Kennaway wrote: > On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote: > > I was trying to update linux_base and got the following build failure: > > Known problem; see the list archives for a patch. > > Kris Already applied those patches, still getting the same error. Beech ------------------------------------------------------------------- Beech Rintoul - SysAdmin - akbeech@sinbad.net /"\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 15: 5:58 2002 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 F1A2037B400 for ; Tue, 10 Sep 2002 15:05:55 -0700 (PDT) Received: from mail.dada.it (mail2.dada.it [195.110.100.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 0448443E6A for ; Tue, 10 Sep 2002 15:05:51 -0700 (PDT) (envelope-from riccardo@torrini.org) Received: (qmail 16848 invoked from network); 10 Sep 2002 22:05:43 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 10 Sep 2002 22:05:43 -0000 Received: from trudy.torrini.home (localhost.torrini.home [127.0.0.1]) by torrini.org (8.12.5/8.12.5) with ESMTP id g8AM4KHU006729; Wed, 11 Sep 2002 00:04:20 +0200 (CEST) (envelope-from riccardo@trudy.torrini.home) Received: (from riccardo@localhost) by trudy.torrini.home (8.12.5/8.12.5/Submit) id g8AM4Fnu006728; Wed, 11 Sep 2002 00:04:15 +0200 (CEST) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Sep 2002 00:04:15 +0200 (CEST) From: Riccardo Torrini To: Giorgos Keramidas Subject: It works ! (was Re: Unable to buildworld (new record, 18")) Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Sep-2002 (19:54:17/GMT) Riccardo Torrini wrote: >> There have been at least two gcc upgrades since then. I believe >> the easiest way to upgrade to today's -current would be to install >> a fairly recent snapshot ... instead of trying to debug ... > I have tryed with a middle version (1 jul 2002) but it fails without > and with make includes before build, now I'm trying with cvsup from > 15 aug 2002 (as written by Munish Chopra on 1 sep: IIRC current was > in good shape between August 12-15, 17, 18, 22-24) ... Ok. All done. My start point was really too old, anyway this is the full story: - starting from -CURRENT of 8 May, used as desktop (full of bells and whistles, homes on a nfs disk on a safe -STABLE local server :-) - cvsuped daily and compiled w/out install at least once a week (this before holidays). - tryed to upgrade to latest -CURRENT last week w/out success, with a lot of error, maybe due to double gcc update (2.95 -> 3.1 -> 3.2) - cvsuped back to 1 jul, new buildworld, failed - found mail into archives speaking about some "good shape" days - cvsuped again to 15 aug, new buildworld, failed - added some switches: -DNOCLEAN, -DNO_WERROR, -DNOCRYPT (one at a time, every time world go forward a bit) - build complete, kernel complete, install complete, reboot ... and Yes! I forgot mergemaster :( - new full buildworld w/out switches, complete fine. new kernel, another full install, mergemaster :-) reboot. NB: build done w/out CPUTYPE (usually was =p3) and with CFLAGS= -O2 -pipe Hoping this can help others not-too-current users. Upgrade always possible, even from old versions (with some care) Now last doubt: after next upgrade to post-gcc_3.2 is a complete port rebuild necessary because c++ ports stop working or not? Thanks a lot, Riccardo, now more-current :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 15:23:52 2002 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 1B5AE37B400; Tue, 10 Sep 2002 15:23:44 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65EED43E6A; Tue, 10 Sep 2002 15:23:43 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AMNYwr096282; Tue, 10 Sep 2002 15:23:38 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209102223.g8AMNYwr096282@gw.catspoiler.org> Date: Tue, 10 Sep 2002 15:23:34 -0700 (PDT) From: Don Lewis Subject: Re: vnode lock assertion problem in nfs_link() To: rwatson@FreeBSD.ORG Cc: current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <200209100419.g8A4JTwr093971@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep, Don Lewis wrote: > On 9 Sep, Robert Watson wrote: > >> What I'd actually like to do is lock vp on going in to the VOP. I need to >> grab the lock in the link() code anyway to do the MAC check. UFS and >> others all immediately lock the vnode on entry anyway... > > Here's a patch to implement this. It compiles and seems to work OK, but > needs review. There are a couple of issues that definitely need a look: > The VOP_LINK(9) man page needs would also need to be updated. Here's a patch to the man page that also fixes a bunch of bit rot that has accumulated: Index: VOP_LINK.9 =================================================================== RCS file: /home/ncvs/src/share/man/man9/VOP_LINK.9,v retrieving revision 1.13 diff -u -r1.13 VOP_LINK.9 --- VOP_LINK.9 1 Oct 2001 16:09:24 -0000 1.13 +++ VOP_LINK.9 10 Sep 2002 22:21:53 -0000 @@ -52,18 +52,13 @@ pathname information about the file .El .Pp -The pathname info must be released on exit. The directory and -file vnodes should NOT be released on exit. +The pathname info should NOT be released on exit because it is done +by the caller. +The directory and file vnodes should NOT be released on exit. .Sh LOCKS -The directory, -.Fa dvp -is locked on entry and should remain locked on return. -The file -.Fa vp -is not locked on entry and should remain that way on return. -If your VOP code locks -.Fa vp , -it must be sure to unlock prior to returning. +.Xr VOP_LINK 9 +expects the directory and file vnodes to be locked on entry and will leave +the vnodes locked on return. .Sh RETURN VALUES Zero is returned if the file was linked successfully, otherwise an error is returned. @@ -74,27 +69,14 @@ { int error = 0; - if (vp->v_mount != dvp->v_mount) { - error = EXDEV; - goto out2; - } - if (vp != dvp && (error = VOP_LOCK(vp))) { - goto out2; - } - - /* - * now that we've locked vp, we have to use out1 instead of out2 - */ + if (vp->v_mount != dvp->v_mount) + return (EXDEV); - if (vp would have too many links) { - error = EMLINK; - goto out1; - } + if (vp would have too many links) + return (EMLINK); - if (vp is immutable) { - error = EPERM; - goto out1; - } + if (vp is immutable) + return (EPERM); /* * Increment link count of vp and write back the on-disc version of it. @@ -108,19 +90,21 @@ ...; } - free(cnp->cn_pnbuf, M_NAMEI); -out1: - if (vp != dvp) - VOP_UNLOCK(vp); -out2: - return error; } .Ed .Sh ERRORS .Bl -tag -width Er +.It Bq Er EMLINK +the file has too many links +.El +.Bl -tag -width Er .It Bq Er EPERM the file is immutable +.El +.Bl -tag -width Er +.It Bq Er EXDEV +a hard link is not possible between different file systems .El .Sh SEE ALSO .Xr vnode 9 , To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 15:46:28 2002 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 2B96237B401; Tue, 10 Sep 2002 15:46:14 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF0643E72; Tue, 10 Sep 2002 15:46:13 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8AMk5wr096324; Tue, 10 Sep 2002 15:46:09 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209102246.g8AMk5wr096324@gw.catspoiler.org> Date: Tue, 10 Sep 2002 15:46:05 -0700 (PDT) From: Don Lewis Subject: vnode lock assertion problem in nfs_rename() To: current@FreeBSD.ORG, jeff@FreeBSD.ORG Cc: Robert Watson In-Reply-To: <200209092300.g89N0Hwr093398@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Sep, Don Lewis wrote: > nfs_link() contains the following code: > > /* > * Push all writes to the server, so that the attribute cache > * doesn't get "out of sync" with the server. > * XXX There should be a better way! > */ > VOP_FSYNC(vp, cnp->cn_cred, MNT_WAIT, cnp->cn_thread); > > The problem is that vp is not locked by the caller, but VOP_FSYNC() > expects its argument to be locked. > > I think we can probably just lock and unlock vp around the call to > VOP_FSYNC() ... There's a similar problem in nfs_rename(): /* * We have to flush B_DELWRI data prior to renaming * the file. If we don't, the delayed-write buffers * can be flushed out later after the file has gone stale * under NFSV3. NFSV2 does not have this problem because * ( as far as I can tell ) it flushes dirty buffers more * often. */ VOP_FSYNC(fvp, fcnp->cn_cred, MNT_WAIT, fcnp->cn_thread); if (tvp) VOP_FSYNC(tvp, tcnp->cn_cred, MNT_WAIT, tcnp->cn_thread); fvp is not locked by the caller. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 16:44:37 2002 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 A2B1337B400; Tue, 10 Sep 2002 16:44:33 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6E3243E42; Tue, 10 Sep 2002 16:44:32 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8ANgXu45566; Tue, 10 Sep 2002 13:42:34 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Tue, 10 Sep 2002 13:42:33 -1000 (HST) From: Vincent Poy To: fanf@FreeBSD.ORG, Subject: -current buildworld fails with revision 1.38 src/usr.bin/uudecode/uudecode.c Message-ID: <20020910134133.Q2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ===> usr.bin/uudecode /usr/obj/usr/src/i386/usr/src/usr.bin/uudecode created for /usr/src/usr.bin/uudecode rm -f .depend mkdep -f .depend -a -D__FBSDID=__RCSID /usr/src/usr.bin/uudecode/uudecode.c echo uudecode: /usr/lib/libc.a >> .depend cc -O -pipe -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -D__FBSDID=__RCSID -c /usr/src/usr.bin/uudecode/uudecode.c /usr/src/usr.bin/uudecode/uudecode.c: In function `decode2': /usr/src/usr.bin/uudecode/uudecode.c:225: warning: comparison between signed and unsigned /usr/src/usr.bin/uudecode/uudecode.c:275: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:286: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:294: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:301: syntax error before "ch" *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 17:10:49 2002 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 A935137B400 for ; Tue, 10 Sep 2002 17:10:46 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31DA943E65 for ; Tue, 10 Sep 2002 17:10:46 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.111.103] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.12 $ on Novell NetWare via secured & encrypted transport (TLS); Tue, 10 Sep 2002 18:10:45 -0600 Message-ID: <3D7E89D3.7090000@hotmail.com> Date: Tue, 10 Sep 2002 17:09:55 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020905 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: World broken at uudecode [Sep 10] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/usr.bin/uudecode/uudecode.c cc1: warnings being treated as errors /usr/src/usr.bin/uudecode/uudecode.c: In function `decode2': /usr/src/usr.bin/uudecode/uudecode.c:225: warning: comparison between signed and unsigned /usr/src/usr.bin/uudecode/uudecode.c:275: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:286: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:294: syntax error before "ch" /usr/src/usr.bin/uudecode/uudecode.c:301: syntax error before "ch" *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 17:31:18 2002 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 8BF1E37B400 for ; Tue, 10 Sep 2002 17:31:14 -0700 (PDT) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA82D43E65 for ; Tue, 10 Sep 2002 17:31:13 -0700 (PDT) (envelope-from rodrigc@attbi.com) Received: from dibbler.ne.client2.attbi.com (localhost [127.0.0.1]) by dibbler.ne.client2.attbi.com (8.12.6/8.12.5) with ESMTP id g8B0VKgr000809; Tue, 10 Sep 2002 20:31:20 -0400 (EDT) (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6/Submit) id g8B0VERv000808; Tue, 10 Sep 2002 20:31:14 -0400 (EDT) Date: Tue, 10 Sep 2002 20:31:14 -0400 From: Craig Rodrigues To: walt Cc: freebsd-current@freebsd.org Subject: Re: World broken at uudecode [Sep 10] Message-ID: <20020910203114.A799@attbi.com> References: <3D7E89D3.7090000@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D7E89D3.7090000@hotmail.com>; from wa1ter@hotmail.com on Tue, Sep 10, 2002 at 05:09:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Sep 10, 2002 at 05:09:55PM -0700, walt wrote: > cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch > -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/usr.bin/uudecode/uudecode.c > cc1: warnings being treated as errors > /usr/src/usr.bin/uudecode/uudecode.c: In function `decode2': > /usr/src/usr.bin/uudecode/uudecode.c:225: warning: comparison between signed and unsigned > /usr/src/usr.bin/uudecode/uudecode.c:275: syntax error before "ch" > /usr/src/usr.bin/uudecode/uudecode.c:286: syntax error before "ch" > /usr/src/usr.bin/uudecode/uudecode.c:294: syntax error before "ch" > /usr/src/usr.bin/uudecode/uudecode.c:301: syntax error before "ch" > *** Error code 1 Try this patch: --- uudecode.c.orig Tue Sep 10 20:26:48 2002 +++ uudecode.c Tue Sep 10 20:29:44 2002 @@ -153,7 +153,7 @@ decode2(void) { int base64; - int n; + size_t n; char ch, *p, *q; void *mode; struct passwd *pw; @@ -258,7 +258,7 @@ warnx("%s: %s: character out of range: [%d-%d]", \ filename, buffn, 1 + ' ', 077 + ' ' + 1); \ return (1); \ -} while (0) +} while (0); /* * `n' is used to avoid writing out all the characters -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 19: 9:47 2002 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 DDA0037B400 for ; Tue, 10 Sep 2002 19:09:40 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FADC43E6A for ; Tue, 10 Sep 2002 19:09:40 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8B29Wwr096594; Tue, 10 Sep 2002 19:09:36 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209110209.g8B29Wwr096594@gw.catspoiler.org> Date: Tue, 10 Sep 2002 19:09:32 -0700 (PDT) From: Don Lewis Subject: Re: Locking problems in exec To: wollman@lcs.mit.edu Cc: current@FreeBSD.ORG In-Reply-To: <200209071746.g87HkcoL048734@khavrinen.lcs.mit.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 7 Sep, Garrett Wollman wrote: > I just noted the following: > > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from ../../../kern/kern_exec.c:368 > lock order reversal > 1st 0xc438e6a8 process lock (process lock) @ ../../../kern/kern_exec.c:368 > 2nd 0xc0413d20 filelist lock (filelist lock) @ ../../../kern/kern_descrip.c:1133 > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from ../../../kern/kern_exec.c:368 > > $ ident /sys/kern/kern_exec.c > /sys/kern/kern_exec.c: > $FreeBSD: src/sys/kern/kern_exec.c,v 1.189 2002/09/05 07:30:14 davidxu Exp $ > $ ident /sys/kern/kern_descrip.c > /sys/kern/kern_descrip.c: > $FreeBSD: src/sys/kern/kern_descrip.c,v 1.158 2002/09/03 20:16:31 jhb Exp $ > > This occurred when starting up Netscape. I just saw this in a recent version of -stable while running mozilla. I think the problem is in the following set?id handling code in execve(): /* Close any file descriptors 0..2 that reference procfs */ setugidsafety(td); /* Make sure file descriptors 0..2 are in use. */ error = fdcheckstd(td); if (error != 0) goto done1; When I looked at this code before, I assumed that fdcheckstd() just verified that the proper fds where in use, but on closer inspection it appears that fdcheckstd() attempts to point any unused fds in 0..2 to /dev/null. This calls falloc(), which calls uma_zalloc() and grabs the filelist lock, all of which happens while execve() holds the process lock. The do_dup() call in fdcheckstd() could also be a problem. I don't think dropping the process lock is correct, and calling falloc() and vn_open() before grabbing the process lock might also be insecure. Other than just causing execve() to fail in this situation, the only other fix that I can think of would be to preallocate the struct file and pre-open /dev/null if we're execing a set?id executable, and then jam this into the descriptor table if it turns out to be needed. Barf! I think netscape and mozilla must be exec'ing some set?id system binary in the background and didn't pass the correct descriptors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 19:30:56 2002 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 DD4D537B401 for ; Tue, 10 Sep 2002 19:30:49 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4E3B43E3B for ; Tue, 10 Sep 2002 19:30:49 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g8B2UnYB022773 for ; Tue, 10 Sep 2002 19:30:49 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g8B2UmdC022771 for current@freebsd.org; Tue, 10 Sep 2002 19:30:48 -0700 (PDT) Date: Tue, 10 Sep 2002 19:30:48 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209110230.g8B2UmdC022771@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Tue Sep 10 18:25:39 PDT 2002 -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Tue Sep 10 19:30:45 PDT 2002 -------------------------------------------------------------- >>> Kernel build for LINT started on Tue Sep 10 19:30:45 PDT 2002 -------------------------------------------------------------- ===> LINT config: Error: device "apm_saver" is unknown config: Error: device "cy" is unknown config: Error: device "cy" does not take a count config: 3 errors WARNING: kernel contains GPL contaminated ext2fs filesystem FYI: static unit limits for vcoda are set: NVCODA=4 FYI: static unit limits for dgb are set: NDGB=1 FYI: static unit limits for card are set: NCARD=1 FYI: static unit limits for meteor are set: NMETEOR=1 *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 20:13:42 2002 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 9A60737B400 for ; Tue, 10 Sep 2002 20:13:40 -0700 (PDT) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 908AD43E6E for ; Tue, 10 Sep 2002 20:13:39 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (patr530-b229.otenet.gr [212.205.244.237]) by mailsrv.otenet.gr (8.12.4/8.12.4) with ESMTP id g8B3DZK9016997; Wed, 11 Sep 2002 06:13:37 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.6/8.12.6) with ESMTP id g8B3DYSx009438; Wed, 11 Sep 2002 06:13:34 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.6/8.12.6/Submit) id g8B3DXAA009437; Wed, 11 Sep 2002 06:13:33 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 11 Sep 2002 06:13:32 +0300 From: Giorgos Keramidas To: Riccardo Torrini Cc: freebsd-current@FreeBSD.ORG Subject: Re: It works ! (was Re: Unable to buildworld (new record, 18")) Message-ID: <20020911031331.GC6892@hades.hell.gr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-09-11 00:04, Riccardo Torrini wrote: > Now last doubt: after next upgrade to post-gcc_3.2 is a complete port > rebuild necessary because c++ ports stop working or not? Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 20:22:58 2002 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 A6CC337B400 for ; Tue, 10 Sep 2002 20:22:54 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 0C43943E72 for ; Tue, 10 Sep 2002 20:22:50 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 19973 invoked by uid 1000); 11 Sep 2002 03:22:52 -0000 Date: Tue, 10 Sep 2002 20:22:52 -0700 (PDT) From: Nate Lawson To: Don Lewis Cc: current@FreeBSD.ORG Subject: Re: Locking problems in exec In-Reply-To: <200209110209.g8B29Wwr096594@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 10 Sep 2002, Don Lewis wrote: > On 7 Sep, Garrett Wollman wrote: > > I just noted the following: > > > > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from ../../../kern/kern_exec.c:368 > > lock order reversal > > 1st 0xc438e6a8 process lock (process lock) @ ../../../kern/kern_exec.c:368 > > 2nd 0xc0413d20 filelist lock (filelist lock) @ ../../../kern/kern_descrip.c:1133 > > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from ../../../kern/kern_exec.c:368 > > > > $ ident /sys/kern/kern_exec.c > > /sys/kern/kern_exec.c: > > $FreeBSD: src/sys/kern/kern_exec.c,v 1.189 2002/09/05 07:30:14 davidxu Exp $ > > $ ident /sys/kern/kern_descrip.c > > /sys/kern/kern_descrip.c: > > $FreeBSD: src/sys/kern/kern_descrip.c,v 1.158 2002/09/03 20:16:31 jhb Exp $ > > > > This occurred when starting up Netscape. > > I just saw this in a recent version of -stable while running mozilla. I > think the problem is in the following set?id handling code in execve(): > > /* Close any file descriptors 0..2 that reference procfs */ > setugidsafety(td); > /* Make sure file descriptors 0..2 are in use. */ > error = fdcheckstd(td); > if (error != 0) > goto done1; > > When I looked at this code before, I assumed that fdcheckstd() just > verified that the proper fds where in use, but on closer inspection it > appears that fdcheckstd() attempts to point any unused fds in 0..2 to > /dev/null. This calls falloc(), which calls uma_zalloc() and grabs the > filelist lock, all of which happens while execve() holds the process > lock. The do_dup() call in fdcheckstd() could also be a problem. > > I don't think dropping the process lock is correct, and calling falloc() > and vn_open() before grabbing the process lock might also be insecure. > Other than just causing execve() to fail in this situation, the only > other fix that I can think of would be to preallocate the struct file > and pre-open /dev/null if we're execing a set?id executable, and then > jam this into the descriptor table if it turns out to be needed. Barf! I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen before grabbing the proc lock. Dropping locks in the middle or pre-allocating should always be a last resort. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 20:28:57 2002 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 4AB7637B400 for ; Tue, 10 Sep 2002 20:28:56 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C725843E4A for ; Tue, 10 Sep 2002 20:28:55 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8B3Slwr096727; Tue, 10 Sep 2002 20:28:51 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209110328.g8B3Slwr096727@gw.catspoiler.org> Date: Tue, 10 Sep 2002 20:28:47 -0700 (PDT) From: Don Lewis Subject: Re: Locking problems in exec To: nate@root.org Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Nate Lawson wrote: > I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen > before grabbing the proc lock. Dropping locks in the middle or > pre-allocating should always be a last resort. That is ok as long as there aren't other threads that can mess things up after fdcheckstd() and setugidsafety() have done their thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 21: 6:13 2002 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 CDECA37B400 for ; Tue, 10 Sep 2002 21:06:11 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 424A343E65 for ; Tue, 10 Sep 2002 21:06:11 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.111.103] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.12 $ on Novell NetWare via secured & encrypted transport (TLS); Tue, 10 Sep 2002 22:06:03 -0600 Message-ID: <3D7EC0FC.3090805@hotmail.com> Date: Tue, 10 Sep 2002 21:05:16 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020905 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: uudecode troubles in sharte/tabset. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG uudecode compiles again, but now I'm getting this making world: ===> share/tabset uudecode < /usr/src/share/tabset/3101.uu uudecode < /usr/src/share/tabset/9837.uu uudecode: stdin: 9837: character out of range: [33-96] *** Error code 1 Stop in /usr/src/share/tabset. Dunno whether the problem is uudecode or tabset. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 21:12:11 2002 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 4534D37B400 for ; Tue, 10 Sep 2002 21:12:08 -0700 (PDT) Received: from ref5.freebsd.org (ref5.FreeBSD.org [216.136.204.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F03F43E3B for ; Tue, 10 Sep 2002 21:12:08 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from ref5.freebsd.org (localhost [127.0.0.1]) by ref5.freebsd.org (8.12.6/8.12.6) with ESMTP id g8B4C7IM097859 for ; Tue, 10 Sep 2002 21:12:07 -0700 (PDT) (envelope-from des@ref5.freebsd.org) Received: (from des@localhost) by ref5.freebsd.org (8.12.6/8.12.6/Submit) id g8B4C7IA097857 for current@freebsd.org; Tue, 10 Sep 2002 21:12:07 -0700 (PDT) Date: Tue, 10 Sep 2002 21:12:07 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209110412.g8B4C7IA097857@ref5.freebsd.org> To: current@freebsd.org Subject: i386 tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> share/tabset uudecode: stdin: 9837: character out of range: [33-96] *** Error code 1 Stop in /local0/scratch/des/src/share/tabset. *** Error code 1 Stop in /local0/scratch/des/src/share. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 22:33: 3 2002 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 559D237B400 for ; Tue, 10 Sep 2002 22:32:59 -0700 (PDT) Received: from espresso.q9media.com (espresso.q9media.com [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD5043E3B for ; Tue, 10 Sep 2002 22:32:59 -0700 (PDT) (envelope-from mike@espresso.q9media.com) Received: by espresso.q9media.com (Postfix, from userid 1002) id 06C269E58; Wed, 11 Sep 2002 01:26:38 -0400 (EDT) Date: Wed, 11 Sep 2002 01:26:38 -0400 From: Mike Barcroft To: walt Cc: freebsd-current@freebsd.org Subject: Re: uudecode troubles in sharte/tabset. Message-ID: <20020911012637.B73618@espresso.q9media.com> References: <3D7EC0FC.3090805@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D7EC0FC.3090805@hotmail.com>; from wa1ter@hotmail.com on Tue, Sep 10, 2002 at 09:05:16PM -0700 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG walt writes: > uudecode compiles again, but now I'm getting this making world: > > ===> share/tabset > uudecode < /usr/src/share/tabset/3101.uu > uudecode < /usr/src/share/tabset/9837.uu > uudecode: stdin: 9837: character out of range: [33-96] > *** Error code 1 > > Stop in /usr/src/share/tabset. > > Dunno whether the problem is uudecode or tabset. Just fixed it. Update your sources. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 23: 9:14 2002 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 4036A37B400 for ; Tue, 10 Sep 2002 23:09:09 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E0F843E3B for ; Tue, 10 Sep 2002 23:09:08 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8B68xwr096967; Tue, 10 Sep 2002 23:09:03 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209110609.g8B68xwr096967@gw.catspoiler.org> Date: Tue, 10 Sep 2002 23:08:59 -0700 (PDT) From: Don Lewis Subject: Re: Locking problems in exec To: nate@root.org Cc: current@FreeBSD.ORG, wollman@lcs.mit.edu In-Reply-To: <200209110328.g8B3Slwr096727@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Don Lewis wrote: > On 10 Sep, Nate Lawson wrote: > >> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen >> before grabbing the proc lock. Dropping locks in the middle or >> pre-allocating should always be a last resort. > > That is ok as long as there aren't other threads that can mess things up > after fdcheckstd() and setugidsafety() have done their thing. It looks like threads aren't a problem because of the call to thread_single() at the top of execve(). Ptrace() is still a potential problem, so we can't call fdcheckstd() and setugidsafety() until after credential_changing has been calculated, setsugid() has been called and tracing has been disabled, all of which are done after proc lock has been grabbed. It also looks like we should pre-allocate newprocsig instead of temporarily dropping the lock. Index: kern_exec.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_exec.c,v retrieving revision 1.189 diff -u -r1.189 kern_exec.c --- kern_exec.c 5 Sep 2002 07:30:14 -0000 1.189 +++ kern_exec.c 11 Sep 2002 05:23:25 -0000 @@ -141,7 +141,7 @@ struct vattr attr; int (*img_first)(struct image_params *); struct pargs *oldargs = NULL, *newargs = NULL; - struct procsig *oldprocsig, *newprocsig; + struct procsig *oldprocsig, *newprocsig = NULL; #ifdef KTRACE struct vnode *tracevp = NULL; #endif @@ -352,6 +352,8 @@ i = imgp->endargs - imgp->stringbase; if (ps_arg_cache_limit >= i + sizeof(struct pargs)) newargs = pargs_alloc(i); + MALLOC(newprocsig, struct procsig *, sizeof(struct procsig), M_SUBPROC, + M_WAITOK); /* close files on exec */ fdcloseexec(td); @@ -369,14 +371,11 @@ mp_fixme("procsig needs a lock"); if (p->p_procsig->ps_refcnt > 1) { oldprocsig = p->p_procsig; - PROC_UNLOCK(p); - MALLOC(newprocsig, struct procsig *, sizeof(struct procsig), - M_SUBPROC, M_WAITOK); bcopy(oldprocsig, newprocsig, sizeof(*newprocsig)); newprocsig->ps_refcnt = 1; oldprocsig->ps_refcnt--; - PROC_LOCK(p); p->p_procsig = newprocsig; + newprocsig = NULL; if (p->p_sigacts == &p->p_uarea->u_sigacts) panic("shared procsig but private sigacts?"); @@ -437,8 +436,15 @@ #endif /* Close any file descriptors 0..2 that reference procfs */ setugidsafety(td); - /* Make sure file descriptors 0..2 are in use. */ + /* + * Make sure file descriptors 0..2 are in use. + * + * fdcheckstd() may call falloc() which may block to + * allocate memory, so temporarily drop the process lock. + */ + PROC_UNLOCK(p); error = fdcheckstd(td); + PROC_LOCK(p); if (error != 0) goto done1; /* @@ -538,6 +544,8 @@ crfree(oldcred); else crfree(newcred); + if (newprocsig != NULL) + free(newprocsig, M_SUBPROC); /* * Handle deferred decrement of ref counts. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 23:45:14 2002 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 CD56737B400; Tue, 10 Sep 2002 23:44:57 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B69943E75; Tue, 10 Sep 2002 23:44:57 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8B6inwr097028; Tue, 10 Sep 2002 23:44:53 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209110644.g8B6inwr097028@gw.catspoiler.org> Date: Tue, 10 Sep 2002 23:44:49 -0700 (PDT) From: Don Lewis Subject: nfs_inactive() bug? -> panic: lockmgr: locking against myself To: current@FreeBSD.org, jeff@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've gotten a couple "lockmgr: locking against myself" panics today and it seems to be somewhat reproduceable. I had the serial console hooked up for the last one, so I was able to get a stack trace: panic: lockmgr: locking against myself Debugger("panic") Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 db> tr Debugger(c0449abc) at Debugger+0x45 panic(c0447760,215,0,c6cd7de0,10002) at panic+0x7c lockmgr(c6cd7ea8,10002,c6cd7de0,c6381f00,c6cd7de0) at lockmgr+0x412 vop_sharedlock(e4b90b58,c047c440,c6cd7de0,1010002,c6381f00) at vop_sharedlock+0x 6e vn_lock(c6cd7de0,10002,c6381f00) at vn_lock+0xb4 vrele(c6cd7de0,c6cd7de0,0,c681cb00,c6381f00,1) at vrele+0x8d nfs_inactive(e4b90bdc,c047c3c0,c6cd7de0,c6381f00,c6381f00) at nfs_inactive+0xbd VOP_INACTIVE(c6cd7de0,c6381f00) at VOP_INACTIVE+0xa0 vrele(c6cd7de0,c6834474,c6834474,e4b90c38,c02eed4a) at vrele+0x9b vn_close(c6cd7de0,2,c681cb00,c6381f00,e4b90c70) at vn_close+0x37 vn_closefile(c6834474,c6381f00) at vn_closefile+0x1e fdrop_locked(c6834474,c6381f00,c04fe8ac,0,c0446020) at fdrop_locked+0x102 fdrop(c6834474,c6381f00,c028a1ec,c6381f00,c6377c8c) at fdrop+0x24 closef(c6834474,c6381f00,c6834474,c6c0d3f8,c6381f00) at closef+0x77 close(c6381f00,e4b90d14,1,b9,202) at close+0x107 syscall(2f,2f,2f,82124cc,23) at syscall+0x243 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (6, FreeBSD ELF32, close), eip = 0x4862ff3b, esp = 0xbfbff2dc, ebp = 0xbfbff358 --- db> show lockedvnods Locked vnodes 0xc6cd7de0: type VREG, usecount 0, writecount 0, refcount 0, flags (VV_OBJBUF) tag VT_NFS, fileid 112174 fsid 0x100ff02 It looks like the call to vrele() from vn_close() is executing the following code: if (vp->v_usecount == 1) { vp->v_usecount--; /* * We must call VOP_INACTIVE with the node locked. * If we are doing a vput, the node is already locked, * but, in the case of vrele, we must explicitly lock * the vnode before calling VOP_INACTIVE. */ if (vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, td) == 0) VOP_INACTIVE(vp, td); VI_LOCK(vp); if (VSHOULDFREE(vp)) vfree(vp); else vlruvp(vp); VI_UNLOCK(vp); It has decremented v_usecount to 0, grabbed an exclusive lock on the vnode, and has called VOP_INACTIVE(). It looks like nfs_inactive() is executing the following code: if (sp) { /* * We need a reference to keep the vnode from being * recycled by getnewvnode while we do the I/O * associated with discarding the buffers unless we * are being forcibly unmounted in which case we already * have our own reference. */ if (ap->a_vp->v_usecount > 0) (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); else if (vget(ap->a_vp, 0, td)) panic("nfs_inactive: lost vnode"); else { (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); vrele(ap->a_vp); } Because v_usecount was 0, nfs_inactive() calls vget(), which increments v_usecount to 1, has called nfs_vinvalbuf(), and finally calls vrele() again. Because v_usecount is 1, vrele() is re-executing the same code and blows up when it tries to grab the lock again. If that didn't cause a panic, VOP_INACTIVE() and nfs_inactive() would be called recursively, which would probably be a bad thing ... I suspect that nfs_inactive() needs to avoid calling vrele() here and should just decrement the v_usecount with the appropriate locking. Something like: VI_LOCK(ap->a_vp); ap->a_vp->v_usecount--; VI_UNLOCK(ap->a_vp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 10 23:58:17 2002 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 35E2137B401; Tue, 10 Sep 2002 23:58:10 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A83EA43E42; Tue, 10 Sep 2002 23:58:09 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8B6w2wr097059; Tue, 10 Sep 2002 23:58:06 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209110658.g8B6w2wr097059@gw.catspoiler.org> Date: Tue, 10 Sep 2002 23:58:02 -0700 (PDT) From: Don Lewis Subject: Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself To: current@FreeBSD.ORG, jeff@FreeBSD.ORG In-Reply-To: <200209110644.g8B6inwr097028@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10 Sep, Don Lewis wrote: > It looks like the call to vrele() from vn_close() is executing the > following code: > > if (vp->v_usecount == 1) { > vp->v_usecount--; > /* > * We must call VOP_INACTIVE with the node locked. > * If we are doing a vput, the node is already locked, > * but, in the case of vrele, we must explicitly lock > * the vnode before calling VOP_INACTIVE. > */ > if (vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, td) == 0) > VOP_INACTIVE(vp, td); > VI_LOCK(vp); > if (VSHOULDFREE(vp)) > vfree(vp); > else > vlruvp(vp); > VI_UNLOCK(vp); > > It has decremented v_usecount to 0, grabbed an exclusive lock on the > vnode, and has called VOP_INACTIVE(). > It looks like nfs_inactive() is executing the following code: > > if (sp) { > /* > * We need a reference to keep the vnode from being > * recycled by getnewvnode while we do the I/O > * associated with discarding the buffers unless we > * are being forcibly unmounted in which case we already > * have our own reference. > */ > if (ap->a_vp->v_usecount > 0) > (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); > else if (vget(ap->a_vp, 0, td)) > panic("nfs_inactive: lost vnode"); > else { > (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); > vrele(ap->a_vp); > } > A potentially better solution just occurred to me. It looks like it would be better if vrele() waited to decrement v_usecount until *after* the call to VOP_INACTIVE() (and after the call to VI_LOCK()). If that were done, nfs_inactive() wouldn't need to muck with v_usecount at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 0:14: 3 2002 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 8AC9237B401; Wed, 11 Sep 2002 00:13:53 -0700 (PDT) Received: from PIKES.panasas.com (gw2.panasas.com [65.194.124.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15F9D43E65; Wed, 11 Sep 2002 00:13:52 -0700 (PDT) (envelope-from ddas@panasas.com) Received: from panasas.com ([172.17.19.38]) by PIKES.panasas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RYSG576N; Wed, 11 Sep 2002 03:13:50 -0400 Message-ID: <3D7EED05.6020709@panasas.com> Date: Wed, 11 Sep 2002 00:13:09 -0700 From: Deepankar Das User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: Don Lewis Cc: current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself References: <200209110644.g8B6inwr097028@gw.catspoiler.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I remember seeing this panic many months back. I had fixed this in our Freebsd source base. Here is the scenario: vrele() { if (vp->v_usecount == 1) { vp->usecount--; if (VSHOULDFREE(vp)) vfree(vp); vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, p); ---- (A) VOP_INACTIVE() { /* translates to nfs_inactive() */ sp = np->n_sillyrename; if (sp) { if (ap->a_vp->v_usecount > 0) { ... } else { vget(ap->a_vp, 0, p); nfs_vinvalbuf(ap->a_vp, 0, ...); vrele(ap->a_vp); ---- (B) } ... } } } } vrele() calls nfs_inactive() since the vp->v_usecount == 0. Before calling nfs_inactive, it locks the vnode at (A) (since VOP_INACTIVE() expects the vnode to be locked and VOP_INACTIVE() releases the lock at the end). In nfs_inactive() a check is made for to see if the file was renamed/deleted while it was still in use. In this case it was, and so np->n_sillyrename is valid. To make sure that the vnode does not get reused while doing the I/O associated with discarding the buffers, the use_count is bumped up using vget(). Then nfs_vinvalbuf() is called to flush and invalidate all dirty buffers. After that vrele() is done on the vnode at (B). vrele() again comes to (A) and tries to lock the vnode, which was already locked before by the same process in the 1st pass. The kernel panics with "locking against myself". The vrele() that is done at (B) causes the cycle to be repeated. vrele() calls nfs_inactive() which calls vrele() and so forth. In nfs_inactive(), we know that the function calling it will free the vnode. So we need not call vfree(). We also know that we should not lock the vnode, again, and call VOP_INACTIVE(). So the fix is to inline the part of vrele() that just decrements the usecount. The following would be the fix. This is 4.3 source base. ==== //depot/dev/freebsd-brick/src/sys/nfs/nfs_node.c#3 (text) ==== 225c225,244 < vrele(ap->a_vp); --- > /* > * Inline part of vrele() since VOP_INACTIVE > * has already been called. > */ > simple_lock(&ap->a_vp->v_interlock); > if (--ap->a_vp->v_usecount <= 0) { > #ifdef DIAGNOSTIC > if (ap->a_vp->v_usecount < 0 || > ap->a_vp->v_writecount != 0) { > vprint("nfs_inactive: bad ref count", > ap->a_vp); > panic("nfs_inactive: ref cnt"); > } > #endif > /* > * Since this is nfs_inactive(), vfree() > * would be called from the caller. > */ > } > simple_unlock(&ap->a_vp->v_interlock); Deepankar Don Lewis wrote: > I've gotten a couple "lockmgr: locking against myself" panics today and > it seems to be somewhat reproduceable. I had the serial console hooked > up for the last one, so I was able to get a stack trace: > > > panic: lockmgr: locking against myself > Debugger("panic") > Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 > db> tr > Debugger(c0449abc) at Debugger+0x45 > panic(c0447760,215,0,c6cd7de0,10002) at panic+0x7c > lockmgr(c6cd7ea8,10002,c6cd7de0,c6381f00,c6cd7de0) at lockmgr+0x412 > vop_sharedlock(e4b90b58,c047c440,c6cd7de0,1010002,c6381f00) at vop_sharedlock+0x > 6e > vn_lock(c6cd7de0,10002,c6381f00) at vn_lock+0xb4 > vrele(c6cd7de0,c6cd7de0,0,c681cb00,c6381f00,1) at vrele+0x8d > nfs_inactive(e4b90bdc,c047c3c0,c6cd7de0,c6381f00,c6381f00) at nfs_inactive+0xbd > VOP_INACTIVE(c6cd7de0,c6381f00) at VOP_INACTIVE+0xa0 > vrele(c6cd7de0,c6834474,c6834474,e4b90c38,c02eed4a) at vrele+0x9b > vn_close(c6cd7de0,2,c681cb00,c6381f00,e4b90c70) at vn_close+0x37 > vn_closefile(c6834474,c6381f00) at vn_closefile+0x1e > fdrop_locked(c6834474,c6381f00,c04fe8ac,0,c0446020) at fdrop_locked+0x102 > fdrop(c6834474,c6381f00,c028a1ec,c6381f00,c6377c8c) at fdrop+0x24 > closef(c6834474,c6381f00,c6834474,c6c0d3f8,c6381f00) at closef+0x77 > close(c6381f00,e4b90d14,1,b9,202) at close+0x107 > syscall(2f,2f,2f,82124cc,23) at syscall+0x243 > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (6, FreeBSD ELF32, close), eip = 0x4862ff3b, esp = 0xbfbff2dc, ebp = > 0xbfbff358 --- > > db> show lockedvnods > Locked vnodes > 0xc6cd7de0: type VREG, usecount 0, writecount 0, refcount 0, flags (VV_OBJBUF) > tag VT_NFS, fileid 112174 fsid 0x100ff02 > > > It looks like the call to vrele() from vn_close() is executing the > following code: > > if (vp->v_usecount == 1) { > vp->v_usecount--; > /* > * We must call VOP_INACTIVE with the node locked. > * If we are doing a vput, the node is already locked, > * but, in the case of vrele, we must explicitly lock > * the vnode before calling VOP_INACTIVE. > */ > if (vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, td) == 0) > VOP_INACTIVE(vp, td); > VI_LOCK(vp); > if (VSHOULDFREE(vp)) > vfree(vp); > else > vlruvp(vp); > VI_UNLOCK(vp); > > It has decremented v_usecount to 0, grabbed an exclusive lock on the > vnode, and has called VOP_INACTIVE(). > > It looks like nfs_inactive() is executing the following code: > > if (sp) { > /* > * We need a reference to keep the vnode from being > * recycled by getnewvnode while we do the I/O > * associated with discarding the buffers unless we > * are being forcibly unmounted in which case we already > * have our own reference. > */ > if (ap->a_vp->v_usecount > 0) > (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); > else if (vget(ap->a_vp, 0, td)) > panic("nfs_inactive: lost vnode"); > else { > (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); > vrele(ap->a_vp); > } > > Because v_usecount was 0, nfs_inactive() calls vget(), which increments > v_usecount to 1, has called nfs_vinvalbuf(), and finally calls vrele() > again. > > Because v_usecount is 1, vrele() is re-executing the same code and blows > up when it tries to grab the lock again. If that didn't cause a panic, > VOP_INACTIVE() and nfs_inactive() would be called recursively, which > would probably be a bad thing ... > > I suspect that nfs_inactive() needs to avoid calling vrele() here and > should just decrement the v_usecount with the appropriate locking. > Something like: > VI_LOCK(ap->a_vp); > ap->a_vp->v_usecount--; > VI_UNLOCK(ap->a_vp); > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ------------------------------------------------------------------------------- Deepankar Das Panasas Inc. Pioneering the World's Most Scalable and Agile Storage Network www.panasas.com ddas@panasas.com 510-608-4366 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 4:25:17 2002 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 3D11037B437; Wed, 11 Sep 2002 04:25:01 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id F11C643E4A; Wed, 11 Sep 2002 04:24:59 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Sep 2002 12:24:58 +0100 (BST) To: Don Lewis Cc: current@FreeBSD.ORG, jeff@FreeBSD.ORG Subject: Re: nfs_inactive() bug? -> panic: lockmgr: locking against myself In-Reply-To: Your message of "Tue, 10 Sep 2002 23:58:02 PDT." <200209110658.g8B6w2wr097059@gw.catspoiler.org> Date: Wed, 11 Sep 2002 12:24:58 +0100 From: Ian Dowse Message-ID: <200209111224.aa37675@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200209110658.g8B6w2wr097059@gw.catspoiler.org>, Don Lewis writes: > >A potentially better solution just occurred to me. It looks like it >would be better if vrele() waited to decrement v_usecount until *after* >the call to VOP_INACTIVE() (and after the call to VI_LOCK()). If that >were done, nfs_inactive() wouldn't need to muck with v_usecount at all. I've looked at this before; I think some filesystems (ufs anyway) depend on v_usecount being 0 when VOP_INACTIVE() is called. The patch I have had lying around for quite a while is below. It adds a vnode flag to avoid recursion into the last-reference handling code in vrele/vput, which is the real problem. It also guarantees that a vnode will not be recycled during VOP_INACTIVE(), so the nfs code no longer needs to hold an extra reference in the first place. The flag manipulation code got a bit messy after Jeff's vnode flag splitting work, so the patch could probably be improved. Whatever way this is done, we should try to avoid adding more hacks to the nfs_inactive() code anyway. Ian Index: sys/vnode.h =================================================================== RCS file: /home/iedowse/CVS/src/sys/sys/vnode.h,v retrieving revision 1.206 diff -u -r1.206 vnode.h --- sys/vnode.h 1 Sep 2002 20:37:21 -0000 1.206 +++ sys/vnode.h 11 Sep 2002 11:06:46 -0000 @@ -220,6 +220,7 @@ #define VI_DOOMED 0x0080 /* This vnode is being recycled */ #define VI_FREE 0x0100 /* This vnode is on the freelist */ #define VI_OBJDIRTY 0x0400 /* object might be dirty */ +#define VI_INACTIVE 0x0800 /* VOP_INACTIVE is in progress */ /* * XXX VI_ONWORKLST could be replaced with a check for NULL list elements * in v_synclist. @@ -377,14 +378,14 @@ /* Requires interlock */ #define VSHOULDFREE(vp) \ - (!((vp)->v_iflag & (VI_FREE|VI_DOOMED)) && \ + (!((vp)->v_iflag & (VI_FREE|VI_DOOMED|VI_INACTIVE)) && \ !(vp)->v_holdcnt && !(vp)->v_usecount && \ (!(vp)->v_object || \ !((vp)->v_object->ref_count || (vp)->v_object->resident_page_count))) /* Requires interlock */ #define VMIGHTFREE(vp) \ - (!((vp)->v_iflag & (VI_FREE|VI_DOOMED|VI_XLOCK)) && \ + (!((vp)->v_iflag & (VI_FREE|VI_DOOMED|VI_XLOCK|VI_INACTIVE)) && \ LIST_EMPTY(&(vp)->v_cache_src) && !(vp)->v_usecount) /* Requires interlock */ Index: nfsclient/nfs_node.c =================================================================== RCS file: /home/iedowse/CVS/src/sys/nfsclient/nfs_node.c,v retrieving revision 1.55 diff -u -r1.55 nfs_node.c --- nfsclient/nfs_node.c 11 Jul 2002 17:54:58 -0000 1.55 +++ nfsclient/nfs_node.c 11 Sep 2002 11:06:46 -0000 @@ -289,21 +289,7 @@ } else sp = NULL; if (sp) { - /* - * We need a reference to keep the vnode from being - * recycled by getnewvnode while we do the I/O - * associated with discarding the buffers unless we - * are being forcibly unmounted in which case we already - * have our own reference. - */ - if (ap->a_vp->v_usecount > 0) - (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); - else if (vget(ap->a_vp, 0, td)) - panic("nfs_inactive: lost vnode"); - else { - (void) nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); - vrele(ap->a_vp); - } + (void)nfs_vinvalbuf(ap->a_vp, 0, sp->s_cred, td, 1); /* * Remove the silly file that was rename'd earlier */ Index: kern/vfs_subr.c =================================================================== RCS file: /home/iedowse/CVS/src/sys/kern/vfs_subr.c,v retrieving revision 1.401 diff -u -r1.401 vfs_subr.c --- kern/vfs_subr.c 5 Sep 2002 20:46:19 -0000 1.401 +++ kern/vfs_subr.c 11 Sep 2002 11:06:46 -0000 @@ -829,7 +829,8 @@ for (count = 0; count < freevnodes; count++) { vp = TAILQ_FIRST(&vnode_free_list); - KASSERT(vp->v_usecount == 0, + KASSERT(vp->v_usecount == 0 && + (vp->v_iflag & VI_INACTIVE) == 0, ("getnewvnode: free vnode isn't")); TAILQ_REMOVE(&vnode_free_list, vp, v_freelist); @@ -1980,8 +1981,8 @@ KASSERT(vp->v_writecount < vp->v_usecount || vp->v_usecount < 1, ("vrele: missed vn_close")); - if (vp->v_usecount > 1) { - + if (vp->v_usecount > 1 || + ((vp->v_iflag & VI_INACTIVE) && vp->v_usecount == 1)) { vp->v_usecount--; VI_UNLOCK(vp); @@ -1991,13 +1992,20 @@ if (vp->v_usecount == 1) { vp->v_usecount--; /* - * We must call VOP_INACTIVE with the node locked. - * If we are doing a vput, the node is already locked, - * but, in the case of vrele, we must explicitly lock - * the vnode before calling VOP_INACTIVE. + * We must call VOP_INACTIVE with the node locked. Mark + * as VI_INACTIVE to avoid recursion. */ - if (vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, td) == 0) + if (vn_lock(vp, LK_EXCLUSIVE | LK_INTERLOCK, td) == 0) { + VI_LOCK(vp); + vp->v_iflag |= VI_INACTIVE; + VI_UNLOCK(vp); VOP_INACTIVE(vp, td); + VI_LOCK(vp); + KASSERT(vp->v_iflag & VI_INACTIVE, + ("vrele: lost VI_INACTIVE")); + vp->v_iflag &= ~VI_INACTIVE; + VI_UNLOCK(vp); + } VI_LOCK(vp); if (VSHOULDFREE(vp)) vfree(vp); @@ -2033,7 +2041,8 @@ KASSERT(vp->v_writecount < vp->v_usecount || vp->v_usecount < 1, ("vput: missed vn_close")); - if (vp->v_usecount > 1) { + if (vp->v_usecount > 1 || + ((vp->v_iflag & VI_INACTIVE) && vp->v_usecount == 1)) { vp->v_usecount--; VOP_UNLOCK(vp, LK_INTERLOCK, td); return; @@ -2042,13 +2051,16 @@ if (vp->v_usecount == 1) { vp->v_usecount--; /* - * We must call VOP_INACTIVE with the node locked. - * If we are doing a vput, the node is already locked, - * so we just need to release the vnode mutex. + * We must call VOP_INACTIVE with the node locked, so + * we just need to release the vnode mutex. Mark as + * as VI_INACTIVE to avoid recursion. */ + vp->v_iflag |= VI_INACTIVE; VI_UNLOCK(vp); VOP_INACTIVE(vp, td); VI_LOCK(vp); + KASSERT(vp->v_iflag & VI_INACTIVE, ("vput: lost VI_INACTIVE")); + vp->v_iflag &= ~VI_INACTIVE; if (VSHOULDFREE(vp)) vfree(vp); else @@ -2331,12 +2343,16 @@ * deactivated before being reclaimed. Note that the * VOP_INACTIVE will unlock the vnode. */ - if (active) { - if (flags & DOCLOSE) - VOP_CLOSE(vp, FNONBLOCK, NOCRED, td); + if (active && (flags & DOCLOSE)) + VOP_CLOSE(vp, FNONBLOCK, NOCRED, td); + if (active && (vp->v_iflag & VI_INACTIVE) == 0) { + vp->v_iflag |= VI_INACTIVE; if (vn_lock(vp, LK_EXCLUSIVE | LK_NOWAIT, td) != 0) panic("vclean: cannot relock."); VOP_INACTIVE(vp, td); + KASSERT(vp->v_iflag & VI_INACTIVE, + ("vclean: lost VI_INACTIVE")); + vp->v_iflag &= ~VI_INACTIVE; } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 7:21:15 2002 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 5903B37B405 for ; Wed, 11 Sep 2002 07:20:59 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C7043E65 for ; Wed, 11 Sep 2002 07:20:59 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.6/8.12.6) with ESMTP id g8BEKwYB047986 for ; Wed, 11 Sep 2002 07:20:58 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.6/8.12.6/Submit) id g8BEKwoH047984 for current@freebsd.org; Wed, 11 Sep 2002 07:20:58 -0700 (PDT) Date: Wed, 11 Sep 2002 07:20:58 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200209111420.g8BEKwoH047984@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- >>> Kernel build for GENERIC started on Wed Sep 11 06:11:26 PDT 2002 -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Wed Sep 11 07:16:38 PDT 2002 -------------------------------------------------------------- >>> Kernel build for LINT started on Wed Sep 11 07:16:40 PDT 2002 -------------------------------------------------------------- ===> vinum ./aicasm: 877 instructions used ./aicasm: 658 instructions used In file included from /var/tmp/des/src/sys/dev/dgb/dgb.c:89: /var/tmp/des/src/sys/i386/isa/isa_device.h:43:31: opt_compat_oldisa.h: No such file or directory /var/tmp/des/src/sys/dev/dgb/dgb.c:92:2: #error "The dgb device requires the old isa compatibility shims" /var/tmp/des/src/sys/dev/iicbus/iic.c:42:25: machine/iic.h: No such file or directory /var/tmp/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:80:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:81:33: machine/physio_proc.h: No such file or directory In file included from /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:86: /var/tmp/des/src/sys/dev/ncv/ncr53c500hw.h:39:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/ncv/ncr53c500_pccard.c:55:27: machine/dvcfg.h: No such file or directory In file included from /var/tmp/des/src/sys/dev/ncv/ncr53c500_pccard.c:63: /var/tmp/des/src/sys/dev/ncv/ncr53c500hw.h:39:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/nsp/nsp.c:80:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/nsp/nsp.c:81:33: machine/physio_proc.h: No such file or directory /var/tmp/des/src/sys/dev/nsp/nsp_pccard.c:52:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/smbus/smb.c:41:25: machine/smb.h: No such file or directory /var/tmp/des/src/sys/dev/stg/tmc18c30.c:78:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/stg/tmc18c30.c:79:33: machine/physio_proc.h: No such file or directory /var/tmp/des/src/sys/dev/stg/tmc18c30_pccard.c:57:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/stg/tmc18c30_isa.c:65:27: machine/dvcfg.h: No such file or directory /var/tmp/des/src/sys/dev/usb/ukbd.c:419:21: ukbdmap.h: No such file or directory In file included from /var/tmp/des/src/sys/dev/wl/if_wl.c:218: /var/tmp/des/src/sys/i386/isa/isa_device.h:43:31: opt_compat_oldisa.h: No such file or directory /var/tmp/des/src/sys/dev/wl/if_wl.c:224:35: machine/if_wl_wavelan.h: No such file or directory /var/tmp/des/src/sys/dev/wl/if_wl.c:227:2: #error "The wl device requires the old isa compatibility shims" /var/tmp/des/src/sys/kern/subr_prof.c:62:30: machine/asmacros.h: No such file or directory /var/tmp/des/src/sys/kern/subr_prof.c:232:2: #error /var/tmp/des/src/sys/kern/subr_prof.c:243:2: #error /var/tmp/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" /var/tmp/des/src/sys/pci/simos.c:57:2: #error "The simos device requires the old pci compatibility shims" /var/tmp/des/src/sys/dev/syscons/syscons.c:117:18: font.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /var/tmp/des/obj/var/tmp/des/src/sys/LINT. *** Error code 1 Stop in /var/tmp/des/obj/var/tmp/des/src/sys/LINT. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 8:55:55 2002 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 D16F037B400 for ; Wed, 11 Sep 2002 08:55:52 -0700 (PDT) Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id C783543E42 for ; Wed, 11 Sep 2002 08:55:51 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.56.224.151]) by e4.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g8BFtoj2139564 for ; Wed, 11 Sep 2002 11:55:50 -0400 Received: from prxysrv.in.ibm.com (prxysrv.in.ibm.com [9.182.24.69]) by northrelay03.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g8BFtia6053466 for ; Wed, 11 Sep 2002 11:55:46 -0400 Received: from symonds.net (saruman.in.ibm.com [9.182.24.82]) by prxysrv.in.ibm.com (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id 8D0B353E1 for ; Wed, 11 Sep 2002 21:38:13 +0530 (IST) Message-ID: <3D7FB29C.3000203@symonds.net> Date: Thu, 12 Sep 2002 02:46:12 +0530 From: Sid Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Subject: Kernel from latest cvsup refuses to boot. - hangs Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Folks, I am still unable to boot into the kernel from the latest cvsup. I did a "make buildworld and make kernel" and when I try to "boot -vs", it goes on to register procfs and then hangs at this stage....this is what it finally prints...and freezes Timecounters tick every 10.000 msec bpf: lo0 attached. I have booted from an older kernel I had. System Info -------------- FreeBSD 5.0-CURRENT #0: Thu Aug 8 21:48:49 IST 2002 root@calvin:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel.sogood/kernel" at 0xc05ad000. Timecounter "i8254" frequency 119s182 Hz Timecounter "TSC" frequency 996769586 Hz CPU: Pentium III/Pentium III Xeon/Celeron (996n77-MHz 686-class CPU) Origin } "GenuineIntel"` Id = 0868a Stepping = 10 Features=0x383fbff Anyone else experiencing this ? TIA Regards Sid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 10: 7:52 2002 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 C3FD237B400; Wed, 11 Sep 2002 10:07:50 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3823743E6E; Wed, 11 Sep 2002 10:07:50 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g8BH7nfO027269; Wed, 11 Sep 2002 10:07:49 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g8BH7nbB027268; Wed, 11 Sep 2002 10:07:49 -0700 (PDT) Date: Wed, 11 Sep 2002 10:07:49 -0700 From: "David O'Brien" To: current@freebsd.org Subject: Any problems with increaseing the dump(8) block size? Message-ID: <20020911170749.GA27252@dragon.nuxi.com> Reply-To: current@freebsd.org Mail-Followup-To: David O'Brien , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd like to make this commit to get better performance on today's streaming tape drives. It seems my DLT drive doesn't stream well with the default block size of '10'. Index: include/protocols/dumprestore.h =================================================================== RCS file: /home/ncvs/src/include/protocols/dumprestore.h,v retrieving revision 1.10 diff -u -r1.10 dumprestore.h --- include/protocols/dumprestore.h 17 Jul 2002 02:03:19 -0000 1.10 +++ include/protocols/dumprestore.h 19 Jul 2002 05:30:39 -0000 @@ -56,7 +56,7 @@ * or TS_ADDR record. Note that it must be a power of two. */ #define TP_BSIZE 1024 -#define NTREC 10 +#define NTREC 64 #define HIGHDENSITYTREC 32 #define TP_NINDIR (TP_BSIZE/2) #define LBLSIZE 16 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 10: 9:39 2002 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 BB79E37B47C for ; Wed, 11 Sep 2002 10:09:20 -0700 (PDT) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 513C643E42 for ; Wed, 11 Sep 2002 10:09:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9324 invoked from network); 11 Sep 2002 17:09:16 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Sep 2002 17:09:16 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g8BH9HBv035521; Wed, 11 Sep 2002 13:09:17 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200209110609.g8B68xwr096967@gw.catspoiler.org> Date: Wed, 11 Sep 2002 13:09:18 -0400 (EDT) From: John Baldwin To: Don Lewis Subject: Re: Locking problems in exec Cc: wollman@lcs.mit.edu, current@FreeBSD.ORG, nate@root.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Sep-2002 Don Lewis wrote: > On 10 Sep, Don Lewis wrote: >> On 10 Sep, Nate Lawson wrote: >> >>> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen >>> before grabbing the proc lock. Dropping locks in the middle or >>> pre-allocating should always be a last resort. >> >> That is ok as long as there aren't other threads that can mess things up >> after fdcheckstd() and setugidsafety() have done their thing. > > It looks like threads aren't a problem because of the call to > thread_single() at the top of execve(). Ptrace() is still a potential > problem, so we can't call fdcheckstd() and setugidsafety() until after > credential_changing has been calculated, setsugid() has been called and > tracing has been disabled, all of which are done after proc lock has > been grabbed. > > It also looks like we should pre-allocate newprocsig instead of > temporarily dropping the lock. We used to do that but backed it out because it wasn't deemed to be that necessary. If you have a demonstrable problematic race condition that this fixes then it might be a good idea. However, allocating stuff we don't need isn't but so great either. I think ptrace(2) is not an issue because ptrace(2) won't attach to a P_INEXEC process IIRC. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 10:15: 9 2002 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 2967737B400 for ; Wed, 11 Sep 2002 10:15:07 -0700 (PDT) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94DAF43E42 for ; Wed, 11 Sep 2002 10:15:06 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g8BHF5v11961 for ; Wed, 11 Sep 2002 10:15:05 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Wed, 11 Sep 2002 10:15:04 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: current@freebsd.org Subject: Re: Any problems with increaseing the dump(8) block size? In-Reply-To: <20020911170749.GA27252@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No. Don't change this- people are very well attuned to using an argument to change it and all your change will do is catch the unwary and possibly break binary compat on apps that define records based off of NTREC. On Wed, 11 Sep 2002, David O'Brien wrote: > I'd like to make this commit to get better performance on today's > streaming tape drives. It seems my DLT drive doesn't stream well with > the default block size of '10'. > > > Index: include/protocols/dumprestore.h > =================================================================== > RCS file: /home/ncvs/src/include/protocols/dumprestore.h,v > retrieving revision 1.10 > diff -u -r1.10 dumprestore.h > --- include/protocols/dumprestore.h 17 Jul 2002 02:03:19 -0000 1.10 > +++ include/protocols/dumprestore.h 19 Jul 2002 05:30:39 -0000 > @@ -56,7 +56,7 @@ > * or TS_ADDR record. Note that it must be a power of two. > */ > #define TP_BSIZE 1024 > -#define NTREC 10 > +#define NTREC 64 > #define HIGHDENSITYTREC 32 > #define TP_NINDIR (TP_BSIZE/2) > #define LBLSIZE 16 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 10:55:58 2002 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 5DE4E37B400 for ; Wed, 11 Sep 2002 10:55:54 -0700 (PDT) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF37343E72 for ; Wed, 11 Sep 2002 10:55:53 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6190 invoked from network); 11 Sep 2002 17:55:49 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Sep 2002 17:55:49 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g8BHtKBv035724 for ; Wed, 11 Sep 2002 13:55:28 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 11 Sep 2002 13:55:21 -0400 (EDT) From: John Baldwin To: current@FreeBSD.org Subject: Call for testers for mlx(4) patch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can people please test the following patch also available at http://www.FreeBSD.org/~jhb/patches/mlx.patch It fixes problems when using older Mylex controllers in Alphas, but I'd like to make sure it doesn't break mlx(4) for other folks before committing. Mike Smith has given the patch a once over as well. Thanks. Index: dev/mlx/mlx_disk.c =================================================================== RCS file: /usr/cvs/src/sys/dev/mlx/mlx_disk.c,v retrieving revision 1.22 diff -u -r1.22 mlx_disk.c --- dev/mlx/mlx_disk.c 12 Sep 2001 08:37:08 -0000 1.22 +++ dev/mlx/mlx_disk.c 9 Sep 2002 14:22:52 -0000 @@ -264,11 +264,15 @@ /* * Set maximum I/O size to the lesser of the recommended maximum and the practical - * maximum. + * maximum except on v2 cards where the maximum is set to 8 pages. */ - s1 = sc->mlxd_controller->mlx_enq2->me_maxblk * MLX_BLKSIZE; - s2 = (sc->mlxd_controller->mlx_enq2->me_max_sg - 1) * PAGE_SIZE; - dsk->si_iosize_max = imin(s1, s2); + if (sc->mlxd_controller->mlx_iftype == MLX_IFTYPE_2) + dsk->si_iosize_max = 8 * PAGE_SIZE; + else { + s1 = sc->mlxd_controller->mlx_enq2->me_maxblk * MLX_BLKSIZE; + s2 = (sc->mlxd_controller->mlx_enq2->me_max_sg - 1) * PAGE_SIZE; + dsk->si_iosize_max = imin(s1, s2); + } return (0); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 11:31: 1 2002 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 575BC37B400 for ; Wed, 11 Sep 2002 11:30:58 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B3CA543E77 for ; Wed, 11 Sep 2002 11:30:54 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 21944 invoked by uid 1000); 11 Sep 2002 18:30:55 -0000 Date: Wed, 11 Sep 2002 11:30:55 -0700 (PDT) From: Nate Lawson To: Sid Carter Cc: current@freebsd.org Subject: Re: Kernel from latest cvsup refuses to boot. - hangs In-Reply-To: <3D7FB29C.3000203@symonds.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's probably a device driver probe problem although it's impossible to tell without more info. Enable options DDB, boot -vs, wait for the hang. Hit CTRL-ALT-ESC to go into DDB and type tr to get a backtrace. Copy the trace info (serial console is best for this). Hit c for continue, wait, repeat. Chances are you'll still be at the same backtrace. If so, then this is the code that's hanging. -Nate On Thu, 12 Sep 2002, Sid Carter wrote: > Hi Folks, > > I am still unable to boot into the kernel from the latest cvsup. > > I did a "make buildworld and make kernel" and when I try to "boot -vs", > it goes on to register procfs and then hangs at this stage....this is > what it finally prints...and freezes > > Timecounters tick every 10.000 msec > bpf: lo0 attached. > > I have booted from an older kernel I had. > > System Info > -------------- > FreeBSD 5.0-CURRENT #0: Thu Aug 8 21:48:49 IST 2002 > root@calvin:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel.sogood/kernel" at 0xc05ad000. > Timecounter "i8254" frequency 119s182 Hz > Timecounter "TSC" frequency 996769586 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (996n77-MHz 686-class CPU) > Origin } "GenuineIntel"` Id = 0868a Stepping = 10 > > Features=0x383fbff OV,P\M-AT,PSE36,MMX,FXSR,SSE> > > Anyone else experiencing this ? > > TIA > Regards > Sid > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 11:38:13 2002 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 C0A3937B400 for ; Wed, 11 Sep 2002 11:38:08 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 02E5B43E4A for ; Wed, 11 Sep 2002 11:38:08 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 21957 invoked by uid 1000); 11 Sep 2002 18:38:09 -0000 Date: Wed, 11 Sep 2002 11:38:09 -0700 (PDT) From: Nate Lawson To: current@freebsd.org Cc: phk@freebsd.org Subject: Re: alpha tinderbox failure In-Reply-To: <200209111420.g8BEKwoH047984@beast.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JKH task: go through conf/NOTES and move devices that don't (or could never) build on alpha to i386/conf/NOTES. At the end of this, LINT should build on alpha and i386. BTW, I would think there should be a pc98/conf/NOTES that most stuff moved out of the global notes should go into as well as i386. Anyone up for this? -Nate On Wed, 11 Sep 2002, Dag-Erling Smorgrav wrote: > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > >>> stage 1: bootstrap tools > -------------------------------------------------------------- > >>> stage 2: cleaning up the object tree > -------------------------------------------------------------- > >>> stage 2: rebuilding the object tree > -------------------------------------------------------------- > >>> stage 2: build tools > -------------------------------------------------------------- > >>> stage 3: cross tools > -------------------------------------------------------------- > >>> stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include > -------------------------------------------------------------- > >>> stage 4: building libraries > -------------------------------------------------------------- > >>> stage 4: make dependencies > -------------------------------------------------------------- > >>> stage 4: building everything.. > -------------------------------------------------------------- > >>> Kernel build for GENERIC started on Wed Sep 11 06:11:26 PDT 2002 > -------------------------------------------------------------- > >>> Kernel build for GENERIC completed on Wed Sep 11 07:16:38 PDT 2002 > -------------------------------------------------------------- > >>> Kernel build for LINT started on Wed Sep 11 07:16:40 PDT 2002 > -------------------------------------------------------------- > ===> vinum > ./aicasm: 877 instructions used > ./aicasm: 658 instructions used > In file included from /var/tmp/des/src/sys/dev/dgb/dgb.c:89: > /var/tmp/des/src/sys/i386/isa/isa_device.h:43:31: opt_compat_oldisa.h: No such file or directory > /var/tmp/des/src/sys/dev/dgb/dgb.c:92:2: #error "The dgb device requires the old isa compatibility shims" > /var/tmp/des/src/sys/dev/iicbus/iic.c:42:25: machine/iic.h: No such file or directory > /var/tmp/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" > /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:80:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:81:33: machine/physio_proc.h: No such file or directory > In file included from /var/tmp/des/src/sys/dev/ncv/ncr53c500.c:86: > /var/tmp/des/src/sys/dev/ncv/ncr53c500hw.h:39:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/ncv/ncr53c500_pccard.c:55:27: machine/dvcfg.h: No such file or directory > In file included from /var/tmp/des/src/sys/dev/ncv/ncr53c500_pccard.c:63: > /var/tmp/des/src/sys/dev/ncv/ncr53c500hw.h:39:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/nsp/nsp.c:80:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/nsp/nsp.c:81:33: machine/physio_proc.h: No such file or directory > /var/tmp/des/src/sys/dev/nsp/nsp_pccard.c:52:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/smbus/smb.c:41:25: machine/smb.h: No such file or directory > /var/tmp/des/src/sys/dev/stg/tmc18c30.c:78:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/stg/tmc18c30.c:79:33: machine/physio_proc.h: No such file or directory > /var/tmp/des/src/sys/dev/stg/tmc18c30_pccard.c:57:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/stg/tmc18c30_isa.c:65:27: machine/dvcfg.h: No such file or directory > /var/tmp/des/src/sys/dev/usb/ukbd.c:419:21: ukbdmap.h: No such file or directory > In file included from /var/tmp/des/src/sys/dev/wl/if_wl.c:218: > /var/tmp/des/src/sys/i386/isa/isa_device.h:43:31: opt_compat_oldisa.h: No such file or directory > /var/tmp/des/src/sys/dev/wl/if_wl.c:224:35: machine/if_wl_wavelan.h: No such file or directory > /var/tmp/des/src/sys/dev/wl/if_wl.c:227:2: #error "The wl device requires the old isa compatibility shims" > /var/tmp/des/src/sys/kern/subr_prof.c:62:30: machine/asmacros.h: No such file or directory > /var/tmp/des/src/sys/kern/subr_prof.c:232:2: #error > /var/tmp/des/src/sys/kern/subr_prof.c:243:2: #error > /var/tmp/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" > /var/tmp/des/src/sys/pci/simos.c:57:2: #error "The simos device requires the old pci compatibility shims" > /var/tmp/des/src/sys/dev/syscons/syscons.c:117:18: font.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /var/tmp/des/obj/var/tmp/des/src/sys/LINT. > *** Error code 1 > > Stop in /var/tmp/des/obj/var/tmp/des/src/sys/LINT. > *** Error code 1 > > Stop in /var/tmp/des/src. > *** Error code 1 > > Stop in /var/tmp/des/src. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 12: 7:47 2002 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 0728D37B401 for ; Wed, 11 Sep 2002 12:07:42 -0700 (PDT) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5265C43E65 for ; Wed, 11 Sep 2002 12:07:41 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1402 invoked from network); 11 Sep 2002 19:08:24 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail14.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Sep 2002 19:08:24 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g8BJ7dBv035994; Wed, 11 Sep 2002 15:07:39 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Sep 2002 15:07:40 -0400 (EDT) From: John Baldwin To: Nate Lawson Subject: Re: alpha tinderbox failure Cc: phk@freebsd.org, current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Sep-2002 Nate Lawson wrote: > JKH task: go through conf/NOTES and move devices that don't (or could > never) build on alpha to i386/conf/NOTES. At the end of this, LINT should > build on alpha and i386. I already did this before when I first created sys/alpha/conf/NOTES. It did build at one time. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 12:49:15 2002 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 B922D37B400 for ; Wed, 11 Sep 2002 12:48:55 -0700 (PDT) Received: from maild.telia.com (maild.telia.com [194.22.190.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF3E43E4A for ; Wed, 11 Sep 2002 12:48:54 -0700 (PDT) (envelope-from john@veidit.net) Received: from d1o1000.telia.com (d1o1000.telia.com [217.208.12.241]) by maild.telia.com (8.12.5/8.12.5) with ESMTP id g8BJmr5h013488 for ; Wed, 11 Sep 2002 21:48:53 +0200 (CEST) X-Original-Recipient: Received: from veidit.net (h162n2fls35o1000.telia.com [217.210.235.162]) by d1o1000.telia.com (8.10.2/8.10.1) with ESMTP id g8BJmqR02460 for ; Wed, 11 Sep 2002 21:48:52 +0200 (CEST) Message-ID: <3D7F9DF4.3000600@veidit.net> Date: Wed, 11 Sep 2002 21:48:04 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: current Subject: libiconv broken Content-Type: multipart/mixed; boundary="------------090202040208040202030805" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------090202040208040202030805 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit updated this morning (08.00 CET) to latest current (from GCC 3.1.1 to GCC 3.2) everything runs smoothly. But libiconv seems to break: cc -I. -I. -I../include -I./../include -O -pipe -march=pentium3 -c ./iconv.c -fPIC -DPIC -o .libs/iconv.lo In file included from gbk.h:64, from converters.h:202, from iconv.c:67: gbkext1.h: In function `gbkext1_mbtowc': gbkext1.h:852: unrecognizable insn: (insn 157 155 159 (set (reg:QI 78) (const_int 128 [0x80])) -1 (nil) (nil)) gbkext1.h:852: Internal compiler error in extract_insn, at recog.c:2150 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.8/lib. *** Error code 1 --------------090202040208040202030805 Content-Type: text/plain; name="libiconv.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="libiconv.log" ===> Cleaning for libtool-1.3.4_4 ===> Cleaning for libiconv-1.8_1 ===> Extracting for libiconv-1.8_1 >> Checksum OK for libiconv-1.8.tar.gz. ===> libiconv-1.8_1 depends on executable: libtool - found ===> Patching for libiconv-1.8_1 ===> Applying FreeBSD patches for libiconv-1.8_1 ===> Configuring for libiconv-1.8_1 configure: WARNING: you should use --build, --host, --target checking whether make sets ${MAKE}... yes checking for i386-portbld-freebsd5.0-gcc... cc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix... checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking how to run the C preprocessor... cc -E checking whether cc needs -traditional... no checking for ranlib... ranlib checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel checking how to copy files... cp -p checking how to make hard links... ln checking whether ln -s works... yes checking build system type... i386-portbld-freebsd5.0 checking host system type... i386-portbld-freebsd5.0 checking for AIX... no checking for minix/config.h... no checking for strerror in -lcposix... no checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for /usr/libexec/elf/ld option to reload object files... -r checking for BSD-compatible nm... nm checking how to recognise dependant libraries... pass_all checking command to parse nm output... ok checking for dlfcn.h... yes checking for i386-portbld-freebsd5.0-ranlib... (cached) ranlib checking for i386-portbld-freebsd5.0-strip... no checking for strip... strip checking for objdir... .libs checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.lo... yes checking if cc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... freebsd5.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... yes creating libtool checking host system type... i386-unknown-freebsdelf5.0 checking for ranlib... ranlib checking whether we are using GNU C... yes checking for object suffix... o checking for executable suffix... no checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.lo... yes checking if cc supports -fno-rtti -fno-exceptions ... yes checking if cc static flag -static works... -static checking whether ln -s works... yes checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes checking for BSD-compatible nm... /usr/bin/nm -B checking command to parse /usr/bin/nm -B output... ok checking how to hardcode library paths into programs... immediate checking for /usr/libexec/elf/ld option to reload object files... -r checking dynamic linker characteristics... freebsdelf5.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for objdir... .libs creating libtool checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for shared library run path origin... done checking for iconv... no, consider installing GNU libiconv checking for msgfmt... no checking for gmsgfmt... : checking for xgettext... no checking for msgmerge... no checking whether NLS is requested... yes checking for GNU gettext in libc... no checking for iconv... (cached) no, consider installing GNU libiconv checking for GNU gettext in libintl... no checking for locale.h... yes checking for stdlib.h... yes checking for mbstate_t... yes checking for mbrtowc... yes checking for wcrtomb... yes checking for mbsinit... yes checking for setlocale... yes checking for wchar.h... yes checking for EILSEQ... yes checking byte ordering... little endian configure: creating ./config.status config.status: creating Makefile config.status: creating lib/Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating man/Makefile config.status: creating tests/Makefile config.status: creating include/iconv.h config.status: creating lib/config.h config.status: creating src/config.h config.status: creating po/POTFILES config.status: creating po/Makefile configure: configuring in libcharset configure: running /bin/sh './configure' --enable-static --without-libintl-prefix --prefix=/usr/local i386-portbld-freebsd5.0 'CFLAGS=-O -pipe -march=pentium3' host_alias=i386-portbld-freebsd5.0 build_alias=i386-portbld-freebsd5.0 target_alias=i386-portbld-freebsd5.0 CC=cc --cache-file=/dev/null --srcdir=. configure: WARNING: you should use --build, --host, --target checking whether make sets ${MAKE}... yes checking for i386-portbld-freebsd5.0-gcc... cc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix... checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking how to run the C preprocessor... cc -E checking whether cc needs -traditional... no checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel checking build system type... i386-portbld-freebsd5.0 checking host system type... i386-portbld-freebsd5.0 checking for AIX... no checking for minix/config.h... no checking for POSIXized ISC... no checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for /usr/libexec/elf/ld option to reload object files... -r checking for BSD-compatible nm... nm checking whether ln -s works... yes checking how to recognise dependant libraries... pass_all checking command to parse nm output... ok checking for dlfcn.h... yes checking for i386-portbld-freebsd5.0-ranlib... no checking for ranlib... ranlib checking for i386-portbld-freebsd5.0-strip... no checking for strip... strip checking for objdir... .libs checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.lo... yes checking if cc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... freebsd5.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... yes creating libtool checking host system type... i386-unknown-freebsdelf5.0 checking for ranlib... ranlib checking whether we are using GNU C... yes checking for object suffix... o checking for executable suffix... no checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.lo... yes checking if cc supports -fno-rtti -fno-exceptions ... yes checking if cc static flag -static works... -static checking whether ln -s works... yes checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes checking for BSD-compatible nm... /usr/bin/nm -B checking command to parse /usr/bin/nm -B output... ok checking how to hardcode library paths into programs... immediate checking for /usr/libexec/elf/ld option to reload object files... -r checking dynamic linker characteristics... freebsdelf5.0 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for objdir... .libs creating libtool checking for langinfo.h... yes checking for nl_langinfo... yes checking for nl_langinfo and CODESET... yes checking whether we are using the GNU C Library 2.1 or newer... no checking for stddef.h... yes checking for stdlib.h... yes checking for string.h... yes checking for setlocale... yes configure: creating ./config.status config.status: creating Makefile config.status: creating lib/Makefile config.status: creating config.h ===> Building for libiconv-1.8_1 builddir="`pwd`"; cd libcharset && make all && make install-lib libdir="$builddir/lib" includedir="$builddir/lib" sysconfdir="$builddir/lib" if [ ! -d include ] ; then mkdir include ; fi cp ./include/libcharset.h.in include/libcharset.h cd lib && make all /bin/sh ../libtool --mode=compile cc -I. -I. -I.. -I./.. -O -pipe -march=pentium3 -DHAVE_CONFIG_H -DLIBDIR=\"/usr/local/libdata\" -c ./localcharset.c mkdir .libs cc -I. -I. -I.. -I./.. -O -pipe -march=pentium3 -DHAVE_CONFIG_H -DLIBDIR=\"/usr/local/libdata\" -c ./localcharset.c -fPIC -DPIC -o .libs/localcharset.lo cc -I. -I. -I.. -I./.. -O -pipe -march=pentium3 -DHAVE_CONFIG_H -DLIBDIR=\"/usr/local/libdata\" -c ./localcharset.c -o localcharset.o >/dev/null 2>&1 mv -f .libs/localcharset.lo localcharset.lo /bin/sh ../libtool --mode=link cc -o libcharset.la -rpath /usr/local/lib -version-info 1 -no-undefined localcharset.lo rm -fr .libs/libcharset.la .libs/libcharset.* .libs/libcharset.* cc -shared -Wl,--rpath -Wl,/usr/local/lib localcharset.lo -Wl,-soname -Wl,libcharset.so.1 -o .libs/libcharset.so.1 (cd .libs && rm -f libcharset.so && ln -sf libcharset.so.1 libcharset.so) ar cru .libs/libcharset.a localcharset.o ranlib .libs/libcharset.a creating libcharset.la (cd .libs && rm -f libcharset.la && ln -sf ../libcharset.la libcharset.la) /bin/sh ./config.charset 'i386-portbld-freebsd5.0' > t-charset.alias mv t-charset.alias charset.alias sed -e '/^#/d' -e 's/@''PACKAGE''@//g' ./ref-add.sin > t-ref-add.sed mv t-ref-add.sed ref-add.sed sed -e '/^#/d' -e 's/@''PACKAGE''@//g' ./ref-del.sin > t-ref-del.sed mv t-ref-del.sed ref-del.sed cd lib && make all cd lib && make install-lib libdir='/usr/ports/converters/libiconv/work/libiconv-1.8/lib' includedir='/usr/ports/converters/libiconv/work/libiconv-1.8/lib' sysconfdir='/usr/ports/converters/libiconv/work/libiconv-1.8/lib' /bin/sh ./../autoconf/mkinstalldirs /usr/ports/converters/libiconv/work/libiconv-1.8/lib /bin/sh ../libtool --mode=install install -C -o root -g wheel -m 444 libcharset.la /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.la install -C -o root -g wheel -m 444 .libs/libcharset.so.1 /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.so.1 (cd /usr/ports/converters/libiconv/work/libiconv-1.8/lib && rm -f libcharset.so && ln -sf libcharset.so.1 libcharset.so) install -C -o root -g wheel -m 444 .libs/libcharset.a /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.a ranlib /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.a chmod 644 /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.a libtool: install: warning: remember to run `libtool --finish /usr/local/lib' /bin/sh ./../autoconf/mkinstalldirs /usr/ports/converters/libiconv/work/libiconv-1.8/lib test -f /usr/ports/converters/libiconv/work/libiconv-1.8/lib/charset.alias && orig=/usr/ports/converters/libiconv/work/libiconv-1.8/lib/charset.alias || orig=charset.alias; sed -f ref-add.sed $orig > /usr/ports/converters/libiconv/work/libiconv-1.8/lib/t-charset.alias; install -C -o root -g wheel -m 444 /usr/ports/converters/libiconv/work/libiconv-1.8/lib/t-charset.alias /usr/ports/converters/libiconv/work/libiconv-1.8/lib/charset.alias; rm -f /usr/ports/converters/libiconv/work/libiconv-1.8/lib/t-charset.alias /bin/sh ./autoconf/mkinstalldirs /usr/ports/converters/libiconv/work/libiconv-1.8/lib install -C -o root -g wheel -m 444 include/libcharset.h /usr/ports/converters/libiconv/work/libiconv-1.8/lib/libcharset.h cd lib && make all /bin/sh ../libtool --mode=compile cc -I. -I. -I../include -I./../include -O -pipe -march=pentium3 -c ./iconv.c mkdir .libs cc -I. -I. -I../include -I./../include -O -pipe -march=pentium3 -c ./iconv.c -fPIC -DPIC -o .libs/iconv.lo In file included from gbk.h:64, from converters.h:202, from iconv.c:67: gbkext1.h: In function `gbkext1_mbtowc': gbkext1.h:852: unrecognizable insn: (insn 157 155 159 (set (reg:QI 78) (const_int 128 [0x80])) -1 (nil) (nil)) gbkext1.h:852: Internal compiler error in extract_insn, at recog.c:2150 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.8/lib. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.8. *** Error code 1 Stop in /usr/ports/converters/libiconv. --------------090202040208040202030805-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 13:21: 9 2002 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 C4CAC37B400; Wed, 11 Sep 2002 13:21:00 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 135FA43E6A; Wed, 11 Sep 2002 13:21:00 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id g8BKKbZ55774; Wed, 11 Sep 2002 10:20:37 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Wed, 11 Sep 2002 10:20:37 -1000 (HST) From: Vincent Poy To: FreeBSD-current@FreeBSD.ORG, Subject: GENERIC kernel panic on boot with latest -current Septembet 11, 2002 due to /usr/src/sys/kern/kern_acct.c v 1.49 Message-ID: <20020911101849.N2914-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Revelent info: * $FreeBSD: src/sys/kern/kern_acct.c,v 1.49 2002/09/11 04:10:41 arr Exp $ Console output... Starting syslogd. Sep 11 12:35:51 bigbang syslogd: kernel boot file is /boot/kernel/kernel Starting named. Starting ntpdate. Turning on accounting. recursed on non-recursive lock (sleep mutex) accounting @ /usr/src/sys/kern/kern_acct.c:343 first acquired @ /usr/src/sys/kern/kern_acct.c:160 panic: recurse Debugger("panic") Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 db> trace Debugger(c0434fbc) at Debugger+0x45 panic(c0438e88,0,c690f6f0,da68cb18,c02bb3ef) at panic+0x7c witness_lock(c04e9ce0,8,c0431166,157,0) at witness_lock+0x305 _mtx_lock_flags(c04e9ce0,0,c0431166,157) at _mtx_lock_flags+0x7f acctwatch(0,c04e9ca0,0,c159e200) at acctwatch+0x1f acct(c15a16c0,da68cd14,1,1,296) at acct+0x1c9 syscall(2f,2f,2f,bfbffdd0,bfbffdd4) at syscall+0x243 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (51, FreeBSD ELF32, acct), eip = 0x280a5d17, esp = 0xbfbffd6c, ebp = 0xbfbffd88 --- db> output with boot -v Starting syslogd. Sep 11 13:05:50 bigbang syslogd: kernel boot file is /boot/kernel/kernel Started named. Starting ntpdate. Turning on accounting. recursed on non-recursive lock (sleep mutex) accounting @ /usr/src/sys/kern/kern_acct.c:343 first acquired @ /usr/src/sys/kern/kern_acct.c:160 panic: recurse Debugger("panic") Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 db> Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 13:54:47 2002 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 D35A037B401 for ; Wed, 11 Sep 2002 13:54:45 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B42943E65 for ; Wed, 11 Sep 2002 13:54:45 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 22434 invoked by uid 1000); 11 Sep 2002 20:54:46 -0000 Date: Wed, 11 Sep 2002 13:54:46 -0700 (PDT) From: Nate Lawson To: Vincent Poy Cc: FreeBSD-current@FreeBSD.ORG, arr@FreeBSD.ORG Subject: Re: GENERIC kernel panic on boot with latest -current Septembet 11, 2002 due to /usr/src/sys/kern/kern_acct.c v 1.49 In-Reply-To: <20020911101849.N2914-100000@oahu.WURLDLINK.NET> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is being worked on. See msg thread in cvs-all, starting with: <200209110410.g8B4Aggt079926@freefall.freebsd.org>. You can back out the change (1.49) if you need to get running. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 11 14: 2: 2 2002 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 3218137B4E0 for ; Wed, 11 Sep 2002 14:01:04 -0700 (PDT) Received: from gioria.dyndns.org (AFontenayssB-104-1-3-39.abo.wanadoo.fr [80.11.10.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA6143E3B for ; Wed, 11 Sep 2002 14:01:01 -0700 (PDT) (envelope-from eagle@gioria.dyndns.org) Received: by gioria.dyndns.org (Postfix, from userid 42) id 1E827374B8; Wed, 11 Sep 2002 23:01:09 +0200 (CEST) Date: Wed, 11 Sep 2002 23:01:08 +0200 From: Sebastien Gioria To: current@freebsd.org Subject: reppetead crashs Message-ID: <20020911230108.A15725@thorm.gioria.dyndns.org> Reply-To: Sebastien Gioria Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Hostname: thorm.gioria.dyndns.org X-Uptime: 10:52PM up 1 day, 12 mins, 6 users, load averages: 2.69, 2.77, 2.83 X-FreeBSD-Release: FreeBSD-4.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi guys, I've got today a lot of repetead crash on my -CURRENT notebook when I do a ftp transfer. I've use ncftp3 and when it hang, I do a CTRL-Z and after this I do a "kill %%". I've under the gnome, using a current as of : eagle bushmills:~>uname -a FreeBSD bushmills.intra.thorm.net 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Tue Sep 10 20:49:42 CEST 2002 root@bushmills.intra.thorm.net:/usr/src/sys/i386/compile/bushmills i386 I'm on a Dell Inspiron 8200 with 512Mb RAM + 40Go Disk + a ATI GeForce4 64Mb + NetGear Wireless MA401 PCCard I've attached the result of the boot -v in my /var/log/message just Hope this can be usefull -- Sebastien Gioria gioria@{FreeBSD,FreeBSD-FR}.ORG French FreeBSD User Group http://www.FreeBSD-FR.ORG FreeBSD committer http://www.FreeBSD.ORG *-> FreeBSD + RollerBlade + Scuba Diving; What need you more ? <-* --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=message-bushmills Sep 11 22:13:55 bushmills syslogd: kernel boot file is /boot/kernel/kernel Sep 11 22:13:55 bushmills kernel: Copyright (c) 1992-2002 The FreeBSD Project. Sep 11 22:13:55 bushmills kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Sep 11 22:13:55 bushmills kernel: The Regents of the University of California. All rights reserved. Sep 11 22:13:55 bushmills kernel: FreeBSD 5.0-CURRENT #8: Tue Sep 10 20:49:42 CEST 2002 Sep 11 22:13:55 bushmills kernel: root@bushmills.intra.thorm.net:/usr/src/sys/i386/compile/bushmills Sep 11 22:13:55 bushmills kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xc05ce000. Sep 11 22:13:55 bushmills kernel: Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05ce0b4. Sep 11 22:13:55 bushmills kernel: Calibrating clock(s) ... TSC clock: 1595295500 Hz, i8254 clock: 1193185 Hz Sep 11 22:13:55 bushmills kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Sep 11 22:13:55 bushmills kernel: Timecounter "i8254" frequency 1193182 Hz Sep 11 22:13:55 bushmills kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Sep 11 22:13:55 bushmills kernel: Timecounter "TSC" frequency 1595301708 Hz Sep 11 22:13:55 bushmills kernel: CPU: Pentium 4 (1595.30-MHz 686-class CPU) Sep 11 22:13:55 bushmills kernel: Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Sep 11 22:13:55 bushmills kernel: Features=0x3febf9ff Sep 11 22:13:55 bushmills kernel: real memory = 536748032 (524168K bytes) Sep 11 22:13:55 bushmills kernel: Physical memory chunk(s): Sep 11 22:13:55 bushmills kernel: 0x00001000 - 0x0009efff, 647168 bytes (158 pages) Sep 11 22:13:55 bushmills kernel: 0x005f5000 - 0x1ffd9fff, 530468864 bytes (129509 pages) Sep 11 22:13:55 bushmills kernel: avail memory = 514527232 (502468K bytes) Sep 11 22:13:55 bushmills kernel: bios32: Found BIOS32 Service Directory header at 0xc00ffe80 Sep 11 22:13:55 bushmills kernel: bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 Sep 11 22:13:55 bushmills kernel: pcibios: PCI BIOS entry at 0xf0000+0xbfee Sep 11 22:13:55 bushmills kernel: pnpbios: Found PnP BIOS data at 0xc00fe2d0 Sep 11 22:13:55 bushmills kernel: pnpbios: Entry = f0000:e2f4 Rev = 1.0 Sep 11 22:13:55 bushmills kernel: pnpbios: Event flag at 4b4 Sep 11 22:13:55 bushmills kernel: Other BIOS signatures found: Sep 11 22:13:55 bushmills kernel: null: Sep 11 22:13:55 bushmills kernel: random: Sep 11 22:13:55 bushmills kernel: mem: Sep 11 22:13:55 bushmills kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x80010064 Sep 11 22:13:55 bushmills kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Sep 11 22:13:55 bushmills kernel: pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=1a308086) Sep 11 22:13:55 bushmills kernel: Using $PIR table, 11 entries at 0xc00fbb90 Sep 11 22:13:55 bushmills kernel: PCI-Only Interrupts: none Sep 11 22:13:55 bushmills kernel: Location Bus Device Pin Link IRQs Sep 11 22:13:55 bushmills kernel: embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 29 D 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 30 A 0x60 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 30 B 0x61 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 30 C 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 30 D 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 1 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 0 A 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 1 A 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 3 A 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 3 B 0x63 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 8 A 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 12 A 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 12 B 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 12 C 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 2 12 D 0x62 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 8 0 A 0x61 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: embedded 8 1 A 0x61 3 4 5 6 7 9 10 11 12 14 15 Sep 11 22:13:55 bushmills kernel: npx0: on motherboard Sep 11 22:13:55 bushmills kernel: npx0: INT 16 interface Sep 11 22:13:55 bushmills kernel: acpi0: on motherboard Sep 11 22:13:55 bushmills kernel: ACPI timer looks GOOD min = 3, max = 4, width = 2 Sep 11 22:13:55 bushmills last message repeated 9 times Sep 11 22:13:55 bushmills kernel: Timecounter "ACPI-fast" frequency 3579545 Hz Sep 11 22:13:55 bushmills kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_cpu0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_tz0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_acad0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_cmbat0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_cmbat1: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_lid0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_button0: on acpi0 Sep 11 22:13:55 bushmills kernel: acpi_button1: on acpi0 Sep 11 22:13:55 bushmills kernel: pcib1: port 0xcf8-0xcff on acpi0 Sep 11 22:13:55 bushmills kernel: pci0: on pcib1 Sep 11 22:13:55 bushmills kernel: pci0: physical bus=0 Sep 11 22:13:55 bushmills kernel: map[10]: type 3, range 32, base e8000000, size 26, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x1a30, revid=0x04 Sep 11 22:13:55 bushmills kernel: bus=0, slot=0, func=0 Sep 11 22:13:55 bushmills kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x1a31, revid=0x04 Sep 11 22:13:55 bushmills kernel: bus=0, slot=1, func=0 Sep 11 22:13:55 bushmills kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Sep 11 22:13:55 bushmills kernel: map[20]: type 4, range 32, base 0000bf80, size 5, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2482, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=29, func=0 Sep 11 22:13:55 bushmills kernel: class=0c-03-00, hdrtype=0x00, mfdev=1 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=11 Sep 11 22:13:55 bushmills kernel: map[20]: type 4, range 32, base 0000bf40, size 5, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2484, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=29, func=1 Sep 11 22:13:55 bushmills kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=b, irq=11 Sep 11 22:13:55 bushmills kernel: map[20]: type 4, range 32, base 0000bf20, size 5, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2487, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=29, func=2 Sep 11 22:13:55 bushmills kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=c, irq=11 Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2448, revid=0x42 Sep 11 22:13:55 bushmills kernel: bus=0, slot=30, func=0 Sep 11 22:13:55 bushmills kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x248c, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=31, func=0 Sep 11 22:13:55 bushmills kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Sep 11 22:13:55 bushmills kernel: map[10]: type 4, range 32, base 000001f0, size 3, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 4, range 32, base 000003f4, size 2, enabled Sep 11 22:13:55 bushmills kernel: map[18]: type 4, range 32, base 00000170, size 3, enabled Sep 11 22:13:55 bushmills kernel: map[1c]: type 4, range 32, base 00000374, size 2, enabled Sep 11 22:13:55 bushmills kernel: map[20]: type 4, range 32, base 0000bfa0, size 4, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x248a, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=31, func=1 Sep 11 22:13:55 bushmills kernel: class=01-01-8a, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=255 Sep 11 22:13:55 bushmills kernel: map[10]: type 4, range 32, base 0000d800, size 8, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 4, range 32, base 0000dc40, size 6, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2485, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=31, func=5 Sep 11 22:13:55 bushmills kernel: class=04-01-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=b, irq=11 Sep 11 22:13:55 bushmills kernel: map[10]: type 4, range 32, base 0000d400, size 8, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 4, range 32, base 0000d080, size 7, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x8086, dev=0x2486, revid=0x02 Sep 11 22:13:55 bushmills kernel: bus=0, slot=31, func=6 Sep 11 22:13:55 bushmills kernel: class=07-03-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=b, irq=11 Sep 11 22:13:55 bushmills kernel: pcib2: at device 1.0 on pci0 Sep 11 22:13:55 bushmills kernel: pcib2: secondary bus 1 Sep 11 22:13:55 bushmills kernel: pcib2: subordinate bus 1 Sep 11 22:13:55 bushmills kernel: pcib2: I/O decode 0xc000-0xcfff Sep 11 22:13:55 bushmills kernel: pcib2: memory decode 0xfc000000-0xfdffffff Sep 11 22:13:55 bushmills kernel: pcib2: prefetched decode 0xd8000000-0xe7ffffff Sep 11 22:13:55 bushmills kernel: pci1: on pcib2 Sep 11 22:13:55 bushmills kernel: pci1: physical bus=1 Sep 11 22:13:55 bushmills kernel: map[10]: type 1, range 32, base fc000000, size 24, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 3, range 32, base e0000000, size 27, enabled Sep 11 22:13:55 bushmills kernel: map[18]: type 3, range 32, base dff80000, size 19, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x10de, dev=0x0174, revid=0xa3 Sep 11 22:13:55 bushmills kernel: bus=1, slot=0, func=0 Sep 11 22:13:55 bushmills kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=11 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D3 current D0 Sep 11 22:13:55 bushmills kernel: pci1: at device 0.0 (no driver attached) Sep 11 22:13:55 bushmills kernel: uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 Sep 11 22:13:55 bushmills kernel: usb0: on uhci0 Sep 11 22:13:55 bushmills kernel: usb0: USB revision 1.0 Sep 11 22:13:55 bushmills kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Sep 11 22:13:55 bushmills kernel: uhub0: 2 ports with 2 removable, self powered Sep 11 22:13:55 bushmills kernel: uhci1: port 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 Sep 11 22:13:55 bushmills kernel: usb1: on uhci1 Sep 11 22:13:55 bushmills kernel: usb1: USB revision 1.0 Sep 11 22:13:55 bushmills kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Sep 11 22:13:55 bushmills kernel: uhub1: 2 ports with 2 removable, self powered Sep 11 22:13:55 bushmills kernel: uhci2: port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 Sep 11 22:13:55 bushmills kernel: usb2: on uhci2 Sep 11 22:13:55 bushmills kernel: usb2: USB revision 1.0 Sep 11 22:13:55 bushmills kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Sep 11 22:13:55 bushmills kernel: uhub2: 2 ports with 2 removable, self powered Sep 11 22:13:55 bushmills kernel: pcib3: at device 30.0 on pci0 Sep 11 22:13:55 bushmills kernel: pcib3: secondary bus 2 Sep 11 22:13:55 bushmills kernel: pcib3: subordinate bus 16 Sep 11 22:13:55 bushmills kernel: pcib3: I/O decode 0xe000-0xffff Sep 11 22:13:55 bushmills kernel: pcib3: memory decode 0xf4000000-0xfbffffff Sep 11 22:13:55 bushmills kernel: pcib3: prefetched decode 0xfff00000-0xfffff Sep 11 22:13:55 bushmills kernel: pci2: on pcib3 Sep 11 22:13:55 bushmills kernel: pci2: physical bus=2 Sep 11 22:13:55 bushmills kernel: map[10]: type 4, range 32, base 0000ec80, size 7, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 1, range 32, base f8fffc00, size 7, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x10b7, dev=0x9200, revid=0x78 Sep 11 22:13:55 bushmills kernel: bus=2, slot=0, func=0 Sep 11 22:13:55 bushmills kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=11 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Sep 11 22:13:55 bushmills kernel: found-> vendor=0x104c, dev=0xac42, revid=0x00 Sep 11 22:13:55 bushmills kernel: bus=2, slot=1, func=0 Sep 11 22:13:55 bushmills kernel: class=06-07-00, hdrtype=0x02, mfdev=1 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=255 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Sep 11 22:13:55 bushmills kernel: found-> vendor=0x104c, dev=0xac42, revid=0x00 Sep 11 22:13:55 bushmills kernel: bus=2, slot=1, func=1 Sep 11 22:13:55 bushmills kernel: class=06-07-00, hdrtype=0x02, mfdev=1 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=255 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Sep 11 22:13:55 bushmills kernel: map[10]: type 1, range 32, base f8fff000, size 11, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 1, range 32, base f8ff8000, size 14, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x104c, dev=0x8027, revid=0x00 Sep 11 22:13:55 bushmills kernel: bus=2, slot=1, func=2 Sep 11 22:13:55 bushmills kernel: class=0c-00-10, hdrtype=0x00, mfdev=1 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=11 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D2 D3 current D0 Sep 11 22:13:55 bushmills kernel: map[10]: type 4, range 32, base 0000ec00, size 7, enabled Sep 11 22:13:55 bushmills kernel: map[14]: type 1, range 32, base f8fff800, size 7, enabled Sep 11 22:13:55 bushmills kernel: found-> vendor=0x10b7, dev=0x9200, revid=0x78 Sep 11 22:13:55 bushmills kernel: bus=2, slot=8, func=0 Sep 11 22:13:55 bushmills kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Sep 11 22:13:55 bushmills kernel: intpin=a, irq=11 Sep 11 22:13:55 bushmills kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Sep 11 22:13:55 bushmills kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2 Sep 11 22:13:55 bushmills kernel: pcib3: device xl0 requested decoded I/O range 0xec80-0xecff Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "xl0" locked from ../../../pci/if_xl.c:1281 Sep 11 22:13:55 bushmills kernel: xl0: Ethernet address: 00:06:5b:b8:dc:4e Sep 11 22:13:55 bushmills kernel: xl0: media options word: a Sep 11 22:13:55 bushmills kernel: xl0: found MII/AUTO Sep 11 22:13:55 bushmills kernel: miibus0: on xl0 Sep 11 22:13:55 bushmills kernel: ukphy0: on miibus0 Sep 11 22:13:55 bushmills kernel: ukphy0: OUI 0x00105a, model 0x0000, rev. 0 Sep 11 22:13:55 bushmills kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "xl0" locked from ../../../pci/if_xl.c:664 Sep 11 22:13:55 bushmills kernel: bpf: xl0 attached Sep 11 22:13:55 bushmills kernel: pcib3: matched entry for 2.1.INTA (source \_SB_.PCI0.LNKD) Sep 11 22:13:55 bushmills kernel: pcib3: slot 1 INTA is routed to irq 11 Sep 11 22:13:55 bushmills kernel: pcic0: irq 11 at device 1.0 on pci2 Sep 11 22:13:55 bushmills kernel: pcib3: device pcic0 requested decoded memory range 0xf4000000-0xfbffffff Sep 11 22:13:55 bushmills kernel: pcic0: PCI Memory allocated: 0xf4000000 Sep 11 22:13:55 bushmills kernel: pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][CSC serial isa irq] Sep 11 22:13:55 bushmills kernel: pcic0: PCI Configuration space: Sep 11 22:13:55 bushmills kernel: 0x00: 0xac42104c 0x02100003 0x06070000 0x00822008 Sep 11 22:13:55 bushmills kernel: 0x10: 0xf4000000 0x020000a0 0x20040400 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x20: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x30: 0x00000000 0x00000000 0x00000000 0x0760010b Sep 11 22:13:55 bushmills kernel: 0x40: 0x00d41028 0x00000001 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x80: 0x3024d021 0x00000600 0x000f0000 0x05033002 Sep 11 22:13:55 bushmills kernel: 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xa0: 0xfe120001 0x00c00000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: pccard0: on pcic0 Sep 11 22:13:55 bushmills kernel: pcib3: matched entry for 2.1.INTA (source \_SB_.PCI0.LNKD) Sep 11 22:13:55 bushmills kernel: pcib3: slot 1 INTA is routed to irq 11 Sep 11 22:13:55 bushmills kernel: pcic1: irq 11 at device 1.1 on pci2 Sep 11 22:13:55 bushmills kernel: pcib3: device pcic1 requested decoded memory range 0xf4000000-0xfbffffff Sep 11 22:13:55 bushmills kernel: pcic1: PCI Memory allocated: 0xf4001000 Sep 11 22:13:55 bushmills kernel: pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][CSC serial isa irq] Sep 11 22:13:55 bushmills kernel: pcic1: PCI Configuration space: Sep 11 22:13:55 bushmills kernel: 0x00: 0xac42104c 0x02100003 0x06070000 0x00822008 Sep 11 22:13:55 bushmills kernel: 0x10: 0xf4001000 0x020000a0 0x20050500 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x20: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x30: 0x00000000 0x00000000 0x00000000 0x0760010b Sep 11 22:13:55 bushmills kernel: 0x40: 0x00d41028 0x00000001 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0x80: 0x3024d021 0x00000600 0x000f0000 0x05033002 Sep 11 22:13:55 bushmills kernel: 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xa0: 0xfe120001 0x00c00000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 Sep 11 22:13:55 bushmills kernel: pccard1: on pcic1 Sep 11 22:13:55 bushmills kernel: pci2: at device 1.2 (no driver attached) Sep 11 22:13:55 bushmills kernel: xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xf8fff800-0xf8fff87f irq 11 at device 8.0 on pci2 Sep 11 22:13:55 bushmills kernel: pcib3: device xl1 requested decoded I/O range 0xec00-0xec7f Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "xl1" locked from ../../../pci/if_xl.c:1281 Sep 11 22:13:55 bushmills kernel: xl1: Ethernet address: 00:06:5b:e8:38:c2 Sep 11 22:13:55 bushmills kernel: xl1: media options word: a Sep 11 22:13:55 bushmills kernel: xl1: found MII/AUTO Sep 11 22:13:55 bushmills kernel: miibus1: on xl1 Sep 11 22:13:55 bushmills kernel: ukphy1: on miibus1 Sep 11 22:13:55 bushmills kernel: ukphy1: OUI 0x00105a, model 0x0000, rev. 0 Sep 11 22:13:55 bushmills kernel: ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "xl1" locked from ../../../pci/if_xl.c:664 Sep 11 22:13:55 bushmills kernel: bpf: xl1 attached Sep 11 22:13:55 bushmills kernel: isab0: at device 31.0 on pci0 Sep 11 22:13:55 bushmills kernel: isa0: on isab0 Sep 11 22:13:55 bushmills kernel: atapci0: port 0xbfa0-0xbfaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 Sep 11 22:13:55 bushmills kernel: ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xbfa0 Sep 11 22:13:55 bushmills kernel: ata0: mask=03 ostat0=50 ostat2=00 Sep 11 22:13:55 bushmills kernel: ata0-master: ATAPI 00 00 Sep 11 22:13:55 bushmills kernel: ata0-slave: ATAPI 14 eb Sep 11 22:13:55 bushmills kernel: ata0: mask=03 stat0=50 stat1=00 Sep 11 22:13:55 bushmills kernel: ata0-master: ATA 01 a5 Sep 11 22:13:55 bushmills kernel: ata0: devices=09 Sep 11 22:13:55 bushmills kernel: ata0: at 0x1f0 irq 14 on atapci0 Sep 11 22:13:55 bushmills kernel: ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xbfa8 Sep 11 22:13:55 bushmills kernel: ata1: mask=03 ostat0=00 ostat2=00 Sep 11 22:13:55 bushmills kernel: ata1-master: ATAPI 00 00 Sep 11 22:13:55 bushmills kernel: ata1-slave: ATAPI 00 00 Sep 11 22:13:55 bushmills kernel: ata1: mask=03 stat0=00 stat1=00 Sep 11 22:13:55 bushmills kernel: ata1: devices=00 Sep 11 22:13:55 bushmills kernel: ata1: at 0x170 irq 15 on atapci0 Sep 11 22:13:55 bushmills kernel: pcm0: port 0xdc40-0xdc7f,0xd800-0xd8ff irq 11 at device 31.5 on pci0 Sep 11 22:13:55 bushmills kernel: pcm0: ac97 codec id 0x4352595b Sep 11 22:13:55 bushmills kernel: pcm0: ac97 codec features mic channel, tone, simulated stereo, bass boost, 20 bit DAC, 18 bit ADC, 5 bit master volume, SRS 3D Stereo Enhancement Sep 11 22:13:55 bushmills kernel: pcm0: ac97 primary codec extended features variable rate PCM, variable rate mic, AMAP Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills last message repeated 2 times Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:fake" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:fake" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:fake" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:fake" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills last message repeated 13 times Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills last message repeated 2 times Sep 11 22:13:55 bushmills kernel: pcm0: sndbuf_setmap 7ab000, 4000; 0xd7bbf000 -> 7ab000 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:record:0" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills last message repeated 2 times Sep 11 22:13:55 bushmills kernel: pcm0: sndbuf_setmap 7af000, 4000; 0xd7bc3000 -> 7af000 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:record:0" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:record:1" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills last message repeated 2 times Sep 11 22:13:55 bushmills kernel: pcm0: sndbuf_setmap 7b3000, 4000; 0xd7bc7000 -> 7b3000 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0:record:1" locked from ../../../dev/sound/pcm/channel.c:677 Sep 11 22:13:55 bushmills kernel: ../../../vm/uma_core.c:1332: could sleep with "pcm0" locked from ../../../dev/sound/pcm/sound.c:134 Sep 11 22:13:55 bushmills last message repeated 2 times Sep 11 22:13:55 bushmills kernel: pci0: at device 31.6 (no driver attached) Sep 11 22:13:55 bushmills kernel: unknown: not probed (disabled) Sep 11 22:13:55 bushmills kernel: unknown: not probed (disabled) Sep 11 22:13:55 bushmills kernel: psmcpnp0 irq 12 on acpi0 Sep 11 22:13:55 bushmills kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Sep 11 22:13:55 bushmills kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Sep 11 22:13:55 bushmills kernel: atkbd: the current kbd controller command byte 0065 Sep 11 22:13:55 bushmills kernel: atkbd: keyboard ID 0x41ab (2) Sep 11 22:13:55 bushmills kernel: kbd0 at atkbd0 Sep 11 22:13:55 bushmills kernel: kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 Sep 11 22:13:55 bushmills kernel: psm0: current command byte:0065 Sep 11 22:13:55 bushmills kernel: psm0: irq 12 on atkbdc0 Sep 11 22:13:55 bushmills kernel: psm0: model IntelliMouse, device ID 3-00, 3 buttons Sep 11 22:13:55 bushmills kernel: psm0: config:00000000, flags:00000000, packet size:4 Sep 11 22:13:55 bushmills kernel: psm0: syncmask:08, syncbits:08 Sep 11 22:13:55 bushmills kernel: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 Sep 11 22:13:55 bushmills kernel: fdc0: FIFO enabled, 8 bytes threshold Sep 11 22:13:55 bushmills kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Sep 11 22:13:55 bushmills kernel: sio0: irq maps: 0x801 0x811 0x801 0x801 Sep 11 22:13:55 bushmills kernel: sio0 port 0x3f8-0x3ff irq 4 on acpi0 Sep 11 22:13:55 bushmills kernel: sio0: type 16550A Sep 11 22:13:55 bushmills kernel: unknown: not probed (disabled) Sep 11 22:13:55 bushmills kernel: ppc0: using extended I/O port range Sep 11 22:13:55 bushmills kernel: ppc0: ECP SPP ECP+EPP SPP Sep 11 22:13:55 bushmills kernel: ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 Sep 11 22:13:55 bushmills kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Sep 11 22:13:55 bushmills kernel: ppc0: FIFO with 16/16/8 bytes threshold Sep 11 22:13:55 bushmills kernel: plip0: on ppbus0 Sep 11 22:13:55 bushmills kernel: bpf: lp0 attached Sep 11 22:13:55 bushmills kernel: lpt0: on ppbus0 Sep 11 22:13:55 bushmills kernel: lpt0: Interrupt-driven port Sep 11 22:13:55 bushmills kernel: ppi0: on ppbus0 Sep 11 22:13:55 bushmills kernel: unknown: not probed (disabled) Sep 11 22:13:55 bushmills last message repeated 6 times Sep 11 22:13:55 bushmills kernel: ata: ata0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: ata: ata1 already exists; skipping it Sep 11 22:13:55 bushmills kernel: atkbdc: atkbdc0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: fdc: fdc0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: pcic: pcic0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: pcic: pcic1 already exists; skipping it Sep 11 22:13:55 bushmills kernel: ppc: ppc0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: sio: sio0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 203 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 243 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 283 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 2c3 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 303 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 343 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 383 Sep 11 22:13:55 bushmills kernel: Trying Read_Port at 3c3 Sep 11 22:13:55 bushmills kernel: sc: sc0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: vga: vga0 already exists; skipping it Sep 11 22:13:55 bushmills kernel: isa_probe_children: disabling PnP devices Sep 11 22:13:55 bushmills kernel: isa_probe_children: probing non-PnP devices Sep 11 22:13:55 bushmills kernel: orm0: