From owner-freebsd-bugs Sun Apr 20 00:47:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA10038 for bugs-outgoing; Sun, 20 Apr 1997 00:47:08 -0700 (PDT) Received: from pragmatix.bangor.ac.uk (pragmatix.bangor.ac.uk [147.143.2.14]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA10033; Sun, 20 Apr 1997 00:47:03 -0700 (PDT) Received: from wildbill.bangor.ac.uk by pragmatix.bangor.ac.uk (SMI-8.6/SMI-SVR4) id IAA09660; Sun, 20 Apr 1997 08:46:55 +0100 Date: Sun, 20 Apr 1997 07:45:09 +0000 (GMT) From: "M.Sapsed" To: Joerg Wunsch cc: freebsd-questions@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: 2.2.1/amd problems In-Reply-To: <19970418132617.YD17230@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Apr 1997, J Wunsch wrote: > > The server in question runs SunOS 4.1.2 and the top of the amd map is > > like this: > > ...if it's SunOS 4, it's NFSv2 only anyway. That should have been 4.1.3... > > /defaults type:=nfs;sublink:=${key};opts:=rw,intr,nosuid,grpid,rsize=1024 > > user rfs:=/export/home;rhost:=server > > > > I'm not a C hacker so can't realistically dive into the amd sources. > > Mike Murphy had a suggestion to add an rdsize option to amd, please > ask him to get his patch for an attempt. amd is missing more NFS > options (like v3), and it seems silly to duplicate the entire option > parsing from mount_nfs(8), but i don't have a more interesting idea > available either. After some comments about ethercards, I replace the old WD 8013 with an SMC Ultra but this didn't help. Mike subsequently suggested removing the rsize=1024. I added this on request from someone using 2.1.x machines who found amd didn't work without it. I tried removing it and amd is now happy on my 2.2.1 machine! Now I need to find whether the other chap really needs it... > > No-one's offered any > > reason for the pause before e.g. more & vi starting either. > > The length of the termcap file is the reason. I can offer you this > for free. :-) Run > > cap_mkdb /usr/share/misc/termcap > > For some reason i have yet to investigate, the compiled termcap.db > file is not distributed with the releases (although it's compiled and > installed during a `make world'). Please submit a PR for this. Yup - that did the trick too! I'm now once more a happy FreeBSD'er! Thanks to all who have helped. Martin ---------------------------------------------------------------------- Martin Sapsed Tel: +44 (0)1248 382409 Computing Lab Fax: +44 (0)1248 383826 University of Wales, Bangor North Wales, LL57 2DG "Who do you say I am?" m.sapsed@bangor.ac.uk Jesus of Nazareth From owner-freebsd-bugs Sun Apr 20 01:20:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11269 for bugs-outgoing; Sun, 20 Apr 1997 01:20:08 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA11256; Sun, 20 Apr 1997 01:20:04 -0700 (PDT) Resent-Date: Sun, 20 Apr 1997 01:20:04 -0700 (PDT) Resent-Message-Id: <199704200820.BAA11256@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, plm@xs4all.nl Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11164 for ; Sun, 20 Apr 1997 01:17:33 -0700 (PDT) Received: from asterix.xs4all.nl (root@asterix.xs4all.nl [194.109.6.11]) by smtp1.xs4all.nl (8.7.6/XS4ALL) with ESMTP id KAA07041 for ; Sun, 20 Apr 1997 10:17:31 +0200 (MET DST) Received: from plm.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.7.5/8.7.2) with UUCP id KAA01917 for FreeBSD-gnats-submit@freebsd.org; Sun, 20 Apr 1997 10:15:42 +0200 (MET DST) Received: (from plm@localhost) by plm.xs4all.nl (8.8.5/8.7.3) id MAA00455; Sat, 19 Apr 1997 12:25:21 +0200 (MET DST) Message-Id: <199704191025.MAA00455@plm.xs4all.nl> Date: Sat, 19 Apr 1997 12:25:21 +0200 (MET DST) From: Peter Mutsaers Reply-To: plm@xs4all.nl To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3356: ncr0 (ncr815) hang Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3356 >Category: kern >Synopsis: ncr0 (ncr815) hang >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 20 01:20:01 PDT 1997 >Last-Modified: >Originator: Peter Mutsaers >Organization: NA >Release: FreeBSD 3.0-CURRENT i386 >Environment: ncr815 SCSI, just did a make world and installed a new kernel (cvsupped on april 18th). Kernel config file: machine "i386" cpu "I586_CPU" ident PLM maxusers 10 options CHILD_MAX=128 options OPEN_MAX=128 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options MFS options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=10 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options SYSVSHM options SYSVSEM options SYSVMSG options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller ncr0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options XSERVER # include code for XFree86 # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 >Description: All processes accessing disk hang. After 10 seconds the following message appeared: ncr0: timeout ccb=f05c7600 (skip) ncr0: timeout ccb=f05c7e00 (skip) >How-To-Repeat: Boot new kernel and generate some disk activity. >Fix: unknown >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Apr 20 04:20:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA16259 for bugs-outgoing; Sun, 20 Apr 1997 04:20:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA16242; Sun, 20 Apr 1997 04:20:02 -0700 (PDT) Date: Sun, 20 Apr 1997 04:20:02 -0700 (PDT) Message-Id: <199704201120.EAA16242@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: i386/3353: NTOHS(x) related compiler warnings and libpcap disfunction Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR i386/3353; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@freebsd.org, skynyrd@opus.cts.cwu.edu Cc: Subject: Re: i386/3353: NTOHS(x) related compiler warnings and libpcap disfunction Date: Sun, 20 Apr 1997 21:11:49 +1000 >tcpdump(1) does not correctly process target ports for monitoring which are >specified symbolically on the command line. Given the command line: >... >tcpdump relies on pcap(3) to call getservbyname(), and coincidentally >interesting compilation warnings are issued when libpcap is built >during make world: > >/usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c: > In function `pcap_nametoaddr': >/usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c:89: > warning: statement with no effect The bugs are that /usr/src/lib/libpcap/Makefile puts `-Dlint' in CFLAGS, and endian.h has broken ifdefs involving lint in -current (was broken in rev.1.14). The Makefile has excessive -Wall flags and -Dlint is a wrong fix for them. The Makefile also has bogus -I flags. There are no sources in ${.CURDIR} except when ${.CURDIR} is the object directory, and this case is handled by `-I.'. The sources are in ${PCAP_DISTDIR}, etc. >cc -E -c ../../contrib/libpcap/nametoaddr.c yields this >(ostensibly correct per endian.h) expansion for line 125: > > (( sp->s_port ) = > __extension__ ({ register u_short __X = ( (u_short)( sp->s_port ) ); > __asm ("xchgb %h1, %b1" > : "=q" (__X) > : "0" (__X)); > __X; }) ) ; You have to compile with the same CFLAGS as the Makefile to see the problem. CFLAGS is too long to type for contrib'ed sources :-(. I will fix endian.h. Bruce From owner-freebsd-bugs Sun Apr 20 08:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA25186 for bugs-outgoing; Sun, 20 Apr 1997 08:00:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA25179; Sun, 20 Apr 1997 08:00:02 -0700 (PDT) Resent-Date: Sun, 20 Apr 1997 08:00:02 -0700 (PDT) Resent-Message-Id: <199704201500.IAA25179@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.HAA24906;Sun; (8.8.5/8.8.5);, 20 Apr 1997 07:53:55.-0700 (PDT) Message-Id: <199704201453.HAA24906@freefall.freebsd.org> Date: Sun, 20 Apr 1997 07:53:55 -0700 (PDT) From: steveric@erols.com To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: kern/3359: FreeBSD wont boot on amd p133 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3359 >Category: kern >Synopsis: FreeBSD wont boot on amd p133 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 20 08:00:01 PDT 1997 >Last-Modified: >Originator: Rich Friedberg >Organization: True Innovations >Release: 2.2.1-RELEASE >Environment: Can't get to it now, wont boot. >Description: 540 MB Western Digital HD running fine in a Pentium 90, all normal Hardware components.. built a AMD k5-p133, Biostar motherboard, put the 540 in, at first when booting it gave a BootMGR prompt, f2 for BSD, pressing f2 brought you to f2 for bsd again. At this point I went ahead and just tried a novice install...this time choosing STANDARD boot sector..I installed the compat20 files, since they are the smallest, it installed ok. On the holographic shell I was able to see that everything on the hard drive is there, and looks fine (which means that FreeBSD is detecting it ok). With the Standard boot sector it boots to 'Missing Operating System'. I tried going to upgrade again from the installation disk to spawn the holopgraphic shell, and recompiled the kernel. Didn't help. Just for kicks I took the 540 out, put it in the intel p90, and it boots PERFECTLY. Are there any known issues that I may not have found for AMD's and FreeBSD? >How-To-Repeat: Try to boot FreeBSD on AMD p133 and Biostar Motherboard. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Apr 20 08:40:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA26989 for bugs-outgoing; Sun, 20 Apr 1997 08:40:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA26978; Sun, 20 Apr 1997 08:40:02 -0700 (PDT) Date: Sun, 20 Apr 1997 08:40:02 -0700 (PDT) Message-Id: <199704201540.IAA26978@freefall.freebsd.org> To: freebsd-bugs Cc: From: Martin Kammerhofer Subject: Re: kern/3267: mtime/ctime sometimes updated when a program is run Reply-To: Martin Kammerhofer Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3267; it has been noted by GNATS. From: Martin Kammerhofer To: freebsd-gnats-submit@freebsd.org, mkamm@icg.tu-graz.ac.at Cc: Subject: Re: kern/3267: mtime/ctime sometimes updated when a program is run Date: Sun, 20 Apr 1997 17:32:56 +0200 After installing patches from -current ( dyson 97/04/05 18:29:49 Modified: sys/i386/i386 trap.c sys/miscfs/procfs procfs_mem.c sys/vm vm_fault.c vm_map.c vm_map.h vm_prot.h Log: Fix the gdb executable modify problem. Thanks to the detective work by Alan Cox , and his description of the problem. ) and recompiling the 2.2.1 kernel the problem seems fixed. Thanks to David Nugent for pointing me to that fix. According to email from Kevin Martin - the original PR submitter - it also works for him. :) From owner-freebsd-bugs Sun Apr 20 09:50:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00585 for bugs-outgoing; Sun, 20 Apr 1997 09:50:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA00567; Sun, 20 Apr 1997 09:50:02 -0700 (PDT) Resent-Date: Sun, 20 Apr 1997 09:50:02 -0700 (PDT) Resent-Message-Id: <199704201650.JAA00567@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.JAA00192;Sun; (8.8.5/8.8.5);, 20 Apr 1997 09:44:44.-0700 (PDT) Message-Id: <199704201644.JAA00192@freefall.freebsd.org> Date: Sun, 20 Apr 1997 09:44:44 -0700 (PDT) From: noroi@mob.or.jp To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/3360: su(1) cannot call MD4Init(3) from libskey Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3360 >Category: bin >Synopsis: su(1) cannot call MD4Init(3) from libskey >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 20 09:50:01 PDT 1997 >Last-Modified: >Originator: IKEDA Kenji >Organization: home >Release: 3.0-970209-SNAP >Environment: FreeBSD kamui.mob.or.jp 3.0-970209-SNAP FreeBSD 3.0-970209-SNAP #0: Wed Mar 26 00:42:54 JST 1997 noroi@kamui.mob.or.jp:/usr/src/sys/compile/JULIA i386 >Description: su(1) cannot call MD4 library in libmd.a. Libmd.a linked before -lskey. >How-To-Repeat: # root has S/KEY password. $ su s/key 98 ka48855 Password: (turning echo on) Password:GALL OWL NOUN PAR RIG CAR /usr/libexec/ld.so: Undefined symbol "_MD4Init" called from su:/usr/lib/libskey.so.2.0 at 0x8029204 >Fix: su-2.00# pwd /usr/src/usr.bin/su su-2.00# diff -u Makefile.orig Makefile --- Makefile.orig Mon Jan 13 15:39:19 1997 +++ Makefile Mon Apr 21 01:33:49 1997 @@ -3,8 +3,8 @@ PROG= su SRCS= su.c -LDADD= -lmd -DPADD= ${LIBMD} +#LDADD= -lmd +#DPADD= ${LIBMD} #LC_AUTH=-DLOGIN_CAP_AUTH COPTS+= -DLOGIN_CAP $(LC_AUTH) @@ -16,6 +16,9 @@ LDADD+= -lskey -lcrypt DPADD+= ${LIBSKEY} ${LIBCRYPT} .endif + +LDADD+= -lmd +DPADD+= ${LIBMD} .if defined(WHEELSU) COPTS+= -DWHEELSU su-2.00# >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Apr 20 13:34:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA14491 for bugs-outgoing; Sun, 20 Apr 1997 13:34:18 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14467 for ; Sun, 20 Apr 1997 13:34:08 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id VAA12580 for freefall.freebsd.org!freebsd-bugs; Sun, 20 Apr 1997 21:29:35 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 20 Apr 1997 21:23:29 +0100 X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 20 Apr 1997 21:20:59 +0100 To: freebsd-bugs@freefall.freebsd.org From: Bob Bishop Subject: Re: kern/3292: Cyrix 486 performance problem Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The root of this problem appears to be that Cyrix 486 DX DX2 and DX4 (and some equivalent TI-branded parts) are correctly identified, but are misclassified as CPU_486DLC where they should be just plain CPU_486. The following patch fixes the problem: *** identcpu.c.orig Sun Apr 20 17:33:35 1997 --- identcpu.c Sun Apr 20 17:37:00 1997 *************** *** 81,87 **** { "i486SX", CPUCLASS_486 }, /* CPU_486SX */ { "i486DX", CPUCLASS_486 }, /* CPU_486 */ { "Pentium", CPUCLASS_586 }, /* CPU_586 */ ! { "Cyrix 486", CPUCLASS_486 }, /* CPU_486DLC */ { "Pentium Pro", CPUCLASS_686 }, /* CPU_686 */ { "Cyrix 5x86", CPUCLASS_486 }, /* CPU_M1SC */ { "Cyrix 6x86", CPUCLASS_486 }, /* CPU_M1 */ --- 81,87 ---- { "i486SX", CPUCLASS_486 }, /* CPU_486SX */ { "i486DX", CPUCLASS_486 }, /* CPU_486 */ { "Pentium", CPUCLASS_586 }, /* CPU_586 */ ! { "Cyrix 486", CPUCLASS_486 }, /* CPU_486 or CPU_486DLC */ { "Pentium Pro", CPUCLASS_686 }, /* CPU_686 */ { "Cyrix 5x86", CPUCLASS_486 }, /* CPU_M1SC */ { "Cyrix 6x86", CPUCLASS_486 }, /* CPU_M1 */ *************** *** 533,540 **** * Don't check (cpu_id & 0x00f0) == 0x50 to detect M2, now. */ switch (cyrix_did & 0x00f0) { - case 0x00: case 0x10: case 0xf0: cpu = CPU_486DLC; break; --- 533,543 ---- * Don't check (cpu_id & 0x00f0) == 0x50 to detect M2, now. */ switch (cyrix_did & 0x00f0) { case 0x10: + /* 486DX, DX2, DX4 doesn't need fancy initialisation */ + cpu = CPU_486; + break; + case 0x00: case 0xf0: cpu = CPU_486DLC; break; -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-bugs Sun Apr 20 21:20:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA14041 for bugs-outgoing; Sun, 20 Apr 1997 21:20:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA14032; Sun, 20 Apr 1997 21:20:03 -0700 (PDT) Date: Sun, 20 Apr 1997 21:20:03 -0700 (PDT) Message-Id: <199704210420.VAA14032@freefall.freebsd.org> To: freebsd-bugs Cc: From: Kazutaka YOKOTA Subject: Re: conf/3354: 2.2.1 Installation problems with Diamond SpeedStar64 Reply-To: Kazutaka YOKOTA Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR conf/3354; it has been noted by GNATS. From: Kazutaka YOKOTA To: pscott@netcom.com Cc: freebsd-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: conf/3354: 2.2.1 Installation problems with Diamond SpeedStar64 Date: Sun, 20 Apr 1997 11:24:08 +0900 >>Number: 3354 >>Category: conf >>Synopsis: 2.2.1 Installation problems with Diamond SpeedStar64 >>Confidential: no >>Severity: serious >>Priority: high >>Responsible: freebsd-bugs >>State: open >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Sat Apr 19 16:30:01 PDT 1997 >>Last-Modified: >>Originator: Paul A. Scott >>Organization: >>Release: 2.2.1 >>Environment: >N/A >>Description: >Attempting to install FreeBSD 2.2.1 (from Walnut Creek CD-ROM or floppy) I hav >e the exact same TWO problems as reported in conf/2775: > >1) On system 1, after kernel uncompresses, the screen goes completely >garbled. Look like running in graphics mode with completely messed up >character maps. Almost looks like static it's so garbled. This occurs with >Diamond Speedstar64 video card. Impossible to continue installation. This is because the video mode parameter table in BIOS is not organized in the standard way and the console driver syscons gets confused. I discussed this matter with Soeren. I don't know when the fix is coming, just yet. >2) On system 2, using a Trident 9000 video card, the screen looks fine, but af >ter kernel probes all devices, the screen goes blank, beeps once, the cursor g >oes to the lower left hand corner of the screen, and the system sits idle. Swi >tching to the alternate console, Alt-F2, I see a single line that says "DEBUG: > ioctl(3, TIOCCONS, NULL) = 0 (success)". Key strokes on the first console ar >e ignored. Key strokes on the alternate console are processed, but no shell is > available. As you can switch between the two vtys, keyboard I/O seems OK... What if you specify the flag 0x01 to the npx0 device in the device configuration menu (in CLI mode)? The symptom you described does not quite match the ones which are solved this way, but, it may just work. Kazu >>How-To-Repeat: >Install 2.2.1 with Diamond SpeedStar64 video card. >>Fix: >Use a different video card, install, compile kernel to use PCVT console driver >, replace original video card. This reportedly worked for someone else who use >d a Trident video card, but did not work for me because even with a Trident vi >deo card the installation stopped as reported above. From owner-freebsd-bugs Mon Apr 21 00:50:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27410 for bugs-outgoing; Mon, 21 Apr 1997 00:50:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27402; Mon, 21 Apr 1997 00:50:04 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 00:50:04 -0700 (PDT) Resent-Message-Id: <199704210750.AAA27402@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA27217;Mon; (8.8.5/8.8.5);, 21 Apr 1997 00:46:09.-0700 (PDT) Message-Id: <199704210746.AAA27217@freefall.freebsd.org> Date: Mon, 21 Apr 1997 00:46:09 -0700 (PDT) From: samath To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: kern/3364: Cannot Login as root Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3364 >Category: kern >Synopsis: Cannot Login as root >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 00:50:01 PDT 1997 >Last-Modified: >Originator: Samath Wijesundera >Organization: Sri Lanka Telecom >Release: 2.1.5 >Environment: FreeBSD >Description: When you change the login shell using vipw of the root to a file name that is not existing file name, you can never login as root to change the setting back >How-To-Repeat: Change the login shell using the vipw utility >Fix: do not know >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 00:51:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA27481 for bugs-outgoing; Mon, 21 Apr 1997 00:51:26 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA27469; Mon, 21 Apr 1997 00:51:23 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id AAA02577; Mon, 21 Apr 1997 00:51:21 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 21 Apr 1997 00:31:25 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: Mystery of the X11 Panic... Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I guess 2.2.1 hates my system. After endless ahc problems, here is the latest (this might have shown up as an ahc problem?): Running 2.2.1-970415 and later, shortly after starting X11, while clicking the mouse on an icon in xfmail, xfm, or, sometimes, just because the system will crash, freeze, die mercilessly. No particular pattern :-( Well, the good news is that the good old 2.2-BETA_A does not suffer from these problems. the better news is that I managed to catch this panic while X11 was running: Fatal trap 12 - Page fault while in kernel mode. in virtual address 0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing it after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). Now, I am a pretty good shell programmer, but never lerned how to panic a kernel with running a program on one :-) There is no explicit bash call on my part, to trigger the fault, but much of the X11 activity forks and exec's all over the place. But you know that already... Anyway, any help will be appreciated...! I must stabilize this kernel!!! Thanx, simon an ahc problem?): Running 2.2.1-970415 and later, shortly after starting X11, while clicking the mouse on an icon in xfmail, xfm, or, sometimes, just because the system will crash, freeze, die mercilessly. No particular patt From owner-freebsd-bugs Mon Apr 21 01:59:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA00581 for bugs-outgoing; Mon, 21 Apr 1997 01:59:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00573 for ; Mon, 21 Apr 1997 01:59:32 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA27852; Mon, 21 Apr 1997 18:52:09 +1000 Date: Mon, 21 Apr 1997 18:52:09 +1000 From: Bruce Evans Message-Id: <199704210852.SAA27852@godzilla.zeta.org.au> To: freebsd-bugs@freebsd.org, Shimon@i-Connect.Net Subject: Re: Mystery of the X11 Panic... Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [cc list trimmed to remove -hackers] >Fatal trap 12 - Page fault while in kernel mode. in virtual address >0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing it >after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. > >Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). This means that cdevsw[maj]->d_open is bad (probably null) although cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. Driver LKM's tend to cause this problem if they are unloaded. Bash may trigger the problem because it does an opendir() on device files (but I thought I fixed this by not opening device files in opendir()). I wouldn't use LKMs for anything important. Bruce From owner-freebsd-bugs Mon Apr 21 03:27:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04250 for bugs-outgoing; Mon, 21 Apr 1997 03:27:06 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04245; Mon, 21 Apr 1997 03:27:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id DAA03554; Mon, 21 Apr 1997 03:28:51 -0700 (PDT) Message-Id: <199704211028.DAA03554@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Simon Shapiro cc: freebsd-hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Mystery of the X11 Panic... In-reply-to: Your message of "Mon, 21 Apr 1997 00:31:25 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Apr 1997 03:28:51 -0700 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Running 2.2.1-970415 and later, shortly after starting X11, while clicking ... >these problems. the better news is that I managed to catch this panic >while X11 was running: > >Fatal trap 12 - Page fault while in kernel mode. in virtual address >0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing it >after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. > >Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). > >Now, I am a pretty good shell programmer, but never lerned how to panic a >kernel with running a program on one :-) > >There is no explicit bash call on my part, to trigger the fault, but much >of the X11 activity forks and exec's all over the place. But you know that >already... > >Anyway, any help will be appreciated...! I must stabilize this kernel!!! This is almost certainly caused by the bug I fixed in kern_exec.c on April 18th. You say "-970415" and later...does this mean that you've updated your source in the past day or so? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-bugs Mon Apr 21 03:30:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04400 for bugs-outgoing; Mon, 21 Apr 1997 03:30:11 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA04395 for ; Mon, 21 Apr 1997 03:30:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id DAA03600; Mon, 21 Apr 1997 03:31:50 -0700 (PDT) Message-Id: <199704211031.DAA03600@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Bruce Evans cc: freebsd-bugs@freebsd.org, Shimon@i-Connect.Net Subject: Re: Mystery of the X11 Panic... In-reply-to: Your message of "Mon, 21 Apr 1997 18:52:09 +1000." <199704210852.SAA27852@godzilla.zeta.org.au> From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Apr 1997 03:31:50 -0700 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >[cc list trimmed to remove -hackers] > >>Fatal trap 12 - Page fault while in kernel mode. in virtual address >>0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing it >>after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. >> >>Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). > >This means that cdevsw[maj]->d_open is bad (probably null) although >cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. >Driver LKM's tend to cause this problem if they are unloaded. Bash >may trigger the problem because it does an opendir() on device files >(but I thought I fixed this by not opening device files in opendir()). >I wouldn't use LKMs for anything important. ...or it could be caused by the bug in kern_exec.c, which could have mangled adjacent buffers or possibly random kernel memory. It seems to involve bash and the kern_exec.c bug was triggered when running small shell scripts. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-bugs Mon Apr 21 04:50:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08255 for bugs-outgoing; Mon, 21 Apr 1997 04:50:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA08249; Mon, 21 Apr 1997 04:50:01 -0700 (PDT) Date: Mon, 21 Apr 1997 04:50:01 -0700 (PDT) Message-Id: <199704211150.EAA08249@freefall.freebsd.org> To: freebsd-bugs Cc: From: David Nugent Subject: Re: kern/3364: Cannot Login as root Reply-To: David Nugent Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3364; it has been noted by GNATS. From: David Nugent To: samath@freefall.freebsd.org Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/3364: Cannot Login as root Date: Mon, 21 Apr 1997 21:41:25 +1000 On Mon Apr 21 00:46:09 EST 1997, samath@freefall.freebsd.org writes: > >Description: > When you change the login shell using vipw of the root to > a file name that is not existing file name, you can never login as > root to change the setting back su -m or boot single-user (which gives you /bin/sh, or a shell of your choice - the passwd database is never consulted). Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-bugs Mon Apr 21 05:10:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA09357 for bugs-outgoing; Mon, 21 Apr 1997 05:10:28 -0700 (PDT) Received: from asteroid.intermedia.ru ([194.85.158.35]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA09317; Mon, 21 Apr 1997 05:09:50 -0700 (PDT) Received: from asteroid.intermedia.ru (localhost.intermedia.ru [127.0.0.1]) by asteroid.intermedia.ru (8.8.5/8.8.5) with ESMTP id QAA02926; Mon, 21 Apr 1997 16:11:49 +0400 (MSD) Message-Id: <199704211211.QAA02926@asteroid.intermedia.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: mtaylor@cybernet.com (Mark Taylor), hackers@freebsd.org, bugs@freebsd.org Subject: Re: vnode as filesystem (crash!) In-reply-to: Your message of "Mon, 14 Apr 1997 13:55:10 PDT." <199704142055.NAA19330@phaeton.artisoft.com> Reply-To: Alex Povolotsky Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Apr 1997 16:11:25 +0400 From: Alex Povolotsky Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmm... I couldn't make vnode working as filesystem at all. How should I init the file intended to be a FS? Alex. From owner-freebsd-bugs Mon Apr 21 05:30:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA10310 for bugs-outgoing; Mon, 21 Apr 1997 05:30:07 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA10302; Mon, 21 Apr 1997 05:30:04 -0700 (PDT) Date: Mon, 21 Apr 1997 05:30:04 -0700 (PDT) Message-Id: <199704211230.FAA10302@freefall.freebsd.org> To: freebsd-bugs Cc: From: Kazutaka YOKOTA Subject: Re: i386/3082: keyboard locks up unexpectedly Reply-To: Kazutaka YOKOTA Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR i386/3082; it has been noted by GNATS. From: Kazutaka YOKOTA To: raj@iphase.com Cc: FreeBSD-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: i386/3082: keyboard locks up unexpectedly Date: Mon, 21 Apr 1997 21:28:25 +0900 >>Number: 3082 >>Category: i386 >>Synopsis: keyboard locks up unexpectedly [....] >>Release: FreeBSD 2.1.6 i386 >>Environment: > > Pentium pro system. > FreeBSD 2.1.6 installed with default sc0 console in config file. > Lines for PS/2 and bus mice commented out in the config file. > > Execution of "uname -a" produced the following output: > > FreeBSD lifeson 2.1.6-RELEASE FreeBSD 2.1.6-RELEASE #4: > root@lifeson:/usr/src/sys/compile/lifeson i386 > >>Description: > > System locks up unexpectedly. There's no set pattern to this. > When this happens, any sort of input from the keyboard becomes > impossible. Even Ctl-C doesn't work. Actually no key works. This is a known problem. It's intermittent and difficult to reproduce. When this happens again, login to the system via serial or network and try the following command. kbdcontrol -r fast < /dev/ttyv0 (You may have to become root to do this.) The command actually changes the keyboard typematic rate and it doesn't do anything special to recover from lock up, but, the keyboard MAY become functional as a side effect under FreeBSD 2.1.X. If you are using X and a PS/2 mouse when the lock up happens and run the above command, the PS/2 mouse may go wild. This is harmless. Switch away from X to another vty (by pressing Ctl+Alt+Fn, yes, I expect the keyboard is working again after the kbdcontrol command) and come back to X, then the mouse should be OK. Hope this might help. Kazu From owner-freebsd-bugs Mon Apr 21 06:21:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA12604 for bugs-outgoing; Mon, 21 Apr 1997 06:21:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA12580 for ; Mon, 21 Apr 1997 06:21:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA25217; Mon, 21 Apr 1997 15:21:41 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA22758; Mon, 21 Apr 1997 15:20:36 +0200 (MET DST) Message-ID: <19970421152036.AM09487@uriah.heep.sax.de> Date: Mon, 21 Apr 1997 15:20:36 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs@freebsd.org Cc: Shimon@i-Connect.Net Subject: Re: Mystery of the X11 Panic... References: <199704210852.SAA27852@godzilla.zeta.org.au> <199704211031.DAA03600@root.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Greenman wrote: > >This means that cdevsw[maj]->d_open is bad (probably null) although > >cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. Nope, Bruce: if ( (cdevsw[maj] == NULL) || (cdevsw[maj]->d_open == NULL)) ^^^^^^^^^^^^^^^^^^^ return ENXIO; This case is tested, and it's actually this test itself that causes the panic. > ...or it could be caused by the bug in kern_exec.c, which could have > mangled adjacent buffers or possibly random kernel memory. It seems > to involve bash and the kern_exec.c bug was triggered when running small > shell scripts. This seems more reasonable after reading that piece of code. Simon didn't tell us the faulting VA, but i bet it's not right NULL. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Apr 21 07:30:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA16719 for bugs-outgoing; Mon, 21 Apr 1997 07:30:21 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16711; Mon, 21 Apr 1997 07:30:18 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id IAA07756; Mon, 21 Apr 1997 08:30:15 -0600 (MDT) Message-Id: <199704211430.IAA07756@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Simon Shapiro cc: freebsd-hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Mystery of the X11 Panic... In-reply-to: Your message of "Mon, 21 Apr 1997 00:31:25 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Apr 1997 08:28:42 -0600 From: "Justin T. Gibbs" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I guess 2.2.1 hates my system. > >After endless ahc problems, here is the latest (this might have shown up as >an ahc problem?): > >Running 2.2.1-970415 and later You mean, you are running from the 2.2 branch (CVSupped or CTMed) as of 970415. 2.2.1 is a static release. Also be aware that the latest ahc driver was committed late on 4/18/97, so if you don't have code that current, you should update. >an ahc problem?): It doesn't sound like it. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Mon Apr 21 09:11:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA27278 for bugs-outgoing; Mon, 21 Apr 1997 09:11:32 -0700 (PDT) Received: (from jkh@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA27257; Mon, 21 Apr 1997 09:11:27 -0700 (PDT) Date: Mon, 21 Apr 1997 09:11:27 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199704211611.JAA27257@freefall.freebsd.org> To: samath, jkh, freebsd-bugs Subject: Re: kern/3364 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: Cannot Login as root State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Mon Apr 21 09:10:58 PDT 1997 State-Changed-Why: This is not a bug, you simply need to boot your system in single-user mode (see the FAQ). It's the -s flag at the boot: prompt. From owner-freebsd-bugs Mon Apr 21 09:23:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA27958 for bugs-outgoing; Mon, 21 Apr 1997 09:23:46 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27953 for ; Mon, 21 Apr 1997 09:23:42 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id JAA04917; Mon, 21 Apr 1997 09:23:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199704210852.SAA27852@godzilla.zeta.org.au> Date: Mon, 21 Apr 1997 09:10:16 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: Bruce Evans Subject: Re: Mystery of the X11 Panic... Cc: freebsd-bugs@freebsd.org Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Bruce Evans; On 21-Apr-97 you wrote: > [cc list trimmed to remove -hackers] > > >Fatal trap 12 - Page fault while in kernel mode. in virtual address > >0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing > it > >after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. > > > >Things go south at _spec_open + 0x6e, complaining about cmpl $0,0(%eax). > > This means that cdevsw[maj]->d_open is bad (probably null) although > cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. > Driver LKM's tend to cause this problem if they are unloaded. Bash > may trigger the problem because it does an opendir() on device files > (but I thought I fixed this by not opening device files in opendir()). > I wouldn't use LKMs for anything important. I thought about that and disabled all lkm's, I think. It only happens to bash if X11R6 is running and only on new 2.2 kernels. I think we need to make sure the kernel does not panic. Right? What can I do to help close this hole? Simon From owner-freebsd-bugs Mon Apr 21 09:42:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA28930 for bugs-outgoing; Mon, 21 Apr 1997 09:42:32 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA28906; Mon, 21 Apr 1997 09:42:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA13683; Mon, 21 Apr 1997 09:39:25 -0700 From: Terry Lambert Message-Id: <199704211639.JAA13683@phaeton.artisoft.com> Subject: Re: vnode as filesystem (crash!) To: mt@folco.lms.ru Date: Mon, 21 Apr 1997 09:39:25 -0700 (MST) Cc: terry@lambert.org, mtaylor@cybernet.com, hackers@freebsd.org, bugs@freebsd.org In-Reply-To: <199704211211.QAA02926@asteroid.intermedia.ru> from "Alex Povolotsky" at Apr 21, 97 04:11:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hmm... I couldn't make vnode working as filesystem at all. How should I init > the file intended to be a FS? Look in the handbook on "how to make a distribution"; it uses a vnconfig'ed vnode to do the job, and covers what you have to do in some detail. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Mon Apr 21 09:50:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA29485 for bugs-outgoing; Mon, 21 Apr 1997 09:50:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA29479; Mon, 21 Apr 1997 09:50:04 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 09:50:04 -0700 (PDT) Resent-Message-Id: <199704211650.JAA29479@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, pst@jnx.com Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29249 for ; Mon, 21 Apr 1997 09:45:05 -0700 (PDT) Received: (from pst@localhost) by red.jnx.com (8.8.5/8.8.5) id JAA15578; Mon, 21 Apr 1997 09:44:29 -0700 (PDT) Message-Id: <199704211644.JAA15578@red.jnx.com> Date: Mon, 21 Apr 1997 09:44:29 -0700 (PDT) From: Paul Traina Reply-To: pst@jnx.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3365: LKMs are a security hole -- need way to disable them Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3365 >Category: kern >Synopsis: LKMs are a security hole -- need way to disable them >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 09:50:02 PDT 1997 >Last-Modified: >Originator: Paul Traina >Organization: Juniper Networks >Release: FreeBSD 2.2-STABLE i386 >Environment: Any FreeBSD machine where you'd like to stop someone who gains root from mucking with your kernel. >Description: It's too easy for someone to gain root and add optional functionality to your kernel (such as the snp pseudo-device, or perhaps BPF support...albiet BPF is a bit harder). >How-To-Repeat: >Fix: I'd like to request two changes: (a) if securitylevel > N then LKM loading is disabled in the kernel (N = the same level that disables changing of the schg flag) (b) a kernel option to disable LKM loading Both of these are good 2.2-stable cannidates. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 10:08:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA01056 for bugs-outgoing; Mon, 21 Apr 1997 10:08:27 -0700 (PDT) Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA00307 for freebsd-bugs@freebsd.org; Mon, 21 Apr 1997 10:00:52 -0700 (PDT) Date: Mon, 21 Apr 1997 10:00:52 -0700 (PDT) Message-Id: <199704211700.KAA00307@freefall.freebsd.org> From: FreeBSD bugmaster To: FreeBSD bugs list Subject: Current problem reports Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The report has been examined by a team member and evaluated. f - feedback The problem has been solved, and the originator has been given a patch or a fix has been committed. The PR remains in this state pending a response from the originator. s - suspended Work on the problem has been postponed. This happens if a timely solution is not possible or is not cost-effective at the present time. The PR continues to exist, though a solution is not being actively sought. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested. Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- a [1995/01/11] i386/105 bde Distributed libm (msun) has non-standard o [1995/02/14] kern/216 davidg /kernel: panic: ffs_alloccg: map corrupte o [1995/12/08] kern/876 NFS allows bogus accesses to cached data a [1996/01/22] kern/965 bde 2.0.5: system crashes daily because of "m a [1996/03/04] kern/1059 hsu null fs panics system o [1996/04/06] kern/1121 dyson System crashes on boot up just after the o [1996/05/07] kern/1177 dyson Machine hangs with message "vm_fork: no p f [1996/06/05] kern/1293 Fatal trap 12: page fault while in kernel o [1996/06/11] kern/1311 dyson Panic: vm_page_free while installing new a [1996/07/15] bin/1387 davidn Group file errors cause absolute havoc a [1996/08/09] kern/1487 bde bug in exec(2) o [1996/09/11] kern/1599 panic: locking against myself s [1996/09/13] conf/1608 FreeBSD's bug tracking system does not re o [1996/09/29] bin/1694 rbootd does not appear to work o [1996/09/30] kern/1698 sup from around 21:51 GMT 28th very unsta a [1996/10/08] kern/1744 run queue or proc list smashed 4 times in o [1996/10/13] kern/1790 access to /dev/kmem panics system f [1996/10/28] kern/1919 se access to files/directories fails, gives o [1996/11/01] kern/1940 TCP doesn't time out of FIN_WAIT_1 and fl o [1996/11/04] i386/1959 DELAY() won't work for fast CPUs o [1996/11/15] kern/2033 unmount of doubly mounted devfs forces pa o [1996/11/29] kern/2121 MAXBSIZE in param.h causes kernel panic i o [1996/12/14] i386/2218 cy.c XON/XOFF handling crashes kernel o [1996/12/20] bin/2258 wollman route add/delete [network] xxx.yyy.zzz.0 o [1996/12/25] kern/2277 2.2-BETA fails to boot on my laptop f [1997/01/01] ports/2352 ports wu-ftp port does not work with DES crypte o [1997/01/03] conf/2367 gibbs Buslogic SCSI driver bad probe of 742A EI f [1997/01/04] kern/2371 gibbs SCSI disk corruption o [1997/01/14] kern/2498 On installation, after selecting drivers, a [1997/01/24] kern/2573 mmap on nfs mounted file hangs system o [1997/01/25] bin/2581 imp security holes in libtermcap o [1997/01/27] bin/2599 Lite2 merg and critical bugfix for games/ o [1997/02/01] kern/2635 NFS cache doesn't check execute permissio o [1997/02/06] kern/2680 bde bind of a local domain socket does not re o [1997/02/11] kern/2717 Panic with daily script (find) o [1997/02/14] bin/2740 wpaul root-fs full erases password table ! o [1997/02/17] kern/2754 Using memory mmapped to an NFS file can c o [1997/02/19] conf/2775 sos Syscons in 2.2 wont work with Diamond Spe o [1997/02/21] misc/2795 Cyclades 8YO -- Not working under 2.1.6-S o [1997/02/26] bin/2821 jkh XFree86 distributed with 2.2-GAMMA corrup o [1997/02/28] bin/2837 Globalyst550 Disk-Drive Not found!! o [1997/03/03] bin/2868 new fetch thinks that NCSA 1.5.2 server r o [1997/03/04] kern/2877 Fatal Trap 12: page fault while in kernel o [1997/03/05] kern/2890 System panic after kernel compiled for 12 o [1997/03/06] kern/2908 Fix for the NFS filehandle bug. o [1997/03/08] kern/2923 panic: vm_fault: fault on nofault entry, o [1997/03/11] bin/2946 res_send.c: make world fails on -current o [1997/03/13] kern/2980 2.2 crashes after accessing DAT-tape. bot o [1997/03/15] kern/3000 Kernel Panic in 2.2-CURRENT Kernel o [1997/03/16] kern/3005 can't completely install 2.1.7 release; s o [1997/03/17] kern/3017 panic: page fault as of March 11th v2.2 o [1997/03/17] bin/3019 Can't use SCSI disk (SCSI ID>3) on instal o [1997/03/20] kern/3046 copying a file to an NFS mounted partitio o [1997/03/22] kern/3067 Keyboard does not fonction after booting o [1997/03/23] misc/3070 Cannot do post install mods to UNIX from o [1997/03/23] kern/3072 Kernel Page Fault During Install of 2.1.7 o [1997/03/25] ports/3102 tg teTex port destroys previous contents of o [1997/03/25] kern/3103 vi large_file --> reboot without panic o [1997/03/26] ports/3106 torstenb pidentd exits with signal 6 o [1997/03/26] bin/3115 date command dumps core o [1997/03/27] kern/3128 Can't Install FreeBSD 2.2.1 o [1997/03/28] bin/3131 dlsym() does not set error on error, brea o [1997/03/30] kern/3150 Cyrix 6x86L-P200+ crashes w/ page fault o [1997/04/01] bin/3165 tex-3.14159.tgz lacks file o [1997/04/07] bin/3226 mpp vi died with a core dump o [1997/04/08] kern/3234 ipfilter.shar - integration complete o [1997/04/09] bin/3243 won't read file bin.cc - says "read -1 of o [1997/04/11] kern/3259 /bin/ps: kernel kernel, lockups, performa o [1997/04/12] kern/3267 mtime/ctime sometimes updated when a prog o [1997/04/15] i386/3300 Adaptec 2940U Problems o [1997/04/17] kern/3312 Adaptec 2940 still causes timeout using 2 o [1997/04/17] i386/3316 FOLLOWUP:Adaptec 2940U Problems->Addition o [1997/04/20] kern/3359 FreeBSD wont boot on amd p133 73 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [1994/11/30] kern/34 davidg nullfs and union mounts can result in wil a [1995/03/20] kern/260 davidg msync and munmap don't bother to update m s [1995/04/01] kern/291 se PCI devices still probe/attach after bein f [1995/05/08] bin/389 Simultaneous creation/deletion of dirs co a [1995/05/09] bin/392 Simultaneous cp and ls of files on dos f/ o [1995/05/16] kern/425 wollman arp entries not getting removed when inte a [1995/06/17] kern/527 dufault dump causes assertion in ncr.c o [1995/07/02] kern/579 bde sio: RS_IBUFSIZE at 256 bytes serial line f [1995/07/04] kern/587 if_le hangs on OACTIVE with 2k buffer s [1995/07/21] i386/631 if_ix does not support bpf, nor does it a s [1995/07/29] kern/638 Transmitted packets not passed to bpf in f [1995/08/11] gnu/672 Nor all ph headers get created o [1995/08/21] kern/703 amurai ppp not always deleting route properly wh o [1995/08/22] bin/706 jmg increased root DNS traffic and long laten f [1995/09/20] kern/730 gibbs 3Com 3C5x9 probe problem f [1995/09/27] kern/750 cd9660 confused by not-ready or I/O error a [1995/10/07] bin/771 telnet character mode not set and broken o [1995/10/18] bin/786 wpaul Problem with NIS and large group maps o [1995/11/12] kern/820 gibbs scsi tape problems f [1995/11/16] bin/826 mpp tcpmux listener in inetd does not work o [1995/11/28] bin/850 joerg dump treats write-protect as an EOT & spo o [1995/12/20] i386/906 davidg /sys/i386/boot/netboot/nb8390.com cannot o [1996/01/01] bin/926 Mounting nfs disks before starting mountd o [1996/02/12] kern/1020 .Boca 16-port board still hangs o [1996/02/12] docs/1023 mpp using touch to create swap file for NFS d a [1996/02/17] bin/1030 steve /bin/sh does not pass environment variabl f [1996/02/28] bin/1050 [floppy] Process (zip) hangs (unkillable) s [1996/03/06] kern/1067 mpp panic: ufs_lock: recursive lock not expec o [1996/03/09] bin/1073 telnet -8 does not work with SunOS or Sol o [1996/03/23] kern/1098 File system corruption (2 cases) o [1996/03/30] bin/1111 scrappy mail.local will happily deliver mail to a f [1996/05/14] kern/1204 umount -f after SCSI reset -> reboot o [1996/05/24] misc/1247 bde Conflicting header files f [1996/05/26] i386/1251 aha0 and bt0(eisa) conflicts again. o [1996/05/26] kern/1256 ZNYX 314 mysterously looses packets o [1996/05/28] kern/1271 phk Kernel panic using PLIP in 27/05 current o [1996/05/31] kern/1284 dyson panic: vm_page_free: freeing busy page o [1996/06/02] i386/1288 bde wdgetctlr (wd.c) return incorrect number o [1996/06/07] kern/1301 davidg DEC FDDI/PCI Adapter: halt code = 6 (DMA o [1996/06/10] kern/1308 dyson vm_page_free: wire count > 1 in 960501-SN a [1996/06/12] bin/1315 ls(1) a [1996/06/18] kern/1333 davidg free vnode isn't: another -stable coredum f [1996/07/03] bin/1364 mpp ps(1) bugs o [1996/07/09] gnu/1379 Man command problem, when it writes into a [1996/07/18] kern/1397 bde can't send to a pipe f [1996/07/24] kern/1423 wollman route causes kernel page fault. f [1996/08/01] bin/1454 steve /bin/sh bug handling <<[n] FD processing o [1996/08/03] bin/1461 Incorrect address binding of Kerberized r o [1996/08/04] kern/1467 gibbs scsi_prevent causing tape problems on clo o [1996/08/18] kern/1512 dyson Use of madvise may may cause bad memory m o [1996/08/22] kern/1533 dyson Machine can be panicked by a userland pro o [1996/08/25] misc/1541 julian fork.o in libc_r fails to compile f [1996/09/05] kern/1570 Setting SHMALL > 35000 causes panic f [1996/09/08] kern/1584 [unionfs] same file is listed twice o [1996/09/08] docs/1588 jfieber Handbook Incorrect LaTeX/PostScript outpu o [1996/09/14] kern/1610 dyson mmap() of unassociated memory + mlock() c o [1996/09/14] kern/1613 I get ls: fts_read: No such file or direc o [1996/09/16] i386/1626 MUSTEK Scanner hangs NCR SCSI controller f [1996/09/18] kern/1637 mss driver causes feedback (squeal) on so o [1996/09/19] bin/1650 telnet encryption with char-mode and asci o [1996/09/21] kern/1661 ft driver hangs uninterruptably at "bavai o [1996/09/26] kern/1684 inconsistent permission failures on NFS r o [1996/09/29] kern/1689 wollman TCP extensions throttles distant connecti o [1996/09/29] kern/1692 Page fault while in kernel modem fatal tr o [1996/10/01] bin/1702 installing of tcl manpages fails from mak o [1996/10/03] kern/1715 le driver non-reentrant o [1996/10/04] kern/1723 gibbs kernel fault when doing scsi reprobe o [1996/10/04] kern/1724 gibbs HP colorado T4000S tape drive hangs syste o [1996/10/04] kern/1726 panic in kmem_malloc (dump available) o [1996/10/05] i386/1730 sos SFF8020 violation and silly bug in atapi. o [1996/10/10] ports/1753 markm SSLeay doesn't work against Microsoft sec o [1996/10/10] kern/1754 netbooted machines freeze with ifconfig a o [1996/10/11] bin/1773 ports A NULL pointer causing segmentation core o [1996/10/13] gnu/1787 markm Diffs with Index: lines are not honored f o [1996/10/15] bin/1810 fsck -p does not check pass 0 filesystems o [1996/10/15] kern/1812 dyson vnodes are left in a locked state o [1996/10/15] kern/1814 cy driver gets deadlocked sometimes a [1996/10/18] kern/1839 mpp Multiple mfs mounts of same mount point o [1996/10/20] kern/1848 breakpoints may be set in shared librarie o [1996/10/21] kern/1856 read-only nfs mount: panic leaf should be o [1996/10/22] ports/1866 wosch popclient flushes remote mailbox even wit o [1996/10/24] kern/1880 kernel crash during boot when using 512 M o [1996/10/25] bin/1891 mountd fails to export o [1996/10/26] bin/1892 install(1) removes target file o [1996/10/29] bin/1927 User CPU time getting accounting as syste o [1996/11/04] bin/1952 guido Long chat script makes ppp dump core o [1996/11/07] bin/1973 jmg pppd uses /etc/ppp/options.tty after comm o [1996/11/08] gnu/1981 ypserv handles null key incorrectly f [1996/11/08] kern/1982 fenner arpresolve: cant allocate llinfo for 207. o [1996/11/13] ports/2000 asami obsolete software in distfiles directory a [1996/11/13] bin/2001 mpp vi confused about lines to display o [1996/11/13] i386/2002 sio doesn't detect com port on Compaq Con o [1996/11/14] misc/2013 'make world' fails on read-only /usr/src o [1996/11/14] kern/2014 sos Console keyboard lockup problem o [1996/11/15] bin/2016 static libtcl references symbols that are o [1996/11/15] kern/2034 julian [devfs] wd* driver "slot name rejection e o [1996/11/15] gnu/2035 peter deque bug, local gnu changes to deque hea o [1996/11/18] kern/2053 de0 driver don't work at 100M for Compex o [1996/11/19] i386/2058 sos amity series machines can not show instal o [1996/11/24] kern/2094 wd1: interrupt timeout: o [1996/11/26] bin/2107 problem building a system from cdrom. o [1996/11/29] kern/2124 sos Hitachi CDR-7730 ATAPI CD-ROM recognized s [1996/12/03] kern/2142 FP mask not saved for signal handlers o [1996/12/03] kern/2144 kernel panic (page fault) running chgrp o [1996/12/08] kern/2181 2.2-ALPHA flickers/wavers part of the upp o [1996/12/09] bin/2187 brian ijppp: LQR is broken o [1996/12/10] misc/2189 mpp netdb.h works not with -traditonal cc fla o [1996/12/10] bin/2191 syslogd stops logging after several hours o [1996/12/13] bin/2206 NIS Makefile can't manage appletalk entri o [1996/12/17] kern/2232 MSDOSFS corrupts MSDOS partitions > 500Mb o [1996/12/18] kern/2248 Mitsumi CD-ROM driver has "timeout" probl s [1996/12/19] bin/2255 Client PPP negotiates Stacker compression o [1996/12/20] bin/2256 PPP process on port will not close when a s [1996/12/22] ports/2268 ports libc from linux emulator does not use /et o [1996/12/22] kern/2270 Hayes ESP serial card locks system as of a [1996/12/25] misc/2283 ache setlocale() in libxpg4 always returns NUL o [1996/12/29] bin/2318 /usr/libexec/rlogind doesn't work after t a [1996/12/30] kern/2325 mpp quota.user enlarged, no boot on 2.2-BETA o [1996/12/30] kern/2330 changing root device to sd0a - ncr0: abor o [1996/12/31] ports/2340 obrien gshar+gunshar needs to be updated to 4.2 o [1997/01/01] kern/2351 panic:timeout table full o [1997/01/06] kern/2388 joerg start unit command screws up some CDROM d o [1997/01/07] gnu/2394 tar will extract files even if -C command f [1997/01/07] kern/2401 joerg 2.2 RELENG sometimes locks up early on bo o [1997/01/08] kern/2425 amd driver does not reprobe devices. o [1997/01/08] conf/2426 At end of install, panic: Going nowhere w o [1997/01/09] bin/2430 mountd stops on loading if subnet mask is o [1997/01/09] i386/2431 panic: get_pv_entry: cannot get a pv_entr o [1997/01/12] i386/2471 Sound: Reset failed - Can't reopen device o [1997/01/13] misc/2479 sos NEC CD-ROM NOT RECOGNIZED; MATROX MISTIQU o [1997/01/13] bin/2489 mpp gnats mangles sections o [1997/01/16] kern/2507 Renaming DOS directories with "mv" causes o [1997/01/18] kern/2521 kernel from 2.1.6 install CD doesn't acce o [1997/01/18] bin/2527 fetch doesn't print enough of the error m o [1997/01/20] kern/2538 worm burning suddenly broken o [1997/01/20] bin/2541 cd (using /bin/sh) may leave you in the w o [1997/01/20] kern/2545 se < sd0(ncr0:6:0): COMMAND FAILED ==> Not o [1997/01/21] bin/2549 sos cdcontrol refuses to play audio CDs from f [1997/01/21] misc/2551 davidn limit too small for user root o [1997/01/23] kern/2569 route -iface breaks inet behaivour f [1997/01/24] kern/2570 fenner arpresolve: cant allocate llinfo o [1997/01/25] bin/2591 sh coredumps when passing an argv of a ce o [1997/01/26] bin/2597 everything stops when the new ld.so is in o [1997/01/29] kern/2613 ache syscons mistakes MONO for MONO VGA o [1997/01/29] misc/2614 make reinstall does not work o [1997/01/29] bin/2616 Installs very irratically from the same c o [1997/01/30] bin/2622 syslogd '-s' behavior either broken or po o [1997/01/31] misc/2625 fixed broken src/includes o [1997/01/31] kern/2628 code clean up of sys/sys o [1997/01/31] kern/2632 enabling psm mouse causes keyboard to not o [1997/01/31] bin/2633 fsck -p in /etc/rc fails with cannot allo o [1997/02/02] kern/2640 2.2-RELENG leaks memory (router/pppd serv s [1997/02/03] kern/2647 changing existing route to -static crashe o [1997/02/04] ports/2664 elm methodically writes garbage into fold o [1997/02/05] kern/2667 wollman bpfattach can hang the system f [1997/02/05] bin/2670 fetch fails with HTTP_PROXY o [1997/02/05] bin/2671 Run-away processes using all CPU time a [1997/02/06] kern/2675 lkmcioctl() is not consistent and careful o [1997/02/07] kern/2690 asami When Using ccd in a mirror mode, file cre o [1997/02/08] kern/2695 sio1 (16540 serial port) is not recognize o [1997/02/09] kern/2698 After rewind I cannot read a tape; blocks o [1997/02/12] kern/2719 added support for magneto-optical SCSI di o [1997/02/13] ports/2731 ports new port: Tcl 8.0A2 o [1997/02/14] kern/2732 mcopy 3.0 causes kernel hang o [1997/02/14] bin/2736 No boot block if no FreeBSD partitions on o [1997/02/14] kern/2738 julian [DEVFS problem] Kernel crashes when you m o [1997/02/15] kern/2742 panic: leaf should be empty o [1997/02/15] bin/2747 davidn cannot submit at jobs from within an at j o [1997/02/17] kern/2751 asami 2GB limitation on CCD device partitions s o [1997/02/18] bin/2762 Precedence mistake in libncurses o [1997/02/19] kern/2768 ktrace(1) -i dumps corrupted trace data o [1997/02/19] bin/2769 fsck needs several runs to clean up bad/d o [1997/02/19] kern/2770 panic: vm_fault: fault on nofault entry o [1997/02/19] kern/2771 panic: bad dir f [1997/02/19] kern/2772 gibbs panic: %s:%c:%d: Target did not send an I o [1997/02/19] kern/2773 bad dir panic o [1997/02/20] misc/2781 Installation crashes if timeout in ftp tr o [1997/02/20] misc/2784 brian userland PPP rises load to 1.00 o [1997/02/20] bin/2785 wpaul callbootd uses an unitialized variable o [1997/02/20] gnu/2786 gcc version 2.7.2.1 C compiler slows down o [1997/02/21] misc/2793 libc_r make fscanf failure o [1997/02/22] kern/2800 DDS large data writing probrem o [1997/02/25] kern/2815 Custom Kernel crashes o [1997/02/27] bin/2829 jkh FTP installs can only fail once o [1997/02/28] bin/2832 w treats corrupted utmp as fatal error o [1997/03/01] kern/2840 mlock+minherit+fork+munlock causes panics o [1997/03/01] ports/2842 ports Expect port upgraded at master site; does o [1997/03/02] bin/2844 libedit sync with NetBSD/OpenBSD o [1997/03/03] i386/2853 syscons beeps even if beeping screen is n o [1997/03/03] kern/2858 dfr FreeBSD NFS client can't mount filesystem o [1997/03/03] bin/2867 sysinstall goes into an infinite loop dur o [1997/03/04] kern/2873 the od0 devies does not handle a Maxoptix o [1997/03/04] docs/2874 The gencat command hasn't got a manual pa o [1997/03/04] bin/2879 steve sh: ! fails to negate the return value of o [1997/03/06] kern/2896 FreeBSD 2.2-GAMMA does not work with DIam o [1997/03/07] bin/2915 the "-fstype ufs" option of "find" seems o [1997/03/07] ports/2918 ports Unable to pass 8+ command line arguments o [1997/03/08] kern/2919 vm_fault: fault on nofault entry, addr: f o [1997/03/09] bin/2925 non-priviledged user can crash FreeBSD!! o [1997/03/11] bin/2948 can't dump 640MB optical disks o [1997/03/11] ports/2956 ports New Port: xgospel-1.10d in ftp.freebsd.or o [1997/03/12] kern/2965 st0 hang/fail on reading 4mm DAT tape for o [1997/03/12] bin/2969 csh and/or builtin printf has problems wi o [1997/03/12] bin/2973 output of iostat is wrong. o [1997/03/15] kern/2991 RTF_LLINFO routes remain when interface i o [1997/03/15] ports/2992 ports xperfmon++ port is out of date a [1997/03/15] ports/2994 ports xpm port does not build for the first tim o [1997/03/15] bin/2997 unterminated string after strncpy o [1997/03/17] conf/3016 fvwm95-2 does not have system resource fi o [1997/03/18] kern/3021 panic after sync during reboot o [1997/03/18] bin/3027 error parsing mount options which include o [1997/03/18] kern/3029 typo in libc o [1997/03/19] kern/3039 higher securelevel (>0) stops X server o [1997/03/21] i386/3048 multicast support necessery in some drive o [1997/03/21] kern/3054 OPL3 sound off by one note o [1997/03/21] bin/3055 umount -f does not work o [1997/03/22] kern/3059 2.2 RELEASE hangs during or immediately a o [1997/03/22] kern/3066 System lock-up after npx0 probe with 2.2- o [1997/03/24] i386/3082 keyboard locks up unexpectedly o [1997/03/24] i386/3083 Toshiba XM-5702B ATAPI CDROM not detected o [1997/03/24] bin/3085 make world fails on compiling dumpfs.c o [1997/03/24] misc/3086 panic: cannot mount root - on boot, when o [1997/03/25] kern/3104 Cannot execute files on a nullfs filesyst o [1997/03/26] kern/3107 2.2.1-RELEASE can't boot on at least two o [1997/03/26] conf/3109 unintellible upgrade doc o [1997/03/26] docs/3114 brian Use of HISADDR in ppp.conf incorrect o [1997/03/27] kern/3122 _POSIX_SAVED_IDS not defined in 2.2 o [1997/03/27] conf/3123 /stand/sysintstall does not perform to up o [1997/03/27] i386/3124 BOOT_PROBE_KEYBOARD hangs system in bootb o [1997/03/27] ports/3125 torstenb inn port incorrect use of perl5 o [1997/03/27] bin/3126 Install with mcd0 still broken. o [1997/03/27] bin/3127 PCI Ether card slower than ISA Ether card o [1997/03/28] i386/3130 Dell Latitude keyboard lock up o [1997/03/28] misc/3133 TIOCSETD error with Cyclades 8Yo o [1997/03/28] kern/3134 Both boot and boot-pao floppies hang afte o [1997/03/29] ports/3142 ports new port: slrn o [1997/03/30] ports/3146 ports new port fix (slrn) o [1997/03/30] gnu/3149 patch-2.1: files possibly created in wron o [1997/03/31] kern/3156 Copying to floppy device file locks machi o [1997/03/31] bin/3158 seg faults and cannot update links using o [1997/04/01] kern/3162 2.2 kernel from mar 25th crashes on nfs s o [1997/04/01] bin/3170 vi freaks and dump core if user doesn't e o [1997/04/02] gnu/3176 `patch' creates files in wrong places o [1997/04/02] ports/3179 ports WebStone 2.0.1 port submitted o [1997/04/02] kern/3180 mlock() causes panic: lockmgr: upgrade ex o [1997/04/04] ports/3193 ports MAKE fails for /usr/ports/net/ucd-snmp o [1997/04/04] i386/3195 ahc panic o [1997/04/05] kern/3201 de0 not re-enabled after hub down o [1997/04/05] ports/3205 ports Mtools-3.0 attempts to flock() a disk par o [1997/04/05] kern/3209 3.0-current panics on shutdown/reboot/hal o [1997/04/06] kern/3216 panic: pmap_zero_page: CMAP busy o [1997/04/06] kern/3219 sppp or arnet gets looped after connectio o [1997/04/07] kern/3220 2.2.1 RELEASE - hangs during boot... o [1997/04/07] bin/3222 Add null termination after strncpy o [1997/04/08] bin/3230 Unable to resolve dev conflict between ed o [1997/04/09] kern/3244 ipfw flush closes connections o [1997/04/10] bin/3246 mtree -c should escape whitespace and spe o [1997/04/11] ports/3256 ports ncftp-2.4.2 in packages-2.2 was not linke o [1997/04/11] docs/3257 make cleandepend is broken in src/ o [1997/04/11] kern/3260 FreeBSD 2.2.1 (and 2.2) npx0 boot problem o [1997/04/12] pending/3263gnats-admintroubles with digiboard o [1997/04/13] ports/3274 ports mars fails to build if "." not in PATH o [1997/04/13] kern/3276 unmount DEVFS ==> panic: unmount: danglin o [1997/04/13] kern/3278 mounting MFS uses up swap space o [1997/04/14] misc/3291 md2.h, md4.h, and md5.h headers useless f o [1997/04/14] kern/3292 Cyrix 486 performance problem o [1997/04/15] kern/3304 NFS V2 readdir hangs o [1997/04/15] bin/3305 Can't do encrypted rlogin into self o [1997/04/16] bin/3307 Unable to Route to a different Class C wi o [1997/04/16] misc/3308 Missing "#include item' when making world o [1996/10/23] bin/1872 automounter (amd) cannot ls directories w o [1996/10/24] kern/1878 sos SONY CDU76E IDE/ATAPI CDROM support. o [1996/10/24] bin/1881 file(1) misidentifies Sun3/m68k executabl o [1996/10/26] docs/1896 compilation errors in share/doc/psd/19.cu o [1996/10/26] bin/1897 Sendmail 8.8.2 requires /etc/sendmail.cw o [1996/10/27] bin/1904 /usr/bin/su is not careful enough in veri o [1996/10/27] misc/1908 jkh FTP install failed DNS lookup o [1996/10/29] bin/1924 if lpd is not running, lpc will say ``no o [1996/10/30] i386/1931 Mitsumi CDrom works well under 2.1.x, fai o [1996/10/31] ports/1939 ports exodus port doesn't build with new g++-2. o [1996/11/01] bin/1941 wtmp and monthly rotation o [1996/11/01] bin/1943 route(8) args o [1996/11/02] bin/1945 Out of date code/comments in dd o [1996/11/03] i386/1950 Sound driver doesn't encode/decode mu-law o [1996/11/04] i386/1953 syscons savers have no default timeout o [1996/11/04] gnu/1961 uucp logging files are in /var/spool/uucp o [1996/11/06] bin/1968 FreeBSD has no rdate(8), here's one o [1996/11/06] bin/1970 csh limtail() bug o [1996/11/09] bin/1985 pkg_delete outputs confusing message when o [1996/11/13] kern/2004 route add -link panic o [1996/11/13] bin/2005 Poor command line argument checking and b o [1996/11/14] bin/2008 kerberos tickets from login all have the o [1996/11/15] kern/2022 Switching from X display to virtual conso o [1996/11/16] bin/2036 cpio size wraparound o [1996/11/16] ports/2038 torstenb sshd dies on FreeBSD machines if run as a o [1996/11/17] bin/2046 brian vjcomp problem in iij-ppp o [1996/11/18] ports/2051 obrien HDF library port o [1996/11/19] bin/2061 DEBUG_FLAGS in bsd.lib.mk is broken o [1996/11/19] bin/2065 wollman in tzsetup/sysinstall, allow user to type o [1996/11/19] misc/2068 Unstable keyboard mappings on the main tt o [1996/11/20] kern/2072 ZIP drive support is available for FreeBS o [1996/11/21] ports/2079 obrien New ports supporting AWE sound driver (fo o [1996/11/21] bin/2080 The scanf family doesn't support 'q' modi o [1996/11/22] docs/2087 ifconfig.8 does not document how to remov o [1996/11/22] bin/2090 clients may bind to FreeBSD ypserv refusi o [1996/11/23] bin/2093 AMD gets sig 11 when /etc/malloc.conf is o [1996/11/24] ports/2096 tg ImageMagick outdated, lzw not supported o [1996/11/25] ports/2100 andreas New port: VGBZoom o [1996/11/25] misc/2105 bsd.lib.mk has problems with STRIP and IN o [1996/11/26] bin/2106 Byte order problem in -current routed o [1996/11/26] i386/2108 sos [ATAPI] wcd driver may hang under certain o [1996/11/28] i386/2117 nb8390.com hangs with some BIOS combinati o [1996/11/28] kern/2118 writing to virtual consoles fails to disp o [1996/11/28] bin/2119 mount lies to child about argv0, which ca o [1996/12/01] bin/2133 netstat -s overflows to negative o [1996/12/02] bin/2137 vm statistics are bad o [1996/12/02] kern/2140 FreeBSD leaves EtherExpress 16 net card i o [1996/12/03] ports/2145 ports qpopper bulletin support broken o [1996/12/03] conf/2146 wrong /dev for COM2 during installation v a [1996/12/04] docs/2153 mpp Manual page of bootparams(8) refers to a o [1996/12/06] i386/2166 psm driver locks the console o [1996/12/07] ports/2169 pst zephyr port does not completely compile o [1996/12/08] ports/2173 peter top does not compile under FBSD 2.1.6 o [1996/12/08] ports/2182 ports FreeBSD's and X-32's list of locales do n o [1996/12/08] bin/2184 sendmail has lots of trouble with local d o [1996/12/08] misc/2185 phk add ability to change partition type in l a [1996/12/10] ports/2190 asami need cross-reference to xpdf from X11 por o [1996/12/12] kern/2199 joerg Got a lots of "Target Busy" messages with o [1996/12/14] kern/2214 File System gets corrupted when mounting o [1996/12/14] bin/2216 Ada specs not being compiled into cc/gcc o [1996/12/16] bin/2227 FreeBSD does not recognize WD7000-ASC dri o [1996/12/17] i386/2234 fbsdboot.exe does not turn off floppy dri o [1996/12/17] i386/2239 some interrupts take too long (i.e. BT946 o [1996/12/18] misc/2242 Suggest add optional mt blocksize 512 o [1996/12/18] bin/2247 imp getopt should return -1 rather than EOF o [1996/12/20] bin/2260 PPP logins using PAP to Nortel/Shiva syst o [1996/12/21] ports/2264 ports latex* ports need updating a [1996/12/21] bin/2265 guido su(1) does not call skeyaccess() o [1996/12/23] kern/2271 FIONREAD on tunnel device returns incorre o [1996/12/24] kern/2273 support for POSIX.4 / POSIX.1a RT-schedul o [1996/12/24] docs/2275 no support for isdn-cards o [1996/12/25] conf/2284 Termcap ibm3163 entry has arrow keys wron o [1996/12/26] bin/2291 race condition in /etc/master.passwd lock o [1996/12/27] kern/2298 Support for DSR/DCD swapping on serial po a [1996/12/27] misc/2302 markm new crypt() including SHS and an extendab o [1996/12/28] misc/2309 Thread safe fixes to malloc, localtime, l o [1996/12/28] ports/2313 torstenb pidentd fails in 2.2-BETA o [1996/12/29] bin/2315 tail segfaults on NFS permission denied o [1996/12/29] misc/2323 FreeBSD.FAQ file in ftp.freebsd.org is lo o [1996/12/30] kern/2327 `Green' saver for pcvt o [1996/12/31] bin/2336 jkh Sysinstall won't install dists on 2nd pas o [1997/01/01] docs/2353 Changes to FAQ o [1997/01/03] bin/2366 libc does not consult /etc/services to fi o [1997/01/03] bin/2368 serial line logins "freeze" during login o [1997/01/05] ports/2379 ports New URT port o [1997/01/06] bin/2382 curses.h / -lcurses incompatible with C++ o [1997/01/06] bin/2383 Inconsistent tputs(3) prototypes in curse o [1997/01/06] misc/2386 patches for new socket credential firewal o [1997/01/06] bin/2387 virtual hosting patches for inetd o [1997/01/06] kern/2390 Some CDROM drives stop audio on cdcontrol o [1997/01/07] kern/2393 filesystems not unmounted following shutd o [1997/01/07] misc/2407 dirent.h does not include sys/types.h o [1997/01/07] bin/2410 pppd(8): failing PAP doesn't force line d o [1997/01/07] kern/2412 Wine does not work o [1997/01/07] ports/2413 peter Cannot redirect "top" output o [1997/01/08] kern/2424 Pressing ALT-Fn during boot -c leave bell o [1997/01/09] kern/2429 Driver for AIMS Lab RadioTrack radio card o [1997/01/10] bin/2437 minor nits on text in 2.2-BETA install o [1997/01/10] bin/2442 davidn setusershell()/endusershell() missing o [1997/01/10] bin/2443 Fetch cannot find the correct boundary be o [1997/01/10] ports/2445 ports New port : Cosmo Gang the Puzzle (games/c o [1997/01/11] bin/2448 semctl() not portable -- freebsd requires o [1997/01/11] bin/2449 brian ij-ppp in auto mode goes into failure loo o [1997/01/11] docs/2455 no description "option COMCONSOLE" MLEN o [1997/01/26] misc/2596 dd refuses to respond to SIGkill o [1997/01/26] i386/2598 ep0 in EISA mode hangs if ep0-device (ISA o [1997/01/28] bin/2603 Added POSIX.4/POSIX.1b constants in unist o [1997/01/28] bin/2604 Added POSIX.4/POSIX.1b shm_open()/shm_unl o [1997/01/28] ports/2607 max New port: Gopher-2.3 o [1997/01/28] bin/2609 Problem receiving more than 1688835 bytes o [1997/01/29] misc/2617 Utility submission - upsmon - UPS monitor o [1997/01/30] kern/2621 Patch to support Cogent EM110 fast-ethern o [1997/01/30] docs/2623 ipfirewall(4) man page is way out of date o [1997/01/30] bin/2624 kdump unaware of semsys and several other o [1997/01/31] bin/2630 xargs does excessive and inconsistent arg o [1997/01/31] bin/2631 kill interprets empty arg as PID 0 o [1997/02/02] gnu/2637 tar dumped core with -g option. f [1997/02/02] ports/2639 jkh FreeBSD 2.2 teTeX-0.4 package does not in a [1997/02/02] bin/2641 wpaul login_access.c doesn't work with NIS by d o [1997/02/03] ports/2653 pst mh-6.8.4 manpage error for slocal o [1997/02/04] bin/2657 ypserv thinks there is no computers in ne o [1997/02/04] bin/2660 When selecting BSD to boot from system ha o [1997/02/04] bin/2665 port 22 isn't being converted to ".ssh" i o [1997/02/05] bin/2668 modification suggested for rarpd o [1997/02/05] bin/2672 Problem with telnetd o [1997/02/06] ports/2677 ports Various ports have checksum problems o [1997/02/06] kern/2681 missing prototype in s [1997/02/07] ports/2684 torstenb ircII port upgrade; 2.9_roof -> 2.9alpha1 o [1997/02/07] kern/2686 struct igmpmsg in s o [1997/02/07] misc/2687 sysinstall umounts floppy after prompting o [1997/02/10] bin/2703 vipw doesn't allow you to edit master.pas o [1997/02/10] kern/2704 Occasional failure to detect wdc1 on boot o [1997/02/10] kern/2705 `(c) 1992-1996 FreeBSD Inc.'; year is now o [1997/02/11] conf/2709 FBSD 2.1.6 X-Server installation setup ut o [1997/02/11] i386/2710 pst if_ppp LKM does not allow ppp line discip o [1997/02/11] bin/2713 ftp daemon processes don't terminate, eve o [1997/02/11] kern/2715 MSDOS-FS 1024/2048 byte/sector media supp o [1997/02/11] kern/2716 od.c/sd.c non 512 byte/sector support imp o [1997/02/13] i386/2729 "make tags" in sys/kern produces barely u o [1997/02/14] bin/2734 jkh pkg_* uses relative paths to executables o [1997/02/14] bin/2735 jkh Add signature support (both MD5 and PGP) o [1997/02/14] bin/2737 yppasswd fails to change password on a su o [1997/02/15] misc/2745 fenner PR querry web form doesn't sort correctly o [1997/02/17] bin/2752 NULL is used instead of 0 many places o [1997/02/20] ports/2778 ports New Port: Version of traceroute which pri o [1997/02/20] docs/2780 2.2 Handbook still says 2.1.6 o [1997/02/20] bin/2782 err man page is slightly wrong o [1997/02/21] misc/2789 na.phone update o [1997/02/21] bin/2792 steve yacc-generated parser and (const)'s and c o [1997/02/22] ports/2797 tg New Port: qmail o [1997/02/23] kern/2806 new kernel tags script o [1997/02/23] kern/2807 pcisupport.c uses sprintf field widths, n o [1997/02/24] docs/2810 Tutorial submission detailing how to upgr o [1997/02/25] i386/2813 hard reference to /usr/src breaks make wo o [1997/02/25] ports/2816 ports New port - aftp ftp-like shell for apple2 o [1997/02/25] ports/2817 ports New port - prodosemu is an Apple2e prodos o [1997/02/26] conf/2819 /etc/rc does not execute 'uname' when con o [1997/02/26] conf/2822 ftp install specifying URL confusing o [1997/02/27] gnu/2827 after make world genclass is not installe o [1997/02/28] docs/2833 Repeated topics on FAQ entry hardware com o [1997/02/28] gnu/2834 Patches to gas and gdb to support MMX ext o [1997/03/02] bin/2845 sync with spiffy new netbsd/openbsd ftp c o [1997/03/02] misc/2848 jmg newsyslog will notify syslogd, not any ot a [1997/03/02] ports/2849 ports correction to New math/cad port (SCILAB) o [1997/03/02] docs/2850 init(8) man page does not document secure o [1997/03/02] bin/2851 script(1) sets argv[0] of the started she o [1997/03/03] kern/2857 DE500 board exhibits capture effect o [1997/03/03] bin/2859 /usr/bin/quota seems to choke on long gro o [1997/03/03] misc/2863 New keymap for Latin American Keyboards o [1997/03/03] bin/2864 Using modload with -p option broken o [1997/03/03] kern/2865 NFS client hangs on umount, ls, df when N o [1997/03/03] ports/2869 ports Submiting new port: tac_plus o [1997/03/03] bin/2871 showmount -e returns error o [1997/03/04] docs/2880 sh man page talks about "...by the time 4 o [1997/03/04] misc/2882 Duplicate line in /etc/services? o [1997/03/05] kern/2886 fenner mbuf leak in multicast code o [1997/03/06] docs/2897 mpp send-pr categories should be explained so o [1997/03/06] bin/2898 fenner arp -a -n buglet o [1997/03/06] ports/2900 ports new port: netris -- a free networked vers a [1997/03/06] ports/2902 ports Fix xmcd port for PACKAGE_BUILDING o [1997/03/06] ports/2903 ports New port: xdeblock o [1997/03/06] ports/2904 ports New port: wm2 a [1997/03/06] ports/2905 ports Fixed port: xshisen-1.36 o [1997/03/07] ports/2916 ports ports sysutils/top/Makefile MASTER_SITES o [1997/03/08] ports/2920 ports patch for mispositioned xv windows under o [1997/03/08] ports/2922 ports Please commit new port: viz-1.1.1 o [1997/03/09] i386/2924 syscons X keyboard gets stuck in capsmode o [1997/03/09] ports/2926 ports xmgt-2.31 port, now in pub/incoming on ft o [1997/03/10] bin/2930 lack of NFS V3 support in amd(8) o [1997/03/10] bin/2933 sysinstall fails when adding packages thr o [1997/03/10] bin/2934 sh(1) has problems with $ENV o [1997/03/10] ports/2936 ports The teTeX port runs strup on /usr/local/b o [1997/03/10] bin/2938 Add -b, -l, and -f options to du(1) o [1997/03/10] docs/2939 `man 8 sticky` == outdated o [1997/03/10] conf/2943 standard-supfile missing src-release and o [1997/03/11] ports/2949 ports bsd.port.mk needs something like FETCH_EN o [1997/03/11] ports/2951 ports xgraph source is not on MASTER_SITE o [1997/03/11] misc/2955 pkg_add failed on xemacs via sysintall o [1997/03/12] ports/2960 ports Update the port(jp-camltk41-1.0):japanese o [1997/03/12] ports/2961 ports New port(jp-vftool-1.2):japanese/virfonts o [1997/03/12] bin/2968 fmt dumps core on ^M o [1997/03/12] ports/2970 ports Easy update to CIM (lang) o [1997/03/12] ports/2971 ports CIM 1.84 --> 1.92 patch o [1997/03/13] ports/2974 ports updated Makefile and patch-ab of jp-dvi2p o [1997/03/13] bin/2977 After enabling moused and vidcontrol and o [1997/03/13] bin/2979 GCC complains about stmt. expr. when comp o [1997/03/13] i386/2984 serial port console only prints ~ 1 char o [1997/03/14] ports/2986 ports fvwm95-2.0.43a port don't install/have ma o [1997/03/14] ports/2988 joerg vga font is not built o [1997/03/15] ports/2993 ports qmail-port-take2-proff.tar.gz in incoming o [1997/03/15] kern/3001 soundblaster8 card does not work correctl o [1997/03/16] misc/3009 packages-2.2/x11/fvwm-1.24r.tgz corrupt o o [1997/03/17] ports/3012 ports qmailanalog port in incoming o [1997/03/18] conf/3022 /etc/sysconfig was not set up with option o [1997/03/18] conf/3023 By default users have no write permission o [1997/03/18] misc/3024 make reinstall in /usr/src requires writa o [1997/03/18] bin/3025 mv to / trailed dirs prints odd error mes o [1997/03/18] bin/3028 sos add support for Glidepoint pointing devic o [1997/03/19] misc/3040 sysinstall XF86Config graphic mode YES=== o [1997/03/19] bin/3042 comm and uniq do not have a case insensit o [1997/03/21] docs/3051 Missing 'mailto:' in some place in the ha a [1997/03/21] ports/3052 ports /usr/ports/lang/expect does not find tkCo o [1997/03/22] kern/3061 route does not accept -genmask o [1997/03/24] misc/3075 2.2-R install "features" (non critical) o [1997/03/24] bin/3080 yacc produces output which doesn't compil o [1997/03/24] ports/3081 ports sitelispdir is a directory no a path in x o [1997/03/24] ports/3090 ports ircii-2.9-roof does not run. o [1997/03/25] ports/3098 ports new ports of kr-nhpf-1.42 o [1997/03/25] kern/3100 IPFW panics upon denying a packet o [1997/03/25] bin/3101 "command" entry of ps -uc is too wide, ou o [1997/03/26] misc/3111 make bootstrap relies on /bin/sh but does o [1997/03/26] docs/3112 Handbook says that users should use sup o [1997/03/26] misc/3113 make libraries failed. o [1997/03/26] bin/3116 iij ppp does not provide link-down notifi o [1997/03/27] misc/3119 /usr/share/syscons/keymaps/german.iso.kbd o [1997/03/27] ports/3121 tg teTeX 0.4 package has missing links ? o [1997/03/28] misc/3136 rc.firewall should be run after interface o [1997/03/28] ports/3137 ports new port of xmake-1.00 o [1997/03/29] bin/3139 qcamcontrol has a bug where I/O errors ar o [1997/03/29] misc/3140 display message is broken on boot.flp o [1997/03/30] ports/3143 ports mkisofs site has moved o [1997/03/30] docs/3147 /usr/share/misc/au.postcodes o [1997/03/30] misc/3148 adjkerntz screws up during GMT/BST change o [1997/03/31] bin/3152 FreeBSD 2.2-STABLE: getty does not initia o [1997/03/31] ports/3153 ports new port request of hcode-2.1mailpatch2 o [1997/03/31] ports/3154 ports new port request of hmconv-1.0pl3 o [1997/03/31] misc/3155 Checksum mismatch o [1997/03/31] gnu/3157 Patches to gas and gdb to support MMX ext a [1997/04/01] bin/3164 mpp view copies the file into vi.recover o [1997/04/01] ports/3166 ports ghostscript-2.6.2 install script has a wr o [1997/04/01] ports/3169 ports nn port broken o [1997/04/01] conf/3171 Typo in /etc/sysconfig o [1997/04/01] kern/3172 CS4232 support trouble for mss0 o [1997/04/02] docs/3178 error in getopt.3 o [1997/04/02] ports/3181 fenner misc/cal is no longer on the master site o [1997/04/03] ports/3185 tg Port submission for LPRng-3.2.1 o [1997/04/03] ports/3189 ports Update plan to version 1.6 o [1997/04/03] bin/3190 RISCom N2 card driver problem? o [1997/04/04] kern/3191 Commiting of the ppa Zip Drive driver to o [1997/04/04] bin/3194 2.2.1-RELEASE hangs when using /stand/sys o [1997/04/05] ports/3199 ports new ports collection: automake-1.0 o [1997/04/05] bin/3202 shutdown(8) don't work if started from an o [1997/04/05] ports/3203 ports xmcd-2.1 won't build o [1997/04/05] bin/3206 su seg-faults when being invoked with an o [1997/04/06] bin/3210 routed having problems with /etc/gateways o [1997/04/06] bin/3211 ctm uses mktemp()> o [1997/04/06] bin/3212 the pkg_* tools use mktemp() o [1997/04/06] ports/3215 ports Update to Gnat port o [1997/04/06] misc/3217 The rmail.c err() function will fail in m o [1997/04/06] bin/3218 syscons causes segmentation fault by repe o [1997/04/07] bin/3221 rpc.rusersd : can't communicate with SunO o [1997/04/07] misc/3225 uucpd.c should normalize host names as lo o [1997/04/08] ports/3227 ports new port(xtimer-8087) o [1997/04/08] bin/3232 XFree86 installation Problem with non-Mic o [1997/04/08] bin/3233 adduser(8) doesn't add users to the wheel o [1997/04/08] misc/3237 SCRIPTS addition to bsd.prog.mk a [1997/04/09] bin/3241 times(3) returns only stime o [1997/04/09] bin/3242 incorrect prototype for initgroups o [1997/04/09] bin/3245 variable substitution "a=${a:=}" in /bin/ o [1997/04/10] ports/3248 ports update a port o [1997/04/10] bin/3249 user ppp does not provide a linkdown hook o [1997/04/10] ports/3250 ports New CAD port: xpns o [1997/04/10] bin/3251 xsysinfo stops refreshing and wastes CPU o [1997/04/10] kern/3253 scsiconf.c: make ZIP disks use optical dr o [1997/04/11] misc/3254 Can't connect to my ISP, because my ISP u o [1997/04/12] bin/3269 exec pppd -detach ... caused a kernel pan o [1997/04/12] docs/3270 command 'cvs init' missing from cvs(1) o [1997/04/13] conf/3272 $@ is deprecated I believe, so use ${.TAR o [1997/04/13] docs/3275 Some man pages has absolutely wrong date o [1997/04/13] ports/3277 ports tcp_wrapper port does not include NIS sup o [1997/04/13] ports/3279 ports new port of KON2 o [1997/04/14] kern/3281 errors when "rm -r"-ing in a mounted ext2 o [1997/04/14] kern/3282 ext2fs causes fs-unmount at shutdown/rebo o [1997/04/14] bin/3283 brandelf fails on files without write per o [1997/04/14] bin/3284 symorder(1): -t option doesn´t work at al o [1997/04/14] bin/3285 date option for pom(6) (phase of the moon o [1997/04/14] bin/3286 missing error checking in mount_mfs(8) ak o [1997/04/14] kern/3287 missing symbols in /usr/src/sys/i386/i386 o [1997/04/14] kern/3288 addition of a -f (force) option to "write o [1997/04/14] bin/3289 login(1) does not check /etc/skey.access o [1997/04/14] docs/3290 port option in lpd not valid o [1997/04/15] docs/3295 ATAPI CDROM not found during setup o [1997/04/15] ports/3296 ports New port(jp-GP-2.01jp):japanese/GP. o [1997/04/15] ports/3297 ports xforms-0.86 port no longer compiles o [1997/04/15] kern/3298 NFS privport handling is broken o [1997/04/15] kern/3299 /dev/console hangs o [1997/04/15] kern/3302 msdos FS bogus error o [1997/04/15] bin/3303 ftpio manpage o [1997/04/15] ports/3306 ports new port-package for ifmail o [1997/04/17] docs/3313 manpage bug in scsi(8) (cmd args are hex) o [1997/04/17] bin/3314 /etc/daily did not run on April 6, 1997 o [1997/04/17] kern/3317 odd TUBA_INCLUDE use in tcp_input.c o [1997/04/17] ports/3318 ports New port: jigsaw (Java-based HTTP server) o [1997/04/18] ports/3320 ports new and updated ports of korean, and upda o [1997/04/18] ports/3321 ports port update request for audio/splay-0.2 t o [1997/04/18] ports/3322 ports setlocale problem in lang/perl5 o [1997/04/18] ports/3330 ports hylafax port seems to be broken (partly) o [1997/04/19] ports/3331 ports new port request of korea/afterstep o [1997/04/19] ports/3332 ports new port request of korea/elm o [1997/04/19] ports/3333 ports new port request of korea/fvwm95 o [1997/04/19] ports/3334 ports new port request of korean/han o [1997/04/19] ports/3335 ports new port request of korean/hanemacs o [1997/04/19] ports/3336 ports new port request of korean/hanmutt o [1997/04/19] ports/3337 ports new port request of korean/helvis o [1997/04/19] ports/3338 ports new port request of korean/hfvwm2 o [1997/04/19] ports/3339 ports new port request of korean/hlatexpsfonts o [1997/04/19] ports/3340 ports new port(update) request of korean/hmconv o [1997/04/19] ports/3341 ports new port request of korean/hpscat o [1997/04/19] ports/3342 ports new port request of korean/linuxdoc-sgml o [1997/04/19] ports/3343 ports new port request of korean/nh2ps o [1997/04/19] ports/3344 ports new port request of korean/netscape3 o [1997/04/19] ports/3345 ports new port request of korean/nhpf o [1997/04/19] ports/3346 ports new port request of korean/pine o [1997/04/19] ports/3347 ports new port request of net/ztelnet o [1997/04/19] ports/3348 ports new port request of korean/nhppf o [1997/04/19] ports/3352 ports New port: cddbd o [1997/04/20] ports/3357 ports I make "pari-GP" ports o [1997/04/20] ports/3358 ports XFMail-1.1 has been released o [1997/04/20] bin/3360 su(1) cannot call MD4Init(3) from libskey o [1997/04/20] ports/3361 ports Enhancement patch for bsd.port.mk o [1997/04/20] ports/3362 ports Ports submission: XFrisk 0.99b4 488 problems total. From owner-freebsd-bugs Mon Apr 21 10:10:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA01167 for bugs-outgoing; Mon, 21 Apr 1997 10:10:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA01160; Mon, 21 Apr 1997 10:10:03 -0700 (PDT) Date: Mon, 21 Apr 1997 10:10:03 -0700 (PDT) Message-Id: <199704211710.KAA01160@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Jin Guojun[ITG]" Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Reply-To: "Jin Guojun[ITG]" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3365; it has been noted by GNATS. From: "Jin Guojun[ITG]" To: FreeBSD-gnats-submit@FreeBSD.ORG, pst@jnx.com Cc: Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Date: Mon, 21 Apr 1997 10:06:14 -0700 > Any FreeBSD machine where you'd like to stop someone who gains root from > mucking with your kernel. > > >Description: > > It's too easy for someone to gain root and add optional functionality to > your kernel (such as the snp pseudo-device, or perhaps BPF support...albiet > BPF is a bit harder). I am not clear how this can happen. One has to be root (having root access) to do LKM load. Some condition for one modifying the LKM object. So how easy for every one to gain root without root access right. If you put LKM object at a non-secure place, then it is not the LKM problem :-) -Jin From owner-freebsd-bugs Mon Apr 21 10:20:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA01655 for bugs-outgoing; Mon, 21 Apr 1997 10:20:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA01634; Mon, 21 Apr 1997 10:20:02 -0700 (PDT) Date: Mon, 21 Apr 1997 10:20:02 -0700 (PDT) Message-Id: <199704211720.KAA01634@freefall.freebsd.org> To: freebsd-bugs Cc: From: Stefan Esser Subject: Re: kern/3356: ncr0 (ncr815) hang Reply-To: Stefan Esser Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3356; it has been noted by GNATS. From: Stefan Esser To: plm@xs4all.nl Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/3356: ncr0 (ncr815) hang Date: Mon, 21 Apr 1997 19:19:47 +0200 On Apr 19, Peter Mutsaers wrote: > >Release: FreeBSD 3.0-CURRENT i386 > >Environment: > > ncr815 SCSI, just did a make world and installed a new kernel (cvsupped > on april 18th). > >Description: > > All processes accessing disk hang. After 10 seconds the following message > appeared: > ncr0: timeout ccb=f05c7600 (skip) > ncr0: timeout ccb=f05c7e00 (skip) > > >How-To-Repeat: > > Boot new kernel and generate some disk activity. Hmmm, sorry, but are you sure nothing else changed on your system ? There has been no change to the driver code between January 5th and April 20th, and that latter one did only change some casts for formal correctnes, but did most likely not result in any changes in the binary being created ... Does a kernel built from sources before April 18th continue to run reliably ? Did you try with a later kernel ? (I just built a new kernel, which doesn't seem to suffer from the problem you describe ...) Regards, STefan From owner-freebsd-bugs Mon Apr 21 10:30:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02122 for bugs-outgoing; Mon, 21 Apr 1997 10:30:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02116; Mon, 21 Apr 1997 10:30:01 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 10:30:01 -0700 (PDT) Resent-Message-Id: <199704211730.KAA02116@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, belkovic@albert.osu.cz Received: from albert.osu.cz (albert.osu.cz [193.84.224.12]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01874 for ; Mon, 21 Apr 1997 10:25:25 -0700 (PDT) Received: (from root@localhost) by albert.osu.cz (8.8.5/8.6.12) id TAA01470; Mon, 21 Apr 1997 19:26:51 +0200 (MET DST) Message-Id: <199704211726.TAA01470@albert.osu.cz> Date: Mon, 21 Apr 1997 19:26:51 +0200 (MET DST) From: belkovic@albert.osu.cz Reply-To: belkovic@albert.osu.cz To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3366: ipx stack or ep driver Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3366 >Category: kern >Synopsis: ipx stack or ep driver >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 10:30:00 PDT 1997 >Last-Modified: >Originator: Josef Belkovics >Organization: Ostrava University >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: HP LC Netserver CPU: Pentium (66.67-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping=7 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 31256576 (30524K bytes) eisa0: ahc0: at 0xbc00-0xbcff irq 15 ahc0: on eisa0 slot 11 ahc0: aic7770 >= Rev E, Twin Channel, A SCSI Id=7, B SCSI Id=7, 4 SCBs (ahc0:0:0): "HP 1.050 GB #A2 0180" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1001MB (2051460 512 byte sectors) (ahc0:1:0): "SEAGATE ST51080N 0943" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 1030MB (2109840 512 byte sectors) chip0 rev 3 on pci0:0 chip1 rev 3 on pci0:4:0 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 4 3C5x9 board(s) on ISA found at 0x300 0x310 0x320 0x330 ep0 at 0x300-0x30f irq 7 on isa ep0: aui/utp/bnc[*UTP*] address 00:20:af:e1:22:7e ep1 at 0x310-0x31f irq 10 on isa ep1: aui/utp/bnc[*AUI*] address 00:60:97:9a:88:ef ep2 at 0x320-0x32f irq 11 on isa ep2: aui/utp/bnc[*AUI*] address 00:60:97:9a:89:c3 ep3 at 0x330-0x33f irq 12 on isa ep3: aui/utp/bnc[*UTP*] address 00:a0:24:31:be:a1 npx0 on motherboard npx0: INT 16 interface >Description: Machine hangs without any messages on console or in syslog. Several times (1 - 5 x) in day. I can't ctrl+alt+del, but ctrl+alt+esc is ok. On the bottom of kgdb list are functions: ipx_error, ipx_forward, ipxintr (ipx_input.c), epread, ep_intr, epintr (if_ep.c). Please login into 'albert.osu.cz', login zzz, password zzz. Then gdb -k, symbol-file KERNEL, exec-file /var/crash/kernel.[1-3], core-file /var/crash/vmcore.[1-3]. File JPB is kernel config. >How-To-Repeat: 4 ep, ipx + IPXrouted, lan with 5 novell servers and WAIT. >Fix: ? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 10:50:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02936 for bugs-outgoing; Mon, 21 Apr 1997 10:50:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02930; Mon, 21 Apr 1997 10:50:02 -0700 (PDT) Date: Mon, 21 Apr 1997 10:50:02 -0700 (PDT) Message-Id: <199704211750.KAA02930@freefall.freebsd.org> To: freebsd-bugs Cc: From: Paul Traina Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Reply-To: Paul Traina Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3365; it has been noted by GNATS. From: Paul Traina To: "Jin Guojun[ITG]" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Date: Mon, 21 Apr 1997 10:39:53 -0700 From: "Jin Guojun[ITG]" Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them > Any FreeBSD machine where you'd like to stop someone who gains root from > mucking with your kernel. > > >Description: > > It's too easy for someone to gain root and add optional functionality to > your kernel (such as the snp pseudo-device, or perhaps BPF support...albiet > BPF is a bit harder). I am not clear how this can happen. One has to be root (having root access) to do LKM load. Some condition for one modifying the LKM object. So how easy for every one to gain root without root access right. If you put LKM object at a non-secure place, then it is not the LKM problem Just because someone's root doesn't mean that you want them to have the ability to modify your OS. That's the whole point of the schg flag, right now, LKM's are a hole in the securitylevel protection model. From owner-freebsd-bugs Mon Apr 21 11:10:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03958 for bugs-outgoing; Mon, 21 Apr 1997 11:10:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03942; Mon, 21 Apr 1997 11:10:01 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 11:10:01 -0700 (PDT) Resent-Message-Id: <199704211810.LAA03942@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, jc@irbs.com Received: from irbs.irbs.com (jc@irbs.irbs.com [199.182.75.129]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03588 for ; Mon, 21 Apr 1997 11:02:08 -0700 (PDT) Received: (from jc@localhost) by irbs.irbs.com (8.8.5/8.8.5) id OAA10624; Mon, 21 Apr 1997 14:02:04 -0400 (EDT) Message-Id: <199704211802.OAA10624@irbs.irbs.com> Date: Mon, 21 Apr 1997 14:02:04 -0400 (EDT) From: John Capo Reply-To: jc@irbs.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3367: 2.1.7.1 panic with route mask == 0 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3367 >Category: kern >Synopsis: 2.1.7.1 panic with route mask == 0 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 11:10:00 PDT 1997 >Last-Modified: >Originator: John Capo >Organization: IRBS Engineering >Release: FreeBSD 2.1.7.1-RELEASE i386 >Environment: 2.[01] kernel >Description: I managed to get a bogus route added via /etc/ppp/ppp.conf that caused a panic due to the mask associated with the route being 0. >How-To-Repeat: It's been a while and I didn't make notes at the time. >Fix: Same fix is in 2.2. Index: route.c =================================================================== RCS file: /usr/cvs/src/sys/net/route.c,v retrieving revision 1.23.4.3 diff -u -r1.23.4.3 route.c --- route.c 1996/06/08 02:02:03 1.23.4.3 +++ route.c 1997/03/16 02:00:25 @@ -511,7 +511,7 @@ * it doesn't fire when we call it there because the node * hasn't been added to the tree yet. */ - if (!(rt->rt_flags & RTF_HOST)) { + if (!(rt->rt_flags & RTF_HOST) && rt_mask(rt) != 0) { struct rtfc_arg arg; arg.rnh = rnh; arg.rt0 = rt; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 11:40:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05840 for bugs-outgoing; Mon, 21 Apr 1997 11:40:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05828; Mon, 21 Apr 1997 11:40:02 -0700 (PDT) Date: Mon, 21 Apr 1997 11:40:02 -0700 (PDT) Message-Id: <199704211840.LAA05828@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3365; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@freebsd.org, pst@jnx.com Cc: Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Date: Tue, 22 Apr 1997 04:30:38 +1000 >I'd like to request two changes: > >(a) if securitylevel > N then LKM loading is disabled in the kernel > (N = the same level that disables changing of the schg flag) This is standard in all versions later than 2.1.0 (N = 0). Bruce From owner-freebsd-bugs Mon Apr 21 11:40:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05858 for bugs-outgoing; Mon, 21 Apr 1997 11:40:10 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05844; Mon, 21 Apr 1997 11:40:06 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 11:40:06 -0700 (PDT) Resent-Message-Id: <199704211840.LAA05844@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, grady@xcf.berkeley.edu Received: from cafeserver.cafenet.net (cafeserver.cafenet.net [204.177.0.40]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA05659 for ; Mon, 21 Apr 1997 11:36:44 -0700 (PDT) Received: from = ([157.151.128.3]) by cafeserver.cafenet.net (8.6.12/8.6.12) with ESMTP id LAA24222 for ; Mon, 21 Apr 1997 11:44:12 -0700 Received: (from root@localhost) by semprini.ip.holonet.net (8.8.5/8.6.9) id LAA02086; Mon, 21 Apr 1997 11:18:43 -0700 (PDT) Message-Id: <199704211818.LAA02086@semprini.ip.holonet.net> Date: Mon, 21 Apr 1997 11:18:43 -0700 (PDT) From: grady@xcf.berkeley.edu Reply-To: grady@xcf.berkeley.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/3368: sysinstall upgrade should confirm before newfs Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3368 >Category: misc >Synopsis: sysinstall upgrade should confirm before newfs >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 11:40:04 PDT 1997 >Last-Modified: >Originator: Steven Grady >Organization: >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: 2.2.1 installation floppy: boot.flp >Description: When doing an upgrade (or perhaps always), sysinstall should ask for confirmation before doing a newfs on any of the filesystems. I know that it says beforehand to be careful of doing a newfs, and indeed I knew very well that I didn't want to newfs, but somehow (I assume because I accidentally hit "t" when setting my /usr mointpoint) I managed to newfs my /usr anyway. Extra confirmations are annoying, but since a newfs is not something you're likely to do much, I think the check is worth the annoyance. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 12:20:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA08088 for bugs-outgoing; Mon, 21 Apr 1997 12:20:11 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA08048; Mon, 21 Apr 1997 12:20:06 -0700 (PDT) Date: Mon, 21 Apr 1997 12:20:06 -0700 (PDT) Message-Id: <199704211920.MAA08048@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Helmut F. Wirth" Subject: Re: i386/3300: Adaptec 2940U Problems Reply-To: "Helmut F. Wirth" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR i386/3300; it has been noted by GNATS. From: "Helmut F. Wirth" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: i386/3300: Adaptec 2940U Problems Date: Thu, 17 Apr 1997 20:50:20 +0200 Justin T. Gibbs wrote: > > There is a known firmware problem with the Quantum Atlas drive that is > tickled by the, now much faster, aic7xxx driver. You should be running > L915 firmware on sd2. You may also be able to update your sd0 drive > to L915, but since the firmware is so different on that drive, I'm not > sure. You can pick up the latest firmware from: > > ftp://ftp.quantum.com/Firmware/Atlas I/ > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== Hello, I did the firmware upgrade for sd2, that is the newer disk which had firmware release L912. It did change nothing ! I submitted a followup to freebsd-gnats. I don't think I can do / need an update for sd0, the older disk. I think only firmware L912 had problems. But I faxed a question concerning the older disk to Quantum. No answer yet. Anyway, thanks for your hints ! -- Helmut F. Wirth Email: hfwirth@ping.at From owner-freebsd-bugs Mon Apr 21 12:50:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA09963 for bugs-outgoing; Mon, 21 Apr 1997 12:50:49 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09953 for ; Mon, 21 Apr 1997 12:50:44 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20155; Mon, 21 Apr 1997 15:50:05 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 21 Apr 1997 15:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id OAA27131; Mon, 21 Apr 1997 14:53:27 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id OAA02323; Mon, 21 Apr 1997 14:59:53 -0400 (EDT) Date: Mon, 21 Apr 1997 14:59:53 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704211859.OAA02323@lakes.water.net> To: ponds!nlsystems.com!dfr, ponds!lakes.water.net!rivers Subject: Re: kern/3304: NFS V2 readdir hangs Cc: ponds!freefall.cdrom.com!freebsd-bugs Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > What appears to be happening is that numb is making a 4096byte sized > readdir request for the first block of the large directory. You can see > this in the trace as request id b6cff051 (btw. you may find it useful to > grep the log for nfs to separate the wood from the trees; next time we > should add 'port nfs' to the tcpdump command). The reply is sent but for > some reason it never makes it into sorecieve. > > You can see that numb retries the request with the same xid several times > but never receives the reply. My guess is that something between numb and > sundog has corrupted the packet and it is failing the checksum in > udp_input. What we need to do is find out how far up the protocol stack > the packet goes. I suggest adding printfs to udp_input and ip_input where > they drop packets with bad checksums (line 154 in udp_usrreq.c). You > should also be able to see it with 'netstat -p udp' and 'netstat -p ip'. Here's the output of those netstat commands: Script started on Mon Apr 21 14:11:18 1997 # netstat -p udp udp: 129 datagrams received 0 with incomplete header 0 with bad data length field 0 with bad checksum 0 dropped due to no socket 13 broadcast/multicast datagrams dropped due to no socket 5 dropped due to full socket buffers 0 not for hashed pcb 111 delivered 116 datagrams output # netstat -p ip ip: 180 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with data size < data length 0 with header length < data size 0 with data length < header length 0 with bad options 0 with incorrect version number 15 fragments received 0 fragments dropped (dup or out of space) 0 fragments dropped after timeout 5 packets reassembled ok 130 packets for this host 0 packets for unknown/unsupported protocol 0 packets forwarded 40 packets not forwardable 0 redirects sent 116 packets sent from this host 0 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented # exit Script done on Mon Apr 21 14:11:25 1997 No checksum problems - but I do notice the "5 dropped due to socket full buffers" line... could that be the reason?... > > You might also try this (untested) hack which should limit readdirs to > smaller bites: > > Index: nfs_vfsops.c > =================================================================== > RCS file: /home/smp/sys/nfs/nfs_vfsops.c,v > retrieving revision 1.1.1.5 > diff -u -r1.1.1.5 nfs_vfsops.c > --- nfs_vfsops.c 1997/04/18 07:09:39 1.1.1.5 > +++ nfs_vfsops.c 1997/04/21 17:19:58 > @@ -748,6 +748,7 @@ > } > if (nmp->nm_readdirsize > maxio) > nmp->nm_readdirsize = maxio; > + nmp->nm_readdirsize = 1024; /* XXX */ > > if ((argp->flags & NFSMNT_MAXGRPS) && argp->maxgrouplist >= 0 && > argp->maxgrouplist <= NFS_MAXGRPS) > Yes! - this particular change does work-around the problem. I'm able to run my "ls -lR" and have it complete successfully [although, there are some strange 'lags' every now and then...] it does work. I've been running it continuously for a few minutes now; no hangs... Now - a good question, which you asked, is why are those packets getting blocked? Also, another question I have is why did this work with 2.1.5 - did it always have a lower readdirsize; or is another problem in 2.2.1 simply masked by lowering the readdirsize? I'm happy to investigate this further - and *overjoyed* that NFS seems to be working for me... let me know what I can do at this end. - Thanks! - - Dave Rivers - From owner-freebsd-bugs Mon Apr 21 15:17:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA17562 for bugs-outgoing; Mon, 21 Apr 1997 15:17:45 -0700 (PDT) Received: from smtp.WPI.EDU (root@smtp.WPI.EDU [130.215.24.62]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17557 for ; Mon, 21 Apr 1997 15:17:42 -0700 (PDT) Received: from bert.WPI.EDU (root@bert.WPI.EDU [130.215.24.121]) by smtp.WPI.EDU (8.8.6.Beta0/8.8.6.Beta0) with ESMTP id SAA28826 for ; Mon, 21 Apr 1997 18:17:38 -0400 Received: from localhost (mcworks@localhost [127.0.0.1]) by bert.WPI.EDU (8.8.6.Beta0/8.8.6.Beta0) with SMTP id SAA08846 for ; Mon, 21 Apr 1997 18:17:38 -0400 (EDT) Date: Mon, 21 Apr 1997 18:17:38 -0400 (EDT) From: Michael McElhaney To: freebsd-bugs@freebsd.org Subject: install Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a P-133, 2.1G IDE hard drive w/ accompanying toshiba 8x IDE cdrom drive, and am running ms-dos6&win95 on a first 1G slice. The second slice is formatted for fbsd and I have been attempting to reinstall the freebsd os after an unfortunate formatting accident from my dos side, but am getting writing errors no matter how simple the install (even on the bins). I have a wcreek cd of FreeBSD v2.1.1, from the fall, which I had previously installed onto my drive using this method of loading from the 1st slice, but as that is not working I am in need of other options. In particular is there a functional atapi-cd boot.flp that could be used so that the installer would recognize my cdrom after boot so as to load from cd? Any thoughts would of use. <<<<<<<--------------->>>>>>> Michael Fitzpatrick McElhaney ============================= WPI Box 2829 phone:ext6394 100 Institute Road, Worcester Massachusetts, 0 1 6 0 9 <<<<<<<--------------->>>>>>> From owner-freebsd-bugs Mon Apr 21 17:37:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01462 for bugs-outgoing; Mon, 21 Apr 1997 17:37:21 -0700 (PDT) Received: (from pst@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01443; Mon, 21 Apr 1997 17:37:18 -0700 (PDT) Date: Mon, 21 Apr 1997 17:37:18 -0700 (PDT) From: Paul Traina Message-Id: <199704220037.RAA01443@freefall.freebsd.org> To: pst@jnx.com, pst, freebsd-bugs Subject: Re: kern/3365 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: LKMs are a security hole -- need way to disable them State-Changed-From-To: open-closed State-Changed-By: pst State-Changed-When: Mon Apr 21 17:36:41 PDT 1997 State-Changed-Why: This is standard in all versions later than 2.1.0 (N = 0). From owner-freebsd-bugs Mon Apr 21 17:40:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01665 for bugs-outgoing; Mon, 21 Apr 1997 17:40:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01638; Mon, 21 Apr 1997 17:40:01 -0700 (PDT) Resent-Date: Mon, 21 Apr 1997 17:40:01 -0700 (PDT) Resent-Message-Id: <199704220040.RAA01638@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, skynyrd@opus.cts.cwu.edu Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00843 for ; Mon, 21 Apr 1997 17:30:00 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id RAA24334 for ; Mon, 21 Apr 1997 17:29:56 -0700 (PDT) Received: (from skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) id RAA26136; Mon, 21 Apr 1997 17:29:54 -0700 (PDT) Message-Id: <199704220029.RAA26136@opus.cts.cwu.edu> Date: Mon, 21 Apr 1997 17:29:54 -0700 (PDT) From: Chris Timmons Reply-To: skynyrd@opus.cts.cwu.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/3371: LBL tcpdump 3.3 -merge submission Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Note: There was a bad value `sw-bug|change-request' for the field `>Class:'. It was set to the default value of `sw-bug'. >Number: 3371 >Category: bin >Synopsis: LBL tcpdump 3.3 -merge submission >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 21 17:40:00 PDT 1997 >Last-Modified: >Originator: Chris Timmons >Organization: Central Washington University >Release: FreeBSD 3.0-CURRENT i386 >Environment: 3.0-CURRENT with recently repaired libpcap (see i386/3353.) >Description: Pre lbl-3.3 tcpdump (like the one in -current) mistakenly believes that the small udp packet is actually a truncated one because of a logic bug in print-udp.c (which probably produced correct results for the wrong reasons on interfaces which padded ethernet packets to ETHERMIN before the bpf_tap.) Of course nowadays we have more advanced hw that pads for us so the driver doesn't have to, and very short packets get shoved down the bpf_tap pipe to bring these bugs to light. But anyways: >How-To-Repeat: To see the bug, use netcat to query a udp time server, such as the one that inetd can run, and monitor the transaction from the same machine using tcpdump: nc -u -z -w 1 pahtoh time 15:54:37.024031 [|udp] 15:54:37.025030 pahtoh.cwu.edu.time > swash.cts.cwu.edu.1267: udp 4 Merged -current+lbl-3.3 correctly processes this: 15:57:39.021435 swash.cts.cwu.edu.1271 > pahtoh.cwu.edu.time: udp 1 15:57:39.022410 pahtoh.cwu.edu.time > swash.cts.cwu.edu.1271: udp 4 >Fix: tcpdump v3.3 from ftp.ee.lbl.gov fixes the problem. Since we are a release behind, I have done nearly all of the work necessary to merge this into -current and created a kit which I have uploaded as ftp://ftp.freebsd.org/pub/FreeBSD/incoming/tcpdump-to-lbl33-merge.tar.gz MD5 (tcpdump-to-lbl33-merge.tar.gz) = 7fa45cf54d5ce868d21bfeaecde55b3e The kit consists of a buildable reference tree that resulted from my local CVS merge (into a copy of the FreeBSD tree) of lbl-3.3 tcpdump, and a patch kit to address merge conflicts (a couple of -Wall patches are included separately.) A complete narrative of length war and peace is included which explains how this would be useful to someone really merging this into our tree. Normally the corresponding release of libpcap would be merged at the same time - I can do that, too, but would like some feedback on whether or not this kind of submission is useful or appropriate. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Apr 21 17:40:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01679 for bugs-outgoing; Mon, 21 Apr 1997 17:40:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01658; Mon, 21 Apr 1997 17:40:03 -0700 (PDT) Date: Mon, 21 Apr 1997 17:40:03 -0700 (PDT) Message-Id: <199704220040.RAA01658@freefall.freebsd.org> To: freebsd-bugs Cc: From: Paul Traina Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Reply-To: Paul Traina Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3365; it has been noted by GNATS. From: Paul Traina To: Bruce Evans Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them Date: Mon, 21 Apr 1997 17:37:25 -0700 Cool, thanks. Will close. From: Bruce Evans Subject: Re: kern/3365: LKMs are a security hole -- need way to disable them >I'd like to request two changes: > >(a) if securitylevel > N then LKM loading is disabled in the kernel > (N = the same level that disables changing of the schg flag) This is standard in all versions later than 2.1.0 (N = 0). Bruce From owner-freebsd-bugs Mon Apr 21 18:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA03939 for bugs-outgoing; Mon, 21 Apr 1997 18:30:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA03925; Mon, 21 Apr 1997 18:30:01 -0700 (PDT) Date: Mon, 21 Apr 1997 18:30:01 -0700 (PDT) Message-Id: <199704220130.SAA03925@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bill Fenner Subject: Re: bin/3371: LBL tcpdump 3.3 -merge submission Reply-To: Bill Fenner Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3371; it has been noted by GNATS. From: Bill Fenner To: FreeBSD-gnats-submit@freebsd.org, skynyrd@opus.cts.cwu.edu Cc: pst@jnx.com Subject: Re: bin/3371: LBL tcpdump 3.3 -merge submission Date: Mon, 21 Apr 1997 18:27:16 PDT I'll volunteer to merge tcpdump 3.3 and libpcap 0.3, unless Paul has more time than I think he has and wants to do it. Bill From owner-freebsd-bugs Mon Apr 21 20:05:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA08560 for bugs-outgoing; Mon, 21 Apr 1997 20:05:56 -0700 (PDT) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA08540; Mon, 21 Apr 1997 20:05:53 -0700 (PDT) Date: Mon, 21 Apr 1997 20:05:53 -0700 (PDT) From: Mike Pritchard Message-Id: <199704220305.UAA08540@freefall.freebsd.org> To: mpp, freebsd-bugs, mpp Subject: Re: docs/3275 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: Some man pages has absolutely wrong date Responsible-Changed-From-To: freebsd-bugs->mpp Responsible-Changed-By: mpp Responsible-Changed-When: Mon Apr 21 20:05:28 PDT 1997 Responsible-Changed-Why: man page problem. From owner-freebsd-bugs Mon Apr 21 21:40:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA12746 for bugs-outgoing; Mon, 21 Apr 1997 21:40:01 -0700 (PDT) Received: from absinthe.i3inc.com (Absinthe.stonos.washington.dc.us [206.27.237.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA12716; Mon, 21 Apr 1997 21:39:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by absinthe.i3inc.com (8.7.2/8.7.2) with SMTP id AAA08665; Tue, 22 Apr 1997 00:37:56 -0400 (EDT) Message-Id: <199704220437.AAA08665@absinthe.i3inc.com> X-Authentication-Warning: absinthe.i3inc.com: Host localhost [127.0.0.1] didn't use HELO protocol To: chris@chris.netmonger.net Cc: freebsd-questions@freebsd.org, bugs@freebsd.org Subject: Re: dialup hangs after Password: prompt, timeout after 300 seconds In-Reply-To: Your message of "Thu, 17 Apr 1997 10:29:02 -0400 (EDT)" References: <199704171429.KAA10535@chris.netmonger.net> X-Mailer: Mew version 1.03 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 22 Apr 1997 00:37:55 -0400 From: Chris Shenton Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [I got login: and password: prompt dialing into my FreeBSD modem sitting on a getty, but it hung at the password: prompt and connection timed out after 300 seconds; telnet was fine, so the account was OK] On Thu, 17 Apr 1997 10:29:02 -0400 (EDT) Christopher Masto wrote: chris> What are you using to dial? Any chance it's tip on another unix box? chris> I have seen people try to use it and have exactly this problem. I chris> think it is either a CR/LF issue, or something to do with turning off chris> the echo. Anyway, I have gotten around it by using cu (cu -l chris> /dev/modem -s 115200). User PPP's term mode seems to work also. I'll be danged! That was it. I was using tip from a FreeBSD-2.1.7 box to connect to the modem/getty on a 2.2.1 box. I was able get in fine with a lowly WinDoze terminal emulation, telling the modem to dial with the usual ATDT stuff. Sounds like some problem with tip? Thanks! [cc'd to Bugs] From owner-freebsd-bugs Mon Apr 21 21:50:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13311 for bugs-outgoing; Mon, 21 Apr 1997 21:50:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13299; Mon, 21 Apr 1997 21:50:02 -0700 (PDT) Date: Mon, 21 Apr 1997 21:50:02 -0700 (PDT) Message-Id: <199704220450.VAA13299@freefall.freebsd.org> To: freebsd-bugs Cc: From: Paul Traina Subject: Re: bin/3371: LBL tcpdump 3.3 -merge submission Reply-To: Paul Traina Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3371; it has been noted by GNATS. From: Paul Traina To: Bill Fenner Cc: FreeBSD-gnats-submit@freebsd.org, skynyrd@opus.cts.cwu.edu Subject: Re: bin/3371: LBL tcpdump 3.3 -merge submission Date: Mon, 21 Apr 1997 21:48:58 -0700 Nope, please do. From: Bill Fenner Subject: Re: bin/3371: LBL tcpdump 3.3 -merge submission I'll volunteer to merge tcpdump 3.3 and libpcap 0.3, unless Paul has more time than I think he has and wants to do it. Bill From owner-freebsd-bugs Mon Apr 21 21:50:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13367 for bugs-outgoing; Mon, 21 Apr 1997 21:50:45 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA13362 for ; Mon, 21 Apr 1997 21:50:42 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA23489; Tue, 22 Apr 1997 00:50:09 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 22 Apr 1997 00:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id WAA08671; Mon, 21 Apr 1997 22:44:55 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id WAA02885; Mon, 21 Apr 1997 22:51:23 -0400 (EDT) Date: Mon, 21 Apr 1997 22:51:23 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704220251.WAA02885@lakes.water.net> To: ponds!nlsystems.com!dfr, ponds!lakes.water.net!rivers Subject: Re: kern/3304: NFS V2 readdir hangs Cc: ponds!freefall.cdrom.com!freebsd-bugs Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > udp: > > 5 dropped due to full socket buffers > >... > > > > ip: > > 5 packets reassembled ok > >... > > > > Yes! - this particular change does work-around the problem. I'm > > able to run my "ls -lR" and have it complete successfully [although, > > there are some strange 'lags' every now and then...] it does work. > > I've been running it continuously for a few minutes now; no hangs... > > Well that is a start. I need to fix up mount_nfs so that you can frob > with the directory read size in these cases. > > > > > Now - a good question, which you asked, is why are those packets > > getting blocked? > > > > Also, another question I have is why did this work with 2.1.5 - did > > it always have a lower readdirsize; or is another problem in 2.2.1 simply > > masked by lowering the readdirsize? > > The readdir code at this level was quite a bit different. I don't know > whether it would have read smaller blocks but it would have certainly read > different ones at different offsets. > > > > > I'm happy to investigate this further - and *overjoyed* that NFS > > seems to be working for me... let me know what I can do at this end. > > I think the most promising candidate is the 'full socket buffers' message. > Could you see if that goes up consistently when you prompt the system to > hang. The match between that and the reassembly number seems to show that > these are large packets. We'll do! > > I am going to bed now. Good luck in your detective work! Thanks again for your help! - Dave Rivers - > > -- > Doug Rabson Mail: dfr@nlsystems.com From owner-freebsd-bugs Mon Apr 21 21:55:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13637 for bugs-outgoing; Mon, 21 Apr 1997 21:55:38 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13628 for ; Mon, 21 Apr 1997 21:55:31 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id VAA00384; Mon, 21 Apr 1997 21:55:29 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 21 Apr 1997 18:49:46 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-bugs@freebsd.org, freebsd-scsi2freebsd.org@sendero.i-connect.net Subject: Scsi_attachdevs PANICs... Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Trying to allocate, somewhere in the neighborhood of 60 drives, I am getting a panic in said routine (scsi/scsiconf.c, line 797). I tried to change the memory type form M_TEMP to M_DEVBUF to no avail. We have a very real need for 6 SCSI-wide busses, each with 15 disks. Maybe more next month. Really! Any clue as to how to make this work will be greatly appreciated. Simon BTW, I am sending theseto the list, not to the responsible parties on the innocent belief that these are problems of general interest :-) Simon mewhere in the neighborhood of 60 drives, I am getting a panic in said routine (scsi/scsiconf.c, line 797). I tried to change the memory type form M_TEMP to M_DEVBUF to no avail. We have a very real need for 6 SCSI-wide busses From owner-freebsd-bugs Mon Apr 21 21:55:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13649 for bugs-outgoing; Mon, 21 Apr 1997 21:55:39 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13634 for ; Mon, 21 Apr 1997 21:55:36 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id VAA00361; Mon, 21 Apr 1997 21:55:27 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199704211031.DAA03600@root.com> Date: Mon, 21 Apr 1997 18:12:04 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: dg@root.com Subject: Re: Mystery of the X11 Panic... Cc: freebsd-bugs@freebsd.org, Bruce Evans , David Greenman Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 21-Apr-97 you wrote: > >[cc list trimmed to remove -hackers] > > > >>Fatal trap 12 - Page fault while in kernel mode. in virtual address > >>0xf71e0014. Tracing back shows that bash (?!) was the culprit, causing > it > >>after calling _Xsyscall -> _syscall -> _vm_open -> _spec_open. > >> > >>Things go south at _spec_open + 0x6e, complaining about cmpl > $0,0(%eax). > > > >This means that cdevsw[maj]->d_open is bad (probably null) although > >cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. > >Driver LKM's tend to cause this problem if they are unloaded. Bash > >may trigger the problem because it does an opendir() on device files > >(but I thought I fixed this by not opening device files in opendir()). > >I wouldn't use LKMs for anything important. > > ...or it could be caused by the bug in kern_exec.c, which could have > mangled adjacent buffers or possibly random kernel memory. It seems > to involve bash and the kern_exec.c bug was triggered when running small > shell scripts. This is very probable, as my xfm configuration spawns many one-two lines scripts. So does xfm itself when it launches applications. It all fits. Simon BTW, assuming this is the bug, what is the fix? It is a nasty one (panics and all :-) Simon From owner-freebsd-bugs Mon Apr 21 21:55:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13678 for bugs-outgoing; Mon, 21 Apr 1997 21:55:46 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13666 for ; Mon, 21 Apr 1997 21:55:43 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id VAA00363; Mon, 21 Apr 1997 21:55:28 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970421152036.AM09487@uriah.heep.sax.de> Date: Mon, 21 Apr 1997 18:20:48 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: (Joerg Wunsch) Subject: Re: Mystery of the X11 Panic... Cc: freebsd-bugs@freebsd.org, (J Wunsch) Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi J Wunsch; On 21-Apr-97 you wrote: > As David Greenman wrote: > > > >This means that cdevsw[maj]->d_open is bad (probably null) although > > >cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. > > Nope, Bruce: > > if ( (cdevsw[maj] == NULL) || (cdevsw[maj]->d_open == > NULL)) > ^^^^^^^^^^^^^^^^^^^ > return ENXIO; > > This case is tested, and it's actually this test itself that causes > the panic. > > > ...or it could be caused by the bug in kern_exec.c, which could have > > mangled adjacent buffers or possibly random kernel memory. It seems > > to involve bash and the kern_exec.c bug was triggered when running > small > > shell scripts. > > This seems more reasonable after reading that piece of code. > > Simon didn't tell us the faulting VA, but i bet it's not right NULL. No, i did not, but AFAICR it was not null. These are easier to spot. Even i can track these down ;-) Simon From owner-freebsd-bugs Tue Apr 22 05:51:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA13213 for bugs-outgoing; Tue, 22 Apr 1997 05:51:44 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13185; Tue, 22 Apr 1997 05:51:23 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id WAA29849; Tue, 22 Apr 1997 22:51:01 +1000 (EST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199704220437.AAA08665@absinthe.i3inc.com> Date: Tue, 22 Apr 1997 22:45:12 +1000 (EST) Organization: Unique Computing From: David Nugent To: Chris Shenton Subject: Re: dialup hangs after Password: prompt, timeout after 300 secon Cc: bugs@freebsd.org, freebsd-questions@freebsd.org, chris@chris.netmonger.net Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 22-Apr-97 Chris Shenton wrote: > [I got login: and password: prompt dialing into my FreeBSD modem sitting > on a getty, but it hung at the password: prompt and connection timed > out after 300 seconds; telnet was fine, so the account was OK] ~ I'll be danged! That was it. I was using tip from a FreeBSD-2.1.7 box > to connect to the modem/getty on a 2.2.1 box. > > I was able get in fine with a lowly WinDoze terminal emulation, > telling the modem to dial with the usual ATDT stuff. > > Sounds like some problem with tip? No, just its default configuration. Unless you've explicitly set parity to none, tip uses even parity. getty handles this situation, but login does not. I've been confused by this situation myself. IMHO, tip should default to 8N1. There's rarely any need these days to use 7 bit parity settings, especially by default, and especially if login does not handle it intelligenty by detecting use of parity and setting termios accordingly (which it could to at a login: prompt, but not Password: unfortunately). Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-bugs Tue Apr 22 06:40:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA15201 for bugs-outgoing; Tue, 22 Apr 1997 06:40:23 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15191 for ; Tue, 22 Apr 1997 06:40:19 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id OAA00376; Tue, 22 Apr 1997 14:39:47 +0100 (BST) Date: Tue, 22 Apr 1997 14:39:46 +0100 (BST) From: Doug Rabson To: Thomas David Rivers cc: freebsd-bugs@freebsd.org Subject: Re: kern/3304: NFS V2 readdir hangs In-Reply-To: <199704220251.WAA02885@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Apr 1997, Thomas David Rivers wrote: > > I think the most promising candidate is the 'full socket buffers' message. > > Could you see if that goes up consistently when you prompt the system to > > hang. The match between that and the reassembly number seems to show that > > these are large packets. > > We'll do! I have been looking at the code again today and it seems to me that the client is not reserving enough space in its sockets when it initialises the mount. Your nasty directory appears to generate a reply packet which is too large for the client to recieve. I added some code to use a slightly less restrictive buffer size in the NFS client. I also tidied up the code which sets the size for readdir requests to make it possible to set it to less than 4k and to be more compatible with 2.1.x. Could you try this patch, both with and without a -r1024 argument to mount_nfs. Index: nfs_socket.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v retrieving revision 1.22 diff -u -r1.22 nfs_socket.c --- nfs_socket.c 1997/03/22 06:53:08 1.22 +++ nfs_socket.c 1997/04/22 13:31:23 @@ -270,8 +270,8 @@ so->so_snd.sb_timeo = 0; } if (nmp->nm_sotype == SOCK_DGRAM) { - sndreserve = nmp->nm_wsize + NFS_MAXPKTHDR; - rcvreserve = nmp->nm_rsize + NFS_MAXPKTHDR; + sndreserve = (nmp->nm_wsize + NFS_MAXPKTHDR) * 2; + rcvreserve = (nmp->nm_rsize + NFS_MAXPKTHDR) * 2; } else if (nmp->nm_sotype == SOCK_SEQPACKET) { sndreserve = (nmp->nm_wsize + NFS_MAXPKTHDR) * 2; rcvreserve = (nmp->nm_rsize + NFS_MAXPKTHDR) * 2; Index: nfs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vfsops.c,v retrieving revision 1.37 diff -u -r1.37 nfs_vfsops.c --- nfs_vfsops.c 1997/04/04 17:49:30 1.37 +++ nfs_vfsops.c 1997/04/22 13:04:47 @@ -302,12 +302,9 @@ } pref = fxdr_unsigned(u_long, fsp->fs_dtpref); if (pref < nmp->nm_readdirsize) - nmp->nm_readdirsize = (pref + NFS_DIRBLKSIZ - 1) & - ~(NFS_DIRBLKSIZ - 1); + nmp->nm_readdirsize = pref; if (max < nmp->nm_readdirsize) { - nmp->nm_readdirsize = max & ~(NFS_DIRBLKSIZ - 1); - if (nmp->nm_readdirsize == 0) - nmp->nm_readdirsize = max; + nmp->nm_readdirsize = max; } nmp->nm_flag |= NFSMNT_GOTFSINFO; } @@ -741,13 +738,11 @@ if ((argp->flags & NFSMNT_READDIRSIZE) && argp->readdirsize > 0) { nmp->nm_readdirsize = argp->readdirsize; - /* Round down to multiple of blocksize */ - nmp->nm_readdirsize &= ~(NFS_DIRBLKSIZ - 1); - if (nmp->nm_readdirsize < NFS_DIRBLKSIZ) - nmp->nm_readdirsize = NFS_DIRBLKSIZ; } if (nmp->nm_readdirsize > maxio) nmp->nm_readdirsize = maxio; + if (nmp->nm_readdirsize > nmp->nm_rsize) + nmp->nm_readdirsize = nmp->nm_rsize; if ((argp->flags & NFSMNT_MAXGRPS) && argp->maxgrouplist >= 0 && argp->maxgrouplist <= NFS_MAXGRPS) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-bugs Tue Apr 22 09:48:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24119 for bugs-outgoing; Tue, 22 Apr 1997 09:48:14 -0700 (PDT) Received: (from fenner@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24084; Tue, 22 Apr 1997 09:48:01 -0700 (PDT) Date: Tue, 22 Apr 1997 09:48:01 -0700 (PDT) From: Bill Fenner Message-Id: <199704221648.JAA24084@hub.freebsd.org> To: fenner, freebsd-bugs, fenner Subject: Re: bin/3371 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: LBL tcpdump 3.3 -merge submission Responsible-Changed-From-To: freebsd-bugs->fenner Responsible-Changed-By: fenner Responsible-Changed-When: Tue Apr 22 09:47:30 PDT 1997 Responsible-Changed-Why: fenner will merge tcpdump 3.3 and libpcap 0.3 From owner-freebsd-bugs Tue Apr 22 09:50:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24205 for bugs-outgoing; Tue, 22 Apr 1997 09:50:50 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA24200 for ; Tue, 22 Apr 1997 09:50:46 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA17751; Tue, 22 Apr 1997 12:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 22 Apr 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id LAA00417; Tue, 22 Apr 1997 11:36:13 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id LAA04318; Tue, 22 Apr 1997 11:42:43 -0400 (EDT) Date: Tue, 22 Apr 1997 11:42:43 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704221542.LAA04318@lakes.water.net> To: ponds!nlsystems.com!dfr, ponds!lakes.water.net!rivers Subject: Re: kern/3304: NFS V2 readdir hangs Cc: ponds!freebsd.org!freebsd-bugs Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 21 Apr 1997, Thomas David Rivers wrote: > > > > I think the most promising candidate is the 'full socket buffers' message. > > > Could you see if that goes up consistently when you prompt the system to > > > hang. The match between that and the reassembly number seems to show that > > > these are large packets. > > > > We'll do! > > I have been looking at the code again today and it seems to me that the > client is not reserving enough space in its sockets when it initialises > the mount. Your nasty directory appears to generate a reply packet which > is too large for the client to recieve. > > I added some code to use a slightly less restrictive buffer size in the > NFS client. I also tidied up the code which sets the size for readdir > requests to make it possible to set it to less than 4k and to be more > compatible with 2.1.x. Could you try this patch, both with and without a > -r1024 argument to mount_nfs. I tried it out with a -r1024 (and -w1024, which shouldn't matter) and without any options except -t60... It worked wonderfully!!! I'd say commit that patch!!! (thanks again) Now, I see you set the rcvreserve to "(nm_rsize + NFS_MAXPKTHDR) * 2" which, for me was enough - but can we determine just what is 'really' enough, or is this just a better guess? [Is it guaranteed to be enough because you bump the readdirsize down to the rsize is rsize is the lesser of the two?] - Dave Rivers - > > Index: nfs_socket.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_socket.c,v > retrieving revision 1.22 > diff -u -r1.22 nfs_socket.c > --- nfs_socket.c 1997/03/22 06:53:08 1.22 > +++ nfs_socket.c 1997/04/22 13:31:23 > @@ -270,8 +270,8 @@ > so->so_snd.sb_timeo = 0; > } > if (nmp->nm_sotype == SOCK_DGRAM) { > - sndreserve = nmp->nm_wsize + NFS_MAXPKTHDR; > - rcvreserve = nmp->nm_rsize + NFS_MAXPKTHDR; > + sndreserve = (nmp->nm_wsize + NFS_MAXPKTHDR) * 2; > + rcvreserve = (nmp->nm_rsize + NFS_MAXPKTHDR) * 2; > } else if (nmp->nm_sotype == SOCK_SEQPACKET) { > sndreserve = (nmp->nm_wsize + NFS_MAXPKTHDR) * 2; > rcvreserve = (nmp->nm_rsize + NFS_MAXPKTHDR) * 2; > Index: nfs_vfsops.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_vfsops.c,v > retrieving revision 1.37 > diff -u -r1.37 nfs_vfsops.c > --- nfs_vfsops.c 1997/04/04 17:49:30 1.37 > +++ nfs_vfsops.c 1997/04/22 13:04:47 > @@ -302,12 +302,9 @@ > } > pref = fxdr_unsigned(u_long, fsp->fs_dtpref); > if (pref < nmp->nm_readdirsize) > - nmp->nm_readdirsize = (pref + NFS_DIRBLKSIZ - 1) & > - ~(NFS_DIRBLKSIZ - 1); > + nmp->nm_readdirsize = pref; > if (max < nmp->nm_readdirsize) { > - nmp->nm_readdirsize = max & ~(NFS_DIRBLKSIZ - 1); > - if (nmp->nm_readdirsize == 0) > - nmp->nm_readdirsize = max; > + nmp->nm_readdirsize = max; > } > nmp->nm_flag |= NFSMNT_GOTFSINFO; > } > @@ -741,13 +738,11 @@ > > if ((argp->flags & NFSMNT_READDIRSIZE) && argp->readdirsize > 0) { > nmp->nm_readdirsize = argp->readdirsize; > - /* Round down to multiple of blocksize */ > - nmp->nm_readdirsize &= ~(NFS_DIRBLKSIZ - 1); > - if (nmp->nm_readdirsize < NFS_DIRBLKSIZ) > - nmp->nm_readdirsize = NFS_DIRBLKSIZ; > } > if (nmp->nm_readdirsize > maxio) > nmp->nm_readdirsize = maxio; > + if (nmp->nm_readdirsize > nmp->nm_rsize) > + nmp->nm_readdirsize = nmp->nm_rsize; > > if ((argp->flags & NFSMNT_MAXGRPS) && argp->maxgrouplist >= 0 && > argp->maxgrouplist <= NFS_MAXGRPS) > > > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > > From owner-freebsd-bugs Tue Apr 22 10:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26374 for bugs-outgoing; Tue, 22 Apr 1997 10:22:00 -0700 (PDT) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26369 for ; Tue, 22 Apr 1997 10:21:56 -0700 (PDT) Received: (mailer@localhost) by gatekeeper.ray.com (8.7.5/8.7.3) id NAA14626 for ; Tue, 22 Apr 1997 13:21:51 -0400 Received: from gianowa.eo.ray.com by gatekeeper.ray.com; Tue Apr 22 13:21:22 1997 Received: from gianowa.eo.ray.com (localhost.eo.ray.com [127.0.0.1]) by gianowa.eo.ray.com (8.8.5/8.8.5) with SMTP id NAA00274 for ; Tue, 22 Apr 1997 13:21:20 -0400 (EDT) Message-ID: <335CF2DA.41C67EA6@eo.ray.com> Date: Tue, 22 Apr 1997 13:21:18 -0400 From: "William A. Gianopoulos" X-Mailer: Mozilla 3.01Gold (X11; U; FreeBSD 2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-bugs@FreeBSD.ORG Subject: How do I write a suid shell script? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I do not seem to be able to write a shell script that will run suid root under either FreeBSD 2.1.7 or FreeBSD 2.2. I have tried using sh both with and without the -p flag, and csh both with and without the -f and -b flags. Any ideas? Please e-mail responses to: gianowa@eo.ray.com Thanks, From owner-freebsd-bugs Tue Apr 22 10:29:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26891 for bugs-outgoing; Tue, 22 Apr 1997 10:29:39 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26880 for ; Tue, 22 Apr 1997 10:29:35 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id SAA11905; Tue, 22 Apr 1997 18:28:49 +0100 (BST) Date: Tue, 22 Apr 1997 18:28:49 +0100 (BST) From: Doug Rabson To: Thomas David Rivers cc: freebsd-bugs@freebsd.org Subject: Re: kern/3304: NFS V2 readdir hangs In-Reply-To: <199704221542.LAA04318@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 22 Apr 1997, Thomas David Rivers wrote: > > > > On Mon, 21 Apr 1997, Thomas David Rivers wrote: > > > > > > I think the most promising candidate is the 'full socket buffers' message. > > > > Could you see if that goes up consistently when you prompt the system to > > > > hang. The match between that and the reassembly number seems to show that > > > > these are large packets. > > > > > > We'll do! > > > > I have been looking at the code again today and it seems to me that the > > client is not reserving enough space in its sockets when it initialises > > the mount. Your nasty directory appears to generate a reply packet which > > is too large for the client to recieve. > > > > I added some code to use a slightly less restrictive buffer size in the > > NFS client. I also tidied up the code which sets the size for readdir > > requests to make it possible to set it to less than 4k and to be more > > compatible with 2.1.x. Could you try this patch, both with and without a > > -r1024 argument to mount_nfs. > > > I tried it out with a -r1024 (and -w1024, which shouldn't matter) > and without any options except -t60... > > It worked wonderfully!!! I'd say commit that patch!!! (thanks again) > > Now, I see you set the rcvreserve to "(nm_rsize + NFS_MAXPKTHDR) * 2" > which, for me was enough - but can we determine just what is 'really' > enough, or is this just a better guess? [Is it guaranteed to be > enough because you bump the readdirsize down to the rsize is rsize > is the lesser of the two?] In the existing code, the main problem I can see is that nm_readdirsize is allowed to be larger than nm_rsize and indeed is forced to be a minimum of 4k for some spurious reason. This would mean that if you set nm_rsize to 1024, you would be guaranteed a hang for the first readdir larger than about 1200 bytes. Did your hang happen with or without -r1024, or both? I still don't quite understand the rules used by the socketbuf for these sizes. It may be that just forcing nm_readdirsize <= nm_rsize is enough. I doubled the size to make it the same as the SEQPACKET and STREAM case; I don't think it will do any harm to leave it doubled. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-bugs Tue Apr 22 10:52:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28691 for bugs-outgoing; Tue, 22 Apr 1997 10:52:46 -0700 (PDT) Received: (from dfr@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28657; Tue, 22 Apr 1997 10:52:37 -0700 (PDT) Date: Tue, 22 Apr 1997 10:52:37 -0700 (PDT) From: Doug Rabson Message-Id: <199704221752.KAA28657@hub.freebsd.org> To: ponds!rivers@dg-rtp.dg.com, dfr, freebsd-bugs Subject: Re: kern/3304 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: NFS V2 readdir hangs State-Changed-From-To: open-closed State-Changed-By: dfr State-Changed-When: Tue Apr 22 10:51:32 PDT 1997 State-Changed-Why: Fixed in rev 1.23 of nfs_socket.c and rev 1.38 of nfs_vfsops.c. From owner-freebsd-bugs Tue Apr 22 12:40:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12516 for bugs-outgoing; Tue, 22 Apr 1997 12:40:11 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12456; Tue, 22 Apr 1997 12:40:04 -0700 (PDT) Resent-Date: Tue, 22 Apr 1997 12:40:04 -0700 (PDT) Resent-Message-Id: <199704221940.MAA12456@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mykes@sportsextra.com Received: from shell.sportsextra.com (shell.sportsextra.com [208.1.220.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10197 for ; Tue, 22 Apr 1997 12:32:05 -0700 (PDT) Received: (from mykes@localhost) by shell.sportsextra.com (8.7.5/8.7.3) id MAA25013; Tue, 22 Apr 1997 12:32:03 -0700 (PDT) Message-Id: <199704221932.MAA25013@shell.sportsextra.com> Date: Tue, 22 Apr 1997 12:32:03 -0700 (PDT) From: Mike Schwartz Reply-To: mykes@sportsextra.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3373: db bug? Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3373 >Category: kern >Synopsis: .db with 600K records and 1.1GB size returns errno=27 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 22 12:40:01 PDT 1997 >Last-Modified: >Originator: Mike Schwartz >Organization: Internet Extra Corporation >Release: FreeBSD 2.1-STABLE i386 >Environment: P166, 128M RAM, 4G disk space. The drive this .db file is on is 97% full with > 100MB free. >Description: When trying to add a new record, using perl dbm functions, perl dies with an error message "Can't write to db reason errno=27." The file has about 600K records in it and is 1.1G in size. -rw-rw-r-- 1 mykes httpd 1125855232 Apr 22 12:29 files.db >How-To-Repeat: create a db file and start adding records to it until it fails? >Fix: I don't have a fix. I had to kludge my software to use 2 .db files. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Apr 22 12:50:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17488 for bugs-outgoing; Tue, 22 Apr 1997 12:50:57 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA17218 for ; Tue, 22 Apr 1997 12:50:36 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA06956; Tue, 22 Apr 1997 15:50:02 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 22 Apr 1997 15:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id PAA06243; Tue, 22 Apr 1997 15:36:35 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id PAA04688; Tue, 22 Apr 1997 15:43:07 -0400 (EDT) Date: Tue, 22 Apr 1997 15:43:07 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704221943.PAA04688@lakes.water.net> To: ponds!nlsystems.com!dfr, ponds!lakes.water.net!rivers Subject: Re: kern/3304: NFS V2 readdir hangs Cc: ponds!freebsd.org!freebsd-bugs Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Doug Rabson writes: > > Now, I see you set the rcvreserve to "(nm_rsize + NFS_MAXPKTHDR) * 2" > > which, for me was enough - but can we determine just what is 'really' > > enough, or is this just a better guess? [Is it guaranteed to be > > enough because you bump the readdirsize down to the rsize is rsize > > is the lesser of the two?] > > In the existing code, the main problem I can see is that nm_readdirsize is > allowed to be larger than nm_rsize and indeed is forced to be a minimum of > 4k for some spurious reason. This would mean that if you set nm_rsize to > 1024, you would be guaranteed a hang for the first readdir larger than > about 1200 bytes. Ahh - I see... the socket buf was much smaller (because it's based on rsize) than the readdirsize... > Did your hang happen with or without -r1024, or both? It definately happened with -r1024 - I don't believe I tried it without a -r1024. > > I still don't quite understand the rules used by the socketbuf for these > sizes. It may be that just forcing nm_readdirsize <= nm_rsize is enough. > I doubled the size to make it the same as the SEQPACKET and STREAM case; I > don't think it will do any harm to leave it doubled. Ok - that sounds reasonable. I was wondering if we could deduce that doubled will always be adequate... Here's another question - I thought -I on mount_nfs was supposed to set the readdirsize... if not, should there be an option on mount_nfs that lets you set this? Such an option could be handy if we run into a similar problem in the future... - Dave Rivers - From owner-freebsd-bugs Tue Apr 22 13:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA00669 for bugs-outgoing; Tue, 22 Apr 1997 13:21:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA00663 for ; Tue, 22 Apr 1997 13:20:58 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA17143; Tue, 22 Apr 1997 22:20:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA29063; Tue, 22 Apr 1997 22:15:39 +0200 (MET DST) Message-ID: <19970422221539.IH04612@uriah.heep.sax.de> Date: Tue, 22 Apr 1997 22:15:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs@freebsd.org Cc: gianowa@eo.ray.com (William A. Gianopoulos) Subject: Re: How do I write a suid shell script? References: <335CF2DA.41C67EA6@eo.ray.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <335CF2DA.41C67EA6@eo.ray.com>; from William A. Gianopoulos on Apr 22, 1997 13:21:18 -0400 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As William A. Gianopoulos wrote: > I do not seem to be able to write a shell script that will run > suid root under either FreeBSD 2.1.7 or FreeBSD 2.2. This security hole has been disabled (about 10 years ago, i think). Look at suidperl if you want setuid scripts. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Tue Apr 22 16:00:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA13695 for bugs-outgoing; Tue, 22 Apr 1997 16:00:07 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA13667; Tue, 22 Apr 1997 16:00:03 -0700 (PDT) Date: Tue, 22 Apr 1997 16:00:03 -0700 (PDT) Message-Id: <199704222300.QAA13667@hub.freebsd.org> To: freebsd-bugs Cc: From: David Nugent Subject: RE: kern/3373: db bug? Reply-To: David Nugent Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3373; it has been noted by GNATS. From: David Nugent To: mykes@sportsextra.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG, Mike Schwartz Subject: RE: kern/3373: db bug? Date: Wed, 23 Apr 1997 08:53:20 +1000 (EST) On 22-Apr-97 Mike Schwartz wrote: >Release: FreeBSD 2.1-STABLE i386 ~ When trying to add a new record, using perl dbm functions, perl dies > with an error message "Can't write to db reason errno=27." errno 27 is "file too large". You're running into a process resource limit. See setrlimit(2) and getrlimit(2), and specifically RLIMIT_FSIZE. If your process is running as root, you can raise the hard limit beyond the size to which the file will grow (or infinity). If not, then you'll have to find the appropriate fix in the kernel to set the default filesize limit to your requirements. (With -current, you can set this up on a per login-class basis with /etc/login.conf). Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-bugs Tue Apr 22 16:57:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA17706 for bugs-outgoing; Tue, 22 Apr 1997 16:57:58 -0700 (PDT) Received: from adam.adonai.net ([205.182.92.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17701 for ; Tue, 22 Apr 1997 16:57:52 -0700 (PDT) Received: from localhost (leec@localhost) by adam.adonai.net (8.8.5/8.7.3) with SMTP id SAA20546; Tue, 22 Apr 1997 18:58:38 -0500 (CDT) Date: Tue, 22 Apr 1997 18:58:38 -0500 (CDT) From: "Lee Crites (AEI)" To: "William A. Gianopoulos" cc: freebsd-bugs@freebsd.org Subject: Re: How do I write a suid shell script? In-Reply-To: <335CF2DA.41C67EA6@eo.ray.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk =>I do not seem to be able to write a shell script that will run =>suid root under either FreeBSD 2.1.7 or FreeBSD 2.2. => =>I have tried using sh both with and without the -p flag, and =>csh both with and without the -f and -b flags. sudo? Lee From owner-freebsd-bugs Tue Apr 22 20:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA29751 for bugs-outgoing; Tue, 22 Apr 1997 20:11:00 -0700 (PDT) Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA29728; Tue, 22 Apr 1997 20:10:53 -0700 (PDT) Date: Tue, 22 Apr 1997 20:10:53 -0700 (PDT) From: David Greenman Message-Id: <199704230310.UAA29728@hub.freebsd.org> To: tege@nada.kth.se, davidg, freebsd-bugs Subject: Re: kern/3329 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: Panic when using tcpdump on fxp device State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Tue Apr 22 20:08:48 PDT 1997 State-Changed-Why: This was fixed in revs 1.34/1.21.2.6 by checking the validity of the packet length provided by the interface. Thanks for the bug report! From owner-freebsd-bugs Tue Apr 22 20:20:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00517 for bugs-outgoing; Tue, 22 Apr 1997 20:20:16 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00439; Tue, 22 Apr 1997 20:20:07 -0700 (PDT) Resent-Date: Tue, 22 Apr 1997 20:20:07 -0700 (PDT) Resent-Message-Id: <199704230320.UAA00439@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.hub.freebsd.org.id.UAA00143;Tue; (8.8.5/8.8.5);, 22 Apr 1997 20:15:32.-0700 (PDT) Message-Id: <199704230315.UAA00143@hub.freebsd.org> Date: Tue, 22 Apr 1997 20:15:32 -0700 (PDT) From: mshine@mindspring.com To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/3374: Cannot Install FreeBSD 2.2.1 - installation hangs when copying bin to root directory Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3374 >Category: bin >Synopsis: Cannot Install FreeBSD 2.2.1 - installation hangs when copying bin to root directory >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: support >Submitter-Id: current-users >Arrival-Date: Tue Apr 22 20:20:02 PDT 1997 >Last-Modified: >Originator: Michael Shine >Organization: Consultant >Release: 2.2.1 >Environment: N/A >Description: I cannot install from FreeBSD 2.2.1 April 1997 CD. The installation hangs when copying bin to the root directory. It gets at most 25% of the way before it hangs. Here is the configuration: SuperMicro P5STE Motherboard with Intel Pentium 200 Adaptec 2940 UW SCSI controller ID 7 Quantum Fireball TM 3.2 SCSI-3 with SCSI ID 0 Toshiba XM-3801B/F1 SCSI-2 CDROM ID 5 device IRQ Port fd0 6 3f0 (floppy disk drive controller) IDE 14 1f0 (IDE controller) IDE 10 168 (IDE controller) lpt0 7 378 (printer port) se0 4 3f8 (mouse) se1 3 2f8 (modem-USR Sportster Voice 33.6 PnP FAX Internal) kb 1 60 (keyboard) I am attempting to install to SCSI Quantum Fireball. Other items: Quantum BF25A011 2.5G Seagate Medalist 1.2G Soundblaster AWE-32 PnP I set the secondary IDE controller to the proper IRQ and port. I remove all devices that do not apply to my system. When I select minimal install, the installation proceeds until it gets to the point where it copies bin to / I have formatted and verified the disk several times. I have set all kinds of options on the Adaptec controller >How-To-Repeat: I have repeated this problems many different ways. I have tried all kinds of options on the Adaptec controller. I have reformatted the disk and verified it several times. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Apr 22 21:50:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA05597 for bugs-outgoing; Tue, 22 Apr 1997 21:50:01 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05577 for ; Tue, 22 Apr 1997 21:49:57 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id VAA10843; Tue, 22 Apr 1997 21:49:40 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199704222300.QAA13667@hub.freebsd.org> Date: Tue, 22 Apr 1997 21:44:23 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: David Nugent Subject: RE: kern/3373: db bug? Cc: freebsd-bugs@hub.freebsd.org, David Nugent Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Nugent; On 22-Apr-97 you wrote: ... > errno 27 is "file too large". > > You're running into a process resource limit. See setrlimit(2) and > getrlimit(2), and specifically RLIMIT_FSIZE. If your process is > running as root, you can raise the hard limit beyond the size to ... Speaking of resource limits, what am I doing wrong that causes mirror (the perl kind) to fail with ``out of memory'' error message when trying to mirror a very large ftp archive? I realize that the archive being Debian GNU/Linux and my machine here being FreeBSD creates severe political stress, but... :-) Simon From owner-freebsd-bugs Tue Apr 22 23:00:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09366 for bugs-outgoing; Tue, 22 Apr 1997 23:00:09 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09336; Tue, 22 Apr 1997 23:00:04 -0700 (PDT) Date: Tue, 22 Apr 1997 23:00:04 -0700 (PDT) Message-Id: <199704230600.XAA09336@hub.freebsd.org> To: freebsd-bugs Cc: From: "Jordan K. Hubbard" Subject: Re: bin/3374: Cannot Install FreeBSD 2.2.1 - installation hangs when copying bin to root directory Reply-To: "Jordan K. Hubbard" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3374; it has been noted by GNATS. From: "Jordan K. Hubbard" To: mshine@mindspring.com Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/3374: Cannot Install FreeBSD 2.2.1 - installation hangs when copying bin to root directory Date: Tue, 22 Apr 1997 22:56:31 -0700 Hmmm. Are you absolutely sure of your SCSI termination and cabling? This really seems like some sort of medium error; either that or the CD is somehow defective. Any debugging output in the 2nd screen at the point that it hangs? Can you enable debugging in the Options screen and run it again? Perhaps the debugging output will be helpful in at least pinpointing the failure. From owner-freebsd-bugs Tue Apr 22 23:42:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11282 for bugs-outgoing; Tue, 22 Apr 1997 23:42:05 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11277 for ; Tue, 22 Apr 1997 23:41:57 -0700 (PDT) Received: (from davidn@localhost) by unique.usn.blaze.net.au (8.8.5/8.8.5) id QAA14820; Wed, 23 Apr 1997 16:40:53 +1000 (EST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 23 Apr 1997 16:38:02 +1000 (EST) Organization: Unique Computing From: David Nugent To: Simon Shapiro Subject: RE: kern/3373: db bug? Cc: freebsd-bugs@hub.freebsd.org, David Nugent Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 23-Apr-97 Simon Shapiro wrote: > (the perl kind) to fail with ``out of memory'' error message when > trying to mirror a very large ftp archive? Probably resource limits again. mirror can get quite large in memory. If you're runing pre-current (or even -current) you can use the shell's limit (csh/tcsh) or ulimit (sh/bash) command to raise the memory limits to something more reasonable. If you're running -current, then you have other options by using limits(1) or configuring login.conf to set a more reasonable hard or soft limit. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-bugs Wed Apr 23 01:40:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16949 for bugs-outgoing; Wed, 23 Apr 1997 01:40:08 -0700 (PDT) Received: from fs.IConNet.NET (core.IConNet.NET [199.173.160.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16864; Wed, 23 Apr 1997 01:39:59 -0700 (PDT) Received: from LOCALNAME (client201-122-1.bellatlantic.net [151.201.122.1]) by fs.IConNet.NET (8.8.5/8.8.5) with SMTP id EAA27802; Wed, 23 Apr 1997 04:41:05 -0400 (EDT) Message-Id: <1.5.4.16.19970423084052.2caf2e18@postoffice.bellatlantic.net> X-Sender: dmm125@postoffice.bellatlantic.net X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 23 Apr 1997 04:40:52 -0400 To: freebsd-bugs@freebsd.org From: Donn Miller Subject: com3 - sio2: "not found", but there Cc: questions@freebsd.org Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I recently had this problem: while booting, and probing for sio2 on the isa bus, I get a "not found at 0x3e8", but I checked with MSD under DOS and this is the correct port address. Also, it is set to probe at irq4, port 0x3e8, which is the setting I use under Windows, which works OK there. I think these settings worked OK under 2.1.5-RELEASE. Maybe there is a bug, or maybe I need to set the flags. If the flags need set, what would be a good set of guidelines to go by? I'm still confused after reading the docs. It is a Wang 14.4 Data Fax Modem (Hayes Compatible). One good thing to have is a way to probe some devices without recompiling the kernel entirely. This might be accomplished by writing some test code (with main() fuction) and linking with the sio device driver, or something like that. Any suggestions would be appreciated. Thanks Donn From owner-freebsd-bugs Wed Apr 23 04:20:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA23878 for bugs-outgoing; Wed, 23 Apr 1997 04:20:13 -0700 (PDT) Received: (from dfr@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA23797; Wed, 23 Apr 1997 04:18:48 -0700 (PDT) Date: Wed, 23 Apr 1997 04:18:48 -0700 (PDT) From: Doug Rabson Message-Id: <199704231118.EAA23797@hub.freebsd.org> To: tenser@big-O.math.psu.edu, dfr, freebsd-bugs Subject: Re: kern/2908 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: Fix for the NFS filehandle bug. State-Changed-From-To: open-closed State-Changed-By: dfr State-Changed-When: Wed Apr 23 04:17:43 PDT 1997 State-Changed-Why: Fixed in rev 1.32 and 1.26.2.2 of vfs_vnops.c. From owner-freebsd-bugs Wed Apr 23 04:25:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA24428 for bugs-outgoing; Wed, 23 Apr 1997 04:25:56 -0700 (PDT) Received: (from dfr@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA24392; Wed, 23 Apr 1997 04:25:47 -0700 (PDT) Date: Wed, 23 Apr 1997 04:25:47 -0700 (PDT) From: Doug Rabson Message-Id: <199704231125.EAA24392@hub.freebsd.org> To: hsu@clinet.fi, dfr, freebsd-bugs Subject: Re: kern/3162 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: 2.2 kernel from mar 25th crashes on nfs server State-Changed-From-To: open-feedback State-Changed-By: dfr State-Changed-When: Wed Apr 23 04:24:43 PDT 1997 State-Changed-Why: Does this still happen with the latest ahc driver from the RELENG_2_2 branch? From owner-freebsd-bugs Wed Apr 23 08:40:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05795 for bugs-outgoing; Wed, 23 Apr 1997 08:40:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05776; Wed, 23 Apr 1997 08:40:02 -0700 (PDT) Resent-Date: Wed, 23 Apr 1997 08:40:02 -0700 (PDT) Resent-Message-Id: <199704231540.IAA05776@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, are@communique.no Received: from www.communique.no (www.communique.no [193.212.204.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA05629 for ; Wed, 23 Apr 1997 08:33:49 -0700 (PDT) Received: (qmail 3902 invoked by uid 1001); 23 Apr 1997 15:23:34 -0000 Message-Id: <19970423152334.3901.qmail@www.communique.no> Date: 23 Apr 1997 15:23:34 -0000 From: are@communique.no Reply-To: are@communique.no To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3375: Ten minute delay at boot-time Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3375 >Category: kern >Synopsis: Consistent 10 min. delay at boot with REL-2.2.1 on Pentium >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 23 08:40:01 PDT 1997 >Last-Modified: >Originator: Are Bryne >Organization: Communique DA >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: Pentium 133 Mhz, Soyo 5TX5 MB, 64 MB unbuffered DIMM, 512 kB L2 cache BIOS plug & play, 2 onboard IDE controllers which are turned off, onboard Creative CT-2505 (Vibra 16C) chip (not enabled in kernel), onboard Adaptec 7880 U/W SCSI controller with SEAGATE ST32171W 2062MB disk, and MATSHITA CD-ROM CR-506. My own no-frills kernel with X-support. >Description: The system seems to freeze right after the boot prompt. I can enter e.g a -c at the prompt, or nothing, but after pressing return, the system will stay put for ten minutes before it continues booting. This happens with both the generic kernel, and my own one. It also seems as if the time lapse is _not_ recorded, so that the clock (as seen with date) sags behind by ten minutes afterwards. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Apr 23 10:20:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11061 for bugs-outgoing; Wed, 23 Apr 1997 10:20:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11053; Wed, 23 Apr 1997 10:20:01 -0700 (PDT) Date: Wed, 23 Apr 1997 10:20:01 -0700 (PDT) Message-Id: <199704231720.KAA11053@hub.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/3375: Ten minute delay at boot-time Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3375; it has been noted by GNATS. From: Bruce Evans To: are@communique.no, FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: kern/3375: Ten minute delay at boot-time Date: Thu, 24 Apr 1997 03:15:22 +1000 > The system seems to freeze right after the boot prompt. I can enter > e.g a -c at the prompt, or nothing, but after pressing return, the > system will stay put for ten minutes before it continues booting. This is probably caused by broken RTC (clock) hardware. If this is the case, then you can probably tell by booting with -v and noticing that the delay occurs after the "Calibrating clock(s) ... " message. There is a timeout, but it is too large (apparently 10 minutes on your system). > This happens with both the generic kernel, and my own one. > It also seems as if the time lapse is _not_ recorded, so that the > clock (as seen with date) sags behind by ten minutes afterwards. The clock is not supposed to stop. Perhaps the i/o's to initialize it somehow stop it. This would explain both problems. Try this fix. The reduced timeout should reduce the delay to < 10 seconds on your machined even if the other change doesn't work. The timeout is still too large for i386's. diff -c2 clock.c~ clock.c *** clock.c~ Mon Apr 7 19:36:15 1997 --- clock.c Thu Apr 24 03:08:45 1997 *************** *** 504,509 **** --- 568,576 ---- writertc(u_char reg, u_char val) { + inb(0x84); outb(IO_RTC, reg); + inb(0x84); outb(IO_RTC + 1, val); + inb(0x84); /* XXX work around wrong order in rtcin() */ } *************** *** 524,528 **** if (!(rtcin(RTC_STATUSD) & RTCSD_PWR)) goto fail; ! timeout = 100000000; /* Read the mc146818A seconds counter. */ --- 591,595 ---- if (!(rtcin(RTC_STATUSD) & RTCSD_PWR)) goto fail; ! timeout = 1000000; /* XXX */ /* Read the mc146818A seconds counter. */ From owner-freebsd-bugs Wed Apr 23 10:30:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11560 for bugs-outgoing; Wed, 23 Apr 1997 10:30:06 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11548; Wed, 23 Apr 1997 10:30:03 -0700 (PDT) Resent-Date: Wed, 23 Apr 1997 10:30:03 -0700 (PDT) Resent-Message-Id: <199704231730.KAA11548@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, charnier@xp11.frmug.org Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA11312 for ; Wed, 23 Apr 1997 10:26:31 -0700 (PDT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id KAA20994 for ; Wed, 23 Apr 1997 10:26:20 -0700 (PDT) Received: (from uucp@localhost) by frmug.org (8.8.5/8.8.5/frmug-2.0) with UUCP id WAA23787 for FreeBSD-gnats-submit@freebsd.org; Tue, 22 Apr 1997 22:41:01 +0200 (MET DST) Received: (from charnier@localhost) by xp11.frmug.org (8.8.5/8.8.5/xp11-uucp-1.1) id WAA07143; Tue, 22 Apr 1997 22:33:57 +0200 (CEST) Message-Id: <199704222033.WAA07143@xp11.frmug.org> Date: Tue, 22 Apr 1997 22:33:57 +0200 (CEST) From: Philippe Charnier Reply-To: charnier@xp11.frmug.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/3376: incorrect output from kdump Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3376 >Category: bin >Synopsis: incorrect output from kdump >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Apr 23 10:30:02 PDT 1997 >Last-Modified: >Originator: Philippe Charnier >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: >Description: When running kdump, I found: "i" 4848 ksh RET read 1 4848 ksh CALL read(0,0x3498c,0x1) 4848 ksh GIO fd 0 read 1 bytes "t" 4848 ksh RET read 1 4848 ksh CALL read(0,0x3498c,0x1) 4848 ksh GIO fd 0 read 1 bytes <-- should be '1 byte' " <-- \n should be printed " 4848 ksh RET read 1 >How-To-Repeat: $ ktrace /usr/local/bin/ksh $ exit $ >Fix: Index: kdump.c =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/kdump/kdump.c,v retrieving revision 1.9 diff -u -r1.9 kdump.c --- kdump.c 1997/03/29 04:30:10 1.9 +++ kdump.c 1997/04/22 20:21:27 @@ -368,14 +368,15 @@ else screenwidth = 80; } - printf("fd %d %s %d bytes\n", ktr->ktr_fd, - ktr->ktr_rw == UIO_READ ? "read" : "wrote", datalen); + printf("fd %d %s %d byte%s\n", ktr->ktr_fd, + ktr->ktr_rw == UIO_READ ? "read" : "wrote", datalen, + datalen == 1 ? "" : "s"); if (maxdata && datalen > maxdata) datalen = maxdata; (void)printf(" \""); col = 8; for (;datalen > 0; datalen--, dp++) { - (void) vis(visbuf, *dp, VIS_CSTYLE, *(dp+1)); + (void) vis(visbuf, *dp, VIS_CSTYLE|VIS_NL, *(dp+1)); cp = visbuf; /* * Keep track of printables and >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Apr 23 11:52:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA16614 for bugs-outgoing; Wed, 23 Apr 1997 11:52:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA16580; Wed, 23 Apr 1997 11:51:56 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA01342; Wed, 23 Apr 1997 20:50:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id UAA03534; Wed, 23 Apr 1997 20:22:00 +0200 (MET DST) Message-ID: <19970423202159.VJ16948@uriah.heep.sax.de> Date: Wed, 23 Apr 1997 20:21:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: dmm125@bellatlantic.net (Donn Miller) Cc: freebsd-bugs@freebsd.org, questions@freebsd.org Subject: Re: com3 - sio2: "not found", but there References: <1.5.4.16.19970423084052.2caf2e18@postoffice.bellatlantic.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <1.5.4.16.19970423084052.2caf2e18@postoffice.bellatlantic.net>; from Donn Miller on Apr 23, 1997 04:40:52 -0400 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Donn Miller wrote: > I recently had this problem: while booting, and probing for > sio2 on the isa bus, I get a "not found at 0x3e8", but I checked > with MSD under DOS and this is the correct port address. Also, it > is set to probe at irq4, port 0x3e8, which is the setting I use > under Windows, which works OK there. This doesn't mean anything. :) > It is a Wang 14.4 Data Fax Modem (Hayes Compatible). Many internal modems are known to have a poor UART emulation. You can try to spot the problem by turning on flags 0x80 in the sio2 driver (using boot -c), this will report the failing probe routine. Then, look into /sys/i386/isa/sio.c, maybe you can tweak some DELAY() value to give your UART emulation a little more time to react. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Apr 23 12:00:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17052 for bugs-outgoing; Wed, 23 Apr 1997 12:00:08 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17027; Wed, 23 Apr 1997 12:00:02 -0700 (PDT) Date: Wed, 23 Apr 1997 12:00:02 -0700 (PDT) Message-Id: <199704231900.MAA17027@hub.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: bin/3376: incorrect output from kdump Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3376; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: charnier@xp11.frmug.org Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/3376: incorrect output from kdump Date: Wed, 23 Apr 1997 20:28:41 +0200 As Philippe Charnier wrote: > When running kdump, I found: > "i" > 4848 ksh RET read 1 > 4848 ksh CALL read(0,0x3498c,0x1) > 4848 ksh GIO fd 0 read 1 bytes > "t" > 4848 ksh RET read 1 > 4848 ksh CALL read(0,0x3498c,0x1) > 4848 ksh GIO fd 0 read 1 bytes <-- should be '1 byte' > " <-- \n should be printed > " > 4848 ksh RET read 1 I agree with your spelling correction. But converting all newlines to \n would be terrible. If you read a text file, it will crunch everything into a single, huge blurb of a line. For example, this snippet from a `ktrace fortune': 3563 fortune CALL read(0x3,0xc000,0x2000) 3563 fortune GIO fd 3 read 8192 bytes "!07/11 PDP a ni deppart m'I !pleH % (1) Alexander the Great was a great general. (2) Great generals are forewarned. (3) Forewarned is forearmed. (4) Four is an even number. (5) Four is certainly an odd number of arms for a man to have. (6) The only number that is both even and odd is infinity. Therefore, Alexander the Great had an infinite number of arms. ...would then look like: 3563 fortune CALL read(0x3,0xc000,0x2000) 3563 fortune GIO fd 3 read 8192 bytes "!07/11 PDP a ni deppart m'I !pleH\n%\n(1) Alexander the Great was a\ great general.\n(2) Great generals are forewarned.\n(3) Forewarned \ is forearmed.\n(4) Four is an even number.\n(5) Four is certainly an\ odd number of arms for a man to have.\n(6) The only number that is \ both even and odd is infinity.\n\nTherefore, Alexander the Great had\ an infinite number of arms. Do you think that's better? :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Apr 23 12:18:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17904 for bugs-outgoing; Wed, 23 Apr 1997 12:18:42 -0700 (PDT) Received: from ns2.win.net (ns2.win.net [204.215.209.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA17898 for ; Wed, 23 Apr 1997 12:18:38 -0700 (PDT) From: Planet_Ocean@profitmaster.com Received: (from nobody@localhost) by ns2.win.net (8.6.12/8.6.9) id OAA02824 for ; Wed, 23 Apr 1997 14:34:48 -0400 Date: Wed, 23 Apr 1997 14:34:48 -0400 Message-Id: <199704231834.OAA02824@ns2.win.net> Received: from pm0-19.ilhawaii.net(204.188.87.28) by ns2.win.net via smap (V1.3) id smaj20175; Wed Apr 23 14:34:04 1997 X-Sender: Planet_Ocean@profitmaster.com (Unverified) X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-bugs@freebsd.org Subject: Your website's "Findability" -- Search Engine Help Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Would you like to improve your website's "findability" in the Search Engines? During the past year, my company has placed over 100 webpages into the Top Ten -- the front page -- of the major search engines... and, for a small fee, I am willing to show you exactly how we did it. My name is Stephen Mahaney. I am the president of Planet Ocean Communications. My web marketing company has literally "written the book" on how to position your website on the front page -- the Top Ten -- of each of the major search engines... guaranteed! Our 45 page book identifies every trick & technique that is being used on the Internet to gain an almost "unfair" advantage in landing websites at the top of the search engine lists -- right where you need to be so that potential customers who are seeking your services or products can find you. Our monthly Newsletter keeps you abreast of the latest techniques and frequent changes that take place in the dynamic world of "search engine" science. However, understanding the process does not require a degree in "rocket" science -- nor do you need to be "technically oriented". Whether your website is a "do-it-yourself" project or you are paying someone to maintain your site, you (or your webmaster) need to know the tricks in this book in order to compete with the professionals who are dominating the front pages of the various search categories. To learn more about how you can obtain this essential information and receive a free subscription to our Newsletter -- SEARCH ENGINE SECRETS UPDATE, go to.... http://www.profitmaster.com/se-win/ You'll be glad you did. Sincerely, Stephen Mahaney - President Planet Ocean Communications *************************************************** Note: We have contacted you based on information that we gathered while visiting your website - If you would prefer not to receive mail from us in the future, please reply with the word "remove" in the subject line and we will gladly exclude you from future correspondence. Thanks *************************************************** Thought for the day... "The only thing a man can take beyond this lifetime is his ethics" From owner-freebsd-bugs Wed Apr 23 17:29:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA02913 for bugs-outgoing; Wed, 23 Apr 1997 17:29:12 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA02904 for ; Wed, 23 Apr 1997 17:29:09 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id RAA23309; Wed, 23 Apr 1997 17:29:07 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 23 Apr 1997 17:21:38 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers.freebsd.org@sendero.i-connect.net, freebsd-bugs@freebsd.org Subject: RELELNG_2_2 is Broken - Help!!! Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What is the value of PCI_SUBID_REG2 ?? sys/pci/pcireg.h defines PCI_SUBID_REG{0,1}, but not 2. sys/pci/pci.c, in line 1758 makes a reference to PCI_SUBID_REG2. I am trying to get a 2.2 kernel that runs for more than 5 minutes without a panic on the open problem (with short shell scripts, etc.). Alternative: How do I checkout of CVS /usr/src/sys as of 13-Feb-97? It is the last kernel I know of to exhibit usable level of stability. [ Before you attack me for bad mouthing the RELENG_2_2 kernel: ] On our development platforms, all kernels since either blow up on aic7xxx, or (I am told) sd.c (if a SCSI disk is lazy and times out), or panics as I reported before, when X11 is running. The SCSI problems is VERY visisble when doing dump. This is correct for 18-Apr-97. due to the problem above, I cannot build newer kernels. Simon t 2. sys/pci/pci.c, in line 1758 makes a reference to PCI_SUBID_REG2. I am trying to get a 2.2 kernel that runs for more than 5 minutes without a panic on the open problem (with short shell scripts, etc.). Alternative: How From owner-freebsd-bugs Wed Apr 23 22:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17157 for bugs-outgoing; Wed, 23 Apr 1997 22:37:11 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17147; Wed, 23 Apr 1997 22:36:58 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.5/8.8.5) id WAA03496; Wed, 23 Apr 1997 22:36:12 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD X-PRIORITY: 2 (High) Priority: urgent Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 23 Apr 1997 22:25:18 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-scsi@freebsd.org, freebsd-bugs@freebsd.org Subject: Panic in sys/scsi/scsiconf.c - Please Help... Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think I posted this before, but now I am stuck, and with no answers so far. So here it is again: I am calling scsi_attachdevs() from a device driver and getting PANIC: extend_set: entry 1 already has storage panic: scsi-attachdevs: malloc. Upon close examination one sees the lines: if(scbus == 0 || scbus->sc_link == 0 || extend_set(scbusses, scsibus, scbus) == 0) { panic("scsi_attachdevs: malloc"); ... When one examins the extend_set erorr message one sees quickly that it returns zero (NULL) when it discovers that the storage being extended is already extended. I am a bit confused abouth this as if storage is already allocated, why would extend_set try to extend it before checking? Also, why would it return ZERO if there IS storage. I am a bit confused. BTW, this happens only on the 176th device on the SCSI bus, so it is a bit difficult to see on most systems. I have disabled the return 0 in extend_set for now, but really need someone who understands this code to tell me which is the proper way of handling it. Thanx, Simon us->sc_link == 0 || extend_set(scbusses, scsibus, scbus) == 0) { panic("scsi_attachdevs: malloc"); ... When one examins the extend_set erorr message one sees quickly that it returns zero (NULL) when From owner-freebsd-bugs Thu Apr 24 09:14:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA13992 for bugs-outgoing; Thu, 24 Apr 1997 09:14:27 -0700 (PDT) Received: from chris.netmonger.net (root@chris.netmonger.net [165.254.145.61]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA13975; Thu, 24 Apr 1997 09:14:05 -0700 (PDT) Received: (from chris@localhost) by chris.netmonger.net (8.8.5/8.8.5) id MAA07353; Thu, 24 Apr 1997 12:13:55 -0400 (EDT) Date: Thu, 24 Apr 1997 12:13:55 -0400 (EDT) From: Christopher Masto Message-Id: <199704241613.MAA07353@chris.netmonger.net> To: obrien@FreeBSD.ORG, bugs@FreeBSD.ORG, jdd@cs.toronto.edu Subject: Re: cvs commit: ports/sysutils/tcplist - Imported sources X-Newsgroups: netmonger.gw.cvs-all In-Reply-To: <199704240804.BAA13586@freefall.freebsd.org> Organization: NetMonger Communications Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In article <199704240804.BAA13586@freefall.freebsd.org> you write: >obrien 97/04/24 01:04:53 > > ports/sysutils/tcplist - Imported sources > Update of /home/ncvs/ports/sysutils/tcplist > In directory freefall.freebsd.org:/e/work/obrien/tcplist There is a minor bug in this program (originally). utils.c, line 287: sv=getservbyport((int)pnum, NULL); Should be: sv=getservbyport(htons((int)pnum), NULL); From owner-freebsd-bugs Thu Apr 24 10:04:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17307 for bugs-outgoing; Thu, 24 Apr 1997 10:04:07 -0700 (PDT) Received: from chris.netmonger.net (chris.netmonger.net [165.254.145.61]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA17254; Thu, 24 Apr 1997 10:03:59 -0700 (PDT) Received: (from chris@localhost) by chris.netmonger.net (8.8.5/8.8.5) id NAA09331; Thu, 24 Apr 1997 13:03:28 -0400 (EDT) Date: Thu, 24 Apr 1997 13:03:28 -0400 (EDT) From: Christopher Masto Message-Id: <199704241703.NAA09331@chris.netmonger.net> To: obrien@FreeBSD.ORG, bugs@FreeBSD.ORG, jdd@cs.toronto.edu Subject: Re: cvs commit: ports/sysutils/tcplist - Imported sources X-Newsgroups: netmonger.gw.cvs-all In-Reply-To: <199704240804.BAA13586@freefall.freebsd.org> Organization: NetMonger Communications Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Whoops, that was "tcp", not NULL, in the getservbyport() before I started messing with it. From owner-freebsd-bugs Thu Apr 24 10:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA19323 for bugs-outgoing; Thu, 24 Apr 1997 10:30:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA19315; Thu, 24 Apr 1997 10:30:02 -0700 (PDT) Resent-Date: Thu, 24 Apr 1997 10:30:02 -0700 (PDT) Resent-Message-Id: <199704241730.KAA19315@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.hub.freebsd.org.id.KAA19025;Thu; (8.8.5/8.8.5);, 24 Apr 1997 10:25:27.-0700 (PDT) Message-Id: <199704241725.KAA19025@hub.freebsd.org> Date: Thu, 24 Apr 1997 10:25:27 -0700 (PDT) From: hafner@forwiss.tu-muenchen.de To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/3379: mprof dumps core on FreeBSD 2.2.1 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3379 >Category: bin >Synopsis: mprof dumps core on FreeBSD 2.2.1 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 24 10:30:01 PDT 1997 >Last-Modified: >Originator: Walter Hafner >Organization: FORWISS >Release: 2.2.1 >Environment: FreeBSD pccog4 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE #0 >Description: tcsh > mprof a.out Segmentation fault (core dumped) 'nuff said >How-To-Repeat: tcsh > cat hello.c #include int main() { printf("Hello!\n"); return 0; } tcsh > gcc hello.c -lc_mp tcsh > mprof a.out Segmentation fault (core dumped) >Fix: No fix! (I installed over FTP ... slow connection, so I didn't get the sources ...) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Apr 24 10:55:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20697 for bugs-outgoing; Thu, 24 Apr 1997 10:55:14 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA20691 for ; Thu, 24 Apr 1997 10:55:08 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id SAA23148; Thu, 24 Apr 1997 18:45:15 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id OAA12523; Thu, 24 Apr 1997 14:23:07 +0200 (CEST) Message-ID: <19970424142306.59692@klemm.gtn.com> Date: Thu, 24 Apr 1997 14:23:06 +0200 From: Andreas Klemm To: Simon Shapiro Cc: freebsd-hackers.freebsd.org@sendero.i-connect.net, freebsd-bugs@freebsd.org Subject: Re: RELELNG_2_2 is Broken - Help!!! References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Simon Shapiro on Wed, Apr 23, 1997 at 05:21:38PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2-STABLE Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Apr 23, 1997 at 05:21:38PM -0700, Simon Shapiro wrote: [-- Warning: iso-8859-8 is not compatible with your display.] > What is the value of PCI_SUBID_REG2 ?? In the commit message to pci.c Stefan wrote 0x40. So one had a nice chance to include the define into pcireg.h ;-) In the meantime Stfan has committed that already. > I am trying to get a 2.2 kernel that runs for more than 5 minutes without a > panic on the open problem (with short shell scripts, etc.). I'm running 2.2-STABLE and have zero problems at all ! Runs perfectly stable ! Maybe you should check your kernel config file or upgrade to 2.2-STABLE and do a make world ??? > Alternative: How do I checkout of CVS /usr/src/sys as of 13-Feb-97? It is > the last kernel I know of to exhibit usable level of stability. With the -D option, which allows you to checkout a release branch or HEAD (-current) at a certain date ... > [ Before you attack me for bad mouthing the RELENG_2_2 kernel: ] > > On our development platforms, all kernels since either blow up on > aic7xxx, or (I am told) sd.c (if a SCSI disk is lazy and times out), or > panics as I reported before, when X11 is running. The SCSI problems is > VERY visisble when doing dump. This is correct for 18-Apr-97. due to the > problem above, I cannot build newer kernels. Just in case that you read the mailing lists and news you might have noticed, that Justin worked very hard on that and if you update your machine to 2.2-STABLE, you'll see, that all the problems will go away. I have a really rock solid 2.2-STABLE here, no matter if I do large I/O disk benchmarks, dumps and such ! I'll give you a kernel config file as reference in the attachement. > I am trying to get a 2.2 kernel that runs for more than 5 minutes without a > panic on the open problem (with short shell scripts, etc.). _The_ open problem ??? Is it a well known problem ? ;-)) Well, I have _zero_ problems in this area. FreeBSD acts as a Internet gateway here and I' gettings nearly all mailing-lists, have squid running, a WWW Server ... and no problems with open. I suggest you tell your problems more verbously. But anyway ... there is a STABLE tree, that's RELENG_2_2, either you cvsup the sources or the cvs repository, if the latter is the case for you, simply checkout RELENG_2_2 # cd /somewhere_with_about_150_MB_free_space # cvs checkout -r RELENG_2_2 src # cd src && time make world >& world.log & Since you have problems with your SCSI subsystem it's surely a good idea to build and install a new stable kernel first before doing a make world. Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-bugs Thu Apr 24 13:40:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29768 for bugs-outgoing; Thu, 24 Apr 1997 13:40:06 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29751; Thu, 24 Apr 1997 13:40:02 -0700 (PDT) Date: Thu, 24 Apr 1997 13:40:02 -0700 (PDT) Message-Id: <199704242040.NAA29751@hub.freebsd.org> To: freebsd-bugs Cc: From: Michael Newlyn Blake Subject: Re: kern/3150: Cyrix 6x86L-P200+ crashes w/ page fault Reply-To: Michael Newlyn Blake Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3150; it has been noted by GNATS. From: Michael Newlyn Blake To: freebsd-gnats-submit@freebsd.org, gilibert@cig.mot.com Cc: mblake@frogtown.com Subject: Re: kern/3150: Cyrix 6x86L-P200+ crashes w/ page fault Date: Thu, 24 Apr 1997 13:29:10 -0700 I am having the exact same problem under 2.2.1, only more so. This seems to happen even when the system isn't being placed under a particularly high load. When the system doesn't crash completely, it can still have problems with the console locking up, not being able to spawn new processes, etc. In fact, at the moment I am at work. The system (fozzy.frogtown.com, 204.188.115.1) has stoped responding, but it is still routing packets between it's PPP interface and ethernet interface. System is an AMD 486 clone 40MHz CPU with 16MB memory. We will be trying to swap out the motherboard this evening in the hopes that it will help some. I think we may have even managed to collect a few crash dumps, but I can't verify that until I get home and reset the computer so I can log in to it. Cheers. ------------------------ Michael Newlyn Blake ENS/MPK18 Building Support Michael.Blake@Eng.Sun.Com x83987/415-786-3987 From owner-freebsd-bugs Thu Apr 24 17:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA10676 for bugs-outgoing; Thu, 24 Apr 1997 17:00:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA10655; Thu, 24 Apr 1997 17:00:02 -0700 (PDT) Resent-Date: Thu, 24 Apr 1997 17:00:02 -0700 (PDT) Resent-Message-Id: <199704250000.RAA10655@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mike@marker.cs.utah.edu Received: from marker.cs.utah.edu (marker.cs.utah.edu [155.99.212.61]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10186 for ; Thu, 24 Apr 1997 16:50:36 -0700 (PDT) Received: (from mike@localhost) by marker.cs.utah.edu (8.8.5/8.7.3) id RAA22720; Thu, 24 Apr 1997 17:50:32 -0600 (MDT) Message-Id: <199704242350.RAA22720@marker.cs.utah.edu> Date: Thu, 24 Apr 1997 17:50:32 -0600 (MDT) From: Mike Hibler Reply-To: mike@marker.cs.utah.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3380: kernel bug: typo in mount export list processing Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3380 >Category: kern >Synopsis: typo in mount export list processing >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 24 17:00:01 PDT 1997 >Last-Modified: >Originator: Mike Hibler >Organization: U.of U. >Release: FreeBSD 2.1.7-RELEASE i386 >Environment: All current versions of {open,net,free}bsd >Description: There is a typo in mount's export list processing that results in FSes being exported to more networks than intended (though unlikely, it could be exploited via NFS, hence the "serious" and "high" rating. In kern/vfs_subr() in vfs_hang_addrlist: if (argp->ex_masklen) { smask = (struct sockaddr *) ((caddr_t) saddr + argp->ex_addrlen); error = copyin(argp->ex_addr, (caddr_t) smask, argp->ex_masklen); if (error) goto out; if (smask->sa_len > argp->ex_masklen) smask->sa_len = argp->ex_masklen; } copyin is using argp->ex_addr instead of argp->ex_mask as the address of the mask. >How-To-Repeat: N/A >Fix: Change ex_addr to ex_mask in the copyin. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Apr 24 19:27:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18129 for bugs-outgoing; Thu, 24 Apr 1997 19:27:45 -0700 (PDT) Received: (from jkh@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18109; Thu, 24 Apr 1997 19:27:39 -0700 (PDT) Date: Thu, 24 Apr 1997 19:27:39 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199704250227.TAA18109@hub.freebsd.org> To: nsayer@quack.kfu.com, jkh, freebsd-bugs Subject: Re: misc/3136 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: rc.firewall should be run after interfaces are up State-Changed-From-To: open-analyzed State-Changed-By: jkh State-Changed-When: Fri Apr 25 04:24:20 MET DST 1997 State-Changed-Why: Would you be willing to review a more comprehensive reorganization of all this which just happens to fix your PR as a side-effect? ;-) From owner-freebsd-bugs Thu Apr 24 23:54:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28293 for bugs-outgoing; Thu, 24 Apr 1997 23:54:32 -0700 (PDT) Received: (from peter@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28266; Thu, 24 Apr 1997 23:54:17 -0700 (PDT) Date: Thu, 24 Apr 1997 23:54:17 -0700 (PDT) From: Peter Wemm Message-Id: <199704250654.XAA28266@hub.freebsd.org> To: mike@marker.cs.utah.edu, peter, freebsd-bugs Subject: Re: kern/3380 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: typo in mount export list processing State-Changed-From-To: open-closed State-Changed-By: peter State-Changed-When: Thu Apr 24 23:50:53 PDT 1997 State-Changed-Why: Suggested fix applied, Thanks! sys_kern.c, rev 1.83 (current), 1.64.2.4 (2.2), 1.30.4.4 (2.1) From owner-freebsd-bugs Fri Apr 25 01:40:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA02594 for bugs-outgoing; Fri, 25 Apr 1997 01:40:03 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA02565; Fri, 25 Apr 1997 01:40:01 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 01:40:01 -0700 (PDT) Resent-Message-Id: <199704250840.BAA02565@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, gareth@eagle.seed.net.tw Received: from g2314a.dorm.ccu.edu.tw (g2314a.dorm.ccu.edu.tw [140.123.212.144]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA02040 for ; Fri, 25 Apr 1997 01:31:09 -0700 (PDT) Received: (from icon@localhost) by g2314a.dorm.ccu.edu.tw (8.8.5/8.7.3) id QAA01334; Fri, 25 Apr 1997 16:29:51 +0800 (CST) Message-Id: <199704250829.QAA01334@g2314a.dorm.ccu.edu.tw> Date: Fri, 25 Apr 1997 16:29:51 +0800 (CST) From: gareth@eagle.seed.net.tw Reply-To: gareth@eagle.seed.net.tw To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3381: 2.2.x kernel panic on traversing and removing an NFS mounted directory. Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3381 >Category: kern >Synopsis: 2.2.x kernel panic on traversing and removing an NFS mountd directory >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 01:40:00 PDT 1997 >Last-Modified: >Originator: Gareth Shue >Organization: >Release: FreeBSD 2.2.1-RELEASE i386 >Environment: FreeBSD 2.2-RELEASE, 2.2.1-RELEASE, 2.2.STABLE #0. >Description: The enclosed program traverse a directory and removes every file. It works fine when (1) on local disk filesystem (2) both on local and nfs mounted filesystem on 2.1.5 RELEASE But, the same program causes kernel panic on FreeBSD 2.2.x when traversing NFS mounted directories. NFS server => 2.1.5-RELEASE, 2.2-RELEASE, 2.2.1-RELEASE >How-To-Repeat: For repeating this problem, we have to mounted a NFS filesytem first. (This test will not affect the NFS server). 1. Compile the enclosed program by "gcc -o myrmdir prog.c" 2. Run it. "myrmdir " 3. kernel panic....rebooting.. ------------------->> prog.c cut here<<--------------------------------------- #include #include int RemoveDir(char *dir) { DIR *dirp; struct dirent *dp; struct stat stbuf; chdir(dir); if ( (dirp = opendir(".")) == NULL ){ perror("opendir()"); exit(-1); } while ( (dp = readdir(dirp)) != NULL ) { if ( !strcmp(dp->d_name, ".") || !strcmp(dp->d_name, "..") ) continue; if ( stat(dp->d_name, &stbuf) == -1 ) { perror("state():"); continue; } if ( S_ISDIR(stbuf.st_mode) ){ RemoveDir(dp->d_name); continue; } printf("unlink %s\n", dp->d_name); unlink(dp->d_name); } closedir(dirp); chdir(".."); rmdir(dir); return 1; } int main(int argc, char *argv[]) { if ( argc < 2 ) exit(-1); RemoveDir(argv[1]); return 1; } ---------------------------->> end here <<------------------------------ >Fix: no ideas. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 04:40:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09439 for bugs-outgoing; Fri, 25 Apr 1997 04:40:05 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09411; Fri, 25 Apr 1997 04:40:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 04:40:02 -0700 (PDT) Resent-Message-Id: <199704251140.EAA09411@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, furuta@sra.co.jp Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA09122 for ; Fri, 25 Apr 1997 04:34:37 -0700 (PDT) Received: from sranhc.sra.co.jp by sraigw.sra.co.jp (8.6.13/3.4W-sraigw) id UAA27048; Fri, 25 Apr 1997 20:34:20 +0900 Received: from sras63.sra.co.jp (root@sras63 [133.137.20.191]) by sranhc.sra.co.jp (8.6.13/3.4W-srambox) with ESMTP id UAA22322 for ; Fri, 25 Apr 1997 20:31:11 +0900 Received: from sras63.sra.co.jp (furuta@localhost [127.0.0.1]) by sras63.sra.co.jp (8.6.12+2.4W3/3.4W-sras63) with ESMTP id UAA25981 for freebsd-gnats-submit@freebsd.org; Fri, 25 Apr 1997 20:34:33 +0900 Message-Id: <199704251134.UAA25981@sras63.sra.co.jp> Date: Fri, 25 Apr 1997 20:34:32 +0900 From: furuta@sra.co.jp Reply-To: furuta@sra.co.jp To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/3382: bootp.8 -t option Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3382 >Category: docs >Synopsis: bootp.8 -t option >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 04:40:01 PDT 1997 >Last-Modified: >Originator: Atsushi Furuta >Organization: Software Research Associates, Inc. >Release: FreeBSD-2.2.1-RELEASE >Environment: FreeBSD-2.2.1-RELEASE >Description: In bootp code, -t timeout is counted in minutes rather than in seconds. >How-To-Repeat: % man 8 bootp >Fix: --- bootpd.8~ Thu Apr 10 13:48:37 1997 +++ bootpd.8 Fri Apr 25 20:29:24 1997 @@ -115,7 +115,7 @@ process will wait for a BOOTP packet before exiting. If no packets are recieved for .I timeout -seconds, then the program will exit. +minutes, then the program will exit. A timeout value of zero means "run forever". In standalone mode, this option is forced to zero. .TP -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 05:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11740 for bugs-outgoing; Fri, 25 Apr 1997 05:30:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA11730; Fri, 25 Apr 1997 05:30:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 05:30:02 -0700 (PDT) Resent-Message-Id: <199704251230.FAA11730@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tri@iki.fi Received: from vipunen.hut.fi (root@vipunen.hut.fi [130.233.224.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA11656 for ; Fri, 25 Apr 1997 05:29:20 -0700 (PDT) Received: from pooh.tky.hut.fi (pooh.tky.hut.fi [130.233.23.135]) by vipunen.hut.fi (8.8.5/8.8.2) with ESMTP id PAA125394 for ; Fri, 25 Apr 1997 15:29:12 +0300 Received: by pooh.tky.hut.fi (PAA01865); Fri, 25 Apr 1997 15:29:11 +0300 (EEST) Message-Id: <199704251229.PAA01865@pooh.tky.hut.fi> Date: Fri, 25 Apr 1997 15:29:11 +0300 (EEST) From: tri@iki.fi Reply-To: tri@iki.fi To: FreeBSD-gnats-submit@freebsd.org Cc: tri-bcc@pooh.tky.hut.fi X-Send-Pr-Version: 3.2 Subject: kern/3384: Bug in telldir-closedir-opendir-seekdir Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3384 >Category: kern >Synopsis: telldir-seekdir can cause livelock >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 05:30:00 PDT 1997 >Last-Modified: >Originator: Timo J. Rinne >Organization: Helsinki University of Technology >Release: FreeBSD 3.0-CURRENT i386 >Environment: i386 - Pentium 3.0-current 970209 - 9704?? >Description: When traversing through directory structure like this pseudocode: traverse(d) { opendir(d) while(e = readdir(d)) if (directory-p(e)) x = telldir(d) closedir(d) traverse(e) opendir(d) seekdir(d, x) closedir(d) } Restoring of the current directory after subtreetraversal causes the directory read to start from beginning leading to livelock. >How-To-Repeat: My colleague Jukka Partanen kindly provided a test program. Gets stuck when ran in directory with ordinary files and subdirectories. Works in NetBSD and Linux, gets stuck in FreeBSD. >Fix: Sorry. No time to debug. We use different OS in our production system. >Audit-Trail: >Unformatted: >>>>>>>>>>>>>>>>>> C U T H E R E >>>>>>>>>>>>>>>>>> /* * * dirtest.c * * Author: Jukka Partanen * * Copyright (c) 1997 Nokia Research Center * All rights reserved * * Created : Thu Apr 24 14:53:03 1997 partanen * Last modified: Fri Apr 25 09:47:13 1997 partanen * * $Id$ * */ #include #include #include #include #include #include static int process_dir(int namelen); static char file[PATH_MAX+1]; int main(int argc, char *argv[]) { char *name = argc > 1 ? argv[1] : "."; int namelen; strcpy(file, name); namelen = strlen(file); if (namelen && file[namelen - 1] == '/') namelen--; return process_dir(namelen); } static int process_dir(int namelen) { long dirpos; DIR *dirp; struct dirent *dp; struct stat statbuf; dirp = opendir(file); if (!dirp) { perror(file); return 1; } while ((dp = readdir(dirp)) != NULL) { file[namelen] = '/'; strcpy(file + namelen + 1, dp->d_name); if (stat(file, &statbuf) < 0) { perror(file); } else { printf("%s\n", file); if ((statbuf.st_mode & S_IFDIR) && strcmp(dp->d_name, ".") && strcmp(dp->d_name, "..")) { dirpos = telldir(dirp); closedir(dirp); process_dir(namelen + strlen(dp->d_name) + 1); file[namelen] = '\0'; dirp = opendir(file); if (!dirp) { perror(file); return 1; } seekdir(dirp, dirpos); } } file[namelen] = '\0'; } closedir(dirp); return 0; } >>>>>>>>>>>>>>>>>> C U T H E R E >>>>>>>>>>>>>>>>>> From owner-freebsd-bugs Fri Apr 25 05:50:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA12935 for bugs-outgoing; Fri, 25 Apr 1997 05:50:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA12915; Fri, 25 Apr 1997 05:50:01 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 05:50:01 -0700 (PDT) Resent-Message-Id: <199704251250.FAA12915@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, soil@quick.net Received: from jg.dyn.ml.org (soil@newport-1-12.quick.net [207.212.160.212]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12804 for ; Fri, 25 Apr 1997 05:48:43 -0700 (PDT) Received: (from soil@localhost) by jg.dyn.ml.org (8.8.5/8.8.5) id FAA00655; Fri, 25 Apr 1997 05:48:40 -0700 (PDT) Message-Id: <199704251248.FAA00655@jg.dyn.ml.org> Date: Fri, 25 Apr 1997 05:48:40 -0700 (PDT) From: soil@quick.net Reply-To: soil@quick.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/3385: error in vis.1, unvis.1 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3385 >Category: docs >Synopsis: error in vis.1, unvis.1 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 05:50:00 PDT 1997 >Last-Modified: >Originator: Josh Gilliam >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: vis.1 8.4 (Berkeley) 4/19/94 unvis.1 8.1 (Berkeley) 6/6/93 >Description: ``appears'' should be changed to ``appeared'' on line 123 of vis.1. ``appears'' should be changed to ``appeared'' on line 56 of unvis.1. >How-To-Repeat: man 1 vis /HISTORY man 1 unvis /HISTORY >Fix: --- vis.1.orig Thu Jul 25 11:11:30 1996 +++ vis.1 Fri Apr 25 05:32:44 1997 @@ -120,5 +120,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . --- unvis.1.orig Fri May 27 05:33:16 1994 +++ unvis.1 Fri Apr 25 05:45:23 1997 @@ -53,5 +53,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 06:21:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA14664 for bugs-outgoing; Fri, 25 Apr 1997 06:21:48 -0700 (PDT) Received: from net2.netview.net (netview.net [199.3.74.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA14656 for ; Fri, 25 Apr 1997 06:21:44 -0700 (PDT) Received: from watney (ip71-188.ts.netview.net [199.3.71.188]) by net2.netview.net (8.8.5/8.8.5) with SMTP id IAA01906 for ; Fri, 25 Apr 1997 08:23:14 -0500 (EST) Date: Fri, 25 Apr 1997 08:23:14 -0500 (EST) Message-Id: <3.0.32.19970425082212.00a7c760@199.3.74.250> X-Sender: jc@199.3.74.250 X-Mailer: Windows Eudora Pro Version 3.0 (32) To: bugs@freebsd.org From: John Clark Subject: owner sticky and mv Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I think I have found a bug while moving (mv) files from one filesystem to another. Files that are owner sticky (in this case root) do not transfer their permissions properly. John Clark [email@john.net] From owner-freebsd-bugs Fri Apr 25 07:09:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17155 for bugs-outgoing; Fri, 25 Apr 1997 07:09:16 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17048; Fri, 25 Apr 1997 07:07:55 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id PAA20068; Fri, 25 Apr 1997 15:07:18 +0100 (BST) Date: Fri, 25 Apr 1997 15:07:18 +0100 (BST) From: Doug Rabson To: tri@iki.fi cc: FreeBSD-gnats-submit@freebsd.org, tri-bcc@pooh.tky.hut.fi, GNATS Management , freebsd-bugs@hub.freebsd.org Subject: Re: kern/3384: Bug in telldir-closedir-opendir-seekdir In-Reply-To: <199704251229.PAA01865@pooh.tky.hut.fi> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You can't use the results of telldir after the directory has been closed. The manpage for seekdir clearly states this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-bugs Fri Apr 25 07:10:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17279 for bugs-outgoing; Fri, 25 Apr 1997 07:10:22 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17240; Fri, 25 Apr 1997 07:10:05 -0700 (PDT) Date: Fri, 25 Apr 1997 07:10:05 -0700 (PDT) Message-Id: <199704251410.HAA17240@hub.freebsd.org> To: freebsd-bugs Cc: From: Doug Rabson Subject: Re: kern/3384: Bug in telldir-closedir-opendir-seekdir Reply-To: Doug Rabson Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3384; it has been noted by GNATS. From: Doug Rabson To: tri@iki.fi Cc: FreeBSD-gnats-submit@freebsd.org, tri-bcc@pooh.tky.hut.fi, GNATS Management , freebsd-bugs@hub.freebsd.org Subject: Re: kern/3384: Bug in telldir-closedir-opendir-seekdir Date: Fri, 25 Apr 1997 15:07:18 +0100 (BST) You can't use the results of telldir after the directory has been closed. The manpage for seekdir clearly states this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-bugs Fri Apr 25 08:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21548 for bugs-outgoing; Fri, 25 Apr 1997 08:11:45 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21543 for ; Fri, 25 Apr 1997 08:11:43 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id BAA01527; Sat, 26 Apr 1997 01:01:54 +1000 Date: Sat, 26 Apr 1997 01:01:54 +1000 From: Bruce Evans Message-Id: <199704251501.BAA01527@godzilla.zeta.org.au> To: bugs@freebsd.org, jc@netview.net Subject: Re: owner sticky and mv Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I think I have found a bug while moving (mv) files from one filesystem to >another. Files that are owner sticky (in this case root) do not transfer >their permissions properly. This may be a feature. The kernel rejects attempts by non-root to set the sticky bit for non-directories. mv(1) has no idea that the problem is caused by the sticky bit, so it doesn't try another chmod() to set the other bits. The sticky bit has no direct effect for non-directories, so perhaps is was being used by root to inhibit moving files :-). Bruce From owner-freebsd-bugs Fri Apr 25 08:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22623 for bugs-outgoing; Fri, 25 Apr 1997 08:31:36 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22618 for ; Fri, 25 Apr 1997 08:31:33 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id BAA02198; Sat, 26 Apr 1997 01:29:56 +1000 Date: Sat, 26 Apr 1997 01:29:56 +1000 From: Bruce Evans Message-Id: <199704251529.BAA02198@godzilla.zeta.org.au> To: dfr@nlsystems.com, freebsd-bugs@hub.freebsd.org Subject: Re: kern/3384: Bug in telldir-closedir-opendir-seekdir Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You can't use the results of telldir after the directory has been closed. > The manpage for seekdir clearly states this. It also says that "It is safe to use a telldir() value immediately after a call to opendir() and before any calls to readdir()". We also use the SINGLEUSE compile time option which gives undocumented semantics. If this were standard then there would by no need to clean up the cookies on close - there would be at most one leaked per close, and programs could be expected to do clean it by seeking before close. The test program dumps core with malloc options AJ due to using a garbage dp after close. Bruce From owner-freebsd-bugs Fri Apr 25 08:38:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA23024 for bugs-outgoing; Fri, 25 Apr 1997 08:38:12 -0700 (PDT) Received: from net2.netview.net (netview.net [199.3.74.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23019 for ; Fri, 25 Apr 1997 08:38:09 -0700 (PDT) Received: from watney (ip71-188.ts.netview.net [199.3.71.188]) by net2.netview.net (8.8.5/8.8.5) with SMTP id KAA02425; Fri, 25 Apr 1997 10:39:41 -0500 (EST) Date: Fri, 25 Apr 1997 10:39:41 -0500 (EST) Message-Id: <3.0.32.19970425103837.00a79210@199.3.74.250> X-Sender: jc@199.3.74.250 X-Mailer: Windows Eudora Pro Version 3.0 (32) To: bugs@freebsd.org, Bruce Evans From: John Clark Subject: Re: owner sticky and mv Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce, >>I think I have found a bug while moving (mv) files from one filesystem to >>another. Files that are owner sticky (in this case root) do not transfer >>their permissions properly. > >This may be a feature. The kernel rejects attempts by non-root to set >the sticky bit for non-directories. mv(1) has no idea that the problem >is caused by the sticky bit, so it doesn't try another chmod() to set >the other bits. The sticky bit has no direct effect for non-directories, >so perhaps is was being used by root to inhibit moving files :-). Try this (as root): NOTE: To demonstrate this bug, you have to be moving a subdirectory across file systems. This assumes that '/root' and '/var' are on different filesystems. mkdir /var/d1 mkdir /var/d1/test touch /var/d1/test/f1_rw touch /var/d1/test/f2_rw touch /var/d1/test/f1_nn touch /var/d1/test/f2_nn chown root.wheel /var/d1/test/f1_rw chown root.wheel /var/d1/test/f2_rw chown nobody.nogroup /var/d1/test/f1_nn chown nobody.nogroup /var/d1/test/f2_nn chmod 4555 /var/d1/test/f1_rw chmod 555 /var/d1/test/f2_rw chmod 4555 /var/d1/test/f1_nn chmod 555 /var/d1/test/f2_nn ls -al /var/d1/test At this point you should see the obvious: drwx------ 2 root wheel 512 Apr 25 10:27 ./ drwx------ 3 root wheel 512 Apr 25 10:27 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-xr-x 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* now: mv /var/d1/test /var ls -al /var/test moving the subdir on the same filesystem, everything is ok: drwx------ 2 root wheel 512 Apr 25 10:30 ./ drwxr-xr-x 20 root wheel 512 Apr 25 10:30 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-xr-x 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* now: mv /var/test /root ls -al /root/test we see that any files owned by the mover get stripped: drwx------ 2 root wheel 512 Apr 25 10:32 ./ drwxr-x--- 9 root wheel 512 Apr 25 10:32 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-s------ 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* I am using umask 077, although it should not affect an 'mv' process. umask of 007: drwx------ 2 root wheel 512 Apr 25 10:33 ./ drwxr-x--- 9 root wheel 512 Apr 25 10:33 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-x--- 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* This is a bug, 'mv' looks at umask of files owned by the mover uid when moving across filesystems. Thanks, John Clark [email@john.net] From owner-freebsd-bugs Fri Apr 25 09:01:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA23983 for bugs-outgoing; Fri, 25 Apr 1997 09:01:21 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23971 for ; Fri, 25 Apr 1997 09:01:17 -0700 (PDT) Received: from net2.netview.net (netview.net [199.3.74.250]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id IAA24735 for ; Fri, 25 Apr 1997 08:44:05 -0700 (PDT) Received: from watney (ip71-188.ts.netview.net [199.3.71.188]) by net2.netview.net (8.8.5/8.8.5) with SMTP id KAA02425; Fri, 25 Apr 1997 10:39:41 -0500 (EST) Date: Fri, 25 Apr 1997 10:39:41 -0500 (EST) Message-Id: <3.0.32.19970425103837.00a79210@199.3.74.250> X-Sender: jc@199.3.74.250 X-Mailer: Windows Eudora Pro Version 3.0 (32) To: bugs@freebsd.org, Bruce Evans From: John Clark Subject: Re: owner sticky and mv Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce, >>I think I have found a bug while moving (mv) files from one filesystem to >>another. Files that are owner sticky (in this case root) do not transfer >>their permissions properly. > >This may be a feature. The kernel rejects attempts by non-root to set >the sticky bit for non-directories. mv(1) has no idea that the problem >is caused by the sticky bit, so it doesn't try another chmod() to set >the other bits. The sticky bit has no direct effect for non-directories, >so perhaps is was being used by root to inhibit moving files :-). Try this (as root): NOTE: To demonstrate this bug, you have to be moving a subdirectory across file systems. This assumes that '/root' and '/var' are on different filesystems. mkdir /var/d1 mkdir /var/d1/test touch /var/d1/test/f1_rw touch /var/d1/test/f2_rw touch /var/d1/test/f1_nn touch /var/d1/test/f2_nn chown root.wheel /var/d1/test/f1_rw chown root.wheel /var/d1/test/f2_rw chown nobody.nogroup /var/d1/test/f1_nn chown nobody.nogroup /var/d1/test/f2_nn chmod 4555 /var/d1/test/f1_rw chmod 555 /var/d1/test/f2_rw chmod 4555 /var/d1/test/f1_nn chmod 555 /var/d1/test/f2_nn ls -al /var/d1/test At this point you should see the obvious: drwx------ 2 root wheel 512 Apr 25 10:27 ./ drwx------ 3 root wheel 512 Apr 25 10:27 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-xr-x 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* now: mv /var/d1/test /var ls -al /var/test moving the subdir on the same filesystem, everything is ok: drwx------ 2 root wheel 512 Apr 25 10:30 ./ drwxr-xr-x 20 root wheel 512 Apr 25 10:30 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-xr-x 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* now: mv /var/test /root ls -al /root/test we see that any files owned by the mover get stripped: drwx------ 2 root wheel 512 Apr 25 10:32 ./ drwxr-x--- 9 root wheel 512 Apr 25 10:32 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-s------ 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* I am using umask 077, although it should not affect an 'mv' process. umask of 007: drwx------ 2 root wheel 512 Apr 25 10:33 ./ drwxr-x--- 9 root wheel 512 Apr 25 10:33 ../ -r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* -r-sr-x--- 1 root wheel 0 Apr 25 10:27 f1_rw* -r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* -r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* This is a bug, 'mv' looks at umask of files owned by the mover uid when moving across filesystems. Thanks, John Clark [email@john.net] From owner-freebsd-bugs Fri Apr 25 09:27:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25123 for bugs-outgoing; Fri, 25 Apr 1997 09:27:03 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25090 for ; Fri, 25 Apr 1997 09:26:51 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA03538; Sat, 26 Apr 1997 02:22:45 +1000 Date: Sat, 26 Apr 1997 02:22:45 +1000 From: Bruce Evans Message-Id: <199704251622.CAA03538@godzilla.zeta.org.au> To: bde@zeta.org.au, bugs@freebsd.org, jc@netview.net Subject: Re: owner sticky and mv Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >NOTE: To demonstrate this bug, you have to be moving a subdirectory across >file systems. This assumes that '/root' and '/var' are on different >filesystems. > >mkdir /var/d1 >mkdir /var/d1/test >touch /var/d1/test/f1_rw >touch /var/d1/test/f2_rw >touch /var/d1/test/f1_nn >touch /var/d1/test/f2_nn >chown root.wheel /var/d1/test/f1_rw >chown root.wheel /var/d1/test/f2_rw >chown nobody.nogroup /var/d1/test/f1_nn >chown nobody.nogroup /var/d1/test/f2_nn >chmod 4555 /var/d1/test/f1_rw >chmod 555 /var/d1/test/f2_rw >chmod 4555 /var/d1/test/f1_nn >chmod 555 /var/d1/test/f2_nn >ls -al /var/d1/test >... >mv /var/test /root >ls -al /root/test > >we see that any files owned by the mover get stripped: > >drwx------ 2 root wheel 512 Apr 25 10:32 ./ >drwxr-x--- 9 root wheel 512 Apr 25 10:32 ../ >-r-sr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f1_nn* >-r-s------ 1 root wheel 0 Apr 25 10:27 f1_rw* >-r-xr-xr-x 1 nobody nogroup 0 Apr 25 10:27 f2_nn* >-r-xr-xr-x 1 root wheel 0 Apr 25 10:27 f2_rw* > >I am using umask 077, although it should not affect an 'mv' process. This works here. I seem to already have a fix for it. The bug is in `cp -p' (mv across file systems uses cp -pRP). diff -c2 cp/utils.c~ cp/utils.c *** cp/utils.c~ Sun Feb 23 12:34:58 1997 --- cp/utils.c Sun Feb 23 12:35:00 1997 *************** *** 160,165 **** */ ! if (pflag && setfile(fs, to_fd)) ! rval = 1; /* * If the source was setuid or setgid, lose the bits unless the --- 160,165 ---- */ ! if (pflag) ! rval = setfile(fs, to_fd); /* * If the source was setuid or setgid, lose the bits unless the Bruce From owner-freebsd-bugs Fri Apr 25 09:40:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25994 for bugs-outgoing; Fri, 25 Apr 1997 09:40:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA25989 for ; Fri, 25 Apr 1997 09:40:50 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA03895; Sat, 26 Apr 1997 02:36:28 +1000 Date: Sat, 26 Apr 1997 02:36:28 +1000 From: Bruce Evans Message-Id: <199704251636.CAA03895@godzilla.zeta.org.au> To: bde@zeta.org.au, bugs@freebsd.org, jc@netview.net Subject: Re: owner sticky and mv Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: >diff -c2 cp/utils.c~ cp/utils.c >*** cp/utils.c~ Sun Feb 23 12:34:58 1997 >--- cp/utils.c Sun Feb 23 12:35:00 1997 >*************** >*** 160,165 **** > */ > >! if (pflag && setfile(fs, to_fd)) >! rval = 1; > /* > * If the source was setuid or setgid, lose the bits unless the >--- 160,165 ---- > */ > >! if (pflag) >! rval = setfile(fs, to_fd); > /* > * If the source was setuid or setgid, lose the bits unless the This isn't quite right - it sometimes changes rval from 1 to 0. The main point of it is not run the `else' clause when setfile() fails. Bruce From owner-freebsd-bugs Fri Apr 25 12:10:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05205 for bugs-outgoing; Fri, 25 Apr 1997 12:10:03 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05199; Fri, 25 Apr 1997 12:10:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 12:10:02 -0700 (PDT) Resent-Message-Id: <199704251910.MAA05199@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, jin@adv-pc-1.lbl.gov Received: from adv-pc-1.lbl.gov (adv-pc-1.lbl.gov [128.3.196.189]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04984 for ; Fri, 25 Apr 1997 12:04:45 -0700 (PDT) Received: (from jin@localhost) by adv-pc-1.lbl.gov (8.8.5/8.8.5) id MAA00477; Fri, 25 Apr 1997 12:04:36 -0700 (PDT) Message-Id: <199704251904.MAA00477@adv-pc-1.lbl.gov> Date: Fri, 25 Apr 1997 12:04:36 -0700 (PDT) From: "Jin Guojun[ITG]" Reply-To: jin@adv-pc-1.lbl.gov To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/3387: sh mis-interpret the file name / awk failure Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3387 >Category: bin >Synopsis: sh mis-interpret the file name / awk failure >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 12:10:01 PDT 1997 >Last-Modified: >Originator: Jin Guojun[ITG] >Organization: /-------------- Jin Guojun ------------ v -- Internet: j_guojun@lbl.gov ---\ | Imaging & Distributed Computing | Usenet: ucbvax!j_guojun@lbl.gov | | Lawrence Berkeley Laboratory | Bitnet: -- | | 50B-2239, Berkeley, CA 94720 - jin%george.lbl.gov@Csa3.LBL.Gov | \--Ph#:(510) 486-7531 + Fax: 486-6363 --^--http://www-itg.lbl.gov/ITG.html-/ >Release: All FreeBSD RELEASE i386 >Environment: All FreeBSD RELEASEs >Description: In a script, if the variable for a file name had a white space at the end, the sh will treat it differently when the file name variable is used at redirected I/O, from used at fopen(). The white space is interpreted as part of the file name when I/O redirections, such as, '<', '<<', '>>', and '>' are used. This is a problem for using in a script. The FreeBSD awk generates such withe space: MyArch=`uname -v | awk -F/ '{printf $NF}` echo "=$MyArch=" =GENERIC = I am not sure which one is the problem, maybe both. >How-To-Repeat: For awk problem, see Description above. Below is the sh issue: % more abc file abc is a testing file % more test.script FILE_NAME="abc " more < $FILE_NAME echo "=$FILE_NAME=" more $FILE_NAME % test.script test.script: cannot open abc : no such file =abc = file abc is a testing file >Fix: one of them has to be fixed, but I do know which (-: Maybe both? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 12:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06471 for bugs-outgoing; Fri, 25 Apr 1997 12:30:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06461; Fri, 25 Apr 1997 12:30:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 12:30:02 -0700 (PDT) Resent-Message-Id: <199704251930.MAA06461@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, scotto@remuda.com Received: from popeye.remuda.com (fisbin.remuda.com [205.153.153.59]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA06303 for ; Fri, 25 Apr 1997 12:27:30 -0700 (PDT) Received: (from scotto@localhost) by popeye.remuda.com (8.6.12/8.6.12) id MAA08948; Fri, 25 Apr 1997 12:25:05 -0700 Message-Id: <199704251925.MAA08948@popeye.remuda.com> Date: Fri, 25 Apr 1997 12:25:05 -0700 From: scotto@remuda.com Reply-To: scotto@remuda.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/3388: /bin/sh doesn't return correct exit status Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3388 >Category: bin >Synopsis: /bin/sh doesn't return correct exit status >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 12:30:01 PDT 1997 >Last-Modified: >Originator: Scott Overholser >Organization: >Release: FreeBSD 2.2.0-RELEASE i386 >Environment: FreeBSD 2.2.0 systems in general >Description: A return in a /bin/sh script should return the exit status of the preceeding command. /bin/sh under FreeBSD 2.2.0-R does not - it returns 0. FreeBSD 2.1.x does not exhibit this problem. This behavior breaks many /bin/sh scripts. >How-To-Repeat: Execute the following commands: $ /bin/sh $ f() return 78 $ g() { f return } $ h() { f } $ f ; echo $? 78 # this is the observed result - it is correct $ g ; echo $? 0 # this is the observed result - it is wrong. we should see 78 here $ h ; echo $? 78 # this is the observed result - it is correct $ exit >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 13:00:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08199 for bugs-outgoing; Fri, 25 Apr 1997 13:00:03 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08193; Fri, 25 Apr 1997 13:00:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 13:00:02 -0700 (PDT) Resent-Message-Id: <199704252000.NAA08193@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.hub.freebsd.org.id.MAA08146;Fri; (8.8.5/8.8.5);, 25 Apr 1997 12:59:41.-0700 (PDT) Message-Id: <199704251959.MAA08146@hub.freebsd.org> Date: Fri, 25 Apr 1997 12:59:41 -0700 (PDT) From: pius@ienet.com To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/3389: syslog.conf(5) man page omits ftp facility Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3389 >Category: docs >Synopsis: syslog.conf(5) man page omits ftp facility >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 13:00:01 PDT 1997 >Last-Modified: >Originator: Pius Fischer >Organization: >Release: FreeBSD 3.0-current from Feb. 10 97 >Environment: FreeBSD iago.ienet.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Mar 5 19:20:16 PST 1997 pius@iago.ienet.com:/usr/src/sys/compile/IAGO i386 >Description: the man page for syslog.conf doesn't mention the ftp facility >How-To-Repeat: man syslog.conf >Fix: Here's a diff -u to rev. 1.5: --- syslog.conf.5.orig Fri Apr 25 12:37:52 1997 +++ syslog.conf.5 Fri Apr 25 12:38:34 1997 @@ -80,7 +80,7 @@ The .Em facility describes the part of the system generating the message, and is one of -the following keywords: auth, authpriv, cron, daemon, kern, lpr, mail, +the following keywords: auth, authpriv, cron, daemon, ftp, kern, lpr, mail, mark, news, syslog, user, uucp and local0 through local7. These keywords (with the exception of mark) correspond to the similar >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Apr 25 13:07:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08563 for bugs-outgoing; Fri, 25 Apr 1997 13:07:20 -0700 (PDT) Received: (from max@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08539; Fri, 25 Apr 1997 13:07:13 -0700 (PDT) Date: Fri, 25 Apr 1997 13:07:13 -0700 (PDT) From: Masafumi NAKANE Message-Id: <199704252007.NAA08539@hub.freebsd.org> To: dima@tejblum.dnttm.rssi.ru, max, freebsd-bugs Subject: Re: docs/3051 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: Missing 'mailto:' in some place in the handbook State-Changed-From-To: open-closed State-Changed-By: max State-Changed-When: Fri Apr 25 22:06:31 MET DST 1997 State-Changed-Why: Suggested fix applied in Rev. 1.55. From owner-freebsd-bugs Fri Apr 25 13:38:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10126 for bugs-outgoing; Fri, 25 Apr 1997 13:38:21 -0700 (PDT) Received: (from max@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10102; Fri, 25 Apr 1997 13:38:10 -0700 (PDT) Date: Fri, 25 Apr 1997 13:38:10 -0700 (PDT) From: Masafumi NAKANE Message-Id: <199704252038.NAA10102@hub.freebsd.org> To: soil@quick.net, max, freebsd-bugs Subject: Re: docs/3178 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: error in getopt.3 State-Changed-From-To: open-closed State-Changed-By: max State-Changed-When: Fri Apr 25 13:37:14 PDT 1997 State-Changed-Why: Suggested correction is done in getopt.3 Rev.1.5. From owner-freebsd-bugs Fri Apr 25 13:49:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10780 for bugs-outgoing; Fri, 25 Apr 1997 13:49:05 -0700 (PDT) Received: (from max@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10759; Fri, 25 Apr 1997 13:49:00 -0700 (PDT) Date: Fri, 25 Apr 1997 13:49:00 -0700 (PDT) From: Masafumi NAKANE Message-Id: <199704252049.NAA10759@hub.freebsd.org> To: soil@quick.net, max, freebsd-bugs Subject: Re: docs/3385 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: error in vis.1, unvis.1 State-Changed-From-To: open-closed State-Changed-By: max State-Changed-When: Fri Apr 25 13:48:04 PDT 1997 State-Changed-Why: Suggested fix applied in vsi.1 rev.1.3 and unvis.1 rev.1.2. From owner-freebsd-bugs Fri Apr 25 21:10:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03499 for bugs-outgoing; Fri, 25 Apr 1997 21:10:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03491; Fri, 25 Apr 1997 21:10:02 -0700 (PDT) Resent-Date: Fri, 25 Apr 1997 21:10:02 -0700 (PDT) Resent-Message-Id: <199704260410.VAA03491@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, yensid@imsa.edu Received: from beach.aca.imsa.edu (beach.aca.imsa.edu [143.195.65.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03359 for ; Fri, 25 Apr 1997 21:08:30 -0700 (PDT) Received: (from yensid@localhost) by beach.aca.imsa.edu (8.8.5/8.8.5) id XAA11566; Fri, 25 Apr 1997 23:18:54 -0500 (CDT) Message-Id: <199704260418.XAA11566@beach.aca.imsa.edu> Date: Fri, 25 Apr 1997 23:18:54 -0500 (CDT) From: yensid@imsa.edu Reply-To: yensid@imsa.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3391 >Category: kern >Synopsis: Pentium optimizations in default bootdisk breaks some 486's >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Apr 25 21:10:01 PDT 1997 >Last-Modified: >Originator: Don Schmidt >Organization: Illinois Math and Science Academy >Release: FreeBSD 2.1.7-RELEASE i386 >Environment: i486 w/AMD BIOS, 28M ram, Diamond Speedstar Pro (Cirrus GD5230 based) vesa video board >Description: On all current boot disks, on certain 486's (mine, at least) after the kernel is loaded, the screen characters turn into unreadable gibberish in simply horrid shades of magenta and orange, leaving the machine in a unusable state. >How-To-Repeat: Would seem to be repeatable only on specific configurations >Fix: Removing support for I586_CPU in the bootdisk kernel would disable the optimizations that are apparently causing the problems. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 26 00:00:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09365 for bugs-outgoing; Sat, 26 Apr 1997 00:00:06 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09353; Sat, 26 Apr 1997 00:00:02 -0700 (PDT) Date: Sat, 26 Apr 1997 00:00:02 -0700 (PDT) Message-Id: <199704260700.AAA09353@hub.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3391; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@FreeBSD.org, yensid@imsa.edu Cc: Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Date: Sat, 26 Apr 1997 16:49:45 +1000 >>Release: FreeBSD 2.1.7-RELEASE i386 >>Environment: > i486 w/AMD BIOS, 28M ram, Diamond Speedstar Pro (Cirrus GD5230 based) > vesa video board > >>Description: > On all current boot disks, on certain 486's (mine, at least) >after the kernel is loaded, the screen characters turn into unreadable >gibberish in simply horrid shades of magenta and orange, leaving the >machine in a unusable state. This can't have anything to do with i586 optimizations. There are no i586 significant optimizations in 2.1.7. There is one (insignificant) i586 optimization - not using the i486-optimized bzero, There is one (insignificant) i586 pessimization - zeroing the TimeStampCounter every clock tick and never using things that depend on this. The i586 mizations are only used on i586's. Bruce From owner-freebsd-bugs Sat Apr 26 00:10:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09700 for bugs-outgoing; Sat, 26 Apr 1997 00:10:02 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09686; Sat, 26 Apr 1997 00:10:00 -0700 (PDT) Date: Sat, 26 Apr 1997 00:10:00 -0700 (PDT) Message-Id: <199704260710.AAA09686@hub.freebsd.org> To: freebsd-bugs Cc: From: Don Schmidt Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Reply-To: Don Schmidt Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3391; it has been noted by GNATS. From: Don Schmidt To: Bruce Evans Cc: FreeBSD-gnats-submit@FreeBSD.org, yensid@imsa.edu Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Date: Sat, 26 Apr 1997 02:09:38 -0500 In message <199704260649.QAA29155@godzilla.zeta.org.au>, Bruce Evans writes: >> >>>Description: >> On all current boot disks, on certain 486's (mine, at least) >>after the kernel is loaded, the screen characters turn into unreadable >>gibberish in simply horrid shades of magenta and orange, leaving the >>machine in a unusable state. > >This can't have anything to do with i586 optimizations. There are no i586 Actually, I think there was a version mix-up; I filed the problem report from a system running 2.1.7, I'm having this problem with 2.2 and later. Sorry 'bout that When I posed this problem to the general problems list, I received responses indicating that this was a problem with the 586 optimizations, and the source seems to agree: freebsd-src/sys/i386/isa/npx.c [...] int npxattach(dvp) struct isa_device *dvp; { /* The caller has printed "irq 13" for the npx_irq13 case. */ [...] #ifdef I586_CPU if (cpu_class == CPUCLASS_586 && npx_ex16) { if (!(dvp->id_flags & NPX_DISABLE_I586_OPTIMIZED_BCOPY)) { bcopy_vector = i586_bcopy; ovbcopy_vector = i586_bcopy; } if (!(dvp->id_flags & NPX_DISABLE_I586_OPTIMIZED_BZERO)) bzero = i586_bzero; if (!(dvp->id_flags & NPX_DISABLE_I586_OPTIMIZED_COPYIO)) { copyin_vector = i586_copyin; copyout_vector = i586_copyout; } } #endif [...] ---------- From owner-freebsd-bugs Sat Apr 26 00:50:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA10885 for bugs-outgoing; Sat, 26 Apr 1997 00:50:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA10878; Sat, 26 Apr 1997 00:50:02 -0700 (PDT) Date: Sat, 26 Apr 1997 00:50:02 -0700 (PDT) Message-Id: <199704260750.AAA10878@hub.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3391; it has been noted by GNATS. From: Bruce Evans To: bde@zeta.org.au, yensid@imsa.edu Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Date: Sat, 26 Apr 1997 17:40:35 +1000 >>> On all current boot disks, on certain 486's (mine, at least) >>... >>This can't have anything to do with i586 optimizations. There are no i586 > >Actually, I think there was a version mix-up; I filed the problem report >from a system running 2.1.7, I'm having this problem with 2.2 and later. >Sorry 'bout that Also a CPU mixup? :-) i586 optimizations are not used on 486's. >When I posed this problem to the general problems list, I received responses >indicating that this was a problem with the 586 optimizations, and the >source seems to agree: > >freebsd-src/sys/i386/isa/npx.c >[...] This decides whether the i586 copying optimizations are used. They are only used on i586's, and then only if they aren't disabled. There is no need to recompile without I586_CPU to control them. So if recompiling without i586_CPU makes a difference, then the problem must have nothing to do with known problems with i586 optimizations :-). Bruce From owner-freebsd-bugs Sat Apr 26 01:20:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11508 for bugs-outgoing; Sat, 26 Apr 1997 01:20:02 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11492; Sat, 26 Apr 1997 01:20:01 -0700 (PDT) Resent-Date: Sat, 26 Apr 1997 01:20:01 -0700 (PDT) Resent-Message-Id: <199704260820.BAA11492@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, root@Burka.NetVision.net.il Received: from Burka.NetVision.net.il (root@burka.NetVision.net.il [194.90.1.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11370 for ; Sat, 26 Apr 1997 01:13:21 -0700 (PDT) Received: (from root@localhost) by Burka.NetVision.net.il (8.8.5/8.8.2) id LAA00405; Sat, 26 Apr 1997 11:13:00 +0300 (IDT) Message-Id: <199704260813.LAA00405@Burka.NetVision.net.il> Date: Sat, 26 Apr 1997 11:13:00 +0300 (IDT) From: Mighty Wizard Reply-To: root@Burka.NetVision.net.il To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3392: System panics Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3392 >Category: kern >Synopsis: System panics every few hours >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 26 01:20:00 PDT 1997 >Last-Modified: >Originator: Mighty Wizard >Organization: NetVision Ltd. >Release: FreeBSD 3.0-CURRENT i386 >Environment: I'm running the latest -current (cvsupped 1 day ago). Here is the kernel config: # # BURKA -- my desktop machine # # $Id: BURKA,v 1.1 1995/01/26 11:38:00 gena Exp $ # machine "i386" cpu "I586_CPU" maxusers 20 ident BURKA options INET #InterNETworking options FFS #Berkeley Fast File System options PROCFS #Process File System options DDB options "COMPAT_43" #Compatible with BSD 4.3 options SYSVSHM options SYSVSEM options SYSVMSG options UCONSOLE #X Console support config kernel root on sd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x07 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty flags 0x00 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty flags 0x00 irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ep0 at isa? port 0x300 net irq 10 vector epintr controller pci0 controller ahc1 controller scbus0 device vx0 device sd0 pseudo-device snp 1 #Snoop device - to look at pty/vty/etc.. pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 16 pseudo-device speaker pseudo-device bpfilter 1 #berkeley packet filter And here is dmesg output: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Thu Apr 24 11:08:29 IDT 1997 root@Burka.NetVision.net.il:/usr/src/sys/compile/BURKA CPU: Pentium (90.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 39350272 (38428K bytes) Probing for devices on PCI bus 0: chip0 rev 64 on pci0:0:0 chip1 rev 1 on pci0:1:0 pci0:8: CMD, device=0x0640, class=storage (ide) int a irq 14 [no driver assigned] vga0 rev 0 int a irq ?? on pci0:9:0 vx0 <3COM 3C590 Etherlink III PCI> rev 0 int a irq 9 on pci0:11:0 utp[*utp*] address 00:20:af:f7:f2:dd Warning! Defective early revision adapter! ahc0 rev 0 int a irq 11 on pci0:12:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2069MB (4238836 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: utp[*UTP*] address 00:60:97:23:a2:8b npx0 flags 0x7 on motherboard npx0: INT 16 interface WARNING: / was not properly dismounted. The system has two ethernet cards (ISA - 3C509 and PCI - 3C590). Each card has it's own IP and connected to two physically different networks (ep0-194.90.1.0 vx0-194.90.6.0). Here is the routing table: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default haifa-cs4500-2-e0 UGSc 12 9 ep0 localhost localhost UH 1 16 lo0 194.90.1 link#3 UC 0 0 haifa-cs4500-2-e0 0:60:83:f3:a4:8 UHLW 10 0 ep0 1150 dns 8:0:20:71:91:f5 UHLW 0 94 ep0 1143 netmon 8:0:20:73:37:27 UHLW 0 1 ep0 1178 burka 0:60:97:23:a2:8b UHLW 4 6958 lo0 mx12 0:20:af:b6:7c:63 UHLW 0 21 ep0 1177 mx11 0:0:b0:2:4a:83 UHLW 1 12 ep0 492 ATH 0:aa:0:c8:3b:a4 UHLW 0 0 ep0 1128 aldan 0:20:af:b6:98:9d UHLW 1 12 ep0 1171 194.90.6 link#1 UC 0 0 nvt 8:0:20:71:9e:ed UHLW 0 3 vx0 1114 romeo 0:a0:24:19:fc:1a UHLW 0 0 vx0 1134 routed -q is running. The system acts as a small ftp/http server. It does not work as a router. >Description: For already a long time my system panics every few hours. I'm not sure when exactly it started. The panic is completely unpredictable, it can occur after 1-2 hours, and it can appear after 30-40 hours and it's not related to any specific network (or other) activity. Here is the panic message (copied from the screen, sorry for any mistakes): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1e fault code = supervisor read, page not present instruction pointer = 0x8:0xf014487d stack pointer = 0x10:0xf4136f0c frame pointer = 0x10:0xf4136f1c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0 , pres 1 , def 321 , gran 1 processor eflags = interrupt enabled, resum, IOPL = 0 current process = 4237 (ftpd) interrupt mask = kernel: type 12 trap, code = 0 Stopped at _in_setsockaddr+0x29: movw 0x1e(%esi),%ax -------------------trace-------------- _in_setsockaddr+0x29 _getsockname1+0x71 _getsocknam+0x13 _syscall+0x127 (I compiled kernel with DDB so i will be able to "catch" the message). >How-To-Repeat: There is no reliable way to repeat this. >Fix: I wish i knew, i suspect that it has something to do with multiple card configuration. I'll disable the second card and check if the problem still there. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 26 01:27:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11655 for bugs-outgoing; Sat, 26 Apr 1997 01:27:16 -0700 (PDT) Received: from students.itb.ac.id (root@students.ITB.ac.id [167.205.22.114]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11650 for ; Sat, 26 Apr 1997 01:27:12 -0700 (PDT) Received: from students.itb.ac.id (denisz@students.ITB.ac.id [167.205.22.114]) by students.itb.ac.id (8.8.5/8.7.3) with SMTP id PAA08682 for ; Sat, 26 Apr 1997 15:27:24 +0700 (JVT) Date: Sat, 26 Apr 1997 15:27:24 +0700 (JVT) From: Deni Kurniawan To: freebsd-bugs@hub.freebsd.org In-Reply-To: <199704260710.AAA09686@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubsribe From owner-freebsd-bugs Sat Apr 26 03:10:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15292 for bugs-outgoing; Sat, 26 Apr 1997 03:10:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15286; Sat, 26 Apr 1997 03:10:02 -0700 (PDT) Resent-Date: Sat, 26 Apr 1997 03:10:02 -0700 (PDT) Resent-Message-Id: <199704261010.DAA15286@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, soil@quick.net Received: from jg.dyn.ml.org (soil@newport-1-12.quick.net [207.212.160.212]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA15143 for ; Sat, 26 Apr 1997 03:05:17 -0700 (PDT) Received: (from soil@localhost) by jg.dyn.ml.org (8.8.5/8.8.5) id DAA10236; Sat, 26 Apr 1997 03:05:13 -0700 (PDT) Message-Id: <199704261005.DAA10236@jg.dyn.ml.org> Date: Sat, 26 Apr 1997 03:05:13 -0700 (PDT) From: soil@quick.net Reply-To: soil@quick.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/3393: ``appears'' -> ``appeared'' in several manual pages Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3393 >Category: docs >Synopsis: ``appears'' -> ``appeared'' in several manual pages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 26 03:10:01 PDT 1997 >Last-Modified: >Originator: Josh Gilliam >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: cksum.1 rev 1.1.1.1 id.1 rev 1.1.1.1 kdump.1 rev 1.2 ktrace.1 rev 1.5 logname.1 rev 1.2 mkfifo.1 rev 1.3 nfsstat.1 rev 1.6 shar.1 rev 1.4 tput.1 rev 1.2 yyfix.1 rev 1.1.1.1 >Description: ``appears'' should be changed to ``appeared'' in: cksum.1, line 163 id.1, line 138 kdump.1, line 99 ktrace.1, line 170 logname.1, line 75 mkfifo.1, line 72 nfsstat.1, line 89 shar.1, line 104 tput.1, line 124 yyfix.1, line 111 >How-To-Repeat: man 1 cksum man 1 id man 1 kdump man 1 ktrace man 1 logname man 1 mkfifo man 1 nfsstat man 1 shar man 1 tput man 1 yyfix /HISTORY >Fix: diff -ur usr.bin.orig/cksum/cksum.1 usr.bin/cksum/cksum.1 --- usr.bin.orig/cksum/cksum.1 Fri May 27 05:30:56 1994 +++ usr.bin/cksum/cksum.1 Sat Apr 26 02:28:43 1997 @@ -160,5 +160,5 @@ .Sh HISTORY The .Nm cksum -utility appears in +utility appeared in .Bx 4.4 . diff -ur usr.bin.orig/id/id.1 usr.bin/id/id.1 --- usr.bin.orig/id/id.1 Fri May 27 05:31:44 1994 +++ usr.bin/id/id.1 Sat Apr 26 02:29:19 1997 @@ -135,5 +135,5 @@ .Pp The .Nm -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/kdump/kdump.1 usr.bin/kdump/kdump.1 --- usr.bin.orig/kdump/kdump.1 Thu Sep 19 12:50:44 1996 +++ usr.bin/kdump/kdump.1 Sat Apr 26 02:29:46 1997 @@ -96,5 +96,5 @@ .Sh HISTORY The .Nm kdump -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/ktrace/ktrace.1 usr.bin/ktrace/ktrace.1 --- usr.bin.orig/ktrace/ktrace.1 Sat Mar 15 02:39:09 1997 +++ usr.bin/ktrace/ktrace.1 Sat Apr 26 02:30:16 1997 @@ -167,5 +167,5 @@ .Sh HISTORY The .Nm ktrace -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/logname/logname.1 usr.bin/logname/logname.1 --- usr.bin.orig/logname/logname.1 Sun Feb 11 14:35:14 1996 +++ usr.bin/logname/logname.1 Sat Apr 26 02:30:46 1997 @@ -72,5 +72,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/mkfifo/mkfifo.1 usr.bin/mkfifo/mkfifo.1 --- usr.bin.orig/mkfifo/mkfifo.1 Wed Jan 15 15:25:21 1997 +++ usr.bin/mkfifo/mkfifo.1 Sat Apr 26 02:31:35 1997 @@ -69,5 +69,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/nfsstat/nfsstat.1 usr.bin/nfsstat/nfsstat.1 --- usr.bin.orig/nfsstat/nfsstat.1 Sat Feb 22 11:56:24 1997 +++ usr.bin/nfsstat/nfsstat.1 Sat Apr 26 02:32:06 1997 @@ -86,5 +86,5 @@ .Sh HISTORY The .Nm nfsstat -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/shar/shar.1 usr.bin/shar/shar.1 --- usr.bin.orig/shar/shar.1 Tue Apr 1 11:09:20 1997 +++ usr.bin/shar/shar.1 Sat Apr 26 02:32:46 1997 @@ -101,5 +101,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/tput/tput.1 usr.bin/tput/tput.1 --- usr.bin.orig/tput/tput.1 Wed Apr 2 02:27:25 1997 +++ usr.bin/tput/tput.1 Sat Apr 26 02:33:14 1997 @@ -121,5 +121,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . diff -ur usr.bin.orig/yacc/yyfix.1 usr.bin/yacc/yyfix.1 --- usr.bin.orig/yacc/yyfix.1 Fri May 27 05:33:41 1994 +++ usr.bin/yacc/yyfix.1 Sat Apr 26 02:34:18 1997 @@ -108,5 +108,5 @@ .Sh HISTORY The .Nm -command appears in +command appeared in .Bx 4.4 . >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Apr 26 05:00:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20065 for bugs-outgoing; Sat, 26 Apr 1997 05:00:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20040; Sat, 26 Apr 1997 05:00:02 -0700 (PDT) Date: Sat, 26 Apr 1997 05:00:02 -0700 (PDT) Message-Id: <199704261200.FAA20040@hub.freebsd.org> To: freebsd-bugs Cc: From: John-Mark Gurney Subject: Re: bin/3387: sh mis-interpret the file name / awk failure Reply-To: John-Mark Gurney Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3387; it has been noted by GNATS. From: John-Mark Gurney To: jin@adv-pc-1.lbl.gov Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/3387: sh mis-interpret the file name / awk failure Date: Sat, 26 Apr 1997 04:51:39 -0700 Jin Guojun[ITG] scribbled this message on Apr 25: > >Description: > > In a script, if the variable for a file name had a white space at > the end, the sh will treat it differently when the file name variable > is used at redirected I/O, from used at fopen(). The white space is > interpreted as part of the file name when I/O redirections, such as, > '<', '<<', '>>', and '>' are used. This is a problem for using in > a script. > The FreeBSD awk generates such withe space: > > MyArch=`uname -v | awk -F/ '{printf $NF}` > echo "=$MyArch=" > =GENERIC = > > I am not sure which one is the problem, maybe both. but of course... when you do the MyArch... it will store EXACTLY what awk outputed... and that is with a \n at the end... one simple fix is: MyArch=`uname -v | awk -F/ '{printf("%s", $NF)}'` MyArch=`echo $MyArch` echo "=$MyArch=" the second setting of MyArch eliminates the \n at the end... I had a simlar problem with a script I was writing... it's just that borne shell does EXACTLY what you tell it... :) > >How-To-Repeat: > > For awk problem, see Description above. > Below is the sh issue: > > % more abc > file abc is a testing file > > % more test.script > FILE_NAME="abc " > more < $FILE_NAME > echo "=$FILE_NAME=" > more $FILE_NAME > > % test.script > test.script: cannot open abc : no such file > =abc = > file abc is a testing file this is just as easy... basicly sh does the variable expansion.. then it does the "parsing" of the command line options... if you replaced the second more with: more "$FILE_NAME" you would have the same problem... if you don't have any objections (as this is borne shell's expected behavior), I'll close this.. ttyl.. -- John-Mark Cu Networking Modem/FAX: +1 541 683 6954 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-bugs Sat Apr 26 10:16:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29220 for bugs-outgoing; Sat, 26 Apr 1997 10:16:36 -0700 (PDT) Received: (from pst@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29201; Sat, 26 Apr 1997 10:16:32 -0700 (PDT) Date: Sat, 26 Apr 1997 10:16:32 -0700 (PDT) From: Paul Traina Message-Id: <199704261716.KAA29201@hub.freebsd.org> To: dlowe@sirius.com, pst, freebsd-bugs Subject: Re: bin/2622 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: syslogd '-s' behavior either broken or poorly documented State-Changed-From-To: open-closed State-Changed-By: pst State-Changed-When: Sat Apr 26 10:15:38 PDT 1997 State-Changed-Why: Fixed via a similar patch. From owner-freebsd-bugs Sat Apr 26 16:20:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16084 for bugs-outgoing; Sat, 26 Apr 1997 16:20:02 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16072; Sat, 26 Apr 1997 16:20:01 -0700 (PDT) Date: Sat, 26 Apr 1997 16:20:01 -0700 (PDT) Message-Id: <199704262320.QAA16072@hub.freebsd.org> To: freebsd-bugs Cc: From: Don Schmidt Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Reply-To: Don Schmidt Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/3391; it has been noted by GNATS. From: Don Schmidt To: Bruce Evans Cc: yensid@imsa.edu, FreeBSD-gnats-submit@FreeBSD.org, yensid@postoffice.imsa.edu Subject: Re: kern/3391: Pentium optimizations in default bootdisk breaks some 486's Date: Sat, 26 Apr 1997 18:12:54 -0500 In message <199704260740.RAA30350@godzilla.zeta.org.au>, Bruce Evans writes: >>>> On all current boot disks, on certain 486's (mine, at least) >>>... >>>This can't have anything to do with i586 optimizations. There are no i586 >Also a CPU mixup? :-) i586 optimizations are not used on 486's. > >This decides whether the i586 copying optimizations are used. They are >only used on i586's, and then only if they aren't disabled. There is no >need to recompile without I586_CPU to control them. So if recompiling >without i586_CPU makes a difference, then the problem must have nothing >to do with known problems with i586 optimizations :-). Again, when I first asked for help, It was indicated to me that "586 optimizations caused problems on some 486's" and that I could fix the problem by passing the flag 0x1 to the npx driver, which appears to disable the bzero optimizations. I can't do that, though, because my screen gets mucked up before I can get to the configuration screen. Assuming that this isn't the problem, though, would you have any suggestions as to what is wrong? I just want to be able to boot! :) Thanks! =============================================================================== Don Schmidt Network Systems Administrator yensid@imsa.edu Illinois Math and Science Academy ----------You can build a Mainframe from the things you find at home!----------