From owner-freebsd-stable Sun Mar 17 02:17:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA04603 for stable-outgoing; Sun, 17 Mar 1996 02:17:31 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA04597 for ; Sun, 17 Mar 1996 02:17:27 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id LAA27655; Sun, 17 Mar 1996 11:00:31 +0100 (MET) Received: (from andreas@localhost) by knobel.gun.de (8.7.5/8.7.3) id IAA15929; Sun, 17 Mar 1996 08:35:41 +0100 (MET) From: Andreas Klemm Message-Id: <199603170735.IAA15929@knobel.gun.de> Subject: Re: Re(2): Commit messages To: rkw@dataplex.net (Richard Wackerbarth) Date: Sun, 17 Mar 1996 08:35:41 +0100 (MET) Cc: freebsd-stable@freebsd.org, peter@jhome.DIALix.COM In-Reply-To: from Richard Wackerbarth at "Mar 16, 96 04:40:32 pm" X-Mailer: ELM [version 2.4ME+ PL13 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Andreas Klemm wrote: > I think that you are missing the point. Even if I use sup or CTM to get the > sources, it is very useful to know what/why things were changed. The commit > messages are the best documentation readily available. However, if I am not > interested in -current, I hate to wade through all the changes that have > absolutely no value to me in order to find the few that do apply to the > -stable branch. You're right, I'm wrong. Some seconds later after hitting 's' I was aware of this, too. -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< "Ich bleibe bei der Aussage und trotze den Flames. :-)" Ulli Horlacher 02/96 From owner-freebsd-stable Sun Mar 17 06:56:58 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA18420 for stable-outgoing; Sun, 17 Mar 1996 06:56:58 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA18410 for ; Sun, 17 Mar 1996 06:56:54 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Sun, 17 Mar 96 15:56 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-stable@freebsd.org id ; Sun, 17 Mar 96 15:56 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA25186; Sun, 17 Mar 96 15:56:32 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9603171456.AA25186@wavehh.hanse.de> Subject: To: freebsd-stable@freebsd.org Date: Sun, 17 Mar 1996 15:56:31 +0100 (MET) Reply-To: cracauer@wavehh.hanse.de X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk who freebsd-stable who freebsd-scsi who freebsd-fs who freebsd-current who freebsd-security who freebsd-realtime lists From owner-freebsd-stable Sun Mar 17 13:35:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07676 for stable-outgoing; Sun, 17 Mar 1996 13:35:56 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07617 Sun, 17 Mar 1996 13:34:47 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id QAA00531; Sun, 17 Mar 1996 16:34:24 -0500 (EST) Date: Sun, 17 Mar 1996 16:34:23 -0500 (EST) From: "Marc G. Fournier" To: stable@freebsd.org cc: current@freebsd.org Subject: pmap_clear_reference panic in -stable... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Not sure if there is active development going on in -stable, or if its just stuff brought over from -current, so I'm sending this to both addresses. Using the March 15th -stable sources to build the following kernel, I arrived at the office to a system panic, as detailed in my PR submitted. I'm unable to get any savecore core dump using a -stable kernel, but -current has been giving me one, so is there a bug with -stable that is preventing this from working? All I'm able to give is DDB output, and the only thing in DDB that I know to "give" is the 'trace' output...is there something else I can do in DDB to give more information for PRs? Here's the PR... ----[ PR ]---- >Submitter-Id: current-users >Originator: Marc G. Fournier >Organization: >Confidential: no >Synopsis: PANIC: pagedaemon/_pmap_clear_reference+0xb2 >Severity: critical >Priority: high >Category: kern >Release: FreeBSD 2.1-STABLE i386 >Class: sw-bug >Environment: FreeBSD 2.1-STABLE #4: Sat Mar 16 17:16:06 EST 1996 scrappy@ki.net:/usr/src/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14704640 (14360K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 327MB (670506 512 byte sectors) (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 234MB (479350 512 byte sectors) (ncr0:3:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 515MB (1056708 512 byte sectors) vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface >Description: Am currently unable to gain a "savecore" core dump after ddb in -stable, so all I have to give is this DDB output. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf48e1000 fault code = supervisor read, page not present instruction pointer = 0x8:0xf019c666 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (pagedaemon) interrupts enabled = net tty bio Stopped at _pmap_clear_reference+0xb2: cmpl $0,0(%edx,%eax,4) db>tra _pmap_clear_reference(333000) at pmap_clear_reference+0xb2 _vm_pageout_scan() at vm_pageout_scan+0x38e _vm_pageout() at vm_pageout+0x1b8 _main() at main+0x46f begin at begin+0x6b >How-To-Repeat: >Fix: ---[ end PR ]--- Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-stable Mon Mar 18 05:28:53 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA21686 for stable-outgoing; Mon, 18 Mar 1996 05:28:53 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA21681 for ; Mon, 18 Mar 1996 05:28:47 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Mon, 18 Mar 96 14:28 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-stable@freebsd.org id ; Mon, 18 Mar 96 14:28 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA22477; Mon, 18 Mar 96 14:28:24 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9603181328.AA22477@wavehh.hanse.de> Subject: Sorry for the junk mail (no subject) To: freebsd-stable@freebsd.org Date: Mon, 18 Mar 1996 14:28:23 +0100 (MET) Reply-To: cracauer@wavehh.hanse.de X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In fact, it was not my intention to get the subscription lists by collecting the humorous replies :-) I'll ask majordomo instead. Sorry Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer - Fax +49 40 522 85 36 BSD User Group Hamburg, Germany http://www.bik-gmbh.de/~cracauer From owner-freebsd-stable Mon Mar 18 09:13:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA06930 for stable-outgoing; Mon, 18 Mar 1996 09:13:16 -0800 (PST) Received: from wsantee.oz.net (wsantee.oz.net [204.118.240.207]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06925 for ; Mon, 18 Mar 1996 09:13:14 -0800 (PST) Received: (from wsantee@localhost) by wsantee.oz.net (8.6.12/8.6.12) id JAA02436 for stable@freebsd.org; Mon, 18 Mar 1996 09:11:52 -0800 From: Wes Santee Message-Id: <199603181711.JAA02436@wsantee.oz.net> Subject: On commit messages for Stable... To: stable@freebsd.org Date: Mon, 18 Mar 1996 09:11:51 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 'Lo all. After writing up the original request for a CVS commit list for the -stable branch only, and seeing the ensuing discussion on the pros and cons of it all, I just wanted to add that if a -stable only mailing list isn't going to happen, is there a line in the commit messages or some other way of telling that a piece is being checked into the -stable branch? I notice many commit messages I get don't say anything about what branch the files are being checked into, while some I've received recently say the branch is RELENG_2_1_0. If there is a surefire way to see if something is being checked into -stable, I can write a procmail recipe to filter on the stuff I want to see which may be a compromise that we all can agree on. Cheers, -- ( -Wes Santee | ) ( (backup) | No one told you when to run... ) ( http://www.oz.net/~wsantee \------------------------------- ) ( For PGP Key, email w/Subject: "Send PGP Key" Powered by FreeBSD ) From owner-freebsd-stable Mon Mar 18 12:15:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04958 for stable-outgoing; Mon, 18 Mar 1996 12:15:34 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA04943 Mon, 18 Mar 1996 12:15:31 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199603182015.MAA04943@freefall.freebsd.org> Subject: Re: On commit messages for Stable... To: wsantee@wsantee.oz.net (Wes Santee) Date: Mon, 18 Mar 1996 12:15:30 -0800 (PST) Cc: stable@freebsd.org In-Reply-To: <199603181711.JAA02436@wsantee.oz.net> from "Wes Santee" at Mar 18, 96 09:11:51 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wes Santee wrote: > > After writing up the original request for a CVS commit list for the > -stable branch only, and seeing the ensuing discussion on the pros and > cons of it all, I just wanted to add that if a -stable only mailing > list isn't going to happen, is there a line in the commit messages or > some other way of telling that a piece is being checked into the > -stable branch? yes. RELENG_2_1_0 is the key that you are looking for. messages that do not have any indicator are commited to the HEAD (ie -current). > > If there is a surefire way to see if something is being checked into > -stable, I can write a procmail recipe to filter on the stuff I want > to see which may be a compromise that we all can agree on. no one would object to you using procmail to filter on this tag. in my own defense, i must say that mail has been "busy" lately what with the internet connectivity problems in california. From owner-freebsd-stable Mon Mar 18 13:06:27 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA15063 for stable-outgoing; Mon, 18 Mar 1996 13:06:27 -0800 (PST) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA15051 for ; Mon, 18 Mar 1996 13:06:21 -0800 (PST) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Mon, 18 Mar 1996 15:06:06 -0600 Message-ID: Date: 18 Mar 1996 15:05:54 -0600 From: "Richard Wackerbarth" Subject: Re: On commit messages for Stable... To: "stable@FreeBSD.org" , "Wes Santee" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Wes Santee wrote: > After writing up the original request for a CVS commit list for the > -stable branch only, and seeing the ensuing discussion on the pros and > cons of it all, I just wanted to add that if a -stable only mailing > list isn't going to happen, is there a line in the commit messages or > some other way of telling that a piece is being checked into the > -stable branch? > > I notice many commit messages I get don't say anything about what > branch the files are being checked into, while some I've received > recently say the branch is RELENG_2_1_0. > > If there is a surefire way to see if something is being checked into > -stable, I can write a procmail recipe to filter on the stuff I want > to see which may be a compromise that we all can agree on. But it is little effort to install that same procmail filter to cause the passed messages to be posted to a separate mailing list. This would have the advantage of reducing the mail traffic at the source rather than the destination. From owner-freebsd-stable Mon Mar 18 15:19:05 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA11729 for stable-outgoing; Mon, 18 Mar 1996 15:19:05 -0800 (PST) Received: from warnick (3rivers3.3rivers.net [206.107.232.32]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA11706 Mon, 18 Mar 1996 15:18:56 -0800 (PST) Received: (from ron@localhost) by warnick (8.6.12/8.6.12) id QAA25820; Mon, 18 Mar 1996 16:17:30 -0700 From: Ron Warnick Message-Id: <199603182317.QAA25820@warnick> Subject: make world breaks at usr.bin/dig To: freebsd-stable@freebsd.org Date: Mon, 18 Mar 1996 16:16:06 -0700 (MST) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get the following in a "make world" from -stable, supped on 3/16: cc -O -I/usr/src/usr.bin/dig/../../usr.sbin/nslookup -o dig dig.o debug.o list.o send.o subr.o debug.o: Undefined symbol `_iso_ntoa' referenced from text segment list.o: Undefined symbol `_iso_ntoa' referenced from text segment *** Error code 1 Any help to make this work would be most appreciated. Ron ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ron Warnick ron@3rivers.net linux -> FreeBSD -> Plan9 From owner-freebsd-stable Mon Mar 18 17:17:02 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA18891 for stable-outgoing; Mon, 18 Mar 1996 17:17:02 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA18881 for ; Mon, 18 Mar 1996 17:16:46 -0800 (PST) Received: by haven.uniserve.com id <30777-5728>; Mon, 18 Mar 1996 17:18:26 -0800 Date: Mon, 18 Mar 1996 17:18:25 -0800 (PST) From: Tom Samplonius To: "Marc G. Fournier" cc: stable@freebsd.org Subject: Re: pmap_clear_reference panic in -stable... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Mar 1996, Marc G. Fournier wrote: > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xf48e1000 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf019c666 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 2 (pagedaemon) > interrupts enabled = net tty bio I've seen several crashes in -stable very similar to this. I don't have DDB in the kernel so I can't confirm whether the back-trace is similar. Tom From owner-freebsd-stable Tue Mar 19 15:42:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA11368 for stable-outgoing; Tue, 19 Mar 1996 15:42:34 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA11345 Tue, 19 Mar 1996 15:41:59 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id PAA03872; Tue, 19 Mar 1996 15:31:12 -0500 (EST) Date: Tue, 19 Mar 1996 15:31:08 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org cc: stable@freebsd.org Subject: Sendmail 8.6.12 -> 8.7.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just wondering if there is any reason why Sendmail 8.7.5 hasn't been migrated/commited to the -stable source tree? If there is none, can someone do it? I'm currently running 8.7.4 on my -stable machine, and doing a 'make world' with the current sources is kinda difficult if I don't want to wipe out my current sendmail :( Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-stable Tue Mar 19 16:14:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA13596 for stable-outgoing; Tue, 19 Mar 1996 16:14:28 -0800 (PST) Received: from mail.jrihealth.com (mail.jrihealth.com [204.249.32.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA13587 for ; Tue, 19 Mar 1996 16:14:24 -0800 (PST) Received: from carebase3.jri.org (danp@carebase3.jri.org [204.249.32.9]) by mail.jrihealth.com (8.3/8.6.6.Beta9) with SMTP id TAA02139; Tue, 19 Mar 1996 19:18:51 -0500 Date: Tue, 19 Mar 1996 19:19:04 -0500 (EST) From: Dan Polivy To: freebsd-stable@freebsd.org Subject: -stable and NCR problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey, I just got -stable working, and have had a few odd problems with my ncr0 PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has changed in the ncr driver from release->stable? I can try and give you more info if you need it...lemme go look in the logs.....Well, just seeing if anyone else has had this problem? Thanks! Dan +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | JRI HIS MIS Systems Administrator/Tech Support | |////////////////////////////////////////////////////////////////| | danp@busstop.org dpolivy@jri.org danp@library.pride.net | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out JRI's Homepage at http://www.jri.org | |////////////////////////////////////////////////////////////////| | For More Info about JRI Health, call 617.457.8150, | | EMail health@jri.org or check out http://www.jri.org/jrihealth | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out my NEW [Moving] WWW page (still under construction) | | currently located at: http://server1.pride.net/~danp | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ From owner-freebsd-stable Tue Mar 19 17:42:17 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19790 for stable-outgoing; Tue, 19 Mar 1996 17:42:17 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19785 Tue, 19 Mar 1996 17:42:09 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id RAA21881; Tue, 19 Mar 1996 17:40:31 -0800 From: "Rodney W. Grimes" Message-Id: <199603200140.RAA21881@GndRsh.aac.dev.com> Subject: Re: Sendmail 8.6.12 -> 8.7.5 To: scrappy@ki.net (Marc G. Fournier) Date: Tue, 19 Mar 1996 17:40:30 -0800 (PST) Cc: current@freebsd.org, stable@freebsd.org In-Reply-To: from "Marc G. Fournier" at Mar 19, 96 03:31:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Hi... > > Just wondering if there is any reason why Sendmail 8.7.5 hasn't > been migrated/commited to the -stable source tree? If there is none, > can someone do it? I'm currently running 8.7.4 on my -stable machine, > and doing a 'make world' with the current sources is kinda difficult if > I don't want to wipe out my current sendmail :( > > Thanks... This is a way to work around your current situation: cd /usr/src/usr.bin cp Makefile makefile vi makefile # nuke sendmail from the SUBDIR list Now your upgraded sendmail will not get touched by a make world, nor will your modified makefile get spammed by a sup or cvs update. Just don't forget to rm the makefile copy when sendmail does get upgraded. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-stable Tue Mar 19 22:15:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06403 for stable-outgoing; Tue, 19 Mar 1996 22:15:43 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06389 for ; Tue, 19 Mar 1996 22:15:13 -0800 (PST) Received: by haven.uniserve.com id <30756-27697>; Tue, 19 Mar 1996 22:17:36 -0800 Date: Tue, 19 Mar 1996 22:17:29 -0800 (PST) From: Tom Samplonius To: "Marc G. Fournier" cc: stable@FreeBSD.ORG Subject: Re: Sendmail 8.6.12 -> 8.7.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, Marc G. Fournier wrote: > Hi... > > Just wondering if there is any reason why Sendmail 8.7.5 hasn't > been migrated/commited to the -stable source tree? If there is none, 8.7.x is still a moving target. The time between .3, .4, and .5 releases has been quite short. I would recommend the 8.6.13 release for -stable, and wait and see how long it takes before 8.7.6 is available. Tom From owner-freebsd-stable Wed Mar 20 07:06:15 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07172 for stable-outgoing; Wed, 20 Mar 1996 07:06:15 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07167 Wed, 20 Mar 1996 07:06:10 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id KAA05394; Wed, 20 Mar 1996 10:04:58 -0500 Date: Wed, 20 Mar 1996 10:04:58 -0500 (EST) From: Charles Owens To: Dan Polivy cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: -stable and NCR problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, Dan Polivy wrote: > Hey, > > I just got -stable working, and have had a few odd problems with my ncr0 > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has > changed in the ncr driver from release->stable? I can try and give you > more info if you need it...lemme go look in the logs.....Well, just > seeing if anyone else has had this problem? Thanks! What are you seeing? I'm seeing this sorta stuff: Mar 17 12:59:39 dingo /kernel: ncr0:0: ERROR (0:140) (40-67-4) (8/13) @ (abc:008c0064). Mar 17 12:59:42 dingo /kernel: script cmd = c0000001 Mar 17 12:59:42 dingo /kernel: reg: da 10 c0 13 47 08 00 0f a4 40 80 67 00 00 07 00. Mar 17 12:59:42 dingo /kernel: ncr0: have to clear fifos. Mar 17 12:59:42 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:42 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:3 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: ncr0:0: ERROR (80:100) (8-2a-0) (8/13) @ (544:900b0000). Mar 17 12:59:43 dingo /kernel: script cmd = 910a0000 Mar 17 12:59:43 dingo /kernel: reg: da 10 80 13 47 08 00 0f 01 08 00 2a 80 00 02 00. Mar 17 12:59:43 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6800. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:1 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): Power on, reset, or bus device reset occurred Usually, after a brief delay, it picks up where it left off with no problem, but I have had a few reboots that could be related. Is this similar to what you're seeing? Should I suspect the driver, my SCSI cable/termination or something else? thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Wed Mar 20 10:46:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA24046 for stable-outgoing; Wed, 20 Mar 1996 10:46:43 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA23617 for ; Wed, 20 Mar 1996 10:38:42 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id NAA00269; Wed, 20 Mar 1996 13:36:57 -0500 (EST) Date: Wed, 20 Mar 1996 13:36:57 -0500 (EST) From: "Marc G. Fournier" To: Dan Polivy cc: freebsd-stable@freebsd.org Subject: Re: -stable and NCR problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, Dan Polivy wrote: > Hey, > > I just got -stable working, and have had a few odd problems with my ncr0 > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has > changed in the ncr driver from release->stable? I can try and give you > more info if you need it...lemme go look in the logs.....Well, just > seeing if anyone else has had this problem? Thanks! > What sort of problems? For me, the only thing I'm noticing is occasional machine hangs, which look surprising like SCSI hangs, but other then that, no problems. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-stable Wed Mar 20 11:51:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA27504 for stable-outgoing; Wed, 20 Mar 1996 11:51:16 -0800 (PST) Received: from ki.net (ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA27366 for ; Wed, 20 Mar 1996 11:49:05 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id OAA04348; Wed, 20 Mar 1996 14:48:00 -0500 (EST) Date: Wed, 20 Mar 1996 14:47:58 -0500 (EST) From: "Marc G. Fournier" To: stable@freebsd.org Subject: memory problems under -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I'm semi-regularly getting the following with -stable: ===> socksys cc -O2 -m486 -DLKM -I. -DCOMPAT_IBCS2 -DKERNEL -I/usr/src/lkm/socksys/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/socksys/socksys.c cc -O2 -m486 -DLKM -I. -DCOMPAT_IBCS2 -DKERNEL -I/usr/src/lkm/socksys/../../sys -W -Wcomment -Wredundant-decls -c /usr/src/lkm/socksys/../../sys/i386/ibcs2/ibcs2_socksys.c ld -r -o socksys_mod.o socksys.o ibcs2_socksys.o ===> syscons Memory fault - core dumped *** Error code 139 Stop. ki# make Segmentation fault (core dumped) ki# pstat -s Device 1K-blocks Used Avail Capacity Type /dev/sd0b 102400 10052 92284 10% Interleaved /dev/sd1b 32768 9668 23036 30% Interleaved /dev/sd2b 32768 9744 22960 30% Interleaved /dev/sd3b 32768 9976 22728 31% Interleaved Total 200448 39440 161008 20% If I wait a couple of minutes, and then run make again, all is well and I can continue rebuilding the system... ...anyone else experiencing this with -stable? The system looks like this, according to dmesg: FreeBSD 2.1-STABLE #4: Sat Mar 16 17:16:06 EST 1996 scrappy@ki.net:/usr/src/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14704640 (14360K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 327MB (670506 512 byte sectors) (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 234MB (479350 512 byte sectors) (ncr0:3:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 515MB (1056708 512 byte sectors) vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface pid 3983 (make), uid 0: exited on signal 11 pid 3985 (make), uid 0: exited on signal 11 Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc From owner-freebsd-stable Wed Mar 20 13:19:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04589 for stable-outgoing; Wed, 20 Mar 1996 13:19:31 -0800 (PST) Received: from mail.jrihealth.com (mail.jrihealth.com [204.249.32.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA04570 Wed, 20 Mar 1996 13:19:21 -0800 (PST) Received: from carebase3.jri.org (danp@carebase3.jri.org [204.249.32.9]) by mail.jrihealth.com (8.3/8.6.6.Beta9) with SMTP id QAA01578; Wed, 20 Mar 1996 16:24:28 -0500 Date: Wed, 20 Mar 1996 16:24:42 -0500 (EST) From: Dan Polivy To: Charles Owens cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: -stable and NCR problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Charles, On Wed, 20 Mar 1996, Charles Owens wrote: > What are you seeing? I'm seeing this sorta stuff: I don't have a log handy..sorry...when I get it, though I will post it.. > Mar 17 12:59:42 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. > Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. I get a few of these....I/O errors too trying to access file.. BUT, this only occurs every once in a while. It ran flawlessly for 2.1-RELEASE, as far as I know....So maybe we can go back to the old driver? Or were there problems with that? > Usually, after a brief delay, it picks up where it left off with no > problem, but I have had a few reboots that could be related. Hmm..I have to reboot to fix it... > Should I suspect the driver, my SCSI cable/termination or something else? I think it may be the driver...But maybe not. I get a bunch of the COMMAND FAILED notices...but keep in mine I have been running -STABLE for less than two days...so I haven't got much to go on...but I couldn't even boot the 2.2-SNAP disk - the ncr driver gave meproblems there, too... Dan +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | JRI HIS MIS Systems Administrator/Tech Support | |////////////////////////////////////////////////////////////////| | danp@busstop.org dpolivy@jri.org danp@library.pride.net | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out JRI's Homepage at http://www.jri.org | |////////////////////////////////////////////////////////////////| | For More Info about JRI Health, call 617.457.8150, | | EMail health@jri.org or check out http://www.jri.org/jrihealth | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out my NEW [Moving] WWW page (still under construction) | | currently located at: http://server1.pride.net/~danp | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ From owner-freebsd-stable Thu Mar 21 09:55:38 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA11810 for stable-outgoing; Thu, 21 Mar 1996 09:55:38 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA11794 Thu, 21 Mar 1996 09:55:33 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id MAA08442; Thu, 21 Mar 1996 12:54:53 -0500 Date: Thu, 21 Mar 1996 12:54:53 -0500 (EST) From: Charles Owens To: questions list FreeBSD cc: stable@freebsd.org Subject: Keeping multiple servers at -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have a number of servers that I'd like to keep relatively current with -stable. I've got the full sources on a support machine and have sup'ed -stable down and successfully did a "make world". What is the best way for me to install the rebuilt stuff on the other servers? The "installmost" target in /usr/src/Makefile looks promising, but it doesn't look like it includes stuff like libraries and man pages. (I was thinking of mounting /usr/src on each server and then doing a make installmost). Any thoughts? --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Thu Mar 21 10:55:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA18571 for stable-outgoing; Thu, 21 Mar 1996 10:55:31 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA18566 Thu, 21 Mar 1996 10:55:28 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA14008; Thu, 21 Mar 1996 11:58:19 -0700 Date: Thu, 21 Mar 1996 11:58:19 -0700 From: Nate Williams Message-Id: <199603211858.LAA14008@rocky.sri.MT.net> To: stable@FreeBSD.org, current@FreeBSD.org CC: hosokawa@mt.cs.keio.ac.jp Subject: Laptop users take notice Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'd like to start a 'freebsd-mobile' mailing lists for users of laptops, notebooks, and other mobile users of FreeBSD. I'm starting on the home stretch for getting APM support working, and the next stage will be finishing up the PC-CARD support, but I'm going to need some more testers soon. What we have now is a pretty good framework based on the work Poul-Henning and the BSD Nomads group have done, but it needs to be filled in. Most of the code to fill it in exists, but needs to be thought out, integrated, and tested. My status on the project is that yesterday I got APM suspend/resume working on my box, so I need to do a bit more cleanup and testing of the APM driver, and then I need some folks to test and review these fixes before I commit them. My proposed schedule for committing code to the tree: (Notice no dates. :) 1) Finish and clean up the APM support 2) Bring in some of the recent PC-CARD patches from the Nomads 3) Bring in and cleanup the user-land patches from the Nomads 4) Tweak the /etc config files as necessary 5) Bring in the driver modifications for PCCARD support I'm more than willing to change my schedule, or let anyone else do the work, but I have an advantage/disadvantage in that I *have* to get this working for a project for my employer. The advantage is that I have time, the disadvantage is that I have a deadline coming up which means I won't be able to use as much on-the-clock time in a few weeks. Also, if necessary I can make patches against -current and -stable (preferrable -stable since that's what I'm running) of all of the above in order to get people jump-started. What I'm looking for: 1) Laptop or notebook owners who can test patches 2) Folks interested in this area to give feedback What I'm not looking for: 1) People who want to throw out the existing interface for something new 2) People who are willing to make suggestions without doing a bit of work to help out. Most of us are stretched pretty thin as it is, but I think getting PC-CARD support in FreeBSD would be a great feather in our cap, and I believe we have the existing framework is adequate for now. I'm willing to co-ordinate the work, and I'm hoping that the patches I generate will be tested fairly well (I have access to 2 different laptops most of the time), but no guarantees. Send me email, and if there is enough interest we can get the postmaster to setup a mailing list on freefall. Thanks! Nate From owner-freebsd-stable Thu Mar 21 13:19:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA28594 for stable-outgoing; Thu, 21 Mar 1996 13:19:28 -0800 (PST) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA28556 for ; Thu, 21 Mar 1996 13:19:17 -0800 (PST) Received: by haven.uniserve.com id <34797-6466>; Thu, 21 Mar 1996 13:21:30 -0800 Date: Thu, 21 Mar 1996 13:21:27 -0800 (PST) From: Tom Samplonius To: Charles Owens cc: stable@freebsd.org Subject: Re: Keeping multiple servers at -stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Mar 1996, Charles Owens wrote: > Hi, > I have a number of servers that I'd like to keep relatively current with > -stable. I've got the full sources on a support machine and have sup'ed > -stable down and successfully did a "make world". What is the best way > for me to install the rebuilt stuff on the other servers? > > The "installmost" target in /usr/src/Makefile looks promising, but it > doesn't look like it includes stuff like libraries and man pages. (I was > thinking of mounting /usr/src on each server and then doing a make > installmost). Mount /usr/src AND /usr/obj on each machine and do a "make SHARED=copies install" Unfortunately, a "make install" requires write access. It would be nice if it didn't so I could do an anonymous NFS export. Tom From owner-freebsd-stable Thu Mar 21 19:19:35 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA08133 for stable-outgoing; Thu, 21 Mar 1996 19:19:35 -0800 (PST) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA08127 for ; Thu, 21 Mar 1996 19:19:30 -0800 (PST) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id TAA28944; Thu, 21 Mar 1996 19:19:07 -0800 Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.13/8.6.9) id TAA05015; Thu, 21 Mar 1996 19:19:06 -0800 Date: Thu, 21 Mar 1996 19:19:05 -0800 (PST) From: Chris Timmons To: Dan Polivy cc: Charles Owens , freebsd-stable@FreeBSD.ORG Subject: Re: -stable and NCR problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had similar problems in stable of a month ago, but it turned out that my seagate hawk was slowly dying. The core dump problem seemed very much like text was becoming corrupted during swap. I went back to 2.1-R and hammered on the drive with bonnie and it finally died altogether. Is there an easy way for you to test out your hardware under 2.1-R to make sure it still works under that release? -Chris From owner-freebsd-stable Fri Mar 22 11:26:54 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA23231 for stable-outgoing; Fri, 22 Mar 1996 11:26:54 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA23225 for ; Fri, 22 Mar 1996 11:26:52 -0800 (PST) Received: from lily.csl.sri.com (lily.csl.sri.com [192.12.33.201]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id LAA20841 for ; Fri, 22 Mar 1996 11:26:21 -0800 (PST) Received: (from gilham@localhost) by lily.csl.sri.com (8.7.3/8.7.3) id LAA12708; Fri, 22 Mar 1996 11:26:20 -0800 (PST) Date: Fri, 22 Mar 1996 11:26:20 -0800 (PST) Message-Id: <199603221926.LAA12708@lily.csl.sri.com> From: Fred Gilham To: stable@freebsd.org Subject: Bootstrap problems Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't know if these problems have already been reported, but... I've been trying to get all my machines up to a common version of -stable, so I've been installing the `release' version off the CD-ROM and then supping the -stable over it. I found that this causes problems because there's a new option to install, `-C', that isn't in the release version, and this causes the installs to fail, since the old install is used until the new one is installed. I got around this by making and manually installing the new version of install. Another problem I had is that in /usr/src/lib/libdisk, the Makefile had the following: MAN3= libdisk.3 MLINKS+= libdisk.3 \ libdisk.3 Open_Disk.3 \ libdisk.3 Clone_Disk.3 \ libdisk.3 Free_Disk.3 \ libdisk.3 Debug_Disk.3 \ libdisk.3 Set_Bios_Geom.3 \ libdisk.3 Delete_Chunk.3 \ libdisk.3 Collapse_Disk.3 \ libdisk.3 Collapse_Chunk.3 \ libdisk.3 Create_Chunk.3 \ libdisk.3 All_FreeBSD.3 \ . . . etc. This caused installing the man pages to fail, and I could only get things to work by changing that to the following: MAN3= libdisk.3 MLINKS+= \ libdisk.3 Open_Disk.3 \ libdisk.3 Clone_Disk.3 \ libdisk.3 Free_Disk.3 \ libdisk.3 Debug_Disk.3 \ libdisk.3 Set_Bios_Geom.3 \ libdisk.3 Delete_Chunk.3 \ libdisk.3 Collapse_Disk.3 \ libdisk.3 Collapse_Chunk.3 \ libdisk.3 Create_Chunk.3 \ libdisk.3 All_FreeBSD.3 \ etc. -Fred Gilham gilham@csl.sri.com From owner-freebsd-stable Fri Mar 22 12:05:02 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA25896 for stable-outgoing; Fri, 22 Mar 1996 12:05:02 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA25876 for ; Fri, 22 Mar 1996 12:04:59 -0800 (PST) Received: by Sisyphos id AA01946 (5.67b/IDA-1.5 for freebsd-stable@freebsd.org); Fri, 22 Mar 1996 21:01:12 +0100 Message-Id: <199603222001.AA01946@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 22 Mar 1996 21:01:11 +0100 In-Reply-To: "Marc G. Fournier" "Re: -stable and NCR problems?" (Mar 20, 13:36) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Marc G. Fournier" Subject: Re: -stable and NCR problems? Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 20, 13:36, "Marc G. Fournier" wrote: } Subject: Re: -stable and NCR problems? } On Tue, 19 Mar 1996, Dan Polivy wrote: } } > Hey, } > } > I just got -stable working, and have had a few odd problems with my ncr0 } > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has } > changed in the ncr driver from release->stable? I can try and give you } > more info if you need it...lemme go look in the logs.....Well, just } > seeing if anyone else has had this problem? Thanks! } > } What sort of problems? } } For me, the only thing I'm noticing is occasional machine hangs, } which look surprising like SCSI hangs, but other then that, no problems. Hmm, does this mean, that the SCSI LED stays on, but there is no further disk activity anymore ? This could be caused by problems with tags or with the SCSI bus. Could you try running without tags for some time ? And you may want to use async transfers only, just to test whether it makes a difference (and if it does, I'd suspect a cable/termination problem). Since I'm going on a vacation for two weeks now, I can't look into this, now. But I'm planning to improve the error recovery code thereafter ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-stable Fri Mar 22 12:07:44 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA26048 for stable-outgoing; Fri, 22 Mar 1996 12:07:44 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA26043 for ; Fri, 22 Mar 1996 12:07:39 -0800 (PST) Received: by Sisyphos id AA02033 (5.67b/IDA-1.5 for freebsd-stable@freebsd.org); Fri, 22 Mar 1996 21:06:38 +0100 Message-Id: <199603222006.AA02033@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 22 Mar 1996 21:06:38 +0100 In-Reply-To: Dan Polivy "-stable and NCR problems?" (Mar 19, 19:19) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Dan Polivy Subject: Re: -stable and NCR problems? Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 19, 19:19, Dan Polivy wrote: } Subject: -stable and NCR problems? } Hey, } } I just got -stable working, and have had a few odd problems with my ncr0 } PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has } changed in the ncr driver from release->stable? I can try and give you } more info if you need it...lemme go look in the logs.....Well, just } seeing if anyone else has had this problem? Thanks! Well, there haven't been any significant changes to the NCR driver between 2.1R and -stable. The most visible one is moving the WIDE negotiation before the SYNC negotiation, as required by the SCSI specs. This is a NOP, unless you are using WIDE controller and drives. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-stable Fri Mar 22 12:49:37 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28703 for stable-outgoing; Fri, 22 Mar 1996 12:49:37 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28698 for ; Fri, 22 Mar 1996 12:49:34 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA19918; Fri, 22 Mar 1996 13:49:11 -0700 Date: Fri, 22 Mar 1996 13:49:11 -0700 From: Nate Williams Message-Id: <199603222049.NAA19918@rocky.sri.MT.net> To: Fred Gilham Cc: stable@freebsd.org Subject: Re: Bootstrap problems In-Reply-To: <199603221926.LAA12708@lily.csl.sri.com> References: <199603221926.LAA12708@lily.csl.sri.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Another problem I had is that in /usr/src/lib/libdisk, the Makefile > had the following: I just fixed that earlier this morning. Nate From owner-freebsd-stable Fri Mar 22 17:58:54 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19973 for stable-outgoing; Fri, 22 Mar 1996 17:58:54 -0800 (PST) Received: from piglet.cc.utexas.edu (djw@piglet.cc.utexas.edu [128.83.108.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA19964 for ; Fri, 22 Mar 1996 17:58:53 -0800 (PST) Received: (from djw@localhost) by piglet.cc.utexas.edu (8.6.11/8.6.11/cc-wf-solaris.mc-1.2) id TAA05061; Fri, 22 Mar 1996 19:58:50 -0600 Date: Fri, 22 Mar 1996 19:58:49 -0600 (CST) From: Dan Walters X-Sender: djw@piglet.cc.utexas.edu To: freebsd-stable@freebsd.org Subject: console freezes/vt100 compatibility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just started playing extensively with FreeBSD lately, just installed the latest -stable, etc., and have 2 questions: 1) I like to switch consoles pretty fast on occasion - should probably just use X, but sometimes I prefer the text mode. Anyway, once in a while it will just stop accepting keyboard input, including ctrl-alt-del. The system will keep compiling, ftping, or whatever, but I can't do anything or shut it down. Has anyone else experienced this or fixed it? I have a P133/2940/16MB system, and a friend of mine with an old 486/66 IDE system has had the same problem, so I'm assuming it's just not me. (Happened with both the generic kernel and one tailored for the system) 2) I play around on a lot of machines, and the syscons driver doesn't seem to fully support vt100, which is about all I need. I tried the pcvt220 deal, but the cursor seemed extremely sluggish and the keymaps didn't seem compatible (couldn't switch consoles?) If anybody has any pointers on this sort of thing I'd like to hear em. :) Thanks! --------------------------------------------------------------------------- Dan Walters djw@mail.utexas.edu --------------------------------------------------------------------------- From owner-freebsd-stable Fri Mar 22 18:59:51 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23379 for stable-outgoing; Fri, 22 Mar 1996 18:59:51 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA23374 for ; Fri, 22 Mar 1996 18:59:48 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA21417; Sat, 23 Mar 1996 13:46:01 +1030 From: Michael Smith Message-Id: <199603230316.NAA21417@genesis.atrad.adelaide.edu.au> Subject: Re: console freezes/vt100 compatibility To: djw@ccwf.cc.utexas.edu (Dan Walters) Date: Sat, 23 Mar 1996 13:46:00 +1030 (CST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from "Dan Walters" at Mar 22, 96 07:58:49 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dan Walters stands accused of saying: > > 1) I like to switch consoles pretty fast on occasion - should probably > just use X, but sometimes I prefer the text mode. Anyway, once in > a while it will just stop accepting keyboard input, including > ctrl-alt-del. The system will keep compiling, ftping, or whatever, > but I can't do anything or shut it down. Has anyone else experienced > this or fixed it? I have a P133/2940/16MB system, and a friend of mine It's a problem with the protocol used to talk to the keyboard, and isn't terribly easy to work around. Basically what happens is that the keyboard controller and the keyboard get out of sync; you can try unplugging and replugging your keyboard, which may clear the problem if it's your keyboard that's confused, and if your keyboard doesn't require a reset from the PC before working (most modern keybpards fit this category). A proper workaround would involve decoupling the keyboard communications stuff from the console driver, and raises nasty issues to do with keeping the keyboard state in sync with the selected VTY. > Dan Walters -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[