From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 00:04:14 2004 Return-Path: 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 2105916A4CE for ; Sun, 3 Oct 2004 00:04:14 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C072743D2D for ; Sun, 3 Oct 2004 00:04:13 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i9304D58033620; Sat, 2 Oct 2004 20:04:13 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i9304APP033619; Sat, 2 Oct 2004 20:04:10 -0400 (EDT) (envelope-from afields) Date: Sat, 2 Oct 2004 20:04:10 -0400 From: Allan Fields To: Hannes Mehnert Message-ID: <20041003000410.GF28121@afields.ca> References: <20041002190838.GA8104@mehnert.org> <20041002205034.GC28121@afields.ca> <20041002211430.GC8104@mehnert.org> <20041002231723.GA700@mehnert.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041002231723.GA700@mehnert.org> User-Agent: Mutt/1.4i cc: phk@phk.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: file system recovery [gbde] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 00:04:14 -0000 On Sun, Oct 03, 2004 at 01:17:23AM +0200, Hannes Mehnert wrote: > On Sat, Oct 02, 2004 at 11:14:30PM +0200, Hannes Mehnert wrote: > > > > I downgraded to -CURRENT from 20040915, but it was also not able > > > > to run fsck. > > > > > > Did you rebuild and install modules? g_bde can be loaded as a module > > > when you run gbde(8) command. > > > > Yes, I'll downgrade to before phks commit and try again. > > Ok, downgraded to 20040910 (phks commit was on Sep 11 to -current). > Didn't work. If you have any other ideas how to fix this, please mail > them. What didn't work in specific? You were able to reattach but the filesystem doesn't check out? If so, try recovering from the image you made. I'm not sure if in doing the fsck it might have changed the structure of the underlying gbde device (upon writing to it). > Best Regards, > > Hannes Mehnert -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 00:15:01 2004 Return-Path: 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 3F39A16A4CE for ; Sun, 3 Oct 2004 00:15:01 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF9D43D2D for ; Sun, 3 Oct 2004 00:15:00 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CDu1j-0001Rk-00; Sun, 03 Oct 2004 02:14:59 +0200 Received: from [217.227.153.30] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CDu1i-0006DB-00; Sun, 03 Oct 2004 02:14:59 +0200 From: Max Laier To: freebsd-current@freebsd.org Date: Sun, 3 Oct 2004 02:14:06 +0200 User-Agent: KMail/1.7 References: <200409272240.00356.A.S.Usov@kvi.nl> <200410012101.01067.max@love2party.net> <200410021858.35419.A.S.Usov@kvi.nl> In-Reply-To: <200410021858.35419.A.S.Usov@kvi.nl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2886916.6Y4RbX6Be8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410030214.14718.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: "Alexander S. Usov" Subject: Re: ALTQ/pf troubles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 00:15:01 -0000 --nextPart2886916.6Y4RbX6Be8 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 02 October 2004 18:58, Alexander S. Usov wrote: > On Friday 01 October 2004 21:00, Max Laier wrote: > > First of all a look at your queue statistics would be helpful: > > $ pfctl -vvsq > > how many packets are being dropped? Which queues do the packets end up > > in? > > > > If you can easily check OpenBSD behavior, that'd be a good check as wel= l. > > Ok. Today I downloaded and installed OpenBSD 3.6-snapshot (it's a centrino > notebook and I wanted to be sure that it will be supported). > Should say that their installer is quite fun, but console and csh are too > old-fashioned. > > So the result is like this: > $ ifconfig bce0 > bce0: flags=3D8a43 mtu 1= 500 > address: 00:c0:9f:1c:1b:8b > media: Ethernet autoselect (100baseTX full-duplex) > status: active > inet6 fe80::2c0:9fff:fe1c:1b8b%bce0 prefixlen 64 scopeid 0x1 > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > > pf.conf is the same, as used in FreeBSD, just bfe0 renamed to bce0 > > without queueing transfer speed is about 35-40KB/s > $ netstat 3 > lo0 in lo0 out total in total out > packets errs packets errs colls packets errs packets errs colls > 2 0 2 0 0 10256 0 12381 0 0 > 0 0 0 0 0 56 0 81 0 0 > > For queue bandwidth 350Kb > $ pfctl -vvsq > queue q priq( default ) > [ pkts: 3646 bytes: 5379512 dropped pkts: 0 bytes: = 0 > ] [ qlength: 0/ 50 ] > [ measured: 26.4 packets/s, 312.48Kb/s ] > > $ netstat 3 > lo0 in lo0 out total in total out > packets errs packets errs colls packets errs packets errs colls > 2 0 2 0 0 13924 0 17688 0 0 > 0 0 0 0 0 54 0 78 0 0 > 0 0 0 0 0 56 0 81 0 0 > > which is correct. > So it's defenitely something is wrong in FreeBSD. > I suspect this is somehow related to bfe driver, as on a different machine > the same system (rsync copy up to the few files in /etc & /var) with the > same configuration but xl card works correctly. Okay. Thank you for the information and hunting. Can you please turn this i= nto=20 a PR? Thanks in advance. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2886916.6Y4RbX6Be8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBX0RWXyyEoT62BG0RAkW6AJ0Woaw+OAx2CKfv/CJuhnGfaVAe1QCdHBMO L7+Fp0f/B8CU3RK87es7Zyg= =5vm2 -----END PGP SIGNATURE----- --nextPart2886916.6Y4RbX6Be8-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 00:37:14 2004 Return-Path: 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 BD6F816A4E8 for ; Sun, 3 Oct 2004 00:37:14 +0000 (GMT) Received: from beagle2.mehnert.org (beagle2.mehnert.org [212.42.235.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2060443D4C for ; Sun, 3 Oct 2004 00:37:14 +0000 (GMT) (envelope-from hannes@mehnert.org) Received: from localhost (port-212-202-198-15.dynamic.qsc.de [212.202.198.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Hannes Mehnert", Issuer "mehnert root CA" (verified OK)) by beagle2.mehnert.org (Postfix) with ESMTP id 71B5D9585D; Sun, 3 Oct 2004 02:37:12 +0200 (CEST) Date: Sun, 3 Oct 2004 02:37:10 +0200 From: Hannes Mehnert To: Allan Fields Message-ID: <20041003003710.GB700@mehnert.org> References: <20041002190838.GA8104@mehnert.org> <20041002205034.GC28121@afields.ca> <20041002211430.GC8104@mehnert.org> <20041002231723.GA700@mehnert.org> <20041003000410.GF28121@afields.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041003000410.GF28121@afields.ca> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: file system recovery [gbde] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 00:37:14 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Oct 02, 2004 at 08:04:10PM -0400, Allan Fields wrote: > What didn't work in specific? You were able to reattach but the > filesystem doesn't check out? Yes, I can attach the bde device (and see a /dev/ad0s2f.bde). fsck still returns with 'fsck_ufs: cannot alloc 1314140572 bytes for inoinfo'. The only difference I can see is that dumpfs doesn't segfault at the first cylinder group, but at the fourth cylinder group (0,1,2 and 3 seem to have valid (non-negative) data. > If so, try recovering from the image you made. I made the backup after I booted the new kernel (and after it froze while being mounted). It doesn't make any difference when I use the backup (same errors). Best Regards, Hannes Mehnert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBX0mzRcuNlziBjRwRArtlAJ95Ze69pP7PEgJKWyhUAT/BgyDCtQCghaX6 BMeKbnaZmIzDHeucl/T/YEA= =s0oB -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 00:46:04 2004 Return-Path: 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 A96C516A4CE for ; Sun, 3 Oct 2004 00:46:04 +0000 (GMT) Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7059543D1F for ; Sun, 3 Oct 2004 00:46:04 +0000 (GMT) (envelope-from freebsd@akruijff.dds.nl) Received: from kruij557.speed.planet.nl (ipd50a97ba.speed.planet.nl [213.10.151.186]) by smtp14.wxs.nl (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I4Z00BW4GSRCS@smtp14.wxs.nl> for freebsd-current@freebsd.org; Sun, 03 Oct 2004 02:46:03 +0200 (CEST) Received: from alex.lan (localhost [127.0.0.1]) by kruij557.speed.planet.nl (8.12.10/8.12.10) with ESMTP id i930k2sS019383; Sun, 03 Oct 2004 02:46:03 +0200 Received: (from akruijff@localhost) by alex.lan (8.12.10/8.12.10/Submit) id i930k2Pi019382; Sun, 03 Oct 2004 02:46:02 +0200 Content-return: prohibited Date: Sun, 03 Oct 2004 02:46:02 +0200 From: Alex de Kruijff In-reply-to: <415D71FF.6040805@tele2.it> To: Esaltato Message-id: <20041003004602.GC1111@alex.lan> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4.2.1i References: <415D71FF.6040805@tele2.it> X-Authentication-warning: alex.lan: akruijff set sender to freebsd@akruijff.dds.nl using -f cc: freebsd-current@freebsd.org Subject: Re: upgrading: 5.2.1 to 5.3 OR a new 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 00:46:04 -0000 On Fri, Oct 01, 2004 at 05:04:31PM +0200, Esaltato wrote: > Hello. What is your general opinion on upgrading FreeBSD installations? > I ask this since 5.3 is close and I'm gonna move to a new hd, but I > don't know whether is more wise to move my existing beloved 5.2.1 > install or to start anew. > Reinstalling has it pros like deleting all the possible junk. But being > FreeBSD a very polished filesystem furnished OS, I think it might be > safe to convert my 5.2.1 to 5.3 without inheriting too much junk. > Are there any cons? Maybe the new tecnhology may leave unexpected > problems pending against the old one? > I must say I'm really in favour of a new install, but thinking to the > many customizations and mods I've done and to the time it could take to > redo them... > Obviously i would take my conf. files with me, upgrading them when > necessary. > Opinions? Stay with 5.2.1 plus patches for now. 5.3 is still BETA afther this comes the candidate releases (RC) and afhter this the acual release 5.3. Afther this comes patches and err_data. -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/FreeBSD/ From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 01:10:15 2004 Return-Path: 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 CD4C816A4CE for ; Sun, 3 Oct 2004 01:10:15 +0000 (GMT) Received: from beagle2.mehnert.org (beagle2.mehnert.org [212.42.235.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E56E43D1F for ; Sun, 3 Oct 2004 01:10:15 +0000 (GMT) (envelope-from hannes@mehnert.org) Received: from localhost (port-212-202-198-15.dynamic.qsc.de [212.202.198.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Hannes Mehnert", Issuer "mehnert root CA" (verified OK)) by beagle2.mehnert.org (Postfix) with ESMTP id C0F5E9585D; Sun, 3 Oct 2004 03:10:13 +0200 (CEST) Date: Sun, 3 Oct 2004 03:10:09 +0200 From: Hannes Mehnert To: Allan Fields Message-ID: <20041003011009.GA958@mehnert.org> References: <20041002190838.GA8104@mehnert.org> <20041002205034.GC28121@afields.ca> <20041002211430.GC8104@mehnert.org> <20041002231723.GA700@mehnert.org> <20041003000410.GF28121@afields.ca> <20041003003710.GB700@mehnert.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041003003710.GB700@mehnert.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: file system recovery [gbde] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 01:10:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Oct 03, 2004 at 02:37:10AM +0200, Hannes Mehnert wrote: > The only difference I can see is that dumpfs doesn't segfault at > the first cylinder group, but at the fourth cylinder group (0,1,2 > and 3 seem to have valid (non-negative) data. Actually, all but cylinder group 5 have valid data. Are there any tools around to edit cylinder group block data? Best Regards, Hannes Mehnert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBX1FvRcuNlziBjRwRAmheAKDBYm7t+gC8nRB1rEk8fkl9crOUKwCaAq5K vrO0n1tj72XrO8wQQhw4Xow= =Js8U -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 01:35:00 2004 Return-Path: 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 30E9016A4CE for ; Sun, 3 Oct 2004 01:35:00 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B99B143D3F for ; Sun, 3 Oct 2004 01:34:59 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i931Xmas069329; Sat, 2 Oct 2004 19:33:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 02 Oct 2004 19:35:17 -0600 (MDT) Message-Id: <20041002.193517.46314784.imp@bsdimp.com> To: vova@fbsd.ru From: "M. Warner Losh" In-Reply-To: <1096620622.907.16.camel@localhost> References: <415C59C7.7090408@pythonemproject.com> <1096620622.907.16.camel@localhost> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: rob@pythonemproject.com cc: freebsd-current@freebsd.org Subject: Re: wifi on 5.3, sort of OT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 01:35:00 -0000 In message: <1096620622.907.16.camel@localhost> Vladimir Grebenschikov writes: : cbb0: mem 0xd0201000-0xd0201fff irq 9 at : device 5.0 on pci2 : cardbus0: on cbb0 : cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff : cbb_power: 0V : : Not sure is it related or not. I've seen this, but never with a cardbus bridge on pci2... status = 0xfffffff is pretty bogus. Warner From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 01:43:56 2004 Return-Path: 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 539C916A4CE for ; Sun, 3 Oct 2004 01:43:56 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F02F443D31 for ; Sun, 3 Oct 2004 01:43:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i931hHHN069411; Sat, 2 Oct 2004 19:43:20 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 02 Oct 2004 19:44:45 -0600 (MDT) Message-Id: <20041002.194445.93451101.imp@bsdimp.com> To: kris@obsecurity.org From: "M. Warner Losh" In-Reply-To: <20041001163250.GA71766@xor.obsecurity.org> References: <20041001163250.GA71766@xor.obsecurity.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: phk@phk.freebsd.dk cc: freebsd-current@freebsd.org cc: daniel_k_eriksson@msn.com Subject: Re: zero and null regression? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 01:43:57 -0000 In message: <20041001163250.GA71766@xor.obsecurity.org> Kris Kennaway writes: : On Fri, Oct 01, 2004 at 05:02:58AM +0000, Daniel Eriksson wrote: : > After upgrading a 6-CURRENT machine from a 5 day old kernel to one cvsuped : > just a few hours ago, special files zero and null created through mknod no : > longer works. : > : > # mknod zerotest c 2 12 : > # chmod 666 zerotest : > # cat zerotest > /dev/null : > cat: zerotest: Socket operation on non-socket : > : > Could this be related to the vfs stuff Poul-Henning Kamp is working with? : : I'm pretty sure this is by design - see phk's commits and related : discussion. Use devfs for device nodes. This is inconvenient when you have a chroot that you use to build products in that isn't a jail... Not impossible to work around, just very inconvenient :-( Warner From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 01:47:07 2004 Return-Path: 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 E3C4816A4CE for ; Sun, 3 Oct 2004 01:47:07 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77A5E43D1D for ; Sun, 3 Oct 2004 01:47:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i931hkQt069412; Sat, 2 Oct 2004 19:43:54 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 02 Oct 2004 19:45:15 -0600 (MDT) Message-Id: <20041002.194515.99052407.imp@bsdimp.com> To: dgilbert@dclg.ca From: "M. Warner Losh" In-Reply-To: <16733.37521.568515.842497@canoe.dclg.ca> References: <16733.37521.568515.842497@canoe.dclg.ca> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: USB hub issue adendum. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 01:47:08 -0000 In message: <16733.37521.568515.842497@canoe.dclg.ca> David Gilbert writes: : I've had the USB hub issue bite be on and off for awhile now. It : appears to be completely random corruption because moving from BETA3 : to BETA6 fixed it (for now) for me. Does BETA7 fix the problems for you? Warner From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 01:53:15 2004 Return-Path: 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 6150916A4CE for ; Sun, 3 Oct 2004 01:53:15 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26DA843D2F for ; Sun, 3 Oct 2004 01:53:15 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i931rEAv033912; Sat, 2 Oct 2004 21:53:14 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i931rEdW033911; Sat, 2 Oct 2004 21:53:14 -0400 (EDT) (envelope-from afields) Date: Sat, 2 Oct 2004 21:53:14 -0400 From: Allan Fields To: Hannes Mehnert Message-ID: <20041003015313.GG28121@afields.ca> References: <20041002190838.GA8104@mehnert.org> <20041002205034.GC28121@afields.ca> <20041002211430.GC8104@mehnert.org> <20041002231723.GA700@mehnert.org> <20041003000410.GF28121@afields.ca> <20041003003710.GB700@mehnert.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041003003710.GB700@mehnert.org> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: file system recovery [gbde] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 01:53:15 -0000 On Sun, Oct 03, 2004 at 02:37:10AM +0200, Hannes Mehnert wrote: > I made the backup after I booted the new kernel (and after it froze > while being mounted). It doesn't make any difference when I use the > backup (same errors). Right, in which case it's the equivalent as if part of your disk was randomly overwritten/corrupt in certain areas because you likely had some writes going over parts of the disk which were used by other files and metadata when it was first mounted and written to. I think your recovery angle is a good approach w/ the older kernel. > Best Regards, > > Hannes Mehnert -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 02:21:49 2004 Return-Path: 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 3B93F16A4CE for ; Sun, 3 Oct 2004 02:21:49 +0000 (GMT) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D5FA43D1D for ; Sun, 3 Oct 2004 02:21:49 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) ESMTP id i932Lk3l023040; Sat, 2 Oct 2004 19:21:48 -0700 Received: from yggdrasil.seektruth.org (c-24-18-235-11.client.comcast.net [24.18.235.11]) (authenticated bits=0)i932Lj5X029180 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 2 Oct 2004 19:21:45 -0700 From: David Syphers To: freebsd-current@freebsd.org Date: Sat, 2 Oct 2004 19:22:16 -0700 User-Agent: KMail/1.7 References: <415D71FF.6040805@tele2.it> In-Reply-To: <415D71FF.6040805@tele2.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410021922.16505.dsyphers@u.washington.edu> cc: Esaltato Subject: Re: upgrading: 5.2.1 to 5.3 OR a new 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 02:21:49 -0000 On Friday 01 October 2004 08:04 am, Esaltato wrote: > Hello. What is your general opinion on upgrading FreeBSD installations? > I ask this since 5.3 is close and I'm gonna move to a new hd, but I > don't know whether is more wise to move my existing beloved 5.2.1 > install or to start anew. > Reinstalling has it pros like deleting all the possible junk. But being > FreeBSD a very polished filesystem furnished OS, I think it might be > safe to convert my 5.2.1 to 5.3 without inheriting too much junk. > Are there any cons? Maybe the new tecnhology may leave unexpected > problems pending against the old one? > I must say I'm really in favour of a new install, but thinking to the > many customizations and mods I've done and to the time it could take to > redo them... > Obviously i would take my conf. files with me, upgrading them when > necessary. > Opinions? I'd recommend a reinstall. There have been several changes since 5.2.1 that require ports to be rebuilt - new perl, new gcc, incompatible library changes - so you'd have to rebuild all your ports anyway. It does take a little while to get everything back the way you want it again (I just did a reinstall myself). But there's something nice about having a clean system. -David From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 04:47:50 2004 Return-Path: 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 48EAA16A4CE; Sun, 3 Oct 2004 04:47:50 +0000 (GMT) Received: from blue.host.is (blue.host.is [212.30.222.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E0943D39; Sun, 3 Oct 2004 04:47:49 +0000 (GMT) (envelope-from martin@swift.is) Received: by blue.host.is (Postfix, from userid 1001) id CE3AC1C8; Sun, 3 Oct 2004 04:47:46 +0000 (GMT) Date: Sun, 3 Oct 2004 04:47:46 +0000 From: Martin Swift To: John Baldwin Message-ID: <20041003044746.GA6694@swift.is> References: <20040921183041.GD10593@swift.is> <20040922081623.GA19645@swift.is> <200409221616.54982.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409221616.54982.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@FreeBSD.org Subject: Re: BETA5 hangs shortly after boot. Unknown cause. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 04:47:50 -0000 [Sorry about the delay, fell ill] On Wed, Sep 22, 2004 at 04:16:54PM -0400, John Baldwin wrote: > On Wednesday 22 September 2004 04:16 am, Martin Swift wrote: > > Using the debug option in the boot menu gives (hand transcript): > > > > ---------- > > Fatal trap 12: page fault while in kernel mode > > fault virual address = 0x0 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc057c368 > > This matters. If you have a kernel.debug, can you do a gdb against it and do > 'l *0xc057c368'? Don't know if I do, can't get that far, machine locks up too fast :-(. Gonna give BETA6 a try. Thanks and sorry I couldn't be of more help, Martin Swift From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 07:00:49 2004 Return-Path: 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 4FA5D16A4CE for ; Sun, 3 Oct 2004 07:00:49 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E58043D54 for ; Sun, 3 Oct 2004 07:00:48 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CE0ML-0006i4-00 for ; Sun, 03 Oct 2004 09:00:41 +0200 Received: from future-is.orange.co.uk ([193.35.129.169]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Oct 2004 09:00:41 +0200 Received: from matth by future-is.orange.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Oct 2004 09:00:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Matt Hamilton Date: Sun, 03 Oct 2004 07:41:08 +0100 Lines: 41 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: future-is.orange.co.uk User-Agent: Mozilla Thunderbird 0.7.3 (Macintosh/20040803) X-Accept-Language: en-us, en X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Sender: news Subject: 5.3-BETA5 AMD64 Python problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 07:00:49 -0000 Hi All, We have just bought ourselves an AMD64 machine (HP DL145) and I have put 5.3-BETA5 on it. This is our first foray into 5.x, so far we have kept all our servers on 4.x. The server is meant to be a Zope server, but I am having trouble with python. Python 2.3.4 as built from ports cannot pass its own unit tests on this platform, specifically it fails test_re.py in about the 4th test (something to do with catching infinite recursion on a regular expression). The test just core dumps (as does trying to start Zope). I thought this was the well known 'FreeBSD has a tiny pthread stack size' issue. This is fixed in recent pythons (and the ports) by calling pthread_setstacksize to increase the stack to 1MB. I've tried this on 5.3-BETA5/AMD64, but to no avail. If I compile python *without* thread support, then the unit test passes. So I think it is related to threads. I've not managed to keep my finger on the -current development pulse, but wasn't threads re-written in 5.x? Or was it just the scheduler (I am using whichever scheduler 5.3-BETA5 uses by default). I've even tried raising the stack size to 64MB in python, but still it core dumps. Anyone else using python on 5.x? Can you test it passes its regex unit tests? As currently I'm unsure if the problem is related to: 1) AMD64 support 2) 5.x's new threads and/or scheduler 3) something else :) I'm pretty sure I've heard of people running Zope on 5.1 (I'm guessing it was i386) so I'm thinking it is a 64-bit issue. -Matt -- Matt Hamilton matth@netsight.co.uk Netsight Internet Solutions, Ltd. Business Vision on the Internet http://www.netsight.co.uk +44 (0)117 9090901 Web Design | Zope/Plone Development & Consulting | Co-location | Hosting From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 07:53:25 2004 Return-Path: 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 2A86016A4CE; Sun, 3 Oct 2004 07:53:25 +0000 (GMT) Received: from green.homeunix.org (pcp04368961pcs.nrockv01.md.comcast.net [69.140.212.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 173BF43D45; Sun, 3 Oct 2004 07:53:20 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id i937r4ja020979; Sun, 3 Oct 2004 03:53:04 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i937r3MK020978; Sun, 3 Oct 2004 03:53:03 -0400 (EDT) (envelope-from green) Date: Sun, 3 Oct 2004 03:53:03 -0400 From: Brian Fundakowski Feldman To: John Baldwin Message-ID: <20041003075303.GG1034@green.homeunix.org> References: <20040924230425.GB1164@green.homeunix.org> <20040925101021.A78979@bpgate.speednet.com.au> <200409271635.44017.jhb@FreeBSD.org> <20041002060201.GB1034@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041002060201.GB1034@green.homeunix.org> User-Agent: Mutt/1.5.6i cc: scottl@FreeBSD.org cc: Andy Farkas cc: freebsd-current@FreeBSD.org cc: julian@FreeBSD.org cc: jeff@FreeBSD.org Subject: Re: panic: APIC: Previous IPI is stuck X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 07:53:25 -0000 On Sat, Oct 02, 2004 at 02:02:01AM -0400, Brian Fundakowski Feldman wrote: > On Mon, Sep 27, 2004 at 04:35:44PM -0400, John Baldwin wrote: > > On Friday 24 September 2004 08:24 pm, Andy Farkas wrote: > > > I have been having this problem for a few weeks now. Glad I'm not the only > > > one. My box is a 4xPPro running 5.3-BETA5. It panics with either ULE > > > or 4BSD. > > > > > > My theory is that a physical IPI gets lost somewhere and the kerenl spins > > > waiting for it. But thats just a stab in the dark because nobody cares to > > > explain why IPI's would be stuck. > > > > The panic has to do with a previous IPI not finished being sent from the same > > CPU. I've yet to determine why this happens. You can try editing > > sys/i386/i386/local_apic.c and turning on 'DETECT_DEADLOCK' (I think it is > > just commented out) and seeing if that improves stability. I also see this > > on a 4xPIIXeon system I use for testing. > > > > > -andyf > > > > > > On Fri, 24 Sep 2004, Brian Fundakowski Feldman wrote: > > > > This is on a 2xAthlon with the SCHED_ULE, HZ=1000, SW_WATCHDOG, and > > > > nothing really special in development. > > > > > > > > FreeBSD green.homeunix.org 6.0-CURRENT FreeBSD 6.0-CURRENT #110: Wed Sep > > > > 22 11:28:27 EDT 2004 > > > > root@green.homeunix.org:/usr/src/sys/i386/compile/GREEN i386 > > > > > > > > panic: APIC: Previous IPI is stuck > > > > cpuid = 1 > > > > KDB: stack backtrace: > > > > kdb_backtrace(c063cae7,1,c063c5e7,d4411b28,c1da2000) at > > > > kdb_backtrace+0x2e panic(c063c5e7,1,f3,1,2) at panic+0x128 > > > > lapic_ipi_vectored(f3,1,c1da2494,1,c0675910) at 64) at > > > > sched_add_internal+0x21e kseq_assign(c0675910,1,c0625a07,5e0,c1da1540) at > > > > kseq_assign+0x4a sched_clock(c1da2000,2,c0621165,17e,d4411c54) at > > > > sched_clock+0x74 statclock(d4411c54,c1ecc840,d4411c3c,c05edc8b,d4411c54) > > > > at statclock+0xf8 rtcintr(d4411c54,c0487af4,c06733a0,2,8) at rtcintr+0x4f > > > > intr_execute_handlers(c1dca8f0,d4411c54,d4411cb4,c05ea0e3,38) at > > > > intr_execute_ha ndlers+0xab > > > > lapic_handle_intr(38) at lapic_handle_intr+0x3a > > > > Xapic_isr1() at Xapic_isr1+0x33 > > > > --- interrupt, eip = 0xc04a640a, esp = 0xd4411c98, ebp = 0xd4411cb4 --- > > > > _mtx_lock_sleep(c06733e0,c1da2000,0,c06220e8,222) at > > > > _mtx_lock_sleep+0x13a _mtx_lock_flags(c06733e0,0,c06220e8,222,0) at > > > > _mtx_lock_flags+0xc0 > > > > ithread_loop(c1da6200,d4411d48,c0621edb,31f,c1da6200) at > > > > ithread_loop+0x15a fork_exit(c0499660,c1da6200,d4411d48) at > > > > fork_exit+0xc6 > > > > fork_trampoline() at fork_trampoline+0x8 > > > > --- trap 0x1, eip = 0, esp = 0xd4411d7c, ebp = 0 --- > > > > KDB: enter: panic > > > > panic: APIC: Previous IPI is stuck > > > > cpuid = 1 > > > > boot() called on cpu#1 > > > > Uptime: 2d0h16m55s > > > > ^^ full hang instead of reset > > Okay, I just got another one of these, exactly the same as that one but > for the fact that the softclock() interrupt was specifically locking > Giant instead of the interrupt thread loop. So the other CPU owned > Giant at the time and the scheduling CPU is trying to acquire it and > interrupted by needing to run the statclock(). > > This is way too coincidental to ignore. > > SCHED_ULE is far too complex for me to understand much of right now; > what prevents sched_clock() from calling kseq_assign() multiple times > per CPU? Are we _absolutely_100%_certain_ that functionality works > correctly? Ping... adding Jeff... I really wish I understood SCHED_ULE, because it seems entirely plausible it's trying to send two IPIs, the first of which would get blocked waiting for the held sched_lock, and the second of which would never have its interrupt serviced because the first one blocked on sched_lock would have interrupts disabled and would remain unable to respond to an IPI... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 09:19:27 2004 Return-Path: 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 CC6F416A4CE for ; Sun, 3 Oct 2004 09:19:27 +0000 (GMT) Received: from telecom.net.et (sparrow.telecom.net.et [213.55.64.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A444B43D53 for ; Sun, 3 Oct 2004 09:19:25 +0000 (GMT) (envelope-from mtm@identd.net) Received: from [213.55.68.144] (HELO rogue.acs.lan) by telecom.net.et (CommuniGate Pro SMTP 3.4.8) with ESMTP id 58891421; Sun, 03 Oct 2004 12:12:14 +0300 Received: by rogue.acs.lan (Postfix, from userid 1000) id D17DFB830; Sun, 3 Oct 2004 12:19:13 +0300 (EAT) Date: Sun, 3 Oct 2004 12:19:13 +0300 From: Mike Makonnen To: Doug White Message-ID: <20041003091913.GA1720@rogue.acs.lan> References: <20041002151123.J37762@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <20041002151123.J37762@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD/6.0-CURRENT (i386) cc: current@freebsd.org Subject: Re: IFS pollution from localpkg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 09:19:27 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Oct 02, 2004 at 03:18:52PM -0700, Doug White wrote: > I guess no one changes the script_name_sep rc.conf variable to something > more dangerous than the default space... > > Anyway, I think we should investigate running local package scripts with > IFS (and other hazardous variables) stripped using env. Or perhaps not > play with IFS at all unless the user sets script_name_sep, and change the > default accordingly. > > I'm not sure why this doesn't mess more stuff up :-/ It looks like this particular bug has been around since that feature was introduced in rev. 1.272 way back in July 2001. I guess people don't use it that much. Does the following patch fix your problem? Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | Fingerprint: AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 mtm@FreeBSD.Org| FreeBSD - Unleash the Daemon ! --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff Index: etc/rc.d/localpkg =================================================================== RCS file: /home/ncvs/src/etc/rc.d/localpkg,v retrieving revision 1.4 diff -u -r1.4 localpkg --- etc/rc.d/localpkg 28 Jul 2004 00:09:18 -0000 1.4 +++ etc/rc.d/localpkg 3 Oct 2004 09:12:25 -0000 @@ -40,7 +40,7 @@ if [ -x "${script}" ]; then (set -T trap 'exit 1' 2 - ${script} start) + /bin/env IFS="${script_save_sep}" ${script} start) elif [ -f "${script}" -o -L "${script}" ]; then echo -n " (skipping ${script##*/}, not executable)" fi @@ -77,7 +77,7 @@ if [ -x "${script}" ]; then (set -T trap 'exit 1' 2 - ${script} stop) + /bin/env IFS="${script_save_sep}" ${script} stop) fi done IFS="${script_save_sep}" --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 10:44:38 2004 Return-Path: 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 DAEB316A4CE for ; Sun, 3 Oct 2004 10:44:38 +0000 (GMT) Received: from mta09-svc.ntlworld.com (mta09-svc.ntlworld.com [62.253.162.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 367E743D3F for ; Sun, 3 Oct 2004 10:44:38 +0000 (GMT) (envelope-from mark@markdnet.demon.co.uk) Received: from [80.6.110.132] by mta09-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20041003103927.IPYR1100.mta09-svc.ntlworld.com@[80.6.110.132]>; Sun, 3 Oct 2004 11:39:27 +0100 In-Reply-To: <20041002102918.W22102@fw.reifenberger.com> References: <20041002081928.GA21439@gothmog.gr> <20041002102918.W22102@fw.reifenberger.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6053756A-1528-11D9-BECB-000A95C1B5C0@markdnet.demon.co.uk> Content-Transfer-Encoding: 7bit From: Mark Dixon Date: Sun, 3 Oct 2004 11:38:34 +0100 To: Michael Reifenberger X-Pgp-Agent: GPGMail 1.0.1 (v33, 10.3) X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: Protection from the dreaded "rm -fr /" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 10:44:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2 Oct 2004, at 09:34, Michael Reifenberger wrote: > This does only help for the obvious case of '/' but not for the > './' and '../' or '../../' ... accidents. > > Furthermore does it prevent root from doing `rm -rf /` which is a > pretty > legal operation for root since he knows what he is doing. > > This is UNIX, not Windows. > I agree, this is not a route we want to go down. root should be able to do whatever they want, no questions asked. If you put in protections to prevent root doing 'silly' things, it will simply encourage admins to be root when they probably shouldn't Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBX9ayLqgJ90OcaiARAu0pAKDv9Hc6bQl9xi8N5OOXIaG3o6zzjgCfeC3G 60/slkjUAZ1+bALuUVT0GJQ= =LCcS -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 11:04:37 2004 Return-Path: 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 0E12E16A4CE for ; Sun, 3 Oct 2004 11:04:37 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id B658743D1F for ; Sun, 3 Oct 2004 11:04:36 +0000 (GMT) (envelope-from raphaelr@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so124589rnk for ; Sun, 03 Oct 2004 04:04:36 -0700 (PDT) Received: by 10.38.208.53 with SMTP id f53mr4715230rng; Sun, 03 Oct 2004 04:04:36 -0700 (PDT) Received: by 10.38.162.46 with HTTP; Sun, 3 Oct 2004 04:04:36 -0700 (PDT) Message-ID: <3f030e4204100304043ef4b8f@mail.gmail.com> Date: Sun, 3 Oct 2004 13:04:36 +0200 From: "Raphael R." To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_221_16269327.1096801476179" cc: bms@spc.org Subject: tcpdump -tttt option loses timezone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Raphael R." List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 11:04:37 -0000 ------=_Part_221_16269327.1096801476179 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline The -tttt option doesn't use timezone, the time is always GMT: # tcpdump -n -tttt 06/13/2004 13:31:35.758527 192.168.2.1 > 192.168.2.254: icmp: echo request 06/13/2004 13:31:35.758684 192.168.2.254 > 192.168.2.1: icmp: echo reply without time option, I have: # tcpdump -n 15:31:30.808613 192.168.2.1 > 192.168.2.254: icmp: echo request 15:31:30.808769 192.168.2.254 > 192.168.2.1: icmp: echo reply The reason is quite simple (based on 3.8.3 source code) in tcpdump.c: .... int tflag = 1; /* print packet arrival time */ .... .... case 't': --tflag; break; .... .... if (tflag > 0) thiszone = gmt2local(0); .... if -tttt option is enabled gmt2local isn't called and thiszone is alway equals to 0. I've provided a patch: --- tcpdump.c.orig Sun Jun 13 15:50:49 2004 +++ tcpdump.c Sun Jun 13 15:56:42 2004 @@ -615,7 +615,7 @@ /* NOTREACHED */ } - if (tflag > 0) + if ((tflag > 0) || (tflag == -3)) thiszone = gmt2local(0); if (RFileName != NULL) { Another solution is to remove the "if (tflag > 0)" test. This bug was discovered on FreeBSD 5.2.1 (tcpdump 3.7.2 + multidlt) with but apply to all others platforms. This bug is now fixed on branch tcpdump_3_8 and HEAD on tcpdump CVS. I hope that it can be fixed before the 5.3-RELEASE. Raphael Raimbault. ------=_Part_221_16269327.1096801476179 Content-Type: application/octet-stream; name="tcpdump.c.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="tcpdump.c.patch" LS0tIHRjcGR1bXAuYy5vcmlnCVN1biBKdW4gMTMgMTU6NTA6NDkgMjAwNAorKysgdGNwZHVtcC5j CVN1biBKdW4gMTMgMTY6MDU6MzQgMjAwNApAQCAtNjE1LDcgKzYxNSw3IEBACiAJCQkvKiBOT1RS RUFDSEVEICovCiAJCX0KIAotCWlmICh0ZmxhZyA+IDApCisJaWYgKCh0ZmxhZyA+IDApIHx8ICh0 ZmxhZyA9PSAtMykpCiAJCXRoaXN6b25lID0gZ210MmxvY2FsKDApOwogCiAJaWYgKFJGaWxlTmFt ZSAhPSBOVUxMKSB7Cg== ------=_Part_221_16269327.1096801476179-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 2 16:54:04 2004 Return-Path: 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 65C5A16A4CE for ; Sat, 2 Oct 2004 16:54:04 +0000 (GMT) Received: from chatserv.de (p15119030.pureserver.info [217.160.175.43]) by mx1.FreeBSD.org (Postfix) with SMTP id D340C43D60 for ; Sat, 2 Oct 2004 16:54:02 +0000 (GMT) (envelope-from sascha@schumann.cx) Received: (qmail 27498 invoked by uid 1040); 2 Oct 2004 16:54:00 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 2 Oct 2004 16:54:01 -0000 Date: Sat, 2 Oct 2004 18:54:00 +0200 (CEST) From: Sascha Schumann X-X-Sender: sas@localhost To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sun, 03 Oct 2004 11:59:47 +0000 Subject: Conclusion of thread "Deadlocks with recent SMP current"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 16:54:04 -0000 Hi, was there any conclusion to that thread? I have got two systems which are showing the exact same symptoms running RELENG_5_2. The busier one deadlocks regularly once a day. What is the recommended way to procede? I don't want to upgrade to RELENG_5 due to the experimental nature of the network stack, gcc 3.4 integration and general dislike of bleeding edge software for production systems. (and yes, the freebsd 5 systems are inherited.) Thanks for any advise. - Sascha From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 12:43:54 2004 Return-Path: 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 A19DB16A4CE for ; Sun, 3 Oct 2004 12:43:54 +0000 (GMT) Received: from web54005.mail.yahoo.com (web54005.mail.yahoo.com [206.190.36.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B86743D45 for ; Sun, 3 Oct 2004 12:43:54 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Message-ID: <20041003124353.29822.qmail@web54005.mail.yahoo.com> Received: from [147.46.44.181] by web54005.mail.yahoo.com via HTTP; Sun, 03 Oct 2004 05:43:53 PDT Date: Sun, 3 Oct 2004 05:43:53 -0700 (PDT) From: spam maps To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 5.3: /stand/ versus /rescue/ ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 12:43:54 -0000 Hello, On my cvs-updated 5.3 system I have /stand/ and /rescue/. /rescue/ is updated according to cvsup/makeworld etc., but /stand/ is not. Is /stand/ becoming redundant? Should these two directories be merged into a single /rescue/? I notice following differences. Files and directories that are in /stand/, but not in /rescue/: /rescue/-sh /rescue/arp /rescue/boot_crunch /rescue/cpio /rescue/find /rescue/minigzip /rescue/ppp /rescue/sed /rescue/sysinstall /rescue/usbd /rescue/usbdevs /rescue/etc/ /rescue/help/ Moreover, for those files that are in both, the /stand/ ones are obviously older than the ones (from cvsup process) in /rescue/. Regards, Rob. _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 12:47:11 2004 Return-Path: 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 2C4D216A4CE for ; Sun, 3 Oct 2004 12:47:11 +0000 (GMT) Received: from web54005.mail.yahoo.com (web54005.mail.yahoo.com [206.190.36.229]) by mx1.FreeBSD.org (Postfix) with SMTP id ADAEE43D1F for ; Sun, 3 Oct 2004 12:47:10 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Message-ID: <20041003124710.30828.qmail@web54005.mail.yahoo.com> Received: from [147.46.44.181] by web54005.mail.yahoo.com via HTTP; Sun, 03 Oct 2004 05:47:10 PDT Date: Sun, 3 Oct 2004 05:47:10 -0700 (PDT) From: spam maps To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 5.3 & bind9: named.conf vs. named.sample ; why are they different? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 12:47:11 -0000 I have these two files in /var/named/etc/namedb, but are different. Is /var/named/etc/namedb/named.conf redundant and old? # diff -u /var/named/etc/namedb/named.conf /var/named/etc/namedb/named.sample --- /var/named/etc/namedb/named.conf Sat Oct 2 14:58:53 2004 +++ /var/named/etc/namedb/named.sample Sat Oct 2 14:55:49 2004 @@ -1,14 +1,28 @@ -// $FreeBSD: src/etc/namedb/named.conf,v 1.15 2004/06/06 11:46:29 schweikh Exp $ +// $FreeBSD: src/etc/namedb/named.conf,v 1.15.2.1 2004/09/30 23:36:07 dougb Exp $ // -// Refer to the named.conf(5) and named(8) man pages for details. If -// you are ever going to set up a primary server, make sure you +// Refer to the named.conf(5) and named(8) man pages, and the documentation +// in /usr/share/doc/bind9 for more details. +// +// If you are going to set up an authoritative server, make sure you // understand the hairy details of how DNS works. Even with // simple mistakes, you can break connectivity for affected parties, // or cause huge amounts of useless Internet traffic. options { - directory "/etc/namedb"; - pid-file "/var/run/named/pid"; + directory "/etc/namedb"; + pid-file "/var/run/named/pid"; + dump-file "/var/dump/named_dump.db"; + statistics-file "/var/stats/named.stats"; + +// If named is being used only as a local resolver, this is a safe default. +// For named to be accessible to the network, comment this option, specify +// the proper IP address, or delete this option. + listen-on { 127.0.0.1; }; + +// If you have IPv6 enabled on this system, uncomment this option for +// use as a local resolver. To give access to the network, specify +// an IPv6 address, or the keyword "any". +// listen-on-v6 { ::1; }; // In addition to the "forwarders" clause, you can force your name // server to never initiate queries of its own, but always ask its @@ -28,30 +42,12 @@ * If there is a firewall between you and nameservers you want * to talk to, you might need to uncomment the query-source * directive below. Previous versions of BIND always asked - * questions using port 53, but BIND 8.1 uses an unprivileged - * port by default. + * questions using port 53, but BIND versions 8 and later + * use a pseudo-random unprivileged UDP port by default. */ // query-source address * port 53; - - /* - * location for the dumpfile. - */ - // dump-file "s/named_dump.db"; }; -// Note: the following will be supported in a future release. -/* -host { any; } { - topology { - 127.0.0.0/8; - }; -}; -*/ - -// Setting up secondaries is way easier and a rough example for this -// is provided below. -// // If you enable a local name server, don't forget to enter 127.0.0.1 // first in your /etc/resolv.conf so this server will be queried. // Also, make sure to enable it in /etc/rc.conf. @@ -63,26 +59,26 @@ zone "0.0.127.IN-ADDR.ARPA" { type master; - file "localhost.rev"; + file "master/localhost.rev"; }; // RFC 3152 zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" { type master; - file "localhost-v6.rev"; + file "master/localhost-v6.rev"; }; // RFC 1886 -- deprecated zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { type master; - file "localhost-v6.rev"; + file "master/localhost-v6.rev"; }; // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! // -// Example secondary config entries. It can be convenient to become -// a secondary at least for the zone your own domain is in. Ask +// Example slave zone config entries. It can be convenient to become +// a slave at least for the zone your own domain is in. Ask - * If running in a sandbox, you may have to specify a different - * location for the dumpfile. - */ - // dump-file "s/named_dump.db"; }; -// Note: the following will be supported in a future release. -/* -host { any; } { - topology { - 127.0.0.0/8; - }; -}; -*/ - -// Setting up secondaries is way easier and a rough example for this -// is provided below. -// // If you enable a local name server, don't forget to enter 127.0.0.1 // first in your /etc/resolv.conf so this server will be queried. // Also, make sure to enable it in /etc/rc.conf. @@ -63,26 +59,26 @@ zone "0.0.127.IN-ADDR.ARPA" { type master; - file "localhost.rev"; + file "master/localhost.rev"; }; // RFC 3152 zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" { type master; - file "localhost-v6.rev"; + file "master/localhost-v6.rev"; }; // RFC 1886 -- deprecated zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { type master; - file "localhost-v6.rev"; + file "master/localhost-v6.rev"; }; // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! // -// Example secondary config entries. It can be convenient to become -// a secondary at least for the zone your own domain is in. Ask +// Example slave zone config entries. It can be convenient to become +// a slave at least for the zone your own domain is in. Ask // your network administrator for the IP address of the responsible // primary. // @@ -92,23 +88,15 @@ // // Before starting to set up a primary zone, make sure you fully // understand how DNS and BIND works. There are sometimes -// non-obvious pitfalls. Setting up a secondary is simpler. +// non-obvious pitfalls. Setting up a slave zone is simpler. // // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. -// -// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf). -// The directory containing the secondary zones must be write accessible -// to bind. The following sequence is suggested: -// -// mkdir /etc/namedb/s -// chown bind:bind /etc/namedb/s -// chmod 750 /etc/namedb/s /* -zone "domain.com" { +zone "example.com" { type slave; - file "s/domain.com.bak"; + file "slave/example.com"; masters { 192.168.1.1; }; @@ -116,7 +104,7 @@ zone "0.168.192.in-addr.arpa" { type slave; - file "s/0.168.192.in-addr.arpa.bak"; + file "slave/0.168.192.in-addr.arpa"; masters { 192.168.1.1; _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 14:16:55 2004 Return-Path: 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 2CB5C16A4CE; Sun, 3 Oct 2004 14:16:55 +0000 (GMT) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA7443D3F; Sun, 3 Oct 2004 14:16:54 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from ape (81-178-127-34.dsl.pipex.com [81.178.127.34]) by pengo.systems.pipex.net (Postfix) with SMTP id 43B334C0028E; Sun, 3 Oct 2004 15:16:49 +0100 (BST) Message-ID: <08d601c4a954$242380b0$f700000a@ape> From: "Markie" To: , "FreeBSD Current" Date: Sun, 3 Oct 2004 15:20:26 +0100 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.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: switching cardbus card hangs in 6-CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 14:16:55 -0000 I installed via a 5.3-BETA5 CD and I was able to switch network cards, a D-Link DWL-G650 and an Intel... can't remember, fxp0 driver; both are cardbus cards anyway. Now I have updated to 6.0-CURRENT (a few days ago) I have noticed I can no longer take the card out. If I do, the system appears appears to hang while running X. I just now tried from the console and it's actually a panic. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id =00 fault virtual address 0x3c fault code = supervisor read, page not present instruction pointer = 0x8:0xc056a2ce stack pointer = 0x10:0xc7c86b90 frame pointer = 0x10:0xc7c86bac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 40 (cbb0) trap number = 12 panic: page fault cpuid = 0 Uptime: 3m53s You'll probably have to excuse the formatting as that was hand typed. Curiously, it doesn't come up with the press any key to reboot or anything and just seems to be stuck there. I don't think that's normal? Perhaps I should send this to the current list too... Any advice? From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 14:30:46 2004 Return-Path: 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 9F4D816A4CE; Sun, 3 Oct 2004 14:30:46 +0000 (GMT) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C0EC43D5A; Sun, 3 Oct 2004 14:30:45 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost.init-main.com [127.0.0.1]) by sana.init-main.com (8.13.1/8.13.1) with ESMTP id i93ET8Sf008251; Sun, 3 Oct 2004 23:29:09 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200410031429.i93ET8Sf008251@sana.init-main.com> To: Uwe Doering From: takawata@jp.freebsd.org In-reply-to: Your message of "Sun, 03 Oct 2004 11:08:49 +0200." <415FC1A1.3020502@geminix.org> Date: Sun, 03 Oct 2004 23:29:08 +0900 Sender: takawata@init-main.com cc: freebsd-current@freebsd.org Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 14:30:46 -0000 In message <415FC1A1.3020502@geminix.org>, Uwe Doering wrote: >Hi there, > >with regard to your above mentioned fix you may be interested in reading >this short discussion, especially my answer to the original article: > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=116615+0+archive/2004/freebsd-stable/20040613.freebsd-stable Thank you for your comment. The code is what nullfs do. static int null_getattr(ap) struct vop_getattr_args /* { struct vnode *a_vp; struct vattr *a_vap; struct ucred *a_cred; struct thread *a_td; } */ *ap; { int error; if ((error = null_bypass((struct vop_generic_args *)ap)) != 0) return (error); ap->a_vap->va_fsid = ap->a_vp->v_mount->mnt_stat.f_fsid.val[0]; return (0); } I'm pleased if you explain why it is done for nullfs and not for unionfs, if any. IMHO, there are not so much advantage in assuming exactly same file exists in different filesystem, if the entity is same. But I want to hear from FS gurus. I found that I reverted the change at CVS rev 1.62. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/unionfs/union_vnops.c.diff?r1=1.61&r2=1.62 From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 15:34:19 2004 Return-Path: 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 7613016A4CE for ; Sun, 3 Oct 2004 15:34:16 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D89643D46 for ; Sun, 3 Oct 2004 15:34:16 +0000 (GMT) (envelope-from david.downey@gmail.com) Received: by mproxy.gmail.com with SMTP id 77so4350754rnk for ; Sun, 03 Oct 2004 08:34:15 -0700 (PDT) Received: by 10.38.70.21 with SMTP id s21mr3580351rna; Sun, 03 Oct 2004 08:34:15 -0700 (PDT) Received: by 10.38.82.69 with HTTP; Sun, 3 Oct 2004 08:34:15 -0700 (PDT) Message-ID: <6917b781041003083422828183@mail.gmail.com> Date: Sun, 3 Oct 2004 11:34:15 -0400 From: "David D.W. Downey" To: Ruslan Ermilov In-Reply-To: <20041003051530.GA2165@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <415EC5E6.2070305@FreeBSD.org> <20041002165116.GB57797@ip.net.ua> <415F796F.8010204@FreeBSD.org> <20041003051530.GA2165@ip.net.ua> cc: Current cc: Scott Long Subject: Re: [Fwd: Re: Inability to create jails under 5.3-BETA6] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "David D.W. Downey" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 15:34:19 -0000 Sorry Ruslan, Had some issues here that necessitated a reinstall which kept me offline since i messaged about this. OK, I'll check out what you said. I just tried under BETA7 using the man page details to try it. I'll check out your suggestion and go from there. My Makefile is currently $FreeBSD: src/Makefile,v 1.306 2004/08/09 11:38:41 harti Exp $ and this is 5.3-BETA7 pull as of yesterday night. Is 1.442 in 6.x or something? (I just redid a fresh pull while working on this email and it's still 1.306) David On Sun, 3 Oct 2004 08:15:30 +0300, Ruslan Ermilov wrote: > Hi Scott, > > On Sat, Oct 02, 2004 at 10:00:47PM -0600, Scott Long wrote: > > Is it better to MFC the hack from HEAD, or just update the manpage? > > > I think it's better to MFC it (I planned to do it anyway), > especially that the patch is trivial and only changes the > type of the DESTDIR variable in three places. (Patch is > attached, in case you want to commit it -- I will be away > from my computer in the next 12 or so hours.) > > Cheers, > > > -- > Ruslan Ermilov > ru@FreeBSD.org > FreeBSD committer > > > > -- David D.W. Downey From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 16:40:26 2004 Return-Path: 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 41E6116A4CE for ; Sun, 3 Oct 2004 16:40:26 +0000 (GMT) Received: from mwinf0108.wanadoo.fr (smtp1.wanadoo.fr [193.252.22.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BECBF43D31 for ; Sun, 3 Oct 2004 16:40:08 +0000 (GMT) (envelope-from dak@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0108.wanadoo.fr (SMTP Server) with SMTP id 9A433180014C for ; Sun, 3 Oct 2004 18:40:07 +0200 (CEST) Received: from smtp.wanadoo.fr (ca-sqy-2-245.w80-8.abo.wanadoo.fr [80.8.55.245]) by mwinf0108.wanadoo.fr (SMTP Server) with ESMTP id 409FA1800145 for ; Sun, 3 Oct 2004 18:40:07 +0200 (CEST) Received: from nebula.wanadoo.fr (localhost [127.0.0.1]) by smtp.wanadoo.fr (8.13.1/8.13.1) with ESMTP id i93Ge6DZ020489 for ; Sun, 3 Oct 2004 18:40:06 +0200 (CEST) (envelope-from dak@nebula.wanadoo.fr) Received: (from dak@localhost) by nebula.wanadoo.fr (8.13.1/8.13.1/Submit) id i93Ge6uA020488 for current@freebsd.org; Sun, 3 Oct 2004 18:40:06 +0200 (CEST) (envelope-from dak) Date: Sun, 3 Oct 2004 18:40:06 +0200 From: Aurelien NEPHTALI To: current@freebsd.org Message-ID: <20041003164006.GA20441@nebula.wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: .symtab section is now broken ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 16:40:26 -0000 Hi, I have coded some tools that read ELF binaries. Thet used to work 1 or 2 years ago but now they don't. These tools parse an ELF file to get addresses of malloc(),free(),etc into the PLT to put breakpoint on them. The problem comes from the .symtab section. I'm using this struct to read symbols: typedef struct s_symhdr { unsigned int st_name; unsigned int st_value; unsigned int st_size; unsigned char st_info; unsigned char st_other; unsigned short st_shndx; } t_symhdr; Before, the field 'st_value' contained the symbol's address into the PLT, now it's null, ie (readelf output): 71: 00000000 41 FUNC GLOBAL DEFAULT UND malloc ^^^^^^^^ value I was suspecting the new gcc so I installed gcc 2.95 but it's the same problem. Is there a reason ? What to do to still get the value I want ? I have tested on NetBSD 1.6.1 and it works fine. Thanks. -- NEPHTALI 'dak' Aurelien TEK2 - Promo 2008 06.19.84.90.10 From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 18:09:26 2004 Return-Path: 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 D666216A4CE; Sun, 3 Oct 2004 18:09:26 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 152F643D1F; Sun, 3 Oct 2004 18:09:26 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (oak.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i93I9PDd032457; Sun, 3 Oct 2004 21:09:25 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 73321-08; Sun, 3 Oct 2004 21:09:24 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i93I9NGN032454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Oct 2004 21:09:24 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i93I9RP0003968; Sun, 3 Oct 2004 21:09:27 +0300 (EEST) (envelope-from ru) Date: Sun, 3 Oct 2004 21:09:27 +0300 From: Ruslan Ermilov To: "David D.W. Downey" Message-ID: <20041003180927.GA3932@ip.net.ua> References: <415EC5E6.2070305@FreeBSD.org> <20041002165116.GB57797@ip.net.ua> <415F796F.8010204@FreeBSD.org> <20041003051530.GA2165@ip.net.ua> <6917b781041003083422828183@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <6917b781041003083422828183@mail.gmail.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: Current cc: Scott Long Subject: Re: [Fwd: Re: Inability to create jails under 5.3-BETA6] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 18:09:26 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 03, 2004 at 11:34:15AM -0400, David D.W. Downey wrote: > Sorry Ruslan, >=20 > Had some issues here that necessitated a reinstall which kept me > offline since i messaged about this. >=20 > OK, I'll check out what you said. I just tried under BETA7 using the > man page details to try it. I'll check out your suggestion and go from > there. >=20 > My Makefile is currently $FreeBSD: src/Makefile,v 1.306 2004/08/09 > 11:38:41 harti Exp $ > and this is 5.3-BETA7 pull as of yesterday night. Is 1.442 in 6.x or > something? (I just redid a fresh pull while working on this email and > it's still 1.306) >=20 You need src/Makefile.inc1,v 1.442 not src/Makefile. > On Sun, 3 Oct 2004 08:15:30 +0300, Ruslan Ermilov wrote: > > Hi Scott, > >=20 > > On Sat, Oct 02, 2004 at 10:00:47PM -0600, Scott Long wrote: > > > Is it better to MFC the hack from HEAD, or just update the manpage? > > >=20 > > I think it's better to MFC it (I planned to do it anyway), > > especially that the patch is trivial and only changes the > > type of the DESTDIR variable in three places. (Patch is > > attached, in case you want to commit it -- I will be away > > from my computer in the next 12 or so hours.) I also attached a ready to commit patch in this email. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYEBXqRfpzJluFF4RAkXYAJ9dVO5ZSfheVN5wtvvxg6LQhtJU5gCeK3Uf 6VOvZt5s0o4KBZpY69QXiaU= =NZSu -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 18:12:13 2004 Return-Path: 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 DA53B16A4CE for ; Sun, 3 Oct 2004 18:12:13 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7727043D4C for ; Sun, 3 Oct 2004 18:12:13 +0000 (GMT) (envelope-from sjr@comcast.net) Received: from istari.comcast.net (pcp08127824pcs.nrockv01.md.comcast.net[69.138.220.134](misconfigured sender)) by comcast.net (sccrmhc11) with ESMTP id <2004100318121001100jv4ipe>; Sun, 3 Oct 2004 18:12:10 +0000 Received: from istari.comcast.net (localhost [127.0.0.1]) by istari.comcast.net (8.12.11/8.12.11) with ESMTP id i93IC79a000175 for ; Sun, 3 Oct 2004 14:12:09 -0400 (EDT) (envelope-from sjr@istari.comcast.net) Message-Id: <200410031812.i93IC79a000175@istari.comcast.net> Date: Sun, 3 Oct 2004 14:12:06 -0400 (EDT) From: "Stephen J. Roznowski" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Subject: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 18:12:14 -0000 Greetings, I'm trying to install 5.3-BETA6 onto an HP Presario SA4000Z. [AMD64 using an nForce3 250 chipset]. I've also upgraded to RELENG_5 and the problem remains. The network configures as "fwe0" and appears to have the correct IP address, but if I attempt to ping the gateway, I get a "Host is down" error. I've tried using "fwip0" instead, but I get the same error. I can provide more [system] details if needed.... So, any ideas what to try next to get the network functional?? Thanks, -SR -- Stephen J. Roznowski (sjr@comcast.net) From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 18:21:48 2004 Return-Path: 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 84B0616A4CE for ; Sun, 3 Oct 2004 18:21:48 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B6F43D45 for ; Sun, 3 Oct 2004 18:21:48 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.34 (FreeBSD)) id 1CEAzT-000CXF-HH for freebsd-current@freebsd.org; Sun, 03 Oct 2004 11:21:47 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16736.17211.132754.898091@ran.psg.com> Date: Sun, 3 Oct 2004 11:21:47 -0700 To: FreeBSD Current Subject: usb serial confuddlement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 18:21:48 -0000 i have a belkin usb serial that used to work a year ago back in the 4.x days. i am having trouble getting it to work now in 6-current. it comes up as ugen0: Belkin USB PDA Adapter Belkin Components, rev 1.10/1.02, addr 4 and # usbdevs -v # edited Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 4: full speed, power 100 mA, config 1, Belkin Components(0x0109), Belkin USB PDA Adapter(0x050d), rev 1.02 port 2 addr 2: full speed, self powered, config 1, USB HUB(0x0500), Western Digital(0x1058), rev 0.07 port 1 powered port 2 addr 3: full speed, self powered, config 1, External HDD(0x0400), Western Digital(0x1058), rev 1.06 port 3 powered port 4 powered i am trying a usbd.conf of device "Belkin USB PDA Adapter" devname "ucom0" vendor 0x0109 product 0x050d # attach but am kinda lost as kermitting to /dev/ucom0 gives me C-Kermit>set line /dev/ucom0 /dev/ucom0: No such file or directory Connection to /dev/ucom0 failed: No such file or directory yet # kldstat Id Refs Address Size Name 1 16 0xc0400000 3a42f4 kernel 2 1 0xc07a5000 6eb8 linprocfs.ko 3 2 0xc07ac000 1fa44 linux.ko 4 1 0xc07cc000 bc08 ipfw.ko 5 1 0xc07d8000 5f84 snd_ich.ko 6 2 0xc07de000 204fc sound.ko 7 1 0xc07ff000 5418 acpi_video.ko 8 15 0xc0805000 5d6f4 acpi.ko 9 1 0xc5981000 3000 ucom.ko should i remove all usb from the kernel? randy From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 18:32:26 2004 Return-Path: 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 DF61516A4CE; Sun, 3 Oct 2004 18:32:26 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0624943D1D; Sun, 3 Oct 2004 18:32:26 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i93IWbYw008147; Sun, 3 Oct 2004 14:32:37 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i93IWbHU008146; Sun, 3 Oct 2004 14:32:37 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 3 Oct 2004 14:32:37 -0400 From: David Schultz To: Takanori Watanabe Message-ID: <20041003183237.GA8100@VARK.MIT.EDU> Mail-Followup-To: Takanori Watanabe , Uwe Doering , freebsd-fs@FreeBSD.ORG, bp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <41601BE0.4050401@geminix.org> <200410031805.i93I5JNZ009076@sana.init-main.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410031805.i93I5JNZ009076@sana.init-main.com> cc: freebsd-fs@FreeBSD.ORG cc: bp@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG cc: Uwe Doering Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 18:32:27 -0000 On Mon, Oct 04, 2004, Takanori Watanabe wrote: > >With 'unionfs' you can have underlying files from two different layers > >(upper and lower) on two different file systems which may, by > >coincidence, have the same inode number. Now, if you override the real > >va_fsid with that of the 'unionfs' mount you'll end up with two > >'unionfs' vnodes that appear to represent the same file (a hard link, > >for instance), but in reality the files are different entities. > >Obviously, both the kernel and applications might draw wrong conclusions > >in this case. > > I think the three filesystem entry > 1. upper layer file > 2. lower layer file > 3. unionfs file > can be treated as different. I didn't pursue this before because I was concerned that it would introduce cache consistency issues between the union vnode and the underlying vnode. But I guess all vnops ultimately wind up at the underlying vnode, so this hopefully isn't an issue... From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 19:05:11 2004 Return-Path: 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 B43EB16A4CE for ; Sun, 3 Oct 2004 19:05:11 +0000 (GMT) Received: from out009.verizon.net (out009pub.verizon.net [206.46.170.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F1C543D1D for ; Sun, 3 Oct 2004 19:05:11 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([141.153.167.39]) by out009.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041003190508.UUHP23440.out009.verizon.net@[10.0.3.231]> for ; Sun, 3 Oct 2004 14:05:08 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: FreeBSD Current In-Reply-To: <16736.17211.132754.898091@ran.psg.com> References: <16736.17211.132754.898091@ran.psg.com> Content-Type: text/plain Message-Id: <1096830295.847.1.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 03 Oct 2004 15:04:56 -0400 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out009.verizon.net from [141.153.167.39] at Sun, 3 Oct 2004 14:05:08 -0500 Subject: Re: usb serial confuddlement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 19:05:11 -0000 On Sun, 2004-10-03 at 14:21, Randy Bush wrote: > i have a belkin usb serial that used to work a year ago back > in the 4.x days. i am having trouble getting it to work now > in 6-current. > > it comes up as > > ugen0: Belkin USB PDA Adapter Belkin Components, rev 1.10/1.02, addr 4 > > and > > # usbdevs -v # edited > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 > port 1 addr 4: full speed, power 100 mA, config 1, Belkin Components(0x0109), Belkin USB PDA Adapter(0x050d), rev 1.02 > port 2 addr 2: full speed, self powered, config 1, USB HUB(0x0500), Western Digital(0x1058), rev 0.07 > port 1 powered > port 2 addr 3: full speed, self powered, config 1, External HDD(0x0400), Western Digital(0x1058), rev 1.06 > port 3 powered > port 4 powered > > i am trying a usbd.conf of > > device "Belkin USB PDA Adapter" > devname "ucom0" > vendor 0x0109 > product 0x050d > # attach > > but am kinda lost as kermitting to /dev/ucom0 gives me > > C-Kermit>set line /dev/ucom0 > /dev/ucom0: No such file or directory > Connection to /dev/ucom0 failed: No such file or directory > > yet > > # kldstat > Id Refs Address Size Name > 1 16 0xc0400000 3a42f4 kernel > 2 1 0xc07a5000 6eb8 linprocfs.ko > 3 2 0xc07ac000 1fa44 linux.ko > 4 1 0xc07cc000 bc08 ipfw.ko > 5 1 0xc07d8000 5f84 snd_ich.ko > 6 2 0xc07de000 204fc sound.ko > 7 1 0xc07ff000 5418 acpi_video.ko > 8 15 0xc0805000 5d6f4 acpi.ko > 9 1 0xc5981000 3000 ucom.ko > > should i remove all usb from the kernel? > > randy > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" You need 'ubsa' module loaded or device 'ubsa' in you kernel configuration. --- Alexandre "Sunny" Kovalenko. From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 19:33:07 2004 Return-Path: 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 8834A16A4CE for ; Sun, 3 Oct 2004 19:33:07 +0000 (GMT) Received: from mwinf0806.wanadoo.fr (smtp8.wanadoo.fr [193.252.22.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2C9643D2F for ; Sun, 3 Oct 2004 19:33:06 +0000 (GMT) (envelope-from dak@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0806.wanadoo.fr (SMTP Server) with SMTP id C81E71800112 for ; Sun, 3 Oct 2004 21:33:05 +0200 (CEST) Received: from smtp.wanadoo.fr (ca-sqy-2-245.w80-8.abo.wanadoo.fr [80.8.55.245]) by mwinf0806.wanadoo.fr (SMTP Server) with ESMTP id 956BD18001AD for ; Sun, 3 Oct 2004 21:33:05 +0200 (CEST) Received: from nebula.wanadoo.fr (localhost [127.0.0.1]) by smtp.wanadoo.fr (8.13.1/8.13.1) with ESMTP id i93JX47t001232 for ; Sun, 3 Oct 2004 21:33:05 +0200 (CEST) (envelope-from dak@nebula.wanadoo.fr) Received: (from dak@localhost) by nebula.wanadoo.fr (8.13.1/8.13.1/Submit) id i93JX4Lb001231 for current@freebsd.org; Sun, 3 Oct 2004 21:33:04 +0200 (CEST) (envelope-from dak) Date: Sun, 3 Oct 2004 21:33:04 +0200 From: Aurelien Nephtali To: current@freebsd.org Message-ID: <20041003193304.GA1202@nebula.wanadoo.fr> References: <20041003164006.GA20441@nebula.wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041003164006.GA20441@nebula.wanadoo.fr> User-Agent: Mutt/1.5.6i Subject: Re: .symtab section is now broken ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 19:33:07 -0000 I fixed the problem by linking with -static but I'm sure that before I wasn't using this. On Sun, Oct 03, 2004 at 06:40:06PM +0200, Aurelien NEPHTALI wrote: > Hi, > > I have coded some tools that read ELF binaries. Thet used to work 1 or 2 years > ago but now they don't. These tools parse an ELF file to get addresses of > malloc(),free(),etc into the PLT to put breakpoint on them. > > The problem comes from the .symtab section. I'm using this struct to read > symbols: > > typedef struct s_symhdr > { > unsigned int st_name; > unsigned int st_value; > unsigned int st_size; > unsigned char st_info; > unsigned char st_other; > unsigned short st_shndx; > } t_symhdr; > > Before, the field 'st_value' contained the symbol's address into the PLT, > now it's null, ie (readelf output): > > 71: 00000000 41 FUNC GLOBAL DEFAULT UND malloc > ^^^^^^^^ > value > > I was suspecting the new gcc so I installed gcc 2.95 but it's the same problem. > > Is there a reason ? What to do to still get the value I want ? > > I have tested on NetBSD 1.6.1 and it works fine. > > Thanks. > > -- > NEPHTALI 'dak' Aurelien > TEK2 - Promo 2008 > 06.19.84.90.10 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- NEPHTALI 'dak' Aurelien TEK2 - Promo 2008 06.19.84.90.10 From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 19:54:38 2004 Return-Path: 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 C351516A4CE for ; Sun, 3 Oct 2004 19:54:38 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E40743D39 for ; Sun, 3 Oct 2004 19:54:38 +0000 (GMT) (envelope-from david.downey@gmail.com) Received: by mproxy.gmail.com with SMTP id 79so3762807rnk for ; Sun, 03 Oct 2004 12:54:34 -0700 (PDT) Received: by 10.38.73.46 with SMTP id v46mr4335470rna; Sun, 03 Oct 2004 12:54:34 -0700 (PDT) Received: by 10.38.82.69 with HTTP; Sun, 3 Oct 2004 12:54:34 -0700 (PDT) Message-ID: <6917b781041003125473180ac5@mail.gmail.com> Date: Sun, 3 Oct 2004 15:54:34 -0400 From: "David D.W. Downey" To: Ruslan Ermilov In-Reply-To: <20041003180927.GA3932@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <415EC5E6.2070305@FreeBSD.org> <20041002165116.GB57797@ip.net.ua> <415F796F.8010204@FreeBSD.org> <20041003051530.GA2165@ip.net.ua> <6917b781041003083422828183@mail.gmail.com> <20041003180927.GA3932@ip.net.ua> cc: Current cc: Scott Long Subject: Re: [Fwd: Re: Inability to create jails under 5.3-BETA6] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "David D.W. Downey" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 19:54:39 -0000 On Sun, 3 Oct 2004 21:09:27 +0300, Ruslan Ermilov wrote: > On Sun, Oct 03, 2004 at 11:34:15AM -0400, David D.W. Downey wrote: > > Sorry Ruslan, > > > > Had some issues here that necessitated a reinstall which kept me > > offline since i messaged about this. > > > > OK, I'll check out what you said. I just tried under BETA7 using the > > man page details to try it. I'll check out your suggestion and go from > > there. > > > > My Makefile is currently $FreeBSD: src/Makefile,v 1.306 2004/08/09 > > 11:38:41 harti Exp $ > > and this is 5.3-BETA7 pull as of yesterday night. Is 1.442 in 6.x or > > something? (I just redid a fresh pull while working on this email and > > it's still 1.306) > > > You need src/Makefile.inc1,v 1.442 not src/Makefile. > > > On Sun, 3 Oct 2004 08:15:30 +0300, Ruslan Ermilov wrote: > > > Hi Scott, > > > > > > On Sat, Oct 02, 2004 at 10:00:47PM -0600, Scott Long wrote: > > > > Is it better to MFC the hack from HEAD, or just update the manpage? > > > > > > > I think it's better to MFC it (I planned to do it anyway), > > > especially that the patch is trivial and only changes the > > > type of the DESTDIR variable in three places. (Patch is > > > attached, in case you want to commit it -- I will be away > > > from my computer in the next 12 or so hours.) > > I also attached a ready to commit patch in this email. > > Also ran into a problem using the method you described of make installworld DESTDIR=$D doing that failed to install quite a few files. /etc/ is almost completely unpopulated. Doesn't even know who root is! (from inside the jail) ==================== # ls etc/ X11 fstab mail ntp ppp rc.d ssh bluetooth gnats mtree pam.d rc.conf resolv.conf ssl defaults isdn namedb periodic rc.conf~ skel # (rc.conf and resolv.conf are edits i made following the man page) My exact sequences were as follows... >From silvani (the host) (codecastle.com is my private internal network) I ran /bin/sh (since no offense but I can't stand csh) # cd /usr/src # cvsup -g -L 2 /usr/sup/current-supfile # D=/usr/local/LOCKBOX/virtual-tree/development/devel.codecastle.com # mkdir -p $D # ls -alh /usr/local/LOCKBOX/virtual-tree/development/ total 10 drwxr-xr-x 5 root wheel 512B Oct 3 13:47 . drwxr-xr-x 4 root wheel 512B Sep 30 00:19 .. drwxrwxr-x 2 root operator 512B Oct 3 00:28 .snap drwxr-xr-x 16 root wheel 512B Oct 3 13:47 desktop.codecastle.com drwxr-xr-x 16 root wheel 512B Oct 3 13:41 devel.codecastle.com # make buildworld # make installworld DESTDIR=$D # jail /usr/local/LOCKBOX/virtual-tree/development/devel.codecastle.com 192.168.1.5 /bin/sh # touch /etc/fstab # echo 'nameserver 4.2.2.1' >> /etc/resolv.conf # echo 'nameserver 4.2.2.3' >> /etc/resolv.conf [Then i hand edited /etc/rc.conf to add the appropriate entries as shown in the man page for jail] Then I did this... # passwd root passwd: root: no such user # Which prompted me to check the /etc dir for passwd and master.passwd. As the above ls showed there were a truckload of files missing just in the /etc/ dir itself. Any ideas? -- David D.W. Downey From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 19:59:41 2004 Return-Path: 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 5E00416A4CE; Sun, 3 Oct 2004 19:59:41 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E24743D1F; Sun, 3 Oct 2004 19:59:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F329251CE1; Sun, 3 Oct 2004 13:00:40 -0700 (PDT) Date: Sun, 3 Oct 2004 13:00:40 -0700 From: Kris Kennaway To: "David D.W. Downey" Message-ID: <20041003200040.GA23567@xor.obsecurity.org> References: <415EC5E6.2070305@FreeBSD.org> <20041002165116.GB57797@ip.net.ua> <415F796F.8010204@FreeBSD.org> <20041003051530.GA2165@ip.net.ua> <6917b781041003083422828183@mail.gmail.com> <20041003180927.GA3932@ip.net.ua> <6917b781041003125473180ac5@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <6917b781041003125473180ac5@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: Scott Long cc: Current Subject: Re: [Fwd: Re: Inability to create jails under 5.3-BETA6] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 19:59:41 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 03, 2004 at 03:54:34PM -0400, David D.W. Downey wrote: > Also ran into a problem using the method you described of make > installworld DESTDIR=3D$D >=20 > doing that failed to install quite a few files. /etc/ is almost > completely unpopulated. Doesn't even know who root is! Er, that's because you forgot the 'make distribution' step in the list (see the jail manpage). Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYFpoWry0BWjoQKURAg4TAJsFzds5VG534W67+svbTXGKEOOyrQCdEX9o GezoBIclbYSNaolnn8oyKYc= =KP3Z -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:01:28 2004 Return-Path: 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 6E2E816A4CE for ; Sun, 3 Oct 2004 20:01:28 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2100243D4C for ; Sun, 3 Oct 2004 20:01:28 +0000 (GMT) (envelope-from david.downey@gmail.com) Received: by mproxy.gmail.com with SMTP id 79so3763068rnk for ; Sun, 03 Oct 2004 13:01:24 -0700 (PDT) Received: by 10.38.171.77 with SMTP id t77mr5263717rne; Sun, 03 Oct 2004 13:01:24 -0700 (PDT) Received: by 10.38.82.69 with HTTP; Sun, 3 Oct 2004 13:01:23 -0700 (PDT) Message-ID: <6917b781041003130131b3359d@mail.gmail.com> Date: Sun, 3 Oct 2004 16:01:23 -0400 From: "David D.W. Downey" To: Kris Kennaway In-Reply-To: <20041003200040.GA23567@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <415EC5E6.2070305@FreeBSD.org> <20041002165116.GB57797@ip.net.ua> <415F796F.8010204@FreeBSD.org> <20041003051530.GA2165@ip.net.ua> <6917b781041003083422828183@mail.gmail.com> <20041003180927.GA3932@ip.net.ua> <6917b781041003125473180ac5@mail.gmail.com> <20041003200040.GA23567@xor.obsecurity.org> cc: Scott Long cc: Current Subject: Re: [Fwd: Re: Inability to create jails under 5.3-BETA6] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "David D.W. Downey" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:01:28 -0000 On Sun, 3 Oct 2004 13:00:40 -0700, Kris Kennaway wrote: > On Sun, Oct 03, 2004 at 03:54:34PM -0400, David D.W. Downey wrote: > > Er, that's because you forgot the 'make distribution' step in the list > (see the jail manpage). > > Kris > DOH! Thanks, -- David D.W. Downey From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:02:10 2004 Return-Path: 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 4A8E816A4D0 for ; Sun, 3 Oct 2004 20:02:10 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1662E43D2F for ; Sun, 3 Oct 2004 20:02:07 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-67-124-50-20.dsl.snfc21.pacbell.net [67.124.50.20])i93K1iIV009605; Sun, 3 Oct 2004 16:01:46 -0400 Message-ID: <41605AB9.8090008@elischer.org> Date: Sun, 03 Oct 2004 13:02:01 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Sascha Schumann References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:02:10 -0000 Sascha Schumann wrote: > Hi, > > was there any conclusion to that thread? I have got two > systems which are showing the exact same symptoms running > RELENG_5_2. The busier one deadlocks regularly once a day. > > What is the recommended way to procede? I don't want to > upgrade to RELENG_5 due to the experimental nature of the > network stack, gcc 3.4 integration and general dislike of > bleeding edge software for production systems. (and yes, the > freebsd 5 systems are inherited.) > > Thanks for any advise. > > - Sascha > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" We have two thread dealock cases hat we are tracking down there are fixes for both in the works. From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:02:46 2004 Return-Path: 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 1467E16A4CE for ; Sun, 3 Oct 2004 20:02:46 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE63543D31 for ; Sun, 3 Oct 2004 20:02:45 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.34 (FreeBSD)) id 1CECZB-0000eP-5o for freebsd-current@freebsd.org; Sun, 03 Oct 2004 13:02:45 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16736.23268.584348.209354@ran.psg.com> Date: Sun, 3 Oct 2004 13:02:44 -0700 To: FreeBSD Current Subject: fails to mount md /tmp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:02:46 -0000 i get # /sbin/mdmfs -s 64m -M md /tmp mdmfs: mdconfig (attach) exited with error code 1 kernel has /dev/md # grep md /sys/i386/conf/RAN #device amd # AMD 53C974 (Tekram DC-390(T)) device md # Memory "disks" but their ain't no /dev/md0 # ls /dev/md* /dev/mdctl i do have /etc/rc.conf set up the same as on systems which mount it successfully # grep tmp /etc/rc.conf tmpmfs="YES" # Set to YES to always create an mfs /tmp, NO to never tmpsize="64m" # Size of mfs /tmp if created clear_tmp_enable="YES" # Clear /tmp at startup. randy From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:07:52 2004 Return-Path: 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 001FE16A4CE; Sun, 3 Oct 2004 20:07:51 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9713D43D1D; Sun, 3 Oct 2004 20:07:51 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i93K832c008713; Sun, 3 Oct 2004 16:08:03 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i93K83cl008712; Sun, 3 Oct 2004 16:08:03 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 3 Oct 2004 16:08:03 -0400 From: David Schultz To: Uwe Doering Message-ID: <20041003200803.GA8668@VARK.MIT.EDU> Mail-Followup-To: Uwe Doering , Takanori Watanabe , freebsd-fs@FreeBSD.ORG, bp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <41601BE0.4050401@geminix.org> <200410031805.i93I5JNZ009076@sana.init-main.com> <20041003183237.GA8100@VARK.MIT.EDU> <41605620.90407@geminix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41605620.90407@geminix.org> cc: freebsd-fs@FreeBSD.ORG cc: bp@FreeBSD.ORG cc: Takanori Watanabe cc: freebsd-current@FreeBSD.ORG Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:07:52 -0000 On Sun, Oct 03, 2004, Uwe Doering wrote: > >>I think the three filesystem entry > >>1. upper layer file > >>2. lower layer file > >>3. unionfs file > >>can be treated as different. > > > >I didn't pursue this before because I was concerned that it would > >introduce cache consistency issues between the union vnode and the > >underlying vnode. But I guess all vnops ultimately wind up at the > >underlying vnode, so this hopefully isn't an issue... > > Applications use the synthesized unionfs vnodes. They have no knowledge > of what's going on underneath. So they can't tell whether one unionfs > vnode refers to a file in the upper layer, and the other to one in the > lower layer. That isn't the issue. The issue is that an application might open the vnode in the unionfs mount, and another application might modify the same file in the underlying file system. If the kernel doesn't understand that it is really the same file, then cache incoherencies will occur. I'm actually not sure to what extent this is a problem already; John Heidemann's Phd thesis had a way of dealing with it, but FreeBSD doesn't do things that way AFAIK. From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:08:14 2004 Return-Path: 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 28AD916A4CE for ; Sun, 3 Oct 2004 20:08:14 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F2943D2F for ; Sun, 3 Oct 2004 20:08:13 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i93K8D90059692; Sun, 3 Oct 2004 13:08:13 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <41605C2C.8050004@freebsd.org> Date: Sun, 03 Oct 2004 13:08:12 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: spam maps References: <20041003124353.29822.qmail@web54005.mail.yahoo.com> In-Reply-To: <20041003124353.29822.qmail@web54005.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.3: /stand/ versus /rescue/ ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:08:14 -0000 /stand is largely defunct. It is, I believe, still used to bootstrap the CD-ROM installation, but has no particular purpose after that point. Most of these do have counterparts in /rescue (e.g. -sh is redundant with sh, minigzip is redundant with gzip, cpio with pax/tar, etc.) sysinstall is in /usr/sbin now. The point of /rescue is to provide a reliable environment from which a broken /bin and /sbin can be repaired. That seems to boil down to basic tools for locating and copying files from various sources (to replace a hosed shared library, for instance). If there are things that should be in /rescue that would be needed in certain scenarios, feel free to propose additions or changes to /rescue. Be prepared to nominate deletions as well; very many people think that /rescue is already too large. Tim spam maps wrote: > Hello, > > On my cvs-updated 5.3 system I have /stand/ and > /rescue/. > > /rescue/ is updated according to cvsup/makeworld etc., > but /stand/ is not. Is /stand/ becoming redundant? > Should these two directories be merged into a single > /rescue/? > > I notice following differences. Files and directories > that are in /stand/, but not in /rescue/: > > /rescue/-sh > /rescue/arp > /rescue/boot_crunch > /rescue/cpio > /rescue/find > /rescue/minigzip > /rescue/ppp > /rescue/sed > /rescue/sysinstall > /rescue/usbd > /rescue/usbdevs > /rescue/etc/ > /rescue/help/ > > Moreover, for those files that are in both, the > /stand/ > ones are obviously older than the ones (from cvsup > process) in /rescue/. > > Regards, > Rob. > > > > _______________________________ > Do you Yahoo!? > Declare Yourself - Register online to vote today! > http://vote.yahoo.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:10:26 2004 Return-Path: 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 90FB916A4D0 for ; Sun, 3 Oct 2004 20:10:26 +0000 (GMT) Received: from chatserv.de (p15119030.pureserver.info [217.160.175.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A21DA43D2F for ; Sun, 3 Oct 2004 20:10:23 +0000 (GMT) (envelope-from sascha@schumann.cx) Received: from lx.foo (chatserv [217.160.175.43]) by chatserv.de (Postfix) with ESMTP id 9ACD611009D for ; Sun, 3 Oct 2004 22:10:21 +0200 (CEST) Date: Sun, 3 Oct 2004 22:10:21 +0200 (CEST) From: Sascha Schumann X-X-Sender: sas@lx To: freebsd-current@freebsd.org In-Reply-To: <20041002210024.GA55807@xor.obsecurity.org> Message-ID: References: <20041002210024.GA55807@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:10:26 -0000 Just to give an update on our progress. db server: Was upgraded to RELENG_5 with conservative settings (no CPUTYPE, kernel config basically GENERIC except an increased MAXDSIZ). Worked ok until we put some load onto it. Crashed hard after about an hour of doing some work. www server: Booted cleanly into 5.3 kernel, but would not boot anymore after the following installworld. Deadlocks during boot with all tested kernels - even those from a 5.2 install medium and the previously successfully running 5.2.1 kernel. vga0: adv1: Invalid baseport of specified. Nearest etc. Both machines are 4xP4 Xeons with 4GB of RAM. If anyone is interested in details, let me know. - Sascha From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:28:13 2004 Return-Path: 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 E859F16A4CE for ; Sun, 3 Oct 2004 20:28:13 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51D4943D4C for ; Sun, 3 Oct 2004 20:28:13 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id B49A95313; Sun, 3 Oct 2004 22:28:11 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id DABC25312; Sun, 3 Oct 2004 22:28:04 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id B5894B860; Sun, 3 Oct 2004 22:28:04 +0200 (CEST) To: "Stephen J. Roznowski" References: <200410031812.i93IC79a000175@istari.comcast.net> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sun, 03 Oct 2004 22:28:04 +0200 In-Reply-To: <200410031812.i93IC79a000175@istari.comcast.net> (Stephen J. Roznowski's message of "Sun, 3 Oct 2004 14:12:06 -0400 (EDT)") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: freebsd-current@freebsd.org Subject: Re: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:28:14 -0000 "Stephen J. Roznowski" writes: > I'm trying to install 5.3-BETA6 onto an HP Presario SA4000Z. [AMD64 > using an nForce3 250 chipset]. I've also upgraded to RELENG_5 and the > problem remains. > > The network configures as "fwe0" and appears to have the correct IP > address, but if I attempt to ping the gateway, I get a "Host is down" > error. I've tried using "fwip0" instead, but I get the same error. fwe0 is the Firewire interface, not the Ethernet interface. The nVidia nForce3 Ethernet interface is not supported. David O'Brien apparently has a driver for it which he hasn't committed yet; you could ask him for the sources. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:32:18 2004 Return-Path: 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 BE8B016A4CE for ; Sun, 3 Oct 2004 20:32:18 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 900E443D1F for ; Sun, 3 Oct 2004 20:32:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DC49151491; Sun, 3 Oct 2004 13:33:18 -0700 (PDT) Date: Sun, 3 Oct 2004 13:33:18 -0700 From: Kris Kennaway To: Sascha Schumann Message-ID: <20041003203318.GA26177@xor.obsecurity.org> References: <20041002210024.GA55807@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Conclusion of thread "Deadlocks with recent SMP current"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:32:18 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 03, 2004 at 10:10:21PM +0200, Sascha Schumann wrote: > Just to give an update on our progress. >=20 > db server: Was upgraded to RELENG_5 with conservative > settings (no CPUTYPE, kernel config basically GENERIC except > an increased MAXDSIZ). Worked ok until we put some load onto > it. Crashed hard after about an hour of doing some work. >=20 > www server: Booted cleanly into 5.3 kernel, but would not > boot anymore after the following installworld. Deadlocks > during boot with all tested kernels - even those from a 5.2 > install medium and the previously successfully running 5.2.1 > kernel. =20 > =20 > vga0: > adv1: Invalid baseport of specified. Nearest etc. > >=20 > Both machines are 4xP4 Xeons with 4GB of RAM. If anyone is > interested in details, let me know. Yes, you'll need to provide actual details if you want someone to try to fix your problems. Kris --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYGIOWry0BWjoQKURArmUAKDAZeaaNPPyaG4HwMaW8it78fH1DACfVHLt vUYs4Q7s/ALKTqFzfRHbjh8= =jhKr -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:33:02 2004 Return-Path: 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 A904516A4CE for ; Sun, 3 Oct 2004 20:33:02 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7783C43D41 for ; Sun, 3 Oct 2004 20:33:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CBD7851491; Sun, 3 Oct 2004 13:34:02 -0700 (PDT) Date: Sun, 3 Oct 2004 13:34:02 -0700 From: Kris Kennaway To: Dag-Erling Sm?rgrav Message-ID: <20041003203402.GB26177@xor.obsecurity.org> References: <200410031812.i93IC79a000175@istari.comcast.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aVD9QWMuhilNxW9f" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: "Stephen J. Roznowski" Subject: Re: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:33:02 -0000 --aVD9QWMuhilNxW9f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 03, 2004 at 10:28:04PM +0200, Dag-Erling Sm?rgrav wrote: > "Stephen J. Roznowski" writes: > > I'm trying to install 5.3-BETA6 onto an HP Presario SA4000Z. [AMD64 > > using an nForce3 250 chipset]. I've also upgraded to RELENG_5 and the > > problem remains. > > > > The network configures as "fwe0" and appears to have the correct IP > > address, but if I attempt to ping the gateway, I get a "Host is down" > > error. I've tried using "fwip0" instead, but I get the same error. >=20 > fwe0 is the Firewire interface, not the Ethernet interface. The > nVidia nForce3 Ethernet interface is not supported. David O'Brien > apparently has a driver for it which he hasn't committed yet; you > could ask him for the sources. /usr/ports/net/nvnet? Kris --aVD9QWMuhilNxW9f Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYGI6Wry0BWjoQKURAvJOAKDmzlavohCjb6Omwynj1hd+NLnfhACeLNRu HFVop3eYpW4i24SIZ7ToBLU= =HOlQ -----END PGP SIGNATURE----- --aVD9QWMuhilNxW9f-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:51:13 2004 Return-Path: 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 F3B3E16A4CE for ; Sun, 3 Oct 2004 20:51:12 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id B74E843D2D for ; Sun, 3 Oct 2004 20:51:12 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 89E665313; Sun, 3 Oct 2004 22:51:11 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id A78EA5312; Sun, 3 Oct 2004 22:51:04 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 8360EB860; Sun, 3 Oct 2004 22:51:04 +0200 (CEST) To: Kris Kennaway References: <200410031812.i93IC79a000175@istari.comcast.net> <20041003203402.GB26177@xor.obsecurity.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sun, 03 Oct 2004 22:51:04 +0200 In-Reply-To: <20041003203402.GB26177@xor.obsecurity.org> (Kris Kennaway's message of "Sun, 3 Oct 2004 13:34:02 -0700") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: freebsd-current@freebsd.org cc: "Stephen J. Roznowski" Subject: Re: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:51:13 -0000 Kris Kennaway writes: > On Sun, Oct 03, 2004 at 10:28:04PM +0200, Dag-Erling Sm?rgrav wrote: > > fwe0 is the Firewire interface, not the Ethernet interface. The > > nVidia nForce3 Ethernet interface is not supported. David O'Brien > > apparently has a driver for it which he hasn't committed yet; you > > could ask him for the sources. > /usr/ports/net/nvnet? only works on i386. there are patches to make it work on amd64, but I've had no luck with them. David claimed in May to have an almost- finished nve(4) driver that worked on amd64. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 20:52:54 2004 Return-Path: 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 3563316A4CE for ; Sun, 3 Oct 2004 20:52:54 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id C45FE43D48 for ; Sun, 3 Oct 2004 20:52:52 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 78060 invoked by uid 89); 3 Oct 2004 20:52:51 -0000 Received: from unknown (HELO ?10.15.141.2?) (ares@max.af.czu.cz@217.11.239.237) by max.af.czu.cz with AES256-SHA encrypted SMTP; 3 Oct 2004 20:52:51 -0000 From: Tomas Randa To: freebsd-current@FreeBSD.ORG Content-Type: text/plain Message-Id: <1096836705.1446.4.camel@ares.office.internetservice.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 03 Oct 2004 22:51:45 +0200 Content-Transfer-Encoding: 7bit Subject: persisting ATA problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 20:52:54 -0000 Hi, I am running VIA8237 ata controller with BETA6 from 02.10.04 and in dmesg still have the following errors: ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=846959 I thing it will good with beta6, because some changes was made on ata, but not. Thanks for help. Tomas Randa From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 21:00:16 2004 Return-Path: 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 C1F3516A4CE for ; Sun, 3 Oct 2004 21:00:16 +0000 (GMT) Received: from update.ods.org (221056.ds.nac.net [66.246.72.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D22C43D5D for ; Sun, 3 Oct 2004 21:00:16 +0000 (GMT) (envelope-from jd@ods.org) Received: from localhost (221056.ds.nac.net [127.0.0.1]) by update.ods.org (Postfix) with ESMTP id 04DD11A524D for ; Sun, 3 Oct 2004 17:00:16 -0400 (EDT) Received: from update.ods.org ([127.0.0.1]) by localhost (update.ods.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96314-01 for ; Sun, 3 Oct 2004 17:00:15 -0400 (EDT) Received: from VPN-jd.ods.org (VPN-jd.ods.org [64.247.11.255]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by update.ods.org (Postfix) with ESMTP id 482F61A5245 for ; Sun, 3 Oct 2004 17:00:15 -0400 (EDT) Date: Sun, 03 Oct 2004 12:32:55 -0400 From: Jason DiCioccio To: freebsd-current@freebsd.org Message-ID: X-Mailer: Mulberry/3.1.3 (Linux/x86) Resent-Date: Sun, 03 Oct 2004 16:55:00 -0400 Resent-From: Jason DiCioccio Resent-To: freebsd-current@freebsd.org Resent-Message-ID: X-Resent-Mailer: Mulberry/3.1.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at ods.org Subject: Serial ATA, Write Caching and Soft-Updates X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 21:00:16 -0000 Greetings! I'm just asking this question mainly out of curiosity. However, I know that Serial ATA drives can support 'native command queuing' (an improved version of tagged command queuing apparently). As a result, are serial ATA drives safe to use in a soft-updates+write caching enabled setup? Do they suffer from the same write caching issues that the PATA drives suffered from? Thanks! -JD- From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 21:01:45 2004 Return-Path: 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 CC07316A4CE; Sun, 3 Oct 2004 21:01:45 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B1CE43D2D; Sun, 3 Oct 2004 21:01:45 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i93L1vFc009209; Sun, 3 Oct 2004 17:01:57 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i93L1uLD009208; Sun, 3 Oct 2004 17:01:56 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 3 Oct 2004 17:01:56 -0400 From: David Schultz To: Uwe Doering Message-ID: <20041003210156.GA9127@VARK.MIT.EDU> Mail-Followup-To: Uwe Doering , Takanori Watanabe , freebsd-fs@FreeBSD.ORG, bp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <41601BE0.4050401@geminix.org> <200410031805.i93I5JNZ009076@sana.init-main.com> <20041003183237.GA8100@VARK.MIT.EDU> <41605620.90407@geminix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41605620.90407@geminix.org> cc: freebsd-fs@FreeBSD.ORG cc: bp@FreeBSD.ORG cc: Takanori Watanabe cc: freebsd-current@FreeBSD.ORG Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 21:01:46 -0000 On Sun, Oct 03, 2004, Uwe Doering wrote: > David Schultz wrote: > >On Mon, Oct 04, 2004, Takanori Watanabe wrote: > > > >>>With 'unionfs' you can have underlying files from two different layers > >>>(upper and lower) on two different file systems which may, by > >>>coincidence, have the same inode number. Now, if you override the real > >>>va_fsid with that of the 'unionfs' mount you'll end up with two > >>>'unionfs' vnodes that appear to represent the same file (a hard link, > >>>for instance), but in reality the files are different entities. > >>>Obviously, both the kernel and applications might draw wrong conclusions > >>>in this case. > >> > >>I think the three filesystem entry > >>1. upper layer file > >>2. lower layer file > >>3. unionfs file > >>can be treated as different. > > > >I didn't pursue this before because I was concerned that it would > >introduce cache consistency issues between the union vnode and the > >underlying vnode. But I guess all vnops ultimately wind up at the > >underlying vnode, so this hopefully isn't an issue... > > Applications use the synthesized unionfs vnodes. They have no knowledge > of what's going on underneath. So they can't tell whether one unionfs > vnode refers to a file in the upper layer, and the other to one in the > lower layer. In my previous message I was confusing two issues, so please allow me to clarify. One issue is that NFS uses the fsid to look up vnodes, so it isn't clear to me what effect this change might have over NFS-exported unionfs mounts. (A while ago they didn't work anyway, but I thought that was fixed.) The other issue is cache coherency between the upper and lower vnodes, which I think unionfs gets wrong when mmap() is involved---I think it needs its own (get|put)pages() that proxy the request to the correct layer. From owner-freebsd-current@FreeBSD.ORG Sun Oct 3 21:22:17 2004 Return-Path: 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 29ECB16A4CE for ; Sun, 3 Oct 2004 21:22:17 +0000 (GMT) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 140F643D4C for ; Sun, 3 Oct 2004 21:22:16 +0000 (GMT) (envelope-from marcos@ThePacific.Net) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id i93LRacr031872 for ; Mon, 4 Oct 2004 10:29:57 +1300 Received: from [172.16.20.10] (gateway-nelson.thepacific.net [202.49.95.33]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id i93LLNjX028247 for ; Mon, 4 Oct 2004 10:21:24 +1300 Message-ID: <41606B0D.3070303@ThePacific.Net> Date: Mon, 04 Oct 2004 10:11:41 +1300 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040910) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: atheros frecuencies limited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Oct 2004 21:22:17 -0000 Hi There. We are legally abaible to run 14 channels on 2.4Ghz, but the Atheros driver on freebsd permit use only 11, I being trying to change the setup with the sysctl otions, nothing work. Same wireless card on diferent OS with diferent driver I can get all the channel. any ideas? cheers Marcos From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 00:12:16 2004 Return-Path: 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 A081D16A4CE; Mon, 4 Oct 2004 00:12:16 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 311E643D45; Mon, 4 Oct 2004 00:12:16 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i940CE7Z006641; Sun, 3 Oct 2004 20:12:14 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i940CEn8006638; Sun, 3 Oct 2004 20:12:14 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 3 Oct 2004 20:12:14 -0400 (EDT) From: Andre Guibert de Bruet To: current@freebsd.org Message-ID: <20041003200636.D90253@alpha.siliconlandmark.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1781484747-1096848734=:90253" X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: boris@freebsd.org Subject: [PATCH] contrib/smbfs/smbutil - 2 typos X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 00:12:16 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1781484747-1096848734=:90253 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Hi, Nothing big, just a couple of annoyances. I've copied boris@ on this email. Could this be committed? :) Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > --0-1781484747-1096848734=:90253 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="smbutil.typo.patch" Content-Transfer-Encoding: BASE64 Content-ID: <20041003201214.F90253@alpha.siliconlandmark.com> Content-Description: Content-Disposition: attachment; filename="smbutil.typo.patch" SW5kZXg6IHByaW50LmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBm aWxlOiAvaG9tZS9uY3ZzL3NyYy9jb250cmliL3NtYmZzL3NtYnV0aWwvcHJp bnQuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMS4xLjENCmRpZmYgLXUg LXIxLjEuMS4xIHByaW50LmMNCi0tLSBwcmludC5jCTE0IERlYyAyMDAxIDEx OjA2OjAzIC0wMDAwCTEuMS4xLjENCisrKyBwcmludC5jCTMgT2N0IDIwMDQg MjM6NTk6NDUgLTAwMDANCkBAIC0xNDUsNyArMTQ1LDcgQEANCiBwcmludF91 c2FnZSh2b2lkKQ0KIHsNCiAJcHJpbnRmKA0KLQkidXNhZ2U6IHNtYnV0aWwg cHJpbnQgW2Nvbm5lY3Rpb24gb3B0aW5vbnNdIC8vdXNlckBzZXJ2ZXIvc2hh cmVcbiINCisJInVzYWdlOiBzbWJ1dGlsIHByaW50IFtjb25uZWN0aW9uIG9w dGlvbnNdIC8vdXNlckBzZXJ2ZXIvc2hhcmVcbiINCiAJKTsNCiAJZXhpdCgx KTsNCiB9DQpJbmRleDogdmlldy5jDQo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvY29udHJpYi9zbWJmcy9zbWJ1 dGlsL3ZpZXcuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMS4xLjMNCmRp ZmYgLXUgLXIxLjEuMS4zIHZpZXcuYw0KLS0tIHZpZXcuYwkyMiBBcHIgMjAw MiAxNjoxNToyMCAtMDAwMAkxLjEuMS4zDQorKysgdmlldy5jCTMgT2N0IDIw MDQgMjM6NTk6NTcgLTAwMDANCkBAIC0xMzAsNyArMTMwLDcgQEANCiB2aWV3 X3VzYWdlKHZvaWQpDQogew0KIAlwcmludGYoDQotCSJ1c2FnZTogc21idXRp bCB2aWV3IFtjb25uZWN0aW9uIG9wdGlub25zXSAvL1t1c2VyQF1zZXJ2ZXJc biINCisJInVzYWdlOiBzbWJ1dGlsIHZpZXcgW2Nvbm5lY3Rpb24gb3B0aW9u c10gLy9bdXNlckBdc2VydmVyXG4iDQogCSk7DQogCWV4aXQoMSk7DQogfQ0K --0-1781484747-1096848734=:90253-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 00:19:42 2004 Return-Path: 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 2E5A716A4CE for ; Mon, 4 Oct 2004 00:19:42 +0000 (GMT) Received: from smtp.easystreet.com (smtp.easystreet.com [69.30.22.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E38F843D2F for ; Mon, 4 Oct 2004 00:19:39 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from [192.168.0.103] (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.easystreet.com (Postfix) with ESMTP id 95C7B36403F for ; Sun, 3 Oct 2004 17:19:39 -0700 (PDT) From: Eric Anholt To: current@FreeBSD.org Content-Type: text/plain Message-Id: <1096849178.859.45.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 03 Oct 2004 17:19:39 -0700 Content-Transfer-Encoding: 7bit Subject: Removing generic AGP options X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 00:19:42 -0000 I would like to remove the generic support from the various AGP drivers. These are the cases of matching the vendor and PCIC_BRIDGE || PCIS_BRIDGE_HOST with AGP capabilities. My reasoning is that, while we sometimes get lucky, most of the times it seems like the wrong type of AGP driver attaches, and people get unexplained hangs when doing "startx." One example would be myself with a new AMD64 system, where agp_via attached when agp_amd64 looks like what was necessary. I know we've had examples of this before with agp_amd, agp_via, and agp_intel in the past. Any opposition? I think most of our drivers have the PCI IDs they currently support anyway (I might check linux before making the change), so I don't think this would have much impact on current users. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 01:03:34 2004 Return-Path: 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 6D80616A4CE for ; Mon, 4 Oct 2004 01:03:34 +0000 (GMT) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5DAF43D2D for ; Mon, 4 Oct 2004 01:03:33 +0000 (GMT) (envelope-from patrick@137.org) Received: from morpheus.infiscape.com ([12.216.47.168]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20041004010332m9200atgkme>; Mon, 4 Oct 2004 01:03:32 +0000 Received: from dsl.80.187.networkiowa.com (dsl.80.187.networkiowa.com [209.234.80.187]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by morpheus.infiscape.com (Postfix) with ESMTP id DBB4D390014 for ; Sun, 3 Oct 2004 20:03:31 -0500 (CDT) From: Patrick Hartling To: freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RQqghuUyuTunfNoIn3LL" Date: Sun, 03 Oct 2004 20:02:15 -0500 Message-Id: <1096851735.869.18.camel@dsl.80.187.networkiowa.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: offsetof() macro, C++, and GCC 3.4.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 01:03:34 -0000 --=-RQqghuUyuTunfNoIn3LL Content-Type: multipart/mixed; boundary="=-9iN2Cm6WIjnvOh4dLc70" --=-9iN2Cm6WIjnvOh4dLc70 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable The offsetof() macro defined in stddef.h evaluates to code that can violate the C++ standard depending upon the context of its use. I have attached code that demonstrates the problem. GCC 3.4.2 in the base system refuses to compile the code, giving this error message: % g++ -c const-exp.cpp const-exp.cpp:14: error: a casts to a type other than an integral or enumeration type cannot appear in a constant-expression const-exp.cpp:14: error: '->' cannot appear in a constant-expression const-exp.cpp:14: error: `&' cannot appear in a constant-expression The gcc34 port (gcc-3.4.2_20040827) builds it just fine. The difference, as far as I can tell, is that gcc34 from the Ports Collection gets offsetof() from its own stddef.h, which has C++-friendly code: /* Offset of member MEMBER in a struct of type TYPE. */ #ifndef __cplusplus #define offsetof(TYPE, MEMBER) ((size_t) &((TYPE *)0)->MEMBER) #else /* The cast to "char &" below avoids problems with user-defined "operator &", which can appear in a POD type. */ #define offsetof(TYPE, MEMBER) \ (__offsetof__ (reinterpret_cast \ (&reinterpret_cast \ (static_cast (0)->MEMBER)))) #endif /* C++ */ Would fixing this problem be as simple as using the above code in /usr/include/stddef.h? The attached code was adapted from some very similar code in Boost.Python (from the file boost/python/object/instance.hpp), which does not compile with the base system GCC 3.4.2. There may be other parts of Boost 1.31.0--and the upcoming Boost 1.32.0--that are affected by this offsetof() problem. -Patrick --=20 Patrick L. Hartling | Research Assistant, VRAC http://www.137.org/patrick/ | 2274 Howe Hall Room 2624 PGP: http://tinyurl.com/2oum9 | http://www.vrac.iastate.edu/ --=-9iN2Cm6WIjnvOh4dLc70-- --=-RQqghuUyuTunfNoIn3LL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBYKEXwZ1qaMh08hcRAhwlAKCiR2TrPIqyH/2a5Vlgsxqrl6pdkQCePMU6 QTKIKSzrRLiajgxLWdKTiJQ= =bEPg -----END PGP SIGNATURE----- --=-RQqghuUyuTunfNoIn3LL-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 01:26:35 2004 Return-Path: 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 4BB3216A4CE for ; Mon, 4 Oct 2004 01:26:35 +0000 (GMT) Received: from fed1rmmtao02.cox.net (fed1rmmtao02.cox.net [68.230.241.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 181D443D48 for ; Mon, 4 Oct 2004 01:26:35 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by fed1rmmtao02.cox.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041004012633.KHLZ26240.fed1rmmtao02.cox.net@mezz.mezzweb.com> for ; Sun, 3 Oct 2004 21:26:33 -0400 Date: Sun, 03 Oct 2004 20:26:49 -0500 To: freebsd-current@freebsd.org References: <200410031812.i93IC79a000175@istari.comcast.net> <20041003203402.GB26177@xor.obsecurity.org> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20041003203402.GB26177@xor.obsecurity.org> User-Agent: Opera M2/7.54 (Linux, build 751) Subject: Re: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 01:26:35 -0000 Resend, but only to freebsd-current. Somehow, my client has dropped freebsd-current from the CC. On Sun, 3 Oct 2004 13:34:02 -0700, Kris Kennaway wrote: > On Sun, Oct 03, 2004 at 10:28:04PM +0200, Dag-Erling Sm?rgrav wrote: >> "Stephen J. Roznowski" writes: >> > I'm trying to install 5.3-BETA6 onto an HP Presario SA4000Z. [AMD64 >> > using an nForce3 250 chipset]. I've also upgraded to RELENG_5 and the >> > problem remains. >> > >> > The network configures as "fwe0" and appears to have the correct IP >> > address, but if I attempt to ping the gateway, I get a "Host is down" >> > error. I've tried using "fwip0" instead, but I get the same error. >> >> fwe0 is the Firewire interface, not the Ethernet interface. The >> nVidia nForce3 Ethernet interface is not supported. David O'Brien >> apparently has a driver for it which he hasn't committed yet; you >> could ask him for the sources. Just wondering if it includes PCI/SMBus? I have nForce2 MCP chipest (not AMD64, just i386) with Gigabit Ethernet, so hope his driver will working on nForce2 as I don't mind to test it if it will working with nForce2. > /usr/ports/net/nvnet? The problem with nvnet is that... It's very out of date. The author of nvnet or whomever (programmer) will have to update to match nvidia.com's newer nForce driver for add more IDs and might (not sure) require update some more codes than just IDs. Cheers, Mezz > Kris -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 01:42:34 2004 Return-Path: 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 4732B16A4CE; Mon, 4 Oct 2004 01:42:34 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC82943D1F; Mon, 4 Oct 2004 01:42:33 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id i941gWqg049017; Sun, 3 Oct 2004 21:42:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id i941gWKk081772; Sun, 3 Oct 2004 21:42:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id CFD027303F; Sun, 3 Oct 2004 21:42:32 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041004014232.CFD027303F@freebsd-current.sentex.ca> Date: Sun, 3 Oct 2004 21:42:32 -0400 (EDT) Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 01:42:34 -0000 TB --- 2004-10-04 00:29:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-10-04 00:29:54 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2004-10-04 00:29:54 - checking out the source tree TB --- 2004-10-04 00:29:54 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2004-10-04 00:29:54 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-10-04 00:35:36 - building world (CFLAGS=-O2 -pipe) TB --- 2004-10-04 00:35:36 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2004-10-04 00:35:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpfs/dumpfs.c (cd /tinderbox/CURRENT/ia64/ia64/src/rescue/rescue/../../sbin/dumpon && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE depend && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE dumpon.o) rm -f .depend mkdep -f .depend -a -DRESCUE /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpon/dumpon.c echo dumpon: /home/tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/i386/usr/lib/libc.a >> .depend cc -O2 -pipe -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpon/dumpon.c /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpon/dumpon.c: In function `check_size': /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpon/dumpon.c:82: warning: comparison between signed and unsigned *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src/sbin/dumpon. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2004-10-04 01:42:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-10-04 01:42:32 - ERROR: failed to build world TB --- 2004-10-04 01:42:32 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 02:20:23 2004 Return-Path: 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 601DC16A4CE for ; Mon, 4 Oct 2004 02:20:23 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B239B43D31 for ; Mon, 4 Oct 2004 02:20:22 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i942Irrr082647; Sun, 3 Oct 2004 20:18:53 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 Oct 2004 20:20:26 -0600 (MDT) Message-Id: <20041003.202026.127179512.imp@bsdimp.com> To: marcos@ThePacific.Net From: "M. Warner Losh" In-Reply-To: <41606B0D.3070303@ThePacific.Net> References: <41606B0D.3070303@ThePacific.Net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: atheros frecuencies limited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 02:20:23 -0000 In message: <41606B0D.3070303@ThePacific.Net> "Marcos Biscaysaqu - ThePacific.net" writes: : We are legally abaible to run 14 channels on 2.4Ghz, but the Atheros : driver on freebsd permit use only 11, I being trying to change the setup : with the sysctl otions, nothing work. Same wireless card on diferent : OS with diferent driver I can get all the channel. : any ideas? Did you buy the wireless card in a regulatory domain that only allows 11 channels? The atheros cards have the reg dom burned into their flash. Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 02:39:08 2004 Return-Path: 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 3765416A4CE; Mon, 4 Oct 2004 02:39:08 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D9343D1D; Mon, 4 Oct 2004 02:39:07 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id i942d7UB027248; Sun, 3 Oct 2004 22:39:07 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id i942d6JL003054; Sun, 3 Oct 2004 22:39:06 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 048F37303F; Sun, 3 Oct 2004 22:39:06 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041004023906.048F37303F@freebsd-current.sentex.ca> Date: Sun, 3 Oct 2004 22:39:06 -0400 (EDT) Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 02:39:08 -0000 TB --- 2004-10-04 01:42:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-10-04 01:42:32 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-10-04 01:42:33 - checking out the source tree TB --- 2004-10-04 01:42:33 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2004-10-04 01:42:33 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-10-04 01:48:38 - building world (CFLAGS=-O2 -pipe) TB --- 2004-10-04 01:48:38 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-10-04 01:48:38 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpfs/dumpfs.c (cd /tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue/../../sbin/dumpon && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE depend && /usr/bin/make -DRESCUE CRUNCH_CFLAGS=-DRESCUE dumpon.o) rm -f .depend mkdep -f .depend -a -DRESCUE /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpon/dumpon.c echo dumpon: /home/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/lib/libc.a >> .depend cc -O2 -pipe -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpon/dumpon.c /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpon/dumpon.c: In function `check_size': /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpon/dumpon.c:82: warning: comparison between signed and unsigned *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/sbin/dumpon. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src/rescue. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-10-04 02:39:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-10-04 02:39:06 - ERROR: failed to build world TB --- 2004-10-04 02:39:06 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 02:58:14 2004 Return-Path: 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 BB12516A4CE; Mon, 4 Oct 2004 02:58:14 +0000 (GMT) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AEB943D2F; Mon, 4 Oct 2004 02:58:14 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from tomcat.kitchenlab.org (adsl-64-142-31-107.sonic.net [64.142.31.107]) by b.mail.sonic.net (8.12.11/8.12.11) with ESMTP id i942wDZp023667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 3 Oct 2004 19:58:13 -0700 Received: from tomcat.kitchenlab.org (localhost.kitchenlab.org [127.0.0.1]) by tomcat.kitchenlab.org (8.13.1/8.13.1) with ESMTP id i942wD4e001939; Sun, 3 Oct 2004 19:58:13 -0700 (PDT) (envelope-from bmah@freebsd.org) Received: (from bmah@localhost) by tomcat.kitchenlab.org (8.13.1/8.13.1/Submit) id i942wDOs001938; Sun, 3 Oct 2004 19:58:13 -0700 (PDT) (envelope-from bmah@freebsd.org) X-Authentication-Warning: tomcat.kitchenlab.org: bmah set sender to bmah@freebsd.org using -f Date: Sun, 3 Oct 2004 19:58:13 -0700 From: "Bruce A. Mah" To: freebsd-current@freebsd.org Message-ID: <20041004025813.GA1912@tomcat.kitchenlab.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-url: http://www.employees.org/~bmah/ User-Agent: Mutt/1.5.6i cc: bmah@freebsd.org Subject: 5.3-BETA6 boot-time hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 02:58:14 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I just updated a RELENG_5 system from sometime around 5.3-BETA4 (17 September) to very late 5.3-BETA6 (just before the 5.3-BETA7 version number bump) and it's now hanging after probing its DVD drive. This problem sounds vaguely like what was described in the thread "ATTN Soren: BETA3 still hangs on ATAPI DVD Detection during boot": http://lists.freebsd.org/pipermail/freebsd-current/2004-September/036543.ht= ml The interesting thing is that my system appeared to be working just fine with the BETA4 code. I've appended verbose boot output from BETA4, as well as the lines that I think were relevant from a BETA6 boot, at least up to the point where it hung. The latter output is hand-copied. The system isn't totally wedged because I can page back through the console's scrollback buffer, but the kernel just doesn't seem to finish probing and attaching devices. I tried disabling ATAPI DMA as Soren suggested in the thread above by setting hw.ata.atapi_dma=3D0 from the loader; this seemed to have no effect. I tried backing out the ata driver updates from 30 September to see if that might help matters, but it didn't seem to help. Neither did booting the kernel from the 5.3-BETA6 bootonly iso image; that hangs in exactly the same way. At this point I'm kind of flailing around at random. At first I had suspected the ata(4) driver but the evidence I've seen so far doesn't really point in that direction. Any ideas? Thanks for any suggestions! Bruce. ----- (5.3-BETA4 boot. This kernel was built from source shortly before 5.3-BETA= 5.) FreeBSD 5.3-BETA4 #4: Fri Sep 17 13:00:00 PDT 2004 root@tomcat.kitchenlab.org:/usr/obj/usr/src/sys/NIMITZ5 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a37000. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc0a37228. Preloaded elf module "/boot/kernel/sound.ko" at 0xc0a372d4. Preloaded elf module "/boot/kernel/uvisor.ko" at 0xc0a37380. Preloaded elf module "/boot/kernel/ucom.ko" at 0xc0a3742c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a374d8. Calibrating clock(s) ... i8254 clock: 1193183 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 996749528 Hz CPU: Intel Pentium III (996.75-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x68a Stepping =3D 10 Features=3D0x383f9ff real memory =3D 535691264 (510 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c29000 - 0x000000001f5b4fff, 513327104 bytes (125324 pages) avail memory =3D 514519040 (490 MB) bios32: Found BIOS32 Service Directory header at 0xc00fdad0 bios32: Entry =3D 0xfdae0 (c00fdae0) Rev =3D 0 Len =3D 1 pcibios: PCI BIOS entry at 0xf0000+0xdb01 pnpbios: Found PnP BIOS data at 0xc00f6830 pnpbios: Entry =3D f0000:5834 Rev =3D 1.0 Other BIOS signatures found: wlan: <802.11 Link Layer> random: io: mem: Pentium Pro MTRR support enabled null: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=3D0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there (id=3D11308086) pcibios: BIOS version 2.10 Found $PIR table, 8 entries at 0xc00f6e20 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 1 A 0x60 3 4 5 7 9 10 11 12 14 15 embedded 0 1 B 0x61 3 4 5 7 9 10 11 12 14 15 embedded 0 2 A 0x60 3 4 5 7 9 10 11 12 14 15 embedded 0 31 A 0xfe 14 embedded 0 31 B 0x61 3 4 5 7 9 10 11 12 14 15 embedded 0 31 C 0x6b 3 4 5 7 9 10 11 12 14 15 embedded 0 31 D 0x63 3 4 5 7 9 10 11 12 14 15 slot 1 1 3 A 0x61 4 5 6 7 9 10 11 12 14 slot 1 1 3 B 0x62 4 5 6 7 9 10 11 12 14 slot 1 1 3 C 0x63 4 5 6 7 9 10 11 12 14 slot 1 1 3 D 0x60 4 5 6 7 9 10 11 12 14 slot 2 1 4 A 0x61 4 5 6 7 9 10 11 12 14 slot 2 1 4 B 0x62 4 5 6 7 9 10 11 12 14 slot 2 1 4 C 0x63 4 5 6 7 9 10 11 12 14 slot 2 1 4 D 0x60 4 5 6 7 9 10 11 12 14 slot 3 1 5 A 0x61 4 5 6 7 9 10 11 12 14 slot 3 1 5 B 0x62 4 5 6 7 9 10 11 12 14 slot 3 1 5 C 0x63 4 5 6 7 9 10 11 12 14 slot 3 1 5 D 0x60 4 5 6 7 9 10 11 12 14 embedded 1 2 A 0x60 4 5 6 7 9 10 11 12 14 embedded 1 2 B 0x61 4 5 6 7 9 10 11 12 14 embedded 1 8 A 0x68 4 5 6 7 9 10 11 12 14 AcpiOsDerivePciId: bus 1 dev 2 func 0 AcpiOsDerivePciId: bus 1 dev 2 func 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 ACPI timer looks GOOD min =3D 2, max =3D 3, width =3D 1 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 unknown: not probed (disabled) unknown: not probed (disabled) cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI PCI link initial configuration: \\_SB_.LNKB irq 0: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 0.3= 1.1 \\_SB_.LNKH irq 0: [ 4 5 6 7 9 10 11 12 14] 10+ low,level,sharable 0.3= 1.2 \\_SB_.LNKD irq 0: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 0.3= 1.3 \\_SB_.LNKA irq 0: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 0.1= =2E0 \\_SB_.LNKB irq 0: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 0.1= =2E1 \\_SB_.LNKC irq 0: [ 4 5 6 7 9 10 11 12 14] 0+ low,level,sharable 0.1= =2E2 \\_SB_.LNKD irq 0: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 0.1= =2E3 \\_SB_.LNKA irq 0: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 0.2= =2E0 \\_SB_.LNKB irq 0: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 0.2= =2E1 \\_SB_.LNKC irq 0: [ 4 5 6 7 9 10 11 12 14] 0+ low,level,sharable 0.2= =2E2 \\_SB_.LNKD irq 0: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 0.2= =2E3 pci0: on pcib0 pci0: physical bus=3D0 found-> vendor=3D0x8086, dev=3D0x1130, revid=3D0x02 bus=3D0, slot=3D0, func=3D0 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0106, statreg=3D0x2090, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) map[10]: type 3, range 32, base e8000000, size 26, enabled map[14]: type 1, range 32, base eff80000, size 19, enabled pcib0: matched entry for 0.2.INTA (src \\_SB_.LNKA) pcib0: possible interrupts: 4 5 6 7 9 10 11 12 14 ACPI PCI link arbitrated settings: \\_SB_.LNKB (references 3, priority 23716): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 110 110 160 220 5110 5110 5110 5110 50110 \\_SB_.LNKD (references 3, priority 23716): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 110 110 160 220 5110 5110 5110 5110 50110 \\_SB_.LNKA (references 2, priority 15811): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 110 110 160 220 5110 5110 5110 5110 50110 \\_SB_.LNKC (references 2, priority 15811): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 110 110 160 220 5110 5110 5110 5110 50110 \\_SB_.LNKH (references 1, priority 7905): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 110 110 160 220 5110 5110 5110 5110 50110 pcib0: slot 2 INTA routed to irq 9 via \\_SB_.LNKA found-> vendor=3D0x8086, dev=3D0x1132, revid=3D0x02 bus=3D0, slot=3D2, func=3D0 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x02b0, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D9 powerspec 2 supports D0 D3 current D0 found-> vendor=3D0x8086, dev=3D0x244e, revid=3D0x11 bus=3D0, slot=3D30, func=3D0 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0107, statreg=3D0x0080, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x06 (1500 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0x2440, revid=3D0x11 bus=3D0, slot=3D31, func=3D0 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x000f, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=3D0x8086, dev=3D0x244b, revid=3D0x11 bus=3D0, slot=3D31, func=3D1 class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) map[20]: type 4, range 32, base 0000cc00, size 5, enabled pcib0: matched entry for 0.31.INTD (src \\_SB_.LNKD) pcib0: possible interrupts: 4 5 6 7 9 10 11 12 14 ACPI PCI link arbitrated settings: \\_SB_.LNKB (references 3, priority 24090): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 220 240 270 440 5220 5220 5220 5220 50220 \\_SB_.LNKD (references 3, priority 24090): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 220 240 270 440 5220 5220 5220 5220 50220 \\_SB_.LNKC (references 2, priority 16060): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 220 240 270 440 5220 5220 5220 5220 50220 \\_SB_.LNKH (references 1, priority 8030): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 220 240 270 440 5220 5220 5220 5220 50220 pcib0: slot 31 INTD routed to irq 5 via \\_SB_.LNKD found-> vendor=3D0x8086, dev=3D0x2442, revid=3D0x11 bus=3D0, slot=3D31, func=3D2 class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Dd, irq=3D5 map[20]: type 4, range 32, base 00000540, size 4, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.LNKB) pcib0: possible interrupts: 4 5 6 7 9 10 11 12 14 ACPI PCI link arbitrated settings: \\_SB_.LNKB (references 3, priority 24466): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 330 350 410 660 5330 5330 5330 5330 50330 \\_SB_.LNKC (references 2, priority 16311): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 330 350 410 660 5330 5330 5330 5330 50330 \\_SB_.LNKH (references 1, priority 8155): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 330 350 410 660 5330 5330 5330 5330 50330 pcib0: slot 31 INTB routed to irq 11 via \\_SB_.LNKB found-> vendor=3D0x8086, dev=3D0x2443, revid=3D0x11 bus=3D0, slot=3D31, func=3D3 class=3D0c-05-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0001, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Db, irq=3D11 map[20]: type 4, range 32, base 0000d400, size 5, enabled pcib0: matched entry for 0.31.INTC (src \\_SB_.LNKH) pcib0: possible interrupts: 4 5 6 7 9 10 11 12 14 ACPI PCI link arbitrated settings: \\_SB_.LNKC (references 2, priority 16562): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 440 460 520 910 5440 5440 5440 5440 50440 \\_SB_.LNKH (references 1, priority 8281): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 440 460 520 910 5440 5440 5440 5440 50440 pcib0: slot 31 INTC routed to irq 10 via \\_SB_.LNKH found-> vendor=3D0x8086, dev=3D0x2444, revid=3D0x11 bus=3D0, slot=3D31, func=3D4 class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Dc, irq=3D10 map[10]: type 4, range 32, base 0000dc00, size 8, enabled map[14]: type 4, range 32, base 0000d800, size 6, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.LNKB) pcib0: slot 31 INTB is already routed to irq 11 found-> vendor=3D0x8086, dev=3D0x2445, revid=3D0x11 bus=3D0, slot=3D31, func=3D5 class=3D04-01-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Db, irq=3D11 agp0: mem 0xeff80000-0xefffffff,0= xe8000000-0xebffffff irq 9 at device 2.0 on pci0 agp0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xe8000000 agp0: Reserved 0x80000 bytes for rid 0x14 type 3 at 0xeff80000 pcib1: at device 30.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xa000-0xafff pcib1: memory decode 0xefd00000-0xefdfffff pcib1: prefetched decode 0xe7b00000-0xe7bfffff pcib1: Subtractively decoded bridge. ACPI PCI link initial configuration: \\_SB_.LNKB irq*11: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 1.3= =2E0 \\_SB_.LNKC irq 0: [ 4 5 6 7 9 10 11 12 14] 0+ low,level,sharable 1.3= =2E1 \\_SB_.LNKD irq* 5: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 1.3= =2E2 \\_SB_.LNKA irq* 9: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 1.3= =2E3 \\_SB_.LNKC irq 0: [ 4 5 6 7 9 10 11 12 14] 0+ low,level,sharable 1.4= =2E0 \\_SB_.LNKD irq* 5: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 1.4= =2E1 \\_SB_.LNKA irq* 9: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 1.4= =2E2 \\_SB_.LNKB irq*11: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 1.4= =2E3 \\_SB_.LNKD irq* 5: [ 4 5 6 7 9 10 11 12 14] 5+ low,level,sharable 1.5= =2E0 \\_SB_.LNKA irq* 9: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 1.5= =2E1 \\_SB_.LNKB irq*11: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 1.5= =2E2 \\_SB_.LNKC irq 0: [ 4 5 6 7 9 10 11 12 14] 0+ low,level,sharable 1.5= =2E3 \\_SB_.LNKA irq* 9: [ 4 5 6 7 9 10 11 12 14] 9+ low,level,sharable 1.2= =2E0 \\_SB_.LNKB irq*11: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 1.2= =2E1 \\_SB_.LNKE irq 0: [ 4 5 6 7 9 10 11 12 14] 11+ low,level,sharable 1.8= =2E0 pci1: on pcib1 pci1: physical bus=3D1 map[10]: type 1, range 32, base 00000000, size 12, enabled found-> vendor=3D0x104c, dev=3D0xac41, revid=3D0x02 bus=3D1, slot=3D2, func=3D0 class=3D06-07-00, hdrtype=3D0x02, mfdev=3D1 cmdreg=3D0x0007, statreg=3D0x0210, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0xc0 (48000 ns), maxlat=3D0x04 (1000 ns) intpin=3Da, irq=3D255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base efdff800, size 11, enabled pcib1: device (null) requested decoded memory range 0xefdff800-0xefdfffff map[14]: type 1, range 32, base efdf8000, size 14, enabled pcib1: device (null) requested decoded memory range 0xefdf8000-0xefdfbfff pcib1: matched entry for 1.2.INTB (src \\_SB_.LNKB) pcib1: slot 2 INTB is already routed to irq 11 found-> vendor=3D0x104c, dev=3D0x8017, revid=3D0x02 bus=3D1, slot=3D2, func=3D1 class=3D0c-00-10, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0116, statreg=3D0x0210, cachelnsz=3D8 (dwords) lattimer=3D0x40 (1920 ns), mingnt=3D0x02 (500 ns), maxlat=3D0x04 (1000 ns) intpin=3Db, irq=3D11 powerspec 1 supports D0 D2 D3 current D0 map[10]: type 1, range 32, base efdfe000, size 12, enabled pcib1: device (null) requested decoded memory range 0xefdfe000-0xefdfefff map[14]: type 4, range 32, base 0000ac00, size 6, enabled pcib1: device (null) requested decoded I/O range 0xac00-0xac3f pcib1: matched entry for 1.8.INTA (src \\_SB_.LNKE) pcib1: possible interrupts: 4 5 6 7 9 10 11 12 14 ACPI PCI link arbitrated settings: \\_SB_.LNKC (references 5, priority 42911): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 750 760 820 1210 5740 5740 5740 5740 50740 \\_SB_.LNKE (references 1, priority 8582): interrupts: 10 9 5 11 12 7 6 4 14 penalty: 750 760 820 1210 5740 5740 5740 5740 50740 pcib1: slot 8 INTA routed to irq 11 via \\_SB_.LNKE found-> vendor=3D0x8086, dev=3D0x2449, revid=3D0x03 bus=3D1, slot=3D8, func=3D0 class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0117, statreg=3D0x0290, cachelnsz=3D8 (dwords) lattimer=3D0x40 (1920 ns), mingnt=3D0x08 (2000 ns), maxlat=3D0x38 (14000 n= s) intpin=3Da, irq=3D11 powerspec 2 supports D0 D1 D2 D3 current D0 cbb0: at device 2.0 on pci1 pcib1: device cbb0 requested decoded memory range 0xefd00000-0xefdfffff cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xefd00000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib1: matched entry for 1.2.INTA (src \\_SB_.LNKA) pcib1: slot 2 INTA is already routed to irq 9 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0xac41104c 0x02100007 0x06070002 0x00822000=20 0x10: 0xefd00000 0x020000a0 0x20030201 0xfffff000=20 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc=20 0x30: 0x00000000 0xfffffffc 0x00000000 0x04400109=20 0x40: 0x89a71509 0x00000001 0x00000000 0x00000000=20 0x50: 0x00000000 0x00000000 0x00000000 0x00000000=20 0x60: 0x00000000 0x00000000 0x00000000 0x00000000=20 0x70: 0x00000000 0x00000000 0x00000000 0x00000000=20 0x80: 0x08249060 0x00000400 0x00000000 0x00001000=20 0x90: 0x216400c0 0x00000000 0x00000000 0x00000000=20 0xa0: 0xfe110001 0x00c00100 0x0000000a 0x0000001f=20 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000=20 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000=20 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000=20 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000=20 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000=20 fwohci0: mem 0xefdf8000-0xefdfbfff,0xefdff800-= 0xefdfffff irq 11 at device 2.1 on pci1 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xefdff800 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:40:ca:07:02:00:53:e4 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:40:ca:00:53:e4 fwe0: bpf attached fwe0: Ethernet address: 02:40:ca:00:53:e4 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=3D0xc800ffc0, gen=3D1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me) firewire0: bus manager 0 (me) fxp0: port 0xac00-0xac3f mem = 0xefdfe000-0xefdfefff irq 11 at device 8.0 on pci1 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xefdfe000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 2449 8086 3013 0003 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:40:ca:28:84:c9 fxp0: [MPSAFE] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x1= 77,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D00 ata0-master: stat=3D0x90 err=3D0x90 lsb=3D0x90 msb=3D0x90 ata0-master: stat=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata0-slave: stat=3D0x00 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata0: reset tp2 stat0=3D50 stat1=3D00 devices=3D0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D01 ata1-master: stat=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata1-slave: stat=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00 ata1: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x4 ata1: [MPSAFE] uhci0: port 0xcc00-0xcc1f i= rq 5 at device 31.2 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xcc00 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 31.3 (no driver attached) uhci1: port 0xd400-0xd41f i= rq 10 at device 31.4 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd400 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: port 0xd800-0xd83f,0xdc00-0xdcff irq 11 at dev= ice 31.5 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xdc00 pcm0: Reserved 0x40 bytes for rid 0x14 type 4 at 0xd800 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features headphone, 20 bit DAC, 18 bit ADC, 6 bit master volume= , Crystal Semi 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, AMAP pcm0: sndbuf_setmap 1f07e000, 4000; 0xd96c1000 -> 1f07e000 pcm0: sndbuf_setmap 1f074000, 4000; 0xd96c5000 -> 1f074000 acpi_button0: on acpi0 unknown: not probed (disabled) psmcpnp0 irq 12 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 dr= q 2 on acpi0 fdc0: output ready timeout fdc0: cmd 3 failed at out byte 1 of 3 device_attach: fdc0 attach returned 6 sio0: irq maps: 0x801 0x811 0x801 0x801 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A unknown: not probed (disabled) ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 dr= q 2 on acpi0 fdc0: output ready timeout fdc0: cmd 3 failed at out byte 1 of 3 device_attach: fdc0 attach returned 6 unknown: not probed (disabled) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ex_isa_identify() unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ahc_isa_probe 10: ioport 0xac00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xe0000-0xe0fff,0xc0000-0xcbfff on isa0 pmtimer0 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x801 0x801 0x801 0x801 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81=20 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96=20 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c=20 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff=20 vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. procfs registered Timecounter "TSC" frequency 996749528 Hz quality 800 Timecounters tick every 10.000 msec lo0: bpf attached cpu0: set speed to 100.0% acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ata0-master: pio=3D0x0c wdma=3D0x22 udma=3D0x45 cable=3D80pin ata0-master: setting PIO4 on Intel ICH2 chip ata0-master: setting UDMA100 on Intel ICH2 chip ad0: ATA-6 disk at ata0-master ad0: 114473MB (234441648 sectors), 232581 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ar: FreeBSD check1 failed ata1-master: pio=3D0x0c wdma=3D0x22 udma=3D0x42 cable=3D40pin ATAPI_RESET time =3D 670us ata1-master: setting PIO4 on Intel ICH2 chip ata1-master: setting UDMA33 on Intel ICH2 chip acd0: DVDR drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 4133KB/s (4133KB/s), 2048KB buffer, UD= MA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, DVDR, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 47998 Hz, will use 48000 Hz [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:167766732 [1] f:00 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:167766795 l:666697= 50 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 85896566784 end 85896599039 GEOM: Configure ad0s2, start 85896599040 length 34134912000 end 120031511039 GEOM: Configure ad0s1a, start 0 length 536870912 end 536870911 GEOM: Configure ad0s1b, start 536870912 length 1073741824 end 1610612735 GEOM: Configure ad0s1c, start 0 length 85896566784 end 85896566783 GEOM: Configure ad0s1d, start 1610612736 length 1073741824 end 2684354559 GEOM: Configure ad0s1e, start 2684354560 length 21474836480 end 24159191039 GEOM: Configure ad0s1f, start 24159191040 length 21474836480 end 45634027519 GEOM: Configure ad0s1g, start 45634027520 length 40262539264 end 85896566783 GEOM: Configure ad0s2a, start 0 length 536870912 end 536870911 GEOM: Configure ad0s2c, start 0 length 34134912000 end 34134911999 GEOM: Configure ad0s2e, start 536870912 length 1073741824 end 1610612735 GEOM: Configure ad0s2f, start 1610612736 length 1073741824 end 2684354559 GEOM: Configure ad0s2g, start 2684354560 length 21474836480 end 24159191039 GEOM: Configure ad0s2h, start 24159191040 length 9975720960 end 34134911999 (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error (probe1:ata0:0:1:0): error 22 (probe1:ata0:0:1:0): Unretryable Error (probe3:ata1:0:1:0): error 22 (probe3:ata1:0:1:0): Unretryable Error (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error (probe1:ata0:0:1:0): error 22 (probe1:ata0:0:1:0): Unretryable Error (probe3:ata1:0:1:0): error 22 (probe3:ata1:0:1:0): Unretryable Error (probe2:ata1:0:0:0): error 6 (probe2:ata1:0:0:0): Unretryable Error (probe6:sbp0:0:2:0): error 22 (probe6:sbp0:0:2:0): Unretryable Error (probe7:sbp0:0:3:0): error 22 (probe7:sbp0:0:3:0): Unretryable Error (probe8:sbp0:0:4:0): error 22 (probe8:sbp0:0:4:0): Unretryable Error (probe9:sbp0:0:5:0): error 22 (probe9:sbp0:0:5:0): Unretryable Error (probe10:sbp0:0:6:0): error 22 (probe10:sbp0:0:6:0): Unretryable Error (probe4:sbp0:0:0:0): error 22 (probe4:sbp0:0:0:0): Unretryable Error (probe5:sbp0:0:1:0): error 22 (probe5:sbp0:0:1:0): Unretryable Error pass0 at ata1 bus 0 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device=20 pass0: Serial Number 3 pass0: 33.000MB/s transfers GEOM: new disk cd0 (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device=20 cd0: Serial Number 3 cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - t= ray closed (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error (cd0:ata1:0:0:0): error 6 (cd0:ata1:0:0:0): Unretryable Error Mounting root from ufs:/dev/ad0s1a start_init: trying /sbin/init Linux ELF exec handler installed linprocfs registered splash: image decoder found: logo_saver ----- (Selected lines from 5.3-BETA6 kernel, built just prior to 5.3-BETA7 version bump. Copied by hand.) atapci0: port 0xffa0-0xffaf,0x376,0x170-0x1= 77,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid0x20 type 4 at 0xffa0 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D00 ata0-master: stat 0x90 err=3D0x90 lsb=3D0x90 msb=3D0x90 ata0-master: stat=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata0-slave: stat=3D0x00 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata0: reset tp2 stat0=3D50 stat1=3D00 devices=3D0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapi0: Reserved 0x08 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D01 ata1-master: stat=3D0x00 err=3D0x01 lsb=3D0x14 msb=3D0xeb ata1-slave: stat=3D0x00 err=3D0x00 lsb=3D0x00 msb=3D0x00 ata1: reset tp2 stat0=3D00 stat1=3D00 devices=3D0x4 ata1: [MPSAFE] ata0-master: pio=3D0x0c wdma=3D0x22 udma=3D0x45 cable=3D80pin ata0-master: setting PIO4 on Intel ICH2 chip ata0-master: setting UDMA100 on Intel ICH2 chip ad0: ATA-6 disk at ata0-master ad0: 114473MB (234441648 sectors), 232581 C, 16 H, 63 S, 512B ad0: 16 secs/int, 1 depth queue, UDMA100 ar: FreeBSD check1 failed ata1-master: pio=3D0x0c wdma=3D0x22 udma=3D0x42 cable=3D40pin ata1-master: setting PIO4 on Intel ICH2 chip ata1-master: setting UDMA33 on Intel ICH2 chip acd0: DVDR drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 4133KB/s (4133KB/s), 2048KB buffer, UD= MA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, DVDR, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disk --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYLxF2MoxcVugUsMRAu82AJ4j/dWZImJjVBDRjeVN+yDAh8NpnwCgt/LU ns5A2jPpD+7U2atUGPhqqqM= =U4d3 -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 03:54:54 2004 Return-Path: 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 DBA9A16A4CE for ; Mon, 4 Oct 2004 03:54:54 +0000 (GMT) Received: from ms-smtp-01.rdc-nyc.rr.com (ms-smtp-01-smtplb.rdc-nyc.rr.com [24.29.109.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31A1B43D1D for ; Mon, 4 Oct 2004 03:54:54 +0000 (GMT) (envelope-from ntwrkguy2000@nyc.rr.com) Received: from laptop (66-108-196-196.nyc.rr.com [66.108.196.196]) i943sS6n007851 for ; Sun, 3 Oct 2004 23:54:51 -0400 (EDT) Message-Id: <200410040354.i943sS6n007851@ms-smtp-01.rdc-nyc.rr.com> From: "Clayton Parker" To: Date: Sun, 3 Oct 2004 23:54:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcSpxdvPbns3XmlZRPWpWCpg9BfRZw== X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Foolish question probably, but I need to ask anyways.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 03:54:55 -0000 I want to use cvsup standard-supfile to keep my system up to date within the 5.X tag but whenever I try to update it, it goes to 6.0-CURRENT which is not what I want. I am on BETA6 and want to get to BETA7...help? My standard-supfile says *default release=cvs tag=RELENG_5 so I don't know what's wrong. Thanks in advance, -Clayton From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 03:57:46 2004 Return-Path: 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 68A7116A4CE; Mon, 4 Oct 2004 03:57:46 +0000 (GMT) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 529A143D2D; Mon, 4 Oct 2004 03:57:46 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from tomcat.kitchenlab.org (adsl-64-142-31-107.sonic.net [64.142.31.107]) by b.mail.sonic.net (8.12.11/8.12.11) with ESMTP id i943vjTW031449 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 3 Oct 2004 20:57:46 -0700 Received: from tomcat.kitchenlab.org (localhost.kitchenlab.org [127.0.0.1]) by tomcat.kitchenlab.org (8.13.1/8.13.1) with ESMTP id i943vjsC000874; Sun, 3 Oct 2004 20:57:45 -0700 (PDT) (envelope-from bmah@freebsd.org) Received: (from bmah@localhost) by tomcat.kitchenlab.org (8.13.1/8.13.1/Submit) id i943vjpt000873; Sun, 3 Oct 2004 20:57:45 -0700 (PDT) (envelope-from bmah@freebsd.org) X-Authentication-Warning: tomcat.kitchenlab.org: bmah set sender to bmah@freebsd.org using -f Date: Sun, 3 Oct 2004 20:57:45 -0700 From: "Bruce A. Mah" To: freebsd-current@freebsd.org Message-ID: <20041004035745.GA837@tomcat.kitchenlab.org> References: <20041004025813.GA1912@tomcat.kitchenlab.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <20041004025813.GA1912@tomcat.kitchenlab.org> X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-url: http://www.employees.org/~bmah/ User-Agent: Mutt/1.5.6i cc: bmah@freebsd.org Subject: Re: 5.3-BETA6 boot-time hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 03:57:46 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable If memory serves me right, Bruce A. Mah wrote: > I just updated a RELENG_5 system from sometime around 5.3-BETA4 (17 > September) to very late 5.3-BETA6 (just before the 5.3-BETA7 version > number bump) and it's now hanging after probing its DVD drive. This > problem sounds vaguely like what was described in the thread "ATTN > Soren: BETA3 still hangs on ATAPI DVD Detection during boot": >=20 > http://lists.freebsd.org/pipermail/freebsd-current/2004-September/036543.= html Ah, disregard. This was actually more closely related to an fdc driver bug discussed in the "5.3-BETA5-i386-disc1 bootstrap failures" thread: http://lists.freebsd.org/pipermail/freebsd-current/2004-September/038602.ht= ml Guess I missed that thread. hint.fd.0.disabled=3D1 is an acceptable workaround to me, at least for now. Sorry for the chatter... Bruce. --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYMo52MoxcVugUsMRAnjpAJ9ZeRXwcsOThcgJw8RtPPad17wNzwCgrJF3 iVJF2qRyzzWYl14ihSKDdNo= =CNAm -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 04:53:14 2004 Return-Path: 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 E367B16A4CE for ; Mon, 4 Oct 2004 04:53:14 +0000 (GMT) Received: from s1.stradamotorsports.com (ip30.gte215.dsl-acs2.sea.iinet.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CB0443D53 for ; Mon, 4 Oct 2004 04:53:14 +0000 (GMT) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] ([192.168.1.16])i944rC8m040317 for ; Sun, 3 Oct 2004 21:53:13 -0700 (PDT) (envelope-from jcw@highperformance.net) Date: Sun, 03 Oct 2004 21:53:20 -0700 From: "Jason C. Wells" To: freebsd-current@freebsd.org Message-ID: <48E727D28B46C650D05F4456@[192.168.1.16]> X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=0.0 required=4.0 tests=none version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: entropy functionality X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 04:53:15 -0000 I see a new feature and tweaks in my system regarding entropy. My reading of /etc/rc.d/random tells me that both are loaded if both exist and the rc.conf variables are anything aren't set to no. What is the difference between entropy_file and entropy_dir in rc.conf? Is -current still the appropriate place to talk about RELENG_5? Thanks, Jason C. Wells From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:05:38 2004 Return-Path: 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 022A916A4CE for ; Mon, 4 Oct 2004 05:05:38 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D6543D2F for ; Mon, 4 Oct 2004 05:05:37 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by mproxy.gmail.com with SMTP id 77so4397257rnk for ; Sun, 03 Oct 2004 22:05:37 -0700 (PDT) Received: by 10.38.70.21 with SMTP id s21mr4072237rna; Sun, 03 Oct 2004 22:05:36 -0700 (PDT) Received: by 10.38.15.21 with HTTP; Sun, 3 Oct 2004 22:05:36 -0700 (PDT) Message-ID: Date: Mon, 4 Oct 2004 00:05:36 -0500 From: Eric Kjeldergaard To: Clayton Parker In-Reply-To: <200410040354.i943sS6n007851@ms-smtp-01.rdc-nyc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200410040354.i943sS6n007851@ms-smtp-01.rdc-nyc.rr.com> cc: freebsd-current@freebsd.org Subject: Re: Foolish question probably, but I need to ask anyways.... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:05:38 -0000 Are you /sure/ you don't have a tag=. in that supfile? . is where 6.0 lives. It's possible you mistakenly have that in there. Just a guess. On Sun, 3 Oct 2004 23:54:38 -0400, Clayton Parker wrote: > I want to use cvsup standard-supfile to keep my system up to date within the > 5.X tag but whenever I try to update it, it goes to 6.0-CURRENT which is not > what I want. I am on BETA6 and want to get to BETA7...help? My > standard-supfile says *default release=cvs tag=RELENG_5 so I don't know > what's wrong. > > Thanks in advance, > -Clayton > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:08:24 2004 Return-Path: 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 D34B016A4CE; Mon, 4 Oct 2004 05:08:24 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6726943D45; Mon, 4 Oct 2004 05:08:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i9457Vij084148; Sun, 3 Oct 2004 23:07:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 Oct 2004 23:09:04 -0600 (MDT) Message-Id: <20041003.230904.100900509.imp@bsdimp.com> To: bmah@freebsd.org From: "M. Warner Losh" In-Reply-To: <20041004035745.GA837@tomcat.kitchenlab.org> References: <20041004025813.GA1912@tomcat.kitchenlab.org> <20041004035745.GA837@tomcat.kitchenlab.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.3-BETA6 boot-time hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:08:24 -0000 In message: <20041004035745.GA837@tomcat.kitchenlab.org> "Bruce A. Mah" writes: : hint.fd.0.disabled=1 is an acceptable workaround to me, at least for now. Does BETA7 fix things for you? Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:08:25 2004 Return-Path: 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 7C7C316A4CE; Mon, 4 Oct 2004 05:08:25 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1569C43D3F; Mon, 4 Oct 2004 05:08:25 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i9456ldM084146; Sun, 3 Oct 2004 23:06:47 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 Oct 2004 23:08:20 -0600 (MDT) Message-Id: <20041003.230820.31058467.imp@bsdimp.com> To: bmah@freebsd.org From: "M. Warner Losh" In-Reply-To: <20041004025813.GA1912@tomcat.kitchenlab.org> References: <20041004025813.GA1912@tomcat.kitchenlab.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.3-BETA6 boot-time hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:08:25 -0000 In message: <20041004025813.GA1912@tomcat.kitchenlab.org> "Bruce A. Mah" writes: : fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 drq 2 on acpi0 What happens if you remove fdc from the kernel? This may be yet another strage resource thing. Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:08:42 2004 Return-Path: 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 1412A16A4D4 for ; Mon, 4 Oct 2004 05:08:42 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id C393A43D1D for ; Mon, 4 Oct 2004 05:08:41 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by mproxy.gmail.com with SMTP id 79so3785585rnk for ; Sun, 03 Oct 2004 22:08:41 -0700 (PDT) Received: by 10.38.73.46 with SMTP id v46mr4670475rna; Sun, 03 Oct 2004 22:08:41 -0700 (PDT) Received: by 10.38.15.21 with HTTP; Sun, 3 Oct 2004 22:08:41 -0700 (PDT) Message-ID: Date: Mon, 4 Oct 2004 00:08:41 -0500 From: Eric Kjeldergaard To: "Jason C. Wells" In-Reply-To: <48E727D28B46C650D05F4456@192.168.1.16> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <48E727D28B46C650D05F4456@192.168.1.16> cc: freebsd-current@freebsd.org Subject: Re: entropy functionality X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:08:42 -0000 RELENG_5 is 5-current and is indeed appropriate to talk about here. Now, as to the other question, you should read the fine manual. `man rc.conf` will tell you what you need to know regarding those. On Sun, 03 Oct 2004 21:53:20 -0700, Jason C. Wells wrote: > I see a new feature and tweaks in my system regarding entropy. My reading > of /etc/rc.d/random tells me that both are loaded if both exist and the > rc.conf variables are anything aren't set to no. What is the difference > between entropy_file and entropy_dir in rc.conf? > > Is -current still the appropriate place to talk about RELENG_5? > > Thanks, > Jason C. Wells > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:11:35 2004 Return-Path: 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 DAA3A16A4CE; Mon, 4 Oct 2004 05:11:35 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD6A43D2F; Mon, 4 Oct 2004 05:11:35 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i945Aagv084183; Sun, 3 Oct 2004 23:10:37 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 Oct 2004 23:12:09 -0600 (MDT) Message-Id: <20041003.231209.04694657.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <48733.1096570677@critter.freebsd.dk> References: <200409301409.25904.jhb@FreeBSD.org> <48733.1096570677@critter.freebsd.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Unit number allocation API X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:11:36 -0000 In message: <48733.1096570677@critter.freebsd.dk> "Poul-Henning Kamp" writes: : My personal guess is that driver->attach() and driver->probe() will : never get out from Giant (I can't seriously see the benefits as : being bigger than the effort) and therefore I think the problem of : locking API's like this can be wholesale ignored for a very long : time. This is my guess as well. I have in my tree some locking assertions to make sure this is the case, and hope to commit them soon. Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:11:35 2004 Return-Path: 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 DAA3A16A4CE; Mon, 4 Oct 2004 05:11:35 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD6A43D2F; Mon, 4 Oct 2004 05:11:35 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i945Aagv084183; Sun, 3 Oct 2004 23:10:37 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 Oct 2004 23:12:09 -0600 (MDT) Message-Id: <20041003.231209.04694657.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <48733.1096570677@critter.freebsd.dk> References: <200409301409.25904.jhb@FreeBSD.org> <48733.1096570677@critter.freebsd.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Unit number allocation API X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:11:36 -0000 In message: <48733.1096570677@critter.freebsd.dk> "Poul-Henning Kamp" writes: : My personal guess is that driver->attach() and driver->probe() will : never get out from Giant (I can't seriously see the benefits as : being bigger than the effort) and therefore I think the problem of : locking API's like this can be wholesale ignored for a very long : time. This is my guess as well. I have in my tree some locking assertions to make sure this is the case, and hope to commit them soon. Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:28:22 2004 Return-Path: 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 2825516A4CE for ; Mon, 4 Oct 2004 05:28:22 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 732AC43D3F for ; Mon, 4 Oct 2004 05:28:21 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.42 (FreeBSD)) id 1CE1Hb-000273-G5; Sun, 03 Oct 2004 11:59:51 +0400 From: Vladimir Grebenschikov To: "M. Warner Losh" In-Reply-To: <20041002.193517.46314784.imp@bsdimp.com> References: <415C59C7.7090408@pythonemproject.com> <1096620622.907.16.camel@localhost> <20041002.193517.46314784.imp@bsdimp.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Sun, 03 Oct 2004 11:59:51 +0400 Message-Id: <1096790391.4282.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: rob@pythonemproject.com cc: freebsd-current@freebsd.org Subject: Re: wifi on 5.3, sort of OT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:28:22 -0000 =F7 =D3=C2, 02/10/2004 =D7 19:35 -0600, M. Warner Losh =D0=C9=DB=C5=D4: > In message: <1096620622.907.16.camel@localhost> > Vladimir Grebenschikov writes: > : cbb0: mem 0xd0201000-0xd0201fff irq 9 at > : device 5.0 on pci2 > : cardbus0: on cbb0 > : cbb0: bad Vcc request. ctrl=3D0xffffff88, status=3D0xffffffff > : cbb_power: 0V > :=20 > : Not sure is it related or not. >=20 > I've seen this, but never with a cardbus bridge on pci2... status =3D > 0xfffffff is pretty bogus. Can you provide some hints how to find root of problems ? (sysctl debug., etc ?) for "cbb0: PC Card card activation failed" > Warner --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:29:33 2004 Return-Path: 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 7B1A416A4CE for ; Mon, 4 Oct 2004 05:29:33 +0000 (GMT) Received: from web54003.mail.yahoo.com (web54003.mail.yahoo.com [206.190.36.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 1590743D39 for ; Mon, 4 Oct 2004 05:29:31 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Message-ID: <20041004052930.72382.qmail@web54003.mail.yahoo.com> Received: from [147.46.44.181] by web54003.mail.yahoo.com via HTTP; Sun, 03 Oct 2004 22:29:30 PDT Date: Sun, 3 Oct 2004 22:29:30 -0700 (PDT) From: spam maps To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 5.3: redundant libraries in /usr/lib after cvsup-ing and build world ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:29:33 -0000 Hello, In /usr/lib I have libraries with dates of my latest world build, and with older dates. I consider the libraries with old dates to be redundant. A typical example is, when I do # ll /usr/lib/*libssh* 289008 Oct 3 17:28 /usr/lib/libssh.a 11 Oct 3 17:28 /usr/lib/libssh.so -> libssh.so.2 194148 Oct 3 17:28 /usr/lib/libssh.so.2 280822 Feb 24 2004 /usr/lib/libssh_p.a "Oct 3" is when I did my last build world. Is /usr/lib/libssh_p.a (Feb. 24) indeed redundant? Can I remove it, without breaking the system? There are many more seemingly redundant libraries with lib*_p.a : libalias_p.a, libatm_p.a, libbluetooth_p.a, libbsdxml_p.a, libbsnmp_p.a, libbz2_p.a, libc_p.a, libc_r_p.a, libcalendar_p.a, libcam_p.a, libcom_err_p.a, libcompat_p.a, libedit_p.a, libcrypt_p.a, libdevinfo_p.a, libdevstat_p.a, libdialog_p.a, libfetch_p.a, libfl_p.a, libform_p.a, libftpio_p.a, libg2c_p.a, libgcc_p.a, libgeom_p.a, libgnuregex_p.a, libhistory_p.a, libipsec_p.a, libipx_p.a, libisc_p.a, libkeycap_p.a, libkiconv_p.a, libkse_p.a, libkvm_p.a, libl_p.a, libln_p.a, libm_p.a, libmd_p.a, libmenu_p.a, libmilter_p.a, libmp_p.a, libncp_p.a, libobjc_p.a, libncurses_p.a, libnetgraph_p.a, libngatm_p.a, libopie_p.a, libpanel_p.a, libpcap_p.a, libradius_p.a, libreadline_p.a, librpcsvc_p.a, libsbuf_p.a, libsdp_p.a, libsmb_p.a, libstdc++_p.a, libsupc++_p.a, libtacplus_p.a, libthr_p.a, libufs_p.a, libugidfw_p.a, libusbhid_p.a, libutil_p.a, libvgl_p.a, libwrap_p.a, libxpg4_p.a, liby_p.a, libypclnt_p.a, libz_p.a, libroken_p.a, libasn1_p.a, libhdb_p.a, libkafs5_p.a, libkrb5_p.a, libkadm5clnt_p.a, libkadm5srv_p.a, libgssapi_p.a, libcrypto_p.a, libssl_p.a, libssh_p.a ----------------------- In addition, I have following libraries with old dates: /usr/lib/libisc.a /usr/lib/libisc.so -> libisc.so.1 /usr/lib/libisc.so.1 /usr/lib/libkse.a /usr/lib/libkse.so -> libkse.so.1 /usr/lib/libkse.so.1 /lib/geom/geom_concat.so.1 /lib/geom/geom_label.so.1 /lib/geom/geom_nop.so.1 /lib/geom/geom_stripe.so.1 /libexec/ld-elf.so.1 Can I remove all these as well? Thanks, Rob. _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:31:12 2004 Return-Path: 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 F075F16A4CE; Mon, 4 Oct 2004 05:31:12 +0000 (GMT) Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0880243D2F; Mon, 4 Oct 2004 05:31:11 +0000 (GMT) (envelope-from bp@butya.kz) Received: from lion.butya.kz (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with SMTP id A06715C9F; Mon, 4 Oct 2004 12:31:06 +0700 (ALMST) Received: from relay.butya.kz (localhost [127.0.0.1]) by localhost.butya.kz (Postfix) with ESMTP id 79AEC5C9D; Mon, 4 Oct 2004 12:31:06 +0700 (ALMST) Received: by relay.butya.kz (Postfix, from userid 1000) id 745055C84; Mon, 4 Oct 2004 12:31:06 +0700 (ALMST) Date: Mon, 4 Oct 2004 12:31:06 +0700 From: Boris Popov To: Uwe Doering Message-ID: <20041004053106.GQ88303@vertex.kz> References: <41601BE0.4050401@geminix.org> <200410031805.i93I5JNZ009076@sana.init-main.com> <20041003183237.GA8100@VARK.MIT.EDU> <41605620.90407@geminix.org> <20041003200803.GA8668@VARK.MIT.EDU> <416069E2.6030403@geminix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <416069E2.6030403@geminix.org> User-Agent: Mutt/1.5.6i cc: freebsd-fs@FreeBSD.ORG cc: David Schultz cc: Takanori Watanabe cc: freebsd-current@FreeBSD.ORG Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:31:13 -0000 On Sun, Oct 03, 2004 at 11:06:42PM +0200, Uwe Doering wrote: > > > >That isn't the issue. The issue is that an application might open > >the vnode in the unionfs mount, and another application might > >modify the same file in the underlying file system. If the kernel > >doesn't understand that it is really the same file, then cache > >incoherencies will occur. I'm actually not sure to what extent > >this is a problem already; John Heidemann's Phd thesis had a way > >of dealing with it, but FreeBSD doesn't do things that way AFAIK. > > Okay, but that's a different matter. What I was addressing at the start > of this discussion is an ambiguity issue with meta data, that is, > information that ends up in stat(2) and friends. Exactly, one never knows what parts of metadata used by applications. I can confirm that ino are ought to be unique inside filesystem, otherwise some programs will fail in a very obscure ways. > > As to your concern, in CURRENT this might be fixed already. There, the > unionfs vnode doesn't have an object attached. Instead, calls to > VOP_GETVOBJECT() get forwarded to the underlying file, so the same > object gets referred as for direct modifications of that file. That > should rule out any coherency problems, IMHO. > > Unfortunately, AFAIK, this fix has never been MFC'ed to 4-STABLE. The > respective CVS commits are union_subr.c (rev. 1.51) and union_vnops.c > (rev. 1.82). Correct, VOP_*VOBJECT() vnops were introduced to fill the gap in absence of UBC and should solve most of the cache coherency problems when used properly. -- Boris Popov http://rbp.euro.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 05:38:01 2004 Return-Path: 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 9133916A4CE for ; Mon, 4 Oct 2004 05:38:01 +0000 (GMT) Received: from rip.psg.com (splat.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BA2743D5F for ; Mon, 4 Oct 2004 05:38:01 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.41 (FreeBSD)) id 1CELXt-000FpV-1D; Mon, 04 Oct 2004 05:38:01 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.42 (FreeBSD)) id 1CELVX-0000G6-53; Sun, 03 Oct 2004 22:35:35 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16736.57638.524126.37243@roam.psg.com> Date: Sun, 3 Oct 2004 22:35:34 -0700 To: "Alexandre \"Sunny\" Kovalenko" References: <16736.17211.132754.898091@ran.psg.com> <1096830295.847.1.camel@RabbitsDen> cc: FreeBSD Current Subject: Re: usb serial confuddlement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 05:38:01 -0000 > You need 'ubsa' module loaded or device 'ubsa' in you kernel > configuration. # kldstat Id Refs Address Size Name 1 18 0xc0400000 3a42f4 kernel 2 1 0xc07a5000 6eb8 linprocfs.ko 3 2 0xc07ac000 1fa44 linux.ko 4 1 0xc07cc000 bc08 ipfw.ko 5 1 0xc07d8000 5f84 snd_ich.ko 6 2 0xc07de000 204fc sound.ko 7 1 0xc07ff000 5418 acpi_video.ko 8 15 0xc0805000 5d6f4 acpi.ko 9 1 0xc0863000 38e8 ubsa.ko 10 2 0xc0867000 36c8 ucom.ko ugen0: Belkin USB PDA Adapter Belkin Components, rev 1.10/1.02, addr 2 # ls /dev/u* /dev/ugen0 /dev/ugen0.2 /dev/usb /dev/usb1 /dev/ugen0.1 /dev/urandom@ /dev/usb0 /dev/usb2 so, still no device, and, of course, a crash some time after usb device removal randy From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:05:29 2004 Return-Path: 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 3308316A4CF for ; Mon, 4 Oct 2004 06:05:29 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16FB943D46 for ; Mon, 4 Oct 2004 06:05:29 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 914D9F1A80; Sun, 3 Oct 2004 23:05:27 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25521-02; Sun, 3 Oct 2004 23:05:26 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id A6595F1A38; Sun, 3 Oct 2004 23:05:26 -0700 (PDT) From: Sean McNeil To: Randy Bush In-Reply-To: <16736.57638.524126.37243@roam.psg.com> References: <16736.17211.132754.898091@ran.psg.com> <16736.57638.524126.37243@roam.psg.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-l4b8W8pgD+A0dtDqPOf1" Message-Id: <1096869926.6566.1.camel@server> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 03 Oct 2004 23:05:26 -0700 X-Virus-Scanned: by amavisd-new at mcneil.com cc: FreeBSD Current cc: "Alexandre \"Sunny\" Kovalenko" Subject: Re: usb serial confuddlement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:05:29 -0000 --=-l4b8W8pgD+A0dtDqPOf1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-10-03 at 22:35, Randy Bush wrote: > > You need 'ubsa' module loaded or device 'ubsa' in you kernel > > configuration. >=20 > # kldstat > Id Refs Address Size Name > 1 18 0xc0400000 3a42f4 kernel > 2 1 0xc07a5000 6eb8 linprocfs.ko > 3 2 0xc07ac000 1fa44 linux.ko > 4 1 0xc07cc000 bc08 ipfw.ko > 5 1 0xc07d8000 5f84 snd_ich.ko > 6 2 0xc07de000 204fc sound.ko > 7 1 0xc07ff000 5418 acpi_video.ko > 8 15 0xc0805000 5d6f4 acpi.ko > 9 1 0xc0863000 38e8 ubsa.ko > 10 2 0xc0867000 36c8 ucom.ko >=20 >=20 > ugen0: Belkin USB PDA Adapter Belkin Components, rev 1.10/1.02, addr 2 >=20 > # ls /dev/u* > /dev/ugen0 /dev/ugen0.2 /dev/usb /dev/usb1 > /dev/ugen0.1 /dev/urandom@ /dev/usb0 /dev/usb2 >=20 >=20 > so, still no device, and, of course, a crash some time after > usb device removal Don't you also need to load uplcom.ko? I do for my serial-usb converter. I had to load it in the boot loader to have it actually work, though. You will also find that the device name has changed. It is no longer ucom0 but ttyU0. Cheers, Sean --=-l4b8W8pgD+A0dtDqPOf1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBYOgmyQsGN30uGE4RAkXUAKCocZoMjrkzbXbdOEYZK4xdJmfNogCfeUyn LhnbEkt4KtVuxSnyjskB9gE= =UAGf -----END PGP SIGNATURE----- --=-l4b8W8pgD+A0dtDqPOf1-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:18:20 2004 Return-Path: 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 267FE16A4CE; Mon, 4 Oct 2004 06:18:20 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA6D143D1D; Mon, 4 Oct 2004 06:18:19 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i946IToh011539; Mon, 4 Oct 2004 02:18:29 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i946ITp7011538; Mon, 4 Oct 2004 02:18:29 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Mon, 4 Oct 2004 02:18:29 -0400 From: David Schultz To: Takanori Watanabe Message-ID: <20041004061829.GB11422@VARK.MIT.EDU> Mail-Followup-To: Takanori Watanabe , Boris Popov , gemini@geminix.org, freebsd-fs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <20041004053106.GQ88303@vertex.kz> <200410040606.i9466UVm012207@sana.init-main.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410040606.i9466UVm012207@sana.init-main.com> cc: freebsd-fs@FreeBSD.ORG cc: Boris Popov cc: freebsd-current@FreeBSD.ORG cc: gemini@geminix.org Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:18:20 -0000 On Mon, Oct 04, 2004, Takanori Watanabe wrote: > In message <20041004053106.GQ88303@vertex.kz>, Boris Popov wrote: > >On Sun, Oct 03, 2004 at 11:06:42PM +0200, Uwe Doering wrote: > >> > > >> >That isn't the issue. The issue is that an application might open > >> >the vnode in the unionfs mount, and another application might > >> >modify the same file in the underlying file system. If the kernel > >> >doesn't understand that it is really the same file, then cache > >> >incoherencies will occur. I'm actually not sure to what extent > >> >this is a problem already; John Heidemann's Phd thesis had a way > >> >of dealing with it, but FreeBSD doesn't do things that way AFAIK. > >> > >> Okay, but that's a different matter. What I was addressing at the start > >> of this discussion is an ambiguity issue with meta data, that is, > >> information that ends up in stat(2) and friends. > > > > Exactly, one never knows what parts of metadata used by applications. > >I can confirm that ino are ought to be unique inside filesystem, otherwise > >some programs will fail in a very obscure ways. > > Ok, the issue Uwe says is when underlying filesystem and > wrapping filesystem are diffent and if there are two files > with same identifier exists. > And the issue I want to fix is when underlying filesystem and > wrapping filesystem are same so getcwd routine failed to distinguish > the mount point. > > So it can be solved by translating fsid if the fsid of a file is same as > that of mountpoint. True? Many applications use the file's inode number and the filesystem device number to uniquely identify files, since this information can be easily and portably extracted via stat(2). IIRC, unionfs has always used the upper layer's device number, which is arguably wrong. I think the main consumer of fsids is NFS, which uses fsids along with i-numbers to construct file handles. umount(..., MNT_BYFSID) is another interface that uses fsids. From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:21:12 2004 Return-Path: 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 1585216A4CE for ; Mon, 4 Oct 2004 06:21:12 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46FDE43D1D for ; Mon, 4 Oct 2004 06:21:11 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (oak.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i946LAVF053344; Mon, 4 Oct 2004 09:21:10 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 10972-10; Mon, 4 Oct 2004 09:21:09 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i946L9Y0053341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Oct 2004 09:21:09 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i946LC08047482; Mon, 4 Oct 2004 09:21:12 +0300 (EEST) (envelope-from ru) Date: Mon, 4 Oct 2004 09:21:12 +0300 From: Ruslan Ermilov To: spam maps Message-ID: <20041004062112.GC47338@ip.net.ua> References: <20041004052930.72382.qmail@web54003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E13BgyNx05feLLmH" Content-Disposition: inline In-Reply-To: <20041004052930.72382.qmail@web54003.mail.yahoo.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-current@freebsd.org Subject: Re: 5.3: redundant libraries in /usr/lib after cvsup-ing and build world ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:21:12 -0000 --E13BgyNx05feLLmH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there, On Sun, Oct 03, 2004 at 10:29:30PM -0700, spam maps wrote: > In /usr/lib I have libraries with dates of my latest > world build, and with older dates. I consider the > libraries with old dates to be redundant. > A typical example is, when I do >=20 > # ll /usr/lib/*libssh* > 289008 Oct 3 17:28 /usr/lib/libssh.a > 11 Oct 3 17:28 /usr/lib/libssh.so -> libssh.so.2 > 194148 Oct 3 17:28 /usr/lib/libssh.so.2 > 280822 Feb 24 2004 /usr/lib/libssh_p.a >=20 > "Oct 3" is when I did my last build world. > Is /usr/lib/libssh_p.a (Feb. 24) indeed redundant? > Can I remove it, without breaking the system? >=20 Yes. It's a profiled library that was installed during the initial install (from CD-ROM or FTP?), and now apparently you have NOPROFILE set in your /etc/make.conf. > There are many more seemingly redundant libraries > with lib*_p.a : >=20 > libalias_p.a, libatm_p.a, libbluetooth_p.a, [20 lines of *_p.a libraries removed] > libgssapi_p.a, libcrypto_p.a, libssl_p.a, libssh_p.a >=20 > ----------------------- >=20 > In addition, I have following libraries with > old dates: >=20 > /usr/lib/libisc.a > /usr/lib/libisc.so -> libisc.so.1 > /usr/lib/libisc.so.1 >=20 > /usr/lib/libkse.a > /usr/lib/libkse.so -> libkse.so.1 > /usr/lib/libkse.so.1 >=20 > /lib/geom/geom_concat.so.1 > /lib/geom/geom_label.so.1 > /lib/geom/geom_nop.so.1 > /lib/geom/geom_stripe.so.1 >=20 > /libexec/ld-elf.so.1 >=20 > Can I remove all these as well? >=20 Yes for the above list, but generally one should be careful with removing the .a libraries -- they are installed with -C. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --E13BgyNx05feLLmH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBYOvYqRfpzJluFF4RAsVGAJ4i6tZjKlLYNJ1YnPlwvRO9qjrxsQCeOpMr zzc214FaFVzUc/f8LE/N4Z4= =Kl4D -----END PGP SIGNATURE----- --E13BgyNx05feLLmH-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:38:45 2004 Return-Path: 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 D06F016A4CE for ; Mon, 4 Oct 2004 06:38:45 +0000 (GMT) Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8A1443D39 for ; Mon, 4 Oct 2004 06:38:43 +0000 (GMT) (envelope-from bp@butya.kz) Received: from lion.butya.kz (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with SMTP id 383BD5CB8; Mon, 4 Oct 2004 13:38:41 +0700 (ALMST) Received: from relay.butya.kz (localhost [127.0.0.1]) by localhost.butya.kz (Postfix) with ESMTP id 10F455CB3; Mon, 4 Oct 2004 13:38:41 +0700 (ALMST) Received: by relay.butya.kz (Postfix, from userid 1000) id 0CBF35CAE; Mon, 4 Oct 2004 13:38:41 +0700 (ALMST) Date: Mon, 4 Oct 2004 13:38:41 +0700 From: Boris Popov To: Key Dof Message-ID: <20041004063840.GR88303@vertex.kz> References: <1095947258.61028.12.camel@ramses> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1095947258.61028.12.camel@ramses> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: smbfs and SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:38:45 -0000 On Thu, Sep 23, 2004 at 03:47:38PM +0200, Key Dof wrote: > Hi, > I am using 5.2.1-p10 with a HTT P4 cpu, when i try to mount smbfs i > get that the module was not compiled with SMP support (in > /var/log/messages) > I put SMP=yes and SMP_SUPPORT=yes in my make.conf and i recompiled smbfs > and mount_smbfs but it didn't change anything. > Any idea how to solve this? Put an entire smbfs options into kernel config and rebuild/reinstall kernel. -- Boris Popov http://rbp.euro.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:43:38 2004 Return-Path: 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 9F52D16A4CE for ; Mon, 4 Oct 2004 06:43:38 +0000 (GMT) Received: from web54010.mail.yahoo.com (web54010.mail.yahoo.com [206.190.36.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 1D0CA43D2D for ; Mon, 4 Oct 2004 06:43:38 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Message-ID: <20041004064337.19785.qmail@web54010.mail.yahoo.com> Received: from [147.46.44.181] by web54010.mail.yahoo.com via HTTP; Sun, 03 Oct 2004 23:43:37 PDT Date: Sun, 3 Oct 2004 23:43:37 -0700 (PDT) From: spam maps To: freebsd-current@freebsd.org In-Reply-To: <20041004062112.GC47338@ip.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: 5.3: redundant libraries in /usr/lib after cvsup-ing and build world ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:43:38 -0000 --- Ruslan Ermilov wrote: > On Sun, Oct 03, 2004 at 10:29:30PM -0700, spam maps > wrote: > > > > /libexec/ld-elf.so.1 > > > > Can I remove all these as well? > > > Yes for the above list, but generally one should be > careful with removing the .a libraries -- they are > installed with -C. # ls -i /libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1 8710 /libexec/ld-elf.so.1 8710 /usr/libexec/ld-elf.so.1 But: # ls -il /libexec/ld-elf.so.1 /usr/libexec/ld-elf.so.1 8710 /libexec/ld-elf.so.1 110872 /usr/libexec/ld-elf.so.1 -> /libexec/ld-elf.so.1 However, /libexec/ld-elf.so.1 has an old date, whereas /usr/libexec/ld-elf.so.1 has the date of most recent world build. Is it still save to remove libexec/ld-elf.so.1 ? Regards, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:44:45 2004 Return-Path: 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 1D7F416A4CE for ; Mon, 4 Oct 2004 06:44:45 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4C7C43D4C for ; Mon, 4 Oct 2004 06:44:44 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id BC8BD5313; Mon, 4 Oct 2004 08:44:43 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id C28745315; Mon, 4 Oct 2004 08:44:37 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 9DDD6B861; Mon, 4 Oct 2004 08:44:37 +0200 (CEST) To: spam maps References: <20041004052930.72382.qmail@web54003.mail.yahoo.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 04 Oct 2004 08:44:37 +0200 In-Reply-To: <20041004052930.72382.qmail@web54003.mail.yahoo.com> (spam maps's message of "Sun, 3 Oct 2004 22:29:30 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.64 cc: freebsd-current@freebsd.org Subject: Re: 5.3: redundant libraries in /usr/lib after cvsup-ing and build world ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:44:45 -0000 spam maps writes: > A typical example is, when I do > > # ll /usr/lib/*libssh* > 289008 Oct 3 17:28 /usr/lib/libssh.a > 11 Oct 3 17:28 /usr/lib/libssh.so -> libssh.so.2 > 194148 Oct 3 17:28 /usr/lib/libssh.so.2 > 280822 Feb 24 2004 /usr/lib/libssh_p.a > > "Oct 3" is when I did my last build world. > Is /usr/lib/libssh_p.a (Feb. 24) indeed redundant? > Can I remove it, without breaking the system? *_p.a are profiling libraries, which you probably disabled by adding NOPROFILE=3DYES to /etc/make.conf. You can safely remove them. > /usr/lib/libisc.a > /usr/lib/libisc.so -> libisc.so.1 > /usr/lib/libisc.so.1 Old libisc from BIND 8. BIND 9 doesn't use it, but some ports may want it. You should keep it around until those ports are fixed. > /usr/lib/libkse.a > /usr/lib/libkse.so -> libkse.so.1 > /usr/lib/libkse.so.1 This library has been renamed. You can remove it. > /lib/geom/geom_concat.so.1 > /lib/geom/geom_label.so.1 > /lib/geom/geom_nop.so.1 > /lib/geom/geom_stripe.so.1 You can remove these. > /libexec/ld-elf.so.1 Do *not* remove this, or you will be very sorry you did. It is normal for ld-elf.so.1 to have a timestamp older than your latest build, because installworld only installs a new ld-elf.so.1 if it differs from the old one. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 06:52:50 2004 Return-Path: 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 3C50316A4CE; Mon, 4 Oct 2004 06:52:50 +0000 (GMT) Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F55143D1D; Mon, 4 Oct 2004 06:52:48 +0000 (GMT) (envelope-from bp@butya.kz) Received: from lion.butya.kz (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with SMTP id 1F9DA5C9F; Mon, 4 Oct 2004 13:52:43 +0700 (ALMST) Received: from relay.butya.kz (localhost [127.0.0.1]) by localhost.butya.kz (Postfix) with ESMTP id EB20B5C9D; Mon, 4 Oct 2004 13:52:42 +0700 (ALMST) Received: by relay.butya.kz (Postfix, from userid 1000) id E3B6C5C84; Mon, 4 Oct 2004 13:52:42 +0700 (ALMST) Date: Mon, 4 Oct 2004 13:52:42 +0700 From: Boris Popov To: Andre Guibert de Bruet Message-ID: <20041004065242.GS88303@vertex.kz> References: <20041003200636.D90253@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041003200636.D90253@alpha.siliconlandmark.com> User-Agent: Mutt/1.5.6i cc: bp@freebsd.org cc: current@freebsd.org Subject: Re: [PATCH] contrib/smbfs/smbutil - 2 typos X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 06:52:50 -0000 On Sun, Oct 03, 2004 at 08:12:14PM -0400, Andre Guibert de Bruet wrote: > Hi, > > Nothing big, just a couple of annoyances. I've copied boris@ on this > email. Could this be committed? :) Yep, it should be committed. Thanks! -- Boris Popov http://rbp.euro.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 07:07:29 2004 Return-Path: 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 F2B7716A4CE; Mon, 4 Oct 2004 07:07:28 +0000 (GMT) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE5D943D45; Mon, 4 Oct 2004 07:07:27 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost.init-main.com [127.0.0.1]) by sana.init-main.com (8.13.1/8.13.1) with ESMTP id i9475jwq012503; Mon, 4 Oct 2004 16:05:45 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200410040705.i9475jwq012503@sana.init-main.com> To: Uwe Doering From: takawata@jp.freebsd.org In-reply-to: Your message of "Mon, 04 Oct 2004 08:26:14 +0200." <4160ED06.6070603@geminix.org> Date: Mon, 04 Oct 2004 16:05:45 +0900 Sender: takawata@init-main.com cc: freebsd-fs@FreeBSD.org cc: Boris Popov cc: das@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: Your CVS fix 1.109 to union_vnops.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 07:07:29 -0000 In message <4160ED06.6070603@geminix.org>, Uwe Doering wrote: >Takanori Watanabe wrote: >> In message <20041004053106.GQ88303@vertex.kz>, Boris Popov wrote: >> >>>On Sun, Oct 03, 2004 at 11:06:42PM +0200, Uwe Doering wrote: >>> >>>>>That isn't the issue. The issue is that an application might open >>>>>the vnode in the unionfs mount, and another application might >>>>>modify the same file in the underlying file system. If the kernel >>>>>doesn't understand that it is really the same file, then cache >>>>>incoherencies will occur. I'm actually not sure to what extent >>>>>this is a problem already; John Heidemann's Phd thesis had a way >>>>>of dealing with it, but FreeBSD doesn't do things that way AFAIK. >>>> >>>>Okay, but that's a different matter. What I was addressing at the start >>>>of this discussion is an ambiguity issue with meta data, that is, >>>>information that ends up in stat(2) and friends. >>> >>> Exactly, one never knows what parts of metadata used by applications. >>>I can confirm that ino are ought to be unique inside filesystem, otherwise >>>some programs will fail in a very obscure ways. >> >> Ok, the issue Uwe says is when underlying filesystem and >> wrapping filesystem are diffent and if there are two files >> with same identifier exists. >> And the issue I want to fix is when underlying filesystem and >> wrapping filesystem are same so getcwd routine failed to distinguish >> the mount point. >> >> So it can be solved by translating fsid if the fsid of a file is same as >> that of mountpoint. True? > >Correct. In this case the inode number is guaranteed to be unique. >This might be okay as a local patch, but it is IMHO not a fix suited for >FreeBSD in general. Ok. How about this? Index: union_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/unionfs/union_vnops.c,v retrieving revision 1.109 diff -u -r1.109 union_vnops.c --- union_vnops.c 2 Oct 2004 17:17:04 -0000 1.109 +++ union_vnops.c 4 Oct 2004 07:04:38 -0000 @@ -951,6 +951,8 @@ error = VOP_GETATTR(vp, vap, ap->a_cred, ap->a_td); if (error) return (error); + ap->a_vap->va_fsid = ap->a_vp->v_mount->mnt_stat.f_fsid.val[0]; + /* XXX isn't this dangerous without a lock? */ union_newsize(ap->a_vp, vap->va_size, VNOVAL); } @@ -972,7 +974,6 @@ union_newsize(ap->a_vp, VNOVAL, vap->va_size); } - ap->a_vap->va_fsid = ap->a_vp->v_mount->mnt_stat.f_fsid.val[0]; if ((vap != ap->a_vap) && (vap->va_type == VDIR)) ap->a_vap->va_nlink += vap->va_nlink; From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 07:10:24 2004 Return-Path: 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 483E016A4CE for ; Mon, 4 Oct 2004 07:10:24 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ED1C43D1F for ; Mon, 4 Oct 2004 07:10:24 +0000 (GMT) (envelope-from rob@pythonemproject.com) Received: from [192.168.1.102] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <20041004071018015003a9rje> (Authid: europax); Mon, 4 Oct 2004 07:10:19 +0000 Message-ID: <4160F7E0.40103@pythonemproject.com> Date: Mon, 04 Oct 2004 00:12:32 -0700 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040816 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <415C59C7.7090408@pythonemproject.com> <1096620622.907.16.camel@localhost> <20041002.193517.46314784.imp@bsdimp.com> <1096790391.4282.1.camel@localhost> In-Reply-To: <1096790391.4282.1.camel@localhost> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-current@freebsd.org cc: "M. Warner Losh" Subject: Re: wifi on 5.3, sort of OT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 07:10:24 -0000 Vladimir Grebenschikov wrote: > ÷ ÓÂ, 02/10/2004 × 19:35 -0600, M. Warner Losh ÐÉÛÅÔ: > >>In message: <1096620622.907.16.camel@localhost> >> Vladimir Grebenschikov writes: >>: cbb0: mem 0xd0201000-0xd0201fff irq 9 at >>: device 5.0 on pci2 >>: cardbus0: on cbb0 >>: cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff >>: cbb_power: 0V >>: >>: Not sure is it related or not. >> >>I've seen this, but never with a cardbus bridge on pci2... status = >>0xfffffff is pretty bogus. > > > Can you provide some hints how to find root of problems ? > (sysctl debug., etc ?) > > for "cbb0: PC Card card activation failed" > > >>Warner > > Thanks for everyone who posted replies. I will eventually figure it out. For now, I got sucked in to AMD-64, so I'm running out of time for all these projects LOL. I'm beginning to hate all drivers. May as well write them in FORTRAN. Rob. From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 07:43:23 2004 Return-Path: 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 57D0B16A4CE for ; Mon, 4 Oct 2004 07:43:23 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BF9543D1D for ; Mon, 4 Oct 2004 07:43:22 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [172.18.2.1] (axiell-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i947hIk3039460; Mon, 4 Oct 2004 09:43:20 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <4160FF10.2090006@DeepCore.dk> Date: Mon, 04 Oct 2004 09:43:12 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomas Randa References: <1096836705.1446.4.camel@ares.office.internetservice.cz> In-Reply-To: <1096836705.1446.4.camel@ares.office.internetservice.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: persisting ATA problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 07:43:23 -0000 Tomas Randa wrote: > Hi, >=20 > I am running VIA8237 ata controller with BETA6 from 02.10.04 and in > dmesg still have the following errors: >=20 > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=3D846= 959 Those messages are just that a WARNING that you system has processed the = command and has gotten the result back from the HW, however tht=20 taskqueue that should send the result back to the system hasn't run yet..= --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 07:48:19 2004 Return-Path: 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 0D99816A4CE; Mon, 4 Oct 2004 07:48:19 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E09B43D5E; Mon, 4 Oct 2004 07:48:18 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [172.18.2.1] (axiell-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i947mE3k039524; Mon, 4 Oct 2004 09:48:16 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <41610039.8030204@DeepCore.dk> Date: Mon, 04 Oct 2004 09:48:09 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bruce A. Mah" References: <20041004025813.GA1912@tomcat.kitchenlab.org> In-Reply-To: <20041004025813.GA1912@tomcat.kitchenlab.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: 5.3-BETA6 boot-time hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: ,