From owner-freebsd-bugs Sun Jul 16 03:01:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA16890 for bugs-outgoing; Sun, 16 Jul 1995 03:01:31 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA16860 for ; Sun, 16 Jul 1995 03:01:24 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23551; Sun, 16 Jul 1995 12:01:21 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA00590; Sun, 16 Jul 1995 12:01:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA16040; Sun, 16 Jul 1995 09:01:22 +0200 From: J Wunsch Message-Id: <199507160701.JAA16040@uriah.heep.sax.de> Subject: Re: CDROM Reading "errors" To: tweten@frihet.com Date: Sun, 16 Jul 1995 09:01:21 +0200 (MET DST) Cc: info@cdrom.com, hahn@and.com, bugs@freebsd.org In-Reply-To: <199507131618.JAA15057@tale.frihet.com> from "David E. Tweten" at Jul 13, 95 09:18:39 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1608 Sender: bugs-owner@freebsd.org Precedence: bulk As David E. Tweten wrote: > > Previously, I've never had any trouble reading Rock Ridge format CDROMs from > Walnut Creek. Recently, a friend asked that I try reading a Walnet Creek > Linux CDROM he couldn't get to boot, or to read on MS-Windows. It generated > large volumes of syslog messages on my FreeBSD 1.0.1 and 1.1.5.1 systems. The > same effect now happens with the new FreeBSD 2.0.5 CDROM. A sample of syslog > output follows: > > Jul 13 00:20:23 tale /386bsd: isofs: name '' - type [f177517e/f17751a0]...not > found > Jul 13 00:20:23 tale /386bsd: isofs: 00 00 3c 00 00 00 00 10 00 00 01 00 00 00 > 00 00 : < > Jul 13 00:20:23 tale /386bsd: isofs: 00 00 ff ff ff ff 00 00 00 00 33 33 00 00 > 00 00 : 33 > Jul 13 00:20:23 tale /386bsd: isofs: 00 00 : > Jul 13 00:20:23 tale /386bsd: > Jul 13 00:20:43 tale /386bsd: isofs:RR[5] idflag=0xf153f120 > Jul 13 00:20:43 tale /386bsd: isofs:RR[5] idflag=0xf153f1a2 Looking at the code in FreeBSD 1's isofs handling, there's a bunch of blatant printf's that apparently do nothing and have been omitted in FreeBSD 2's cd9660 file system. Is the CD unreadable, or is it just that the printf's are annoying? If it's really unreadable, the problem must be the ``name '' - type ...'' thingie, the RR[5]'s are benign. From a quick glance over the code, i've got no idea. If it's simply annoying, kill the printf's out of isofs_rrip.c, and recompile your kernel. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Jul 16 03:01:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA16922 for bugs-outgoing; Sun, 16 Jul 1995 03:01:34 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA16876 for ; Sun, 16 Jul 1995 03:01:29 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23559; Sun, 16 Jul 1995 12:01:25 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA00596; Sun, 16 Jul 1995 12:01:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA16282; Sun, 16 Jul 1995 09:18:36 +0200 From: J Wunsch Message-Id: <199507160718.JAA16282@uriah.heep.sax.de> Subject: Re: Help To: mrichards@unog.ch Date: Sun, 16 Jul 1995 09:18:35 +0200 (MET DST) Cc: bugs@FreeBSD.org In-Reply-To: <9507140538.AA28981@ungeneva.unog.ch> from "mrichards@unog.ch" at Jul 14, 95 08:25:00 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1240 Sender: bugs-owner@FreeBSD.org Precedence: bulk As mrichards@unog.ch wrote: > > > We just installed a copy of FreeBSD. The install program was great > but when we reboot the machine we recieve an error message saying that > the floppy is not configured correctly. In order to correct the > problem the set-up program must be run twice. First it must be set to > a non matching disk i.e.(360k) then reset it back to a 1.44 meg 3.5 > in. this allows us to reboot the machine with a dos diskette but when > we reboot with freebsd the same problem occurs. The PC is an AST > Premmia 4/66. When I tried to run sysinstall from the hd the I > received a message that said that there was no floppy in the 1.2 meg > drive. The program must be reconfiguring the set-up to a 1.2 meg > drive. I don't get the picture, sorry. Can you quote any messages, e.g. from the second virtual screen (Alt-F2), _literally_ here? Can you also quote all messages related to fdc0 and fd0 when the system is booting? (Remember, you can scroll back through those messages by hitting ScrLck and PgUp.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Jul 16 03:13:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA18667 for bugs-outgoing; Sun, 16 Jul 1995 03:13:50 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA18651 ; Sun, 16 Jul 1995 12:13:48 +0200 Date: Sun, 16 Jul 1995 12:13:48 +0200 From: Joerg Wunsch Message-Id: <199507161013.MAA18651@freefall.cdrom.com> To: jdp@polstra.com, joerg, freebsd-bugs Subject: Changed information for PR conf/620 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Default /etc/hosts.equiv causes rsh/rlogin hangups State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sun Jul 16 12:12:43 MET DST 1995 State-Changed-Why: ruserok() now fixed to accept comments starting in column 1, fix appeared in /home/ncvs/src/lib/libc/net/rcmd.c,v <-- rcmd.c new revision: 1.4; previous revision: 1.3 From owner-freebsd-bugs Sun Jul 16 04:16:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA21336 for bugs-outgoing; Sun, 16 Jul 1995 04:16:13 -0700 Received: from tale.frihet.com (root@ns.frihet.com [165.227.57.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA21329 for ; Sun, 16 Jul 1995 04:16:11 -0700 Received: from localhost.frihet.com (tweten@localhost.frihet.com [127.0.0.1]) by tale.frihet.com (8.6.10/8.6.6) with SMTP id EAA02268; Sun, 16 Jul 1995 04:14:58 -0700 Message-Id: <199507161114.EAA02268@tale.frihet.com> X-Authentication-Warning: tale.frihet.com: Host localhost.frihet.com didn't use HELO protocol X-Mailer: exmh version 1.5.3 12/28/94 Reply-To: "David E. Tweten" To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: info@cdrom.com, hahn@and.com, bugs@freebsd.org Subject: Re: CDROM Reading "errors" Date: Sun, 16 Jul 1995 04:14:58 -0700 From: "David E. Tweten" Sender: bugs-owner@freebsd.org Precedence: bulk Joerg Wunsch wrote: > Is the CD unreadable, or is it just that the printf's are annoying? CD reads seem to work in spite of the flood of syslog messages, though my testing isn't exhaustive. I can trash the printfs, but it struck me as odd that this sort of thing has never been a problem reading any other Rock Ridge CDs. The two Walnut Creek CDs (Linux and FreeBSD 2.0.5) are the first, and so far only CDs to have the problem. -- David E. Tweten | PGP Key fingerprint = | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 The only flags worth saluting are those you are permitted to burn. From owner-freebsd-bugs Sun Jul 16 05:31:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA22483 for bugs-outgoing; Sun, 16 Jul 1995 05:31:32 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA22476 for ; Sun, 16 Jul 1995 05:31:29 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA26690; Sun, 16 Jul 1995 14:31:25 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA01375; Sun, 16 Jul 1995 14:31:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id NAA18993; Sun, 16 Jul 1995 13:39:06 +0200 From: J Wunsch Message-Id: <199507161139.NAA18993@uriah.heep.sax.de> Subject: Re: CDROM Reading "errors" To: tweten@frihet.com Date: Sun, 16 Jul 1995 13:39:05 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, info@cdrom.com, hahn@and.com, bugs@freebsd.org In-Reply-To: <199507161114.EAA02268@tale.frihet.com> from "David E. Tweten" at Jul 16, 95 04:14:58 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1859 Sender: bugs-owner@freebsd.org Precedence: bulk As David E. Tweten wrote: > > Joerg Wunsch wrote: > > Is the CD unreadable, or is it just that the printf's are annoying? > > CD reads seem to work in spite of the flood of syslog messages, though my > testing isn't exhaustive. I can trash the printfs, but it struck me as odd > that this sort of thing has never been a problem reading any other Rock Ridge > CDs. The two Walnut Creek CDs (Linux and FreeBSD 2.0.5) are the first, and so > far only CDs to have the problem. They seem to be ignored now. This is the 1.1 code: /* * Flag indicating * Nothing to do.... */ static int isofs_rrip_idflag( p, ana ) ISO_RRIP_IDFLAG *p; ISO_RRIP_ANALYZE *ana; { char buf[3]; buf[0] = p->h.type[0]; buf[1] = p->h.type[1]; buf[2] = 0x00; printf("isofs:%s[%d] idflag=0x%x\n", buf, isonum_711(p->h.length), p->flags ); return 0; } ...and this is from 2.2-current: /* * Flag indicating */ static int cd9660_rrip_idflag(p,ana) ISO_RRIP_IDFLAG *p; ISO_RRIP_ANALYZE *ana; { ana->fields &= isonum_711(p->flags)|~0xff; /* don't touch high bits */ /* special handling of RE field */ if (ana->fields&ISO_SUSP_RELDIR) return cd9660_rrip_reldir(p,ana); return ISO_SUSP_IDFLAG; } (Relocated directories seem to be handled in another piece of code in 1.1, or there's simply a bug.) Note that there are a few more ``Nothing to do...'' functions in the 1.1 code that might issue blatant printf's. I don't have the time to look into the CD9600 standard right now in order to see what the RR's might be for. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Jul 16 06:09:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA23554 for bugs-outgoing; Sun, 16 Jul 1995 06:09:01 -0700 Received: from haywire.DIALix.COM (peter@haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA23547 for ; Sun, 16 Jul 1995 06:08:57 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id VAA09209; Sun, 16 Jul 1995 21:08:52 +0800 Date: Sun, 16 Jul 1995 21:08:52 +0800 (WST) From: Peter Wemm To: bugs@freebsd.org Subject: oops! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk I just got this about when having a pppd carrier drop... Data modified on freelist: word 0 of object 0xf0a5e040 size 36 previous type in_multi (0xf0a78280 != 0xdeadc0de) I seem to recall this occurring before I started messing with ppp-2.2, (I've only just re-enabled options DIAGNOSTIC, as I don't have time for doom.. :-) This is on a very recent -current system (36 hours since last sup+build). Is there still work-in-progress in this area (I presume interface cleaning is the culprit) or should I start looking? -Peter From owner-freebsd-bugs Sun Jul 16 06:20:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA23885 for bugs-outgoing; Sun, 16 Jul 1995 06:20:21 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA23879 for ; Sun, 16 Jul 1995 06:20:19 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id GAA14084; Sun, 16 Jul 1995 06:19:41 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id GAA00173; Sun, 16 Jul 1995 06:20:52 -0700 Message-Id: <199507161320.GAA00173@corbin.Root.COM> To: Peter Wemm cc: bugs@freebsd.org Subject: Re: oops! In-reply-to: Your message of "Sun, 16 Jul 95 21:08:52 +0800." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 16 Jul 1995 06:20:50 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk >I just got this about when having a pppd carrier drop... > >Data modified on freelist: word 0 of object 0xf0a5e040 size 36 > previous type in_multi (0xf0a78280 != 0xdeadc0de) > >I seem to recall this occurring before I started messing with ppp-2.2, >(I've only just re-enabled options DIAGNOSTIC, as I don't have time for >doom.. :-) > >This is on a very recent -current system (36 hours since last sup+build). > >Is there still work-in-progress in this area (I presume interface >cleaning is the culprit) or should I start looking? There aren't any known bugs that would cause this in -current. Good luck finding it! :-) -DG From owner-freebsd-bugs Sun Jul 16 10:57:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02588 for bugs-outgoing; Sun, 16 Jul 1995 10:57:58 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02582 ; Sun, 16 Jul 1995 10:57:56 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id KAA20814; Sun, 16 Jul 1995 10:57:21 -0700 Message-Id: <199507161757.KAA20814@time.cdrom.com> To: "David E. Tweten" cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), info@cdrom.com, hahn@and.com, bugs@freebsd.org Subject: Re: CDROM Reading "errors" In-reply-to: Your message of "Sun, 16 Jul 1995 04:14:58 PDT." <199507161114.EAA02268@tale.frihet.com> Date: Sun, 16 Jul 1995 10:57:21 -0700 From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > testing isn't exhaustive. I can trash the printfs, but it struck me as odd > that this sort of thing has never been a problem reading any other Rock Ridge > CDs. The two Walnut Creek CDs (Linux and FreeBSD 2.0.5) are the first, and so I used to be able to reproduce this under 1.x with all sorts of CDs. You just don't have a big enough collectin.. :-) Jordan From owner-freebsd-bugs Sun Jul 16 11:40:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA03519 for bugs-outgoing; Sun, 16 Jul 1995 11:40:17 -0700 Received: from tale.frihet.com (root@ns.frihet.com [165.227.57.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA03513 for ; Sun, 16 Jul 1995 11:40:15 -0700 Received: from localhost.frihet.com (tweten@localhost.frihet.com [127.0.0.1]) by tale.frihet.com (8.6.10/8.6.6) with SMTP id LAA01967; Sun, 16 Jul 1995 11:39:14 -0700 Message-Id: <199507161839.LAA01967@tale.frihet.com> X-Authentication-Warning: tale.frihet.com: Host localhost.frihet.com didn't use HELO protocol X-Mailer: exmh version 1.5.3 12/28/94 Reply-To: "David E. Tweten" To: "Jordan K. Hubbard" cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), info@cdrom.com, hahn@and.com, bugs@freebsd.org Subject: Re: CDROM Reading "errors" Date: Sun, 16 Jul 1995 11:39:14 -0700 From: "David E. Tweten" Sender: bugs-owner@freebsd.org Precedence: bulk Jordan K. Hubbard srites: > I used to be able to reproduce this under 1.x with all sorts of CDs. You > just don't have a big enough collectin.. :-) Okay. I surrender. Printf's trashed. Now, to begin actually to use the Walnet Creek 2.0.5 CDROM to replace my historical curiosity operating systems! -- David E. Tweten | PGP Key fingerprint = | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 The only flags worth saluting are those you are permitted to burn. From owner-freebsd-bugs Sun Jul 16 11:51:40 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA04113 for bugs-outgoing; Sun, 16 Jul 1995 11:51:40 -0700 Received: (from mpp@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA04098 ; Sun, 16 Jul 1995 11:51:38 -0700 Date: Sun, 16 Jul 1995 11:51:38 -0700 From: Mike Pritchard Message-Id: <199507161851.LAA04098@freefall.cdrom.com> To: mpp@legarto.minn.net, mpp, freebsd-bugs Subject: Changed information for PR bin/603 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: chpass screws up password change/expire fields State-Changed-From-To: open-closed State-Changed-By: mpp State-Changed-When: Sun Jul 16 11:49:31 PDT 1995 State-Changed-Why: Fixed in revision 1.3 of chpass/util.c. From owner-freebsd-bugs Sun Jul 16 20:14:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA23098 for bugs-outgoing; Sun, 16 Jul 1995 20:14:55 -0700 Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA23089 for ; Sun, 16 Jul 1995 20:14:52 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <07682-0@bunyip.cc.uq.oz.au>; Mon, 17 Jul 1995 13:14:21 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id NAA08975 for ; Mon, 17 Jul 1995 13:18:52 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id DAA23394 for ; Mon, 17 Jul 1995 03:16:07 GMT Message-Id: <199507170316.DAA23394@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: bugs@freebsd.org Subject: i386/337 fixed. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jul 1995 13:16:06 +1000 From: Stephen Hocking Sender: bugs-owner@freebsd.org Precedence: bulk Last lot of patches that went into -current on seagate.c appear to have fixed this hang for me. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-bugs Sun Jul 16 21:39:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA28391 for bugs-outgoing; Sun, 16 Jul 1995 21:39:49 -0700 Received: (from peter@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA28374 ; Sun, 16 Jul 1995 21:39:48 -0700 Date: Sun, 16 Jul 1995 21:39:48 -0700 From: Peter Wemm Message-Id: <199507170439.VAA28374@freefall.cdrom.com> To: ken@wc206.residence.gatech.edu, peter, freebsd-bugs Subject: Changed information for PR bin/578 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: w -h doesn't suppress "USER TTY"...etc. State-Changed-From-To: open-closed State-Changed-By: peter State-Changed-When: Sun Jul 16 21:38:52 PDT 1995 State-Changed-Why: Suggested fix applied in rev 1.6 of w.c From owner-freebsd-bugs Mon Jul 17 00:35:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA09258 for bugs-outgoing; Mon, 17 Jul 1995 00:35:00 -0700 Received: from mercury.unt.edu (mercury.unt.edu [129.120.1.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA09246 ; Mon, 17 Jul 1995 00:34:57 -0700 Received: from gab.unt.edu by mercury.unt.edu with SMTP id AB12801 (5.65c/IDA-1.4.4); Fri, 14 Jul 1995 08:28:52 -0500 Received: from GAB/SpoolDir by gab.unt.edu (Mercury 1.13); Fri, 14 Jul 95 8:28:52 CST6CDT Received: from SpoolDir by GAB (Mercury 1.13); Fri, 14 Jul 95 8:28:43 CST6CDT From: "John Booth" Organization: University of North Texas To: hackers@freebsd.org, bugs@freebsd.org Date: Fri, 14 Jul 1995 08:28:40 CST6CDT Subject: Adaptec 2940 w/hp dat drives, freeze machine Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: <895FA01E2D@gab.unt.edu> Sender: bugs-owner@freebsd.org Precedence: bulk 3 times a charm? This 3rd time I've sent to hackers@freebsd.org and I haven't seen it appear on the list....we still receive messages we send correct? Guess will see if it appears on bug list. ------- Forwarded Message Follows ------- X-cs: From: Self To: hackers@freebsd.org Subject: Adaptec 2940 w/hp dat drives, freeze machine Date: Thu, 13 Jul 1995 12:40:34 I didn't see this message get to the list. Just started using tape devices w/this machine. After doing a mt status, then mt erase, then mt erase here's what got logged. Jul 11 14:59:38 www /kernel: ahc0: target 1, lun 0 (st0) timed out 14:59:38 www /kernel: st0(ahc0:1:0): command: 19,1,0,0,0,0-[0 bytes] Jul 11 14:59:38 www /kernel: Jul 11 15:02:33 www /kernel: ep0: Status: 2002 Jul 11 15:06:41 www /kernel: ep0: Status: 2002 Jul 11 15:07:01 www /kernel: ahc0: target 1, lun 0 (st0) timed out 15:07:01 www /kernel: st0(ahc0:1:0): command: 0,0,0,0,0,0-[0 bytes] Jul 11 15:07:01 www /kernel: Jul 11 15:08:00 www /kernel: ahc0: target 5, lun 0 (sd0) timed out Jul 11 15:08:00 www /kernel: sd0(ahc0:5:0): command: 28,0,0,24,3a,f0,0,0,10,0-[8192 bytes] Jul 11 15:08:00 www /kernel: ------------------------------ www /kernel: 000: 6e 6f 62 6f 64 79 00 2a 00 00 55 6e 70 72 69 76 www /kernel: 016: 69 6c 65 67 65 64 20 75 73 65 72 00 2f 6e 6f 6e www /kernel: 032: 65 78 69 73 74 65 6e 74 00 2f 6e 6f 6e 65 78 69 www /kernel: 048: 73 74 65 6e 74 00 2f 72 6f 6f 74 00 2f 75 73 72 Jul 11 15:08:00 www /kernel: ------------------------------ Jul 11 15:08:00 www /kernel: Jul 11 15:08:41 www /kernel: ahc0: target 1, lun 0 (st0) timed out 15:08:41 www /kernel: st0(ahc0:1:0): command: 0,0,0,0,0,0-[0 bytes] Jul 11 15:08:41 www /kernel: machine machine just dies. No panic, just stop responding. Will ping, but no telnet. Can switch virtual terms ok....went into kernel debugger and it was doing scsi operations. Mt was donig wmesg was scsicmd-- also there were time outs for the devices. I put it in kernel debugger, did about 5-20 nexts and it got Page-Fault 12 supervisor read. I have done this about 3 times in a row, is easy to replicate. Here's dmesg FreeBSD 2.0.5-RELEASE #0: Tue Jul 11 12:46:23 1995 john@www.cas.unt.edu:/usr/src/sys/compile/www CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping=4 Features=0x1bf real memory = 33161216 (8096 pages) avail memory = 31182848 (7613 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ahc0 not found wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 3 3C5x9 board(s) on ISA found at 0x300 0x200 0x220 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/bnc/utp[*BNC*] address 00:20:af:38:54:e6 irq 10 ep1 at 0x200-0x20f irq 3 on isa ep1: aui/bnc/utp[*BNC*] address 00:20:af:9e:19:7e irq 3 ep2 at 0x220-0x22f irq 5 on isa ep2: aui/bnc/utp[*BNC*] address 00:20:af:9e:19:98 irq 5 npx0 on motherboard npx0: INT 16 interface Probing for devices on the pci0 bus: configuration mode 2 allows 16 devices. chip0 rev 17 on pci0:0 chip1 rev 67 on pci0:2 ahc0 rev 0 int a irq 9 on pci0:6 ahc0: reading board settings ahc0: 294x Single Channel, SCSI Id=7, aic7870, 16 SCBs ahc0: Downloading Sequencer Program...Done ahc0: Probing channel A ahc0: target 1 synchronous at 5.0MB/s, offset = 0x8 (ahc0:1:0): "HP HP35480A 1109" type 1 removable SCSI 2 st0(ahc0:1:0): Sequential-Access density code 0x13, drive empty ahc0: target 2 synchronous at 5.0MB/s, offset = 0x8 (ahc0:2:0): "HP HP35480A 1009" type 1 removable SCSI 2 st1(ahc0:2:0): Sequential-Access density code 0x13, drive empty ahc0: target 3 synchronous at 5.0MB/s, offset = 0x8 (ahc0:3:0): "HP HP35480A 1009" type 1 removable SCSI 2 st2(ahc0:3:0): Sequential-Access density code 0x13, drive empty ahc0: target 4 synchronous at 5.0MB/s, offset = 0x8 (ahc0:4:0): "HP HP35480A 9 09" type 1 removable SCSI 2 st3(ahc0:4:0): Sequential-Access density code 0x13, drive empty ahc0: target 5 synchronous at 5.0MB/s, offset = 0x8 ahc0: target 5 Tagged Queuing Device (ahc0:5:0): "HP C2490A-300 4140" type 0 fixed SCSI 2 sd0(ahc0:5:0): Direct-Access 2033MB (4165272 512 byte sectors) sd0(ahc0:5:0): with 2630 cyls, 18 heads, and an average 87 sectors/track vga0 rev 0 int a irq 255 on pci0:12 pci0: uses 4096 bytes of memory from ffbff000 upto ffbfffff. pci0: uses 256 bytes of I/O space from fc00 upto fcff. WARNING: / was not properly dismounted. sd0: raw partition size != slice size sd0: start 0, end 4165271, size 4165272 sd0c: start 0, end 4294967295, size 0 sd0: raw partition size != slice size sd0: start 0, end 4165271, size 4165272 sd0c: start 0, end 4294967295, size 0 ---------------------------------------------------------------------- College of Arts & Sciences Computing Services John A. Booth, john@gab.unt.edu From owner-freebsd-bugs Mon Jul 17 02:11:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA17114 for bugs-outgoing; Mon, 17 Jul 1995 02:11:43 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA17101 for ; Mon, 17 Jul 1995 02:11:31 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from sirius.physik.fu-berlin.de (130.133.3.140) with smtp id ; Mon, 17 Jul 95 11:11 MEST Received: by sirius.physik.fu-berlin.de; id AA26972; Mon, 17 Jul 1995 11:10:52 +0200 From: Thomas Graichen Message-Id: <9507170910.AA26972@sirius.physik.fu-berlin.de> Subject: mcd0: timeout getreply To: bugs@freebsd.org Date: Mon, 17 Jul 1995 11:10:52 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1073 Sender: bugs-owner@freebsd.org Precedence: bulk hello i always get a "mcd0: timeout getreply" then halting the machine (after the syncing disks line is printed) - two questions: * why i get this ? * i it possible to change it in the kernel sources generally by: - changing the default DELAY_GETREPLY to a higher value (i think this should solve it - or am i wrong - i'll try it) - or better - make it configurable via the config file by changing #define DELAY_GETREPLY 1500000 to #if !defined(DELAY_GETREPLY) #define DELAY_GETREPLY 1500000 #endif thanks in advance - t _______________________________________________________||_____________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| ___________________________||____email: graichen@omega.physik.fu-berlin.de____ From owner-freebsd-bugs Mon Jul 17 02:26:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA18024 for bugs-outgoing; Mon, 17 Jul 1995 02:26:04 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA18010 for ; Mon, 17 Jul 1995 02:26:00 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id CAA01207; Mon, 17 Jul 1995 02:25:24 -0700 From: "Rodney W. Grimes" Message-Id: <199507170925.CAA01207@gndrsh.aac.dev.com> Subject: Re: mcd0: timeout getreply To: graichen@sirius.physik.fu-berlin.de (Thomas Graichen) Date: Mon, 17 Jul 1995 02:25:24 -0700 (PDT) Cc: bugs@freebsd.org In-Reply-To: <9507170910.AA26972@sirius.physik.fu-berlin.de> from "Thomas Graichen" at Jul 17, 95 11:10:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1130 Sender: bugs-owner@freebsd.org Precedence: bulk > > hello > > i always get a "mcd0: timeout getreply" then halting the machine (after the > syncing disks line is printed) - two questions: > > * why i get this ? I am not sure, never having played with a mcd0 type drive :-(. > * i it possible to change it in the kernel sources generally by: > > - changing the default DELAY_GETREPLY to a higher value (i think this should > solve it - or am i wrong - i'll try it) Please try this and let us know if that fixed the problem. If you can make the problem go away with say a value of 15000000 (ie, 10x what it is now) please do a binary search for the value that just makes it work and send that to us. > - or better - make it configurable via the config file by changing > > #define DELAY_GETREPLY 1500000 > > to > > #if !defined(DELAY_GETREPLY) > #define DELAY_GETREPLY 1500000 > #endif I'd rather not, we want to eliminate config and kernel options like this, not make more of them. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Mon Jul 17 03:17:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA21573 for bugs-outgoing; Mon, 17 Jul 1995 03:17:54 -0700 Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA21563 for ; Mon, 17 Jul 1995 03:17:48 -0700 Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.11/8.6.9) id MAA29201 for bugs@freebsd.org; Mon, 17 Jul 1995 12:17:44 +0200 From: Thomas Gellekum Message-Id: <199507171017.MAA29201@ghpc6.ihf.rwth-aachen.de> Subject: add setlocale() to more(1) To: bugs@freebsd.org Date: Mon, 17 Jul 1995 12:17:43 +0200 (MET DST) Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 592 Sender: bugs-owner@freebsd.org Precedence: bulk Moin, I have added a call to setlocale() to more(1) to make it aware of different character encodings. The patch is attached below. tg *** /usr/src/usr.bin/more/main.c.orig Fri May 27 14:30:45 1994 --- /usr/src/usr.bin/more/main.c Sun Jul 16 10:48:53 1995 *************** *** 51,56 **** --- 51,57 ---- #include #include #include + #include int ispipe; int new_file; *************** *** 295,300 **** --- 296,303 ---- exit(0); } + setlocale(LC_CTYPE, ""); + raw_mode(1); get_term(); open_getchr(); From owner-freebsd-bugs Mon Jul 17 05:22:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA27749 for bugs-outgoing; Mon, 17 Jul 1995 05:22:54 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA27742 for ; Mon, 17 Jul 1995 05:22:49 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id NAA05146; Mon, 17 Jul 1995 13:23:41 +0100 Date: Mon, 17 Jul 1995 13:23:40 +0100 (BST) From: Doug Rabson To: Matt Dillon cc: bugs@freebsd.org Subject: Re: More on NFS bug... can be reproduced with dd In-Reply-To: <199507150240.TAA26207@blob.best.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk On Fri, 14 Jul 1995, Matt Dillon wrote: > dd if=bigfile of=outfile bs=1536 > > Where if and of are both on an NFS mounted filesystem seems to reproduce > the bug. Is is possible that this might be fixed by the recent change to vfs_bio? Can you reproduce it with that fix in place? -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-bugs Mon Jul 17 06:52:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA00396 for bugs-outgoing; Mon, 17 Jul 1995 06:52:47 -0700 Received: from deep-thought.demos.su (root@deep-thought.demos.su [192.91.186.133]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA00390 for ; Mon, 17 Jul 1995 06:52:42 -0700 Received: by deep-thought.demos.su id RAA00516; (8.6.11/D) Mon, 17 Jul 1995 17:42:55 +0400 To: bugs@freebsd.org, Thomas Gellekum References: <199507171017.MAA29201@ghpc6.ihf.rwth-aachen.de> In-Reply-To: <199507171017.MAA29201@ghpc6.ihf.rwth-aachen.de>; from Thomas Gellekum at Mon, 17 Jul 1995 12:17:43 +0200 (MET DST) Message-ID: Organization: DEMOS Date: Mon, 17 Jul 1995 17:42:54 +0400 (MSD) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: add setlocale() to more(1) Lines: 29 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 821 Sender: bugs-owner@freebsd.org Precedence: bulk In message <199507171017.MAA29201@ghpc6.ihf.rwth-aachen.de> Thomas Gellekum writes: >Moin, >I have added a call to setlocale() to more(1) to make it aware of >different character encodings. The patch is attached below. >+ setlocale(LC_CTYPE, ""); >+ Please, never do such things, reasons list: 1) 'More' limited to 8bit chars only, so setlocale here cause it break all rune (16bit) chars. Supporting of 16bit chars require total 'more' rewritting. 2) Support for 8bit chars already exists, but activates differently: all you need to do setenv ENABLE_STARTUP_LOCALE Check /etc/sysconfig for more detailed example. -- Andrey A. Chernov : ache@FreeBSD.org : From 33th IETF FidoNet: 2:5020/230.3 : Stockholm RELCOM Team,FreeBSD Team : From owner-freebsd-bugs Mon Jul 17 08:16:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA05066 for bugs-outgoing; Mon, 17 Jul 1995 08:16:00 -0700 Received: (from wollman@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA05051 ; Mon, 17 Jul 1995 08:15:59 -0700 Date: Mon, 17 Jul 1995 08:15:59 -0700 From: "Garrett A. Wollman" Message-Id: <199507171515.IAA05051@freefall.cdrom.com> To: jmb@kryten.Atinc.COM, wollman, freebsd-bugs Subject: Changed information for PR kern/619 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: incorrect error code from SIOCAIFADDR ioctl on p2p interface State-Changed-From-To: open-closed State-Changed-By: wollman State-Changed-When: Mon Jul 17 08:15:28 PDT 1995 State-Changed-Why: Suggested fix applied: /home/ncvs/src/sys/netinet/in.c,v <-- in.c new revision: 1.15; previous revision: 1.14 done From owner-freebsd-bugs Mon Jul 17 10:14:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA11115 for bugs-outgoing; Mon, 17 Jul 1995 10:14:51 -0700 Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA11087 for ; Mon, 17 Jul 1995 10:14:43 -0700 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.144.4]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id TAA11510 for ; Mon, 17 Jul 1995 19:06:08 +0200 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.12/8.6.9) id TAA18552; Mon, 17 Jul 1995 19:06:01 +0200 Date: Mon, 17 Jul 1995 19:06:01 +0200 Message-Id: <199507171706.TAA18552@caramba.cs.tu-berlin.de> To: bugs@freebsd.org Subject: /usr/share/perl/dialog.ph MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: bugs-owner@freebsd.org Precedence: bulk $ perl -cw dialog.ph syntax error in file dialog.ph at line 21, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 22, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 23, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 24, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 25, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 26, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 27, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 28, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 29, next 2 tokens "\attributes[" syntax error in file dialog.ph at line 30, next 2 tokens "\attributes[" dialog.ph has too many errors. Solution: $ sed 's/\&attributes\[/$attributes[/' dialog.ph > dialog.ph.new $ mv dialog.ph.new dialog.ph Wolfram From owner-freebsd-bugs Mon Jul 17 14:04:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA23558 for bugs-outgoing; Mon, 17 Jul 1995 14:04:02 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA23489 for ; Mon, 17 Jul 1995 14:03:27 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id XAA01044 for ; Mon, 17 Jul 1995 23:00:31 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id XAA01464 for ; Mon, 17 Jul 1995 23:00:30 +0200 Message-Id: <199507172100.XAA01464@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: bugs@freebsd.org Subject: Inconsistency in the headers? Date: Mon, 17 Jul 1995 23:00:30 +0200 From: Mark Murray Sender: bugs-owner@freebsd.org Precedence: bulk Hi I am checking out some code, and I keep on getting this: > for i in des md idea rc4 lhash error rsa ssl ; do (cd $i; echo "making $i..."; make CC=gcc CFLAG='-O3 -DPROTO' INSTALLTOP='/usr/local/ssl' PEX_LIBS='' EX_LIBS='' all ); done; > making des... > gcc -DRAND -O3 -DPROTO -c read_pwd.c > In file included from read_pwd.c:13: > /usr/include/signal.h:45: conflicting types for `sys_siglist' > /usr/include/unistd.h:136: previous declaration of `sys_siglist' > /usr/include/signal.h:70: conflicting types for `psignal' > /usr/include/unistd.h:135: previous declaration of `psignal' > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. It looks like our headers are inconsistent? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Mon Jul 17 18:23:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03953 for bugs-outgoing; Mon, 17 Jul 1995 18:23:06 -0700 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA03947 for ; Mon, 17 Jul 1995 18:23:03 -0700 Received: by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02) id AA24179; Mon, 17 Jul 1995 21:22:25 -0400 Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.11/8.6.5) with ESMTP id UAA00168; Mon, 17 Jul 1995 20:39:25 -0400 Received: (from rivers@localhost) by lakes (8.6.11/8.6.9) id UAA03372; Mon, 17 Jul 1995 20:42:20 -0400 Date: Mon, 17 Jul 1995 20:42:20 -0400 From: Thomas David Rivers Message-Id: <199507180042.UAA03372@lakes> To: uriah.heep.sax.de!joerg_wunsch@dg-rtp.dg.com, freebsd-bugs@freebsd.org Subject: Re: make doesn't like lines with a tab only Sender: bugs-owner@freebsd.org Precedence: bulk joerg_wunsch@uriah.heep.sax.de wrote: > As Mats Lofkvist wrote: > > > > > > the following "Makefile" > > --SNIP-- > > foo: bar > > xyzzy -o foo bar > > > > --SNIP-- > > > > results in: > > "Makefile", line 3: Need an operator > > Fatal errors encountered -- cannot continue > > What semantics would you imply with this Makefile? Since a leading > TAB is taken to be as a line with shell commands, but there's no > command at all, i wouldn't care to accept this as a "bug"... > > (I.e., it doesn't bother me too much which error message i'm getting > for a bogus Makefile.) > > -- I didn't say anything when this was discussed, because I agreed with Joerg's approach... However, I keep running into "standard/portable" makefiles that insist on doing this. After I ran into the fifth such makefile - I've changed my mind on this - and would now argue that we need to re-instate the previous behavior, just for ease of use. - Dave Rivers - From owner-freebsd-bugs Mon Jul 17 19:44:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA05769 for bugs-outgoing; Mon, 17 Jul 1995 19:44:11 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA05763 for ; Mon, 17 Jul 1995 19:44:09 -0700 Received: (root@localhost) by blob.best.net (8.6.12/8.6.5) id TAA27458; Mon, 17 Jul 1995 19:44:07 -0700 Date: Mon, 17 Jul 1995 19:44:07 -0700 From: Matt Dillon Message-Id: <199507180244.TAA27458@blob.best.net> To: bugs@freebsd.org Subject: core dumps don't include anonymous memory that has been mmap()'d Sender: bugs-owner@freebsd.org Precedence: bulk This is one for the TODO I suppose. It would be nice if anonymously mapped memory showed up in the core dumps, but I'm not holding my breath! -Matt From owner-freebsd-bugs Mon Jul 17 22:36:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09865 for bugs-outgoing; Mon, 17 Jul 1995 22:36:49 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA09859 for ; Mon, 17 Jul 1995 22:36:48 -0700 Received: (root@localhost) by blob.best.net (8.6.12/8.6.5) id WAA09284; Mon, 17 Jul 1995 22:36:43 -0700 Date: Mon, 17 Jul 1995 22:36:43 -0700 From: Matt Dillon Message-Id: <199507180536.WAA09284@blob.best.net> To: dfr@render.com Cc: bugs@freebsd.org Subject: Re: More on NFS bug... can be reproduced with dd Sender: bugs-owner@freebsd.org Precedence: bulk Yes, the allocbuf() patch did the trick! -Matt >On Fri, 14 Jul 1995, Matt Dillon wrote: > >> dd if=bigfile of=outfile bs=1536 >> >> Where if and of are both on an NFS mounted filesystem seems to reproduce >> the bug. > >Is is possible that this might be fixed by the recent change to vfs_bio? >Can you reproduce it with that fix in place? > >-- >Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com > Phone: +44 171 251 4411 > FAX: +44 171 251 0939 > > From owner-freebsd-bugs Tue Jul 18 01:56:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA16908 for bugs-outgoing; Tue, 18 Jul 1995 01:56:09 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA16890 ; Tue, 18 Jul 1995 01:56:01 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA05328; Tue, 18 Jul 1995 18:40:13 +0930 From: Michael Smith Message-Id: <199507180910.SAA05328@genesis.atrad.adelaide.edu.au> Subject: Re: Need help for FreeBSD To: vuong@jrtc169.ds.cubic.com (Tan Vuong) Date: Tue, 18 Jul 1995 18:40:13 +0930 (CST) Cc: hackers@freebsd.org, bugs@freebsd.org, questions@freebsd.org In-Reply-To: <9507142048.AA04570@jrtc134.> from "Tan Vuong" at Jul 14, 95 01:48:49 pm Content-Type: text Content-Length: 770 Sender: bugs-owner@freebsd.org Precedence: bulk Tan Vuong stands accused of saying: > Problem: When extracting FreeBSD 2.0. Solution : Return the FreeBSD 2.0 CDrom and exchange for the 2.0.5 CD. > Can not extract Xfree86-3.1: > See the message "Verify checksum..." > and then "Extract ....". But the system hang forever. > Try two different CD. The same problem. Hit Alt-F2. > Tan Vuong -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[ From owner-freebsd-bugs Tue Jul 18 06:23:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA27092 for bugs-outgoing; Tue, 18 Jul 1995 06:23:04 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA27063 ; Tue, 18 Jul 1995 06:22:59 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id GAA05217; Tue, 18 Jul 1995 06:22:21 -0700 Message-Id: <199507181322.GAA05217@time.cdrom.com> To: Michael Smith cc: vuong@jrtc169.ds.cubic.com (Tan Vuong), hackers@freebsd.org, bugs@freebsd.org, questions@freebsd.org Subject: Re: Need help for FreeBSD In-reply-to: Your message of "Tue, 18 Jul 1995 18:40:13 +0930." <199507180910.SAA05328@genesis.atrad.adelaide.edu.au> Date: Tue, 18 Jul 1995 06:22:20 -0700 From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > Solution : Return the FreeBSD 2.0 CDrom and exchange for the 2.0.5 CD. He doesn't even have to return the CD. Walnut Creek has a new policy: If you want to "return" one of our CDs, just call and ask and we'll send you a new one. You do NOT have to send us back your old one! We trust you.. Jordan From owner-freebsd-bugs Tue Jul 18 08:51:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27357 for bugs-outgoing; Tue, 18 Jul 1995 08:51:12 -0700 Received: (from gibbs@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27339 ; Tue, 18 Jul 1995 08:51:10 -0700 Date: Tue, 18 Jul 1995 08:51:10 -0700 From: "Justin T. Gibbs" Message-Id: <199507181551.IAA27339@freefall.cdrom.com> To: pritc003@maroon.tc.umn.edu, gibbs, freebsd-bugs Subject: Changed information for PR kern/253 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Tagged queuing with an Adaptec 2842 controller doesn't work State-Changed-From-To: analyzed-closed State-Changed-By: gibbs State-Changed-When: Tue Jul 18 08:45:57 PDT 1995 State-Changed-Why: With the addition of disabling tagged queuing for devices that say the support tagged queuing but reject tagged queuing messages, the driver appears to work with every drive I've tested and tagged queing enabled. It would be nice to allow tagged queuing more selectively, but I look at that as a task to be performed generically by the SCSI system, but not by individual drivers. From owner-freebsd-bugs Tue Jul 18 08:57:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27685 for bugs-outgoing; Tue, 18 Jul 1995 08:57:25 -0700 Received: (from gibbs@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27667 ; Tue, 18 Jul 1995 08:57:23 -0700 Date: Tue, 18 Jul 1995 08:57:23 -0700 From: "Justin T. Gibbs" Message-Id: <199507181557.IAA27667@freefall.cdrom.com> To: ragge@ludd.luth.se, gibbs, freebsd-bugs Subject: Changed information for PR kern/586 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Timeouts on SCSI Adaptec 2940 State-Changed-From-To: open-analyzed State-Changed-By: gibbs State-Changed-When: Tue Jul 18 08:52:05 PDT 1995 State-Changed-Why: From owner-freebsd-bugs Tue Jul 18 08:58:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27815 for bugs-outgoing; Tue, 18 Jul 1995 08:58:46 -0700 Received: (from gibbs@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27800 ; Tue, 18 Jul 1995 08:58:44 -0700 Date: Tue, 18 Jul 1995 08:58:44 -0700 From: "Justin T. Gibbs" Message-Id: <199507181558.IAA27800@freefall.cdrom.com> To: ragge@ludd.luth.se, gibbs, freebsd-bugs Subject: Changed information for PR kern/586 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Timeouts on SCSI Adaptec 2940 State-Changed-From-To: analyzed-open State-Changed-By: gibbs State-Changed-When: Tue Jul 18 08:57:34 PDT 1995 State-Changed-Why: State changed accidentally. From owner-freebsd-bugs Tue Jul 18 09:49:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA29734 for bugs-outgoing; Tue, 18 Jul 1995 09:49:42 -0700 Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA29727 for ; Tue, 18 Jul 1995 09:49:36 -0700 Received: from genesis by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0sYFpQ-000jBcC; Tue, 18 Jul 95 11:49 CDT Message-Id: From: mikebo@tellabs.com (Mike Borowiec) Subject: FBSD v2.0.5R: AHA2742AT + Exabyte scrogged my root disk! To: bugs@freebsd.org Date: Tue, 18 Jul 1995 11:48:59 -0500 (CDT) Cc: mikebo@tellabs.com (Mike Borowiec) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2256 Sender: bugs-owner@freebsd.org Precedence: bulk Greetings - I'm truly amazed with the work done by the FreeBSD team, but today I'm an unhappy camper... After putting the finishing touches on my 2.0.5 configuration, I tried to load the 2.0.5 distribution tree from an Exabyte 8200 tape to disk. During the tar extract, I got the following messages repeatedly: st1: oops not queued biodone: buffer already done tar: read error on /dev/rst1: Input/output error ahc0: target 0, lun 0 (sd0) timed out Whenever I access the Exabyte, the root drive seems to be completely inaccessible. The tar extract finally failed, but I subsequently found that my root disk was completely trashed, chock full of corruption! To recover I had to run fsck several times and allow it to remove several dozen critical programs and configuration files. ARGH! Ever since moving to this Adaptec 2742AT, I've had nothing but trouble with FreeBSD. I'm seriously considering dumping the card and going back to my reliable old 1542B... EISA system board or no, I need stability and the use of both my tape drives (Exabyte 8200 and Archive Viper QIC150), both of which worked flawlessly with the 1542, both of which are utterly useless with the 2742AT and FreeBSD 2.0.5R. I've written to this list before and most of the time I get tremendous support - but this AIC7xxx driver/tape drive problem is another matter. This is just the latest catastrophy in the AIC7xxx vs. st() problems. I don't want to start a AIC7xxx vs. st() finger-pointing war - I just want this to work without trashing my system. I humbly suggest that more priority be placed on debugging this before 2.1R is released... I'm more than happy to spend hours to provide all the information regarding my machine/OS configuration, provided someone is willing to take a serious look into it... Regards, - Mike PS> I don't get these mailing lists, so please reply via e-mail. Thanks! -- -------------------------------------------------------------------------- Michael Borowiec Network Operations Tellabs Operations, Inc. mikebo@TELLABS.COM 1000 Remington Blvd. MS109 708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440 -------------------------------------------------------------------------- From owner-freebsd-bugs Tue Jul 18 12:24:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA08378 for bugs-outgoing; Tue, 18 Jul 1995 12:24:45 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA08369 ; Tue, 18 Jul 1995 12:24:43 -0700 Message-Id: <199507181924.MAA08369@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: mikebo@tellabs.com (Mike Borowiec) cc: bugs@freebsd.org Subject: Re: FBSD v2.0.5R: AHA2742AT + Exabyte scrogged my root disk! In-reply-to: Your message of "Tue, 18 Jul 95 11:48:59 CDT." Date: Tue, 18 Jul 1995 12:24:43 -0700 From: "& freefall.cdrom.com" Sender: bugs-owner@freebsd.org Precedence: bulk >Greetings - >I'm truly amazed with the work done by the FreeBSD team, but today I'm >an unhappy camper... > >After putting the finishing touches on my 2.0.5 configuration, I tried >to load the 2.0.5 distribution tree from an Exabyte 8200 tape to disk. >During the tar extract, I got the following messages repeatedly: > > st1: oops not queued > biodone: buffer already done > tar: read error on /dev/rst1: Input/output error > ahc0: target 0, lun 0 (sd0) timed out > >Whenever I access the Exabyte, the root drive seems to be completely >inaccessible. The tar extract finally failed, but I subsequently found >that my root disk was completely trashed, chock full of corruption! To >recover I had to run fsck several times and allow it to remove several >dozen critical programs and configuration files. ARGH! This was fixed recently in -current. If you have kernel source, the patch is simple. I've appended it to this message. >Ever since moving to this Adaptec 2742AT, I've had nothing but trouble >with FreeBSD. I'm seriously considering dumping the card and going back >to my reliable old 1542B... EISA system board or no, I need stability and >the use of both my tape drives (Exabyte 8200 and Archive Viper QIC150), >both of which worked flawlessly with the 1542, both of which are utterly >useless with the 2742AT and FreeBSD 2.0.5R. It was actually a SCSI system bug that hit the 2742 particuallarly hard because of the way it allocates per command resources. >I've written to this list before and most of the time I get tremendous >support - but this AIC7xxx driver/tape drive problem is another matter. >This is just the latest catastrophy in the AIC7xxx vs. st() problems. >I don't want to start a AIC7xxx vs. st() finger-pointing war - I just >want this to work without trashing my system. Try the patch and get back to me. As the author of the driver and the proud new owner of a tape drive, you should see rapid progress on these problems. >I humbly suggest that more priority be placed on debugging this before >2.1R is released... I'm more than happy to spend hours to provide all >the information regarding my machine/OS configuration, provided someone >is willing to take a serious look into it... Already being done. Between the aic7xxx driver and the SCSI system as a whole, all of my free time is already allocated. > >Regards, >- Mike -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== Index: st.c =================================================================== RCS file: /home/ncvs/src/sys/scsi/st.c,v retrieving revision 1.37 diff -c -r1.37 st.c *** 1.37 1995/07/09 08:14:24 --- st.c 1995/07/16 09:13:14 *************** *** 12,18 **** * on the understanding that TFS is not responsible for the correct * functioning of this software in any circumstances. * ! * $Id: st.c,v 1.37 1995/07/09 08:14:24 joerg Exp $ */ /* --- 12,18 ---- * on the understanding that TFS is not responsible for the correct * functioning of this software in any circumstances. * ! * $Id: st.c,v 1.38 1995/07/16 09:13:14 gibbs Exp $ */ /* *************** *** 1102,1108 **** 0, /* can't retry a read on a tape really */ 100000, bp, ! flags | SCSI_NOSLEEP) == SUCCESSFULLY_QUEUED) { stqueues++; } else { badnews: --- 1102,1108 ---- 0, /* can't retry a read on a tape really */ 100000, bp, ! flags) == SUCCESSFULLY_QUEUED) { stqueues++; } else { badnews: From owner-freebsd-bugs Tue Jul 18 13:59:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA14300 for bugs-outgoing; Tue, 18 Jul 1995 13:59:25 -0700 Received: from aero.org (aero.org [130.221.16.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA14291 for ; Tue, 18 Jul 1995 13:59:22 -0700 Received: from antares.aero.org ([130.221.192.46]) by aero.org with SMTP id <111123-1>; Tue, 18 Jul 1995 13:58:48 -0700 Received: from anpiel.aero.org by antares.aero.org (4.1/AMS-1.0) id AA19964 for freebsd-bugs@freebsd.org; Tue, 18 Jul 95 13:58:45 PDT To: freebsd-bugs@freebsd.org Subject: slice editor doesn't always show '=' flag Date: Tue, 18 Jul 1995 13:58:32 -0700 From: "Mike O'Brien" Message-Id: <95Jul18.135848pdt.111123-1@aero.org> Sender: bugs-owner@freebsd.org Precedence: bulk I successfully installed 2.0.5R this weekend, though I am still recovering from my success (recompiling everything). I was prepared to go the whole distance, so I dumped the initial DOS partition on my hard drive as well as the FreeBSD file systems. If I had to, I was ready to scrub the whole drive, repartition, and reinstall, so the slice stuff would be happy. I entered the slice editor and looked around at what it had to say. Uh-oh, no '=' flags, the kernel's gonna complain about "Partition not completely contained in slice" or something. Guess I'll have to repartition, I said to myself. I found the partition editor medium confusing, since it wouldn't let me change the size of the DOS partition. I figured I had to do this since there were no '=' flags on either my DOS or my FreeBSD partition. I undid everything, left the slice editor, and went into the partition editor to see what it had to say. I looked around in there without changing anything, left it, and went back into the slice editor. Lo and behold, now I had '=' flags! Hoo-ray! I messed with some stuff, undid everything...and the original numbers were back, all right, but this time there were no '=' flags. I exited the slice editor, re-entered it, and sure enough, there were the '=' flags, back again. I left well enough alone, installed all of 2.0.5 from CD-ROM, and when it booted, the kernel was completely happy with all the partitions, just as they'd been in 2.0R. Pant, pant. I guess what I'm saying here is that the '=' stuff is currently an invitation to heart attacks. I would have checked the 'bugs' archive except the Web page says it's unavailable right now. Mike O'Brien From owner-freebsd-bugs Tue Jul 18 15:29:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA19097 for bugs-outgoing; Tue, 18 Jul 1995 15:29:17 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA19091 for ; Tue, 18 Jul 1995 15:29:14 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id AAA26435 ; Wed, 19 Jul 1995 00:27:31 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id AAA07370 ; Wed, 19 Jul 1995 00:27:30 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507182227.AAA07370@blaise.ibp.fr> Subject: Re: FW: auto-logout To: freelist@elf.kendall.mdcc.edu (FreeBSD Mailing List drop) Date: Wed, 19 Jul 1995 00:27:30 +0200 (MET DST) Cc: dunser@msmailgw.sdsmt.edu, bugs@freebsd.org In-Reply-To: from "FreeBSD Mailing List drop" at Jul 14, 95 04:03:10 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#880 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 497 Sender: bugs-owner@freebsd.org Precedence: bulk > Lemmie guess - tcsh is your shell? Try 'set auto-logout=0'. If you want it > for all your users, put it in the share/skel/dot.login file so all the > new users you create will have that setting. Two ways to stop it : 1. the fastest and less limiting one : unset autologout in .tcshrc. 2. recompile without the corresponding #define (check config_f.h). -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995 From owner-freebsd-bugs Tue Jul 18 21:20:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id VAA02994 for bugs-outgoing; Tue, 18 Jul 1995 21:20:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id VAA02981 ; Tue, 18 Jul 1995 21:20:01 -0700 Date: Tue, 18 Jul 1995 21:20:01 -0700 Message-Id: <199507190420.VAA02981@freefall.cdrom.com> From: gordon@sneaky.lonestar.org Reply-To: gordon@sneaky.lonestar.org To: freebsd-bugs Subject: bin/623: mtree(8) changes file modes and owners it shouldn't In-Reply-To: Your message of Tue, 18 Jul 95 20:51 CDT Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 623 >Category: bin >Synopsis: mtree(8) changes file modes and owners it shouldn't >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 18 21:20:00 1995 >Originator: Gordon Burditt >Organization: what organization? >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5 >Description: mtree(8) seems to change modes and owners of files not contained in the description file if files with the same last component are described elsewhere in the description. This was originally discovered when it appeared that a slightly modified BSD.local.dist and BSD.usr.dist were fighting over the permissions of /usr/local/bin when BSD.usr.dist contained no specification for them. >How-To-Repeat: % su root # cat > /tmp/mtree # This is a cut-down version of BSD.usr.dist /set type=dir uname=bin gname=bin mode=0755 . uname=root gname=wheel bin .. /set type=dir uname=bin gname=bin mode=0755 include .. /set type=dir uname=bin gname=bin mode=0775 # you can get around the problem by putting "ignore" on the local line. local mode=0775 .. .. ^D # mkdir /tmp/test # cd /tmp/test # mtree -e -U -f ../mtree -p /tmp/test (mtree creates 3 directories, bin, include, and local, as it should) # mkdir local/bin local/include local/lib local/libexec # chmod 0 local/* # chown root.wheel local/* (these 4 directories are NOT described in the mtree description) # mtree -e -U -f ../mtree -p /tmp/test local/bin: user (3, 0, modified) gid (7, 0, modified) permissions (0755, 0, modified) local/include: user (3, 0, modified) gid (7, 0, modified) permissions (0755, 0, modified) # ls -l local total 8 drwxr-xr-x 2 bin bin 512 Jul 18 20:23 bin drwxr-xr-x 2 bin bin 512 Jul 18 20:23 include d--------- 2 root wheel 512 Jul 18 20:23 lib d--------- 2 root wheel 512 Jul 18 20:23 libexec Why is it changing modes and owners on these files which have no specified permissions? It seems to be using the permissions for ./bin and ./include to change ./local/bin and ./local/include . >Fix: You can work around this by putting "ignore" on directories whose substructure you don't want changed. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jul 18 22:10:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id WAA04740 for bugs-outgoing; Tue, 18 Jul 1995 22:10:11 -0700 Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id WAA04733 for ; Tue, 18 Jul 1995 22:10:09 -0700 From: mikebo@tellabs.com Received: from tellabk.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0sYRO2-000jC1C; Wed, 19 Jul 95 00:09 CDT Received: by tellabk.tellabs.com (4.1/1.9) id AA13275; Wed, 19 Jul 95 00:09:32 CDT Message-Id: <9507190509.AA13275@tellabk.tellabs.com> Subject: Re: FBSD v2.0.5R: AHA2742AT + Exabyte scrogged my root disk! To: gibbs@freefall.cdrom.com Date: Wed, 19 Jul 1995 00:09:32 -0500 (CDT) Cc: mikebo (Mike Borowiec), bugs@freebsd.org In-Reply-To: <199507181924.MAA08369@freefall.cdrom.com> from "& freefall.cdrom.com" at Jul 18, 95 12:24:43 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 7381 Sender: bugs-owner@freebsd.org Precedence: bulk Justin - You wrote: > Michael Borowiec wrote: > >After putting the finishing touches on my 2.0.5 configuration, I tried > >to load the 2.0.5 distribution tree from an Exabyte 8200 tape to disk. > >During the tar extract, I got the following messages repeatedly: > > > > st1: oops not queued > > biodone: buffer already done > > tar: read error on /dev/rst1: Input/output error > > ahc0: target 0, lun 0 (sd0) timed out > > > >Whenever I access the Exabyte, the root drive seems to be completely > >inaccessible. The tar extract finally failed, but I subsequently found > >that my root disk was completely trashed, chock full of corruption! To > >recover I had to run fsck several times and allow it to remove several > >dozen critical programs and configuration files. ARGH! > > This was fixed recently in -current. If you have kernel source, the > patch is simple. I've appended it to this message. ... > It was actually a SCSI system bug that hit the 2742 particuallarly hard > because of the way it allocates per command resources. ... > Try the patch and get back to me. As the author of the driver and the > proud new owner of a tape drive, you should see rapid progress on these > problems. > I downloaded the latest st.c from "current" and built a new kernel. I successfully loaded the ~450MB 2.0.5-RELEASE tree from my Exabyte to disk. However, I noticed the following anomolous behavior: o two "ahc0: target 0, lun 0 (sd0) timed out" messages at the beginning of the tar, and a few more at the end while the tape was rewinding. I was holding my breath, as last time this happened I got five or six such messages before the OS panic'ed and corrupted my root. I WAS able to access the root drive while the tar ran. o I get "ahc0: target 0, lun 0 (sd0) timed out" messages around once every ~10 seconds whenever I do any non-read/write tape operation, such as: rewind, rewoffl, etc.. During these operations, the SCSI bus activity light (powered by the 2742AT) is lit constantly, and accesses to disk drives are defered until the operation completes and the light goes out. o In the past, when doing SCSI transfers, the bus activity light flickered in concert with the drive activity lights. Now it appears to stay lit solid during an entire tape job. Disk to disk copies do exhibit the flicker... The worst problem appears to be solved, but there would seem to be a few more dust-bunnies under the couch. I would be pleased to assist by testing your mods on my system. See my dmesg output below... > ... Between the aic7xxx driver and the SCSI system as a > whole, all of my free time is already allocated. > We appreciate it! Regards, - Mike -- -------------------------------------------------------------------------- Michael Borowiec Network Operations Tellabs Operations, Inc. mikebo@TELLABS.COM 1000 Remington Blvd. MS109 708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440 -------------------------------------------------------------------------- -- dmesg output: Jul 18 20:47:12 timesink /kernel: FreeBSD 2.0.5-RELEASE #2: Tue Jul 18 20:42:33 CDT 1995 Jul 18 20:47:12 timesink /kernel: kroot@timesink:/usr/src/sys/compile/TIMESINK Jul 18 20:47:13 timesink /kernel: CPU: i486DX (486-class CPU) Jul 18 20:47:13 timesink /kernel: real memory = 16384000 (4000 pages) Jul 18 20:47:13 timesink /kernel: avail memory = 14749696 (3601 pages) Jul 18 20:47:13 timesink /kernel: Probing for devices on the ISA bus: Jul 18 20:47:13 timesink /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 18 20:47:13 timesink /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 18 20:47:13 timesink /kernel: ed0 at 0x280-0x29f irq 9 maddr 0xd4000 msize 16384 on isa Jul 18 20:47:13 timesink /kernel: ed0: address 00:00:c0:d1:09:2d, type WD8013EP (16 bit) Jul 18 20:47:13 timesink /kernel: bpf: ed0 attached Jul 18 20:47:13 timesink /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 18 20:47:13 timesink /kernel: sio0: type 16550A Jul 18 20:47:13 timesink /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jul 18 20:47:13 timesink /kernel: lpt0: Interrupt-driven port Jul 18 20:47:13 timesink /kernel: lp0: TCP/IP capable interface Jul 18 20:47:13 timesink /kernel: mse0 at 0x23c irq 3 on isa Jul 18 20:47:13 timesink /kernel: pca0 on motherboard Jul 18 20:47:13 timesink /kernel: pca0: PC speaker audio driver Jul 18 20:47:13 timesink /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 18 20:47:14 timesink /kernel: fdc0: NEC 72065B Jul 18 20:47:14 timesink /kernel: fd0: 1.44MB 3.5in Jul 18 20:47:14 timesink /kernel: fd1: 1.2MB 5.25in Jul 18 20:47:14 timesink /kernel: ahc0: reading board settings Jul 18 20:47:14 timesink /kernel: ahc0: 274x Twin Channel, A SCSI Id=7, B SCSI Id=7, aic7770 >= Rev E, 4 SCBs Jul 18 20:47:14 timesink /kernel: ahc0: Using Level Sensitive Interrupts Jul 18 20:47:14 timesink /kernel: ahc0: Downloading Sequencer Program...Done Jul 18 20:47:14 timesink /kernel: ahc0 at 0x5000-0x50ff irq 11 on eisa slot 5 Jul 18 20:47:14 timesink /kernel: ahc0: Probing channel A Jul 18 20:47:14 timesink /kernel: ahc0 waiting for scsi devices to settle Jul 18 20:47:15 timesink /kernel: ahc0: target 0 synchronous at 4.4MB/s, offset = 0xf Jul 18 20:47:15 timesink /kernel: (ahc0:0:0): "IMPRIMIS 94601-15 1250" type 0 fixed SCSI 1 Jul 18 20:47:15 timesink /kernel: sd0(ahc0:0:0): Direct-Access 989MB (2026965 512 byte sectors) Jul 18 20:47:15 timesink /kernel: (ahc0:1:0): "MAXTOR XT-4380S B5A" type 0 fixed SCSI 1 Jul 18 20:47:15 timesink /kernel: sd1(ahc0:1:0): Direct-Access 318MB (651630 512 byte sectors) Jul 18 20:47:15 timesink /kernel: (ahc0:2:0): "ARCHIVE VIPER 150 20000 -000" type 1 removable SCSI 1 Jul 18 20:47:15 timesink /kernel: st0(ahc0:2:0): Sequential-Access st0: Archive Viper 150 is a known rogue Jul 18 20:47:15 timesink /kernel: density code 0x0, drive empty Jul 18 20:47:15 timesink /kernel: (ahc0:5:0): "EXABYTE EXB-8200 4.25" type 1 removable SCSI 1 Jul 18 20:47:15 timesink /kernel: st1(ahc0:5:0): Sequential-Access density code 0x0, Jul 18 20:47:15 timesink /kernel: st1(ahc0:5:0): Target Busy Jul 18 20:47:16 timesink /kernel: Jul 18 20:47:16 timesink /kernel: st1(ahc0:5:0): Target Busy Jul 18 20:47:16 timesink /kernel: Jul 18 20:47:16 timesink /kernel: st1(ahc0:5:0): Target Busy Jul 18 20:47:16 timesink /kernel: drive empty Jul 18 20:47:16 timesink /kernel: (ahc0:6:0): "NEC CD-ROM DRIVE:501 2.2" type 5 removable SCSI 2 Jul 18 20:47:17 timesink /kernel: cd0(ahc0:6:0): CD-ROM cd present.[100146 x 2048 byte records] Jul 18 20:47:17 timesink /kernel: ahc0: Probing Channel B Jul 18 20:47:17 timesink /kernel: ahc0 waiting for scsi devices to settle Jul 18 20:47:17 timesink /kernel: ahb0 not found Jul 18 20:47:17 timesink /kernel: aha0 not found at 0x330 Jul 18 20:47:18 timesink /kernel: npx0 on motherboard Jul 18 20:47:18 timesink /kernel: npx0: INT 16 interface Jul 18 20:47:18 timesink /kernel: sb0 at 0x220 irq 5 drq 1 on isa Jul 18 20:47:18 timesink /kernel: sb0: Jul 18 20:47:18 timesink /kernel: opl0 at 0x388 on isa Jul 18 20:47:18 timesink /kernel: opl0: Jul 18 20:47:18 timesink /kernel: bpf: lo0 attached Jul 18 20:47:18 timesink /kernel: bpf: ppp0 attached Jul 18 20:47:18 timesink /kernel: bpf: sl0 attached -- end of dmesg output From owner-freebsd-bugs Tue Jul 18 22:27:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id WAA05301 for bugs-outgoing; Tue, 18 Jul 1995 22:27:29 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id WAA05294 ; Tue, 18 Jul 1995 22:27:27 -0700 Message-Id: <199507190527.WAA05294@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: mikebo@tellabs.com cc: bugs@freebsd.org Subject: Re: FBSD v2.0.5R: AHA2742AT + Exabyte scrogged my root disk! In-reply-to: Your message of "Wed, 19 Jul 95 00:09:32 CDT." <9507190509.AA13275@tellabk.tellabs.com> Date: Tue, 18 Jul 1995 22:27:27 -0700 From: "Justin T. Gibbs" Sender: bugs-owner@freebsd.org Precedence: bulk >Justin - >You wrote: >> >> Try the patch and get back to me. As the author of the driver and the >> proud new owner of a tape drive, you should see rapid progress on these >> problems. >> >I downloaded the latest st.c from "current" and built a new kernel. >I successfully loaded the ~450MB 2.0.5-RELEASE tree from my Exabyte >to disk. However, I noticed the following anomolous behavior: You're problem appears that you are not allowing your exabyte to disconnect when it is performing a command. Do you have the disconnection priveledge enabled via the eisa configuration utility? or does the exabyte just not perform disconnections? The SCSI system should be made to handle these types of situtions regardless, but it always comes down to what timeout level is sufficient to deal with targets that don't disconnect, but also discovers devices that are truely hung. I'll have to give this some more thought. If you can't get disconnections to work on your tape drive, go into st.c and increase the timeout for the tape driver. This unfortunately won't deal with commands to other devices that are waiting for the bus to go free, but it may help. >The worst problem appears to be solved, but there would seem to be >a few more dust-bunnies under the couch. I would be pleased to assist >by testing your mods on my system. See my dmesg output below... There are more than a few dust bunnies under the couch, but most of them will require carefull consideration in order to sweep out. >> ... Between the aic7xxx driver and the SCSI system as a >> whole, all of my free time is already allocated. >> >We appreciate it! >Regards, >- Mike >-- >-------------------------------------------------------------------------- >Michael Borowiec Network Operations Tellabs Operations, Inc. >mikebo@TELLABS.COM 1000 Remington Blvd. MS109 >708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440 >-------------------------------------------------------------------------- -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Tue Jul 18 23:38:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id XAA08803 for bugs-outgoing; Tue, 18 Jul 1995 23:38:15 -0700 Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id XAA08792 for ; Tue, 18 Jul 1995 23:38:08 -0700 From: mikebo@tellabs.com Received: from tellabk.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0sYSl3-000jBzC; Wed, 19 Jul 95 01:37 CDT Received: by tellabk.tellabs.com (4.1/1.9) id AA13545; Wed, 19 Jul 95 01:37:23 CDT Message-Id: <9507190637.AA13545@tellabk.tellabs.com> Subject: Re: FBSD v2.0.5R: AHA2742AT + Exabyte scrogged my root disk! To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Wed, 19 Jul 1995 01:37:22 -0500 (CDT) Cc: mikebo (Mike Borowiec), bugs@freebsd.org In-Reply-To: <199507190527.WAA05294@freefall.cdrom.com> from "Justin T. Gibbs" at Jul 18, 95 10:27:27 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1152 Sender: bugs-owner@freebsd.org Precedence: bulk Justin - You wrote: > >I downloaded the latest st.c from "current" and built a new kernel. > >I successfully loaded the ~450MB 2.0.5-RELEASE tree from my Exabyte > >to disk. However, I noticed the following anomolous behavior: > > You're problem appears that you are not allowing your exabyte to disconnect > when it is performing a command. Do you have the disconnection priveledge > enabled via the eisa configuration utility? or does the exabyte just not > perform disconnections? > You hit the nail on the head! I had disabled disconnects because the 2.0R driver complained about them, and forgot to turn them back on with 2.0.5R. A quick DOS session with the EISA utility and it works fine now... thanks! - Mike BTW - My wife says you stay up too late hacking... ;v) -- -------------------------------------------------------------------------- Michael Borowiec Network Operations Tellabs Operations, Inc. mikebo@TELLABS.COM 1000 Remington Blvd. MS109 708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440 -------------------------------------------------------------------------- From owner-freebsd-bugs Wed Jul 19 02:10:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id CAA17329 for bugs-outgoing; Wed, 19 Jul 1995 02:10:11 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id CAA17322 ; Wed, 19 Jul 1995 02:10:07 -0700 Date: Wed, 19 Jul 1995 02:10:07 -0700 Message-Id: <199507190910.CAA17322@freefall.cdrom.com> From: asami@cs.berkeley.edu Reply-To: asami@cs.berkeley.edu To: freebsd-bugs Subject: bin/624: pkg_manage doesn't show directory symlinks In-Reply-To: Your message of Wed, 19 Jul 1995 02:03:14 -0700 <199507190903.CAA01018@silvia.HIP.Berkeley.EDU> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 624 >Category: bin >Synopsis: pkg_manage doesn't show directory symlinks >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jul 19 02:10:03 1995 >Originator: Satoshi Asami >Organization: The Awesome FreeBSD Ports Team >Release: FreeBSD 2.2-CURRENT i386 >Environment: Any of the latest pkg_manages >Description: While I'm trying to traverse the directory tree to get to the package directory, pkg_manage doesn't show the symlinks to directories as candidates to cd into. This may be annoying like when the user started out at /usr/ports and packages is a symlink to /cdrom/ports/packages. >How-To-Repeat: Obvious. >Fix: Not obvious. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jul 19 05:24:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id FAA21640 for bugs-outgoing; Wed, 19 Jul 1995 05:24:15 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id FAA21634 for ; Wed, 19 Jul 1995 05:24:14 -0700 Received: (dillon@localhost) by blob.best.net (8.6.12/8.6.5) id FAA26031; Wed, 19 Jul 1995 05:24:07 -0700 Date: Wed, 19 Jul 1995 05:24:07 -0700 From: Matt Dillon Message-Id: <199507191224.FAA26031@blob.best.net> To: bugs@freebsd.org Subject: probable race condition in ufs/ffs/ffs_vfsops.c:ffs_vget() Sender: bugs-owner@freebsd.org Precedence: bulk We've been getting the following panic: panic: ffs_valloc: dup alloc It took a long while, and I could find no *direct* cause of the panic. Fortunately I had a debug kernel and a crash dump to work with. I still have it in case this doesn't turn out to solve the problem. It would appear that the inode that was allocated from the bitmap was VERY much in use... a non-zero length REG file with very valid-looking fields. The weird thing is that the latest access/modify/change timestamp on the inode was several HUNDRED seconds earlier then the time of the crash. I believe I have found the problem... a race condition in ffs_vget(). Here's a synopsis: (1) lookup (dev,ino) in hash table, return on success (2) allocate new vnode and new inode structure MALLOC(..., M_WAITOK) for the inode (3) enter new inode into hash table. The problem is that MALLOC() can block. If it does, you can potentially have TWO processes attempt to lookup an uncached inode simultaniously in a low memory situation. The MALLOC() blocks until memory is available, both processes unblock *AFTER* having determined that the inode wasn't cached, and *both* processes allocate new vnode/inode structures representing the *same* inode and enter both of them into the hash table. At some point in the future the inode is deallocated and the bitmap for it cleared, but this only removes one of the two cached inode structures. sync() comes along and commits the other one... poof, you now have an active inode on the platter whos bitmap entry is cleared. At some later time someone tries to create a new file and BANG it hits the screwed inode. The solution, as far as I can tell, is to check the hash table after MALLOC returns as well as before to determine if another process beat us to it. I put the following code just before the ufs_ihashins(). I do NOT know whether this code fixes the problem yet or even if the code is valid in terms of freeing the right stuff before returning... (I'll tell you in a few days re: the crashes... I'll either get more panics or I will not). #if 1 if ((*vpp = ufs_ihashget(dev, ino)) != NULL) { vp->v_data = NULL; vput(vp); printf("INODE COLLISION: %d\n", ino); FREE(ip, type); return (0); } #endif ... ufs_ihashins(ip); ... etc... -Matt From owner-freebsd-bugs Wed Jul 19 06:47:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id GAA24294 for bugs-outgoing; Wed, 19 Jul 1995 06:47:29 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id GAA24284 for ; Wed, 19 Jul 1995 06:47:15 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA22543; Wed, 19 Jul 1995 23:44:44 +1000 Date: Wed, 19 Jul 1995 23:44:44 +1000 From: Bruce Evans Message-Id: <199507191344.XAA22543@godzilla.zeta.org.au> To: bugs@freebsd.org, dillon@blob.best.net Subject: Re: probable race condition in ufs/ffs/ffs_vfsops.c:ffs_vget() Sender: bugs-owner@freebsd.org Precedence: bulk > panic: ffs_valloc: dup alloc > I believe I have found the problem... a race condition in ffs_vget(). > Here's a synopsis: > (1) lookup (dev,ino) in hash table, return on success > (2) allocate new vnode and new inode structure MALLOC(..., M_WAITOK) > for the inode > (3) enter new inode into hash table. > The problem is that MALLOC() can block. If it does, you can potentially > have TWO processes attempt to lookup an uncached inode simultaniously > in a low memory situation. The MALLOC() blocks until memory is available, getnewvnode() can block in the same way :-(. This problem makes using the M_WAITOK flag difficult. It can only be used in suroutines if all callers are known to not care if the subroutine blocks. I wonder how common it is for malloc() to block? Several drivers complain if malloc(..., M_NOWAIT) fails and a few drivers don't check if malloc(..., M_NOWAIT) fails, but there haven't been many bug reports about this. > The solution, as far as I can tell, is to check the hash table after > MALLOC returns as well as before to determine if another process beat > us to it. I put the following code just before the ufs_ihashins(). I > do NOT know whether this code fixes the problem yet or even if the > code is valid in terms of freeing the right stuff before returning... > (I'll tell you in a few days re: the crashes... I'll either get > more panics or I will not). >#if 1 > if ((*vpp = ufs_ihashget(dev, ino)) != NULL) { > vp->v_data = NULL; I think it clobbers the in-use v_data here. I think you should lock the vnode before possibly blocking. Bruce From owner-freebsd-bugs Wed Jul 19 08:50:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA28749 for bugs-outgoing; Wed, 19 Jul 1995 08:50:46 -0700 Received: from silver.sdsmt.edu (silver.sdsmt.edu [151.159.1.1]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id IAA28737 for ; Wed, 19 Jul 1995 08:50:41 -0700 Received: from msmail.sdsmt.edu (msmail.sdsmt.edu [151.159.1.43]) by silver.sdsmt.edu (8.6.12/8.6.12) with SMTP id JAA26465 for ; Wed, 19 Jul 1995 09:50:38 -0600 Received: by msmail.sdsmt.edu with Microsoft Mail id <300D29CD@msmail.sdsmt.edu>; Wed, 19 Jul 95 09:50:37 MDT From: "Unser, Danny" To: "'FreeBSD - Bugs'" Subject: probelm with X windows stuff Date: Wed, 19 Jul 95 09:49:00 MDT Message-ID: <300D29CD@msmail.sdsmt.edu> Encoding: 13 TEXT X-Mailer: Microsoft Mail V3.0 Sender: bugs-owner@freebsd.org Precedence: bulk There appears to be a problem with tcl/tk I keep getting the error: ld.so: wish: libtk.so.3.6: Undefined error: 0 Or when I try to compile tkflexfax I get the error: ld.so: tclsh: libtcl.so.7.3: Undefined error: 0 Any ideas with this one? Dan From owner-freebsd-bugs Wed Jul 19 11:09:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA04073 for bugs-outgoing; Wed, 19 Jul 1995 11:09:44 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA04060 for ; Wed, 19 Jul 1995 11:09:37 -0700 Received: (dillon@localhost) by blob.best.net (8.6.12/8.6.5) id LAA07002; Wed, 19 Jul 1995 11:09:16 -0700 Date: Wed, 19 Jul 1995 11:09:16 -0700 From: Matt Dillon Message-Id: <199507191809.LAA07002@blob.best.net> To: Kirk McKusick Cc: davidg@root.com, bugs@freebsd.org Subject: Re: possible ffs_vget() race condition Sender: bugs-owner@freebsd.org Precedence: bulk I've got some kernel printf()'s in the two critical code areas along with my fix so by this time tomorrow I should know whether the hole is getting hit. Oh, there are also some pretty serious problems with the sysctl() stuff... mainly with all the list traversals the sysctl()'s do without locking and the copyout's inside the loops (which can block, causing the list being traverse and most specifically the 'current' item to be ripped out from under sysctl())... I had to stop using pstat -T because of the problem (it would crash the machine every couple of hours). Since I absolutely need ps, I wound up patched the proc stuff sysctl's adding a lock count to the process structure which the exit/zombie code blocks on, but haven't posted the patches because the whole sysctl thing really needs a good going over to solve the problems. -Matt : To: arch@FreeBSD.org : cc: dillon@blob.best.net : Subject: possible ffs_vget() race condition : From: David Greenman : Reply-To: davidg@Root.COM : Date: Wed, 19 Jul 1995 06:52:48 -0700 : : Any comments, Kirk? : : -DG : :This is a bug. I believe that the correct fix is to use a non-blocking :malloc. If it fails, then do a blocking malloc, a free, and then restart :with another call to ufs_ihashget. If another vnode has showed up while :you were blocked in getnewvnode or malloc, free the previously allocated :vnode, and return the one found by ufs_ihashget. : : ~Kirk : From owner-freebsd-bugs Wed Jul 19 11:27:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA05319 for bugs-outgoing; Wed, 19 Jul 1995 11:27:12 -0700 Received: from chez.CS.Berkeley.EDU (chez.CS.Berkeley.EDU [128.32.211.112]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA05310 for ; Wed, 19 Jul 1995 11:27:11 -0700 Received: from chez.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by chez.CS.Berkeley.EDU (8.7.Beta.2/8.6.9) with ESMTP id LAA14283; Wed, 19 Jul 1995 11:24:55 -0700 (PDT) Message-Id: <199507191824.LAA14283@chez.CS.Berkeley.EDU> To: Matt Dillon Subject: Re: possible ffs_vget() race condition cc: davidg@root.com, bugs@freebsd.org In-reply-to: Your message of "Wed, 19 Jul 1995 11:09:16 PDT." <199507191809.LAA07002@blob.best.net> Date: Wed, 19 Jul 1995 11:24:51 -0700 From: Kirk McKusick Sender: bugs-owner@freebsd.org Precedence: bulk Date: Wed, 19 Jul 1995 11:09:16 -0700 From: Matt Dillon To: Kirk McKusick Cc: davidg@root.com, bugs@freebsd.org Subject: Re: possible ffs_vget() race condition I've got some kernel printf()'s in the two critical code areas along with my fix so by this time tomorrow I should know whether the hole is getting hit. Oh, there are also some pretty serious problems with the sysctl() stuff... mainly with all the list traversals the sysctl()'s do without locking and the copyout's inside the loops (which can block, causing the list being traverse and most specifically the 'current' item to be ripped out from under sysctl())... I had to stop using pstat -T because of the problem (it would crash the machine every couple of hours). Since I absolutely need ps, I wound up patched the proc stuff sysctl's adding a lock count to the process structure which the exit/zombie code blocks on, but haven't posted the patches because the whole sysctl thing really needs a good going over to solve the problems. -Matt I do not believe that sysctl is the source of your problem. For all data structures except the vnode table, it does a vslock on the copyout buffer before starting the list traversal. Thus the copyout cannot block. More likely your problems are arising because the information that pstat is trying to report is coming from /dev/kmem rather than through sysctl. Switching it to be accessible from sysctl should solve your problem. ~Kirk From owner-freebsd-bugs Wed Jul 19 12:53:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA07910 for bugs-outgoing; Wed, 19 Jul 1995 12:53:54 -0700 Received: from elf.kendall.mdcc.edu (elf.kendall.mdcc.edu [147.70.150.122]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id MAA07903 for ; Wed, 19 Jul 1995 12:53:51 -0700 Received: (from freelist@localhost) by elf.kendall.mdcc.edu (8.6.11/8.6.9) id PAA29481; Wed, 19 Jul 1995 15:42:41 -0400 Date: Wed, 19 Jul 1995 15:42:38 -0400 (EDT) From: FreeBSD Mailing List drop To: Ollivier Robert cc: dunser@msmailgw.sdsmt.edu, bugs@freebsd.org Subject: Re: FW: auto-logout In-Reply-To: <199507182227.AAA07370@blaise.ibp.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk On Wed, 19 Jul 1995, Ollivier Robert wrote: > > Lemmie guess - tcsh is your shell? Try 'set auto-logout=0'. If you want it > > for all your users, put it in the share/skel/dot.login file so all the > > new users you create will have that setting. > > Two ways to stop it : > 1. the fastest and less limiting one : unset autologout in .tcshrc. > 2. recompile without the corresponding #define (check config_f.h). Less limiting, but also less illuminating for your users. set autologout=0 makes it pretty clear that it can be set to another time if they so desire. If they just delete the unset, they then have the default autologout time. Guess it depends on if you think it's a useful feature or not.... From owner-freebsd-bugs Wed Jul 19 12:54:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id MAA07997 for bugs-outgoing; Wed, 19 Jul 1995 12:54:24 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id MAA07978 ; Wed, 19 Jul 1995 12:54:22 -0700 Received: (root@localhost) by blob.best.net (8.6.12/8.6.5) id MAA16549; Wed, 19 Jul 1995 12:54:04 -0700 Date: Wed, 19 Jul 1995 12:54:04 -0700 From: Matt Dillon Message-Id: <199507191954.MAA16549@blob.best.net> To: bde@zeta.org.au Cc: davidg@Root.COM, arch@FreeBSD.org, bugs@FreeBSD.org Subject: Re: possible ffs_vget() race condition Sender: bugs-owner@FreeBSD.org Precedence: bulk >>:>#if 1 >>:> if ((*vpp = ufs_ihashget(dev, ino)) != NULL) { >>:> vp->v_data = NULL; >>: >>:I think it clobbers the in-use v_data here. I think you should lock >>:the vnode before possibly blocking. > >> Hmm... I was under the impression that the whole of the newly >> allocated vnode (vp) at that point in the code had yet to be >> associated with anything. i.e. that nobody else would have any > >Yes; I confused *vpp with vp. > >Bruce Urk... The OS just hit the hole, so I guess it's a real problem! And, unfortunately, panic'd trying to access the inode through vp->v_data which I had NULL'd out in my patch... so, obviously, I am not freeing it properly. If someone could email me the proper way to free it at this point (where we've allocated the vnode but then determine we have to throw it out due to a duplicate before we setup the inode for it), I'd appreciate it. -Matt From owner-freebsd-bugs Wed Jul 19 13:21:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id NAA08896 for bugs-outgoing; Wed, 19 Jul 1995 13:21:02 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id NAA08888 for ; Wed, 19 Jul 1995 13:20:58 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA28881; Wed, 19 Jul 95 14:13:29 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9507192013.AA28881@cs.weber.edu> Subject: Re: possible ffs_vget() race condition To: dillon@blob.best.net (Matt Dillon) Date: Wed, 19 Jul 95 14:13:28 MDT Cc: mckusick@McKusick.COM, davidg@root.com, bugs@freebsd.org In-Reply-To: <199507191809.LAA07002@blob.best.net> from "Matt Dillon" at Jul 19, 95 11:09:16 am X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@freebsd.org Precedence: bulk > Oh, there are also some pretty serious problems with the sysctl() > stuff... mainly with all the list traversals the sysctl()'s do > without locking and the copyout's inside the loops (which can > block, causing the list being traverse and most specifically the > 'current' item to be ripped out from under sysctl())... I had > to stop using pstat -T because of the problem (it would crash > the machine every couple of hours). A lot of the system configuration stuff is bogus/unportable/both. The use of manifest constants to do the descriptor structs in sysctl.h is patently bogus. The CTLTYPE_QUAD definition and the size variant CTLTYPE_INT are both rather annoying; these should be sized values, and QUAD should probably not be allowed at all, since 64 bit values are (as yet) intolerably unportable. Not to mention the use of a shift of an embeded constant '63' and a -1 to get the RLIM_INFINITY value in resource.h. Instead of (~(u_quad_t)0). Anything touching on quad code is pretty much half baked. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Wed Jul 19 13:25:40 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id NAA09164 for bugs-outgoing; Wed, 19 Jul 1995 13:25:40 -0700 Received: from cs.utah.edu (cs.utah.edu [128.110.4.21]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id NAA09142 ; Wed, 19 Jul 1995 13:25:31 -0700 Received: from venus.cs.utah.edu by cs.utah.edu (8.6.12/utah-2.21-cs) id OAA01851; Wed, 19 Jul 1995 14:24:37 -0600 Received: by venus.cs.utah.edu (8.6.10/utah-2.15sun-leaf) id OAA26702; Wed, 19 Jul 1995 14:24:13 -0600 Date: Wed, 19 Jul 1995 14:24:13 -0600 From: mike@cs.utah.edu (Mike Hibler) Message-Id: <199507192024.OAA26702@venus.cs.utah.edu> To: bde@zeta.org.au, dillon@blob.best.net Subject: Re: possible ffs_vget() race condition Cc: arch@FreeBSD.org, bugs@FreeBSD.org, davidg@Root.COM Sender: bugs-owner@FreeBSD.org Precedence: bulk > Urk... The OS just hit the hole, so I guess it's a real problem! > And, unfortunately, panic'd trying to access the inode through > vp->v_data which I had NULL'd out in my patch... so, obviously, I > am not freeing it properly. > > If someone could email me the proper way to free it at this point (where > we've allocated the vnode but then determine we have to throw it out > due to a duplicate before we setup the inode for it), I'd appreciate it. > > -Matt > You may have hit another race caused by the blocking malloc. Here is how it bit us (in our 4.3/4.4-ish BSD on hp700): getnewvnode() puts the new vnode on the mount list (insmntque), malloc blocks so v_data doesn't get set, some process runs that does a sync(), ffs_sync traverses the mountlist and dereferences the 0 v_data field. Our particular scenerio was using a large MFS. MFS is uniquely suited to exposing this race since it not only uses the racy code, it uses lots of memory too! P.S. We "fixed" it by having the caller of getnewvnode put the vnode on the mount list when it is completely initialized. This won't fix your original problem though. From owner-freebsd-bugs Wed Jul 19 13:43:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id NAA09837 for bugs-outgoing; Wed, 19 Jul 1995 13:43:33 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id NAA09829 for ; Wed, 19 Jul 1995 13:43:24 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA09134 ; Wed, 19 Jul 1995 22:41:42 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id WAA12409 ; Wed, 19 Jul 1995 22:41:42 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507192041.WAA12409@blaise.ibp.fr> Subject: Re: probelm with X windows stuff To: dunser@msmailgw.sdsmt.edu (Unser, Danny) Date: Wed, 19 Jul 1995 22:41:41 +0200 (MET DST) Cc: bugs@freebsd.org In-Reply-To: <300D29CD@msmail.sdsmt.edu> from "Unser, Danny" at Jul 19, 95 09:49:00 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#880 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 508 Sender: bugs-owner@freebsd.org Precedence: bulk > ld.so: wish: libtk.so.3.6: Undefined error: 0 > > Or when I try to compile tkflexfax I get the error: > ld.so: tclsh: libtcl.so.7.3: Undefined error: 0 Did you update the shared libray path by running ldconfig -m ? -m Instead of replacing the contents of ld.so.hints with those found in the directories specified, ``merge'' in new entries. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995 From owner-freebsd-bugs Wed Jul 19 14:30:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA11530 for bugs-outgoing; Wed, 19 Jul 1995 14:30:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA11522 ; Wed, 19 Jul 1995 14:30:03 -0700 Date: Wed, 19 Jul 1995 14:30:03 -0700 Message-Id: <199507192130.OAA11522@freefall.cdrom.com> From: henrich@crh.cl.msu.edu Reply-To: henrich@crh.cl.msu.edu To: freebsd-bugs Subject: kern/625: keyboard lockup during boot and forevcer after In-Reply-To: Your message of Wed, 19 Jul 1995 17:23:18 -0400 <199507192123.RAA05775@crh.cl.msu.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 625 >Category: kern >Synopsis: keyboard lockups during boot and forever after >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 19 14:30:02 1995 >Originator: Charles Henrich >Organization: Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5-RELEASE on a Micron P100 Millenia Micronics PCI Triton Motherboard >Description: If I press a key during the boot: prompt, or with the OS-BS boot, manager or if I do a soft reset (not coming up from a power up) When the login: prompt arrives the keyboard is nonfunctional, Num Lock is not lit, etc.. >How-To-Repeat: Reboot anytime and when it comes back its dead, or during a fresh boot type at the boot: prompt. >Fix: Wish I knew, this is annoying as hell >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jul 19 17:38:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA18435 for bugs-outgoing; Wed, 19 Jul 1995 17:38:12 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA18411 ; Wed, 19 Jul 1995 17:38:08 -0700 Received: (dillon@localhost) by blob.best.net (8.6.12/8.6.5) id RAA01062; Wed, 19 Jul 1995 17:37:43 -0700 Date: Wed, 19 Jul 1995 17:37:43 -0700 From: Matt Dillon Message-Id: <199507200037.RAA01062@blob.best.net> To: mike@cs.utah.edu (Mike Hibler) Cc: bde@zeta.org.au, arch@FreeBSD.org, bugs@FreeBSD.org, davidg@Root.COM Subject: Re: possible ffs_vget() race condition Sender: bugs-owner@FreeBSD.org Precedence: bulk I've tried putting a tsleep/wakeup style lock around the routine, starting just after the initial hash lookup fails. That ought to fix #1 temporarily until you guys come up with something more permanent that deals with #1 and #2. -Matt From owner-freebsd-bugs Thu Jul 20 00:57:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id AAA26725 for bugs-outgoing; Thu, 20 Jul 1995 00:57:05 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id AAA26718 for ; Thu, 20 Jul 1995 00:56:51 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08602; Thu, 20 Jul 1995 09:56:45 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) id JAA11798 for FreeBSD-bugfiler@freefall.cdrom.com; Thu, 20 Jul 1995 09:56:44 +0200 Date: Thu, 20 Jul 1995 09:56:44 +0200 From: kieber@sax.sax.de (Ulf Kieber) Message-Id: <199507200756.JAA11798@sax.sax.de> Subject: /usr/share/misc/inter.phone outdated Index: share/misc/inter.phone FreeBSD-2.0.5 Apparently-To: FreeBSD-bugfiler@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk Description: German reunification was _way_ back. Fixing anachronism. Repeat-By: more /usr/share/misc/inter.phone Fix: Apply the following diff: *** share/misc/inter.phone.orig Sat Jun 10 11:58:21 1995 --- share/misc/inter.phone Thu Jul 20 09:39:57 1995 *************** *** 67,77 **** 34:71:Palma de Mallorca:Spain 34:76:Zaragoza:Spain 36:1:Budapest:Hungary - 37:2:Berlin:German Democratic Republic - 37:30:Frankfurt:German Democratic Republic - 37:41:Leipzig:German Democratic Republic - 37:51:Dresden:German Democratic Republic - 37:71:Karl-Marx-Stadt:German Democratic Republic 38:11:Belgrade:Yugoslavia 38:41:Zagreb:Yugoslavia 38:50:Dubrovnik:Yugoslavia --- 67,72 ---- *************** *** 152,161 **** 49:228:Bonn:Germany, Fed. Rep. of 49:231:Dortmund:Germany, Fed. Rep. of 49:30:Berlin:Germany, Fed. Rep. of 49:40:Hamburg:Germany, Fed. Rep. of 49:421:Bremen:Germany, Fed. Rep. of 49:511:Hannover:Germany, Fed. Rep. of ! 49:69:Frankfurt:Germany, Fed. Rep. of 49:711:Stuttgart:Germany, Fed. Rep. of 49:89:Munich:Germany, Fed. Rep. of 49:911:Nuremberg:Germany, Fed. Rep. of --- 147,160 ---- 49:228:Bonn:Germany, Fed. Rep. of 49:231:Dortmund:Germany, Fed. Rep. of 49:30:Berlin:Germany, Fed. Rep. of + 49:335:Frankfurt/Oder:Germany, Fed. Rep. of + 49:341:Leipzig:Germany, Fed. Rep. of + 49:351:Dresden:Germany, Fed. Rep. of + 49:371:Chemnitz:Germany, Fed. Rep. of 49:40:Hamburg:Germany, Fed. Rep. of 49:421:Bremen:Germany, Fed. Rep. of 49:511:Hannover:Germany, Fed. Rep. of ! 49:69:Frankfurt/Main:Germany, Fed. Rep. of 49:711:Stuttgart:Germany, Fed. Rep. of 49:89:Munich:Germany, Fed. Rep. of 49:911:Nuremberg:Germany, Fed. Rep. of -- Ulf Kieber <{uk1, news}@irz.inf.tu-dresden.de>; ; Don't expect me to be a breeder, and I won't assume you're a fag. From owner-freebsd-bugs Thu Jul 20 01:23:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA27593 for bugs-outgoing; Thu, 20 Jul 1995 01:23:15 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id BAA27581 for ; Thu, 20 Jul 1995 01:23:08 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA09318; Thu, 20 Jul 1995 10:23:02 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA12026 for bugs@FreeBSD.org; Thu, 20 Jul 1995 10:23:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA16788 for bugs@FreeBSD.org; Thu, 20 Jul 1995 08:39:41 +0200 From: J Wunsch Message-Id: <199507200639.IAA16788@uriah.heep.sax.de> Subject: Re: FW: auto-logout To: bugs@FreeBSD.org Date: Thu, 20 Jul 1995 08:39:41 +0200 (MET DST) Reply-To: bugs@FreeBSD.org In-Reply-To: from "FreeBSD Mailing List drop" at Jul 19, 95 03:42:38 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 803 Sender: bugs-owner@FreeBSD.org Precedence: bulk As FreeBSD Mailing List drop wrote: > > Less limiting, but also less illuminating for your users. set > autologout=0 makes it pretty clear that it can be set to another time if > they so desire. If they just delete the unset, they then have the default > autologout time. Instead of hacking compile-time options behind the scenes, admins that like to change this globally are free to put it into /etc/csh.cshrc. Why do many people prefer compile-time hacking instead of proper run-time configuration? Also seen as an advise in Usenet regarding sendmail's feature of canonicalizing addresses via DNS, where FEATURE(nocanonify) is the appropriate answer. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Thu Jul 20 01:23:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA27629 for bugs-outgoing; Thu, 20 Jul 1995 01:23:30 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id BAA27582 for ; Thu, 20 Jul 1995 01:23:09 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA09333; Thu, 20 Jul 1995 10:23:06 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA12034; Thu, 20 Jul 1995 10:23:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA16822; Thu, 20 Jul 1995 08:41:47 +0200 From: J Wunsch Message-Id: <199507200641.IAA16822@uriah.heep.sax.de> Subject: Re: kern/625: keyboard lockup during boot and forevcer after To: henrich@crh.cl.msu.edu Date: Thu, 20 Jul 1995 08:41:47 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199507192130.OAA11522@freefall.cdrom.com> from "henrich@crh.cl.msu.edu" at Jul 19, 95 02:30:03 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 625 Sender: bugs-owner@FreeBSD.org Precedence: bulk As henrich@crh.cl.msu.edu wrote: > > If I press a key during the boot: prompt, or with the OS-BS boot, > manager or if I do a soft reset (not coming up from a power up) > When the login: prompt arrives the keyboard is nonfunctional, Num Lock > is not lit, etc.. With either console driver, or only with syscons? I don't think pcvt's keyboard code is better, but this would help us decide whether it's the console driver or (almost unimaginable) the boot code. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Thu Jul 20 04:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id EAA05010 for bugs-outgoing; Thu, 20 Jul 1995 04:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id EAA05000 ; Thu, 20 Jul 1995 04:40:01 -0700 Date: Thu, 20 Jul 1995 04:40:01 -0700 Message-Id: <199507201140.EAA05000@freefall.cdrom.com> From: root@xaa.stack.urc.tue.nl Reply-To: root@xaa.stack.urc.tue.nl To: freebsd-bugs Subject: bin/626: ruptime doesn't like big uptimes In-Reply-To: Your message of Thu, 20 Jul 1995 13:33:46 +0200 <199507201133.NAA01441@xaa.stack.urc.tue.nl> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 626 >Category: bin >Synopsis: ruptime doesn't like uptimes > 1 year >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Jul 20 04:40:01 1995 >Originator: Mark Huizer >Organization: Stack, Eindhoven University of Technology >Release: FreeBSD 2.0-BUILT-19950622 i386 >Environment: Network with a machine that is 377 days up >Description: A machine with uptime >1 year appears wrong in the ruptime list >How-To-Repeat: ruptime at our domain gives... at up 9+03:35, 0 users, load 0.00, 0.00, 0.00 drakar up 2+23:12, 0 users, load 0.00, 0.00, 0.00 gem up ??:??, 0 users, load 0.00, 0.00, 0.00 sensus down 21:43 skynet up 13+15:30, 0 users, load 0.23, 0.10, 0.08 snail up 4:52, 0 users, load 0.04, 0.03, 0.07 terra up 29+02:40, 2 users, load 0.30, 0.23, 0.00 test1 up 12+20:58, 2 users, load 0.00, 0.00, 0.00 test2 up 33+21:24, 1 user, load 0.01, 0.01, 0.00 test4 up 2+19:55, 0 users, load 0.00, 0.00, 0.00 triple up 16+11:29, 4 users, load 1.06, 1.01, 1.02 turtle up 1+21:15, 17 users, load 0.68, 0.75, 0.69 www2 up 0:31, 1 user, load 0.00, 0.00, 0.00 xaa up 0:40, 4 users, load 0.06, 0.06, 0.01 zen up 3+21:15, 7 users, load 0.12, 0.12, 0.14 >Fix: *** ruptime.c Wed Jun 14 13:35:30 1995 --- ruptime.c.new Thu Jul 20 13:27:36 1995 *************** *** 196,203 **** static char resbuf[32]; int days, hours, minutes; ! if (tval < 0 || tval > DAYSPERNYEAR * SECSPERDAY) { ! (void)snprintf(resbuf, sizeof(resbuf), " %s ??:??", updown); return (resbuf); } /* round to minutes. */ --- 196,203 ---- static char resbuf[32]; int days, hours, minutes; ! if (tval < 0 /* || tval > DAYSPERNYEAR * SECSPERDAY */ ) { ! (void)snprintf(resbuf, sizeof(resbuf), " %s ??:??", updown); return (resbuf); } /* round to minutes. */ *************** *** 208,217 **** hours %= HOURSPERDAY; if (days) (void)snprintf(resbuf, sizeof(resbuf), ! "%s %2d+%02d:%02d", updown, days, hours, minutes); else (void)snprintf(resbuf, sizeof(resbuf), ! "%s %2d:%02d", updown, hours, minutes); return (resbuf); } --- 208,217 ---- hours %= HOURSPERDAY; if (days) (void)snprintf(resbuf, sizeof(resbuf), ! "%s %4d+%02d:%02d", updown, days, hours, minutes); else (void)snprintf(resbuf, sizeof(resbuf), ! "%s %2d:%02d", updown, hours, minutes); return (resbuf); } >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jul 20 08:20:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA11263 for bugs-outgoing; Thu, 20 Jul 1995 08:20:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA11256 ; Thu, 20 Jul 1995 08:20:02 -0700 Date: Thu, 20 Jul 1995 08:20:02 -0700 Message-Id: <199507201520.IAA11256@freefall.cdrom.com> From: vak@cronyx.ru Reply-To: vak@cronyx.ru To: freebsd-bugs Subject: kern/627: vidcontrol causes crash when booted with sc0 disabled In-Reply-To: Your message of Thu, 20 Jul 1995 19:12:13 +0400 <199507201512.TAA00322@hanoi.net.kiae.su> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 627 >Category: kern >Synopsis: vidcontrol causes crash when booted with sc0 disabled >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 20 08:20:01 1995 >Originator: Serge V.Vakulenko >Organization: Cronyx Ltd. >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: >Description: When the system is loaded with the sc0 driver configured, but disabled (in kernel config mode), then any vidcontrol call causes the system crash. >How-To-Repeat: 1. Boot the kernel with -h -c options. 2. Disable the sc0 driver (disable sc0). Quit the config mode (quit). 3. After the system is loaded, try, say, "vidcontrol -c blink". The system will crash. >Fix: Apply the following patch: --- syscons205.c Tue May 30 12:03:13 1995 +++ syscons.c Thu Jul 20 17:16:29 1995 @@ -303,7 +303,7 @@ { int unit = minor(dev); - if (unit > MAXCONS || unit < 0) + if (! init_done || unit > MAXCONS || unit < 0) return(NULL); if (unit == MAXCONS) return CONSOLE_TTY; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jul 20 10:03:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA14531 for bugs-outgoing; Thu, 20 Jul 1995 10:03:53 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id KAA14524 for ; Thu, 20 Jul 1995 10:03:47 -0700 Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.11/8.6.9) id NAA00171; Thu, 20 Jul 1995 13:00:32 -0400 From: Charles Henrich Message-Id: <199507201700.NAA00171@crh.cl.msu.edu> Subject: Re: kern/625: keyboard lockup during boot and forevcer after To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 20 Jul 1995 13:00:32 -0400 (EDT) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199507200641.IAA16822@uriah.heep.sax.de> from "J Wunsch" at Jul 20, 95 08:41:47 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 398 Sender: bugs-owner@FreeBSD.org Precedence: bulk > With either console driver, or only with syscons? I don't think > pcvt's keyboard code is better, but this would help us decide whether > it's the console driver or (almost unimaginable) the boot code. I just tried pcvt and everything works as advertised.. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Thu Jul 20 11:37:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA18287 for bugs-outgoing; Thu, 20 Jul 1995 11:37:01 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA18281 for ; Thu, 20 Jul 1995 11:36:53 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA04386; Fri, 21 Jul 1995 04:32:13 +1000 Date: Fri, 21 Jul 1995 04:32:13 +1000 From: Bruce Evans Message-Id: <199507201832.EAA04386@godzilla.zeta.org.au> To: dillon@blob.best.net, terry@cs.weber.edu Subject: Re: possible ffs_vget() race condition Cc: bugs@FreeBSD.org, davidg@Root.COM, mckusick@McKusick.COM Sender: bugs-owner@FreeBSD.org Precedence: bulk >A lot of the system configuration stuff is bogus/unportable/both. The >use of manifest constants to do the descriptor structs in sysctl.h >is patently bogus. >The CTLTYPE_QUAD definition and the size variant CTLTYPE_INT are both >rather annoying; these should be sized values, and QUAD should probably >not be allowed at all, since 64 bit values are (as yet) intolerably >unportable. Enumerated or defined types are more flexible. You can support an arbitrary number of scalar types or type/representation pairs by converting the values using a routine indexed by the type. >Not to mention the use of a shift of an embeded constant '63' and a -1 >to get the RLIM_INFINITY value in resource.h. >Instead of (~(u_quad_t)0). The shift method has the advantage of giving the correct result :-). You meant ((~(u_quad_t)0) >> 1). This depends on u_quad_t being larger than int. Bruce From owner-freebsd-bugs Thu Jul 20 14:10:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA24324 for bugs-outgoing; Thu, 20 Jul 1995 14:10:06 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA24317 ; Thu, 20 Jul 1995 14:10:04 -0700 Date: Thu, 20 Jul 1995 14:10:04 -0700 Message-Id: <199507202110.OAA24317@freefall.cdrom.com> From: Wolfram Schneider Reply-To: Wolfram Schneider To: freebsd-bugs Subject: bin/628: sa(1) print not processes which call only ounces In-Reply-To: Your message of Thu, 20 Jul 1995 22:50:21 +0200 <199507202050.WAA03081@localhost.cs.tu-berlin.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 628 >Category: bin >Synopsis: sa(1) print not processes which call only ounces >Confidential: yes >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 20 14:10:03 1995 >Originator: Wolfram Schneider >Organization: Hohenschoensiehstenich >Release: FreeBSD 2.0-ALPHA i386 >Environment: OS out of date >Description: sa(1) print not processes which call only onces >How-To-Repeat: cp /bin/ls /tmp/ELES /tmp/ELES sa | grep ELES | wc 0 0 0 # second try /tmp/ELES sa |grep ELES 2 0.00re 0.00cp 0avio 10229k ELES >Fix: --- pdb.c.old Mon Sep 26 22:22:56 1994 +++ pdb.c Thu Jul 20 19:30:03 1995 @@ -249,7 +249,7 @@ goto next; } if (!aflag && - ((ci.ci_flags & CI_UNPRINTABLE) != 0 || ci.ci_calls <= 1)) { + ((ci.ci_flags & CI_UNPRINTABLE) != 0 || ci.ci_calls < 1)) { /* put into ***other */ add_ci(&ci, &ci_other); goto next; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jul 20 15:03:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA26593 for bugs-outgoing; Thu, 20 Jul 1995 15:03:31 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA26586 for ; Thu, 20 Jul 1995 15:03:29 -0700 Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.11/8.6.9) id SAA00232; Thu, 20 Jul 1995 18:04:32 -0400 Date: Thu, 20 Jul 1995 18:04:32 -0400 From: Charles Henrich Message-Id: <199507202204.SAA00232@crh.cl.msu.edu> To: henrich@crh.cl.msu.edu, freebsd-bugs@freebsd.org Subject: Re: kern/625: keyboard lockup during boot and forevcer after Newsgroups: lists.freebsd.bugs References: <3um2he$16ag@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #3 (NOV) Sender: bugs-owner@freebsd.org Precedence: bulk In lists.freebsd.bugs you write: >> With either console driver, or only with syscons? I don't think >> pcvt's keyboard code is better, but this would help us decide whether >> it's the console driver or (almost unimaginable) the boot code. >I just tried pcvt and everything works as advertised.. >-Crh I lied, it still fails occasonially :( -Crh -- Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Thu Jul 20 15:27:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA27097 for bugs-outgoing; Thu, 20 Jul 1995 15:27:02 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id PAA27091 for ; Thu, 20 Jul 1995 15:27:00 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA03618; Thu, 20 Jul 95 16:19:02 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9507202219.AA03618@cs.weber.edu> Subject: Re: possible ffs_vget() race condition To: bde@zeta.org.au (Bruce Evans) Date: Thu, 20 Jul 95 16:19:02 MDT Cc: dillon@blob.best.net, bugs@freebsd.org, davidg@Root.COM, mckusick@McKusick.COM In-Reply-To: <199507201832.EAA04386@godzilla.zeta.org.au> from "Bruce Evans" at Jul 21, 95 04:32:13 am X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@freebsd.org Precedence: bulk > The shift method has the advantage of giving the correct result :-). > You meant ((~(u_quad_t)0) >> 1). This depends on u_quad_t being > larger than int. I don't understand why this would depend on quad being larger than int; because the naked 1 is of type int? Then quad would need to be >= int, not necessarily larger. I think we can guarantee quad >= long >= int. 8-). Better than depending on quad == 64 bits in any case. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Thu Jul 20 16:11:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id QAA28315 for bugs-outgoing; Thu, 20 Jul 1995 16:11:19 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA28308 for ; Thu, 20 Jul 1995 16:11:15 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id JAA10420; Fri, 21 Jul 1995 09:08:47 +1000 Date: Fri, 21 Jul 1995 09:08:47 +1000 From: Bruce Evans Message-Id: <199507202308.JAA10420@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@cs.weber.edu Subject: Re: possible ffs_vget() race condition Cc: bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk [Cc list trimmed] >> The shift method has the advantage of giving the correct result :-). >> You meant ((~(u_quad_t)0) >> 1). This depends on u_quad_t being >> larger than int. >I don't understand why this would depend on quad being larger than int; >because the naked 1 is of type int? I should have said larger or the same size as an int. ~(foo_t)0 is usually wrong if foo_t is shorter than an int (it is the same as ~0 because of the broken ANSI value-preserving promotion rules), so using it gives a bad example for beginners to follow. ((foo_t)(-1)) always works although you may need further casts (e.g., on the i386, (u_short)(-1) is (int)0xffff, so shifting right 1 works right but shifting left 16 and then shifting right gives surprising results. The type of the shift count doesn't affect the type of the result. Bruce From owner-freebsd-bugs Thu Jul 20 17:29:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA00328 for bugs-outgoing; Thu, 20 Jul 1995 17:29:47 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA00322 for ; Thu, 20 Jul 1995 17:29:46 -0700 Received: from shell1.best.com (shell1 [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id RAA04918 for ; Thu, 20 Jul 1995 17:29:45 -0700 Received: (root@localhost) by shell1.best.com (8.6.12/8.6.5) id RAA21522; Thu, 20 Jul 1995 17:29:43 -0700 Date: Thu, 20 Jul 1995 17:29:43 -0700 From: Matt Dillon Message-Id: <199507210029.RAA21522@shell1.best.com> To: bugs@freebsd.org Subject: verification of ffs_vget() bug Sender: bugs-owner@freebsd.org Precedence: bulk Here are some real numbers... the collision occurs much more often then I would have thought in a heavily loaded system! I believe this solves the 'dup alloc' panic we were getting in the inode allocation routines. I still will not know for sure for another day or two to see if the machine panics again. The panics generally occured once a day, but it is obvious from the numbers below that the actual inodes were getting munged much more often then that. (my temporary ffs_vget() code is included below as well) -Matt Jul 20 12:40:09 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 54994 Jul 20 12:49:00 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55046 Jul 20 12:54:24 shell1 /kernel: INODE COLLISION: mount f21a3a00 ino 38675 Jul 20 12:55:58 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 54978 Jul 20 13:08:39 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55135 Jul 20 13:21:34 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 54978 Jul 20 13:21:43 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 54984 Jul 20 13:34:21 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55177 Jul 20 13:40:50 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55001 Jul 20 13:49:44 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 53837 Jul 20 14:04:19 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55045 Jul 20 14:09:02 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 55169 Jul 20 14:30:16 shell1 /kernel: INODE COLLISION: mount f21a3e00 ino 53837 Jul 20 15:04:44 shell1 /kernel: INODE COLLISION: mount f219f200 ino 39130 Jul 20 17:09:37 shell1 /kernel: INODE COLLISION: mount f219f200 ino 92571 Jul 20 17:11:46 shell1 /kernel: INODE COLLISION: mount f21a3a00 ino 222911 /* * Look up a FFS dinode number to find its incore vnode, otherwise read it * in from disk. If it is in core, wait for the lock bit to clear, then * return the inode locked. Detection and handling of mount points must be * done by the calling routine. */ int ffs_inode_hash_lock = 0; int ffs_vget(mp, ino, vpp) struct mount *mp; ino_t ino; struct vnode **vpp; { register struct fs *fs; register struct inode *ip; struct ufsmount *ump; struct buf *bp; struct vnode *vp; dev_t dev; int type, error; ump = VFSTOUFS(mp); dev = ump->um_dev; if ((*vpp = ufs_ihashget(dev, ino)) != NULL) return (0); /* * lockout the creation of new entries in the FFS * hash table in case getnewvnode/MALLOC blocks, * otherwise a duplicate could occur! */ if (ffs_inode_hash_lock) { while (ffs_inode_hash_lock) { ffs_inode_hash_lock = -1; tsleep(&ffs_inode_hash_lock, PVM, "ffsinohs", 0); } /* * someone else allocated (dev,ino) before we could */ if ((*vpp = ufs_ihashget(dev, ino)) != NULL) { printf("INODE COLLISION: mount %08lx ino %d\n", (u_long)mp, (int)ino ); return (0); } } ffs_inode_hash_lock = 1; /* Allocate a new vnode/inode. */ type = ump->um_devvp->v_tag == VT_MFS ? M_MFSNODE : M_FFSNODE; /* XXX */ if ((error = getnewvnode(VT_UFS, mp, ffs_vnodeop_p, &vp)) != 0) { if (ffs_inode_hash_lock < 0) { wakeup(&ffs_inode_hash_lock); } ffs_inode_hash_lock = 0; *vpp = NULL; return (error); } MALLOC(ip, struct inode *, sizeof(struct inode), type, M_WAITOK); bzero((caddr_t)ip, sizeof(struct inode)); vp->v_data = ip; ip->i_vnode = vp; ip->i_fs = fs = ump->um_fs; ip->i_dev = dev; ip->i_number = ino; #ifdef QUOTA { int i; for (i = 0; i < MAXQUOTAS; i++) ip->i_dquot[i] = NODQUOT; } #endif /* * Put it onto its hash chain and lock it so that other requests * for this inode will block if they arrive while we are sleeping * waiting for old data structures to be purged or for the * contents of the disk portion of this inode to be read. */ ufs_ihashins(ip); /* * Wakeup anybody blocked in our lock */ if (ffs_inode_hash_lock < 0) { wakeup(&ffs_inode_hash_lock); } ffs_inode_hash_lock = 0; /* Read in the disk contents for the inode, copy into the inode. */ error = bread(ump->um_devvp, fsbtodb(fs, ino_to_fsba(fs, ino)), (int)fs->fs_bsize, NOCRED, &bp); if (error) { /* * The inode does not contain anything useful, so it would * be misleading to leave it on its hash chain. With mode * still zero, it will be unlinked and returned to the free * list by vput(). */ vput(vp); brelse(bp); *vpp = NULL; return (error); } ip->i_din = *((struct dinode *)bp->b_data + ino_to_fsbo(fs, ino)); brelse(bp); /* * Initialize the vnode from the inode, check for aliases. * Note that the underlying vnode may have changed. */ error = ufs_vinit(mp, ffs_specop_p, FFS_FIFOOPS, &vp); if (error) { vput(vp); *vpp = NULL; return (error); } /* * Finish inode initialization now that aliasing has been resolved. */ ip->i_devvp = ump->um_devvp; VREF(ip->i_devvp); /* * Set up a generation number for this inode if it does not * already have one. This should only happen on old filesystems. */ if (ip->i_gen == 0) { if (++nextgennumber < (u_long)time.tv_sec) nextgennumber = time.tv_sec; ip->i_gen = nextgennumber; if ((vp->v_mount->mnt_flag & MNT_RDONLY) == 0) ip->i_flag |= IN_MODIFIED; } /* * Ensure that uid and gid are correct. This is a temporary * fix until fsck has been changed to do the update. */ if (fs->fs_inodefmt < FS_44INODEFMT) { /* XXX */ ip->i_uid = ip->i_din.di_ouid; /* XXX */ ip->i_gid = ip->i_din.di_ogid; /* XXX */ } /* XXX */ *vpp = vp; return (0); } From owner-freebsd-bugs Thu Jul 20 17:34:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA00522 for bugs-outgoing; Thu, 20 Jul 1995 17:34:56 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA00516 for ; Thu, 20 Jul 1995 17:34:55 -0700 Received: (root@localhost) by blob.best.net (8.6.12/8.6.5) id RAA05301; Thu, 20 Jul 1995 17:34:17 -0700 Date: Thu, 20 Jul 1995 17:34:17 -0700 From: Matt Dillon Message-Id: <199507210034.RAA05301@blob.best.net> To: root@corbin.Root.COM Cc: bugs@freebsd.org Subject: Re: possible ffs_vget() race condition Sender: bugs-owner@freebsd.org Precedence: bulk I think a better solution would be to have the vnode allocation routine install dummy functions/data such that it can be freed at any time. This would incidently solve the second problem as well (where sync comes along and gets confused by the partially allocated vnode that someone mentioned a few messages back). -Matt >> Doesn't vrele() call VOP_INACTIVE and therefore >> ufs_inactive, which will try to dereference >> vp->v_data which is NULL? > > Hmmm. You're right. Any thoughts, Kirk? What happens if the v_op pointer is >set to NULL before doing the vrele()? ...Does the VOP_INACTIVE become a nop, or >does the machine panic when dereferencing the pointer? :-) > The only other solution I can think of would be to create a special routine >for releasing vnodes with no FS specific data yet attached...but that seems >like another kludge. > >-DG > From owner-freebsd-bugs Thu Jul 20 20:19:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id UAA04871 for bugs-outgoing; Thu, 20 Jul 1995 20:19:33 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id UAA04863 for ; Thu, 20 Jul 1995 20:19:31 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id UAA00562; Thu, 20 Jul 1995 20:19:06 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id UAA07026; Thu, 20 Jul 1995 20:20:06 -0700 Message-Id: <199507210320.UAA07026@corbin.Root.COM> To: Matt Dillon cc: bugs@freebsd.org Subject: Re: verification of ffs_vget() bug In-reply-to: Your message of "Thu, 20 Jul 95 17:29:43 PDT." <199507210029.RAA21522@shell1.best.com> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 20 Jul 1995 20:20:05 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk > Here are some real numbers... the collision occurs much more often > then I would have thought in a heavily loaded system! I'll say! John and I went through the possible failure scenarios and we think that severe problems resulting in a system crash would be rare on most systems (which is obviously proven true), but that cache coherency problems and other strange behavior might be likely. > (my temporary ffs_vget() code is included below as well) Actually, you're fix looks pretty good. After talking with Kirk awhile about your fix, other possible fixes, etc, I think we've concluded that doing the global lock is as good a fix as any for the problem, and appears to be the lowest overhead solution. Thanks for the fix... -DG From owner-freebsd-bugs Thu Jul 20 20:30:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id UAA05402 for bugs-outgoing; Thu, 20 Jul 1995 20:30:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id UAA05391 ; Thu, 20 Jul 1995 20:30:03 -0700 Date: Thu, 20 Jul 1995 20:30:03 -0700 Message-Id: <199507210330.UAA05391@freefall.cdrom.com> From: loodvrij@gridpoint.com Reply-To: loodvrij@gridpoint.com To: freebsd-bugs Subject: kern/629: user mode ppp dies when sending In-Reply-To: Your message of Thu, 20 Jul 95 19:40 AKDT Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 629 >Category: kern >Synopsis: user mode ppp dies when sending >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 20 20:30:01 1995 >Originator: Bruce 'Loodvrij' Keeler >Organization: Bruce J. Keeler Internet: loodvrij@cyb.alaska.net >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 486-66, Adaptec SCSI, 16Megs, 16550A's, external Microcom 28.8 modem >Description: PPP works fine for a while, but when sending anything more than small amouts of data out it stops receiving. Packets go out, but none come back. I know data is being received by the modem, and I know that the ppp process recieves it and writes it to the tun, but then it just disappears. >How-To-Repeat: Try to send any serious amounts of data out over a ppp link. >Fix: Wish I knew. I've put debugging stuff in ppp so I'm sure its writing to the tunnel, but printf's placed in tunwrite() stop when the problem appears. I'll carry on investigating, but I'm about out of ideas, so I thought I'd turn it over to the pros. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jul 21 01:18:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA15113 for bugs-outgoing; Fri, 21 Jul 1995 01:18:09 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id BAA15107 for ; Fri, 21 Jul 1995 01:18:05 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from omega.physik.fu-berlin.de (130.133.3.51) with smtp id ; Fri, 21 Jul 95 10:17 MEST Received: by omega.physik.fu-berlin.de; id AA25956; Fri, 21 Jul 1995 10:17:53 +0200 From: Thomas Graichen Message-Id: <9507210817.AA25956@omega.physik.fu-berlin.de> Subject: 3 ways to crash FreeBSD (2.0.5 and 950412-SNAP) To: bugs@freebsd.org Date: Fri, 21 Jul 1995 10:17:53 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4107 Sender: bugs-owner@freebsd.org Precedence: bulk hello - here are my 3 ways to crash FreeBSD: * simply hit ctrl-alt-del while booting multiple times -> at the probes of the floppies and/or the wd drives the system stops with a panic (i'va also managed it to panic the system TWICE at once) - this is total reproducable - if it is'nt for you - please send me a mail and i'll give you any more information you need (this happens on 950412-SNAP and 2.0.5 RELEASE) * simply do the following as root at the console: modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o (this will giva an error) modunload -n star_saver this is also total reproducable on 950412-SNAP and 2.0.5 RELEASE and leads also to a kernel panic * the last is a problem i have since the early january SNAP's - this is what i've written some times before to jordan: the system crashes then i log in (but couriously not if somebody else or root does this) via xdm - /var/log/messages says Feb 9 10:49:44 julia /vmunix: Error in getattr: 70 Feb 9 10:49:45 julia /vmunix: Feb 9 10:49:45 julia /vmunix: Feb 9 10:49:45 julia /vmunix: Fatal trap 12: page fault while in kernel mode Feb 9 10:49:45 julia /vmunix: fault virtual address = 0x40 Feb 9 10:49:45 julia /vmunix: fault code = supervisor read, page not present Feb 9 10:49:45 julia /vmunix: instruction pointer = 0x8:0xf0125b1b Feb 9 10:49:45 julia /vmunix: code segment = base 0x0, limit 0xffff f, type 0x1b Feb 9 10:49:45 julia /vmunix: = DPL 0, pres 1, def32 1, gran1 Feb 9 10:49:45 julia /vmunix: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 9 10:49:45 julia /vmunix: current process = 122 (xdm) Feb 9 10:49:45 julia /vmunix: interrupt mask = Feb 9 10:49:46 julia /vmunix: panic: page fault Feb 9 10:49:46 julia /vmunix: Feb 9 10:49:46 julia /vmunix: syncing disks... 28 28 25 21 16 10 1 done its absolutely reproducable: reboot - xdm is started - i try to login - the xdm login window disappears - i here the disk writing the coredump - but the problem did'nt appear if somebody else logs in (who has his homedirectory on another machine - but both dec alpha's osf/1 3.0 - we are mounting the homedirs via amd with nfs) - my nfs-homedir-server says: Feb 9 10:45:48 sirius vmunix: NFS server: stale file handle fs(8,2054) file 116839 gen 792314558 Feb 9 10:45:48 sirius vmunix: getattr, client address = 130.133.3.235, errno 22 it only happens sometimes - but if - it will happen at any try to login after the system has rebooted after that panic - loging in as root and doing a "su - myusername" then logout and login as me works then - if you need any more information - please send a mail to me (by the way - we have some problems with our net - because our net-segment is too long - but this should max. result in an but not in an kernel panic!) * and one last thing: we mount all our homedir's via amd - which mounts them if they are needed (user logs in) and tries to unmount them automatic if they are no longer used - but FreeBSD seems to loose the directories from time to time - that means the directory will be mounted again and again (this way i sometimes get 20 times the same dir mounted) - and after each of these overmountings i get an "getting cwd failed" from my tcsh (because the directory is new ... mounted) - do you have any ideas ? to all the points above - i'll try to give you all the information you need and as far as i can all the help i may give you - thanks in advance - t _______________________________________________________||_____________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| ___________________________||____email: graichen@omega.physik.fu-berlin.de____ From owner-freebsd-bugs Fri Jul 21 01:56:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id BAA16730 for bugs-outgoing; Fri, 21 Jul 1995 01:56:33 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id BAA16680 for ; Fri, 21 Jul 1995 01:56:19 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA25145; Fri, 21 Jul 1995 10:55:17 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA25826; Fri, 21 Jul 1995 10:55:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA20479; Fri, 21 Jul 1995 08:11:57 +0200 From: J Wunsch Message-Id: <199507210611.IAA20479@uriah.heep.sax.de> Subject: Re: kern/625: keyboard lockup during boot and forevcer after To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Fri, 21 Jul 1995 08:11:57 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com, sos@freebsd.org In-Reply-To: <199507201700.NAA00171@crh.cl.msu.edu> from "Charles Henrich" at Jul 20, 95 01:00:32 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 526 Sender: bugs-owner@freebsd.org Precedence: bulk As Charles Henrich wrote: > > > With either console driver, or only with syscons? I don't think > > pcvt's keyboard code is better, but this would help us decide whether > > it's the console driver or (almost unimaginable) the boot code. > > I just tried pcvt and everything works as advertised.. Hmm, i believe that's already the second report of this kind. Søren, any clues? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jul 21 02:05:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id CAA17503 for bugs-outgoing; Fri, 21 Jul 1995 02:05:18 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id CAA17490 ; Fri, 21 Jul 1995 02:04:44 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA25187; Fri, 21 Jul 1995 10:56:08 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA25829; Fri, 21 Jul 1995 10:55:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA20508; Fri, 21 Jul 1995 08:14:11 +0200 From: J Wunsch Message-Id: <199507210614.IAA20508@uriah.heep.sax.de> Subject: Re: kern/625: keyboard lockup during boot and forevcer after To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Fri, 21 Jul 1995 08:14:10 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.org, sos@FreeBSD.org, hm@altona.hamburg.com (Hellmuth Michaelis) In-Reply-To: <199507202204.SAA00232@crh.cl.msu.edu> from "Charles Henrich" at Jul 20, 95 06:04:32 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 609 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Charles Henrich wrote: > > In lists.freebsd.bugs you write: > > >> With either console driver, or only with syscons? I don't think > >> pcvt's keyboard code is better, but this would help us decide whether > >> it's the console driver or (almost unimaginable) the boot code. > > >I just tried pcvt and everything works as advertised.. > > >-Crh > > I lied, it still fails occasonially :( What are the occasions? Can you try ``options "PCVT_SCANSET=2"''? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jul 21 08:30:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA06121 for bugs-outgoing; Fri, 21 Jul 1995 08:30:41 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id IAA06101 for ; Fri, 21 Jul 1995 08:30:32 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from omega.physik.fu-berlin.de (130.133.3.51) with smtp id ; Fri, 21 Jul 95 17:30 MEST Received: by omega.physik.fu-berlin.de; id AA08034; Fri, 21 Jul 1995 17:30:25 +0200 From: Thomas Graichen Message-Id: <9507211530.AA08034@omega.physik.fu-berlin.de> Subject: small change to boot.c To: bugs@freebsd.org Date: Fri, 21 Jul 1995 17:30:24 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1266 Sender: bugs-owner@freebsd.org Precedence: bulk hello the following code i sent to rodney grimes - and he said i should send it to bugs - here is it: this is a very small patch for /usr/src/sys/i386/boot/biosboot/boot.c --- cut here --- --- boot.c.org Wed May 31 23:42:38 1995 +++ boot.c Thu Jul 20 16:50:47 1995 @@ -245,7 +245,7 @@ /********************************************************/ /* Load the string table */ /********************************************************/ - printf("+0x%x+0x%x] ", sizeof(int), i); + printf("+0x%x+0x%x]\n", sizeof(int), i); xread((void *)addr, i); addr += i; --- cut here --- this avaids the "lineoverflow" which you'll always get at 80 column displays at bootup t _______________________________________________________||_____________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| ___________________________||____email: graichen@omega.physik.fu-berlin.de____ From owner-freebsd-bugs Fri Jul 21 10:30:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA13007 for bugs-outgoing; Fri, 21 Jul 1995 10:30:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA12998 ; Fri, 21 Jul 1995 10:30:02 -0700 Date: Fri, 21 Jul 1995 10:30:02 -0700 Message-Id: <199507211730.KAA12998@freefall.cdrom.com> From: Lars Fredriksen Reply-To: Lars Fredriksen To: freebsd-bugs Subject: i386/631: if_ix do not support bpf and multicast(?) In-Reply-To: Your message of Fri, 21 Jul 1995 12:18:00 -0500 <199507211718.MAA01159@lxf5415.lisleil.attgis.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 631 >Category: i386 >Synopsis: if_ix does not support bpf, nor does it appear to support MC. >Confidential: yes >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 21 10:30:01 1995 >Originator: Lars Fredriksen >Organization: >Release: FreeBSD-current >Environment: >Description: The if_ix (Intel EtherExpress) driver doesn't support the bpf interface. Nor does it seem to support MultiCast. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jul 21 10:40:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA13752 for bugs-outgoing; Fri, 21 Jul 1995 10:40:25 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id KAA13742 for ; Fri, 21 Jul 1995 10:40:22 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA13495; Fri, 21 Jul 1995 10:40:30 -0700 From: "Rodney W. Grimes" Message-Id: <199507211740.KAA13495@gndrsh.aac.dev.com> Subject: Re: i386/631: if_ix do not support bpf and multicast(?) To: fredriks@cuuxb.att.com Date: Fri, 21 Jul 1995 10:40:30 -0700 (PDT) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199507211730.KAA12998@freefall.cdrom.com> from "Lars Fredriksen" at Jul 21, 95 10:30:02 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1150 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > >Number: 631 > >Category: i386 > >Synopsis: if_ix does not support bpf, nor does it appear to support MC. > >Confidential: yes > >Severity: serious > >Priority: medium > >Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >State: open > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Jul 21 10:30:01 1995 > >Originator: Lars Fredriksen > >Organization: > >Release: FreeBSD-current > >Environment: > > >Description: > > The if_ix (Intel EtherExpress) driver doesn't support the bpf > interface. Nor does it seem to support MultiCast. > > >How-To-Repeat: > >Fix: > >Audit-Trail: > >Unformatted: I have a submission from a person to add bpf to it, the problems is, he sent it to me and stated he fully well knew it causes lock ups and other problems. I do not have time now, or in the immediate future to debug this attempt at adding bpf to the driver. Would you like to give it a try? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Fri Jul 21 11:32:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA16527 for bugs-outgoing; Fri, 21 Jul 1995 11:32:23 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA16520 for ; Fri, 21 Jul 1995 11:32:16 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id OAA05262; Fri, 21 Jul 1995 14:31:32 -0400 From: A boy and his worm gear Message-Id: <199507211831.OAA05262@skynet.ctr.columbia.edu> Subject: Re: 3 ways to crash FreeBSD (2.0.5 and 950412-SNAP) To: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Date: Fri, 21 Jul 1995 14:31:27 -0400 (EDT) Cc: bugs@freebsd.org In-Reply-To: <9507210817.AA25956@omega.physik.fu-berlin.de> from "Thomas Graichen" at Jul 21, 95 10:17:53 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 5725 Sender: bugs-owner@freebsd.org Precedence: bulk Of all the gin joints in all the world, Thomas Graichen had to walk into mine and say: > hello - here are my 3 ways to crash FreeBSD: [three-finger salute during boot causes stange crash] Just a guess: I remember someone saying that CTRL-ALT-DEL is supposed to cause the kernel to send a signal to init to tell it to start shutting down the system. If it tries to do the same thing when init isn't running (yet), then I imagine nasty things would happen. > * simply do the following as root at the console: > > modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o > modload -u -o /tmp/saver_mod -e saver_init -q /lkm/${saver}_saver_mod.o > (this will giva an error) > modunload -n star_saver I think I fixed this one. I noticed a similar problem with the if_sl module; all the MISC type modules are suceptible to the bug. The problem is that duplicate checking (i.e. checking to see if the user is trying to load a second instance of the same module) didn't work quite right with MISC modules: there are handler routines for other module types (VFS, EXEC, etc...) which do the checking before the module is actually called for the first time, but there is no such handler function for MISC modules, and MISC modules aren't smart enough to do it themselves. What's happening is that the duplicate checking is done _after_ the module's internal initialization routine is called. By the time the kernel notices the problem, the module has already wired itself in. As part of the error handling, the kernel tries to unmap the duplicate instance of the module. This is akin to gnawing your own arm off: the next time the now-dead module's address space is referenced, the system will blow up. What you need to do to fix this is grab a new copy of /usr/src/sys/sys/lkm.h, install it (it goes in /usr/include/sys too, if you have just the lkm sources installed) and rebuild all the MISC modules. The new lkm.h has a tiny modification in the DISPATCH() macro: it makes a quick call to lkmexists() before actually trying to run the module's initialization routine. (This should be pulled into the STABLE branch if it hasn't already.) > * the last is a problem i have since the early january SNAP's - this is what > i've written some times before to jordan: > > the system crashes then i log in (but couriously not if somebody else or > root does this) via xdm - /var/log/messages says > > Feb 9 10:49:44 julia /vmunix: Error in getattr: 70 Lessee... errno 70 is Stale NFS file handle. > Feb 9 10:49:45 julia /vmunix: instruction pointer = 0x8:0xf0125b1b ^^^^^^^^ Do an 'nm /vmunix' and see if you can find a symbol with an address close to this one. This will give you a rough idea of where the system is getting hosed (though it may not point you directly at the problem). > its absolutely reproducable: reboot - xdm is started - i try to login - the > xdm login window disappears - i here the disk writing the coredump - but the > problem did'nt appear if somebody else logs in (who has his homedirectory on > another machine - but both dec alpha's osf/1 3.0 - we are mounting the > homedirs via amd with nfs) - my nfs-homedir-server says: > > Feb 9 10:45:48 sirius vmunix: NFS server: stale file handle fs(8,2054) file > 116839 gen 792314558 > Feb 9 10:45:48 sirius vmunix: getattr, client address = 130.133.3.235, errno > 22 Errno 22 is Invalid Argument. This stuff is out of my league, but it sounds like a locking problem or race condition. It happens that there have been many changes to the NFS and VM code in FreeBSD-current. You might try setting up a -current system and seeing if the problem persists. > * and one last thing: > we mount all our homedir's via amd - which mounts them if they are needed > (user logs in) and tries to unmount them automatic if they are no longer used > - but FreeBSD seems to loose the directories from time to time - that means > the directory will be mounted again and again (this way i sometimes get 20 > times the same dir mounted) - and after each of these overmountings i get an > "getting cwd failed" from my tcsh (because the directory is new ... mounted) - > do you have any ideas ? Sorry: I use amd on my system and it works fine. My configuration is probably different from yours though. (I mount each user's home directory just once and then use amd to create symlinks that point to the right directies in each filesystem. So amd mounts /q/elara/home/elara via NFS, creates a /home/elara link that points to /q/elara/home/elara, then it makes, for example, a /homes/foouser link that points to /home/elara/foouser (and a /homes/baruser that points to /home/elara/baruser, and a /homes/bazuser, etc...) This way, everyone's home directory is always /homes/. Note that I use the Berkeley amd on all my machines too. The only special thing I have to do with FreeBSD is use the resvport option.) > to all the points above - i'll try to give you all the information you need > and as far as i can all the help i may give you - thanks in advance - t Try -current first and see if the problems are still there. -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~ From owner-freebsd-bugs Fri Jul 21 13:18:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id NAA22429 for bugs-outgoing; Fri, 21 Jul 1995 13:18:44 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id NAA22422 ; Fri, 21 Jul 1995 13:18:33 -0700 Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.11/8.6.9) id QAA00324; Fri, 21 Jul 1995 16:15:10 -0400 From: Charles Henrich Message-Id: <199507212015.QAA00324@crh.cl.msu.edu> Subject: Re: kern/625: keyboard lockup during boot and forevcer after To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 21 Jul 1995 16:15:10 -0400 (EDT) Cc: freebsd-bugs@FreeBSD.org, sos@FreeBSD.org, hm@altona.hamburg.com In-Reply-To: <199507210614.IAA20508@uriah.heep.sax.de> from "J Wunsch" at Jul 21, 95 08:14:10 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 287 Sender: bugs-owner@FreeBSD.org Precedence: bulk > What are the occasions? I cant seem to pinpoint it, its pissing me off. Im going to put some debugging in the drivers and see what I can get out. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Fri Jul 21 16:18:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id QAA29385 for bugs-outgoing; Fri, 21 Jul 1995 16:18:30 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA29378 ; Fri, 21 Jul 1995 16:18:26 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id QAA21061; Fri, 21 Jul 1995 16:17:47 -0700 To: A boy and his worm gear cc: graichen@omega.physik.fu-berlin.de (Thomas Graichen), bugs@freebsd.org Subject: Re: 3 ways to crash FreeBSD (2.0.5 and 950412-SNAP) In-reply-to: Your message of "Fri, 21 Jul 1995 14:31:27 EDT." <199507211831.OAA05262@skynet.ctr.columbia.edu> Date: Fri, 21 Jul 1995 16:17:47 -0700 Message-ID: <21059.806368667@time.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > (This should be pulled into the STABLE branch if it hasn't already.) David has stated that he won't merge stuff into the STABLE branch unless the author sends him a context diff. So, there you go - ball's in your court on that one still! :) Jordan From owner-freebsd-bugs Sat Jul 22 09:49:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id JAA03067 for bugs-outgoing; Sat, 22 Jul 1995 09:49:41 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id JAA03061 for ; Sat, 22 Jul 1995 09:49:40 -0700 Received: (root@localhost) by blob.best.net (8.6.12/8.6.5) id JAA11816; Sat, 22 Jul 1995 09:49:33 -0700 Date: Sat, 22 Jul 1995 09:49:33 -0700 From: Matt Dillon Message-Id: <199507221649.JAA11816@blob.best.net> To: bugs@freebsd.org Subject: Here's a new one: /bin/mv truncates destination if dest is NFS Sender: bugs-owner@freebsd.org Precedence: bulk Here's another one... /bin/mv truncates the destination file if the destination is an NFS filesytem. * Create a 24254 byte file * as root, chgrp the file to a group the user has no permissions on * as the user, /bin/mv file dest where dest is on an NFS mount. What happens is that the fchown() that /bin/mv does blows away the last dirty buffer from the filecopy (which used 8K chunks) that /bin/mv did, so the output file winds up being only 16K long!! This only occurs when fchown() fails due to not being able to transfer the group permissions to the destination file, i.e. when you get: mv2: /home/au/z: set owner/group: Operation not permitted If I put a sleep() in just before the fchown() and manually /bin/sync after the file is written but before the fchown(), the file size comes out properly. -Matt From owner-freebsd-bugs Sat Jul 22 15:22:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA06786 for bugs-outgoing; Sat, 22 Jul 1995 15:22:12 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id PAA06777 for ; Sat, 22 Jul 1995 15:22:07 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA04195; Sun, 23 Jul 1995 00:21:29 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA07522; Sun, 23 Jul 1995 00:38:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA26741; Sun, 23 Jul 1995 00:10:37 +0200 From: J Wunsch Message-Id: <199507222210.AAA26741@uriah.heep.sax.de> Subject: Re: small change to boot.c To: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Date: Sun, 23 Jul 1995 00:10:37 +0200 (MET DST) Cc: bugs@FreeBSD.org In-Reply-To: <9507211530.AA08034@omega.physik.fu-berlin.de> from "Thomas Graichen" at Jul 21, 95 05:30:24 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 650 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Thomas Graichen wrote: > > hello > > the following code i sent to rodney grimes - and he said i should send it to > bugs - here is it: about to commit it... > addr += i; > --- cut here --- Please don't add those cut here lines. Patch is smart enough about picking a patch from an entire mail message, but it gets confused about just this line since it happens to start with a hyphen. :-( Nobody would really be going to cut it there anyway, so it's useless at all. Thanks for the patch! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jul 22 15:34:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA07377 for bugs-outgoing; Sat, 22 Jul 1995 15:34:55 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id AAA07363 ; Sun, 23 Jul 1995 00:34:54 +0200 Date: Sun, 23 Jul 1995 00:34:54 +0200 From: Joerg Wunsch Message-Id: <199507222234.AAA07363@freefall.cdrom.com> To: xaa@xaa.stack.urc.tue.nl, joerg, freebsd-bugs Subject: Changed information for PR bin/626 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: ruptime doesn't like uptimes > 1 year State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sun Jul 23 00:34:02 MET DST 1995 State-Changed-Why: Suggested fix partially applied. Fixed in version 1.3 of ruptime.c. From owner-freebsd-bugs Sat Jul 22 15:37:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA07552 for bugs-outgoing; Sat, 22 Jul 1995 15:37:29 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id PAA07542 for ; Sat, 22 Jul 1995 15:37:26 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA04375; Sun, 23 Jul 1995 00:37:04 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA07575; Sun, 23 Jul 1995 00:54:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA26805; Sun, 23 Jul 1995 00:30:21 +0200 From: J Wunsch Message-Id: <199507222230.AAA26805@uriah.heep.sax.de> Subject: Re: small change to boot.c To: graichen@omega.physik.fu-berlin.de (Thomas Graichen) Date: Sun, 23 Jul 1995 00:30:20 +0200 (MET DST) Cc: bugs@FreeBSD.org In-Reply-To: <9507211530.AA08034@omega.physik.fu-berlin.de> from "Thomas Graichen" at Jul 21, 95 05:30:24 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 388 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Thomas Graichen wrote: > > - printf("+0x%x+0x%x] ", sizeof(int), i); > + printf("+0x%x+0x%x]\n", sizeof(int), i); Your patch was garbled. DON'T submit patches obtained by cut&paste in an xterm, please!!! It botches the tabs. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jul 22 18:07:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA11549 for bugs-outgoing; Sat, 22 Jul 1995 18:07:56 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id SAA11543 for ; Sat, 22 Jul 1995 18:07:54 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id SAA01100; Sat, 22 Jul 1995 18:05:43 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: graichen@omega.physik.fu-berlin.de (Thomas Graichen), bugs@FreeBSD.org Subject: Re: small change to boot.c In-reply-to: Your message of "Sun, 23 Jul 1995 00:30:20 +0200." <199507222230.AAA26805@uriah.heep.sax.de> Date: Sat, 22 Jul 1995 18:05:43 -0700 Message-ID: <1098.806461543@time.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > Your patch was garbled. DON'T submit patches obtained by cut&paste > in an xterm, please!!! It botches the tabs. I agree, but just FYI the patch command has a -l flag which causes it to ignore whitespace differences. It really helps in cases like this, though it's still somewhat bogus since you lose the tab in the source code.. Still, it can save you a lot of trouble when the patch is *large* and you can always run the results through indent to recreate the lost tab info (and probably clean up the file considerably in the process :-). Jordan From owner-freebsd-bugs Sat Jul 22 18:26:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA12409 for bugs-outgoing; Sat, 22 Jul 1995 18:26:11 -0700 Received: (from ache@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA12395 ; Sat, 22 Jul 1995 18:26:11 -0700 Date: Sat, 22 Jul 1995 18:26:11 -0700 From: "Andrey A. Chernov" Message-Id: <199507230126.SAA12395@freefall.cdrom.com> To: fenner@parc.xerox.com, ache, freebsd-bugs Subject: Changed information for PR bin/612 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: traceroute doesn't print * if other ICMP traffic exists State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Sat Jul 22 18:25:41 PDT 1995 State-Changed-Why: Fix applied in traceroute.c v1.3 From owner-freebsd-bugs Sat Jul 22 23:53:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id XAA22460 for bugs-outgoing; Sat, 22 Jul 1995 23:53:01 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id XAA22454 for ; Sat, 22 Jul 1995 23:52:54 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA13068; Sun, 23 Jul 1995 08:52:33 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA09597; Sun, 23 Jul 1995 09:09:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA00266; Sun, 23 Jul 1995 08:29:52 +0200 From: J Wunsch Message-Id: <199507230629.IAA00266@uriah.heep.sax.de> Subject: Re: small change to boot.c To: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) Date: Sun, 23 Jul 1995 08:29:51 +0200 (MET DST) Cc: graichen@omega.physik.fu-berlin.de In-Reply-To: <1098.806461543@time.cdrom.com> from "Jordan K. Hubbard" at Jul 22, 95 06:05:43 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 876 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > > Your patch was garbled. DON'T submit patches obtained by cut&paste > > in an xterm, please!!! It botches the tabs. > > I agree, but just FYI the patch command has a -l flag which causes it > to ignore whitespace differences. I know, and i have used it. Anyway, it stopped my mass-patch from working, and finally caused the confused log messages plus some extra work -- so i thought i should remind people that cutting from an xterm is dangerous (cutting from Emacs is okay, it retains the tabs). This is no criticism to Thomas here, it's just his submission where i've stumbled across it again, but he hasn't been the first one (and Thomas, of course, we're thankful for getting the patch!) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)