From owner-freebsd-current Sun Feb 21 0:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A1011148C for ; Sun, 21 Feb 1999 00:46:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA18860; Sun, 21 Feb 1999 00:46:22 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Feb 1999 00:46:22 -0800 (PST) From: Matthew Dillon Message-Id: <199902210846.AAA18860@apollo.backplane.com> To: John Polstra Cc: hibma@skylink.it, current@FreeBSD.ORG Subject: Re: const char * References: <199902210456.UAA18273@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :don't think there's any way to get rid of the warning without changing :the declarations. : :In my opinion, the use of "-Wcast-qual" is bogus. Often the whole :point of a cast is to remove a qualifier such as const. It's one :thing to warn when that's done implicitly, and quite another thing to :warn when the programmer has clearly expressed his intent through the :use of a cast. : :John :-- : John Polstra jdp@polstra.com There are only a few cases where cast-qual is bogus. 99% of the warnings it generated were quite real. Maybe not bugs, but definitely programming by misadventure. Volatile and const are only going to become more important as we get deeper into the SMP issues. Especially volatile. cast-qual is necessary to keep people from making bozo mistakes. 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 Feb 21 2:16:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id D48FA116AE for ; Sun, 21 Feb 1999 02:15:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA13128; Sun, 21 Feb 1999 16:37:20 +1100 Date: Sun, 21 Feb 1999 16:37:20 +1100 From: Bruce Evans Message-Id: <199902210537.QAA13128@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, hibma@skylink.it Subject: Re: const char * Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >../../dev/usb/ukbd.c: In function `ukbd_detach': >../../dev/usb/ukbd.c:373: warning: cast discards `const' from pointer >target type >... >It is a consequence of the following type definition: > >(sys/bus_private.h) >struct device { >... > const char* desc; /* driver specific description */ >... >} > >One problem I have is that a string like that might be produced by >concatenating a few strings together. In the case of USB the desc is >the string returned by the device. At attach the string is created and >malloc()-ed, at detach free()-ed. At the (bus) level, `desc' is just a string. It is const mainly so that callers can pass a literal string to device_set_desc() without getting a warning from -Wcast-qual. Unfortunately, this prevents the bus level from helping you keep track of how the string was created. The warning could be avoided using a table of the original (non-const) addresses of the (malloc()ed) strings passed to device_set_desc(). This is a bit much to avoid a harmless warning, but you would need to do it if not all strings were malloc()ed. The warning can be avoided by (ab)using a variant union. I plan to use a suitably macroised version of this to fix warnings for library functions. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 2:16:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 73F52116D1; Sun, 21 Feb 1999 02:15:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA07200; Sun, 21 Feb 1999 14:58:06 +1100 Date: Sun, 21 Feb 1999 14:58:06 +1100 From: Bruce Evans Message-Id: <199902210358.OAA07200@godzilla.zeta.org.au> To: current@FreeBSD.ORG, romanp@wuppy.rcs.ru Subject: Re: Problems with nfsstat and dynamic OID Cc: dfr@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hello! Five minutes ago I type 'nfsstat' and got: > >nfsstat: sysctl: No such file or directory > >I take a look at the source and that's what I found: >Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS, >but name[1] has a value of vfc.vfc_typenum, returned by getvfsbyname(3). >And it is very bad, 'cause vfc_typenum contains fs type number assigned >by kernel, not sysctl OID! As we can see in nfs_vfsops.c NFS sysctl node >declared with OID_AUTO (on my system it becomes 119, not 4 as returned by >getvfsbyname). Now that it is possible to change the sysctl tree at runtime, the changes are not actually (completely) made for vfs sysctls. Special code for making "impossible" changes for vfs sysctls went away. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 2:21:23 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 A89B811830 for ; Sun, 21 Feb 1999 02:21:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id CAA01420; Sun, 21 Feb 1999 02:20:51 -0800 Date: Sun, 21 Feb 1999 02:20:51 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: grog@lemis.com, paulz@trantor.xs4all.nl, freebsd-current@FreeBSD.ORG Subject: Re: Slow seq. write on Seagate ST36530N In-Reply-To: <199902210201.TAA16287@panzer.plutotech.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 > > > > It sounds like a good idea, and it is. What I want to see is scsi_da use > > this automatically. I have never liked the "punch it, Chewey!" approach > > CAM has been taking..... > > What do you mean "scsi_da use this automatically"? > > All of the tagged queueing stuff is controlled in the transport layer. > What are you proposing that the DA driver do? > It is up to a target driver to control properties of performance and reliability on the target device and to mediate between filesystems and that device. The da driver should be checking for and adjusting performance criteria based upon this. Whether it is now currently mistakenly placed in the transport layer (tags are a property of parallel SCSI- tags, qua tags, are not the issue, but the number of parallem operations at a time is) is not the issue. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 3:11:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.bhl (1Cust14.tnt1.lafayette.in.da.uu.net [208.254.19.14]) by hub.freebsd.org (Postfix) with ESMTP id 8A1911142D; Sun, 21 Feb 1999 03:11:35 -0800 (PST) (envelope-from bhlewis@gte.net) Received: from ylana.home.bhl (localhost.home.bhl [127.0.0.1]) by home.bhl (8.9.3/8.8.8) with ESMTP id GAA64516; Sun, 21 Feb 1999 06:11:26 -0500 (EST) (envelope-from bhlewis@ylana.home.bhl) Message-Id: <199902211111.GAA64516@home.bhl> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Michael Reifenberger , freebsd-current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: Compaq built-in ncr & tl controllers with 4.0 In-reply-to: Your message of "Thu, 18 Feb 1999 22:38:02 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Feb 1999 06:11:26 -0500 From: Benjamin Lewis Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mr. Rabson- Sorry it's been so long for me to get back to you about the patch you sent. The machine is located accross country & 3 time zones away, so coordinating with the people at the console has been tedious. In any case, the patch worked brilliantly. The machine is now running a 4.0 generic kernel and is in the process of building and installing the SMP kernel. I would suggest that the patches make their way into the 4.0 and 3.1 source trees, although I have yet to test them on a machine that was not affected by the PCI bus probe problem. I'll incorporate the patch into a more conventional 4.0 machine later today and let you know the results. We want to thank you so much for your quick response. The owners of the machine are quite gratified that they will be able to take advantage of the second processor after all. The dmesg from the machine appears below, in case you find it interesting. -Ben Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Feb 20 16:51:12 PST 1999 bhlewis@server.mediumlook.com:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (299.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80fbff real memory = 16777216 (16384K bytes) avail memory = 13316096 (13004K bytes) Preloaded elf kernel "kernel" at 0xf0342000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 vga0: rev 0x43 int a irq 11 on pci0.13.0 chip1: rev 0x0c on pci0.15.0 ide_pci0: rev 0x0a int a irq 15 on pci0 .15.1 chip2: rev 0x01 on pci0.17.0 Probing for devices on PCI bus 1: tl0: rev 0x10 int a irq 11 on pci1.7.0 tl0: Ethernet address: 00:80:5f:85:97:2e tl0: autoneg complete, link status good (half-duplex, 10Mbps) ncr0: rev 0x04 int a irq 11 on pci1.9.0 adv0: rev 0x02 int a irq 11 on pci1.10. 0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 0, queue depth 16 Probing for devices on PCI bus 2: Probing for PnP devices: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: @@@0000 [0x0000 0000] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 1378KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 not found at 0x170 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at adv0 bus 0 target 4 lun 0 da1: Removable Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: Attempt to query device size failed: NOT READY, Medium not present da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) -- Benjamin Lewis bhlewis@gte.net -or- bhlewis@purdue.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 3:36:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id C9F3911190 for ; Sun, 21 Feb 1999 03:36:35 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.51]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4F01 for ; Sun, 21 Feb 1999 12:36:33 +0100 Received: from daemon.ninth-circle.org (daemon.ninth-circle.org [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id MAA74608 for ; Sun, 21 Feb 1999 12:19:09 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [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, 21 Feb 1999 12:19:08 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: Hold it! LINT / GENERIC inconsistency Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone care to look at LINT and GENERIC and in particular at the ppc0 line? GENERIC lists ppc0 as a device, LINT as a controller. Since config accepts GENERIC's format I'm inclined to think that's the correct one. But one of my own files has controller in it and is also accepted, but I don't think we can mix device/controller lines with each other, right? Someone care to enlighten me or update the appropriate files? CURRENT sources from yesterday 20-2-1999. --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org> asmodai(at)wxs.nl This is my Truth, tell me your's... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 3:36:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 2ED8B111E8 for ; Sun, 21 Feb 1999 03:36:48 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA02068; Sun, 21 Feb 1999 22:35:34 +1100 Date: Sun, 21 Feb 1999 22:35:34 +1100 From: Bruce Evans Message-Id: <199902211135.WAA02068@godzilla.zeta.org.au> To: current@FreeBSD.ORG, green@unixhelp.org Subject: Re: one SysV bug/fix, how many more Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >parts of proc (p_vmspace etc.) For that matter, does any of kern_exit.c:exit1() >need to be spl()d? It sure seems like it to me. Along with other parts of >kern_exit.c, and many other things having to do with refcnt's. Is it just my >paranoia, or have I got this spl concept correct? spl is for blocking interrupts. Process-related things shouldn't be and mostly aren't touched by interrupts. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 3:42:18 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 EF9B011BB4; Sun, 21 Feb 1999 03:42:14 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA55422; Sun, 21 Feb 1999 11:41:31 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 21 Feb 1999 11:41:30 +0000 (GMT) From: Doug Rabson To: Benjamin Lewis Cc: Michael Reifenberger , freebsd-current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: Compaq built-in ncr & tl controllers with 4.0 In-Reply-To: <199902211111.GAA64516@home.bhl> 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, 21 Feb 1999, Benjamin Lewis wrote: > Mr. Rabson- > > Sorry it's been so long for me to get back to you about the patch you sent. > The machine is located accross country & 3 time zones away, so coordinating > with the people at the console has been tedious. > > In any case, the patch worked brilliantly. The machine is now running a 4.0 > generic kernel and is in the process of building and installing the SMP kernel. > I would suggest that the patches make their way into the 4.0 and 3.1 source > trees, although I have yet to test them on a machine that was not affected by > the PCI bus probe problem. I'll incorporate the patch into a more > conventional 4.0 machine later today and let you know the results. > > We want to thank you so much for your quick response. The owners of the > machine are quite gratified that they will be able to take advantage of the > second processor after all. > > The dmesg from the machine appears below, in case you find it interesting. I've committed the fix to both branches, thanks for the feedback. -- 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 Sun Feb 21 3:50:46 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 88CBF11804; Sun, 21 Feb 1999 03:50:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA55454; Sun, 21 Feb 1999 11:49:13 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 21 Feb 1999 11:49:13 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: current@FreeBSD.ORG, romanp@wuppy.rcs.ru, dfr@FreeBSD.ORG Subject: Re: Problems with nfsstat and dynamic OID In-Reply-To: <199902210358.OAA07200@godzilla.zeta.org.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 Sun, 21 Feb 1999, Bruce Evans wrote: > >Hello! Five minutes ago I type 'nfsstat' and got: > > > >nfsstat: sysctl: No such file or directory > > > >I take a look at the source and that's what I found: > >Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS, > >but name[1] has a value of vfc.vfc_typenum, returned by getvfsbyname(3). > >And it is very bad, 'cause vfc_typenum contains fs type number assigned > >by kernel, not sysctl OID! As we can see in nfs_vfsops.c NFS sysctl node > >declared with OID_AUTO (on my system it becomes 119, not 4 as returned by > >getvfsbyname). > > Now that it is possible to change the sysctl tree at runtime, the changes > are not actually (completely) made for vfs sysctls. Special code for > making "impossible" changes for vfs sysctls went away. Oh. Thats nasty. I don't want to allocate special oids for 'privileged' nodes. I think the userland code should use sysctlbyname() instead. This patch seems to fix it for me: Index: nfsstat.c =================================================================== RCS file: /home/ncvs/src/usr.bin/nfsstat/nfsstat.c,v retrieving revision 1.12 diff -u -r1.12 nfsstat.c --- nfsstat.c 1998/10/25 10:59:44 1.12 +++ nfsstat.c 1999/02/21 11:47:08 @@ -162,16 +162,9 @@ err(1, "kvm_read"); } } else { - int name[3]; size_t buflen = sizeof *stp; - struct vfsconf vfc; - if (getvfsbyname("nfs", &vfc) < 0) - err(1, "getvfsbyname: NFS not compiled into kernel"); - name[0] = CTL_VFS; - name[1] = vfc.vfc_typenum; - name[2] = NFS_NFSSTATS; - if (sysctl(name, 3, stp, &buflen, (void *)0, (size_t)0) < 0) { + if (sysctlbyname("vfs.nfs.nfsstats", stp, &buflen, (void *)0, (size_t)0) < 0) { err(1, "sysctl"); } } -- 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 Sun Feb 21 3:55:43 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 E142F111E8; Sun, 21 Feb 1999 03:55:29 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA55502; Sun, 21 Feb 1999 11:54:09 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 21 Feb 1999 11:54:09 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: current@FreeBSD.ORG, romanp@wuppy.rcs.ru, dfr@FreeBSD.ORG Subject: Re: Problems with nfsstat and dynamic OID In-Reply-To: <199902210358.OAA07200@godzilla.zeta.org.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 Sun, 21 Feb 1999, Bruce Evans wrote: > >Hello! Five minutes ago I type 'nfsstat' and got: > > > >nfsstat: sysctl: No such file or directory > > > >I take a look at the source and that's what I found: > >Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS, > >but name[1] has a value of vfc.vfc_typenum, returned by getvfsbyname(3). > >And it is very bad, 'cause vfc_typenum contains fs type number assigned > >by kernel, not sysctl OID! As we can see in nfs_vfsops.c NFS sysctl node > >declared with OID_AUTO (on my system it becomes 119, not 4 as returned by > >getvfsbyname). > > Now that it is possible to change the sysctl tree at runtime, the changes > are not actually (completely) made for vfs sysctls. Special code for > making "impossible" changes for vfs sysctls went away. A related problem is in mountd which should be fixed by this patch: Index: mountd.c =================================================================== RCS file: /home/ncvs/src/sbin/mountd/mountd.c,v retrieving revision 1.34 diff -u -r1.34 mountd.c --- mountd.c 1998/12/29 09:38:49 1.34 +++ mountd.c 1999/02/21 11:53:45 @@ -255,7 +255,7 @@ char **argv; { SVCXPRT *udptransp, *tcptransp; - int c, error, mib[3]; + int c, error; struct vfsconf vfc; error = getvfsbyname("nfs", &vfc); @@ -321,10 +321,7 @@ } } if (!resvport_only) { - mib[0] = CTL_VFS; - mib[1] = vfc.vfc_typenum; - mib[2] = NFS_NFSPRIVPORT; - if (sysctl(mib, 3, NULL, NULL, &resvport_only, + if (sysctlbyname("vfs.nfs.nfs_privport", NULL, NULL, &resvport_only, sizeof(resvport_only)) != 0 && errno != ENOENT) { syslog(LOG_ERR, "sysctl: %m"); exit(1); -- 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 Sun Feb 21 4:34: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 4FAAD11740; Sun, 21 Feb 1999 04:33:36 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA05724; Sun, 21 Feb 1999 23:32:15 +1100 Date: Sun, 21 Feb 1999 23:32:15 +1100 From: Bruce Evans Message-Id: <199902211232.XAA05724@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: Problems with nfsstat and dynamic OID Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG, romanp@wuppy.rcs.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Now that it is possible to change the sysctl tree at runtime, the changes >> are not actually (completely) made for vfs sysctls. Special code for >> making "impossible" changes for vfs sysctls went away. > >Oh. Thats nasty. I don't want to allocate special oids for 'privileged' >nodes. I think the userland code should use sysctlbyname() instead. >This patch seems to fix it for me: > >Index: nfsstat.c >=================================================================== >RCS file: /home/ncvs/src/usr.bin/nfsstat/nfsstat.c,v >retrieving revision 1.12 >diff -u -r1.12 nfsstat.c >--- nfsstat.c 1998/10/25 10:59:44 1.12 >+++ nfsstat.c 1999/02/21 11:47:08 >@@ -162,16 +162,9 @@ > err(1, "kvm_read"); > } > } else { >- int name[3]; > size_t buflen = sizeof *stp; >- struct vfsconf vfc; > >- if (getvfsbyname("nfs", &vfc) < 0) >- err(1, "getvfsbyname: NFS not compiled into kernel"); >- name[0] = CTL_VFS; >- name[1] = vfc.vfc_typenum; >- name[2] = NFS_NFSSTATS; >- if (sysctl(name, 3, stp, &buflen, (void *)0, (size_t)0) < 0) { >+ if (sysctlbyname("vfs.nfs.nfsstats", stp, &buflen, (void *)0, (size_t)0) < 0) { > err(1, "sysctl"); > } > } The old interface is the standard one (although the above code shows how inconvenient it is). mountd uses it too. Perhaps the sysctl oid could be assigned to the vfs type number instead of vice versa. The type number namespace can already have holes, although it can't be very sparse because getvfsbyname(3) has to do an O(n) search of it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 4:54: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 CC7DF118BF; Sun, 21 Feb 1999 04:53:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id NAA16216; Sun, 21 Feb 1999 13:51:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: dfr@nlsystems.com, current@FreeBSD.ORG, dfr@FreeBSD.ORG, romanp@wuppy.rcs.ru Subject: Re: Problems with nfsstat and dynamic OID In-reply-to: Your message of "Sun, 21 Feb 1999 23:32:15 +1100." <199902211232.XAA05724@godzilla.zeta.org.au> Date: Sun, 21 Feb 1999 13:51:31 +0100 Message-ID: <16214.919601491@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199902211232.XAA05724@godzilla.zeta.org.au>, Bruce Evans writes: >>Index: nfsstat.c >>=================================================================== >>RCS file: /home/ncvs/src/usr.bin/nfsstat/nfsstat.c,v >>retrieving revision 1.12 >>diff -u -r1.12 nfsstat.c >>--- nfsstat.c 1998/10/25 10:59:44 1.12 >>+++ nfsstat.c 1999/02/21 11:47:08 >>@@ -162,16 +162,9 @@ >> err(1, "kvm_read"); >> } >> } else { >>- int name[3]; >> size_t buflen = sizeof *stp; >>- struct vfsconf vfc; >> >>- if (getvfsbyname("nfs", &vfc) < 0) >>- err(1, "getvfsbyname: NFS not compiled into kernel"); >>- name[0] = CTL_VFS; >>- name[1] = vfc.vfc_typenum; >>- name[2] = NFS_NFSSTATS; >>- if (sysctl(name, 3, stp, &buflen, (void *)0, (size_t)0) < 0) { >>+ if (sysctlbyname("vfs.nfs.nfsstats", stp, &buflen, (void *)0, (size_t)0) < 0) { >> err(1, "sysctl"); >> } >> } > >The old interface is the standard one (although the above code shows how >inconvenient it is). mountd uses it too. There is nothing "less standard" about sysctlbyname to my knowledge... -- 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 Sun Feb 21 5:14:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id EF25011BDD for ; Sun, 21 Feb 1999 05:14:32 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id VAA19372; Sun, 21 Feb 1999 21:14:05 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199902211314.VAA19372@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: problem during online register StarOffice 5.0 In-reply-to: Your message of "Fri, 19 Feb 1999 13:38:21 +0200." <36CD4D2D.8B6B939@altavista.net> Content-Transfer-Encoding: quoted-printable Date: Sun, 21 Feb 1999 21:14:05 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > I had the same problem, when first installing SO5, and found "workarrou= nd". W hen > you start SO and get question "do you want to register now", reply "no"= , then > select menu "Tools"->"Macro..."->"Organazer.." select "Libraries" tab a= nd ena ble > all libraries (by checking checkboxes). Then re-enter registration mode= (menu > "Help"-> "Registration..". Maybe this will help (it worked for me). > = > Sincerely, > = > Maxim Umm, what libraries should be there? I only have a single checkbox next to a single library ("Standard") and only one choice in the dropdown box = (which "soffice"). This can't be disabled.. Should there be more? Perhaps this is the problem? > Chan Yiu Wah wrote: > = > > Hello, > > > > I encounterd an error when I tried to the online register StarOffice = 5.0. T he > > error is uforms =3D ActiveDocument.UNO.Drawpage.Forms.=A0 Is there an= other way t o > > register to get the unlimit access for personal edition (so5).=A0 Tha= nks. > > > > Clarence > > > > 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 > = Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 5:14:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 09E5611C05; Sun, 21 Feb 1999 05:14:37 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA08457; Mon, 22 Feb 1999 00:14:35 +1100 Date: Mon, 22 Feb 1999 00:14:35 +1100 From: Bruce Evans Message-Id: <199902211314.AAA08457@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: Problems with nfsstat and dynamic OID Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG, dfr@nlsystems.com, romanp@wuppy.rcs.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>The old interface is the standard one (although the above code shows how >>inconvenient it is). mountd uses it too. > >There is nothing "less standard" about sysctlbyname to my knowledge... sysctl() is in Linux (starting in 2.1.x), BSD4.4, NetBSD, OpenBSD, etc. sysctlbyname() is in FreeBSD (starting in 2.2). Some of the Linux sysctl numbers are even binary compatible. However, all Linux filesystem sysctls are incompatible, starting with the top-level identifier being named CTL_FS instead of CTL_VFS. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 5:37:27 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 D02CF10E01; Sun, 21 Feb 1999 05:37:19 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA55635; Sun, 21 Feb 1999 13:32:57 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 21 Feb 1999 13:32:57 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG, dfr@FreeBSD.ORG, romanp@wuppy.rcs.ru Subject: Re: Problems with nfsstat and dynamic OID In-Reply-To: <199902211314.AAA08457@godzilla.zeta.org.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, 22 Feb 1999, Bruce Evans wrote: > >>The old interface is the standard one (although the above code shows how > >>inconvenient it is). mountd uses it too. > > > >There is nothing "less standard" about sysctlbyname to my knowledge... > > sysctl() is in Linux (starting in 2.1.x), BSD4.4, NetBSD, OpenBSD, etc. > sysctlbyname() is in FreeBSD (starting in 2.2). > > Some of the Linux sysctl numbers are even binary compatible. However, > all Linux filesystem sysctls are incompatible, starting with the top-level > identifier being named CTL_FS instead of CTL_VFS. If more than just NFS was defining its own sysctl variables, I might be worried but as I found out when I did the original dynamic sysctl work, only NFS actually used the (IMHO) ugly mechanism for rewiring its oid number by putting a pointer to the oid in its struct vfsops. Since sysctlbyname exists and is obviously a better mechanism for reading the variable (based on code complexity), then why not use it? We maintain both nfsstat and mountd in our tree and I don't see anyone expecting to be able to run Net/OpenBSD versions of those utilities on FreeBSD. If people feel strongly that we should continue to support the old mechanism, I guess I could modify vfs_register to change the oid numbers. It doesn't really seem worth it to me though. -- 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 Sun Feb 21 5:42:50 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 EAF5410E54; Sun, 21 Feb 1999 05:42:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA16368; Sun, 21 Feb 1999 14:41:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: Bruce Evans , current@FreeBSD.ORG, dfr@FreeBSD.ORG, romanp@wuppy.rcs.ru Subject: Re: Problems with nfsstat and dynamic OID In-reply-to: Your message of "Sun, 21 Feb 1999 13:32:57 GMT." Date: Sun, 21 Feb 1999 14:41:33 +0100 Message-ID: <16366.919604493@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Do ug Rabson writes: >Since >sysctlbyname exists and is obviously a better mechanism for reading the >variable (based on code complexity), then why not use it? I support this. It was the intention of sysctlbyname() to minimize the use of "well-known-OIDs" as much as possible. -- 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 Sun Feb 21 7: 5:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 387AC1149B for ; Sun, 21 Feb 1999 07:05:18 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id QAA21226; Sun, 21 Feb 1999 16:05:10 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id PAA00927; Sun, 21 Feb 1999 15:36:52 +0100 (CET) (envelope-from nsouch) Message-ID: <19990221153652.01510@breizh.teaser.fr> Date: Sun, 21 Feb 1999 15:36:52 +0100 From: Nicolas Souchu To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Current Subject: Re: Hold it! LINT / GENERIC inconsistency References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Sun, Feb 21, 1999 at 12:19:08PM +0100 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 21, 1999 at 12:19:08PM +0100, Jeroen Ruigrok/Asmodai wrote: > >Anyone care to look at LINT and GENERIC and in particular at the ppc0 line? > >GENERIC lists ppc0 as a device, LINT as a controller. GENERIC wins. > >Since config accepts GENERIC's format I'm inclined to think that's the >correct one. But one of my own files has controller in it and is also >accepted, but I don't think we can mix device/controller lines with each >other, right? > >Someone care to enlighten me or update the appropriate files? I do it. Thanks for the report. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Feb 21 7:15:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7653F10EB8 for ; Sun, 21 Feb 1999 07:15:56 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA06982; Sun, 21 Feb 1999 10:15:48 -0500 (EST) Date: Sun, 21 Feb 1999 10:15:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: one SysV bug/fix, how many more In-Reply-To: <199902211135.WAA02068@godzilla.zeta.org.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 Sun, 21 Feb 1999, Bruce Evans wrote: > >parts of proc (p_vmspace etc.) For that matter, does any of kern_exit.c:exit1() > >need to be spl()d? It sure seems like it to me. Along with other parts of > >kern_exit.c, and many other things having to do with refcnt's. Is it just my > >paranoia, or have I got this spl concept correct? > > spl is for blocking interrupts. Process-related things shouldn't be and > mostly aren't touched by interrupts. > > Bruce > But without an spl, couldn't multiple processes do Very Bad Things in a partially shared proc context? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 7:31:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id CCCE7111D2 for ; Sun, 21 Feb 1999 07:30:52 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA15265; Mon, 22 Feb 1999 02:30:50 +1100 Date: Mon, 22 Feb 1999 02:30:50 +1100 From: Bruce Evans Message-Id: <199902211530.CAA15265@godzilla.zeta.org.au> To: bde@zeta.org.au, green@unixhelp.org Subject: Re: one SysV bug/fix, how many more Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> spl is for blocking interrupts. Process-related things shouldn't be and >> mostly aren't touched by interrupts. >But without an spl, couldn't multiple processes do Very Bad Things in a >partially shared proc context? They can do that with or without an spl if they don't lock things properly spl can give improper giant locking as a side effect, but it doesn't necessarily prevent other processes running, since tsleep() isn't locked by spls. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 7:34:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7B94610E01 for ; Sun, 21 Feb 1999 07:34:28 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA11592; Sun, 21 Feb 1999 10:34:25 -0500 (EST) Date: Sun, 21 Feb 1999 10:34:24 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: one SysV bug/fix, how many more In-Reply-To: <199902211530.CAA15265@godzilla.zeta.org.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, 22 Feb 1999, Bruce Evans wrote: > >> spl is for blocking interrupts. Process-related things shouldn't be and > >> mostly aren't touched by interrupts. > > >But without an spl, couldn't multiple processes do Very Bad Things in a > >partially shared proc context? > > They can do that with or without an spl if they don't lock things properly > spl can give improper giant locking as a side effect, but it doesn't > necessarily prevent other processes running, since tsleep() isn't locked > by spls. Okay, so we'd need a true mutex, not spl. Do you not agree that there are some pretty glaring races in code that assumes that vmspace, signals, etc. aren't shared? > > Bruce > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 8:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (Postfix) with ESMTP id E0FC410EB8; Sun, 21 Feb 1999 08:32:43 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.2.NOMIME/8.9.1) with ESMTP id PAA20893; Sun, 21 Feb 1999 15:31:33 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Sun, 21 Feb 1999 15:31:33 +0300 (MSK) From: "Roman V. Palagin" To: Doug Rabson Cc: Bruce Evans , current@FreeBSD.ORG, dfr@FreeBSD.ORG Subject: Re: Problems with nfsstat and dynamic OID 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 Sun, 21 Feb 1999, Doug Rabson wrote: > > Oh. Thats nasty. I don't want to allocate special oids for 'privileged' > nodes. I think the userland code should use sysctlbyname() instead. > This patch seems to fix it for me: Works for me too. This problem exists not only in -current, i believe. Should all sysctl be replaced by sysctlbyname? I just grep sysctl in `find /usr/src/usr.bin *.c` and got many lines. Just start checking... > > Index: nfsstat.c > =================================================================== > RCS file: /home/ncvs/src/usr.bin/nfsstat/nfsstat.c,v > retrieving revision 1.12 > diff -u -r1.12 nfsstat.c > --- nfsstat.c 1998/10/25 10:59:44 1.12 > +++ nfsstat.c 1999/02/21 11:47:08 > @@ -162,16 +162,9 @@ > err(1, "kvm_read"); > } > } else { > - int name[3]; > size_t buflen = sizeof *stp; > - struct vfsconf vfc; > > - if (getvfsbyname("nfs", &vfc) < 0) > - err(1, "getvfsbyname: NFS not compiled into kernel"); > - name[0] = CTL_VFS; > - name[1] = vfc.vfc_typenum; > - name[2] = NFS_NFSSTATS; > - if (sysctl(name, 3, stp, &buflen, (void *)0, (size_t)0) < 0) { > + if (sysctlbyname("vfs.nfs.nfsstats", stp, &buflen, (void *)0, (size_t)0) < 0) { > err(1, "sysctl"); > } > } > > -- > 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 > ------------------------------------------------------------------------- Roman V. Palagin | Friday, monday, what's the difference. System Administrator | (C) Jordan K. Hubbard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 9:23:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id 5479311651 for ; Sun, 21 Feb 1999 09:23:25 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id LAA04062; Sun, 21 Feb 1999 11:23:24 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id LAA09437; Sun, 21 Feb 1999 11:23:24 -0600 (CST) Date: Sun, 21 Feb 1999 12:23:24 -0500 From: Nathan Dorfman To: Lyndon Nerenberg Cc: Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: CardBus Support (was: support for 3Com 3C575 network controller?) Message-ID: <19990221122324.A8721@rtfm.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Lyndon Nerenberg on Sat, Feb 20, 1999 at 08:02:17PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 20, 1999 at 08:02:17PM +0000, Lyndon Nerenberg wrote: > I've been trying to get some progamming doc out of TI for > the PCI1200 PCI/Cardbus bridge (used in the Dell Inspiron > 7000), however they cannot seem to understand that I'm not > asking for a pre-written device driver :-( > > Does anyone out there have doc for the PCI1200 (and > preferably the entire PCI12xx family) they could send me? > Or have a knowledgable contact inside TI that could send > same to me? While CardBus isn't supported, this controller (in my Fujitsu Lifebook 280dx) works with PAO because the PCI<->CardBus bridge supposedly uses some kind of Intel-compatible mode. I've been unable to get it to work under stock pccard without PAO (look at my post to -hackers yesterday), but it worked with PAO without a hitch. > --lyndon -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications usenet posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 9:28:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (Postfix) with ESMTP id A7AAF115DD for ; Sun, 21 Feb 1999 09:28:28 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id SAA02550; Sun, 21 Feb 1999 18:34:22 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 21 Feb 1999 18:34:22 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Lyndon Nerenberg Cc: Nate Williams , "Dan - Sr. Admin" , freebsd-current@FreeBSD.ORG Subject: Re: paranoid patches 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, 18 Feb 1999, Lyndon Nerenberg wrote: > > > Basically, it is a patch into libkvm and w, that will allow a user (with > > > the exception to the super user, naturally) to only view processes or > > > information belonging to him/herself. > > > The only problem with this is setuid binaries. The processes may have > > been started by me (top, etc..), but this wouldn't allow me to monitor > > the process once it's started. > > And, anything that can read /dev/[k]mem is free to bypass libkvm and just > grovel around in the kernel memory space, anyway. Not only that - you would need to disable other holes as well, which has been done on purpose. Think of /procfs and sysctl kern.proc..something. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 9:41:57 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 9C74811CD6 for ; Sun, 21 Feb 1999 09:41:55 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA06507; Sun, 21 Feb 1999 09:35:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA19103; Sun, 21 Feb 1999 09:35:40 -0800 (PST) (envelope-from jdp@polstra.com) 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: <199902210846.AAA18860@apollo.backplane.com> Date: Sun, 21 Feb 1999 09:35:40 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Dillon Subject: Re: const char * Cc: current@FreeBSD.ORG, hibma@skylink.it Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: >: >:In my opinion, the use of "-Wcast-qual" is bogus. Often the whole >:point of a cast is to remove a qualifier such as const. It's one >:thing to warn when that's done implicitly, and quite another thing >:to warn when the programmer has clearly expressed his intent through >:the use of a cast. > > There are only a few cases where cast-qual is bogus. 99% of > the warnings it generated were quite real. Maybe not bugs, but > definitely programming by misadventure. Volatile and const are > only going to become more important as we get deeper into the > SMP issues. Especially volatile. cast-qual is necessary to keep > people from making bozo mistakes. I would find -Wcast-qual tolerable if it behaved just a little bit differently. It should allow without complaint explicit casts which change _only_ the constness. For example, casting from "const char *" to "char *" explicitly would be OK. But casting from, say, "const char *" to "void *" would still produce a warning. This would make it possible to get rid of the warnings in those cases where it made sense to cast away const (e.g., dealing with bad but standard interfaces). The above is more or less how C++'s "const_cast(x)" construct works. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 10:24:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from demo.esys.ca (demo.esys.ca [207.167.22.130]) by hub.freebsd.org (Postfix) with ESMTP id E267511AFA for ; Sun, 21 Feb 1999 10:24:56 -0800 (PST) (envelope-from lyndon@execmail.ca) Received: from ht46l.orthanc.ab.ca (thingfish.v-wave.com [24.108.17.129]) by demo.esys.ca (2.0.4/SMS 2.0.4-beta-5) with ESMTP id CAA01482; Mon, 22 Feb 1999 02:33:31 -0700 From: Lyndon Nerenberg Date: Sun, 21 Feb 1999 18:26:15 +0000 To: Terry Lambert Subject: Re: CardBus Support (was: support for 3Com 3C575 network controller?) Cc: dfr@nlsystems.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199902202318.QAA20687@usr08.primenet.com> References: <199902202318.QAA20687@usr08.primenet.com> from "Lyndon Nerenberg" at Feb 20, 99 08:02:17 pm Message-ID: X-Mailer: Execmail for Win32 Version 5.0 pc5 Build (35) MIME-Version: 1.0 Content-Type: Multipart/signed; boundary="Part9902211826.D"; protocol="application/pgp-signature"; micalg="pgp-sha1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Part9902211826.D Content-Type: Text/Plain; charset="us-ascii"; name="ipm.txt" Content-Disposition: inline; filename="ipm.txt" > There are PDF and zipped PostScript data sheets for these > parts on TI's web page: > > http://www.ti.com/sc/docs/folders/analog/pci1211.html Ya, I found those by doing a search inside the TI site. The problem is the data sheets those URLs point to only describe the hardware side of things. There's nothing there describing how to deal with the chips in software. --lyndon --Part9902211826.D Content-Type: Application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.5.2 (C) 1997-1998 Network Associates, Inc. and its affiliated companies. iQA/AwUBNtBPyRvgRSChfsw2EQIwPQCcDAiFSLHqZpqg/awR2Dht4b3Bt1YAoJCD K8bgH13rKFwM6ppSZwUrgEj1 =yK6J -----END PGP SIGNATURE----- --Part9902211826.D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 10:26:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from demo.esys.ca (demo.esys.ca [207.167.22.130]) by hub.freebsd.org (Postfix) with ESMTP id B3F0711B0C for ; Sun, 21 Feb 1999 10:26:41 -0800 (PST) (envelope-from lyndon@execmail.ca) Received: from ht46l.orthanc.ab.ca (thingfish.v-wave.com [24.108.17.129]) by demo.esys.ca (2.0.4/SMS 2.0.4-beta-5) with ESMTP id CAA01486; Mon, 22 Feb 1999 02:35:16 -0700 From: Lyndon Nerenberg Date: Sun, 21 Feb 1999 18:27:59 +0000 To: Nathan Dorfman Subject: Re: CardBus Support (was: support for 3Com 3C575 network controller?) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19990221122324.A8721@rtfm.net> References: <19990221122324.A8721@rtfm.net> Message-ID: X-Mailer: Execmail for Win32 Version 5.0 pc5 Build (35) MIME-Version: 1.0 Content-Type: Multipart/signed; boundary="Part9902211828.F"; protocol="application/pgp-signature"; micalg="pgp-sha1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Part9902211828.F Content-Type: Text/Plain; charset="us-ascii"; name="ipm.txt" Content-Disposition: inline; filename="ipm.txt" > While CardBus isn't supported, this controller (in my Fujitsu Lifebook 280dx) > works with PAO because the PCI<->CardBus bridge supposedly uses some kind > of Intel-compatible mode. I've been unable to get it to work under stock > pccard without PAO (look at my post to -hackers yesterday), but it worked > with PAO without a hitch. I looked at PAO, but it doesn't appear to support the 3.X branch, which I'm running. If there's a PAO for 3.X, please let me know where it is (!). --lyndon --Part9902211828.F Content-Type: Application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.5.2 (C) 1997-1998 Network Associates, Inc. and its affiliated companies. iQA/AwUBNtBQMhvgRSChfsw2EQIhogCeJB5PFPesZprqy+UO6ksdDjf+HQcAoIra nIYcz9ZmLD23WMIQkRhq5lb8 =Ccva -----END PGP SIGNATURE----- --Part9902211828.F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 11:11:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 352B411487 for ; Sun, 21 Feb 1999 11:11:41 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 26139 invoked by uid 1001); 21 Feb 1999 19:11:39 +0000 (GMT) To: bhlewis@gte.net Cc: dfr@nlsystems.com, root@nihil.plaut.de, freebsd-current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: Compaq built-in ncr & tl controllers with 4.0 From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 21 Feb 1999 06:11:26 -0500" References: <199902211111.GAA64516@home.bhl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 21 Feb 1999 20:11:39 +0100 Message-ID: <26137.919624299@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry it's been so long for me to get back to you about the patch you sent. > The machine is located accross country & 3 time zones away, so coordinating > with the people at the console has been tedious. > > In any case, the patch worked brilliantly. The machine is now running a 4.0 > generic kernel and is in the process of building and installing the SMP kernel. I can confirm that the patch solved the PCI bus problem here too. The machine here is now running 3.1-STABLE. I have included the dmesg output at the end of this message. As for SMP, we're not quite there yet. First, "generic" SMP kernel panics because it finds 50 INTRs. After building a new kernel with 50 INTRs, we got a new panic: "assign_apic_irq: inconsistent table". I can't say I'm surprised, because I *know* there are problems with the Compaq mptable (from earlier message about MP Proliants). So I'm now digging into the Compaq mptable - which is also included at the end of this message. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- 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.1-STABLE #2: Sun Feb 21 17:10:46 CET 1999 toor@newsfeed1.telia.no:/usr/src/sys/compile/NEWSFEED1 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 332803853 Hz CPU: Pentium II/Xeon/Celeron (332.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff> real memory = 603979776 (589824K bytes) avail memory = 584593408 (570892K bytes) Preloaded elf kernel "kernel" at 0xf02a5000. eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 vga0: rev 0x22 int a irq 255 on pci0.6.0 chip1: rev 0x07 on pci0.15.0 chip2: rev 0x03 on pci0.17.0 Probing for devices on PCI bus 1: ncr0: rev 0x14 int a irq 9 on pci1.4.0 ncr1: rev 0x14 int b irq 10 on pci1.4.1 fxp0: rev 0x05 int a irq 10 on pci1.7.0 fxp0: Ethernet address 00:90:27:13:f6:21 tl0: rev 0x10 int a irq 5 on pci1.8.0 tl0: Ethernet address: 00:08:c7:1e:a7:35 tl0: autoneg complete, link status good (half-duplex, 100Mbps) Probing for devices on PCI bus 2: 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: failed to get data. psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 1378KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers Waiting 5 seconds for SCSI devices to settle changing root device to da0s3a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da2 at ncr0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da3 at ncr0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) ---------------------------------------------------------------------- =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f4ff0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x00 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f7d78 signature: 'PCMP' base table length: 532 version: 1.4 checksum: 0x31 OEM ID: 'COMPAQ ' Product ID: 'PROLIANT ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 58 local APIC address: 0xfee00000 extended table length: 76 extended table checksum: 77 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x10 BSP, usable 6 2 1 0x0381 0 0x10 AP, usable 6 5 1 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 EISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 1 4:A 8 19 INT active-lo level 1 4:B 8 18 INT active-lo level 0 10:A 8 23 INT active-lo level 0 10:B 8 23 INT active-lo level 0 10:C 8 23 INT active-lo level 0 10:D 8 23 INT active-lo level 0 11:A 8 22 INT active-lo level 0 11:B 8 22 INT active-lo level 0 11:C 8 22 INT active-lo level 0 11:D 8 22 INT active-lo level 0 12:A 8 21 INT active-lo level 0 12:B 8 21 INT active-lo level 0 12:C 8 21 INT active-lo level 0 12:D 8 21 INT active-lo level 0 13:A 8 20 INT active-lo level 0 13:B 8 20 INT active-lo level 0 13:C 8 20 INT active-lo level 0 13:D 8 20 INT active-lo level 1 6:A 8 19 INT active-lo level 1 6:B 8 19 INT active-lo level 1 6:C 8 19 INT active-lo level 1 6:D 8 19 INT active-lo level 1 7:A 8 18 INT active-lo level 1 7:B 8 18 INT active-lo level 1 7:C 8 18 INT active-lo level 1 7:D 8 18 INT active-lo level 1 8:A 8 17 INT active-lo level 1 8:B 8 17 INT active-lo level 1 8:C 8 17 INT active-lo level 1 8:D 8 17 INT active-lo level 1 9:A 8 16 INT active-lo level 1 9:B 8 16 INT active-lo level 1 9:C 8 16 INT active-lo level 1 9:D 8 16 INT conforms conforms 9 1 8 1 INT conforms conforms 9 0 8 2 INT conforms conforms 9 3 8 3 INT conforms conforms 9 4 8 4 INT conforms conforms 9 5 8 5 INT conforms conforms 9 6 8 6 INT conforms conforms 9 7 8 7 INT conforms conforms 9 8 8 8 INT conforms conforms 9 9 8 9 INT conforms conforms 9 10 8 10 INT conforms conforms 9 11 8 11 INT conforms conforms 9 12 8 12 INT conforms conforms 9 13 8 24 INT conforms conforms 9 14 8 14 INT conforms conforms 9 15 8 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 9 0 255 0 NMI conforms conforms 9 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 11:58:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from poo.smooch (ts03-090.dublin.indigo.ie [194.125.148.100]) by hub.freebsd.org (Postfix) with ESMTP id ADA5411734 for ; Sun, 21 Feb 1999 11:58:25 -0800 (PST) (envelope-from blokey@indigo.ie) Received: (from plop@localhost) by poo.smooch (8.9.2/8.9.1) id TAA38103 for current@freebsd.org; Sun, 21 Feb 1999 19:58:12 GMT (envelope-from plop) Message-ID: <19990221195810.A32005@smooch> Date: Sun, 21 Feb 1999 19:58:10 +0000 From: Smelly Pooh To: current@freebsd.org Subject: ports Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed that as I'm constantly syncing my /usr/ports directory and upgrading programs, the old packages stay there. If I pkg_delete them and there's an unchanged file that exists in both the update and the original then tat gets deleted too. Any way of cleanly removing old packages? Incidentally are the ports trees for all the FreeBSD releases the same one? I mean if I'm running 2.2.x do I still get all the latest ports? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 13: 2:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 39DBB10E9A for ; Sun, 21 Feb 1999 13:02:34 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id OAA20768; Sun, 21 Feb 1999 14:02:04 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902212102.OAA20768@panzer.plutotech.com> Subject: Re: Slow seq. write on Seagate ST36530N In-Reply-To: from Matthew Jacob at "Feb 21, 1999 2:20:51 am" To: mjacob@feral.com Date: Sun, 21 Feb 1999 14:02:04 -0700 (MST) Cc: ken@plutotech.com, grog@lemis.com, paulz@trantor.xs4all.nl, freebsd-current@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 Matthew Jacob wrote... > > > > > > It sounds like a good idea, and it is. What I want to see is scsi_da use > > > this automatically. I have never liked the "punch it, Chewey!" approach > > > CAM has been taking..... > > > > What do you mean "scsi_da use this automatically"? > > > > All of the tagged queueing stuff is controlled in the transport layer. > > What are you proposing that the DA driver do? > > > > It is up to a target driver to control properties of performance and > reliability on the target device and to mediate between filesystems and > that device. The da driver should be checking for and adjusting > performance criteria based upon this. Whether it is now currently > mistakenly placed in the transport layer (tags are a property of > parallel SCSI- tags, qua tags, are not the issue, but the number of > parallem operations at a time is) is not the issue. I think it would be very difficult for the DA driver, or any other peripheral driver to accurately adjust the number of parallel operations based on performance. How does the peripheral driver know whether the underlying device is being "pounded" or just "pinged"? What may be "pounding" for one device might simply be "pinging" for another. Even if you measured latency for each command, there's no way to know the reason for the latency of any given command without in-depth knowledge of the device in question. (e.g., there's no way to know whether a higher-than-average time to completion is the result of an overloaded device, or the result of something like a thermal recalibration...) I think the best we could hope for is some sort of userland benchmarking process that would establish roughly the "best" number of transactions for a given device. Based on what I've seen, I would say that this would generally be either 1, or whatever we determine automatically from the device's queue full responses. There are, I think, relatively few devices that should be in the land in between those values. (e.g., device X doesn't return queue full until we reach 48 transactions, but its performance really stinks if you go above 30 transactions) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 13: 9:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from nu.binary.net (nu.binary.net [12.13.120.25]) by hub.freebsd.org (Postfix) with ESMTP id 982BC11778 for ; Sun, 21 Feb 1999 13:09:40 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by nu.binary.net (8.9.1a/8.9.0) with ESMTP id PAA70904; Sun, 21 Feb 1999 15:09:39 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id PAA19046; Sun, 21 Feb 1999 15:09:39 -0600 (CST) Date: Sun, 21 Feb 1999 16:09:39 -0500 From: Nathan Dorfman To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: CardBus Support (was: support for 3Com 3C575 network controller?) Message-ID: <19990221160939.A18594@rtfm.net> References: <19990221122324.A8721@rtfm.net> <19990221122324.A8721@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Lyndon Nerenberg on Sun, Feb 21, 1999 at 06:27:59PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 21, 1999 at 06:27:59PM +0000, Lyndon Nerenberg wrote: > > > While CardBus isn't supported, this controller (in my Fujitsu Lifebook 280dx) > > works with PAO because the PCI<->CardBus bridge supposedly uses some kind > > of Intel-compatible mode. I've been unable to get it to work under stock > > pccard without PAO (look at my post to -hackers yesterday), but it worked > > with PAO without a hitch. > > I looked at PAO, but it doesn't appear to support the 3.X > branch, which I'm running. If there's a PAO for 3.X, please > let me know where it is (!). That's why I can't run PAO (and consequently no PCMCIA working on my laptop at the moment). There's a PAO for 3.0, but I'm not sure if it's for -stable or 3.0-release. You can only get it by cvsupping pao3 from jaz.jp.freebsd.org. > --lyndon -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications usenet posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 13:46: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3553911BB5 for ; Sun, 21 Feb 1999 13:45:54 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id PAA18992; Sun, 21 Feb 1999 15:45:46 -0600 (CST) Date: Sun, 21 Feb 1999 15:45:46 -0600 (CST) From: Steve Price To: Nathan Dorfman Cc: Lyndon Nerenberg , freebsd-current@FreeBSD.ORG Subject: Re: CardBus Support (was: support for 3Com 3C575 network controller?) In-Reply-To: <19990221160939.A18594@rtfm.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 Sun, 21 Feb 1999, Nathan Dorfman wrote: # > I looked at PAO, but it doesn't appear to support the 3.X # > branch, which I'm running. If there's a PAO for 3.X, please # > let me know where it is (!). # # That's why I can't run PAO (and consequently no PCMCIA working on my # laptop at the moment). There's a PAO for 3.0, but I'm not sure if it's # for -stable or 3.0-release. You can only get it by cvsupping pao3 from # jaz.jp.freebsd.org. I'm running pccard just fine on a Dell Inspiron 7000 with 4.0. I had to tweak sio.c to increase a delay for the FIFO tests but other than that my modem (Zoom 56K LT DataFax) and 3CCE589ET network card are both humming along no problems. I'm going to commit the pccard.conf entries for them RSN. Between Doug and Terry I think I have enough to start playing with getting support for the network card that started this thread. :) -steve # -- # Nathan Dorfman The statements and opinions in my # Unix Admin @ Frontline Communications usenet posts are mine, not FCC's. # "The light at the end of the tunnel is the headlight of an approaching # train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 14:41:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id C19F210E36 for ; Sun, 21 Feb 1999 14:41:14 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id QAA14912 for ; Sun, 21 Feb 1999 16:41:13 -0600 (CST) Date: Sun, 21 Feb 1999 16:41:13 -0600 (CST) From: Steve Price To: current@freebsd.org Subject: /etc/pccard_ether troubles 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 All, Anyone have any objections (now that we have dhclient in the tree) to pointing pccard_ether at its new home? -steve Index: pccard_ether =================================================================== RCS file: /home/ncvs/src/etc/pccard_ether,v retrieving revision 1.10 diff -u -r1.10 pccard_ether --- pccard_ether 1999/02/10 18:08:16 1.10 +++ pccard_ether 1999/02/16 03:36:46 @@ -16,12 +16,12 @@ if [ "x$pccard_ifconfig" != "xNO" ] ; then if [ "x$pccard_ifconfig" = "xDHCP" ] ; then - if [ -f /usr/local/sbin/dhclient ] ; then + if [ -f /sbin/dhclient ] ; then if [ -s /var/run/dhclient.pid ] ; then kill `cat /var/run/dhclient.pid` rm /var/run/dhclient.pid fi - /usr/local/sbin/dhclient + /sbin/dhclient elif [ -f /usr/local/sbin/dhcpc ] ; then if [ -s /var/run/dhcpc.pid ] ; then kill `cat /var/run/dhcpc.pid` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 17: 7:13 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 2347D11C4F for ; Sun, 21 Feb 1999 17:07:10 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id TAA24692; Sun, 21 Feb 1999 19:07:09 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id TAA01964; Sun, 21 Feb 1999 19:07:09 -0600 (CST) Date: Sun, 21 Feb 1999 19:07:09 -0600 From: Alan Cox To: green@unixhelp.org Cc: current@freebsd.org Subject: Re: one SysV bug/fix, how many more Message-ID: <19990221190709.A1929@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your bug fix is in my queue. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 19:12: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 59AC71117A for ; Sun, 21 Feb 1999 19:11:58 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a19 ([207.164.233.81]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id XAA06659 for ; Sun, 21 Feb 1999 23:24:44 -0500 Message-ID: <003901be5e11$02748c00$0a00000a@a19.my.intranet> From: "RT" To: Subject: NFS Problems Date: Sun, 21 Feb 1999 22:11:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I update 3-Stable nearly weekly, and have been experiencing the same problem for quite a while now. NFS imports, on the client side appear to be losing data. When this occurs, I see .nfs78969 files on the server side. The program on the client side always freezes (top reports it's STAT as 'D'). This occurs regularly. I've tried nfsv3 and nfsv2. Read-only imports do not cause this freezing problem. The affected file often ends up being a size of 0. Are there some switches I should try? I assume (without testing) that 4-current would also show the same problems as 3-stable. Which is why I posted here. The server is 3-stable, clients are 3-stable. In fact, they share /usr, /bin, /sbin, /home and /var/db/pkg. Everything is read only except /home. I'd love to get this thing fixed if someone could point me in any direction at all... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 19:39:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.aa.net [206.125.75.16]) by hub.freebsd.org (Postfix) with ESMTP id 51A2D11B7B for ; Sun, 21 Feb 1999 19:39:45 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from imo.plaintalk.bellevue.wa.us (imo.plaintalk.bellevue.wa.us [192.168.1.7]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id TAA01916; Sun, 21 Feb 1999 19:39:43 -0800 (PST) Received: (from dennisg@localhost) by imo.plaintalk.bellevue.wa.us (8.8.7/8.8.7) id TAA07493; Sun, 21 Feb 1999 19:39:43 -0800 (PST) Message-Id: <199902220339.TAA07493@imo.plaintalk.bellevue.wa.us> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Dennis Glatting Date: Sun, 21 Feb 99 19:39:42 -0800 To: "Kenneth D. Merry" Subject: Re: Slow seq. write on Seagate ST36530N Cc: freebsd-current@FreeBSD.ORG Reply-To: dennis.glatting@plaintalk.bellevue.wa.us References: <199902210729.AAA17355@panzer.plutotech.com> X-No-Archive: : yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On the ST410800W I am getting, according to iozone: > > FWIW, several people have reported bad performance with that > drive when tagged queueing is enabled. Their firmware > revisions, however, were 71xx, not 45xx. Apparantly drives > with firmware that starts with 00 work okay. > I have contacted Seagate. Seagate's technical support staff says Seagate doesn't do firmware upgrades, rather I have to locate a vendor with disks having the revision level I seek and purchase a new disk. What is the source for firmware upgrades? -dpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 20: 4:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id A831912297 for ; Sun, 21 Feb 1999 20:04:10 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA22794; Sun, 21 Feb 1999 21:04:05 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902220404.VAA22794@panzer.plutotech.com> Subject: Re: Slow seq. write on Seagate ST36530N In-Reply-To: <199902220339.TAA07493@imo.plaintalk.bellevue.wa.us> from Dennis Glatting at "Feb 21, 1999 7:39:42 pm" To: dennis.glatting@plaintalk.bellevue.wa.us Date: Sun, 21 Feb 1999 21:04:05 -0700 (MST) Cc: freebsd-current@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 Dennis Glatting wrote... > > > > On the ST410800W I am getting, according to iozone: > > > > FWIW, several people have reported bad performance with that > > drive when tagged queueing is enabled. Their firmware > > revisions, however, were 71xx, not 45xx. Apparantly drives > > with firmware that starts with 00 work okay. > > > > I have contacted Seagate. Seagate's technical support staff > says Seagate doesn't do firmware upgrades, rather I have to > locate a vendor with disks having the revision level I seek and > purchase a new disk. That's pretty lame. > What is the source for firmware upgrades? I don't know, I've never upgraded the firmware on a Seagate disk. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 20: 9:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.aa.net [206.125.75.16]) by hub.freebsd.org (Postfix) with ESMTP id 04A5611A77 for ; Sun, 21 Feb 1999 20:09:00 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from imo.plaintalk.bellevue.wa.us (imo.plaintalk.bellevue.wa.us [192.168.1.7]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id UAA01954; Sun, 21 Feb 1999 20:08:59 -0800 (PST) Received: (from dennisg@localhost) by imo.plaintalk.bellevue.wa.us (8.8.7/8.8.7) id UAA07503; Sun, 21 Feb 1999 20:08:59 -0800 (PST) Message-Id: <199902220408.UAA07503@imo.plaintalk.bellevue.wa.us> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Dennis Glatting Date: Sun, 21 Feb 99 20:08:57 -0800 To: "Kenneth D. Merry" Subject: Re: Slow seq. write on Seagate ST36530N Cc: freebsd-current@FreeBSD.ORG Reply-To: dennis.glatting@plaintalk.bellevue.wa.us References: <199902220404.VAA22794@panzer.plutotech.com> X-No-Archive: : yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is the source for firmware upgrades? > > I don't know, I've never upgraded the firmware on a Seagate > disk. > I have. I upgraded 30 Seagate drives in a Sun SSA-110. The upgrade firmware came from Sun as one of their patches. This is the first time I have tried it at home, so to speak. :) -dpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 20:18:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from sally.nas.nasa.gov (sally.nas.nasa.gov [129.99.144.16]) by hub.freebsd.org (Postfix) with ESMTP id EE90411F67 for ; Sun, 21 Feb 1999 20:18:33 -0800 (PST) (envelope-from bross@sally.nas.nasa.gov) Received: (from bross@localhost) by sally.nas.nasa.gov (8.9.1a/NAS8.8.7n) id UAA18190; Sun, 21 Feb 1999 20:18:32 -0800 (PST) Date: Sun, 21 Feb 1999 20:18:32 -0800 (PST) From: "Wilson S. Ross" Message-Id: <199902220418.UAA18190@sally.nas.nasa.gov> To: current@FreeBSD.org Subject: 3.0->3.1 elf issues? Cc: bross@sally.nas.nasa.gov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was the 3.0-RELEASE I got ~Dec 30 aout kernel? 'file /kernel' gives /kernel: unknown pure executable but 'strings /kernel | grep -i elf' gives FreeBSD ELF among other stuff. So far, I just did 'make world' in /usr/src/, updated my config per GENERIC diff, and built the kernel. The warning to look at http://www.freebsd.org/~peter/elfday.html on make install has me wondering if 'make world' was the right thing to do in the 1st place, and wondering whether and how to update my bootblock. As far as my newcomer to freebsd upgrade experience, the info I wound up getting from people (not some 'how-to' easy-upgrade web page) was: - need to see req'd changes to /etc by inspecting cvsup output - need to update config file by looking at diff of GENERIC - need to figure how to do the diff since GENERIC was replaced Bill Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 20:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 9027F10FE3 for ; Sun, 21 Feb 1999 20:54:43 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id XAA19404 for current@freebsd.org; Sun, 21 Feb 1999 23:54:25 -0500 (EST) From: Mikhail Teterin Message-Id: <199902220454.XAA19404@kot.ne.mediaone.net> Subject: Re: sh(1) -- exec vs. fork In-Reply-To: <199902200258.AA26119@waltz.rahul.net> from Rahul Dhesi at "Feb 19, 1999 06:58:32 pm" To: current@freebsd.org Date: Sun, 21 Feb 1999 23:54:24 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Date: Fri, 19 Feb 99 11:43:59 EST => From: Mikhail Teterin => To: current@freebsd.org => Message-Id: <199902191644.LAA08791@misha.cisco.com> => Subject: sh(1) -- exec vs. fork => Reply-To: mi@aldan.algebra.com = => I just finished going through a couple of crontabs prepending the => command-lines with ``exec'', when it hit me. => => Can shell itself recognize, there will be no more commands and just => proceed to exec without forking? What would this break? =... = = =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 Feb 21 22:10:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles184.castles.com [208.214.165.184]) by hub.freebsd.org (Postfix) with ESMTP id 2494B10E01 for ; Sun, 21 Feb 1999 22:10:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01966; Sun, 21 Feb 1999 22:05:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902220605.WAA01966@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "RT" Cc: current@FreeBSD.ORG Subject: Re: NFS Problems In-reply-to: Your message of "Sun, 21 Feb 1999 22:11:13 EST." <003901be5e11$02748c00$0a00000a@a19.my.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Feb 1999 22:05:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I update 3-Stable nearly weekly, and have been experiencing the same problem > for quite a while now. NFS imports, on the client side appear to be losing > data. When this occurs, I see .nfs78969 files on the server side. These files exist because they've been deleted but not closed; this is probably just an artifact of the program being stuck. > The > program on the client side always freezes (top reports it's STAT as 'D'). You need to pass the 'l' switch to ps and look at the 'wchan' column to see where it's actually stuck. > Are there some switches I should try? I assume (without testing) that > 4-current would also show the same problems as 3-stable. Which is why I > posted here. There have actually been some changes in 4.0 which might affect this, if I understand correctly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Feb 21 23:18:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles184.castles.com [208.214.165.184]) by hub.freebsd.org (Postfix) with ESMTP id D4A9310F33 for ; Sun, 21 Feb 1999 23:18:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA02233; Sun, 21 Feb 1999 22:58:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902220658.WAA02233@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Roman V. Palagin" Cc: current@FreeBSD.ORG Subject: Re: Problems with nfsstat and dynamic OID In-reply-to: Your message of "Sat, 20 Feb 1999 22:32:42 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Feb 1999 22:58:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I fixed this a while back to use sysctlbyname, as it should have been done. Bruce subsequently backed it out (bad idea, IMO). You should file a PR or otherwise petition bde@freebsd.org to un-revert his change. > Hello! Five minutes ago I type 'nfsstat' and got: > > nfsstat: sysctl: No such file or directory > > I take a look at the source and that's what I found: > Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS, > but name[1] has a value of vfc.vfc_typenum, returned by getvfsbyname(3). > And it is very bad, 'cause vfc_typenum contains fs type number assigned > by kernel, not sysctl OID! As we can see in nfs_vfsops.c NFS sysctl node > declared with OID_AUTO (on my system it becomes 119, not 4 as returned by > getvfsbyname). > > Operating system is 4.0-CURRENT as of 1999/02/20. What you think? > > p.s. Sorry for bad English :( > > ------------------------------------------------------------------------- > Roman V. Palagin | RVP1-6BONE | Just because you're paranoid > Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Feb 21 23:33:41 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 7E79411013 for ; Sun, 21 Feb 1999 23:33:36 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA20392 for current@FreeBSD.ORG; Mon, 22 Feb 1999 08:33:34 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 5BAEA883A; Mon, 22 Feb 1999 08:19:45 +0100 (CET) Date: Mon, 22 Feb 1999 08:19:45 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: 3.0->3.1 elf issues? Message-ID: <19990222081945.A24840@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199902220418.UAA18190@sally.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199902220418.UAA18190@sally.nas.nasa.gov>; from Wilson S. Ross on Sun, Feb 21, 1999 at 08:18:32PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5084 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wilson S. Ross: > Was the 3.0-RELEASE I got ~Dec 30 aout kernel? 'file /kernel' gives Yes, the default kernel format was changed to ELF on Jan., 6th. 3.0-RELEASE builds a.out kernel but you can generated ELF ones if you want. > - need to see req'd changes to /etc by inspecting cvsup output Or you could use "mergemaster" for that (in ports). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 21 23:52:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 58BEE10F33 for ; Sun, 21 Feb 1999 23:52:33 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA01270; Mon, 22 Feb 1999 18:52:27 +1100 Date: Mon, 22 Feb 1999 18:52:27 +1100 From: Bruce Evans Message-Id: <199902220752.SAA01270@godzilla.zeta.org.au> To: mike@smith.net.au, romanp@wuppy.rcs.ru Subject: Re: Problems with nfsstat and dynamic OID Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I fixed this a while back to use sysctlbyname, as it should have been >done. Bruce subsequently backed it out (bad idea, IMO). You only worked around the previous breakage of vfs sysctls for the statically configured case. The dynamically configured case was more fundamentally broken (sysctls were not wired at all). Other applications that use vfs sysctls, e.g., mountd(8), remained broken in all cases. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 1: 2:44 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 0DB2510E84 for ; Mon, 22 Feb 1999 01:02:00 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. ([212.42.68.187]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id LAA19276 for ; Mon, 22 Feb 1999 11:02:08 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id LAA08578 for ; Mon, 22 Feb 1999 11:01:55 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36D11CBD.157C9D56@altavista.net> Date: Mon, 22 Feb 1999 11:00:45 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Additions to pccard.conf Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is my additions to pccard.conf (Eiger 33.6 modem and AR-P500 ethernet cards). It would be nice to see it in pccard.conf. #AR-P500 ethernet card card "IC-CARD" "IC-CARD"         config  0x20  "ed0" 15         insert  echo AR-P500 inserted         insert  /etc/pccard_ether ed0         insert  /sbin/ifconfig ed0 inet 192.168.1.100         insert  /sbin/route add 0 192.168.1.50         remove  echo AR-P500 removed         remove  /sbin/route delete 0 192.168.1.50         remove  ifconfig ed0 delete #Eiger 33.6 modem card "AT&T" "V34+ Fax Modem"         config 0x23 "sio1" 10         insert echo Eiger 33.6K modem inserted         remove echo Eiger 33.6K modem removed Sincerely, Maxim Sobolev   To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 1:33:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from antioche.lip6.fr (antioche.lip6.fr [132.227.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 8AD3211742 for ; Mon, 22 Feb 1999 01:31:32 -0800 (PST) (envelope-from bouyer@antioche.lip6.fr) Received: from antifer.ipv6.lip6.fr (antifer.ipv6.lip6.fr [132.227.72.132]) by antioche.lip6.fr (8.8.8/8.8.5) with ESMTP id KAA00289 for ; Mon, 22 Feb 1999 10:31:30 +0100 (MET) Received: (bouyer@localhost) by antifer.ipv6.lip6.fr (8.8.8/8.6.4) id KAA07547; Mon, 22 Feb 1999 10:15:49 +0100 (MET) Message-ID: <19990222101549.39279@antioche.lip6.fr> Date: Mon, 22 Feb 1999 10:15:49 +0100 From: Manuel Bouyer To: freebsd-current@FreeBSD.ORG Subject: Promise IDE board docs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I initially intended to ask this to John Dyson, but I don't know how to reach him. Maybe someone else on this list can anserw :) I'm looking for documentations about the promise PCI IDE controller, to add support for this in NetBSD. Does someone know how John got the informations for the FreeBSD support ? I sent a mail to the support address listed on their www page, but got nothing back yet ... -- Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 3:55: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by hub.freebsd.org (Postfix) with ESMTP id 7B37610E85 for ; Mon, 22 Feb 1999 03:54:52 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id FAA19957; Mon, 22 Feb 1999 05:54:45 -0600 (CST) Received: from sji-ca44-119.ix.netcom.com(209.111.212.247) by dfw-ix14.ix.netcom.com via smap (V1.3) id rma019953; Mon Feb 22 05:54:24 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id DAA25715; Mon, 22 Feb 1999 03:54:20 -0800 (PST) Date: Mon, 22 Feb 1999 03:54:20 -0800 (PST) Message-Id: <199902221154.DAA25715@silvia.hip.berkeley.edu> To: blokey@indigo.ie Cc: current@freebsd.org In-reply-to: <19990221195810.A32005@smooch> (message from Smelly Pooh on Sun, 21 Feb 1999 19:58:10 +0000) Subject: Re: ports From: asami@freebsd.org (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Send messages like this to -ports next time, please....) * I've noticed that as I'm constantly syncing my /usr/ports directory and * upgrading programs, the old packages stay there. If I pkg_delete them and * there's an unchanged file that exists in both the update and the original then * tat gets deleted too. Any way of cleanly removing old packages? Incidentally pkg_delete the old one before adding the new one? ;) * are the ports trees for all the FreeBSD releases the same one? I mean if I'm * running 2.2.x do I still get all the latest ports? ports-current (the tree you get if you cvsup ports now) only supports 3.1-stable and 4.0-current. If you're running 2.2.x, you are on your own. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 5: 1:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id BE4E810F22 for ; Mon, 22 Feb 1999 05:01:43 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id VAA25830 for ; Mon, 22 Feb 1999 21:01:39 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id VAA20628 for freebsd-current@freebsd.org; Mon, 22 Feb 1999 21:01:37 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902221301.VAA20628@b1.hkstar.com> Subject: how to setup tv tuner card (bt878) To: freebsd-current@freebsd.org Date: Mon, 22 Feb 1999 21:01:36 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I am newbie to play with the tv tuner card (bt848). Can anyone show me the steps. I had tried to config my kernel to include device brktr0 with no success. The error was bt848_i2c.* file missing. Can anyone teach me. thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 5: 4: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id BD9D110F1F for ; Mon, 22 Feb 1999 05:04:03 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id FAA15939; Mon, 22 Feb 1999 05:02:33 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id FAA10351; Mon, 22 Feb 1999 05:02:32 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id FAA28797; Mon, 22 Feb 1999 05:02:31 -0800 (PST) From: Don Lewis Message-Id: <199902221302.FAA28797@salsa.gv.tsc.tdk.com> Date: Mon, 22 Feb 1999 05:02:31 -0800 In-Reply-To: "Kenneth D. Merry" "Re: Slow seq. write on Seagate ST36530N" (Feb 19, 2:15pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Kenneth D. Merry" , paulz@trantor.xs4all.nl (Paul van der Zwan) Subject: Re: Slow seq. write on Seagate ST36530N Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Feb 19, 2:15pm, "Kenneth D. Merry" wrote: } Subject: Re: Slow seq. write on Seagate ST36530N } } The Write Cache Enable (WCE) bit is in mode page 8. To check it: } } camcontrol modepage -n da -u 1 -v -m 8 } } To edit the mode page: } } camcontrol modepage -n da -u 1 -v -m 8 -e To make this change permanent, you need to do camcontrol modepage -n da -u 1 -v -m 8 -e -P 3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 5:28:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from daytona.hkstar.com (daytona.hkstar.com [202.82.3.25]) by hub.freebsd.org (Postfix) with ESMTP id 0BF3010E64 for ; Mon, 22 Feb 1999 05:28:44 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by daytona.hkstar.com (8.9.1/8.9.1) with ESMTP id VAA09527 for ; Mon, 22 Feb 1999 21:28:42 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id VAA22057 for freebsd-current@freebsd.org; Mon, 22 Feb 1999 21:28:37 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902221328.VAA22057@b1.hkstar.com> Subject: how to setup tv tuner card (bt878) To: freebsd-current@freebsd.org Date: Mon, 22 Feb 1999 21:28:37 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I encounctered an error when tried to config my kernel to include the tv tuner card (bt878). The error was as followings. Any idea ? My source tree is src-cur.3756. Thanks. clarence =======Error ======= bkern/umoddi3.c swapkernel.c ioconf.c param.c vnode_if.c config.c ../../pci/brooktree848.c:393: smbus_if.h: No such file or directory ../../pci/brooktree848.c:394: iicbus_if.h: No such file or directory ../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory ../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop. =======Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 6:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 7B53B10EC7 for ; Mon, 22 Feb 1999 06:17:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id OAA03507; Mon, 22 Feb 1999 14:17:51 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA02749; Mon, 22 Feb 1999 14:10:00 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199902221410.OAA02749@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: current@freebsd.org Subject: Re: Additions to pccard.conf In-reply-to: Your message of "Mon, 22 Feb 1999 11:00:45 +0200." <36D11CBD.157C9D56@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Feb 1999 14:10:00 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here is my additions to pccard.conf (Eiger 33.6 modem and AR-P500 > ethernet cards). It would be nice to see it in pccard.conf. [.....] Done. send-pr is probably a better way to do this though ;-I > Sincerely, > = > Maxim Sobolev -- = Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 6:47:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id E0EFF11035 for ; Mon, 22 Feb 1999 06:47:09 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id GAA24200; Mon, 22 Feb 1999 06:46:15 -0800 (PST) Message-ID: <19990222064614.D14395@best.com> Date: Mon, 22 Feb 1999 06:46:15 -0800 From: "Jan B. Koum " To: current@freebsd.org, Matthew Dillon , dyson@iquest.net Cc: "Michael T. Stolarchuk" Subject: [mts@off.to: freebsd low kernel expert...] Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZoaI/ZTpAVc4A5k6" X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ZoaI/ZTpAVc4A5k6 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=muttY14395 So.. can anyone help? These folks are a vendor (www.nfr.net) who are making a port to a FreeBSD platform. Thanks, -- Yan --ZoaI/ZTpAVc4A5k6 Content-Type: message/rfc822 Content-Description: Forwarded message from "Michael T. Stolarchuk" Content-Disposition: attachment; filename=muttt14395 Received: from proxy2.ba.best.com (root@proxy2.ba.best.com [206.184.139.13]) by shell6.ba.best.com (8.9.2/8.9.2/best.sh) with ESMTP id GAA20342 for ; Mon, 22 Feb 1999 06:20:48 -0800 (PST) Received: from off.to ([198.87.148.130]) by proxy2.ba.best.com (8.9.3/8.9.2/best.in) with ESMTP id GAA12832 for ; Mon, 22 Feb 1999 06:20:29 -0800 (PST) Received: from off.to (localhost [127.0.0.1]) by off.to (8.9.1/8.9.1) with ESMTP id JAA23471; Mon, 22 Feb 1999 09:20:24 -0500 (EST) Message-Id: <199902221420.JAA23471@off.to> To: "Jan B. Koum " cc: mts@off.to Subject: freebsd low kernel expert... In-reply-to: Your message of "Sun, 21 Feb 1999 18:19:11 PST." <19990221181911.A23656@best.com> Date: Mon, 22 Feb 1999 09:20:24 -0500 From: "Michael T. Stolarchuk" i'm looking for someone who can answer some questions about interrupt processing code in freebsd 3.0... not the stuff after the SMP processors get to C code, but the glue between the hardware and the C code... i want to find the `pc' of the interrupting processor... i can find the pc of the other processors, but don't yet know how to get the previous-pc for the processor which fielded the interrupt. mts. --ZoaI/ZTpAVc4A5k6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 8:43: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from lenka.ph.ipex.cz (lenka.ph.ipex.cz [62.168.16.2]) by hub.freebsd.org (Postfix) with ESMTP id D734310F94 for ; Mon, 22 Feb 1999 08:42:44 -0800 (PST) (envelope-from kan@sti.cz) Received: from linux.sti.cz (linux.sti.cz [62.168.16.129]) by lenka.ph.ipex.cz (8.8.5/IPEX) with ESMTP id RAA25595 for ; Mon, 22 Feb 1999 17:42:41 +0100 Received: from sti.cz (kan.sti.cz [192.168.0.18]) by linux.sti.cz (8.8.7/8.7.3) with ESMTP id SAA27343 for ; Mon, 22 Feb 1999 18:49:15 +0100 Message-ID: <36D1898A.6D9C7B44@sti.cz> Date: Mon, 22 Feb 1999 17:44:58 +0100 From: "Alexander N. Kabaev" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Filesystem deadlock Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE as of today) to lookup. Shortly after this script is started, all disk activity stops and any attempt to create new process causes system to freese. While in DDB, ps command shows, that all ten fgrep processes are sleeping on inode, all xargs are in waitpid and all sh processes are in wait. Unfortunately, I cannot run -g kernel on my box at this time, so amount of useful information I can provide is pretty much limited :( #!/bin/sh for j in 1 2 3 4 5 6 7 8 9 10; do echo -n $i $j nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka; done' \ >/dev/null 2>&1 & echo done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 10: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 3BC2D10E5F for ; Mon, 22 Feb 1999 09:59:58 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id MAA13359 for ; Mon, 22 Feb 1999 12:59:56 -0500 (EST) Date: Mon, 22 Feb 1999 12:59:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@freebsd.org Subject: buildworld problems 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 been unable to buildworld for a day or so now, much to my frustration. I've tried recvsuping my /home/ncvs, as well as rechecking out, etc. I get the following: cd /usr/src/lib/libskey; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/src /tmp/usr/bin/make -B install cc -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werr or -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o sk eyaccess.o cc1: warnings being treated as errors /usr/obj/usr/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:146: warning: `__maskrune' defined but not used /usr/obj/usr/src/tmp/usr/include/ctype.h:160: warning: `__toupper' defined but n ot used /usr/obj/usr/src/tmp/usr/include/ctype.h:167: warning: `__tolower' defined but n ot used The -Werror seems like a bad idea. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 10:22:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (33-sweet.camalott.com [208.239.153.33]) by hub.freebsd.org (Postfix) with ESMTP id 4F33311151 for ; Mon, 22 Feb 1999 10:22:10 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.2/8.9.1) id MAA01651; Mon, 22 Feb 1999 12:21:21 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: "RT" , current@FreeBSD.ORG Subject: Re: NFS Problems References: <199902220605.WAA01966@dingo.cdrom.com> From: Joel Ray Holveck Date: 22 Feb 1999 12:21:20 -0600 In-Reply-To: Mike Smith's message of "Sun, 21 Feb 1999 22:05:51 -0800" Message-ID: <86iucucna7.fsf@detlev.UUCP> Lines: 16 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The program on the client side always freezes (top reports it's >> STAT as 'D'). > You need to pass the 'l' switch to ps and look at the 'wchan' column to > see where it's actually stuck. This reminds me; do we have a utility to reference wmesg strings back to the code that sets them, a la TAGS? Would this be useful? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 10:41:29 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 8E1741191E for ; Mon, 22 Feb 1999 10:41:17 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA62886; Mon, 22 Feb 1999 18:22:02 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902221722.SAA62886@freebsd.dk> Subject: Re: Promise IDE board docs In-Reply-To: <19990222101549.39279@antioche.lip6.fr> from Manuel Bouyer at "Feb 22, 1999 10:15:49 am" To: bouyer@antioche.lip6.fr (Manuel Bouyer) Date: Mon, 22 Feb 1999 18:22:02 +0100 (CET) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Manuel Bouyer wrote: > Hi, > I initially intended to ask this to John Dyson, but I don't know how > to reach him. Maybe someone else on this list can anserw :) > I'm looking for documentations about the promise PCI IDE controller, > to add support for this in NetBSD. Does someone know how John got the > informations for the FreeBSD support ? > I sent a mail to the support address listed on their www page, but > got nothing back yet ... You can the docs from their web/ftp site, I did (long ago), bear in mind that they are pretty limitted, and only provides rudimentary information on the chips. If you have questions, I might be able to answer, having just written the support for our new ata/atapi system.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 10:59:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id A82E911B73 for ; Mon, 22 Feb 1999 10:59:11 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id TAA18368 for ; Mon, 22 Feb 1999 19:59:10 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma018366; Mon, 22 Feb 99 19:59:10 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id TAA23495 for ; Mon, 22 Feb 1999 19:59:10 +0100 (MET) Received: (qmail 94593 invoked by uid 666); 22 Feb 1999 18:59:32 -0000 Date: Mon, 22 Feb 1999 19:59:32 +0100 From: Jos Backus To: freebsd-current@freebsd.org Subject: panic: zone: entry not free Message-ID: <19990222195932.A94515@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This occurs almost immediately after copying a file to an msdos fs. I can provide more info if that is deemed useful. FreeBSD jos.mp-c.com 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Sat Feb 20 19:31:56 CET 1999 jos@jos.mp-c.com:/usr/src/sys/compile/JOS i386 Thanks, -- 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 Mon Feb 22 11:10:12 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 7DF9811ED0 for ; Mon, 22 Feb 1999 11:10:02 -0800 (PST) (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 OAA08201; Mon, 22 Feb 1999 14:09:57 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id OAA17947; Mon, 22 Feb 1999 14:09:52 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Feb 1999 14:09:51 -0500 (EST) To: Søren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise IDE board docs In-Reply-To: <199902221722.SAA62886@freebsd.dk> References: <19990222101549.39279@antioche.lip6.fr> <199902221722.SAA62886@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14033.43264.683731.347347@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S=F8ren Schmidt writes: >=20 > If you have questions, I might be able to answer, having just writte= n > the support for our new ata/atapi system.... >=20 Is this new ata/atapi system the rumored rewrite of the existing IDE (i386/isa/wd.c, /pci/ide_pci.c) driver? How close are you to completion? I have a slightly off-track question -- should I be able to throw 3 of these boards in a modern (440bx based) motherboard, and run 6 ATA disks (1 per controller, 2 controllers per card) & expect things to 'just work' or should I expect problems? LINT doesn't list example configs beyond 1 Promise in addition to the on-board controllers, so I'm wondering if anybody's ever tested a config like this...? Thanks, Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Mon Feb 22 11:29:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.arc.nasa.gov (gaia.arc.nasa.gov [128.102.141.102]) by hub.freebsd.org (Postfix) with ESMTP id 6E85011BF6 for ; Mon, 22 Feb 1999 11:29:19 -0800 (PST) (envelope-from dsullivan@gaia.arc.nasa.gov) Date: Mon, 22 Feb 1999 11:16:33 -0800 (PST) From: Don Sullivan X-Sender: sullivan@alpine.arc.nasa.gov To: current@freebsd.org Subject: ELF interpreter /compat/linux/lib/ld-linux.so.1 not found 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 RSI's IDL/ENVI product's license manager (lmgrd) previously (2.2.8) ran just fine. (linux emulation) Now that I've upgraded to 3.1, it exits with an abort trap, and the above message... Any thoughts/suggestions would be REALLY welcome. Thanks in advance, Don P.S. the library indicated (/compat/linux/lib/ld-linux.so.1) most definately IS there, new Globetrotter lmgrd acts identically, the balance of the (linux) distribution, i.e. IDL and ENVI run just fine, albeit in demo mode. ----------------------------------------------- Don Sullivan NASA Ames Research Center MS 242-4 Moffett Field, CA 94035-1000 Voice: 650 604 0526 Fax: 650 604 4680 email: dsullivan@gaia.arc.nasa.gov ----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 11:30: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 096BE11F0A for ; Mon, 22 Feb 1999 11:30:02 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA13875 for ; Mon, 22 Feb 1999 14:30:01 -0500 (EST) Date: Mon, 22 Feb 1999 14:30:00 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@freebsd.org Subject: softupdates crash 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 kernel code cvsup'd this morning, I believe. FreeBSD sleipnir.watson.org 4.0-CURRENT FreeBSD 4.0-CURRENT #20: Mon Feb 22 11:53:53 EST 1999 robert@sleipnir.watson.org:/usr/src/sys/compile/SLEIPNIR_AUDIT i386 panic(f01f13a7) at Debugger+0x37 worklist_remove(f0bd56a0) at worklist_remove+0x2a free_diradd(f0bd56a0) at free_dir+0x26 handle_written_filepage(f0d171c0, f19aea40, f19aea40, f0a4fc00, f19aea40) at handle_written_filepage+0x59 softdep_disk_write_complete(f19aea40) at softdep_disk_write_complete+0x8d biodone(f19aea40,f0a4fd60,400,3,2) at biodone+0x9b wdintr(0,0,2f,2f,efbfcf84) at wdintr+0x5a2 Xresume14() at Xresume14+0x2b --- interrupt, eip = 0x807af68, esp = 0xf4e77ff0, ebp = 0xefbfcb78 --- Sorry for any typos, this was rapidly copied down from the console of a machine w/o a serial console :-(. Was building world at the time, as well as running X. buildworld was niced. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 11:50: 4 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 380EF1107E for ; Mon, 22 Feb 1999 11:49:51 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA63198; Mon, 22 Feb 1999 20:49:39 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902221949.UAA63198@freebsd.dk> Subject: Re: Promise IDE board docs In-Reply-To: <14033.43264.683731.347347@grasshopper.cs.duke.edu> from Andrew Gallatin at "Feb 22, 1999 2: 9:51 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 22 Feb 1999 20:49:39 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Andrew Gallatin wrote: > > Søren Schmidt writes: > > > > If you have questions, I might be able to answer, having just written > > the support for our new ata/atapi system.... > > > > Is this new ata/atapi system the rumored rewrite of the existing IDE > (i386/isa/wd.c, /pci/ide_pci.c) driver? How close are you to > completion? Yes. I have ATA disks running, and I'm close to having the ATAPI part done also. So far things are looking very good, performance is up one notch on all the ATA HW I have in my lab. I have no projected date for this yet, but progress is speeding up.. > I have a slightly off-track question -- should I be able to throw 3 of > these boards in a modern (440bx based) motherboard, and run 6 ATA > disks (1 per controller, 2 controllers per card) & expect things to > 'just work' or should I expect problems? LINT doesn't list example > configs beyond 1 Promise in addition to the on-board controllers, so > I'm wondering if anybody's ever tested a config like this...? It "should" work, but the promise support in the old system is, well, hacky at best. I'm not sure if Promise supports more than one card at a time, but from looking at the chip specs, it should work just fine, and if the hardware works, at least the new driver will support it. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 12:15: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id BFEE510FBB for ; Mon, 22 Feb 1999 12:15:02 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id PAA14248 for ; Mon, 22 Feb 1999 15:15:01 -0500 (EST) Date: Mon, 22 Feb 1999 15:15:01 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: current@freebsd.org Subject: Re: softupdates crash (doh) 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 Looks like it may actually have been triggered by a bug in my kernel auditing code, which turned out to be doing stuff when I didn't think it should have. Sorry about that :-). On Mon, 22 Feb 1999, Robert Watson wrote: > kernel code cvsup'd this morning, I believe. > FreeBSD sleipnir.watson.org 4.0-CURRENT FreeBSD 4.0-CURRENT #20: Mon Feb > 22 11:53:53 EST 1999 > robert@sleipnir.watson.org:/usr/src/sys/compile/SLEIPNIR_AUDIT i386 > > panic(f01f13a7) at Debugger+0x37 > worklist_remove(f0bd56a0) at worklist_remove+0x2a > free_diradd(f0bd56a0) at free_dir+0x26 > handle_written_filepage(f0d171c0, f19aea40, f19aea40, f0a4fc00, f19aea40) > at handle_written_filepage+0x59 > softdep_disk_write_complete(f19aea40) at > softdep_disk_write_complete+0x8d > biodone(f19aea40,f0a4fd60,400,3,2) at biodone+0x9b > wdintr(0,0,2f,2f,efbfcf84) at wdintr+0x5a2 > Xresume14() at Xresume14+0x2b > --- interrupt, eip = 0x807af68, esp = 0xf4e77ff0, ebp = 0xefbfcb78 --- > > Sorry for any typos, this was rapidly copied down from the console of a > machine w/o a serial console :-(. > > Was building world at the time, as well as running X. buildworld was > niced. > > > Robert N Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C > > Carnegie Mellon University http://www.cmu.edu/ > TIS Labs at Network Associates, Inc. http://www.tis.com/ > SafePort Network Services http://www.safeport.com/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 12:49:11 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 B863811981 for ; Mon, 22 Feb 1999 12:49:05 -0800 (PST) (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 PAA10351; Mon, 22 Feb 1999 15:49:04 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id PAA18284; Mon, 22 Feb 1999 15:48:58 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Feb 1999 15:48:58 -0500 (EST) To: Søren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise IDE board docs In-Reply-To: <199902221949.UAA63198@freebsd.dk> References: <14033.43264.683731.347347@grasshopper.cs.duke.edu> <199902221949.UAA63198@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14033.49662.962807.144887@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S=F8ren Schmidt writes: > > Is this new ata/atapi system the rumored rewrite of the existing I= DE > > (i386/isa/wd.c, /pci/ide_pci.c) driver? How close are you to > > completion? >=20 > Yes. I have ATA disks running, and I'm close to having the ATAPI > part done also. So far things are looking very good, performance > is up one notch on all the ATA HW I have in my lab. > I have no projected date for this yet, but progress is speeding up..= That's really good news. I'm looking forward to using the IDE interfaces in my alphas ;-) Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Mon Feb 22 13:32:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mescalero.asd1.rl.ac.uk (mescalero.asd1.rl.ac.uk [130.246.170.11]) by hub.freebsd.org (Postfix) with ESMTP id E8E4610FD8 for ; Mon, 22 Feb 1999 13:32:12 -0800 (PST) (envelope-from tmb@rcru.rl.ac.uk) Received: from rcru.rl.ac.uk (localhost [127.0.0.1]) by mescalero.asd1.rl.ac.uk (8.9.2/8.9.1) with ESMTP id VAA14921; Mon, 22 Feb 1999 21:31:59 GMT (envelope-from tmb@rcru.rl.ac.uk) Message-Id: <199902222131.VAA14921@mescalero.asd1.rl.ac.uk> To: Don Sullivan Cc: current@freebsd.org Subject: Re: ELF interpreter /compat/linux/lib/ld-linux.so.1 not found In-reply-to: Your message of "Mon, 22 Feb 1999 11:16:33 PST." Date: Mon, 22 Feb 1999 21:31:59 +0000 From: Mark Blackman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you'll need to upgrade to a slightly newer than 3.1-RELEASE version of the kernel and recompile. Anything newer than about Feb. 19 should do. See freebsd-emulation lists last week for details. Mark Blackman In message , Don S ullivan writes: > >RSI's IDL/ENVI product's license manager (lmgrd) previously (2.2.8) >ran just fine. (linux emulation) Now that I've upgraded to 3.1, it >exits with an abort trap, and the above message... > >Any thoughts/suggestions would be REALLY welcome. > >Thanks in advance, >Don > >P.S. the library indicated (/compat/linux/lib/ld-linux.so.1) most >definately IS there, new Globetrotter lmgrd acts identically, the >balance of the (linux) distribution, i.e. IDL and ENVI run just >fine, albeit in demo mode. >----------------------------------------------- > Don Sullivan > NASA Ames Research Center > MS 242-4 > Moffett Field, CA 94035-1000 > Voice: 650 604 0526 > Fax: 650 604 4680 > email: dsullivan@gaia.arc.nasa.gov >----------------------------------------------- > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 13:37:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 6700111012 for ; Mon, 22 Feb 1999 13:37:44 -0800 (PST) (envelope-from lyndon@execmail.ca) Received: from execmail.ca (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.1/8.9.1/Execmail 2.1) with ESMTP id OAA20524 for ; Mon, 22 Feb 1999 14:37:38 -0700 Message-Id: <199902222137.OAA20524@rembrandt.esys.ca> Date: Mon, 22 Feb 1999 14:37:32 -0700 From: Lyndon Nerenberg Subject: PCI-1220 doc's found To: freebsd-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 I finally managed to extract a copy of the PCI-1220 chip documentation from TI. If anyone needs a copy of this, e-mail me and I'll forward it along. (Beware, it's a 3.5 MB PDF.) (If I get the okay from TI I'll also put it up for FTP someplace.) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 14: 2:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id 23A1B10E91; Mon, 22 Feb 1999 14:02:53 -0800 (PST) (envelope-from freebsd@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10F3RD-000I1oC; Mon, 22 Feb 1999 17:02:51 -0500 (EST) Message-Id: From: freebsd@tomqnx.com (Tom Torrance) Subject: Re: ports In-Reply-To: <199902221154.DAA25715@silvia.hip.berkeley.edu> from Satoshi Asami at "Feb 22, 1999 3:54:20 am" To: asami@FreeBSD.ORG (Satoshi Asami) Date: Mon, 22 Feb 1999 17:02:51 -0500 (EST) Cc: blokey@indigo.ie, current@FreeBSD.ORG, ports@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 Content-Length: 3653 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attaching my description of a similar problem/solution as it directly addresses the problem and may be of interest to many people. See below... > (Send messages like this to -ports next time, please....) > > * I've noticed that as I'm constantly syncing my /usr/ports directory and > * upgrading programs, the old packages stay there. If I pkg_delete them and > * there's an unchanged file that exists in both the update and the original then > * tat gets deleted too. Any way of cleanly removing old packages? Incidentally > > pkg_delete the old one before adding the new one? ;) > > * are the ports trees for all the FreeBSD releases the same one? I mean if I'm > * running 2.2.x do I still get all the latest ports? > > ports-current (the tree you get if you cvsup ports now) only supports > 3.1-stable and 4.0-current. If you're running 2.2.x, you are on your > own. > > Satoshi Here it comes... > On Mon, 22 Feb 1999, Tom Torrance at home wrote: > > > This port fails when applying patches for FreeBSD. > > If you're monstrously annoyed at it merely being broken, then I guess I > can understand what you wrote ... but if you wanted help, you have to > give enough info, so that someone else can figure out why it broke for > you. > > How about including the actual error listing, the date on the perl5 > port's Makefile (so we can tell the age of it) the date on your > /usr/share/mk/bsd.port.mk file, and the FreeBSD version you're running. > At the time I was running a cvsup-15.4 client, as far as I remember (since updated to cvsup-16.0) under 2.2-stable. The system software was updated last as of Feb 13, 1999. The ports tree was as up-to-date as cvsup could make it. I got the info to fix it from John Polstra a year or two ago, in reference to a source tree problem I was having at that time, but had since forgotten about! (blush) The problem was old patch files that were not deleted by cvsup, which will not delete anything that it did not either write, or verify was there *and valid, expressly* on an update. It otherwise leaves trash lying around. The first thing one has to do with cvsup is verify/register the files one has by running it against the exact same release as the files one has before running a cvsup update to get the later files. Otherwise, as I understand it, any files deleted from the master tree between the time your version of the ports tree was created (usually when the cdrom distribution is created) and the first time you do a cvsup run to update it, will NEVER be detected and deleted by cvsup. An example, if you are running current or RELENG_3 and happen to have inserted the required files or symlinks to activate the softupdates code, cvsup will not delete them. Verification/registration is AFAIK not possible with ports, as there are not any separate cvs ports releases, as there is with the source tree. I got around the problem by: 1) deleting /usr/sup/ports* 2) deleting /usr/ports/* 3) cvsuping the entire ports tree. (ouch) This got rid of the invalid patch-aa file for perl5 as well as a number of other invalid files that were in my tree, which was quite old. All my ports are now running fine, and will continue to do so (hopefully). Anyone that wants to cvsup the ports tree on a system would be well advised to "rm /usr/ports/*" before the *first* time they run cvsup. This is particularly important if they have jost installed an old release. The first run will then automatically be a verification/registration run. Thanks for your reply. It is much appreciated - I really did not give any info, and I was frustrated. Forgive me. Cheers, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 14: 7:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 15F0510F88 for ; Mon, 22 Feb 1999 14:07:30 -0800 (PST) (envelope-from lyndon@execmail.ca) Received: from execmail.ca (zappa.esys.ca [198.161.92.28]) by rembrandt.esys.ca (2.1/8.9.1/Execmail 2.1) with ESMTP id PAA20749 for ; Mon, 22 Feb 1999 15:07:27 -0700 Message-Id: <199902222207.PAA20749@rembrandt.esys.ca> Date: Mon, 22 Feb 1999 15:07:21 -0700 From: Lyndon Nerenberg Subject: PCI-1220 doc URL To: freebsd-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 It's online now at: ftp://ftp.execmail.ca/pub/staff/lyndon/misc/PCI1220.pdf --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 14:26: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2B73010E91 for ; Mon, 22 Feb 1999 14:26:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00897; Mon, 22 Feb 1999 14:20:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902222220.OAA00897@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck Cc: Mike Smith , "RT" , current@FreeBSD.ORG Subject: Re: NFS Problems In-reply-to: Your message of "22 Feb 1999 12:21:20 CST." <86iucucna7.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Feb 1999 14:20:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> The program on the client side always freezes (top reports it's > >> STAT as 'D'). > > You need to pass the 'l' switch to ps and look at the 'wchan' column to > > see where it's actually stuck. > > This reminds me; do we have a utility to reference wmesg strings back > to the code that sets them, a la TAGS? Would this be useful? No, and yes respectively. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Feb 22 14:31:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 5E79110FEC for ; Mon, 22 Feb 1999 14:31:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00943; Mon, 22 Feb 1999 14:26:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902222226.OAA00943@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Sullivan Cc: current@freebsd.org Subject: Re: ELF interpreter /compat/linux/lib/ld-linux.so.1 not found In-reply-to: Your message of "Mon, 22 Feb 1999 11:16:33 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Feb 1999 14:26:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bug in 3.1-release, upgrade to a 3.1-stable kernel. > RSI's IDL/ENVI product's license manager (lmgrd) previously (2.2.8) > ran just fine. (linux emulation) Now that I've upgraded to 3.1, it > exits with an abort trap, and the above message... > > Any thoughts/suggestions would be REALLY welcome. > > Thanks in advance, > Don > > P.S. the library indicated (/compat/linux/lib/ld-linux.so.1) most > definately IS there, new Globetrotter lmgrd acts identically, the > balance of the (linux) distribution, i.e. IDL and ENVI run just > fine, albeit in demo mode. > ----------------------------------------------- > Don Sullivan > NASA Ames Research Center > MS 242-4 > Moffett Field, CA 94035-1000 > Voice: 650 604 0526 > Fax: 650 604 4680 > email: dsullivan@gaia.arc.nasa.gov > ----------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Feb 22 14:51: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from phluffy.fks.bt (net25-cust199.pdx.wantweb.net [24.236.25.199]) by hub.freebsd.org (Postfix) with ESMTP id 348D911576 for ; Mon, 22 Feb 1999 14:50:54 -0800 (PST) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id OAA08922 for ; Mon, 22 Feb 1999 14:50:46 -0800 (PST) (envelope-from myke@ees.com) Date: Mon, 22 Feb 1999 14:50:46 -0800 (PST) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: current@freebsd.org Subject: IDE controller detected in linux but not FreeBSD? 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 Last summer I encountered a P133 machine where linux detected the IDE controller, but FreeBSD did not. I wrote it off as a fluke. I've now come into possession of a stack of DECpc 433dxLP machines. These are 486/33 machines in a slimline desktop case. They have integrated IDE controllers, and I'm not able to find any discrete chip for this function. Linux sees the controller fine, but FreeBSD doesn't see it at all. Are there some flags I could pass to the wd driver to pick up this controller? - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 16: 9:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from sis.bytes.gen.nz (unknown [203.97.44.72]) by hub.freebsd.org (Postfix) with ESMTP id 67EB810FF7 for ; Mon, 22 Feb 1999 16:09:49 -0800 (PST) (envelope-from phillip@sis.bytes.gen.nz) Received: from expert [202.50.175.1] by sis.bytes.gen.nz (FTGate 2, 1, 2, 1); Tue, 23 Feb 99 13:12:40 +1300 Message-ID: <002001be5ec0$53b95820$01af32ca@expert> From: "Phillip Hardy" To: Subject: unsubscribe me... (PLEASE!) Date: Tue, 23 Feb 1999 13:06:14 +1300 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Sorry for posting this to the Group. 2. Is there a problem with Unsubscribeing from majordomo on the FreeBSD server? have send this massabe and the auth code (after reciveing it) 3 times now and it is not unsubing me ;( i even try my email after the unsub freebsd-current etc.. nothing.. just keep geting the messages ;) Thanks Everyone. Phill >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 16:17:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 8338311294 for ; Mon, 22 Feb 1999 16:16:41 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id CAA30150; Tue, 23 Feb 1999 02:39:31 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id CAA01625; Tue, 23 Feb 1999 02:41:14 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199902222341.CAA01625@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Mon, 22 Feb 1999 19:59:32 +0100." <19990222195932.A94515@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Feb 1999 02:41:14 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > This occurs almost immediately after copying a file to an msdos fs. I can > provide more info if that is deemed useful. I suspect your kernel compiled with INVARIANTS, you load msdosfs module dynamically, and the module isn't compiled with INVARIANTS. If so, don't do that. If not, please provide more info. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 18:27:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id 6BF1311E19 for ; Mon, 22 Feb 1999 18:27:17 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id KAA21604 for ; Tue, 23 Feb 1999 10:27:16 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id KAA00889 for freebsd-current@freebsd.org; Tue, 23 Feb 1999 10:27:13 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902230227.KAA00889@b1.hkstar.com> Subject: Can anyone tell me the meaning of it To: freebsd-current@freebsd.org Date: Tue, 23 Feb 1999 10:27:12 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I recenetly installed a multifunction tv card called FlyVideo (bt878) for my i386. I run dmesg with following warning. Can anyone tell me how to fix it ? Is there any document which guide the newbie in using the fxtv? Thanks. Clarence ======= dmesg ======= bktr0: rev 0x02 int a irq 5 on pci0.10.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 Warning - card vendor 0 unknown. This can cause poor performance Miro TV, Temic NTSC tuner. ======= dmesg ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 18:28:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 0750111E31 for ; Mon, 22 Feb 1999 18:27:52 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA28583; Mon, 22 Feb 1999 21:27:36 -0500 (EST) Date: Mon, 22 Feb 1999 21:27:36 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Joel Ray Holveck Cc: Mike Smith , RT , current@FreeBSD.ORG Subject: Re: NFS Problems In-Reply-To: <86iucucna7.fsf@detlev.UUCP> 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 22 Feb 1999, Joel Ray Holveck wrote: > >> The program on the client side always freezes (top reports it's > >> STAT as 'D'). > > You need to pass the 'l' switch to ps and look at the 'wchan' column to > > see where it's actually stuck. > > This reminds me; do we have a utility to reference wmesg strings back > to the code that sets them, a la TAGS? Would this be useful? > > Thanks, > joelh Ahem: glimpse! :) > > -- > Joel Ray Holveck - joelh@gnu.org > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 18:56:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id 40B07110A9; Mon, 22 Feb 1999 18:56:53 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10F81h-000I1oC; Mon, 22 Feb 1999 21:56:49 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Missing files/directories To: hackers@freebsd.org, current@freebsd.org Date: Mon, 22 Feb 1999 21:56:49 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2753 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the weekend I reported to hackers about problems experienced with 2.2-stable and RELENG-3 systems where I experienced files that disappeared from cache and Mail directories that disappeared. The RELENG-3 system had files affected with softupdates enabled. The 2.2-stable system had sub-directories missing from the same directories that I was writing to via nfsv2. By coincidence, I had cvsup'd and compiled new kernels and naturally made the assumption that there was causality there. Subsequently I have come to believe that the problem may have more to do with what I was doing, not changes to the code. For about 3-4 hours prior to noticing the problems, I had been repetitively editing dot files, then writing a kludge of dot files to the local system hard drive and to the nfs exported FS of the other computer, while occasionally checking mail on that computer. All files and directories missing were being updated for one reason or another by myself or by mail processes while I was doing this. It is speculation, but there is a good chance that there is a bug in the cache-handling code that causes problems with other files or directories being dropped from cache because of bad processing common to BOTH or ALL releases, when large numbers of dot files are being written. The dot files themselves did not disappear - other items to be written disappeared before their writes actually occurred. I know that this is a frustrating kind of message to receive, but I am not a developer & not qualified to go into the code myself. Also no logs or hard output are available - files/directories simply disappeared without any error messages. I just did a scan of the entire /usr/src/sys tree for \"\\.\" and \'\\.\' to see what code sections might be affected - mostly cache-handling. In quantity, not bad, really. Others have apparently reported missing files to do with nfs I believe. THis might or might not be a related problem. I guess that I am asking someone who is qualified, and concerned about missing files or directories, if they would be willing to do what I cannot - check the code for bad interactions when dot files are being written- bearing in mind that it is OTHER files/directories that are disappearing from cache before being written. Is anyone out there sufficiently intrigued by the possibility to invest some valuable time? I am a QA tester, not a developer, and therefore much more comfortable with discussion of symptoms and speculative causality than most developers I have known. I hope that someone thinks enough of the possibility to invest some time, which I know is in very short supply. I cannot deny that this is (informed) speculation - there are no guarantees. Regards and best wishes, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 19:43:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8891811052 for ; Mon, 22 Feb 1999 19:43:08 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA01964; Mon, 22 Feb 1999 22:43:12 -0500 (EST) Date: Mon, 22 Feb 1999 22:43:12 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Alexander N. Kabaev" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Filesystem deadlock In-Reply-To: <36D1898A.6D9C7B44@sti.cz> 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, 22 Feb 1999, Alexander N. Kabaev wrote: > The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE > as of today) to lookup. Shortly after this script is started, all disk activity > > stops and any attempt to create new process causes system to freese. While in DDB, ps command > > shows, that all ten fgrep processes are sleeping on inode, all xargs are in waitpid and > > all sh processes are in wait. You forget about all the processes (just a few, actually) stuck in "kmaw" (kmem_alloc_wait). This is definitely reproducible :( Should be simple for someone more knowledgeable to diagnose, as it looks to be a straight vm/vfs(ufs/ffs) interaction. > > Unfortunately, I cannot run -g kernel on my box > at this time, so amount of useful information I can provide is pretty much > limited :( > > #!/bin/sh > for j in 1 2 3 4 5 6 7 8 9 10; do > echo -n $i $j > nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka; > done' \ > >/dev/null 2>&1 & > echo > done > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 23:12:54 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 0117411A6F for ; Mon, 22 Feb 1999 23:12:51 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id CAA02316; Tue, 23 Feb 1999 02:12:50 -0500 (EST) (envelope-from luoqi) Date: Tue, 23 Feb 1999 02:12:50 -0500 (EST) From: Luoqi Chen Message-Id: <199902230712.CAA02316@lor.watermarkgroup.com> To: green@unixhelp.org, kan@sti.cz Subject: Re: Filesystem deadlock Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 22 Feb 1999, Alexander N. Kabaev wrote: > > > The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE > > as of today) to lookup. Shortly after this script is started, all disk activity > > > > stops and any attempt to create new process causes system to freese. While in DDB, ps command > > > > shows, that all ten fgrep processes are sleeping on inode, all xargs are in waitpid and > > > > all sh processes are in wait. > > You forget about all the processes (just a few, actually) stuck in "kmaw" > (kmem_alloc_wait). This is definitely reproducible :( Should be simple for > someone more knowledgeable to diagnose, as it looks to be a straight > vm/vfs(ufs/ffs) interaction. > This seems to be the good old vnode deadlock during vm_fault() that has been reported a couple of times, and there's still no satisfactory solution to it: fgrep does something like this: (don't ask me why) addr = mmap(0, len, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd, offset); read(fd, addr, count); the read() syscall first locks the vnode, read the data from disk, then copy the data to buffer at addr, now if addr is not in core, there'll be a page fault and the fault handler vm_fault will try to lock the vnode pager backing the page at addr, which is already locked, deadlock. This deadlock then propagates all the way back to the root vnode and the whole system would freeze. -lq > > > > Unfortunately, I cannot run -g kernel on my box > > at this time, so amount of useful information I can provide is pretty much > > limited :( > > > > #!/bin/sh > > for j in 1 2 3 4 5 6 7 8 9 10; do > > echo -n $i $j > > nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka; > > done' \ > > >/dev/null 2>&1 & > > echo > > done > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 23:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 5708B11AD6 for ; Mon, 22 Feb 1999 23:24:13 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 5547 invoked from network); 23 Feb 1999 07:24:10 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Feb 1999 07:24:10 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id CAA02628; Tue, 23 Feb 1999 02:24:07 -0500 (EST) Message-Id: <199902230724.CAA02628@y.dyson.net> Subject: Re: Filesystem deadlock In-Reply-To: <199902230712.CAA02316@lor.watermarkgroup.com> from Luoqi Chen at "Feb 23, 99 02:12:50 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Tue, 23 Feb 1999 02:24:07 -0500 (EST) Cc: green@unixhelp.org, kan@sti.cz, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Luoqi Chen said: > > > This seems to be the good old vnode deadlock during vm_fault() that has been > reported a couple of times, and there's still no satisfactory solution to it: > fgrep does something like this: (don't ask me why) > > addr = mmap(0, len, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd, offset); > read(fd, addr, count); > > the read() syscall first locks the vnode, read the data from disk, then copy > the data to buffer at addr, now if addr is not in core, there'll be a page > fault and the fault handler vm_fault will try to lock the vnode pager backing > the page at addr, which is already locked, deadlock. This deadlock then > propagates all the way back to the root vnode and the whole system would > freeze. > I believe that I had a pseudo-fix to that, and it might have been removed. (In non-multithreaded kernels, when having to do things like the above, allowing recursive locks under certain circumstances can solve the problem. The key is to avoid the case where it covers up real bugs.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 22 23:25:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 18765119C2 for ; Mon, 22 Feb 1999 23:25:47 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 6421 invoked from network); 23 Feb 1999 07:25:45 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Feb 1999 07:25:45 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id CAA02636; Tue, 23 Feb 1999 02:25:44 -0500 (EST) Message-Id: <199902230725.CAA02636@y.dyson.net> Subject: Re: Promise IDE board docs In-Reply-To: <199902221949.UAA63198@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Feb 22, 99 08:49:39 pm" To: sos@freebsd.dk (Søren Schmidt) Date: Tue, 23 Feb 1999 02:25:44 -0500 (EST) Cc: gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 Søren Schmidt said: > > It "should" work, but the promise support in the old system is, well, > hacky at best. I'm not sure if Promise supports more than one card > at a time, but from looking at the chip specs, it should work just > fine, and if the hardware works, at least the new driver will support > it. > I run with two (2) boards, but it appears that certain (all?) versions of the bios require that you remove the chip from all but one board. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 0:11: 4 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 3F1BE11F51 for ; Tue, 23 Feb 1999 00:10:52 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA64568; Tue, 23 Feb 1999 09:10:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902230810.JAA64568@freebsd.dk> Subject: Re: Promise IDE board docs In-Reply-To: <199902230725.CAA02636@y.dyson.net> from "John S. Dyson" at "Feb 23, 1999 2:25:44 am" To: dyson@iquest.net Date: Tue, 23 Feb 1999 09:10:47 +0100 (CET) Cc: gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems John S. Dyson wrote: > Søren Schmidt said: > > > > It "should" work, but the promise support in the old system is, well, > > hacky at best. I'm not sure if Promise supports more than one card > > at a time, but from looking at the chip specs, it should work just > > fine, and if the hardware works, at least the new driver will support > > it. > > > I run with two (2) boards, but it appears that certain (all?) versions > of the bios require that you remove the chip from all but one board. Bingo, looking at the HW specs I was pretty sure it would, but not being able to try it, I wouldn't bet on it. The BIOS on those boards are a different story, I run mine without the BIOS too, but then one has to setup the tranferrates etc by hand. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 0:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 626B9121AF for ; Tue, 23 Feb 1999 00:41:13 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id JAA23042 for ; Tue, 23 Feb 1999 09:41:11 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma023038; Tue, 23 Feb 99 09:41:12 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA08836 for ; Tue, 23 Feb 1999 09:41:07 +0100 (MET) Received: (qmail 97041 invoked by uid 666); 23 Feb 1999 08:41:20 -0000 Date: Tue, 23 Feb 1999 09:41:20 +0100 From: Jos Backus To: Dmitrij Tejblum Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990223094120.A97001@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990222195932.A94515@hal.mpn.cp.philips.com> <199902222341.CAA01625@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902222341.CAA01625@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Tue, Feb 23, 1999 at 02:41:14AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 02:41:14AM +0300, Dmitrij Tejblum wrote: > Jos Backus wrote: > > This occurs almost immediately after copying a file to an msdos fs. I can > > provide more info if that is deemed useful. > > I suspect your kernel compiled with INVARIANTS, Yes, and with INVARIANTS_SUPPORT as well as per Matt's instructions. > you load msdosfs module dynamically, and the module isn't compiled with > INVARIANTS. This is after a successful world and subsequent kernel build. > If so, don't do that. I'm not aware that I do, really. jos:/usr/src/sys/modules/msdos# grep INVARIANTS * jos:/usr/src/sys/modules/msdos# jos:/usr/src/sys/msdosfs# grep INVARIANTS * jos:/usr/src/sys/msdosfs# How does one add INVARIANTS support to modules? > If not, please provide more info. I'm not sure what I'm doing wrong. If I'm not, I will, of course. Just tell me what you want to know. Thanks, -- 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 Feb 23 1:12:48 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 B6F5F110E8 for ; Tue, 23 Feb 1999 01:12:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA60552; Tue, 23 Feb 1999 09:04:48 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 23 Feb 1999 09:04:48 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: mike@smith.net.au, romanp@wuppy.rcs.ru, current@freebsd.org Subject: Re: Problems with nfsstat and dynamic OID In-Reply-To: <199902220752.SAA01270@godzilla.zeta.org.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, 22 Feb 1999, Bruce Evans wrote: > >I fixed this a while back to use sysctlbyname, as it should have been > >done. Bruce subsequently backed it out (bad idea, IMO). > > You only worked around the previous breakage of vfs sysctls for the > statically configured case. The dynamically configured case was more > fundamentally broken (sysctls were not wired at all). Other applications > that use vfs sysctls, e.g., mountd(8), remained broken in all cases. Even then, only NFS' sysctls were 'fixed' to use vfc_typenum as their oid numbers. Other filesystems with sysctls such as ufs were still 'broken'. It is possible to change vfs_register so that it hacks the vfc_typenum into any oid it finds under 'vfs.' with the right name. I prefer just changing the supported mode of access to sysctlbyname(). -- 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 Feb 23 1:14: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id DAC4810F4E for ; Tue, 23 Feb 1999 01:11:45 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id MAA04066; Tue, 23 Feb 1999 12:08:07 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id MAA01169; Tue, 23 Feb 1999 12:09:03 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199902230909.MAA01169@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Tue, 23 Feb 1999 09:41:20 +0100." <19990223094120.A97001@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii From: Dmitrij Tejblum Date: Tue, 23 Feb 1999 12:09:03 +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > On Tue, Feb 23, 1999 at 02:41:14AM +0300, Dmitrij Tejblum wrote: > > Jos Backus wrote: > > > This occurs almost immediately after copying a file to an msdos fs. I can > > > provide more info if that is deemed useful. > > > > I suspect your kernel compiled with INVARIANTS, > > Yes, and with INVARIANTS_SUPPORT as well as per Matt's instructions. > > > you load msdosfs module dynamically, and the module isn't compiled with > > INVARIANTS. > > This is after a successful world and subsequent kernel build. > > > If so, don't do that. > > I'm not aware that I do, really. > > jos:/usr/src/sys/modules/msdos# grep INVARIANTS * > jos:/usr/src/sys/modules/msdos# > jos:/usr/src/sys/msdosfs# grep INVARIANTS * > jos:/usr/src/sys/msdosfs# Inline functions in vm/vm_zone.h depend on INVARIANTS. These functions used in msdosfs and in other parts of the kernel. > How does one add INVARIANTS support to modules? You could add -DINVARIANTS to CFLAGS in sys/module/msdosfs/Makefile. You better just link msdosfs statically, or remove INVARIANTS from your kernel. That is, INVARIANTS in kernel incompatible with dynamic loading. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 1:18:46 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 DA03010FEC for ; Tue, 23 Feb 1999 01:18:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.2/8.9.1) with ESMTP id BAA01441; Tue, 23 Feb 1999 01:18:43 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA29786; Tue, 23 Feb 1999 09:18:42 GMT (envelope-from obrien) Date: Tue, 23 Feb 1999 01:18:42 -0800 From: "David O'Brien" To: Mark Murray Cc: current@freebsd.org Subject: LSOF import into base system? Message-ID: <19990223011842.B29230@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199902221734.JAA21318@vashon.polstra.com> <199902221758.TAA36742@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902221758.TAA36742@greenpeace.grondar.za>; from Mark Murray on Mon, Feb 22, 1999 at 07:58:02PM +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 Excerpt from ports@freebsd.org: > MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through. If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Before discussing this issue, one should ``man 1 fstat''. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 1:31:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id DF3AE10E88 for ; Tue, 23 Feb 1999 01:31:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA05470; Tue, 23 Feb 1999 20:31:46 +1100 Date: Tue, 23 Feb 1999 20:31:46 +1100 From: Bruce Evans Message-Id: <199902230931.UAA05470@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: Problems with nfsstat and dynamic OID Cc: current@freebsd.org, mike@smith.net.au, romanp@wuppy.rcs.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >I fixed this a while back to use sysctlbyname, as it should have been >> >done. Bruce subsequently backed it out (bad idea, IMO). >> >> You only worked around the previous breakage of vfs sysctls for the >> statically configured case. The dynamically configured case was more >> fundamentally broken (sysctls were not wired at all). Other applications >> that use vfs sysctls, e.g., mountd(8), remained broken in all cases. > >Even then, only NFS' sysctls were 'fixed' to use vfc_typenum as their oid >numbers. Other filesystems with sysctls such as ufs were still 'broken'. Except there weren't any such filesystems at the time. Now that ffs's reallocblks is enabled, there are vfs.ffs.doreallocblks and vfs.ffs.doasyncfree, but these weren't and aren't a problem because ffs can't be an LKM er KLD, and there is no need to access them at the library level. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 1:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 5347110EA7 for ; Tue, 23 Feb 1999 01:59:34 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id KAA17148 for ; Tue, 23 Feb 1999 10:59:33 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma017145; Tue, 23 Feb 99 10:59:33 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id KAA28938 for ; Tue, 23 Feb 1999 10:59:29 +0100 (MET) Received: (qmail 2939 invoked by uid 666); 23 Feb 1999 09:59:39 -0000 Date: Tue, 23 Feb 1999 10:59:39 +0100 From: Jos Backus To: Dmitrij Tejblum Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990223105939.D97001@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902230909.MAA01169@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Tue, Feb 23, 1999 at 12:09:03PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote: > Inline functions in vm/vm_zone.h depend on INVARIANTS. These functions > used in msdosfs and in other parts of the kernel. OK, I see. > > How does one add INVARIANTS support to modules? > > You could add -DINVARIANTS to CFLAGS in sys/module/msdosfs/Makefile. > You better just link msdosfs statically, or remove INVARIANTS from your > kernel. I'll try this tonight, thanks. > That is, INVARIANTS in kernel incompatible with dynamic loading. Somehow this strikes me as a Bad Thing... 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 Feb 23 2: 4:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id EDB8A110C4 for ; Tue, 23 Feb 1999 02:04:46 -0800 (PST) (envelope-from davidhol@wrs.com) Received: from papermill (papermill.wrs.com [147.11.48.34]) by mail.wrs.com (8.9.1/8.9.1) with ESMTP id CAA17275 for ; Tue, 23 Feb 1999 02:04:46 -0800 (PST) Message-Id: <199902231004.CAA17275@mail.wrs.com> To: freebsd-current@freebsd.org From: David Holloway Subject: pci based kernel modules. Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Tue, 23 Feb 1999 02:04:46 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to load kernel modules that are supposed to operate on pci devices? ... Does pci_rescan() need to be finished ? What am I missing here? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 2:22:22 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 4E8CE113AD; Tue, 23 Feb 1999 02:21:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10FEy5-0000OA-00; Tue, 23 Feb 1999 12:21:33 +0200 From: Sheldon Hearn To: obrien@FreeBSD.ORG Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: LSOF import into base system? In-reply-to: Your message of "Tue, 23 Feb 1999 01:18:42 PST." <19990223011842.B29230@dragon.nuxi.com> Date: Tue, 23 Feb 1999 12:21:32 +0200 Message-ID: <1497.919765292@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Feb 1999 01:18:42 PST, "David O'Brien" wrote: > If people feel this is desired, I can easily bmake and import it. > From working with Vic Abell, I know he is interested in any > problems/issues that we may find in LSOF if we find issues when > scrutinizing it. Hi David, I think Vic's responsiveness and enthusiasm for team-work means that the software gets excellent attention when it comes to FreeBSD issues. And since the software is under very active development by him, it looks like the following trade-off is in the air on this one: 1) We score rapid FreeBSD-specific tweaking if it's in the base system. 2) We score off up-to-date software if it's in the ports tree. My worry is that we won't really score _that_ much FreeBSD-specific tweaking against the loss of having the version in the base system fall behind Vic's development edge. Or do you reckon lsof will be kept up to date in the base system? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 3:17: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 6345910F0C; Tue, 23 Feb 1999 03:16:14 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:QyMktQSKn31lYUIHeQtEWDxIjF3nR57Y@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id NAA49256; Tue, 23 Feb 1999 13:16:12 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:ZDcx0SRFN3JJWwx94jf4s028r4mmZirK@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id NAA40560; Tue, 23 Feb 1999 13:16:10 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199902231116.NAA40560@greenpeace.grondar.za> To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: LSOF import into base system? In-Reply-To: Your message of " Tue, 23 Feb 1999 01:18:42 PST." <19990223011842.B29230@dragon.nuxi.com> References: <199902221734.JAA21318@vashon.polstra.com> <199902221758.TAA36742@greenpeace.grondar.za> <19990223011842.B29230@dragon.nuxi.com> Date: Tue, 23 Feb 1999 13:16:09 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > Excerpt from ports@freebsd.org: > > MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through. > > If people feel this is desired, I can easily bmake and import it. > From working with Vic Abell, I know he is interested in any > problems/issues that we may find in LSOF if we find issues when > scrutinizing it. > > Before discussing this issue, one should ``man 1 fstat''. Garrett feels happier about fstat as it is "Original BSD Code". Any chances of engineering the functional diffs between fstat(1) and lsof(1) back into fstat? If the problem is too great, I'll vote for an import. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 4:24: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id D6AA410EA8 for ; Tue, 23 Feb 1999 04:23:58 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id GAA26818; Tue, 23 Feb 1999 06:23:28 -0600 (CST) From: Kevin Day Message-Id: <199902231223.GAA26818@home.dragondata.com> Subject: Re: Filesystem deadlock In-Reply-To: from Brian Feldman at "Feb 22, 1999 10:43:12 pm" To: green@unixhelp.org (Brian Feldman) Date: Tue, 23 Feb 1999 06:23:28 -0600 (CST) Cc: kan@sti.cz, freebsd-current@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 > On Mon, 22 Feb 1999, Alexander N. Kabaev wrote: > > > The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE > > as of today) to lookup. Shortly after this script is started, all disk activity > > > > stops and any attempt to create new process causes system to freese. While in DDB, ps command > > > > shows, that all ten fgrep processes are sleeping on inode, all xargs are in waitpid and > > > > all sh processes are in wait. > > You forget about all the processes (just a few, actually) stuck in "kmaw" > (kmem_alloc_wait). This is definitely reproducible :( Should be simple for > someone more knowledgeable to diagnose, as it looks to be a straight > vm/vfs(ufs/ffs) interaction. This is happening to me too, with a system that was from the 19th's SNAP, as well as today's kernel. (except I don't see anything in 'kmaw'). The process 'swapper' is stuck in 'inode', as well as anything else that's tried to touch the disk. Lots of 'sh's sitting in 'wait'. This machine is a heavy NFS client, but I'm not sure that it's related. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 6:53:42 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 5C9D111118 for ; Tue, 23 Feb 1999 06:53:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id JAA14766; Tue, 23 Feb 1999 09:53:31 -0500 (EST) (envelope-from wollman) Date: Tue, 23 Feb 1999 09:53:31 -0500 (EST) From: Garrett Wollman Message-Id: <199902231453.JAA14766@khavrinen.lcs.mit.edu> To: David Holloway Cc: freebsd-current@FreeBSD.ORG Subject: pci based kernel modules. In-Reply-To: <199902231004.CAA17275@mail.wrs.com> References: <199902231004.CAA17275@mail.wrs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is it possible to load kernel modules that are supposed > to operate on pci devices? Not yet. There are several of us who have worked on parts of this problem in the past, but we're not there yet. Join new-bus-arch@bostonradio.org if you are interested in helping out. -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 Tue Feb 23 7:16:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 01349119ED for ; Tue, 23 Feb 1999 07:16:28 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA13116; Tue, 23 Feb 1999 16:16:26 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA11127; Tue, 23 Feb 1999 16:16:26 +0100 (MET) Date: Tue, 23 Feb 1999 16:16:26 +0100 From: Eivind Eklund To: Jos Backus Cc: Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990223161625.B10845@bitbox.follo.net> References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990223105939.D97001@hal.mpn.cp.philips.com>; from Jos Backus on Tue, Feb 23, 1999 at 10:59:39AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 10:59:39AM +0100, Jos Backus wrote: > On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote: > > Inline functions in vm/vm_zone.h depend on INVARIANTS. These functions > > used in msdosfs and in other parts of the kernel. > > OK, I see. > > > > How does one add INVARIANTS support to modules? > > > > You could add -DINVARIANTS to CFLAGS in sys/module/msdosfs/Makefile. > > You better just link msdosfs statically, or remove INVARIANTS from your > > kernel. > > I'll try this tonight, thanks. > > > That is, INVARIANTS in kernel incompatible with dynamic loading. > > Somehow this strikes me as a Bad Thing... It _is_ a bad thing. I've been pondering what to do with the intrusive invariant checks - make them dependent on INTRUSIVE_INVARIANTS, perhaps? That would still make some KLDs incompatible with INTRUSIVE_INVARIANTS, but that is probably the best we can do. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 7:37:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 626691138E for ; Tue, 23 Feb 1999 07:37:40 -0800 (PST) (envelope-from netch@lucky.net) Received: (from netch@localhost) by burka.carrier.kiev.ua (8.Who.Cares/8.Who.Cares) id RAA07564; Tue, 23 Feb 1999 17:37:39 +0200 (EET) (envelope-from netch) Date: Tue, 23 Feb 1999 17:37:39 +0200 (EET) From: Valentin Nechayev Message-Id: <199902231537.RAA07564@burka.carrier.kiev.ua> To: freebsd-current@freebsd.org Subject: Re: Filesystem deadlock In-Reply-To: <36D1898A.6D9C7B44@sti.cz> Organization: Lucky Netch Incorporated User-Agent: tin/pre-1.4-980226 (UNIX) (FreeBSD/2.2.6-RELEASE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander N. Kabaev wrote: ANK> The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE ANK> as of today) to lookup. 2.2.8 and 3.0-RELEASE are not vulnerable, by the way. ANK> Shortly after this script is started, all disk ANK> activity stops and any attempt to create new process causes system to ANK> freese. No, creating of new process is possible, but no file can be opened. All memory activity does not hang: i.e., top redraws list of active processes. Also, command '( export A=1 B=2 set )' works - that is, fork() works. ANK> While in DDB, ps command shows, that all ten fgrep processes are ANK> sleeping on inode, all xargs are in waitpid and ANK> all sh processes are in wait. In original tests, any process can stop in 'inode' state when it try to open a file. For example, try type 'ps' at another terminal and You can see shell stopped in 'inode' state ;( ANK> #!/bin/sh ANK> for j in 1 2 3 4 5 6 7 8 9 10; do ANK> echo -n $i $j ~~ ;( ANK> nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka; ANK> done' \ >>/dev/null 2>&1 & ANK> echo ANK> done -- -- Valentin Nechayev netch@lucky.net II:LDXIII/MCMLXXII.CCC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 8: 8:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id EBEC9120C0 for ; Tue, 23 Feb 1999 08:08:38 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id RAA07173 for ; Tue, 23 Feb 1999 17:08:37 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma007169; Tue, 23 Feb 99 17:08:37 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id RAA03676 for ; Tue, 23 Feb 1999 17:08:36 +0100 (MET) Received: (qmail 6577 invoked by uid 666); 23 Feb 1999 16:08:57 -0000 Date: Tue, 23 Feb 1999 17:08:57 +0100 From: Jos Backus To: Eivind Eklund Cc: Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990223170857.A6208@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <19990223161625.B10845@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990223161625.B10845@bitbox.follo.net>; from Eivind Eklund on Tue, Feb 23, 1999 at 04:16:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 04:16:26PM +0100, Eivind Eklund wrote: > > Somehow this strikes me as a Bad Thing... > > It _is_ a bad thing. I've been pondering what to do with the > intrusive invariant checks - make them dependent on > INTRUSIVE_INVARIANTS, perhaps? Depends on how dangerous these invariant violations are, I would think. Iow, do they justify a panic()? > That would still make some KLDs incompatible with INTRUSIVE_INVARIANTS, but > that is probably the best we can do. At least that way the non-intrusive ones can be left in (and still be useful). 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 Feb 23 8:25:59 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 C5CE51169B for ; Tue, 23 Feb 1999 08:25:56 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA09126; Tue, 23 Feb 1999 11:25:53 -0500 (EST) (envelope-from luoqi) Date: Tue, 23 Feb 1999 11:25:53 -0500 (EST) From: Luoqi Chen Message-Id: <199902231625.LAA09126@lor.watermarkgroup.com> To: dyson@iquest.net, luoqi@watermarkgroup.com Subject: Re: Filesystem deadlock Cc: freebsd-current@FreeBSD.ORG, green@unixhelp.org, kan@sti.cz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen said: > > > > > This seems to be the good old vnode deadlock during vm_fault() that has been > > reported a couple of times, and there's still no satisfactory solution to it: > > fgrep does something like this: (don't ask me why) > > > > addr = mmap(0, len, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd, offset); > > read(fd, addr, count); > > > > the read() syscall first locks the vnode, read the data from disk, then copy > > the data to buffer at addr, now if addr is not in core, there'll be a page > > fault and the fault handler vm_fault will try to lock the vnode pager backing > > the page at addr, which is already locked, deadlock. This deadlock then > > propagates all the way back to the root vnode and the whole system would > > freeze. > > > I believe that I had a pseudo-fix to that, and it might have been removed. > (In non-multithreaded kernels, when having to do things like the above, > allowing recursive locks under certain circumstances can solve the problem. > The key is to avoid the case where it covers up real bugs.) > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > Do you still have that piece of code? Does it handle the case involves more than one process? For example, process 1 mmaps file B and reads file A into the mmapped region, while process 2 mmaps file A and reads file B, this could also result in a deadlock. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 10:17:40 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 DD3241112D for ; Tue, 23 Feb 1999 10:17:35 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.2/8.9.1) with ESMTP id KAA09759; Tue, 23 Feb 1999 10:17:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA56481; Tue, 23 Feb 1999 18:17:34 GMT (envelope-from obrien) Date: Tue, 23 Feb 1999 10:17:34 -0800 From: "David O'Brien" To: Mark Murray Cc: current@freebsd.org Subject: Re: LSOF import into base system? Message-ID: <19990223101734.A28823@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199902221734.JAA21318@vashon.polstra.com> <199902221758.TAA36742@greenpeace.grondar.za> <19990223011842.B29230@dragon.nuxi.com> <199902231116.NAA40560@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902231116.NAA40560@greenpeace.grondar.za>; from Mark Murray on Tue, Feb 23, 1999 at 01:16:09PM +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 > Garrett feels happier about fstat as it is "Original BSD Code". Any > chances of engineering the functional diffs between fstat(1) and > lsof(1) back into fstat? I guess it is possible, but it would probably take someone like Peter, bde, or Matt Dillon that understands well all of our layerd filesystem ops. > If the problem is too great, I'll vote for an import. IMO, either importing LSOF or doing nothing is the most time efficient and productive options. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 10:19:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 6912311353 for ; Tue, 23 Feb 1999 10:19:05 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id TAA19102; Tue, 23 Feb 1999 19:18:57 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA11994; Tue, 23 Feb 1999 19:18:57 +0100 (MET) Date: Tue, 23 Feb 1999 19:18:57 +0100 From: Eivind Eklund To: Jos Backus Cc: Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990223191857.H10845@bitbox.follo.net> References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <19990223161625.B10845@bitbox.follo.net> <19990223170857.A6208@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990223170857.A6208@hal.mpn.cp.philips.com>; from Jos Backus on Tue, Feb 23, 1999 at 05:08:57PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 05:08:57PM +0100, Jos Backus wrote: > On Tue, Feb 23, 1999 at 04:16:26PM +0100, Eivind Eklund wrote: > > > Somehow this strikes me as a Bad Thing... > > > > It _is_ a bad thing. I've been pondering what to do with the > > intrusive invariant checks - make them dependent on > > INTRUSIVE_INVARIANTS, perhaps? > > Depends on how dangerous these invariant violations are, I would think. > Iow, do they justify a panic()? IMO, any invariant violation justifies a panic(). Otherwise, people would not pay heed to them. Invariant violations are pretty serious. However, my opinion is also that invariant checks should be non-intrusive - ie, they should not change the normal code path, only add extra checks. A couple of the invariants we have modify the behaviour to make it possible to check for things, and this should be separate from the ones that doesn't modify the behaviour beyond adding checks. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 10:29:36 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 C4806112B9 for ; Tue, 23 Feb 1999 10:29:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id KAA09971; Tue, 23 Feb 1999 10:28:25 -0800 (PST) (envelope-from obrien) Date: Tue, 23 Feb 1999 10:28:25 -0800 From: "David O'Brien" To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: LSOF import into base system? Message-ID: <19990223102825.A9812@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19990223011842.B29230@dragon.nuxi.com> <1497.919765292@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <1497.919765292@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Feb 23, 1999 at 12:21:32PM +0200 X-Operating-System: FreeBSD 3.1-STABLE 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 think Vic's responsiveness and enthusiasm for team-work means that the > software gets excellent attention when it comes to FreeBSD issues. We get very high attention by Vic. I've provided him access (or obtained access) to FreeBSD-CURRENT many times when he requested so he could test things. I've never seen attention to this degree before for FreeBSD from a software author. He truly cares that LSOF runs excellent on FreeBSD. > My worry is that we won't really score _that_ much FreeBSD-specific > tweaking against the loss of having the version in the base system fall > behind Vic's development edge. IMHO, the only thing we gain is that one doesn't have to install the port anymore to get LSOF. If we import it into contrib/, I think we will be doing vendor branch imports quite often. A few seemed to feel strongly that it should be imported. Some were worried about it's "security" (really safe software engr.). Of course the port can still be audited and diffs passed back to Vic. > Or do you reckon lsof will be kept up to date in the base system? If nobody else does, I would. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 10:30:32 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 E76EA11496; Tue, 23 Feb 1999 10:30:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA26570; Tue, 23 Feb 1999 19:30:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Eivind Eklund Cc: Jos Backus , Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Tue, 23 Feb 1999 19:18:57 +0100." <19990223191857.H10845@bitbox.follo.net> Date: Tue, 23 Feb 1999 19:30:08 +0100 Message-ID: <26568.919794608@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990223191857.H10845@bitbox.follo.net>, Eivind Eklund writes: >A couple of the invariants we have modify the >behaviour to make it possible to check for things, and this should be >separate from the ones that doesn't modify the behaviour beyond adding >checks. That sounds more like DIAGNOSTIC kind of material, doesn't it ? -- 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 Tue Feb 23 11:32:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (45-sweet.camalott.com [208.239.153.45]) by hub.freebsd.org (Postfix) with ESMTP id 10D5C1114F for ; Tue, 23 Feb 1999 11:32:13 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.2/8.9.1) id NAA20337; Tue, 23 Feb 1999 13:31:23 -0600 (CST) (envelope-from joelh) To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: NFS Problems References: <199902222220.OAA00897@dingo.cdrom.com> From: Joel Ray Holveck Date: 23 Feb 1999 13:31:21 -0600 In-Reply-To: Mike Smith's message of "Mon, 22 Feb 1999 14:20:42 -0800" Message-ID: <86btikdiie.fsf@detlev.UUCP> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This reminds me; do we have a utility to reference wmesg strings back >> to the code that sets them, a la TAGS? Would this be useful? > No, and yes respectively. I have the scanner mostly written; there is one bug yet to fix (This time for sure!). Presently, it creates a single file WTAGS which contains an easily-read (my man or machine) flat file index. I will presently be modifying it to generate Emacs's etags format, as well as ctags, and as soon as I learn it, GSYMS format. At the moment, the scanner scans tsleep, asleep, and ttysleep calls. What other sleep functions can have the wchan specified as a string literal? There being no robust manner to handle calls with a computed or dereferenced wchan, such as acquire(), I will allow for a notation of /* WCHAN: foo */ to cause the appropriate information to be added to the database. Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 11:32:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id A28251120C for ; Tue, 23 Feb 1999 11:32:30 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 25493 invoked from network); 23 Feb 1999 19:32:27 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Feb 1999 19:32:27 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id OAA04081; Tue, 23 Feb 1999 14:32:25 -0500 (EST) Message-Id: <199902231932.OAA04081@y.dyson.net> Subject: Re: Filesystem deadlock In-Reply-To: <199902231625.LAA09126@lor.watermarkgroup.com> from Luoqi Chen at "Feb 23, 99 11:25:53 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Tue, 23 Feb 1999 14:32:25 -0500 (EST) Cc: dyson@iquest.net, luoqi@watermarkgroup.com, freebsd-current@FreeBSD.ORG, green@unixhelp.org, kan@sti.cz From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Luoqi Chen said: > > > Do you still have that piece of code? Does it handle the case involves more > than one process? For example, process 1 mmaps file B and reads file A into > the mmapped region, while process 2 mmaps file A and reads file B, this could > also result in a deadlock. > It used to be part of the tree, but I seem to remember that it was removed (by those who understand the code :-)) soon after I left. I will look for it, and see if it would help with the problem(s). -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 11:42:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id F17241128C for ; Tue, 23 Feb 1999 11:42:01 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 6772 invoked from network); 23 Feb 1999 19:41:59 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Feb 1999 19:41:59 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id OAA04104; Tue, 23 Feb 1999 14:41:57 -0500 (EST) Message-Id: <199902231941.OAA04104@y.dyson.net> Subject: Re: Promise IDE board docs In-Reply-To: <199902230810.JAA64568@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Feb 23, 99 09:10:47 am" To: sos@freebsd.dk (Søren Schmidt) Date: Tue, 23 Feb 1999 14:41:57 -0500 (EST) Cc: dyson@iquest.net, gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 Søren Schmidt said: > It seems John S. Dyson wrote: > > Søren Schmidt said: > > > > > > It "should" work, but the promise support in the old system is, well, > > > hacky at best. I'm not sure if Promise supports more than one card > > > at a time, but from looking at the chip specs, it should work just > > > fine, and if the hardware works, at least the new driver will support > > > it. > > > > > I run with two (2) boards, but it appears that certain (all?) versions > > of the bios require that you remove the chip from all but one board. > > Bingo, looking at the HW specs I was pretty sure it would, but not > being able to try it, I wouldn't bet on it. > The BIOS on those boards are a different story, I run mine without > the BIOS too, but then one has to setup the tranferrates etc by > hand. > Now, that is INTERESTING. With the bios that I have, all of the ports on both boards get configured properly, and run UDMA. Next time I crack my box open, I'll let you know the bios version and board (and bios) positions. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 11:42:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 2BB251128C; Tue, 23 Feb 1999 11:42:36 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id NAA21558; Tue, 23 Feb 1999 13:42:16 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id NAA21554; Tue, 23 Feb 1999 13:42:16 -0600 (CST) Message-ID: <01b401be5f64$ab1019c0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" , "FreeBSD-Stable" Subject: listproc problem? Date: Tue, 23 Feb 1999 13:42:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been seeing 5 hour delays from when the message was sent to the list and when the message arrives in my mailbox. It seems to be a problem with the following jump: Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id NAA00902; Tue, 23 Feb 1999 13:26:13 -0600 (CST) Received: by hub.freebsd.org (Postfix, from userid 538) id AECC411D08; Tue, 23 Feb 1999 07:34:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 5DD8B11B6C; Tue, 23 Feb 1999 07:34:37 -0800 (PST) (envelope-from owner-freebsd-stable) Also, as a side note, how do I set up my box to use PostFix instead of sendmail? I heard that it was (or was considered) included in the 3.1-RELEASE, it just wasn't enabled by default. Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 14: 1:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 5890B115BD for ; Tue, 23 Feb 1999 14:01:47 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA06631 for ; Tue, 23 Feb 1999 23:01:36 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id WAA01911; Tue, 23 Feb 1999 22:56:15 +0100 (CET) (envelope-from nsouch) Message-ID: <19990223225615.15493@breizh.teaser.fr> Date: Tue, 23 Feb 1999 22:56:15 +0100 From: Nicolas Souchu To: current@freebsd.org Subject: kernel build failure at nfs_serv.c Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Updating at Mar 23 fév 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_serv.c ../../nfs/nfs_serv.c:103: `sysctl__vfs_nfs_children' undeclared here (not in a function) ../../nfs/nfs_serv.c:103: initializer element for `sysctl___vfs_nfs_async.oid_parent' is not constant *** Error code 1 Stop. Any clue? -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Tue Feb 23 14: 2:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 190F81180E; Tue, 23 Feb 1999 14:02:08 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA10788; Tue, 23 Feb 1999 23:01:57 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id WAA01900; Tue, 23 Feb 1999 22:54:25 +0100 (CET) (envelope-from nsouch) Message-ID: <19990223225425.28013@breizh.teaser.fr> Date: Tue, 23 Feb 1999 22:54:25 +0100 From: Nicolas Souchu To: Warner Losh Cc: "Jonathan M. Bresler" , chuckr@mat.net, freebsd-current@freebsd.org Subject: Re: lpt0 References: <199902141331.FAA27832@hub.freebsd.org> <19990213191714.53383@breizh.prism.uvsq.fr> <199902141331.FAA27832@hub.freebsd.org> <199902170516.WAA51425@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199902170516.WAA51425@harmony.village.org>; from Warner Losh on Tue, Feb 16, 1999 at 10:16:05PM -0700 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 16, 1999 at 10:16:05PM -0700, Warner Losh wrote: > >In message <199902141331.FAA27832@hub.freebsd.org> "Jonathan M. Bresler" writes: >: how much information about this should be included in >: /usr/src/UPDATING? the entry there talks about the change but does >: not provide enough information to successfully upgrade (ppc0 is not >: mentioned, nor does it provide a pointer to where to go for more >: information.) ;( > >I'm about to commit a change to UPDATING to point to this URL and man >page. I'm just now catching up from being gone for a week. Thanks, I've update the web page since you refer to it in UPDATING. > >Warner > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Tue Feb 23 14:27:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 5ABD71140C; Tue, 23 Feb 1999 14:27:39 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA01117; Tue, 23 Feb 1999 22:26:09 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00707; Tue, 23 Feb 1999 08:22:47 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199902230822.IAA00707@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: tom@tomqnx.com (Tom Torrance at home) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Missing files/directories In-reply-to: Your message of "Mon, 22 Feb 1999 21:56:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Feb 1999 08:22:47 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't claim to know a great deal about cache code etc, but I'm pretty sure that it's extremely unlikely that the file name has any chance of affecting the buffer cache. While NFS has its fair share of problems (with which Matt is dealing with admirably), I would think that the code that does the work there is equally unlikely to know anything about file names. Having said all that in as vague a way as possible, the reason I'm posting this is that you seem to be experiencing difficulties with ppp that are of a similar nature - that is, completely inexplicable and unseen by anyone else - disappearing default routes, ppp.linkdown not being processed, I'm beginning to suspect a hardware problem - perhaps with your disk controller or something. This wouldn't easily explain the default route problem, but may explain the failure to process ppp.linkdown.... Maybe you could try treating the other machine (your son's machine?) as the gateway, and see if things become more stable. If they do, the finger might be pointed more firmly at hardware. > On the weekend I reported to hackers about problems experienced with > 2.2-stable and RELENG-3 systems where I experienced files that > disappeared from cache and Mail directories that disappeared. > The RELENG-3 system had files affected with softupdates enabled. > The 2.2-stable system had sub-directories missing from the > same directories that I was writing to via nfsv2. > > By coincidence, I had cvsup'd and compiled new kernels and naturally > made the assumption that there was causality there. Subsequently > I have come to believe that the problem may have more to do with what > I was doing, not changes to the code. > > For about 3-4 hours prior to noticing the problems, I had been > repetitively editing dot files, then writing a kludge of dot files > to the local system hard drive and to the nfs exported FS of the > other computer, while occasionally checking mail on that computer. > > All files and directories missing were being updated for > one reason or another by myself or by mail processes while > I was doing this. > > It is speculation, but there is a good chance that there is a bug > in the cache-handling code that causes problems with other files > or directories being dropped from cache because of bad processing > common to BOTH or ALL releases, when large numbers of dot files are > being written. The dot files themselves did not disappear - other > items to be written disappeared before their writes actually > occurred. > > I know that this is a frustrating kind of message to receive, but > I am not a developer & not qualified to go into the code myself. > Also no logs or hard output are available - files/directories > simply disappeared without any error messages. > > I just did a scan of the entire /usr/src/sys tree for \"\\.\" > and \'\\.\' to see what code sections might be affected - mostly > cache-handling. In quantity, not bad, really. > > Others have apparently reported missing files to do with nfs > I believe. THis might or might not be a related problem. > > I guess that I am asking someone who is qualified, and concerned > about missing files or directories, if they would be willing > to do what I cannot - check the code for bad interactions when > dot files are being written- bearing in mind that it is OTHER > files/directories that are disappearing from cache before being > written. > > Is anyone out there sufficiently intrigued by the possibility > to invest some valuable time? > > I am a QA tester, not a developer, and therefore much more > comfortable with discussion of symptoms and speculative > causality than most developers I have known. I hope that > someone thinks enough of the possibility to invest some > time, which I know is in very short supply. I cannot deny > that this is (informed) speculation - there are no guarantees. > > Regards and best wishes, > Tom -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 14:32:50 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 023B411C2A for ; Tue, 23 Feb 1999 14:32:22 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA04987; Tue, 23 Feb 1999 23:32:11 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 712FF8839; Tue, 23 Feb 1999 23:24:48 +0100 (CET) Date: Tue, 23 Feb 1999 23:24:48 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Cc: "David E . O'Brien" Subject: Re: LSOF import into base system? Message-ID: <19990223232448.A36271@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG, "David E . O'Brien" References: <199902221734.JAA21318@vashon.polstra.com> <199902221758.TAA36742@greenpeace.grondar.za> <19990223011842.B29230@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990223011842.B29230@dragon.nuxi.com>; from David E . O'Brien on Tue, Feb 23, 1999 at 01:18:42AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5084 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E . O'Brien: > If people feel this is desired, I can easily bmake and import it. > >From working with Vic Abell, I know he is interested in any > problems/issues that we may find in LSOF if we find issues when > scrutinizing it. Well, the way I see it, Vic is already maintaining LSOF for so many platforms that I don't see any real advantage in importing it. As long as he can sync with FreeBSD internal changes (and he can because he has access to such systems -- thanks you for that), we have a a working lsof. That way, Vic doesn't have divergent versions (you don't plan to update contrib/lsof for each change Vic makes to other platforms don't you ?). To be honest, I would not miss fstat(1), even if it is good ol' BSD code, I install lsof everywhere. Putting lsof features into fstat is just IMO a waste of time and code. Now, can we import Postfix instead ? :-) :-) [ducks and runs] -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 14:33:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 50A4611C89 for ; Tue, 23 Feb 1999 14:33:46 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA24159; Wed, 24 Feb 1999 07:33:43 +0900 (JST) Message-ID: <36D329D1.73146EEF@newsguy.com> Date: Wed, 24 Feb 1999 07:21:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jos Backus Cc: Dmitrij Tejblum , freebsd-current@FreeBSD.org Subject: Re: panic: zone: entry not free References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > > > That is, INVARIANTS in kernel incompatible with dynamic loading. > > Somehow this strikes me as a Bad Thing... Invariants is not for the production minded. It is for those who work with things likely to get broken. Say, for instance, -current. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 16:20:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 2511911222; Tue, 23 Feb 1999 16:20:04 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id KAA24978; Wed, 24 Feb 1999 10:50:03 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA30351; Wed, 24 Feb 1999 10:50:01 +1030 Date: Wed, 24 Feb 1999 10:50:01 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "Thomas T. Veldhouse" Cc: FreeBSD-Current , FreeBSD-Stable Subject: Re: listproc problem? In-Reply-To: <01b401be5f64$ab1019c0$236319ac@w142844.carlson.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 Tue, 23 Feb 1999, Thomas T. Veldhouse wrote: > Also, as a side note, how do I set up my box to use PostFix instead of > sendmail? I heard that it was (or was considered) included in the > 3.1-RELEASE, it just wasn't enabled by default. It was shouted down as unnecessary bloat in favour of a port. However, I haven't seen this port submitted yet..until then looks like you'll have to install manually. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 16:43:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3083F10F06; Tue, 23 Feb 1999 16:43:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA54257; Tue, 23 Feb 1999 16:40:18 -0800 (PST) (envelope-from dillon) Date: Tue, 23 Feb 1999 16:40:18 -0800 (PST) From: Matthew Dillon Message-Id: <199902240040.QAA54257@apollo.backplane.com> To: Poul-Henning Kamp Cc: Eivind Eklund , Jos Backus , Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <26568.919794608@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <19990223191857.H10845@bitbox.follo.net>, Eivind Eklund writes: : :>A couple of the invariants we have modify the :>behaviour to make it possible to check for things, and this should be :>separate from the ones that doesn't modify the behaviour beyond adding :>checks. : :That sounds more like DIAGNOSTIC kind of material, doesn't it ? : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." It sure does. DIAGNOSTIC is historically intrusive. INVARIANTS should definitely *not* be intrusive. 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 Feb 23 18:31:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id AF6071166A; Tue, 23 Feb 1999 18:31:00 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10FU3m-000I5dC; Tue, 23 Feb 1999 21:28:26 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: Missing files/directories In-Reply-To: <199902230822.IAA00707@keep.lan.Awfulhak.org> from Brian Somers at "Feb 23, 1999 8:22:47 am" To: brian@Awfulhak.org (Brian Somers) Date: Tue, 23 Feb 1999 21:28:26 -0500 (EST) Cc: tom@tomqnx.com, hackers@FreeBSD.ORG, current@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 Content-Length: 514 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, brian, Good idea - I will set up tests tomorrow following your advice. I don't want to be right - I want to be problem-free:-) I can't use my son's machine as he is behind a firewall I can't breach so I will set it up with a couple of machines here on my LAN, internally. I might just swap out the old 2.2-stable server for another machine running the latest RELENG_3. I'll have to think about that... I'll get the results to you as soon as I can. Hopefully within the next couple of days. Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 23 18:39:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 70AF811777 for ; Tue, 23 Feb 1999 18:39:12 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA22168; Tue, 23 Feb 1999 21:39:14 -0500 (EST) Date: Tue, 23 Feb 1999 21:39:14 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Ollivier Robert Cc: current@FreeBSD.ORG, "David E . O'Brien" Subject: Re: LSOF import into base system? In-Reply-To: <19990223232448.A36271@keltia.freenix.fr> 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, 23 Feb 1999, Ollivier Robert wrote: > According to David E . O'Brien: > > If people feel this is desired, I can easily bmake and import it. > > >From working with Vic Abell, I know he is interested in any > > problems/issues that we may find in LSOF if we find issues when > > scrutinizing it. > > Well, the way I see it, Vic is already maintaining LSOF for so many > platforms that I don't see any real advantage in importing it. As long as > he can sync with FreeBSD internal changes (and he can because he has access > to such systems -- thanks you for that), we have a a working lsof. > > That way, Vic doesn't have divergent versions (you don't plan to update > contrib/lsof for each change Vic makes to other platforms don't you ?). > > To be honest, I would not miss fstat(1), even if it is good ol' BSD code, I > install lsof everywhere. Putting lsof features into fstat is just IMO a > waste of time and code. AHEM! I use it. Often. I'm certain many others do to. Don't get rid of it, ever! > > Now, can we import Postfix instead ? :-) :-) [ducks and runs] > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 13:28:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 048E211140 for ; Wed, 24 Feb 1999 13:19:18 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id PAA18532; Wed, 24 Feb 1999 15:17:48 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma018519; Wed, 24 Feb 99 15:17:41 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10Fg4C-00013j-00; Wed, 24 Feb 1999 15:17:40 +0000 From: Tony Finch To: current@freebsd.org Subject: mount -o union broken recently? X-Newsgroups: chiark.mail.freebsd.stable In-Reply-To: Organization: Demon Internet Ltd Message-Id: Date: Wed, 24 Feb 1999 15:17:40 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been experimenting with union mounts today with a recent -stable (cvsupped yesterday), and I haven't had much luck. Because cvsup likes to obliterate local changes, I thought it would be convenient to keep the altered files on a separate filesystem and use a union mount to overlay them on the upstream source when I compile things. So: # mount /dev/da0s1a on / (local, writes: sync 420 async 3185) procfs on /proc (local) /dev/da0s1e on /www (local, writes: sync 2 async 0) # mount /dev/da0s1f /srcdelta # ls -l /srcdelta total 1 drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys # umount /srcdelta # ls /usr/src COPYRIGHT UPDATING include share CVS bin kerberosIV sys Makefile contrib lib tools Makefile.inc0 crypto libexec usr.bin Makefile.inc1 etc release usr.sbin Makefile.upgrade games sbin README gnu secure # mount -o union /dev/da0s1f /usr/src # ls -l /usr/src total 1 drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys # umount /usr/src # uname -a FreeBSD shirt.www.demon.net 3.1-STABLE FreeBSD 3.1-STABLE #6: Thu Feb 18 02:26:59 GMT 1999 root@shirt.www.demon.net:/usr/src/sys/compile/SHIRT i386 # However, on another machine running 3.0-RELEASE mount -o union works as expected: # ls -l total 6 drwxr-xr-x 2 root wheel 512 Feb 18 16:36 da1 drwxr-xr-x 2 root wheel 512 Dec 11 11:06 da2 # mount /dev/da1s1e da1 # mount /dev/da2s1e da2 # ls -l da?/* -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da2/this_is_da2 # umount da2 # mount -o union /dev/da2s1e /www/da1 # ls -l da?/* -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da2 # Shirt's kernel configuration is below. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net machine "i386" cpu "I686_CPU" ident SHIRT maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_NOSERVER #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem #options "CD9660" #ISO 9660 Filesystem #options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NETALIAS options NETBIND options SOFTUPDATES options "MAXMEM=(64*1024)" options PQ_MEDIUMCACHE options INCLUDE_CONFIG_FILE options PERFMON options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_DEFAULT_TO_ACCEPT options ICMP_BANDLIM options DUMMYNET config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM controller ncr0 controller scbus0 device da0 device pass0 device cd0 #Only need one of these, the code dynamically grows # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver #pseudo-device splash #options VM86 #options VESA # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # serial port device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel port device ppc0 at isa? port? net irq 7 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device tl0 device tx0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 13:53:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35]) by hub.freebsd.org (Postfix) with ESMTP id 7C2AD11FAB for ; Wed, 24 Feb 1999 13:37:28 -0800 (PST) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.2/8.7) id XAA38737 for current@freebsd.org; Wed, 24 Feb 1999 23:26:42 +1030 (CST) Date: Wed, 24 Feb 1999 23:26:42 +1030 (CST) From: Mark Newton Message-Id: <199902241256.XAA38737@atdot.dotat.org> To: current@freebsd.org Subject: HEADS UP: struct proc changing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While everyone is hob-nobbing at USENIX I thought I'd take the opportunity to make a gratuitous change to the proc structure. I'll be adding a pointer to the end of it which can be used by emulators for storing process-related emulator-specific information. It'll initially be used for storing information related to signal context state in the SysVR4 emulator, but there's no reason other emulators can't use it to hook into state data they need to store on a process-by-process base. I'll commit it tomorrow; You'll need to rebuild libkvm and any statically linked binaries which are linked against libkvm (or just do a make world). Cheers, - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 13:53:59 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 495C911C06 for ; Wed, 24 Feb 1999 13:40:17 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id BAA10360; Wed, 24 Feb 1999 01:26:43 -0500 (EST) (envelope-from luoqi) Date: Wed, 24 Feb 1999 01:26:43 -0500 (EST) From: Luoqi Chen Message-Id: <199902240626.BAA10360@lor.watermarkgroup.com> To: dyson@iquest.net Subject: Re: Filesystem deadlock Cc: freebsd-current@FreeBSD.org, tegge@fast.no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen said: > > > > > Do you still have that piece of code? Does it handle the case involves more > > than one process? For example, process 1 mmaps file B and reads file A into > > the mmapped region, while process 2 mmaps file A and reads file B, this could > > also result in a deadlock. > > > It used to be part of the tree, but I seem to remember that it was removed > (by those who understand the code :-)) soon after I left. I will look for > it, and see if it would help with the problem(s). > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > I have some thoughts on how to solve this problem. A deadlock can occur when you read into a mmapped region or write from a mmapped region, a solution to this problem must be able to handle both cases. For the first case (read), (as originally suggested by Tor Egge), we could allow vm_fault's shared lock attempt to succeed even if there's already a process waiting for the exclusive lock. This is unlikely to create any starvation problem. For the second case (write), it's trickier if there're two processes involved. My solution is not to use exclusive lock for write, because in most cases we don't need to lock the vnode exclusively, except when disk block allocation is required. We could instead perform a lock upgrade before and a downgrade after the block allocation, so the process will only hold a shared lock when copying from the mmapped address, and thus deadlock can be avoided just as in the first case. Comments? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:11: 9 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 0F7D4123C0 for ; Wed, 24 Feb 1999 14:07:21 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA62896; Wed, 24 Feb 1999 08:51:03 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 24 Feb 1999 08:51:03 +0000 (GMT) From: Doug Rabson To: Nicolas Souchu Cc: current@freebsd.org Subject: Re: kernel build failure at nfs_serv.c In-Reply-To: <19990223225615.15493@breizh.teaser.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Feb 1999, Nicolas Souchu wrote: > Hi folks, > > Updating at Mar 23 fév 1999 22:52:33 CET, > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_serv.c > ../../nfs/nfs_serv.c:103: `sysctl__vfs_nfs_children' undeclared here (not in a function) > ../../nfs/nfs_serv.c:103: initializer element for `sysctl___vfs_nfs_async.oid_parent' is not constant > *** Error code 1 > > Stop. > > Any clue? I think this is fixed - try updating nfs_serv.c -- 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 Wed Feb 24 14:13: 9 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 1726512204 for ; Wed, 24 Feb 1999 14:07:21 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA62889; Wed, 24 Feb 1999 08:48:17 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 24 Feb 1999 08:48:17 +0000 (GMT) From: Doug Rabson To: Joel Ray Holveck Cc: Mike Smith , current@freebsd.org Subject: Re: NFS Problems In-Reply-To: <86btikdiie.fsf@detlev.UUCP> 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 23 Feb 1999, Joel Ray Holveck wrote: > >> This reminds me; do we have a utility to reference wmesg strings back > >> to the code that sets them, a la TAGS? Would this be useful? > > No, and yes respectively. > > I have the scanner mostly written; there is one bug yet to fix (This > time for sure!). Presently, it creates a single file WTAGS which > contains an easily-read (my man or machine) flat file index. I will > presently be modifying it to generate Emacs's etags format, as well as > ctags, and as soon as I learn it, GSYMS format. > > At the moment, the scanner scans tsleep, asleep, and ttysleep calls. > What other sleep functions can have the wchan specified as a string > literal? There being no robust manner to handle calls with a computed > or dereferenced wchan, such as acquire(), I will allow for a notation > of /* WCHAN: foo */ to cause the appropriate information to be added > to the database. lockinit() takes a wmesg string which is used when a process sleeps on the lock. -- 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 Wed Feb 24 14:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id E475C12313 for ; Wed, 24 Feb 1999 14:09:22 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.2/8.7.3) id KAA38608; Wed, 24 Feb 1999 10:08:28 +0100 (MET) Message-ID: <19990224100828.A37788@cons.org> Date: Wed, 24 Feb 1999 10:08:28 +0100 From: Martin Cracauer To: mi@aldan.algebra.com, current@FreeBSD.ORG Subject: Re: sh(1) -- exec vs. fork References: <199902191644.LAA08791@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199902191644.LAA08791@misha.cisco.com>; from Mikhail Teterin on Fri, Feb 19, 1999 at 11:43:59AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199902191644.LAA08791@misha.cisco.com>, Mikhail Teterin wrote: > I just finished going through a couple of crontabs prepending the > command-lines with ``exec'', when it hit me. > > Can shell itself recognize, there will be no more commands and just > proceed to exec without forking? What would this break? > > This should never, of course, happen in interactive mode... > > The shell's source requires studying, but, may be, a knowledgeable > person can answer right away? FreeBSD's /bin/sh does a forkless exec in some cases, which is why we have the echo -n in /etc/rc: (trap 'exit 1' 2 ; ${script} start ; echo -n) The problem with not forking is that trap handling is being broken. Currently, our /bin/sh eliminates one instance when subshells are started with '(...)', the last command in the brackets is just exec'ed without fork. Example: #! /bin/sh echo $$ ( echo $$ cat ) The subshell replaces the outer instances, the pids echoed are the same. But this will break asynchronous traps (which are not Posix, BTW), hence it doesn't do this for the outermost shell of a shell script: #! /bin/sh echo $$ cat The outer shell still exists when cat is exec'ed. Obviously, while this inconsistent behaviour gets most cases right, it isn't perfect, as seen in the /etc/rc hack above. What is needed here is that the process elimination happens only when no traps are set. I looked into this in September (with help from Tor Egge), we need a count of active traps and if traps are active, don't do subshell elimination. The problem here is that counting active traps isn't that easy. Also, this would only solve the lower half of the problem, that too much elimination happens for subshells. The upper half, that elimination could/should happen for toplevel shells when the last command of a script is being exectued needs more thought. I feel uncomfortable having a shellscript running without a handle to the toplevel controlling shell process. For example, you might want to use it get the whole process group of everything it started. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id DBACA12307 for ; Wed, 24 Feb 1999 14:09:22 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.2/8.7.3) id KAA38684; Wed, 24 Feb 1999 10:11:04 +0100 (MET) Message-ID: <19990224101104.B37788@cons.org> Date: Wed, 24 Feb 1999 10:11:04 +0100 From: Martin Cracauer To: dyson@iquest.net, =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG Subject: Re: Promise IDE board docs References: <199902221949.UAA63198@freebsd.dk> <199902230725.CAA02636@y.dyson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.1i In-Reply-To: <199902230725.CAA02636@y.dyson.net>; from John S. Dyson on Tue, Feb 23, 1999 at 02:25:44AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199902230725.CAA02636@y.dyson.net>, John S. Dyson wrote: > Søren Schmidt said: > > > > It "should" work, but the promise support in the old system is, well, > > hacky at best. I'm not sure if Promise supports more than one card > > at a time, but from looking at the chip specs, it should work just > > fine, and if the hardware works, at least the new driver will support > > it. > > > I run with two (2) boards, but it appears that certain (all?) versions > of the bios require that you remove the chip from all but one board. I did run such a setup as well, but the disks on the first controller with BIOS ran much faster than those on the BIOSless controller. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:14:57 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 6EAE812294 for ; Wed, 24 Feb 1999 14:10:53 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-04.iptelecom.net.ua [212.42.68.132]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA22930 for ; Wed, 24 Feb 1999 10:36:25 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA06085 for ; Wed, 24 Feb 1999 10:35:58 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36D3B9BF.5723CAFC@altavista.net> Date: Wed, 24 Feb 1999 10:35:11 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Strange routing to www.freebsd.org ;) Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm today discovered strange routing to www.freebsd.org sh$ traceroute www.freebsd.org [...] 15  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  698.413 ms  608.198 ms  578.823 m s 16  R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)  609.090 ms  598.030 ms  599.085 ms 17  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  978.255 ms  608.167 ms  578.853 m s 18  R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)  598.453 ms  598.058 ms  608.966 ms 19  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  618.394 ms  598.144 ms  589.037 m s 20  R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)  598.230 ms  608.151 ms  748.804 ms 21  T1-CDROM-00-EX.US.CRL.NET (165.113.118.2)  608.493 ms  618.058 ms  638.848 m s [etc to infinity] What the matter? Maxim Sobolev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:15:35 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 70F22120A4 for ; Wed, 24 Feb 1999 14:11:21 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA66939; Wed, 24 Feb 1999 10:31:46 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902240931.KAA66939@freebsd.dk> Subject: Re: Promise IDE board docs In-Reply-To: <19990224101104.B37788@cons.org> from Martin Cracauer at "Feb 24, 1999 10:11: 4 am" To: cracauer@cons.org (Martin Cracauer) Date: Wed, 24 Feb 1999 10:31:46 +0100 (CET) Cc: dyson@iquest.net, gallatin@cs.duke.edu, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Martin Cracauer wrote: > In <199902230725.CAA02636@y.dyson.net>, John S. Dyson wrote: > > Søren Schmidt said: > > > > > > It "should" work, but the promise support in the old system is, well, > > > hacky at best. I'm not sure if Promise supports more than one card > > > at a time, but from looking at the chip specs, it should work just > > > fine, and if the hardware works, at least the new driver will support > > > it. > > > > > I run with two (2) boards, but it appears that certain (all?) versions > > of the bios require that you remove the chip from all but one board. > > I did run such a setup as well, but the disks on the first controller > with BIOS ran much faster than those on the BIOSless controller. Hmm, which suggests that I need to leave the "do it by hand" code in there and recommend removing the BIOS :( -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:17:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (Postfix) with ESMTP id 563F012096 for ; Wed, 24 Feb 1999 14:13:41 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.3/8.9.1) with ESMTP id NAA01119 for ; Wed, 24 Feb 1999 13:49:12 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 24 Feb 1999 13:49:12 -0500 (EST) From: "Alok K. Dhir" To: current@freebsd.org Subject: Staroffice 5.01? 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 Has anyone gotten SO501 to run on -current? Thx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 14:46:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 1854810FA3 for ; Wed, 24 Feb 1999 14:46:47 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id JAA19646 for ; Wed, 24 Feb 1999 09:29:18 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma019642; Wed, 24 Feb 99 09:29:18 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA03766 for ; Wed, 24 Feb 1999 09:29:15 +0100 (MET) Received: (qmail 9913 invoked by uid 666); 24 Feb 1999 08:29:35 -0000 Date: Wed, 24 Feb 1999 09:29:35 +0100 From: Jos Backus To: Dmitrij Tejblum Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free Message-ID: <19990224092935.A9904@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902230909.MAA01169@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Tue, Feb 23, 1999 at 12:09:03PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 23, 1999 at 12:09:03PM +0300, Dmitrij Tejblum wrote: > You could add -DINVARIANTS to CFLAGS in sys/module/msdosfs/Makefile. OK, did that, no more panics. Thanks! > Dima 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 Wed Feb 24 14:51:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 07DC9110A4 for ; Wed, 24 Feb 1999 14:51:39 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id XAA04899; Wed, 24 Feb 1999 23:51:18 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.2/8.8.8) id XAA09435; Wed, 24 Feb 1999 23:51:17 +0100 (CET) Message-ID: <19990224235117.A9283@enst.fr> Date: Wed, 24 Feb 1999 23:51:17 +0100 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: IDE CDROM not found with PIIX4 chipset, -current kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having problems with an IDE controller on my motherboard. I can't seem to be able to get it to recognize a CDROM drive (it's the only device plugged on the second IDE controller). The kernel seems to timeout on that second controller during the probe phase. Maybe that's one of the infamous PIIX 4 bugs... The machine is a Dell Optiplex. The first weird thing is that the CDROM drive is found if I plug another IDE drive as slave on the second controller. The second weird thing is that it's recognized perfectly correctly if I boot a Linux installation disk... So I assume they found a workaround, if that's a PIIX 4 bug. I've tried to change the device flags (with and without DMA), to no avail. I've followed every recent patch to the IDE code, none of these seems to help (the last kernel I tried is a 4.0-current from Monday). Here's my dmesg: ide_pci0: rev 0x01 on pci0.7.1 ... wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa ... then nothing, it times out after a while and goes on with the boot, no CDROM is ever found. Here's an excerpt from my kernel config. Did I miss something obvious? controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 15: 3:17 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 300B3113D3 for ; Wed, 24 Feb 1999 15:02:42 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10FnIk-0002z3-00; Thu, 25 Feb 1999 01:01:10 +0200 From: Sheldon Hearn To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Wed, 24 Feb 1999 23:51:17 +0100." <19990224235117.A9283@enst.fr> Date: Thu, 25 Feb 1999 01:01:09 +0200 Message-ID: <11472.919897269@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Feb 1999 23:51:17 +0100, Pierre Beyssac wrote: > Here's an excerpt from my kernel config. Did I miss something obvious? > > controller wdc0 [...] > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > controller wdc1 [...] > disk wd2 at wdc1 drive 0 > disk wd3 at wdc1 drive 1 > > options ATAPI #Enable ATAPI support for IDE bus > options ATAPI_STATIC #Don't do it as an LKM > device acd0 #IDE CD-ROM Um... Do you really have 4 wd devices plugged in? If so, where on earth are you plugging the CDROM device in? :) Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM device on your primary IDE controller. So you'd do something like: controller wdc0 controller wdc1 disk wd0 at wdc0 drive 0 disk wd1 at wdc1 drive 0 disk wd2 at wdc1 drive 1 ...followed by your acd device, naturally. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 15:42:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id D37A914BD4 for ; Wed, 24 Feb 1999 15:41:53 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id PAA01398 for ; Wed, 24 Feb 1999 15:41:42 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199902242341.PAA01398@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: CVS and Y2K In-reply-to: Your message of "Tue, 23 Feb 1999 21:20:13 MST." <199902240420.VAA13186@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Feb 1999 15:41:42 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does FreeBSD still ship with CVS version 1.9.26? If so it needs to be > > upgraded within the next 9 months or so. 1.9.26 can't parse dates > > past 1999-12-31. > > Have you verified this? from http://www.cyclic.com/cvs/info-y2k.html: Do not plan to continue to use CVS 1.9 or older beyond the year 2000. Such versions of CVS have known bugs in their ability to handle dates beyond 2000. These bugs are fixed in CVS 1.10, and we recommend an upgrade to CVS 1.10 some time before the year 2000. ( 4.0-current as of yesterday ) [15:36:04]102<0> cvs -v Concurrent Versions System (CVS) 1.9.26 (client/server) bummer... -- obfuscate v.t. darken; obscure; bewilder. int i;main(){for(;i["]; Wed, 24 Feb 1999 16:05:06 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id BAA03200; Thu, 25 Feb 1999 01:04:48 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.2/8.8.8) id BAA00460; Thu, 25 Feb 1999 01:04:48 +0100 (CET) Message-ID: <19990225010448.A335@enst.fr> Date: Thu, 25 Feb 1999 01:04:48 +0100 From: Pierre Beyssac To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <19990224235117.A9283@enst.fr> <11472.919897269@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <11472.919897269@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Feb 25, 1999 at 01:01:09AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote: > > controller wdc1 [...] > > disk wd2 at wdc1 drive 0 > > disk wd3 at wdc1 drive 1 > > Um... Do you really have 4 wd devices plugged in? Uh, well, no, just 2 (on the first IDE controller). > Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM > device on your primary IDE controller. So you'd do something like: Wow. Thanks a million! I didn't even have to go so far, I just deleted wd2 and wd3 and acd0 now appears as if by magic. I can't tell you how extremely stupid I now feel... OTOH, I copied this from the GENERIC kernel config file, assuming it recognizes an ATAPI CDROM when it finds one. So my puzzled question is now: how can the GENERIC kernel work in that case, since it declares wd[0-3] ? -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 16:36: 1 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 E7E7C14C1D for ; Wed, 24 Feb 1999 16:35:11 -0800 (PST) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id TAA29279; Wed, 24 Feb 1999 19:33:09 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: sos@freebsd.dk (Søren Schmidt) Cc: current@freebsd.org Subject: Re: Promise IDE board docs Date: Thu, 25 Feb 1999 00:41:19 GMT Message-ID: <36d49bf8.1109180096@mail.sentex.net> References: <19990224101104.B37788@cons.org> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote: > >Hmm, which suggests that I need to leave the "do it by hand" code in >there and recommend removing the BIOS :( Are there any plans to support the Promise Fast Trak IDE RAID controller ? ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 16:56:33 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 88F1414C2F for ; Wed, 24 Feb 1999 16:56:23 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA29163; Thu, 25 Feb 1999 11:25:42 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: Thu, 25 Feb 1999 11:25:42 +1030 (CST) From: "Daniel O'Connor" To: "Alok K. Dhir" Subject: RE: Staroffice 5.01? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Feb-99 Alok K. Dhir wrote: > Has anyone gotten SO501 to run on -current? I have and its quite good, but it hangs occasionally.. The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..) What problems are you having? --- 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 Wed Feb 24 17:18:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 1C0A714CEA for ; Wed, 24 Feb 1999 17:18:09 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 162 invoked from network); 24 Feb 1999 16:17:52 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 24 Feb 1999 16:17:52 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id LAA06563; Wed, 24 Feb 1999 11:17:52 -0500 (EST) Message-Id: <199902241617.LAA06563@y.dyson.net> Subject: Re: Promise IDE board docs In-Reply-To: <19990224101104.B37788@cons.org> from Martin Cracauer at "Feb 24, 99 10:11:04 am" To: cracauer@cons.org (Martin Cracauer) Date: Wed, 24 Feb 1999 11:17:52 -0500 (EST) Cc: dyson@iquest.net, sos@freebsd.dk, gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 Martin Cracauer said: > In <199902230725.CAA02636@y.dyson.net>, John S. Dyson wrote: > > Søren Schmidt said: > > > > > > It "should" work, but the promise support in the old system is, well, > > > hacky at best. I'm not sure if Promise supports more than one card > > > at a time, but from looking at the chip specs, it should work just > > > fine, and if the hardware works, at least the new driver will support > > > it. > > > > > I run with two (2) boards, but it appears that certain (all?) versions > > of the bios require that you remove the chip from all but one board. > > I did run such a setup as well, but the disks on the first controller > with BIOS ran much faster than those on the BIOSless controller. > The order of the boards is critical, and which bios is installed. Of course, YMMV. Each drive on each controller in my case runs at full speed :-). On the bootup sequence, I get one BIOS display of eight drive slots, as if I am using one board, with 8 drive positions (even though I really have two boards.) Of course, the PCI bus probes the controllers as two controllers, but the BIOS kind of acts like one logical controller. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 18: 8:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 9FE5714BE9; Wed, 24 Feb 1999 18:08:38 -0800 (PST) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id DAA24627; Thu, 25 Feb 1999 03:08:21 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <36D4B092.8B076D55@partitur.se> Date: Thu, 25 Feb 1999 03:08:18 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org Subject: panic: aha0 Invalid CCB or SG list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Sorry for the crosspost, but I'd like to now if this is fixed in -current) Hi! I've seen three crashes in the last couple of weeks, with a server box that's been running stable as a rock for two years, at least. It has an adaptec 2940UW with six disks, and an adaptec 1542CP that's connected to a seagate travan tape driver. It's running STABLE-3.1 from Feb 19 1999, and since the last upgrade, I've seen three crashes, all related to dumping to tape. Since I got no info on what happened, I decided to sit down with the machine, run a backup sequence to tape, and wait for it to possibly crash. After 90 minutes, I was about to give up when suddenly, poof: panic: aha0 Invalid CCB or SG list. So, it's probably the 1540 driver (or hardware)? Can anybody shed some light on what to do? Is it software? That's my guess, since the machine never ONCE has crashed until the upgrade to 3.x. I had one crash when running current form beginning of January (soon after moving to 3.x), and now theese three in a week. The 1540 has been in the machine for about six months. Before starting the panicking backup, I spawned off a few logs: netstat -I de0 -w 5 and vmstat -p sa -p da -w 5 I'm not sure how to interpret them, but there's an excerpt at the end of this mail of the vmstat output (it stops in the middle of a row, when the crash occurred). The backups are made with amanda (see the ports collection), and uses gzip, hence the outbursts of cpu load. The netstat seems pretty uninteresting; quite normal. If there's anything I can do to help debug I'll do it, but device drivers are a little above my level of expertise. Thanks in advance! /Palle Here's a 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.1-STABLE #0: Fri Feb 19 23:35:59 CET 1999 girgen@tb303.partitur.se:/usr/src/sys/compile/TRUMPET Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 198948269 Hz CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff real memory = 201326592 (196608K bytes) avail memory = 192790528 (188272K bytes) Preloaded elf kernel "kernel" at 0xf02b5000. Probing for devices on PCI bus 0: Correcting Natoma config for non-SMP chip0: rev 0x02 on pci0.0.0 chip1: rev 0x00 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 de0: rev 0x20 int a irq 12 on pci0.11.0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:27:eb:e9 vga0: rev 0x54 int a irq 9 on pci0.12.0 ahc0: rev 0x00 int a irq 11 on pci0.13.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs 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 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdreset: error1: 0x0 wdreset: error1: 0x0 wdc0 not found at 0x1f0 aha0 at 0x330-0x333 irq 10 drq 7 on isa aha0: AHA-1542CP FW Rev. D.0 (ID=46) SCSI Host Adapter, SCSI ID 7, 16 CCBs vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 5 seconds for SCSI devices to settle de0: enabling 100baseTX port sa0 at aha0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.333MB/s transfers (3.333MHz, offset 8) da4 at ahc0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) changing root device to da0s1a da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) WARNING: / was not properly dismounted ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates --------------- # and here's the kernel config: machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident TRUMPET maxusers 150 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MFS_ROOT #MFS usable as root device, "MFS" req'ed options EXPORTMFS options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem #options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #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 NETATALK #options PQ_LARGECACHE # color for 512k/16k cache options INCLUDE_CONFIG_FILE # Include this file in kernel options "NO_F00F_HACK" #This is not a Pentium options SOFTUPDATES config kernel root on da0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ahc0 controller aha0 at isa? port ? cam irq ? controller scbus0 device da0 device sa0 options "SA_SPACE_TIMEOUT=(2*60)" options "SA_REWIND_TIMEOUT=(2*60)" options "SA_ERASE_TIMEOUT=(4*60)" device pass0 # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at isa? port "IO_NPX" irq 13 device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # parallell port controller ppbus0 device nlpt0 at ppbus? device psm0 at isa? port "IO_KBD" conflicts tty irq 12 device de0 #device fxp0 #device vx0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's options SYSVSEM options SYSVSHM options SYSVMSG options "SHMMAXPGS=9000" pseudo-device bpfilter 4 #Berkeley packet filter the result of vmstat -p sa -p da -w 5: procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 7 0 13560 23524 2 0 0 0 1 0 222 0 0 573 3857 1968 76 15 9 1 7 0 14396 21028 8 0 0 0 7 0 224 0 0 535 3942 1837 65 16 19 1 7 0 14608 18604 2 0 0 0 0 0 218 0 0 534 3801 1877 67 13 20 1 5 0 15088 16108 9 0 0 0 7 0 187 0 0 506 3331 1745 62 12 27 3 6 0 15320 13716 2 0 0 0 0 0 209 0 0 552 3716 1905 63 15 22 3 5 0 15620 10768 2 0 0 0 1 0 200 0 0 490 3532 1854 72 17 12 4 4 0 15320 8228 31 0 1 0 36 0 184 0 0 490 4316 1656 65 13 22 1 5 0 15448 9588 3 0 0 0 1 249 178 0 0 521 3160 1819 79 17 4 1 5 0 13600 10256 66 0 1 0 59 209 147 1 0 484 3144 1564 72 17 11 2 6 0 13536 7312 18 0 0 0 8 0 159 0 0 462 3824 1598 64 13 23 0 7 0 14868 10324 54 0 0 0 38 249 155 0 0 457 3114 1379 42 12 46 3 4 0 16004 7016 30 0 0 0 0 0 177 0 0 526 3777 1722 55 14 31 1 5 0 15496 8412 9 0 0 0 9 249 199 0 0 552 3458 1854 74 16 10 1 7 0 15496 11152 13 0 0 0 12 249 183 0 0 513 3210 1698 50 15 35 1 5 0 15708 8688 9 0 0 0 9 0 185 0 0 507 3222 1706 58 13 29 5 4 0 13352 8016 13 0 0 0 12 0 211 0 0 541 4085 2211 21 12 67 4 4 0 15768 6836 18 0 0 0 39 0 207 0 0 531 4726 1930 43 13 44 1 7 0 15600 10168 6 0 1 0 7 250 173 0 0 501 3091 1626 38 12 50 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 0 8 0 14676 8368 1 0 0 0 0 0 171 0 0 466 3141 1697 42 11 47 2 6 0 14676 10576 6 0 0 0 7 249 202 0 0 513 3575 1753 69 15 16 4 4 0 13928 7988 18 0 0 0 1 0 185 0 0 500 3285 1717 54 15 31 1 7 0 13772 6708 1 0 0 0 0 0 152 0 0 511 2698 1518 29 10 61 1 5 0 14004 9864 1 0 0 0 1 249 166 0 0 488 2932 1561 40 11 49 4 4 0 11816 8520 1 0 0 0 0 0 137 0 0 484 2438 1365 25 9 66 0 8 0 12148 6608 1 0 0 0 1 0 134 0 0 443 2414 1403 38 12 50 3 4 0 11980 9504 1 0 0 0 0 249 154 0 0 458 2701 1462 45 11 44 1 5 0 12492 10952 1 0 0 0 0 225 191 0 0 500 3383 1809 72 16 12 1 5 0 12972 7280 1 0 0 0 1 0 183 0 0 512 3231 1800 81 19 0 2 5 0 14372 8672 1 0 0 0 0 249 183 0 0 520 3251 1814 84 15 1 3 5 0 14372 10104 1 0 0 0 0 249 183 0 0 494 3220 1762 84 15 1 2 5 0 13148 6552 1 0 0 0 0 0 176 0 0 485 3109 1767 82 16 2 1 7 0 13148 8424 1 0 0 0 0 250 184 0 0 475 3231 1769 71 13 15 1 8 0 13208 11040 2 0 0 0 16 249 186 0 0 450 3308 1666 48 14 38 2 7 0 13484 7164 1 0 0 0 0 0 191 0 17 458 3548 1703 42 17 41 4 4 0 14368 7560 1 0 0 0 0 252 207 1 18 482 3829 1733 56 19 25 0 8 0 14368 6572 1 0 0 0 1 253 167 1 18 447 3142 1715 74 21 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 8 0 13900 7300 1 0 0 0 1 252 157 0 18 426 3055 1544 41 17 42 1 7 0 13900 7728 1 0 0 0 1 250 178 0 18 461 3485 1689 44 19 37 3 7 0 13460 8952 1 0 0 0 0 250 195 0 18 456 3720 1813 36 14 50 2 7 0 13940 10544 1 0 0 0 1 249 174 0 12 465 3194 1609 43 17 41 1 7 0 14524 7384 1 0 0 0 1 0 170 0 8 417 3095 1561 53 15 31 1 9 0 14824 8384 1 0 0 0 0 249 156 0 18 416 2963 1482 33 18 49 0 9 0 14752 10192 1 0 0 0 1 250 199 0 18 492 3988 2012 23 17 60 0 9 0 13964 6836 1 0 0 0 0 0 210 0 18 469 4218 2123 27 18 55 2 8 0 13016 8604 1 0 0 0 1 250 209 0 18 661 4203 2307 27 17 56 3 6 0 12716 9568 1 0 0 0 1 205 192 0 18 496 3955 2122 21 14 65 2 7 0 12576 10544 1 0 0 0 1 202 192 1 18 496 3949 2090 23 14 64 1 7 0 12996 8428 1 0 0 0 0 0 196 0 14 444 3703 1871 50 17 33 2 7 0 13328 6804 1 0 0 0 1 0 190 0 0 434 3484 1799 50 15 35 3 5 0 13328 9400 1 0 0 0 0 249 198 1 0 538 3419 1862 71 15 15 1 7 0 13540 47520 1 0 0 0 2023 0 173 0 0 535 2885 1689 60 15 24 2 7 0 12228 47096 21 0 2 0 20 0 96 0 0 335 1804 932 14 8 79 0 8 0 14300 45400 1 0 0 0 0 0 146 0 0 390 2634 1426 42 12 46 2 4 0 14300 43744 1 0 0 0 0 0 190 0 0 442 3377 1763 48 14 39 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 3 4 0 13556 41908 1 0 0 0 0 0 188 0 0 452 3298 1631 51 14 35 1 6 0 13076 40540 1 0 0 0 1 0 167 1 0 497 3016 1669 42 11 47 2 6 0 11140 39564 1 0 0 0 0 0 148 1 0 542 2615 1589 27 11 61 1 7 0 11140 38308 1 0 0 0 1 0 189 1 0 435 3409 1712 41 14 45 0 7 0 11744 36996 8 0 0 0 8 0 161 0 0 413 2939 1546 38 10 52 1 8 0 15456 35028 135 0 4 0 140 0 123 1 0 559 3471 1273 28 12 60 2 7 0 15620 32648 1 0 0 0 0 0 0 1 15 1990 3691 1850 6 19 75 0 9 0 15620 29692 1 0 0 0 0 0 0 0 18 1422 2596 1289 4 14 81 3 7 0 16648 26612 9 0 1 0 1 0 2 0 18 540 842 390 1 8 91 1 8 0 11684 23796 9 0 0 0 16 0 1 0 18 561 889 404 1 8 91 1 8 0 14036 20848 4 0 0 0 4 0 1 0 18 558 857 404 1 7 92 1 8 0 13164 17960 1 0 0 0 0 0 1 0 18 538 814 376 1 7 91 1 8 0 11640 15020 1 0 0 0 1 0 2 0 18 535 781 383 1 8 90 1 8 0 9908 12124 1 0 0 0 0 0 0 0 18 474 671 321 1 7 93 010 0 9256 8100 1 0 0 0 0 0 1 0 18 441 521 288 1 5 94 1 8 0 9424 9264 1 0 0 0 0 249 0 1 18 451 517 298 1 6 93 3 6 0 9656 11344 1 0 0 0 1 252 1 1 18 431 592 277 5 7 87 2 9 0 15776 7204 55 0 1 0 7 0 1 0 18 465 2907 1754 18 13 69 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 2 7 0 16876 10056 54 0 0 0 1 251 0 1 5 448 3551 1676 11 12 77 0 6 0 14628 8896 14 0 0 0 99 0 0 0 17 314 9091 445 80 9 11 1 8 0 15108 8720 2 0 0 0 1 249 0 0 18 429 2817 1382 56 16 28 1 6 0 15108 8528 1 0 0 0 0 249 0 2 18 519 4204 1944 72 22 6 3 6 0 16232 8320 1 0 0 0 1 255 1 1 18 516 4381 1905 74 21 5 1 6 0 16052 8160 1 0 0 0 0 250 1 0 18 526 4543 2031 71 20 9 1 6 0 15128 7952 1 0 0 0 1 253 0 0 18 536 4625 2024 71 24 5 2 7 0 13396 8560 1 0 0 0 0 253 0 0 18 531 3598 1692 48 19 33 5 3 0 13096 9248 2 0 0 0 1 252 0 1 18 541 3680 1703 45 16 40 1 6 0 13096 9232 1 0 0 0 0 249 0 1 18 521 4385 1932 66 22 12 4 5 0 13980 9592 1 0 0 0 1 250 1 1 18 534 4180 1854 55 20 25 1 7 0 13980 10464 1 0 0 0 1 254 0 0 18 503 3808 1749 40 16 44 6 4 0 14312 10384 1 0 0 0 0 255 0 0 18 488 3727 1841 61 18 21 3 6 0 13096 10640 1 0 0 0 1 250 0 0 18 532 4238 1898 57 20 24 1 6 0 14352 9840 1 0 0 0 1 251 0 0 18 477 3492 1879 63 22 15 1 8 0 15520 9456 1 0 0 0 1 249 0 0 18 482 3470 1803 56 22 21 1 6 0 16092 10224 5 0 0 0 4 249 1 0 18 573 4353 1921 45 17 37 1 6 0 16932 9712 1 0 0 0 0 249 0 8 18 479 3184 1657 62 18 20 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 16040 9936 1 0 0 0 0 249 0 0 18 569 4936 2127 61 21 18 3 5 0 14308 8280 1 0 0 0 1 251 0 1 18 436 3118 1807 77 23 0 1 6 0 13936 8404 12 0 0 0 6 251 1 0 7 420 2990 1789 81 19 0 2 6 0 13096 7464 1 0 0 0 0 250 0 0 14 421 2999 1767 77 23 0 3 5 0 13328 10848 1 0 0 0 1 501 2 0 18 442 3077 1826 76 24 0 1 6 0 14296 9116 1 0 0 0 0 249 1 1 18 441 3065 1748 77 23 0 1 8 0 14628 7304 1 0 0 0 0 249 0 0 18 438 3153 1846 77 23 0 1 6 0 14064 10472 1 0 0 0 1 499 0 2 18 452 3230 1872 76 24 0 1 6 0 15620 8644 1 0 0 0 0 249 0 0 18 442 3222 1861 76 24 0 2 6 0 15948 6680 1 0 0 0 0 249 0 0 18 445 3215 1880 80 20 0 4 5 0 16520 9736 3 0 0 0 2 498 0 0 18 442 3240 1847 78 22 0 1 8 0 16520 7800 1 0 0 0 0 250 1 0 18 453 3265 1910 78 22 0 1 6 0 15328 10944 1 0 0 0 1 500 0 0 18 455 3217 1889 76 24 0 2 5 0 13596 9040 1 0 0 0 0 250 0 0 18 453 3253 1854 78 22 0 1 6 0 13224 7136 1 0 0 0 0 249 0 0 18 446 3241 1847 74 26 0 1 6 0 13224 10248 1 0 0 0 1 498 0 0 18 447 3231 1872 74 26 0 3 4 0 13456 8304 1 0 0 0 0 249 0 1 18 475 3242 1906 77 23 0 1 8 0 13792 11184 1 0 0 0 1 498 1 1 18 476 3206 1871 80 20 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 2 7 0 14124 9320 1 0 0 0 1 249 0 0 18 461 3261 1929 77 23 0 1 6 0 13560 7416 1 0 0 0 0 249 0 0 18 447 3213 1866 77 22 0 1 6 0 14816 10440 31 0 2 0 22 498 3 0 18 452 3218 1862 77 23 0 1 6 0 16212 8512 1 0 0 0 0 249 0 0 18 462 3236 1864 77 22 0 1 6 0 16852 7824 2 0 0 0 1 249 2 0 9 443 3252 1914 82 18 0 1 6 0 16852 8488 1 0 0 0 1 249 1 0 1 434 3236 1930 83 17 0 2 5 0 15628 6608 1 0 0 0 0 250 2 0 18 449 3238 1873 76 24 0 1 6 0 13896 9728 1 0 0 0 1 499 0 0 18 445 3181 1874 77 23 0 2 6 0 16180 11344 49 0 2 0 11 498 2 1 18 488 3462 1788 75 24 2 1 6 0 15376 9328 8 0 0 0 42 249 2 1 18 480 3775 1858 74 24 2 3 4 0 15044 7764 52 0 1 0 47 249 1 1 18 445 4135 1723 73 26 2 1 6 0 15044 11216 1 0 0 0 2 502 2 0 18 453 2974 1715 69 24 7 2 6 0 15036 9480 1 0 0 0 0 249 1 0 18 447 3093 1769 74 23 3 1 6 0 16092 7312 56 0 1 0 24 251 1 1 18 440 4371 1874 73 27 0 1 7 0 15864 6680 55 0 1 0 79 250 0 1 18 448 4002 1674 68 25 6 1 6 0 16760 10328 1 0 0 0 1 499 1 0 18 471 2826 1677 70 22 8 1 6 0 16428 8584 1 0 0 0 0 249 0 0 18 451 3125 1830 81 19 0 2 6 0 16920 6656 53 0 1 0 14 251 1 2 18 460 3556 1721 72 25 3 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 8 0 15368 10896 4 0 0 0 38 500 1 1 18 428 3437 1743 79 21 1 2 7 0 14472 9496 1 0 0 0 1 249 0 1 18 594 2877 1952 67 26 7 1 6 0 14640 7648 1 0 0 0 0 249 0 1 18 520 3097 1885 73 25 2 1 6 0 14988 10728 1 0 0 0 1 498 0 0 18 479 3205 1895 77 23 0 1 6 0 14720 8812 2 0 0 0 1 249 0 0 18 468 3189 1875 75 24 0 1 6 0 14580 6968 1 0 0 0 1 249 1 1 18 463 3178 1852 76 24 0 2 7 0 14912 10272 1 0 0 0 1 498 0 0 18 570 3049 1996 77 23 0 2 6 0 13696 10432 1 0 0 0 0 249 1 0 5 509 3108 1941 81 19 0 1 6 0 14640 9288 1 0 0 0 1 252 0 1 15 434 3045 1743 78 22 0 4 4 0 16372 7624 1 0 0 0 1 250 0 0 18 429 3059 1728 78 22 0 1 8 0 16040 11000 1 0 0 0 1 498 0 0 18 427 3033 1712 78 22 0 1 6 0 15296 9456 1 0 0 0 0 249 0 0 18 446 3010 1751 76 24 0 1 8 0 14480 7500 1 0 0 0 0 247 1 0 18 437 3188 1836 77 23 0 1 8 0 12748 10672 1 0 0 0 1 501 1 1 18 455 3192 1873 77 23 0 1 6 0 12748 8776 1 0 0 0 1 249 0 0 18 438 3208 1874 76 24 0 1 7 0 13312 6872 1 0 0 0 0 249 0 0 18 438 3207 1851 78 22 0 1 6 0 12980 9968 1 0 0 0 1 500 0 0 18 460 3219 1871 75 25 0 1 6 0 12980 8040 1 0 0 0 0 249 0 1 18 454 3197 1856 76 24 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 4 4 0 13684 11144 2 0 0 0 2 498 1 1 18 440 3231 1824 76 24 0 1 6 0 13120 9240 1 0 0 0 0 249 0 1 18 438 3222 1835 75 25 0 1 6 0 14344 7312 1 0 0 0 0 249 0 0 18 437 3209 1873 77 23 0 1 6 0 16076 10432 1 0 0 0 1 498 0 0 18 459 3202 1882 75 25 0 1 6 0 15704 8412 1 0 0 0 1 249 0 0 18 460 3196 1870 76 24 0 1 6 0 14960 6568 1 0 0 0 0 249 0 0 18 437 3210 1853 73 27 0 2 5 0 14780 9672 1 0 0 0 1 501 1 0 18 437 3197 1844 77 23 0 1 6 0 13048 7768 1 0 0 0 0 249 0 0 18 436 3224 1821 76 24 0 1 6 0 12748 10960 1 0 0 0 1 500 0 0 18 435 3187 1845 77 23 0 1 6 0 13312 10544 1 0 0 0 0 249 0 0 8 431 3211 1907 79 21 0 1 6 0 12980 9248 1 0 0 0 0 249 0 0 14 434 3215 1856 80 20 0 1 7 0 13632 7296 1 0 0 0 1 251 0 0 18 444 3071 1817 78 22 0 2 5 0 13964 10352 1 0 0 0 3 498 1 0 18 446 3113 1800 76 24 0 2 6 0 13400 8512 1 0 0 0 1 249 0 0 18 436 3140 1797 78 22 0 4 4 0 14624 6832 1 0 0 0 0 251 0 0 18 432 3122 1770 79 21 0 2 8 0 15736 10152 1 0 0 0 1 499 0 0 18 428 3072 1721 79 21 0 1 6 0 15404 8664 1 0 0 0 0 249 0 0 18 427 3030 1708 77 23 0 3 6 0 18696 11048 122 0 8 0 19 498 9 2 18 449 3294 1802 75 25 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 18556 9248 3 0 0 0 1 249 3 0 18 434 3225 1820 77 23 0 4 4 0 17828 7456 1 0 0 0 0 249 1 1 18 433 3104 1760 79 21 0 1 6 0 17828 10696 1 0 0 0 1 499 1 1 18 434 3128 1814 77 23 0 1 6 0 13480 9072 1 0 0 0 0 250 0 1 18 458 3096 1847 77 23 0 1 6 0 13148 7400 1 0 0 0 0 251 0 0 18 435 3059 1767 76 24 0 4 3 0 12980 10720 1 0 0 0 1 501 0 0 18 430 3089 1772 79 21 0 3 6 0 13312 8856 1 0 0 0 0 249 0 0 18 435 3183 1831 76 24 0 1 6 0 13524 7056 1 0 0 0 0 249 1 0 18 437 3183 1848 79 21 0 1 6 0 14304 10104 32 0 2 0 24 503 3 0 18 440 3238 1830 75 24 0 1 6 0 16036 8176 1 0 0 0 0 249 1 0 18 437 3194 1815 76 24 0 1 6 0 16036 11320 1 0 0 0 1 498 0 0 18 452 3192 1840 77 23 0 2 6 0 18980 10684 1 0 0 0 1 249 1 0 11 433 3083 1809 79 21 0 1 8 0 18200 10024 1 0 0 0 0 249 0 0 10 434 3188 1879 79 21 0 1 6 0 16636 8336 1 0 0 0 0 251 1 1 18 450 3106 1820 77 23 0 1 6 0 16636 11296 1 0 0 0 1 499 0 0 18 450 2973 1726 77 22 1 1 6 0 14132 9488 1 0 0 0 1 249 0 0 18 437 3174 1821 76 24 0 2 6 0 13800 7856 1 0 0 0 0 250 0 0 18 426 3032 1738 80 20 0 3 5 0 13972 11120 1 0 0 0 1 502 1 0 18 432 3138 1823 76 24 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 14304 9184 1 0 0 0 0 249 1 0 18 437 3207 1867 76 24 0 1 6 0 13864 7312 1 0 0 0 0 249 1 1 18 438 3202 1855 74 26 0 1 7 0 14344 10448 2 0 0 0 1 498 0 0 18 436 3205 1833 78 22 0 2 6 0 15736 8592 1 0 0 0 1 251 0 0 18 436 3195 1870 79 21 0 2 6 0 15704 6980 1 0 0 0 0 250 1 0 18 426 3019 1750 80 20 0 1 6 0 19228 10372 3 0 0 0 12 500 1 0 18 436 3166 1846 76 24 0 1 6 0 19976 7996 31 0 1 0 3 251 7 0 18 437 3716 1778 75 24 1 1 6 0 18792 6716 10 0 0 0 34 251 2 1 18 452 3105 1817 77 23 0 2 5 0 18492 10096 1 0 0 0 1 498 2 0 18 445 3089 1815 77 23 0 1 6 0 15860 8128 69 0 5 0 54 249 2 0 18 437 3178 1641 75 24 1 1 6 0 15364 11364 71 0 1 0 54 498 0 0 18 428 3248 1669 77 23 0 1 6 0 14992 9736 1 0 0 0 1 249 0 0 18 428 3068 1754 79 21 0 3 4 0 15744 10480 1 0 0 0 0 249 3 0 5 451 3099 1831 79 21 0 1 5 0 15956 7248 1 0 0 0 0 0 1 0 0 458 3406 1825 73 16 11 0 8 0 16200 27764 1 0 0 0 1269 498 2 34 0 1552 3016 1820 61 29 10 1 7 0 17560 19068 1 0 0 0 19 0 0 71 0 1675 3118 1683 40 33 28 3 6 0 15768 13772 1 0 0 0 2 0 0 26 0 955 3650 1822 57 21 21 3 6 0 16928 10736 1 0 0 0 0 0 0 1 0 506 3266 1620 56 15 30 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 8 0 18128 8168 1 0 0 0 9 0 0 0 0 499 3057 1569 44 14 42 3 5 0 16436 10476 3 0 0 0 4 249 2 2 0 574 3387 1658 41 12 47 1 7 0 15764 8436 1 0 0 0 1 0 0 1 0 518 3216 1616 40 14 46 1 8 0 13680 10656 74 0 0 0 55 249 0 8 0 503 2962 1427 48 13 40 0 9 0 16932 7964 4 0 1 0 0 0 1 4 0 532 3005 1603 45 13 42 1 5 0 16568 10768 1 0 0 0 8 249 1 1 0 470 3352 1704 63 14 23 3 6 0 16900 8104 1 0 0 0 0 0 0 2 0 461 3317 1702 68 16 16 1 5 0 19940 10308 19 4 0 0 8 249 0 4 0 550 3636 1877 63 17 20 0 9 0 23136 7996 11 0 0 0 9 0 1 2 0 480 2777 1510 40 13 46 1 5 0 25276 9624 81 2 3 0 55 249 0 4 0 515 3291 1642 63 14 22 2 8 0 28692 7016 137 0 3 0 154 0 14 450 4 804 3217 1164 29 13 58 1 8 0 28316 8776 1 0 0 0 1 252 0 808 18 1101 1884 970 2 14 84 1 9 0 23696 7508 71 0 0 0 62 0 0 254 4 707 890 501 8 9 83 010 0 18880 9424 1 0 0 0 1 250 1 316 17 682 798 495 1 7 92 2 7 0 14184 11276 1 0 0 0 3 249 1 153 18 532 477 345 1 7 92 1 8 0 11576 8100 10 0 0 0 11 0 0 359 18 728 989 561 2 10 88 1 8 0 11220 10148 1 0 0 0 8 249 1 351 18 669 910 499 1 7 92 0 9 0 12888 6916 7 0 0 0 7 0 2 426 18 752 1166 595 2 8 90 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 0 9 0 13220 8908 1 0 0 0 0 249 0 111 18 383 476 218 0 8 92 2 7 0 13432 10904 10 0 0 0 13 251 1 105 18 415 528 248 1 7 92 0 9 0 13912 7788 14 0 0 0 16 0 4 117 18 387 641 236 1 8 91 1 8 0 13604 9896 1 0 0 0 1 252 0 115 18 374 491 223 0 6 93 0 9 0 13568 6884 1 0 0 0 0 0 1 115 18 373 492 220 0 8 92 1 9 0 15160 8928 1 0 0 0 0 252 0 112 18 373 487 221 0 7 92 1 9 0 13600 11088 1 0 0 0 1 252 0 112 18 370 483 216 0 7 93 0 9 0 14560 8160 7 0 0 0 7 0 0 112 18 377 555 226 0 7 93 1 8 0 14388 10244 1 0 0 0 0 251 1 107 18 372 478 213 0 7 92 0 9 0 12432 7300 1 0 0 0 1 0 0 113 18 374 499 220 0 7 92 1 8 0 12432 9392 1 0 0 0 1 251 0 108 18 517 487 365 0 7 93 0 9 0 10256 6448 1 0 0 0 0 0 1 100 18 530 467 382 0 7 93 1 8 0 10588 8592 1 0 0 0 1 260 0 106 18 436 470 286 0 7 93 0 9 0 10148 10640 1 0 0 0 0 252 0 105 18 397 477 245 0 6 93 0 9 0 10488 9420 31 1 1 0 21 0 2 105 7 367 376 179 0 5 95 1 9 0 12180 7252 1 0 0 0 1 0 0 99 13 364 399 195 0 5 94 3 7 0 12180 9328 1 0 0 0 1 256 0 103 18 377 467 225 2 7 92 1 9 0 14276 6384 1 0 0 0 0 0 1 98 18 370 461 217 0 7 93 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 0 9 0 13764 8528 1 0 0 0 0 251 0 92 18 349 445 197 2 6 92 4 8 0 18668 9544 48 0 1 0 7 250 2 89 18 354 1236 747 9 8 83 3 7 0 18672 10200 20 0 0 0 1 249 1 103 18 377 2033 1313 13 12 75 1 9 0 16536 6940 10 0 0 0 1 0 0 102 18 362 1566 938 7 10 83 1 9 0 16540 8824 6 0 0 0 1 252 0 102 18 368 1557 941 5 10 85 3 7 0 17460 9692 52 0 0 0 0 249 1 60 18 344 12842 731 36 11 53 2 6 0 15612 8664 4 0 0 0 123 0 0 129 18 397 4922 1108 46 12 42 1 6 0 15792 7696 1 0 0 0 0 251 0 196 18 472 3645 1887 73 21 7 3 6 0 16572 7524 3 0 0 0 1 249 2 310 18 586 5573 2397 65 23 12 2 6 0 17204 7780 1 0 0 0 1 252 0 206 18 611 3522 1867 45 20 36 1 8 0 16724 7296 1 0 0 0 0 249 0 188 18 472 3542 1741 83 17 0 1 8 0 19492 8880 1 0 0 0 1 252 0 433 18 718 7817 2975 47 27 25 2 6 0 18700 10896 2 0 0 0 1 249 0 486 18 758 8779 3336 42 27 31 5 5 0 16840 7920 1 0 0 0 0 0 0 503 18 805 9042 3409 44 27 29 3 6 0 16840 9904 1 0 0 0 0 250 0 527 18 838 9448 3568 48 26 26 1 6 0 13860 6920 1 0 0 0 0 0 1 497 18 795 8947 3402 43 27 30 5 5 0 13860 10328 1 0 0 0 1 256 0 490 10 778 8775 3298 46 20 34 0 9 0 14192 8376 1 0 0 0 0 0 0 519 12 832 9366 3531 46 25 29 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 3 4 0 14192 10352 1 0 0 0 0 252 0 469 18 794 8442 3256 42 25 33 3 6 0 14404 7344 1 0 0 0 0 0 0 577 18 871 10263 3713 53 27 19 3 6 0 14884 9424 1 0 0 0 0 254 0 555 18 841 9866 3612 53 26 20 1 8 0 16244 6376 1 0 0 0 0 0 1 565 18 866 10114 3736 53 27 21 0 9 0 16544 8388 1 0 0 0 0 252 1 548 18 863 9737 3551 48 28 24 3 5 0 19312 10416 1 0 0 0 1 250 0 585 18 879 10359 3711 53 31 17 4 5 0 18832 7416 1 0 0 0 0 0 0 571 18 866 10103 3650 54 28 18 0 9 0 17140 9468 1 0 0 0 3 251 1 523 18 787 9362 3489 47 27 26 1 8 0 16840 10640 1 0 0 0 1 250 1 271 18 578 4797 2126 38 19 42 1 8 0 14232 10480 1 0 0 0 1 250 2 211 18 513 3910 1870 72 19 9 2 5 0 14232 9840 1 0 0 0 0 250 1 174 18 457 3286 1719 78 20 1 2 6 0 14564 9152 1 0 0 0 0 250 0 155 18 423 2971 1583 80 20 0 1 6 0 14564 8536 1 0 0 0 1 249 0 157 18 435 3029 1595 81 19 0 4 5 0 14404 8016 1 0 0 0 0 251 0 191 18 464 3607 1768 78 20 1 1 6 0 14252 7600 1 0 0 0 0 250 0 240 18 504 4388 1959 78 22 1 1 6 0 15920 7064 1 0 0 0 0 249 1 215 18 481 4004 1903 75 22 3 1 6 0 15920 6552 1 0 0 0 0 251 0 205 18 478 3705 1853 66 21 13 1 6 0 18348 10976 1 0 0 0 1 500 0 198 18 474 3720 1795 78 22 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 17836 11288 1 0 0 0 1 249 0 206 12 475 3767 1822 83 17 0 1 6 0 15836 7192 1 0 0 0 0 0 0 188 8 457 3436 1725 83 17 0 3 4 0 15836 6472 1 0 0 0 0 249 0 155 18 424 2975 1600 83 17 0 2 7 0 14188 10848 1 0 0 0 1 498 0 164 18 449 3173 1641 81 17 2 2 7 0 14188 6480 1 0 0 0 0 0 0 183 18 453 2941 1496 37 17 46 3 4 0 14520 6840 1 0 0 0 0 250 0 271 18 544 4848 2040 61 20 19 3 6 0 14520 6984 1 0 0 0 0 249 0 253 18 537 4564 1956 65 19 16 2 6 0 14080 7312 1 0 0 0 0 250 0 279 18 552 5015 2115 60 21 18 1 6 0 14860 6648 1 0 0 0 1 249 0 159 18 442 3061 1601 71 18 11 2 6 0 16220 7152 1 0 0 0 0 249 1 282 18 548 5038 2123 56 21 23 1 8 0 16220 8944 1 0 0 0 0 250 0 560 18 820 9790 3404 52 31 16 0 9 0 16664 11024 5 0 0 0 26 251 0 170 18 439 2918 1391 23 13 63 1 6 0 16152 11200 1 0 0 0 0 249 0 268 18 536 4846 2052 65 21 14 1 6 0 14152 11184 1 0 0 0 1 250 0 310 18 582 5590 2238 76 24 0 2 7 0 14628 6612 1 0 0 0 0 0 0 234 18 517 4144 1806 55 19 26 3 4 0 13704 7344 1 0 0 0 0 251 0 335 18 623 5939 2353 58 24 18 1 6 0 13704 6400 1 0 0 0 0 250 0 174 18 472 3328 1692 81 19 0 4 4 0 14036 10832 1 0 0 0 1 499 0 179 18 448 3392 1734 82 18 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 2 6 0 14036 10048 1 0 0 0 0 249 0 171 18 458 3281 1709 78 22 0 1 6 0 14248 9424 1 0 0 0 0 251 0 177 18 451 3364 1655 78 22 0 1 6 0 14560 9016 31 0 2 0 21 249 3 172 15 450 3287 1636 79 21 0 2 6 0 16252 10600 1 0 0 0 0 249 0 300 7 567 5314 2218 79 21 0 1 6 0 16244 9936 1 0 0 0 0 249 2 197 18 479 3682 1746 81 19 0 1 6 0 15976 9264 1 0 0 0 1 251 1 194 18 481 3671 1773 79 21 0 2 6 0 15464 8752 1 0 0 0 0 251 0 193 18 461 3615 1744 79 21 0 1 6 0 14420 9040 2 0 0 0 1 251 0 360 18 643 6484 2513 71 24 4 1 6 0 14120 8304 1 0 0 0 0 251 0 176 18 452 3344 1656 79 21 0 1 6 0 14352 7464 1 0 0 0 0 250 0 179 18 476 3415 1708 80 20 0 4 5 0 14352 6688 1 0 0 0 0 249 1 172 18 478 3283 1656 78 22 0 2 6 0 14036 11008 1 0 0 0 1 499 0 177 18 481 3386 1666 78 22 0 1 6 0 13868 10264 1 0 0 0 2 251 0 169 18 447 3242 1660 82 18 0 1 6 0 14420 10192 1 0 0 0 0 251 0 285 18 584 5252 2245 77 21 3 1 6 0 14900 9636 2 0 0 0 1 252 0 196 18 462 3670 1732 81 19 0 1 6 0 16260 9040 1 0 0 0 0 250 0 196 18 462 3659 1734 81 19 0 1 6 0 16260 8472 1 0 0 0 0 251 0 193 18 472 3628 1736 79 21 0 1 6 0 15508 8204 12 0 0 0 5 251 1 244 18 531 4527 1992 71 23 6 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 14996 7504 1 0 0 0 1 249 0 206 18 486 3865 1836 78 22 0 2 5 0 13304 6936 1 0 0 0 1 249 1 216 18 501 4055 1842 81 19 0 1 6 0 13304 6660 1 0 0 0 1 249 0 303 18 572 5507 2239 77 23 0 3 5 0 13536 6544 1 0 0 0 0 250 0 348 18 617 6243 2467 74 26 0 1 6 0 13536 10544 1 0 0 0 1 465 1 274 18 539 4994 2128 74 25 0 1 6 0 13868 7224 1 0 0 0 0 0 0 246 2 489 4326 1955 84 16 0 2 6 0 13868 6672 1 0 0 0 0 251 0 250 18 523 4593 2030 77 23 0 1 6 0 14080 10944 22 0 1 0 18 498 3 228 18 513 4245 1923 75 24 1 2 7 0 14860 10960 1 0 0 0 0 250 1 209 18 476 3451 1672 56 19 25 1 6 0 16220 11120 1 0 0 0 0 250 1 237 18 505 4238 1874 63 20 17 2 8 0 16220 6640 1 0 0 0 0 0 0 257 18 520 4376 1847 55 21 25 1 6 0 15508 6800 1 0 0 0 0 254 1 176 18 445 3018 1535 49 18 32 2 6 0 14996 6504 1 0 0 0 0 251 0 208 18 478 3699 1806 59 23 19 1 6 0 13304 11248 1 0 0 0 1 499 0 183 18 454 3379 1653 72 18 10 3 6 0 13304 6980 1 0 0 0 1 0 0 261 18 524 4615 2017 47 21 31 4 4 0 14188 7656 1 0 0 0 0 250 0 295 18 571 5392 2216 58 20 22 2 6 0 14188 7056 1 0 0 0 0 251 0 174 18 456 3319 1633 77 21 3 0 9 0 14860 8468 4 0 0 0 2 249 2 176 18 449 2906 1383 24 13 62 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 211 0 15700 10072 1 0 0 0 1 251 0 158 18 439 2506 1267 15 14 71 1 6 0 15260 6608 1 0 0 0 0 0 1 173 18 446 2747 1292 22 12 65 2 5 0 15740 10448 1 0 0 0 1 502 0 154 18 422 2982 1687 79 20 0 1 6 0 17100 8928 1 0 0 0 0 249 0 152 18 420 2973 1728 78 22 0 1 6 0 17400 7672 1 0 0 0 0 249 0 161 18 431 3101 1683 79 21 0 1 6 0 15808 11240 1 0 0 0 1 499 1 148 18 428 2932 1639 76 24 0 1 6 0 16288 9744 14 0 0 0 7 249 0 154 18 434 3032 1725 79 21 0 1 6 0 15436 6996 4 0 0 0 2 0 1 175 4 431 2962 1543 54 15 31 3 5 0 15136 7888 1 0 0 0 0 250 0 202 18 469 3505 1589 42 18 39 2 6 0 15368 8112 1 0 0 0 0 251 0 293 18 561 5234 2097 69 21 9 3 6 0 13908 9604 1 0 0 0 0 250 0 155 18 423 2517 1243 23 12 65 3 6 0 14240 9840 1 0 0 0 1 252 1 143 18 414 2437 1323 44 15 41 3 6 0 14240 11248 1 0 0 0 0 249 0 142 18 406 2386 1200 19 14 67 1 8 0 14420 7940 1 0 0 0 0 0 2 140 18 408 2314 1107 16 12 73 3 5 0 14900 8168 1 0 0 0 1 249 0 227 18 518 4108 1869 60 20 21 3 4 0 16760 7376 1 0 0 0 0 249 0 203 18 503 3664 1781 73 21 6 1 6 0 16760 6800 1 0 0 0 0 250 0 210 18 477 3904 1814 79 21 0 0 9 0 16348 6816 1 0 0 0 0 249 1 206 18 471 3807 1780 57 21 22 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 15836 6688 1 0 0 0 0 249 0 158 18 421 2952 1562 64 18 18 1 6 0 12828 10800 1 0 0 0 1 498 0 163 18 430 3120 1680 80 20 0 1 6 0 12520 10024 1 0 0 0 0 249 0 171 18 437 3252 1652 79 21 0 1 6 0 13564 9320 1 0 0 0 1 251 0 172 18 442 3257 1681 77 23 0 1 6 0 13564 8440 1 0 0 0 0 249 0 168 18 435 3209 1666 81 19 0 2 5 0 13896 7712 1 0 0 0 0 251 1 173 18 441 3199 1695 76 21 3 1 8 0 15368 7216 135 0 3 0 153 249 15 140 18 514 3878 1524 58 20 23 1 8 0 15344 9268 1 0 0 0 0 251 0 0 18 1139 2019 1000 3 16 82 1 8 0 15824 11344 31 0 1 0 21 250 2 0 18 1073 1928 940 3 13 84 1 8 0 17516 10324 1 0 0 0 0 0 1 0 6 974 1562 777 3 10 87 1 8 0 12516 8028 1 0 0 0 1 0 0 0 15 897 1491 727 1 7 91 0 9 0 12344 10048 1 0 0 0 0 250 1 0 18 482 706 325 0 7 92 1 8 0 11832 7164 1 0 0 0 0 0 1 0 18 458 653 301 0 7 93 2 8 0 10512 9176 1 0 0 0 0 249 1 1 18 469 654 300 0 6 94 1 8 0 9640 11216 1 0 0 0 0 249 0 0 18 447 627 286 0 8 92 2 7 0 9564 8272 1 0 0 0 0 0 0 0 18 457 648 298 0 7 92 0 9 0 9564 10384 1 0 0 0 0 250 0 0 18 463 660 305 0 6 94 1 8 0 9832 7408 1 0 0 0 0 0 0 0 18 460 651 304 0 7 93 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 0 9 0 9832 9480 1 0 0 0 0 251 1 0 18 444 622 287 0 7 92 1 8 0 10044 6600 1 0 0 0 0 0 0 0 18 451 637 288 1 7 92 1 8 0 10524 8656 2 0 0 0 1 250 0 0 18 448 636 294 0 8 92 1 8 0 11884 10704 1 0 0 0 0 250 0 0 18 422 598 273 0 8 92 1 8 0 12184 7812 1 0 0 0 0 0 0 0 18 425 594 273 0 6 93 1 8 0 11772 9872 1 0 0 0 0 250 0 0 18 442 633 290 0 7 93 1 8 0 11260 6984 1 0 0 0 0 0 1 0 18 432 586 266 0 6 93 1 8 0 9568 9040 1 0 0 0 0 250 1 0 18 448 631 277 0 7 93 0 9 0 9268 11088 1 0 0 0 2 258 0 0 18 404 552 242 0 7 92 1 8 0 10152 8944 1 0 0 0 0 0 0 0 18 409 572 250 1 6 93 0 9 0 10572 6392 1 0 0 0 0 0 2 0 11 400 500 209 1 5 94 0 9 0 10904 8408 1 0 0 0 1 255 0 0 17 414 536 242 0 7 93 0 9 0 10904 66036 1 0 0 0 3115 0 1 0 5 366 333 155 1 5 94 1 8 0 10524 62820 1 0 0 0 12 0 1 0 18 383 469 217 2 15 83 2 9 0 16860 58856 36 0 0 0 1 0 0 2 18 369 1257 775 10 8 82 2 8 0 18228 55688 6 0 0 0 0 0 0 1 18 415 1609 964 5 8 87 2 8 0 18232 52484 2 0 0 0 0 0 0 1 18 392 1488 887 4 10 86 2 9 0 17312 49424 3 0 0 0 0 0 0 1 18 390 1467 859 5 10 86 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 8 0 17812 45348 52 0 0 0 0 0 1 0 18 352 5674 668 30 9 61 2 6 0 13900 43620 3 0 0 0 89 0 0 0 18 395 3008 992 24 14 62 1 6 0 13900 38276 1 0 0 0 1 0 0 0 18 469 3369 1721 58 21 21 1 6 0 14132 33812 2 0 0 0 0 0 0 0 18 564 4849 2049 57 21 23 3 6 0 13856 28444 1 0 0 0 0 0 0 0 18 525 4268 1950 73 23 4 2 7 0 13708 24696 1 0 0 0 0 0 1 1 18 437 2818 1380 29 14 57 3 6 0 13708 20992 1 0 0 0 0 0 2 0 18 500 3770 1710 34 13 53 0 9 0 14700 17216 1 0 0 0 1 0 0 0 18 448 2802 1345 27 14 59 1 6 0 14700 12792 1 0 0 0 0 0 0 0 18 690 7407 2790 67 27 5 3 5 0 16060 7120 1 0 0 0 0 0 0 0 18 468 3568 1746 80 20 0 1 6 0 16060 6512 1 0 0 0 0 256 0 0 18 463 3630 1789 81 19 0 3 5 0 15208 10736 1 0 0 0 1 503 0 0 18 476 3547 1764 79 21 0 1 6 0 15336 10048 1 0 0 0 1 250 0 0 18 484 3673 1790 79 21 0 2 5 0 13644 9400 1 0 0 0 1 249 1 0 18 462 3477 1764 83 17 0 4 4 0 13644 11024 1 0 0 0 1 249 0 0 2 462 3562 1759 82 18 0 2 6 0 13504 10448 1 0 0 0 0 250 0 0 18 470 3813 1789 74 26 0 2 5 0 13196 9816 1 0 0 0 0 249 0 0 18 512 4508 2025 77 23 0 1 6 0 13528 9192 1 0 0 0 0 249 0 0 18 499 4273 1951 76 24 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 1 6 0 13052 8688 1 0 0 0 1 251 0 0 18 501 4360 1952 77 23 0 1 6 0 14220 8080 1 0 0 0 0 251 1 0 18 499 4166 1924 77 23 0 2 6 0 14696 6732 1 0 0 0 0 249 0 13 18 542 4097 1979 78 22 0 1 6 0 16224 9960 1 0 0 0 1 499 0 4 18 550 3899 1966 78 22 0 2 6 0 16524 9168 1 0 0 0 0 249 1 0 18 493 3959 1845 78 22 0 2 5 0 15972 8624 1 0 0 0 1 252 2 0 18 497 4036 1864 77 23 0 2 6 0 15972 8072 1 0 0 0 1 249 1 0 18 495 4036 1859 78 22 0 0 9 0 13644 8496 1 0 0 0 0 250 1 0 18 481 3594 1664 53 17 30 1 6 0 13272 8896 1 0 0 0 0 249 0 0 18 428 2634 1352 46 16 38 1 6 0 13876 7784 1 0 0 0 1 249 1 0 18 418 2947 1622 80 20 0 1 6 0 13876 6616 1 0 0 0 0 249 1 0 18 441 2986 1657 80 20 0 2 6 0 13900 10344 1 0 0 0 1 498 0 0 18 443 2976 1630 79 21 0 3 4 0 12964 9272 1 0 0 0 1 250 0 0 18 433 3001 1628 78 22 0 1 6 0 14528 7980 63 0 3 0 44 249 6 0 18 435 3059 1658 80 20 0 1 6 0 14528 6840 1 0 0 0 0 249 0 0 18 437 2988 1634 81 19 0 3 5 0 16220 10736 1 0 0 0 1 501 1 1 18 469 3006 1668 79 21 0 2 6 0 16388 11152 1 0 0 0 0 249 0 0 4 466 2964 1676 82 18 0 1 6 0 16456 8968 1 0 0 0 0 252 0 13 18 557 2937 1797 77 23 0 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 sa0 in sy cs us sy id 3 5 0 14764 7640 1 0 0 0 1 250 0 7 18 460 2961 1685 81 19 0 1 6 0 15104 6432 1 0 0 0 0 249 1 5 18 425 2958 1666 79 21 0 3 6 0 15104 10256 1 0 0 0 1 498 0 2 18 421 2964 1633 79 21 0 1 6 0 15336 9064 1 0 0 0 1 249 0 1 18 458 3056 1669 79 21 0 2 6 0 14828 7832 1 0 0 0 0 252 0 3 18 458 3006 1667 77 23 0 1 6 0 15160 6560 1 0 0 0 1 249 0 2 18 439 2980 1643 78 22 0 1 6 0 13944 10480 1 0 0 0 1 502 0 2 18 482 3102 1695 80 20 0 1 6 0 15500 9228 27 0 2 0 18 251 4 1 18 441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 19:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 6748C14CC3; Wed, 24 Feb 1999 19:29:32 -0800 (PST) From: "Jonathan M. Bresler" To: veldy@visi.com Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-reply-to: <01b401be5f64$ab1019c0$236319ac@w142844.carlson.com> (veldy@visi.com) Subject: Re: listproc problem? References: <01b401be5f64$ab1019c0$236319ac@w142844.carlson.com> Message-Id: <19990225032932.6748C14CC3@hub.freebsd.org> Date: Wed, 24 Feb 1999 19:29:32 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: "Thomas T. Veldhouse" > Date: Tue, 23 Feb 1999 13:42:37 -0600 > Content-Type: text/plain; > charset="iso-8859-1" > X-Priority: 3 > X-MSMail-Priority: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 > Sender: owner-freebsd-current@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > I have been seeing 5 hour delays from when the message was sent to the list > and when the message arrives in my mailbox. It seems to be a problem with > the following jump: looks like we had an issue while trying to reach mail2.sol.net. that one hop took about 3 hours (not five...gotta watch those timezone changes ;) > > Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) > by mail2.sol.net (8.8.8/8.8.8/SNNS-1.02) with ESMTP id NAA00902; > Tue, 23 Feb 1999 13:26:13 -0600 (CST) > Received: by hub.freebsd.org (Postfix, from userid 538) > id AECC411D08; Tue, 23 Feb 1999 07:34:37 -0800 (PST) > Received: from localhost (localhost [127.0.0.1]) > by hub.freebsd.org (Postfix) with SMTP > id 5DD8B11B6C; Tue, 23 Feb 1999 07:34:37 -0800 (PST) > (envelope-from owner-freebsd-stable) > > Also, as a side note, how do I set up my box to use PostFix instead of > sendmail? I heard that it was (or was considered) included in the > 3.1-RELEASE, it just wasn't enabled by default. it was considered but not included in the end....the disucssion in the committers mailing list indicated that people were not ready to go that way yet. we will try again soon. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 19:42:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 8400914CC5 for ; Wed, 24 Feb 1999 19:41:07 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA26270; Thu, 25 Feb 1999 14:10:50 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA08286; Thu, 25 Feb 1999 14:09:32 +1030 (CST) Message-ID: <19990225140931.K52343@lemis.com> Date: Thu, 25 Feb 1999 14:09:31 +1030 From: Greg Lehey To: Pierre Beyssac , Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <19990224235117.A9283@enst.fr> <11472.919897269@axl.noc.iafrica.com> <19990225010448.A335@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990225010448.A335@enst.fr>; from Pierre Beyssac on Thu, Feb 25, 1999 at 01:04:48AM +0100 WWW-Home-Page: http://www.lemis.com/~grog 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 Thursday, 25 February 1999 at 1:04:48 +0100, Pierre Beyssac wrote: > On Thu, Feb 25, 1999 at 01:01:09AM +0200, Sheldon Hearn wrote: >>> controller wdc1 [...] >>> disk wd2 at wdc1 drive 0 >>> disk wd3 at wdc1 drive 1 >> >> Um... Do you really have 4 wd devices plugged in? > > Uh, well, no, just 2 (on the first IDE controller). > >> Assuming you don't have 4 drives, I'd suggest you slave your ATAPI CDROM >> device on your primary IDE controller. So you'd do something like: > > Wow. Thanks a million! I didn't even have to go so far, I just > deleted wd2 and wd3 and acd0 now appears as if by magic. I can't > tell you how extremely stupid I now feel... You shouldn't do. What you did shouldn't have any effect on the problem. You may find that sometimes it gets recognized, other times it doesn't. FreeBSD still has difficulties with some ATAPI CD-ROM drives. If you continue to have trouble (and I suspect you will), you should enter a PR with send-pr or at http://www.freebsd.org/send-pr.html. Make sure to give exact details of your hardware and software configuration. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 20: 5:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (37-sweet.camalott.com [208.239.153.37]) by hub.freebsd.org (Postfix) with ESMTP id A779214D26 for ; Wed, 24 Feb 1999 20:05:01 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.2/8.9.1) id WAA27704; Wed, 24 Feb 1999 22:04:54 -0600 (CST) (envelope-from joelh) To: current@FreeBSD.ORG Subject: Re: NFS Problems References: <199902222220.OAA00897@dingo.cdrom.com> From: Joel Ray Holveck Date: 24 Feb 1999 22:04:50 -0600 In-Reply-To: Mike Smith's message of "Mon, 22 Feb 1999 14:20:42 -0800" Message-ID: <861zjfcen1.fsf@detlev.UUCP> Lines: 374 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This reminds me; do we have a utility to reference wmesg strings back >> to the code that sets them, a la TAGS? Would this be useful? > No, and yes respectively. Okay, I've got an early version written. It's got some fairly substantial TODO's, and needs a fair bit of cleanup. I would appreciate any comments anybody has. -----cut here----- #! /usr/bin/perl -w # Copyright (c) 1999 Joel Ray Holveck. All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $Id$ # NAME # wtags - generate wchan tag file # # SYNOPSIS # wtags [-cegw] [-v] [path] # # DESCRIPTION # wtags scans a 4.4BSD kernel source tree and creates a database # listing all the wchan's which are explicitly specified to # tsleep(9) or similar functions. This is useful for identifying # where in the kernel a process may be hung. # # The source tree to be searched may be specified with path, or # the current directory is used. Subdirectories are always # scanned, and symbolic links are always followed. # # The options are as follows: # # -c Generate ctags(1)-compatible output. Output is appended # to the file "tags" in the current directory. This file # is typically used with vi(1). # # -e Generate etags(1)-compatible output. Output is appended # to the file "TAGS" in the current directory. This file # is typically used with Emacs(1). # # -g Generate gtags(1)-compatible output. Output is appended # to the file "GSYMS" in the current directory. This file # is typically used with the global(1) tags system by # Shigio Yamaguchi, which may be used with vi(1), Emacs(1), # or other systems. # # -w Generate a native file format (described below). This # format is designed to be easily read by humans or machines, # but no utilities currently use it. -w is the default if # no other output format is specified. # # -v Generate warnings for many cases when a possible call to # tsleep(9) or a related function is found, but a wchan # could not be isolated. There are normally many of these # in correct code; one version of wtags produced 83 such # diagnostics on the 4.4BSD-Lite kernel. See DIAGNOSTICS, # below. # # wtags will only recognize string literals for wchan arguments. # A function (such as lf_setlock) which uses a string constant # instead, or one (such as ttread) which uses one of a few known # possibilities selected via :? or another mechanism, may have a # comment such as /* WCHAN: lockf */ on the line in question. # wtags will then use the indicated channel, and ignore any tsleep # call on that line. # # FILES # /sys Traditional kernel source location # WTAGS Default output file, used with -w or if no other # tag file is specified # TAGS Emacs(1) tags output file, used with -e # tags vi(1) tags file, used with -c # GSYMS global(1) tags file, used with -g # # DIAGNOSTICS # If the -v option is specified, then whenever tsleep (or another # function that uses wchan) is written in the source file, but no # wchan can be found, a diagnostic is printed. These diagnostics # do not always properly describe the issue. # # There is one exception to this: if the item appears to be a # reference to tsleep from within a comment (using a heuristic), # then no diagnostic is printed. # # SEE ALSO # ps(1), etags(1), ctags(1), global(1), tsleep(9), glimpse(1) # # NOTES # wtags was designed under FreeBSD. Any contributions to allow it # to work with other OS's would be appreciated. # # wtags is written for Perl 5. It may break under other versions # of Perl. # # HISTORY # wtags was originally written on 22 February, 1999 for FreeBSD 4.0 by # Joel Ray Holveck . # # BUGS # -e and -g are not yet implemented. Notes on the respective file # formats are in the source. # # Presently, only calls to tsleep, asleep, ttysleep, and lockinit are # scanned. A list of other calls to be scanned is in the source. # # Mentions of tsleep in strings are not skipped, and will normally # generate a diagnostic (if -v is specified). # TODO: # # 0. Fix multiline functionality. Try scanning /sys/kern/subr_log.c for # an example. # # 1. Add etags(1) support. Since I use Emacs so often, this was my original # goal. I will describe the file format for Emacs's TAGS here: # Each file is listed separately. At the beginning of the file's entries # is a formfeed, newline, the complete filename, and the number of bytes # until the next entry, all terminated by a newline. Example: # ^L # /usr/local/src/emacs-20.3/src/alloca.c,785 # The bytecount is from after the newline to before the next formfeed # (or EOF). Each item in the file is on a separate line. If the tag has # a name, then the line contains the search string, a del (\177), the # tag name, a ^A (\001), the line number, a comma, and the byte number. # This means that we will probably be using something along the lines of: # tsleep^?wait^A1132,29901 # This will make Emacs search for "tsleep" when the match is used. # (If the item has no name, then the name and the ^A are elided.) # # 2. Add gtags(1) support. Specifically, these should be added to GSYMS. # I still need to do more research on the GSYMS file format. It seems # that each record includes the name of the tag, the filename, and a # comma-separated list of line numbers where the tag appears. If a tag # appears in more than one file, then more than one entry is created. # # 3. Add support for more sleep calls. I need to change out of # hardcoded regexps first. As of FreeBSD 4.0-CURRENT (24 Feb 1999), # the calls in question include usbd_bulk_transfer (from # /sys/dev/usb/usbdi_util.c), waitforit (from /sys/i386/isa/matcd/matcd.c), # wdsleep (from /sys/i386/isa/wd.c and /sys/pc98/pc98/wd.c), wtwait # (from /sys/i386/isa/wt.c), BPF_SLEEP (from /sys/net/bpf.c), and # vm_page_sleep and vm_page_asleep (both from /sys/vm/vm_page.c). use strict; use Getopt::Std; use vars qw($opt_w $opt_c $opt_v); # A hash indexing wchan strings to a list of locations. The location # format currently is filename\tlineno, but this may change (probably # to append ",byteno") when etags support is added. # Current example: # "slock"-> [ "/sys/kern/kern_lock.c\t557" ] # future example: # "slock"-> [ "/sys/kern/kern_lock.c\t557,14263" ] # it is also likely that etags support will use a completely different # system. my %wchan; # a hash indexing location strings to the function name being used (eg, # "kern_lock.c\t557"->"tsleep") my %sleepcall; # a hash relating sleep calls to the argument offset of the # wchan string # FIXME The regexes that scan for these calls should be built # from this. my %wchanarg; $wchanarg{"tsleep"}=2; $wchanarg{"asleep"}=2; $wchanarg{"ttysleep"}=3; $wchanarg{"lockinit"}=2; # $prog_label is prefixed on all warnings and error messages. to # comply with standards, it should be "wtags: ", but leaving it empty # allows you to use emacs's compile-mode with its output to check the # source of each warning message against the offending kernel source. # my $prog_label = "wtags: "; my $prog_label = ""; sub scanfile { my ($file) = @_; open FILE, $file or warn "$prog_label$file: can't open: $!; skipped\n"; while () { # FIXME Isn't recognized on subsequent lines m,/\*\s*WCHAN:\s*([A-Za-z0-9]+)\s*\*/, && goto EXPLICIT_WCHAN; /\b(tsleep|asleep|ttysleep|lockinit)(.*)/ || next; my $looks_like_comment; my $sleepcall = $1; # Saved to add to %sleepcall my $rest = $2; # This matches either /* or a line starting with a * (for # boxed comments). # FIXME This doesn't work for calls within calls. $looks_like_comment = ((m,^\s*/?\*,) ? 1 : 0); $_ = $rest; GOT_SLEEP: # We keep the current arg number in $arg. If we are in a # comment, then set $incomment to 1. parens is the current # parens level. Inside the tsleep call's parens is level 0. my ($curarg, $incomment, $parens, $lines_scanned) = (0, 0, -1, 0); while ($curarg < $wchanarg{$sleepcall}) { # Handle this first so it can next; to itself. if ($incomment) { if (m,\*/(.*),) { $_ = $1; $incomment = 0; } else { if (++$lines_scanned >= 5) { $opt_v and warn "$prog_label$file: $.: tsleep call over five lines; skipped\n"; goto PARSE_FAILED; } $_ = ; if (!defined $_) { $opt_v and warn "$prog_label$file: $.: early EOF hit; continuing"; goto PARSE_FAILED; } next; } } # Parse out the following: /*, */, (, ), ',', and 'tsleep'. # FIXME Doesn't exclude tokens within strings if (m:.*?(/\*|\*/|\(|\)|,|\btsleep|\basleep|\bttysleep|\blockinit)(.*)$:) { if ($1 eq "/*") { $incomment = $1; } elsif ($1 eq "*/") { # End of comment hit goto PARSE_FAILED; } elsif ($1 eq "(") { ++$parens; } elsif ($1 eq ")") { $parens--; if ($parens < 0) { # Suppress the warning if there is a comment # that includes a reference to tsleep just # like this one does. if (!($looks_like_comment && $curarg == 0)) { $opt_v and warn "$prog_label$file: $.: tsleep call with too few args; skipped\n"; } goto PARSE_FAILED; } } elsif ($1 eq ",") { $parens == 0 and $curarg++; } elsif ($1 eq "*/") { # There was a reference to tsleep within a comment. goto PARSE_FAILED; } else { # new tsleep call $opt_v and warn "$prog_label$file: $.: tsleep called within tsleep\n"; $sleepcall = $1; $_ = $2; goto GOT_SLEEP; } $_ = $2; } else { # This is taken out because it probably is not useful. # if ($parens == -1) { # # This was probably a reference to tsleep, rather than # # a call. # goto PARSE_FAILED; # } $_ = ; # get the next line if (!defined $_) { $opt_v and warn "$prog_label$file: $.: early EOF hit; continuing"; goto PARSE_FAILED; } $looks_like_comment = ((m,^\s*/?\*,) ? 1 : 0); # mostly for switching to the next tsleep call if (++$lines_scanned >= 5) { # This is probably a sign of a misparse, or incomplete code # (say, in an #if 0 or something). $opt_v and warn "$prog_label$file: $.: tsleep call over five lines; skipped\n"; goto PARSE_FAILED; } } } # We are now looking at the correct argument. # FIXME Handle looking at a comment while (/^\s*$/) { # End of line was after the comma; skip blank lines. $_ = ; if (!defined $_) { $opt_v and warn "$prog_label$file: $.: early EOF hit; continuing"; goto PARSE_FAILED; } } if (! m,^\s*"([^\042]*)",) { # Use octal to keep quotes matched for emacs $opt_v and warn "$prog_label$file: $.: wmesg is not a string literal; skipped\n"; goto PARSE_FAILED; } EXPLICIT_WCHAN: my $wmesg = $1; if (defined $wchan{$wmesg}) { push @{ $wchan{$wmesg} }, ("$file\t$."); } else { $wchan{$wmesg} = [ "$file\t$." ]; } $sleepcall{$wmesg} = $sleepcall; PARSE_FAILED: } close FILE; } sub scandir { my ($wd, $glob) = @_; my $file; my @flist; print "==> $wd\n"; @flist = glob("$wd/$glob"); defined @flist or warn "${prog_label}can't scan $wd: $!; skipped\n"; foreach $file (@flist) { if (-d $file) { scandir($file,$glob); } else { $file =~ /.c$/ and scanfile($file); } } } getopts('cvw'); $opt_c or $opt_w = 1; # -w is the default output format $opt_w and (open WTAGS, ">WTAGS" or die "${prog_label}can't create WTAGS:$!\n"); $opt_c and (open CTAGS, ">>tags" or die "${prog_label}can't append to tags:$!\n"); # Use the output of `pwd` as the directory if nothing was specified on the # command line. my $wd = ((defined $ARGV[0])?$ARGV[0]:`pwd`); $wd =~ s,/?\n?$,,; # Strip off any terminating slash and/or newline scandir($wd, "*"); # FIXME This loop should be built and eval'd. foreach my $wchan (sort keys %wchan) { $opt_w && print WTAGS "\f\n$wchan\n"; foreach my $spot (@{ $wchan{$wchan} }) { # Should I use a regex for ctags instead? $opt_c && print CTAGS "$wchan\t$spot\n"; $opt_w && print WTAGS "$spot\n"; } } close CTAGS; close WTAGS; __END__ -----cut here----- -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 20:41: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id DACBC14D02; Wed, 24 Feb 1999 20:40:49 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10FsYd-000I5dC; Wed, 24 Feb 1999 23:37:55 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: Missing files/directories In-Reply-To: <199902230822.IAA00707@keep.lan.Awfulhak.org> from Brian Somers at "Feb 23, 1999 8:22:47 am" To: brian@Awfulhak.org (Brian Somers) Date: Wed, 24 Feb 1999 23:37:55 -0500 (EST) Cc: tom@tomqnx.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM919917475-1022-0_ Content-Transfer-Encoding: 7bit Content-Length: 11787 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM919917475-1022-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi Brian, It was a good thought, but we can't put the blame on bad hardware. These tests were done on the RELENG_3 system cvsup'd as of Feb 22 @ 20:00 EST. All tests were run internal to the same machine. So that I don't remain the only guy in the world to see these test results, Control files are included so you can test locally:-) "ppp0 -direct" on localhost is started by port 6671. I know (now) that setting up the test this way the ppp's were communicating via localhost rather than the tunnel, but this way was much cleaner as far as verifying exactly how close the results were to what I saw running the server under 2.2-stable. There were differences, but the main issues are demonstrated. You will recall our discussion about the server hanging around under 2.2-stable after the client is terminated? Required by the RFCs you said? Under RELENG_3 the server meekly goes away, which makes sense to me. Two tests were done. The first involved "kill -KILL clientpid". The second was "kill -TERM clientpid". In the first test, the server illegally removed the default route. In the second test, the server did the same - neither ppp actioned the second command in the linkdown scripts. I was surprised that the first test ended immediately - I thought the LQR packets would cause the server to terminate after 1 minute. Files: test1.netstat0 shows routing after boot test1.netstat1 shows routing after "ppp -background testloop" test1.psaxl show ps results for the executing processes. test1.netstat2 shows routing after killing the client. test1.tun0 ifconfig while active. test1.tun1 ifconfig while active. test2.netstat routing tables after terminating the client. Logs are supplied for both tests. I hope that this is very helpful to you. I really appreciate your efforts!! Cheers, Tom > Hi, > > I don't claim to know a great deal about cache code etc, but I'm > pretty sure that it's extremely unlikely that the file name has any > chance of affecting the buffer cache. While NFS has its fair > share of problems (with which Matt is dealing with admirably), I > would think that the code that does the work there is equally unlikely > to know anything about file names. > > Having said all that in as vague a way as possible, the reason I'm > posting this is that you seem to be experiencing difficulties with > ppp that are of a similar nature - that is, completely inexplicable > and unseen by anyone else - disappearing default routes, ppp.linkdown > not being processed, > > I'm beginning to suspect a hardware problem - perhaps with your disk > controller or something. This wouldn't easily explain the default > route problem, but may explain the failure to process ppp.linkdown.... > > Maybe you could try treating the other machine (your son's machine?) > as the gateway, and see if things become more stable. If they do, > the finger might be pointed more firmly at hardware. > > > On the weekend I reported to hackers about problems experienced with > > 2.2-stable and RELENG-3 systems where I experienced files that > > disappeared from cache and Mail directories that disappeared. > > The RELENG-3 system had files affected with softupdates enabled. > > The 2.2-stable system had sub-directories missing from the > > same directories that I was writing to via nfsv2. > > > > By coincidence, I had cvsup'd and compiled new kernels and naturally > > made the assumption that there was causality there. Subsequently > > I have come to believe that the problem may have more to do with what > > I was doing, not changes to the code. > > > > For about 3-4 hours prior to noticing the problems, I had been > > repetitively editing dot files, then writing a kludge of dot files > > to the local system hard drive and to the nfs exported FS of the > > other computer, while occasionally checking mail on that computer. > > > > All files and directories missing were being updated for > > one reason or another by myself or by mail processes while > > I was doing this. > > > > It is speculation, but there is a good chance that there is a bug > > in the cache-handling code that causes problems with other files > > or directories being dropped from cache because of bad processing > > common to BOTH or ALL releases, when large numbers of dot files are > > being written. The dot files themselves did not disappear - other > > items to be written disappeared before their writes actually > > occurred. > > > > I know that this is a frustrating kind of message to receive, but > > I am not a developer & not qualified to go into the code myself. > > Also no logs or hard output are available - files/directories > > simply disappeared without any error messages. > > > > I just did a scan of the entire /usr/src/sys tree for \"\\.\" > > and \'\\.\' to see what code sections might be affected - mostly > > cache-handling. In quantity, not bad, really. > > > > Others have apparently reported missing files to do with nfs > > I believe. THis might or might not be a related problem. > > > > I guess that I am asking someone who is qualified, and concerned > > about missing files or directories, if they would be willing > > to do what I cannot - check the code for bad interactions when > > dot files are being written- bearing in mind that it is OTHER > > files/directories that are disappearing from cache before being > > written. > > > > Is anyone out there sufficiently intrigued by the possibility > > to invest some valuable time? > > > > I am a QA tester, not a developer, and therefore much more > > comfortable with discussion of symptoms and speculative > > causality than most developers I have known. I hope that > > someone thinks enough of the possibility to invest some > > time, which I know is in very short supply. I cannot deny > > that this is (informed) speculation - there are no guarantees. > > > > Regards and best wishes, > > Tom > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > > --ELM919917475-1022-0_ Content-Type: application/x-gtar Content-Disposition: attachment; filename=testppp.tgz Content-Description: Test1 and test2 results Content-Transfer-Encoding: base64 H4sIAMfM1DYAA+1dbXPaSBLO1/Ar5nJ1VcmVQ/SCJKAue+XCSdZXjs2ZcPshlQ+yELbOILFIjp37 9TejdwmNpkcSsN5MV23AQD+al+6eme6e3sD2g/5ms+lbnrt8sR+SJUkfDNALhGRDk8grpuQVfyjL A4R0XdfkgS6rOvlEV7QXSNpTewr04AfmFqEXgbeu/d3jnW2vDtGgw9LCXpoPq2Dce+nbAQqcte09 BEiK/lz9vt3YW8dbIDn5xLtF0zvTt9HkzgzQxHNd2wrQxWSKzqf4n4m3Xpvuovdy4fjmzcpG/hbj 2X7vpe2Gf2PI3kvTsuxNCN/rrTxvEz99YX93LButTWf11Mfz8bv7hMVyPdZ1Q45/4ZirtCGOG701 H4I711zbaOt5QfbRvf0DTf97PzT+9noUfeoszcVii/vSl/pyX07eKEjRtH7ynxQ16a3jjtNGW3fm Brd6tfIe0dpb2LgdW9ztKlQlg4++9u3td3uL3n03t++C9ebdxgxu/AV69QpJsmH0eqRL3A+TkCJp fVmT+gO1L1c/iABjxc6e5MdDvfLMBSLvC6O+8ixzdef5QTTcPTxpARdDr3dsWRbET0Fi/1eOe7/w Ht09PINh/xE2+5n9N4j9VzRZ2P+DUGKtsJov7JUd2Jll6UvvlEH6cfLDXi+xdBmLrI36ymCEP5be yXqZRRGW4Y9LBf1/2OzlGUz9N4xM/zWD6D/+odD/Q1BO//HOoqT8mQaHX2YbJ8Xoh+8LxiD8ScES ZEYjz6/k+I/d/Z+eiP7LfdcOsBoEe1I4lv7rUqL/Kj7/Dcj5z5Alof+HoGt8PHPcWxSQs4ff6527 gb3F4jDunWHJcFwzcDw3mahPZmA/mj9Qjj6uzFs/fHdtL6M3c3w6JHRpB84SfXja4PNLLz5n5llz Rxgl/mj+aWalXydvpOjF3ki91HBkKBUfzX/NPSR+HcYoK0/qZQ9Of0ZWv78qKE/zSfZeqmhLRfOl sS6Nh9Z4YY9vlmNbDtty8VvCrMWvowyFvOjDwfHsYEH/5f08g+X/wat+sv4rkq6F+q8K/T8IPTP9 T3YgGaWbipzm5vQ//WmEEjy4Mnr/Swr0Tk0ZqwxJrjllE0AMScWzK1pY3xwp1xylZXO4raMe/0rP o0RbuFwHKjtFbwsZ48w67qAoYJTjW2pVTlHIizGU/mw71oL9V/bzDNb+z5C1dP9n6Epo/xVZ2P9D 0KHsf0cGl9vCxYZD1pUM5XnbJiVpsZKihB8bRhPbFOl/6ADybjuXroiI/ksSTf/xic9I9n+qIUX6 r+lC/w9CH+0bpAyQoowleayM0MLc3ocjgkXiqypr38ZRvG+M1ZrYCYfYh6Vp4Q/CzUsPDoC3gERB xmiytbEhWWAsZK08H78ji48NwooDjCFaGLhEpUhjQ5QsPNkQIItp8gGkcTaUhtn4ACJmVvy0MaZj rpryhjHapsyFqG4bEBIH/ntMTXFgkeOmE08NqjIB9Uy7ptMpmuFviGK9vjGt+1usD+4iDCG/6fMg 3WC2FX794JNNgePf8TCnSh5r9ttfkLexXWI6mqDECQbhDsVrMTplQHvxl0bsSV9wt0CaQTBIpkQO 4ozwmUFgr7G5kJG3RM16Ej4ftwOmZVUIESeBsNg2hwBcTKZj9HH2OVkMXsVQr5DpIxMFW9P1N96W ra4pWNqWWbgCWHeme2ujc9cJwt7htk0iOWqJGKMQwFngbTY7iKrERrwwf9jbUMcaMM9sd4GFb+nc Xtu/v5bfxGvee/72oNPJx8nV5+lX5RsH0/T66ssVP9vpZPL5dPpV/4akJykmDvbP1/Ovg28I73C5 uE4/nU8u55+jx6o3Q1Vd3pgcAP+en16EHf46/IY2Ww/bDktStJNo+/Idi5ZMOrIu7xZAE5mXq2Ty iGDheX2LZ7mJcFzb1vdK4eDH/OmkQ1Itc2kfWTrQ6fzLrxGmRlplKYqKXk9+PZ2SkdHetDIYp9a9 kAkhE2Xbk8oBMT5YRtobn5KgtcAsNDTFIQ29wjuo5qvvvLxRqeYs7WRP8TEAP9+xdk+Ztfzps+8c H48HmboTtHZcMjiu53Jh4V3gBm9sNg94L4iBLi4+XH76gF4vt94awUQhD3T1EIRI1x9m06vLGQYi xyR+nLhBs/lk8mE2azQ2ZPMY7/KbzM2lHTx623sQK0kxbrIBrUNruAMFQWYbxvIBDNYi2paRu0X4 5fTs7JpYx1x+MpydrAKRJQsRdPSffyF/5QU+enSCu/Atsrz1Zmv7PvEXtx3+3Hada7UrYXazraIO ofJHG8JOdgzPp7vdLIZUmWmzGtY1telyWGVc5hsey7L+UXRj4WUt/OA93xSnLqw0eRDV5A62gdzN OGSi5RzOU3OLhzlyjUX+3QVstAr8eKUPnKWDJ8lbIv/BsrDEYphjO+47ojT+I+0vAMSI/2jqQMri P0aY/6cPRPznIFTnVpOwOhhYHaz4lle4V019sLkIQ61zLkGpCSMxHKAlhHZxpASsZSCJDgONJNER oKGkHYTk4hrKXSVrClF/ta05JuU+XBqhIXfVYPi/mVvii8crIRFJfKJwyMNOcYuxhUbmCkvH4gcR jgcfKBMpYtZQfNwwHbxwoAGXjBaiMdEFPlAkpgTDGYqhKQpnLIaqb8DYCY0/FzxhRhwSjG5CDgW0 bmIOAEjeoEM1JPUQw48J9gMWueCOwPLTeD2BRX6wK7DE1iB6UEToyBlIEZFWgSAxnyDf7v7ns513 lyUapbOnEI3nqeq0UCHMl8BaDxo5KAAt5XZQVGOCHPaUDQ/cY0/bbEQue+KlT132oXLygBVc7ZnT nhsi9rJnzvrwJAXw2Ne1B+Szp40O2GlPmR+Q1z7h7chtX4Trxm9PwQQ77mltauO5L2LyO2JL/J16 YiFzwO28p4C29N4zh5HhSzzGMLZz4D/HHrf04TNFp9Ua2akXv87UMN34ReaiH1/Z9eMDJ7rsdVdi r3v1Jf52mDt3/wtw6liF+RCIUwe9lt6M0Scsfv+ztx66+VH21lHRKjYoZ96j24S5IAzx/Ecnfbxq lF0s4O6FC3KFf4SnRx8dt+wpatKntCOkV8m6CgKtknAyzOPqBYyKUyFKlQVnSmgDsGCW6tTAcOqM AlsOYKC5eezzACT12EgdN9xRrKK+bfljJCHPCmxsuR33JPuDVHrjAEeBF2ARkCKFe4eRT9DGNu/z nyC8DvyGR6CMKo9Go/bDCxBJCmpp+/rF3q7J3TabizuXwu1b1b5QMER5puR4pkZGYa5GI517tuJH xdMlazvzJatqlzNGOVtYu1td6PScESPPw0jc7emc4vXB9bZrc/XmzxOm3RvF8V/ffNpfcJN1/1fJ 4r+6pqsk/qsYAxH/PQQl11FVOaoFIMd/K+GLbKg6uaA5wNZpRczVLLzi+89/RvdUJbxwakQd0dv4 xlEvwzMIGqnmkcfTB0OMp0h0vFGo3uhtXPXy2OPzZ6dI/8lVzv09g1n/TUvr/0rSINR/SVGF/h+C yMyP0ZLc4n8/lDT5H/PpyfTq/PLLVfjvyfX88vL88tPJ5/nFl/PJ6ezLL2gdPISO+t5Lx7WD7HhI NmXpVhp/szZ9vDd8Wi6TcMCx+ypol1L931PtJ0Jc+q+H9b8lVeR/HYTIzHei/0pe/2Wh/8+EiP4r Sf2fPT0DXv9noA3UcP3XVbH+H4SeWf2fI9VJGyQLVVUVoePU/0HKMEUhLyNVb1r/Rzlq/R9Fknb1 X9OE/h+EMiebOhrjM3vhNoQyzN2GYNb/YQHw5G1TsbjStjlQqrO2OQCqk7bZAIz6P2wA/vo/XJgl FzsP705lEh5mav0fXhBa/R8eHP76PzwTD6r/UwlIyzivrf/DQqpNOmcxw3LOwSjQ+j+8gKW4DZi9 pv4PFYOv/g+4KdT6P2AEWv0fKkCTZPx6sCZZXE0Q61PxCeKQjVhd/wfIzJP2XQ9JSe1lMNEye5nP qk/sZbBT8npZXIW0Xt0aSkNTUjkAGmX1QieSp/4PEJMr1U1IR1468AFKGY0WN8eVDp7bANwGA5AM KGTi55AJrnRJbuMDSJZs0lBGqiTP6jvf2ahUcgJvE7D4eer/sLDA9X9AQID6PzwNqrhLAB4bylUC 6NxU3CSgsja6SMBAa7oDhUBSrhGAWwS/RcCAZOWCs9hbpII3Gn7GFQIoZjfbKtg9jD/CEHayY3g+ 3e1mMWxzdaBRU5suh4CLAwxevvo/VLDm9X94Ievr/1Si7dTvodf/YS1RtfV/CjDaqAZm5ty6YSLu CQqSHFUYADORvjwc1TAVg1v5/3ptCcbVpgrTlSbwEmOtZIpXqSIwVEpuPlleSh7JgTSWlJYNpcBq QKuTwhLD0w0s7R4Bg7+YnD4weG4RMKCbXSKIQMsp6dBR2NlaJFcIdvdRVEjIBQIqM+DaEZCXT0+g oHxqUjc+rItMjacsblLFpQ9gJ7vSMNCFqyYD31AwYU5vnnED33YBI8RHRNKqB5g41F+XGQxji6Qr ct4maYbGa5WKl2Xwj3cvyxgdWqYdx0I0JJXXZaC2qHxbhsUnLssISinN/zle/UfdyPJ/0/w/TRH5 P4egurCqhO3G8Btf/Uc6CrT+IxOhXR5RAtYykYgOA80koiNAU4l2EFj1H3kgoPUfeTF56z/S8ZvW fwQgsuo/MmUUVv+RCcOZikNTFM5cHKq+AXNnaPz0+o90jG5STgpo3eScACB5k06qIXnqPzIwwXHg Ihc8EFx+Gm8kuMgPDgWX2BpkjxQROgoGU0SkVSLQTz+fsNj+/uezXXSfJRrs+o9CNJ6BqvPUf+Rf DxoFqAAt5Q5QVWOCEjYoGx54xgZtswGo/8gEY9d/hEEA6z/ytQeUs0EbHXDSBmV+QFkbCW9HaRtF uG7yNiiY4MQNWpvaZG4UMfkD8SX+TiPxkDngTt6ggLbM3mAOIyOWfIxhbJfA8Rx73DKHgyk6rdbI TrM46kwNM42jyMxX/5GO1rz+Iz9mbf3H3YB+zcS2yROomwR6iUI6TpMShbvxmR3/05m9QqEXEi1D 79MYSeGgSXjl9dy39pPjByUppqOmbUwxauoe0mHqEiFK8VRIJBqiY4Vyinj3zIzRNpCaVsB1g8AH XBOsbhDmr9mQsxMP6GfTLuYbWkWVZ/AaJx/QACBVZht1Me0XrUQo11xCEg9Ajaovq9lMeVt0tXEW UxGg2zSm0u5or3lMsPFtOmvNcplousKRHsIILJSzO3LpHGSqcske4Mk6VHoH45wNSe6gzA47u6Mi 9CTSOwQJEiRIkCBBggQJEiRIkCBBggQJEiRIkCBBggQJEiRIkKCfif4P0wx0aQDIAAA= --ELM919917475-1022-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 20:46:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (Postfix) with ESMTP id 1634A14D45 for ; Wed, 24 Feb 1999 20:46:19 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.3/8.9.1) with ESMTP id XAA88833; Wed, 24 Feb 1999 23:45:22 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 24 Feb 1999 23:45:22 -0500 (EST) From: "Alok K. Dhir" To: "Daniel O'Connor" Cc: "Alok K. Dhir" , Current@Freebsd.Org Subject: RE: Staroffice 5.01? In-Reply-To: <85256723.00053D08.00@WBLN0014.worldbank.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 I was unable to install it. It complains about not being able to copy 'setup.zip' to '/tmp/sv001.tmp' and keeps bombing out. This is after pointing LD_LIBRARY_PATH to a place with glibc2, etc. Did you have any trouble installing? Al On Wed, 24 Feb 1999, Daniel O'Connor wrote: > > > On 24-Feb-99 Alok K. Dhir wrote: > > Has anyone gotten SO501 to run on -current? > I have and its quite good, but it hangs occasionally.. > The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..) > > What problems are you having? > > --- > 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 > > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 21: 5:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id EEDBD14D60; Wed, 24 Feb 1999 20:58:02 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10FspL-000I5dC; Wed, 24 Feb 1999 23:55:11 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: Missing files/directories In-Reply-To: <199902230822.IAA00707@keep.lan.Awfulhak.org> from Brian Somers at "Feb 23, 1999 8:22:47 am" To: brian@Awfulhak.org (Brian Somers) Date: Wed, 24 Feb 1999 23:55:11 -0500 (EST) Cc: tom@tomqnx.com, hackers@FreeBSD.ORG, current@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 Content-Length: 717 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot to mention to those following this thread, files and directories were definitely removed from /root that were not scheduled for writing under ANY circumstances, on the RELENG_3 machine. In fact, on the RELENG_3 machine all files and directories (except ALL the .xxxxx files) were removed from /root. I put a union on the /home directory nfsv2 exported from the 2.2-stable machine, which has been rock-solid ever since. THe problems that system had were when I was writing to its file system from RELENG_3. I am still very suspicious of those dot files even if I am the only one. All files and directories missing are ONLY missing from the directories to which I was writing the dot files! Cheers, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 21:10:24 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 6477D14DEC for ; Wed, 24 Feb 1999 21:10:18 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA01767; Thu, 25 Feb 1999 15:39:44 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: Thu, 25 Feb 1999 15:39:44 +1030 (CST) From: "Daniel O'Connor" To: "Alok K. Dhir" Subject: RE: Staroffice 5.01? Cc: Current@Freebsd.Org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-99 Alok K. Dhir wrote: > I was unable to install it. It complains about not being able to copy > 'setup.zip' to '/tmp/sv001.tmp' and keeps bombing out. This is after > pointing LD_LIBRARY_PATH to a place with glibc2, etc. > > Did you have any trouble installing? What I did was the following... Make this directory /usr/local/Office50/lib/ Unpack the glibc libs in there unzip -L the setup.zip file in the inst directory. cd into the inst directory and run setup --- 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 Wed Feb 24 21:22:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 6E76C14E35 for ; Wed, 24 Feb 1999 21:21:58 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA14623; Thu, 25 Feb 1999 16:20:20 +1100 Date: Thu, 25 Feb 1999 16:20:20 +1100 From: Bruce Evans Message-Id: <199902250520.QAA14623@godzilla.zeta.org.au> To: beyssac@enst.fr, freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've been having problems with an IDE controller on my motherboard. >I can't seem to be able to get it to recognize a CDROM drive (it's >the only device plugged on the second IDE controller). The kernel >seems to timeout on that second controller during the probe phase. >Maybe that's one of the infamous PIIX 4 bugs... The machine is a >Dell Optiplex. That's one of the infamous FreeBSD bugs :-). The wd probe has never really supported cdrom drives. It works best when there is an ordinary drive on the master and a cdrom drive on the slave. Then it essentially doesn't see the slave, and control passes to the atapi probe which does support cdrom drives. It works worst with a cdrom master and no slave. Then it at first sees the master as a broken ordinary drive and times out attempting to reset it. Then it does a quick subprobe for a cdrom drive, and if it sees a cdrom drive then it doesn't see an ordinary drive and control passes to the atapi probe ... The subprobe apparently doesn't work for new drives. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 21:30:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from pobox.ids.net (pobox.ids.net [155.212.1.122]) by hub.freebsd.org (Postfix) with ESMTP id 4E20714F20 for ; Wed, 24 Feb 1999 21:30:21 -0800 (PST) (envelope-from CGiordano@ids.net) Received: from ids.net (dyn082a.sco-ri.ids.net [155.212.204.82]) by pobox.ids.net (8.9.1a/8.9.1.1) with ESMTP id AAA23664; Thu, 25 Feb 1999 00:30:02 -0500 (EST) Message-ID: <36D4DEB1.35FEF648@ids.net> Date: Thu, 25 Feb 1999 00:25:05 -0500 From: "Christopher M. Giordano" Reply-To: CGiordano@ids.net X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Alok K. Dhir" Cc: current@FreeBSD.ORG Subject: Re: Staroffice 5.01? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alok K. Dhir" wrote: > > Has anyone gotten SO501 to run on -current? Yes, it runs fairly well "out of the box", without the registration problems of the previous version. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 22:32:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 31D0214C80 for ; Wed, 24 Feb 1999 22:32:26 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from q.bolero.rahul.net (bolero.rahul.net) by bolero-x.rahul.net with SMTP id AA15387 (5.67b8/IDA-1.5 for ); Wed, 24 Feb 1999 22:32:10 -0800 Message-Id: <199902250632.AA15387@bolero-x.rahul.net> Received: (qmail 14857 invoked from network); 25 Feb 1999 06:29:59 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 25 Feb 1999 06:29:59 -0000 To: freebsd-current@freebsd.org Subject: please don't check mail for root logins Date: Wed, 24 Feb 1999 22:29:58 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a suggestion for the FreeBSD maintainers. In /bin/login, please don't check for mail when the user is root. And in the case that the mail filesystem is mounted via NFS from a non-responding server, it hangs root logins. Root logins on machine A should never ever ever require machine B to be up. Rahul P.S. Patch on request, but it's too trivial to submit as one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 24 23:27: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id F303F14C43 for ; Wed, 24 Feb 1999 23:27:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA00776; Wed, 24 Feb 1999 23:26:47 -0800 (PST) (envelope-from dillon) Date: Wed, 24 Feb 1999 23:26:47 -0800 (PST) From: Matthew Dillon Message-Id: <199902250726.XAA00776@apollo.backplane.com> To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins References: <199902250632.AA15387@bolero-x.rahul.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a suggestion for the FreeBSD maintainers. : :In /bin/login, please don't check for mail when the user is root. And :in the case that the mail filesystem is mounted via NFS from a :non-responding server, it hangs root logins. : :Root logins on machine A should never ever ever require machine B :to be up. : :Rahul You should be able to fix this trivially in /etc/login.conf. Look at the standard: entry's setenv for MAIL and do something similar for root's, pointing MAIL somewhere else. I haven't 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 Thu Feb 25 0: 3:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A0EE814C11 for ; Thu, 25 Feb 1999 00:03:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA01163; Thu, 25 Feb 1999 00:03:15 -0800 (PST) (envelope-from dillon) Date: Thu, 25 Feb 1999 00:03:15 -0800 (PST) From: Matthew Dillon Message-Id: <199902250803.AAA01163@apollo.backplane.com> To: "Daniel C. Sobral" Cc: Jos Backus , Dmitrij Tejblum , freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <36D329D1.73146EEF@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Jos Backus wrote: :> :> > That is, INVARIANTS in kernel incompatible with dynamic loading. :> :> Somehow this strikes me as a Bad Thing... : :Invariants is not for the production minded. It is for those who :work with things likely to get broken. Say, for instance, -current. ::-) : :-- :Daniel C. Sobral (8-DCS) I would disagree with that. Invariants are for people who want their data to be as safe as possible and don't mind eating a little cpu doing extra sanity checks in the kernel. It is something I would almost certainly enable in a production kernel. DIAGNOSTIC, on the otherhand, is something I would only enable in an extreme test environment. :dcs@newsguy.com :dcs@freebsd.org -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 Feb 25 0:53:48 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 98BF914D18 for ; Thu, 25 Feb 1999 00:53:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA67980; Thu, 25 Feb 1999 08:52:51 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 25 Feb 1999 08:52:16 +0000 (GMT) From: Doug Rabson To: "Daniel O'Connor" Cc: "Alok K. Dhir" , current@freebsd.org Subject: RE: Staroffice 5.01? 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, 25 Feb 1999, Daniel O'Connor wrote: > > On 24-Feb-99 Alok K. Dhir wrote: > > Has anyone gotten SO501 to run on -current? > I have and its quite good, but it hangs occasionally.. > The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..) > > What problems are you having? Hangs sometimes for me too. It also has problems printing which is strange. From looking at the output, a stray character creeps into the postscript near the beginning. If I fix that by hand the postscript will print. -- 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 Thu Feb 25 0:58:38 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 1CF5F14CE1 for ; Thu, 25 Feb 1999 00:58:34 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA07804; Thu, 25 Feb 1999 19:28:10 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: Thu, 25 Feb 1999 19:28:10 +1030 (CST) From: "Daniel O'Connor" To: Doug Rabson Subject: RE: Staroffice 5.01? Cc: current@freebsd.org, "Alok K. Dhir" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-99 Doug Rabson wrote: > Hangs sometimes for me too. It also has problems printing which is > strange. From looking at the output, a stray character creeps into the > postscript near the beginning. If I fix that by hand the postscript will > print. Weird stuff.. I haven't used it much, but I did do a Word 97 to Word 95 conversion in it and it worked perfectly which impressed me :) --- 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 Feb 25 1:51:50 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 263CC14CF9 for ; Thu, 25 Feb 1999 01:49:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA69146; Thu, 25 Feb 1999 10:49:05 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902250949.KAA69146@freebsd.dk> Subject: Re: Promise IDE board docs In-Reply-To: <36d49bf8.1109180096@mail.sentex.net> from Mike Tancsa at "Feb 25, 1999 0:41:19 am" To: mike@sentex.net (Mike Tancsa) Date: Thu, 25 Feb 1999 10:49:05 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Mike Tancsa wrote: > On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote: > > > >Hmm, which suggests that I need to leave the "do it by hand" code in > >there and recommend removing the BIOS :( > > Are there any plans to support the Promise Fast Trak IDE RAID controller ? Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just with a more "advanced" BIOS that does the RAID stuff. The current planned support is to use it just as a Ultra33 controller, and then use ccd to do the RAID magic under FreeBSD. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 4:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 75FDD14D65 for ; Thu, 25 Feb 1999 04:15:51 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA17180 (5.67b8/IDA-1.5 for ); Thu, 25 Feb 1999 04:15:34 -0800 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA16445; Thu, 25 Feb 1999 04:15:31 -0800 Message-Id: <199902251215.AA16445@waltz.rahul.net> To: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins In-Reply-To: Message from Matthew Dillon of Wed, 24 Feb 99 23:26:47 -0800 Date: Thu, 25 Feb 99 04:15:30 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good idea, thanks, and I now realize that it won't work, and neither will changing /bin/login -- because sshd does not seem to honor either one. I will have to try re-installing sshd with the --with-login flag. When I last tried that flag, the use of a .hushlogin file caused failed logins for some reason, so I reinstalled sshd without --with-login . Drat! I hate it when software bypasses standard system routines. Rahul > Date: Wed, 24 Feb 99 23:26:47 PST > From: Matthew Dillon > To: Rahul Dhesi > Cc: freebsd-current@FreeBSD.ORG > Message-Id: <199902250726.XAA00776@apollo.backplane.com> > Subject: Re: please don't check mail for root logins > :I have a suggestion for the FreeBSD maintainers. > : > :In /bin/login, please don't check for mail when the user is root. And > :in the case that the mail filesystem is mounted via NFS from a > :non-responding server, it hangs root logins. > : > :Root logins on machine A should never ever ever require machine B > :to be up. > : > :Rahul > > You should be able to fix this trivially in /etc/login.conf. Look > at the standard: entry's setenv for MAIL and do something similar for > root's, pointing MAIL somewhere else. I haven't 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 4:35:58 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 2096414BFC; Thu, 25 Feb 1999 04:35:46 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Fzxh-000FpP-00; Thu, 25 Feb 1999 14:32:17 +0200 From: Sheldon Hearn To: tom@tomqnx.com (Tom Torrance at home) Cc: brian@Awfulhak.org (Brian Somers), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Missing files/directories In-reply-to: Your message of "Wed, 24 Feb 1999 23:55:11 EST." Date: Thu, 25 Feb 1999 14:32:17 +0200 Message-ID: <60846.919945937@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Feb 1999 23:55:11 EST, Tom Torrance at home wrote: > I am still very suspicious of those dot files even if I am the > only one. Hi Tom, Since it does indeed look like you _are_ the only one, I'd suggest putting this discussion on hold until you can come back to the list with the only thing that will carry the thread forward in a productive direction. Namely, come up with an _exact_ set of (preferably command-line) instructions for reproducing the problem. Since we're discussing free software, you can be fairly confident that this isn't a conspiracy to shut you up. It's just difficult for anyone to comment on symptoms he or she imagines impossible without seeing the problem you're reporting. If you can produce a step-by-step guide to reproducing the problem, you're more likely to get some solid answers to your questions. Until then, I imagine everyone else is probably thinking the same thing I am -- "wtf?!" :-) Later, Sheldon PS: I'd also suggest that you use just _one_ FreeBSD mailing list when you do follow up. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 4:50: 2 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 413C214D6D for ; Thu, 25 Feb 1999 04:49:59 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id HAA20577; Thu, 25 Feb 1999 07:48:09 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990225070213.05df08f0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 25 Feb 1999 07:56:22 -0500 To: =?iso-8859-1?Q?S=F8ren?= Schmidt From: Mike Tancsa Subject: Re: Promise IDE board docs Cc: current@FreeBSD.ORG In-Reply-To: <199902250949.KAA69146@freebsd.dk> References: <36d49bf8.1109180096@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:49 AM 2/25/99 , S=F8ren Schmidt wrote: >It seems Mike Tancsa wrote: >> On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote: >> > >> >Hmm, which suggests that I need to leave the "do it by hand" code in >> >there and recommend removing the BIOS :( >>=20 >> Are there any plans to support the Promise Fast Trak IDE RAID controller= ? > >Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just >with a more "advanced" BIOS that does the RAID stuff. The current planned >support is to use it just as a Ultra33 controller, and then use ccd to >do the RAID magic under FreeBSD. Interesting. So the BIOS doesnt actually do the RAID work ? It still needs to be done in software ? ---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 Thu Feb 25 5:54:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id D487F14D95; Thu, 25 Feb 1999 05:54:29 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id HAA05742; Thu, 25 Feb 1999 07:53:54 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id HAA05738; Thu, 25 Feb 1999 07:53:52 -0600 (CST) Message-ID: <022501be60c6$6107e110$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Kris Kennaway" Cc: "FreeBSD-Current" , "FreeBSD-Stable" Subject: Re: listproc problem? Date: Thu, 25 Feb 1999 07:54:34 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Also, as a side note, how do I set up my box to use PostFix instead of >> sendmail? I heard that it was (or was considered) included in the >> 3.1-RELEASE, it just wasn't enabled by default. > >It was shouted down as unnecessary bloat in favour of a port. However, I >haven't seen this port submitted yet..until then looks like you'll have to >install manually. > I have done that and it works pretty well. It is still BETA though. It is probably just as well that it isn't in the core distribution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 6:22:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 37DD014D82; Thu, 25 Feb 1999 06:22:16 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id OAA29673; Thu, 25 Feb 1999 14:21:56 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA39130; Thu, 25 Feb 1999 13:34:32 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199902251334.NAA39130@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn Cc: tom@tomqnx.com (Tom Torrance at home), brian@Awfulhak.org (Brian Somers), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Missing files/directories In-reply-to: Your message of "Thu, 25 Feb 1999 14:32:17 +0200." <60846.919945937@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 13:34:32 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > PS: I'd also suggest that you use just _one_ FreeBSD mailing list when > you do follow up. Indeed - Tom's using RELENG_3, not -current ;^P -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 6:22:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id CAA2914D86; Thu, 25 Feb 1999 06:22:21 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id OAA29676; Thu, 25 Feb 1999 14:22:00 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA39106; Thu, 25 Feb 1999 13:31:19 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199902251331.NAA39106@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: tom@tomqnx.com (Tom Torrance at home) Cc: brian@Awfulhak.org (Brian Somers), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Missing files/directories In-reply-to: Your message of "Wed, 24 Feb 1999 23:37:55 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 13:31:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Brian, > > It was a good thought, but we can't put the blame on bad hardware. > > These tests were done on the RELENG_3 system cvsup'd > as of Feb 22 @ 20:00 EST. All tests were run internal to the > same machine. So that I don't remain the only guy in the world > to see these test results, Control files are included so you > can test locally:-) Your best test engine would be either -current or using the latest ppp from my web site. The RELENG_3 version doesn't have a lot of recent changes. > "ppp0 -direct" on localhost is started by port 6671. > > I know (now) that setting up the test this way the ppp's were > communicating via localhost rather than the tunnel, but this way > was much cleaner as far as verifying exactly how close the results > were to what I saw running the server under 2.2-stable. There were > differences, but the main issues are demonstrated. Hmm, not 100% - see below. > You will recall our discussion about the server hanging around > under 2.2-stable after the client is terminated? Required by the > RFCs you said? Under RELENG_3 the server meekly goes away, which > makes sense to me. > > Two tests were done. The first involved "kill -KILL clientpid". > The second was "kill -TERM clientpid". > In the first test, the server illegally removed the default route. > In the second test, the server did the same - neither ppp actioned > the second command in the linkdown scripts. If a kill -KILL results in your default route disappearing, then that conclusively proves that ppp is not to blame :-/ If find this a bit strange though - this certainly doesn't happen on my machines - I frequently instruct my machine to connect to the 'net and then tunnel into an internal machine with something like ``ssh realmachine ssh internalmachine ppp -direct in''. In my setup, internalmachine is using realmachine as it's default gateway, and that default has never disappeared unexpectedly. WRT the second command, it looks like you've hit a problem that's next on my list to fix - since the radius changes, the interface netmasks are a bit faulty, and it's likely that there were some not-quite-so-bad problems in RELENG_3 too. Your commands should work ok if you change them to ``add 10.0.1.1/32 127.0.0.1'' and ``add 10.0.1.2/32 127.0.0.1''. > I was surprised that the first test ended immediately - I thought > the LQR packets would cause the server to terminate after 1 minute. When you specify the device as a tcp link or a program to execute, ppp can tell immediately when the peer goes away - the results are exactly the same as loosing carrier. This is why testing via the tcp link doesn't always cover all angles (I've suffered from these problems myself). The only problem is when we're using a device that's a character special that doesn't support CD (carrier) > Files: > test1.netstat0 shows routing after boot > test1.netstat1 shows routing after "ppp -background testloop" > test1.psaxl show ps results for the executing processes. > test1.netstat2 shows routing after killing the client. > test1.tun0 ifconfig while active. > test1.tun1 ifconfig while active. > test2.netstat routing tables after terminating the client. > Logs are supplied for both tests. > > I hope that this is very helpful to you. I really appreciate > your efforts!! And I yours - thanks. > Cheers, > Tom -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 7:52: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from filer2.isc.rit.edu (filer2.isc.rit.edu [129.21.3.107]) by hub.freebsd.org (Postfix) with ESMTP id 2155114DB9 for ; Thu, 25 Feb 1999 07:52:02 -0800 (PST) (envelope-from jcptch@osfmail.isc.rit.edu) Received: from grace ("port 3532"@[129.21.3.102]) by osfmail.isc.rit.edu (PMDF V5.2-31 #34621) with SMTP id <0F7P008H5W11ML@osfmail.isc.rit.edu> for freebsd-current@FreeBSD.ORG; Thu, 25 Feb 1999 10:51:01 -0500 (EST) Received: by grace (5.65v4.0/1.1.19.2/21Sep98-0910AM) id AA17284; Thu, 25 Feb 1999 10:51:01 -0500 Date: Thu, 25 Feb 1999 10:51:01 -0500 From: jcptch@osfmail.isc.rit.edu Subject: Re: please don't check mail for root logins In-reply-to: <199902251215.AA16445@waltz.rahul.net>; from Rahul Dhesi on Thu, Feb 25, 1999 at 04:15:30AM -0800 To: freebsd-current@FreeBSD.ORG Mail-followup-to: freebsd-current@FreeBSD.ORG Message-id: <19990225105101.A15559@osfmail.isc.rit.edu> MIME-version: 1.0 X-Mailer: Mutt 0.95i Content-type: text/plain; charset=us-ascii X-Operating-System: OSF1 alpha References: <199902251215.AA16445@waltz.rahul.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999 at 04:15:30AM -0800, Rahul Dhesi wrote: > Good idea, thanks, and I now realize that it won't work, and neither > will changing /bin/login -- because sshd does not seem to honor either > one. You could try taking a look in sshd_config and setting UseLogin Yes. -- Jon Parise (parise@pobox.com) . .: current environment :. Rochester Inst. of Technology : OSF1 grace V4.0 878 alpha Computer Science House Member : user: jcptch host: grace https://www.csh.rit.edu/~jon/ : term: vt100 tty: ttysb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 7:55:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from landsraad.net (caladan.arrakis.es [195.5.65.34]) by hub.freebsd.org (Postfix) with ESMTP id BBF8514E1C for ; Thu, 25 Feb 1999 07:54:57 -0800 (PST) (envelope-from magickey@arrakis.es) Received: from 10.0.1.1.inf (ih-228.arrakis.es [195.5.77.228]) by landsraad.net (8.9.3/8.9.3) with SMTP id QAA28103 for freebsd-current@freebsd.org; Thu, 25 Feb 1999 16:56:46 +0100 (MET) Date: Thu, 25 Feb 1999 16:56:46 +0100 (MET) From: magickey@arrakis.es To: freebsd-current@freebsd.org Subject: ELECTRONIC ILLUSIONS FOR MAGICIANS Message-Id: Content-Type: TEXT/PLAIN charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear magician: This letter is to present you my new catalogue, videocatalogue (VHS PAL videocassette) AND WEB of electronic equipment for magicians. I am looking forward to hearing from you with any questions you have. Yours faithfully Eduardo Hernando de Liñán Director of La Llave Magica If you wish to be removed from this list please contact WRITE IN Subject: DELETE magickey@arrakis.es AMIGO EN LA MÁGIA: ME DIRIJO A TI PARA PRESENTARTE MI COLECCÍÓN DE EFECTOS DE ILUSIONISMO ELÉCTRÓNICOS, PODRAS ENCONTRARLOS EN JUNTO A ELLOS, TAMBIÉN ENCONTRARAS UN CATÁLOGO DE PIROTÉCNIA, PARA ESCENARIOS Y DE EFECTOS DE ILUMINACIÓN DE ÚLTIMA GENERACIÓN. EN EL DESEO DE QUE ELLOS TE APORTEN TANTAS SATISFACCIONES COMO ME HAN PROPORCIONADO A MÌ, QUEDO ENTERAMENTE A TU DISPOSICIÓN. Atentamente Eduardo Hernando de Liñan PARA NO RECIBIR NUNCA MÁS NUESTRA CIRCULAR, ENVIE UN MAIL INDICANDO EN Asunto: DELETE magickey@arrakis.es To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 8:17:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id CD28B14DCF for ; Thu, 25 Feb 1999 08:17:15 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id RAA00620; Thu, 25 Feb 1999 17:16:54 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.2/8.8.8) id RAA00983; Thu, 25 Feb 1999 17:16:53 +0100 (CET) Message-ID: <19990225171653.A846@enst.fr> Date: Thu, 25 Feb 1999 17:16:53 +0100 From: Pierre Beyssac To: Greg Lehey , Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <19990224235117.A9283@enst.fr> <11472.919897269@axl.noc.iafrica.com> <19990225010448.A335@enst.fr> <19990225140931.K52343@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990225140931.K52343@lemis.com>; from Greg Lehey on Thu, Feb 25, 1999 at 02:09:31PM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999 at 02:09:31PM +1030, Greg Lehey wrote: > > Wow. Thanks a million! I didn't even have to go so far, I just > > deleted wd2 and wd3 and acd0 now appears as if by magic. I can't > > tell you how extremely stupid I now feel... > > You shouldn't do. What you did shouldn't have any effect on the > problem. Yet it definitely has. The CDROM never probed before, now it does (at least every time I tried: only about half a dozen reboots for the moment). So there's probably something strange with the probe code and how it interacts with wd[0-3] declarations. So the CDROM now probes correctly, but OTOH I didn't manage to use it. I get the following message every time: bofh /kernel: atapi1.0: controller not ready for cmd The machine then seems to hang, more or less (X11 kindly moves the mouse pointer, but the network is dead). > FreeBSD still has difficulties with some ATAPI CD-ROM drives. If you > continue to have trouble (and I suspect you will), you should enter a > PR with send-pr or at http://www.freebsd.org/send-pr.html. Make sure > to give exact details of your hardware and software configuration. I tried to find out why it worked with a Linux kernel by comparing our IDE code and theirs, but it was way beyond my comprehension. I'm not trained for the black magic of IDE probing. I'll try to investigate some more, then I'll try a bug report. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 8:26:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id E830414BE9 for ; Thu, 25 Feb 1999 08:26:34 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id RAA01065; Thu, 25 Feb 1999 17:26:16 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.2/8.8.8) id RAA01060; Thu, 25 Feb 1999 17:26:14 +0100 (CET) Message-ID: <19990225172614.B846@enst.fr> Date: Thu, 25 Feb 1999 17:26:14 +0100 From: Pierre Beyssac To: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <199902250520.QAA14623@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902250520.QAA14623@godzilla.zeta.org.au>; from Bruce Evans on Thu, Feb 25, 1999 at 04:20:20PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999 at 04:20:20PM +1100, Bruce Evans wrote: > doesn't see the slave, and control passes to the atapi probe which does > support cdrom drives. It works worst with a cdrom master and no slave. Sadly, that's exactly the out-of-the-box Dell configuration: 2 disks on the first IDE, just a CDROM on the second IDE. I'd have changed the hardware configuration to swap the second disk with the CDROM, but I thought it would be much better if it could be made to work, since it apparently can... -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 8:40:56 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 F40A514D46 for ; Thu, 25 Feb 1999 08:40:31 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10G3ow-0001ks-00; Thu, 25 Feb 1999 18:39:30 +0200 From: Sheldon Hearn To: Pierre Beyssac Cc: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Thu, 25 Feb 1999 17:16:53 +0100." <19990225171653.A846@enst.fr> Date: Thu, 25 Feb 1999 18:39:30 +0200 Message-ID: <6749.919960770@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Feb 1999 17:16:53 +0100, Pierre Beyssac wrote: > I tried to find out why it worked with a Linux kernel by comparing > our IDE code and theirs, but it was way beyond my comprehension. > I'm not trained for the black magic of IDE probing. I used this particular issue for the launch of my first adventure into serial console kernel debugging. Multo fun. I can offer you two interesting points: 1) I have an ATAPI drive that FreeBSD 2.2-STABLE won't detect on boot if it contains a disc. 2) I found that stepping through the kernel caused exactly the same problems I was having with accessing my one ATAPI drive that I experience just running normally with my other drive. So it looks like at least one problem regarding ATAPI has to do with timings. So far, the conversations I've had with clueful FreeBSD hackers have led me to accept the following: A) The ATAPI standard is weak and the variety of implimentations thereof is even worse. B) The odds that your ATAPI CDROM drive will behave predictably in accordance with said standards are directly proportional to its age. It seems that newer (24xspeed+) drives suck. C) The ATAPI code in FreeBSD is about as good as our hackers care to make it, given the demotivating impact of A and B above. I spent a good few days stepping around my kernel over serial connection, using a "working" 4xspeed drive and a "broken" 36xspeed drive and testing a reproducible fault with cdcontrol. I'm a pretty stubborn guy, but I gave up. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 8:41:24 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 2962014DA5 for ; Thu, 25 Feb 1999 08:41:18 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10G3pz-0001lf-00; Thu, 25 Feb 1999 18:40:35 +0200 From: Sheldon Hearn To: Pierre Beyssac Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Thu, 25 Feb 1999 17:26:14 +0100." <19990225172614.B846@enst.fr> Date: Thu, 25 Feb 1999 18:40:35 +0200 Message-ID: <6798.919960835@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Feb 1999 17:26:14 +0100, Pierre Beyssac wrote: > I'd have changed the hardware configuration to swap the second disk > with the CDROM, but I thought it would be much better if it could > be made to work, since it apparently can... Nope, it's almost certainly better to have your random access disks on two different controllers. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 9:10:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id A3EC014DA3 for ; Thu, 25 Feb 1999 09:10:05 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Thu, 25 Feb 1999 18:12:05 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D09754E@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Sheldon Hearn' , Pierre Beyssac Cc: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: RE: IDE CDROM not found with PIIX4 chipset, -current kernel Date: Thu, 25 Feb 1999 18:07:39 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Sheldon Hearn [SMTP:sheldonh@iafrica.com] > Sent: Thursday, February 25, 1999 5:40 PM > To: Pierre Beyssac > Cc: Greg Lehey; freebsd-current@FreeBSD.ORG > Subject: Re: IDE CDROM not found with PIIX4 chipset, -current > kernel > > > > On Thu, 25 Feb 1999 17:16:53 +0100, Pierre Beyssac wrote: > > > I tried to find out why it worked with a Linux kernel by comparing > > our IDE code and theirs, but it was way beyond my comprehension. > > I'm not trained for the black magic of IDE probing. > > I used this particular issue for the launch of my first adventure into > serial console kernel debugging. Multo fun. > > I can offer you two interesting points: > > 1) I have an ATAPI drive that FreeBSD 2.2-STABLE won't detect on boot > if > it contains a disc. > > 2) I found that stepping through the kernel caused exactly the same > problems I was having with accessing my one ATAPI drive that I > experience just running normally with my other drive. So it looks > like at least one problem regarding ATAPI has to do with timings. > > So far, the conversations I've had with clueful FreeBSD hackers have > led > me to accept the following: > > A) The ATAPI standard is weak and the variety of implimentations > thereof > is even worse. > > B) The odds that your ATAPI CDROM drive will behave predictably in > accordance with said standards are directly proportional to its > age. > It seems that newer (24xspeed+) drives suck. > > C) The ATAPI code in FreeBSD is about as good as our hackers care to > make it, given the demotivating impact of A and B above. > > I spent a good few days stepping around my kernel over serial > connection, using a "working" 4xspeed drive and a "broken" 36xspeed > drive and testing a reproducible fault with cdcontrol. I'm a pretty > stubborn guy, but I gave up. [ML] Heh, it would seem that the prevailing OS is not really ATAPI compliant and the manufacturers try to make their hardware more easily detectable for the prevailing OS family. How about this "brilliant" idea: put a logic analyzer on the IDE cable and measure the timings the prevailing OS family/BIOS uses? Sadly, I don't have access to a logic analyzer :( Anyone with (good) connections to a (university) hardware lab? /Marino > Ciao, > Sheldon. > > > 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 Thu Feb 25 9:15: 4 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 C4CE914D20 for ; Thu, 25 Feb 1999 09:14:58 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10G4MQ-0001pK-00; Thu, 25 Feb 1999 19:14:06 +0200 From: Sheldon Hearn To: Ladavac Marino Cc: Pierre Beyssac , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Thu, 25 Feb 1999 18:07:39 +0100." <97A8CA5BF490D211A94F0000F6C2E55D09754E@s-lmh-wi-900.corpnet.at> Date: Thu, 25 Feb 1999 19:14:06 +0200 Message-ID: <7025.919962846@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Feb 1999 18:07:39 +0100, Ladavac Marino wrote: > How about this "brilliant" idea: put a logic analyzer on the IDE > cable and measure the timings the prevailing OS family/BIOS uses? My understanding from previous conversations is that the situation you're often faced with is that you'll break support for one set of drives by fixing support for another. Ciao, Sheldon. PS: It's not usually necessary to quote back the entire content of a message you reply to when you're replying less than 30 minutes after the original was posted. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 9:54:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 5ACCE14DFF for ; Thu, 25 Feb 1999 09:54:41 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id SAA05140; Thu, 25 Feb 1999 18:54:22 +0100 (MET) Received: (from beyssac@localhost) by bofh.enst.fr (8.9.2/8.8.8) id SAA01732; Thu, 25 Feb 1999 18:54:18 +0100 (CET) Message-ID: <19990225185418.C846@enst.fr> Date: Thu, 25 Feb 1999 18:54:18 +0100 From: Pierre Beyssac To: Sheldon Hearn Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <19990225172614.B846@enst.fr> <6798.919960835@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <6798.919960835@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Feb 25, 1999 at 06:40:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999 at 06:40:35PM +0200, Sheldon Hearn wrote: > > I'd have changed the hardware configuration to swap the second disk > > with the CDROM, but I thought it would be much better if it could > > be made to work, since it apparently can... > > Nope, it's almost certainly better to have your random access disks on > two different controllers. Oh yes, I won't try to argue against that since I quite agree. I'll try this once I get tired trying my current config :-). I was just considering that the more configurations that work, the better for FreeBSD's ease of installation/configuration. The problem is bound to happen again since this is a configuration (CDROM by itself on a second IDE controller) currently sold by Dell. Don't ask me why, Dell always tends to make weird choices regarding how they install IDE devices and controllers. I suspect this has to do with this weird, differently abled stuff sold by a major company which lost the source code for it, arrogant enough to call it an OS. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 12:17:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id E93EB14E29 for ; Thu, 25 Feb 1999 12:17:10 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id MAA01740 for ; Thu, 25 Feb 1999 12:16:56 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199902252016.MAA01740@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: Promise IDE board docs In-reply-to: Your message of "Thu, 25 Feb 1999 07:56:22 EST." <4.1.19990225070213.05df08f0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 25 Feb 1999 12:16:56 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, = just > >with a more "advanced" BIOS that does the RAID stuff. The current plan= ned > >support is to use it just as a Ultra33 controller, and then use ccd to= > >do the RAID magic under FreeBSD. > = > Interesting. So the BIOS doesnt actually do the RAID work ? It still n= eeds > to be done in software ? I think what he means is that if the OS supports it, the RAID stuff is done in the BIOS. We don't yet support it, so it has to be done with sof= tware. as an aside, I'd suggest vinum over ccd for the software part. I have two 4 gig drives, and the performance is on par with what = I've seen from single 8 and even 12 gig drives. Cheers, -- = obfuscate v.t. darken; obscure; bewilder. int i;main(){for(;i["]; Thu, 25 Feb 1999 12:56:19 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA02983 for Current@FreeBSD.ORG; Thu, 25 Feb 1999 21:55:57 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CC90C8832; Thu, 25 Feb 1999 21:27:06 +0100 (CET) Date: Thu, 25 Feb 1999 21:27:06 +0100 From: Ollivier Robert To: Current@FreeBSD.ORG Subject: Re: Staroffice 5.01? Message-ID: <19990225212706.A12474@keltia.freenix.fr> Mail-Followup-To: Current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Daniel O'Connor on Thu, Feb 25, 1999 at 03:39:44PM +1030 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5084 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Daniel O'Connor: > unzip -L the setup.zip file in the inst directory. > cd into the inst directory and run setup You don't even need this with 5.01. I installed it today on my 4.0-CURRENT machine and everything went fine. I'used the same method as described on . -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 12:57:57 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 66E3B14DA4 for ; Thu, 25 Feb 1999 12:57:00 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA02986 for freebsd-current@FreeBSD.ORG; Thu, 25 Feb 1999 21:56:42 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4AEBC8832; Thu, 25 Feb 1999 21:31:36 +0100 (CET) Date: Thu, 25 Feb 1999 21:31:36 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins Message-ID: <19990225213136.B12474@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199902251215.AA16445@waltz.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199902251215.AA16445@waltz.rahul.net>; from Rahul Dhesi on Thu, Feb 25, 1999 at 04:15:30AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5084 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Rahul Dhesi: > Good idea, thanks, and I now realize that it won't work, and neither > will changing /bin/login -- because sshd does not seem to honor either > one. The sshd in ports should honor the login.conf stuff. One of the patches adds FreeBSD as a target with login_cap.h. Look into patch-af in sshd/patches. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 13:21:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (Postfix) with ESMTP id 40A0814E01 for ; Thu, 25 Feb 1999 13:21:44 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.3/8.9.1) with ESMTP id QAA06613; Thu, 25 Feb 1999 16:18:11 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 25 Feb 1999 16:18:10 -0500 (EST) From: "Alok K. Dhir" To: Ollivier Robert Cc: Current@Freebsd.Org Subject: Re: Staroffice 5.01? In-Reply-To: <85256723.00734913.00@WBLN0014.worldbank.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 Thanks all - I finally got it to work. It still stops and asks me to "insert StarOffice 5.01, yes, no, cancel". Hitting cancel a few times allows the installation to continue. I had gotten this far before, but didn't try hitting cancel. Does anyone's installation allow them to use the web browsing or email component? Al On Thu, 25 Feb 1999, Ollivier Robert wrote: > > According to Daniel O'Connor: > > unzip -L the setup.zip file in the inst directory. > > cd into the inst directory and run setup > > You don't even need this with 5.01. I installed it today on my 4.0-CURRENT > machine and everything went fine. I'used the same method as described on > . > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 13:48: 9 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 6615314DCC for ; Thu, 25 Feb 1999 13:48:03 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA00506; Thu, 25 Feb 1999 13:47:46 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id NAA01813; Thu, 25 Feb 1999 13:47:46 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 25 Feb 1999 13:47:46 -0800 (PST) Message-Id: <199902252147.NAA01813@vashon.polstra.com> To: dot@dotat.at Subject: Re: mount -o union broken recently? In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Tony Finch wrote: > I have been experimenting with union mounts today with a recent > -stable (cvsupped yesterday), and I haven't had much luck. > > Because cvsup likes to obliterate local changes, You might wish to CVSup the repository itself (not use checkout mode), and then apply the techniques described in the CVSup FAQ to maintain your local changes. You can find the CVSup FAQ at . I've never messed with "mount -o union" before. But looking at the tests you did, I'm not so sure you've drawn the right conclusions. Here's your test that failed: > # mount > /dev/da0s1a on / (local, writes: sync 420 async 3185) > procfs on /proc (local) > /dev/da0s1e on /www (local, writes: sync 2 async 0) > # mount /dev/da0s1f /srcdelta > # ls -l /srcdelta > total 1 > drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys > # umount /srcdelta > # ls /usr/src > COPYRIGHT UPDATING include share > CVS bin kerberosIV sys > Makefile contrib lib tools > Makefile.inc0 crypto libexec usr.bin > Makefile.inc1 etc release usr.sbin > Makefile.upgrade games sbin > README gnu secure > # mount -o union /dev/da0s1f /usr/src > # ls -l /usr/src > total 1 > drwxr-xr-x 6 root wheel 512 Feb 18 10:32 sys > # umount /usr/src > # uname -a > FreeBSD shirt.www.demon.net 3.1-STABLE FreeBSD 3.1-STABLE #6: Thu Feb 18 02:26:59 GMT 1999 root@shirt.www.demon.net:/usr/src/sys/compile/SHIRT i386 > # OK, in that test, you did the union mount onto "/usr/src", which was _not_ a mount point. But you did something different in the test that succeeded: > However, on another machine running 3.0-RELEASE mount -o union works > as expected: > > # ls -l > total 6 > drwxr-xr-x 2 root wheel 512 Feb 18 16:36 da1 > drwxr-xr-x 2 root wheel 512 Dec 11 11:06 da2 > # mount /dev/da1s1e da1 > # mount /dev/da2s1e da2 > # ls -l da?/* > -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 > -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da2/this_is_da2 > # umount da2 > # mount -o union /dev/da2s1e /www/da1 > # ls -l da?/* > -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da1 > -rw-r--r-- 1 root wheel 0 Feb 18 16:36 da1/this_is_da2 > # Here, you did the union mount on top of an existing mount point (da1). I don't know for sure, but I suspect that this is the only case in which union mounts are designed to work. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 14:14: 3 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 BDD0214DFE for ; Thu, 25 Feb 1999 14:14:01 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA13731; Thu, 25 Feb 1999 14:03:38 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdc13716; Thu Feb 25 22:03:21 1999 Date: Thu, 25 Feb 1999 14:03:07 -0800 (PST) From: Julian Elischer To: John Polstra Cc: dot@dotat.at, current@FreeBSD.ORG Subject: Re: mount -o union broken recently? In-Reply-To: <199902252147.NAA01813@vashon.polstra.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, 25 Feb 1999, John Polstra wrote: [...] > > Here, you did the union mount on top of an existing mount point (da1). > I don't know for sure, but I suspect that this is the only case in > which union mounts are designed to work. I was led to believe (last time I read the code) that any directory should be ok for a union mount.... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 15: 8:52 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 2116E14DDF; Thu, 25 Feb 1999 15:08:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id XAA12061; Thu, 25 Feb 1999 23:08:31 GMT 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 QAA04402; Thu, 25 Feb 1999 16:08:35 -0700 (MST) Message-Id: <199902252308.QAA04402@harmony.village.org> To: Palle Girgensohn Subject: Re: panic: aha0 Invalid CCB or SG list Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 25 Feb 1999 03:08:18 +0100." <36D4B092.8B076D55@partitur.se> References: <36D4B092.8B076D55@partitur.se> Date: Thu, 25 Feb 1999 16:08:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36D4B092.8B076D55@partitur.se> Palle Girgensohn writes: : I've seen three crashes in the last couple of weeks, with a server : box that's been running stable as a rock for two years, at least. It : has an adaptec 2940UW with six disks, and an adaptec 1542CP that's : connected to a seagate travan tape driver. OK. This card is known to be good. At least I've not had any problems with it. : It's running STABLE-3.1 from Feb 19 1999, and since the last : upgrade, I've seen three crashes, all related to dumping to : tape. Since I got no info on what happened, I decided to sit down : with the machine, run a backup sequence to tape, and wait for it to : possibly crash. After 90 minutes, I was about to give up when : suddenly, poof: : panic: aha0 Invalid CCB or SG list. : : So, it's probably the 1540 driver (or hardware)? Ah. OK. I'm not doing tape stuff on my machine. How fast is that seagate tr-4 that you are doing? : Can anybody shed some light on what to do? Is it software? That's my : guess, since the machine never ONCE has crashed until the upgrade to : 3.x. I had one crash when running current form beginning of January : (soon after moving to 3.x), and now theese three in a week. The 1540 : has been in the machine for about six months. Chances are really good that this is software. The invalid ccb or sg list is due to either a race condition or something taht corrupts these things. : If there's anything I can do to help debug I'll do it, but device : drivers are a little above my level of expertise. If you can wait a day or three, I might be able to find something that will help. However, I don't have a tape drive right now to test it with. I'll see what I can beg, borrow or steal. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 15:23:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 37DC314E48 for ; Thu, 25 Feb 1999 15:23:12 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA19922 (5.67b8/IDA-1.5 for ); Thu, 25 Feb 1999 15:22:56 -0800 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA19634; Thu, 25 Feb 1999 15:08:38 -0800 Message-Id: <199902252308.AA19634@waltz.rahul.net> To: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins In-Reply-To: Message from jcptch@osfmail.isc.rit.edu of Thu, 25 Feb 99 10:51:01 -0500 Date: Thu, 25 Feb 99 15:08:38 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG UserLogin is just a flag that is needed to enable --with-login at runtime. It doesn't prevent failed logins when a .hushlogin file is present -- that's a bug in sshd that will need to be fixed first. Rahul > Date: Thu, 25 Feb 99 10:51:01 EST > From: jcptch@osfmail.isc.rit.edu > To: freebsd-current@FreeBSD.ORG > Message-Id: <19990225105101.A15559@osfmail.isc.rit.edu> > Subject: Re: please don't check mail for root logins > On Thu, Feb 25, 1999 at 04:15:30AM -0800, Rahul Dhesi wrote: > > > Good idea, thanks, and I now realize that it won't work, and neither > > will changing /bin/login -- because sshd does not seem to honor either > > one. > > You could try taking a look in sshd_config and setting UseLogin Yes. > > -- > Jon Parise (parise@pobox.com) . .: current environment :. > Rochester Inst. of Technology : OSF1 grace V4.0 878 alpha > Computer Science House Member : user: jcptch host: grace > https://www.csh.rit.edu/~jon/ : term: vt100 tty: ttysb > > > 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 Thu Feb 25 15:26: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 EEC1E14E15 for ; Thu, 25 Feb 1999 15:26:10 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA10222 for Current@Freebsd.Org; Fri, 26 Feb 1999 00:25:51 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 42AC28833; Thu, 25 Feb 1999 23:37:51 +0100 (CET) Date: Thu, 25 Feb 1999 23:37:51 +0100 From: Ollivier Robert To: Current@Freebsd.Org Subject: Re: Staroffice 5.01? Message-ID: <19990225233751.B13230@keltia.freenix.fr> Mail-Followup-To: Current@Freebsd.Org References: <85256723.00734913.00@WBLN0014.worldbank.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Alok K. Dhir on Thu, Feb 25, 1999 at 04:18:10PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5084 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alok K. Dhir: > Thanks all - I finally got it to work. It still stops and asks me to > "insert StarOffice 5.01, yes, no, cancel". Hitting cancel a few times > allows the installation to continue. I haven't seen this. > Does anyone's installation allow them to use the web browsing or > email component? The web browing part works beautifully (although SO5 is by itself more memory hungry than Netscape :-)) and I haven't tried the mail part. I don't even plan to test it, Mutt is working perfectly. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 16:24:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles204.castles.com [208.214.165.204]) by hub.freebsd.org (Postfix) with ESMTP id 0CFC614DD6 for ; Thu, 25 Feb 1999 16:24:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA02795; Thu, 25 Feb 1999 16:18:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902260018.QAA02795@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jos Backus Cc: freebsd-current@freebsd.org Subject: Re: panic: zone: entry not free In-reply-to: Your message of "Mon, 22 Feb 1999 19:59:32 +0100." <19990222195932.A94515@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 16:18:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you thought you could follow the code around a bit and work out why it's happening, that would be very helpful... > This occurs almost immediately after copying a file to an msdos fs. I can > provide more info if that is deemed useful. > > FreeBSD jos.mp-c.com 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Sat Feb 20 19:31:56 > CET 1999 jos@jos.mp-c.com:/usr/src/sys/compile/JOS i386 > > Thanks, > -- > 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 > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Thu Feb 25 16:30:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D44B14DFA for ; Thu, 25 Feb 1999 16:29:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA10608; Thu, 25 Feb 1999 16:29:14 -0800 (PST) (envelope-from dillon) Date: Thu, 25 Feb 1999 16:29:14 -0800 (PST) From: Matthew Dillon Message-Id: <199902260029.QAA10608@apollo.backplane.com> To: Rahul Dhesi Cc: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins References: <199902252308.AA19634@waltz.rahul.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :UserLogin is just a flag that is needed to enable --with-login at runtime. :It doesn't prevent failed logins when a .hushlogin file is present -- :that's a bug in sshd that will need to be fixed first. : :Rahul There is a 'CheckMail' option. You should be able to set it to NO. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 16:39:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles204.castles.com [208.214.165.204]) by hub.freebsd.org (Postfix) with ESMTP id 3DD3A14DFF for ; Thu, 25 Feb 1999 16:39:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA02910; Thu, 25 Feb 1999 16:34:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902260034.QAA02910@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jan B. Koum " Cc: current@freebsd.org, "Michael T. Stolarchuk" Subject: Re: [mts@off.to: freebsd low kernel expert...] In-reply-to: Your message of "Mon, 22 Feb 1999 06:46:15 PST." <19990222064614.D14395@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 16:34:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i'm looking for someone who can answer some questions about > interrupt processing code in freebsd 3.0... not the stuff > after the SMP processors get to C code, but the glue between > the hardware and the C code... Bruce Evans (bde@freebsd.org) and Steve Passe (fsmp@freebsd.org) are probably your best contacts. > i want to find the `pc' of the interrupting processor... i can > find the pc of the other processors, but don't yet know how > to get the previous-pc for the processor which fielded the > interrupt. If you're referring to the pc at which the processor running the interrupt handler was interrupted, I expect that you'll have to unwind the stack to find it. Note that AFAIK we support multiple interrupt entry, so you may have one handler interrupted by another. It may be easier if you have a specific context in which you need to get at the suspended PC. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Thu Feb 25 16:58:45 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 0A9F614DD6 for ; Thu, 25 Feb 1999 16:58:37 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA16016; Fri, 26 Feb 1999 11:28:14 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: Fri, 26 Feb 1999 11:28:14 +1030 (CST) From: "Daniel O'Connor" To: "Alok K. Dhir" Subject: Re: Staroffice 5.01? Cc: Current@FreeBSD.ORG, Ollivier Robert Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Feb-99 Alok K. Dhir wrote: > Does anyone's installation allow them to use the web browsing or > email component? It hangs when I try to use IMAP.. --- 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 Feb 25 17:25:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id EF96414E3D for ; Thu, 25 Feb 1999 17:25:22 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id JAA27894 for ; Fri, 26 Feb 1999 09:25:05 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id JAA03495 for freebsd-current@freebsd.org; Fri, 26 Feb 1999 09:25:02 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902260125.JAA03495@b1.hkstar.com> Subject: how to set the ne2000 pci network card in the config file To: freebsd-current@freebsd.org Date: Fri, 26 Feb 1999 09:25:02 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I recently found that my pci network card didn't work for me any more. It was recognized by the system but I could config it. This didn't happen before and I didn't why. I had tried to config it as ed1 .... in my config file. Then it was probed by the system as ed2 .... When I tried to config it as ed2 in the config file. It was probed by the system as ed3. Can anyone tell me how to solve it. Thanks.c Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 17:45: 0 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 26E0814DA2 for ; Thu, 25 Feb 1999 17:44:56 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id UAA05210 for ; Thu, 25 Feb 1999 20:44:35 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20980; Thu, 25 Feb 1999 20:44:34 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id UAA74596 for freebsd-current@freebsd.org; Thu, 25 Feb 1999 20:44:34 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199902260144.UAA74596@bb01f39.unx.sas.com> Subject: Really! strange uid value To: freebsd-current@freebsd.org Date: Thu, 25 Feb 1999 20:44:34 -0500 (EST) 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 have some machines running 3.0-19981209-SNAP. I have seen some core dumps from pdksh (which I haven't figured out yet) that have some really strange uid values. -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink Well, I must say I'm impressed that FreeBSD can support a user base that is so large! :-) :-) Has anyone else run into this? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 18:18:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 8405C14DFA for ; Thu, 25 Feb 1999 18:18:23 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id UAA19445; Thu, 25 Feb 1999 20:17:51 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <020301be612e$364f2920$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Chan Yiu Wah" Cc: References: <199902260125.JAA03495@b1.hkstar.com> Subject: Re: how to set the ne2000 pci network card in the config file Date: Thu, 25 Feb 1999 20:17:50 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.203 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.203 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Chan Yiu Wah > I recently found that my pci network card didn't work for me any more. It > was recognized by the system but I could config it. This didn't happen before > and I didn't why. I had tried to config it as ed1 .... in my config file. > Then it was probed by the system as ed2 .... When I tried to config it as ed2 > in the config file. It was probed by the system as ed3. Can anyone tell me > how to solve it. Thanks.c > If you could show us how you were configuring ed[1,2] in your config file we would probably be able to help you. You possibly are using: device ed1 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr This sets up ed1 for a ed* ISA card. Thus when the system probe finds your card, it assigns it as ed2, since PCI devices are automatically assigned to the next ed* interface. You should change you config file so that the device line looks as follows: device ed1 This will set it up so that the first ed* PCI card found is assigned to the ed1 interface. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 20:14:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip221.houston2.tx.pub-ip.psi.net [38.11.201.221]) by hub.freebsd.org (Postfix) with ESMTP id AC06314E99 for ; Thu, 25 Feb 1999 20:13:58 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.2/8.9.2) id WAA00613; Thu, 25 Feb 1999 22:14:33 -0600 (CST) (envelope-from chris) Date: Thu, 25 Feb 1999 22:14:31 -0600 From: Chris Costello To: "John W. DeBoskey" Cc: current@freebsd.org Subject: Re: Really! strange uid value Message-ID: <19990225221431.A504@holly.dyndns.org> Reply-To: chris@calldei.com References: <199902260144.UAA74596@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: <199902260144.UAA74596@bb01f39.unx.sas.com>; from John W. DeBoskey on Thu, Feb 25, 1999 at 08:44:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 25, 1999, John W. DeBoskey put this into my mailbox: > Hi, > > I have some machines running 3.0-19981209-SNAP. I have seen > some core dumps from pdksh (which I haven't figured out yet) > that have some really strange uid values. > > -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink > > Well, I must say I'm impressed that FreeBSD can support a user > base that is so large! :-) :-) > > > Has anyone else run into this? Tried running fsck? > > > Thanks! > John > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- "In order to make an apple pie from scratch, you must first create the universe." -- Carl Sagan, Cosmos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 23: 2:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 4C9A014ECF; Thu, 25 Feb 1999 23:02:51 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id XAA82677; Thu, 25 Feb 1999 23:02:35 -0800 (PST) From: Archie Cobbs Message-Id: <199902260702.XAA82677@bubba.whistle.com> Subject: New mpd release available To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Date: Thu, 25 Feb 1999 23:02:35 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (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 FYI, A new release of mpd is available in ports/net/mpd, or at: ftp://ftp.whistle.com/pub/archie/mpd New features: - Support for netgraph: PPP over synchronous lines, frame relay, etc. - Includes much more complete chat script (eg, auto-programs your Bitsurfr, incoming ring dial-back, etc) - Complete user/reference manual included Next step: using netgraph ppp and interface nodes instead of /dev/tun* so IP packets never leave the kernel (developers welcome!) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 25 23:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8DD7414E0A for ; Thu, 25 Feb 1999 23:50:34 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA11759; Fri, 26 Feb 1999 16:49:55 +0900 (JST) Message-ID: <36D64CF8.997C55F9@newsguy.com> Date: Fri, 26 Feb 1999 16:27:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn Cc: Pierre Beyssac , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <6749.919960770@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > 2) I found that stepping through the kernel caused exactly the same > problems I was having with accessing my one ATAPI drive that I > experience just running normally with my other drive. So it looks > like at least one problem regarding ATAPI has to do with timings. FreeBSD code has had it share of bugs due to spec violation, generally showing up as "timing" problems. One can search the PR for "HITACHI" or "ATAPI" (I can't quite recall what subject I choose) PRs from me. First time, someone found the bug, I incorporated it in my code, sent PR, and distributed the patch to anyone who complained about it (on the lists I read). Then, the code was changed (the whole code), and my PR was closed because it did not apply anymore. Alas, the new code had the same bug. I don't quite recall if I opened a new PR or just sent the patch to (probably) Soren. It was somehow distressing, though, that the new code had the exact same bug as the old, even though it was quite different code. This was ages ago, though. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 1:21:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.ptt.ru (unknown [195.34.0.100]) by hub.freebsd.org (Postfix) with SMTP id 5F90E14F48 for ; Fri, 26 Feb 1999 01:21:39 -0800 (PST) (envelope-from voux@iname.com) Received: (qmail 18299 invoked from network); 26 Feb 1999 09:21:21 -0000 Received: from dialup-29118.dialup.ptt.ru (195.34.29.118) by dialup.ptt.ru with SMTP; 26 Feb 1999 09:21:21 -0000 Date: Fri, 26 Feb 1999 12:24:29 +0300 (MSK) From: voux X-Sender: voux@hedgehog.shadow.net To: Chan Yiu Wah Cc: freebsd-current@FreeBSD.ORG Subject: Re: how to set the ne2000 pci network card in the config file In-Reply-To: <199902260125.JAA03495@b1.hkstar.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 You should to add in yours KERNEL config file line: device ed0 and then recompile, reinstall kernel. On Fri, 26 Feb 1999, Chan Yiu Wah wrote: > Hello, > > I recently found that my pci network card didn't work for me any more. It > was recognized by the system but I could config it. This didn't happen before > and I didn't why. I had tried to config it as ed1 .... in my config file. > Then it was probed by the system as ed2 .... When I tried to config it as ed2 > in the config file. It was probed by the system as ed3. Can anyone tell me > how to solve it. Thanks.c > > Clarence > > > > 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 Feb 26 1:35:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.IM.ntu.edu.tw (freebsd.im.ntu.edu.tw [140.112.106.205]) by hub.freebsd.org (Postfix) with ESMTP id 5FEAB14EEA for ; Fri, 26 Feb 1999 01:35:19 -0800 (PST) (envelope-from eric@FreeBSD.IM.ntu.edu.tw) Received: from localhost (eric@localhost) by FreeBSD.IM.ntu.edu.tw (8.9.3/8.9.1) with ESMTP id RAA03934 for ; Fri, 26 Feb 1999 17:41:02 +0800 (CST) (envelope-from eric@FreeBSD.IM.ntu.edu.tw) Date: Fri, 26 Feb 1999 17:41:02 +0800 (CST) From: Eric To: freebsd-current@freebsd.org Subject: Cable Modems 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 All:) Sorry , I don't know much about cable modem technology. So I was wondering if there's any support(or plan) for cable modems? since I have already got a network adapter is there anything necessary for cable modem? Best Rgards , To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 1:58:36 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 A959714F6E for ; Fri, 26 Feb 1999 01:57:39 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10GK0G-000IiV-00; Fri, 26 Feb 1999 11:56:16 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" Cc: Pierre Beyssac , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Fri, 26 Feb 1999 16:27:52 +0900." <36D64CF8.997C55F9@newsguy.com> Date: Fri, 26 Feb 1999 11:56:16 +0200 Message-ID: <71924.920022976@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Feb 1999 16:27:52 +0900, "Daniel C. Sobral" wrote: > It was somehow distressing, though, that the new code had the exact > same bug as the old, even though it was quite different code. When you say "the new code", are you referring to the newer acd driver as opposed to the older wcd driver? If so, do you think it'll be worth my while trying to mangle into the acd code your diffs against the wcd code? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 5:36:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 66F8014F48 for ; Fri, 26 Feb 1999 05:36:20 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id NAA02681; Fri, 26 Feb 1999 13:36:03 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xmab02672; Fri, 26 Feb 99 13:36:03 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10GNQx-0002lU-00; Fri, 26 Feb 1999 13:36:03 +0000 To: current@freebsd.org From: Tony Finch Subject: Re: mount -o union broken recently? In-Reply-To: References: <199902252147.NAA01813@vashon.polstra.com> Message-Id: Date: Fri, 26 Feb 1999 13:36:03 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: >On Thu, 25 Feb 1999, John Polstra wrote: > >[...] >> >> Here, you did the union mount on top of an existing mount point (da1). >> I don't know for sure, but I suspect that this is the only case in >> which union mounts are designed to work. > >I was led to believe (last time I read the code) that any directory should >be ok for a union mount.... I was led to believe the same by the manual: union Causes the namespace at the mount point to appear as the union of the mounted filesystem root and the existing di- rectory. Lookups will be done in the mounted filesystem first. If those operations fail due to a non-existent file the underlying directory is then accessed. All cre- ates are done in the mounted filesystem. I did a brief experiment on the 3.0-RELEASE machine as follows: # mount /dev/da0s1a on / (local, writes: sync 1163 async 18438) procfs on /proc (local) /dev/da0s1e on /usr (local, writes: sync 363 async 41653) /dev/da1s1e on /www/da1 (local, writes: sync 12 async 38) # ls da1/subdir this_is_da1 # mount -o union /dev/da2s1e da1/subdir # ls da1/subdir this_is_da1 this_is_da2 # So that machine is happy enough with union nounts on top of subdirectories. On the 3.1-STABLE machine, I tried union mounting on top of a mount point: # mount /dev/da0s1a on / (local, writes: sync 9824 async 55852) /dev/da0s1e on /www (local, writes: sync 5484 async 10400) procfs on /proc (local) /dev/da0s1f on /srcdelta (local, writes: sync 2569 async 2659) # ls /srcdelta thing # ls /www apache obj # umount /srcdelta # mount -o union /dev/da0s1f /www # ls /www thing # Still no joy. Is it sorrect that this magic is implemented in sys/kern/vfs_lookup.c? The odd thing is that AFAICS no-one has made significant changes to this code. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 5:54:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 6B89814F40 for ; Fri, 26 Feb 1999 05:53:56 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.2/8.9.2) id IAA45190; Fri, 26 Feb 1999 08:49:58 -0500 (EST) (envelope-from lee) Message-ID: <19990226084958.A45181@tidalwave.net> Date: Fri, 26 Feb 1999 08:49:58 -0500 From: Lee Cremeans To: Eric Cc: current@freebsd.org Subject: Re: Cable Modems Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Eric on Fri, Feb 26, 1999 at 05:41:02PM +0800 X-OS: FreeBSD 3.0-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 26, 1999 at 05:41:02PM +0800, Eric wrote: > Hi All:) > Sorry , I don't know much about cable modem technology. > So I was wondering if there's any support(or plan) > for cable modems? since I have already got a network > adapter is there anything necessary for cable modem? > > Best Rgards , [Just so you know, -current is the wrong place for this sort of question. Use questions@freebsd.org in the future. ] I set up a COM21 cable modem at work using a FreeBSD box as the gateway, and it seems to work well. For decent (bidirectional) cable networks, you should only need an Ethernet card (and possibly a DHCP package). For others, it depends; some modems require a login (tying them to Windows in most cases), and some have analog-modem return (requiring a modem in the computer and the use of ppp(8); the COM21 at work can run in either bidirectional or modem-return mode.) -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 7: 5:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from d1o29.telia.com (d1o29.telia.com [194.236.214.241]) by hub.freebsd.org (Postfix) with ESMTP id 8E7E814F4E; Fri, 26 Feb 1999 07:05:13 -0800 (PST) (envelope-from girgen@partitur.se) Received: from stordatan.telia.com (t2o29p108.telia.com [194.236.214.228]) by d1o29.telia.com (8.8.8/8.8.5) with ESMTP id QAA23119; Fri, 26 Feb 1999 16:04:53 +0100 (MET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.2/8.9.1) with ESMTP id QAA00468; Fri, 26 Feb 1999 16:04:27 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <36D6B7FB.C919EE6A@partitur.se> Date: Fri, 26 Feb 1999 16:04:27 +0100 From: User Girgen Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: panic: aha0 Invalid CCB or SG list References: <36D4B092.8B076D55@partitur.se> <199902252308.QAA04402@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <36D4B092.8B076D55@partitur.se> Palle Girgensohn writes: > : I've seen three crashes in the last couple of weeks, with a server > : box that's been running stable as a rock for two years, at least. It > : has an adaptec 2940UW with six disks, and an adaptec 1542CP that's > : connected to a seagate travan tape driver. > > OK. This card is known to be good. At least I've not had any > problems with it. Same here, until now. > : It's running STABLE-3.1 from Feb 19 1999, and since the last > : upgrade, I've seen three crashes, all related to dumping to > : tape. Since I got no info on what happened, I decided to sit down > : with the machine, run a backup sequence to tape, and wait for it to > : possibly crash. After 90 minutes, I was about to give up when > : suddenly, poof: > : panic: aha0 Invalid CCB or SG list. > : > : So, it's probably the 1540 driver (or hardware)? > > Ah. OK. I'm not doing tape stuff on my machine. How fast is that > seagate tr-4 that you are doing? It claims 600 Kbytes/s; normally around 550 Kb when at its best, but it depends. > : Can anybody shed some light on what to do? Is it software? That's my > : guess, since the machine never ONCE has crashed until the upgrade to > : 3.x. I had one crash when running current form beginning of January > : (soon after moving to 3.x), and now theese three in a week. The 1540 > : has been in the machine for about six months. > > Chances are really good that this is software. The invalid ccb or sg > list is due to either a race condition or something taht corrupts > these things. > > : If there's anything I can do to help debug I'll do it, but device > : drivers are a little above my level of expertise. > > If you can wait a day or three, I might be able to find something that > will help. However, I don't have a tape drive right now to test it > with. I'll see what I can beg, borrow or steal. I can wait, no problem. It seems that the crashes occur when the CPU is 100% loaded. (The backup system (amanda) is running gzip on dumps before writing to tape. It's a parallell process: the client dumps and gzips, and sent the zipped file over network to tape host, which puts it on a scratch disk. These files are written to tape by the tape host. The crashes occur when the tape host is scheduled for level 0 dumps itself, meaning it will perform gzip at the same it is writing to tape. This explains why it doesn't happen every night.) Thanks a lot for helping! /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 7:51:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netsys.hn (unknown [206.48.255.45]) by hub.freebsd.org (Postfix) with ESMTP id 358BC14EDA; Fri, 26 Feb 1999 07:51:41 -0800 (PST) (envelope-from freebsd@netsys.hn) Received: from [206.48.255.64] (dedicated.netsys.hn [206.48.255.64]) by mail.netsys.hn (8.9.1/8.9.1) with SMTP id JAA19504; Fri, 26 Feb 1999 09:52:25 -0600 (CST) Message-Id: <199902261552.JAA19504@mail.netsys.hn> To: "freebsd-questions@FreeBSD.ORG" , "freebsd-current@freebsd.org" , "freebsd-release@freebsd.org" Subject: Usernames longer than 8 characters? Date: Fri, 26 Feb 99 09:52:20 -0500 From: FreeBSD Questions X-Mailer: E-Mail Connection v2.5.03 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- Hello, I have FreeBSD 2.2.1-RELEASE. That version allows me to put usernames no longer than 8 characters. Now with the new versions of FreeBSD I can have as many as you need. I saw the "Make your own World" upgrading tutorial and I got scared. My server is the authentication server for my 1500 clients and mistaking would be fatal. There is another way of upgrading that part of usernames longer than 8 charac. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 8:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 50D0F14FBF for ; Fri, 26 Feb 1999 08:09:40 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem31.masternet.it [194.184.65.41]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id RAA24725; Fri, 26 Feb 1999 17:08:27 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990226171154.00980df0@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 26 Feb 1999 17:17:08 +0100 To: FreeBSD Questions From: Gianmarco Giovannelli Subject: Re: Usernames longer than 8 characters? Cc: current@freebsd.org In-Reply-To: <199902261552.JAA19504@mail.netsys.hn> 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.52 26/02/99 -0500, you wrote: >I have FreeBSD 2.2.1-RELEASE. That version allows me to put usernames no >longer than 8 characters. Now with the new versions of FreeBSD I can have as >many as you need. > >I saw the "Make your own World" upgrading tutorial and I got scared. My >server is the authentication server for my 1500 clients and mistaking would >be fatal. > >There is another way of upgrading that part of usernames longer than 8 >charac. Uhm... yes there is but it is not more than an hack. And you can have incompatibilities with some programs. So beware. I think the upgrade is the better solution. Also a more better solution is to prepare another HD with FreeBSD 3.1 on it and the migrate only the necessary files. Then a quick swap can solve all your problems. I know it is an expensive solution, but perhaps it the only way to do things without having troubles at all. Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 10:10:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id BBA7314F9E for ; Fri, 26 Feb 1999 10:10:06 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA06389; Sat, 27 Feb 1999 03:09:23 +0900 (JST) Message-ID: <36D6E315.91969389@newsguy.com> Date: Sat, 27 Feb 1999 03:08:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Sheldon Hearn Cc: Pierre Beyssac , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <71924.920022976@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > > It was somehow distressing, though, that the new code had the exact > > same bug as the old, even though it was quite different code. > > When you say "the new code", are you referring to the newer acd driver > as opposed to the older wcd driver? If so, do you think it'll be worth > my while trying to mangle into the acd code your diffs against the wcd > code? No. As I said, that was ages ago... :-) Once we had a wd.c whose code path was quite different from what we have (had) in wd.c now. i368/1730. Funny that did doesn't seem to be the original PR that was fixed, but one applying to the "new" (then :) code. Didn't have much success searching for my own PRs. It ought to do substring searching on the web pages, but it doesn't. :-( OTOH, it seems some of my PRs were filed as confidential, even though they were not, so that my also explain why I couldn't find the other PR. Relevant parts: > This happens because a DELAY is missing in one loop, and ARS_BSY > flag is being ignored in another (atapi_request_immediate and > atapi_wait_cmd functions). On the code: > ireason = inb (ata->port + AR_IREASON); > ac->result.status = inb (ata->port + AR_STATUS); > phase = (ireason & (ARI_CMD | ARI_IN)) | > - (ac->result.status & ARS_DRQ); > + (ac->result.status & (ARS_DRQ|ARS_BSY)); > if (phase == PHASE_CMDOUT) > break; > DELAY (10); The missing delay is not relevant. (Or, at least, I hope acd is not missing delays in wait loops!) The problem is the ARS_BSY signal. If my memory doesn't fail me, if ARS_BSY is active, then the other signals may contain trash. In this particular loop, ARS_BSY could be active, but it wasn't being checked for, on the assumption that ARS_DRQ would only be up (down?) when the operation completed. Mmmmm.... Found my PRs now. It definitely looks like a PR went confidential... :-( I think I explained the bug a lot better on the other one... :-( Oh, well. Well, feel free to search for ARS_DRQ and ARS_BSY on acd (if it uses the same defines...). The ATAPI document I used was SFF8020. It might have been obsoleted by now. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 12:28:48 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 C21E414FFC for ; Fri, 26 Feb 1999 12:28:38 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA73138; Fri, 26 Feb 1999 21:27:14 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902262027.VAA73138@freebsd.dk> Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-Reply-To: <36D6E315.91969389@newsguy.com> from "Daniel C. Sobral" at "Feb 27, 1999 3: 8:21 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Fri, 26 Feb 1999 21:27:14 +0100 (CET) Cc: sheldonh@iafrica.com, beyssac@enst.fr, grog@lemis.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Daniel C. Sobral wrote: > On the code: > > > ireason = inb (ata->port + AR_IREASON); > > ac->result.status = inb (ata->port + AR_STATUS); > > phase = (ireason & (ARI_CMD | ARI_IN)) | > > - (ac->result.status & ARS_DRQ); > > + (ac->result.status & (ARS_DRQ|ARS_BSY)); > > if (phase == PHASE_CMDOUT) > > break; > > DELAY (10); > > The missing delay is not relevant. (Or, at least, I hope acd is not > missing delays in wait loops!) > > The problem is the ARS_BSY signal. If my memory doesn't fail me, if > ARS_BSY is active, then the other signals may contain trash. In this > particular loop, ARS_BSY could be active, but it wasn't being > checked for, on the assumption that ARS_DRQ would only be up (down?) > when the operation completed. This has been in there for ages, if the PR is still open it should be closed. Be patient though, I'm working as much as I can on the (really) new subsystem, and I hope to release the first snaps soon... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 12:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C3BE41519A for ; Fri, 26 Feb 1999 12:37:02 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA12010; Sat, 27 Feb 1999 05:33:44 +0900 (JST) Message-ID: <36D704E8.B6E97A0D@newsguy.com> Date: Sat, 27 Feb 1999 05:32:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: sheldonh@iafrica.com, beyssac@enst.fr, grog@lemis.com, freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <199902262027.VAA73138@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > > The problem is the ARS_BSY signal. If my memory doesn't fail me, if > > ARS_BSY is active, then the other signals may contain trash. In this > > particular loop, ARS_BSY could be active, but it wasn't being > > checked for, on the assumption that ARS_DRQ would only be up (down?) > > when the operation completed. > = > This has been in there for ages, if the PR is still open it should > be closed. It is closed. We were discussing (actually, I was wondering) whether it might have resurfaced with acd. > Be patient though, I'm working as much as I can on the (really) new > subsystem, and I hope to release the first snaps soon... Hey, my cd-rom works fine. *I* am in no hurry. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 13:21:38 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 2E56F1508B for ; Fri, 26 Feb 1999 13:21:34 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA73269; Fri, 26 Feb 1999 22:20:24 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199902262120.WAA73269@freebsd.dk> Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-Reply-To: <36D704E8.B6E97A0D@newsguy.com> from "Daniel C. Sobral" at "Feb 27, 1999 5:32:40 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Fri, 26 Feb 1999 22:20:24 +0100 (CET) Cc: sheldonh@iafrica.com, beyssac@enst.fr, grog@lemis.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 It seems Daniel C. Sobral wrote: > "Søren Schmidt" wrote: > > > > > The problem is the ARS_BSY signal. If my memory doesn't fail me, if > > > ARS_BSY is active, then the other signals may contain trash. In this > > > particular loop, ARS_BSY could be active, but it wasn't being > > > checked for, on the assumption that ARS_DRQ would only be up (down?) > > > when the operation completed. > > > > This has been in there for ages, if the PR is still open it should > > be closed. > > It is closed. We were discussing (actually, I was wondering) whether > it might have resurfaced with acd. Nope, that code snippet is in atapi.c its not in any of the drivers... (and newer has been). -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 13:22:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 3ADE8150EC for ; Fri, 26 Feb 1999 13:22:08 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA03975 (5.67b8/IDA-1.5 for ); Fri, 26 Feb 1999 13:21:52 -0800 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA05324; Fri, 26 Feb 1999 13:21:42 -0800 Message-Id: <199902262121.AA05324@waltz.rahul.net> To: freebsd-current@FreeBSD.ORG Subject: Re: please don't check mail for root logins In-Reply-To: Message from Ollivier Robert of Thu, 25 Feb 99 21:31:36 +0100 Date: Fri, 26 Feb 99 13:21:42 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe you are right about login.conf being used. But let me describe in more detail the problems I encountered with sshd. From sshd.c: /* Check if .hushlogin exists. Note that we cannot use userfile here because we are in the child. */ sprintf(line, "%.200s/.hushlogin", pw->pw_dir); quiet_login = stat(line, &st) >= 0; #if defined (__FreeBSD__) && defined(HAVE_LOGIN_CAP_H) quiet_login = login_getcapbool(lc, "hushlogin", quiet_login); #endif The above code sets quiet_login based on the existence of a .hushlogin file, then loses that value and sets it again from login_getcapbool, thus effectively ignoring any .hushlogin file. I tried to fix this error by changing the last assignment above to: quiet_login |= login_getcapbool(lc, "hushlogin", quiet_login); Once I did this, sshd did detect the presence of a .hushlogin file, but then it would abort with a signal (don't remember which signal), which prevented anybody from logging in who had a .hushlogin file. At this point I undid the UserLogin feature and reverted to using sshd in its native mode. Relying on login.conf to have root's mail not checked seems promising. But it seems to me that not checking root's mail ought to be the default everywhere -- in login.conf, in sshd, and in /bin/login. When the user discovers that he can't log in as root to fix a problem, it's already too late to be going back and changing the defaults. And root's mail should always be forwarded to a non-root user anyway. Rahul > Date: Thu, 25 Feb 99 21:31:36 +0100 > From: Ollivier Robert > To: freebsd-current@FreeBSD.ORG > Message-Id: <19990225213136.B12474@keltia.freenix.fr> > Subject: Re: please don't check mail for root logins > According to Rahul Dhesi: > > Good idea, thanks, and I now realize that it won't work, and neither > > will changing /bin/login -- because sshd does not seem to honor either > > one. > > The sshd in ports should honor the login.conf stuff. One of the patches > adds FreeBSD as a target with login_cap.h. > > Look into patch-af in sshd/patches. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 > > > > 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 Feb 26 14:14: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4752115012 for ; Fri, 26 Feb 1999 14:14:01 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA15128; Sat, 27 Feb 1999 07:10:48 +0900 (JST) Message-ID: <36D71BA6.6FA23D40@newsguy.com> Date: Sat, 27 Feb 1999 07:09:42 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: sheldonh@iafrica.com, beyssac@enst.fr, grog@lemis.com, freebsd-current@FreeBSD.ORG Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <199902262120.WAA73269@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > Nope, that code snippet is in atapi.c its not in any of the drivers... > (and newer has been). You're right. Goes to show how long I haven't touched this part of the code. Alas, just reviewed it out of curiosity. It sure got more readable... :-) But I still hate those inb loops without DELAY... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 14:26:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 8A18614CA3 for ; Fri, 26 Feb 1999 14:26:16 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA26475; Fri, 26 Feb 1999 21:16:44 +0100 From: Luigi Rizzo Message-Id: <199902262016.VAA26475@labinfo.iet.unipi.it> Subject: Re: mount -o union broken recently? To: dot@dotat.at (Tony Finch) Date: Fri, 26 Feb 1999 21:16:44 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: from "Tony Finch" at Feb 26, 99 01:35:44 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 776 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (about union mounts on 3.1 not returning all files with an 'ls' in 3.1 while it did in 3.0) > Is it sorrect that this magic is implemented in sys/kern/vfs_lookup.c? > The odd thing is that AFAICS no-one has made significant changes to > this code. i just experienced the above today while trying diskless, and while ls only seems to return the entries for the topmost directory, files are accessible if you know the name. no idea if this is of any help. on a related subject; i noticed that using mount_null on a directory with device entries (e.g. still in the diskless case, say /foo/dev is an mfs partition with device entries, and i do a mount_null /foo/dev /dev ) causes very bad effects such as crashing the system when i start X. ideas about this as well ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 14:35:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id 346B51502F for ; Fri, 26 Feb 1999 14:35:35 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id SAA07185 for freebsd-current@freebsd.org; Fri, 26 Feb 1999 18:47:17 GMT (envelope-from dm) Message-ID: <19990226184716.A6943@globalserve.net> Date: Fri, 26 Feb 1999 18:47:16 +0000 From: "Dan - Sr. Admin" To: freebsd-current@freebsd.org Subject: fresh cvsup failed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make clean && make world cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/mtree/compare.c /usr/src/usr.sbin/mtree/compare.c:52: sha.h: No such file or directory /usr/src/usr.sbin/mtree/compare.c:55: ripemd.h: No such file or directory /usr/src/usr.sbin/mtree/compare.c: In function `compare': /usr/src/usr.sbin/mtree/compare.c:240: warning: assignment makes pointer from integer without a cast /usr/src/usr.sbin/mtree/compare.c:258: warning: assignment makes pointer from integer without a cast *** Error code 1 Stop. Regards, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "Which is worse: ignorance or apathy? Who knows? Who cares?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 17:28:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id 019CB1504C for ; Fri, 26 Feb 1999 17:28:15 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id JAA04996 for ; Sat, 27 Feb 1999 09:27:59 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id JAA11390 for freebsd-current@freebsd.org; Sat, 27 Feb 1999 09:27:57 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902270127.JAA11390@b1.hkstar.com> Subject: how to setuppci ed1 (ne2000) To: freebsd-current@freebsd.org Date: Sat, 27 Feb 1999 09:27:57 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, This is follow up of my previous requesting for help on setting the pci ed1 (NE2000) NIC. I had followed the advice to set device ed1 in my config file and reinstall using the procedures config -r kernel-name, make depend && make all && make install at the ../../compile/kernel-name. After rebooting my system, the sampe problem still exist that is I config it as ed1 and the system probe it as ed2. I cannot use ifconfig to config anymore. The error for ifconfig ed2 (for example it is used as ed2) does not exist. Any idea ? Thanks Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 17:59:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from d1o29.telia.com (d1o29.telia.com [194.236.214.241]) by hub.freebsd.org (Postfix) with ESMTP id 643AB15057; Fri, 26 Feb 1999 17:59:36 -0800 (PST) (envelope-from girgen@partitur.se) Received: from stordatan.telia.com (t3o29p72.telia.com [194.236.215.72]) by d1o29.telia.com (8.8.8/8.8.5) with ESMTP id CAA13495; Sat, 27 Feb 1999 02:59:16 +0100 (MET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.2/8.9.1) with ESMTP id MAA01196; Fri, 26 Feb 1999 12:50:18 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <36D68A7A.CC8FEF98@partitur.se> Date: Fri, 26 Feb 1999 12:50:18 +0100 From: User Girgen Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: panic: aha0 Invalid CCB or SG list References: <36D4B092.8B076D55@partitur.se> <199902252308.QAA04402@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <36D4B092.8B076D55@partitur.se> Palle Girgensohn writes: > : I've seen three crashes in the last couple of weeks, with a server > : box that's been running stable as a rock for two years, at least. It > : has an adaptec 2940UW with six disks, and an adaptec 1542CP that's > : connected to a seagate travan tape driver. > > OK. This card is known to be good. At least I've not had any > problems with it. > > : It's running STABLE-3.1 from Feb 19 1999, and since the last > : upgrade, I've seen three crashes, all related to dumping to > : tape. Since I got no info on what happened, I decided to sit down > : with the machine, run a backup sequence to tape, and wait for it to > : possibly crash. After 90 minutes, I was about to give up when > : suddenly, poof: > : panic: aha0 Invalid CCB or SG list. > : > : So, it's probably the 1540 driver (or hardware)? > > Ah. OK. I'm not doing tape stuff on my machine. How fast is that > seagate tr-4 that you are doing? It claims it can do 600 Kbytes/s, but most often it's around 550 when writing large "prepared" dump files. > > : Can anybody shed some light on what to do? Is it software? That's my > : guess, since the machine never ONCE has crashed until the upgrade to > : 3.x. I had one crash when running current form beginning of January > : (soon after moving to 3.x), and now theese three in a week. The 1540 > : has been in the machine for about six months. > > Chances are really good that this is software. The invalid ccb or sg > list is due to either a race condition or something taht corrupts > these things. > > : If there's anything I can do to help debug I'll do it, but device > : drivers are a little above my level of expertise. > > If you can wait a day or three, I might be able to find something that > will help. However, I don't have a tape drive right now to test it > with. I'll see what I can beg, borrow or steal. > > Warner I can wait, no problem. I don't think I have a choice, anyway ;-) It seems to be working better when not utilizing the CPU 100% when writing to tape. As I mentioned, I'm using amanda to dump both server and a bunch of workstations. Amanda does gzip on the the dumps before writing them to a scratch disk on the tape host, from where they are written to tape. Since the backup client performs the gzip, I don't see crashes every night, but only when a lot of the dumps scheduled are from the tape host itself (that is, when the tape host is gzipping away att 100% CPU, while at the same writing to tape). Thanks for helping! /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 18:49:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id C1D4B15045 for ; Fri, 26 Feb 1999 18:49:15 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id CAA14895; Sat, 27 Feb 1999 02:48:58 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma014882; Sat, 27 Feb 99 02:48:49 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10GZo8-0003Ko-00; Sat, 27 Feb 1999 02:48:48 +0000 From: Tony Finch To: current@freebsd.org Subject: Re: mount -o union broken recently? In-Reply-To: <199902262016.VAA26475@labinfo.iet.unipi.it> References: Message-Id: Date: Sat, 27 Feb 1999 02:48:48 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > >(about union mounts on 3.1 not returning all files with an 'ls' in >3.1 while it did in 3.0) > >> Is it sorrect that this magic is implemented in sys/kern/vfs_lookup.c? >> The odd thing is that AFAICS no-one has made significant changes to >> this code. > >i just experienced the above today while trying diskless, and while >ls only seems to return the entries for the topmost directory, files >are accessible if you know the name. no idea if this is of any help. This is exactly the right pointer, thanks! The problem appears to be the change between revs 1.108 and 1.109 of sys/kern/vfs_syscalls.c. A couple of (very similar) blocks of code related to `mount -o union` seem to have been mixed up with some code related to `mount -t union` and therefore removed. It's a shame that the two things get confused so much. I originally missed vfs_syscalls.c because a `find /usr/src/sys | xargs grep MNT_UNION` on 3.1 didn't show it. Replacing the errant code fixes the problem. Here's a patch against 1.112.2.1. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net --- vfs_syscalls.c.3.1 Sat Feb 27 02:15:13 1999 +++ vfs_syscalls.c Sat Feb 27 02:30:42 1999 @@ -2763,6 +2763,17 @@ if (error) return (error); } + if ((SCARG(uap, count) == auio.uio_resid) && + (vp->v_flag & VROOT) && + (vp->v_mount->mnt_flag & MNT_UNION)) { + struct vnode *tvp = vp; + vp = vp->v_mount->mnt_vnodecovered; + VREF(vp); + fp->f_data = (caddr_t) vp; + fp->f_offset = 0; + vrele(tvp); + goto unionread; + } error = copyout((caddr_t)&loff, (caddr_t)SCARG(uap, basep), sizeof(long)); p->p_retval[0] = SCARG(uap, count) - auio.uio_resid; @@ -2828,6 +2839,17 @@ goto unionread; if (error) return (error); + } + if ((SCARG(uap, count) == auio.uio_resid) && + (vp->v_flag & VROOT) && + (vp->v_mount->mnt_flag & MNT_UNION)) { + struct vnode *tvp = vp; + vp = vp->v_mount->mnt_vnodecovered; + VREF(vp); + fp->f_data = (caddr_t) vp; + fp->f_offset = 0; + vrele(tvp); + goto unionread; } if (SCARG(uap, basep) != NULL) { error = copyout((caddr_t)&loff, (caddr_t)SCARG(uap, basep), To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 21:17: 4 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 A83DB15089 for ; Fri, 26 Feb 1999 21:17:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA08150; Fri, 26 Feb 1999 21:16:45 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id VAA05738; Fri, 26 Feb 1999 21:16:41 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 26 Feb 1999 21:16:41 -0800 (PST) Message-Id: <199902270516.VAA05738@vashon.polstra.com> To: dot@dotat.at Subject: Re: mount -o union broken recently? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Tony Finch wrote: > Luigi Rizzo wrote: > > > >i just experienced the above today while trying diskless, and while > >ls only seems to return the entries for the topmost directory, files > >are accessible if you know the name. no idea if this is of any help. > > This is exactly the right pointer, thanks! The problem appears to be > the change between revs 1.108 and 1.109 of sys/kern/vfs_syscalls.c. A > couple of (very similar) blocks of code related to `mount -o union` > seem to have been mixed up with some code related to `mount -t union` > and therefore removed. It's a shame that the two things get confused > so much. I originally missed vfs_syscalls.c because a `find > /usr/src/sys | xargs grep MNT_UNION` on 3.1 didn't show it. Replacing > the errant code fixes the problem. Here's a patch against 1.112.2.1. Great sleuthing, guys! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 22:23: 3 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 54E0B150F6 for ; Fri, 26 Feb 1999 22:22:51 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA02475; Fri, 26 Feb 1999 22:15:49 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdsY2473; Sat Feb 27 06:15:49 1999 Date: Fri, 26 Feb 1999 22:15:47 -0800 (PST) From: Julian Elischer To: John Polstra Cc: dot@dotat.at, current@FreeBSD.ORG Subject: Re: mount -o union broken recently? In-Reply-To: <199902270516.VAA05738@vashon.polstra.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 you want to commit? (after you sir...) julian On Fri, 26 Feb 1999, John Polstra wrote: > In article , > Tony Finch wrote: > > Luigi Rizzo wrote: > > > > > >i just experienced the above today while trying diskless, and while > > >ls only seems to return the entries for the topmost directory, files > > >are accessible if you know the name. no idea if this is of any help. > > > > This is exactly the right pointer, thanks! The problem appears to be > > the change between revs 1.108 and 1.109 of sys/kern/vfs_syscalls.c. A > > couple of (very similar) blocks of code related to `mount -o union` > > seem to have been mixed up with some code related to `mount -t union` > > and therefore removed. It's a shame that the two things get confused > > so much. I originally missed vfs_syscalls.c because a `find > > /usr/src/sys | xargs grep MNT_UNION` on 3.1 didn't show it. Replacing > > the errant code fixes the problem. Here's a patch against 1.112.2.1. > > Great sleuthing, guys! > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > > > 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 Feb 26 22:26:10 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 359FA1502A for ; Fri, 26 Feb 1999 22:26:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id WAA08349; Fri, 26 Feb 1999 22:25:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id WAA06022; Fri, 26 Feb 1999 22:25:47 -0800 (PST) (envelope-from jdp@polstra.com) 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: Fri, 26 Feb 1999 22:25:47 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Julian Elischer Subject: Re: mount -o union broken recently? Cc: current@FreeBSD.ORG, dot@dotat.at Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > you want to commit? > > (after you sir...) No, really, after you ... :-) Seriously, I don't know the code in question very well. I'd rather not commit it myself. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 26 22:31:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles100.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id F416B150B0 for ; Fri, 26 Feb 1999 22:31:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00556; Fri, 26 Feb 1999 22:25:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902270625.WAA00556@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chan Yiu Wah Cc: freebsd-current@freebsd.org Subject: Re: how to setuppci ed1 (ne2000) In-reply-to: Your message of "Sat, 27 Feb 1999 09:27:57 +0800." <199902270127.JAA11390@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Feb 1999 22:25:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is follow up of my previous requesting for help on setting the pci ed1 > (NE2000) NIC. I had followed the advice to set device ed1 in my config file > and reinstall using the procedures config -r kernel-name, make depend && > make all && make install at the ../../compile/kernel-name. After rebooting > my system, the sampe problem still exist that is I config it as ed1 and the > system probe it as ed2. I cannot use ifconfig to config anymore. The error > for ifconfig ed2 (for example it is used as ed2) does not exist. Any idea ? You are not following the instructions. The PCI device will be assigned to the 'ed' unit one greater than the highest number shown in the kernel config file, and this number can be clearly seen when the system is booting. Please do not send trivial questions like this to the -current list. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Fri Feb 26 23:22:54 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 68A90150BC for ; Fri, 26 Feb 1999 23:22:53 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA03348; Fri, 26 Feb 1999 23:17:10 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdPp3345; Sat Feb 27 07:17:00 1999 Date: Fri, 26 Feb 1999 23:16:57 -0800 (PST) From: Julian Elischer To: John Polstra Cc: current@FreeBSD.ORG, dot@dotat.at Subject: Re: mount -o union broken recently? 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, 26 Feb 1999, John Polstra wrote: > Julian Elischer wrote: > > you want to commit? > > > > (after you sir...) > > No, really, after you ... :-) Done in 3.1 and 4 julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 0:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id A45FF150BC for ; Sat, 27 Feb 1999 00:21:10 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA24763; Sat, 27 Feb 1999 19:20:34 +1100 Date: Sat, 27 Feb 1999 19:20:34 +1100 From: Bruce Evans Message-Id: <199902270820.TAA24763@godzilla.zeta.org.au> To: dcs@newsguy.com, sos@freebsd.dk Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel Cc: beyssac@enst.fr, freebsd-current@FreeBSD.ORG, grog@lemis.com, sheldonh@iafrica.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Nope, that code snippet is in atapi.c its not in any of the drivers... >> (and newer has been). > >You're right. Goes to show how long I haven't touched this part of >the code. Alas, just reviewed it out of curiosity. It sure got more >readable... :-) But I still hate those inb loops without DELAY... There's only one, at least in my version. I sent this in for review a year or so ago, but received no reply. The main points are that it honours ATA timing in atapi_wait() and checks for ARS_BUSY in atapi_wait(). This hopefully makes bogus checks like the one in rev.1.22 unnecessary (status 0xff has ARS_BSY set so it is invalid). I haven't tested the PC98 case. I removed PC98 code that seems to only compensate for bugs in atapi_wait(). Bruce diff -c2 atapi.c~ atapi.c *** atapi.c~ Sat Feb 27 19:05:47 1999 --- atapi.c Tue Dec 29 01:17:34 1998 *************** *** 229,234 **** */ if (ata->accel && ata->intrcmd) { ! ata->intrcmd = 0; ! ata->slow = 1; } --- 229,234 ---- */ if (ata->accel && ata->intrcmd) { ! ata->intrcmd = 0; ! ata->slow = 1; } *************** *** 399,414 **** struct atapi_params *ap; char tb [DEV_BSIZE]; - #ifdef PC98 - int cnt; - outb(0x432,unit%2); - print(("unit = %d,select %d\n",unit,unit%2)); - #endif /* Wait for controller not busy. */ - #ifdef PC98 - outb (port + AR_DRIVE, unit / 2 ? ARD_DRIVE1 : ARD_DRIVE0); - #else - outb (port + AR_DRIVE, unit ? ARD_DRIVE1 : ARD_DRIVE0); - #endif if (atapi_wait (port, 0) < 0) { print (("atapiX.%d at 0x%x: controller busy, status=%b\n", --- 399,404 ---- *************** *** 417,461 **** } ! /* Issue ATAPI IDENTIFY command. */ #ifdef PC98 ! outb (port + AR_DRIVE, unit/2 ? ARD_DRIVE1 : ARD_DRIVE0); ! ! /* Wait for DRQ deassert. */ ! for (cnt=2000; cnt>0; --cnt) ! if (! (inb (port + AR_STATUS) & ARS_DRQ)) ! break; ! ! outb (port + AR_COMMAND, ATAPIC_IDENTIFY); ! DELAY(500); #else outb (port + AR_DRIVE, unit ? ARD_DRIVE1 : ARD_DRIVE0); - outb (port + AR_COMMAND, ATAPIC_IDENTIFY); #endif ! /* Check that device is present. */ ! if (inb (port + AR_STATUS) == 0xff) { ! print (("atapiX.%d at 0x%x: no device\n", unit, port)); ! if (unit == 1) ! /* Select unit 0. */ ! outb (port + AR_DRIVE, ARD_DRIVE0); return (0); } /* Wait for data ready. */ if (atapi_wait (port, ARS_DRQ) != 0) { print (("atapiX.%d at 0x%x: identify not ready, status=%b\n", unit, port, inb (port + AR_STATUS), ARS_BITS)); - if (unit == 1) - /* Select unit 0. */ - outb (port + AR_DRIVE, ARD_DRIVE0); - return (0); - } - - /* check that DRQ isn't a fake */ - if (inb (port + AR_STATUS) == 0xff) { - print (("atapiX.%d at 0x%x: no device\n", unit, port)); - if (unit == 1) - /* Select unit 0. */ - outb (port + AR_DRIVE, ARD_DRIVE0); return (0); } --- 407,434 ---- } ! /* Select the drive. */ #ifdef PC98 ! /* XXX what is this? */ ! outb(0x432,unit%2); ! print(("unit = %d,select %d\n",unit,unit%2)); ! outb (port + AR_DRIVE, unit / 2 ? ARD_DRIVE1 : ARD_DRIVE0); #else outb (port + AR_DRIVE, unit ? ARD_DRIVE1 : ARD_DRIVE0); #endif ! /* Wait for controller not busy again. Necessary? */ ! if (atapi_wait (port, 0) < 0) { ! print (("atapiX.%d at 0x%x: controller busy, status=%b\n", ! unit, port, inb (port + AR_STATUS), ARS_BITS)); return (0); } + /* Issue ATAPI IDENTIFY command. */ + outb (port + AR_COMMAND, ATAPIC_IDENTIFY); + /* Wait for data ready. */ if (atapi_wait (port, ARS_DRQ) != 0) { print (("atapiX.%d at 0x%x: identify not ready, status=%b\n", unit, port, inb (port + AR_STATUS), ARS_BITS)); return (0); } *************** *** 499,503 **** u_char s; ! /* Wait 5 sec for BUSY deassert. */ for (cnt=500000; cnt>0; --cnt) { s = inb (port + AR_STATUS); --- 472,479 ---- u_char s; ! /* Wait at least 400 nsec for BSY to become valid. */ ! DELAY(1); ! ! /* Wait 5 sec for BSY deassert. */ for (cnt=500000; cnt>0; --cnt) { s = inb (port + AR_STATUS); *************** *** 511,518 **** return (s & ARS_CHECK); ! /* Wait 50 msec for bits wanted. */ for (cnt=5000; cnt>0; --cnt) { s = inb (port + AR_STATUS); ! if ((s & bits_wanted) == bits_wanted) return (s & ARS_CHECK); DELAY (10); --- 487,494 ---- return (s & ARS_CHECK); ! /* Wait 50 msec for bits wanted and BSY still deasserted. */ for (cnt=5000; cnt>0; --cnt) { s = inb (port + AR_STATUS); ! if ((s & (bits_wanted | ARS_BSY)) == bits_wanted) return (s & ARS_CHECK); DELAY (10); *************** *** 1019,1023 **** extern int atapi_lock (int ctlr); ! extern void wdintr (int); /* --- 995,999 ---- extern int atapi_lock (int ctlr); ! void wdintr(void *vunit); /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 0:39:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from daytona.hkstar.com (daytona.hkstar.com [202.82.3.25]) by hub.freebsd.org (Postfix) with ESMTP id 8F780150FB for ; Sat, 27 Feb 1999 00:39:35 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by daytona.hkstar.com (8.9.1/8.9.1) with ESMTP id QAA00355 for ; Sat, 27 Feb 1999 16:39:15 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id QAA12568 for freebsd-current@freebsd.org; Sat, 27 Feb 1999 16:39:15 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199902270839.QAA12568@b1.hkstar.com> Subject: What it means when running soffice 5.01 To: freebsd-current@freebsd.org Date: Sat, 27 Feb 1999 16:39:14 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, Is there anyone knows what it means when running the soffice 5.01 . The message keeps growing as I using the soffice. Is it harmful the system? cheers Clarence ========= fbsd-elf# ./soffice Feb 27 22:51:03 fbsd-elf last message repeated 238 times Feb 27 22:52:12 fbsd-elf /kernel: cmd soffice.bin pid 1013 tried to use non-present sched_yield Feb 27 22:51:03 fbsd-elf last message repeated 238 times Feb 27 22:52:12 fbsd-elf /kernel: cmd soffice.bin pid 1013 tried to use non-present sched_yield ========= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 2: 5:36 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 D639614C19 for ; Sat, 27 Feb 1999 02:05:31 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA76632; Sat, 27 Feb 1999 10:04:59 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Feb 1999 10:04:59 +0000 (GMT) From: Doug Rabson To: Chan Yiu Wah Cc: freebsd-current@freebsd.org Subject: Re: What it means when running soffice 5.01 In-Reply-To: <199902270839.QAA12568@b1.hkstar.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, 27 Feb 1999, Chan Yiu Wah wrote: > > Hello, > > Is there anyone knows what it means when running the soffice 5.01 . > The message keeps growing as I using the soffice. Is it harmful the system? You need to add these lines to your kernel config file: options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" -- 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 Sat Feb 27 2:12:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 2B0131512C for ; Sat, 27 Feb 1999 02:12:55 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.70]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1824; Sat, 27 Feb 1999 11:12:37 +0100 Received: from daemon.ninth-circle.org (abaddon@daemon.ninth-circle.org [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id LAA35011; Sat, 27 Feb 1999 11:12:56 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [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: <199902260144.UAA74596@bb01f39.unx.sas.com> Date: Sat, 27 Feb 1999 11:12:56 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "John W. DeBoskey" Subject: RE: Really! strange uid value Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-Feb-99 John W. DeBoskey wrote: > Hi, > > I have some machines running 3.0-19981209-SNAP. I have seen > some core dumps from pdksh (which I haven't figured out yet) > that have some really strange uid values. > > -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink Whoaha, this is exactly what I got when I tried to compile some things over NFS. The created directory and files were also like this: 1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ funny, the same value. There is something left out very fundamentally somewhere. The only time(s) went it roared it's head here was with NFS (v3 and v2). Any special things about your box, because we need to find a common ground to track where it messed up. --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org> asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 4: 5:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 434EC14BE1 for ; Sat, 27 Feb 1999 04:05:47 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA28189; Sat, 27 Feb 1999 13:05:27 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA35911; Sat, 27 Feb 1999 13:05:26 +0100 (MET) Date: Sat, 27 Feb 1999 13:05:26 +0100 From: Eivind Eklund To: Luigi Rizzo Cc: Tony Finch , current@FreeBSD.ORG Subject: Re: mount -o union broken recently? Message-ID: <19990227130525.L19632@bitbox.follo.net> References: <199902262016.VAA26475@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902262016.VAA26475@labinfo.iet.unipi.it>; from Luigi Rizzo on Fri, Feb 26, 1999 at 09:16:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 26, 1999 at 09:16:44PM +0100, Luigi Rizzo wrote: > (about union mounts on 3.1 not returning all files with an 'ls' in 3.1 > while it did in 3.0) > > > Is it sorrect that this magic is implemented in sys/kern/vfs_lookup.c? > > The odd thing is that AFAICS no-one has made significant changes to > > this code. > > i just experienced the above today while trying diskless, and while ls > only seems to return the entries for the topmost directory, files are > accessible if you know the name. no idea if this is of any help. > > on a related subject; i noticed that using mount_null on a directory > with device entries (e.g. still in the diskless case, say /foo/dev is > an mfs partition with device entries, and i do a mount_null /foo/dev > /dev ) causes very bad effects such as crashing the system when i > start X. ideas about this as well ? Yes. NULLFS mounts do not work, due to a combination of aliasing problems and locking problems. There is a preliminary patch at http://www.freebsd.org/~eivind/FixNULL.patch that I believe fix the aliasing problems, and some of the locking problems, but not all. Using nullfs with this works somewhat, but sometimes get locks screwed up (which result in access to one file just hanging). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 5:32: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 18CA014F0F for ; Sat, 27 Feb 1999 05:32:06 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA08157 for current@freebsd.org; Sat, 27 Feb 1999 08:31:19 -0500 (EST) From: Mikhail Teterin Message-Id: <199902271331.IAA08157@kot.ne.mediaone.net> Subject: Re: Really! strange uid value In-Reply-To: from Jeroen Ruigrok/Asmodai at "Feb 27, 1999 11:12:56 am" To: current@freebsd.org Date: Sat, 27 Feb 1999 08:31:19 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink =this is exactly what I got when I tried to compile some things over NFS. =The created directory and files were also like this: = =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ = =funny, the same value. There is something left out very fundamentally =somewhere. Just FYI. This number is 0xFFFFFFFE in hex... A search for this number through the sources does not bring anything under NFS itself, though the following may give a clue: src/sys/coda/coda.h: if (fid->Vnode == 0xfffffffe || fid->Vnode == 0xffffffff) src/sys/i386/include/apm_bios.h: #define APMINI_NOT32BIT 0xfffffffe src/usr.sbin/rpc.statd/file.c: status_info->ourState = (status_info->ourState + 2) & 0xfffffffe; I ran the search over the 3.1-STABLE sources -- try it against yours... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 5:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (Postfix) with ESMTP id 70CF315072 for ; Sat, 27 Feb 1999 05:41:39 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mikez by aire.open.ac.uk with local (Exim 2.12 #1) id 10Gjze-0005oX-00 for current@freebsd.org; Sat, 27 Feb 1999 13:41:22 +0000 To: current@freebsd.org Subject: Problem building natd Content-Length: 1340 Message-Id: From: Mike Zanker Date: Sat, 27 Feb 1999 13:41:22 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.0-CURRENT supped about 3 hours ago, make buildworld: ===> usr.sbin/natd cc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/natd.c /usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName': /usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function `SetPacketAliasAddress' /usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink': /usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function `PacketAliasPermanentLink' cc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/icmp.c cc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -o natd natd.o icmp.o -lalias natd.o: In function `SetAliasAddressFromIfName': natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress' natd.o: In function `SetupPermanentLink': natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any clues? Regards, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 5:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 26CF114F0F for ; Sat, 27 Feb 1999 05:52:47 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id OAA28541; Sat, 27 Feb 1999 14:52:24 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id OAA02702; Sat, 27 Feb 1999 14:50:07 +0100 (CET) (envelope-from nsouch) Message-ID: <19990227145007.28637@breizh.teaser.fr> Date: Sat, 27 Feb 1999 14:50:07 +0100 From: Nicolas Souchu To: Doug Rabson Cc: current@freebsd.org Subject: Re: kernel build failure at nfs_serv.c References: <19990223225615.15493@breizh.teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: ; from Doug Rabson on Wed, Feb 24, 1999 at 08:51:03AM +0000 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 24, 1999 at 08:51:03AM +0000, Doug Rabson wrote: > >On Tue, 23 Feb 1999, Nicolas Souchu wrote: > >> Hi folks, >> >> Updating at Mar 23 fév 1999 22:52:33 CET, >> >> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_serv.c >> ../../nfs/nfs_serv.c:103: `sysctl__vfs_nfs_children' undeclared here (not in a function) >> ../../nfs/nfs_serv.c:103: initializer element for `sysctl___vfs_nfs_async.oid_parent' is not constant >> *** Error code 1 >> >> Stop. >> >> Any clue? > >I think this is fixed - try updating nfs_serv.c > World updated yesterday still fails in modules/nfs. Thanks for your help. Nicholas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sat Feb 27 5:54: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id E583C15095 for ; Sat, 27 Feb 1999 05:53:43 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 10316 invoked by uid 1001); 27 Feb 1999 13:53:26 +0000 (GMT) To: mi@kot.ne.mediaone.net Cc: current@freebsd.org Subject: Re: Really! strange uid value From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 27 Feb 1999 08:31:19 -0500 (EST)" References: <199902271331.IAA08157@kot.ne.mediaone.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 27 Feb 1999 14:53:26 +0100 Message-ID: <10314.920123606@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jeroen Ruigrok/Asmodai once stated: > > => -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink > > =this is exactly what I got when I tried to compile some things over NFS. > =The created directory and files were also like this: > = > =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ > = > =funny, the same value. There is something left out very fundamentally > =somewhere. > > Just FYI. This number is 0xFFFFFFFE in hex... A search for this number > through the sources does not bring anything under NFS itself, though the > following may give a clue: Remember that the "nobody" user is uid 65534 (0xfffe). The signed extension of this to 32 bits is 0xfffffffe. Maybe you're seeing uid 0 being translated to 65534 (due to NFS) and then sign extended. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 6: 6:13 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 57791150B7 for ; Sat, 27 Feb 1999 06:06:06 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA77554; Sat, 27 Feb 1999 14:05:42 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Feb 1999 14:05:42 +0000 (GMT) From: Doug Rabson To: Nicolas Souchu Cc: current@freebsd.org Subject: Re: kernel build failure at nfs_serv.c In-Reply-To: <19990227145007.28637@breizh.teaser.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Feb 1999, Nicolas Souchu wrote: > On Wed, Feb 24, 1999 at 08:51:03AM +0000, Doug Rabson wrote: > > > >On Tue, 23 Feb 1999, Nicolas Souchu wrote: > > > >> Hi folks, > >> > >> Updating at Mar 23 fév 1999 22:52:33 CET, > >> > >> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_serv.c > >> ../../nfs/nfs_serv.c:103: `sysctl__vfs_nfs_children' undeclared here (not in a function) > >> ../../nfs/nfs_serv.c:103: initializer element for `sysctl___vfs_nfs_async.oid_parent' is not constant > >> *** Error code 1 > >> > >> Stop. > >> > >> Any clue? > > > >I think this is fixed - try updating nfs_serv.c > > > > World updated yesterday still fails in modules/nfs. > > Thanks for your help. If you could send me your kernel config, I'll fix it. It must be a particular combination of options which is causing trouble. -- 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 Sat Feb 27 6:42:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 021AC150A7 for ; Sat, 27 Feb 1999 06:42:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.200]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA15FA; Sat, 27 Feb 1999 15:41:57 +0100 Received: from daemon.ninth-circle.org (abaddon@daemon.ninth-circle.org [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id PAA51408; Sat, 27 Feb 1999 15:42:18 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [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: <10314.920123606@verdi.nethelp.no> Date: Sat, 27 Feb 1999 15:42:17 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: sthaug@nethelp.no Subject: Re: Really! strange uid value Cc: current@freebsd.org, mi@kot.ne.mediaone.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Feb-99 sthaug@nethelp.no wrote: >> Jeroen Ruigrok/Asmodai once stated: >> >> => -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 >> pdksh.core.xclink >> >> =this is exactly what I got when I tried to compile some things over >> NFS. >> =The created directory and files were also like this: >> = >> =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ >> = >> =funny, the same value. There is something left out very fundamentally >> =somewhere. >> >> Just FYI. This number is 0xFFFFFFFE in hex... A search for this number >> through the sources does not bring anything under NFS itself, though the >> following may give a clue: > > Remember that the "nobody" user is uid 65534 (0xfffe). The signed > extension of this to 32 bits is 0xfffffffe. Maybe you're seeing uid 0 > being translated to 65534 (due to NFS) and then sign extended. Could be, but that is still not correct behaviour as far as my knowledge goes. It should not get sign extended IMHO. Am I correct in assuming this (call to the more knowledgeable ones)? --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org> asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 7: 7:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id EB50D1508F for ; Sat, 27 Feb 1999 07:07:19 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem04.masternet.it [194.184.65.14]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id QAA00375 for ; Sat, 27 Feb 1999 16:06:56 +0100 (MET) Message-ID: <36D80A24.E7D63892@giovannelli.it> Date: Sat, 27 Feb 1999 16:07:17 +0100 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: make world fails on natd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My current box, cvsupped at abot 15:30 (CET) of the 27-02-1999 fails to complete the make world : ===> usr.sbin/natd cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/nat d.c cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/icm p.c gzip -cn /usr/src/usr.sbin/natd/natd.8 > natd.8.gz /usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName': /usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function `SetPacketAliasAd dress' /usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink': /usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function `PacketAliasPerm anentLink' cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -o natd natd.o icmp.o -lali as natd.o: In function `SetAliasAddressFromIfName': natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress' natd.o: In function `SetupPermanentLink': natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink' *** Error code 1 1 error -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 7:27: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 61564150BD for ; Sat, 27 Feb 1999 07:27:02 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA18020; Sun, 28 Feb 1999 00:26:50 +0900 (JST) Message-ID: <36D8091D.C386863F@newsguy.com> Date: Sun, 28 Feb 1999 00:02:53 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Really! strange uid value References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > > this is exactly what I got when I tried to compile some things over NFS. > The created directory and files were also like this: > > 1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ > > funny, the same value. There is something left out very fundamentally > somewhere. That looks like user nobody to me, though I might be mistaken. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 7:31:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 9FA4814F2F for ; Sat, 27 Feb 1999 07:29:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA18002; Sun, 28 Feb 1999 00:26:43 +0900 (JST) Message-ID: <36D80748.2F8F2EBA@newsguy.com> Date: Sat, 27 Feb 1999 23:55:04 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Bruce Evans Cc: sos@freebsd.dk, beyssac@enst.fr, freebsd-current@FreeBSD.ORG, grog@lemis.com, sheldonh@iafrica.com Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel References: <199902270820.TAA24763@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > There's only one, at least in my version. There is the PC98 one you removed, and then this one in atapi_request_immediate(): > /* Wait for data i/o phase. */ > for (cnt=20000; cnt>0; --cnt) > if (((inb (ata->port + AR_IREASON) & (ARI_CMD | ARI_IN)) | > (inb (ata->port + AR_STATUS) & ARS_DRQ)) != PHASE_CMDOUT) > break; > > I sent this in for review a year or so ago, but received no reply. > The main points are that it honours ATA timing in atapi_wait() and > checks for ARS_BUSY in atapi_wait(). This hopefully makes bogus checks > like the one in rev.1.22 unnecessary (status 0xff has ARS_BSY set so it > is invalid). I haven't tested the PC98 case. I removed PC98 code that > seems to only compensate for bugs in atapi_wait(). Looks reasonable to me, but I haven't read the specs in two years. Still, from the symptoms people described, I would urge anyone with trouble to test this patch. I realize sos is introducing a new driver soon, but, at the very least, this would be a -stable material. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 7:39: 8 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 4538A14E0F for ; Sat, 27 Feb 1999 07:39:05 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA77668; Sat, 27 Feb 1999 15:38:32 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 27 Feb 1999 15:38:32 +0000 (GMT) From: Doug Rabson To: Jeroen Ruigrok/Asmodai Cc: sthaug@nethelp.no, current@freebsd.org, mi@kot.ne.mediaone.net Subject: Re: Really! strange uid value 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, 27 Feb 1999, Jeroen Ruigrok/Asmodai wrote: > On 27-Feb-99 sthaug@nethelp.no wrote: > >> Jeroen Ruigrok/Asmodai once stated: > >> > >> => -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 > >> pdksh.core.xclink > >> > >> =this is exactly what I got when I tried to compile some things over > >> NFS. > >> =The created directory and files were also like this: > >> = > >> =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ > >> = > >> =funny, the same value. There is something left out very fundamentally > >> =somewhere. > >> > >> Just FYI. This number is 0xFFFFFFFE in hex... A search for this number > >> through the sources does not bring anything under NFS itself, though the > >> following may give a clue: > > > > Remember that the "nobody" user is uid 65534 (0xfffe). The signed > > extension of this to 32 bits is 0xfffffffe. Maybe you're seeing uid 0 > > being translated to 65534 (due to NFS) and then sign extended. > > Could be, but that is still not correct behaviour as far as my knowledge > goes. It should not get sign extended IMHO. Am I correct in assuming this > (call to the more knowledgeable ones)? Do you have a simple repeatable test? What OS is the server running? This kind of problem is easy to fix if I can reproduce it but I don't really have enough information. A packet trace of what happened when things went wrong would be helpful (tcpdump -vv -s300 is pretty useful). -- 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 Sat Feb 27 7:57:27 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 7A6C9150CF for ; Sat, 27 Feb 1999 07:57:22 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id QAA22646 for freebsd-current@FreeBSD.ORG; Sat, 27 Feb 1999 16:57:02 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9DEAB8704; Sat, 27 Feb 1999 10:13:44 +0100 (CET) Date: Sat, 27 Feb 1999 10:13:44 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: What it means when running soffice 5.01 Message-ID: <19990227101344.A567@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199902270839.QAA12568@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199902270839.QAA12568@b1.hkstar.com>; from Chan Yiu Wah on Sat, Feb 27, 1999 at 04:39:14PM +0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5098 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Chan Yiu Wah: > Is there anyone knows what it means when running the soffice 5.01 . > The message keeps growing as I using the soffice. Is it harmful the system? It is explained on htt://lt.tar.com/. You need the following lines in your kernel config file: # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- # POSIX P1003.1B # Real time extensions added int the 1993 Posix # P1003_1B: Infrastructure # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING # _KPOSIX_VERSION: Version kernel is built for options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 8:17:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 2563714FB3 for ; Sat, 27 Feb 1999 08:17:43 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA18010; Sun, 28 Feb 1999 03:17:20 +1100 Date: Sun, 28 Feb 1999 03:17:20 +1100 From: Bruce Evans Message-Id: <199902271617.DAA18010@godzilla.zeta.org.au> To: asmodai@wxs.nl, dfr@nlsystems.com Subject: Re: Really! strange uid value Cc: current@FreeBSD.ORG, mi@kot.ne.mediaone.net, sthaug@nethelp.no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ >> >> = >> >> =funny, the same value. There is something left out very fundamentally >> >> =somewhere. >> >> >> >> Just FYI. This number is 0xFFFFFFFE in hex... A search for this number >> >> through the sources does not bring anything under NFS itself, though the >> >> following may give a clue: >> > >> > Remember that the "nobody" user is uid 65534 (0xfffe). The signed >> > extension of this to 32 bits is 0xfffffffe. Maybe you're seeing uid 0 >> > being translated to 65534 (due to NFS) and then sign extended. >> >> Could be, but that is still not correct behaviour as far as my knowledge >> goes. It should not get sign extended IMHO. Am I correct in assuming this >> (call to the more knowledgeable ones)? > >Do you have a simple repeatable test? What OS is the server running? FreeBSD server, FreeBSD client, nfsv3: # cd world_writable_nfs_mounted_directory_which_shouldnt_exist # cat ^\ # ls -l cat.core -rw------- 1 4294967294 wheel 225280 Feb 28 03:06 cat.core 4294967294 is just the default mapped uid for root. It is (uid_t)-2. See mountd sources. It has nothing to do with user nobody or 65534, except possibly on buggy clients that silently truncate it mod 65536. Perhaps it is a bug to use (uid_t)-2 instead of 65534. For clients with only 16-bit uid_t's you would want to keep all uids on the server < 65536. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 11:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id DCC4814BDB for ; Sat, 27 Feb 1999 11:36:41 -0800 (PST) (envelope-from bford@uop.cs.uop.edu) Received: (from bford@localhost) by uop.cs.uop.edu (8.8.8/8.8.8) id LAA25060 for freebsd-current@freebsd.org; Sat, 27 Feb 1999 11:36:24 -0800 (PST) From: Bret Ford Message-Id: <199902271936.LAA25060@uop.cs.uop.edu> Subject: Broken world To: freebsd-current@freebsd.org Date: Sat, 27 Feb 1999 11:36:21 -0800 (PST) X-Anon-Password: foobiebletch 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 My 4.0-current buildworld broke. The sources were from yesterday night. The system is currently 4.0-current from Feb 16. My UNIX system is a 486 main board with an evergreen upgrade. The world was almost over, too! Argh! :-) Bret Ford ===> usr.sbin/natd gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/natd.c /usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName': /usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function `SetPacketAliasAddress' /usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink': /usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function `PacketAliasPermanentLink' gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/icmp.c gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -o natd natd.o icmp.o -lalias natd.o: In function `SetAliasAddressFromIfName': natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress' natd.o: In function `SetupPermanentLink': natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 11:39:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 391631514F for ; Sat, 27 Feb 1999 11:38:40 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (jbloom.ne.mediaone.net [24.128.100.196]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id OAA27271; Sat, 27 Feb 1999 14:38:16 -0500 (EST) Message-ID: <36D849AC.A36743C1@acm.org> Date: Sat, 27 Feb 1999 14:38:20 -0500 From: Jim Bloom X-Mailer: Mozilla 4.5 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Really! strange uid value References: <199902271617.DAA18010@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that (uid_t)-2 has a lot to do with the user nobody. That was the historical reason why the uid 65534 for chosen for nobody back when uid_t was only 16 bits. I would recommend that the default mapped uid for root be defined as 65534 instead of (uid_t)-2. This seems to make the most sense when trying to avoid user suprises. I would also suggest the default gid be changed similarly. (On Solaris 2.5.1, nobody is now uid 60001 with nobody4 as uid 65534 (for SunOS 4).) Jim Bloom bloom@acm.org Bruce Evans wrote: > > 4294967294 is just the default mapped uid for root. It is (uid_t)-2. > See mountd sources. It has nothing to do with user nobody or 65534, > except possibly on buggy clients that silently truncate it mod 65536. > Perhaps it is a bug to use (uid_t)-2 instead of 65534. For clients > with only 16-bit uid_t's you would want to keep all uids on the > server < 65536. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 11:59:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.bc.wave.home.com (ha1.rdc1.bc.wave.home.com [24.2.10.66]) by hub.freebsd.org (Postfix) with ESMTP id 8A34B15167 for ; Sat, 27 Feb 1999 11:59:44 -0800 (PST) (envelope-from pangolin@home.com) Received: from cr1003333-a.crdva1.bc.wave.home.com ([24.113.51.240]) by mail.rdc1.bc.wave.home.com (InterMail v4.00.03 201-229-104) with ESMTP id <19990227195928.SCCF11952.mail.rdc1.bc.wave.home.com@cr1003333-a.crdva1.bc.wave.home.com> for ; Sat, 27 Feb 1999 11:59:28 -0800 Content-Length: 3600 X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:990227115927:368=_" Date: Sat, 27 Feb 1999 11:59:28 -0800 (PST) Reply-To: Jonathan Hanna Organization: Pangolin Systems From: Jonathan Hanna To: current@freebsd.org Subject: lockmgr panic with mmap() Message-Id: <19990227195928.SCCF11952.mail.rdc1.bc.wave.home.com@cr1003333-a.crdva1.bc.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990227115927:368=_ Content-Type: text/plain; charset=us-ascii The attached program sometimes causes a lockmgr panic. I do not think is always did. I am running 4.0-CURRENT form Feb 19. The trace is: panic lockmgr: locking against self lockmgr mv_map_growstack grow_stack trap_pfault trap calltrap subyte syscall ... A command on a running image such as this usually does it, though I do not know what conditions are neccessary: fincore /usr/local/netscape-4.5/communicator-4.5.bin Jonathan Hanna --_=XFMail.1.3.p0.FreeBSD:990227115927:368=_ Content-Disposition: attachment; filename="fincore.c" Content-Transfer-Encoding: base64 Content-Description: fincore.c Content-Type: application/octet-stream; name=fincore.c; SizeOnDisk=1938 CiNpbmNsdWRlIDxzdGRpby5oPgojaW5jbHVkZSA8dW5pc3RkLmg+CiNpbmNsdWRlIDxzdGRsaWIu aD4KI2luY2x1ZGUgPHN5cy90eXBlcy5oPgojaW5jbHVkZSA8c3lzL21tYW4uaD4KI2luY2x1ZGUg PGZjbnRsLmg+CiNpbmNsdWRlIDxzeXMvc3RhdC5oPgojaW5jbHVkZSA8bWFjaGluZS9wYXJhbS5o PgoKLyoKKiogcHJpbnQgcGFnZXMgb2YgZmlsZSBpbiBjb3JlCiovCgp2b2lkIHVzYWdlKGNoYXIg Km5hbWUpCnsKCXByaW50ZigiVXNhZ2U6ICVzIFstbnNdIGZpbGVzLi4uXG4iLG5hbWUpOwoJcHJp bnRmKCJcdC1uXHRcdERvIG5vdCBwcmludCBmaWxlbmFtZVxuIik7CglwcmludGYoIlx0LW9cdFx0 T25seSBwcmludCBmaWxlcyB3aXRoIGF0IGxlYXN0IG9uZSBwYWdlIGluIGNvcmVcbiIpOwoJcHJp bnRmKCJcdC1zXHRcdERvIG5vdCBwcmludCBmaWxlIHNpemUgaW4gcGFnZXNcbiIpOwp9CgptYWlu KGludCBhYyxjaGFyICoqYXYpCnsKCWludCBjOwoJaW50IHByaW50X25hbWUgPSAxOwoJaW50IHBy aW50X3NpemVwYWdlcyA9IDE7CglpbnQgb25seV9ub256ZXJvID0gMDsKCWludCBzdGF0dXMgPSAw OwoKCXdoaWxlKChjID0gZ2V0b3B0KGFjLGF2LCJub3MiKSkgIT0gLTEpIHsKCQlzd2l0Y2goYykg ewoJCWNhc2UgJ24nOgoJCQlwcmludF9uYW1lID0gMDsKCQkJYnJlYWs7CgkJY2FzZSAnbyc6CgkJ CW9ubHlfbm9uemVybyA9IDE7CgkJCWJyZWFrOwoJCWNhc2UgJ3MnOgoJCQlwcmludF9zaXplcGFn ZXMgPSAwOwoJCQlicmVhazsKCQlkZWZhdWx0OgoJCQl1c2FnZShhdlswXSk7CgkJCWV4aXQoMSk7 CgkJfQoJfQoJZm9yKDsgb3B0aW5kIDwgYWMgOyBvcHRpbmQrKykgewoJCWludCBmZDsKCQlpbnQg cGluZCxwY291bnQ7CgkJY2FkZHJfdCBhZGRyOwoJCXN0cnVjdCBzdGF0IHN0YXRidWY7CgkJc2l6 ZV90IGxlbjsKCQlzaXplX3QgbnVtcGFnZXM7CgkJY2hhciAqcHZlYzsKCgkJaWYgKChmZCA9IG9w ZW4oYXZbb3B0aW5kXSxPX1JET05MWSkpIDwgMCkgewoJCQlwZXJyb3IoYXZbb3B0aW5kXSk7CgkJ CXN0YXR1cyA9IDE7CgkJCWNvbnRpbnVlOwoJCX0KCQlpZiAoZnN0YXQoZmQsJnN0YXRidWYpKSB7 CgkJCXBlcnJvcigiZnN0YXQiKTsKCQkJY2xvc2UoZmQpOwoJCQlzdGF0dXMgPSAxOwoJCQljb250 aW51ZTsKCQl9CgkJbGVuID0gc3RhdGJ1Zi5zdF9zaXplOwoJCW51bXBhZ2VzID0gbGVuL1BBR0Vf U0laRSArICgobGVuICUgUEFHRV9TSVpFKSAhPSAwKTsKCgkJaWYgKCEgKHN0YXRidWYuc3RfbW9k ZSAmIChTX0lGUkVHfFNfSUZDSFIpKSkgewoJCQlwY291bnQgPSAwOwoJCX0gZWxzZSBpZiAobGVu KSB7CgkJCWlmICgoYWRkciA9IG1tYXAoMCxsZW4sUFJPVF9SRUFELE1BUF9TSEFSRUQsZmQsMCkp ID09IE1BUF9GQUlMRUQpIHsKCQkJCXBlcnJvcigibW1hcCIpOwoJCQkJZXhpdCgxKTsKCQkJfQoJ CQlwdmVjID0gbWFsbG9jKG51bXBhZ2VzKTsKCQkJaWYgKG1pbmNvcmUoYWRkcixsZW4scHZlYykp CgkJCXsKCQkJCXBlcnJvcigibWluY29yZSIpOwoJCQkJZXhpdCgxKTsKCQkJfQoJCQlmb3IocGNv dW50ID0gMCxwaW5kID0gMCA7IHBpbmQgPCBudW1wYWdlcyA7IHBpbmQrKykgewoJCQkJaWYgKHB2 ZWNbcGluZF0pIHBjb3VudCsrOwoJCQl9CgkJCWZyZWUocHZlYyk7CgkJCWlmIChtdW5tYXAoYWRk cixsZW4pKSB7CgkJCQlwZXJyb3IoIm11bm1hcCIpOwoJCQkJZXhpdCgxKTsKCQkJfQoJCX0gZWxz ZSB7CgkJCXBjb3VudCA9IDA7CgkJfQoJCWlmIChwY291bnQgfHwgIW9ubHlfbm9uemVybykgewoJ CQlpZiAocHJpbnRfbmFtZSkgcHJpbnRmKCIlczogIixhdltvcHRpbmRdKTsKCQkJcHJpbnRmKCIl ZCIscGNvdW50KTsKCQkJaWYgKHByaW50X3NpemVwYWdlcykgcHJpbnRmKCIvJWQiLG51bXBhZ2Vz KTsKCQkJcHJpbnRmKCJcbiIpOwoJCX0KCQljbG9zZShmZCk7Cgl9CglleGl0KHN0YXR1cyk7Cn0K --_=XFMail.1.3.p0.FreeBSD:990227115927:368=_-- 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 Sat Feb 27 12:56:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 24D1A1516F for ; Sat, 27 Feb 1999 12:56:10 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA25323; Sat, 27 Feb 1999 15:55:52 -0500 (EST) Date: Sat, 27 Feb 1999 15:55:51 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Jonathan Hanna Cc: current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() In-Reply-To: <19990227195928.SCCF11952.mail.rdc1.bc.wave.home.com@cr1003333-a.crdva1.bc.wave.home.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, 27 Feb 1999, Jonathan Hanna wrote: > > The attached program sometimes causes a lockmgr panic. I do not think is always > did. I am running 4.0-CURRENT form Feb 19. > > The trace is: > panic lockmgr: locking against self > lockmgr > mv_map_growstack > grow_stack > trap_pfault > trap > calltrap > subyte > syscall > ... > > A command on a running image such as this usually does it, though I do not know what > conditions are neccessary: > > fincore /usr/local/netscape-4.5/communicator-4.5.bin > > Jonathan Hanna > > GDB is free software and you are welcome to 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. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2875392 initial pcb at 23ef40 panicstr: lockmgr: locking against myself panic messages: --- panic: lockmgr: locking against myself syncing disks... 10 10 6 done dumping to dev 20001, offset 73728 dump 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:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xf0137821 in panic (fmt=0xf0206116 "lockmgr: locking against myself") at ../../kern/kern_shutdown.c:448 #2 0xf0133738 in lockmgr (lkp=0xf5f5f280, flags=2, interlkp=0x0, p=0xf5f688e0) at ../../kern/kern_lock.c:320 #3 0xf01a5b25 in vm_map_growstack (p=0xf5f688e0, addr=134524928) at ../../vm/vm_map.c:666 #4 0xf01dc52a in grow_stack (p=0xf5f688e0, sp=134524928) at ../../i386/i386/vm_machdep.c:571 #5 0xf01d836f in trap_pfault (frame=0xf5f70ec8, usermode=0, eva=134524928) at ../../i386/i386/trap.c:808 #6 0xf01d806e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1, tf_esi = 0, tf_ebp = -168358064, tf_isp = -168358160, tf_ebx = 672337920, tf_edx = 134524928, tf_ecx = -168366080, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = -266506240, tf_cs = 8, tf_eflags = 66067, tf_esp = -266694180, tf_ss = 134524928}) at ../../i386/i386/trap.c:437 #7 0xf01d7000 in suibyte () #8 0xf01d899f in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 321312, tf_esi = 134524928, tf_ebp = -272640092, tf_isp = -168357932, tf_ebx = -272640036, tf_edx = 7, tf_ecx = 7, tf_eax = 78, tf_trapno = 12, tf_err = 2, tf_eip = 671697364, tf_cs = 31, tf_eflags = 582, tf_esp = -272640248, tf_ss = 47}) at ../../i386/i386/trap.c:1100 #9 0xf01cb69c in Xint0x80_syscall () #10 0x80485d1 in ?? () (kgdb) frame 8 #8 0xf01d899f in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 321312, tf_esi = 134524928, tf_ebp = -272640092, tf_isp = -168357932, tf_ebx = -272640036, tf_edx = 7, tf_ecx = 7, tf_eax = 78, tf_trapno = 12, tf_err = 2, tf_eip = 671697364, tf_cs = 31, tf_eflags = 582, tf_esp = -272640248, tf_ss = 47}) at ../../i386/i386/trap.c:1100 1100 error = (*callp->sy_call)(p, args); (kgdb) print callp $1 = (struct sysent *) 0x0 (kgdb) quit Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 13:10:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (Postfix) with ESMTP id 7943F15138 for ; Sat, 27 Feb 1999 13:10:21 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id VAA24134; Sat, 27 Feb 1999 21:10:04 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma024118; Sat, 27 Feb 99 21:10:00 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 10Gqzj-0004Fk-00; Sat, 27 Feb 1999 21:09:55 +0000 To: current@freebsd.org From: Tony Finch Cc: Tony Finch Subject: Re: mount -o union broken recently? In-Reply-To: References: Message-Id: Date: Sat, 27 Feb 1999 21:09:55 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: >On Fri, 26 Feb 1999, John Polstra wrote: >> Julian Elischer wrote: >> > you want to commit? >> > >> > (after you sir...) >> >> No, really, after you ... :-) > >Done >in 3.1 and 4 I just remembered that MNT_UNION occurs in another file which on investigation turned out to be amongst the unionfs code that was moved. It should be removed so that the code isn't run twice when unionfs is enabled. Sorry for missing it the first time round! I also tidied up the vfs_syscalls patch a bit. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net --- miscfs/union/union_subr.c.3.1 Sat Feb 27 20:44:14 1999 +++ miscfs/union/union_subr.c Sat Feb 27 20:47:28 1999 @@ -1183,15 +1183,6 @@ return -1; /* goto unionread */ } } - if (((*vp)->v_flag & VROOT) && ((*vp)->v_mount->mnt_flag & MNT_UNION)) { - struct vnode *tvp = *vp; - *vp = (*vp)->v_mount->mnt_vnodecovered; - VREF(*vp); - fp->f_data = (caddr_t) *vp; - fp->f_offset = 0; - vrele(tvp); - return -1; /* goto unionread */ - } return error; } --- kern/vfs_syscalls.c.3.2 Sat Feb 27 20:55:32 1999 +++ kern/vfs_syscalls.c Sat Feb 27 21:00:26 1999 @@ -2756,23 +2756,24 @@ VOP_UNLOCK(vp, 0, p); if (error) return (error); - if (union_dircheckp && SCARG(uap, count) == auio.uio_resid) { - error = union_dircheckp(p, &vp, fp); - if (error == -1) + if (SCARG(uap, count) == auio.uio_resid) { + if (union_dircheckp) { + error = union_dircheckp(p, &vp, fp); + if (error == -1) + goto unionread; + if (error) + return (error); + } + if ((vp->v_flag & VROOT) && + (vp->v_mount->mnt_flag & MNT_UNION)) { + struct vnode *tvp = vp; + vp = vp->v_mount->mnt_vnodecovered; + VREF(vp); + fp->f_data = (caddr_t) vp; + fp->f_offset = 0; + vrele(tvp); goto unionread; - if (error) - return (error); - } - if ((SCARG(uap, count) == auio.uio_resid) && - (vp->v_flag & VROOT) && - (vp->v_mount->mnt_flag & MNT_UNION)) { - struct vnode *tvp = vp; - vp = vp->v_mount->mnt_vnodecovered; - VREF(vp); - fp->f_data = (caddr_t) vp; - fp->f_offset = 0; - vrele(tvp); - goto unionread; + } } error = copyout((caddr_t)&loff, (caddr_t)SCARG(uap, basep), sizeof(long)); @@ -2833,23 +2834,24 @@ VOP_UNLOCK(vp, 0, p); if (error) return (error); - if (union_dircheckp && SCARG(uap, count) == auio.uio_resid) { - error = union_dircheckp(p, &vp, fp); - if (error == -1) + if (SCARG(uap, count) == auio.uio_resid) { + if (union_dircheckp) { + error = union_dircheckp(p, &vp, fp); + if (error == -1) + goto unionread; + if (error) + return (error); + } + if ((vp->v_flag & VROOT) && + (vp->v_mount->mnt_flag & MNT_UNION)) { + struct vnode *tvp = vp; + vp = vp->v_mount->mnt_vnodecovered; + VREF(vp); + fp->f_data = (caddr_t) vp; + fp->f_offset = 0; + vrele(tvp); goto unionread; - if (error) - return (error); - } - if ((SCARG(uap, count) == auio.uio_resid) && - (vp->v_flag & VROOT) && - (vp->v_mount->mnt_flag & MNT_UNION)) { - struct vnode *tvp = vp; - vp = vp->v_mount->mnt_vnodecovered; - VREF(vp); - fp->f_data = (caddr_t) vp; - fp->f_offset = 0; - vrele(tvp); - goto unionread; + } } if (SCARG(uap, basep) != NULL) { error = copyout((caddr_t)&loff, (caddr_t)SCARG(uap, basep), To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 14:26: 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 DF28F1518B for ; Sat, 27 Feb 1999 14:25:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA13183; Sat, 27 Feb 1999 14:25:34 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id OAA10686; Sat, 27 Feb 1999 14:25:33 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 27 Feb 1999 14:25:33 -0800 (PST) Message-Id: <199902272225.OAA10686@vashon.polstra.com> To: bford@uop.cs.uop.edu Subject: Re: Broken world In-Reply-To: <199902271936.LAA25060@uop.cs.uop.edu> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199902271936.LAA25060@uop.cs.uop.edu>, Bret Ford wrote: > My 4.0-current buildworld broke. The sources were from yesterday > night. The system is currently 4.0-current from Feb 16. My UNIX > system is a 486 main board with an evergreen upgrade. The > world was almost over, too! Argh! :-) > > Bret Ford > > ===> usr.sbin/natd > gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/natd.c > /usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName': > /usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function `SetPacketAliasAddress' > /usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink': > /usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function `PacketAliasPermanentLink' > gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/natd/icmp.c > gcc -O -Wall -I/tigger/obj/usr/src/tmp/usr/include -o natd natd.o icmp.o -lalias > natd.o: In function `SetAliasAddressFromIfName': > natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress' > natd.o: In function `SetupPermanentLink': > natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink' > *** Error code 1 It was broken by the recent commit to "src/lib/libalias". You can probably get around it by reverting that directory to around Feb 25. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 17:14:45 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 6AB6A150BD for ; Sat, 27 Feb 1999 17:14:40 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id UAA58001 for ; Sat, 27 Feb 1999 20:13:01 -0500 (EST) Date: Sat, 27 Feb 1999 20:13:00 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: gcc 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 know that, back when we ran aout, our gcc was a long way changed from the stock gnu gcc ... I'm wondering how much our gcc is changed, now, from the gcc that is the regular GNU distribution? I'm wondering about the size of a project, to upgrade the compiler (this wants a relative answer, how much larger or smaller a job is it now, that it would have been a year ago under aout)? Is anyone doing this? Has there been a decision, most especially from core, about whether we want to use the gcc 2.8.1, or the egcs compiler? What with the rather largeish changes that have gone into C++, it's becoming necessary to have a more up to date compiler. Just speaking about ports, there are a large and growing number of them that compile under 2.8.1, but have problems under 2.7.2.1 (because of exceptions, and other newer features). I'm finally feeling pressure to use a later compiler. I'm making do with the one from ports, but I'm curious about our system compiler. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 17:25:57 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 86A2515187 for ; Sat, 27 Feb 1999 17:25:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA19881; Sat, 27 Feb 1999 17:25:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sat, 27 Feb 1999 20:13:00 EST." Date: Sat, 27 Feb 1999 17:25:28 -0800 Message-ID: <19877.920165128@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering about the size of a project, to upgrade the compiler (this > wants a relative answer, how much larger or smaller a job is it now, > that it would have been a year ago under aout)? Is anyone doing this? Peter was working on it, but I strongly suspect he won't have time to even think about this in the very near future and we shouldn't allow him to add it to his plate, no matter how loudly he demands to suffer to excess. :-) It would probably be cool to find out what the last set of issues he identified and/or fixed with this was though. > Has there been a decision, most especially from core, about whether we > want to use the gcc 2.8.1, or the egcs compiler? I'm not sure I'd call it a "decision", but there are strong leanings towards egcs. It simply seems to be moving more aggressively (and more well-fundedly) in the right directions whereas gcc 2.8.1 has been very slow to update. > What with the rather largeish changes that have gone into C++, it's > becoming necessary to have a more up to date compiler. Just speaking Yes. I can say authoritatively, for example, that there will probably never be a new sysinstall or package handling system without this change occurring since the new tools are written almost entirely in C++ and TCL and require many features not provided by 2.7.2.x. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 17:37:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 3C7171503C for ; Sat, 27 Feb 1999 17:37:09 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA13066 for ; Sun, 28 Feb 1999 12:06:51 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA10194 for FreeBSD-current@FreeBSD.ORG; Sun, 28 Feb 1999 12:06:49 +1030 (CST) Message-ID: <19990228120649.U7279@lemis.com> Date: Sun, 28 Feb 1999 12:06:49 +1030 From: Greg Lehey To: FreeBSD current users Subject: Testers wanted for SiS 5591 code Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i WWW-Home-Page: http://www.lemis.com/~grog 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 I've been given some code for recognizing and initializing Sis 5591 chipsets. In particular, it solves a recently introduced problem with IDE Ultra DMA. It works fine for me, modulo a couple of puzzling messages in the verbose probes, which I'll remove when I've had time to study the data sheet. What I want to do now is to get it looked at by as many people as possible before committing it. If you have a motherboard with this chipset (and no other, not even other SiS chipsets), you can pick up ftp://ftp.lemis.com/pub/ide_pci.c. It's based on the current (since 17 January) version and goes in /sys/pci. If you do, please let me know how it works for you. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 18:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-a.abtsfd1.bc.wave.home.com [24.113.18.89]) by hub.freebsd.org (Postfix) with ESMTP id B9CE815496 for ; Sat, 27 Feb 1999 18:18:02 -0800 (PST) (envelope-from norn@norn.ca.eu.org) Received: (from norn@localhost) by norn.ca.eu.org (8.9.3/8.9.2) id SAA00278; Wed, 27 Jan 1999 18:17:21 -0800 (PST) (envelope-from norn) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <19990228120649.U7279@lemis.com> Date: Wed, 27 Jan 1999 18:17:20 -0800 (PST) Reply-To: Chris Piazza From: Chris Piazza To: Greg Lehey Subject: RE: Testers wanted for SiS 5591 code Cc: FreeBSD current users Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Feb-99 Greg Lehey wrote: > I've been given some code for recognizing and initializing Sis 5591 > chipsets. In particular, it solves a recently introduced problem with > IDE Ultra DMA. It works fine for me, modulo a couple of puzzling > messages in the verbose probes, which I'll remove when I've had time > to study the data sheet. What I want to do now is to get it looked at > by as many people as possible before committing it. > > If you have a motherboard with this chipset (and no other, not even > other SiS chipsets), you can pick up > ftp://ftp.lemis.com/pub/ide_pci.c. It's based on the current (since > 17 January) version and goes in /sys/pci. If you do, > please let me know how it works for you. Great, I was waiting for this.. Seems to work fine: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #77: Sat Feb 27 18:09:34 PST 1999 norn@norn.ca.eu.org:/usr/src/sys/compile/NORN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046751 Hz CPU: Pentium/P54C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67043328 (65472K bytes) avail memory = 62689280 (61220K bytes) Preloaded elf kernel "kernel" at 0xf026c000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ide_pci0: rev 0xd0 int a irq 14 on pci0.0.1 chip1: rev 0x01 on pci0.1.0 chip2: rev 0x00 on pci0.2.0 vga0: rev 0x41 on pci0.9.0 es1: rev 0x00 int a irq 11 on pci0.10.0 pcm1: using I/O space register mapping at 0xe400 de0: rev 0x21 int a irq 10 on pci0.11.0 de0: SMC 21041 [10Mb/s] pass 2.1 de0: address 00:e0:29:10:af:8a Probing for devices on PCI bus 1: 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 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa000a000 on isa wdc0: unit 0 (wd0): , DMA, 32-bit wd0: 2442MB (5001696 sectors), 4962 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit wd1: 9765MB (20000536 sectors), 19841 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 2066KB/sec, 256KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface de0: enabling 10baseT port Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert disabled, rule-based forwarding disabled , default to accept, logging limited to 100 packets/entry de0 XXX: driver didn't set ifq_maxlen changing root device to wd1s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates norn@norn (~)> dd if=/dev/zero of=testfile bs=32k count=1000 1000+0 records in 1000+0 records out 32768000 bytes transferred in 2.315757 secs (14150016 bytes/sec) --- Chris Piazza Abbotsford, BC, Canada cpiazza@home.net finger norn@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 18:21:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 0D91B14D55 for ; Sat, 27 Feb 1999 18:21:18 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA13175; Sun, 28 Feb 1999 12:51:01 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA10492; Sun, 28 Feb 1999 12:51:00 +1030 (CST) Message-ID: <19990228125100.V7279@lemis.com> Date: Sun, 28 Feb 1999 12:51:00 +1030 From: Greg Lehey To: Chris Piazza Cc: FreeBSD current users Subject: Re: Testers wanted for SiS 5591 code References: <19990228120649.U7279@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chris Piazza on Wed, Jan 27, 1999 at 06:17:20PM -0800 WWW-Home-Page: http://www.lemis.com/~grog 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 January 1999 at 18:17:20 -0800, Chris Piazza wrote: > On 28-Feb-99 Greg Lehey wrote: >> I've been given some code for recognizing and initializing Sis 5591 >> chipsets. In particular, it solves a recently introduced problem with >> IDE Ultra DMA. It works fine for me, modulo a couple of puzzling >> messages in the verbose probes, which I'll remove when I've had time >> to study the data sheet. What I want to do now is to get it looked at >> by as many people as possible before committing it. >> >> If you have a motherboard with this chipset (and no other, not even >> other SiS chipsets), you can pick up >> ftp://ftp.lemis.com/pub/ide_pci.c. It's based on the current (since >> 17 January) version and goes in /sys/pci. If you do, >> please let me know how it works for you. > > Great, I was waiting for this.. > > Seems to work fine: Good to hear. > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa000a000 on isa > wdc0: unit 0 (wd0): , DMA, 32-bit > wd0: 2442MB (5001696 sectors), 4962 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): , DMA, 32-bit > wd1: 9765MB (20000536 sectors), 19841 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, intr, dma, iordis > acd0: drive speed 2066KB/sec, 256KB cache > acd0: supported read types: CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked Try enabling UDMA on wdc1 and see if things still work OK. You could also enable multi-block DMA on both controllers. I use the flags 0xa0ffa0ff, which does both of these things. Also, if you could send me the output of a verbose boot, it would be interesting. Unfortunately, you'll need to change your kernel config to save that much output: options "MSGBUF_SIZE=32768" # big msgbuf Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 18:22:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 2BDAA154DD for ; Sat, 27 Feb 1999 18:22:38 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id PAA00618; Sun, 28 Feb 1999 15:21:38 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.2/8.9.1) id PAA56895; Sun, 28 Feb 1999 15:21:38 +1300 (NZDT) (envelope-from jabley) Date: Sun, 28 Feb 1999 15:21:38 +1300 From: Joe Abley To: freebsd-current@freebsd.org Cc: jabley@clear.co.nz Subject: TI PCI-1220 cardbus/PCI bridge Message-ID: <19990228152138.A56854@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any work in progress on sys/pccard/*? I'm using a Gateway Solo for the week which has the PCI/cardbus bridge mentioned in the title, and I have been getting spurious results with 4.0-CURRENT (supped a couple of days ago). If there are some patches in test which might enhance support for this laptop, pointers would be appreciated. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 18:52:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id BFFB7151B3 for ; Sat, 27 Feb 1999 18:52:19 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id UAA70693; Sat, 27 Feb 1999 20:52:02 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id UAA15399; Sat, 27 Feb 1999 20:52:02 -0600 (CST) Date: Sat, 27 Feb 1999 21:52:02 -0500 From: Nathan Dorfman To: Joe Abley Cc: freebsd-current@FreeBSD.ORG Subject: Re: TI PCI-1220 cardbus/PCI bridge Message-ID: <19990227215202.A14100@rtfm.net> References: <19990228152138.A56854@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990228152138.A56854@clear.co.nz>; from Joe Abley on Sun, Feb 28, 1999 at 03:21:38PM +1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 03:21:38PM +1300, Joe Abley wrote: > Is there any work in progress on sys/pccard/*? > > I'm using a Gateway Solo for the week which has the PCI/cardbus bridge > mentioned in the title, and I have been getting spurious results with > 4.0-CURRENT (supped a couple of days ago). > > If there are some patches in test which might enhance support for this > laptop, pointers would be appreciated. I have the same controller in my LifeBook 280dx, and I'd like to point out that it works fine with PAO, and not at all with 3.1-R. What probably needs to be done is a port of the pao3 kit (available via cvsup from jaz.jp.freebsd.org) to 3.1-R (and -stable). Maybe I need a swift kick in the rear to get off IRC and get around to it. > Joe -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications usenet posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 19:29:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1E18C14E84 for ; Sat, 27 Feb 1999 19:29:48 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA22458; Sun, 28 Feb 1999 14:29:23 +1100 Date: Sun, 28 Feb 1999 14:29:23 +1100 From: Bruce Evans Message-Id: <199902280329.OAA22458@godzilla.zeta.org.au> To: chuckr@mat.net, freebsd-current@FreeBSD.ORG Subject: Re: gcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I know that, back when we ran aout, our gcc was a long way changed from >the stock gnu gcc ... I'm wondering how much our gcc is changed, now, >from the gcc that is the regular GNU distribution? $ cvs diff -r FSF /usr/src/contrib/gcc | wc 1746 7551 57123 [error output shows a botched import of gcc/config/alpha with no FSF tag; cvs history shows that gcc/config/alpha isn't even on a vendor branch] Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 20:30:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 1DFB914FA4 for ; Sat, 27 Feb 1999 20:30:36 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA26179 for current@freebsd.org; Sat, 27 Feb 1999 23:37:12 -0500 From: Bill Paul Message-Id: <199902280437.XAA26179@skynet.ctr.columbia.edu> Subject: Request for review: changes to if_vlan.c To: current@freebsd.org Date: Sat, 27 Feb 1999 23:37:10 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 9005 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While trying to figure out a way to support VLANs with the Alteon gigabit NIC, I stumled across /sys/net/if_vlan.c. It seems simple enough: pseudo IP interfaces are created which interacts with an underlying physical interface and fixes up frame headers to deal with VLAN tag encapsulation and extraction. Unfortunately, the code totally fails to take into account the possibility that the underlying interface can perform VLAN tag insertion and extraction all by itself. The Alteon gigabit NIC is just such an example: if you select 'VLAN assist' when configuring the send/receive rings, the firmware will handle all the VLAN naughty bits for you. However, I still want to be able to use the VLAN pseudo interfaces that if_vlan.c. provides, so to that end I tweaked it a little to handle interfaces that do their own VLAN tag handling. The diffs are appended to this message. What I did was change vlan_output() so that if the IFF_LINK1 flag is set on the vlan pseudo interface, the packet will be forwarded unmolested to the interface's output routine, with a pointer to the vlan's ifnet structure in the mbuf packet header. The underlying driver code can then track down the vlan interface's structure information and find the vlan tag number (which it needs to provide in the TX descriptor). Reception is another issue; the existing vlan_input() routine expects that it can find the 'parent' driver's ifnet structure in the mbuf packet header and tries to extract the vlan tag directly from the ethernet header (which it then uses to track down the associated vlan pseudo interface). With the Alteon NIC, the driver's receive routine already knows the tag number, but in order to get it to the vlan code it would have to mangle the header on the packet that it just received, which is pointless given that the firmware already went to the trouble of finding it to begin with. Consequently, I added a second input routine, vlan_input_tag(), which works almost like the original vlan_input() except that the tag can pe specified explicitly as an argument. Lastly, I found what I think is a bug in vlan_output(). If the code finds that the parent interface's output queue is full, it does an IF_QFULL(), but then goes on try and queue the packet with IF_ENQUEUE() anyway. I think this is wrong, and I inserted a 'continue' statement rahter than let the code fall through like it was before. I'm not certain this is the correct fix though... possibly vlan_output() should return with ENOBUFS. Interested persons should review the diffs and pipe up if they have some passionate argument argument against them. Also, I should point out that while if_vlan provides the necessary kernel hackery to implement VLANs, there isn't any user space utility for configuring vlan interfaces (ifconfig doesn't seem to have any vlan-specific code that I could see, and is no vlanconfig). There also is no vlan(4) man page. If whoever originally added the vlan code has plans to fix these two things, then by all means do so, otherwise I'm going to take it upon myself to hack up ifconfig and write the man pages myself. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= *** if_vlan.c.orig Sat Feb 27 22:52:58 1999 --- if_vlan.c Sat Feb 27 23:04:41 1999 *************** *** 39,44 **** --- 39,48 ---- * ether_output() left on our output queue queue when it calls * if_start(), rewrite them for use by the real outgoing interface, * and ask it to send them. + * + * XXX It's incorrect to assume that we must always kludge up + * headers on the physical device's behalf: some devices support + * VLAN tag insersion and extraction in firmware. */ #include "vlan.h" *************** *** 113,124 **** ifp->if_resolvemulti = 0; } } ! PSEUDO_SET(vlaninit, if_vlan); static void vlan_ifinit(void *foo) { ! ; } static void --- 117,128 ---- ifp->if_resolvemulti = 0; } } ! PSEUDO_SET(vlaninit, if_vlan) static void vlan_ifinit(void *foo) { ! return; } static void *************** *** 142,163 **** bpf_mtap(ifp, m); #endif /* NBPFILTER > 0 */ - M_PREPEND(m, EVL_ENCAPLEN, M_DONTWAIT); - if (m == 0) - continue; - /* M_PREPEND takes care of m_len, m_pkthdr.len for us */ - /* ! * Transform the Ethernet header into an Ethernet header ! * with 802.1Q encapsulation. */ ! bcopy(mtod(m, char *) + EVL_ENCAPLEN, mtod(m, char *), ! sizeof(struct ether_header)); ! evl = mtod(m, struct ether_vlan_header *); ! evl->evl_proto = evl->evl_encap_proto; ! evl->evl_encap_proto = htons(vlan_proto); ! evl->evl_tag = htons(ifv->ifv_tag); ! printf("vlan_start: %*D\n", sizeof *evl, (char *)evl, ":"); /* * Send it, precisely as ether_output() would have. --- 146,183 ---- bpf_mtap(ifp, m); #endif /* NBPFILTER > 0 */ /* ! * If the LINK1 flag is set, it means the underlying interface ! * can do VLAN tag insertion itself and doesn't require us to ! * create a special header for it. In this case, we just pass ! * the packet along. However, we need some way to tell the ! * interface where the packet came from so that it knows how ! * to find the VLAN tag to use, so we set the rcvif in the ! * mbuf header to our ifnet. */ ! if (ifp->if_flags & IFF_LINK1) { ! m->m_pkthdr.rcvif = ifp; ! } else { ! M_PREPEND(m, EVL_ENCAPLEN, M_DONTWAIT); ! if (m == 0) ! continue; ! /* M_PREPEND takes care of m_len, m_pkthdr.len for us */ ! ! /* ! * Transform the Ethernet header into an Ethernet header ! * with 802.1Q encapsulation. ! */ ! bcopy(mtod(m, char *) + EVL_ENCAPLEN, mtod(m, char *), ! sizeof(struct ether_header)); ! evl = mtod(m, struct ether_vlan_header *); ! evl->evl_proto = evl->evl_encap_proto; ! evl->evl_encap_proto = htons(vlan_proto); ! evl->evl_tag = htons(ifv->ifv_tag); ! #ifdef DEBUG ! printf("vlan_start: %*D\n", sizeof *evl, ! (char *)evl, ":"); ! #endif ! } /* * Send it, precisely as ether_output() would have. *************** *** 166,177 **** --- 186,244 ---- if (IF_QFULL(&p->if_snd)) { IF_DROP(&p->if_snd); /* XXX stats */ + continue; } IF_ENQUEUE(&p->if_snd, m); if ((p->if_flags & IFF_OACTIVE) == 0) p->if_start(p); } ifp->if_flags &= ~IFF_OACTIVE; + + return; + } + + void + vlan_input_t(struct ether_header *eh, struct mbuf *m, u_int16_t t) + { + int i; + struct ifvlan *ifv; + + for (i = 0; i < NVLAN; i++) { + ifv = &ifv_softc[i]; + if (ifv->ifv_tag == t) + break; + } + + if (i >= NVLAN || (ifv->ifv_if.if_flags & IFF_UP) == 0) { + m_freem(m); + ifv->ifv_p->if_data.ifi_noproto++; + return; + } + + /* + * Having found a valid vlan interface corresponding to + * the given source interface and vlan tag, run the + * the real packet through ethert_input(). + */ + m->m_pkthdr.rcvif = &ifv->ifv_if; + + #if NBPFILTER > 0 + if (ifv->ifv_if.if_bpf) { + /* + * Do the usual BPF fakery. Note that we don't support + * promiscuous mode here, since it would require the + * drivers to know about VLANs and we're not ready for + * that yet. + */ + struct mbuf m0; + m0.m_next = m; + m0.m_len = sizeof(struct ether_header); + m0.m_data = (char *)eh; + bpf_mtap(&ifv->ifv_if, &m0); + } + #endif + ether_input(&ifv->ifv_if, eh, m); + return; } int *************** *** 248,254 **** /* * Set up our ``Ethernet address'' to reflect the underlying ! * physical interface's. */ ifa1 = ifnet_addrs[ifv->ifv_if.if_index - 1]; ifa2 = ifnet_addrs[p->if_index - 1]; --- 315,321 ---- /* * Set up our ``Ethernet address'' to reflect the underlying ! * physical interfaces. */ ifa1 = ifnet_addrs[ifv->ifv_if.if_index - 1]; ifa2 = ifnet_addrs[p->if_index - 1]; *************** *** 303,308 **** --- 370,377 ---- case SIOCSIFMTU: /* * Set the interface MTU. + * This is bogus. The underlying interface might support + * jumbo frames. */ if (ifr->ifr_mtu > ETHERMTU) { error = EINVAL; *** if_vlan_var.h.orig Sat Feb 27 22:52:58 1999 --- if_vlan_var.h Sat Feb 27 22:53:21 1999 *************** *** 79,84 **** --- 79,86 ---- /* shared with if_ethersubr.c: */ extern u_int vlan_proto; extern int vlan_input(struct ether_header *eh, struct mbuf *m); + extern void vlan_input_tag(struct ether_header *eh, + struct mbuf *m, u_int16_t t); #endif #endif /* _NET_IF_VLAN_VAR_H_ */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 20:33:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id A1DE814F81 for ; Sat, 27 Feb 1999 20:33:23 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA26193 for current@freebsd.org; Sat, 27 Feb 1999 23:40:00 -0500 From: Bill Paul Message-Id: <199902280440.XAA26193@skynet.ctr.columbia.edu> Subject: Re: if_vlan (small correction) To: current@freebsd.org Date: Sat, 27 Feb 1999 23:39:59 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 763 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops... I just realized: the output function in if_vlan is vlan_start(), not vlan_output(), and it returns void, so what I said about ENOBUFS is wrong. I still think the 'continue' that I added is correct though. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 21:33: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 5A8701509D for ; Sat, 27 Feb 1999 21:33:04 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id AAA24362 for ; Sun, 28 Feb 1999 00:32:56 -0500 (EST) Date: Sun, 28 Feb 1999 00:32:51 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: Re: lockmgr panic with mmap() (fwd) 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 attached program sometimes causes a lockmgr panic. I do not think is always > did. I am running 4.0-CURRENT form Feb 19. > > The trace is: > panic lockmgr: locking against self > lockmgr > mv_map_growstack > grow_stack > trap_pfault > trap > calltrap > subyte > syscall > ... > > A command on a running image such as this usually does it, though I do not know what > conditions are neccessary: > > fincore /usr/local/netscape-4.5/communicator-4.5.bin > > Jonathan Hanna > > Yep, this is reproducible :( GDB is free software and you are welcome to 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. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2875392 initial pcb at 23ef40 panicstr: lockmgr: locking against myself panic messages: --- panic: lockmgr: locking against myself syncing disks... 10 10 6 done dumping to dev 20001, offset 73728 dump 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:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xf0137821 in panic (fmt=0xf0206116 "lockmgr: locking against myself") at ../../kern/kern_shutdown.c:448 #2 0xf0133738 in lockmgr (lkp=0xf5f5f280, flags=2, interlkp=0x0, p=0xf5f688e0) at ../../kern/kern_lock.c:320 #3 0xf01a5b25 in vm_map_growstack (p=0xf5f688e0, addr=134524928) at ../../vm/vm_map.c:666 #4 0xf01dc52a in grow_stack (p=0xf5f688e0, sp=134524928) at ../../i386/i386/vm_machdep.c:571 #5 0xf01d836f in trap_pfault (frame=0xf5f70ec8, usermode=0, eva=134524928) at ../../i386/i386/trap.c:808 #6 0xf01d806e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1, tf_esi = 0, tf_ebp = -168358064, tf_isp = -168358160, tf_ebx = 672337920, tf_edx = 134524928, tf_ecx = -168366080, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = -266506240, tf_cs = 8, tf_eflags = 66067, tf_esp = -266694180, tf_ss = 134524928}) at ../../i386/i386/trap.c:437 #7 0xf01d7000 in suibyte () #8 0xf01d899f in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 321312, tf_esi = 134524928, tf_ebp = -272640092, tf_isp = -168357932, tf_ebx = -272640036, tf_edx = 7, tf_ecx = 7, tf_eax = 78, tf_trapno = 12, tf_err = 2, tf_eip = 671697364, tf_cs = 31, tf_eflags = 582, tf_esp = -272640248, tf_ss = 47}) at ../../i386/i386/trap.c:1100 #9 0xf01cb69c in Xint0x80_syscall () #10 0x80485d1 in ?? () (kgdb) frame 8 #8 0xf01d899f in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 321312, tf_esi = 134524928, tf_ebp = -272640092, tf_isp = -168357932, tf_ebx = -272640036, tf_edx = 7, tf_ecx = 7, tf_eax = 78, tf_trapno = 12, tf_err = 2, tf_eip = 671697364, tf_cs = 31, tf_eflags = 582, tf_esp = -272640248, tf_ss = 47}) at ../../i386/i386/trap.c:1100 1100 error = (*callp->sy_call)(p, args); (kgdb) print callp $1 = (struct sysent *) 0x0 (kgdb) quit Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 22:15:12 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 8827614E69 for ; Sat, 27 Feb 1999 22:15:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id GAA22496; Sun, 28 Feb 1999 06:14:48 GMT 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 XAA54962; Sat, 27 Feb 1999 23:15:19 -0700 (MST) Message-Id: <199902280615.XAA54962@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: gcc Cc: Chuck Robey , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 27 Feb 1999 17:25:28 PST." <19877.920165128@zippy.cdrom.com> References: <19877.920165128@zippy.cdrom.com> Date: Sat, 27 Feb 1999 23:15:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19877.920165128@zippy.cdrom.com> "Jordan K. Hubbard" writes: : I'm not sure I'd call it a "decision", but there are strong leanings : towards egcs. It simply seems to be moving more aggressively (and : more well-fundedly) in the right directions whereas gcc 2.8.1 has been : very slow to update. I for one would love to see 2.8.1 or newer in the tree for my own, selfish reasons. Many ports (new architectures) would benefit from this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 22:19:23 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 9A3B714E69 for ; Sat, 27 Feb 1999 22:19:22 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA20658; Sat, 27 Feb 1999 22:19:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Warner Losh Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sat, 27 Feb 1999 23:15:19 MST." <199902280615.XAA54962@harmony.village.org> Date: Sat, 27 Feb 1999 22:19:09 -0800 Message-ID: <20655.920182749@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I for one would love to see 2.8.1 or newer in the tree for my own, > selfish reasons. Many ports (new architectures) would benefit from > this. Is that to say that you prefer it over egcs 1.1.1? If so, why? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 27 22:56:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ianai.BlackSun.org (Ianai.blacksun.org [168.100.186.33]) by hub.freebsd.org (Postfix) with ESMTP id 57861151B8 for ; Sat, 27 Feb 1999 22:56:10 -0800 (PST) (envelope-from tugrul@ianai.BlackSun.org) Received: from localhost (tugrul@localhost) by ianai.BlackSun.org (8.8.8/8.8.7) with SMTP id BAA21827 for ; Sun, 28 Feb 1999 01:51:45 -0500 (EST) (envelope-from tugrul@ianai.BlackSun.org) Date: Sun, 28 Feb 1999 01:51:45 -0500 (EST) From: Tugrul To: freebsd-current@freebsd.org Subject: Re: SiS 5591 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 Seems to work alright here. dmesg and dd tests follow. [before] mercury# dd if=/dev/zero of=/tmp/zero bs=1024k count=32 32+0 records in 32+0 records out 33554432 bytes transferred in 6.013635 secs (5579725 bytes/sec) mercury# [after] mercury# dd if=/dev/zero of=/tmp/zero bs=1024k count=32 32+0 records in 32+0 records out 33554432 bytes transferred in 5.892770 secs (5634706 bytes/sec) mercury# Not much gain with this drive :/ 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.1-STABLE #0: Sun Feb 28 01:32:47 EST 1999 galatalt@mercury.novastar.com:/usr/src/sys/compile/MERCURY Timecounter "i8254" frequency 1193225 Hz CPU: Pentium/P55C (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 33554432 (32768K bytes) avail memory = 29986816 (29284K bytes) Preloaded elf kernel "kernel" at 0xf02b7000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0xc1 int a irq 14 on pci0.1.1 vga0: rev 0x06 int a irq 10 on pci0.7.0 xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.15.0 xl0: Ethernet address: 00:60:08:20:72:c8 xl0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for PnP devices: 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 not found ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2439MB (4995648 sectors), 4956 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): , removable, iordy acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable changer, unlocked acd0: changer slot 0 no disk acd1: changer slot 1 no disk acd2: changer slot 2 no disk acd3: changer slot 3 no disk vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message