From owner-freebsd-hackers Sun Dec 16 1:31:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 7E75F37B405 for ; Sun, 16 Dec 2001 01:31:20 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 5798D786E4; Sun, 16 Dec 2001 20:01:14 +1030 (CST) Date: Sun, 16 Dec 2001 20:01:14 +1030 From: Greg Lehey To: wkt@tuhs.org Cc: Terry Lambert , Peter Jeremy , freebsd-hackers@FreeBSD.org Subject: Re: Adding a new FS to FreeBSD Message-ID: <20011216200114.U62493@monorchid.lemis.com> References: <20011216115556.A62493@monorchid.lemis.com> <200112160737.fBG7bXt24793@minnie.tuhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112160737.fBG7bXt24793@minnie.tuhs.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 16 December 2001 at 18:37:33 +1100, Warren Toomey wrote: > I would say that FreeBSD already has a nearly-working UFS > implementation. Also, the structure of UFS is so well documented in > various books that, even if FreeBSD's UFS implementation was > deficient, it could be rectified with reference to the books. I think we should put that in the fortune database :-) Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 1:56:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id F2CDB37B405; Sun, 16 Dec 2001 01:56:37 -0800 (PST) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id fBG9ubu22662; Sun, 16 Dec 2001 01:56:37 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sun, 16 Dec 2001 01:55:47 -0800 Received: from [17.219.180.26] (minshallidsl1.apple.com [17.219.180.26]) by scv3.apple.com (8.11.3/8.11.3) with ESMTP id fBG9tWK00460; Sun, 16 Dec 2001 01:55:37 -0800 (PST) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <200112160122.fBG1Mtq18851@apollo.backplane.com> References: <58885.1008217148@winston.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 16 Dec 2001 00:01:17 -0800 To: Matthew Dillon , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@freebsd.org, msmith@mass.dis.org From: Conrad Minshall Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 5:22 PM -0800 12/15/01, Matthew Dillon wrote: > Ho! Will do. I'm going to try to speed things up a bit by > having the NFS server export an MFS filesystem. > > -Matt Two things I've done to speed it up are to restrict the size of transfers (use the -o flag) and eliminate all the size checks (use the -n flag). Why would MFS be much faster than UFS? On the server doesn't the whole file end up cached? ...and the metadata changes likewise via softupdates. Running fsx during resource shortages (low memory or buf structs) has exposed a bug or two. Running it with operations 512 or page aligned also exposed bugs - see usage for those flags. Note that if you get a failure at operation 50 million there is an fsx flag which allows you to restart at, say, 49 million. Of course some failures don't reproduce reliably at the same spot anyway. I gave out fsx source code at the recent CIFS (SMB) plugfest. If I make the 2002 Connectathon I'll give it out there too. I don't test it on Windows so those defines may be in need of repair. Please send me any patches or cool additions. -- Conrad Minshall, conrad@apple.com, 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 7:25:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 4260C37B416 for ; Sun, 16 Dec 2001 07:25:13 -0800 (PST) Received: (qmail 97152 invoked by uid 3193); 16 Dec 2001 15:25:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Dec 2001 15:25:12 -0000 Date: Sun, 16 Dec 2001 10:25:12 -0500 (EST) From: Mike Silbersack X-Sender: To: Cc: , Subject: RE: 3Com driver problems In-Reply-To: <176.cf4901.294bd7bc@aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Dec 2001 HP889@aol.com wrote: > We dont sell ethernet drivers, and Im not trying to "hide". Why does linux > have specific code to disable the stats under load if Im making this up? Why > can you lock up a FreeBSD 4.4 system with a 3com card at 20Kpps due to > counter overflow interrupts in about 3 seconds? Well, I'm unable to lock up my -current box with a 3c905-tx (non-B or C). However, I can see the delay (apparently) caused by the stat collection routine, which was previously mentioned in the message http://docs.freebsd.org/cgi/getmsg.cgi?fetch=12982+0+archive/2001/freebsd-net/20010114.freebsd-net Interestingly enough, the delay seems to grow as I run the test longer and longer. (My test is ping -s 1400 -i .001 boxwithxlnic.) The delay seems to be able to grow to as much as 12 ms, though it's typically less, around 5 ms or so. If I switch back to the dc interface, I see no delayed packets. I see the hack you refer to in the 3c59x.c driver; I also notice that 3com's official driver (3c90x.c) doesn't contain such a workaround. They must be doing something subtly different which avoids the problem. I have a few ideas, I'll try them out next week and see what I can come up with. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 7:28:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 38D3537B416 for ; Sun, 16 Dec 2001 07:28:30 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA16651; Sun, 16 Dec 2001 10:28:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id fBGFRuD09584; Sun, 16 Dec 2001 10:27:56 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15388.48508.65545.403221@grasshopper.cs.duke.edu> Date: Sun, 16 Dec 2001 10:27:56 -0500 (EST) To: David Greenman Cc: rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? In-Reply-To: <20011215150933.B86349@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> <3C1B32EB.ACBA8DB@mindspring.com> <20011215135635.A86349@nexus.root.com> <3C1BD22F.F3A52BF4@mindspring.com> <20011215150933.B86349@nexus.root.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Greenman writes: > >David Greenman wrote: > >> >In any case, disabling it is what ClickArray ended up doing, as well, > >> >for the Tigon II, until the firmware could be fixed. > >> > >> We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). > > > >Crap. Thanks for the info. > > > >Have you manually calculated the checksum on a bad packet to see > >how it's off? > > Yes. It's typically off by 0x1051, but varies depending on the TCP/IP > header contents. Hmm.. Since you've already got the code for calculating the checksum in the driver written, why not use it? Eg, why not pass the csum up & set CSUM_DATA_VALID iff the csum ends up being 0? Are you worried that the firmware will yield false posatives too? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 9:51:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r09.mx.aol.com (imo-r09.mx.aol.com [152.163.225.105]) by hub.freebsd.org (Postfix) with ESMTP id 6FFFE37B41D; Sun, 16 Dec 2001 09:51:24 -0800 (PST) Received: from TD790@aol.com by imo-r09.mx.aol.com (mail_out_v31_r1.9.) id n.14a.5dcd50d (4330); Sun, 16 Dec 2001 12:51:12 -0500 (EST) From: TD790@aol.com Message-ID: <14a.5dcd50d.294e390f@aol.com> Date: Sun, 16 Dec 2001 12:51:11 EST Subject: 3Com driver problems To: hackers@freebsd.org Cc: isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 12/16/01 10:25:31 AM Eastern Standard Time, silby@silby.com writes: > Well, I'm unable to lock up my -current box with a 3c905-tx (non-B or C). > However, I can see the delay (apparently) caused by the stat collection > routine, which was previously mentioned in the message > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=12982+0+archive/2001/freebsd- > net/20010114.freebsd-net > > Interestingly enough, the delay seems to grow as I run the test longer and > longer. (My test is ping -s 1400 -i .001 boxwithxlnic.) The delay seems > to be able to grow to as much as 12 ms, though it's typically less, around > 5 ms or so. If I switch back to the dc interface, I see no delayed > packets. > ping is not a very good test...one of the reasons that most people cant find problems generally. plus you want to use smaller packets to get the pps up. The ave size packet is under 400 bytes on the net and it better simulates real life. Once you saturate the wire the lockup occurs rather quickly....you have to get to the point where the overflows are happening faster than the machine can process the interupts. intels "official" driver for linux locks up quite easily...dont assume that the manufacturer puts out bulletproof drivers, because they dont test them that rigorously. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 11:17:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id E0E7C37B419 for ; Sun, 16 Dec 2001 11:17:09 -0800 (PST) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.6/8.11.6) with ESMTP id fBGJH5u00621; Sun, 16 Dec 2001 12:17:06 -0700 (MST) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200112161917.fBGJH5u00621@hunkular.glarp.com> To: Bruce M Simpson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: closeing files in detach() In-Reply-To: Your message of "Thu, 13 Dec 2001 23:24:46 GMT." <20011213232446.D17058@spc.org> Date: Sun, 16 Dec 2001 12:17:05 -0700 From: Brad Huntting Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> There's a mention in the FBSD hacking guide that a detach() routine >> for a device driver can forcably close all open descriptors for >> its device before it unloads. >> >> How does one do this? > Check this out (from one of my USB device drivers I haven't yet > forced upon the world): > > /* nuke the vnodes for any processes attached to us. */ > vp = SLIST_FIRST(&sc->dev->si_hlist); > if (vp) > VOP_REVOKE(vp, REVOKEALL); > destroy_dev(sc->dev); > > This will cause all open fds for that device to be revoked. Er... Something is wrong here. destroy_dev() supposedly takes a dev_t which is typedef u_int32_t in . Are we using the same OS? I'm working with 4.4-RELEASE. brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 11:58:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id A753337B419; Sun, 16 Dec 2001 11:58:22 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBGJvHq72458; Sun, 16 Dec 2001 11:57:18 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Conrad Minshall Cc: Matthew Dillon , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: Message from Conrad Minshall of "Sun, 16 Dec 2001 00:01:17 PST." Date: Sun, 16 Dec 2001 11:57:17 -0800 Message-ID: <72454.1008532637@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I gave out fsx source code at the recent CIFS (SMB) plugfest. If I make > the 2002 Connectathon I'll give it out there too. I don't test it on > Windows so those defines may be in need of repair. Please send me any > patches or cool additions. Guy Harris of NetApp sent me a whole mess-o-changes to it and when I went to forward them to you, I found that I must have been in delete-o-matic mode at some point earlier in my inbox since it was gone. I've requested that he send them to me again and will forward them to you once I get a copy again. Whoops! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:15:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id ED56137B417 for ; Sun, 16 Dec 2001 12:15:34 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBGKLtq01665; Sun, 16 Dec 2001 12:21:55 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112162021.fBGKLtq01665@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jordan Hubbard Cc: Conrad Minshall , Matthew Dillon , Peter Wemm , hackers@FreeBSD.ORG Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-reply-to: Your message of "Sun, 16 Dec 2001 11:57:17 PST." <72454.1008532637@winston.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 Dec 2001 12:21:55 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JFWIW, you can build fsx with minimal or no changes on Windows with David Korn's UWIN kit. All of the other posix-y kits have internal problems that will cause spurious failures. If you want to use Windows boxes as test clients (probably a good idea) this is fairly important... > > I gave out fsx source code at the recent CIFS (SMB) plugfest. If I make > > the 2002 Connectathon I'll give it out there too. I don't test it on > > Windows so those defines may be in need of repair. Please send me any > > patches or cool additions. > > Guy Harris of NetApp sent me a whole mess-o-changes to it and when I > went to forward them to you, I found that I must have been in > delete-o-matic mode at some point earlier in my inbox since it was > gone. I've requested that he send them to me again and will forward > them to you once I get a copy again. Whoops! > > - Jordan -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:22:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 9CCD937B417; Sun, 16 Dec 2001 12:22:23 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id fBGKKfu98497; Sun, 16 Dec 2001 15:20:41 -0500 (EST) (envelope-from mike) Date: Sun, 16 Dec 2001 15:20:41 -0500 From: Mike Barcroft To: wkt@tuhs.org Cc: Greg Lehey , Terry Lambert , Peter Jeremy , freebsd-hackers@FreeBSD.org Subject: Re: Caldera and the Ancient UNIX license Message-ID: <20011216152041.A93504@espresso.q9media.com> References: <20011216115556.A62493@monorchid.lemis.com> <200112160618.fBG6IcK23973@minnie.tuhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112160618.fBG6IcK23973@minnie.tuhs.org>; from wkt@minnie.tuhs.org on Sun, Dec 16, 2001 at 05:18:37PM +1100 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warren Toomey writes: > As for commercial use, that's a separate issue. I don't know how easy > it would be for us to talk Caldera into allowing that. Isn't Caldera keen on the BSD license? Here's a relevent quote: "Following the acquisition of Webmin by Caldera, all past and future versions of Webmin are available under the BSD license." Perhaps Caldera would be interested in releasing this gem into the open source community. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:25:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2829137B41B; Sun, 16 Dec 2001 12:25:45 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBGKOSt22277; Sun, 16 Dec 2001 12:24:28 -0800 (PST) (envelope-from dillon) Date: Sun, 16 Dec 2001 12:24:28 -0800 (PST) From: Matthew Dillon Message-Id: <200112162024.fBGKOSt22277@apollo.backplane.com> To: Conrad Minshall Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Two things I've done to speed it up are to restrict the size of transfers :(use the -o flag) and eliminate all the size checks (use the -n flag). : :Why would MFS be much faster than UFS? On the server doesn't the whole :file end up cached? ...and the metadata changes likewise via softupdates. With NFSv3 it's semi-asynchronous (2-phase commit), but you still must eventually commit the data. Also, ftruncate() on the FreeBSD server side creates a special case that requires all data to be flushed out to its physical media. Kirk had so many problems trying to integrate ftruncate() into softupdates that he finally gave up and threw the FSYNC in. I'm guessing that the FSYNC in ftruncate() on the server side is mostly responsible for the slowness. The NFSv3 two-phase commits are reasonably decoupled for smallish (< 8MB) file sizes but we definitely have some sequencing problems with larger file sizes... I should be able to saturate a 100BaseT network link doing a linear NFS write and the best I can get is 2-3 MBytes/sec. I'm analying the problem but may not be able to get a patch in by the 4.5 release. :Running fsx during resource shortages (low memory or buf structs) has :exposed a bug or two. : :Running it with operations 512 or page aligned also exposed bugs - see :usage for those flags. Yes, those are mainly the ones I found. About 7 bug fixes are going to go into the next FreeBSD release related to mmap & DEV_BSIZE NFS interactions. I'll set a MAXMEM limit and run the test in a low-memory environment as well. So far with a fairly normal box + bug fixes the program runs fine in an overnight test. We still have a known issue with out-of-order operations from nfsiod's that apparently may come up after a week or so of testing. I asked Jordan to try to track down the NeXT guy who fixed that one in the old NFS stack. We also have known issues with multiple clients competing for the same file creating issues. :Note that if you get a failure at operation 50 million there is an fsx flag :which allows you to restart at, say, 49 million. Of course some failures :don't reproduce reliably at the same spot anyway. : :I gave out fsx source code at the recent CIFS (SMB) plugfest. If I make :the 2002 Connectathon I'll give it out there too. I don't test it on :Windows so those defines may be in need of repair. Please send me any :patches or cool additions. : :-- :Conrad Minshall, conrad@apple.com, 408 974-2749 I've already used the restart option to good effect! Awesome option! When I first ran the program it couldn't get through 10,000 operations without failing. As I started fixing things in FreeBSD the number of operations increased. When it got to around 30,000 I started using the option to reproduce the bug at the stuck-point more quickly and most of the time it worked. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:29:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6EC3A37B417; Sun, 16 Dec 2001 12:29:11 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA27695; Mon, 17 Dec 2001 07:29:08 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01KBYT8595WGVMJMZ9@cim.alcatel.com.au>; Mon, 17 Dec 2001 07:29:06 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id fBGKT5K60598; Mon, 17 Dec 2001 07:29:05 +1100 Content-return: prohibited Date: Mon, 17 Dec 2001 07:29:04 +1100 From: Peter Jeremy Subject: Re: Caldera and the Ancient UNIX license In-reply-to: <200112160618.fBG6IcK23973@minnie.tuhs.org>; from wkt@minnie.tuhs.org on Sun, Dec 16, 2001 at 05:18:37PM +1100 To: wkt@tuhs.org Cc: Greg Lehey , Terry Lambert , freebsd-hackers@FreeBSD.org Message-id: <20011217072904.P73243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20011216115556.A62493@monorchid.lemis.com> <200112160618.fBG6IcK23973@minnie.tuhs.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001-Dec-16 17:18:37 +1100, Warren Toomey wrote: >Firstly, call me crazy, but I thought the 2BSD filesystem layout was >essentially UFS, i.e i-nodes at the start, and therefore would be >pretty much the same as /sys/ufs/ufs in FreeBSD. I'll have to do a >compare of the source code and get back to you .... I'm specifically looking at 2.11BSD - which is architecturally UFS but various sizes and constants are different (eg fewer direct/indirect blocks in the inode). In some ways this simplifies things (it may be possible to re-use much or all of the FreeBSD UFS code) but it also confuses things (eg having two different struct dinode's defined, and there will probably be be global variable/function name clashes). In any case, I'm more interested in how to go about porting a new FS into FreeBSD, rather than having Terry actually do the port for me. The other almost-the-same UFS that could be useful is the Tru64 UFS. Last time I tried, I could mount a Tru64 UFS CD-ROM on FreeBSD, but the box would panic fairly quickly when I tried to access the FS (I didn't keep a close record and this was some time ago). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:40:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 03D0437B41C for ; Sun, 16 Dec 2001 12:40:17 -0800 (PST) Received: (from uucp@localhost) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) id fBGKeD417605; Sun, 16 Dec 2001 21:40:13 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.6/8.11.3) id fBGKZoF07177; Sun, 16 Dec 2001 21:35:50 +0100 (CET) (envelope-from andreas) Date: Sun, 16 Dec 2001 21:35:50 +0100 From: Andreas Klemm To: apsfilter-hackers@apsfilter.org Cc: freebsd-hackers@freebsd.org Subject: aps2file doesn't work on FreeBSD Message-ID: <20011216203550.GA7135@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i X-Operating-System: FreeBSD 4.4-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable No matter if root or not ... root@titan[ttyp2]{139} ~ aps2file -D -P lp /etc/passwd /usr/local/bin/aps2file: cannot create /dev/stdout: permission denied andreas@titan[ttyp2]{1011} ~ aps2file -D -P lp /etc/passwd /usr/local/bin/aps2file: cannot create /dev/stdout: permission denied Cc: to FreeBSD-hackers, any idea why this doesn't work ??? Here's the relevant piece of script. print2file() { : ${INPUT_FILE:=3D/dev/stdin} ${OUTPUT_FILE:=3D/dev/stdout} # start with an almost empty environment to emulate running under LPRng env -i CONTROL=3Ddummy SPOOL_DIR=3D${SPOOL:-/var/spool/lpd/$QUEUE} \ APS2FILE_CONTEXT=3Ddummy "$SHELL" $DEBUG "$APSFILTER" -h"$HOSTNAME"= \ -n"$USER" -f$(basename "$INPUT_FILE") $Z_OPTS \ < "$INPUT_FILE" > "$OUTPUT_FILE" } Andreas /// --=20 Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Arc= hives Songs from our band >> 64Bits << http://www.64bits.de Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.ht= ml --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8HQWmd3o+lGxvbLoRAlloAKCsYYhtABGUyUQG3xyaJZSR0+umyQCePVY+ 9EAxnxaIz7cKtr2U4kC+Di4= =XctA -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:48:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 4C22937B41D for ; Sun, 16 Dec 2001 12:48:39 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBGKdkP88596; Sun, 16 Dec 2001 12:39:46 -0800 (PST) (envelope-from dg) Date: Sun, 16 Dec 2001 12:39:46 -0800 From: David Greenman To: Andrew Gallatin Cc: rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011216123946.A88592@nexus.root.com> References: <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> <3C1B32EB.ACBA8DB@mindspring.com> <20011215135635.A86349@nexus.root.com> <3C1BD22F.F3A52BF4@mindspring.com> <20011215150933.B86349@nexus.root.com> <15388.48508.65545.403221@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15388.48508.65545.403221@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Sun, Dec 16, 2001 at 10:27:56AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >David Greenman writes: > > >David Greenman wrote: > > >> >In any case, disabling it is what ClickArray ended up doing, as well, > > >> >for the Tigon II, until the firmware could be fixed. > > >> > > >> We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). > > > > > >Crap. Thanks for the info. > > > > > >Have you manually calculated the checksum on a bad packet to see > > >how it's off? > > > > Yes. It's typically off by 0x1051, but varies depending on the TCP/IP > > header contents. > >Hmm.. Since you've already got the code for calculating the checksum >in the driver written, why not use it? Eg, why not pass the csum up & >set CSUM_DATA_VALID iff the csum ends up being 0? Are you worried that >the firmware will yield false posatives too? Yes, I think it can just as easily return false positives. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 12:56:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from science.slc.edu (Science.SLC.Edu [198.83.6.248]) by hub.freebsd.org (Postfix) with ESMTP id 20C5937B417 for ; Sun, 16 Dec 2001 12:56:07 -0800 (PST) Received: (from aschneid@localhost) by science.slc.edu (8.11.0/8.11.0) id fBGKrx934747; Sun, 16 Dec 2001 15:53:59 -0500 (EST) (envelope-from aschneid) Date: Sun, 16 Dec 2001 15:53:58 -0500 From: Anthony Schneider To: Andreas Klemm Cc: apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD Message-ID: <20011216155358.A34707@mail.slc.edu> References: <20011216203550.GA7135@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011216203550.GA7135@titan.klemm.gtn.com>; from andreas@apsfilter.org on Sun, Dec 16, 2001 at 09:35:50PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Well, I'm not sure if you really want to be "creating" /dev/stdout, but the $USER variable after an su is still your login name before the su. anthony:/home/anthony:24% su Password: flack# echo $USER anthony flack#=20 try it with an su -l, or explicitly set $USER to 'root', or even replace -n"$USER" with -n"root". this is all assuming that -n is specifying some sort of user privilege which you intend in this example to be root. if not, please forget this email. :) -Anthony. On Sun, Dec 16, 2001 at 09:35:50PM +0100, Andreas Klemm wrote: > No matter if root or not ... >=20 > root@titan[ttyp2]{139} ~ aps2file -D -P lp /etc/passwd > /usr/local/bin/aps2file: cannot create /dev/stdout: permission denied >=20 > andreas@titan[ttyp2]{1011} ~ aps2file -D -P lp /etc/passwd > /usr/local/bin/aps2file: cannot create /dev/stdout: permission denied >=20 > Cc: to FreeBSD-hackers, any idea why this doesn't work ??? >=20 > Here's the relevant piece of script. >=20 > print2file() > { > : ${INPUT_FILE:=3D/dev/stdin} ${OUTPUT_FILE:=3D/dev/stdout} >=20 > # start with an almost empty environment to emulate running under LPR= ng > env -i CONTROL=3Ddummy SPOOL_DIR=3D${SPOOL:-/var/spool/lpd/$QUEUE} \ > APS2FILE_CONTEXT=3Ddummy "$SHELL" $DEBUG "$APSFILTER" -h"$HOSTNAM= E" \ > -n"$USER" -f$(basename "$INPUT_FILE") $Z_OPTS \ > < "$INPUT_FILE" > "$OUTPUT_FILE" > } >=20 >=20 > Andreas /// >=20 > --=20 > Andreas Klemm > Apsfilter Homepage http://www.apsfilter.org > Support over mailing-lists (only!) http://www.apsfilter.org/support > Mailing-list archive http://www.apsfilter.org/Lists-A= rchives > Songs from our band >> 64Bits << http://www.64bits.de > Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.= html --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwdCeQACgkQ+rDjkNht5F0yXgCfdcWmrvVPPfJ69Mr5ssPzLe3z nkQAniV6IKJtSI3GclzC4J1W20IjAyhh =hp3m -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 13: 5: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 750A137B41B; Sun, 16 Dec 2001 13:04:57 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBGL4a139769; Sun, 16 Dec 2001 22:04:36 +0100 (CET) (envelope-from wkb) Date: Sun, 16 Dec 2001 22:04:36 +0100 From: Wilko Bulte To: Peter Jeremy Cc: wkt@tuhs.org, Greg Lehey , Terry Lambert , freebsd-hackers@FreeBSD.ORG Subject: Re: Caldera and the Ancient UNIX license Message-ID: <20011216220436.A39726@freebie.xs4all.nl> References: <20011216115556.A62493@monorchid.lemis.com> <200112160618.fBG6IcK23973@minnie.tuhs.org> <20011217072904.P73243@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011217072904.P73243@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Dec 17, 2001 at 07:29:04AM +1100 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 17, 2001 at 07:29:04AM +1100, Peter Jeremy wrote: > On 2001-Dec-16 17:18:37 +1100, Warren Toomey wrote: .. > The other almost-the-same UFS that could be useful is the Tru64 UFS. > Last time I tried, I could mount a Tru64 UFS CD-ROM on FreeBSD, but > the box would panic fairly quickly when I tried to access the FS (I > didn't keep a close record and this was some time ago). Assuming T64 installation CD is plain ufs I get: freebie# mount -tufs -r /dev/cd0a /mnt mount: /dev/cd0a on /mnt: incorrect super block and (assuming dumpfs is usable for this one): freebie# dumpfs /dev/cd0a magic 11954 time Fri Jul 30 00:10:11 1999 id [ 0 0 ] cylgrp dynamic inodes 4.2/4.3BSD nbfree 9265 ndir 900 nifree 64532 nffree 960 ncg 51 ncyl 809 size 640000 blocks 629375 bsize 8192 shift 13 mask 0xffffe000 fsize 1024 shift 10 mask 0xfffffc00 frag 8 shift 3 fsbtodb 1 cpg 16 bpg 1584 fpg 12672 ipg 1536 minfree 0% optim space maxcontig 4096 maxbpg 4096 rotdelay 0ms rps 90 ntrak 16 nsect 99 npsect 99 spc 1584 symlinklen 0 trackskew 7 interleave 1 contigsumsize 0 nindir 2048 inopb 64 nspf 2 maxfilesize 0 sblkno 16 cblkno 24 iblkno 32 dblkno 224 sbsize 2048 cgsize 3072 cgoffset 56 cgmask 0xfffffff0 csaddr 224 cssize 1024 shift 9 mask 0xfffffe00 cgrotor 3 fmod 0 ronly 0 clean 3 flags none blocks available in each of 8 rotational positions cylinder number 0: position 0: 0 12 18 24 35 41 47 58 64 70 81 87 93 position 1: 1 7 13 30 36 42 53 59 65 76 82 88 position 2: 2 8 19 25 31 37 43 48 54 60 66 71 77 83 89 94 position 3: 3 14 20 26 49 55 61 72 78 84 95 position 4: 9 15 21 32 38 44 67 73 79 90 96 position 5: 4 10 16 27 33 39 50 56 62 68 74 85 91 97 position 6: 5 11 22 28 34 45 51 57 80 86 92 position 7: 6 17 23 29 40 46 52 63 69 75 98 cs[].cs_(nbfree,ndir,nifree,nffree): dumpfs: /dev/cd0a: Invalid argument freebie# freebie# and on the console: dscheck(#cd/0): b_bcount 1024 is not on a sector boundary (ssize 2048) -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 13:21:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by hub.freebsd.org (Postfix) with ESMTP id D168D37B41D for ; Sun, 16 Dec 2001 13:21:26 -0800 (PST) Received: from d1o907.telia.com (d1o907.telia.com [195.252.38.241]) by mailg.telia.com (8.11.6/8.11.6) with ESMTP id fBGLLOP10899; Sun, 16 Dec 2001 22:21:24 +0100 (CET) Received: from ludd.luth.se (h216n2fls21o907.telia.com [213.66.203.216]) by d1o907.telia.com (8.8.8/8.8.8) with ESMTP id WAA02983; Sun, 16 Dec 2001 22:21:22 +0100 (CET) Message-ID: <3C1D1075.6050405@ludd.luth.se> Date: Sun, 16 Dec 2001 22:21:57 +0100 From: Joachim =?ISO-8859-1?Q?Str=F6mbergson?= Organization: =?ISO-8859-1?Q?Str=F6mbergson?= Intergalactic AB User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011121 X-Accept-Language: en-US MIME-Version: 1.0 To: Matthew Dillon Cc: Jordan Hubbard , hackers@FreeBSD.ORG Subject: Apple and BSD (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> <200112162024.fBGKOSt22277@apollo.backplane.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Aloha! Sorry to jump in here but.. I've read the thread starting with Jordans posting of the Apple testcase code with great interest. To me this has been one of the most interesting and reassuring readings in hackers for a long time. (Yes, I'm a lurker here). First, I take the testcase code as a sign that Apple does indeed give back to the Open Source community. I've read some concerns that Apple as a long time proprietary developer might not do that, but this is a good sign indeed. Second, the speed at which the FreeBSD community, especially Matt used the testcase to iron out, hunt down bugs and respond to the problems the testcase highlighted have been truly astonishing. It really shows how fast and well a community can react and be flexible and efficient. As a simple user and sysadm I'm impressed and grateful. Couln't this whole thing be documented and highlighted in the monthly development newsletter or something? It's way to good not to be written down. Just my 1 Euro. -- Med vänlig hälsning, Cheers! Joachim Strömbergson ============================================================================ Joachim Strömbergson - ASIC designer, nice to *cute* animals. snail: phone: mail & web: Sävenäsgatan 5A +46 31 - 27 98 47 watchman@ludd.luth.se 416 72 Göteborg +46 733 75 97 02 www.ludd.luth.se/~watchman ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 13:23:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 33D7C37B41D for ; Sun, 16 Dec 2001 13:23:55 -0800 (PST) Received: (from uucp@localhost) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) id fBGLK1G20952; Sun, 16 Dec 2001 22:20:01 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.6/8.11.3) id fBGLDIH00927; Sun, 16 Dec 2001 22:13:18 +0100 (CET) (envelope-from andreas) Date: Sun, 16 Dec 2001 22:13:18 +0100 From: Andreas Klemm To: Anthony Schneider Cc: apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD Message-ID: <20011216211318.GA902@titan.klemm.gtn.com> References: <20011216203550.GA7135@titan.klemm.gtn.com> <20011216155358.A34707@mail.slc.edu> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20011216155358.A34707@mail.slc.edu> User-Agent: Mutt/1.3.23.1i X-Operating-System: FreeBSD 4.4-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > try it with an su -l, or explicitly set $USER to 'root', or even replace > -n"$USER" with -n"root". this is all assuming that -n is specifying some > sort of user privilege which you intend in this example to be root. > if not, please forget this email. :) > -Anthony. I'm looking for a technical reason, why I can't write to /dev/stdout, which works under Linux but not with FreeBSD. It doesn't work for a user and not after doing a su -l. Andreas /// --=20 Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Support over mailing-lists (only!) http://www.apsfilter.org/support Mailing-list archive http://www.apsfilter.org/Lists-Arc= hives Songs from our band >> 64Bits << http://www.64bits.de Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.ht= ml --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8HQ5td3o+lGxvbLoRAmi4AJ9ZEp0VpCP5fq/NzBV0TfVw+N0APQCfW2Jk Qq0TyBM5RRmc3aLwBkya7yk= =za3c -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 16:16:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id EBB3637B41A for ; Sun, 16 Dec 2001 16:16:41 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 3BAB8786E3; Mon, 17 Dec 2001 10:46:40 +1030 (CST) Date: Mon, 17 Dec 2001 10:46:40 +1030 From: Greg Lehey To: wkt@tuhs.org Cc: Terry Lambert , Peter Jeremy , freebsd-hackers@FreeBSD.org Subject: Re: Caldera and the Ancient UNIX license Message-ID: <20011217104640.A14500@monorchid.lemis.com> References: <20011216115556.A62493@monorchid.lemis.com> <200112160618.fBG6IcK23973@minnie.tuhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112160618.fBG6IcK23973@minnie.tuhs.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 16 December 2001 at 17:18:37 +1100, Warren Toomey wrote: > In article by Greg Lehey: > [about if and how Caldera is enforcing the Ancient UNIX > http://www2.caldera.com/offers/ancient.html. Note also > that in fact they allow access to the code via > license described at http://www2.caldera.com/offers/ancient001/ > without you first agreeing to the license...] > >> That may be easier than you think. I'm copying Warren Toomey on >> this. Warren is (a) a FreeBSD user and (b) the person who negotiated >> these contracts in the first place. Warren, Peter is thinking of >> porting the 2BSD file system (not sure whether that's UFS or the >> original UNIX file system) to FreeBSD. As Terry observes, the current >> license doesn't allow that. > > Firstly, call me crazy, but I thought the 2BSD filesystem layout was > essentially UFS, i.e i-nodes at the start, and therefore would be > pretty much the same as /sys/ufs/ufs in FreeBSD. I'll have to do a > compare of the source code and get back to you .... One of the things I said before you came in was that that depends on the value of 2. 2.0BSD certainly didn't have ffs. > Which brings me to the question, does anybody know a good contact at > Caldera who can point us to the `right person' to negotiate on this. > I knew the guy at SCO who dealt with this, but not at Caldera. Hmm, I thought you would know. Have you asked Dion? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 16:53:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from science.slc.edu (Science.SLC.Edu [198.83.6.248]) by hub.freebsd.org (Postfix) with ESMTP id 3572637B419 for ; Sun, 16 Dec 2001 16:53:15 -0800 (PST) Received: (from aschneid@localhost) by science.slc.edu (8.11.0/8.11.0) id fBH0otx36256; Sun, 16 Dec 2001 19:50:55 -0500 (EST) (envelope-from aschneid) Date: Sun, 16 Dec 2001 19:50:54 -0500 From: Anthony Schneider To: Andreas Klemm Cc: apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD Message-ID: <20011216195054.A36208@mail.slc.edu> References: <20011216203550.GA7135@titan.klemm.gtn.com> <20011216155358.A34707@mail.slc.edu> <20011216211318.GA902@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011216211318.GA902@titan.klemm.gtn.com>; from andreas@apsfilter.org on Sun, Dec 16, 2001 at 10:13:18PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Well, the reason I brought up $USER inheritance is that on linux, $USER is = root after an su to root, whereas on FreeBSD, the $USER is the same as before th= e su. =20 Not really thinking, I thought that perhaps that refleted the inherited $UI= D, which I was wrong about. Sorry for that. You might want to also include the relevant open() or creat() call from the apsfilter code. -Anthony. On Sun, Dec 16, 2001 at 10:13:18PM +0100, Andreas Klemm wrote: > > try it with an su -l, or explicitly set $USER to 'root', or even replace > > -n"$USER" with -n"root". this is all assuming that -n is specifying so= me > > sort of user privilege which you intend in this example to be root. > > if not, please forget this email. :) > > -Anthony. >=20 > I'm looking for a technical reason, why I can't write to > /dev/stdout, which works under Linux but not with FreeBSD. >=20 > It doesn't work for a user and not after doing a su -l. >=20 >=20 > Andreas /// >=20 > --=20 > Andreas Klemm > Apsfilter Homepage http://www.apsfilter.org > Support over mailing-lists (only!) http://www.apsfilter.org/support > Mailing-list archive http://www.apsfilter.org/Lists-A= rchives > Songs from our band >> 64Bits << http://www.64bits.de > Inofficial band pages with add-on stuff http://www.apsfilter.org/64bits.= html --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwdQW0ACgkQ+rDjkNht5F2SJQCeMkW0Hl9cVQrfvdbQUPf74McH ZOgAn0d1pAW7OG4e7dt792tKARnij3da =B+13 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 17:40: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 04C6537B41E for ; Sun, 16 Dec 2001 17:40:01 -0800 (PST) Received: from ubik.demon.co.uk ([194.222.125.229]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 16Fml3-0003TI-0K; Mon, 17 Dec 2001 01:39:59 +0000 Message-ID: Date: Mon, 17 Dec 2001 01:37:54 +0000 To: freebsd-hackers@freebsd.org Cc: "Brandon D. Valentine" From: Tony Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <200112130608.fBD689K49906@apollo.backplane.com> <20011213043851.Y56723-100000@turtle.looksharp.net> In-Reply-To: <20011213043851.Y56723-100000@turtle.looksharp.net> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011213043851.Y56723-100000@turtle.looksharp.net>, Brandon D. Valentine writes > [snip] >but it still can't touch the FreeBSD NFS implementation. The more >robust you make it the easier it is for me to argue for deployment of >more FreeBSD systems in NFS server roles. The only advantage Linux has >got right now is XFS, which is admittedly a pretty large advantage on >multi terabyte filesystems where fsck is impossible. That is what I wanted to hear, an unambiguous argument that a solid implementation of JFS would be useful to some user segment. Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 17:40:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 548C737B41D; Sun, 16 Dec 2001 17:40:00 -0800 (PST) Received: from ubik.demon.co.uk ([194.222.125.229]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 16Fml3-0003TH-0K; Mon, 17 Dec 2001 01:39:58 +0000 Message-ID: Date: Mon, 17 Dec 2001 01:34:27 +0000 To: Greg Lehey Cc: freebsd-hackers@freebsd.org, Terry Lambert , Hiten Pandya From: Tony Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> In-Reply-To: <20011211182856.A67986@monorchid.lemis.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011211182856.A67986@monorchid.lemis.com>, Greg Lehey writes >On Monday, 10 December 2001 at 22:45:22 -0800, Terry Lambert wrote: >> >> No, it's not. The Linux JFS is derived from the OS/2 JFS code, not >> the good AIX JFS code. > >That's correct, but note that AIX is moving to this code base too, so >it's not as if it's second-rate. From what I've seen of the >structures, JFS2 is *much* better than JFS1. I haven't compared >performance. I have had a little look at the online documentation for IBM's Linux JFS project, from Steve Best & Dave Kleikamp. A few things caught my eye that would dissuade me from using Linux JFS as a base for FreeBSD: 1. "JFS only operates on meta-data ... It does not log file data or recover this data to a consistent state." [JFS overview] "The logging style introduces a synchronous write to the log disk into each inode or vfs operation that modifies meta-data." [JFS overview] This doesn't sound any more robust than FreeBSD's current Softupdates. JFS wins though as fsck is faster on a reboot ... Does AIX JFS log any file data? 2. "The minimum file system size supported by JFS is 16Mbytes." [JFS overview] "JFS will not support diskettes as an underlying file system." [JFS overview] I believe AIX JFS does support diskettes / removable media. 3. Linux JFS does not support AIX JFS volumes. [various places] I am not clear whether this is inherent in some data structures being different, or just that Linux doesn't process LVM info. JFS on AIX is "backward compatible" with Enhanced JFS (JFS2). 4. The Linux JFS driver is noticeably incomplete [from JFS todo list]: o SMP bugs. o Only 4096 byte block sizes currently supported. (512, 1024 and 2048 should be available too.) o No defrag tool. o FS resizing is not yet available. o Log file must be on the JFS partition. o Disk quotas are not currently supported. o Extended Attributes and Access Control Lists are not functional. 5. "JFS is still guru-friendly (meaning that you need a Linux guru on hand), but it will eventually grow into administrator-friendly." [JFS FAQ] I'm not sure what this means, possibly just that the FS utilities and man pages need some work. Although the "I .. never found un-resolvable problems" in the same paragraph is a shade short of a ringing endorsement of reliability. (Linux JFS was announced in May 2000, so there has been some time to work on this.) Undoubtedly JFS on FreeBSD would be expected to work with Linux JFS volumes, but inter-operation with AIX JFS & JFS2 is also desirable. My questions at this point are: * is there any IBM material, white papers or whatever, that I could study to find out about JFS(2) on AIX? * where is a good place to start learning about FreeBSD file systems, specifically UFS? Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 17:40:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 53C3C37B41C for ; Sun, 16 Dec 2001 17:40:00 -0800 (PST) Received: from ubik.demon.co.uk ([194.222.125.229]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 16Fml3-0003TG-0K; Mon, 17 Dec 2001 01:39:58 +0000 Message-ID: Date: Mon, 17 Dec 2001 01:33:40 +0000 To: freebsd-hackers@freebsd.org, Hiten Pandya From: Tony Naggs Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011211120104.28477.qmail@web21101.mail.yahoo.com> In-Reply-To: <20011211120104.28477.qmail@web21101.mail.yahoo.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011211120104.28477.qmail@web21101.mail.yahoo.com>, Hiten Pandya writes >hi, > >BTW, i am a first timer at porting a file system... That is okay, few programmers ever port more than one file system. Most useful is to have some experience programming and debugging FreeBSD kernel code. Also useful would be some knowledge of the theory; how journals for a file system work, optimizing disk accesses, etc... also to have experience in debugging or adding features to one. >if the proffesionals think that it is not wise or >useful to port the FS (especially IBM's), it is OK, Does FreeBSD have something like JFS already? No. Would it be nice to have JFS support in FreeBSD? Yes. Has anybody ever said "I would deploy 1000 FreeBSD servers if they ran JFS"? 100? 10? 1? Probably not. As I understand it, the big win with JFS is that after a system restart fsck has little to do, (barring disk media faults). Just syncing up the file system with the journaled logs. So servers with huge file systems boot up quickly. For a JFS implementation to be accepted in this environment the code has to be good, well tested and avoid hassle with GPL. (IMO) >but, just in case, anyone else (more than three >people) I think three people would be a good number. A file system is fairly small, and the parts all rely on each other. Having too many people means lots of effort is spent on sharing out tasks, coordinating, ... rather than coding & testing. The obvious splits are: file-system design & implementation, utilities, testing and documentation. >would like to port this FS to FreeBSD, my target would >be to get it done by September 2002, if we work in a >group... I don't know how hard it is to fit a new FS into FreeBSD, I haven't even done anything with the kernel up till now. So I would not want to timetable anything too strictly. Though having it available for 5.0 (Q4 20002) would be good! >i dont have web-space where i can host this project, >and we would need a mailing list... probably > >freebsd-jfs would help.. >and http://people.freebsd.org/~bsdjfs freebsd-fs is probably good enough for a mailing list, it is fairly quiet most of the time. >but thats only if three of more people are _really_ >interested in porting it... cause as you know... >porting an IBM file system (from looks) is not a >one man job :-) >Sorry, as you know, i am only 15 years old, and my It is good to be interested and enthusiastic. I do not want to put you off contributing, but I wonder what you are looking for. Committing to a project of several months seems quite a big step for someone who also has school and exams to worry about. My impression from reading your posts here, and elsewhere such as freebsd-ia64, is that you are enthusiastic but want some guidance. Can I make some suggestions: Find a small piece of work to do, maybe a few days. This will help you learn the tools and build your confidence, and also get a perspective on the work required for bigger projects. There is only one line about UFS in the FreeBSD Developers' Handbook. Maybe you could write a couple of pages about it for the documentation project. At least knowing how it interfaces to the kernel is an important step in designing and adding a new file system. Meanwhile I can research what is required to implement JFS. Then, say, after Christmas we can get together and try to make a plan for adding JFS to FreeBSD. Regards, Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 18:16:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from MAIL2.MINDANDSPIRIT.COM (mail2.mindandspirit.com [65.162.84.100]) by hub.freebsd.org (Postfix) with ESMTP id 305B337B416 for ; Sun, 16 Dec 2001 18:16:14 -0800 (PST) Received: (from apache@localhost) by MAIL2.MINDANDSPIRIT.COM (8.11.6/8.11.0) id fBH2DQH14349; Sun, 16 Dec 2001 21:13:26 -0500 Date: Sun, 16 Dec 2001 21:13:26 -0500 Message-Id: <200112170213.fBH2DQH14349@MAIL2.MINDANDSPIRIT.COM> To: FREEBSD-HACKERS@FREEBSD.ORG From: Miss Cleo subject: Linus Torvalds hope you are doing well! Content-type: text/html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cleo Flashing
 

Dear Linus Torvalds,

As a master Tarot reader I use my talents and the power of the Tarot to see into the future. My prediction abilities have been known to change lives.

Now is the time, Linus Torvalds, for your life to change.

I know that you are anxiously seeking answers that concern your life. You are likely very serious about finding out something specific. I think you know what I'm talking about…

Linus Torvalds, I want you to call us right away. I'm providing you with a special phone number to receive FREE TAROT ADVICE without any cost or obligation.

 

  

Linus Torvalds, Call Toll-Free 1-800-409-0402.

Go ahead and use this time to ask your most important questions. Get the answers you need about relationships, love, money and your future!

Linus Torvalds, it is urgent that you call as soon as possible!
With your 5 FREE MINUTES OF PSYCHIC ADVICE you'll have all the time to ask anything you want, so there's nothing to lose. Something's likely to occur in the next week that could change everything!

Don't hesitate or waste precious time!

Please call now, toll-FREE 1-800-409-0402.

Wishing you spiritual light & prayers,
Miss Cleo

P.S. This special number for FREE ADVICE is reserved for you. Please do not share it with anybody. Call immediately, Linus Torvalds, this FREE offer is for a limited time.

Call Now!
It's a FREE Call!
Call 1-800-487-1968

Si usted prefiere su lectura en español, llámenos al 800-543-4051. Esta llamada es gratis.

Must be 18+. For entertainment purposes only.

 

If you wish to unsubscribe from further emailings, please Click Here.

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 19: 8:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id F020E37B41C for ; Sun, 16 Dec 2001 19:08:28 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id fBH38SQ04185 for ; Sun, 16 Dec 2001 22:08:28 -0500 (EST) Date: Sun, 16 Dec 2001 22:08:27 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: A quick VM question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What are the backing objects of the stack and heap area of a process's address space? When are they created? I saw the code vm_map_insert(), but the object argument given is NULL. Thanks, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 16 20: 5: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fep05-svc.mail.telepac.pt (fep05-svc.mail.telepac.pt [194.65.5.209]) by hub.freebsd.org (Postfix) with ESMTP id 9978937B419 for ; Sun, 16 Dec 2001 20:04:07 -0800 (PST) Received: from user ([213.13.76.47]) by fep05-svc.mail.telepac.pt (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20011217040727.CPTQ8450.fep05-svc.mail.telepac.pt@user>; Mon, 17 Dec 2001 04:07:27 +0000 From: on5line-ads-request@o-a.com To: Subject: Information finding software Date: Sun, 16 Dec 2001 21:53:15 -0600 X-Priority: 1 X-MSMail-Priority: High Message-Id: <20011217040727.CPTQ8450.fep05-svc.mail.telepac.pt@user> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG READY TO KNOW? CONFIDENTIAL! The SOFTWARE They Want BANNED In all 50 STATES. Why? Because these secrets were never intended to reach your eyes... Get the facts on anyone Locate Missing Persons, find Lost Relatives, obtain Addresses and Phone Numbers of old school friends, even Skip Trace Dead Beat Spouses. This is not a Private Investigator, but a sophisticated SOFTWARE program DESIGNED to automatically CRACK YOUR CASE with links to thousands of Public Record databases. Find out SECRETS about your relatives, friends, enemies, and everyone else! Even your spouse! With the New, INTERNET SPY AND YOU! It's absolutely astounding! Here's what you can learn. License plate number Get anyone's name and address with just a license plate number (Find that girl you met in traffic! Driving record! Get anyone's driving record! Social security number! Trace anyone by social security number! Address! Get anyone's address with just a name! Unlisted phone numbers Get anyone's phone number with just a name even unlisted numbers! Locate! Long lost friends, relatives, a past lover who broke your heart! E-mail Send anonymous e-mail completely untraceable! Dirty secrets! Discover dirty secrets your in-laws don't want you to know! Investigate anyone! Use the sources that private investigators use (all on the Internet) secretly! Ex-spouse! Learn how to get information on an ex-spouse that will help you win in court! (Dig up old skeletons) Criminal search Background check! Find out about your daughter's boyfriend! Find out! If you are being investigated! Neighbors! Learn all about your mysterious neighbors! Find out what they have to hide! People you work with! Be astonished by what you'll learn about people you work with! Education verification! Did he really graduate college? Find out! Internet Spy and You! Software will help you discover ANYTHING about anyone, with clickable hyperlinks and no typing in Internet addresses! Just insert the floppy disk and Go! You will be shocked and amazed by the secrets that can be discovered about absolutely everyone! Find out the secrets they don't want you to know! About others, about yourself! It's INCREDIBLE what you can find out using Internet Spy and You and the Internet! You'll be riveted to your computer screen! Get the software they're trying to ban! Before it's too late! ACT NOW!! ONLY $19.95!! REGULAR PRICE $24.95 ORDER NOW AND RECEIVE THE SPY SOFTWARE FOR $19.95! THAT'S RIGHT ONLY $19.95 We will SEND YOU our Internet Spy and You SOFTWARE so you can begin discovering all the secrets you ever wanted to know! You can Know EVERYTHING about ANYONE with our Internet Spy and You Software. Works with all browsers and all versions of AOL! REGULAR PRICE IS $24.95 ORDER TODAY AND SAVE!! SEND ONLY $19.95 US FUNDS , MONEY ORDER, CASH, CHECK, OR CREDIT CARD Foreign money orders must be payable on a US BANK AND IN US FUNDS NO EXCEPTIONS! DON'T WAIT TO GET STARTED...It's as easy as 1, 2, 3. STEP 1 - Print the order form text below. STEP 2 - Type or print your order information into the order form section. STEP 3 - Mail order form and payment to the address below. Send to: GOODWINN COMMUNICATIONS 390 SOUTH TYNDALL PKWY #108 PARKER, FL 32404 Name: ________________________________________ Address: ________________________________________ City/State/Zip: ______________________________________ FOR MASTER CARD AND VISA CREDIT CARD ORDERS ONLY! Account Number: ____________________________________ Exp. Date: ________________________ Phone number required______________________________ Signature______________________ DISCLAIMER: The seller of this powerful software resource will not be held responsible for how the purchaser chooses to use it's resources. To be removed from our mailing list oscar02b@yahoo.com and put off in the subject. Thank you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 0: 7:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-d.strhg1.mi.home.com [24.13.43.207]) by hub.freebsd.org (Postfix) with ESMTP id 7F12B37B426 for ; Mon, 17 Dec 2001 00:07:52 -0800 (PST) Received: by turtle.looksharp.net (Postfix, from userid 1003) id CD3CB3ECF; Mon, 17 Dec 2001 03:09:19 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turtle.looksharp.net (Postfix) with ESMTP id C9D56BAA6; Mon, 17 Dec 2001 03:09:19 -0500 (EST) Date: Mon, 17 Dec 2001 03:09:19 -0500 (EST) From: "Brandon D. Valentine" To: Anthony Schneider Cc: Andreas Klemm , , Subject: Re: aps2file doesn't work on FreeBSD In-Reply-To: <20011216195054.A36208@mail.slc.edu> Message-ID: <20011217030451.V94172-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 16 Dec 2001, Anthony Schneider wrote: >Well, the reason I brought up $USER inheritance is that on linux, $USER >is root after an su to root, whereas on FreeBSD, the $USER is the same >as before the su. [Line wrap at 72, please] Excerpt from su(1): --- By default, the environment is unmodified with the exception of USER, HOME, and SHELL. HOME and SHELL are set to the target login's default values. USER is set to the target login, unless the target login has a user ID of 0, in which case it is unmodified. The invoked shell is the target login's. This is the traditional behavior of su. -l Simulate a full login. --- You are observing none other than the expected behavior. I have never seen Linux (GNU) su do things any differently in this regard. If they do, it's broken. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 0:59: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from science.slc.edu (Science.SLC.Edu [198.83.6.248]) by hub.freebsd.org (Postfix) with ESMTP id 97FF737B417 for ; Mon, 17 Dec 2001 00:59:00 -0800 (PST) Received: (from aschneid@localhost) by science.slc.edu (8.11.0/8.11.0) id fBH8uja40425; Mon, 17 Dec 2001 03:56:45 -0500 (EST) (envelope-from aschneid) Date: Mon, 17 Dec 2001 03:56:45 -0500 From: Anthony Schneider To: "Brandon D. Valentine" Cc: Andreas Klemm , apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD Message-ID: <20011217035644.A40375@mail.slc.edu> References: <20011216195054.A36208@mail.slc.edu> <20011217030451.V94172-100000@turtle.looksharp.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011217030451.V94172-100000@turtle.looksharp.net>; from bandix@looksharp.net on Mon, Dec 17, 2001 at 03:09:19AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Linux: anthony:/home/anthony:9% uname -a Linux lappy.slc.edu 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686 unkno= wn anthony:/home/anthony:10% su Password:=20 [root@lappy anthony]# echo $USER root [root@lappy anthony]# exit anthony:/home/anthony:11% su -l Password:=20 [root@lappy /root]# echo $USER root [root@lappy /root]#=20 FreeBSD: anthony:/home/anthony:20% uname -a FreeBSD flack.slc.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:= 55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 anthony:/home/anthony:21% su Password: flack# echo $USER anthony flack# exit anthony:/home/anthony:22% su -l Password: flack# echo $USER root flack# logout anthony:/home/anthony:23%=20 =46rom 'info su' on my linux box: By default, `su' does not change the current directory. It sets the environment variables `HOME' and `SHELL' from the password entry for USER, and if USER is not the super-user, sets `USER' and `LOGNAME' to USER. By default, the shell is not a login shell. su version (on my linux box): [root@lappy anthony]# su --version su (GNU sh-utils) 2.0 Written by David MacKenzie. Copyright (C) 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lappy anthony]#=20 Perhaps it's time to contact gnu? -Anthony. [ and apologies for the line wrapping ] On Mon, Dec 17, 2001 at 03:09:19AM -0500, Brandon D. Valentine wrote: > On Sun, 16 Dec 2001, Anthony Schneider wrote: >=20 > >Well, the reason I brought up $USER inheritance is that on linux, $USER > >is root after an su to root, whereas on FreeBSD, the $USER is the same > >as before the su. >=20 > [Line wrap at 72, please] >=20 > Excerpt from su(1): > --- > By default, the environment is unmodified with the exception of USER, > HOME, and SHELL. HOME and SHELL are set to the target login's default > values. USER is set to the target login, unless the target login has a > user ID of 0, in which case it is unmodified. The invoked shell is the > target login's. This is the traditional behavior of su. > > -l Simulate a full login. > --- >=20 > You are observing none other than the expected behavior. I have never > seen Linux (GNU) su do things any differently in this regard. If they > do, it's broken. >=20 > Brandon D. Valentine > --=20 > "Iam mens praetrepidans avet vagari." > - G. Valerius Catullus, Carmina, XLVI >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwds0QACgkQ+rDjkNht5F0pBQCeO2tVCBiOIzu3tbHo0N/nUpjM 1KkAnj8oZIAYTo2V3NAyo2QgOharyhmg =dw+V -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 1: 5: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id 13D5C37B41A for ; Mon, 17 Dec 2001 01:04:56 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id BAA22383; Mon, 17 Dec 2001 01:04:19 -0800 Message-ID: <3C1DB513.1020807@owt.com> Date: Mon, 17 Dec 2001 01:04:19 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Anthony Schneider Cc: "Brandon D. Valentine" , Andreas Klemm , apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD References: <20011216195054.A36208@mail.slc.edu> <20011217030451.V94172-100000@turtle.looksharp.net> <20011217035644.A40375@mail.slc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anthony Schneider wrote: > Linux: > > anthony:/home/anthony:9% uname -a > Linux lappy.slc.edu 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686 unknown > anthony:/home/anthony:10% su > Password: > [root@lappy anthony]# echo $USER > root > [root@lappy anthony]# exit > anthony:/home/anthony:11% su -l > Password: > [root@lappy /root]# echo $USER > root > [root@lappy /root]# It may work on Linux that way but you are supposed to do a "su -" on FreeBSD. For example, opal:kent> su Password: opal# env USER=kent opal:kent> su - Password: USER=root The system knows the difference. Kent > > > FreeBSD: > > anthony:/home/anthony:20% uname -a > FreeBSD flack.slc.edu 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 > anthony:/home/anthony:21% su > Password: > flack# echo $USER > anthony > flack# exit > anthony:/home/anthony:22% su -l > Password: > flack# echo $USER > root > flack# logout > anthony:/home/anthony:23% > > From 'info su' on my linux box: > > By default, `su' does not change the current directory. It sets the > environment variables `HOME' and `SHELL' from the password entry for > USER, and if USER is not the super-user, sets `USER' and `LOGNAME' to > USER. By default, the shell is not a login shell. > > su version (on my linux box): > > [root@lappy anthony]# su --version > su (GNU sh-utils) 2.0 > Written by David MacKenzie. > > Copyright (C) 1999 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > [root@lappy anthony]# > > Perhaps it's time to contact gnu? > > -Anthony. > > [ and apologies for the line wrapping ] > > On Mon, Dec 17, 2001 at 03:09:19AM -0500, Brandon D. Valentine wrote: > >>On Sun, 16 Dec 2001, Anthony Schneider wrote: >> >> >>>Well, the reason I brought up $USER inheritance is that on linux, $USER >>>is root after an su to root, whereas on FreeBSD, the $USER is the same >>>as before the su. >>> >>[Line wrap at 72, please] >> >>Excerpt from su(1): >>--- >>By default, the environment is unmodified with the exception of USER, >>HOME, and SHELL. HOME and SHELL are set to the target login's default >>values. USER is set to the target login, unless the target login has a >>user ID of 0, in which case it is unmodified. The invoked shell is the >>target login's. This is the traditional behavior of su. >> >>-l Simulate a full login. >>--- >> >>You are observing none other than the expected behavior. I have never >>seen Linux (GNU) su do things any differently in this regard. If they >>do, it's broken. >> >>Brandon D. Valentine >>-- >>"Iam mens praetrepidans avet vagari." >>- G. Valerius Catullus, Carmina, XLVI >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-hackers" in the body of the message >> > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 1:29: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 1C8D437B41A; Mon, 17 Dec 2001 01:29:06 -0800 (PST) Received: from pool0052.cvx40-bradley.dialup.earthlink.net ([216.244.42.52] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16Fu4t-00043y-00; Mon, 17 Dec 2001 01:28:55 -0800 Message-ID: <3C1DBAD9.67104EFA@mindspring.com> Date: Mon, 17 Dec 2001 01:28:57 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: wkt@tuhs.org, Greg Lehey , freebsd-hackers@FreeBSD.org Subject: Re: Caldera and the Ancient UNIX license References: <20011216115556.A62493@monorchid.lemis.com> <200112160618.fBG6IcK23973@minnie.tuhs.org> <20011217072904.P73243@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Jeremy wrote: > I'm specifically looking at 2.11BSD - which is architecturally UFS but > various sizes and constants are different (eg fewer direct/indirect > blocks in the inode). In some ways this simplifies things (it may be > possible to re-use much or all of the FreeBSD UFS code) but it also > confuses things (eg having two different struct dinode's defined, and > there will probably be be global variable/function name clashes). From memory, use of negative numbers to indicate indirect blocks and thus double the fields was also a recent addition by BSD 4.x. > In any case, I'm more interested in how to go about porting a new FS > into FreeBSD, rather than having Terry actually do the port for me. I'll write it up as the result of doing a port. I'd prefer something non-trivial. I could do BFS fairly easily, right now, since I have some disk images of BFS disks, and some SCO documentation. The SCO documentation on the S51K is not online since the Caldera takeover, it seems, though I have a number of installation disks for drivers for Interactive UNIX that I could use for the reference. The JFS is annoying, in that the minimal image size is 16M for a FS, since this is the smallest partition container for an aggregate, but it is also a possibility (though I will not be pulling down 16M disk images over my modem, and the need to run a local JFS, and thus risk claims of contamination is too great to cause me to pursue it now). The Trade Secret areguments are moot, for independent developement, or for redisclosure of a disclosure, though illegal, which was already made public (in fact, it is a First Ammendement right, which may be abbridged only by as a result of dire National Security interests, according to a recent Apellate Court ruling in the DeCSS case). The BSD 2.x UFS is attractive because it would be useful, as well as being close to another FS, and having (almost) the right license. I would be interested to know how it stacks up against the Net/1 and Net/2 UFS distributions (Net/2 was withdrawn by UCB as part of the USL/UCB settlement, but is still legally available elsewhere). > Last time I tried, I could mount a Tru64 UFS CD-ROM on FreeBSD, but > the box would panic fairly quickly when I tried to access the FS (I > didn't keep a close record and this was some time ago). This has potential, if you can physically give me a copy of a CDROM with one of these FS's on it, and some idea of the layout from an academic or other published source (for the purposes of reverse engineering, header files are considered published sources, for the most part, but check your license -- not the notice in the header files -- to be sure. Compaq has been rather more cooperative, in any case. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 1:46: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id A996337B432 for ; Mon, 17 Dec 2001 01:45:58 -0800 (PST) Received: from pool0052.cvx40-bradley.dialup.earthlink.net ([216.244.42.52] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16FuKu-0001qH-00; Mon, 17 Dec 2001 01:45:28 -0800 Message-ID: <3C1DBEBA.FE49EC65@mindspring.com> Date: Mon, 17 Dec 2001 01:45:30 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Anthony Schneider Cc: Andreas Klemm , apsfilter-hackers@apsfilter.org, freebsd-hackers@FreeBSD.ORG Subject: Re: aps2file doesn't work on FreeBSD References: <20011216203550.GA7135@titan.klemm.gtn.com> <20011216155358.A34707@mail.slc.edu> <20011216211318.GA902@titan.klemm.gtn.com> <20011216195054.A36208@mail.slc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anthony Schneider wrote: > > Well, the reason I brought up $USER inheritance is that on linux, $USER is root > after an su to root, whereas on FreeBSD, the $USER is the same as before the su. > Not really thinking, I thought that perhaps that refleted the inherited $UID, > which I was wrong about. Sorry for that. This is broken in Linux. USER is the login user name, which is invariant over "su", according to POSIX. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 2: 0:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wells.tecc.co.uk (wells.tecc.co.uk [195.217.37.90]) by hub.freebsd.org (Postfix) with ESMTP id 385C237B41A for ; Mon, 17 Dec 2001 02:00:20 -0800 (PST) Received: from leven (leven.tecc.co.uk [195.217.37.153]) by wells.tecc.co.uk (8.9.3+Sun/8.9.3) with SMTP id KAA12092 for ; Mon, 17 Dec 2001 10:00:19 GMT From: "Andy" To: "freebsd-hackers@FreeBSD. ORG" Subject: Q regarding booting from Mylex acceleraid170 Date: Mon, 17 Dec 2001 10:00:19 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Originally posted to questions- with no answer, maybe someone here can help? cheers Andy -----Original Message----- Sent: 12 December 2001 15:38 To: freebsd-questions@freebsd.org Subject: Q regarding booting from Mylex acceleraid170 Hi All I have a Dell Poweredge 2550 with on board SCSI 7899 controller. That controller is not actually fitted to any drives, only the tape unit (DDS3). I actually have a Mylex Acceleraid170 board attached to the four Scsi drives creating a single drive volume. All seems to work fine but the boot up is painfully slow, for example:- /kernel: acd0: CDROM at ata0-master using PIO4 /kernel: Waiting 3 seconds for SCSI devices to settle [Wait 2.5 minutes here, then] /kernel: mly0: physical device 0:6 sense data received /kernel: mly0: sense key 5 asc 00 ascq 00 /kernel: mly0: info 00000000 csi 00000000 [Wait a further 3 minutes here, then] /kernel: mly0: enclosure 6 unit 0 access offline Mounting root from ufs:/dev/da0s1a [Wait a further 2 minutes here then] /kernel: da0 at mly0 bus 1 target 0 lun 0 /kernel: da0: Fixed Direct Access SCSI-3 device /kernel: da0: 135.168MB/s transfers /kernel: da0: 34688MB (71041024 512 byte sectors: 255H 63S/T 4422C) [booting continues normally from here] Anyone any idea why this is all so slow? Not complaining too much since it works but I can't help thinking I've done something wrong because of this. fyi I'm running 4-STABLE [as of 12/12/2001] and it happens with both GENERIC and my custom kernel. Before going to STABLE I installed R4.3 from CDRom and it did the same there also (GENERIC and custom). cheers Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 2: 1: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id C849D37B41E for ; Mon, 17 Dec 2001 02:01:01 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 3154C62D01 for ; Mon, 17 Dec 2001 02:01:01 -0800 (PST) Date: Mon, 17 Dec 2001 02:01:35 -0800 (PST) From: Lamont Granquist To: Subject: What a FBSD FS needs to do? In-Reply-To: <3C1DBAD9.67104EFA@mindspring.com> Message-ID: <20011217014953.G15950-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can anyone give a brief overview (or point to one) of what a FS in FreeBSD needs to do to interact with the rest of the OS? The general picture I've got is of some code which interacts with the VFS layer above it and the block I/O layer down below it. It is this correct? And what are the APIs in those layers? (and how does the FS interact with the VM?) (I actually plan on sitting down and reading the FFS sources at some point in the near future and seeing if I can learn that way, but any help would be appreciated...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 2:17:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 537B437B416; Mon, 17 Dec 2001 02:17:24 -0800 (PST) Received: from pool0020.cvx21-bradley.dialup.earthlink.net ([209.179.192.20] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16FupX-0004dI-00; Mon, 17 Dec 2001 02:17:07 -0800 Message-ID: <3C1DC607.7A757837@mindspring.com> Date: Mon, 17 Dec 2001 02:16:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tony Cc: Greg Lehey , freebsd-hackers@freebsd.org, Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tony wrote: > 1. "JFS only operates on meta-data ... It does not log file data or > recover this data to a consistent state." [JFS overview] Yes. > "The logging style introduces a synchronous write to the log disk > into each inode or vfs operation that modifies meta-data." [JFS > overview] This is actually only for small directories an immediate metadata; most operations are in facted journalled, instead. Realize also that, though it doesn't do it, the synchronicity is once again an issue of ordered writes... so Soft Updates could be applied here. > This doesn't sound any more robust than FreeBSD's current > Softupdates. JFS wins though as fsck is faster on a reboot ... They actually discuss the failure modes for JFS, which include most reasons you would need to run an fsck. For a relatively quiescent system, the consistancy will be restored via journal pass, but if the journal consistency is bad, then it will do a full fsck. So it is likely to be necessary on IDE disks, which can spam sectors when writing during a power loss (things would be better un SCSI). Note that one of the reasons for the DC holdup time on the InterJet was to ensure the drive write cache was flushed, so that the drive was quiescent -- not in the middle of a write operation -- when DC finally failed. > Does AIX JFS log any file data? Yes (or ratherm, it journals it). And the EXT3 FS and BSD LFS do the same, and so do XFS and VxFS, though the last two do lazy synchronization. > 2. "The minimum file system size supported by JFS is 16Mbytes." [JFS > overview] Yeah, annoying, that. > "JFS will not support diskettes as an underlying file system." [JFS > overview] Just a size thing. > I believe AIX JFS does support diskettes / removable media. Yes, it does. > 3. Linux JFS does not support AIX JFS volumes. [various places] > > I am not clear whether this is inherent in some data structures > being different, or just that Linux doesn't process LVM info. This is AIX JFS vs OS/2 JFS. There would also be byte order issues, since the PPX running AIX operates in Motorolla byte order (network byte order), and not Intel byte order (wrong byte order 8^)). > JFS on AIX is "backward compatible" with Enhanced JFS (JFS2). JFS2 on AIX supports OS/2 JFS. > 4. The Linux JFS driver is noticeably incomplete [from JFS todo list]: > o SMP bugs. A given. They would need to introduce synchronization points in their SMP to address this. Linux SMP has similar problems in most code requiring ordered operations. > o Only 4096 byte block sizes currently supported. > (512, 1024 and 2048 should be available too.) It's a page granularity issue, due to explicit cache coherency requirements for an incompletely unified VM and buffer cache implementation. Going to the Intelk page size for the block size was an easy cop-out on the coherency update issues. > o No defrag tool. Actually, I saw one of these. You need to read the more detailed information, and not just the overview. > o FS resizing is not yet available. It can grow them, up to the size of the aggregate. The problem is that the LVM support for PP spanning (aggregating aggregates) is not there. Also, since they currently onbly permit a single aggregate set per partition, you tend to carve up your disks with no space to spare. In contrast, on OS/2 (or AIX, in the absence of LVM and/or disk spanning for lack of additional disks), you can have multiple aggregate sets per, so you usually end up with the whole disk being given over to a single monolithic block with multiple aggregate sets (one per FS). So I think this is just an artifact on the grow, and the lack of a defragmenter on a shrink (see above, about the defragger). > o Log file must be on the JFS partition. Not really a problem. > o Disk quotas are not currently supported. On FreeBSD, quotas should be implemented as a stacking layer with namespace folding anyway. I look at this one as "incentive". > o Extended Attributes and Access Control Lists are not functional. Actually file streams are not functional, which is not the same thing. > 5. "JFS is still guru-friendly (meaning that you need a Linux guru on > hand), but it will eventually grow into administrator-friendly." > [JFS FAQ] > > I'm not sure what this means, possibly just that the FS utilities > and man pages need some work. It means default installation using a RedHat or other Linux CDROM. > Undoubtedly JFS on FreeBSD would be expected to work with Linux JFS > volumes, but inter-operation with AIX JFS & JFS2 is also desirable. AIX JFS2 is achievable. AIX JFS is not, with that code, since it is a subset of the AIX JFS functionality, to begin with. > My questions at this point are: > * is there any IBM material, white papers or whatever, that I could > study to find out about JFS(2) on AIX? There are several "Redbooks", and a lot of white papers. > * where is a good place to start learning about FreeBSD file systems, > specifically UFS? Right now, the code. We need an FS writers guide, which is why I've made what offers I have with regards to other FS support, recently... to permit me to write one up, minimally, as a DDJ article on a porting project. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 2:19:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id E7B0B37B419 for ; Mon, 17 Dec 2001 02:19:46 -0800 (PST) Received: from pool0020.cvx21-bradley.dialup.earthlink.net ([209.179.192.20] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16Fus5-0005Wq-00; Mon, 17 Dec 2001 02:19:45 -0800 Message-ID: <3C1DC6C3.497BDF02@mindspring.com> Date: Mon, 17 Dec 2001 02:19:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: A quick VM question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang wrote: > What are the backing objects of the stack and heap area of a process's > address space? When are they created? I saw the code vm_map_insert(), but > the object argument given is NULL. Anonymous pages: swap. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 3:18:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id C17F637B41D; Mon, 17 Dec 2001 03:18:10 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.6/8.11.4) id fBHBHuF94349; Mon, 17 Dec 2001 03:17:56 -0800 (PST) (envelope-from kris) Date: Mon, 17 Dec 2001 03:17:55 -0800 From: Kris Kennaway To: "Daniel O'Connor" Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG, Alson van der Meulen Subject: Re: sha1 program Message-ID: <20011217031755.C94298@citusc17.usc.edu> References: <20011215091852.A91288@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yEPQxsgoJgBvi8ip" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from doconnor@gsoft.com.au on Sun, Dec 16, 2001 at 01:57:44PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 16, 2001 at 01:57:44PM +1030, Daniel O'Connor wrote: >=20 > On 15-Dec-2001 Kris Kennaway wrote: > > Or just ln -sf /usr/bin/openssl /usr/bin/sha1 > > =20 > > OpenSSL already checks the name it's invoked under and behaves > > accordingly. >=20 > Does it grok the options for md5? :) > -s would be easy to simulate in a shell script. > -p would be much more difficult unless openssl supports it. I have no idea off-hand what flags it supports, but I'd expect it to not be completely downwards-compatible. The OpenSSL folks might be interested in patches though. Kris --yEPQxsgoJgBvi8ip Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8HdRjWry0BWjoQKURAmSPAJ4wjKj5jT6BL8aWkCthWb2TFAnP7ACg3WvE AXYB81lbtCGP62h515qfBEA= =KfI0 -----END PGP SIGNATURE----- --yEPQxsgoJgBvi8ip-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 4: 1:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 328A437B417 for ; Mon, 17 Dec 2001 04:01:42 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id fBHC1f017113 for ; Mon, 17 Dec 2001 13:01:41 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 17 Dec 2001 13:06:04 +0100 (CET) From: Martin Blapp To: Subject: deadlock with softupdates ? Message-ID: <20011217125752.P43207-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We have a newserver running here, which freezes every 2-3 days. Break into db is still possible. It is a STABLE 4.4 machine, with new kernel. NEWS # mount /dev/da0s1a on / (ufs, local, soft-updates) /dev/da0s1e on /var (ufs, local, soft-updates) /dev/da1s1e on /news (ufs, local, soft-updates) /dev/da2s1e on /news/spool/overview (ufs, local, soft-updates) procfs on /proc (procfs, local) /dev/twed0s1e on /news/spool/articles/1 (ufs, local, soft-updates) /dev/twed1s1e on /news/spool/articles/2 (ufs, local, soft-updates) The latter two filesystems have 10 big files with the cyclic news filesystem on them. So we have a filesystem on a filesystem. I guess this is what makes the problems. I've got a kernel dump of a hanged session, but it is not very informative. bash-2.05a# ps -M /var/crash/vmcore.0 -N /usr/src/sys/compile/NEWS/kernel.deb-axl | more UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 8 289 1 100 10 0 668 0 wait IW #C5- 0:00.00 (sh) 8 290 1 100 10 0 668 0 wait IW #C5- 0:00.00 (sh) 8 292 289 0 -18 0 680 0 vmwait DL #C5- 0:30.78 (sh) 8 293 290 0 -14 0 3644 0 inode D #C5- 0:49.73 (perl) 0 12263 1 0 10 0 1200 0 wait IWs #C5 0:00.00 (login) 0 12295 12263 0 18 0 1324 0 pause IW #C5 0:00.00 (csh) 0 12297 12295 0 10 0 1060 0 wait IW #C5 0:00.00 (bash) 0 12300 12297 0 -5 0 1532 0 sysctl D+ #C5 6:58.09 (systat) 1042 677 671 0 18 0 580 0 pause IWs #C5 0:00.00 (ksh) 0 689 677 0 18 0 1336 0 pause IW #C5 0:00.00 (csh) 0 696 689 0 18 0 588 0 pause I #C5 0:00.03 (ksh) 8 13284 696 12 10 0 632 0 wait I #C5 0:00.01 (sh) 8 13742 13284 12 10 0 636 0 wait I+ #C5 0:00.01 (sh) 8 13750 13742 0 -18 0 172960 0 vmwait DL+ #C5 0:01.82 (suck) 0 317 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 316 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 315 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 314 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 313 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 312 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 319 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 318 1 0 3 0 948 0 ttyin IWs+ #C1 0:00.00 (getty) 0 12307 12306 0 10 0 1064 0 wait IWs #C9 0:00.00 (bash) 0 12312 12307 0 10 0 1064 0 wait IW #C9 0:00.00 (bash) 0 12313 12312 0 -18 0 2012 0 vmwait D+ #C9 8:22.42 (top) 0 59816 59812 0 3 0 1064 0 ttyin Is+ #C6 0:00.04 (bash) 1042 35037 35035 2 18 0 580 0 pause IWs #C6 0:00.00 (ksh) 0 35050 35037 0 18 0 1336 0 pause IW #C6 0:00.00 (csh) 0 35059 35050 0 3 0 600 0 ttyin I+ #C6 0:00.17 (ksh) 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 544 0 wait ILs ?? 0:00.01 (init) 0 2 0 0 -14 0 0 0 inode DL ?? 0:36.22 (pagedaemon 0 3 0 38 18 0 0 0 psleep DL ?? 0:00.61 (vmdaemon) 0 4 0 0 -18 0 0 0 psleep DL ?? 0:43.03 (bufdaemon) 0 5 0 0 18 0 0 0 syncer DL ?? 10:42.21 (syncer) 0 137 1 0 -18 0 2404 0 vmwait DLs ?? 0:54.90 (gated) 0 149 1 0 2 0 960 0 select Ss ?? 3:42.56 (syslogd) 0 158 1 0 2 -12 1272 0 select S: mov 0x141(%ebx),%al frame 1 at 0xd78bdc34: ebp d78bdc50, eip 0xc0238897 : add $0x10,%esp frame 2 at 0xd78bdc50: ebp d78bdd00, eip 0xc0230574 : add $0x8,%esp frame 3 at 0xd78bdd00: ebp d78bdd28, eip 0xc0284b9e : mov %eax,%ecx frame 4 at 0xd78bdd28: ebp d78bdd6c, eip 0xc02847af : jmp 0xc0284afe frame 5 at 0xd78bdd6c: ebp d78bdde4, eip 0xc0276730 : push %ebx frame 6 at 0xd78bdde4: ebp d78bde48, eip 0xc0226dbe : mov %eax,0xffffffd4(%ebp) frame 7 at 0xd78bde48: ebp d78bde7c, eip 0xc01aba18 : mov %eax,0xffffffe8(%ebp) frame 8 at 0xd78bde7c: ebp d78bdef8, eip 0xc0185cc0 : mov %eax,%esi frame 9 at 0xd78bdef8: ebp d78bdf2c, eip 0xc0185b86 : mov %eax,%esi frame 10 at 0xd78bdf2c: ebp d78bdfa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) (kgdb) defproc 13750 13750 d78cd0c0 d7b9b000 8 13742 13742 804006 3 suck vmwait c031f718 frame 0 at 0xd7b9dc08: ebp d7b9dc34, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7b9dc34: ebp d7b9dc50, eip 0xc0238897 : add $0x10,%esp frame 2 at 0xd7b9dc50: ebp d7b9dd00, eip 0xc0230574 : add $0x8,%esp frame 3 at 0xd7b9dd00: ebp d7b9dd28, eip 0xc0284b9e : mov %eax,%ecx frame 4 at 0xd7b9dd28: ebp d7b9dd6c, eip 0xc02847af : jmp 0xc0284afe frame 5 at 0xd7b9dd6c: ebp d7b9dde4, eip 0xc0276730 : push %ebx frame 6 at 0xd7b9dde4: ebp d7b9de48, eip 0xc0226dbe : mov %eax,0xffffffd4(%ebp) frame 7 at 0xd7b9de48: ebp d7b9de7c, eip 0xc01aba18 : mov %eax,0xffffffe8(%ebp) frame 8 at 0xd7b9de7c: ebp d7b9def8, eip 0xc0185cc0 : mov %eax,%esi frame 9 at 0xd7b9def8: ebp d7b9df2c, eip 0xc0185b86 : mov %eax,%esi frame 10 at 0xd7b9df2c: ebp d7b9dfa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) Do you have a clue how I can debug this problem ? Martin Martin Blapp, mb@imp.ch ------------------------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: 57E 7CCD 2769 E7AC C5FA DF2C 19C6 DCD1 1B3A EC9C ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 4:20:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nsvm09.zaq.ne.jp (nsvm09.zaq.ne.jp [211.124.0.170]) by hub.freebsd.org (Postfix) with SMTP id 4229137B429 for ; Mon, 17 Dec 2001 04:19:04 -0800 (PST) Received: (qmail 3477 invoked from network); 17 Dec 2001 21:19:01 +0900 Received: from zaqd3875bb3.zaq.ne.jp (HELO mail.njstar.net) (211.135.91.179) by nsvm09.zaq.ne.jp with SMTP; 17 Dec 2001 21:19:01 +0900 From: "Shannon.G@njstar.com" To: "8687@hotbot.com" <8687@hotbot.com> Message-ID: <1008613073.0733327407@mail.njstar.net> Subject: Conference calls are safe MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Dec 2001 04:19:04 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Take Control Of Your Conference Calls

Long Distance Conferencing
Only 18 Cents Per Minute

Connects Up To 100 Participants=21

  • No setup fees
  • No contracts or monthly fees
  • Call anytime, from anywhere, to anywhere
  • International Dial In 18 cents per minute
  • Simplicity in set up and administration
  • Operator Help available 24/7

    • G= et the best quality, the easiest to use, and lowest rate in the industry.

    If you like saving = money, fill out the form below and one of our consultants will contact you.

    Required Input Field*

    Name*
    Web Address*
    Company Name*
    State*
    Business Phone*
    Home Phone
    Email Address*
    Type of Business



    This ad is being sent in compliance with Senate Bill 1618= , Title 3, Section 301. You have recently visited our web site, referral or affiliate sit= es which indicated you were interested in communication services. If this email is reaching = you in error and you feel that you have not contacted us, Click here. We sincerely apologize, and assure you will be r= emoved from our distribution list.

    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 6:35:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 2C3EF37B416 for ; Mon, 17 Dec 2001 06:35:16 -0800 (PST) Received: from pool0043.cvx21-bradley.dialup.earthlink.net ([209.179.192.43] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FyrI-0006nc-00; Mon, 17 Dec 2001 06:35:12 -0800 Message-ID: <3C1E02A1.98BFFE5@mindspring.com> Date: Mon, 17 Dec 2001 06:35:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Lamont Granquist Cc: freebsd-hackers@FreeBSD.org Subject: Re: What a FBSD FS needs to do? References: <20011217014953.G15950-100000@coredump.scriptkiddie.org> Content-Type: multipart/mixed; boundary="------------02B49AC6CDE37E406593A945" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------02B49AC6CDE37E406593A945 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lamont Granquist wrote: > > Can anyone give a brief overview (or point to one) of what a FS in FreeBSD > needs to do to interact with the rest of the OS? The general picture I've > got is of some code which interacts with the VFS layer above it and the > block I/O layer down below it. It is this correct? And what are the APIs > in those layers? (and how does the FS interact with the VM?) Briefly, there are ~185 kernel entry points which are consumed by the FFS code. To see these, go into the directory were you build your kernel and have object files lying around, and conunt them, e.g.: # cd /sys/compile/GENERIC # sh # ld -o /tmp/ffsobj ffs* ufs* >/tmp/ffs.link 2>&1 # cd /tmp # vi ffs.link :1,$g/:$/d :1,$g/more undefined/d :1,$s/'$// :1,$s/^.*`// :x # sort -o ffs.sort < ffs.link # uniq < ffs.sort > ffs.uniq # wc -l ffs.uniq 185 I have attached an example of the result, for my older 4.x based system to this email. If you look at these, you will see 5 broad categories: 1) Kernel support services. These are things like bzero, copyin, printf, uiomove, timeout, tsleepm untimeout, etc., and are required support functions that aren't really FS specific. Another OS would call then "generic kernel services", but wouldn't have the whole story. 2) VFS services. These are things like vfs_add_vnops, vfs_export, vfs_timestamp, etc., and are required for registration and recognition of the FS as a VFS. There are also services for manipulation of VFS specific kernel resources in this category. 3) Vnode services. These are things like all of the vop_* operations, vget, vgone, NDFREE, and so on. These services services represent both VFS service, which the VFS can call for stacking reasons (it calls these services, rather than calling the VFS specific routines it defines in orcer to abstract the VFS so that you can do VFS stacking, and things won't break), and VFS specific resource that are managed by the OS (such as vnodes, etc.). Note: The NDFREE reference is actually an implemenation error, since it breaks the "caller allocates/caller frees" paradigm; this is a long-standing layering issue. 4) Virtual memory and I/O services. These are things like malloc, free, cache_enter, getblk, bread, vm_object_deallocate, vinvalbuf, etc.. These services represent the VFS' interaction with the VM system, and, as a result, the buffer cache. The spl* functions, which are used for concurrency control, as well as the locking primitives, fall into this category. It's important to note that most of these operations only exist in "local media" FSs... if your VFS were implementing a stacking layer, you would not have almost any of these used by it, since the services consumed would be pretty much covered in #3, above. 5) Miscellaneous functions. Into this category, I lump all the inconvenient to explain functions, like the spec_* functions, which implement the special device operations exported by the VFS (when you look up a device, you actually get a specfs vnode back, instead of an FFS vinode, but since the backing object is an FFS object, you have to reference it through the FFS), and, similarly, the fifo_* operations (which are used to manage named pipes -- FIFO objects -- in the same way. You would also see "__divdi3" here, as well as other systhetic functions which are, in reality, an artifact of the compiler. Practically, nearly half of these undefined symbols could be made to go away, with little to no effect on performance. In particular, the descriptor references could be factored out at FS instance time, when the mount takes place, and a stack is "frozen" as a mounted FS instance. The way you would do this is to sort the VOP and VFSOP lists, respectively, and then build direct references, rather than descriptor references, and access them by index, rather than descirptor (this would be slightly faster, too). Other references could additionally be eliminated, as they are really the result of sloppy references (e.g. the spec_* and fifo_* entries: the first by mount-based externalization and inheritance, and the seconfd by pure inheritance, enforced at instance time). A lot of the b* buffer cache operations should probably be via an ops structure dereference; this means an additional pointer dereference at runtime, so some of the wins you got by sorting the VOP list and using an index, insteaqd of areverse lookup of the descriptor reference, get paid back at that time, but overall you are still better off. Ig you have ever programmed an IFS under Windows, you are familiar with the concept of function table reference definition at IFS registration time: this is basically tyhe same approach as there). The total external exposure could therefore be dropped to perhaps 30 or more symbols, which would make understanding things a whole lot easier. As far as the externally exposed symbols are concerned, the place to look for these is in the VFSOPS and VOPS tables; these are contained in /sys/ufs/ffs/ffs_vfsops.c and /sys/ufs/ffs/ffs_vnops.c, in descriptor tables. These tables define the VFS consumer interface used to talk to an FS by any VFS layer consumer. There are three consumers of the VFS layer at present: the system calls, the static references to things like the ufs_*, fifo_*, and spec_* operations by the ffs_* code, and the NFS server code. Putatively, there is also VFS stacking modules, but since only trivial versions of those actually work (they have overly complex interaction with the VM system, in particular, the cache coherency), so they don't really count as something you have to worry about supporting at this point, at least not any more than any other VFS supports them directly. This would all be significantly better handled in the context of a journal of a new, independent FS port to FreeBSD, since it would be possible to address the more arcan issues and the issues of ideal vs. practical kernel interaction, at a much more abstract (and thus useful to future FS writers) level. Using the FFS as your example is not generally a good idea, particularly since it has some additional complexity for things like Soft Updates and legacy stuff that make it a really bad example of "how to do things the right way when you are starting from scratch". I'm pretty sure Kirk and others would agree with this assessment. In any case, there's your "brief" overview. You would do well to read John Heidemann's thesis, and the documentation for the FICUS framework out of UCLA, on which the stacking code is based, as well as Matt Dillon's small articles that give a brief overview of the FreeBSD unified VM and buffer cache system. See: ftp://ftp.cs.ucla.edu/pub/ficus/ http://www.daemonnews.org/ -- Terry --------------02B49AC6CDE37E406593A945 Content-Type: text/plain; charset=us-ascii; name="ffs.uniq" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ffs.uniq" M_TEMP NDFREE __divdi3 __moddi3 addaliasu addlog allocbuf bawrite bcmp bcopy bdevvp bdirty bdwrite biodone biowait bowrite bqrelse bread breadn brelse bremfree buf_wmesg bwillwrite bwrite bzero cache_enter cache_purge cluster_read cluster_write copyin copyinstr copyout copystr crfree curproc desiredvnodes dev2udev devsw devtoname dsname fifo_printinfo fifo_vnodeop_p fifo_vnoperate free getblk geteblk getmicrouptime getnewvnode groupmember hashinit iftovt_tab incore knote lbolt lf_advlock lockinit lockmgr lockmgr_printinfo log major makedev malloc malloc_init malloc_uninit minor mntvnode_slock module_register_init mountlist namei nchstats panic pmap_zero_page printf psignal random relookup rootdev rootvp scanc securelevel skpc spec_vnodeop_p spec_vnoperate speedup_syncer splbio splx suser_xxx sysctl__debug_children sysctl__vfs_children sysctl_handle_int tablefull time_second timeout tsleep uiomove untimeout uprintf vcount vflush vfs_add_vnodeops vfs_bio_awrite vfs_bio_clrbuf vfs_busy_pages vfs_cache_lookup vfs_export vfs_export_lookup vfs_getnewfsid vfs_getvfs vfs_modevent vfs_mountedon vfs_object_create vfs_rm_vnodeops vfs_stdextattrctl vfs_stduninit vfs_timestamp vget vgone vinvalbuf vm_freeze_copyopts vm_object_reference vm_object_vndeallocate vm_page_free_toq vm_page_zero_invalid vn_close vn_isdisk vn_lock vn_open vn_rdwr vnode_pager_generic_getpages vnode_pager_generic_putpages vnode_pager_setsize vop_access_desc vop_advlock_desc vop_balloc_desc vop_bmap_desc vop_bwrite_desc vop_cachedlookup_desc vop_close_desc vop_create_desc vop_default_desc vop_defaultop vop_freeblks_desc vop_fsync_desc vop_getattr_desc vop_getpages_desc vop_inactive_desc vop_ioctl_desc vop_islocked_desc vop_link_desc vop_lock_desc vop_lookup_desc vop_mkdir_desc vop_mknod_desc vop_mmap_desc vop_open_desc vop_pathconf_desc vop_poll_desc vop_print_desc vop_putpages_desc vop_read_desc vop_readdir_desc vop_readlink_desc vop_reallocblks_desc vop_reclaim_desc vop_remove_desc vop_rename_desc vop_rmdir_desc vop_setattr_desc vop_stdislocked vop_stdlock vop_stdpoll vop_stdunlock vop_strategy_desc vop_symlink_desc vop_unlock_desc vop_whiteout_desc vop_write_desc vprint vput vrecycle vref vrele vtruncbuf vttoif_tab wakeup --------------02B49AC6CDE37E406593A945-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 6:38:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id A48A837B416 for ; Mon, 17 Dec 2001 06:38:39 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id B653A2DE111 for ; Mon, 17 Dec 2001 08:38:38 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBHEcbm52265 for hackers@freebsd.org; Mon, 17 Dec 2001 08:38:37 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 17 Dec 2001 08:38:37 -0600 From: D J Hawkey Jr To: hackers@freebsd.org Subject: Fwd: [Re: DELACK bugfix: This tbench is giving me a fit] Message-ID: <20011217083837.A52180@sheol.localdomain> Reply-To: hawkeyd@visi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, All. A couple of friends are testing my DELACK backport, and their initial run (pre-patch) of 'tbench' is, well, outrageous. My numbers weren't anywhere near this bad. Their boxes are functional, "production" boxes, one is 4.3R and the other is 4.4S. Their hardware is [relatively] current; certainly not ancient. I queried as to whether they remembered to start 'tbench_srv'; one replied affirmative, the other hasn't gotten back to me on that. I supplied instructions to them both, and they're not dummies, so I'm confident they did. The tests are on 127.1, so NIC and network media shouldn't matter. As John asks, then, WTF??? TIA, Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ ----- Forwarded message from a friend of mine ----- It is taking over 90 minutes to run, take a look at the attached log. What am I forgetting to do? John [router:/usr/local/src/dbench]# time ./tbench 1 localhost .1 clients started ..............+* Throughput 0.0242604 MB/sec (NB=0.0303256 MB/sec 0.242604 MBit/sec) 5441.96s real 1.20s user 2.16s system ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 9:22:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.mediadesign.nl (md2.mediadesign.nl [212.19.205.67]) by hub.freebsd.org (Postfix) with SMTP id 4417A37B405 for ; Mon, 17 Dec 2001 09:22:49 -0800 (PST) Received: (qmail 6362 invoked by uid 1002); 17 Dec 2001 17:22:45 -0000 Date: Mon, 17 Dec 2001 18:22:45 +0100 From: Alson van der Meulen To: freebsd-hackers@FreeBSD.ORG Subject: Re: sha1 program Message-ID: <20011217182244.F10171@md2.mediadesign.nl> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20011215091852.A91288@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Dec 16, 2001 at 01:57:44PM +1030, Daniel O'Connor wrote: > > On 15-Dec-2001 Kris Kennaway wrote: > > Or just ln -sf /usr/bin/openssl /usr/bin/sha1 > > > > OpenSSL already checks the name it's invoked under and behaves > > accordingly. > > Does it grok the options for md5? :) > -s would be easy to simulate in a shell script. > -p would be much more difficult unless openssl supports it. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/28988 Before we start this discussion again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 10:50:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 69A3737B53A for ; Mon, 17 Dec 2001 10:48:05 -0800 (PST) Received: (qmail 8801 invoked from network); 17 Dec 2001 18:48:03 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 17 Dec 2001 18:48:03 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011217125752.P43207-100000@levais.imp.ch> Date: Mon, 17 Dec 2001 10:47:46 -0800 (PST) From: John Baldwin To: Martin Blapp Subject: RE: deadlock with softupdates ? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 17-Dec-01 Martin Blapp wrote: > > We have a newserver running here, which freezes > every 2-3 days. Break into db is still possible. > > It is a STABLE 4.4 machine, with new kernel. > > NEWS # mount > /dev/da0s1a on / (ufs, local, soft-updates) > /dev/da0s1e on /var (ufs, local, soft-updates) > /dev/da1s1e on /news (ufs, local, soft-updates) > /dev/da2s1e on /news/spool/overview (ufs, local, soft-updates) > procfs on /proc (procfs, local) > /dev/twed0s1e on /news/spool/articles/1 (ufs, local, soft-updates) > /dev/twed1s1e on /news/spool/articles/2 (ufs, local, soft-updates) > > The latter two filesystems have 10 big files with the cyclic news > filesystem on them. So we have a filesystem on a filesystem. You have lots of processes blocked in 'inode'. So it looks like it could be an inode deadlock problem. You might try mailing Kirk McKusick directly if he doesn't respond to this. Be sure and keep the debug kernel and crashdump image around. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 11: 6:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B782937B6F9; Mon, 17 Dec 2001 11:05:57 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBHJ5WG03500; Mon, 17 Dec 2001 11:05:33 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Dominic Mitchell Cc: Conrad Minshall , Matthew Dillon , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: Message from Dominic Mitchell of "17 Dec 2001 10:16:48 GMT." Date: Mon, 17 Dec 2001 11:05:32 -0800 Message-ID: <3496.1008615932@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to get the license issue clarified, then it can go in /usr/src/tools/regression. - Jordan > Jordan Hubbard writes: > > > Guy Harris of NetApp sent me a whole mess-o-changes to it and when I > > went to forward them to you, I found that I must have been in > > delete-o-matic mode at some point earlier in my inbox since it was > > gone. I've requested that he send them to me again and will forward > > them to you once I get a copy again. Whoops! > > Would it be worth making a port for this tool? It sounds like it's > too important to get lost in a mailing list archive. There's a > precedence set by having /usr/ports/sysutils/crashme. :-) > > -Dom > > -- > | Semantico: creators of major online resources | > | URL: http://www.semantico.com/ | > | Tel: +44 (1273) 722222 | > | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 11:11:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbeast.ahaza.com (mailbeast.ahaza.com [209.180.221.132]) by hub.freebsd.org (Postfix) with ESMTP id E2DBE37B75A; Mon, 17 Dec 2001 11:11:37 -0800 (PST) Received: from akira.ahaza.com (akira.ahaza.com [172.16.30.230]) by mailbeast.ahaza.com (8.11.1/8.11.1) with ESMTP id fBHJBaX77845; Mon, 17 Dec 2001 11:11:36 -0800 (PST) (envelope-from quark@akira.ahaza.com) Received: (from quark@localhost) by akira.ahaza.com (8.11.6/8.11.6) id fBHJBau00743; Mon, 17 Dec 2001 11:11:36 -0800 (PST) (envelope-from quark) Date: Mon, 17 Dec 2001 11:11:36 -0800 From: Tim Wiess To: Terry Lambert Cc: Tony , Greg Lehey , freebsd-hackers@FreeBSD.ORG, Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011217111136.A467@ahaza.com> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> <3C1DC607.7A757837@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1DC607.7A757837@mindspring.com>; from tlambert2@mindspring.com on Mon, Dec 17, 2001 at 02:16:39AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > This doesn't sound any more robust than FreeBSD's current > > Softupdates. JFS wins though as fsck is faster on a reboot ... Please correct me if I'm wrong. But I heard that Kirk (or perhaps someone else) is continuing softupdates development with the intent of removing any dependency for fsck. > > Does AIX JFS log any file data? > > Yes (or ratherm, it journals it). And the EXT3 FS and BSD LFS do the > same, and so do XFS and VxFS, though the last two do lazy synchronization. Actually, for the record, XFS only logs file metadata. > > * where is a good place to start learning about FreeBSD file systems, > > specifically UFS? Well, if you have a copy of the "Daemon Book", chapters 6 - 8 would probably be a good place to start. Also, for geneneral FS design I highly recommend Dominic Giampaolo's book "Practical File System Design". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 11:52:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D45F037B425 for ; Mon, 17 Dec 2001 11:52:32 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBHJx4302270; Mon, 17 Dec 2001 11:59:04 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112171959.fBHJx4302270@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Andy" Cc: "freebsd-hackers@FreeBSD. ORG" Subject: Re: Q regarding booting from Mylex acceleraid170 In-reply-to: Your message of "Mon, 17 Dec 2001 10:00:19 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Dec 2001 11:59:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I have a Dell Poweredge 2550 with on board SCSI 7899 controller. > That controller is not actually fitted to any drives, only the > tape unit (DDS3). > > I actually have a Mylex Acceleraid170 board attached to the four > Scsi drives creating a single drive volume. All seems to work fine > but the boot up is painfully slow, for example:- This looks like an incompatibility between the Mylex firmware and the intelligent backplane in the server: > /kernel: mly0: physical device 0:6 sense data received > /kernel: mly0: sense key 5 asc 00 ascq 00 > /kernel: mly0: info 00000000 csi 00000000 This is the Mylex card being unhappy about the backplane... > [Wait a further 3 minutes here, then] > > /kernel: mly0: enclosure 6 unit 0 access offline And here it finally gives up on it. > Anyone any idea why this is all so slow? Not complaining too > much since it works but I can't help thinking I've done something > wrong because of this. It's an incompatibility between the backplane and the Mylex controller. You might try looking for firmware upgrades from Dell or Mylex, but realistically Dell use Adaptec and AMI controllers and they aren't likely to support your use of another vendor's controllers in their hardware. Mylex technical support might have something to say on the subject, although the results you'll get will vary enormously depending on which tech you get and whether they're a Linux bigot or not. Your best alternative would be to swap to a comparable AMI controller, something like a MegaRAID Express 500. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 12: 2:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 729C337B41E for ; Mon, 17 Dec 2001 12:02:26 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBHK2I332492; Mon, 17 Dec 2001 12:02:18 -0800 (PST) (envelope-from dillon) Date: Mon, 17 Dec 2001 12:02:18 -0800 (PST) From: Matthew Dillon Message-Id: <200112172002.fBHK2I332492@apollo.backplane.com> To: Martin Blapp Cc: Subject: Re: deadlock with softupdates ? References: <20011217125752.P43207-100000@levais.imp.ch> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :We have a newserver running here, which freezes :every 2-3 days. Break into db is still possible. : :It is a STABLE 4.4 machine, with new kernel. Yahoo noticed a deadlock in the vnode recycling code. If your machine below is hitting the kern.maxvnodes limit it could be the same thing. The way to tell is to generate a kernel core along with the debug version of the kernel binary (/usr/src/sys/compile//kernel.debug), and backtrace each locked-up process to see if any of them are going through the recycle code. Yahoo has a fix for that particular problem that they and I are testing. -Matt :NEWS # mount :/dev/da0s1a on / (ufs, local, soft-updates) :/dev/da0s1e on /var (ufs, local, soft-updates) :/dev/da1s1e on /news (ufs, local, soft-updates) :/dev/da2s1e on /news/spool/overview (ufs, local, soft-updates) :procfs on /proc (procfs, local) :/dev/twed0s1e on /news/spool/articles/1 (ufs, local, soft-updates) :/dev/twed1s1e on /news/spool/articles/2 (ufs, local, soft-updates) : :The latter two filesystems have 10 big files with the cyclic news :filesystem on them. So we have a filesystem on a filesystem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 12:53:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web13401.mail.yahoo.com (web13401.mail.yahoo.com [216.136.175.59]) by hub.freebsd.org (Postfix) with SMTP id F1E9237B416 for ; Mon, 17 Dec 2001 12:53:27 -0800 (PST) Message-ID: <20011217205327.26677.qmail@web13401.mail.yahoo.com> Received: from [65.80.95.196] by web13401.mail.yahoo.com via HTTP; Mon, 17 Dec 2001 12:53:27 PST Date: Mon, 17 Dec 2001 12:53:27 -0800 (PST) From: "Pedro F. Giffuni" Reply-To: giffunip@yahoo.com Subject: Re: Adding a new FS to FreeBSD To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If it's just for the exercise of porting a filesystem, there are at least three filesystems available under a BSD license: 1) Minix: all the OS was released under a BSD like license, not to mention that it is perfectly documented. 2,3) NetBSD's ext2fs and LFS have surely been updated for their UBC effort. These probably wouldn't have any advantage over FFS though. If someone has a wishlist it would be nice to be able to mount the FFS variant's, not only Tru64 UFS, but especifically Solaris. Now that a SPARC64 port is coming it would be really handy. just my $0.02, Pedro. __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 13:31:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 308A637B405 for ; Mon, 17 Dec 2001 13:31:17 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id fBHLVD093995; Mon, 17 Dec 2001 22:31:13 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 17 Dec 2001 22:35:36 +0100 (CET) From: Martin Blapp To: Matthew Dillon Cc: Subject: Re: deadlock with softupdates ? In-Reply-To: <200112172002.fBHK2I332492@apollo.backplane.com> Message-ID: <20011217223123.P59342-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Matt, > Yahoo noticed a deadlock in the vnode recycling code. If your machine > below is hitting the kern.maxvnodes limit it could be the same thing. > The way to tell is to generate a kernel core along with the debug > version of the kernel binary (/usr/src/sys/compile//kernel.debug), > and backtrace each locked-up process to see if any of them are going > through the recycle code. It cannot be kern.maxvnodes, cause the newsserver is using the cyclic news filesystem. And there is also enough ram. It seems to be a vnode deadlock: (kgdb) defproc 2 2 d78cd0c0 d6445000 0 0 0 100204 3 pagedaemon inode c2c0c200 frame 0 at 0xd6447e24: ebp d6447e50, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd6447e50: ebp d6447e74, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd6447e74: ebp d6447e98, eip 0xc0171ea5 : mov %eax,%edi frame 3 at 0xd6447e98: ebp d6447eb0, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd6447eb0: ebp d6447ebc, eip 0xc022e44d : leave frame 5 at 0xd6447ebc: ebp d6447ee4, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd6447ee4: ebp d6447f00, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd6447f00: ebp d6447f84, eip 0xc023a52d : add $0xc,%esp frame 8 at 0xd6447f84: ebp d6447f9c, eip 0xc023af53 : movl $0x0,0xc02eff1c (kgdb) x/x 0xd6447f00 0xd6447f00: 0xd6447f84 (kgdb) x/10 0xd6447f00 0xd6447f00: 0xd6447f84 0xc023a52d 0xd7e5a180 0x00040002 0xd6447f10: 0xd47c2c60 0x00000000 0x00000000 0x00000000 0xd6447f20: 0xd7e5a180 0x00000020 (kgdb) showcache 0xd7e5a180 history.hash Can you help me to debug this bug ? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 13:41:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 51A9A37B41E for ; Mon, 17 Dec 2001 13:41:30 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBHLfSc33112; Mon, 17 Dec 2001 13:41:28 -0800 (PST) (envelope-from dillon) Date: Mon, 17 Dec 2001 13:41:28 -0800 (PST) From: Matthew Dillon Message-Id: <200112172141.fBHLfSc33112@apollo.backplane.com> To: Martin Blapp Cc: Subject: Re: deadlock with softupdates ? References: <20011217223123.P59342-100000@levais.imp.ch> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If it is a vnode deadlock you have to find which process or processes it is deadlocking against. Do a ps -axl -M vmcore.X -N kernel.X on the kernel core, pick out all the processes blocked on inode or whatever, then from gdb go to each process (proc N) and do a backtrace (back). -Matt Matthew Dillon : : :Hi Matt, : :> Yahoo noticed a deadlock in the vnode recycling code. If your machine :> below is hitting the kern.maxvnodes limit it could be the same thing. :> The way to tell is to generate a kernel core along with the debug :> version of the kernel binary (/usr/src/sys/compile//kernel.debug), :> and backtrace each locked-up process to see if any of them are going :> through the recycle code. : :It cannot be kern.maxvnodes, cause the newsserver is using the cyclic :news filesystem. And there is also enough ram. : :It seems to be a vnode deadlock: : :(kgdb) defproc 2 : 2 d78cd0c0 d6445000 0 0 0 100204 3 pagedaemon inode c2c0c200 : frame 0 at 0xd6447e24: ebp d6447e50, eip 0xc017a529 : mov 0x141(%ebx),%al : frame 1 at 0xd6447e50: ebp d6447e74, eip 0xc0171c24 : mov %eax,%esi : frame 2 at 0xd6447e74: ebp d6447e98, eip 0xc0171ea5 : mov %eax,%edi : frame 3 at 0xd6447e98: ebp d6447eb0, eip 0xc01a2008 : jmp 0xc01a200e : frame 4 at 0xd6447eb0: ebp d6447ebc, eip 0xc022e44d : leave : frame 5 at 0xd6447ebc: ebp d6447ee4, eip 0xc01ac04b : add $0x4,%esp : frame 6 at 0xd6447ee4: ebp d6447f00, eip 0xc01a4e18 : mov %eax,%esi : frame 7 at 0xd6447f00: ebp d6447f84, eip 0xc023a52d : add $0xc,%esp : frame 8 at 0xd6447f84: ebp d6447f9c, eip 0xc023af53 : movl $0x0,0xc02eff1c : :(kgdb) x/x 0xd6447f00 :0xd6447f00: 0xd6447f84 :(kgdb) x/10 0xd6447f00 :0xd6447f00: 0xd6447f84 0xc023a52d 0xd7e5a180 0x00040002 :0xd6447f10: 0xd47c2c60 0x00000000 0x00000000 0x00000000 :0xd6447f20: 0xd7e5a180 0x00000020 :(kgdb) showcache 0xd7e5a180 :history.hash : :Can you help me to debug this bug ? : :Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 13:46:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id DFF3737B405; Mon, 17 Dec 2001 13:46:49 -0800 (PST) Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id fBHLkmu29351; Mon, 17 Dec 2001 13:46:49 -0800 (PST) Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Mon, 17 Dec 2001 13:46:40 -0800 Received: from [17.219.180.26] (minshallidsl1.apple.com [17.219.180.26]) by scv2.apple.com (8.11.3/8.11.3) with ESMTP id fBHLkHB14100; Mon, 17 Dec 2001 13:46:17 -0800 (PST) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <200112162024.fBGKOSt22277@apollo.backplane.com> References: <58885.1008217148@winston.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Dec 2001 13:45:18 -0800 To: Matthew Dillon From: Conrad Minshall Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@freebsd.org, msmith@mass.dis.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:24 PM -0800 12/16/01, Matthew Dillon wrote: > program runs fine in an overnight test. We still have a known issue > with out-of-order operations from nfsiod's that apparently may come > up after a week or so of testing. I asked Jordan to try to track down > the NeXT guy who fixed that one in the old NFS stack. This bug showed up recently here with fsx testing. I seem to have fixed it last week in MacOS X. The diffs were widespread but the idea was simple enough so a few code snippets should suffice: nfs_request gets a new argument (u_int64_t *xidp) and fills it in here: m = nfsm_rpchead(cred, nmp->nm_flag, procnum, auth_type, auth_len, auth_str, verf_len, verf_str, mrest, mrest_len, &mheadend, &xid); if (xidp) *xidp = xid + ((u_int64_t)nfs_xidwrap << 32); nfsm_rpchead bumps nfs_xidwrap when avoiding a zero xid. Callers of nfs_request take the returned xid and pass it via the macros to nfs_loadattrcache, from which the following code is snipped: if (*xidp < np->n_xid) { /* * We have already updated attributes with a response from * a later request. The attributes we have here are probably * stale so we drop them (just return). However, our * out-of-order receipt could be correct - if the requests were * processed out of order at the server. Given the uncertainty * we invalidate our cached attributes. *xidp is zeroed here * to indicate the attributes were dropped - only getattr * cares - it needs to retry the rpc. */ np->n_attrstamp = 0; *xidp = 0; return (0); } Further down in nfs_loadattrcache: np->n_xid = *xidp; Note xids are kept in a 64 bit form so relative comparison won't fail in the unlikely case that xids wrap around zero. Here's the change in nfs_getattr. I don't expect to ever see the panic. avoidfloods = 0; tryagain: nfsstats.rpccnt[NFSPROC_GETATTR]++; nfsm_reqhead(vp, NFSPROC_GETATTR, NFSX_FH(v3)); nfsm_fhtom(vp, v3); nfsm_request(vp, NFSPROC_GETATTR, ap->a_p, ap->a_cred, &xid); if (!error) { nfsm_loadattr(vp, ap->a_vap, &xid); if (!xid) { /* out-of-order rpc - attributes were dropped */ m_freem(mrep); if (avoidfloods++ < 100) goto tryagain; /* * avoidfloods>1 is bizarre. at 100 pull the plug */ panic("nfs_getattr: getattr flood\n"); } -- Conrad Minshall, conrad@apple.com, 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 13:54:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id DDEE037B41C; Mon, 17 Dec 2001 13:54:18 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id fBHLsF095498; Mon, 17 Dec 2001 22:54:15 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 17 Dec 2001 22:58:39 +0100 (CET) From: Martin Blapp To: Matthew Dillon , Cc: Subject: Re: deadlock with softupdates ? In-Reply-To: <200112172141.fBHLfSc33112@apollo.backplane.com> Message-ID: <20011217225006.T59342-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Do a ps -axl -M vmcore.X -N kernel.X on the kernel core, > pick out all the processes blocked on inode or whatever, inode ps -axl -M vmcore.0 -N /usr/src/sys/compile/NEWS/kernel.debug | grep inode 8 293 290 0 -14 0 3644 0 inode D #C5- 0:49.73 (perl) 0 2 0 0 -14 0 0 0 inode DL ?? 0:36.22 (pagedaemon) 8 288 1 0 -14 0 133420 0 inode DLs ?? 28:25.45 (innd) 8 13771 288 0 -14 4 2072 0 inode DN ?? 0:00.01 (nnrpd) 8 13775 288 0 -14 4 2128 0 inode DN ?? 0:00.01 (nnrpd) 8 13779 288 0 -14 4 2120 0 inode DN ?? 0:00.01 (nnrpd) 8 13781 288 0 -14 4 45968 0 inode DN ?? 0:00.01 (nnrpd) > then from gdb go to each process (proc N) and do a backtrace > (back). (kgdb) defproc 288 288 d78cd0c0 d788e000 8 1 288 000005 3 innd inode c2c0c200 frame 0 at 0xd7890d8c: ebp d7890db8, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7890db8: ebp d7890ddc, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd7890ddc: ebp d7890e00, eip 0xc0171cd4 : mov %eax,%edi frame 3 at 0xd7890e00: ebp d7890e18, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd7890e18: ebp d7890e24, eip 0xc022e44d : leave frame 5 at 0xd7890e24: ebp d7890e4c, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd7890e4c: ebp d7890e68, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd7890e68: ebp d7890e84, eip 0xc023d038 : add $0xc,%esp frame 8 at 0xd7890e84: ebp d7890f34, eip 0xc023060c : mov %eax,0xffffffbc(%ebp) frame 9 at 0xd7890f34: ebp d7890f5c, eip 0xc0284b9e : mov %eax,% (kgdb) defproc 293 293 d78cd0c0 d7888000 8 290 6 004006 3 perl inode c1f87400 frame 0 at 0xd788abe8: ebp d788ac14, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd788ac14: ebp d788ac38, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd788ac38: ebp d788ac5c, eip 0xc0171e88 : mov %eax,%edi frame 3 at 0xd788ac5c: ebp d788ac74, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd788ac74: ebp d788ac80, eip 0xc022e44d : leave frame 5 at 0xd788ac80: ebp d788aca8, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd788aca8: ebp d788acc4, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd788acc4: ebp d788ace8, eip 0xc02290d4 : add $0xc,%esp frame 8 at 0xd788ace8: ebp d788ad20, eip 0xc02265de : mov 0x10(%ebp),%ecx frame 9 at 0xd788ad20: ebp d788ad38, eip 0xc022b964 : test %eax,%eax frame 10 at 0xd788ad38: ebp d788ad84, eip 0xc01a32b6 : mov %eax,0xffffffd8(%ebp) frame 11 at 0xd788ad84: ebp d788add8, eip 0xc01a2c74 : mov %eax,%ebx frame 12 at 0xd788add8: ebp d788ae74, eip 0xc01ab45f : mov %eax,%ebx frame 13 at 0xd788ae74: ebp d788af2c, eip 0xc01a7568 : mov %eax,%ebx frame 14 at 0xd788af2c: ebp d788afa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) (kgdb) defproc 13771 13771 d78cd0c0 d7c16000 8 288 288 004004 3 nnrpd inode c2024b00 frame 0 at 0xd7c18c08: ebp d7c18c34, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7c18c34: ebp d7c18c58, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd7c18c58: ebp d7c18c7c, eip 0xc0171ea5 : mov %eax,%edi frame 3 at 0xd7c18c7c: ebp d7c18c94, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd7c18c94: ebp d7c18ca0, eip 0xc022e44d : leave frame 5 at 0xd7c18ca0: ebp d7c18cc8, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd7c18cc8: ebp d7c18ce4, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd7c18ce4: ebp d7c18d30, eip 0xc01a01b3 : mov %eax,%ebx frame 8 at 0xd7c18d30: ebp d7c18d3c, eip 0xc022e44d : leave frame 9 at 0xd7c18d3c: ebp d7c18d84, eip 0xc01a3179 : mov %eax,0xffffffd8(%ebp) frame 10 at 0xd7c18d84: ebp d7c18dd8, eip 0xc01a2c74 : mov %eax,%ebx frame 11 at 0xd7c18dd8: ebp d7c18e74, eip 0xc01ab45f : mov %eax,%ebx frame 12 at 0xd7c18e74: ebp d7c18f2c, eip 0xc01a7568 : mov %eax,%ebx frame 13 at 0xd7c18f2c: ebp d7c18fa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) (kgdb) defproc 13775 13775 d78cd0c0 d7b17000 8 288 288 004004 3 nnrpd inode c1f87400 frame 0 at 0xd7b19c7c: ebp d7b19ca8, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7b19ca8: ebp d7b19ccc, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd7b19ccc: ebp d7b19cf0, eip 0xc0171e88 : mov %eax,%edi frame 3 at 0xd7b19cf0: ebp d7b19d08, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd7b19d08: ebp d7b19d14, eip 0xc022e44d : leave frame 5 at 0xd7b19d14: ebp d7b19d3c, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd7b19d3c: ebp d7b19d58, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd7b19d58: ebp d7b19d7c, eip 0xc02290d4 : add $0xc,%esp frame 8 at 0xd7b19d7c: ebp d7b19db4, eip 0xc02265de : mov 0x10(%ebp),%ecx frame 9 at 0xd7b19db4: ebp d7b19dcc, eip 0xc022b964 : test %eax,%eax frame 10 at 0xd7b19dcc: ebp d7b19e18, eip 0xc01a32b6 : mov %eax,0xffffffd8(%ebp) frame 11 at 0xd7b19e18: ebp d7b19e6c, eip 0xc01a2c74 : mov %eax,%ebx frame 12 at 0xd7b19e6c: ebp d7b19f2c, eip 0xc01a86b5 : mov %eax,%ebx frame 13 at 0xd7b19f2c: ebp d7b19fa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) (kgdb) defproc 13779 13779 d78cd0c0 d7b7f000 8 288 288 004004 3 nnrpd inode c1f87400 frame 0 at 0xd7b81be8: ebp d7b81c14, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7b81c14: ebp d7b81c38, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd7b81c38: ebp d7b81c5c, eip 0xc0171e88 : mov %eax,%edi frame 3 at 0xd7b81c5c: ebp d7b81c74, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd7b81c74: ebp d7b81c80, eip 0xc022e44d : leave frame 5 at 0xd7b81c80: ebp d7b81ca8, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd7b81ca8: ebp d7b81cc4, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd7b81cc4: ebp d7b81ce8, eip 0xc02290d4 : add $0xc,%esp frame 8 at 0xd7b81ce8: ebp d7b81d20, eip 0xc02265de : mov 0x10(%ebp),%ecx frame 9 at 0xd7b81d20: ebp d7b81d38, eip 0xc022b964 : test %eax,%eax frame 10 at 0xd7b81d38: ebp d7b81d84, eip 0xc01a32b6 : mov %eax,0xffffffd8(%ebp) frame 11 at 0xd7b81d84: ebp d7b81dd8, eip 0xc01a2c74 : mov %eax,%ebx frame 12 at 0xd7b81dd8: ebp d7b81e74, eip 0xc01ab45f : mov %eax,%ebx frame 13 at 0xd7b81e74: ebp d7b81f2c, eip 0xc01a7568 : mov %eax,%ebx frame 14 at 0xd7b81f2c: ebp d7b81fa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) (kgdb) defproc 13781 13781 d78cd0c0 d7911000 8 288 288 004004 3 nnrpd inode c2024c00 frame 0 at 0xd7913c08: ebp d7913c34, eip 0xc017a529 : mov 0x141(%ebx),%al frame 1 at 0xd7913c34: ebp d7913c58, eip 0xc0171c24 : mov %eax,%esi frame 2 at 0xd7913c58: ebp d7913c7c, eip 0xc0171e88 : mov %eax,%edi frame 3 at 0xd7913c7c: ebp d7913c94, eip 0xc01a2008 : jmp 0xc01a200e frame 4 at 0xd7913c94: ebp d7913ca0, eip 0xc022e44d : leave frame 5 at 0xd7913ca0: ebp d7913cc8, eip 0xc01ac04b : add $0x4,%esp frame 6 at 0xd7913cc8: ebp d7913ce4, eip 0xc01a4e18 : mov %eax,%esi frame 7 at 0xd7913ce4: ebp d7913d30, eip 0xc01a01b3 : mov %eax,%ebx frame 8 at 0xd7913d30: ebp d7913d3c, eip 0xc022e44d : leave frame 9 at 0xd7913d3c: ebp d7913d84, eip 0xc01a3179 : mov %eax,0xffffffd8(%ebp) frame 10 at 0xd7913d84: ebp d7913dd8, eip 0xc01a2c74 : mov %eax,%ebx frame 11 at 0xd7913dd8: ebp d7913e74, eip 0xc01ab45f : mov %eax,%ebx frame 12 at 0xd7913e74: ebp d7913f2c, eip 0xc01a7568 : mov %eax,%ebx frame 13 at 0xd7913f2c: ebp d7913fa0, eip 0xc028520d : mov %eax,0xffffffb8(%ebp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 14:13:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0DA2437B419; Mon, 17 Dec 2001 14:13:55 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBHMDp633346; Mon, 17 Dec 2001 14:13:51 -0800 (PST) (envelope-from dillon) Date: Mon, 17 Dec 2001 14:13:51 -0800 (PST) From: Matthew Dillon Message-Id: <200112172213.fBHMDp633346@apollo.backplane.com> To: Martin Blapp Cc: , Subject: Re: deadlock with softupdates ? References: <20011217225006.T59342-100000@levais.imp.ch> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> then from gdb go to each process (proc N) and do a backtrace :> (back). : :(kgdb) defproc 288 : 288 d78cd0c0 d788e000 8 1 288 000005 3 innd inode :c2c0c200 : frame 0 at 0xd7890d8c: ebp d7890db8, eip 0xc017a529 : mov 0x141(%ebx),%al : frame 1 at 0xd7890db8: ebp d7890ddc, eip 0xc0171c24 : mov %eax,%esi : frame 2 at 0xd7890ddc: ebp d7890e00, eip 0xc0171cd4 : mov %eax,%edi : frame 3 at 0xd7890e00: ebp d7890e18, eip 0xc01a2008 : jmp 0xc01a200e : frame 4 at 0xd7890e18: ebp d7890e24, eip 0xc022e44d : leave : frame 5 at 0xd7890e24: ebp d7890e4c, eip 0xc01ac04b : add $0x4,%esp : frame 6 at 0xd7890e4c: ebp d7890e68, eip 0xc01a4e18 : mov %eax,%esi : frame 7 at 0xd7890e68: ebp d7890e84, eip 0xc023d038 : add $0xc,%esp : frame 8 at 0xd7890e84: ebp d7890f34, eip 0xc023060c : mov %eax,0xffffffbc(%ebp) : frame 9 at 0xd7890f34: ebp d7890f5c, eip 0xc0284b9e : mov %eax,% Are you sure this is the correct kernel binary? zinitna() doesn't call vget() and vm_fault doesn't call zinitna. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 14:19:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 618A137B405; Mon, 17 Dec 2001 14:19:24 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id fBHMJK096833; Mon, 17 Dec 2001 23:19:20 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 17 Dec 2001 23:23:44 +0100 (CET) From: Martin Blapp To: Matthew Dillon Cc: , Subject: Re: deadlock with softupdates ? In-Reply-To: <200112172213.fBHMDp633346@apollo.backplane.com> Message-ID: <20011217231944.S59342-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Matt, > Are you sure this is the correct kernel binary? zinitna() doesn't > call vget() and vm_fault doesn't call zinitna. Hrm, sorry, I just have noted that the debug kernel produces slightly different output that the normal kernel :-( Why this ? I didn't do a cvs update since I built the kernel. (kgdb) proc 293 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171e88 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc02290d4 in ufs_ihashget () #9 0xc02265de in ffs_vget () #10 0xc022b964 in ufs_root () #11 0xc01a32b6 in lookup () #12 0xc01a2c74 in namei () #13 0xc01ab45f in vn_open () #14 0xc01a7568 in open () #15 0xc028520d in syscall2 () #16 0xc02767b5 in Xint0x80_syscall () #17 0x48082c6f in ?? () #18 0x4808729b in ?? () #19 0x4807e11d in ?? () #20 0x480e7ebd in ?? () #21 0x8048e75 in ?? () #22 0x8048d61 in ?? () (kgdb) proc 2 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171ea5 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc023a52d in vm_pageout_scan () #9 0xc023af53 in vm_pageout () (kgdb) proc 288 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171cd4 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc023d038 in vnode_pager_lock () #9 0xc023060c in vm_fault () #10 0xc0284b9e in trap_pfault () #11 0xc0284663 in trap () #12 0x807e5e7 in ?? () #13 0x807dfb4 in ?? () #14 0x80595d1 in ?? () #15 0x805e6d8 in ?? () #16 0x805d5fa in ?? () #17 0x805e271 in ?? () #18 0x80589ab in ?? () #19 0x805bec5 in ?? () #20 0x804f1e1 in ?? () (kgdb) proc 13771 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171ea5 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc01a01b3 in vfs_cache_lookup () #9 0xc022e44d in ufs_vnoperate () #10 0xc01a3179 in lookup () #11 0xc01a2c74 in namei () #12 0xc01ab45f in vn_open () #13 0xc01a7568 in open () #14 0xc028520d in syscall2 () #15 0xc02767b5 in Xint0x80_syscall () #16 0x807a646 in ?? () #17 0x80755ca in ?? () #18 0x8056052 in ?? () #19 0x804ea19 in ?? () (kgdb) proc 13775 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171e88 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc02290d4 in ufs_ihashget () #9 0xc02265de in ffs_vget () #10 0xc022b964 in ufs_root () #11 0xc01a32b6 in lookup () #12 0xc01a2c74 in namei () #13 0xc01a86b5 in stat () #14 0xc028520d in syscall2 () #15 0xc02767b5 in Xint0x80_syscall () #16 0x806334f in ?? () #17 0x8063add in ?? () #18 0x805e9b6 in ?? () #19 0x8055ece in ?? () #20 0x8056825 in ?? () #21 0x804ea19 in ?? () (kgdb) proc 13779 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171e88 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc02290d4 in ufs_ihashget () #9 0xc02265de in ffs_vget () #10 0xc022b964 in ufs_root () #11 0xc01a32b6 in lookup () #12 0xc01a2c74 in namei () #13 0xc01ab45f in vn_open () #14 0xc01a7568 in open () #15 0xc028520d in syscall2 () #16 0xc02767b5 in Xint0x80_syscall () #17 0x807280e in ?? () #18 0x805e387 in ?? () #19 0x805e96c in ?? () #20 0x8055ece in ?? () #21 0x8056825 in ?? () #22 0x804ea19 in ?? () (kgdb) proc 13781 (kgdb) bt #0 0xc017ad88 in mi_switch () #1 0xc017a529 in tsleep () #2 0xc0171c24 in acquire () #3 0xc0171e88 in lockmgr () #4 0xc01a2008 in vop_stdlock () #5 0xc022e44d in ufs_vnoperate () #6 0xc01ac04b in vn_lock () #7 0xc01a4e18 in vget () #8 0xc01a01b3 in vfs_cache_lookup () #9 0xc022e44d in ufs_vnoperate () #10 0xc01a3179 in lookup () #11 0xc01a2c74 in namei () #12 0xc01ab45f in vn_open () #13 0xc01a7568 in open () #14 0xc028520d in syscall2 () #15 0xc02767b5 in Xint0x80_syscall () #16 0x804efd3 in ?? () #17 0x8055f10 in ?? () #18 0x8056825 in ?? () #19 0x804ea19 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 14:34:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 9FCEA37B41A for ; Mon, 17 Dec 2001 14:34:09 -0800 (PST) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.6/8.11.6) with ESMTP id fBHMY1u90733; Mon, 17 Dec 2001 15:34:02 -0700 (MST) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200112172234.fBHMY1u90733@hunkular.glarp.com> To: Bruce M Simpson Cc: freebsd-hackers@freebsd.org Subject: Re: closeing files in detach() In-Reply-To: Your message of "Mon, 17 Dec 2001 04:03:03 GMT." <20011217040303.E7698@spc.org> Date: Mon, 17 Dec 2001 15:34:01 -0700 From: Brad Huntting Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I wrote the driver against -CURRENT, but browsing through > on a 4.4-STABLE box reveals that specfs is in use there, too. I haven't > been trying my driver out against -STABLE yet, but -CURRENT works just fine. > > typedef struct specinfo *dev_t; > ^ this is what I have in 4.4-STABLE. Oops... It seems this is what you get with -D_KERNEL, but userland programs see an int. Ok. thanx! brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 14:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id EAA7E37B41C for ; Mon, 17 Dec 2001 14:46:09 -0800 (PST) Received: (qmail 35688 invoked by uid 3193); 17 Dec 2001 22:46:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Dec 2001 22:46:08 -0000 Date: Mon, 17 Dec 2001 17:46:08 -0500 (EST) From: Mike Silbersack X-Sender: To: Cc: , Subject: Re: 3Com driver problems (fixed) In-Reply-To: <14a.5dcd50d.294e390f@aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 16 Dec 2001 TD790@aol.com wrote: > ping is not a very good test...one of the reasons that most people cant find > problems generally. plus you want to use smaller packets to get the pps up. > The ave size packet is under 400 bytes on the net and it better simulates > real life. Once you saturate the wire the lockup occurs rather > quickly....you have to get to the point where the overflows are happening > faster than the machine can process the interupts. Blah blah blah blah blah. I know ping isn't a great network diagnostic tool, but it allowed me to see the problem easily. You're welcome to run further tests with your flooder of choice to confirm my findings. The problem with stats interrupts causing slowdown was indeed due to a bug in our driver, and not some hardware bug. I have fixed the bug and committed the fix to -current; the fix will be MFC'd in a day or two, before the 4.5 codefreeze begins. In the meantime, you can grab the diff out of cvsweb if you're interested. And yes, it was pretty bad. The reason I didn't notice it too much is because stats interrupts were disabled under -current as a temporary fix; that change never got ported back to 4.x. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 14:51:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from priv-edtnes09-hme0.telusplanet.net (mtaout.telus.net [199.185.220.235]) by hub.freebsd.org (Postfix) with ESMTP id 1B65837B50B; Mon, 17 Dec 2001 14:51:06 -0800 (PST) Received: from fireball ([209.52.193.31]) by priv-edtnes09-hme0.telusplanet.net (InterMail vM.5.01.04.01 201-253-122-122-101-20011014) with SMTP id <20011217225103.FRAL28264.priv-edtnes09-hme0.telusplanet.net@fireball>; Mon, 17 Dec 2001 15:51:03 -0700 Message-ID: <001301c1874d$50ae0d20$02000003@tornado> From: "Dave Reyenga" To: , Cc: Subject: Instead of JFS, why not a whole new FS? Date: Mon, 17 Dec 2001 22:50:45 -0000 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG How about writing a new filesystem based on UFS? This would save all of the hassle that JFS would bring: licensing, porting time, etc. Of course, it would likely bust any compatibility desired. What I'm thinking is a filesystem that takes the current UFS and improves upon it. It could support larger partitions, more partitions in a slice, and perhaps a "Journal" partition (like the current "swap" partition) among other new features. What do others have to say about this? Are there any major flaws in my idea? It just seems to me that this would cut a lot of hassle. Those are just my $0.02. I know I've said it before, but I wasn't nearly as clear last time. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 15: 0:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id EE01B37B632; Mon, 17 Dec 2001 15:00:16 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011217230016.REBT10701.rwcrmhc53.attbi.com@InterJet.elischer.org>; Mon, 17 Dec 2001 23:00:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA36312; Mon, 17 Dec 2001 14:55:18 -0800 (PST) Date: Mon, 17 Dec 2001 14:55:17 -0800 (PST) From: Julian Elischer To: Dave Reyenga Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org, hiten@uk.FreeBSD.org Subject: Re: Instead of JFS, why not a whole new FS? In-Reply-To: <001301c1874d$50ae0d20$02000003@tornado> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It is possible that Kirk may be thinking about doing this. He mumbled something about a new FS a while ago but it wasn't clear whether he was thinking of doing it, or he was just saying "someone will eventually do it". On Mon, 17 Dec 2001, Dave Reyenga wrote: > How about writing a new filesystem based on UFS? This would save all of the > hassle that JFS would bring: licensing, porting time, etc. Of course, it > would likely bust any compatibility desired. > > What I'm thinking is a filesystem that takes the current UFS and improves > upon it. It could support larger partitions, more partitions in a slice, and > perhaps a "Journal" partition (like the current "swap" partition) among > other new features. > > What do others have to say about this? Are there any major flaws in my idea? > It just seems to me that this would cut a lot of hassle. > > Those are just my $0.02. I know I've said it before, but I wasn't nearly as > clear last time. > > -Craig > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 15: 5:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21107.mail.yahoo.com (web21107.mail.yahoo.com [216.136.227.109]) by hub.freebsd.org (Postfix) with SMTP id 7E74537B63C for ; Mon, 17 Dec 2001 15:04:19 -0800 (PST) Message-ID: <20011217230419.68884.qmail@web21107.mail.yahoo.com> Received: from [62.254.0.5] by web21107.mail.yahoo.com via HTTP; Mon, 17 Dec 2001 15:04:19 PST Date: Mon, 17 Dec 2001 15:04:19 -0800 (PST) From: Hiten Pandya Subject: Re: Instead of JFS, why not a whole new FS? To: dreyenga@telus.net Cc: freebsd-fs@freebsd.org, hackers@freebsd.org In-Reply-To: <001301c1874d$50ae0d20$02000003@tornado> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Dave Reyenga wrote: > How about writing a new filesystem based on UFS? > This would save all of the > hassle that JFS would bring: licensing, porting > time, etc. Of course, it > would likely bust any compatibility desired. hi, first of all, a project called UFS2 has been started by Kirk McKusick on improving the existing UFS file system and improving 'softupdates' and other stuff in this file system. > What I'm thinking is a filesystem that takes the > current UFS and improves > upon it. It could support larger partitions, more > partitions in a slice, and > perhaps a "Journal" partition (like the current > "swap" partition) among > other new features. I dont know that this could be possible of having a 'Journal' partition, though I may be wrong. > What do others have to say about this? Are there any > major flaws in my idea? > It just seems to me that this would cut a lot of > hassle. One flaw in your idea is, that it would literally take longer to make this kind of file system on our current UFS source base. The reason is due to the code maturity level that UFS has reached of around 20 years. I think porting JFS will take less time than upgrading the current UFS, which as a matter of fact has already been started by Kirk McKusick himself. Regarding 'hassle', for me; nothing is a hassle as long as it can be acheived. If you are really interested in upgrading the current UFS, it would be good if you got in touch with Kirk McKusick himself. regards, =Hiten = ===== =Hiten = __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 15:18:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21108.mail.yahoo.com (web21108.mail.yahoo.com [216.136.227.110]) by hub.freebsd.org (Postfix) with SMTP id 0990337B41F for ; Mon, 17 Dec 2001 15:18:08 -0800 (PST) Message-ID: <20011217231807.22270.qmail@web21108.mail.yahoo.com> Received: from [62.254.0.5] by web21108.mail.yahoo.com via HTTP; Mon, 17 Dec 2001 15:18:07 PST Date: Mon, 17 Dec 2001 15:18:07 -0800 (PST) From: Hiten Pandya Subject: JFS4BSD Project @ SourceForge.net To: hackers@freebsd.org Cc: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Greetings, Regarding the 'JFS for FreeBSD' discussion, I have started a project at SourceForge.net, which is for the porting of JFS. If you would like to join the JFS4BSD team in porting the JFS to the FreeBSD Operating System, please do not hesitate to either send a mail through SourceForge.net or send me an email at: hiten@uk.FreeBSD.org, and write the following in the subject: "[subscribe] jfs4bsd", which will help me sort the mail out for the subscription. Everyone is welcome! Note: You will need an account at SourceForge in order to join any project including 'jfs4bsd'. The following are the details for the project: ================================================ Project Full Name: JFS for FreeBSD (JFS4BSD) Project Unix Name: jfs4bsd CVS Server: cvs.jfs4bsd.sourceforge.net Web Site: jfs4bsd.sourceforge.net ================================================ If you are not intending to join the project, please ignore this mail. Thank You for your co-operation, Regards, Hiten Pandya __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 15:25:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 2F24437B420 for ; Mon, 17 Dec 2001 15:25:10 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 193872DDB0D; Mon, 17 Dec 2001 17:25:09 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBHNP7S55235; Mon, 17 Dec 2001 17:25:07 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 17 Dec 2001 17:25:07 -0600 (CST) Message-Id: <200112172325.fBHNP7S55235@sheol.localdomain> Mime-Version: 1.0 X-Newsreader: knews 0.9.8a Reply-To: hawkeyd@visi.com Organization: if (!FIFO) if (!LIFO) break; References: <001301c1874d$50ae0d20$02000003_tornado@ns.sol.net> In-Reply-To: <001301c1874d$50ae0d20$02000003_tornado@ns.sol.net> From: hawkeyd@visi.com (D J Hawkey Jr) Subject: Re: Instead of JFS, why not a whole new FS? X-Original-Newsgroups: sol.lists.freebsd.fs,sol.lists.freebsd.hackers To: dreyenga@telus.net, hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <001301c1874d$50ae0d20$02000003_tornado@ns.sol.net>, dreyenga@telus.net writes: > How about writing a new filesystem based on UFS? This would save all of the > hassle that JFS would bring: licensing, porting time, etc. Of course, it > would likely bust any compatibility desired. > > What I'm thinking is a filesystem that takes the current UFS and improves > upon it. It could support larger partitions, more partitions in a slice, and > perhaps a "Journal" partition (like the current "swap" partition) among > other new features. > > What do others have to say about this? Are there any major flaws in my idea? > It just seems to me that this would cut a lot of hassle. If I might: "Why?". UFS/FFS is/are proven through time. Throw in the softupdates technology, and you have the upside of journalling, without the downside of journalling. No. I'm not going into details, first because I'm not qualified, and second, others already have. Was it Matt? I don't recall now, who made the observation, [sic] "Why does the Linux camp get so excited about the support for so many filesystems? Pick one, and make it the best you can.". In a recent thread about NFS performance, one post mentioned that ReiserFS died quite early in the test. If it's that much better, why didn't it survive that much better? The one thing that journalling FSes deliver that FFS with softupdates doesn't right now is a 'fsck'less boot after an uncontrolled shutdown. I have read that the Project has this on their TODO list. I know a post like this one can start a flameware for statements made without facts to back them up, but the facts exist, have been pointed out many times, and I don't want to mis-quote or mis-appropriate them. > Those are just my $0.02. I know I've said it before, but I wasn't nearly as > clear last time. > > -Craig And this is just my two-cents' worth, as well. Dave -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 16: 8:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 69B6937B41A; Mon, 17 Dec 2001 16:08:11 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 14C4A786E3; Tue, 18 Dec 2001 10:38:09 +1030 (CST) Date: Tue, 18 Dec 2001 10:38:09 +1030 From: Greg Lehey To: Dave Reyenga Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org, hiten@uk.FreeBSD.org Subject: Re: Instead of JFS, why not a whole new FS? Message-ID: <20011218103809.V14500@monorchid.lemis.com> References: <001301c1874d$50ae0d20$02000003@tornado> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c1874d$50ae0d20$02000003@tornado> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 17 December 2001 at 22:50:45 -0000, Dave Reyenga wrote: > How about writing a new filesystem based on UFS? If it's based on UFS, it's not a new file system. > This would save all of the hassle that JFS would bring: licensing, > porting time, etc. There are no hassles with licensing. You'd be balancing porting time against writing time. Guess which would take longer. > What I'm thinking is a filesystem that takes the current UFS and > improves upon it. It could support larger partitions, That's relatively trivial. The big issue is compatibility. > more partitions in a slice, That's relatively trivial. The big issue is compatibility. > and perhaps a "Journal" partition (like the current "swap" > partition) Well, I don't think the journal would be like swap. > among other new features. That's pretty much what IBM did. They called the result JFS. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 16:21:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.his.com (herndon10.his.com [209.67.207.13]) by hub.freebsd.org (Postfix) with ESMTP id 1180F37B416; Mon, 17 Dec 2001 16:21:18 -0800 (PST) Received: from REELHN.O (max2h-227.his.com [216.32.85.227]) by mail.his.com (8.9.3/8.9.3) with SMTP id TAA12617; Mon, 17 Dec 2001 19:21:14 -0500 (EST) From: Subject: FREE CELLULAR PHONE OFFER-GUARANTEED APPROVAL Date: Mon, 17 Dec 2001 19:26:05 Message-Id: <585.488701.103845@REELHNS.O> Reply-To: freecellphone49@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG NOW YOU CAN RECEIVE A FREE CELLULAR PHONE FROM GMC AUTHORIZED DEALER FOR AT&T,WORLDCOM,SPRINT,VOICESTREAM,VERIZON AND CINGULAR. WE HAVE MANY MODELS& STYLES TO CHOOSE FROM LIKE THE NOKIA 3390,MOTOROLA STARTEC AND THE NOKIA 8260.WE GUARANTEE YOUR APPROVAL REGARDLESS OF YOUR PAST CREDIT HISTORY. ALL PHONES COMES WITH CALLER ID, VOICEMAIL,CALL WAITING AND EMAIL TEXT MESSAGING. SOME PHONES EVEN HAVE A WEB BROWSER TO SURF THE INTERNET.THE PHONES ARE 100% FREE WITH ACTIVATION. THE RATE PLANS START AT $19.99 PER MONTH,SOME PLANS HAVE UNLIMITED NIGHTS AND WEEKENDS WITH FREE LONG DISTANCE. THIS IS A LIMITED OFFER! YOU CAN HAVE YOUR PHONE DELIVERED IN 48 HOURS. FOR MORE INFORMATION OR TO ORDER YOUR PHONE CALL 1-866-206-0820 THATS 1-866-206-0820. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 17: 0:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 7F34637B41D for ; Mon, 17 Dec 2001 17:00:45 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id A859315E; Tue, 18 Dec 2001 01:00:36 +0000 (GMT) Date: Tue, 18 Dec 2001 01:00:36 +0000 From: Josef Karthauser To: D J Hawkey Jr Cc: dreyenga@telus.net, hackers@freebsd.org Subject: Re: Instead of JFS, why not a whole new FS? Message-ID: <20011218010036.B1618@tao.org.uk> References: <001301c1874d$50ae0d20$02000003_tornado@ns.sol.net> <200112172325.fBHNP7S55235@sheol.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112172325.fBHNP7S55235@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 17, 2001 at 05:25:07PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Dec 17, 2001 at 05:25:07PM -0600, D J Hawkey Jr wrote: > The one thing that journalling FSes deliver that FFS with softupdates doesn't > right now is a 'fsck'less boot after an uncontrolled shutdown. I have read > that the Project has this on their TODO list. This has been the default in -current for a few months now. It requires snapshots, which hasn't been MFC'd yet. Joe --hHWLQfXTYDoKhP50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwelTQACgkQXVIcjOaxUBaQdgCeMtqGUJzqVCzreB0qLkg1ce8L 3vMAn1VZYYeREv1asV64U7MDd2VYYDCZ =NRgD -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 18:29:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 985C037B41A; Mon, 17 Dec 2001 18:29:47 -0800 (PST) Received: from pool0289.cvx40-bradley.dialup.earthlink.net ([216.244.43.34] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16GA0n-0002CE-00; Mon, 17 Dec 2001 18:29:46 -0800 Message-ID: <3C1EAA1A.CA49932@mindspring.com> Date: Mon, 17 Dec 2001 18:29:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Reyenga Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org, hiten@uk.FreeBSD.org Subject: Re: Instead of JFS, why not a whole new FS? References: <001301c1874d$50ae0d20$02000003@tornado> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dave Reyenga wrote: > > How about writing a new filesystem based on UFS? This would save all of the > hassle that JFS would bring: licensing, porting time, etc. Of course, it > would likely bust any compatibility desired. > > What I'm thinking is a filesystem that takes the current UFS and improves > upon it. It could support larger partitions, more partitions in a slice, and > perhaps a "Journal" partition (like the current "swap" partition) among > other new features. > > What do others have to say about this? Are there any major flaws in my idea? > It just seems to me that this would cut a lot of hassle. Any FS that shares code with an existing FS will not flush out the full list of problems associated with writing a new FS in the context of a FreeBSD system. For that reason, any UFS based system, including but not limited to FFS, LFS, EXT2FS, etc., is probably not a good example to use for an educational project. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 20:25:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B1F037B41D; Mon, 17 Dec 2001 20:25:26 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBI4O4Z47987; Mon, 17 Dec 2001 20:24:04 -0800 (PST) (envelope-from dillon) Date: Mon, 17 Dec 2001 20:24:04 -0800 (PST) From: Matthew Dillon Message-Id: <200112180424.fBI4O4Z47987@apollo.backplane.com> To: Conrad Minshall Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :... :> with out-of-order operations from nfsiod's that apparently may come :> up after a week or so of testing. I asked Jordan to try to track down :> the NeXT guy who fixed that one in the old NFS stack. : :This bug showed up recently here with fsx testing. I seem to have fixed it :last week in MacOS X. The diffs were widespread but the idea was simple :enough so a few code snippets should suffice: : :nfs_request gets a new argument (u_int64_t *xidp) and fills it in here: : :... Ok, I understand. That will probably be a little too complex to make the 4.5 release, but I'll do it post-4.5. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 17 21: 5:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id AD6F437B41D for ; Mon, 17 Dec 2001 21:05:41 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id D991B62D01 for ; Mon, 17 Dec 2001 21:05:40 -0800 (PST) Date: Mon, 17 Dec 2001 21:06:16 -0800 (PST) From: Lamont Granquist To: Subject: Re: What a FBSD FS needs to do? In-Reply-To: <3C1E02A1.98BFFE5@mindspring.com> Message-ID: <20011217205835.S4651-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 17 Dec 2001, Terry Lambert wrote: [...snippage all over...] wow! thanks! that was much more than i'd hoped for! unfortunately i'm very much a beginner to kernel hacking, so don't expect any ported filesystems out of me in the near future... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 0:55:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F2CB637B405 for ; Tue, 18 Dec 2001 00:55:19 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBI8tIb68150; Tue, 18 Dec 2001 00:55:18 -0800 (PST) (envelope-from dillon) Date: Tue, 18 Dec 2001 00:55:18 -0800 (PST) From: Matthew Dillon Message-Id: <200112180855.fBI8tIb68150@apollo.backplane.com> To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A quick VM question References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :What are the backing objects of the stack and heap area of a process's :address space? When are they created? I saw the code vm_map_insert(), but :the object argument given is NULL. : :Thanks, : :-Zhihui The backing objects are OBJT_DEFAULT objects. They are typically created when the system first needs to retrieve the map entry's object or needs to clip the map entry (for example, when extending the stack or [s]brk()ing), so as to reduce the number of actual VM objects created and to share the same VM object (with different offsets) whenever possible. If you look in vm/vm_map.c that is what all those NULL tests and calls to vm_object_allocate(OBJT_DEFAULT, ...) do. An OBJT_DEFAULT object is effectively a swap-backed object, just one that does not yet have any swap associated with it. If/When the system decides it needs to swap it will convert OBJT_DEFAULT objects for the memory in question to OBJT_SWAP objects. The two are really almost the same type of VM object. The type distinction is simply used to optimize performance. The main VM object types are: OBJT_PHYS physically-backed, never swapped out. OBJT_DEFAULT swap-backed with no swap yet assigned OBJT_SWAP swap-backed OBJT_VNODE vnode (e.g. file) backed object -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 1:46:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id D4D8037B41C for ; Tue, 18 Dec 2001 01:46:29 -0800 (PST) Received: from swordfish.energyhq.org (swordfish.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 019B123F92; Fri, 14 Dec 2001 18:27:13 +0100 (CET) Date: Fri, 14 Dec 2001 18:26:03 +0100 From: Miguel Mendez To: "Rafter Man" Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... Message-Id: <20011214182603.4ceb67dc.flynn@energyhq.homeip.net> In-Reply-To: <20011214150349.3305.qmail@linuxmail.org> References: <20011214150349.3305.qmail@linuxmail.org> Organization: Energy, Inc X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Dec 2001 23:03:49 +0800 "Rafter Man" wrote: > 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++. As the BeOS developers used to say: NO C++ in the kernel. Follow that simple rule and you'll be safe :-) -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 2: 1:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swordfish.energyhq.org (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 5F2B137B419 for ; Tue, 18 Dec 2001 02:01:30 -0800 (PST) Received: from there (localhost [127.0.0.1]) by swordfish.energyhq.org (8.11.6/8.11.6) with SMTP id fBI9vYn38445 for ; Tue, 18 Dec 2001 10:57:35 +0100 (CET) (envelope-from flynn@energyhq.homeip.net) Message-Id: <200112180957.fBI9vYn38445@swordfish.energyhq.org> Content-Type: text/plain; charset="iso-8859-1" From: Miguel Mendez Organization: Energy HQ To: freebsd-hackers@FreeBSD.org Subject: Enhancing the CS461x audio driver... Date: Tue, 18 Dec 2001 10:57:34 +0100 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there hackers, I have a Terratec card based on the CS461x chip that comes with an S/PDIF optical output which I'd like to use. This feature is available under Windows but not under FreeBSD. I've downloaded some docs from the Crystal Semiconductor site but need some help as of where to start from. My idea is to add an ioctcl call to enable/disable the digital output, but I have no previous experience with driver hacking. Is this feature already in the TODO list of the driver already or has someone else started working on this? Yours, -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 2:55:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 5366737B41D for ; Tue, 18 Dec 2001 02:55:37 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 991084BE; Tue, 18 Dec 2001 10:55:27 +0000 (GMT) Date: Tue, 18 Dec 2001 10:55:27 +0000 From: Josef Karthauser To: Matthew Dillon Cc: Martin Blapp , freebsd-hackers@FreeBSD.ORG Subject: Re: deadlock with softupdates ? Message-ID: <20011218105527.A708@tao.org.uk> Mail-Followup-To: Josef Karthauser , Matthew Dillon , Martin Blapp , freebsd-hackers@FreeBSD.ORG References: <20011217223123.P59342-100000@levais.imp.ch> <200112172141.fBHLfSc33112@apollo.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="DKU6Jbt7q3WqK7+M" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112172141.fBHLfSc33112@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Dec 17, 2001 at 01:41:28PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --DKU6Jbt7q3WqK7+M Content-Type: multipart/mixed; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 17, 2001 at 01:41:28PM -0800, Matthew Dillon wrote: > If it is a vnode deadlock you have to find which process or > processes it is deadlocking against. >=20 > Do a ps -axl -M vmcore.X -N kernel.X on the kernel core, > pick out all the processes blocked on inode or whatever, > then from gdb go to each process (proc N) and do a backtrace > (back). I've a similar problem with -current from recent (within the last week or two). genius# ps -axl -M vmcore.15 -N kernel.15=20 (attached file) The back traces for the processes locked in inode is also attached. Being green to debugging this kind of thing what should I do next? Joe --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=ps UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 274 1 0 8 0 840 0 wait D+ #C:- 0:00.01 (sh) 88 317 274 0 96 0 26064 0 select D+ #C:- 0:00.37 (mysqld) 0 328 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 329 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 330 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 331 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 332 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 334 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 333 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 0 335 1 0 5 0 1080 0 ttyin Ds+ #C: 0:00.00 (getty) 100 4345 4344 0 96 0 22772 0 select Ds+ #C: 0:05.88 (slrn) 100 1618 1617 0 -12 0 3452 0 inode Ds+ #C: 0:01.90 (mutt) 0 0 0 0 -16 0 0 0 sched DLs ?? 0:00.11 (swapper) 0 1 0 0 8 0 664 0 wait DLs ?? 0:00.01 (init) 0 2 0 0 -16 0 0 0 psleep DL ?? 0:00.04 (pagedaemon 0 3 0 0 20 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 20 0 0 0 pgzero DL ?? 0:00.00 (pagezero) 0 5 0 0 -16 0 0 0 psleep DL ?? 0:00.18 (bufdaemon) 0 6 0 0 20 0 0 0 syncer DL ?? 0:06.43 (syncer) 0 10 0 16 -16 0 0 0 - RL ?? 659:48.43 (idle) 0 11 0 0 -44 0 0 0 - WL ?? 0:01.34 (swi1: net) 0 12 0 0 -48 0 0 0 - WL ?? 37:12.86 (swi6: tty: 0 13 0 0 -32 0 0 0 - WL ?? 0:00.00 (swi4: vm) 0 14 0 0 76 0 0 0 sleep DL ?? 0:01.55 (random) 0 15 0 0 0 0 0 0 - WL ?? 0:09.37 (swi5: task 0 16 0 0 -40 0 0 0 - WL ?? 0:00.00 (swi2: camn 0 17 0 0 -36 0 0 0 - WL ?? 0:00.00 (swi3: camb 0 18 0 0 -21 0 0 0 - WL ?? 0:00.00 (irq13:) 0 19 0 0 -21 0 0 0 - WL ?? 0:03.93 (irq9:) 0 20 0 0 -80 0 0 0 - WL ?? 0:00.00 (irq11: pci 0 21 0 0 -64 0 0 0 - WL ?? 0:19.25 (irq14: ata 0 22 0 0 -64 0 0 0 - WL ?? 0:00.00 (irq15: ata 0 23 0 0 -64 0 0 0 - WL ?? 0:01.20 (irq5: uhci 0 24 0 0 -60 0 0 0 - RL ?? 0:00.23 (irq1: atkb 0 25 0 0 -60 0 0 0 - WL ?? 0:00.05 (irq12: psm 0 26 0 0 -64 0 0 0 - WL ?? 0:00.00 (irq6: fdc0 0 27 0 0 -48 0 0 0 - WL ?? 0:00.00 (swi0: tty: 0 28 0 0 -60 0 0 0 - WL ?? 0:00.00 (irq4: sio0 0 29 0 0 -60 0 0 0 - WL ?? 0:00.00 (irq7: ppc0 0 30 0 0 -84 0 0 0 - WL ?? 0:00.00 (irq0: clk) 0 31 0 0 -84 0 0 0 - WL ?? 0:00.00 (irq8: rtc) 0 150 1 0 -12 0 1084 0 inode Ds ?? 0:00.36 (syslogd) 0 156 1 0 -12 0 1432 0 inode Ds ?? 0:00.81 (ntpd) 0 162 1 0 96 0 1208 0 select Ds ?? 0:00.02 (inetd) 0 164 1 0 -12 0 1124 0 inode Ds ?? 0:00.07 (cron) 0 167 1 0 96 0 1092 0 select Ds ?? 0:00.01 (lpd) 0 169 1 0 96 0 2380 0 select Ds ?? 0:00.05 (sshd) 0 171 0 0 8 0 0 0 usbevt DL ?? 0:00.37 (usb0) 0 172 1 0 96 0 1040 0 select Ds ?? 0:00.06 (usbd) 0 229 1 0 96 0 1036 0 select Ds ?? 0:15.30 (moused) 0 259 1 0 96 0 2236 0 select Ds ?? 0:00.94 (httpd) 65534 265 259 0 4 0 2260 0 accept D ?? 0:00.00 (httpd) 65534 266 259 0 4 0 2260 0 accept D ?? 0:00.00 (httpd) 65534 267 259 0 4 0 2260 0 accept D ?? 0:00.00 (httpd) 65534 268 259 0 4 0 2260 0 accept D ?? 0:00.00 (httpd) 65534 269 259 0 4 0 2260 0 accept D ?? 0:00.00 (httpd) 1001 271 1 0 96 0 3248 0 select Ds ?? 0:00.01 (cvsupd) 0 336 1 0 20 0 2892 0 pause D ?? 0:00.07 (xdm) 0 342 336 0 96 0 33168 0 select Ds ?? 1:59.86 (XFree86) 0 343 336 0 8 0 3096 0 wait Ds ?? 0:00.04 (xdm) 0 376 1 0 -12 0 1136 0 inode Ds ?? 0:00.38 (master) 1003 378 376 0 -12 0 1256 0 inode D ?? 0:03.75 (qmgr) 0 389 1 0 96 0 3024 0 select D ?? 0:00.03 (xconsole) 100 427 343 0 8 0 820 0 wait Ds ?? 0:00.01 (sh) 100 431 427 0 -12 0 4320 0 inode D ?? 0:04.76 (wmaker) 100 432 431 0 96 0 1844 0 select Ds ?? 0:00.34 (ssh-agent) 100 438 431 0 96 0 9124 0 select D ?? 0:01.44 (gimp) 100 439 431 0 8 0 2640 0 nanslp D ?? 0:47.38 (wmCalClock 100 440 431 0 -12 0 2092 0 inode D ?? 0:51.70 (wmtop) 100 441 431 0 -12 0 2104 0 inode D ?? 0:35.55 (wmapm) 100 442 431 0 -12 0 2140 0 inode D ?? 0:02.89 (wmbiff) 100 458 438 0 96 0 5740 0 select D ?? 0:00.41 (script-fu) 0 484 1 0 8 0 712 0 wait Ds ?? 0:00.01 (dhclient) 100 1616 442 0 8 0 824 0 wait D ?? 0:00.00 (sh) 100 1617 1616 0 96 0 2476 0 select D ?? 0:01.59 (rxvt) 100 4344 431 0 96 0 2372 0 select D ?? 0:00.24 (rxvt) 1003 4863 376 0 -12 0 1176 0 inode D ?? 0:00.01 (cleanup) 1003 4887 376 0 96 0 1584 0 select D ?? 0:00.03 (trivial-re 1003 4911 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 4944 376 0 96 0 0 0 - Z ?? 0:00.00 (pickup) 1003 4956 376 0 96 0 0 0 - Z ?? 0:00.00 (local) 1003 4960 376 0 96 0 0 0 - Z ?? 0:00.00 (local) 100 4961 1 0 -12 0 1412 0 inode Ds ?? 0:00.97 (procmail) 1003 5015 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5016 376 0 -12 0 1160 0 inode D ?? 0:00.01 (cleanup) 1003 5017 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5018 376 1 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5019 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5020 376 0 -12 0 1160 0 inode D ?? 0:00.01 (cleanup) 1003 5021 376 0 -12 0 1160 0 inode D ?? 0:00.01 (cleanup) 1003 5022 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5023 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5024 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5025 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5026 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5027 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5028 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5032 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5033 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5034 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5035 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5036 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5037 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5038 376 0 96 0 0 0 - Z ?? 0:00.00 (smtpd) 1003 5039 376 0 -18 0 1160 0 vfscac D ?? 0:00.01 (cleanup) 1003 5040 376 0 -12 0 1160 0 inode D ?? 0:00.01 (cleanup) 1003 5041 376 0 -12 0 1160 0 inode D ?? 0:00.01 (cleanup) 0 5042 164 0 -8 0 1140 0 piperd D ?? 0:00.00 (cron) 2 5044 5042 0 8 0 824 0 wait Ds ?? 0:00.00 (sh) 2 5046 5044 0 -18 0 864 0 vfscac D ?? 0:00.01 (sh) 0 5050 164 0 -8 0 1140 0 piperd D ?? 0:00.00 (cron) 0 5051 5050 0 8 0 824 0 wait Ds ?? 0:00.00 (sh) 0 5052 5051 0 -18 0 824 0 vfscac D ?? 0:00.00 (sh) 0 5053 484 0 -12 0 712 0 inode D ?? 0:00.00 (dhclient) --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=typescript Content-Transfer-Encoding: quoted-printable Script started on Tue Dec 18 10:51:21 2001 genius# kldload /boot/kernel/if_aue.ko=1B[30Dexit=1B[K=1B[8Cpwd=1B[K=1B[8Cr= oupwqd=1B[7Dexec zsh=1B[8Dls -ltr=1B[K=1B[7Dexec zsh=1B[8Droupwqd=1B[K=1B[7= Dpwd=1B[K=1B[8Cexit=1B[8Ckldload /boot/kernel/if_aue.ko=1B[30D=1B[K=07gdb -= k /usr/obj/usr/src/sys/GENIUS/kernel.debug vmcore.15 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at phsyical address 0x00493000 initial pcb at physical address 0x00357120 panicstr: bwrite: buffer is not busy??? panic messages: --- panic: from debugger syncing disks... panic: bwrite: buffer is not busy??? Uptime: 11h46m15s pfs_vncache_unload(): 156 entries remaining /dev/vmmon: Module vmmon: unloaded dumping to dev ad0s2b, offset 128 dump ata0: resetting devices .. done 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493= 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 47= 4 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 4= 55 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 = 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418= 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 39= 9 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 3= 80 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 = 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343= 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 32= 4 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 3= 05 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 = 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268= 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 24= 9 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 2= 30 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 = 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193= 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 17= 4 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 1= 55 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 = 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118= 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99= 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74= 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49= 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24= 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0=20 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:492 492 if (!dodump) (kgdb) proc 1618 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe2f27e1c, mtx=3D0xc0356970, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe2f27e1c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe2f27e1c, flags=3D16973826,=20 interlkp=3D0xe2f27dec, td=3D0xe4564d04) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe461cb74) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe461cb74) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe2f27d80, flags=3D131074, td=3D0xe4564d04) at vnode_if.h:693 #7 0xc020e7ac in lookup (ndp=3D0xe461cc44) at /usr/src/sys/kern/vfs_lookup= .c:315 #8 0xc020e4a4 in namei (ndp=3D0xe461cc44) at /usr/src/sys/kern/vfs_lookup.= c:168 #9 0xc0215d55 in stat (td=3D0xe4564d04, uap=3D0xe461cd20) at /usr/src/sys/kern/vfs_syscalls.c:1976 #10 0xc02b1c88 in syscall (frame=3D{tf_fs =3D 47, tf_es =3D 674365487,=20 tf_ds =3D -1078001617, tf_edi =3D 0, tf_esi =3D 9, tf_ebp =3D -107794= 0696,=20 tf_isp =3D -463352460, tf_ebx =3D 0, tf_edx =3D 134984064,=20 tf_ecx =3D 1008661449, tf_eax =3D 188, tf_trapno =3D 0, tf_err =3D 2,= =20 tf_eip =3D 673929315, tf_cs =3D 31, tf_eflags =3D 647, tf_esp =3D -10= 77941188,=20 tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap.c:1150 #11 0xc02a52ed in syscall_with_err_pushed () #12 0x80599d0 in ?? () #13 0x806b735 in ?? () #14 0x804b699 in ?? () (kgdb) proc 150 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe2f27e1c, mtx=3D0xc0356970, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe2f27e1c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe2f27e1c, flags=3D16973826,=20 interlkp=3D0xe2f27dec, td=3D0xe07fa404) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe42cca54) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe42cca54) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe2f27d80, flags=3D131074, td=3D0xe07fa404) at vnode_if.h:693 #7 0xc020e7ac in lookup (ndp=3D0xe42ccc2c) at /usr/src/sys/kern/vfs_lookup= .c:315 #8 0xc020e4a4 in namei (ndp=3D0xe42ccc2c) at /usr/src/sys/kern/vfs_lookup.= c:168 #9 0xc02193d8 in vn_open_cred (ndp=3D0xe42ccc2c, flagp=3D0xe42ccbf8, cmode= =3D420,=20 cred=3D0xc6933600) at /usr/src/sys/kern/vfs_vnops.c:162 #10 0xc021919e in vn_open (ndp=3D0xe42ccc2c, flagp=3D0xe42ccbf8, cmode=3D42= 0) at /usr/src/sys/kern/vfs_vnops.c:85 #11 0xc02147ca in open (td=3D0xe07fa404, uap=3D0xe42ccd20) at /usr/src/sys/kern/vfs_syscalls.c:1115 #12 0xc02b1c88 in syscall (frame=3D{tf_fs =3D 134545455, tf_es =3D 47,=20 tf_ds =3D -1078001617, tf_edi =3D 4, tf_esi =3D 672274624,=20 tf_ebp =3D -1077942300, tf_isp =3D -466825868, tf_ebx =3D 672197864,= =20 tf_edx =3D 672274624, tf_ecx =3D 16, tf_eax =3D 5, tf_trapno =3D 0, t= f_err =3D 2,=20 tf_eip =3D 671798595, tf_cs =3D 31, tf_eflags =3D 659, tf_esp =3D -10= 77942344,=20 tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap.c:1150 #13 0xc02a52ed in syscall_with_err_pushed () #14 0x804b3cd in ?? () #15 0x804b36a in ?? () #16 0x804ac39 in ?? () #17 0x804a59c in ?? () #18 0x804a36a in ?? () #19 0x8049709 in ?? () (kgdb) proc 156 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe2f27e1c, mtx=3D0xc0356970, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe2f27e1c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe2f27e1c, flags=3D16973826,=20 interlkp=3D0xe2f27dec, td=3D0xe07f9b04) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe42e8a54) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe42e8a54) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe2f27d80, flags=3D131074, td=3D0xe07f9b04) at vnode_if.h:693 #7 0xc020e7ac in lookup (ndp=3D0xe42e8c2c) at /usr/src/sys/kern/vfs_lookup= .c:315 #8 0xc020e4a4 in namei (ndp=3D0xe42e8c2c) at /usr/src/sys/kern/vfs_lookup.= c:168 #9 0xc0219202 in vn_open_cred (ndp=3D0xe42e8c2c, flagp=3D0xe42e8bf8, cmode= =3D420,=20 cred=3D0xc6939d00) at /usr/src/sys/kern/vfs_vnops.c:116 #10 0xc021919e in vn_open (ndp=3D0xe42e8c2c, flagp=3D0xe42e8bf8, cmode=3D42= 0) at /usr/src/sys/kern/vfs_vnops.c:85 #11 0xc02147ca in open (td=3D0xe07f9b04, uap=3D0xe42e8d20) at /usr/src/sys/kern/vfs_syscalls.c:1115 #12 0xc02b1c88 in syscall (frame=3D{tf_fs =3D -1078001617, tf_es =3D 134742= 063,=20 tf_ds =3D -1078001617, tf_edi =3D 8, tf_esi =3D 672569536,=20 tf_ebp =3D -1077937204, tf_isp =3D -466711180, tf_ebx =3D 672492776,= =20 tf_edx =3D 672569536, tf_ecx =3D 16, tf_eax =3D 5, tf_trapno =3D 22, = tf_err =3D 2,=20 tf_eip =3D 672093507, tf_cs =3D 31, tf_eflags =3D 659, tf_esp =3D -10= 77937248,=20 tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap.c:1150 #13 0xc02a52ed in syscall_with_err_pushed () #14 0x805ed48 in ?? () #15 0x805eaa0 in ?? () #16 0x805fa53 in ?? () #17 0x805f61a in ?? () #18 0x8049ba9 in ?? () (kgdb) proc 164 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe2f2741c, mtx=3D0xc0356c40, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe2f2741c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe2f2741c, flags=3D16842754,=20 interlkp=3D0xe2f273ec, td=3D0xe07f9804) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe4319b08) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe4319b08) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe2f27380, flags=3D65538, td=3D0xe07f9804) at vnode_if.h:693 #7 0xc0210ec9 in vget (vp=3D0xe2f27380, flags=3D2, td=3D0xe07f9804) at /usr/src/sys/kern/vfs_subr.c:1572 #8 0xc020b107 in vfs_cache_lookup (ap=3D0xe4319bc4) at /usr/src/sys/kern/vfs_cache.c:651 #9 0xc027c729 in ufs_vnoperate (ap=3D0xe4319bc4) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #10 0xc020e9b9 in lookup (ndp=3D0xe4319c44) at vnode_if.h:45 #11 0xc020e4a4 in namei (ndp=3D0xe4319c44) at /usr/src/sys/kern/vfs_lookup.= c:168 #12 0xc0215d55 in stat (td=3D0xe07f9804, uap=3D0xe4319d20) at /usr/src/sys/kern/vfs_syscalls.c:1976 #13 0xc02b1c88 in syscall (frame=3D{tf_fs =3D 47, tf_es =3D 47, tf_ds =3D 4= 7,=20 tf_edi =3D -1077936680, tf_esi =3D 1, tf_ebp =3D -1077936852,=20 tf_isp =3D -466510476, tf_ebx =3D -1077936784, tf_edx =3D -1077936892= ,=20 tf_ecx =3D 5, tf_eax =3D 188, tf_trapno =3D 12, tf_err =3D 2,=20 tf_eip =3D 671832163, tf_cs =3D 31, tf_eflags =3D 647, tf_esp =3D -10= 77937616,=20 tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap.c:1150 #14 0xc02a52ed in syscall_with_err_pushed () #15 0x8049bd9 in ?? () #16 0x804994d in ?? () (kgdb) proc 376 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe430a45c, mtx=3D0xc0356220, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe430a45c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe430a45c, flags=3D16973826,=20 interlkp=3D0xe430a42c, td=3D0xe07f8604) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe4346a54) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe4346a54) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe430a3c0, flags=3D131074, td=3D0xe07f8604) at vnode_if.h:693 #7 0xc020e7ac in lookup (ndp=3D0xe4346c2c) at /usr/src/sys/kern/vfs_lookup= .c:315 #8 0xc020e4a4 in namei (ndp=3D0xe4346c2c) at /usr/src/sys/kern/vfs_lookup.= c:168 #9 0xc02193d8 in vn_open_cred (ndp=3D0xe4346c2c, flagp=3D0xe4346bf8, cmode= =3D0,=20 cred=3D0xc7141600) at /usr/src/sys/kern/vfs_vnops.c:162 #10 0xc021919e in vn_open (ndp=3D0xe4346c2c, flagp=3D0xe4346bf8, cmode=3D0) at /usr/src/sys/kern/vfs_vnops.c:85 #11 0xc02147ca in open (td=3D0xe07f8604, uap=3D0xe4346d20) at /usr/src/sys/kern/vfs_syscalls.c:1115 #12 0xc02b1c88 in syscall (frame=3D{tf_fs =3D -1078001617, tf_es =3D 47,=20 tf_ds =3D -1078001617, tf_edi =3D 1, tf_esi =3D 134611560,=20 tf_ebp =3D -1077937640, tf_isp =3D -466326156, tf_ebx =3D 134608392,= =20 tf_edx =3D 134584716, tf_ecx =3D 134614644, tf_eax =3D 5, tf_trapno = =3D 12,=20 tf_err =3D 2, tf_eip =3D 671835459, tf_cs =3D 31, tf_eflags =3D 647,= =20 tf_esp =3D -1077937684, tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap= .c:1150 #13 0xc02a52ed in syscall_with_err_pushed () #14 0x804b7ee in ?? () #15 0x804e578 in ?? () #16 0x8049bfb in ?? () #17 0x8049705 in ?? () (kgdb) proc 378 (kgdb) bt #0 0xc01db56d in mi_switch () at /usr/src/sys/kern/kern_synch.c:781 #1 0xc01dad33 in msleep (ident=3D0xe430a45c, mtx=3D0xc0356220, priority=3D= 72,=20 wmesg=3D0xc02f599d "inode", timo=3D0) at /usr/src/sys/kern/kern_synch.c= :496 #2 0xc01cb0b5 in acquire (lkp=3D0xe430a45c, extflags=3D16777280, wanted=3D= 1536) at /usr/src/sys/kern/kern_lock.c:168 #3 0xc01cb460 in lockmgr (lkp=3D0xe430a45c, flags=3D16973826,=20 interlkp=3D0xe430a42c, td=3D0xe4398404) at /usr/src/sys/kern/kern_lock.= c:374 #4 0xc020d161 in vop_stdlock (ap=3D0xe4415b54) at /usr/src/sys/kern/vfs_default.c:252 #5 0xc027c729 in ufs_vnoperate (ap=3D0xe4415b54) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2658 #6 0xc021a002 in vn_lock (vp=3D0xe430a3c0, flags=3D131074, td=3D0xe4398404) at vnode_if.h:693 #7 0xc020e7ac in lookup (ndp=3D0xe4415ca4) at /usr/src/sys/kern/vfs_lookup= .c:315 #8 0xc020e4a4 in namei (ndp=3D0xe4415ca4) at /usr/src/sys/kern/vfs_lookup.= c:168 #9 0xc0217119 in rename (td=3D0xe4398404, uap=3D0xe4415d20) at /usr/src/sys/kern/vfs_syscalls.c:2921 #10 0xc02b1c88 in syscall (frame=3D{tf_fs =3D 134610991, tf_es =3D -1078001= 617,=20 tf_ds =3D -465502161, tf_edi =3D 134647048, tf_esi =3D 134647176,=20 tf_ebp =3D -1077938220, tf_isp =3D -465478284, tf_ebx =3D 134701088,= =20 tf_edx =3D 134647068, tf_ecx =3D -10, tf_eax =3D 128, tf_trapno =3D 0= ,=20 tf_err =3D 2, tf_eip =3D 671865731, tf_cs =3D 31, tf_eflags =3D 659,= =20 tf_esp =3D -1077938360, tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap= .c:1150 #11 0xc02a52ed in syscall_with_err_pushed () #12 0x804f014 in ?? () #13 0x8049f24 in ?? () #14 0x8049b09 in ?? () #15 0x804d478 in ?? () #16 0x8049cae in ?? () #17 0x8049889 in ?? () (kgdb) q genius# ^D=08=08exit Script done on Tue Dec 18 10:52:51 2001 --Nq2Wo0NMKNjxTN9z-- --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwfIJ8ACgkQXVIcjOaxUBZVdACg5GxyTvJ6XD8jbIL5oDwULJJX CYYAnAnOzTsr9FAX0L3dSag3707L6fhU =7P2B -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 4: 0:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 435E137B41E for ; Tue, 18 Dec 2001 04:00:43 -0800 (PST) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 16GIvD-000FIu-0W; Tue, 18 Dec 2001 12:00:42 +0000 Received: from haveblue (haveblue.rings [10.2.4.64]) by vilnya.demon.co.uk (Postfix) with SMTP id 92B4F2E850; Tue, 18 Dec 2001 11:59:49 +0000 (GMT) Message-ID: <009501c187bb$81781810$4004020a@haveblue> From: "cameron grant" To: "Miguel Mendez" , References: <200112180957.fBI9vYn38445@swordfish.energyhq.org> Subject: Re: Enhancing the CS461x audio driver... Date: Tue, 18 Dec 2001 11:59:13 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I have a Terratec card based on the CS461x chip that comes with an S/PDIF > optical output which I'd like to use. This feature is available under Windows > but not under FreeBSD. I've downloaded some docs from the Crystal > Semiconductor site but need some help as of where to start from. My idea is > to add an ioctcl call to enable/disable the digital output, but I have no > previous experience with driver hacking. Is this feature already in the TODO > list of the driver already or has someone else started working on this? if you have docs that actually specify how to control the spdif output, send them to me and i'll include it in a future driver version. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 4: 5:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [62.49.202.23]) by hub.freebsd.org (Postfix) with ESMTP id 762F937B41B for ; Tue, 18 Dec 2001 04:05:45 -0800 (PST) Received: from mike by lindt.urgle.com with local (Exim 3.33 #1) id 16GIzz-000POw-00; Tue, 18 Dec 2001 12:05:31 +0000 Date: Tue, 18 Dec 2001 12:05:31 +0000 From: Mike Bristow To: "Brandon D. Valentine" Cc: hackers@FreeBSD.ORG Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Message-ID: <20011218120531.A97576@lindt.urgle.com> References: <200112130608.fBD689K49906@apollo.backplane.com> <20011213043851.Y56723-100000@turtle.looksharp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011213043851.Y56723-100000@turtle.looksharp.net>; from bandix@looksharp.net on Thu, Dec 13, 2001 at 04:39:58AM -0500 X-Rated: SEAL Team 6, Ft. Bragg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 04:39:58AM -0500, Brandon D. Valentine wrote: > On Wed, 12 Dec 2001, Matthew Dillon wrote: > > > All I can say is... holy shit! > > Dude, you kick ass. At work I've been dealing with Linux's crappy NFS > implementation for years, while FreeBSD has always been pretty damn good > by comparison. Linux finally got a decent amount of performance under > 2.4 (which finally does NFSv3 to hosts other than other Linux boxen), > but it still can't touch the FreeBSD NFS implementation. The more > robust you make it the easier it is for me to argue for deployment of > more FreeBSD systems in NFS server roles. The only advantage Linux has > got right now is XFS, which is admittedly a pretty large advantage on > multi terabyte filesystems where fsck is impossible. I'm guessing that the real requirment here is is "when the system is turned on after an unclean shutdown (eg, power failure), it should be able to export it's NFS filesystems quickly". I suspect that the background fsck[1] that's available in FreeBSD-current fits the bill just as well as JFS or XFS - and I'll also bet that it'll be available in a FreeBSD-release before I'd trust data to a port of JFS or XFS. [1] If you've missed it, the basic idea is: for $fs in $all_filesystems ; do if is_a_softupdate_filesystem($fs) ; then fsck $fs & else fsck $fs fi done except it happens in fsck itself, rather than a shell script. -- Mike Bristow, embonpointful, but not managerial, damnit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 4:34:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls18.ne.ipsvc.net (chmls18.ne.ipsvc.net [24.147.1.153]) by hub.freebsd.org (Postfix) with ESMTP id F28EE37B41A for ; Tue, 18 Dec 2001 04:34:31 -0800 (PST) Received: from gandalf (h00045ae37142.ne.mediaone.net [65.96.123.237]) by chmls18.ne.ipsvc.net (8.11.6/8.11.6) with SMTP id fBICYTG19624 for ; Tue, 18 Dec 2001 07:34:29 -0500 (EST) Message-ID: <00ab01c187c0$53ac5cc0$6401a8c0@gandalf> From: "Dragon Fire" To: Subject: Re: deadlock with softupdates ? Date: Tue, 18 Dec 2001 07:34:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We saw something very similar to this about a year using FFS and soft updates when we were building a NAS appliance. The details escape me and I no longer work the company so I cannot grep the source code but here's what I remember. The softupdate code periodically flushes the meta data. There is a flag in the soft update code that periodically sets a flag to starts the meta data flush timer. There was a condition in which this flag was not set properly causing FFS to freeze, in particular with NFS running. Hope this helps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 5:18:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aragorn.ics.muni.cz (aragorn.ics.muni.cz [147.251.4.33]) by hub.freebsd.org (Postfix) with ESMTP id 947F237B41C; Tue, 18 Dec 2001 05:18:08 -0800 (PST) Received: from dior.ics.muni.cz (dior.ics.muni.cz [147.251.6.10]) by aragorn.ics.muni.cz (8.8.5/8.8.5) with ESMTP id OAA21064; Tue, 18 Dec 2001 14:18:07 +0100 (MET) Received: from kloboucek (root@localhost) (authenticated as hopet with LOGIN) by dior.ics.muni.cz (8.10.1/8.10.0.Beta12) with ESMTP id fBIDI6o23995; Tue, 18 Dec 2001 14:18:06 +0100 (MET) From: "Petr Holub" To: , , , Subject: tx driver Date: Tue, 18 Dec 2001 14:17:09 +0100 Message-ID: <003c01c187c6$4c323e00$d2e86cc2@kloboucek> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all! I've encountered really awful behavior of my SMC card using tx driver in FreeBSD 4.3. On 100 Mbps network I get the throughput just about 200 kBps :-( Colleagues of mine running some PC based routers have very similar experiences with this driver (in both 4.3 and 4.4 Rel's) The same card running under the exactely same conditions in NetBSD is working pretty good (11 MBps) and in Windows 2000 (8 MBps). Also running other cards (like those with rl drivers) on the same network gives very reasonable results in FreeBSD (approx. 10.5 MBps) so I'm pretty convinced driver is to blame. Does anybody have some workaround for this? (If there is a need for me to send better diagnostics than it's no problem.) Best regards, Petr Holub ================================================================ Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 2 Institute of Compt. Science 10200 Praha, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: Petr.Holub@cesnet.cz phone: +420-5-41512278 e-mail: hopet@ics.muni.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 18 5:20:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aragorn.ics.muni.cz (aragorn.ics.muni.cz [147.251.4.33]) by hub.freebsd.org (Postfix) with ESMTP id 3E96437B416; Tue, 18 Dec 2001 05:18:07 -0800 (PST) Received: from dior.ics.muni.cz (dior.ics.muni.cz [147.251.6.10]) by aragorn.ics.muni.cz (8.8.5/8.8.5) with ESMTP id OAA21057; Tue, 18 Dec 2001 14:18:05 +0100 (MET) Received: from kloboucek (root@localhost) (authenticated as hopet with LOGIN) by dior.ics.muni.cz (8.10.1/8.10.0.Beta12) with ESMTP id fBIDI4o23988; Tue, 18 Dec 2001 14:18:04 +0100 (MET) From: "Petr Holub" To: , , Subject: firewire driver Date: Tue, 18 Dec 2001 14:17:07 +0100 Message-ID: <003801c187c6$4aee4c50$d2e86cc2@kloboucek> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0039_01C187CE.ACB2B450" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0039_01C187CE.ACB2B450 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Hi all! I'm struggling my FireWire OHCI based card in my notebook. I'm using driver from DVTS project (that's what I finally want to have up and running). I'm running FreeBSD 4.4 Release. dmesg of my machine is in the attachement (using boot -v). I've already added proper id for my card in both files required (0x8027). The problem is when booting I get "could not map memory" error in this part of code: ------------------------------------------------------------------- fwohci.c: #define DEF_CACHE_LINE 0x10 cache_line = DEF_CACHE_LINE; pci_write_config(dev, PCIR_CACHELNSZ, cache_line, 1); /**/ fun = pci_read_config(dev, 0xf0, 4); fun |= 7; pci_write_config(dev, 0xf0, fun, 4); /**/ rid = PCI_MAP_REG_START; sc->fc.mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0, ~0, 1, RF_ACTIVE); if (!sc->fc.mem) { device_printf(dev, "could not map memory\n"); error = ENXIO; goto fail; } sc->base = rman_get_virtual(sc->fc.mem); #endif /* __FreeBSD__ */ ifp->if_flags &= ~IFF_UP; /* Stop all DMA operation db.immediately */ fwohci_stop_dma(sc, -1); ------------------------------------------------------------------- I tried to use #define PCI_ENABLE_IO_MODES in pci/pci.c but got no difference. I've noticed there is a option PCI_ENABLE_IO_MODES in -CURRENT kernel, but I'm not able to use it since this machine is a production one. I think this option can help somehow - at least it seems so from the description of this option in LINT. But I haven't seen it in 4-STABLE. What I'm suspicious about is this part of dmesg: found-> vendor=0x104c, dev=0x8027, revid=0x00 class=0c-00-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 cmdreg=0x0006, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=11 which seems to me like BIOS forgot to allocate some memory for this card. Just to mention: card itself is OK since it's working on the same machine in Windows 2000 (e.g. in Adobe Premiere 6.0). But it's possible Windows driver does the allocation on its own (btw: Windows drivers are the default ones: 1394bus.sys and ohci1394.sys). Does anybody have some idea how to move on? With best regards, Petr Holub ================================================================ Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 2 Institute of Compt. Science 10200 Praha, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: Petr.Holub@cesnet.cz phone: +420-5-41512278 e-mail: hopet@ics.muni.cz ------=_NextPart_000_0039_01C187CE.ACB2B450 Content-Type: application/octet-stream; name="dmesg.KLOBOUCEK" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.KLOBOUCEK" Copyright (c) 1992-2001 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 4.4-RELEASE #6: Mon Dec 10 15:16:37 CET 2001=0A= toor@kloboucek.ics.muni.cz:/usr/src/sys/compile/KLOBOUCEK=0A= Calibrating clock(s) ... TSC clock: 902080409 Hz, i8254 clock: 1193228 Hz=0A= CLK_USE_I8254_CALIBRATION not specified - using default frequency=0A= Timecounter "i8254" frequency 1193182 Hz=0A= CLK_USE_TSC_CALIBRATION not specified - using old calibration method=0A= CPU: Pentium III/Pentium III Xeon/Celeron (902.05-MHz 686-class CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0x68a Stepping =3D 10=0A= = Features=3D0x383f9ff=0A= real memory =3D 267292672 (261028K bytes)=0A= Physical memory chunk(s):=0A= 0x00001000 - 0x0009efff, 647168 bytes (158 pages)=0A= 0x0041f000 - 0x0fee0fff, 262938624 bytes (64194 pages)=0A= avail memory =3D 256208896 (250204K bytes)=0A= bios32: Found BIOS32 Service Directory header at 0xc00f1c80=0A= bios32: Entry =3D 0xf14a0 (c00f14a0) Rev =3D 0 Len =3D 1=0A= pcibios: PCI BIOS entry at 0x16a0=0A= pnpbios: Found PnP BIOS data at 0xc00fbce0=0A= pnpbios: Entry =3D f0000:bd10 Rev =3D 1.0=0A= pnpbios: OEM ID cd041=0A= Other BIOS signatures found:=0A= ACPI: 000f7220=0A= Preloaded elf kernel "kernel" at 0xc03f9000.=0A= netsmb_dev: loaded=0A= Pentium Pro MTRR support enabled=0A= md0: Malloc disk=0A= Creating DISK md0=0A= Math emulator present=0A= pci_open(1): mode 1 addr port (0x0cf8) is 0x80001004=0A= pci_open(1a): mode1res=3D0x80000000 (0x80000000)=0A= pci_cfgcheck: device 0 [class=3D060000] [hdr=3D00] is there = (id=3D11308086)=0A= Using $PIR table, 4 entries at 0xc00f1c10=0A= apm0: on motherboard=0A= apm: found APM BIOS v1.2, connected at v1.2=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= pcib0: on motherboard=0A= found-> vendor=3D0x8086, dev=3D0x1130, revid=3D0x11=0A= class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0006, statreg=3D0x2090, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= found-> vendor=3D0x8086, dev=3D0x1132, revid=3D0x11=0A= class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0007, statreg=3D0x02b0, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Da, irq=3D11=0A= map[10]: type 1, range 32, base f8000000, size 26=0A= map[14]: type 1, range 32, base f7800000, size 19=0A= found-> vendor=3D0x8086, dev=3D0x2448, revid=3D0x03=0A= class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0=0A= subordinatebus=3D1 secondarybus=3D1=0A= cmdreg=3D0x0107, statreg=3D0x0080, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x06 (1500 ns), maxlat=3D0x00 (0 ns)=0A= found-> vendor=3D0x8086, dev=3D0x244c, revid=3D0x03=0A= class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x010f, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= found-> vendor=3D0x8086, dev=3D0x244a, revid=3D0x03=0A= class=3D01-01-80, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= map[20]: type 1, range 32, base 0000b800, size 4=0A= found-> vendor=3D0x8086, dev=3D0x2442, revid=3D0x03=0A= class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Dd, irq=3D9=0A= map[20]: type 1, range 32, base 0000b400, size 5=0A= found-> vendor=3D0x8086, dev=3D0x2444, revid=3D0x03=0A= class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Dc, irq=3D9=0A= map[20]: type 1, range 32, base 0000b000, size 5=0A= found-> vendor=3D0x8086, dev=3D0x2445, revid=3D0x03=0A= class=3D04-01-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Db, irq=3D10=0A= map[10]: type 1, range 32, base 0000e000, size 8=0A= map[14]: type 1, range 32, base 0000e100, size 6=0A= found-> vendor=3D0x8086, dev=3D0x2446, revid=3D0x03=0A= class=3D07-03-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0005, statreg=3D0x0280, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)=0A= intpin=3Db, irq=3D10=0A= map[10]: type 1, range 32, base 0000e500, size 8=0A= map[14]: type 1, range 32, base 0000e300, size 7=0A= pci0: on pcib0=0A= agp0: mem = 0xf7800000-0xf787ffff,0xf8000000-0xfbffffff irq 11 at device 2.0 on pci0=0A= agp0: allocating GATT for aperture of size 64M=0A= pcib1: at device 30.0 = on pci0=0A= found-> vendor=3D0x10ec, dev=3D0x8139, revid=3D0x10=0A= class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0007, statreg=3D0x0290, cachelnsz=3D0 (dwords)=0A= lattimer=3D0x40 (1920 ns), mingnt=3D0x20 (8000 ns), maxlat=3D0x40 = (16000 ns)=0A= intpin=3Da, irq=3D4=0A= map[10]: type 1, range 32, base 0000d800, size 8=0A= map[14]: type 1, range 32, base f7000000, size 8=0A= found-> vendor=3D0x104c, dev=3D0xac42, revid=3D0x00=0A= class=3D06-07-00, hdrtype=3D0x02, mfdev=3D1=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0007, statreg=3D0x0210, cachelnsz=3D8 (dwords)=0A= lattimer=3D0x40 (1920 ns), mingnt=3D0x40 (16000 ns), maxlat=3D0x03 (750 = ns)=0A= intpin=3Da, irq=3D11=0A= found-> vendor=3D0x104c, dev=3D0xac42, revid=3D0x00=0A= class=3D06-07-00, hdrtype=3D0x02, mfdev=3D1=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0007, statreg=3D0x0210, cachelnsz=3D8 (dwords)=0A= lattimer=3D0x40 (1920 ns), mingnt=3D0x40 (16000 ns), maxlat=3D0x03 (750 = ns)=0A= intpin=3Da, irq=3D11=0A= found-> vendor=3D0x104c, dev=3D0x8027, revid=3D0x00=0A= class=3D0c-00-10, hdrtype=3D0x00, mfdev=3D1=0A= subordinatebus=3D0 secondarybus=3D0=0A= cmdreg=3D0x0006, statreg=3D0x0210, cachelnsz=3D8 (dwords)=0A= lattimer=3D0x40 (1920 ns), mingnt=3D0x02 (500 ns), maxlat=3D0x04 (1000 = ns)=0A= intpin=3Da, irq=3D11=0A= pci1: on pcib1=0A= rl0: port 0xd800-0xd8ff mem = 0xf7000000-0xf70000ff irq 4 at device 4.0 on pci1=0A= rl0: Ethernet address: 00:e0:18:2c:ea:6a=0A= miibus0: on rl0=0A= rlphy0: on miibus0=0A= rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0A= bpf: rl0 attached=0A= pcic0: irq 11 at device 7.0 on pci1=0A= pcic0: PCI Memory allocated: 0x44000000=0A= pcic0: TI12XX PCI Config Reg: [speaker enable][FUNC pci int + CSC serial = isa irq]=0A= pccard0: on pcic0=0A= pcic1: irq 11 at device 7.1 on pci1=0A= pcic1: PCI Memory allocated: 0x44001000=0A= pcic1: TI12XX PCI Config Reg: [speaker enable][FUNC pci int + CSC serial = isa irq]=0A= using shared irq11.=0A= pccard1: on pcic1=0A= fwohci0: irq 11 at device 7.2 on pci1=0A= pcilynx0: PCI bus latency was changing to 200.=0A= fwohci0: could not map memory=0A= device_probe_and_attach: fwohci0 attach returned 6=0A= isab0: at device 31.0 = on pci0=0A= isa0: on isab0=0A= atapci0: port 0xb800-0xb80f at device = 31.1 on pci0=0A= ata0: iobase=3D0x01f0 altiobase=3D0x03f6 bmaddr=3D0xb800=0A= ata0: mask=3D03 status0=3D50 status1=3D00=0A= ata0: mask=3D03 ostat0=3D50 ostat2=3D00=0A= ata0-master: ATAPI probe a=3D00 b=3D00=0A= ata0-slave: ATAPI probe a=3D00 b=3D00=0A= ata0: mask=3D03 status0=3D50 status1=3D00=0A= ata0-master: ATA probe a=3D01 b=3Da5=0A= ata0: devices=3D01=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata1: iobase=3D0x0170 altiobase=3D0x0376 bmaddr=3D0xb808=0A= ata1: mask=3D03 status0=3D00 status1=3D00=0A= ata1: mask=3D03 ostat0=3D00 ostat2=3D00=0A= ata1-master: ATAPI probe a=3D00 b=3D00=0A= ata1-slave: ATAPI probe a=3D00 b=3D00=0A= ata1: mask=3D03 status0=3D00 status1=3D00=0A= ata1: devices=3D00=0A= ata1: at 0x170 irq 15 on atapci0=0A= uhci0: port = 0xb400-0xb41f irq 9 at device 31.2 on pci0=0A= usb0: on uhci0=0A= usb0: USB revision 1.0=0A= uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub0: 2 ports with 2 removable, self powered=0A= uhci1: port = 0xb000-0xb01f irq 9 at device 31.4 on pci0=0A= using shared irq9.=0A= usb1: on uhci1=0A= usb1: USB revision 1.0=0A= uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub1: 2 ports with 2 removable, self powered=0A= pcm0: port 0xe100-0xe13f,0xe000-0xe0ff irq 10 at = device 31.5 on pci0=0A= pcm0: ac97 codec id 0x83847600 (SigmaTel STAC9700/9783/9784)=0A= pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, = SigmaTel 3D Enhancement=0A= pcm: setmap 2e000, 4000; 0xcf722000 -> 2e000=0A= pcm: setmap 32000, 4000; 0xcf726000 -> 32000=0A= pcm: setmap 36000, 4000; 0xcf72a000 -> 36000=0A= pci0: (vendor=3D0x8086, dev=3D0x2446) at 31.6 irq 10=0A= ata-: ata0 exists, using next available unit number=0A= ata-: ata1 exists, using next available unit number=0A= pcic-: pcic0 exists, using next available unit number=0A= pcic-: pcic1 exists, using next available unit number=0A= Trying Read_Port at 203=0A= Trying Read_Port at 243=0A= Trying Read_Port at 283=0A= Trying Read_Port at 2c3=0A= Trying Read_Port at 303=0A= Trying Read_Port at 343=0A= Trying Read_Port at 383=0A= Trying Read_Port at 3c3=0A= isa_probe_children: disabling PnP devices=0A= isa_probe_children: probing non-PnP devices=0A= orm0: