From owner-freebsd-bugs Sun Nov 26 07:01:20 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12011 for bugs-outgoing; Sun, 26 Nov 1995 07:01:20 -0800 Received: from venus.star.net (root@venus.star.net [199.232.114.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA12002 for ; Sun, 26 Nov 1995 07:01:15 -0800 Received: from jsabean.venus.star.net (beverly20p.star.net [199.232.114.239]) by venus.star.net (8.6.11/8.6.9) with SMTP id LAA09894 for ; Sun, 26 Nov 1995 11:01:41 -0500 Message-ID: <30B8AB55.7810@star.net> Date: Sun, 26 Nov 1995 10:00:53 -0800 From: James Sabean X-Mailer: Mozilla 2.0b1 (Windows; I; 16bit) MIME-Version: 1.0 To: bugs@freebsd.org Subject: deleting route to interface tun0 X-URL: http://www.freebsd.org/support.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk After booting, I eventually get a message like the following: deleting route to interface tun0 (timed out) This happens even if I have an active PPP session. Any suggestions? Is there a way to set the timeout? Is this a bug? lp0 and tun0 are the only interfaces that I have configured. Jim From owner-freebsd-bugs Sun Nov 26 07:20:40 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12899 for bugs-outgoing; Sun, 26 Nov 1995 07:20:40 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA12893 for ; Sun, 26 Nov 1995 07:20:33 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id KAA16847; Sun, 26 Nov 1995 10:08:10 -0500 Date: Sun, 26 Nov 1995 10:08:08 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: deleting route to interface tun0 To: James Sabean cc: bugs@freebsd.org In-Reply-To: <30B8AB55.7810@star.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk On Sun, 26 Nov 1995, James Sabean wrote: > After booting, I eventually get a message like the following: > > deleting route to interface tun0 (timed out) > > This happens even if I have an active PPP session. try adding the following lines to /etc/ppp/ppp.conf: set timeout 0 disable lqr deny lqr > > Any suggestions? Is there a way to set the timeout? Is this a > bug? lp0 and tun0 are the only interfaces that I have > configured. > > Jim > Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-bugs Sun Nov 26 09:23:57 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA20499 for bugs-outgoing; Sun, 26 Nov 1995 09:23:57 -0800 Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA20489 for ; Sun, 26 Nov 1995 09:23:15 -0800 Received: by agora.rdrop.com (Smail3.1.28.1 #8) id m0tJknB-0002T9C; Sun, 26 Nov 95 09:22 PST Message-Id: From: batie@agora.rdrop.com (Alan Batie) Subject: Re: Quotas? To: d_burr@ix.netcom.com (Donald Burr) Date: Sun, 26 Nov 1995 09:22:45 -0800 (PST) Cc: freebsd-bugs@freebsd.org In-Reply-To: from "Donald Burr" at Nov 25, 95 06:56:24 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 450 Sender: owner-bugs@freebsd.org Precedence: bulk > if [ "X${check_quotas}" = X"YES" ]; then Arg. I hate it when it's something obvious. I had the userquotas in fstab, but forgot about quotaon. Thanks, that fixed it... -- Alan Batie ______ batie@agora.rdrop.com \ / Freedom for me to be and do +1 503 452-0960 \ / only what *you* approve of 45 28 59 N / 122 43 20 W / 440' MSL \/ is no freedom at all. From owner-freebsd-bugs Sun Nov 26 10:49:36 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA24725 for bugs-outgoing; Sun, 26 Nov 1995 10:49:36 -0800 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA24719 for ; Sun, 26 Nov 1995 10:49:18 -0800 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from prospero (130.133.3.126) with smtp id ; Sun, 26 Nov 95 19:47 MET Received: (from graichen@localhost) by prospero (8.6.12/8.6.12) id SAA00910; Sun, 26 Nov 1995 18:50:55 +0100 From: Thomas Graichen Message-Id: <199511261750.SAA00910@prospero> Subject: Re: Quotas? To: batie@agora.rdrop.com (Alan Batie) Date: Sun, 26 Nov 1995 18:50:53 +0100 (MET) Cc: bugs@freebsd.org In-Reply-To: from "Alan Batie" at Nov 25, 95 05:24:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1337 Sender: owner-bugs@freebsd.org Precedence: bulk > > I'm building a new 2.1.0 system, and it appears that quotas are not > functional. I do have "options QUOTA" in the config file, but I have > imposed quotas on a filesystem, and can go in and create files exceeding > the quota. "quota -v" shows nothing until I run quotacheck, at which > point "quota -v" shows the correct values, but I can still use additional > space, and the values are not updated until the next "quotacheck". > i also tried quota's on 2.1.0 (to test rpc.rquotad - which i'll commit in the next days :-) - and it worked well for me - options QUOTA, userquota in /etc/fstab, check_quotas=ON in /etc/sydconfig, reboot, edquota username, cp big_file userhomedir -> message qoutas are exceeded and grace 7 days - where's the problem ? 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 - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-bugs Sun Nov 26 14:36:30 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA07736 for bugs-outgoing; Sun, 26 Nov 1995 14:36:30 -0800 Received: from ncc-1701-d.starfleet.gov (ix-sb1-09.ix.netcom.com [204.32.201.41]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA07731 for ; Sun, 26 Nov 1995 14:36:21 -0800 Received: (from d_burr@localhost) by ncc-1701-d.starfleet.gov (8.6.11/8.6.9) id OAA00654; Sun, 26 Nov 1995 14:39:06 -0800 Date: Sun, 26 Nov 1995 14:39:02 -0800 (PST) From: Donald Burr X-Sender: d_burr@ncc-1701-d To: "Jonathan M. Bresler" cc: James Sabean , bugs@freebsd.org Subject: Re: deleting route to interface tun0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk On Sun, 26 Nov 1995, Jonathan M. Bresler wrote: > On Sun, 26 Nov 1995, James Sabean wrote: > > > After booting, I eventually get a message like the following: > > > > deleting route to interface tun0 (timed out) > > > > This happens even if I have an active PPP session. > > try adding the following lines to /etc/ppp/ppp.conf: > > set timeout 0 > disable lqr > deny lqr Sorry, this won't do it. The "timeout" messages have to do with dynamic routing. You must either be running routed or gated on your system. The only way I know of, to fix this, is to stop running routed/gated (disable it through /etc/sysconfig). Donald Burr [d_burr@ix.netcom.com], PO Box 91212, Santa Barbara CA 93190-1212 TEL (805)564-1871 / FAX 564-2315 / WWW http://www.geopages.com/WallStreet/2072 PGP Public Key available by request (send e-mail) or on Public Key Servers. ** Uphold your right to privacy - Use PGP. ** From owner-freebsd-bugs Sun Nov 26 15:08:20 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA09672 for bugs-outgoing; Sun, 26 Nov 1995 15:08:20 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA09666 for ; Sun, 26 Nov 1995 15:08:15 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id RAA28305; Sun, 26 Nov 1995 17:55:45 -0500 Date: Sun, 26 Nov 1995 17:55:43 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: deleting route to interface tun0 To: Donald Burr cc: James Sabean , bugs@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk On Sun, 26 Nov 1995, Donald Burr wrote: > On Sun, 26 Nov 1995, Jonathan M. Bresler wrote: > > set timeout 0 > > disable lqr > > deny lqr > > Sorry, this won't do it. The "timeout" messages have to do with dynamic > routing. You must either be running routed or gated on your system. The > only way I know of, to fix this, is to stop running routed/gated > (disable it through /etc/sysconfig). then we need to get the man page fixed, i guess. SETTING IDLE TIMER To check/set idletimer, use the ``show timeout'' and ``set timeout'' com- mands. Ex: ppp ON tama> set timeout 600 The timeout period is measured in seconds, the default value for which is 180 or 3 min. To disable the idle timer function, use the command ``set timeout 0''. In -auto mode, an idle timeout causes the PPP session to be closed, though the ppp program itself remains running. Another trigger packet will cause it to attempt to reestablish the link. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-bugs Sun Nov 26 16:21:29 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA16115 for bugs-outgoing; Sun, 26 Nov 1995 16:21:29 -0800 Received: from parody.tecc.co.uk (parody.tecc.co.uk [193.128.6.83]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA16106 for ; Sun, 26 Nov 1995 16:21:11 -0800 Received: (from james@localhost) by parody.tecc.co.uk (8.6.12/8.6.12) id XAA01155; Sun, 26 Nov 1995 23:37:29 GMT Date: Sun, 26 Nov 1995 23:37:28 +0000 () From: James Raynard To: freebsd-bugs@freefall.freebsd.org Subject: Re: List of open Problem Reports In-Reply-To: <199511251230.EAA26252@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG Precedence: bulk On Sat, 25 Nov 1995, GNU GNATS wrote: > [1995/07/08] i386/602 disklabel : changes to cylinder details not saved As the reporter of this fault, I would like to withdraw it as the problem does not occur (in this form) in 2.1.0-RELEASE. However, the drive is still detected as having the wrong number of sectors at boot time and there is still no way of correcting this (AFAIK). The installation program appears to ignore both the BIOS data and any existing disklabel. It is possible to enter a different geometry in the slice editor, but it does not re-calculate the number of sectors. In 2.0R, it was possible to re-label the disk and then re-install, with the correct disk label being recognised. wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 327MB (670320 sectors), 665 cyls, 16 heads, 63 S/T, 512 B/S In fact it is a 425MB disk with 832608 sectors. This is not critical, as it's a fairly mediocre machine that I only use for dialling-up, but it would be nice to get it sorted out. Other than that, 2.1.0R is excellent! James Segmentation fault (core dumped): cannot find file '.signature' From owner-freebsd-bugs Sun Nov 26 21:13:52 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02728 for bugs-outgoing; Sun, 26 Nov 1995 21:13:52 -0800 Received: from sunny.bog.msu.su (dima@sunny.bog.msu.su [158.250.20.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA02721 for ; Sun, 26 Nov 1995 21:13:43 -0800 Received: (from dima@localhost) by sunny.bog.msu.su (8.6.12/8.6.12) id IAA03381; Mon, 27 Nov 1995 08:12:19 +0300 Date: Mon, 27 Nov 1995 08:12:18 +0300 (????) From: Dmitry Khrustalev To: James Sabean cc: bugs@freebsd.org Subject: Re: deleting route to interface tun0 In-Reply-To: <30B8AB55.7810@star.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk On Sun, 26 Nov 1995, James Sabean wrote: > After booting, I eventually get a message like the following: > > deleting route to interface tun0 (timed out) > > This happens even if I have an active PPP session. > > Any suggestions? Is there a way to set the timeout? Is this a > bug? lp0 and tun0 are the only interfaces that I have > configured. You are running gated? Add the following lines to your gated.conf : interfaces { interface all passive simplex; } ; -Dima > > Jim > From owner-freebsd-bugs Mon Nov 27 01:11:21 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA16472 for bugs-outgoing; Mon, 27 Nov 1995 01:11:21 -0800 Received: from phenix.lure.u-psud.fr (phenix.lure.u-psud.fr [193.55.20.208]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA16442 for ; Mon, 27 Nov 1995 01:10:59 -0800 Date: Mon, 27 Nov 1995 01:10:59 -0800 Message-Id: <199511270910.BAA16442@freefall.freebsd.org> Received: from pcbetaille by phenix.lure.u-psud.fr (MX V4.1 VAX) with SMTP; Mon, 27 Nov 1995 10:09:25 MET DST X-Sender: betaille@phenix.lure.u-psud.fr X-Mailer: Windows Eudora Version 1.4.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-bugs@freebsd.org From: betaille@lure.u-psud.fr (Betaille Daniel) Subject: password for ftp loading Sender: owner-bugs@freebsd.org Precedence: bulk I inderstand now why I can't get freebsd 2.1.0Release through ftp: In 2.0.5 the password sent to connect onto the server was "installer@ftp.ibp.fr" and the login name "anonymous", but in 2.1.0 login name and password are ftp, so the server don't accept the connexion. I wrote a few days ago to the ftpmaster of ibp.fr but don't get any answer. What is the solution? Thanks D. Betaille From owner-freebsd-bugs Mon Nov 27 01:33:18 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA17325 for bugs-outgoing; Mon, 27 Nov 1995 01:33:18 -0800 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.138]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA17318 for ; Mon, 27 Nov 1995 01:33:12 -0800 From: gpalmer@westhill.cdrom.com Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.12/8.6.12) with SMTP id BAA02833; Mon, 27 Nov 1995 01:33:01 -0800 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: betaille@lure.u-psud.fr (Betaille Daniel) cc: freebsd-bugs@freebsd.org Subject: Re: password for ftp loading In-reply-to: Your message of "Mon, 27 Nov 1995 01:10:59 PST." <199511270910.BAA16442@freefall.freebsd.org> Date: Mon, 27 Nov 1995 01:33:00 -0800 Message-ID: <2831.817464780@westhill.cdrom.com> Sender: owner-bugs@freebsd.org Precedence: bulk Betaille Daniel wrote in message ID <199511270910.BAA16442@freefall.freebsd.org>: > I inderstand now why I can't get freebsd 2.1.0Release through ftp: In > 2.0.5 the password sent to connect onto the server was > "installer@ftp.ibp.fr" and the login name "anonymous", but in 2.1.0 ^^^^^^^^^^^^^^^^^^^^ This is a bogon that I noticed during the 2.0.5R cycle, but didn't have time to do anything about. More important bogons lurked in that code. > login name and password are ftp, so the server don't accept the > connexion. I wrote a few days ago to the ftpmaster of ibp.fr but don't > get any answer. What is the solution? I dunno. It >>SHOULD<< send ``ftp@'', but either Jordan backed out the patch I sent him, or the patch I sent in doesn't work right (if nothing else, it should still produce ``ftp@'' at the very least). Gary From owner-freebsd-bugs Mon Nov 27 03:15:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA23403 for bugs-outgoing; Mon, 27 Nov 1995 03:15:10 -0800 Received: from beatrix.fss.fokker.nl (beatrix.fss.fokker.nl [145.73.136.30]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA23398 for ; Mon, 27 Nov 1995 03:15:02 -0800 Received: from huh.fss.fokker.nl by beatrix.fss.fokker.nl with SMTP id AA02322 (5.67b/IDA-1.5 for ); Mon, 27 Nov 1995 12:12:43 +0100 From: Jan Hein Buhrman Received: by huh.fss.fokker.nl (931110.SGI//ident-1.0) id AA19171; Mon, 27 Nov 95 12:12:38 +0100 Date: Mon, 27 Nov 95 12:12:38 +0100 Message-Id: <9511271112.AA19171@huh.fss.fokker.nl> To: betaille@lure.u-psud.fr Cc: freebsd-bugs@freebsd.org In-Reply-To: <199511270910.BAA16442@freefall.freebsd.org> (betaille@lure.u-psud.fr) Subject: Re: password for ftp loading Sender: owner-bugs@freebsd.org Precedence: bulk >>>>> "Daniel" == Betaille Daniel writes: > I inderstand now why I can't get freebsd 2.1.0Release through ftp: > In 2.0.5 the password sent to connect onto the server was > "installer@ftp.ibp.fr" and the login name "anonymous", but in 2.1.0 > login name and password are ftp, so the server don't accept the > connexion. I wrote a few days ago to the ftpmaster of ibp.fr but don't > get any answer. What is the solution? Thanks D. Betaille If memory serves me well: you can set your ftp login name and password in the OPTIONS menu. Regards, -- Jan-Hein Buhrman -- Fokker Space & Systems -- -- ---------------------- +31 71 52.45472 ------------------------------------ From owner-freebsd-bugs Mon Nov 27 09:31:56 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15543 for bugs-outgoing; Mon, 27 Nov 1995 09:31:56 -0800 Received: from bigbird.vmicls.com (bigbird.vmicls.com [198.17.96.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA15535 for ; Mon, 27 Nov 1995 09:31:48 -0800 Received: from gonzo by bigbird.vmicls.com (8.6.9/SMI-4.1-vmicls-master-host-1) id MAA05544; Mon, 27 Nov 1995 12:34:05 -0500 From: Jerry.Kendall@vmicls.com (Jerry Kendall) Organization: VMI Communications and Learning Systems Received: by gonzo (5.0/vmi-client-host-1) id AA07791; Mon, 27 Nov 1995 12:34:02 +0500 Date: Mon, 27 Nov 1995 12:34:02 +0500 Message-Id: <9511271734.AA07791.gonzo@vmicls.com> To: freebsd-bugs@freebsd.org Subject: I would like to help out X-Sun-Charset: US-ASCII content-length: 161 Sender: owner-bugs@freebsd.org Precedence: bulk I would like to know how I go about fixing a few of the problems on the bug list. Specifically, where do I get a detailed description of the problem ??? Jerry From owner-freebsd-bugs Mon Nov 27 11:58:27 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23618 for bugs-outgoing; Mon, 27 Nov 1995 11:58:27 -0800 Received: from tellab5.lisle.tellabs.com (tellab5.lisle.tellabs.com [138.111.243.28]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA23578 ; Mon, 27 Nov 1995 11:58:13 -0800 From: mikebo@tellabs.com Received: from sunc210.hq.tellabs.com by tellab5.lisle.tellabs.com with smtp (Smail3.1.29.1 #4) id m0tK9Gx-000jDsC; Mon, 27 Nov 95 13:31 CST Received: by sunc210.hq.tellabs.com (SMI-8.6/1.9) id NAA03249; Mon, 27 Nov 1995 13:31:16 -0600 Message-Id: <199511271931.NAA03249@sunc210.hq.tellabs.com> Subject: 2.0.5R: SCSI hang and panic... HELP To: bugs@freebsd.org Date: Mon, 27 Nov 1995 13:31:15 -0600 (CST) Cc: mikebo (Mike Borowiec), hackers@freebsd.org, questions@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk I'm having tape drive problems... I'm trying to back-up my 2.0.5R machine to 8mm Exabyte, but every time I get close to finishing my tar backup, this happens: ahc0: target 0, lun 0 (sd0) timed out ahc0: target 0, lun 0 (sd0) timed out ...[repeats]... SCSI bus hangs, and I'm forced to reboot system... Rarely, the above messages are followed by: ahc_scsi_cmd0: more than 256 DMA segs sd0: oops not queued biodone: buffer already done Once, this even happened: /: bad dir ino 2 at offset 0: mangled entry panic: bad dir dumping to dev 40, offset 32768 ahc0: not responding The machine is a 486DX50 EISA/VESA w/16MB, with an Adaptec 2742AT EISA SCSI card. Please find dmesg output below... The system kernel is all generic 2.0.5R EXCEPT it has an updated st.c: ($Id: st.c,v 1.38 1995/07/16 09:13:14 gibbs Exp $). Anyone see this before... know of a solution? Any suggestions would be most appreciated... Thanks! - Mike -------------------------------------------------------------------------- Included dmesg output: FreeBSD 2.0.5-RELEASE #0: Fri Sep 1 00:16:43 CDT 1995 kroot@timesink:/usr/src/sys/compile/TIMESINK CPU: i486DX (486-class CPU) real memory = 16384000 (4000 pages) avail memory = 14749696 (3601 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 9 maddr 0xd4000 msize 16384 on isa ed0: address 00:00:c0:d1:09:2d, type WD8013EP (16 bit) bpf: ed0 attached sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface mse0 at 0x23c irq 3 on isa pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in ahc0: reading board settings ahc0: 274x Twin Channel, A SCSI Id=7, B SCSI Id=7, aic7770 >= Rev E, 4 SCBs ahc0: Using Level Sensitive Interrupts ahc0: Downloading Sequencer Program...Done ahc0 at 0x5000-0x50ff irq 11 on eisa slot 5 ahc0: Probing channel A ahc0 waiting for scsi devices to settle ahc0: target 0 synchronous at 4.4MB/s, offset = 0xf (ahc0:0:0): "IMPRIMIS 94601-15 1250" type 0 fixed SCSI 1 sd0(ahc0:0:0): Direct-Access 989MB (2026965 512 byte sectors) ahc0: target 1 synchronous at 10.0MB/s, offset = 0xf (ahc0:1:0): "MAXTOR XT-4380S B5A" type 0 fixed SCSI 1 sd1(ahc0:1:0): Direct-Access 318MB (651630 512 byte sectors) (ahc0:2:0): "ARCHIVE VIPER 150 20000 -000" type 1 removable SCSI 1 st0(ahc0:2:0): Sequential-Access st0: Archive Viper 150 is a known rogue density code 0x0, drive empty (ahc0:5:0): "EXABYTE EXB-8200 4.25" type 1 removable SCSI 1 st1(ahc0:5:0): Sequential-Access density code 0x0, drive empty (ahc0:6:0): "NEC CD-ROM DRIVE:501 2.2" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM cd present.[313218 x 2048 byte records] ahc0: Probing Channel B ahc0 waiting for scsi devices to settle ahb0 not found aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa sb0: opl0 at 0x388 on isa opl0: bpf: lo0 attached bpf: ppp0 attached bpf: sl0 attached -- -------------------------------------------------------------------------- Michael Borowiec - mikebo@tellabs.com - Tellabs Operations Inc. Senior Member of Technical Staff 4951 Indiana Avenue, MS 63 708-512-8211 FAX: 708-512-7099 Lisle, IL 60532 USA -------------------------------------------------------------------------- From owner-freebsd-bugs Mon Nov 27 12:44:14 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA26335 for bugs-outgoing; Mon, 27 Nov 1995 12:44:14 -0800 Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA26161 for ; Mon, 27 Nov 1995 12:43:36 -0800 Received: from plentium.clinet.fi (plentium.clinet.fi [194.100.0.7]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id WAA01108; Mon, 27 Nov 1995 22:43:25 +0200 Received: (hsu@localhost) by plentium.clinet.fi (8.6.12/8.6.4) id WAA13502; Mon, 27 Nov 1995 22:43:03 +0200 Date: Mon, 27 Nov 1995 22:43:03 +0200 Message-Id: <199511272043.WAA13502@plentium.clinet.fi> From: Heikki Suonsivu To: gpalmer@westhill.cdrom.com Cc: freebsd-bugs@freefall.FreeBSD.org In-reply-to: gpalmer@westhill.cdrom.com's message of 27 Nov 1995 14:20:48 +0200 Subject: Re: password for ftp loading Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@FreeBSD.ORG Precedence: bulk I dunno. It >>SHOULD<< send ``ftp@'', but either Jordan backed out the patch I sent him, or the patch I sent in doesn't work right (if nothing else, it should still produce ``ftp@'' at the very least). "ftp@" is usually not accepted by fascist ftp servers. They require that the address is of a specific form, even though the actual contents is not checked (a@b is usually enough). -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi work +358-0-4375209 fax -4555276 home -8031121 From owner-freebsd-bugs Mon Nov 27 13:44:57 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA01273 for bugs-outgoing; Mon, 27 Nov 1995 13:44:57 -0800 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA01262 for ; Mon, 27 Nov 1995 13:44:41 -0800 Received: by Sysiphos id AA03231 (5.67b/IDA-1.5 for bugs@freebsd.org); Mon, 27 Nov 1995 22:41:54 +0100 Message-Id: <199511272141.AA03231@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 27 Nov 1995 22:41:53 +0100 In-Reply-To: iain@nwpeople.demon.co.uk (Iain Baird) "NCR815 problem" (Nov 27, 18:26) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: iain@nwpeople.demon.co.uk Subject: Re: NCR815 problem Cc: bugs@freebsd.org Sender: owner-bugs@freebsd.org Precedence: bulk On Nov 27, 18:26, Iain Baird wrote: } Subject: NCR815 problem } I have just installed an NCR-815 PCI SCSI controller in my PC. } When I boot 2.1.0-951026-SNAP (off IDE) I get the following error: } } pci_map_mem failed: device's memrange 0xc8000-0xc80ff is } incompatible with its bridge's memrange 0x4000000-0xffffffff } } After this the driver still detects sd0 correctly, but I'm unable } to access it in any way. } } Occasionally (with cache enabled) the above error is followed by: } } CACHE TEST FAILED: reg dstat-sstat2 readback ffffffff. } CACHE INCORRECTLY CONFIGURED. } } Disabling the cache doesn't prevent the pci_map_mem error. } } What does all this mean? Do I need a new motherboard? } Have I got a duff NCR815? Thanks in advance for any help. Hmmm, this is a very surprising bug report :) Well, seems your system violates one of the assumptions of the PCI code: The PCI devices are expected to be mapped to addresses beyond the 1st Gigabyte of address space. This used to be treated as fatal, but I choose to make it a warning message, when I found that some Compaq machine behaved just the way your system does ... Your system uses much lower addresses: 0xc0000 is an address below 1MB, i.e. in the ISA peripheral address space. This ought to work, provided your system doesn't try to cache accesses to the 640KB to 1MB address range, and that you didn't turn on copying of BIOS ROMs into RAM at those addresses. Could you please verify the BIOS setup ? } Probing for devices on the PCI bus: } chip0 rev 4 on pci0:0 } chip1 rev 3 on pci0:2 } ncr0 rev 3 int a irq 15 on pci0:3 ^^ I'd rather avoid IRQ 15 in a system that also got IDE drives. Haven't heard that it actually caused problems, but I'd be afraid that IDE might want to have 14 and 15 for its own use (and might for example install interrupt handlers). } pci_map_mem failed: device's memrange 0xcc000-0xcc0ff is incompatible with its bridge's memrange 0x4000000-0xffffffff } ncr0 waiting for scsi devices to settle } (ncr0:0:0): "SEAGATE ST31250N 0006" type 0 fixed SCSI 2 } sd0(ncr0:0:0): Direct-Access } sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } 973MB (1994037 512 byte sectors) } vga0 rev 0 on pci0:4 } pci0:5: vendor=0x1c1c, device=0x0001, class=old (misc) [no driver assigned] ^^^^^^ any idea, what kind of device that is ? } ncr0 rev 3 int a irq 15 on pci0:3 } pci_map_mem failed: device's memrange 0xcc000-0xcc0ff is incompatible with its bridge's memrange 0x4000000-0xffffffff } CACHE TEST FAILED: reg dstat-sstat2 readback ffffffff. The cache test makes the CPU and the NCR write memory, and verifies, that they get the correct results reading back the values written by the other one. If this test fails, then the NCR could not reliably access the command queue written by the host CPU, and the driver aborts at this point, since proceeding might wreck your data. But this is most likely a secondary effect, caused by the use of an unsuitable attach address, which has been choosen by the PCI BIOS. If you have copying of BIOS ROMs to DRAM enabled in the BIOS, then please try without ... If this doesn't help, then send **verbose** boot messages, i.e. enter "-v" at the "Boot: " prompt. This will make the log contain additional PCI setup information ... You will be able to use that 815 controller card, but it might be necessary to build a custom kernel. 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-bugs Mon Nov 27 14:30:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA05353 for bugs-outgoing; Mon, 27 Nov 1995 14:30:07 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA05346 ; Mon, 27 Nov 1995 14:30:03 -0800 Date: Mon, 27 Nov 1995 14:30:03 -0800 Message-Id: <199511272230.OAA05346@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/839: by default, "at" is allowed only for superuser Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR bin/839; it has been noted by GNATS. From: J Wunsch To: ylo@cs.hut.fi Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/839: by default, "at" is allowed only for superuser Date: Mon, 27 Nov 1995 23:18:45 +0100 (MET) As Tatu Ylonen wrote: > > By default, the "at" command is only allowed for superuser. > This is overly restrictive, since it should not involve any security > risks. I think, this conforms with the traditional Unix behaviour. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Nov 27 17:10:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17213 for bugs-outgoing; Mon, 27 Nov 1995 17:10:06 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17202 ; Mon, 27 Nov 1995 17:10:04 -0800 Resent-Date: Mon, 27 Nov 1995 17:10:04 -0800 Resent-Message-Id: <199511280110.RAA17202@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, peter@jhome.DIALix.COM Received: from jhome.DIALix.COM (jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA16841 for ; Mon, 27 Nov 1995 17:05:59 -0800 Received: (from peter@localhost) by jhome.DIALix.COM (8.6.12/8.6.9) id JAA27254; Tue, 28 Nov 1995 09:05:23 +0800 Message-Id: <199511280105.JAA27254@jhome.DIALix.COM> Date: Tue, 28 Nov 1995 09:05:23 +0800 From: Peter Wemm Reply-To: peter@jhome.DIALix.COM To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/840: Kernel page directory invalid Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 840 >Category: kern >Synopsis: Kernel page directory invalid >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 17:10:01 PST 1995 >Last-Modified: >Originator: Peter Wemm >Organization: At this time of the day??? >Release: FreeBSD 2.2-CURRENT i386 >Environment: Two machines have shown this problem:- One of our news servers (average uptime about a week): FreeBSD gecko2.DIALix.COM 2.2-CURRENT FreeBSD 2.2-CURRENT #2: Fri Oct 27 21:02:24 WST 1995 pwroot@gecko2.DIALix.com:/home/src/sys/compile/NEWS i386 And a small machine in my boss's office that he works on (and paniced while talking to me on the phone when idle.. Apparently cron forked or something): FreeBSD office.DIALix.oz.au 2.2-CURRENT FreeBSD 2.2-CURRENT #2: Mon Sep 25 02:58:48 WST 1995 pwroot@office.DIALix.oz.au:/usr/src/sys/compile/OFFICE i386 >Description: The news server appeared to crash more often when innd was compiled to use mmap() for the active file and the dbz history table indexes. This is only subjective though.. It appeared to last about three days on average with mmap() and appears to last about a week without.. But it did vary, and we just may have had a bad run of the same problem with mmap() active. We've had the news server silently reboot overnight without saving it's dmesg buffer and this is the first time we've caught it. gecko2 (the news server) locked up at "Syncing disks" this morning with: Kernel page directory invalid! pa=0x989023 va=0xefbfe000 When this was read out to me on the phone, I remembered that the office machine had crashed from the same problem. dmesg for the news server (note the vnode_pager_putpages error at the end) FreeBSD 2.2-CURRENT #2: Fri Oct 27 21:02:24 WST 1995 pwroot@gecko2.DIALix.com:/home/src/sys/compile/NEWS CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 33554432 (32768K bytes) avail memory = 30748672 (30028K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:40:c7:11:09:1f, type NE2000 (16 bit) sio0 not found at 0x3f8 sio1 not found at 0x2f8 lpt0 not found at 0xffffffff si0 irq 12 maddr 0xe8000 msize 32768 on isa si0: card: SIHOST2, ports: 8, modules: 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 bt0 not found at 0x330 aha0 at 0x330-0x333 irq 11 drq 5 on isa (aha0:0:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1042MB (2134305 512 byte sectors) (aha0:1:0): "QUANTUM VP32210 581H" type 0 fixed SCSI 2 sd1(aha0:1:0): Direct-Access 2103MB (4308352 512 byte sectors) npx0 on motherboard npx0: INT 16 interface new masks: bio c0000840, tty c0031002, net c0031022 WARNING: / was not properly dismounted. vnode_pager_putpages: attempt to write meta-data!!! -- 0xfffe9000(ff) I've not updated it's kernel for a while after hearing about problems others are having with post-november-7 kernels, but it might be worth a try to see if it throws any new light on it. >How-To-Repeat: Run a news server and wait... >Fix: If only I knew.. :-) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 18:50:15 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA24327 for bugs-outgoing; Mon, 27 Nov 1995 18:50:15 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA24305 ; Mon, 27 Nov 1995 18:50:09 -0800 Resent-Date: Mon, 27 Nov 1995 18:50:09 -0800 Resent-Message-Id: <199511280250.SAA24305@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA23973 for ; Mon, 27 Nov 1995 18:48:07 -0800 Received: (root@localhost) by hauki.clinet.fi (8.6.12/8.6.4) id EAA02241; Tue, 28 Nov 1995 04:47:53 +0200 Message-Id: <199511280247.EAA02241@hauki.clinet.fi> Date: Tue, 28 Nov 1995 04:47:53 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/841: stale nfs mounts cannot be umounted Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 841 >Category: bin >Synopsis: stale nfs mounts cannot be umounted >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 18:50:03 PST 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: a stale nfs mount, like this one: df: /m/hauki/customer: Stale NFS file handle >Description: Trying to umount it fails: hsu#katiska.clinet.fi Tue 163: umount /m/hauki/customer umount: hauki.clinet.fi:/m/hauki/customer: No such file or directory hsu#katiska.clinet.fi Tue 165: umount -f /m/hauki/customer umount: hauki.clinet.fi:/m/hauki/customer: No such file or directory hsu#katiska.clinet.fi Tue 166: mount /m/hauki/customer mount: /m/hauki/customer: Stale NFS file handle So the only way to get rid of it is to reboot the machine. On FreeBSD 1.1.5.1 -f is enough, on SunOS it can be umounted if there are no stale handles on the mounted filesystem (killing holders of them fixes that). >How-To-Repeat: Get a disk crash on your nfs server and try to get things up again. A big hammer will probably do, if you don't happen to own any barracudas. >Fix: Force option should do something? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 19:50:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA28800 for bugs-outgoing; Mon, 27 Nov 1995 19:50:10 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA28760 ; Mon, 27 Nov 1995 19:50:05 -0800 Resent-Date: Mon, 27 Nov 1995 19:50:05 -0800 Resent-Message-Id: <199511280350.TAA28760@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, lyndon@orthanc.com Received: from orodruin.orthanc.com (orodruin.orthanc.com [204.244.20.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA28694 for ; Mon, 27 Nov 1995 19:49:18 -0800 Received: (from lyndon@localhost) by orodruin.orthanc.com (8.6.12/8.6.12) id TAA20603; Mon, 27 Nov 1995 19:49:10 -0800 Message-Id: <199511280349.TAA20603@orodruin.orthanc.com> Date: Mon, 27 Nov 1995 19:49:10 -0800 From: lyndon@orthanc.com Reply-To: lyndon@orthanc.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/842: hackers@freebsd.org is suffering meltdown Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 842 >Category: docs >Synopsis: hackers@freebsd.org is suffering meltdown >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 19:50:02 PST 1995 >Last-Modified: >Originator: Lyndon Nerenberg >Organization: Orthanc Systems: Internet and UNIX consulting >Release: FreeBSD 2.1.0-951104-SNAP i386 >Environment: FreeBSD X.X >Description: The amount of discussion on hackers@freebsd.org related to the lack of an iBCS2 man page has exceeded the effort required to fix the problem :-) >How-To-Repeat: echo "where is the iBCS2 doc?" | mail hackers@freebsd.org >Fix: Add the following man page to the distribution. .Dd November 27, 1995 .Dt IBCS2 8 .Os FreeBSD-Experimental .Sh NAME .Nm ibcs2 .Nd load iBCS2 runtime support for SCO and ISC binaries .Sh SYNOPSIS .Nm ibcs2 .Sh DESCRIPTION The .Nm utility loads kernel runtime support for iBCS2 compliant programs. This runtime support is limited to emulation of the iBCS2 system call interface, and is far from complete. COFF binaries and shared libraries are supported, however no shared libraries are provided with the FreeBSD distribution. .Sh FILES .Bl -tag -width /lkm/ibcs2_coff.o -compact .It Pa /lkm/ibcs2_mod.o .It Pa /lkm/ibcs2_coff_mod.o .It Pa /lkm/socksys_mod.o iBCS2 loadable kernel modules .Sh "SEE ALSO" .Pa /sys/i386/ibcs2/README.iBCS2 , .Xr modload 8 , .Xr lkm 4 .Sh BUGS The emulation is very incomplete. .Pp Running dynamically linked binaries requires access to an existing SCO system from which you can grab the shared libraries. .Pp You can't really use this without reading the source code. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 20:30:03 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA00630 for bugs-outgoing; Mon, 27 Nov 1995 20:30:03 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA00624 ; Mon, 27 Nov 1995 20:30:01 -0800 Resent-Date: Mon, 27 Nov 1995 20:30:01 -0800 Resent-Message-Id: <199511280430.UAA00624@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.star89.galstar.com Received: from aldan (PPP-83-3.BU.EDU [128.197.8.87]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA00406 for ; Mon, 27 Nov 1995 20:20:25 -0800 Received: (from root@localhost) by aldan (8.6.12/8.6.12) id XAA16273; Mon, 27 Nov 1995 23:19:05 -0500 Message-Id: <199511280419.XAA16273@aldan> Date: Mon, 27 Nov 1995 23:19:05 -0500 From: mi@ALDAN.star89.galstar.com Reply-To: mi@ALDAN.star89.galstar.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/843: manpath complaints about /usr/X386/man Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 843 >Category: docs >Synopsis: manpath complaints about /usr/X386/man >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 20:30:01 PST 1995 >Last-Modified: >Originator: &khail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: Out of the box /etc/manpath.config lists nonexistent /usr/X386/man directory as a MANDATORY_MANPATH. >How-To-Repeat: manpath >Fix: Remove (comment out) /usr/X386/man line >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 21:10:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02315 for bugs-outgoing; Mon, 27 Nov 1995 21:10:07 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02296 ; Mon, 27 Nov 1995 21:10:03 -0800 Resent-Date: Mon, 27 Nov 1995 21:10:03 -0800 Resent-Message-Id: <199511280510.VAA02296@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA01884 for ; Mon, 27 Nov 1995 21:06:46 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id HAA04462 for ; Tue, 28 Nov 1995 07:06:17 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id HAA03154; Tue, 28 Nov 1995 07:06:51 +0200 Message-Id: <199511280506.HAA03154@katiska.clinet.fi> Date: Tue, 28 Nov 1995 07:06:51 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/844: mbuf panic, dump available Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 844 >Category: kern >Synopsis: mbuf panic, dump available >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 21:10:01 PST 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: Nov 27 20:29:47 hauki /kernel: FreeBSD 2.2-CURRENT #2: Sun Nov 26 06:35:44 EET 1995 Nov 27 20:29:47 hauki /kernel: hsu@katiska.clinet.fi:/usr/current/src/sys/compile/CLINETSERVER Nov 27 20:29:48 hauki /kernel: CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) Nov 27 20:29:48 hauki /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 Nov 27 20:29:48 hauki /kernel: Features=0x1bf Nov 27 20:29:48 hauki /kernel: real memory = 33554432 (32768K bytes) Nov 27 20:29:48 hauki /kernel: avail memory = 30068736 (29364K bytes) Nov 27 20:29:48 hauki /kernel: Probing for devices on the ISA bus: Nov 27 20:29:48 hauki /kernel: vt0 at 0x60-0x6f irq 1 on motherboard Nov 27 20:29:48 hauki /kernel: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Nov 27 20:29:48 hauki /kernel: ed0 not found at 0x280 Nov 27 20:29:48 hauki /kernel: lpt0 at 0x378-0x37f irq 7 on isa Nov 27 20:29:49 hauki /kernel: lpt0: Interrupt-driven port Nov 27 20:29:49 hauki /kernel: lp0: TCP/IP capable interface Nov 27 20:29:49 hauki /kernel: lpt1 not found at 0xffffffff Nov 27 20:29:49 hauki /kernel: lpt2 not found at 0xffffffff Nov 27 20:29:49 hauki /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Nov 27 20:29:49 hauki /kernel: sio0: type 16550A Nov 27 20:29:49 hauki /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Nov 27 20:29:49 hauki /kernel: sio1: type 16550A Nov 27 20:29:49 hauki /kernel: sio2 not found at 0x3e8 Nov 27 20:29:49 hauki /kernel: sio3 not found at 0x2e8 Nov 27 20:29:49 hauki /kernel: pca0 on isa Nov 27 20:29:50 hauki /kernel: pca0: PC speaker audio driver Nov 27 20:29:50 hauki /kernel: bt0: Bt946C/ 0-PCI/EISA/VLB(32bit) bus Nov 27 20:29:50 hauki /kernel: bt0: reading board settings, busmastering, int=11 Nov 27 20:29:50 hauki /kernel: bt0: version 4.23, sync, parity, 32 mbxs, 32 ccbs Nov 27 20:29:50 hauki /kernel: bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 Nov 27 20:29:50 hauki /kernel: bt0: targ 2 sync rate=10.00MB/s(100ns), offset=15 Nov 27 20:29:50 hauki /kernel: bt0: Using Strict Round robin scheme Nov 27 20:29:50 hauki /kernel: bt0 at 0x330 irq 11 on isa Nov 27 20:29:50 hauki /kernel: bt0 waiting for scsi devices to settle Nov 27 20:29:50 hauki /kernel: (bt0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Nov 27 20:29:50 hauki /kernel: sd0(bt0:0:0): Direct-Access 1003MB (2055035 512 byte sectors) Nov 27 20:29:50 hauki /kernel: sd0(bt0:0:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Nov 27 20:29:50 hauki /kernel: (bt0:2:0): "IBM OEM 0662S12 3 30" type 0 fixed SCSI 2 Nov 27 20:29:51 hauki /kernel: sd2(bt0:2:0): Direct-Access 1003MB (2055035 512 byte sectors) Nov 27 20:29:51 hauki /kernel: sd2(bt0:2:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Nov 27 20:29:51 hauki /kernel: aha0 not probed due to I/O address conflict with bt0 at 0x330 Nov 27 20:29:51 hauki /kernel: wdc0 not found at 0x1f0 Nov 27 20:29:51 hauki /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Nov 27 20:29:51 hauki /kernel: fdc0: NEC 72065B Nov 27 20:29:51 hauki /kernel: fd0: 1.44MB 3.5in Nov 27 20:29:51 hauki /kernel: mcd0: timeout getting status Nov 27 20:29:51 hauki /kernel: mcd0 not found at 0x300 Nov 27 20:29:51 hauki /kernel: npx0 on motherboard Nov 27 20:29:51 hauki /kernel: npx0: INT 16 interface Nov 27 20:29:51 hauki /kernel: matcdc0 not found at 0xffffffff Nov 27 20:29:51 hauki /kernel: matcdc1 not found at 0xffffffff Nov 27 20:29:52 hauki /kernel: matcdc2 not found at 0xffffffff Nov 27 20:29:52 hauki /kernel: matcdc3 not found at 0xffffffff Nov 27 20:29:52 hauki /kernel: Probing for devices on the PCI bus: Nov 27 20:29:52 hauki /kernel: pci0:0: Silicon Integrated Systems, device=0x5511, class=bridge (host) [no driver assigned] Nov 27 20:29:52 hauki /kernel: chip0 rev 1 on pci0:1 Nov 27 20:29:52 hauki /kernel: vga0 rev 0 int a irq 12 on pci0:9 Nov 27 20:29:52 hauki /kernel: chip1 rev 2 on pci0:10 Nov 27 20:29:52 hauki /kernel: pci0:11: Bus Logic, device=0x1040, class=storage (scsi) [no driver assigned] Nov 27 20:29:52 hauki /kernel: Probing for devices on the PCI bus: Nov 27 20:29:52 hauki /kernel: de0 rev 35 int a irq 10 on pci1:4 Nov 27 20:29:52 hauki /kernel: de0: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:00:c0:50:01:c0 Nov 27 20:29:52 hauki /kernel: de0: enabling Thinwire/AUI port Nov 27 20:29:52 hauki /kernel: de1 rev 35 int a irq 12 on pci1:5 Nov 27 20:29:53 hauki /kernel: de1: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:00:c0:1e:02:c0 Nov 27 20:29:53 hauki /kernel: de1: enabling Thinwire/AUI port Nov 27 20:29:53 hauki /kernel: changing root device to sd0a Nov 27 20:29:53 hauki /kernel: new masks: bio c0000840, tty c003009a, net c003149a Nov 27 20:29:53 hauki /kernel: WARNING: / was not properly dismounted. Nov 27 20:29:53 hauki /kernel: sd2: raw partition size != slice size Nov 27 20:29:53 hauki /kernel: sd2: start 0, end 2055034, size 2055035 Nov 27 20:29:53 hauki /kernel: sd2c: start 0, end 2038904, size 2038905 >Description: mbuf panic, best documented in the crash dump. against sup from around 26th Nov 17:00 GMT. The dump is available in ftp://clinet.fi/pub/FreeBSD/crashdumps/{kernel,vmcore}.1.gz This could be related to Nov 27 18:41:13 hauki /kernel: Probing for devices on the PCI bus: Nov 27 18:41:13 hauki /kernel: de0 rev 35 int a irq 1 0 on pci1:4 Nov 27 18:41:13 hauki /kernel: Data modified on freelist: word 0 of object 0xf0d 40a00 size 256 previous type free (0x9a0328 != 0xdeadc0de) Nov 27 18:41:13 hauki /kernel: de0: DC21040 [10Mb/s] pass 2.3 Ethernet address 0 0:00:c0:50:01:c0 Nov 27 18:41:13 hauki /kernel: de0: enabling Thinwire/AUI port Nov 27 18:41:13 hauki /kernel: de1 rev 35 int a irq 1 2 on pci1:5 Nov 27 18:41:13 hauki /kernel: de1: DC21040 [10Mb/s] pass 2.3 Ethernet address 0 0:00:c0:1e:02:c0 I have seen these occasionally in a running system, but this is the first time I see one within boot messages. >How-To-Repeat: I don't know (relates to my previous report, this is the only dump which actually made it to the disk, others were lost in panic before savecore completed). >Fix: Don't know, but data structure being freed contains 0xdeadc0de data... >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 21:20:08 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02960 for bugs-outgoing; Mon, 27 Nov 1995 21:20:08 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA02927 ; Mon, 27 Nov 1995 21:20:05 -0800 Resent-Date: Mon, 27 Nov 1995 21:20:05 -0800 Resent-Message-Id: <199511280520.VAA02927@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA02357 for ; Mon, 27 Nov 1995 21:10:50 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id HAA04516 for ; Tue, 28 Nov 1995 07:10:29 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id HAA03321; Tue, 28 Nov 1995 07:11:04 +0200 Message-Id: <199511280511.HAA03321@katiska.clinet.fi> Date: Tue, 28 Nov 1995 07:11:04 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/845: Automatic reboot says you can abort but boots anyway Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 845 >Category: kern >Synopsis: Automatic reboot says you can abort but boots anyway >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 21:20:02 PST 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: Nov 27 20:40:31 hauki /kernel: FreeBSD 2.2-CURRENT #2: Sun Nov 26 06:35:44 EET 1995 Nov 27 20:40:31 hauki /kernel: hsu@katiska.clinet.fi:/usr/current/src/sys/compile/CLINETSERVER Nov 27 20:40:31 hauki /kernel: CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) Nov 27 20:40:31 hauki /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 Nov 27 20:40:31 hauki /kernel: Features=0x1bf Nov 27 20:40:31 hauki /kernel: real memory = 33554432 (32768K bytes) Nov 27 20:40:31 hauki /kernel: avail memory = 30068736 (29364K bytes) Nov 27 20:40:31 hauki /kernel: Probing for devices on the ISA bus: Nov 27 20:40:32 hauki /kernel: vt0 at 0x60-0x6f irq 1 on motherboard Nov 27 20:40:32 hauki /kernel: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Nov 27 20:40:32 hauki /kernel: ed0 not found at 0x280 Nov 27 20:40:32 hauki /kernel: lpt0 at 0x378-0x37f irq 7 on isa Nov 27 20:40:32 hauki /kernel: lpt0: Interrupt-driven port Nov 27 20:40:32 hauki /kernel: lp0: TCP/IP capable interface Nov 27 20:40:32 hauki /kernel: lpt1 not found at 0xffffffff Nov 27 20:40:32 hauki /kernel: lpt2 not found at 0xffffffff Nov 27 20:40:32 hauki /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Nov 27 20:40:33 hauki /kernel: sio0: type 16550A Nov 27 20:40:33 hauki /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Nov 27 20:40:33 hauki /kernel: sio1: type 16550A Nov 27 20:40:33 hauki /kernel: sio2 not found at 0x3e8 Nov 27 20:40:33 hauki /kernel: sio3 not found at 0x2e8 Nov 27 20:40:33 hauki /kernel: pca0 on isa Nov 27 20:40:33 hauki /kernel: pca0: PC speaker audio driver Nov 27 20:40:33 hauki /kernel: bt0: Bt946C/ 0-PCI/EISA/VLB(32bit) bus Nov 27 20:40:33 hauki /kernel: bt0: reading board settings, busmastering, int=11 Nov 27 20:40:33 hauki /kernel: bt0: version 4.23, sync, parity, 32 mbxs, 32 ccbs Nov 27 20:40:33 hauki /kernel: bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 Nov 27 20:40:34 hauki /kernel: bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 Nov 27 20:40:34 hauki /kernel: bt0: targ 2 sync rate=10.00MB/s(100ns), offset=15 Nov 27 20:40:34 hauki /kernel: bt0: Using Strict Round robin scheme Nov 27 20:40:34 hauki /kernel: bt0 at 0x330 irq 11 on isa Nov 27 20:40:34 hauki /kernel: bt0 waiting for scsi devices to settle Nov 27 20:40:34 hauki /kernel: (bt0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Nov 27 20:40:34 hauki /kernel: sd0(bt0:0:0): Direct-Access 1003MB (2055035 512 byte sectors) Nov 27 20:40:34 hauki /kernel: sd0(bt0:0:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Nov 27 20:40:34 hauki /kernel: (bt0:1:0): "SEAGATE ST32550N 0012" type 0 fixed SCSI 2 Nov 27 20:40:34 hauki /kernel: sd1(bt0:1:0): Direct-Access 2047MB (4194058 512 byte sectors) Nov 27 20:40:34 hauki /kernel: sd1(bt0:1:0): with 3511 cyls, 11 heads, and an average 108 sectors/track Nov 27 20:40:34 hauki /kernel: (bt0:2:0): "IBM OEM 0662S12 3 30" type 0 fixed SCSI 2 Nov 27 20:40:34 hauki /kernel: sd2(bt0:2:0): Direct-Access 1003MB (2055035 512 byte sectors) Nov 27 20:40:34 hauki /kernel: sd2(bt0:2:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Nov 27 20:40:35 hauki /kernel: aha0 not probed due to I/O address conflict with bt0 at 0x330 Nov 27 20:40:35 hauki /kernel: wdc0 not found at 0x1f0 Nov 27 20:40:35 hauki /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Nov 27 20:40:35 hauki /kernel: fdc0: NEC 72065B Nov 27 20:40:35 hauki /kernel: fd0: 1.44MB 3.5in Nov 27 20:40:35 hauki /kernel: mcd0: timeout getting status Nov 27 20:40:35 hauki /kernel: mcd0 not found at 0x300 Nov 27 20:40:35 hauki /kernel: npx0 on motherboard Nov 27 20:40:35 hauki /kernel: npx0: INT 16 interface Nov 27 20:40:35 hauki /kernel: matcdc0 not found at 0xffffffff Nov 27 20:40:35 hauki /kernel: matcdc1 not found at 0xffffffff Nov 27 20:40:35 hauki /kernel: matcdc2 not found at 0xffffffff Nov 27 20:40:36 hauki /kernel: matcdc3 not found at 0xffffffff Nov 27 20:40:36 hauki /kernel: Probing for devices on the PCI bus: Nov 27 20:40:36 hauki /kernel: pci0:0: Silicon Integrated Systems, device=0x5511, class=bridge (host) [no driver assigned] Nov 27 20:40:36 hauki /kernel: chip0 rev 1 on pci0:1 Nov 27 20:40:36 hauki /kernel: vga0 rev 0 int a irq 12 on pci0:9 Nov 27 20:40:36 hauki /kernel: chip1 rev 2 on pci0:10 Nov 27 20:40:36 hauki /kernel: pci0:11: Bus Logic, device=0x1040, class=storage (scsi) [no driver assigned] Nov 27 20:40:36 hauki /kernel: Probing for devices on the PCI bus: Nov 27 20:40:36 hauki /kernel: de0 rev 35 int a irq 10 on pci1:4 Nov 27 20:40:36 hauki /kernel: de0: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:00:c0:50:01:c0 Nov 27 20:40:36 hauki /kernel: de0: enabling Thinwire/AUI port Nov 27 20:40:36 hauki /kernel: de1 rev 35 int a irq 12 on pci1:5 Nov 27 20:40:37 hauki /kernel: de1: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:00:c0:1e:02:c0 Nov 27 20:40:37 hauki /kernel: de1: enabling Thinwire/AUI port Nov 27 20:40:37 hauki /kernel: changing root device to sd0a Nov 27 20:40:37 hauki /kernel: new masks: bio c0000840, tty c003009a, net c003149a Nov 27 20:40:37 hauki /kernel: sd2: raw partition size != slice size Nov 27 20:40:37 hauki /kernel: sd2: start 0, end 2055034, size 2055035 Nov 27 20:40:37 hauki /kernel: sd2c: start 0, end 2038904, size 2038905 >Description: After a panic, the system says Automatic reboot in 15 seconds, press any key to abort but keypress has no effect, it reboots anyway, making it hard to recover the panic message. I think this feature worked before, but I'm not sure whether it worked after I switched into pcvt. >How-To-Repeat: Get a panic and see if you can stop the system from rebooting. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 21:21:25 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA03060 for bugs-outgoing; Mon, 27 Nov 1995 21:21:25 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA03039 for ; Mon, 27 Nov 1995 21:21:19 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA23599; Tue, 28 Nov 1995 06:21:13 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA18522; Tue, 28 Nov 1995 06:21:13 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id XAA07523; Mon, 27 Nov 1995 23:44:33 +0100 From: J Wunsch Message-Id: <199511272244.XAA07523@uriah.heep.sax.de> Subject: Re: I would like to help out To: Jerry.Kendall@vmicls.com (Jerry Kendall) Date: Mon, 27 Nov 1995 23:44:33 +0100 (MET) Cc: freebsd-bugs@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9511271734.AA07791.gonzo@vmicls.com> from "Jerry Kendall" at Nov 27, 95 12:34:02 pm 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: 534 Sender: owner-bugs@freebsd.org Precedence: bulk As Jerry Kendall wrote: > > I would like to know how I go about fixing a few of the problems > on the bug list. > > Specifically, > where do I get a detailed description of the problem ??? I think, there are Web (http://www.freebsd.org/) and email (majordomo@freebsd.org) interfaces right now. If you've got an account on freefall, you can also use query-pr directly. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Nov 27 21:40:08 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA04094 for bugs-outgoing; Mon, 27 Nov 1995 21:40:08 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA04047 ; Mon, 27 Nov 1995 21:40:05 -0800 Resent-Date: Mon, 27 Nov 1995 21:40:05 -0800 Resent-Message-Id: <199511280540.VAA04047@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA03581 for ; Mon, 27 Nov 1995 21:31:22 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id HAA04723 for ; Tue, 28 Nov 1995 07:30:57 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id HAA03920; Tue, 28 Nov 1995 07:31:37 +0200 Message-Id: <199511280531.HAA03920@katiska.clinet.fi> Date: Tue, 28 Nov 1995 07:31:37 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/846: 2.1R install disk tries to use sd0 even if not requested. Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 846 >Category: conf >Synopsis: 2.1R install disk tries to use sd0 even if not requested. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 27 21:40:03 PST 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.2-CURRENT i386 >Environment: A system with SCSI disks, trying to add a new one. >Description: I tried to install second hard disk (actually recovering after a crash and reinstalling the driver after formatting). As the fdisk utility is mostly incomprehensible and disklabel clumsy, I tried to use the boot floppy to the job. I specified that I want to install only the sd1 and no other disks (tagged only the sd1 in the form, sd0 being the root disk and sd2 being another disk already in the system). fdisk went fine, but disklabel offered me both sd0 and sd1. I could create the partitions to sd1 but if I try W)rite, it asks if I'm sure I want to build the filesystems now, which I didn't quite find a nice idea for my root disk :-(. I bailed out, so I don't know whether it would really have newfs's my root disk if I had continued. >How-To-Repeat: I think you can repeat this by trying to do a FreeBSD installation on sd1 when there already is an existing FreeBSD installation on sd0, just specify that you only want to use sd1 and completely ignore sd0. Won't work. >Fix: Workaround: use only the fdisk part of the boot floppies and disklabel -e to take care of the rest. The boot diskette should not do anything to other disks than the one being installed? fdisk which comes with the system is very unhelpful (if you print an error message, you also print help for either what to do or how to find more information. disklabel is just clumsy, I kind of wish that I could install disks without playing with a calculator to find out that I got the offsets right. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Nov 27 22:30:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA07530 for bugs-outgoing; Mon, 27 Nov 1995 22:30:05 -0800 Received: from mirage.mirageport.com (root@gw-mirage.cyberport.com [204.134.75.198]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA07471 for ; Mon, 27 Nov 1995 22:29:53 -0800 Received: from mirage (cowan@localhost [127.0.0.1]) by mirage.mirageport.com (8.6.12/8.6.9) with SMTP id AAA00917 for ; Tue, 28 Nov 1995 00:33:27 -0700 Message-Id: <199511280733.AAA00917@mirage.mirageport.com> Date: Tue, 28 Nov 95 00:33:28 -0700 From: Cowan Bowman X-Mailer: Mozilla 1.1N (X11; I; Linux 1.2.13 i486) MIME-Version: 1.0 To: bugs@freebsd.org Subject: Keyboard lockup on boot installation disk X-URL: http://www.freebsd.org/support.html Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-bugs@freebsd.org Precedence: bulk Hi, I am having problems installing FreeBSD. When it probes for the keyboard it fails to find it. I get this message on the boot sequence. scprobe: keyboard RESET failed fe My machine is an Intel based 386DX running at 25 Mhz. The mother board is an ISA type. Is there anyway I could get a fix for this? If there is anymore information you might need to help with this problem e-mail me back with what you need to know and I will send it to you. Thanks a lot, I look foward to using this OS but need to get over this problem. Cowan L. Bowman cowan@mirage.mirageport.com From owner-freebsd-bugs Mon Nov 27 23:30:12 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA12290 for bugs-outgoing; Mon, 27 Nov 1995 23:30:12 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA12260 ; Mon, 27 Nov 1995 23:30:07 -0800 Date: Mon, 27 Nov 1995 23:30:07 -0800 Message-Id: <199511280730.XAA12260@freefall.freebsd.org> To: freebsd-bugs Cc: From: Lyndon Nerenberg (VE7TCP) Subject: Re: docs/842: hackers@freebsd.org is suffering meltdown Reply-To: Lyndon Nerenberg (VE7TCP) Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR docs/842; it has been noted by GNATS. From: Lyndon Nerenberg (VE7TCP) To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: docs/842: hackers@freebsd.org is suffering meltdown Date: Mon, 27 Nov 1995 23:20:50 -0800 You would think I could get this right ;-( < .Bl -tag -width /lkm/ibcs2_coff.o -compact > .Bl -tag -width /lkm/ibcs2_coff_mod.o -compact --foo From owner-freebsd-bugs Mon Nov 27 23:56:03 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA14493 for bugs-outgoing; Mon, 27 Nov 1995 23:56:03 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA14138 ; Mon, 27 Nov 1995 23:51:29 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA27257; Tue, 28 Nov 1995 08:50:46 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA19039; Tue, 28 Nov 1995 08:50:46 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA09229; Tue, 28 Nov 1995 08:26:17 +0100 From: J Wunsch Message-Id: <199511280726.IAA09229@uriah.heep.sax.de> Subject: Re: 2.0.5R: SCSI hang and panic... HELP To: mikebo@tellabs.com Date: Tue, 28 Nov 1995 08:26:16 +0100 (MET) Cc: bugs@freebsd.org, mikebo@freefall.freebsd.org, hackers@freebsd.org, questions@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199511271931.NAA03249@sunc210.hq.tellabs.com> from "mikebo@tellabs.com" at Nov 27, 95 01:31:15 pm 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: 743 Sender: owner-bugs@freebsd.org Precedence: bulk As mikebo@tellabs.com wrote: > > ahc0: target 0, lun 0 (sd0) timed out > ahc0: target 0, lun 0 (sd0) timed out > ...[repeats]... > > SCSI bus hangs, and I'm forced to reboot system... This is probably for Justin... perhaps it's already fixed in 2.1 however. > Once, this even happened: > /: bad dir ino 2 at offset 0: mangled entry > panic: bad dir Boot the installation floppy, select "Fixit", insert the fixit floppy, and fsck /dev/rsd0a manually. This assumes the 2.1 boot/fixit floppy pair, you can also use them for 2.0.5 (except for actually running an installation). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Tue Nov 28 01:20:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA19076 for bugs-outgoing; Tue, 28 Nov 1995 01:20:13 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA18991 ; Tue, 28 Nov 1995 01:20:06 -0800 Date: Tue, 28 Nov 1995 01:20:06 -0800 Message-Id: <199511280920.BAA18991@freefall.freebsd.org> To: freebsd-bugs Cc: From: Lyndon Nerenberg (VE7TCP) Subject: Re: docs/842: hackers@freebsd.org is suffering meltdown Reply-To: Lyndon Nerenberg (VE7TCP) Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR docs/842; it has been noted by GNATS. From: Lyndon Nerenberg (VE7TCP) To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: docs/842: hackers@freebsd.org is suffering meltdown Date: Tue, 28 Nov 1995 01:14:40 -0800 The *really* *final* version of this sucker. (Jeeez I'm glad I don't actually run this stuff :-) ChangeLog: Might as well include the demo files ... .Dd November 27, 1995 .Dt IBCS2 8 .Os FreeBSD-Experimental .Sh NAME .Nm ibcs2 .Nd load iBCS2 runtime support for SCO and ISC binaries .Sh SYNOPSIS .Nm ibcs2 .Sh DESCRIPTION The .Nm utility loads kernel runtime support for iBCS2 compliant programs. This runtime support is limited to emulation of the iBCS2 system call interface, and is far from complete. COFF binaries and shared libraries are supported, however no shared libraries are provided with the FreeBSD distribution. .Sh FILES .Bl -tag -width /usr/share/examples/ibcs2/* -compact .It Pa /lkm/ibcs2_mod.o .It Pa /lkm/ibcs2_coff_mod.o .It Pa /lkm/socksys_mod.o iBCS2 loadable kernel modules. .Pp .It Pa /usr/share/examples/ibcs2/* Sample object files with which to test the emulator. .Sh "SEE ALSO" .Pa /sys/i386/ibcs2/README.iBCS2 , .Xr modload 8 , .Xr lkm 4 .Sh BUGS The emulation is very incomplete. .Pp Running dynamically linked binaries requires access to an existing SCO system from which you can grab the shared libraries. .Pp You can't really use this without reading the source code. From owner-freebsd-bugs Tue Nov 28 02:40:16 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA24376 for bugs-outgoing; Tue, 28 Nov 1995 02:40:16 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA24282 ; Tue, 28 Nov 1995 02:40:08 -0800 Resent-Date: Tue, 28 Nov 1995 02:40:08 -0800 Resent-Message-Id: <199511281040.CAA24282@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, lyndon@orodruin.orthanc.com Received: from orodruin.orthanc.com (orodruin.orthanc.com [204.244.20.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA23929 for ; Tue, 28 Nov 1995 02:34:25 -0800 Received: (from lyndon@localhost) by orodruin.orthanc.com (8.6.12/8.6.12) id CAA24061; Tue, 28 Nov 1995 02:34:23 -0800 Message-Id: <199511281034.CAA24061@orodruin.orthanc.com> Date: Tue, 28 Nov 1995 02:34:23 -0800 From: Lyndon Nerenberg Reply-To: lyndon@orodruin.orthanc.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/847: man(1) references optional pager Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 847 >Category: docs >Synopsis: man(1) references optional pager >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 28 02:40:05 PST 1995 >Last-Modified: >Originator: Lyndon Nerenberg >Organization: Orthanc Systems: Internet and UNIX consulting >Release: FreeBSD 2.1.0-951104-SNAP i386 >Environment: 2.1 >Description: man(1) has a SEE ALSO referring to less(1) which may not be installed. >How-To-Repeat: >Fix: Patch /usr/src/gnu/usr.bin/man/man/man.man (or whatever it is :-) --- 1.1 1995/11/28 10:30:06 +++ man.man 1995/11/28 10:30:15 @@ -127,7 +127,7 @@ .B %pager% is used. .SH "SEE ALSO" -apropos(1), whatis(1), manpath(1), less(1), groff(1). +apropos(1), whatis(1), manpath(1), groff(1). .SH BUGS The .B \-t >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Nov 28 02:54:48 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA25337 for bugs-outgoing; Tue, 28 Nov 1995 02:54:48 -0800 Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id CAA25295 for ; Tue, 28 Nov 1995 02:53:39 -0800 Date: Mon, 27 Nov 1995 18:26:55 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <11708@nwpeople.demon.co.uk> To: bugs@freebsd.org Cc: se@zpr.uni-koeln.de Subject: NCR815 problem X-Mailer: PCElm 1.10 Lines: 105 Sender: owner-bugs@freebsd.org Precedence: bulk I have just installed an NCR-815 PCI SCSI controller in my PC. When I boot 2.1.0-951026-SNAP (off IDE) I get the following error: pci_map_mem failed: device's memrange 0xc8000-0xc80ff is incompatible with its bridge's memrange 0x4000000-0xffffffff After this the driver still detects sd0 correctly, but I'm unable to access it in any way. Occasionally (with cache enabled) the above error is followed by: CACHE TEST FAILED: reg dstat-sstat2 readback ffffffff. CACHE INCORRECTLY CONFIGURED. Disabling the cache doesn't prevent the pci_map_mem error. What does all this mean? Do I need a new motherboard? Have I got a duff NCR815? Thanks in advance for any help. Full dmesg output follows below. iain -- Iain Baird Network People International Tel: +44 (0)1732 743591 FreeBSD 2.1.0-951026-SNAP #0: Mon Nov 27 02:28:15 GMT 1995 root@nomad:/usr/src/sys/compile/NOMAD.NCR CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 15065088 (14712K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:8e:30:a1, type SMC8416C/SMC8416BT (16 bit) 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 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: chip0 rev 4 on pci0:0 chip1 rev 3 on pci0:2 ncr0 rev 3 int a irq 15 on pci0:3 pci_map_mem failed: device's memrange 0xcc000-0xcc0ff is incompatible with its bridge's memrange 0x4000000-0xffffffff ncr0 waiting for scsi devices to settle (ncr0:0:0): "SEAGATE ST31250N 0006" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 973MB (1994037 512 byte sectors) vga0 rev 0 on pci0:4 pci0:5: vendor=0x1c1c, device=0x0001, class=old (misc) [no driver assigned] FreeBSD 2.1.0-951026-SNAP #0: Mon Nov 27 02:28:15 GMT 1995 root@nomad:/usr/src/sys/compile/NOMAD.NCR CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 15065088 (14712K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:8e:30:a1, type SMC8416C/SMC8416BT (16 bit) 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 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: chip0 rev 4 on pci0:0 chip1 rev 3 on pci0:2 ncr0 rev 3 int a irq 15 on pci0:3 pci_map_mem failed: device's memrange 0xcc000-0xcc0ff is incompatible with its bridge's memrange 0x4000000-0xffffffff CACHE TEST FAILED: reg dstat-sstat2 readback ffffffff. CACHE INCORRECTLY CONFIGURED. vga0 rev 0 on pci0:4 pci0:5: vendor=0x1c1c, device=0x0001, class=old (misc) [no driver assigned] From owner-freebsd-bugs Tue Nov 28 05:20:45 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA05169 for bugs-outgoing; Tue, 28 Nov 1995 05:20:45 -0800 Received: (from bde@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA05147 ; Tue, 28 Nov 1995 05:20:43 -0800 Date: Tue, 28 Nov 1995 05:20:43 -0800 From: Bruce Evans Message-Id: <199511281320.FAA05147@freefall.freebsd.org> To: timothyh@pipex.net, bde, freebsd-bugs Subject: Re: bin/836 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: tr doesn't interpolate ranges properly State-Changed-From-To: open-closed State-Changed-By: bde State-Changed-When: Tue Nov 28 05:20:03 PST 1995 State-Changed-Why: Fixed in rev.1.6 of tr/str.c From owner-freebsd-bugs Tue Nov 28 05:50:00 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA06521 for bugs-outgoing; Tue, 28 Nov 1995 05:50:00 -0800 Received: from sam.wal-mart.com (sam.wal-mart.com [161.173.243.62]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id FAA06515 for ; Tue, 28 Nov 1995 05:49:50 -0800 Received: by sam.wal-mart.com (1.37.109.4/16.2) id AA17541; Tue, 28 Nov 95 08:43:45 -0500 Received: from mtaie01.wal-mart.com with uucp; Tue, 28 Nov 95 07:46:04 Received: from meother.wal-mart.com by mtaie01.wal-mart.com (4.1/3.1.090690-Wal-Mart Stores) id AA07697; Tue, 28 Nov 95 07:46:04 CST Received: by meother.wal-mart.com with Microsoft Mail id <01BABD65.31410040@meother.wal-mart.com>; Tue, 28 Nov 1995 07:43:22 -0600 Message-Id: <01BABD65.31410040@meother.wal-mart.com> From: Marc Othersen To: "'bugs@freebsd.org'" Subject: Mouse problems Date: Tue, 28 Nov 1995 07:43:20 -0600 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-bugs@freebsd.org Precedence: bulk Howdy! I seem to be having a bit of trouble installing the X-Window system. = I have a Dell P75 with 5 Gigs and 64 Meg of RAM. The error I get concerns the = mouse. I use the xf86config utility and select a PS/2 mouse (mine is a Microsoft mouse with 2 buttons). The rest of the configuration runs = just fine but when I type 'startx' from the command line I get 'Mouse = not configured'. How do I configure a mouse??? Did the xf86config utility not do this? = I have the /dev/mouse device which is linking to /dev/psm0. The 'cat < = /dev/mouse' trick says the same message. Any ideas? Marc Othersen meother@wal-mart.com or marco@cs.tamu.edu From owner-freebsd-bugs Tue Nov 28 09:18:26 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA19577 for bugs-outgoing; Tue, 28 Nov 1995 09:18:26 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA19572 for ; Tue, 28 Nov 1995 09:18:22 -0800 Received: from fw.ast.com by ast.com with SMTP id AA02864 (5.67b/IDA-1.5 for ); Tue, 28 Nov 1995 09:19:48 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tKTVl-00008UC; Tue, 28 Nov 95 11:08 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tKTHh-00081GC; Tue, 28 Nov 95 10:53 WET Message-Id: Date: Tue, 28 Nov 95 10:53 WET To: bugs@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Tue Nov 28 1995, 10:53:32 CST Subject: newfs gets you fewer inodes these days. Why? Sender: owner-bugs@freebsd.org Precedence: bulk I just installed 2.1 on a system that had a secondary 2GB SCSI that had not been disklabeled and such since the 1.1.5.1 days. It ran 2.0.5 that way without incident but I thought it would be nice to get rid of all the moaning and complaining the 'slicer makes while booting. Ha! After installation, I discovered that the partitions no longer had sufficient inodes to hold the contents I needed to restore. The 1.1.5.1 filesystems were newfs'ed with default settings for inodes back in the 1.1.5.1 days, so THE DEFAULTS WERE USED. Promise. I was amazed at the time that I didn't have to tweak the values. As an example of what is happening, a 450Meg partition ended up with nearly 210K inodes on 1.1.5.1, but on 2.1.0, it got 61438, even less than what a SCO UNIX system would provide for the same size "divvy" (65520). 61438 inodes was I got even with that partition a bit bigger (now 504Meg). So, now I have to figure out how to make the partitions larger (including / and /usr which are both a bit on the small side Inode-wise) whilst still being able to take advantage of some of the installation automation. Does anybody know why the blocks-to-inodes default ratio calculation was changed because it certainly makes migrations more difficult. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Tue Nov 28 09:44:00 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA21627 for bugs-outgoing; Tue, 28 Nov 1995 09:44:00 -0800 Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA21505 for ; Tue, 28 Nov 1995 09:41:32 -0800 Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA04778 for bugs@freebsd.org; Tue, 28 Nov 1995 18:40:33 +0100 From: Luigi Rizzo Message-Id: <199511281740.SAA04778@labinfo.iet.unipi.it> Subject: minor problems with 2.1.0 install To: bugs@freebsd.org Date: Tue, 28 Nov 1995 18:40:32 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 904 Sender: owner-bugs@freebsd.org Precedence: bulk A few minor problems with the 2.1.0-release install disk. I already mentioned a few of them in the snaps. * the "probe" option is still missing from the kernel config menus * when in "visual"mode, in the kenrel config, cannot set the ioaddr on lnc0 higher than 0x2000. My PCI lnc0 is at 0xff80 ... Best part, I can set it to the right address in non-visual mode, then when I enter the visual mode and look at the card the system hangs (possibly in an endless loop to get an in-range address ?) Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-bugs Tue Nov 28 11:04:28 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA26982 for bugs-outgoing; Tue, 28 Nov 1995 11:04:28 -0800 Received: (from jkh@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA26960 ; Tue, 28 Nov 1995 11:04:21 -0800 Date: Tue, 28 Nov 1995 11:04:21 -0800 From: "Jordan K. Hubbard" Message-Id: <199511281904.LAA26960@freefall.freebsd.org> To: mi@ALDAN.star89.galstar.com, jkh, freebsd-bugs Subject: Re: docs/843 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: manpath complaints about /usr/X386/man State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Tue Nov 28 11:03:48 PST 1995 State-Changed-Why: Suggested fix applied. From owner-freebsd-bugs Tue Nov 28 11:06:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA27047 for bugs-outgoing; Tue, 28 Nov 1995 11:06:13 -0800 Received: from ccnet.ccnet.com (root@ccnet.ccnet.com [192.215.96.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA27042 for ; Tue, 28 Nov 1995 11:06:04 -0800 Received: from localhost (h98-156.ccnet.com [192.215.98.156]) by ccnet.ccnet.com (8.6.12/8.6.12) with ESMTP id LAA13213 for ; Tue, 28 Nov 1995 11:01:47 -0800 Received: by localhost (LAA16610); Tue, 28 Nov 1995 11:53:49 GMT Date: Tue, 28 Nov 1995 11:53:49 GMT From: Radha Krishnan Message-Id: <199511281153.LAA16610@localhost> To: bugs@freebsd.org Subject: Make world failure on -current Sender: owner-bugs@freebsd.org Precedence: bulk Hi, Would there have been a incorrect "Commit" of /usr/src/gnu/lib/libgmp Makefile some time?? Make world bombed in the directory above. The offending rule was before-install: install -C ........ When duly corrected to be "install -c" , make proceeds ok. Just wanted to bring it to your attention. Thanks, Radha ----- -------------------------------------------------------------------------- Radha Krishnan radha@ccnet.com An avid FreeBSD Fan !! -------------------------------------------------------------------------- ------ From owner-freebsd-bugs Tue Nov 28 11:57:25 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA29675 for bugs-outgoing; Tue, 28 Nov 1995 11:57:25 -0800 Received: from fxqjm.uafadm.alaska.edu (fxqjm.uafadm.alaska.edu [137.229.15.92]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA29667 for ; Tue, 28 Nov 1995 11:57:19 -0800 Received: (from root@localhost) by fxqjm.uafadm.alaska.edu (8.6.12/8.6.12) id KAA00890; Tue, 28 Nov 1995 10:57:59 -0900 Date: Tue, 28 Nov 1995 10:57:58 -0900 (AKST) From: Quanah Mount To: bugs@freebsd.org Subject: Umm.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk is there anyway you could set up Mosaic so that it doesn't need Motif, which you don't provide, nor can I find on the net? From owner-freebsd-bugs Tue Nov 28 12:05:44 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA00526 for bugs-outgoing; Tue, 28 Nov 1995 12:05:44 -0800 Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA00520 for ; Tue, 28 Nov 1995 12:05:41 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA17656; Tue, 28 Nov 1995 13:07:47 -0700 Date: Tue, 28 Nov 1995 13:07:47 -0700 From: Nate Williams Message-Id: <199511282007.NAA17656@rocky.sri.MT.net> To: Radha Krishnan Cc: bugs@freebsd.org Subject: Re: Make world failure on -current In-Reply-To: <199511281153.LAA16610@localhost> References: <199511281153.LAA16610@localhost> Sender: owner-bugs@freebsd.org Precedence: bulk > Would there have been a incorrect "Commit" of /usr/src/gnu/lib/libgmp > Makefile some time?? Make world bombed in the directory above. The offending > rule was > before-install: install -C ........ > > When duly corrected to be "install -c" , make proceeds ok. > > Just wanted to bring it to your attention. Thanks, the problem was that the new 'install' program wasn't installed yet which has the '-C' option on it. I added 'install' to the lib-tools target to avoid update problems from older systems. Nate From owner-freebsd-bugs Tue Nov 28 13:00:11 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA04867 for bugs-outgoing; Tue, 28 Nov 1995 13:00:11 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA04823 ; Tue, 28 Nov 1995 13:00:07 -0800 Date: Tue, 28 Nov 1995 13:00:07 -0800 Message-Id: <199511282100.NAA04823@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: kern/845: Automatic reboot says you can abort but boots anyway Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR kern/845; it has been noted by GNATS. From: J Wunsch To: hsu@clinet.fi Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/845: Automatic reboot says you can abort but boots anyway Date: Tue, 28 Nov 1995 21:16:25 +0100 (MET) As Heikki Suonsivu wrote: > > After a panic, the system says > > Automatic reboot in 15 seconds, press any key to abort > > but keypress has no effect, it reboots anyway, making it hard to > recover the panic message. > > I think this feature worked before, but I'm not sure whether it > worked after I switched into pcvt. This is a pcvt bogon. I have yet to figure out why this happens. (The code to handle this is there and "looks right", but it never worked after the transition to the cnstat() functions.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Tue Nov 28 13:17:02 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA06256 for bugs-outgoing; Tue, 28 Nov 1995 13:17:02 -0800 Received: (from joerg@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA06230 ; Tue, 28 Nov 1995 13:16:58 -0800 Date: Tue, 28 Nov 1995 13:16:58 -0800 From: Joerg Wunsch Message-Id: <199511282116.NAA06230@freefall.freebsd.org> To: lyndon@orthanc.com, joerg, freebsd-bugs Subject: Re: docs/842 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: hackers@freebsd.org is suffering meltdown State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Tue Nov 28 22:12:16 MET 1995 State-Changed-Why: Suggested man page incorporated. I've added a Copyright on behalf of Lyndon - i hope you agree. From owner-freebsd-bugs Tue Nov 28 14:19:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA10493 for bugs-outgoing; Tue, 28 Nov 1995 14:19:07 -0800 Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA10483 for ; Tue, 28 Nov 1995 14:18:48 -0800 Received: (from scrappy@localhost) by hub.org (8.7.1/8.7.1) id RAA15072; Tue, 28 Nov 1995 17:16:31 -0500 (EST) Date: Tue, 28 Nov 1995 17:16:24 -0500 (EST) From: "Marc G. Fournier" To: Frank Durda IV cc: bugs@FreeBSD.ORG Subject: Re: newfs gets you fewer inodes these days. Why? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG Precedence: bulk On Tue, 28 Nov 1995, Frank Durda IV wrote: > I just installed 2.1 on a system that had a secondary 2GB SCSI that > had not been disklabeled and such since the 1.1.5.1 days. It > ran 2.0.5 that way without incident but I thought it would be nice > to get rid of all the moaning and complaining the 'slicer makes while > booting. Ha! > > After installation, I discovered that the partitions no longer > had sufficient inodes to hold the contents I needed to restore. > > The 1.1.5.1 filesystems were newfs'ed with default settings for > inodes back in the 1.1.5.1 days, so THE DEFAULTS WERE USED. Promise. > I was amazed at the time that I didn't have to tweak the values. > > As an example of what is happening, a 450Meg partition ended up with nearly > 210K inodes on 1.1.5.1, but on 2.1.0, it got 61438, even less than what > a SCO UNIX system would provide for the same size "divvy" (65520). > 61438 inodes was I got even with that partition a bit bigger (now 504Meg). > On a 2.1R system, /dev/sd1e was added to the system after installing: System 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/wd0a 29727 19148 8200 70% 911 6767 12% / /dev/wd0e 98479 79653 10947 88% 4599 26119 15% /usr /dev/wd0g 99887 16090 75806 18% 815 25039 3% /home /dev/sd1e 297423 117577 156052 43% 17732 59066 23% /usr/src /dev/sd0f 193215 145112 38442 79% 8042 41876 16% /usr/local /dev/sd0e 98479 60948 29652 67% 3342 27376 11% /usr/local/src /dev/wd0f 65663 43154 17255 71% 57 22981 0% /usr/local/src/Installed /dev/sd1f 181503 53229 113753 32% 11677 34401 25% /home/news/spool procfs 4 4 0 100% 46 134 26% /proc Notice that the number of I-nodes created on a 300Meg partition was over 75,000 I-nodes. In fact, as far back as I can remember (2years, min), file systems under BSDi, another *BSD variant, defaulted to a 4block-to-1inode ratio. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-bugs Tue Nov 28 15:13:11 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA14949 for bugs-outgoing; Tue, 28 Nov 1995 15:13:11 -0800 Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA14937 for ; Tue, 28 Nov 1995 15:12:58 -0800 Received: (from scrappy@localhost) by hub.org (8.7.1/8.7.1) id SAA15739; Tue, 28 Nov 1995 18:11:44 -0500 (EST) Date: Tue, 28 Nov 1995 18:11:34 -0500 (EST) From: "Marc G. Fournier" To: Radha Krishnan cc: bugs@FreeBSD.ORG Subject: Re: Make world failure on -current In-Reply-To: <199511281153.LAA16610@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.ORG Precedence: bulk On Tue, 28 Nov 1995, Radha Krishnan wrote: > Hi, > Would there have been a incorrect "Commit" of /usr/src/gnu/lib/libgmp > Makefile some time?? Make world bombed in the directory above. The offending > rule was > before-install: install -C ........ > -C was something added in just recently, not sure if it was in 2.1.0R, or in one of the -current, but it is new. Check the install source you have online, you probably just have to install a new version Should be under: /usr/src/usr.bin/xinstall Marc G. Fournier | POP Mail Telnet Acct DNS Hosting scrappy@hub.org | WWW Services Database Services | Knowledge, soon to be: | | Information and scrappy@ki.net | WWW: http://hub.org | Communications, Inc From owner-freebsd-bugs Tue Nov 28 21:30:12 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12148 for bugs-outgoing; Tue, 28 Nov 1995 21:30:12 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12129 ; Tue, 28 Nov 1995 21:30:05 -0800 Resent-Date: Tue, 28 Nov 1995 21:30:05 -0800 Resent-Message-Id: <199511290530.VAA12129@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA11181 for" ; Tue, 28.Nov.1995.21:20:02.-0800 Received: from fw.ast.com by ast.com with SMTP id AA04943 (5.67b/IDA-1.5 for ); Tue, 28 Nov 1995 21:21:18 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tKeYB-00008DC; Tue, 28 Nov 95 22:55 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tKdxR-000CQlC; Tue, 28 Nov 95 22:17 WET Message-Id: Date: Tue, 28 Nov 95 22:17 WET From: uhclem%nemesis@fw.ast.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/848: Inst gripes about geometry but won't accept true values FDIV040 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 848 >Category: misc >Synopsis: Inst gripes about geometry but won't accept true values FDIV040 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 28 21:30:03 PST 1995 >Last-Modified: >Originator: Frank Durda IV >Organization: That costs extra >Release: FreeBSD 2.1-STABLE i386 >Environment: 2.1.0-RELEASE (or STABLE?) System consists of a 540Meg IDE and 2.0GB SCSI. Boots from IDE. SCSI Adapter is a Adaptec 1540B, latest firmware and microcode. BIOS boots from the IDE and has no CMOS settings for the SCSI devices. >Description: During the installation, the SCSI drive was partitioned. The partition software complains that the geometry is not correct and that it should be corrected or terrible things will happen. Using the "G" command, the correct values are entered, ie 2707 cylinders, 19 heads, 81 sectors (per manufacturers data sheet for a Seagate ST12550N). After the data is entered, the partition software again says that the geometry is not correct and the same values that were there before reappear (2039/64/32), along with messages warning of woe and disaster somewhere down the road should you not use the "G"eometry command to set the correct values. Trying again gets you the same result and the data you enter is discarded. Interestingly, the internally computed values 2039x64x32 equal 4,175,872 blocks, which is greater than 2707x19x81==4,166,073. This looks (on the surface) like a really bad thing, as we may have computed a block count greater than the true size of the media, and then later the system will attempt to write who-knows-what out there. In the case of this particular drive, the 81 sectors per track is the average rounded-down (according to the data sheet), so there is some slop and the true user sector count was 4,177,781 so even the "bogus" numbers still work. In reality, I suspect the drive returns the true block count and it is divided against the hardwired 64 and 32, yielding 2039 as the closest number that fits. It would be nice if the user could give the system the vendor recommended numbers, particularly when the software currently encourages the user to do this. On some types of drives, the user could end up with less usable space on the drive because of these hardwired values. I got lucky. >How-To-Repeat: Try to set the settings to the true dimensions of a drive where these are different than the %d/64/32 that the partition program seems to be stuck on. >Fix: Choose: 1. Fix the partition software (also disklabel utility) to accept the real values for that drive. or 2. Change the warnings to say the system is substituting these values and they are close and might give you a bit more space or might give you less, and everything will be fine, rather than implying that something bad will happen if you can't cram the real settings into the software (which apparently you can't). It would also be nice if the system explained what magical hat these various numbers (64 & 32) were being pulled from as well. If input to the "G" command can't be accepted even when it is valid, you might as well pull the command. or 3. Both 1 and 2. This step in the installation could really throw a lot of people trying to install for the first time, and it only seems to do this to people with SCSI drives, which are supposed to be the drives of choice for FreeBSD. We need to make this more friendly in a big way. *END* >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Nov 28 21:30:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12149 for bugs-outgoing; Tue, 28 Nov 1995 21:30:13 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12142 ; Tue, 28 Nov 1995 21:30:09 -0800 Resent-Date: Tue, 28 Nov 1995 21:30:09 -0800 Resent-Message-Id: <199511290530.VAA12142@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA12102 for" ; Tue, 28.Nov.1995.21:29:54.-0800 Received: from fw.ast.com by ast.com with SMTP id AA05077 (5.67b/IDA-1.5 for ); Tue, 28 Nov 1995 21:31:21 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tKeYC-00008VC; Tue, 28 Nov 95 22:55 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tKeEM-000CQ2C; Tue, 28 Nov 95 22:34 WET Message-Id: Date: Tue, 28 Nov 95 22:34 WET From: uhclem%nemesis@fw.ast.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/849: Install skimps on inodes and newfs default is wrong FDIV041 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 849 >Category: misc >Synopsis: Install skimps on inodes and newfs default is wrong FDIV041 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 28 21:30:06 PST 1995 >Last-Modified: >Originator: Frank Durda IV >Organization: Burmashave >Release: FreeBSD 2.1-STABLE i386 >Environment: FreeBSD 2.1-RELEASE (or STABLE?) >Description: During installation a 500 Meg partition was created to hold a news spool that had previously existed on the drive that was a 450 Meg. During the restore, it was found the files would not all fit (out of inodes). It appears that the installation is invoking newfs with -i 4096, which produces one inode for every 8 blocks. So on a 500Meg partition, only 61,437 inodes were created. In 1.1.5.1 (don't know about 2.0.x), the installation as it was ran newfs with NO parameters, which produced roughly 220,000 inodes. In 2.1.0, the man page for newfs says: "-i number of bytes per inode. The default is to create an inode for each 2048 bytes of data space." and that description matches the action seen in 1.1.5.1. However, in 2.1.0, newfs behaves as though the default has been changed to 4096, yielding only 122,877 inodes in the above example. Here are some tests: 1K Total Used Avail Iused Ifree Cyl groups newfs no parms 496367 1 456656 1 122877 16 newfs -i 1024 452735 1 416515 1 471037 11 * newfs -i 2048 481007 1 442525 1 245757 16 newfs -i 4096 496367 1 456656 1 122877 16 newfs -i 8192 504047 1 463722 1 61437 16 * newfs generates a warning about not getting as many cylinder groups. >How-To-Repeat: On a partition you don't care about, compare the inode count set by install vs what you get with the various settings shown above. >Fix: 1. Fix install to not pass -i 8192 or make the parameter a settable parameter on each partition. This doesn't appear to be an option now. 2. Fix newfs so that the default is 2048 so it matches previous behavior and the manpage. *END* >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Nov 28 21:40:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12964 for bugs-outgoing; Tue, 28 Nov 1995 21:40:06 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA12934 ; Tue, 28 Nov 1995 21:40:03 -0800 Resent-Date: Tue, 28 Nov 1995 21:40:03 -0800 Resent-Message-Id: <199511290540.VAA12934@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA12779 for" ; Tue, 28.Nov.1995.21:36:54.-0800 Received: from fw.ast.com by ast.com with SMTP id AA05191 (5.67b/IDA-1.5 for ); Tue, 28 Nov 1995 21:38:21 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tKezq-00008DC; Tue, 28 Nov 95 23:23 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tKevg-000CU4C; Tue, 28 Nov 95 23:19 WET Message-Id: Date: Tue, 28 Nov 95 23:19 WET From: uhclem%nemesis@fw.ast.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/850: dump treats write-protect as an EOT & spoils set FDIV042 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 850 >Category: bin >Synopsis: dump treats write-protect as an EOT & spoils set FDIV042 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 28 21:40:02 PST 1995 >Last-Modified: >Originator: Frank Durda IV >Organization: None >Release: FreeBSD 2.1-STABLE i386 >Environment: FreeBSD 2.1.0-RELEASE (or STABLE?) SCSI Viper 150 Tape Drive >Description: When doing a multi-volume level zero dump, the second tape was inserted with the write-protect pin set (aka SAFE). When dump was told the next volume was mounted and ready, the driver reported the WRITE PROTECT error to the root console, but dump simply reported "Dump: Volume 2 begins with blocks from inode 21341 Dump: End of Tape detected Dump: Change Volumes: Mount Volume #3" The operator didn't realize what happened, and inserted a third tape. (I suspect that he walked away immediately after responding to the second volume and came back later and found the system wanting the next tape.) The backup should have only required two tapes but three were "used". The dump appeared successful. Now the hard drive was reformatted and the level 0 dump was used to restore as in "restore -rvf". After reading tape Volume 1, restore asks for Volume 2, which is inserted, and restore complains that this is not the correct tape. Volume 3 is inserted and we are told that it is not Volume 2. We are now trapped. Back in the old days on the VAX-11/780, we used to forget to put the write rings in all the time on the 6250 tapes, and BSD 4.3 dump NEVER pulled this stunt. It always said that something was wrong (like the open failed) and "Do you want to retry the open?" and gave you a chance to pull the tape, write-enable it and keep going, even if it was the first or nth tape of the set. Clearly something has changed in dump or the way that the write-protect error is reported back to dump is different and that "want to retry" code isn't being run. >How-To-Repeat: Use the above procedure after making a good dump set first and hiding it away somewhere. >Fix: Absolutely! (he says with bloodshot eyes as he trys to bail the site out using older tapes and they keep saying this never happened with the Brand S system) - - - - - - - - - - - - - - Because the way this happened reminded me, I'll make my pitch again for adding two new system-wide error returns specifically to deal with issues related to removable media. (The last time I mentioned it in "arch" nobody even bothered to flame the idea, wave the NIH banner, etc.) One new error number should be used for reporting write protect errors, such as tapes or removable discs that are protected (or the media is ready-only). We can't sit back and simply reject requests in the write call in the drivers anymore with new hardware appearing, such as a SCSI drive that supports both MO media and CD-ROMs. Or CD-burners that can be written to but only in certain areas. Right now, most drivers appear to return something akin to an I/O Error, leaving the user wondering if the media is flawed, the wrong type or not formatted, or the wrong filesystem type, or perhaps write-protected? A second new error number should be used to report that the media is offline or that the drive is not ready. In other words, this error code would allow the user/application to tell that "yes, the driver is installed, and the dev being access is configured and all that stuff, but that the problem is that the tape or disc isn't loaded or up to speed at this second." In the first new error number case, we currently spray a write protect message on the console, but only root gets to see that, and we want people to not run root, so the mortal user gets little or no information on what went wrong on a write protect error. Just a flimsy I/O error or some other code even less descriptive. In the second new error number case, dividing non-existant/not-configured types errors from not-ready errors will really improve the "user-friendlyness" of the applications. The "not configured" case is not recoverable; being offline or not ready is a recoverable condition and the user should be given the chance to revover. Windows and even MS-DOS make these distinctions in their error reporting, we should too. (Geez, even TRSDOS did.) Yes, the block I/O drivers would have to be updated (I'll be happy to do them all!) to take advantage of the new error returns, but I still think we should seriously think about having them. *END* >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Nov 28 22:00:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA14139 for bugs-outgoing; Tue, 28 Nov 1995 22:00:07 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA14100 ; Tue, 28 Nov 1995 22:00:04 -0800 Resent-Date: Tue, 28 Nov 1995 22:00:04 -0800 Resent-Message-Id: <199511290600.WAA14100@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.star89.galstar.com Received: from aldan (PPP-83-3.BU.EDU [128.197.8.87]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA13740 for ; Tue, 28 Nov 1995 21:53:36 -0800 Received: (from root@localhost) by aldan (8.6.12/8.6.12) id AAA28031; Wed, 29 Nov 1995 00:52:13 -0500 Message-Id: <199511290552.AAA28031@aldan> Date: Wed, 29 Nov 1995 00:52:13 -0500 From: mi@ALDAN.star89.galstar.com Reply-To: mi@ALDAN.star89.galstar.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: ports/851: building port xspread-2.1 fails Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 851 >Category: ports >Synopsis: building port xspread-2.1 fails >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 28 22:00:02 PST 1995 >Last-Modified: >Originator: &khail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: Automatic build of port xspread fails. Patch does not apply automaticly. xmkmf fails after patch is applied manualy If go to work/xspread2.1 and do xmkmf by hands. Make works fine after that. >How-To-Repeat: su cd /usr/ports/math/xspread make patch >Fix: Do not know how to automate what I've done properly (-:. Must be somthing silly. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Nov 28 22:43:18 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA16011 for bugs-outgoing; Tue, 28 Nov 1995 22:43:18 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA16006 for ; Tue, 28 Nov 1995 22:43:15 -0800 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 HAA15274 ; Wed, 29 Nov 1995 07:41:50 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id HAA14557 ; Wed, 29 Nov 1995 07:41:50 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id AAA00429; Wed, 29 Nov 1995 00:49:52 +0100 (MET) From: Ollivier Robert Message-Id: <199511282349.AAA00429@keltia.freenix.fr> Subject: Re: Make world failure on -current To: radha@ccnet.ccnet.com (Radha Krishnan) Date: Wed, 29 Nov 1995 00:49:52 +0100 (MET) Cc: bugs@freebsd.org In-Reply-To: <199511281153.LAA16610@localhost> from "Radha Krishnan" at Nov 28, 95 11:53:49 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1378 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk It seems that Radha Krishnan said: > When duly corrected to be "install -c" , make proceeds ok. Just SUP the latest sources, recompile install and do the make world again. The install -C is correct. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #7: Mon Nov 6 21:08:06 MET 1995 From owner-freebsd-bugs Tue Nov 28 23:00:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA16605 for bugs-outgoing; Tue, 28 Nov 1995 23:00:06 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA16541 ; Tue, 28 Nov 1995 23:00:03 -0800 Date: Tue, 28 Nov 1995 23:00:03 -0800 Message-Id: <199511290700.XAA16541@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Jordan K. Hubbard" Subject: Re: misc/849: Install skimps on inodes and newfs default is wrong FDIV041 Reply-To: "Jordan K. Hubbard" Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR misc/849; it has been noted by GNATS. From: "Jordan K. Hubbard" To: uhclem%nemesis@fw.ast.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: misc/849: Install skimps on inodes and newfs default is wrong FDIV041 Date: Tue, 28 Nov 1995 22:48:35 -0800 > 1. Fix install to not pass -i 8192 or make the parameter a settable > parameter on each partition. This doesn't appear to be an > option now. But it is a settable parameter? > 2. Fix newfs so that the default is 2048 so it matches previous > behavior and the manpage. Agreed, will do. Jordan From owner-freebsd-bugs Wed Nov 29 00:00:04 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA18840 for bugs-outgoing; Wed, 29 Nov 1995 00:00:04 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA18791 ; Wed, 29 Nov 1995 00:00:02 -0800 Resent-Date: Wed, 29 Nov 1995 00:00:02 -0800 Resent-Message-Id: <199511290800.AAA18791@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.star89.galstar.com Received: from aldan (PPP-83-13.BU.EDU [128.197.8.97]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA18735 for ; Tue, 28 Nov 1995 23:58:07 -0800 Received: (from mi@localhost) by aldan (8.6.12/8.6.12) id CAA28943; Wed, 29 Nov 1995 02:55:45 -0500 Message-Id: <199511290755.CAA28943@aldan> Date: Wed, 29 Nov 1995 02:55:45 -0500 From: mi@ALDAN.star89.galstar.com Reply-To: mi@ALDAN.star89.galstar.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/852: sendmail seems to loose messages Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 852 >Category: bin >Synopsis: Sendmail is loosing mail (apparently)! >Confidential: yes >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 29 00:00:01 PST 1995 >Last-Modified: >Originator: &khail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: ppp connection. Mail goes away directly using SMTP >Description: For some reasons connection hang (first time in three days). pppd did not notice. sendmail logged: Nov 29 02:38:42 aldan sendmail[28759]: NOQUEUE: SYSERR(mi): before readcf: fd 1 not op en: Bad file descriptor Nov 29 02:38:42 aldan sendmail[28759]: NOQUEUE: SYSERR(mi): before readcf: fd 2 not op en: Bad file descriptor After connection reastablished (gracefully killed pppd and started again), mail was not sent out (at least, not logged as such), and mailq says: "... empty". >How-To-Repeat: Do not know how to hang the line without pppd noticing. Unplug the modem? >Fix: Do not know. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Nov 29 01:03:44 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA22831 for bugs-outgoing; Wed, 29 Nov 1995 01:03:44 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA22337 for ; Wed, 29 Nov 1995 00:58:09 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA10577; Wed, 29 Nov 1995 09:56:04 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA02674; Wed, 29 Nov 1995 09:56:03 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA14491; Wed, 29 Nov 1995 09:37:40 +0100 From: J Wunsch Message-Id: <199511290837.JAA14491@uriah.heep.sax.de> Subject: Re: Mouse problems To: meother@sam.wal-mart.com (Marc Othersen) Date: Wed, 29 Nov 1995 09:37:40 +0100 (MET) Cc: bugs@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <01BABD65.31410040@meother.wal-mart.com> from "Marc Othersen" at Nov 28, 95 07:43:20 am 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: 644 Sender: owner-bugs@freebsd.org Precedence: bulk As Marc Othersen wrote: > > I seem to be having a bit of trouble installing the X-Window system. = > I have > a Dell P75 with 5 Gigs and 64 Meg of RAM. The error I get concerns the = > mouse. I use the xf86config utility and select a PS/2 mouse (mine is a > Microsoft mouse with 2 buttons). PS/2 mouse is the wrong selection. Select "Microsoft" then. (PS/2 is the `keyboard mouse', i.e. it's connected via the keyboard controller, usually with a 6-pin mini-DIN connector.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Nov 29 01:29:21 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA24479 for bugs-outgoing; Wed, 29 Nov 1995 01:29:21 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA24472 for ; Wed, 29 Nov 1995 01:29:14 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA12774; Wed, 29 Nov 1995 20:28:21 +1100 Date: Wed, 29 Nov 1995 20:28:21 +1100 From: Bruce Evans Message-Id: <199511290928.UAA12774@godzilla.zeta.org.au> To: freebsd-bugs@freefall.freebsd.org, jkh@time.cdrom.com Subject: Re: misc/849: Install skimps on inodes and newfs default is wrong FDIV041 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk > > 1. Fix install to not pass -i 8192 or make the parameter a settable > > parameter on each partition. This doesn't appear to be an > > option now. > > But it is a settable parameter? Ask the author of sysinstall :-). > > 2. Fix newfs so that the default is 2048 so it matches previous > > behavior and the manpage. > > Agreed, will do. 4.4lite2 has fixed the manpage to match the new behaviour. There is something to be said for this - if your fragment size is 4096 or more then you are very unlikely to want the bytes/inode default of 2048. Bruce From owner-freebsd-bugs Wed Nov 29 07:40:08 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA24635 for bugs-outgoing; Wed, 29 Nov 1995 07:40:08 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA24550 ; Wed, 29 Nov 1995 07:40:05 -0800 Date: Wed, 29 Nov 1995 07:40:05 -0800 Message-Id: <199511291540.HAA24550@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Justin T. Gibbs" Subject: Re: misc/848: Inst gripes about geometry but won't accept true values FDIV040 Reply-To: "Justin T. Gibbs" Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR misc/848; it has been noted by GNATS. From: "Justin T. Gibbs" To: uhclem%nemesis@fw.ast.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/848: Inst gripes about geometry but won't accept true values FDIV040 Date: Wed, 29 Nov 1995 07:34:00 -0800 >2.1.0-RELEASE (or STABLE?) >System consists of a 540Meg IDE and 2.0GB SCSI. Boots from IDE. >SCSI Adapter is a Adaptec 1540B, latest firmware and microcode. >BIOS boots from the IDE and has no CMOS settings for the SCSI devices. > >>Description: > >During the installation, the SCSI drive was partitioned. >The partition software complains that the geometry is not correct >and that it should be corrected or terrible things will happen. > >Using the "G" command, the correct values are entered, ie 2707 cylinders, >19 heads, 81 sectors (per manufacturers data sheet for a Seagate ST12550N). This is not the geometry you should be entering. For any Adaptec controller in standard translation mode (<= 1 gig drive or "support DOS drives greater than 1 gig" disabled), the geometry exported by the card is 64heads, 32sec/track, #MB reported by the probe for the drive cylinders. The capacity of the drive, your controller, and your controller settings determine the correct geometry, not the real geometry of the drive. >After the data is entered, the partition software again says that the >geometry is not correct and the same values that were there before >reappear (2039/64/32), along with messages warning of woe and disaster >somewhere down the road should you not use the "G"eometry command to set >the correct values. Trying again gets you the same result and the data >you enter is discarded. I don't rememeber the order for values in that dialog, but I thought that the number of heads came first. If you use the huristic I mention above, you should get the correct geometry. >>Fix: > >Choose: > 1. Fix the partition software (also disklabel utility) to accept > the real values for that drive. You didn't supply the correct geometry. If it had accepted your values, you wouldn't be able to boot off of that drive. >or 2. Change the warnings to say the system is substituting these values > and they are close and might give you a bit more space or might > give you less, and everything will be fine, rather than implying > that something bad will happen if you can't cram the real settings > into the software (which apparently you can't). It would > also be nice if the system explained what magical hat these various > numbers (64 & 32) were being pulled from as well. > If input to the "G" command can't be accepted even when it is valid, > you might as well pull the command. I have no idea where 2.1 gets its numbers from, but the real solution is to beef up our boot sequence so we can properly save the BIOS values for all drives and use a "drive marking scheme" compatible with NT so that we can do an acurate mapping of geometry to device. >or 3. Both 1 and 2. > >This step in the installation could really throw a lot of people trying >to install for the first time, and it only seems to do this to people with >SCSI drives, which are supposed to be the drives of choice for FreeBSD. >We need to make this more friendly in a big way. Agreed. Its been a long standing problem. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Wed Nov 29 07:40:31 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA24701 for bugs-outgoing; Wed, 29 Nov 1995 07:40:31 -0800 Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA24361 for ; Wed, 29 Nov 1995 07:36:56 -0800 Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.11/8.6.9) id QAA04526 for bugs@freebsd.org; Wed, 29 Nov 1995 16:35:17 +0100 From: Thomas Gellekum Message-Id: <199511291535.QAA04526@ghpc6.ihf.rwth-aachen.de> Subject: trouble installing 2.1 To: bugs@freebsd.org Date: Wed, 29 Nov 1995 16:35:16 +0100 (MET) 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: 582 Sender: owner-bugs@freebsd.org Precedence: bulk Moin moin, I was trying to install 2.1.0 on a 386SX/16/6MB with a single IDE disk (Fujitsu M2613T). The kernel starts /stand/sysinstall, after a long while it clears the screen and then it hangs. The debug screen on ALT-F2 shows the following: wd0: wdcontrol: wdcommand failed reading fsbn 0wd0: status d0 err or 0 wd0: wdstart: wdcontrol returned nonzero, state=1 I have tried to disable any unused devices; no change. I also tried a different controller; no change. The machine is currently running 2.0.5 without a hitch. Any ideas? tg From owner-freebsd-bugs Wed Nov 29 11:23:37 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA11900 for bugs-outgoing; Wed, 29 Nov 1995 11:23:37 -0800 Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA11617 for ; Wed, 29 Nov 1995 11:17:54 -0800 Date: Wed, 29 Nov 1995 19:17:12 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <11948@nwpeople.demon.co.uk> To: se@zpr.uni-koeln.de (Stefan Esser) Cc: bugs@freebsd.org Subject: Re: NCR815 problem X-Mailer: PCElm 1.10 Lines: 175 Sender: owner-bugs@freebsd.org Precedence: bulk Thanks for you reply to my previous mail. > On Nov 27, 18:26, Iain Baird wrote: > } Subject: NCR815 problem > } I have just installed an NCR-815 PCI SCSI controller in my PC. > } When I boot 2.1.0-951026-SNAP (off IDE) I get the following error: > } > } pci_map_mem failed: device's memrange 0xc8000-0xc80ff is > } incompatible with its bridge's memrange 0x4000000-0xffffffff > } > } CACHE TEST FAILED: reg dstat-sstat2 readback ffffffff. > } CACHE INCORRECTLY CONFIGURED. > > Well, seems your system violates one of the assumptions > of the PCI code: The PCI devices are expected to be mapped > to addresses beyond the 1st Gigabyte of address space. > Your system uses much lower addresses: 0xc0000 is an > address below 1MB, i.e. in the ISA peripheral address > space. What causes this? Is it my motherboard/BIOS, or the NCR 815 card? I have been thinking about replacing the motherboard. > This ought to work, provided your system doesn't try to > cache accesses to the 640KB to 1MB address range, and > that you didn't turn on copying of BIOS ROMs into RAM at > those addresses. > > Could you please verify the BIOS setup ? I've turned caching and shadowing off. I haven't seen any cache test failures since. > } ncr0 rev 3 int a irq 15 on pci0:3 > ^^ > I'd rather avoid IRQ 15 in a system that also got IDE > drives. Haven't heard that it actually caused problems, > but I'd be afraid that IDE might want to have 14 and 15 > for its own use (and might for example install interrupt > handlers). I have experimented with this, using other IRQs makes no difference. I have only one IDE controller, it uses IRQ 14. > } pci0:5: vendor=0x1c1c, device=0x0001, class=old (misc) [no driver assigned] > ^^^^^^ > any idea, what kind of device that is ? Yes: it's a DTC PCI IDE Controller card. My motherboard has no on-board IDE controller, the system came with the DTC card. Here are some system details: Gateway 2000 4DX2-66P PhoenixBIOS 4.03 GPCI 4.03.09 Intel P&P BIOS Extensions v2.07 NCR SMDS v3.0 PCI SCSI BIOS, PCI Rev 2.0 NCR PCI04-3.06.00 > You will be able to use that 815 controller card, but it might > be necessary to build a custom kernel. Well, I got a little further, but I have been unable to get sd0 to work under FreeBSD. It works fine under DOS. I have attempted to disklabel the sd0 manually, but I think I'm tripping over the new slice support. I consulted the FAQ, it didn't help - the FAQ was clear enough, but nothing it suggested actually worked. Finally I used the installation floppy to create a FreeBSD partition on sd0. I had previously created a DOS partition so that the correct BIOS geometries would be picked up (1021/31/63). I chose "Dedicate whole disk to FreeBSD" and "Don't cooperate with other OS's". I forced a write from the partition menu. I then booted off IDE, verbose boot messages follow below. Note the last message: sd0s1: C/H/S end 1021/0/24 (24527) != end 1994036: invalid Attempts to disklabel the partition failed with the same error. I don't know whether I'm doing something wrong, or hitting a hardware problem or a bug. Something seems to be trashing the geometry. I'll be grateful for any further assistance you can give. iain -- Iain Baird Network People International Tel: +44 (0)1732 743591 The following boot messages were obtained with: External cache disabled Caching of C800-CBFF,CC00-CFFF disabled (Should this make any difference, if external cache is disabled? What about internal L1 cache?) Shadowing of C800-CBFF,CC00-CFFF disabled IRQ 15 the only IRQ left free for PCI FreeBSD 2.1.0-951026-SNAP #0: Mon Nov 27 02:28:15 GMT 1995 root@nomad:/usr/src/sys/compile/NOMAD.NCR CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 15065088 (14712K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:8e:30:a1, type SMC8416C/SMC8416BT (16 bit) 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 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface pcibus_setup(1): mode1res=0x0000000e (0x80000000), mode2res=0x0e (0x0e) pcibus_setup(2): mode1res=0x00000000 (0x80000000) pcibus_setup(3): mode1res=0x00000000 (0xff000001) pcibus_setup(4): now trying mechanism 2 pcibus_check: device 0 is there (id=04838086) Probing for devices on the PCI bus: configuration mode 2 allows 16 devices. chip0 rev 4 on pci0:0 CPU: 486DX2 or 486DX4, bus=33MHz, CPU->Memory posting ON Warning: NO DRAM parity! Cache: None DRAM: page mode code fetch, read and write, memory clocks=X-1-2-1 CPU->PCI: posting ON, burst mode ON PCI->Memory: posting ON chip1 rev 3 on pci0:2 Bus Modes: Bus Park, Bus Lock, Coprocessor errors enabled Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Configuration RAM: 0C00h,0800h-08FFh Port 92: enabled ncr0 rev 3 int a irq 15 on pci0:3 mapreg[10] type=1 addr=0000ff00 size=0100. mapreg[14] type=0 addr=000cc000 size=0100. pci_map_mem failed: device's memrange 0xcc000-0xcc0ff is incompatible with its bridge's memrange 0x4000000-0xffffffff reg20: virtual=0xf2a4f000 physical=0xcc000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl23 95/09/07) ncr0 waiting for scsi devices to settle (ncr0:0:0): "SEAGATE ST31250N 0006" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 973MB (1994037 512 byte sectors) sd0(ncr0:0:0): with 3712 cyls, 5 heads, and an average 107 sectors/track vga0 rev 0 on pci0:4 mapreg[10] type=0 addr=40000000 size=800000. pci0:5: vendor=0x1c1c, device=0x0001, class=old (misc) [no driver assigned] pci0: uses 8388608 bytes of memory from 40000000 upto 407fffff. pci0: uses 256 bytes of I/O space from ff00 upto ffff. BIOS Geometries: 0:03fe0f3f 0..1022=1023 cylinders, 0..15=16 heads, 1..63=63 sectors 1:03fc1e3f 0..1020=1021 cylinders, 0..30=31 heads, 1..63=63 sectors 0 accounted for wd0s1: type 0x6, start 63, end = 409247, size 409185 : OK wd0s2: type 0xa5, start 409248, end = 1056383, size 647136 : OK sd0s1: type 0xa5, start 0, end = 1994036, size 1994037 sd0s1: C/H/S end 1021/0/24 (24527) != end 1994036: invalid From owner-freebsd-bugs Wed Nov 29 13:55:58 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA23837 for bugs-outgoing; Wed, 29 Nov 1995 13:55:58 -0800 Received: from georgewk.slip.netcom.com (georgewk.slip.netcom.com [192.187.228.86]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA23809 for ; Wed, 29 Nov 1995 13:55:37 -0800 Received: (from coredump@localhost) by georgewk.slip.netcom.com (8.7/8.6.12) id NAA00535; Wed, 29 Nov 1995 13:48:41 -0800 (PST) Date: Wed, 29 Nov 1995 13:48:39 -0800 (PST) From: invalid opcode To: J Wunsch cc: bugs@freebsd.org Subject: Re: Mouse problems In-Reply-To: <199511290837.JAA14491@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk > > mouse. I use the xf86config utility and select a PS/2 mouse (mine is a > > Microsoft mouse with 2 buttons). > > PS/2 mouse is the wrong selection. Select "Microsoft" then. > > (PS/2 is the `keyboard mouse', i.e. it's connected via the keyboard > controller, usually with a 6-pin mini-DIN connector.) > > -- > cheers, J"org No, that is what a PS/2 mouse is, a 6pin mini-DIN connection. This person is using a Dell which come standard with ps/2 ports for the mice, by saying that he was using a 2 button Microsoft mouse, he was implying that it was just that, and a ps/2 connection. I SERIOUSLY doubt that it is serial or bus. coredump@georgewk.slip.netcom.com From owner-freebsd-bugs Wed Nov 29 16:30:04 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA06924 for bugs-outgoing; Wed, 29 Nov 1995 16:30:04 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA06886 ; Wed, 29 Nov 1995 16:30:02 -0800 Date: Wed, 29 Nov 1995 16:30:02 -0800 Message-Id: <199511300030.QAA06886@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: misc/848: Inst gripes about geometry but won't accept true values FDIV040 Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR misc/848; it has been noted by GNATS. From: J Wunsch To: uhclem%nemesis@fw.ast.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/848: Inst gripes about geometry but won't accept true values FDIV040 Date: Thu, 30 Nov 1995 01:10:24 +0100 (MET) As uhclem%nemesis@fw.ast.com wrote: > > > Interestingly, the internally computed values 2039x64x32 equal 4,175,872 > blocks, which is greater than 2707x19x81==4,166,073. This looks (on > the surface) like a really bad thing, as we may have computed a block count > greater than the true size of the media, and then later the system will > attempt to write who-knows-what out there. In the case of this particular > drive, the 81 sectors per track is the average rounded-down (according to > the data sheet), so there is some slop and the true user sector count was > 4,177,781 so even the "bogus" numbers still work. For SCSI disk, libdisk rounds the true disk size (as obtained from the disk) down to what it thinks is the closest cylinder boundary below. No harm can happen for non-bootable drives. (For FreeBSD-only disks, you can even use the entire disk capacity with the ``dangerously dedicated'' option. C/H/S is effectively ignored then.) However, i agree that the warning is bogus and confuses the users. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Nov 29 17:23:57 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA10624 for bugs-outgoing; Wed, 29 Nov 1995 17:23:57 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA10551 for ; Wed, 29 Nov 1995 17:22:50 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id CAA17644; Thu, 30 Nov 1995 02:22:21 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id CAA12296; Thu, 30 Nov 1995 02:22:21 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id BAA17405; Thu, 30 Nov 1995 01:55:37 +0100 From: J Wunsch Message-Id: <199511300055.BAA17405@uriah.heep.sax.de> Subject: Re: Umm.. To: root@fxqjm.uafadm.alaska.edu (Quanah Mount) Date: Thu, 30 Nov 1995 01:55:37 +0100 (MET) Cc: bugs@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Quanah Mount" at Nov 28, 95 10:57:58 am 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: 437 Sender: owner-bugs@FreeBSD.org Precedence: bulk As Quanah Mount wrote: > > is there anyway you could set up Mosaic so that it doesn't need Motif, > which you don't provide, nor can I find on the net? You have to buy Motif. Or find somebody who's bought it, and compiles you a Mosaic with a statically linked Motif lib. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Nov 29 17:50:53 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12316 for bugs-outgoing; Wed, 29 Nov 1995 17:50:53 -0800 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA12290 for ; Wed, 29 Nov 1995 17:50:45 -0800 Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA15056; Wed, 29 Nov 1995 20:50:06 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 29 Nov 1995 20:50 EST Received: (rivers@localhost) by ponds.UUCP (8.6.11/8.6.5) id MAA00373; Wed, 29 Nov 1995 12:31:02 -0500 Date: Wed, 29 Nov 1995 12:31:02 -0500 From: Thomas David Rivers Message-Id: <199511291731.MAA00373@ponds.UUCP> To: freebsd-bugs@freefall.FreeBSD.org, freebsd-hackers@freefall.FreeBSD.org, rivers@dg-rtp.dg.com Subject: Strangeness in /usr/include/runetype.h? Content-Type: text Content-Length: 1474 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk I've found an interesting situation, try compiling the following file with -D_POSIX_SOURCE defined: ------------ start ------------- #include #include #include ------------ end ------------- You'll get: In file included from /usr/include/ctype.h:51, from t.c:4: /usr/include/runetype.h:58: parse error before `rune_t' /usr/include/runetype.h:58: warning: no semicolon at end of struct or union /usr/include/runetype.h:59: warning: data definition has no type or storage class ... indicating 'rune_t' wasn't defined. There is a note in /usr/include/machine/ansi.h: * Note that _WCHAR_T_ and _RUNE_T_ must be of the same type. When wchar_t * and rune_t are typedef'd, _WCHAR_T_ will be undef'd, but _RUNE_T remains * defined for ctype.h. */ #define _BSD_WCHAR_T_ int /* wchar_t */ #define _BSD_RUNE_T_ int /* rune_t */ And, finally, in /usr/include/runetype.h we have: #ifdef _BSD_WCHAR_T_ typedef _BSD_WCHAR_T_ rune_t; typedef _BSD_WCHAR_T_ wchar_t; #undef _BSD_WCHAR_T_ #endif my suggestion is that this becomes: #ifdef _BSD_WCHAR_T_ typedef _BSD_WCHAR_T_ rune_t; typedef _BSD_WCHAR_T_ wchar_t; #undef _BSD_WCHAR_T_ #else typedef _BSD_RUNE_T_ rune_t; #endif I discovered this on a 2.0.5 system, but I looked on freefall.cdrom.com (which claims to be running 2.1-STABLE) and discovered this hasn't changed there. - Dave Rivers - From owner-freebsd-bugs Wed Nov 29 17:50:56 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA12322 for bugs-outgoing; Wed, 29 Nov 1995 17:50:56 -0800 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA12295 for ; Wed, 29 Nov 1995 17:50:47 -0800 Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA15118; Wed, 29 Nov 1995 20:50:11 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 29 Nov 1995 20:50 EST Received: (rivers@localhost) by ponds.UUCP (8.6.11/8.6.5) id MAA01025; Wed, 29 Nov 1995 12:58:56 -0500 Date: Wed, 29 Nov 1995 12:58:56 -0500 From: Thomas David Rivers Message-Id: <199511291758.MAA01025@ponds.UUCP> To: freebsd-bugs@freefall.FreeBSD.org, freebsd-hackers@freefall.FreeBSD.org, rivers@dg-rtp.dg.com Subject: More on runetype.h issues. Content-Type: text Content-Length: 568 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Well - My previous suggestion appears to not be correct; as I just got a error message: In file included from /usr/include/ctype.h:51, from host/unix/host.h:45, from /tmp/parser.y:34: /usr/include/runetype.h:50: redefinition of `rune_t' /usr/include/stddef.h:50: `rune_t' previously declared here shape - error during execution; retcode: 1 when I had changed /usr/include/runetype.h as I previously mentioned, and *not* compiled with _POSIX_SOURCE defined. There's obviously more thinking to be done here. - Dave Rivers - From owner-freebsd-bugs Wed Nov 29 19:42:07 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA18849 for bugs-outgoing; Wed, 29 Nov 1995 19:42:07 -0800 Received: from stephen.sysdev.com (root@stephen.sysdev.com [206.2.3.27]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA18844 for ; Wed, 29 Nov 1995 19:41:49 -0800 Received: (from jeff@localhost) by stephen.sysdev.com (8.6.12/8.6.12) id VAA09247 for bugs@FreeBSD.org; Wed, 29 Nov 1995 21:39:46 -0600 Date: Wed, 29 Nov 1995 21:39:46 -0600 From: Jeff Mohler Message-Id: <199511300339.VAA09247@stephen.sysdev.com> To: bugs@FreeBSD.org Subject: pkg_add Sender: owner-bugs@FreeBSD.org Precedence: bulk I have the release of 2.1.0 FreeBSD. Every single package that I want to install through sysinstall in a post-installation config..errors out. I had this problem on the SNAP release..and thought it was fixed. Any ideas?? Thank you..this is for my office..and we're chomping at the bit to get the rest of the OS installed. Jeff Mohler Systems Integrator From owner-freebsd-bugs Wed Nov 29 20:35:29 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA21845 for bugs-outgoing; Wed, 29 Nov 1995 20:35:29 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA21820 for ; Wed, 29 Nov 1995 20:35:03 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id UAA05343; Wed, 29 Nov 1995 20:32:54 -0800 To: Jeff Mohler cc: bugs@freebsd.org Subject: Re: pkg_add In-reply-to: Your message of "Wed, 29 Nov 1995 21:39:46 CST." <199511300339.VAA09247@stephen.sysdev.com> Date: Wed, 29 Nov 1995 20:32:54 -0800 Message-ID: <5341.817705974@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-bugs@freebsd.org Precedence: bulk Uh. More details please? Type of installation medium, etc? > I have the release of 2.1.0 FreeBSD. > > Every single package that I want to install through sysinstall in a post-inst allation config..errors out. > > I had this problem on the SNAP release..and thought it was fixed. > > Any ideas?? > > Thank you..this is for my office..and we're chomping at the bit to get the > rest of the OS installed. > > Jeff Mohler > Systems Integrator From owner-freebsd-bugs Wed Nov 29 21:26:26 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA24886 for bugs-outgoing; Wed, 29 Nov 1995 21:26:26 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA24823 ; Wed, 29 Nov 1995 21:25:57 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA28894; Thu, 30 Nov 1995 16:21:10 +1100 Date: Thu, 30 Nov 1995 16:21:10 +1100 From: Bruce Evans Message-Id: <199511300521.QAA28894@godzilla.zeta.org.au> To: freebsd-bugs@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org, ponds!rivers@dg-rtp.dg.com, rivers@dg-rtp.dg.com Subject: Re: Strangeness in /usr/include/runetype.h? Sender: owner-bugs@FreeBSD.ORG Precedence: bulk >I've found an interesting situation, try compiling the following >file with -D_POSIX_SOURCE defined: >------------ start ------------- >#include >#include >#include >------------ end ------------- >You'll get: >In file included from /usr/include/ctype.h:51, > from t.c:4: >/usr/include/runetype.h:58: parse error before `rune_t' >/usr/include/runetype.h:58: warning: no semicolon at end of struct or union >/usr/include/runetype.h:59: warning: data definition has no type or storage class >... > my suggestion is that this becomes: >#ifdef _BSD_WCHAR_T_ >typedef _BSD_WCHAR_T_ rune_t; >typedef _BSD_WCHAR_T_ wchar_t; >#undef _BSD_WCHAR_T_ >#else >typedef _BSD_RUNE_T_ rune_t; >#endif This will result in rune_t sometimes being redefined. Typedefs can't be redefined. and should have something like #ifdef _BSD_WCHAR_T_ typedef _BSD_WCHAR_T_ wchar_t; #undef _BSD_WCHAR_T_ #endif and they should not pollute the namespace by defining rune_t. should have something like #ifdef _BSD_WCHAR_T_ typedef _BSD_WCHAR_T_ wchar_t; #undef _BSD_WCHAR_T_ #endif typedef _BSD_RUNE_T_ rune_t; should not pollute the namespace by including ... Bruce From owner-freebsd-bugs Wed Nov 29 23:21:15 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA03401 for bugs-outgoing; Wed, 29 Nov 1995 23:21:15 -0800 Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA03393 for ; Wed, 29 Nov 1995 23:21:06 -0800 Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.6.12/8.6.9) with ESMTP id XAA10176; Wed, 29 Nov 1995 23:20:56 -0800 Message-Id: <199511300720.XAA10176@pain.csrv.uidaho.edu> To: Jeff Mohler cc: bugs@freebsd.org Subject: Re: pkg_add In-reply-to: Your message of "Wed, 29 Nov 1995 21:39:46 CST." <199511300339.VAA09247@stephen.sysdev.com> X-Web: <"http://www.cs.uidaho.edu:8000"> X-OS: 4.4BSD derivatives MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10171.817716052.1@pain.csrv.uidaho.edu> Date: Wed, 29 Nov 1995 23:20:53 -0800 From: Faried Nawaz Sender: owner-bugs@freebsd.org Precedence: bulk Jeff Mohler wrote... I have the release of 2.1.0 FreeBSD. Every single package that I want to install through sysinstall in a post-ins tallation config..errors out. what kind of error is it, exactly? Thank you..this is for my office..and we're chomping at the bit to get the rest of the OS installed. you could try ftp'ing the packages and using pkg_manage. From owner-freebsd-bugs Thu Nov 30 09:10:08 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA03604 for bugs-outgoing; Thu, 30 Nov 1995 09:10:08 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA03575 ; Thu, 30 Nov 1995 09:10:03 -0800 Resent-Date: Thu, 30 Nov 1995 09:10:03 -0800 Resent-Message-Id: <199511301710.JAA03575@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, daveho@infocom.com Received: from infocom.com (tye.infocom.com [199.120.185.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA03148 for ; Thu, 30 Nov 1995 09:02:53 -0800 Received: (from daveho@localhost) by infocom.com (8.6.12/8.6.12) id LAA03354; Thu, 30 Nov 1995 11:59:56 -0500 Message-Id: <199511301659.LAA03354@infocom.com> Date: Thu, 30 Nov 1995 11:59:56 -0500 From: daveho@infocom.com Reply-To: daveho@infocom.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/853: NIS server problem Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 853 >Category: bin >Synopsis: NIS map services.byname not exported to clients correctly >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 30 09:10:02 PST 1995 >Last-Modified: >Originator: David Hovemeyer >Organization: Nerd Central >Release: FreeBSD 2.1-STABLE i386 >Environment: 2.1.0-951020-SNAP 2.1.0-RELEASE (problem affects both) >Description: The FreeBSD box is being used as an NIS server. The problem is with the services.byname map: for services with both a tcp and udp version, only the udp version is visible through NIS. This causes problems for clients looking for the tcp service. >How-To-Repeat: On a client, do $ ypcat services.byname|grep telnet telnet/tcp is not shown. >Fix: The problem seems to be that the services.byname database is being created with only the service name as a key: the effect being that when the upd service is added, it overwrites the tcp service with the same name. I don't know enough about NIS to fix this myself, but it sounds like upd or tcp need to be encoded in the database key. >Audit-Trail: >Unformatted: David Hovemeyer From owner-freebsd-bugs Thu Nov 30 10:19:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA07972 for bugs-outgoing; Thu, 30 Nov 1995 10:19:10 -0800 Received: from snoopy.cogentlink.com (root@ns.cogentlink.com [206.3.51.14]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA07965 ; Thu, 30 Nov 1995 10:19:06 -0800 Received: from [206.3.51.17] ([206.3.51.17]) by snoopy.cogentlink.com (8.6.11/8.6.9) with SMTP id NAA04251; Thu, 30 Nov 1995 13:57:31 -0500 Date: Thu, 30 Nov 1995 13:57:31 -0500 X-Sender: dstraub@cogentlink.com (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freeBSD.org, bugs@freeBSD.org From: dstraub@cogentlink.com (David Straub) Subject: Install Problem Sender: owner-bugs@freeBSD.org Precedence: bulk Two possibly unrelated issues are preventing my installation from floppy disks. First, the Boot floppy disk often hangs a half-dozen times when it comes to Uncompressing kernel... It finally loads the install program using the same floppy and I've tried re-rawriting other floppies with no help. Second, I get a problem that says "panic: page fault syncing disks" which I attribute to the labels portion of install. The newfs is set up as "-b 8192 -f 2048 -u 4096" for all partitions. Does this mean my IDE hard drive is incompatible with this bytes per sector scheme? Also, I haven't seen any specs for what the configuration means. Any assistance would be greatly appreciated. ds. From owner-freebsd-bugs Thu Nov 30 11:00:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA11638 for bugs-outgoing; Thu, 30 Nov 1995 11:00:05 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA11589 ; Thu, 30 Nov 1995 11:00:02 -0800 Resent-Date: Thu, 30 Nov 1995 11:00:02 -0800 Resent-Message-Id: <199511301900.LAA11589@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, jkh@mimsy.cdrom.com Received: from mimsy.cdrom.com (mimsy.cdrom.com [192.216.223.173]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA11526 for ; Thu, 30 Nov 1995 10:59:48 -0800 Received: (from root@localhost) by mimsy.cdrom.com (8.6.11/8.6.9) id KAA01336; Thu, 30 Nov 1995 10:59:47 -0800 Message-Id: <199511301859.KAA01336@mimsy.cdrom.com> Date: Thu, 30 Nov 1995 10:59:47 -0800 From: Jordan Hubbard Reply-To: jkh@mimsy.cdrom.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/854: swapinfo shows incorrect information for vnconfig'd swap. Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 854 >Category: bin >Synopsis: swapinfo shows incorrect information for vnconfig'd swap. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 30 11:00:01 PST 1995 >Last-Modified: >Originator: Jordan Hubbard >Organization: FreeBSD Project >Release: FreeBSD 2.1-STABLE >Environment: >Description: On a system with swap space added via vnconfig, swapinfo prints an entry like this for the vn0 device: /dev/?? 65536 0 65472 0% Interleaved >How-To-Repeat: dd if=/dev/zero of=/usr/swapfile bs=4k count=16384 vnconfig /dev/vn1 /usr/swapfile swapon /dev/vn1 >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Nov 30 11:49:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA16095 for bugs-outgoing; Thu, 30 Nov 1995 11:49:10 -0800 Received: from fxqjm.uafadm.alaska.edu (fxqjm.uafac.alaska.edu [137.229.15.199]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA16087 for ; Thu, 30 Nov 1995 11:49:07 -0800 Received: (from root@localhost) by fxqjm.uafadm.alaska.edu (8.6.12/8.6.12) id KAA00589; Thu, 30 Nov 1995 10:49:46 -0900 Date: Thu, 30 Nov 1995 10:49:45 -0900 (AKST) From: Quanah Mount To: bugs@freebsd.org Subject: Mosaic.... Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="KAA00576.817760927/fxqjm.uafadm.alaska.edu" Content-ID: Sender: owner-bugs@freebsd.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --KAA00576.817760927/fxqjm.uafadm.alaska.edu Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Do you think you could put up a package for Mosaic for those of us who don't have Motif to compile it with? --KAA00576.817760927/fxqjm.uafadm.alaska.edu-- From owner-freebsd-bugs Thu Nov 30 17:10:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA10316 for bugs-outgoing; Thu, 30 Nov 1995 17:10:06 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA10282 ; Thu, 30 Nov 1995 17:10:03 -0800 Resent-Date: Thu, 30 Nov 1995 17:10:03 -0800 Resent-Message-Id: <199512010110.RAA10282@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, wagner@luthien.in-berlin.de Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA09916 for ; Thu, 30 Nov 1995 17:03:01 -0800 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from bolzen.in-berlin.de (194.94.235.1) with smtp id ; Fri, 1 Dec 95 02:02 MET Received: by bolzen.in-berlin.de (Smail3.1.29.1 #3) id m0tLJrZ-0007ScC; Fri, 1 Dec 95 02:02 GMT+0100 Received: by luthien.in-berlin.de (8.6.12/1.34) id AAA22165; Fri, 1 Dec 1995 00:00:07 +0100 Message-Id: <199511302300.AAA22165@luthien.in-berlin.de> Date: Fri, 1 Dec 1995 00:00:07 +0100 From: wagner@luthien.in-berlin.de Reply-To: wagner@luthien.in-berlin.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/855: /bin/expr broken in 2.1.0-RELEASE Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 855 >Category: bin >Synopsis: /bin/expr broken in 2.1.0-RELEASE >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 30 17:10:02 PST 1995 >Last-Modified: >Originator: Olaf Wagner >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: The ':'-operator fails for certain regular expressions (see below). Due to this failure several scripts of the cnews-distribution (eg. upact and recovact) produced an corrupted active file with one missing field. It took me some time to isolate the problem and to recover all the news data... >How-To-Repeat: [/usr/lib/news] root % expr "1111111111" : '.*\('$dots'\)$ ' 1111111111 [/usr/lib/news] root % expr "0000000000" : '.*\('$dots'\)$ ' [/usr/lib/news] root % >Fix: As I don't have any more time to have a look at the sources, I will install /bin/expr from the 2.0.5 distribution, wich worked correctly. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Nov 30 19:20:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA20518 for bugs-outgoing; Thu, 30 Nov 1995 19:20:13 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA20441 ; Thu, 30 Nov 1995 19:20:05 -0800 Resent-Date: Thu, 30 Nov 1995 19:20:05 -0800 Resent-Message-Id: <199512010320.TAA20441@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id TAA19680 for" ; Thu, 30.Nov.1995.19:12:42.-0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tLLsp-000072C; Thu, 30 Nov 95 21:11 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tLLmf-000CR4C; Thu, 30 Nov 95 21:05 WET Message-Id: Date: Thu, 30 Nov 95 21:05 WET From: uhclem%nemesis@fw.ast.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/856: Install 2.0.5 Upgrade option does too much damage FDIV043 Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 856 >Category: misc >Synopsis: Install 2.0.5 Upgrade option does too much damage FDIV043 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 30 19:20:03 PST 1995 >Last-Modified: >Originator: Frank Durda IV >Organization: None >Release: FreeBSD 2.1-STABLE i386 >Environment: A 2.0.5 RELEASE system was upgraded to 2.1.0-RELEASE using the 2.1.0-RELEASE system and the Install "Upgrade 2.0.5" option, instead of wiping the disks and starting over. >Description: I had the opportunity to try the 2.0.5 to 2.1.0 upgrade on a 2.0.5 system and find that this option should not be used by even experienced persons. Note that prior to the upgrade, I made to complete dumps of the system on different tapes, and a tar of /etc which I hid down in a partition well out of the way of any installation process. So all I lost was time, and some EMAIL that was trashed by the resulting system. Here are some of the problems encountered: 1. During the upgrade, you are asked for a location where a copy of /etc can be saved. It offered /usr/tmp/etc, but I selected /a/etc2.0.5 instead. The installation appears to run normally, then the system starts "resurrecting" files in /etc. It pops up several times listing files that it can't handle that the user must deal manually with, such as sysconfig, rc, rc.serial, kerberosIV, etc. It suggests you write the names down (I did) and fix them in a shell you are offered later. That's fine. When I got the shell, I started by doing a diff against the old file the install placed in /a/etc2.0.5 and what was in /etc now. The first several files were identical, but that didn't surprise me since this system wasn't very configured. Then I noted that files that should have been different were not, such as sysconfig. I checked the files in /a/etc/2.0.5, and several (but not all) showed modification times of just a few minutes earlier, instead of weeks earlier from the previous 2.0.5 installation. I suspect the upgrade procedure inadvertantly copies the new files over the old ones in the "safe" directory. Fortunately I had a "tar" hidden around that could be used to recover the files as they stood prior to upgrading, and then the diffs could be done. 2. Once I got through with this shell (and I was in it for nearly an hour), I didn't know what I was supposed to do next. There may have been an instruction when the shell was spawned, but it scrolled off the screen 50-odd minutes earlier.) So I did a CTRL-D, and got the message: PANIC: Not going anywhere without init! or something to that effect. The system halted and left all the filesystems were dirty. What is the correct procedure to get out of the shell and completing the upgrade installation? 3. After rebooting and cleaning, I updated the kernel configuration and attempted a kernel build. The kernel failed to compile in a couple of places due to old files from the 2.0.5 distribution that aren't in 2.1.0, but aren't deleted in the upgrade. Their presence confused make depend/make and resulted in compiler errors. Deleting the extra files and re-doing the make depend/make produced a kernel OK. Then I started a 'make world' and started running into the same type of problem in applications and libraries. I finally blew the make world off. This type of problem would only show up if you really upgraded a 2.0.5 system, and not if you simply re-ran the upgrade on a system that was already (or close to) 2.1.0. This may explain how this problem escaped detection. 4. I rum SMAIL on this system, so as soon as the above issues were ironed-out, I re-installed it from the pre-compiled binaries. (It is one of those ports distributions). Anyway, it installs its files and then moans that a version already exists on the system and the install may not be proper, suggesting you run pkg_delete. So I do this, and re-install. But the package refuses, until I delete the ".is_installed" file. Then it installs without complaint, but mail delivery no longer works. I fiddled and even re-compiled SMAIL and installed that, and mail would not be delivered. Finally, I restored all of the files from the 2.0.5 tree that had anything to do with SMAIL, and most of the problem went away. However, the system doesn't recognize itself by one of its domain names anymore, and keeps sending mail to itself, and mail to a local user is never delivered (it just sits in /var/spool/smail/input and gets examined every two minutes and put back there), so I will probably nuke the entire system and install 2.1.0 from scratch and see what happens. This is just too weird. >How-To-Repeat: See above. >Fix: Don't use the upgrade option. The user warning clearly isn't scary enough and it will cause problems no matter who you are. Even if you have SCSI drives. :-) (This was an all-SCSI system, not that it matters.) I recommend that the upgrade option be pulled from the next release unless we can determine a way to address deleting "old 2.0.5" files without deleting user-created files that may be lurking in the same directories. Also fix the update of /etc so that the "safe" files don't get altered. I don't know what to suggest about how SMAIL disintegrated after the upgrade. I know non-port versions of SMAIL work OK on 2.1.0. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Nov 30 22:30:08 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA18065 for bugs-outgoing; Thu, 30 Nov 1995 22:30:08 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA18030 ; Thu, 30 Nov 1995 22:30:05 -0800 Resent-Date: Thu, 30 Nov 1995 22:30:05 -0800 Resent-Message-Id: <199512010630.WAA18030@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@ALDAN.star89.galstar.com Received: from aldan (PPP-74-5.BU.EDU [128.197.7.121]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA17051 for ; Thu, 30 Nov 1995 22:24:46 -0800 Received: (from mi@localhost) by aldan (8.6.12/8.6.12) id BAA12694; Fri, 1 Dec 1995 01:23:30 -0500 Message-Id: <199512010623.BAA12694@aldan> Date: Fri, 1 Dec 1995 01:23:30 -0500 From: Mikhail Teterin Reply-To: mi@ALDAN.star89.galstar.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: ports/857: elm port does not compile after straightforward config Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 857 >Category: ports >Synopsis: Need ANSI_C define to not declare some functions >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Nov 30 22:30:02 PST 1995 >Last-Modified: >Originator: &khail Teterin >Organization: >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: lding for elm-2.4m8a cd lib; /usr/bin/make - all gcc -fpcc-struct-return -traditional -O2 -fno-strength-reduce -m486 -I../hdrs -c add_site.c In file included from ../hdrs/headers.h:93, from add_site.c:27: ../hdrs/defs.h:670: conflicting types for `lseek' /usr/include/sys/types.h:84: previous declaration of `lseek' *** Error code 1 >How-To-Repeat: su cd /usr/ports/mail/elm make configure do not add -DANSI_C when asked for additional CC options >Fix: Add -DANSI_C into the list of default extra options (in config.sh?) With it, non needed declarations will be removed by C-preprocessor. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Dec 1 00:25:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA10019 for bugs-outgoing; Fri, 1 Dec 1995 00:25:10 -0800 Received: (from joerg@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA09991 ; Fri, 1 Dec 1995 00:25:07 -0800 Date: Fri, 1 Dec 1995 00:25:07 -0800 From: Joerg Wunsch Message-Id: <199512010825.AAA09991@freefall.freebsd.org> To: wagner@luthien.in-berlin.de, joerg, freebsd-bugs Subject: Re: bin/855 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: /bin/expr broken in 2.1.0-RELEASE State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Fri Dec 1 09:22:19 MET 1995 State-Changed-Why: This has already been fixed in rev 1.11 of expr.y by the time of submission. From owner-freebsd-bugs Fri Dec 1 00:40:11 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA15077 for bugs-outgoing; Fri, 1 Dec 1995 00:40:11 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA15038 ; Fri, 1 Dec 1995 00:40:08 -0800 Date: Fri, 1 Dec 1995 00:40:08 -0800 Message-Id: <199512010840.AAA15038@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/855: /bin/expr broken in 2.1.0-RELEASE Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR bin/855; it has been noted by GNATS. From: J Wunsch To: wagner@luthien.in-berlin.de Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/855: /bin/expr broken in 2.1.0-RELEASE Date: Fri, 1 Dec 1995 08:52:55 +0100 (MET) As wagner@luthien.in-berlin.de wrote: > > The ':'-operator fails for certain regular expressions (see below). For all those where the first operand was a valid number. > As I don't have any more time to have a look at the sources, I will > install /bin/expr from the 2.0.5 distribution, wich worked correctly. It was broken in other respects. (It compared all numbers as strings.) The fix is already in -current; i'll send it to you in a separate reply (without the list). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Dec 1 00:50:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA18141 for bugs-outgoing; Fri, 1 Dec 1995 00:50:13 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA18114 ; Fri, 1 Dec 1995 00:50:07 -0800 Resent-Date: Fri, 1 Dec 1995 00:50:07 -0800 Resent-Message-Id: <199512010850.AAA18114@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, cgull@smoke.marlboro.vt.us Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA16883 for ; Fri, 1 Dec 1995 00:45:49 -0800 Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.6.*cough-wheeze*/8.6.9) id DAA04115; Fri, 1 Dec 1995 03:44:48 -0500 Message-Id: <199512010844.DAA04115@smoke.marlboro.vt.us> Date: Fri, 1 Dec 1995 03:44:48 -0500 From: john hood Reply-To: cgull@smoke.marlboro.vt.us To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/858: sh dumps core on uninitialized memory in editline Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 858 >Category: bin >Synopsis: sh dumps core on uninitialized memory in editline >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 1 00:50:03 PST 1995 >Last-Modified: >Originator: john hood >Organization: >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: standard binary distribution of freebsd 2.0.5. bug also verified with freebsd 2.1 boot and fixit floppies. >Description: editline will dereference an uninitialized pointer under certain circumstances. the memory pointer in question only gets stomped by certain malloc/free usage patterns, though, so this is apparently not a common problem. >How-To-Repeat: ------------------------------8<------------------------------ #!/bin/sh DIR=/tmp cd $DIR cat > .profile <<\Bonk #!/bin/sh set -x # 57 slashes ok, 58 kills something ////////////////////////////////////////////////////////// set -o ignoreeof set -o emacs # sh core dumps on this command echo "Made it!" Bonk ln -s /bin/sh ./-sh HOME=$DIR PATH=.:$PATH -sh ------------------------------8<------------------------------ >Fix: *** /usr/src/lib/libedit/term.c Tue May 30 01:43:15 1995 --- term.c Wed Nov 29 17:03:20 1995 *************** *** 310,315 **** --- 310,316 ---- el->el_term.t_buf = (char *) el_malloc(TC_BUFSIZE); el->el_term.t_cap = (char *) el_malloc(TC_BUFSIZE); el->el_term.t_fkey = (fkey_t *) el_malloc(4 * sizeof(fkey_t)); + (void) memset(el->el_term.t_fkey, 0, 4 * sizeof(fkey_t)); el->el_term.t_loc = 0; el->el_term.t_str = (char **) el_malloc(T_str * sizeof(char*)); (void) memset(el->el_term.t_str, 0, T_str * sizeof(char*)); >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Dec 1 01:20:09 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA25070 for bugs-outgoing; Fri, 1 Dec 1995 01:20:09 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA25019 ; Fri, 1 Dec 1995 01:20:04 -0800 Resent-Date: Fri, 1 Dec 1995 01:20:04 -0800 Resent-Message-Id: <199512010920.BAA25019@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, cgull@smoke.marlboro.vt.us Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA22949 for ; Fri, 1 Dec 1995 01:11:22 -0800 Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.6.*cough-wheeze*/8.6.9) id EAA04330; Fri, 1 Dec 1995 04:10:12 -0500 Message-Id: <199512010910.EAA04330@smoke.marlboro.vt.us> Date: Fri, 1 Dec 1995 04:10:12 -0500 From: john hood Reply-To: cgull@smoke.marlboro.vt.us To: FreeBSD-gnats-submit@freebsd.org Cc: netbsd-bugs@netbsd.org, flla@stud.uni-sb.de X-Send-Pr-Version: 3.2 Subject: bin/859: longstanding ash -c bug [FreeBSD report] Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 859 >Category: bin >Synopsis: /bin/sh -c does not ignore SIGINT >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 1 01:20:03 PST 1995 >Last-Modified: >Originator: john hood >Organization: none >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: any variant of the Almquist shell I've ever tested, including netbsd 0.9, netbsd 1.0-current-sparc of about six months ago, freebsd 1.1.5.1, freebsd 2.1.5, the antique Linux port of the Almquist shell, and the way ancient comp.sources.unix distribution by Almquist himself (yes, i've been extremely lame about this bug) >Description: 'sh -c command' does not ignore/handle SIGINT while waiting for command to complete. >How-To-Repeat: keyboard SIGINT in emacs or vi while posting in trn, or try this interactive ditty and see if the subshell keeps on running: ------------------------------8<------------------------------ #!/bin/sh # # test sig handling in sh -c # # create second script TF=/tmp/test.$$ cat > $TF <<\/EOF #!/bin/sh echo -e "shell c flags: $-" trap trap : 2 3 echo "Type ^C and ^\\" for i in a b c d e do sleep 1 echo shell c: $i done /EOF chmod a+x $TF if [ $# != 1 ] then echo "$0 shell-to-test" exit 1 fi SHELL=$1 echo -e "shell a flags: $-" trap trap : 2 3 $SHELL -c "echo shell b flags: $-; trap; $TF" echo 'shell a exit: ' $? rm $TF ------------------------------8<------------------------------ >Fix: none >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Dec 1 03:08:19 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA13971 for bugs-outgoing; Fri, 1 Dec 1995 03:08:19 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA13938 ; Fri, 1 Dec 1995 03:08:13 -0800 Date: Fri, 1 Dec 1995 03:08:13 -0800 From: Poul-Henning Kamp Message-Id: <199512011108.DAA13938@freefall.freebsd.org> To: rgrimes@gndrsh.aac.dev.com, phk, freebsd-bugs Subject: Re: bin/410 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: bad144(8) should probably scan the bad block remap sectors State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:07:18 PST 1995 State-Changed-Why: I commit the change, hoping that somebody will notice if it breaks anything before 2.2 hits the road. From owner-freebsd-bugs Fri Dec 1 03:09:14 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14110 for bugs-outgoing; Fri, 1 Dec 1995 03:09:14 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14086 ; Fri, 1 Dec 1995 03:09:08 -0800 Date: Fri, 1 Dec 1995 03:09:08 -0800 From: Poul-Henning Kamp Message-Id: <199512011109.DAA14086@freefall.freebsd.org> To: rgrimes@gndrsh.aac.dev.com, phk, freebsd-bugs Subject: Re: kern/411 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: bad144 allow you to add blocks in the remap area State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:08:28 PST 1995 State-Changed-Why: Commit this one too, hoping that we don't break anything. From owner-freebsd-bugs Fri Dec 1 03:14:15 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14594 for bugs-outgoing; Fri, 1 Dec 1995 03:14:15 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14569 ; Fri, 1 Dec 1995 03:14:10 -0800 Date: Fri, 1 Dec 1995 03:14:10 -0800 From: Poul-Henning Kamp Message-Id: <199512011114.DAA14569@freefall.freebsd.org> To: muir@idiom.com, phk, freebsd-bugs Subject: Re: misc/220 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: Cancel still doesn't work during install State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:13:16 PST 1995 State-Changed-Why: Much water has run under sysinstall since, and the problem is addressed better but not perfect in newer version. From owner-freebsd-bugs Fri Dec 1 03:15:17 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14759 for bugs-outgoing; Fri, 1 Dec 1995 03:15:17 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14732 ; Fri, 1 Dec 1995 03:15:14 -0800 Date: Fri, 1 Dec 1995 03:15:14 -0800 From: Poul-Henning Kamp Message-Id: <199512011115.DAA14732@freefall.freebsd.org> To: muir@idiom.com, phk, freebsd-bugs Subject: Re: misc/221 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: lots of error messages during unpacking via ftp install State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:14:41 PST 1995 State-Changed-Why: sysinstall has improved a lot since. Try 2.1.0 :-) From owner-freebsd-bugs Fri Dec 1 03:16:50 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA15016 for bugs-outgoing; Fri, 1 Dec 1995 03:16:50 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14990 ; Fri, 1 Dec 1995 03:16:43 -0800 Date: Fri, 1 Dec 1995 03:16:43 -0800 From: Poul-Henning Kamp Message-Id: <199512011116.DAA14990@freefall.freebsd.org> To: joerg_wunsch@uriah.heep.sax.de, phk, freebsd-bugs Subject: Re: gnu/231 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: send-pr initializes Organization with ~/.signature State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:16:04 PST 1995 State-Changed-Why: Nobody has any better idea, so it may not be right, but it is the best we can do. From owner-freebsd-bugs Fri Dec 1 03:20:22 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA15354 for bugs-outgoing; Fri, 1 Dec 1995 03:20:22 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA15332 ; Fri, 1 Dec 1995 03:20:18 -0800 Date: Fri, 1 Dec 1995 03:20:18 -0800 From: Poul-Henning Kamp Message-Id: <199512011120.DAA15332@freefall.freebsd.org> To: pst@Shockwave.COM, phk, freebsd-bugs Subject: Re: kern/248 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: scbus attach/probe information is inconsistent State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:18:12 PST 1995 State-Changed-Why: We don't do that anymore. From owner-freebsd-bugs Fri Dec 1 03:28:28 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA16344 for bugs-outgoing; Fri, 1 Dec 1995 03:28:28 -0800 Received: (from phk@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA16126 ; Fri, 1 Dec 1995 03:27:03 -0800 Date: Fri, 1 Dec 1995 03:27:03 -0800 From: Poul-Henning Kamp Message-Id: <199512011127.DAA16126@freefall.freebsd.org> To: jc@irbs.com, phk, freebsd-bugs Subject: Re: kern/707 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: Too few printf args State-Changed-From-To: open-closed State-Changed-By: phk State-Changed-When: Fri Dec 1 03:26:34 PST 1995 State-Changed-Why: This code has changed substantially, patch doesn't apply anymore. From owner-freebsd-bugs Fri Dec 1 04:20:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA19573 for bugs-outgoing; Fri, 1 Dec 1995 04:20:10 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA19492 ; Fri, 1 Dec 1995 04:20:05 -0800 Date: Fri, 1 Dec 1995 04:20:05 -0800 Message-Id: <199512011220.EAA19492@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: bin/854: swapinfo shows incorrect information for vnconfig'd swap. Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The following reply was made to PR bin/854; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@freebsd.org, jkh@mimsy.cdrom.com Cc: Subject: Re: bin/854: swapinfo shows incorrect information for vnconfig'd swap. Date: Fri, 1 Dec 1995 23:06:21 +1100 >On a system with swap space added via vnconfig, swapinfo prints an >entry like this for the vn0 device: >/dev/?? 65536 0 65472 0% Interleaved >>How-To-Repeat: > dd if=/dev/zero of=/usr/swapfile bs=4k count=16384 > vnconfig /dev/vn1 /usr/swapfile ^0 > swapon /dev/vn1 ^0 This is probably because you don't have /dev/vn0b and/or because you didn't specify swapping on the `b' partition. Unless slicing is enabled, the slice _and_ partition bits in the minor number are ignored, so /dev/vn0 is a bogus alias for /dev/vn0b and swapping on /dev/vn0 may work for bogus reasons. If slicing is enabled, then vnsize() is broken - it returns the full size, not the partition size. Bruce From owner-freebsd-bugs Fri Dec 1 13:31:20 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA25858 for bugs-outgoing; Fri, 1 Dec 1995 13:31:20 -0800 Received: from mv.mv.com (lopez@mv.MV.COM [192.80.84.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA25850 for ; Fri, 1 Dec 1995 13:31:17 -0800 Received: (lopez@localhost) by mv.mv.com (8.7.1/mem-940616) id QAA25902 for bugs@freebsd.org; Fri, 1 Dec 1995 16:31:15 -0500 (EST) Date: Fri, 1 Dec 1995 16:31:15 -0500 (EST) From: Lawrence Lopez Message-Id: <199512012131.QAA25902@mv.mv.com> To: bugs@freebsd.org Subject: yellow pages bugs Sender: owner-bugs@freebsd.org Precedence: bulk Fri Dec 1 16:22:11 EST 1995 off of gatekeeper.dec.com: yp_mkdb Reliability issue. FreeBSD 2.0.5 from walnut creek and current mirror at ftp://gatekeeper.dec.com //pub/BSD/FreeBSD/FreeBSD-current /src/gnu/usr.sbin/yp_mkdb/yp_mkdb.c /usr/src/gnu/usr.sbin/yp_mkdb/yp_mkdb.c It looks like it is attempting to create a new data base file in a temporary file. It then removes the old file and rename the temporary file. In fact it does no such thing! In fact it actually loads the new information on top of the old file. It is not clear whether active users of a data base file care (this depends on how good 'hash' of db is.) The code: sprintf(filename, "%s~.db", DbName); if ((dp = dbopen(DbName,O_RDWR|O_EXCL|O_CREAT, PERM_SECURE, DB_HASH, &openinfo)) == NULL) { perror("dbopen"); fprintf(stderr, "%s: Cannot open\n", filename); exit(1); } should have 'DbName' replaced with filename. I think '%s~.db' should be '%s~' The code: sprintf(filename, "%s.db", DbName); sprintf(filename2, "%s~.db", DbName); unlink(filename); rename(filename2, filename); should have the '.db' removed. all return codes should be checked. In fact both the unlink and rename fail. From owner-freebsd-bugs Fri Dec 1 14:13:43 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA28654 for bugs-outgoing; Fri, 1 Dec 1995 14:13:43 -0800 Received: from mv.mv.com (lopez@mv.MV.COM [192.80.84.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA28628 for ; Fri, 1 Dec 1995 14:13:33 -0800 Received: (lopez@localhost) by mv.mv.com (8.7.1/mem-940616) id RAA04139 for bugs@freebsd.org; Fri, 1 Dec 1995 17:13:19 -0500 (EST) Date: Fri, 1 Dec 1995 17:13:19 -0500 (EST) From: Lawrence Lopez Message-Id: <199512012213.RAA04139@mv.mv.com> To: bugs@freebsd.org Subject: Seconds Yellow Pages Bug Sender: owner-bugs@freebsd.org Precedence: bulk Fri Dec 1 16:22:11 EST 1995 off of gatekeeper.dec.com: yp_passwd Garbage passed to yppasswdd As a result of not terminating a string garbage is being passwd to yppasswdd. FreeBSD 2.0.5 from walnut creek and ftp://gatekeeper.dec.com /pub/BSD/FreeBSD/FreeBSD-current /src/usr.bin/passwd/local_passwd.c I have shown the correction for the later version. In: char * getnewpasswd(pw, nis) struct passwd *pw; int nis; The code: #ifdef NEWSALT salt[0] = _PASSWORD_EFMT1; to64(&salt[1], (long)(29 * 25), 4); to64(&salt[5], random(), 4); #else /* Make a good size salt for algoritms that can use it. */ to64(&salt[0], random(), 3); gettimeofday(&tv,0); to64(&salt[3], tv.tv_usec, 3); to64(&salt[6], tv.tv_sec, 2); salt[8] = '\0'; #endif Appears at the end. It needs the following: salt[9] = '\0'; After: to64(&salt[5], random(), 4); Thank you! Larry Lopez. If a better submission method exists or a straight update then tell me. From owner-freebsd-bugs Fri Dec 1 15:49:53 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA05569 for bugs-outgoing; Fri, 1 Dec 1995 15:49:53 -0800 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id PAA05554 for ; Fri, 1 Dec 1995 15:49:45 -0800 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15047(5)>; Fri, 1 Dec 1995 15:49:06 PST Received: by crevenia.parc.xerox.com id <177478>; Fri, 1 Dec 1995 15:48:54 -0800 From: Bill Fenner To: bugs@freebsd.org Subject: Floppy drive stays on when booting /kernel -c? Message-Id: <95Dec1.154854pst.177478@crevenia.parc.xerox.com> Date: Fri, 1 Dec 1995 15:48:50 PST Sender: owner-bugs@freebsd.org Precedence: bulk I am booting from the 2.1.0-RELEASE boot.flp, as I finally decided to upgrade my 2.0.5 box. My ethernet cards are configured at non-standard addresses (well, I don't think the "standard" addresses are one of the options on the SMC Elite Ultra, but that's beside the point). So I had to boot with /kernel -c, but then got distracted and didn't even watch it finish loading. I just looked over at the PC, and the floppy drive light is on (although the drive isn't still spinning). The kernel is sitting there at the config> prompt, and I can do all I need to, but it's pretty disconcerting to see the drive light still on... Bill From owner-freebsd-bugs Fri Dec 1 18:17:14 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA12807 for bugs-outgoing; Fri, 1 Dec 1995 18:17:14 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA12801 for ; Fri, 1 Dec 1995 18:17:10 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id SAA05881; Fri, 1 Dec 1995 18:16:44 -0800 To: Bill Fenner cc: bugs@freebsd.org Subject: Re: Floppy drive stays on when booting /kernel -c? In-reply-to: Your message of "Fri, 01 Dec 1995 15:48:50 PST." <95Dec1.154854pst.177478@crevenia.parc.xerox.com> Date: Fri, 01 Dec 1995 18:16:43 -0800 Message-ID: <5878.817870603@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-bugs@freebsd.org Precedence: bulk Not a bug. > I am booting from the 2.1.0-RELEASE boot.flp, as I finally decided to upgrade > my 2.0.5 box. My ethernet cards are configured at non-standard addresses > (well, I don't think the "standard" addresses are one of the options on > the SMC Elite Ultra, but that's beside the point). So I had to boot with > /kernel -c, but then got distracted and didn't even watch it finish loading. > > I just looked over at the PC, and the floppy drive light is on (although > the drive isn't still spinning). The kernel is sitting there at the config> > prompt, and I can do all I need to, but it's pretty disconcerting to see > the drive light still on... > > Bill From owner-freebsd-bugs Fri Dec 1 18:38:26 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA13587 for bugs-outgoing; Fri, 1 Dec 1995 18:38:26 -0800 Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA13580 for ; Fri, 1 Dec 1995 18:38:14 -0800 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id EAA07829 for ; Sat, 2 Dec 1995 04:38:05 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id EAA18682; Sat, 2 Dec 1995 04:38:13 +0200 Date: Sat, 2 Dec 1995 04:38:13 +0200 Message-Id: <199512020238.EAA18682@katiska.clinet.fi> From: Heikki Suonsivu To: freebsd-bugs@freefall.FreeBSD.org Subject: Obsolete pty code patch committed (for devfs)? Reply-To: Heikki Suonsivu Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@FreeBSD.ORG Precedence: bulk The below just committed in current doesn't seem right: diff -cr /usr/previous/current/src/sys/kern/tty_pty.c /usr/current/src/sys/kern/tty_pty.c *** /usr/previous/current/src/sys/kern/tty_pty.c Sat Nov 4 18:40:47 1995 --- /usr/current/src/sys/kern/tty_pty.c Wed Nov 29 18:34:18 1995 ... *************** *** 733,735 **** --- 737,797 ---- } return (error); } + + #define CDEV_MAJOR_S 5 + #define CDEV_MAJOR_C 6 + #ifdef JREMOD + struct cdevsw pts_cdevsw = + { ptsopen, ptsclose, ptsread, ptswrite, /*5*/ + ptyioctl, ptsstop, nullreset, ptydevtotty,/* ttyp */ + ttselect, nommap, NULL }; + + struct cdevsw ptc_cdevsw = + { ptcopen, ptcclose, ptcread, ptcwrite, /*6*/ + ptyioctl, nullstop, nullreset, ptydevtotty,/* ptyp */ + ptcselect, nommap, NULL }; + + static ptc_devsw_installed = 0; + + static void ptc_drvinit(void *unused) + { + #ifdef DEVFS + int i + char jnames[] = "pqrstu" + char knames[] = "0123456789abcdef" This is wrong; its pqrsPQRS and 0123456789abcdefghijklmnopqrstuv. + char devname[16]; 32? + #define MAXUNITS (6 * 16) 256 + #endif + dev_t dev; + dev_t dev_c; + + if( ! ptc_devsw_installed ) { + dev = makedev(CDEV_MAJOR_S,0); + cdevsw_add(&dev,&pts_cdevsw,NULL); + dev_c = makedev(CDEV_MAJOR_C,0); + cdevsw_add(&dev_c,&ptc_cdevsw,NULL); + ptc_devsw_installed = 1; + #ifdef DEVFS + /*XXX*/ + #if NPTY > MAXUNITS + #undef NPTY + #define NPTY MAXUNITS + #endif + for ( i = 0 ; i; Fri, 1 Dec 1995 22:41:40 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA29708; Sat, 2 Dec 1995 17:37:05 +1100 Date: Sat, 2 Dec 1995 17:37:05 +1100 From: Bruce Evans Message-Id: <199512020637.RAA29708@godzilla.zeta.org.au> To: bugs@FreeBSD.ORG, fenner@parc.xerox.com Subject: Re: Floppy drive stays on when booting /kernel -c? Sender: owner-bugs@FreeBSD.ORG Precedence: bulk >I am booting from the 2.1.0-RELEASE boot.flp, as I finally decided to upgrade >my 2.0.5 box. My ethernet cards are configured at non-standard addresses >(well, I don't think the "standard" addresses are one of the options on >the SMC Elite Ultra, but that's beside the point). So I had to boot with >/kernel -c, but then got distracted and didn't even watch it finish loading. >I just looked over at the PC, and the floppy drive light is on (although >the drive isn't still spinning). The kernel is sitting there at the config> >prompt, and I can do all I need to, but it's pretty disconcerting to see >the drive light still on... Did you boot from a floppy? There are several bugs involving not turning the floppy motor off at the right time: * after booting from a floppy, the bootstrap doesn't turn the motor off; it is normally turned off when the floppy device is probed. The probe may be delayed for a long time if you boot with -c. The probe will not be called if a floppy device isn't configured/enabled. * after panics and perhaps even after normal shutdowns, the timeouts may be masked and/or the delays may not be long enough for the motor to be turned off. Bruce From owner-freebsd-bugs Fri Dec 1 22:45:56 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA26699 for bugs-outgoing; Fri, 1 Dec 1995 22:45:56 -0800 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id WAA26686 for ; Fri, 1 Dec 1995 22:45:50 -0800 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15324(8)>; Fri, 1 Dec 1995 22:45:14 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177478>; Fri, 1 Dec 1995 22:45:09 -0800 To: "Jordan K. Hubbard" cc: bugs@freebsd.org Subject: Re: Floppy drive stays on when booting /kernel -c? In-reply-to: Your message of "Fri, 01 Dec 95 18:16:43 PST." <5878.817870603@time.cdrom.com> Date: Fri, 1 Dec 1995 22:45:07 PST From: Bill Fenner Message-Id: <95Dec1.224509pst.177478@crevenia.parc.xerox.com> Sender: owner-bugs@freebsd.org Precedence: bulk >Not a bug. Merci beaucoup, Monsieur Foucault. From owner-freebsd-bugs Sat Dec 2 01:46:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA09352 for bugs-outgoing; Sat, 2 Dec 1995 01:46:06 -0800 Received: (from peter@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA09333 ; Sat, 2 Dec 1995 01:45:55 -0800 Date: Sat, 2 Dec 1995 01:45:55 -0800 From: Peter Wemm Message-Id: <199512020945.BAA09333@freefall.freebsd.org> To: cgull@smoke.marlboro.vt.us, peter, freebsd-bugs Subject: Re: bin/858 Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Synopsis: sh dumps core on uninitialized memory in editline State-Changed-From-To: open-closed State-Changed-By: peter State-Changed-When: Sat Dec 2 01:44:36 PST 1995 State-Changed-Why: Suggested fix applied in rev 1.7 of libedit/term.c From owner-freebsd-bugs Sat Dec 2 03:50:21 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA07213 for bugs-outgoing; Sat, 2 Dec 1995 03:50:21 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA07195 ; Sat, 2 Dec 1995 03:50:11 -0800 Resent-Date: Sat, 2 Dec 1995 03:50:11 -0800 Resent-Message-Id: <199512021150.DAA07195@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA06497 for" ; Sat, 2.Dec.1995.03:40:57.-0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id DAA00768; Sat, 2 Dec 1995 03:40:50 -0800 Message-Id: <199512021140.DAA00768@silvia.HIP.Berkeley.EDU> Date: Sat, 2 Dec 1995 03:40:50 -0800 From: asami@cs.berkeley.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/860: visual mode in kernel -c too restrictive Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 860 >Category: kern >Synopsis: visual mode in kernel -c is too restrictive >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 2 03:50:06 PST 1995 >Last-Modified: >Originator: Satoshi Asami >Organization: University of California >Release: FreeBSD 2.1-RELEASE i386 >Environment: 2.1R, GENERIC kernel >Description: I tried to change the port address of my lance ethernet (AMD on-board PCI) to 0xffe0, but the "vi" mode didn't let me do that. The non-visual mode doesn't complain about it, and the machine works fine with that address, so the port should be valid. >How-To-Repeat: Go to the lnc0 line (for example) in userconfig, and try to change the port number to something beyond the ISA I/O range. >Fix: Remove whatever sanity check Jordan put in? :) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Dec 2 04:30:42 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA10815 for bugs-outgoing; Sat, 2 Dec 1995 04:30:42 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA10795 for freebsd-bugs; Sat, 2 Dec 1995 04:30:39 -0800 Date: Sat, 2 Dec 1995 04:30:39 -0800 From: GNU GNATS Message-Id: <199512021230.EAA10795@freefall.freebsd.org> To: freebsd-bugs Subject: List of open Problem Reports Sender: owner-bugs@FreeBSD.ORG Precedence: bulk This is the list of currently open problem reports [1994/11/14] bin/17 "mount -t foo /dev/wd1h /mnt" gives incorrect error [1994/11/18] conf/22 Cannot use links to share kernel objects [1994/11/23] kern/27 Loopback mounts confuse unmount-on-reboot code [1994/11/30] kern/34 nullfs and union mounts can result in wild pointer r [1994/12/06] kern/42 PC-NFS on -current can't access disks [1994/12/07] kern/44 ep driver won't work with anything but bnc [1994/12/13] misc/48 /etc/rc does not recover recovery files [1994/12/14] kern/51 Panic accessing NFS mounted file system [1994/12/18] misc/67 It took 20 tries to get free-bsd installed [1994/12/18] misc/68 bininst leaves system kinda hung [1994/12/20] conf/76 fdisk can't be trusted. [1994/12/21] i386/79 Reboots sometimes don't complete. [1994/12/23] misc/83 System crash after abrupt end of slip session [1995/01/03] kern/95 Configuring a SLIP device with source = destination [1995/01/10] bin/104 pax -rwl may corrupt filesystem [1995/01/14] bin/115 systat iostat display doesn't scale high enough [1995/01/14] bin/116 disk transfer rates reported by systat :iostat are t [1995/01/14] misc/118 use of 386bsd partition tag makes multi-os boot hard [1995/01/14] misc/120 first Initial security report is bogus becuase of ls [1995/01/14] bin/124 traceroute doesn't support -g flag. [1995/01/14] docs/127 locate man page does not have any clues to how the d [1995/01/14] bin/129 fsck cannot take a mount point as an argument [1995/01/14] docs/131 there is no man page for uucpd [1995/01/14] docs/132 gettytab documentation is split between /etc/gettyta [1995/01/14] bin/133 mail program doesn't have editheaders option [1995/01/15] bin/146 version of compress is kinda old and slow [1995/01/19] bin/151 One of the pkg_add set /tmp mod to 755 [1995/01/20] bin/153 mount -u improvement for diskless systems [1995/01/21] kern/157 Quota system does not work [1995/01/21] docs/164 no ptrace(2) manual page. [1995/01/21] docs/165 No documentation on kernel boot flags. [1995/01/21] misc/166 /usr/include/machine/asmacros.h includes uninstalled [1995/01/21] kern/169 Errors from mkdir & mv when directories paths end wi [1995/01/21] bin/170 ar does not print an error message with readonly lib [1995/01/21] bin/172 cp -f does not work [1995/01/21] bin/173 rc trys to mount modload fs before ld is available. [1995/01/21] bin/174 Poor error message from stty [1995/01/22] kern/176 EIDRM not defined in errno.h [1995/01/24] gnu/183 can't resolve "operator <<" overload [1995/01/24] bin/184 send-pr says "Aborting ..." and happily removes the [1995/01/25] kern/185 kernel stability problems - can't sustain uptimes > [1995/01/25] bin/188 disklabel uses c partition by default, kernel says d [1995/01/30] gnu/196 size of bss in *.o's reported wrong by size [1995/01/30] bin/198 1.1.5.1 pine binary loops; top shows fancy values [1995/02/01] bin/199 quiz(6) reading database bug, pattern matching bug [1995/02/01] misc/202 System hang or reboot without clues, tcp ppp named r [1995/02/14] kern/214 Using wt driver crashes system [1995/02/14] kern/216 /kernel: panic: ffs_alloccg: map corrupted [1995/02/14] docs/218 dbm references from hash(3) [1995/02/16] kern/219 Performance on local net drops too much when SNDBUF [1995/02/16] i386/222 boot prompt doesn't always work [1995/03/02] misc/229 acos() core dump [1995/03/03] bin/230 C++ contructors not being called [1995/03/05] docs/232 The mandoc .St macro doesn't work or misses IEEE754 [1995/03/11] kern/238 failed assertion in ncr.c --> no more scsi disk acce [1995/03/13] bin/241 strange behavior of /bin/sh [1995/03/17] kern/247 Berkeley Packet Filter fix [1995/03/19] gnu/256 nasty gdb bug back in 031595 system [1995/03/20] docs/263 There is absolutely no documentation for the dialog [1995/03/21] kern/266 ifconfig panics kernel built without option NFS [1995/03/28] kern/275 qic-02 streamer won't work [1995/03/28] kern/277 netstat -r reports entries with negative expire time [1995/03/28] kern/281 Messages printed when checking CD ROM device too ver [1995/03/28] kern/282 buslogic adapter information WAY too verbose [1995/03/29] kern/284 Network gives permission denied [1995/03/30] kern/287 Several header files are not consistent [1995/03/31] kern/288 panic: free: multiple frees [1995/04/01] kern/291 PCI devices still probe/attach after being disabled [1995/04/04] kern/299 SCSI probes stop at ID 7 even for WIDE busses [1995/04/05] bin/300 __fdnlist fails on kernels created by cc -g and stri [1995/04/06] conf/301 Log rotation wastes _much_ to much space [1995/04/06] kern/302 Changing st tapes after extract crashes system [1995/04/09] docs/317 Install README doesn't list matcd as install choice [1995/04/09] bin/323 Creating lost+found causes fsck to stop fsck -y FDIV [1995/04/09] bin/326 Weekly cron generates some usage and error messages [1995/04/09] bin/327 Clock management punishes you if CMOS != GMT FDIV020 [1995/04/09] bin/329 FTP transfers above 99K shown in scientific notation [1995/04/11] kern/336 make world fails on NCR-SCSI machine [1995/04/14] docs/341 vnconfig(8) disagrees with its man page [1995/04/14] kern/343 tcpdump with filter fails on tun and lo devices [1995/04/14] misc/344 Signal 11 when running a user program [1995/04/15] kern/345 panic "biodone: page busy < 0" [1995/04/17] kern/349 Panic with bad dir [1995/04/20] kern/353 xcdplayer crashes machine (with NCR810 SCSI) [1995/04/20] kern/354 Can't configure two IP aliases with the same network [1995/04/20] misc/355 policy on /usr/local permission in base release [1995/04/20] bin/357 pkg_delete aborts when subcommand fails [1995/04/26] kern/366 queue changes broke ISO tpip code [1995/04/26] kern/367 kernel hangs after ep0 attach message appears [1995/04/26] i386/369 AHA-154X-A problems [1995/05/01] gnu/373 In response to admittedly bogus code, gcc emits an o [1995/05/01] kern/374 panic: bad dir [1995/05/02] kern/376 tcpdump seems to cause spontaneous reboots [1995/05/03] kern/378 (apparently) bounce buffer code gets used on 32bit b [1995/05/05] kern/383 dd to from /dev/mem panics the machine. [1995/05/06] kern/384 ep0 conflicts with some other drivers [1995/05/06] kern/385 ep0 finds card on irq 10 when it's actually on 11 [1995/05/07] kern/387 scsistrategy doesn't use bounce buffers [1995/05/08] bin/389 Simultaneous creation/deletion of dirs corrupts file [1995/05/11] i386/394 IP multicast not supported by ep driver [1995/05/12] bin/398 VI doesnt do the correct thing [1995/05/13] bin/401 Add REMOTE_* variables [1995/05/13] bin/402 w -n shows non-numeric addresses [1995/05/13] misc/403 FreeBSD 1-compiled tcsh, bash and zsh binaries dump [1995/05/14] kern/405 The gpio driver does not work with the AT-GPIB, only [1995/05/14] kern/416 page fault in syscons.c:scopen() [1995/05/14] bin/419 pkg_delete refuses to delete an incompletely added p [1995/05/15] misc/423 Sound devices are too insecure [1995/05/16] kern/425 arp entries not getting removed when interface chang [1995/05/16] kern/427 eg doesn't work with more than one card [1995/05/16] kern/428 configure is not foolproof [1995/05/19] misc/431 Processes sometime's hang and wont die when they hav [1995/05/21] bin/432 mixer should print out the current mixer settings by [1995/05/22] kern/434 umapfs panics when mounting ufs over itself [1995/05/23] kern/435 mb_map full, network starts jumping off and on, fina [1995/05/23] misc/437 addition for /usr/src/usr.bin/file/Magdir/zyxel [1995/05/23] i386/440 want vidcontrol option to apply settings to all sysc [1995/05/24] gnu/442 when invoked from "make' cc not including name lists [1995/05/25] kern/443 65 sendmails crashes system [1995/05/26] i386/444 GUS sound driver does not seem to work. [1995/05/26] kern/446 unable to diskless-boot a PC when the server mounts [1995/05/27] gnu/450 tar --exclude -c doesn't work [1995/05/28] gnu/451 cvsinit/cvs doesn't work as expected with perl [1995/05/28] kern/452 vnode swapping panics [1995/05/29] bin/457 We may have an obscure csh bug [1995/05/30] docs/458 px doc does not find include figure [1995/05/30] kern/459 Systems freezes w/ 2842 [1995/05/31] bin/464 dialog_gauge goes one char too far for 100% value [1995/05/31] kern/466 Unexpected disk errors during installation/newfs [1995/06/01] misc/469 ctm leaves temp files after errors [1995/06/01] kern/471 System can not access SCSI DAT tape. [1995/06/02] bin/476 kvm_openfiles called w/ too small error buffer [1995/06/02] bin/477 telnet autologin ain't working [1995/06/03] docs/480 We don't have an rhosts.5 man page [1995/06/04] bin/486 ls includes utmp.h but doesn't use it [1995/06/05] kern/492 sysinstall shows "success" after "no space" failure. [1995/06/07] bin/499 pkg_manage percent done is broken/dependancies arent [1995/06/07] bin/500 pkg_manage fails to continue without return sometime [1995/06/12] bin/506 "Release" id generated by send-pr looks incorrect. [1995/06/14] bin/514 Crash recovery impossible without static mt/chflags. [1995/06/14] gnu/515 Info command has no tutorial [1995/06/15] bin/517 Bad group change with 'install' [1995/06/15] bin/519 execution of quotacheck from /etc/rc fails [1995/06/15] docs/520 instructions are not clear as to what the url should [1995/06/15] docs/521 catgets() man page error [1995/06/17] kern/527 dump causes assertion in ncr.c [1995/06/17] kern/528 slow 386 reports excessive interrupt-level buffer ov [1995/06/17] conf/529 Please put mountd's '-n' flag into /etc/sysconfig [1995/06/18] misc/530 Failed install from SCSI tape [1995/06/18] kern/532 buslogic bt 445S hangups wit FreeBSD 2.0.5 [1995/06/20] docs/536 No copyrights in usr/src/lib/libc/stdtime [1995/06/20] bin/537 FSCK Fails [1995/06/22] kern/540 ed0 is loosing packets on input [1995/06/22] i386/541 Alternate Reset method by unmapping ALSO broken [1995/06/23] bin/557 ar utility exausts all available file descriptors [1995/06/26] kern/565 [1995/06/27] bin/569 Slattach behaviour inconsistant [1995/07/02] kern/579 sio: RS_IBUFSIZE at 256 bytes serial lines loose dat [1995/07/02] bin/580 xntpd doesn't work with Tobit DCF77 receiver. [1995/07/02] bin/581 iijppp may hang indefinitely [1995/07/02] misc/583 rlogin over PPP does not handle input [1995/07/03] kern/586 Timeouts on SCSI Adaptec 2940 [1995/07/04] kern/587 if_le hangs on OACTIVE with 2k buffer [1995/07/04] kern/588 Configuration of DEC ethernet cards not possible [1995/07/04] conf/589 /etc/rc should eval amd ${amdflags} [1995/07/05] kern/590 pager input errors on NCR SCSI 486 mainboard [1995/07/05] bin/591 SPAP request REJexted in stead of NAKed [1995/07/05] bin/594 "mkdir -p some/path/" fails to create last path comp [1995/07/06] i386/596 and conflict with _POSIX_SOURCE [1995/07/07] bin/599 pkg_add does not stop if dependencies are missing [1995/07/08] i386/602 disklabel : changes to cylinder details not saved [1995/07/09] misc/605 [1995/07/13] kern/611 WIDE-dhcp doesn't work with FreeBSD-2.0 bpf [1995/07/14] kern/614 SCSI tape timeout for forward space file is too shor [1995/07/19] bin/624 pkg_manage doesn't show directory symlinks [1995/07/19] kern/625 keyboard lockups during boot and forever after [1995/07/20] kern/627 vidcontrol causes crash when booted with sc0 disable [1995/07/20] kern/629 user mode ppp dies when sending [1995/07/21] i386/631 if_ix does not support bpf, nor does it appear to su [1995/07/24] docs/633 no manpage for ndbm [1995/07/26] bin/635 makefile for sbin/route doesn't make keywords.h when [1995/07/27] kern/637 If used heavily, ahc will crash, with disk timeouts [1995/07/29] kern/638 Transmitted packets not passed to bpf in if_le.c [1995/08/01] docs/646 vmstat man page out of date [1995/08/01] kern/647 Sound cards fail to work [1995/08/01] bin/648 Formatted output is not converted correctly [1995/08/02] gnu/650 Current flex is outdated [1995/08/03] kern/652 Multiple addresses on one interface interacts badly [1995/08/04] kern/653 ftp or kernel - multiple transfers when sendport dis [1995/08/05] gnu/655 ld -r of shared objects worked in 1.1.5, not in 2.0. [1995/08/07] bin/658 ifconfig alias has to be separately given [1995/08/07] bin/660 /bin/sh has problem with redirection. [1995/08/07] bin/661 Hercules is not capable of having a ISO-Latin1 Scree [1995/08/08] docs/663 newfs man page refers to format(8) [1995/08/08] bin/664 pkg_add(1) man page doesn't reference pkg_manage(1) [1995/08/08] ports/665 pkg_manage can't handle installing dvips [1995/08/08] gnu/666 The ldconfig program in SNAP wasn't good [1995/08/11] gnu/672 Nor all ph headers get created [1995/08/11] ports/673 /bin/sh + inn1.4 innwatch going belly up [1995/08/11] kern/674 quad speed cdrom not being found [1995/08/11] bin/675 make does unnecessary rebuilds [1995/08/12] bin/676 mv -i [1995/08/12] kern/677 X gets a bus error when calling mmap() [1995/08/13] kern/679 chown(2) ignores set-user-id and set-group-id bits f [1995/08/13] bin/680 2.0.5's tip using termios doesn't act the way it did [1995/08/13] docs/681 bad description of Adaptec 2842 in LINT [1995/08/14] bin/683 cron(8) [1995/08/14] docs/686 SIGSYS documented badly [1995/08/14] kern/688 Page fault: supervisor write, page not present [1995/08/15] ports/690 X11 install targets unfriendly [1995/08/15] kern/691 Performance 10 times slower 2.0.5R & Adaptec AHA-284 [1995/08/15] i386/692 My modem is not found if my external cache is disabl [1995/08/16] bin/693 `pkg_add' is umask-sensitive [1995/08/16] bin/694 No include file in rpcgen output [1995/08/16] kern/695 cat B > C ; cmp B C can fail! [1995/08/17] misc/697 "make -DCLOBBER" is broken [1995/08/18] kern/700 The comments in /sys/net/in.h are confusing [1995/08/21] kern/703 ppp not always deleting route properly when a ppp li [1995/08/22] bin/706 increased root DNS traffic and long latencies for r- [1995/08/27] ports/710 mpeg_play outdated [1995/08/29] bin/711 /etc/magic not installed [1995/08/29] bin/715 ls gives weird tabular form [1995/08/31] bin/716 W returns wrong results at login [1995/09/01] misc/717 ft.c attach fail on my Mountain tape drive [1995/09/02] bin/718 pkg_add incorrectly prints an error message [1995/09/15] bin/722 Off-by-one error in wbkgd() in ncurses [1995/09/19] bin/728 /bin/sh messes up quoting when going through eval [1995/09/20] kern/729 unexpected signal 4/10/11 [1995/09/20] kern/730 3Com 3C5x9 probe problem [1995/09/21] docs/731 socketpair(2) and man page inconsistent about return [1995/09/22] bin/732 getpwent() dumps core if NIS password file is malfor [1995/09/23] docs/735 missing description for mount options in fstab(5) ma [1995/09/25] gnu/737 FreeBSD-current/src/gnu/usr.bin/gzip/Makefile [1995/09/26] kern/738 Using ktrace will cause a system reboot [1995/09/26] bin/739 Some problems when an output filter reads all input [1995/09/26] docs/740 man loadfont says /usr/share/misc/vgafonts instead o [1995/09/26] docs/741 netstat -rn not showing all routes in Kernel - not i [1995/09/26] kern/742 syslog errors accessing Mac hard disks [patch] [1995/09/27] bin/743 vi cannot edit a file where the name starts with + [1995/09/27] kern/745 occasional filesystem inconsistencies, and "panic: f [1995/09/27] bin/746 `talk' forbids talking from write-protected terminal [1995/09/27] bin/747 date(1) gives weird time zones and interprets GMT[+- [1995/09/27] docs/748 zic.8 man page refers to /usr/local/etc/zoneinfo [1995/09/27] kern/750 cd9660 confused by not-ready or I/O errors FDIV030 [1995/09/28] bin/751 crontab(1): `crontab -e' exits on SIGINT [1995/09/28] kern/752 setting multiple addresses for a single interfaces l [1995/09/28] kern/753 my archive scsi tape drive does not work [1995/09/28] docs/754 there is no man page for the psm(4) mouse driver [1995/09/29] docs/755 man page joy(4) has incorrect ioctl() arguments [1995/10/01] kern/757 Removal of mounted CD-ROM causes reboot & single use [1995/10/01] bin/759 nfsd without arg's doesn't work [1995/10/02] kern/761 route add may cause panic when used incorrectly [1995/10/03] kern/765 umount -f can`t umount a NFS filesystem in use [1995/10/04] bin/766 file doesn't grok HTML; /etc/magic in wrong place [1995/10/05] misc/767 Configure-time does time-warp on non-UTC CMOS - FDIV [1995/10/06] bin/769 xntpd does not detach from controlling terminal [1995/10/06] kern/770 Floppy kernel won't boot with T485 or IDT L2 cache F [1995/10/08] kern/772 page fault while in kernel mode (two cases) [1995/10/09] kern/774 dump fails with "slave couldn't reopen disk: Device [1995/10/10] kern/775 changing root device was wrong when exist IDE drive [1995/10/11] bin/777 patch doesn't realize stdin is closed and asks quest [1995/10/12] bin/778 tar complains "EOF not on block boundary" on a good [1995/10/12] bin/779 #include gets undefined 'rune_t' type. [1995/10/14] kern/781 OPEN_MAX in kernel config and FD_SETSIZE in /usr/inc [1995/10/18] bin/786 Problem with NIS and large group maps [1995/10/23] bin/789 pkg_add doesn't work [1995/10/25] kern/792 cd9660 very slow. [1995/10/25] kern/793 ep0 cannot be configured and more. [1995/10/26] kern/794 swap partition at offset 0 still broken [1995/10/27] misc/796 Network install doesn't update /etc/hosts FDIV036 [1995/10/27] bin/797 X probeonly during install gets Not Found error FDIV [1995/10/29] kern/798 PPP panics, touches 0xdeadc0de pointers [1995/10/29] misc/799 sysinstall segfaults if part of distribution missing [1995/10/29] docs/801 rlogind k, v, and x options are not documented [1995/10/30] misc/802 default fstab mounts disks in bad order [1995/10/31] bin/803 bsd m4 chokes and dies while FSF m4 works... [1995/10/31] kern/805 SMC Ultra 8216 incorrectly probed (if_ed driver) [1995/10/31] kern/806 kernel default parameters need tuning [1995/11/01] bin/809 `.' gives the minimum number of (DIGITS+SIGN) [1995/11/09] ports/814 unable to compile the port of "pine3.91" [1995/11/11] bin/815 mountd reports unknown hosts with non-informative me [1995/11/11] bin/817 Wrong route to remote network [1995/11/12] kern/820 scsi tape problems [1995/11/13] kern/821 Config doesn't properly trap signals [1995/11/15] kern/824 system hangs after a few hours without saying why [1995/11/16] bin/826 tcpmux listener in inetd does not work [1995/11/16] kern/827 System hangs when doing a "route add" command [1995/11/20] ports/829 the lynx patches don't patch things correctly [1995/11/20] kern/830 installing hang [1995/11/20] kern/831 one minor complaint about the kernel visual config c [1995/11/21] i386/832 Tape drive busy errors - dump aborts [1995/11/21] i386/833 SCSI hard disks time out during tape rewind - FDIV03 [1995/11/22] kern/834 the console keyboard locks up randonly under pcvt [1995/11/22] kern/835 ed panics with SMC ultra with iomem, if no iomem in [1995/11/24] bin/837 test -h evaluates to false on symlink to nonexistant [1995/11/24] misc/838 /usr/src/lib Makefile assumes you want to install... [1995/11/25] bin/839 by default, use of "at" is overly restricted [1995/11/27] kern/840 Kernel page directory invalid [1995/11/27] bin/841 stale nfs mounts cannot be umounted [1995/11/27] kern/844 mbuf panic, dump available [1995/11/27] kern/845 Automatic reboot says you can abort but boots anyway [1995/11/27] conf/846 2.1R install disk tries to use sd0 even if not reque [1995/11/28] docs/847 man(1) references optional pager [1995/11/28] misc/848 Inst gripes about geometry but won't accept true val [1995/11/28] misc/849 Install skimps on inodes and newfs default is wrong [1995/11/28] bin/850 dump treats write-protect as an EOT & spoils set FDI [1995/11/28] ports/851 building port xspread-2.1 fails [1995/11/29] bin/852 Sendmail is loosing mail (apparently)! [1995/11/30] bin/853 NIS map services.byname not exported to clients corr [1995/11/30] bin/854 swapinfo shows incorrect information for vnconfig'd [1995/11/30] misc/856 Install 2.0.5 Upgrade option does too much damage FD [1995/11/30] ports/857 Need ANSI_C define to not declare some functions [1995/12/01] bin/859 /bin/sh -c does not ignore SIGINT [1995/12/02] kern/860 visual mode in kernel -c is too restrictive This is the list of problem reports already analyzed: [1994/12/01] kern/35 mount -t union -o -b : lower layer not seen by shell [1995/01/11] i386/105 Distributed libm (msun) has non-standard error handl [1995/01/22] docs/177 man pages missing for SYSV IPC funtions [1995/02/14] kern/215 SNAP-950112 crashed with "panic: page fault" [1995/03/20] kern/260 msync and munmap don't bother to update mod times [1995/03/20] docs/264 There are no manual pages for the forms library. [1995/03/22] kern/267 NFS code gives error messages, systems jams for a fe [1995/05/09] bin/392 Simultaneous cp and ls of files on dos f/s hangs pro [1995/06/01] ports/467 utils/kp wrong distfile place after make fetch [1995/06/21] docs/538 MAP_FILE not mentioned in mmap man page. [1995/08/11] bin/671 No quot available. [1995/10/07] bin/771 telnet character mode not set and broken when set - [1995/10/15] kern/782 chmod does a null pointer dereference /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat Dec 2 04:30:43 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA10816 for bugs-outgoing; Sat, 2 Dec 1995 04:30:43 -0800 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA10800 for freebsd-bugs; Sat, 2 Dec 1995 04:30:39 -0800 Date: Sat, 2 Dec 1995 04:30:39 -0800 From: GNU GNATS Message-Id: <199512021230.EAA10800@freefall.freebsd.org> To: freebsd-bugs Subject: Summary of Problem Reports Sender: owner-bugs@FreeBSD.ORG Precedence: bulk Number of currently open reports: 314 Number of curently analyzed reports: 13 From owner-freebsd-bugs Sat Dec 2 10:26:11 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA23000 for bugs-outgoing; Sat, 2 Dec 1995 10:26:11 -0800 Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA22991 for ; Sat, 2 Dec 1995 10:26:07 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0tLwF7-0000zcC; Sat, 2 Dec 95 12:00 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0tLwDO-000C0aC; Sat, 2 Dec 95 11:59 WET Message-Id: Date: Sat, 2 Dec 95 11:59 WET To: bugs@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sat Dec 2 1995, 11:59:09 CST Subject: Mission Impossible-style crashes on 2.1.0 Sender: owner-bugs@freebsd.org Precedence: bulk I have several systems (6) that I recently upgraded to 2.1.0-RELEASE. These systems all ran 2.0.5 previously, and had no crashes in at least the previous 90 days (very nice). However, in the seven days since upgrading to 2.1.0, the same hardware has experienced an average of 10 unexpected reboots, or just over one a day. The systems with more load (news vs no news) crash more often. Usually these crashes happen when I am not around, so all I find is login: prompts and no clues to the cause. /var/log/messages simply shows that the system was running its normal stuff and then it was booting. Finally it happened in front of me on one of the systems. The system was reasonably idle (tind was active and I was in vi writing and no X), when the console keyboard went dead. All the keyboard lights turned off (NUM LOCK is normally on) and disk activity stopped. I tried changing screens and hitting a few keys like NUM LOCK, but no action. I then unplugged and reconnected the keyboard. That didn't help either. Then around 15 seconds after the system went dead, the screen cleared and the system rebooted. This has happened twice when I was at the console, and the above actions were taken during one of those two events. All residual clues suggest that this is the same failure that occurs when I am away. (All systems are protected by UPS power, so this isn't a power thing and they are in locations over a 30-mile area.) Since there is no visible panic and nothing in the logs, I am looking for suggestions on how to investigate this problem. I don't think a triple-fault is occurring, because the system reset would occur instantly. The odd thing is the 15-second delay is consistent, like it is deliberate. (I wonder if a panic is occurring and not being displayed for some reason and the 15-second timer for press a key to avoid a reboot is running.) (On one system the system froze as above, but stayed there until I reset it manually several hours later. Again, all keyboard lights were off and the logs had nothing useful. Since this only happened once on one machine, I'll treat this as a different issue for now.) On two of the systems where I can't put up with this number of crashes, the 2.0.5 kernel is now being run. After two days, those systems no longer crash. These systems are a mix of 486DX/SX-33/25/100 and Pentium 75/90, all with SCSI, some with IDE+SCSI, no-CD-ROMs at the moment, between 8 and 16Meg of RAM. All have WD/SMC Ether cards (usually 8013EW) and the drivers are active. Anyway, if anyone has seen something like this, or has suggestions on how to get more useful information from the system when this happens, I would appreciate it. (I do have access to port 80 and port 300 debuggers if that will help.) I really don't want to have to run the 2.0.5 kernel on 2.1.0 systems. Thanks! Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Sat Dec 2 20:23:27 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA17295 for bugs-outgoing; Sat, 2 Dec 1995 20:23:27 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA17252 for ; Sat, 2 Dec 1995 20:22:55 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA07904; Sun, 3 Dec 1995 15:17:33 +1100 Date: Sun, 3 Dec 1995 15:17:33 +1100 From: Bruce Evans Message-Id: <199512030417.PAA07904@godzilla.zeta.org.au> To: bugs@freebsd.org, uhclem%nemesis@fw.ast.com Subject: Re: Mission Impossible-style crashes on 2.1.0 Sender: owner-bugs@freebsd.org Precedence: bulk >Finally it happened in front of me on one of the systems. The system was >reasonably idle (tind was active and I was in vi writing and no X), when >the console keyboard went dead. All the keyboard lights turned off >(NUM LOCK is normally on) and disk activity stopped. I tried changing >screens and hitting a few keys like NUM LOCK, but no action. I then >unplugged and reconnected the keyboard. That didn't help either. >Then around 15 seconds after the system went dead, the screen cleared and >the system rebooted. This seems to be a normal panic except there is no console output (PANIC_REBOOT_WAIT_TIME) is 15 seconds). >Since there is no visible panic and nothing in the logs, I am >looking for suggestions on how to investigate this problem. I don't >think a triple-fault is occurring, because the system reset would occur >instantly. The odd thing is the 15-second delay is consistent, Try using a serial console (connect a 9600 bps terminal to sio0 and boot with -h). Bruce