From owner-freebsd-bugs Sun Jun 18 00:21:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA04737 for bugs-outgoing; Sun, 18 Jun 1995 00:21:24 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA04723 ; Sun, 18 Jun 1995 00:21:23 -0700 Date: Sun, 18 Jun 1995 00:21:23 -0700 From: David Greenman Message-Id: <199506180721.AAA04723@freefall.cdrom.com> To: alan@Epilogue.Com, davidg, freebsd-bugs Subject: Changed information for PR docs/511 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: bpf(4) is gone State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Sun Jun 18 00:20:08 PDT 1995 State-Changed-Why: This was fixed shortly after the 2.0 release. From owner-freebsd-bugs Sun Jun 18 00:50:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA05308 for bugs-outgoing; Sun, 18 Jun 1995 00:50:16 -0700 Received: from leibniz.math.psu.edu (root@leibniz.math.psu.edu [146.186.130.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA05302 for ; Sun, 18 Jun 1995 00:50:15 -0700 Received: from napier.math.psu.edu (wilcox@napier.math.psu.edu [146.186.132.4]) by leibniz.math.psu.edu (8.6.10/8.6.9) with ESMTP id DAA28188 for ; Sun, 18 Jun 1995 03:49:50 -0400 Received: from localhost (wilcox@localhost) by napier.math.psu.edu (8.6.10/8.6.9) with ESMTP id DAA00647 for ; Sun, 18 Jun 1995 03:49:40 -0400 Message-Id: <199506180749.DAA00647@napier.math.psu.edu> X-Mailer: exmh version 1.5.3 12/28/94 To: freebsd-bugs@freebsd.org Subject: More on NIS problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 18 Jun 1995 03:49:39 -0400 From: Ken Wilcox Sender: bugs-owner@freebsd.org Precedence: bulk I've seen a lot of nis problems running around. Here is my input. I have a FreeBSD 2.0.5R machine being the master server for what is going to be a ton of freebsd machines. I have this for my netgroup file staffhost1 (machine.xxx.yyy.zzz,-,) (machine2.xxx.yyy.zzz,-,) staffhost2 (machine3.xxx.yyy.zzz,-,) (machine4.xxx.yyy.zzz,-,) staffhosts staffhost1 staffhost2 Then when I do ypmatch staffhosts netgroup I get staffhost1 staffhost2 staffhosts staffhost1 staffhost2 If I try to expand this in any fashion, it gets real ugly real quick. Any reason this is doing this? -Ken Wilcox From owner-freebsd-bugs Sun Jun 18 02:34:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA08447 for bugs-outgoing; Sun, 18 Jun 1995 02:34:32 -0700 Received: from escape.com (dima@escape.com [198.6.71.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA08441 for ; Sun, 18 Jun 1995 02:34:30 -0700 Received: (dima@localhost) by escape.com (8.6.10/8.6.5) id FAA05352; Sun, 18 Jun 1995 05:29:43 -0400 Date: Sun, 18 Jun 1995 05:29:42 -0400 (EDT) From: "Dima (ELO)" To: bugs@FreeBSD.org Subject: problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi, I am having a problem. I cannot copy files from mounted dos partition to unix partition. Every time I try to do it, I get system panic. My system: P5-90, 16M RAM,adaptec 2940w, 1GB scsi fujitsu Thank you, Dima From owner-freebsd-bugs Sun Jun 18 05:37:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA11578 for bugs-outgoing; Sun, 18 Jun 1995 05:37:44 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA11571 for ; Sun, 18 Jun 1995 05:37:42 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA21585; Sun, 18 Jun 1995 14:37:40 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA10669; Sun, 18 Jun 1995 14:37:39 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id OAA17862; Sun, 18 Jun 1995 14:18:34 +0200 From: J Wunsch Message-Id: <199506181218.OAA17862@uriah.heep.sax.de> Subject: Re: problem To: dima@escape.com (Dima) Date: Sun, 18 Jun 1995 14:18:34 +0200 (MET DST) Cc: bugs@FreeBSD.org In-Reply-To: from "Dima" at Jun 18, 95 05:29:42 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 351 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Dima wrote: > > > Hi, I am having a problem. > I cannot copy files from mounted dos partition to unix partition. > Every time I try to do it, I get system panic. What about telling us something more? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Jun 18 09:26:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA18239 for bugs-outgoing; Sun, 18 Jun 1995 09:26:07 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA18233 ; Sun, 18 Jun 1995 09:26:03 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id MAA03947; Sun, 18 Jun 1995 12:25:43 -0400 Date: Sun, 18 Jun 1995 12:25:43 -0400 From: "House of Debuggin'" Message-Id: <199506181625.MAA03947@skynet.ctr.columbia.edu> To: freebsd-bugs@freebsd.org, wilcox@math.psu.edu Subject: Re: More on NIS problems Cc: bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk > I've seen a lot of nis problems running around. Here is my input. >have a FreeBSD 2.0.5R machine being the master server for what is going >to be a ton of freebsd machines. I have this for my netgroup file >staffhost1 (machine.xxx.yyy.zzz,-,) (machine2.xxx.yyy.zzz,-,) >staffhost2 (machine3.xxx.yyy.zzz,-,) (machine4.xxx.yyy.zzz,-,) >staffhosts staffhost1 staffhost2 >Then when I do ypmatch staffhosts netgroup I get >staffhost1 staffhost2 staffhosts staffhost1 staffhost2 >If I try to expand this in any fashion, it gets real ugly real quick. >Any reason this is doing this? >-Ken Wilcox Yeah: the reason is the 'netgroup' (and 'ethers.*' and 'bootparams') targets in /var/yp/Makefile are a little goofy. (My fault I'm afraid: I'm not terribly good with awk.) I just commited a fix to -current. Here's a diff that should fix the problem. Apply this to a virgin copy of /var/yp/Makefile, then remangle it to fit your system. The first hunk will undoubtedly fail since the CVS id strings may not match exactly. You can safely ignore the error. 4c4 < # $Id: Makefile.yp,v 1.7 1995/05/30 05:05:34 rgrimes Exp $ --- > # $Id: Makefile.yp,v 1.6 1995/04/02 01:53:47 wpaul Exp $ 29c29 < # --- > # 121c121 < print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \ --- > print $$2"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \ 132c132 < print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \ --- > print $$1"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \ 143c143 < print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(BOOTPARAMS) \ --- > print $$0 }' $^ | $(DBLOAD) -i $(BOOTPARAMS) \ 154c154 < print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(NETGROUP) \ --- > print $$0 }' $^ | $(DBLOAD) -i $(NETGROUP) \ Note that I'm currently working on closing out three NIS-related problem reports (508, 509 and 510) which have to do libc's handling of netgroups. I have preliminary fixes for 508 and 509, and I'm still working with Bill Fenner to try and resolve 510 (he claims that the +@netgroup host matching in /etc/hosts.equiv doesn't work, but I haven't been able to duplicate the problem, so I'm kinda stumped). PR #508 and #509 shouldn't affect you unless you have certain errors in your netgroup database, but if you run into problems I can send you a patch. On the other hand, if you *do* have +@netgroup host matching working, I'd like to hear about it so I'll know I'm not crazy. If you uncover any other problems, don't hesitate to report them. -Bill ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~ From owner-freebsd-bugs Sun Jun 18 10:12:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA20307 for bugs-outgoing; Sun, 18 Jun 1995 10:12:53 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA20293 ; Sun, 18 Jun 1995 10:12:50 -0700 Message-Id: <199506181712.KAA20293@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Dima (ELO)" cc: bugs@freebsd.org Subject: Re: problem In-reply-to: Your message of "Sun, 18 Jun 95 05:29:42 EDT." Date: Sun, 18 Jun 1995 10:12:50 -0700 From: "Justin T. Gibbs" Sender: bugs-owner@freebsd.org Precedence: bulk > >Hi, I am having a problem. >I cannot copy files from mounted dos partition to unix partition. >Every time I try to do it, I get system panic. > >My system: >P5-90, 16M RAM,adaptec 2940w, 1GB scsi fujitsu > >Thank you, > >Dima Can you be a little more specific about the panic? What would be most helpfull is the address of the panic and the name of the routine where the exception occured in your kernel. You can get the address of all kernel entry points with "nm". -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Sun Jun 18 10:20:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA20807 for bugs-outgoing; Sun, 18 Jun 1995 10:20:20 -0700 Received: from alf.zfn.uni-bremen.de (alf.zfn.uni-bremen.de [134.102.20.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA20792 for ; Sun, 18 Jun 1995 10:20:14 -0700 Received: from deceased.hb.north.de by alf.zfn.uni-bremen.de (AIX 3.2/UCB 5.64/4.940318) id AA34937; Sun, 18 Jun 1995 19:18:40 +0200 Received: from jelal.hb.north.de by deceased.hb.north.de with uucp (Smail3.1.29.1) id m0sNO0Q-000Z3DC; Sun, 18 Jun 95 19:19 MET DST Received: by jelal.hb.north.de (SMail-ST 0.95gcc/2.5+) id AA00648; Sun, 18 Jun 1995 19:04:34 +0200 (CEDT) Received: (from nox@localhost) by dose (8.6.9/8.6.9) id TAA00975; Sun, 18 Jun 1995 19:00:51 +0200 Date: Sun, 18 Jun 1995 19:00:51 +0200 From: Juergen Lock Message-Id: <199506181700.TAA00975@dose> To: joerg_wunsch@uriah.heep.sax.de Subject: Re: problem Cc: freebsd-bugs@freebsd.org In-Reply-To: <199506181218.OAA17862@uriah.heep.sax.de> References: Organization: none Sender: bugs-owner@freebsd.org Precedence: bulk In article <199506181218.OAA17862@uriah.heep.sax.de> you write: >As Dima wrote: >> >> >> Hi, I am having a problem. >> I cannot copy files from mounted dos partition to unix partition. >> Every time I try to do it, I get system panic. > >What about telling us something more? sounds familiar, see kern/371 :) this was on 2.0R though, haven't tried 2.0.5 yet... oh and does utime() work on mouted dos files for any of you here? or did one of the patches break it. (i can repost them if anyone wants, at least they seem to have fixed the panics...) and while we're talking about ms-dog, any chance the doom^H^H^H^Hlinux emulator could be used to run their dog emulation? ok i guess i'm dreaming now... Juergen :) From owner-freebsd-bugs Sun Jun 18 10:34:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA21748 for bugs-outgoing; Sun, 18 Jun 1995 10:34:08 -0700 Received: from blaze.trentu.ca (mamrs@BLAZE.TRENTU.CA [192.75.12.200]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA21738 for ; Sun, 18 Jun 1995 10:34:07 -0700 Received: by blaze.trentu.ca (5.65/DEC-Ultrix/4.4) id AA23115; Sun, 18 Jun 1995 13:34:04 -0400 Date: Sun, 18 Jun 1995 13:34:02 -0400 (EDT) From: "Michael R. Skarupa" To: bugs@FreeBSD.org Subject: Release 2.0.5 with Updated boot.flp Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk To Whom it may concern I would like to report to your team that I had major problems with FreeBSD 2.0.5. I installed it four times with the original boot.flp, and installed it once with the June 12 boot.flp. All came to the same result, the /usr mount was lost on either shutdown or boot up. It would work for awhile, maybe a dozen cycles of bootup then it would loose /usr mount. I also generated my own kernel from the GENERIC kernel, and really did not change any of the options except remove unwanted drivers, and added my sound card, and also added SYSV extensions. I put on the full release with all the parts including DES, dict, and games, etc. I also put on the full X-Windows distribution except for the xdm package. Once the system was up and running, I then used to the ports command to compile seyon, fvwm, rzsz and gunzip. I added Xaw3d, xpm, and tcsh as binaries. Before I compiled the above programs I copied the Xaw3d include files and the libaries over the Xaw include files and libraries. The last stage in my feable install attemps were to delete unwanted directories in the experimnt and commmerce directories to conserve on disk storage. In order to perform these tasks I created one user account for myself, and gave myself super user status by appending my user name to the wheel group. Since I like to use Unix so well I ended up installing a minimal system with just the binaries, man pages, and games. I also installed kermit for communications purposes. I am going to leave my system like this until I hear how I can run it in confidence, or a new snap release comes out that works. If you need more information I will be happy to supply it. I am very dissappointed that things did not work out. I really enjoy FreeBSD and could not face putting Linux on my machine, as I can also get access to a Linux distribution CD. Thank You for Your Concerns Michael R. Skarupa Trent University From owner-freebsd-bugs Sun Jun 18 10:43:57 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA22509 for bugs-outgoing; Sun, 18 Jun 1995 10:43:57 -0700 Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA22503 for ; Sun, 18 Jun 1995 10:43:55 -0700 Received: by gvr.win.tue.nl (8.6.10/1.53) id TAA03536; Sun, 18 Jun 1995 19:43:48 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199506181743.TAA03536@gvr.win.tue.nl> Subject: 2.05R: failure to get fd parameters correctly To: freebsd-bugs@freebsd.org Date: Sun, 18 Jun 1995 19:43:47 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 644 Sender: bugs-owner@freebsd.org Precedence: bulk I tried to install 2.05R on a CSSI only system with a 2GB Quantum EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) Anyway: after installing all of it, it failed to boot from the fixed disk with a missing operating system. So I tried to reinstall it but now I chang4ed the geomtery to what 2.0R reported when booting. This just failed. Every key I touched I got this popu menu shouting that I entered the wrong geometry :-( I `solved' the problem by adding a dos partition of 1 meg, but this is bad. I dont want DOS. And I dont understand why I caanot use the geometry reported by 2.0R when booting for the 2.05R installs... -Guido From owner-freebsd-bugs Sun Jun 18 10:56:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23248 for bugs-outgoing; Sun, 18 Jun 1995 10:56:18 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA23238 ; Sun, 18 Jun 1995 10:56:16 -0700 Message-Id: <199506181756.KAA23238@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: guido@gvr.win.tue.nl (Guido van Rooij) cc: freebsd-bugs@freebsd.org Subject: Re: 2.05R: failure to get fd parameters correctly In-reply-to: Your message of "Sun, 18 Jun 95 19:43:47 +0200." <199506181743.TAA03536@gvr.win.tue.nl> Date: Sun, 18 Jun 1995 10:56:16 -0700 From: "Justin T. Gibbs" Sender: bugs-owner@freebsd.org Precedence: bulk >I tried to install 2.05R on a CSSI only system with a 2GB Quantum >EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) >Anyway: after installing all of it, it failed to boot from the >fixed disk with a missing operating system. >So I tried to reinstall it but now I chang4ed the geomtery to >what 2.0R reported when booting. This just failed. Every key I touched >I got this popu menu shouting that I entered the wrong geometry :-( >I `solved' the problem by adding a dos partition of 1 meg, but this >is bad. I dont want DOS. And I dont understand why I caanot use the geometry >reported by 2.0R when booting for the 2.05R installs... > >-Guido I installed to an Empire 2100 last nigt using the standard Adaptec geometry since it was hanging of a 2742T. What kind of disk controller are you using? -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Sun Jun 18 11:02:52 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA23818 for bugs-outgoing; Sun, 18 Jun 1995 11:02:52 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA23811 for ; Sun, 18 Jun 1995 11:02:50 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA02028; Sun, 18 Jun 1995 11:02:50 -0700 From: "Rodney W. Grimes" Message-Id: <199506181802.LAA02028@gndrsh.aac.dev.com> Subject: Re: 2.05R: failure to get fd parameters correctly To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Sun, 18 Jun 1995 11:02:49 -0700 (PDT) Cc: freebsd-bugs@freebsd.org In-Reply-To: <199506181743.TAA03536@gvr.win.tue.nl> from "Guido van Rooij" at Jun 18, 95 07:43:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1292 Sender: bugs-owner@freebsd.org Precedence: bulk > > I tried to install 2.05R on a CSSI only system with a 2GB Quantum > EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) What is wrong with the Quantum Empire 2100S? I use to have one and loved it, and I know lots of folks who have them and have had no problem with them. Please don't slam the product without stating a reason it is bad, you hurt some of your fellow hackers when you do this as next time I go to sell someone an Empire 2100 who has read your post I have to dispell what was said :-(. If it has some facts to it makes it easier for me to counter or confirm :-). > Anyway: after installing all of it, it failed to boot from the > fixed disk with a missing operating system. > So I tried to reinstall it but now I chang4ed the geomtery to > what 2.0R reported when booting. This just failed. Every key I touched > I got this popu menu shouting that I entered the wrong geometry :-( > I `solved' the problem by adding a dos partition of 1 meg, but this > is bad. I dont want DOS. And I dont understand why I caanot use the geometry > reported by 2.0R when booting for the 2.05R installs... > > -Guido > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun Jun 18 11:28:57 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25468 for bugs-outgoing; Sun, 18 Jun 1995 11:28:57 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA25462 for ; Sun, 18 Jun 1995 11:28:54 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA04003; Mon, 19 Jun 1995 04:27:17 +1000 Date: Mon, 19 Jun 1995 04:27:17 +1000 From: Bruce Evans Message-Id: <199506181827.EAA04003@godzilla.zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, nox@jelal.hb.north.de Subject: Re: problem Cc: freebsd-bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk >>> Hi, I am having a problem. >>> I cannot copy files from mounted dos partition to unix partition. >>> Every time I try to do it, I get system panic. >> >>What about telling us something more? Especially the FreeBSD version number and the command used to duplicate the bug. It sounds like a FreeBSD-2.0 bug. >sounds familiar, see kern/371 :) this was on 2.0R though, haven't >tried 2.0.5 yet... Everything in kern/371 seemed to be fixed before it was submitted, but I didn't have time to check. I just checked. The panic for chflags() (which is done for `cp -p') was fixed on 1994/12/27. The panic for rename() was fixed on 1995/04/11. > oh and does utime() work on mouted dos files for any of you here? That was fixed on 1994/12/27 too. Bruce From owner-freebsd-bugs Sun Jun 18 11:48:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26381 for bugs-outgoing; Sun, 18 Jun 1995 11:48:59 -0700 Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26355 for ; Sun, 18 Jun 1995 11:48:56 -0700 Received: by gvr.win.tue.nl (8.6.10/1.53) id UAA03766; Sun, 18 Jun 1995 20:48:38 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199506181848.UAA03766@gvr.win.tue.nl> Subject: Re: 2.05R: failure to get fd parameters correctly To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sun, 18 Jun 1995 20:48:38 +0200 (MET DST) Cc: freebsd-bugs@freebsd.org In-Reply-To: <199506181802.LAA02028@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 18, 95 11:02:49 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 859 Sender: bugs-owner@freebsd.org Precedence: bulk Rodney W. Grimes wrote: > > > > > I tried to install 2.05R on a CSSI only system with a 2GB Quantum > > EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) > > What is wrong with the Quantum Empire 2100S? I use to have one and > loved it, and I know lots of folks who have them and have had no > problem with them. Please don't slam the product without stating > a reason it is bad, you hurt some of your fellow hackers when you > do this as next time I go to sell someone an Empire 2100 who has > read your post I have to dispell what was said :-(. If it has some > facts to it makes it easier for me to counter or confirm :-). > We use it for news here. And within 8 months we are now using the third one. 2 others just began giving various media errors. And yes, automatic reallocs were enabled on this disk. I think this is bad. -Guido From owner-freebsd-bugs Sun Jun 18 11:50:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26530 for bugs-outgoing; Sun, 18 Jun 1995 11:50:27 -0700 Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26500 ; Sun, 18 Jun 1995 11:50:22 -0700 Received: by gvr.win.tue.nl (8.6.10/1.53) id UAA03786; Sun, 18 Jun 1995 20:50:16 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199506181850.UAA03786@gvr.win.tue.nl> Subject: Re: 2.05R: failure to get fd parameters correctly To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Sun, 18 Jun 1995 20:50:15 +0200 (MET DST) Cc: freebsd-bugs@freebsd.org In-Reply-To: <199506181756.KAA23238@freefall.cdrom.com> from "Justin T. Gibbs" at Jun 18, 95 10:56:16 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1028 Sender: bugs-owner@freebsd.org Precedence: bulk Justin T. Gibbs wrote: > > >I tried to install 2.05R on a CSSI only system with a 2GB Quantum > >EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) > >Anyway: after installing all of it, it failed to boot from the > >fixed disk with a missing operating system. > >So I tried to reinstall it but now I chang4ed the geomtery to > >what 2.0R reported when booting. This just failed. Every key I touched > >I got this popu menu shouting that I entered the wrong geometry :-( > >I `solved' the problem by adding a dos partition of 1 meg, but this > >is bad. I dont want DOS. And I dont understand why I caanot use the geometry > >reported by 2.0R when booting for the 2.05R installs... > > > >-Guido > > I installed to an Empire 2100 last nigt using the standard Adaptec > geometry since it was hanging of a 2742T. What kind of disk controller > are you using? OOps...sorry: An ncr 53c810 controller. This is waht 2.0R thought of it: sd2: 2006MB (4108600 total sec), 3053 cyl, 12 head, 112 sec, bytes/sec 512 -Guido From owner-freebsd-bugs Sun Jun 18 12:10:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27485 for bugs-outgoing; Sun, 18 Jun 1995 12:10:53 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA27479 for ; Sun, 18 Jun 1995 12:10:51 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA02187; Sun, 18 Jun 1995 12:10:49 -0700 From: "Rodney W. Grimes" Message-Id: <199506181910.MAA02187@gndrsh.aac.dev.com> Subject: Re: 2.05R: failure to get fd parameters correctly To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Sun, 18 Jun 1995 12:10:49 -0700 (PDT) Cc: freebsd-bugs@freebsd.org In-Reply-To: <199506181848.UAA03766@gvr.win.tue.nl> from "Guido van Rooij" at Jun 18, 95 08:48:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1162 Sender: bugs-owner@freebsd.org Precedence: bulk > > Rodney W. Grimes wrote: > > > > > > > > I tried to install 2.05R on a CSSI only system with a 2GB Quantum > > > EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) > > > > What is wrong with the Quantum Empire 2100S? I use to have one and > > loved it, and I know lots of folks who have them and have had no > > problem with them. Please don't slam the product without stating > > a reason it is bad, you hurt some of your fellow hackers when you > > do this as next time I go to sell someone an Empire 2100 who has > > read your post I have to dispell what was said :-(. If it has some > > facts to it makes it easier for me to counter or confirm :-). > > > > We use it for news here. And within 8 months we are now using the > third one. 2 others just began giving various media errors. And yes, > automatic reallocs were enabled on this disk. > I think this is bad. I agree, this is bad. Care to give me the serial numbers off of them? Did you get them replaced under warranty? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun Jun 18 12:18:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27769 for bugs-outgoing; Sun, 18 Jun 1995 12:18:55 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA27762 ; Sun, 18 Jun 1995 12:18:51 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA04907; Mon, 19 Jun 1995 05:18:08 +1000 Date: Mon, 19 Jun 1995 05:18:08 +1000 From: Bruce Evans Message-Id: <199506181918.FAA04907@godzilla.zeta.org.au> To: gibbs@freefall.cdrom.com, guido@gvr.win.tue.nl Subject: Re: 2.05R: failure to get fd parameters correctly Cc: freebsd-bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk >> >is bad. I dont want DOS. And I dont understand why I caanot use the geometry >> >reported by 2.0R when booting for the 2.05R installs... >This is waht 2.0R thought of it: >sd2: 2006MB (4108600 total sec), 3053 cyl, 12 head, 112 sec, bytes/sec 512 2.0R worked because it didn't insist on a valid geometry (sec < 64) and the invalid geometry happened not to be used (only one partition starting on the first track). Bruce From owner-freebsd-bugs Sun Jun 18 12:23:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27978 for bugs-outgoing; Sun, 18 Jun 1995 12:23:27 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA27972 for ; Sun, 18 Jun 1995 12:23:26 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18337; Sun, 18 Jun 95 13:16:30 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506181916.AA18337@cs.weber.edu> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Sun, 18 Jun 95 13:16:29 MDT Cc: bde@zeta.org.au, bugs@FreeBSD.org, hlew@genome.Stanford.EDU In-Reply-To: <199506180538.PAA15480@godzilla.zeta.org.au> from "Bruce Evans" at Jun 18, 95 03:38:55 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > >> This seems to be the case that I said can't work. Apparently wd1 doesn't > >> have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. > > >YES. > > >Makes perfect sense, actually. Once you are booting BSD, the disk BSD is > >on is hat it thinks the boot disk is. It can't know the INT 13 chaining > >used by the BIOS. > > It's not clear to me whether this is an installation error. Why is Ontrack > managling disks that it isn't on? Consider the case of two identical drives that need OnTrack, one as the master and one as the slave. The OnTrack, dealing as it does with only bootable devices, must apply to all. > Can the problem be fixed by installing Ontrack on all disks, I believe so, though not for any good reason. The reason it would work is that BSD would see the ontrack on the boot device and act appropriately for a boot device not root. The geometry management of the second device by OnTrack, being correct, is still acceptable. > or configuring it to only manage the disk(s) that it is installed on? I find it questionable to believe that OnTrack adjusts the starting sector and not simply the geometry for the secondary disks. If it does the former, then I would say it is a bug in OnTrack, since it is generating unusable area on the second disk. The difference, of course, to the user is that the BSD install to the second disk should either be by way of an OnTrack boot of the BSD floppy, or into a 63 sector ofsset partition table, respectively. As I said before, you *could* work around this with an install order dance if you were aware of the behaviour beforehand. The main issue will be the main partition table entry location for the BSD partition (in an Ontrack adjusted table or not) and the offset locations in the BSD disklabel (or not). I believe one or both of these to be the case because of the demonstrated failures. > >I hesistate to describe the process (so I won't) since it's rather complex > >and requires a deep understanding of the boot process. In broad strokes, > >it would involve modifying the second disks partition table, installing, > >modifying the installed disk label and partition table, and going from there. > > This won't work. If there is only one partition table, then the FreeBSD > boot loader and FreeBSD proper will see the same one, and FreeBSD proper > needs to see a table modified as above. I was under the impression that the FreeBSD proper view was abstracted from the disklabel seperate from the C/H/S area within the disklabel for the BIOS boot. If this is still the case, then you could hack the absolute offsets with relative impunity. If it's not the case, well, then that's a problem. > >If you *only* have BSD on the second drive, and are willing to blow it > >away, you can get the same effect by making the BSD drive the primary > >drive, installing OnTrack (assuming you have it), then installing BSD onto > >what is now the first drive. > > >When you put ehe drive back to the second drive and put the original drive > >back on, it should work. > > Only if Ontrack doesn't doubly manage the second drive after you put it > back. It shouldn't be possible for this to happen according to the OnTrack people. Also this soloution assumes the offsets are applied to non-bootable drives, which may not be the case (it could be the BSD disklabel screwup above). > I think we're finding complications where none exist. It's hard to debug > without seeing the output of boot -v and sysinstall. Yes. In this case, though, I'd like to see the pfdisk output for both drives given a DOS boot from floppy followed by a DOS boot from the HD. It would identify the problem precisely once the BSD code was examined to see what it would do with the resulting case. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Sun Jun 18 12:26:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA28123 for bugs-outgoing; Sun, 18 Jun 1995 12:26:41 -0700 Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA28117 ; Sun, 18 Jun 1995 12:26:37 -0700 Received: by gvr.win.tue.nl (8.6.10/1.53) id VAA03960; Sun, 18 Jun 1995 21:26:02 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199506181926.VAA03960@gvr.win.tue.nl> Subject: Re: 2.05R: failure to get fd parameters correctly To: bde@zeta.org.au (Bruce Evans) Date: Sun, 18 Jun 1995 21:26:01 +0200 (MET DST) Cc: gibbs@freefall.cdrom.com, freebsd-bugs@freebsd.org In-Reply-To: <199506181918.FAA04907@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 05:18:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 517 Sender: bugs-owner@freebsd.org Precedence: bulk That explains a lot..thanks.. -Guido Bruce Evans wrote: > > >> >is bad. I dont want DOS. And I dont understand why I caanot use the geometry > >> >reported by 2.0R when booting for the 2.05R installs... > > >This is waht 2.0R thought of it: > > >sd2: 2006MB (4108600 total sec), 3053 cyl, 12 head, 112 sec, bytes/sec 512 > > 2.0R worked because it didn't insist on a valid geometry (sec < 64) and the > invalid geometry happened not to be used (only one partition starting on > the first track). > > Bruce > From owner-freebsd-bugs Sun Jun 18 12:40:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA29808 for bugs-outgoing; Sun, 18 Jun 1995 12:40:56 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA29802 for ; Sun, 18 Jun 1995 12:40:54 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id MAA04258; Sun, 18 Jun 1995 12:40:52 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id MAA00739; Sun, 18 Jun 1995 12:41:09 -0700 Message-Id: <199506181941.MAA00739@corbin.Root.COM> To: "Michael R. Skarupa" cc: bugs@freebsd.org Subject: Re: Release 2.0.5 with Updated boot.flp In-reply-to: Your message of "Sun, 18 Jun 95 13:34:02 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 18 Jun 1995 12:41:09 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk >the /usr mount was lost on either shutdown or boot up. It would work for >awhile, maybe a dozen cycles of bootup then it would loose /usr mount. I Can you explain what you mean by "would lose the /usr mount"? I really have no idea what you're talking about. Do you mean that there is some sort of filesystem corruption? If so, could you be more specific? -DG From owner-freebsd-bugs Sun Jun 18 12:58:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA00600 for bugs-outgoing; Sun, 18 Jun 1995 12:58:04 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA00594 for ; Sun, 18 Jun 1995 12:58:03 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18449; Sun, 18 Jun 95 13:51:06 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506181951.AA18449@cs.weber.edu> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Sun, 18 Jun 95 13:51:06 MDT Cc: bde@zeta.org.au, hlew@genome.Stanford.EDU, bugs@FreeBSD.ORG In-Reply-To: <199506180547.PAA15709@godzilla.zeta.org.au> from "Bruce Evans" at Jun 18, 95 03:47:18 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.ORG Precedence: bulk > >So can DOS access more than 504MB per partition on SCSI drives? > > Yes, up to 8GB, provided the BIOS supports it (I haven't figured out how > to make my U34F or BT445C support more than 1024MB - they always use the > 64H 32S geometry). Modern EIDE BIOSes also support up to 8GB. Disk > managers are only required for old BIOSes. I think the key word there is "per partition". The answer is 2G, with 32k clusters. The DOS theoretical limit is 4G with 64k clusters, but in practice this introduces a conflict with the file truncation command (which is a standard write of 0 bytes at the truncation offset). The conflict arises from the inability to specify a transfer in excess of 65535 bytes, since the 0 is reserved, and thus a failure to transfer the full 64k (which you would do using a 0 token or a +1 to the requested amount). Now the DOS partitions themselves are limited by the 24 bit sector locator (C:10/H:8/S:6) on a translated geometry drive, limiting the representable geometry of the drive to 8G (assuming full translation). DOS, however accesses drives via DOS file system. > >Oh well.... I guess the only alternative is to swap the hard drive cables > >and redo the master/slave jumpers... :-( > > How would that help? You would still need Ontrack somewhere to use more > than 504MB for DOS on the big drive. Putting Ontrack somewhere apparently > affects everywhere. By manyally installing the OnTrack (assuming he has the disks) onto the second drive, he will cause BSD to see the OnTrack and (hopefully) react accordingly on the second drive. In point of fact, I would rather see the pfdisk output (as described in the previous post) before he goes ahead with this approach. There may be an unrecoverable (at present) BSD limitation that would prevent this from working. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Sun Jun 18 13:00:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA00822 for bugs-outgoing; Sun, 18 Jun 1995 13:00:22 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA00816 for ; Sun, 18 Jun 1995 13:00:21 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18689; Sun, 18 Jun 1995 13:00:04 -0700 Date: Sun, 18 Jun 1995 13:00:03 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bde@zeta.org.au, terry@cs.weber.edu, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506180538.PAA15480@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sun, 18 Jun 1995, Bruce Evans wrote: > I think we're finding complications where none exist. It's hard to debug > without seeing the output of boot -v and sysinstall. Okay.... here is the output if I let the Ontrack DM load the dynamic overlay and then use the option to boot from the boot.flp. If I choose wd(1,a)/kernel.GENERIC -v FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 jkh@westhill.cdrom.com:/usr/src/sys/compile/GENERIC CPU: i386DX (386-class CPU) real memory = 7995392 (1952 pages) avail memory = 6627328 (1618 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 not found at 0x280 ed1 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 bt0 not found at 0x330 uha0 not found at 0x330 ahc1 not found ahb0 not found aha0 not found at 0x330 aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found wt0 not found at 0x300 mcd0: disabled, not probed. mcd1: disabled, not probed. matcd0: disabled, not probed. scd0 not found at 0x230 ie0 not found at 0x360 ep0 not found at 0x300 ix0 not found at 0x300 le0: no board found at 0x300 le0 not found at 0x300 lnc0 not found at 0x280 lnc1 not found at 0x300 ze0 not found at 0x300 zp0 not found at 0x300 npx0 at 0xf0-0xff irq 13 on motherboard Probing for devices on the pci0 bus: configuration mode 2 allows 16 devices. changing root device to wd1a BIOS Geometries: 0:03391f3f 825 cyl, 31 heads, 63 sects 1:03fd0f3f 1021 cyl, 15 heads, 63 sects 0 accounted for wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK ------------ Notice that no where in the boot process does it mention about the Ontrack DM. Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am not supposed to)... It shows these extra lines after the "0 accounted for" wd0: Found "Ontrack Disk Manager" on this disk. wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK panic: cannot mount root syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort From owner-freebsd-bugs Sun Jun 18 13:13:52 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01330 for bugs-outgoing; Sun, 18 Jun 1995 13:13:52 -0700 Received: from bronze.coil.com (bronze.coil.com [198.4.94.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01324 for ; Sun, 18 Jun 1995 13:13:50 -0700 Received: from localhost (echet@localhost) by bronze.coil.com (8.6.4/8.6.12) id QAA17830; Sun, 18 Jun 1995 16:16:31 -0400 From: Eric Chet Message-Id: <199506182016.QAA17830@bronze.coil.com> Subject: Re: Release 2.0.5 with Updated boot.flp To: davidg@Root.COM Date: Sun, 18 Jun 1995 16:16:30 -0400 (EDT) Cc: bugs@freebsd.org In-Reply-To: <199506181941.MAA00739@corbin.Root.COM> from "David Greenman" at Jun 18, 95 12:41:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 614 Sender: bugs-owner@freebsd.org Precedence: bulk > > >the /usr mount was lost on either shutdown or boot up. It would work for > >awhile, maybe a dozen cycles of bootup then it would loose /usr mount. I > > Can you explain what you mean by "would lose the /usr mount"? I really have > no idea what you're talking about. Do you mean that there is some sort of > filesystem corruption? If so, could you be more specific? > > -DG > I think I know what he is talking about. I booted up my machine two days ago, and the /usr was not mounted. Actually it was like it did not exist. Any ideas, this is on 2.0.5R the latest boot.flp. Eric -- echet@coil.com From owner-freebsd-bugs Sun Jun 18 13:29:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01777 for bugs-outgoing; Sun, 18 Jun 1995 13:29:03 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01771 for ; Sun, 18 Jun 1995 13:29:02 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18707; Sun, 18 Jun 1995 13:29:00 -0700 Date: Sun, 18 Jun 1995 13:28:59 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506172244.AA16053@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sat, 17 Jun 1995, Terry Lambert wrote: > Probably you made the BSD parition entry in the DM pseudo-partition table. Actually, drive C (wd0) is all msdos, and I wanted drive D (wd1) to be all FreeBSD, so there are no BSD partitions on wd0 which has the Ontrack DM. > > When you boot off the floppy, is it directly from the floppy or from the DM > boot menu? I have tried both ways and FreeBSD can boot up if I manually type: wd(1,a)/kernel > > This would tell for sure. > > You should boot DOS off floppy and run pfdisk. Okay, if boot from DOS (and with no Ontrack DM installed)... here's the output from pfdisk 0 (the 850MB Ontrack DM DOS Drive) and pfdisk 1 (540 MB FreeBSD drive) # Partition table on device: 0 geometry 1024 16 63 (cyls heads sectors) # ID First(cyl) Last(cyl) Name # start, length (sectors) 1 84 0 1652 unkno # 1, 1666223 # note: last(1): phys=(628,15,63) logical=(1652,15,63) # note: first(1): phys=(0,0,2) should be (0,1,1) 2 0 0 0 empty # 0, 0 3 0 0 0 empty # 0, 0 4 0 0 0 empty # 0, 0 # Partition table on device: 1 geometry 1022 16 63 (cyls heads sectors) # ID First(cyl) Last(cyl) Name # start, length (sectors) 1 165 0 1052 unkno # 63, 1061361 # note: last(1): phys=(1023,15,63) logical=(1052,15,63) 2 0 0 0 empty # 0, 0 3 0 0 0 empty # 0, 0 4 0 0 0 empty # 0, 0 --------- Now if I boot from the hard drive with Ontrack DM's dynamic drive overlay installed... # Partition table on device: 0 geometry 826 32 63 (cyls heads sectors) # ID First(cyl) Last(cyl) Name # start, length (sectors) 1 1 0 825 DOS12 # 63, 1665153 2 0 0 0 empty # 0, 0 3 0 0 0 empty # 0, 0 4 0 0 0 empty # 0, 0 # Partition table on device: 1 geometry 1022 16 63 (cyls heads sectors) # ID First(cyl) Last(cyl) Name # start, length (sectors) 1 165 0 1052 unkno # 63, 1061361 # note: last(1): phys=(1023,15,63) logical=(1052,15,63) 2 0 0 0 empty # 0, 0 3 0 0 0 empty # 0, 0 4 0 0 0 empty # 0, 0 So it appears that nothing changes on the 540MB drive that doesn't use Ontrack DM. So any ideas? From owner-freebsd-bugs Sun Jun 18 13:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01866 for bugs-outgoing; Sun, 18 Jun 1995 13:30:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA01859 ; Sun, 18 Jun 1995 13:30:02 -0700 Date: Sun, 18 Jun 1995 13:30:02 -0700 Message-Id: <199506182030.NAA01859@freefall.cdrom.com> From: deischen@iworks.InterWorks.org Reply-To: deischen@iworks.InterWorks.org To: freebsd-bugs Subject: misc/530: Failed install from SCSI tape In-Reply-To: Your message of Sun, 18 Jun 1995 16:33:01 -0400 <199506182033.QAA03447@rigel> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 530 >Category: misc >Synopsis: Failed install from SCSI tape >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 18 13:30:01 1995 >Originator: Daniel M. Eischen >Organization: >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 90 MHz Pentium box 2940W SCSI controller HP 1533C DAT tape drive >Description: When installing from tape (from the boot disk installation menu), I had placed the tape in the drive before booting. After I went through the various menus and finally got to the COMMIT, when it started reading from the tape, I got an error message: 10240-byte block too large. Well words to that effect. The default blocking factor for tar is 20 512-byte blocks, so if we cannot install as that, then the Install document should be updated to ensure the user makes the tape correctly. I remade the tape on another system with a blocking factor of 1. I went through the same exact procedure again and it worked fine. >How-To-Repeat: >Fix: Either fix the documentation (?) or the SCSI tape driver. Correcting the documentation is simple, but it seems like you'd really like to be able to handle tapes of default block size. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Jun 18 13:31:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02005 for bugs-outgoing; Sun, 18 Jun 1995 13:31:38 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01970 for ; Sun, 18 Jun 1995 13:31:24 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id WAA28570; Sun, 18 Jun 1995 22:31:04 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id WAA26088; Sun, 18 Jun 1995 22:31:03 +0200 Message-Id: <199506182031.WAA26088@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "House of Debuggin'" cc: freebsd-bugs@freebsd.org Subject: Re: More on NIS problems Date: Sun, 18 Jun 1995 22:31:03 +0200 From: Mark Murray Sender: bugs-owner@freebsd.org Precedence: bulk Hi Bill > Note that I'm currently working on closing out three NIS-related > problem reports (508, 509 and 510) which have to do libc's handling > of netgroups. I have preliminary fixes for 508 and 509, and I'm > still working with Bill Fenner to try and resolve 510 (he claims > that the +@netgroup host matching in /etc/hosts.equiv doesn't work, > but I haven't been able to duplicate the problem, so I'm kinda > stumped). PR #508 and #509 shouldn't affect you unless you have > certain errors in your netgroup database, but if you run into > problems I can send you a patch. On the other hand, if you *do* > have +@netgroup host matching working, I'd like to hear about > it so I'll know I'm not crazy. While you are busy on some bugs, please have a look at one that is really bothering me. (I plan to get to it in a while - but that will take a month or so...). Mine is bin/375, and the problem is that with kerberos running, the only way for a user to login to an account that is in the maps is to use the Kerberos password. I am sure that this is a screwup in the order that things get queried. FTP does not work except for anonymous, and password changing is also stuffed. > If you uncover any other problems, don't hesitate to report them. Here's mine! M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 From owner-freebsd-bugs Sun Jun 18 13:40:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02547 for bugs-outgoing; Sun, 18 Jun 1995 13:40:08 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02531 for ; Sun, 18 Jun 1995 13:40:04 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18716; Sun, 18 Jun 1995 13:40:02 -0700 Date: Sun, 18 Jun 1995 13:40:01 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: Bruce Evans , bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506172320.AA16151@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk > If you *only* have BSD on the second drive, and are willing to blow it > away, you can get the same effect by making the BSD drive the primary > drive, installing OnTrack (assuming you have it), then installing BSD onto > what is now the first drive. Yep, I only have FreeBSD on the second drive, but unfortunately, Ontrack is smart in that it won't install on a drive that didn't have the software bundled with the hard drive in the first place. Now the question is if I did swap cables and redo the jumpers, will DOS boot from drive D if I used the FreeBSD bootmanager on drive C. (The bios says boot from A and then C.) I can see a potential problem in that I will not be able to access the DOS files from FreeBSD because no Ontrack DM boot overlay will ever be loaded. > The DOSBOOT.COM might be more easily hacked to work -- but it depends > on if negative offsets are allowed. Okay, I have not heard a lot about this DOSBOOT.COM, so will it let me boot up FreeBSD from wd1a from DOS (wd0)? If it does, then this will be a good temporary fix (of course I have to boot up DOS every time I want to use FreeBSD or a place a script in the autosec.bat). From owner-freebsd-bugs Sun Jun 18 13:46:35 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02834 for bugs-outgoing; Sun, 18 Jun 1995 13:46:35 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02828 for ; Sun, 18 Jun 1995 13:46:33 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18724; Sun, 18 Jun 1995 13:46:27 -0700 Date: Sun, 18 Jun 1995 13:46:26 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bde@zeta.org.au, terry@cs.weber.edu, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506180538.PAA15480@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sun, 18 Jun 1995, Bruce Evans wrote: > It's not clear to me whether this is an installation error. Why is Ontrack > managling disks that it isn't on? Can the problem be fixed by installing > Ontrack on all disks, or configuring it to only manage the disk(s) that it > is installed on? Actually Ontrack does not seem to do anything to disks that it is not on. A pfdisk output (in my last message which should be floating by any second now) kind of shows that none of the geometries are changed on my non-Ontrack hard drive. From owner-freebsd-bugs Sun Jun 18 13:53:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03176 for bugs-outgoing; Sun, 18 Jun 1995 13:53:06 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA03169 for ; Sun, 18 Jun 1995 13:53:01 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18732; Sun, 18 Jun 1995 13:52:55 -0700 Date: Sun, 18 Jun 1995 13:52:54 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506180547.PAA15709@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sun, 18 Jun 1995, Bruce Evans wrote: > >It's too bad that DOS can't handle more than 504 MB for a large EIDE > >drive. Because if it could I wouldn't need to install the Ontrack DM > >overlay, and then FreeBSD would work like a charm. Oh... It's no a DOS limitation... ? Ooops... > DOS has no problems handling >= 504 MB. This is a BIOS problem. This is strange because I can configure the bios for 32 heads and over 800 Megs, but if I do a fdisk, DOS says the maximum partition size is 504 MB. > > >So can DOS access more than 504MB per partition on SCSI drives? > > Yes, up to 8GB, provided the BIOS supports it (I haven't figured out how > to make my U34F or BT445C support more than 1024MB - they always use the > 64H 32S geometry). Modern EIDE BIOSes also support up to 8GB. Disk > managers are only required for old BIOSes. > > >Oh well.... I guess the only alternative is to swap the hard drive cables > >and redo the master/slave jumpers... :-( > > How would that help? You would still need Ontrack somewhere to use more > than 504MB for DOS on the big drive. Putting Ontrack somewhere apparently > affects everywhere. Actually, Ontrack seems to only affect the drives it is installed in. But if I can get FreeBSD to boot up the 540MB one and then use the boot manager to boot up the 850MB (and still load the Ontrack DM overlay from the 850MB), then I think the bootup problem is gone. (Well, the tradeoff is I won't be able to access DOS from FreeBSD if I did do the cable swap and master/slave jumper fix. From owner-freebsd-bugs Sun Jun 18 13:58:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03355 for bugs-outgoing; Sun, 18 Jun 1995 13:58:24 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA03346 for ; Sun, 18 Jun 1995 13:58:22 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18733; Sun, 18 Jun 95 14:51:20 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506182051.AA18733@cs.weber.edu> Subject: Re: 2.05R: failure to get fd parameters correctly To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Sun, 18 Jun 95 14:51:20 MDT Cc: gibbs@freefall.cdrom.com, freebsd-bugs@freebsd.org In-Reply-To: <199506181850.UAA03786@gvr.win.tue.nl> from "Guido van Rooij" at Jun 18, 95 08:50:15 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@freebsd.org Precedence: bulk > Justin T. Gibbs wrote: > > >I tried to install 2.05R on a CSSI only system with a 2GB Quantum > > >EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) > > >Anyway: after installing all of it, it failed to boot from the > > >fixed disk with a missing operating system. > > >So I tried to reinstall it but now I chang4ed the geomtery to > > >what 2.0R reported when booting. This just failed. Every key I touched > > >I got this popu menu shouting that I entered the wrong geometry :-( > > >I `solved' the problem by adding a dos partition of 1 meg, but this > > >is bad. I dont want DOS. And I dont understand why I caanot use the geometry > > >reported by 2.0R when booting for the 2.05R installs... > > > > > >-Guido > > > > I installed to an Empire 2100 last nigt using the standard Adaptec > > geometry since it was hanging of a 2742T. What kind of disk controller > > are you using? > > OOps...sorry: > An ncr 53c810 controller. > > This is waht 2.0R thought of it: > > sd2: 2006MB (4108600 total sec), 3053 cyl, 12 head, 112 sec, bytes/sec 512 The problem with the quantum and the NCR controller is the sequencer code having a window between checking for other bus users and asserting bus ownership because it is a fast drive. This hole was closed on the Adaptec sequencer code, and the procedural fix reported to the hackers list. I am unsure if the fix has been incorporated into updated NCR sequencer code -- in fact, I doubt that it has. Your current alternatives are: 1) Use a non-NCR controller 2) Use a different disk that does not exercise the hole. I believe the hole is exercised by drives that are called "AV drvies". These drives achieve their faster throughput by not doing thermal recalibration. This is in fact a terrifically bad hack to get the desired results, and will definitely increase the failure rates you'll see when using the drives. 3) Go to the Hackers list archives, and using that information and information obtained from NCR, fix the sequencer code. Hopefully if you choose this option, you will donate the code back, both for the rest of the NCR controller owners benefit and for your own benefit in not having to reintegrate the changes you make each time the driver is revised. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Sun Jun 18 14:32:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA04619 for bugs-outgoing; Sun, 18 Jun 1995 14:32:16 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA04611 for ; Sun, 18 Jun 1995 14:32:15 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19481; Sun, 18 Jun 95 15:25:11 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506182125.AA19481@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Sun, 18 Jun 95 15:25:10 MDT Cc: bde@zeta.org.au, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 18, 95 01:28:59 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > Okay, if boot from DOS (and with no Ontrack DM installed)... here's the > output from pfdisk 0 (the 850MB Ontrack DM DOS Drive) and pfdisk 1 (540 > MB FreeBSD drive) > > # Partition table on device: 0 > geometry 1024 16 63 (cyls heads sectors) > # ID First(cyl) Last(cyl) Name # start, length (sectors) > 1 84 0 1652 unkno # 1, 1666223 > # note: last(1): phys=(628,15,63) logical=(1652,15,63) > # note: first(1): phys=(0,0,2) should be (0,1,1) > 2 0 0 0 empty # 0, 0 > 3 0 0 0 empty # 0, 0 > 4 0 0 0 empty # 0, 0 This is the OnTrack DM pseudo-partition table; this makes the BIOS POST happy. This drive has OnTrack installed on it. > # Partition table on device: 1 > geometry 1022 16 63 (cyls heads sectors) > # ID First(cyl) Last(cyl) Name # start, length (sectors) > 1 165 0 1052 unkno # 63, 1061361 > # note: last(1): phys=(1023,15,63) logical=(1052,15,63) > 2 0 0 0 empty # 0, 0 > 3 0 0 0 empty # 0, 0 > 4 0 0 0 empty # 0, 0 This is the BSD "pseudo" partition table -- it's "pseudo" because it is correct from a DOS perspective and the information is actually used by BSD in the boot process. > Now if I boot from the hard drive with Ontrack DM's dynamic drive overlay > installed... > > # Partition table on device: 0 > geometry 826 32 63 (cyls heads sectors) > # ID First(cyl) Last(cyl) Name # start, length (sectors) > 1 1 0 825 DOS12 # 63, 1665153 > 2 0 0 0 empty # 0, 0 > 3 0 0 0 empty # 0, 0 > 4 0 0 0 empty # 0, 0 This is the real DOS partition table. This is the table embedded in the DOS MBR (master boot record) that you are using OS-BS to replace. This partition table is being logically offset by the INT 13 redirector installed by the OnTrack DM's MBR. > # Partition table on device: 1 > geometry 1022 16 63 (cyls heads sectors) > # ID First(cyl) Last(cyl) Name # start, length (sectors) > 1 165 0 1052 unkno # 63, 1061361 > # note: last(1): phys=(1023,15,63) logical=(1052,15,63) > 2 0 0 0 empty # 0, 0 > 3 0 0 0 empty # 0, 0 > 4 0 0 0 empty # 0, 0 This is, once again, the BSD "pseudo" partition table. It;s existance here indicates that the OnTrack DM is not translating the second drives start location, nor is it translating the second drives geometry. Probably this is the case because it has not identified itself as existing on the second partition at all. The point of this is that the BIOS geometry seen by the OS-BS is not a translated geometry. > So it appears that nothing changes on the 540MB drive that doesn't use > Ontrack DM. So any ideas? Yes. The information above is sufficient, barring an error in the interpretation of the geometry by BSD, to get you installed correctly and booting BSD off the second drive using OS-BS. What you need to do is: 1) Make sure DM is on the first drive [this is done] 2) Boot the first drive under DOS to activate the DM INT 13 redirector. 3) Use the DOS installation to install OS-BS onto the first drive as a replacement for the displace DOS MBR. The partition table will exist in the OS-BS MBR instead of the DOS MBR. *) At this point, you should be able to boot of the first drive into the OS-BS menu and select "DOS", acusing the DOS to boot correctly. Do not proceed past this point until this is the case. 4) At this point you should be able to ask it to boot of the second drive (assuming you have OS-BS installed correctly. This will fail, but you should make sure that you can attempt to boot off the second drive. Subsequent steps will [potentially] require the reinstallation of BSD. If you are not prepared to do this, you should rely on booting with a floppy. To make it more convenient, you can change the default device in the floppy boot blocks, which will result in the floppy booting the correct device. The method for doing this is well documented in the hackers list archive on freefall.cdrom.com. This archive can also be accessed via www at http://www.freebsd.org. 5) Install OS-BS on the second drive. This may or may not be easy to accomplish. If the partition table on the second drive is a remnant of a DOS install, then this will be easy; otherwise you will have to use the DOS command fdisk/mbr on the second DOS drive. YOU MUST GIVE THE DOS DRIVE LETTER AS A PARAMETER. In addition, the /mbr option is not available in DOS revisions prior to 5.0. At this point you can install OS-BS and reinstall BSD. Now when you boot, you will get an option to choose the DOS partition or the second drive. Tho boot BSD, choose the second drive option in the OS-BS menu. You will get another OS-BS menu (the DOS option in this menus will not work). Choose the FreeBSD option, and it should boot correctly. The single possibility for error at this point is if the FreeBSD install incorrectly selects disklabel contents based on detecting the DM on the first drive. If this happens, you will need to contact the FreeBSD team for an updated installation that does not make this mistake. ====== Cannonically, the BSD should rewrite a boot manager on their own to make this process simpler. Realistically, this probably can not be done sufficiently portably, since the OnTrack DM is not the only program that uses the MBR replacement/INT 13 redirector mechanism to hide BIOS patches at the start of your hard drive. The best that can be achieved is the partial compatabilty. The one issue here is that the OS-BS install on the second drive could probably be avoided, and the non-working menu entries omitted. In that case, it subtracts a step from the boot process. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Sun Jun 18 14:36:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA04766 for bugs-outgoing; Sun, 18 Jun 1995 14:36:13 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA04760 for ; Sun, 18 Jun 1995 14:36:12 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19499; Sun, 18 Jun 95 15:29:12 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506182129.AA19499@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Sun, 18 Jun 95 15:29:11 MDT Cc: bde@zeta.org.au, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 18, 95 01:40:01 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > The DOSBOOT.COM might be more easily hacked to work -- but it depends > > on if negative offsets are allowed. > > Okay, I have not heard a lot about this DOSBOOT.COM, so will it let me > boot up FreeBSD from wd1a from DOS (wd0)? If it does, then this will be > a good temporary fix (of course I have to boot up DOS every time I want > to use FreeBSD or a place a script in the autosec.bat). The DOSBOOT.COM loads the master boot record off the drive and gives control to it; in efect, it is a soft (targetable) reboot. The hacks you could do would choose the target. The source is either in the i386 directory or in the netboot directory (I forget). The file you will want to copy to your DOS disk as DOSBOOT.COM is dosboot.nohdr (again from memory -- check the docs and makefiles in the sources). This will be useless unless you can get booted and running to the point where the sources are installed and you can boot normally (if with a lot of effort). In otherwords, think about this *later*. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Sun Jun 18 15:34:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA06668 for bugs-outgoing; Sun, 18 Jun 1995 15:34:44 -0700 Received: from todonix.ping.de (root@todonix.ping.de [193.100.14.43]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA06656 for ; Sun, 18 Jun 1995 15:34:26 -0700 Received: by todonix.ping.de (Smail3.1.28.1 #1) id m0sNSsV-000720C; Mon, 19 Jun 95 00:31 MET DST Message-Id: From: jan@todonix.ping.de (Jan Wedekind) Subject: 2.05R reboot hangs To: bugs@freebsd.org Date: Mon, 19 Jun 1995 00:31:39 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2119 Sender: bugs-owner@freebsd.org Precedence: bulk Hi, sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). the kernel config is as follows. (no more devices are configured!) Jan FreeBSD 2.0.5-RELEASE #5: Sun Jun 18 19:53:26 MET DST 1995 root@leary:/usr/src/sys/compile/DEBUG CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 33161216 (8096 pages) avail memory = 30523392 (7452 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:40:95:e0:29:37, type NE2000 (16 bit) lpt0 at 0x378-0x37f on isa sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A cy0 irq 10 maddr 0xd4000 msize 8192 on isa cy1 irq 11 maddr 0xd6000 msize 8192 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface Probing for devices on the pci0 bus: configuration mode 2 allows 16 devices. chip0 rev 4 on pci0:0 ncr0 rev 1 int a irq 14 on pci0:1 reg20: virtual=0xf4a48000 physical=0xfbfef000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) (ncr0:0:0): "FUJITSU M2684S-512 2035" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 507MB (1039329 512 byte sectors) chip1 rev 3 on pci0:2 vga0 rev 0 int a irq 15 on pci0:5 ncr1 rev 2 int a irq 9 on pci0:6 reg20: virtual=0xf4a49000 physical=0xfafff000 size=0x100 ncr1: restart (scsi reset). ncr1 scanning for targets 0..6 (V2 pl21 95/03/21) (ncr1:4:0): "HP HP35470A 1109" type 1 removable SCSI 2 st0(ncr1:4:0): Sequential-Access st0(ncr1:4:0): 200ns (5 Mb/sec) offset 8. density code 0x13, drive empty pci0: uses 8389120 bytes of memory from fafff000 upto fbfef0ff. pci0: uses 512 bytes of I/O space from e400 upto e8ff. pid 178: tail: uid 0: exited on signal 3 From owner-freebsd-bugs Sun Jun 18 16:13:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA07901 for bugs-outgoing; Sun, 18 Jun 1995 16:13:39 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA07890 ; Sun, 18 Jun 1995 16:13:36 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id QAA02506; Sun, 18 Jun 1995 16:13:19 -0700 From: "Rodney W. Grimes" Message-Id: <199506182313.QAA02506@gndrsh.aac.dev.com> Subject: Re: 2.05R: failure to get fd parameters correctly To: terry@cs.weber.edu (Terry Lambert) Date: Sun, 18 Jun 1995 16:13:19 -0700 (PDT) Cc: guido@gvr.win.tue.nl, gibbs@freefall.cdrom.com, freebsd-bugs@freebsd.org In-Reply-To: <9506182051.AA18733@cs.weber.edu> from "Terry Lambert" at Jun 18, 95 02:51:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2796 Sender: bugs-owner@freebsd.org Precedence: bulk > > > Justin T. Gibbs wrote: > > > >I tried to install 2.05R on a CSSI only system with a 2GB Quantum > > > >EMPIRE_2100S (Btw: dont try this at hoime..that disk sucks) > > > >Anyway: after installing all of it, it failed to boot from the > > > >fixed disk with a missing operating system. > > > >So I tried to reinstall it but now I chang4ed the geomtery to > > > >what 2.0R reported when booting. This just failed. Every key I touched > > > >I got this popu menu shouting that I entered the wrong geometry :-( > > > >I `solved' the problem by adding a dos partition of 1 meg, but this > > > >is bad. I dont want DOS. And I dont understand why I caanot use the geometry > > > >reported by 2.0R when booting for the 2.05R installs... > > > > > > > >-Guido > > > > > > I installed to an Empire 2100 last nigt using the standard Adaptec ^^^^^^^^^^^ Wrong drive Terry, the problems you are discussing are the Quantum Grand Prix series. > > > geometry since it was hanging of a 2742T. What kind of disk controller > > > are you using? > > > > OOps...sorry: > > An ncr 53c810 controller. > > > > This is waht 2.0R thought of it: > > > > sd2: 2006MB (4108600 total sec), 3053 cyl, 12 head, 112 sec, bytes/sec 512 > > The problem with the quantum and the NCR controller is the sequencer > code having a window between checking for other bus users and asserting > bus ownership because it is a fast drive. > > This hole was closed on the Adaptec sequencer code, and the procedural > fix reported to the hackers list. > > I am unsure if the fix has been incorporated into updated NCR sequencer > code -- in fact, I doubt that it has. > > Your current alternatives are: > > 1) Use a non-NCR controller > > 2) Use a different disk that does not exercise the hole. I believe > the hole is exercised by drives that are called "AV drvies". > These drives achieve their faster throughput by not doing thermal > recalibration. This is in fact a terrifically bad hack to get > the desired results, and will definitely increase the failure > rates you'll see when using the drives. > > 3) Go to the Hackers list archives, and using that information > and information obtained from NCR, fix the sequencer code. > Hopefully if you choose this option, you will donate the code > back, both for the rest of the NCR controller owners benefit > and for your own benefit in not having to reintegrate the > changes you make each time the driver is revised. > > > Terry Lambert > terry@cs.weber.edu > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun Jun 18 16:24:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA08488 for bugs-outgoing; Sun, 18 Jun 1995 16:24:33 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA08482 for ; Sun, 18 Jun 1995 16:24:31 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id QAA02555; Sun, 18 Jun 1995 16:23:18 -0700 From: "Rodney W. Grimes" Message-Id: <199506182323.QAA02555@gndrsh.aac.dev.com> Subject: Re: 2.05R reboot hangs To: jan@todonix.ping.de (Jan Wedekind) Date: Sun, 18 Jun 1995 16:23:18 -0700 (PDT) Cc: bugs@freebsd.org In-Reply-To: from "Jan Wedekind" at Jun 19, 95 00:31:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 453 Sender: bugs-owner@freebsd.org Precedence: bulk > > Hi, > > sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). ^^^^^^^^^^^ CHeck that you have your external cache set to write-through mode, and ISA GAT mode disabled in the BIOS setup screens. ... probe stuff deleted ... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun Jun 18 16:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA09159 for bugs-outgoing; Sun, 18 Jun 1995 16:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA09150 ; Sun, 18 Jun 1995 16:40:01 -0700 Date: Sun, 18 Jun 1995 16:40:01 -0700 Message-Id: <199506182340.QAA09150@freefall.cdrom.com> From: peterb@muc.de Reply-To: peterb@muc.de To: freebsd-bugs Subject: misc/531: SCSI Tape Problems In-Reply-To: Your message of Mon, 19 Jun 1995 01:27:27 +0200 <199506182327.BAA00966@fns.muc.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 531 >Category: misc >Synopsis: writing a scsi tape doesn't work >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: support >Submitter-Id: current-users >Arrival-Date: Sun Jun 18 16:40:01 1995 >Originator: Peter Bechtold >Organization: -- >Release: FreeBSD 2.0.5-RELEASE >Environment: 486DX4/100 20MB Ram VL AHA2842 w/ 3 SCSI-I- and 2 SCSI-II-disk drives and 1 SCSI-II-tape drive (Tandberg 3820) >Description: bash# tar cvvf /dev/rst0 commerce.tgz -r--r----- root/wheel 4670570 Jun 9 14:30 1995 commerce.tgz tar: can't write to /dev/rst0 : Input/output error >How-To-Repeat: just try to write anything to the tape read is ok >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Jun 18 16:54:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA10172 for bugs-outgoing; Sun, 18 Jun 1995 16:54:02 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA10166 for ; Sun, 18 Jun 1995 16:54:01 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id QAA17386 for ; Sun, 18 Jun 1995 16:53:11 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id QAA12191 for ; Sun, 18 Jun 1995 16:53:28 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id QAA00309 for bugs@freebsd.org; Sun, 18 Jun 1995 16:52:09 -0700 Date: Sun, 18 Jun 1995 16:52:09 -0700 From: "Russell L. Carter" Message-Id: <199506182352.QAA00309@geli.clusternet> To: bugs@freebsd.org Subject: 2.0.5R crash writing to /dev/rst0 Sender: bugs-owner@freebsd.org Precedence: bulk Either my conner 4326 DAT died at the same time I installed 2.0.5R, or there is a problem with the ncr driver since then. I don't know which it is for sure yet, but I am beginning to suspect 2.0.5R. Here are the symptoms. If I can verify that the drive is ok I will submit it as bug. tar -cvf /dev/rst0 /usr runs for several minutes before "Can't add file: input/output error" messages start spewing to the screen. Eventually, the load goes very high (as evidenced by xload), and access to all file systems is lost. Switching to the console shows continual scrolling of the following messages: sd0(ncr0:1:0):COMMAND FAILED (4 28) @f10f2000 Assertion cp==np->header.cp failed file "../../pci/ncr.c",line 5395. Then either a panic ensues, or hang, if I try to switch back to X. Dropping into the debugger to generate a dump fails because the file systems are hosed. Finally, upon reboot, I have yet to have a problem noticed by fsck. If I don't use the tape the system has yet to crash for the last 9 days. Tarring up large chunks of the file system (using MRS or regular 90m media, 1.2 G file system) tickles the problem every time. Here's dmesg: FreeBSD 2.0.5-ALPHA #0: Thu Jun 15 21:05:46 PDT 1995 rcarter@geli.clusternet:/usr/src/sys/compile/RLCDE CPU: 100-MHz Pentium 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 66715648 (16288 pages) avail memory = 63012864 (15384 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 lpt0 at 0x278-0x27f 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 npx0 on motherboard npx0: INT 16 interface Probing for devices on the pci0 bus: configuration mode 1 allows 32 devices. pci0:0: INTEL CORPORATION, device=0x122d, class=bridge [not supported] pci0:7: INTEL CORPORATION, device=0x122e, class=bridge [not supported] ncr0 rev 2 int a irq 9 on pci0:9 reg20: virtual=0xf58a1000 physical=0xfbfef000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) ncr0 waiting for scsi devices to settle (ncr0:1:0): "SEAGATE ST32550N 0012" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2047MB (4194058 512 byte sectors) (ncr0:3:0): "TEAC CD-ROM CD-50 1.06" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): asynchronous. cd0(ncr0:3:0): UNIT ATTENTION asc:28,0 cd0(ncr0:3:0): Not ready to ready transition, medium may have changed cd present.[400000 x 2048 byte records] (ncr0:6:0): "ARCHIVE 4326XX 27871-XXX 494A" type 1 removable SCSI 2 st0(ncr0:6:0): Sequential-Access st0(ncr0:6:0): 200ns (5 Mb/sec) offset 8. density code 0x13, drive empty vga0 rev 0 int a irq 12 on pci0:10 de0 rev 17 int a irq 10 on pci0:11 reg20: virtual=0xf58a2000 physical=0xfafff000 size=0x80 de0: DC21140 [10-100Mb/s] pass 1.1 Ethernet address 00:00:c0:dd:f7:9d de0: enabling 100baseTX UTP port de1 rev 35 int a irq 11 on pci0:12 reg20: virtual=0xf58a3000 physical=0xfaffe000 size=0x80 de1: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:c0:95:ec:20:ff de1: enabling 10baseT/UTP port pci0: uses 8389120 bytes of memory from faffe000 upto fbfef0ff. pci0: uses 512 bytes of I/O space from d800 upto e4ff. WARNING: / was not properly dismounted. From owner-freebsd-bugs Sun Jun 18 17:23:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11432 for bugs-outgoing; Sun, 18 Jun 1995 17:23:43 -0700 Received: from mpp.com (mpp.Minn.Net [204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA11424 for ; Sun, 18 Jun 1995 17:23:40 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id TAA23766; Sun, 18 Jun 1995 19:22:39 -0500 From: Mike Pritchard Message-Id: <199506190022.TAA23766@mpp.com> Subject: Re: misc/531: SCSI Tape Problems To: peterb@muc.de Date: Sun, 18 Jun 1995 19:22:38 -0500 (CDT) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506182340.QAA09150@freefall.cdrom.com> from "peterb@muc.de" at Jun 18, 95 04:40:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 919 Sender: bugs-owner@FreeBSD.org Precedence: bulk > >Release: FreeBSD 2.0.5-RELEASE > >Environment: > > 486DX4/100 20MB Ram VL > AHA2842 w/ 3 SCSI-I- and 2 SCSI-II-disk drives and > 1 SCSI-II-tape drive (Tandberg 3820) > > >Description: > > bash# tar cvvf /dev/rst0 commerce.tgz > -r--r----- root/wheel 4670570 Jun 9 14:30 1995 commerce.tgz > tar: can't write to /dev/rst0 : Input/output error > > >How-To-Repeat: > > just try to write anything to the tape > read is ok Does it do this all of the time? I've got the same controller (2842) with an Archive 2150S SCSI-I tape drive, and sometimes the first attempt to write to the drive after a boot fails in the above manner. At the same time I also see a console message that says: st0: bad request, must be between 0 and 0 Immediately retrying the failed command usually works just fine. -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-bugs Sun Jun 18 17:37:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11880 for bugs-outgoing; Sun, 18 Jun 1995 17:37:24 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA11873 for ; Sun, 18 Jun 1995 17:37:23 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id RAA18742; Sun, 18 Jun 1995 17:36:33 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id RAA21856; Sun, 18 Jun 1995 17:36:49 -0701 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id RAA00411; Sun, 18 Jun 1995 17:35:30 -0700 Date: Sun, 18 Jun 1995 17:35:30 -0700 From: "Russell L. Carter" Message-Id: <199506190035.RAA00411@geli.clusternet> To: mpp@legarto.minn.net, peterb@muc.de Subject: Re: misc/531: SCSI Tape Problems Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk |Does it do this all of the time? I've got the same controller (2842) |with an Archive 2150S SCSI-I tape drive, and sometimes the first |attempt to write to the drive after a boot fails in the above manner. |At the same time I also see a console message that says: | |st0: bad request, must be between 0 and 0 | |Immediately retrying the failed command usually works just fine. I get the same single error, but then retrying leads to the hang I described in my email. The initial writing messages look fine. But I'm using the ncr, hmm. Maybe it's not the controller? Russell |-- |Mike Pritchard |mpp@legarto.minn.net |"Go that way. Really fast. If something gets in your way, turn" | | From owner-freebsd-bugs Sun Jun 18 17:37:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA11939 for bugs-outgoing; Sun, 18 Jun 1995 17:37:45 -0700 Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA11933 for ; Sun, 18 Jun 1995 17:37:42 -0700 Received: from fns.muc.de ([193.174.4.223]) by colin.muc.de with SMTP id <25539-3>; Mon, 19 Jun 1995 02:37:28 +0200 Received: (from peterb@localhost) by fns.muc.de (8.6.11/8.6.9) id CAA01575; Mon, 19 Jun 1995 02:28:36 +0200 Date: Mon, 19 Jun 1995 02:28:34 +0200 From: Peter Bechtold To: Mike Pritchard cc: freebsd-bugs@freefall.cdrom.com Subject: Re: misc/531: SCSI Tape Problems In-Reply-To: <199506190022.TAA23766@mpp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk No, trying again brings the same result. (Actually, my tape reacted like described above w/ 2.0R, but not anymore ...) Peter -- # Peter Bechtold # peterb@muc.de # Tel./Fax (+49 / 0) 89 / 542 0774 # On Mon, 19 Jun 1995, Mike Pritchard wrote: > > >Release: FreeBSD 2.0.5-RELEASE > > >Environment: > > > > 486DX4/100 20MB Ram VL > > AHA2842 w/ 3 SCSI-I- and 2 SCSI-II-disk drives and > > 1 SCSI-II-tape drive (Tandberg 3820) > > > > >Description: > > > > bash# tar cvvf /dev/rst0 commerce.tgz > > -r--r----- root/wheel 4670570 Jun 9 14:30 1995 commerce.tgz > > tar: can't write to /dev/rst0 : Input/output error > > > > >How-To-Repeat: > > > > just try to write anything to the tape > > read is ok > > Does it do this all of the time? I've got the same controller (2842) > with an Archive 2150S SCSI-I tape drive, and sometimes the first > attempt to write to the drive after a boot fails in the above manner. > At the same time I also see a console message that says: > > st0: bad request, must be between 0 and 0 > > Immediately retrying the failed command usually works just fine. > -- > Mike Pritchard > mpp@legarto.minn.net > "Go that way. Really fast. If something gets in your way, turn" > From owner-freebsd-bugs Sun Jun 18 18:17:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA13892 for bugs-outgoing; Sun, 18 Jun 1995 18:17:02 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA13882 ; Sun, 18 Jun 1995 18:17:00 -0700 Message-Id: <199506190117.SAA13882@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Eric Chet cc: davidg@root.com, bugs@freebsd.org Subject: Re: Release 2.0.5 with Updated boot.flp In-reply-to: Your message of "Sun, 18 Jun 95 16:16:30 EDT." <199506182016.QAA17830@bronze.coil.com> Date: Sun, 18 Jun 1995 18:17:00 -0700 From: "Justin T. Gibbs" Sender: bugs-owner@freebsd.org Precedence: bulk >> >> >the /usr mount was lost on either shutdown or boot up. It would work for >> >awhile, maybe a dozen cycles of bootup then it would loose /usr mount. I >> >> Can you explain what you mean by "would lose the /usr mount"? I really ha >ve >> no idea what you're talking about. Do you mean that there is some sort of >> filesystem corruption? If so, could you be more specific? >> >> -DG >> > >I think I know what he is talking about. I booted up my machine two days >ago, and the /usr was not mounted. Actually it was like it did not exist. >Any ideas, this is on 2.0.5R the latest boot.flp. > >Eric -- echet@coil.com Could this at all be related to my experience two nights ago? Compiling a "-g"'d kernel and suddenly processes start dying with sig 6,9,10, or 11. Halt the system and reboot, and fsck eats /usr causing any future mounts to state that the superblock is bad. A fsck -b fails to find alternate superblocks. Fsck also did a good job of killing 95% of my data on partitions that weren't even active during the failure. I really believe that either fsck was not moddified correctly when the immutible flags were added to the filesystems, or is in general too agressive when performing clean up, and now, you can't even mount a partition that is dirty to attempt to recover data before going to fsck. End result was a total re-install on my home system (any thing of importance disapeared without even a trace in the lost+found directory), but I will say that the single floppy install over PPP was nice. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Sun Jun 18 18:45:52 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15428 for bugs-outgoing; Sun, 18 Jun 1995 18:45:52 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id SAA15422 for ; Sun, 18 Jun 1995 18:45:50 -0700 Received: from server.cs.virginia.edu by uvaarpa.virginia.edu id aa23537; 18 Jun 95 21:45 EDT Received: from mamba.cs.Virginia.EDU (mamba-fo.cs.Virginia.EDU) by uvacs.cs.virginia.edu (4.1/5.1.UVA) id AA19712; Sun, 18 Jun 95 21:45:41 EDT Posted-Date: Sun, 18 Jun 1995 21:45:42 -0400 (EDT) Received: by mamba.cs.Virginia.EDU (5.x/SMI-2.0) id AA06594; Sun, 18 Jun 1995 21:45:42 -0400 Date: Sun, 18 Jun 1995 21:45:42 -0400 (EDT) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: bugs@freebsd.org Subject: /usr/src/bin (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk Resent because of local mail problems. You should have received this, but I can't know for sure. I certainly lost any reply. Adrian adrian@virginia.edu ---->>>>| Support your local programmer, http://www.cs.virginia.edu/~atf3r/ --->>>| STOP Software Patent Abuses NOW! Member: The League for -->>| info at ftp.uu.net:/doc/lpf, print Programming Freedom ->| "join.ps.Z" for an application ---------- Forwarded message ---------- Date: Sat, 17 Jun 1995 12:19:45 -0400 (EDT) From: Adrian T. Filipi-Martin To: bugs@freebsd.org Subject: /usr/src/bin Hi folks, Unless I am hallucinating, 2.0.5-RELEASE does not install the sources for /bin. I checked the release/sysinstall/dist.{h,c} files, and find no mention of sbin.* in the source distributions section. The oversight seems to have carried over to menu.c as well. It appears that by adding a single line to menu.c, dist.h and dist.c for the sbin distribution fixes the problem. Appended is a small diff of what I changed. Note that I also made a couple of minor changes to install.c, such that sysinstall could safely be run at a later time to add distributions without destroying your devices or extracting the root.flp. These latter changes are not thoroughly thought through, so work still needs to be done to make sysinstall safe. BTW, the release sources also have object files packed in there. They survive a 'make cleandist', so this is probably the root of the problem. cheers, Adrian adrian@virginia.edu ---->>>>| Support your local programmer, http://www.cs.virginia.edu/~atf3r/ --->>>| STOP Software Patent Abuses NOW! Member: The League for -->>| info at ftp.uu.net:/doc/lpf, print Programming Freedom ->| "join.ps.Z" for an application -------------------------------------------------------------- diff -cr release/sysinstall/dist.c release.new/sysinstall/dist.c *** release/sysinstall/dist.c Sat Jun 10 05:35:49 1995 --- release.new/sysinstall/dist.c Sat Jun 17 10:50:13 1995 *************** *** 104,109 **** --- 104,110 ---- { "slibexec", "/usr/src", &SrcDists, DIST_SRC_LIBEXEC, NULL }, { "slkm", "/usr/src", &SrcDists, DIST_SRC_LKM, NULL }, { "srelease", "/usr/src", &SrcDists, DIST_SRC_RELEASE, NULL }, + { "sbin", "/usr/src", &SrcDists, DIST_SRC_BIN, NULL }, { "ssbin", "/usr/src", &SrcDists, DIST_SRC_SBIN, NULL }, { "sshare", "/usr/src", &SrcDists, DIST_SRC_SHARE, NULL }, { "ssys", "/usr/src", &SrcDists, DIST_SRC_SYS, NULL }, diff -cr release/sysinstall/dist.h release.new/sysinstall/dist.h *** release/sysinstall/dist.h Sat Jun 10 04:59:20 1995 --- release.new/sysinstall/dist.h Sat Jun 17 10:48:59 1995 *************** *** 46,51 **** --- 46,52 ---- #define DIST_SRC_SYS 0x0800 #define DIST_SRC_UBIN 0x1000 #define DIST_SRC_USBIN 0x2000 + #define DIST_SRC_BIN 0x4000 #define DIST_SRC_ALL 0xFFFF /* Subtypes for XFree86 distribution */ diff -cr release/sysinstall/install.c release.new/sysinstall/install.c *** release/sysinstall/install.c Sat Jun 10 03:58:37 1995 --- release.new/sysinstall/install.c Sat Jun 17 11:39:17 1995 *************** *** 271,277 **** return 0; configFstab(); } ! if (!SystemWasInstalled && !root_extract()) { msgConfirm("Failed to load the ROOT distribution. Please correct\nthis problem and try again."); return 0; } --- 271,277 ---- return 0; configFstab(); } ! if (RunningAsInit && !SystemWasInstalled && !root_extract()) { msgConfirm("Failed to load the ROOT distribution. Please correct\nthis problem and try again."); return 0; } *************** *** 290,296 **** } /* Resurrect /dev after bin distribution screws it up */ ! if (!SystemWasInstalled) { msgNotify("Remaking all devices.. Please wait!"); if (vsystem("cd /dev; sh MAKEDEV all")) msgConfirm("MAKEDEV returned non-zero status"); --- 290,296 ---- } /* Resurrect /dev after bin distribution screws it up */ ! if (RunningAsInit && !SystemWasInstalled) { msgNotify("Remaking all devices.. Please wait!"); if (vsystem("cd /dev; sh MAKEDEV all")) msgConfirm("MAKEDEV returned non-zero status"); diff -cr release/sysinstall/menus.c release.new/sysinstall/menus.c *** release/sysinstall/menus.c Sat Jun 10 04:59:24 1995 --- release.new/sysinstall/menus.c Sat Jun 17 11:19:55 1995 *************** *** 457,462 **** --- 457,464 ---- DMENU_SET_FLAG, &SrcDists, DIST_SRC_LKM, 0, dmenuFlagCheck }, { "release", "/usr/src/release (release-generation tools) [533K]", DMENU_SET_FLAG, &SrcDists, DIST_SRC_RELEASE, 0, dmenuFlagCheck }, + { "bin", "/usr/src/bin (system binaries) [???MB]", + DMENU_SET_FLAG, &SrcDists, DIST_SRC_BIN, 0, dmenuFlagCheck }, { "sbin", "/usr/src/sbin (system binaries) [1.3MB]", DMENU_SET_FLAG, &SrcDists, DIST_SRC_SBIN, 0, dmenuFlagCheck }, { "share", "/usr/src/share (documents and shared files) [10MB]", From owner-freebsd-bugs Sun Jun 18 18:58:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15854 for bugs-outgoing; Sun, 18 Jun 1995 18:58:26 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA15848 ; Sun, 18 Jun 1995 18:58:23 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id SAA04855; Sun, 18 Jun 1995 18:58:22 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id SAA00913; Sun, 18 Jun 1995 18:58:40 -0700 Message-Id: <199506190158.SAA00913@corbin.Root.COM> To: "Justin T. Gibbs" cc: Eric Chet , bugs@freebsd.org Subject: Re: Release 2.0.5 with Updated boot.flp In-reply-to: Your message of "Sun, 18 Jun 95 18:17:00 PDT." <199506190117.SAA13882@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 18 Jun 1995 18:58:38 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk >and now, you can't even mount a partition that is dirty to attempt to >recover data before going to fsck. End result was a total re-install Sure you can. "mount -f". -DG From owner-freebsd-bugs Sun Jun 18 20:20:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA18868 for bugs-outgoing; Sun, 18 Jun 1995 20:20:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA18861 ; Sun, 18 Jun 1995 20:20:03 -0700 Date: Sun, 18 Jun 1995 20:20:03 -0700 Message-Id: <199506190320.UAA18861@freefall.cdrom.com> From: Charlie Root Reply-To: Charlie Root To: freebsd-bugs Subject: kern/532: FreeBSD hangs with my BT445s In-Reply-To: Your message of Sun, 18 Jun 1995 16:51:10 +0200 <199506181451.QAA00677@amelie.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 532 >Category: kern >Synopsis: buslogic bt 445S hangups wit FreeBSD 2.0.5 >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: support >Submitter-Id: current-users >Arrival-Date: Sun Jun 18 20:20:02 1995 >Originator: Erwan Arzur >Organization: >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5R Amd 486DX4 100 w 16 Mb RAM bt0 : buslogic 445S Firm. Rev. 3.37 sd0 : Micropolis 1 Go wd0 : Seagate 540 Mb wd1 : WD Caviar 210 Mb st0 : Tandberg TDC 3800 525 Mb DC 6525 Tape drive This configuration was smoothly working with FreeBSD 1.1.5.1 using the bt-742a-32.c driver ... >Description: FreeBSD works well with this configuration until i try to extract some data from my tape drive. After some time (during this all seems to be OK) the board seems to be locked, not responding to commands ... The kernel output is : bt0 : biodone : buffer already done (repeated 2 or 3 times) and then bt0 not responding ... I am there unable to read or write any data to the drive and i must then push the Big Red Button ... After rebooting, the file systems are broken and i loose a lot of data :-) >How-To-Repeat: try to extract the 3rd file of a tape (mt fsf 2) if the files are quite big ... it happens ! it happened to me only during a file skipping session on the tape drive, but i think a big restore or tar will reproduce it ... >Fix: ??? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Jun 18 23:24:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA28547 for bugs-outgoing; Sun, 18 Jun 1995 23:24:19 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA28541 for ; Sun, 18 Jun 1995 23:24:17 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10668; Mon, 19 Jun 1995 08:24:14 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA16926; Mon, 19 Jun 1995 08:24:13 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA09188; Mon, 19 Jun 1995 08:20:21 +0200 From: J Wunsch Message-Id: <199506190620.IAA09188@uriah.heep.sax.de> Subject: Re: misc/530: Failed install from SCSI tape To: deischen@iworks.InterWorks.org Date: Mon, 19 Jun 1995 08:20:20 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506182030.NAA01859@freefall.cdrom.com> from "deischen@iworks.InterWorks.org" at Jun 18, 95 01:30:02 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 567 Sender: bugs-owner@FreeBSD.org Precedence: bulk As deischen@iworks.InterWorks.org wrote: > > > Either fix the documentation (?) or the SCSI tape driver. Correcting the > documentation is simple, but it seems like you'd really like to be able > to handle tapes of default block size. This is not a problem with the SCSI driver -- it can handle all tape block sizes your tape drive can. It's just an oversight (IMHO) in the documentation for the installation process. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Jun 19 00:20:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00738 for bugs-outgoing; Mon, 19 Jun 1995 00:20:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00728 ; Mon, 19 Jun 1995 00:20:01 -0700 Date: Mon, 19 Jun 1995 00:20:01 -0700 Message-Id: <199506190720.AAA00728@freefall.cdrom.com> From: darrylo@sr.hp.com Reply-To: darrylo@sr.hp.com To: freebsd-bugs Subject: misc/533: typo prevents send-pr info from being accessed In-Reply-To: Your message of Mon, 19 Jun 1995 00:11:10 -0700 <199506190711.AA199185870@hpnmhjw.sr.hp.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 533 >Category: misc >Synopsis: typo prevents send-pr info from being accessed >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 19 00:20:00 1995 >Originator: Darryl Okahata >Organization: At Home >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 2.0.5R >Description: When you run "info", the description for send-pr looks something like: * Send-PR: (send-pr): Manual for the system used to send problem reports or contributions back to the FreeBSD maintainers. The ":" after "(send-pr)" prevents info from locating the info for send-pr. >How-To-Repeat: Run "info" and try to access the docs for "send-pr". >Fix: Change the ":" to ".". >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Jun 19 00:20:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00760 for bugs-outgoing; Mon, 19 Jun 1995 00:20:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA00742 ; Mon, 19 Jun 1995 00:20:02 -0700 Date: Mon, 19 Jun 1995 00:20:02 -0700 Message-Id: <199506190720.AAA00742@freefall.cdrom.com> From: darrylo@sr.hp.com Reply-To: darrylo@sr.hp.com To: freebsd-bugs Subject: bin/534: chmod doesn't work through symlinks In-Reply-To: Your message of Mon, 19 Jun 1995 00:11:06 -0700 <199506190711.AA199165866@hpnmhjw.sr.hp.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 534 >Category: bin >Synopsis: chmod doesn't work through symlinks >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 19 00:20:01 1995 >Originator: Darryl Okahata >Organization: At Home >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 2.0.5R, default installed kernel >Description: File permissions cannot be changed if a file is referenced via a symlink. >How-To-Repeat: Script started on Sun Jun 18 23:28:04 1995 bash$ mkdir t bash$ cd t bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. bash$ touch .x bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:28 .x bash$ ln -s .x .y bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:28 .y -> .x bash$ chmod 755 .y bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:28 .x ^^^^^^^^^^ Permissions did not change lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:28 .y -> .x bash$ chmod 755 .x bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x ^^^^^^^^^^ This changed. lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:28 .y -> .x bash$ chmod 644 .y bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:28 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x ^^^^^^^^^^ No change. lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:28 .y -> .x bash$ touch foo bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:29 .y -> .x -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:29 foo bash$ ln -s foo yuk bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:29 .y -> .x -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:29 foo lrwxr-xr-x 1 darrylo xxx 3 Jun 18 23:29 yuk -> foo bash$ chmod 755 yuk bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:29 .y -> .x -rw-r--r-- 1 darrylo xxx 0 Jun 18 23:29 foo lrwxr-xr-x 1 darrylo xxx 3 Jun 18 23:29 yuk -> foo bash$ chmod 755 foo bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:29 .y -> .x -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:29 foo lrwxr-xr-x 1 darrylo xxx 3 Jun 18 23:29 yuk -> foo bash$ chmod 644 yuk bash$ ls -la total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x lrwxr-xr-x 1 darrylo xxx 2 Jun 18 23:29 .y -> .x -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:29 foo lrwxr-xr-x 1 darrylo xxx 3 Jun 18 23:29 yuk -> foo bash$ ls -laL total 4 drwxr-xr-x 2 darrylo xxx 512 Jun 18 23:29 . drwxr-xr-x 3 darrylo xxx 512 Jun 18 23:28 .. -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .x -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:28 .y -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:29 foo -rwxr-xr-x 1 darrylo xxx 0 Jun 18 23:29 yuk bash$ exit Script done on Sun Jun 18 23:30:08 1995 >Fix: None >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Jun 19 03:39:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA09131 for bugs-outgoing; Mon, 19 Jun 1995 03:39:20 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA09115 for ; Mon, 19 Jun 1995 03:39:08 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA30605 for bugs@freebsd.org; Mon, 19 Jun 1995 20:36:03 +1000 Date: Mon, 19 Jun 1995 20:36:03 +1000 From: Bruce Evans Message-Id: <199506191036.UAA30605@godzilla.zeta.org.au> To: bugs@freebsd.org Subject: bogus release version string Sender: bugs-owner@freebsd.org Precedence: bulk In bug reports we get release version strings like Release: FreeBSD 2.0-BUILT-19950603 i386 1. This provides very little information about the version - it might be for plain 2.0 built late or for 2.2 built early. 2. The current version isn't 2.0 or 2.1, it's pre-2.2. Bruce From owner-freebsd-bugs Mon Jun 19 04:51:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA13209 for bugs-outgoing; Mon, 19 Jun 1995 04:51:26 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA13197 for ; Mon, 19 Jun 1995 04:51:17 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id NAA26300 ; Mon, 19 Jun 1995 13:51:14 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id NAA18754 ; Mon, 19 Jun 1995 13:51:13 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199506191151.NAA18754@blaise.ibp.fr> Subject: Re: bogus release version string To: bde@zeta.org.au (Bruce Evans) Date: Mon, 19 Jun 1995 13:51:13 +0200 (MET DST) Cc: bugs@freebsd.org In-Reply-To: <199506191036.UAA30605@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 08:36:03 pm X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 686 Sender: bugs-owner@freebsd.org Precedence: bulk > Release: FreeBSD 2.0-BUILT-19950603 i386 > > 1. This provides very little information about the version - it might be > for plain 2.0 built late or for 2.2 built early. > > 2. The current version isn't 2.0 or 2.1, it's pre-2.2. I don't think putting the _build_ date in the version is a good idea. I rather liked the 2.1-Development one. Build date is in the rest of uname output so why duplicate it ? Especially when the build date has nothing to do with the sources dates... Better to put 2.2-Development there IMO. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-bugs Mon Jun 19 05:53:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA14520 for bugs-outgoing; Mon, 19 Jun 1995 05:53:06 -0700 Received: from epcc.ed.ac.uk (root@daedalus.epcc.ed.ac.uk [129.215.56.21]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA14472 for ; Mon, 19 Jun 1995 05:51:07 -0700 Message-Id: <1193.9506191250@subnode.epcc.ed.ac.uk> Subject: syscons UK keyboard map bug To: bugs@freebsd.org Date: Mon, 19 Jun 1995 13:50:06 +0100 (BST) From: Scott Telford X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1048 Sender: bugs-owner@freebsd.org Precedence: bulk The syscons UK keyboard map ("uk.iso.kbd") in 2.0.5 has a "\" where it should have a "`", judging from the UK-layout keybards I've seen. Here's a patch: --- uk.iso.kbd_orig Sat Jun 10 10:58:32 1995 +++ uk.iso.kbd Fri Jun 16 22:03:15 1995 @@ -43,7 +43,7 @@ 038 'l' 'L' ff ff 'l' 'L' ff ff C 039 ';' ':' nop nop ';' ':' nop nop O 040 ''' '@' nul nul ''' '@' nul nul O - 041 '\' '|' fs fs '\' '\' fs fs O + 041 '`' '|' fs fs '\' '\' fs fs O 042 lshift lshift lshift lshift lshift lshift lshift lshift O 043 '#' '~' nop nop '~' '~' nop nop O 044 'z' 'Z' sub sub 'z' 'Z' sub sub C -- Scott Telford, Edinburgh Parallel Computing Centre, University of Edinburgh, Mayfield Rd, Edinburgh, EH9 3JZ, UK.(+44 131 650 5978) -- "We do want to tour again, we will tour again" - Kate Bush, Munich, 1980. -- From owner-freebsd-bugs Mon Jun 19 05:59:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA14838 for bugs-outgoing; Mon, 19 Jun 1995 05:59:12 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA14828 for ; Mon, 19 Jun 1995 05:59:08 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA02612; Mon, 19 Jun 1995 22:55:16 +1000 Date: Mon, 19 Jun 1995 22:55:16 +1000 From: Bruce Evans Message-Id: <199506191255.WAA02612@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org, terry@cs.weber.edu Sender: bugs-owner@FreeBSD.org Precedence: bulk >Okay.... here is the output if I let the Ontrack DM load the dynamic >overlay and then use the option to boot from the boot.flp. >If I choose wd(1,a)/kernel.GENERIC -v >FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 >... >wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S >... >wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S >... >changing root device to wd1a >BIOS Geometries: > 0:03391f3f 825 cyl, 31 heads, 63 sects > 1:03fd0f3f 1021 cyl, 15 heads, 63 sects > 0 accounted for >wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK This all seems OK. >------------ >Notice that no where in the boot process does it mention about the >Ontrack DM. This is OK. wd0 isn't looked at since your'e not trying to boot from it, so Ontrack isn't seen to be on it. It would be seen when the DOS partition is mounted if you got that far. Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am >not supposed to)... >It shows these extra lines after the "0 accounted for" >wd0: Found "Ontrack Disk Manager" on this disk. >wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK >panic: cannot mount root This is normal. hd(1,a) becomes wd0a, which you don't have, but Ontrack gets noticed when wd0 is looked at in the failed attempt to open wd0a. Bruce From owner-freebsd-bugs Mon Jun 19 06:19:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA15541 for bugs-outgoing; Mon, 19 Jun 1995 06:19:34 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA15524 for ; Mon, 19 Jun 1995 06:19:25 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA03425; Mon, 19 Jun 1995 23:16:11 +1000 Date: Mon, 19 Jun 1995 23:16:11 +1000 From: Bruce Evans Message-Id: <199506191316.XAA03425@godzilla.zeta.org.au> To: hlew@genome.Stanford.EDU, terry@cs.weber.edu Subject: Re: 2.05R panics on boot Cc: bde@zeta.org.au, bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >Okay, if boot from DOS (and with no Ontrack DM installed)... here's the >output from pfdisk 0 (the 850MB Ontrack DM DOS Drive) and pfdisk 1 (540 >MB FreeBSD drive) ># Partition table on device: 0 >geometry 1024 16 63 (cyls heads sectors) ># ID First(cyl) Last(cyl) Name # start, length (sectors) >1 84 0 1652 unkno # 1, 1666223 ># note: last(1): phys=(628,15,63) logical=(1652,15,63) ># note: first(1): phys=(0,0,2) should be (0,1,1) >2 0 0 0 empty # 0, 0 >3 0 0 0 empty # 0, 0 >4 0 0 0 empty # 0, 0 This is OK (except the `should be' note shouldn't be). ># Partition table on device: 1 >geometry 1022 16 63 (cyls heads sectors) ># ID First(cyl) Last(cyl) Name # start, length (sectors) >1 165 0 1052 unkno # 63, 1061361 ># note: last(1): phys=(1023,15,63) logical=(1052,15,63) >2 0 0 0 empty # 0, 0 >3 0 0 0 empty # 0, 0 >4 0 0 0 empty # 0, 0 OK, but several other things will have to be right to handle the partition extending beyond cylinder 1024: 1) The BSD boot partition (normally wd1a) must not extend beyond cylinder 1024. 2) bad144 must not be used. 3) The boot manager must not object to booting such partitions. I think the OS/2 boot manager would object. >--------- >Now if I boot from the hard drive with Ontrack DM's dynamic drive overlay >installed... ># Partition table on device: 0 >geometry 826 32 63 (cyls heads sectors) ># ID First(cyl) Last(cyl) Name # start, length (sectors) >1 1 0 825 DOS12 # 63, 1665153 >2 0 0 0 empty # 0, 0 >3 0 0 0 empty # 0, 0 >4 0 0 0 empty # 0, 0 This is OK. ># Partition table on device: 1 >geometry 1022 16 63 (cyls heads sectors) ># ID First(cyl) Last(cyl) Name # start, length (sectors) >1 165 0 1052 unkno # 63, 1061361 ># note: last(1): phys=(1023,15,63) logical=(1052,15,63) >2 0 0 0 empty # 0, 0 >3 0 0 0 empty # 0, 0 >4 0 0 0 empty # 0, 0 OK. >So it appears that nothing changes on the 540MB drive that doesn't use >Ontrack DM. So any ideas? The problem seems to have nothing to do with disk manager. Maybe your boot manager objects to partitions extending beyond cylinder 1024. Bruce From owner-freebsd-bugs Mon Jun 19 06:39:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA16964 for bugs-outgoing; Mon, 19 Jun 1995 06:39:05 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA16957 for ; Mon, 19 Jun 1995 06:39:00 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA04073; Mon, 19 Jun 1995 23:37:45 +1000 Date: Mon, 19 Jun 1995 23:37:45 +1000 From: Bruce Evans Message-Id: <199506191337.XAA04073@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> DOS has no problems handling >= 504 MB. This is a BIOS problem. >This is strange because I can configure the bios for 32 heads and over >800 Megs, but if I do a fdisk, DOS says the maximum partition size is 504 MB. This _is_ strange. How do you know that you can configure the BIOS like this. I only have old BIOS's that allow you to enter 32 heads in setup but don't actually support 32 heads. Bruce From owner-freebsd-bugs Mon Jun 19 06:56:16 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA17888 for bugs-outgoing; Mon, 19 Jun 1995 06:56:16 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA17876 for ; Mon, 19 Jun 1995 06:56:09 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA04517; Mon, 19 Jun 1995 23:50:16 +1000 Date: Mon, 19 Jun 1995 23:50:16 +1000 From: Bruce Evans Message-Id: <199506191350.XAA04517@godzilla.zeta.org.au> To: hlew@genome.Stanford.EDU, terry@cs.weber.edu Subject: Re: 2.05R panics on boot Cc: bde@zeta.org.au, bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> So it appears that nothing changes on the 540MB drive that doesn't use >> Ontrack DM. So any ideas? >Yes. The information above is sufficient, barring an error in the >interpretation of the geometry by BSD, to get you installed correctly >and booting BSD off the second drive using OS-BS. Er, why are we discussing OS-BS? FreeBSD's sysinstall supports only bteasy, and someone reported that OS-BS doesn't support booting from drives other than the first. If you decide to install a boot manager, then it must be installed on the first drive. Where does FreeBSD put it if you install FreeBSD on the second drive? Bruce From owner-freebsd-bugs Mon Jun 19 08:40:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA24342 for bugs-outgoing; Mon, 19 Jun 1995 08:40:38 -0700 Received: from space.physics.uiowa.edu (hobbes.physics.uiowa.edu [128.255.32.77]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA24336 for ; Mon, 19 Jun 1995 08:40:35 -0700 Received: from chip.physics.uiowa.edu by space.physics.uiowa.edu (5.x/SMI-SVR4) id AA28609; Mon, 19 Jun 1995 10:40:32 -0500 Received: by chip.physics.uiowa.edu (5.x/SMI-SVR4) id AA01055; Mon, 19 Jun 1995 10:40:30 -0500 Date: Mon, 19 Jun 1995 10:40:30 -0500 From: ljg@space.physics.uiowa.edu (Larry Granroth) Message-Id: <9506191540.AA01055@chip.physics.uiowa.edu> To: bugs@freebsd.org Subject: class C network with a 255 octet X-Sun-Charset: US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk Help! I cannot install FreeBSD 2.0.5-RELEASE via ftp or nfs because the installation program won't accept my (totally valid) network addresses: gateway: 128.255.32.1 router.physics.uiowa.edu nameserver: 128.255.32.77 hobbes.physics.uiowa.edu ftpserver: 128.255.32.166 chip.physics.uiowa.edu target: 128.255.32.77 ljgpc.physics.uiowa.edu My guess is it is (incorrectly) complaining about the 255's above. Thanks in advance for your help. -Larry larry-granroth@uiowa.edu From owner-freebsd-bugs Mon Jun 19 08:57:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA25333 for bugs-outgoing; Mon, 19 Jun 1995 08:57:22 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA25298 for ; Mon, 19 Jun 1995 08:57:16 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA04155; Mon, 19 Jun 1995 17:57:11 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA20448; Mon, 19 Jun 1995 17:57:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id IAA09424; Mon, 19 Jun 1995 08:25:02 +0200 From: J Wunsch Message-Id: <199506190625.IAA09424@uriah.heep.sax.de> Subject: Re: misc/531: SCSI Tape Problems To: peterb@muc.de (Peter Bechtold) Date: Mon, 19 Jun 1995 08:25:01 +0200 (MET DST) Cc: mpp@legarto.minn.net, freebsd-bugs@freefall.cdrom.com In-Reply-To: from "Peter Bechtold" at Jun 19, 95 02:28:34 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 431 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Peter Bechtold wrote: > > No, trying again brings the same result. > (Actually, my tape reacted like described above w/ 2.0R, but not > anymore ...) Does this mean the problem does no longer exist??? In case it's still valid: what are the console messages from the SCSI subsystem? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Jun 19 09:08:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA26048 for bugs-outgoing; Mon, 19 Jun 1995 09:08:30 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA26033 for ; Mon, 19 Jun 1995 09:08:27 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA01169; Mon, 19 Jun 1995 09:07:30 -0700 From: "Rodney W. Grimes" Message-Id: <199506191607.JAA01169@gndrsh.aac.dev.com> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Mon, 19 Jun 1995 09:07:30 -0700 (PDT) Cc: bugs@FreeBSD.org In-Reply-To: <199506191255.WAA02612@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 10:55:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1611 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > >Okay.... here is the output if I let the Ontrack DM load the dynamic > >overlay and then use the option to boot from the boot.flp. > > >If I choose wd(1,a)/kernel.GENERIC -v > > >FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 > >... > >wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S > >... > >wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S > >... > >changing root device to wd1a > >BIOS Geometries: > > 0:03391f3f 825 cyl, 31 heads, 63 sects > > 1:03fd0f3f 1021 cyl, 15 heads, 63 sects > > 0 accounted for > >wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK > > This all seems OK. > > >------------ > >Notice that no where in the boot process does it mention about the > >Ontrack DM. > > This is OK. wd0 isn't looked at since your'e not trying to boot > from it, so Ontrack isn't seen to be on it. It would be seen when the > DOS partition is mounted if you got that far. > > Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am > >not supposed to)... > > >It shows these extra lines after the "0 accounted for" > >wd0: Found "Ontrack Disk Manager" on this disk. > >wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK > >panic: cannot mount root > > This is normal. hd(1,a) becomes wd0a, which you don't have, but > Ontrack gets noticed when wd0 is looked at in the failed attempt to > open wd0a. I think you really meant to say ``hd(1,a) becomes sd0a, which...'' -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Mon Jun 19 09:34:52 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA27839 for bugs-outgoing; Mon, 19 Jun 1995 09:34:52 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA27828 for ; Mon, 19 Jun 1995 09:34:48 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA09759; Tue, 20 Jun 1995 02:31:08 +1000 Date: Tue, 20 Jun 1995 02:31:08 +1000 From: Bruce Evans Message-Id: <199506191631.CAA09759@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >From rgrimes@gndrsh.aac.dev.com Tue Jun 20 02:09:41 1995 >Received: from gndrsh.aac.dev.com ([198.145.92.241]) by godzilla.zeta.org.au (8.6.9/8.6.9) with ESMTP id CAA09000 for ; Tue, 20 Jun 1995 02:08:16 +1000 >Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA01169; Mon, 19 Jun 1995 09:07:30 -0700 >From: "Rodney W. Grimes" >Message-Id: <199506191607.JAA01169@gndrsh.aac.dev.com> >Subject: Re: 2.05R panics on boot >To: bde@zeta.org.au (Bruce Evans) >Date: Mon, 19 Jun 1995 09:07:30 -0700 (PDT) >Cc: bugs@FreeBSD.org >In-Reply-To: <199506191255.WAA02612@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 10:55:16 pm >X-Mailer: ELM [version 2.4 PL24] >MIME-Version: 1.0 >Content-Type: text/plain; charset=US-ASCII >Content-Transfer-Encoding: 7bit >Content-Length: 1611 >> >> >Okay.... here is the output if I let the Ontrack DM load the dynamic >> >overlay and then use the option to boot from the boot.flp. >> >> >If I choose wd(1,a)/kernel.GENERIC -v >> >> >FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 >> >... >> >wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S >> >... >> >wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S >> >... >> >changing root device to wd1a >> >BIOS Geometries: >> > 0:03391f3f 825 cyl, 31 heads, 63 sects >> > 1:03fd0f3f 1021 cyl, 15 heads, 63 sects >> > 0 accounted for >> >wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK >> >> This all seems OK. >> >> >------------ >> >Notice that no where in the boot process does it mention about the >> >Ontrack DM. >> >> This is OK. wd0 isn't looked at since your'e not trying to boot >> from it, so Ontrack isn't seen to be on it. It would be seen when the >> DOS partition is mounted if you got that far. >> Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am >> >not supposed to)... >> >> >It shows these extra lines after the "0 accounted for" >> >wd0: Found "Ontrack Disk Manager" on this disk. >> >wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK >> >panic: cannot mount root >> >> This is normal. hd(1,a) becomes wd0a, which you don't have, but >> Ontrack gets noticed when wd0 is looked at in the failed attempt to >> open wd0a. >I think you really meant to say ``hd(1,a) becomes sd0a, which...'' I meant what I said. It can't have become sd0a because then wd0 wouldn't have been looked at. It only becomes sd0a if the disklabel type is DTYPE_SCSI. sd(0,a) becomes wd0a for the same reason. sysinstall sets the disklabel type correctly under the assumption that scsi disk names start with 's'. Typing hd(*, *) has no effect on the FreeBSD major device. It only forces the FreeBSD unit number to 0. Bruce From owner-freebsd-bugs Mon Jun 19 10:09:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA00280 for bugs-outgoing; Mon, 19 Jun 1995 10:09:39 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA00274 for ; Mon, 19 Jun 1995 10:09:36 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA01402; Mon, 19 Jun 1995 10:08:46 -0700 From: "Rodney W. Grimes" Message-Id: <199506191708.KAA01402@gndrsh.aac.dev.com> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Mon, 19 Jun 1995 10:08:46 -0700 (PDT) Cc: bde@zeta.org.au, bugs@FreeBSD.org In-Reply-To: <199506191631.CAA09759@godzilla.zeta.org.au> from "Bruce Evans" at Jun 20, 95 02:31:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3511 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > >From rgrimes@gndrsh.aac.dev.com Tue Jun 20 02:09:41 1995 > >Received: from gndrsh.aac.dev.com ([198.145.92.241]) by godzilla.zeta.org.au (8.6.9/8.6.9) with ESMTP id CAA09000 for ; Tue, 20 Jun 1995 02:08:16 +1000 > >Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA01169; Mon, 19 Jun 1995 09:07:30 -0700 > >From: "Rodney W. Grimes" > >Message-Id: <199506191607.JAA01169@gndrsh.aac.dev.com> > >Subject: Re: 2.05R panics on boot > >To: bde@zeta.org.au (Bruce Evans) > >Date: Mon, 19 Jun 1995 09:07:30 -0700 (PDT) > >Cc: bugs@FreeBSD.org > >In-Reply-To: <199506191255.WAA02612@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 10:55:16 pm > >X-Mailer: ELM [version 2.4 PL24] > >MIME-Version: 1.0 > >Content-Type: text/plain; charset=US-ASCII > >Content-Transfer-Encoding: 7bit > >Content-Length: 1611 > > >> > >> >Okay.... here is the output if I let the Ontrack DM load the dynamic > >> >overlay and then use the option to boot from the boot.flp. > >> > >> >If I choose wd(1,a)/kernel.GENERIC -v > >> > >> >FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 > >> >... > >> >wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S > >> >... > >> >wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S > >> >... > >> >changing root device to wd1a > >> >BIOS Geometries: > >> > 0:03391f3f 825 cyl, 31 heads, 63 sects > >> > 1:03fd0f3f 1021 cyl, 15 heads, 63 sects > >> > 0 accounted for > >> >wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK > >> > >> This all seems OK. > >> > >> >------------ > >> >Notice that no where in the boot process does it mention about the > >> >Ontrack DM. > >> > >> This is OK. wd0 isn't looked at since your'e not trying to boot > >> from it, so Ontrack isn't seen to be on it. It would be seen when the > >> DOS partition is mounted if you got that far. > >> Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am > >> >not supposed to)... > >> > >> >It shows these extra lines after the "0 accounted for" > >> >wd0: Found "Ontrack Disk Manager" on this disk. > >> >wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK > >> >panic: cannot mount root > >> > >> This is normal. hd(1,a) becomes wd0a, which you don't have, but > >> Ontrack gets noticed when wd0 is looked at in the failed attempt to > >> open wd0a. > > >I think you really meant to say ``hd(1,a) becomes sd0a, which...'' > > I meant what I said. It can't have become sd0a because then wd0 > wouldn't have been looked at. It only becomes sd0a if the disklabel > type is DTYPE_SCSI. sd(0,a) becomes wd0a for the same reason. > sysinstall sets the disklabel type correctly under the assumption that > scsi disk names start with 's'. Typing hd(*, *) has no effect on the > FreeBSD major device. It only forces the FreeBSD unit number to 0. Then something has been changed in what is going on in the boot code with respect to hd(X,a), as this *DID* cause bootdev to be set to sd(X-1,a). And these comments are now need of updating: README.386BSD:use device 'hd' README.386BSD:hd is special in that the kernel is always told to use unit 0, README.serial: Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. boot.c: "Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.\n" > > Bruce > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Mon Jun 19 10:39:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01449 for bugs-outgoing; Mon, 19 Jun 1995 10:39:44 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01443 for ; Mon, 19 Jun 1995 10:39:34 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id SAA09593; Mon, 19 Jun 1995 18:38:17 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: Bruce Evans cc: hlew@genome.Stanford.EDU, terry@cs.weber.edu, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-reply-to: Your message of "Mon, 19 Jun 1995 23:50:16 +1000." <199506191350.XAA04517@godzilla.zeta.org.au> Date: Mon, 19 Jun 1995 18:38:17 +0100 Message-ID: <9591.803583497@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > drives other than the first. If you decide to install a boot manager, > then it must be installed on the first drive. Where does FreeBSD put > it if you install FreeBSD on the second drive? It doesn't. This may need to be revised. Jordan From owner-freebsd-bugs Mon Jun 19 10:55:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02064 for bugs-outgoing; Mon, 19 Jun 1995 10:55:26 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02057 for ; Mon, 19 Jun 1995 10:55:15 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id SAA09694; Mon, 19 Jun 1995 18:55:00 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: ljg@space.physics.uiowa.edu (Larry Granroth) cc: bugs@freebsd.org Subject: Re: class C network with a 255 octet In-reply-to: Your message of "Mon, 19 Jun 1995 10:40:30 CDT." <9506191540.AA01055@chip.physics.uiowa.edu> Date: Mon, 19 Jun 1995 18:54:59 +0100 Message-ID: <9692.803584499@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk Wurgh! I guess I was a little too rabid in my error checking! :-( I'll release something shortly which fixes this. Sorry about that! Jordan > Help! > > I cannot install FreeBSD 2.0.5-RELEASE via ftp or nfs because the > installation program won't accept my (totally valid) network addresses: > > gateway: 128.255.32.1 router.physics.uiowa.edu > nameserver: 128.255.32.77 hobbes.physics.uiowa.edu > ftpserver: 128.255.32.166 chip.physics.uiowa.edu > target: 128.255.32.77 ljgpc.physics.uiowa.edu > > My guess is it is (incorrectly) complaining about the 255's above. > > Thanks in advance for your help. > > -Larry > > larry-granroth@uiowa.edu > From owner-freebsd-bugs Mon Jun 19 11:29:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA03516 for bugs-outgoing; Mon, 19 Jun 1995 11:29:54 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA03510 for ; Mon, 19 Jun 1995 11:29:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA12339; Tue, 20 Jun 1995 04:17:06 +1000 Date: Tue, 20 Jun 1995 04:17:06 +1000 From: Bruce Evans Message-Id: <199506191817.EAA12339@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: 2.05R panics on boot Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> >I think you really meant to say ``hd(1,a) becomes sd0a, which...'' >> >> I meant what I said. It can't have become sd0a because then wd0 >> wouldn't have been looked at. It only becomes sd0a if the disklabel >> type is DTYPE_SCSI. sd(0,a) becomes wd0a for the same reason. >> sysinstall sets the disklabel type correctly under the assumption that >> scsi disk names start with 's'. Typing hd(*, *) has no effect on the >> FreeBSD major device. It only forces the FreeBSD unit number to 0. >Then something has been changed in what is going on in >the boot code with respect to hd(X,a), as this *DID* cause bootdev >to be set to sd(X-1,a). And these comments are now need of updating: >README.386BSD:use device 'hd' >README.386BSD:hd is special in that the kernel is always told to use unit 0, >README.serial: Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. >boot.c: "Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.\n" Nothing has changed. The documentation just doesn't tell you what happens in unsupported cases. The only supported case is booting from sd0 when wd0 (and perhaps other wd's) are installed. Bruce From owner-freebsd-bugs Mon Jun 19 12:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04901 for bugs-outgoing; Mon, 19 Jun 1995 12:10:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA04894 ; Mon, 19 Jun 1995 12:10:01 -0700 Date: Mon, 19 Jun 1995 12:10:01 -0700 Message-Id: <199506191910.MAA04894@freefall.cdrom.com> From: Mattias Karlsson Reply-To: Mattias Karlsson To: freebsd-bugs Subject: misc/535: Sysinstall takes down the network. In-Reply-To: Your message of Mon, 19 Jun 1995 21:16:32 +0200 <199506191916.VAA21147@vortex.sdf.luth.se> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 535 >Category: misc >Synopsis: Sysinstall takes down the network. >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jun 19 12:10:00 1995 >Originator: Mattias Karlsson >Organization: Skelleftea Computer society >Release: FreeBSD 2.0.5-Release i386 >Environment: >Description: When i was installing today i logged in to one of out servers and started to read my mail and after a while my telnet hang. After some research i discovered that the sysinstall had both removed the default route and ifconfiged down the ethernet interface. My syggestion is to atleast warn before the network is taken down. >How-To-Repeat: Try to install a 2.0.5-RELEASE computer, telnet to another host and wait while sysinstall finishes. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Jun 19 12:45:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06098 for bugs-outgoing; Mon, 19 Jun 1995 12:45:05 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA06092 for ; Mon, 19 Jun 1995 12:45:03 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA22060; Mon, 19 Jun 95 13:38:00 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506191938.AA22060@cs.weber.edu> Subject: Re: 2.05R: failure to get fd parameters correctly To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 19 Jun 95 13:37:59 MDT Cc: guido@gvr.win.tue.nl, gibbs@freefall.cdrom.com, freebsd-bugs@freebsd.org In-Reply-To: <199506182313.QAA02506@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 18, 95 04:13:19 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@freebsd.org Precedence: bulk > > > > I installed to an Empire 2100 last nigt using the standard Adaptec > ^^^^^^^^^^^ > > Wrong drive Terry, the problems you are discussing are the Quantum > Grand Prix series. Well, never mind then (unless you want them to work too)! I guess he's booting fine, then. 8^). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Mon Jun 19 12:51:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06744 for bugs-outgoing; Mon, 19 Jun 1995 12:51:30 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA06738 for ; Mon, 19 Jun 1995 12:51:29 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id MAA09912 ; Mon, 19 Jun 1995 12:50:55 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Mattias Karlsson cc: freebsd-bugs@freefall.cdrom.com Subject: Re: misc/535: Sysinstall takes down the network. In-reply-to: Your message of "Mon, 19 Jun 1995 12:10:01 PDT." <199506191910.MAA04894@freefall.cdrom.com> Date: Mon, 19 Jun 1995 12:50:54 -0700 Message-ID: <9910.803591454@westhill.cdrom.com> From: Gary Palmer Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199506191910.MAA04894@freefall.cdrom.com>, Mattias Karlsson writes: > When i was installing today i logged in to one of out servers and > started to read my mail and after a while my telnet hang. After some > research i discovered that the sysinstall had both removed the default > route and ifconfiged down the ethernet interface. My syggestion is to > atleast warn before the network is taken down. If you plan to use the systinstall EHS for doing non-installation related work, expect the unexpected!!! I honestly can't call this a bug, and that if you `abuse' the facilites provided, that we can't do much to provide a safety net. Sure, we can do a msgConfirm before the net is taken down, but since you are not meant to be interacting with the network, the installation program is, there SHOULDN'T be a problem! YES, we can do this, but do we really want to ask the users permission to ifconfig down the network EVERY time? We'd get requests to take such a facility out pretty soon, I can tell you!! Gary From owner-freebsd-bugs Mon Jun 19 17:23:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA27942 for bugs-outgoing; Mon, 19 Jun 1995 17:23:34 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA27907 for ; Mon, 19 Jun 1995 17:23:26 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id XAA10190; Mon, 19 Jun 1995 23:25:00 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: Gary Palmer cc: Mattias Karlsson , freebsd-bugs@freefall.cdrom.com Subject: Re: misc/535: Sysinstall takes down the network. In-reply-to: Your message of "Mon, 19 Jun 1995 12:50:54 PDT." <9910.803591454@westhill.cdrom.com> Date: Mon, 19 Jun 1995 23:25:00 +0100 Message-ID: <10188.803600700@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > If you plan to use the systinstall EHS for doing non-installation > related work, expect the unexpected!!! I honestly can't call this a > bug, and that if you `abuse' the facilites provided, that we can't do > much to provide a safety net. Actually, this is a more than reasonable complaint and I've just added code to leave the network completely alone if you run sysinstall again in "post-installation mode." It was always my intention to make sysinstall more generally useful as a post-configuration tool and I simply failed to put all the requisite "am I really running as init?" checks in to make this more possible. > YES, we can do this, but do we really want to ask the users permission > to ifconfig down the network EVERY time? We'd get requests to take > such a facility out pretty soon, I can tell you!! Sorry Gary, but the truth of the matter is that sysinstall shouldn't be tweaking the network AT ALL when run for the second time! The code that whacked the network up and down (and did a few other obnoxious things which I've now corrected as well) was simply too stupid to know when its services were no longer needed. This has been fixed and was a genuine, bogus, evil nasty bug. Thanks, Mattias, for reporting it! It will be part of the next set of UPDATES floppies I'll be rolling soon. Jordan From owner-freebsd-bugs Mon Jun 19 22:10:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA22747 for bugs-outgoing; Mon, 19 Jun 1995 22:10:49 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA22741 for ; Mon, 19 Jun 1995 22:10:47 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id WAA13504 for ; Mon, 19 Jun 1995 22:09:39 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id WAA05519 for ; Mon, 19 Jun 1995 22:10:15 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id WAA00258; Mon, 19 Jun 1995 22:08:57 -0700 Date: Mon, 19 Jun 1995 22:08:57 -0700 From: "Russell L. Carter" Message-Id: <199506200508.WAA00258@geli.clusternet> To: freebsd-bugs@freebsd.org, rcarter@geli.com Subject: Re: more on st cataclysmic error 8-) Sender: bugs-owner@freebsd.org Precedence: bulk |I ejected the tape, reinserted it, and then tried: | |geli# pax -rvf /dev/rst0 Duh! replacing the "r" with a "w" worked ok, but very slowly. Roughly half the throughput at the beginning. Russell From owner-freebsd-bugs Mon Jun 19 22:28:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA23805 for bugs-outgoing; Mon, 19 Jun 1995 22:28:53 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA23793 for ; Mon, 19 Jun 1995 22:28:51 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id WAA15769 for ; Mon, 19 Jun 1995 22:27:42 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id WAA12947 for ; Mon, 19 Jun 1995 22:26:35 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id VAA00321; Mon, 19 Jun 1995 21:37:54 -0700 Date: Mon, 19 Jun 1995 21:37:54 -0700 From: "Russell L. Carter" Message-Id: <199506200437.VAA00321@geli.clusternet> To: freebsd-bugs@freebsd.org Subject: more on st cataclysmic error 8-) Cc: rcarter@geli.com Sender: bugs-owner@freebsd.org Precedence: bulk Ok, I've got some more data on the /dev/rst0 bug. There still remains the possibility that it is my drive. Careful watching showed the following output from ncrcontrol: 24 456 4 256 0 0 20 200 19456 6 1 24 1 19 260 5 120 0 0 14 140 14013 7 0 19 0 22 380 4 200 0 0 18 180 17687 6 2 22 2 18 288 2 128 0 0 16 160 16384 3 0 18 0 11 218 2 128 0 0 9 90 20294 3 0 11 0 23 392 3 192 0 0 20 200 17453 5 1 23 1 16 268 2 128 0 0 14 140 17152 3 0 16 0 16 268 2 128 0 0 14 140 17152 3 1 16 1 12 228 2 128 0 0 10 100 19456 3 1 12 1 10 154 1 64 0 0 9 90 15770 3 0 10 0 18 342 3 192 0 0 15 150 19456 6 1 18 1 36 576 4 256 0 0 32 320 16384 5 1 36 1 13 238 2 128 0 0 11 110 18747 3 1 13 1 16 252 2 112 0 0 14 140 16128 3 0 16 0 32 544 8 304 0 0 24 240 17408 11 0 32 0 12 228 2 128 0 0 10 100 19456 4 0 12 0 16 268 2 128 0 0 14 140 17152 3 1 16 1 total ST32550N CD-ROM C 4326XX 2 transf. disconn interru t/s kb/s t/s kb/s t/s kb/s t/s kb/s length exp une fly brk 5 50 0 0 0 0 5 50 10240 0 0 5 0 12 228 2 128 0 0 10 100 19456 2 0 12 0 10 154 1 64 0 0 9 90 15770 2 0 10 0 7 124 1 64 0 0 6 60 18139 2 1 7 1 18 274 9 184 0 0 9 90 15588 17 0 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 154 1 64 0 0 9 90 15770 1 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 28 496 4 256 0 0 24 240 18139 5 1 28 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 1024 2 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12 157 2 57 0 0 10 100 13397 2 1 12 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 32 544 8 304 0 0 24 240 17408 9 1 32 1 total ST32550N CD-ROM C 4326XX 2 transf. disconn interru t/s kb/s t/s kb/s t/s kb/s t/s kb/s length exp une fly brk 0 0 0 0 0 0 0 0 0 0 0 0 0 39 660 5 320 0 0 34 340 17329 6 0 39 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 154 1 64 0 0 9 90 15770 2 1 10 1 28 496 4 256 0 0 24 240 18139 4 0 28 0 At the very start the throughput is about 2x better than what you see at the top of the ncrcontrol output. This, allowed to complete the progression, hangs my system every time. An immediate ^C on the pax process gave: /usr/local/pkg/numerics/medusa/medusa/examples/sphere/grid.uu /usr/local/pkg/numerics/medusa/medusa/examples/sphere/headdp /usr/local/pkg/numerics/medusa/medusa/examples/sphere/grid.fmt^C pax: Signal caught, cleaning up. pax: Waiting for tape drive close to complete...done. pax: ustar vol 1, 21573 files, 0 bytes read, 380528640 bytes written. geli# I ejected the tape, reinserted it, and then tried: geli# pax -rvf /dev/rst0 windocs.tar.gz windocs.tar.gz.1Jun 19 21:23:52 geli /kernel: in getcc reselect by t1. Jun 19 21:23:52 geli /kernel: in getcc reselect by t1. Jun 19 21:24:23 geli last message repeated 118 times Jun 19 21:24:23 geli last message repeated 118 times windocs.tar.gz.2^C pax: Signal caught, cleaning up. pax: Waiting for tape drive close to complete...done. pax: ustar vol 1, 3 files, 6563840 bytes read, 0 bytes written. I'm using pax because it's more verbose about it's problems. Tar is much less verbose about the exact same problem. After this, the regular file systems are ok, and there is nothing detected by fsck. What's up? Nothing interesting is output to either the console or /var/log/messages at this stage. Russell From owner-freebsd-bugs Mon Jun 19 23:07:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA27325 for bugs-outgoing; Mon, 19 Jun 1995 23:07:45 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA27319 for ; Mon, 19 Jun 1995 23:07:44 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id XAA19535 for ; Mon, 19 Jun 1995 23:06:35 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id XAA25395 for ; Mon, 19 Jun 1995 23:07:11 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id XAA00362; Mon, 19 Jun 1995 23:05:53 -0700 Date: Mon, 19 Jun 1995 23:05:53 -0700 From: "Russell L. Carter" Message-Id: <199506200605.XAA00362@geli.clusternet> To: freebsd-bugs@freebsd.org, rcarter@geli.com Subject: SOLVED: Re: more on st cataclysmic error 8-) Sender: bugs-owner@freebsd.org Precedence: bulk Through process-of-elimination I think I've found the problem. It is the middle of June, temperatures have climbed into the middle 70Fs here, and damn, but the tape drive is overheating! I pulled it out of the case and have now just successfully backed up 1G+ twice in a row, so improved cooling might be the solution. (I installed this thing in Jan, and we've had a regular winter extending to middle June, very odd.) Russell From owner-freebsd-bugs Mon Jun 19 23:22:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA28678 for bugs-outgoing; Mon, 19 Jun 1995 23:22:03 -0700 Received: from balboa.eng.uci.edu (balboa.eng.uci.edu [128.200.61.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA28672 for ; Mon, 19 Jun 1995 23:22:01 -0700 Received: from localhost.uci.edu by balboa.eng.uci.edu with SMTP id AA21591 (5.65c/IDA-1.4.4 for freebsd-bugs@freebsd.org); Mon, 19 Jun 1995 23:21:53 -0700 Message-Id: <199506200621.AA21591@balboa.eng.uci.edu> To: freebsd-bugs@freebsd.org Subject: FreeBSD 1.0 incompatability Date: Mon, 19 Jun 1995 23:21:52 -0700 From: Steven Wallace Sender: bugs-owner@freebsd.org Precedence: bulk The tcsh for FreeBSD 1.0 that has worked great for me for the longest time now seg faults in FreeBSD 2.0.5. It only faults if I telnet or rlogin and use the shell. If I use an xterm there is no problem with it. The 2.0.5 tcsh works fine in both cases. The corefile gives me this info: (gdb) where #0 0x455c3d34 in ?? () Cannot access memory at address 0x6b3a524f. Use the tcsh on the 1.0 CDROM. Steven From owner-freebsd-bugs Mon Jun 19 23:57:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA00529 for bugs-outgoing; Mon, 19 Jun 1995 23:57:23 -0700 Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA00483 for ; Mon, 19 Jun 1995 23:56:55 -0700 Received: from fns.muc.de ([193.174.4.223]) by colin.muc.de with SMTP id <25537-2>; Tue, 20 Jun 1995 08:56:36 +0200 Received: (from peterb@localhost) by fns.muc.de (8.6.11/8.6.9) id IAA04389; Tue, 20 Jun 1995 08:47:41 +0200 Date: Tue, 20 Jun 1995 08:47:39 +0200 From: Peter Bechtold To: Joerg Wunsch cc: mpp@legarto.minn.net, freebsd-bugs@freefall.cdrom.com Subject: Re: misc/531: SCSI Tape Problems In-Reply-To: <199506190625.IAA09424@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Mon, 19 Jun 1995, J Wunsch wrote: > As Peter Bechtold wrote: > > > > No, trying again brings the same result. > > (Actually, my tape reacted like described above w/ 2.0R, but not > > anymore ...) > > Does this mean the problem does no longer exist??? No. Writing a tape worked with 2.0R, but not with 2.0.5R anymore ... > > In case it's still valid: what are the console messages from the > SCSI subsystem? Jun 19 01:25:00 fns /kernel: st0: oops not queued Jun 19 01:25:01 fns /kernel: biodone: buffer already done Peter -- # Peter Bechtold # peterb@muc.de # Tel./Fax (+49 / 0) 89 / 542 0774 # From owner-freebsd-bugs Tue Jun 20 00:10:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA01442 for bugs-outgoing; Tue, 20 Jun 1995 00:10:22 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA01431 for ; Tue, 20 Jun 1995 00:10:18 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA02600; Tue, 20 Jun 1995 00:10:13 -0700 From: "Rodney W. Grimes" Message-Id: <199506200710.AAA02600@gndrsh.aac.dev.com> Subject: Re: SOLVED: Re: more on st cataclysmic error 8-) To: rcarter@geli.com (Russell L. Carter) Date: Tue, 20 Jun 1995 00:10:12 -0700 (PDT) Cc: freebsd-bugs@freebsd.org, rcarter@geli.com In-Reply-To: <199506200605.XAA00362@geli.clusternet> from "Russell L. Carter" at Jun 19, 95 11:05:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2052 Sender: bugs-owner@freebsd.org Precedence: bulk > > > is the middle of June, temperatures have climbed into the middle > 70Fs here, and damn, but the tape drive is overheating! I pulled > it out of the case and have now just successfully backed up 1G+ > twice in a row, so improved cooling might be the solution. (I installed > this thing in Jan, and we've had a regular winter extending to > middle June, very odd.) Ahh.. didn't even think about that, but yes, DAT drives are hot running. I always place them in the the case such that there is dead air under them and preferable right in line with the power supply air inlets so that you get good air flow to the tape drive. I never place another device immediatly below or above a DAT drive unless I absolutely must. The down side of this placement is that it likes to suck all the room dust through your dust sensitive tape drive :-(. Also note that dual fan cases with one fan in front pushing air and one fan in the power supply pulling air actually cause very poor air flow to occur accross the drive bays. I usually reverse the front fan and have it blow as well thus reducing the problem of direct air flow from the inlet fan to the outlet fan with little else getting cooled. [I actually just prefer single fan cases with a decent fan in the power supply since it eliminates the bad air flow I have seen in so many cases that use a push/pull fan combo.] Or if it is to be multiple fans they should all be mounted in the rear of the case blowing outward, I like negative pressure dust sucking monsters, so much infact the MSE/800 I worked on for Rolm Milspec had 8 EGG variable speed fans in it that could push 2000CFM combined and vacumn a 6 square foot area infront of the machine for you :-) If you wanted to post a note about machine status you just wrote it on a 8.5" x 11" sheet and hurled in front of the machine, it would get sucked onto the front and stay... :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Tue Jun 20 02:08:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA11131 for bugs-outgoing; Tue, 20 Jun 1995 02:08:07 -0700 Received: (from asami@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA11109 ; Tue, 20 Jun 1995 02:08:05 -0700 Date: Tue, 20 Jun 1995 02:08:05 -0700 From: Satoshi Asami Message-Id: <199506200908.CAA11109@freefall.cdrom.com> To: henrich@crh.cl.msu.edu, asami, freebsd-bugs Subject: Changed information for PR ports/504 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: NN port defines invalid TMP_DIRECTORY in global.c State-Changed-From-To: open-closed State-Changed-By: asami State-Changed-When: Tue Jun 20 02:06:35 PDT 1995 State-Changed-Why: Fixed (/usr/tmp -> /var/tmp) in revision 1.3 of patch-ab by ache. From owner-freebsd-bugs Tue Jun 20 03:30:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA12830 for bugs-outgoing; Tue, 20 Jun 1995 03:30:45 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA12821 for ; Tue, 20 Jun 1995 03:30:42 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA01260; Tue, 20 Jun 1995 03:29:23 -0700 Date: Tue, 20 Jun 1995 03:29:23 -0700 Message-Id: <199506201029.DAA01260@silvia.HIP.Berkeley.EDU> To: bde@zeta.org.au CC: bugs@freebsd.org In-reply-to: <199506191036.UAA30605@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 19 Jun 1995 20:36:03 +1000) Subject: Re: bogus release version string From: asami@cs.berkeley.edu (Satoshi Asami) Sender: bugs-owner@freebsd.org Precedence: bulk * Release: FreeBSD 2.0-BUILT-19950603 i386 * * 1. This provides very little information about the version - it might be * for plain 2.0 built late or for 2.2 built early. I agree. Is there some way to let cvs generate an $Id$-like string that has the checkout time, not the checkin time? Then we can put it in one of the header files and pull it into the kernel, and this will give us a reasonable approximation assuming the whole source is checked out at once (certainly true for sup from freefall or ctm). Satoshi From owner-freebsd-bugs Tue Jun 20 03:55:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA15418 for bugs-outgoing; Tue, 20 Jun 1995 03:55:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA15411 for ; Tue, 20 Jun 1995 03:55:04 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA06090; Tue, 20 Jun 1995 20:52:28 +1000 Date: Tue, 20 Jun 1995 20:52:28 +1000 From: Bruce Evans Message-Id: <199506201052.UAA06090@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, bde@zeta.org.au Subject: Re: bogus release version string Cc: bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk > * Release: FreeBSD 2.0-BUILT-19950603 i386 > * > * 1. This provides very little information about the version - it might be > * for plain 2.0 built late or for 2.2 built early. >I agree. Is there some way to let cvs generate an $Id$-like string >that has the checkout time, not the checkin time? Then we can put it >in one of the header files and pull it into the kernel, and this will >give us a reasonable approximation assuming the whole source is >checked out at once (certainly true for sup from freefall or ctm). `cvs co ...; date >some-header.h' :-) I'd prefer for `cvs commit' to print the date step commit the changed header (not recursively, and without doubly the number of commits). Bruce From owner-freebsd-bugs Tue Jun 20 04:16:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA16487 for bugs-outgoing; Tue, 20 Jun 1995 04:16:08 -0700 Received: (from asami@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA16469 ; Tue, 20 Jun 1995 04:16:07 -0700 Date: Tue, 20 Jun 1995 04:16:07 -0700 From: Satoshi Asami Message-Id: <199506201116.EAA16469@freefall.cdrom.com> To: gene@starkhome.cs.sunysb.edu, asami, freebsd-bugs Subject: Changed information for PR ports/526 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: rmail-spool-directory misconfigured in editors/xemacs State-Changed-From-To: open-closed State-Changed-By: asami State-Changed-When: Tue Jun 20 04:14:54 PDT 1995 State-Changed-Why: Fix added as patch-ab. From owner-freebsd-bugs Tue Jun 20 05:20:55 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA17576 for bugs-outgoing; Tue, 20 Jun 1995 05:20:55 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA17569 for ; Tue, 20 Jun 1995 05:20:52 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id FAA02858; Tue, 20 Jun 1995 05:18:41 -0700 From: "Rodney W. Grimes" Message-Id: <199506201218.FAA02858@gndrsh.aac.dev.com> Subject: Re: bogus release version string To: bde@zeta.org.au (Bruce Evans) Date: Tue, 20 Jun 1995 05:18:41 -0700 (PDT) Cc: asami@cs.berkeley.edu, bde@zeta.org.au, bugs@freebsd.org In-Reply-To: <199506201052.UAA06090@godzilla.zeta.org.au> from "Bruce Evans" at Jun 20, 95 08:52:28 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1318 Sender: bugs-owner@freebsd.org Precedence: bulk > > > * Release: FreeBSD 2.0-BUILT-19950603 i386 > > * > > * 1. This provides very little information about the version - it might be > > * for plain 2.0 built late or for 2.2 built early. > > >I agree. Is there some way to let cvs generate an $Id$-like string > >that has the checkout time, not the checkin time? Then we can put it > >in one of the header files and pull it into the kernel, and this will > >give us a reasonable approximation assuming the whole source is > >checked out at once (certainly true for sup from freefall or ctm). > > `cvs co ...; date >some-header.h' :-) > > I'd prefer for `cvs commit' to print the date step commit the changed > header (not recursively, and without doubly the number of commits). cvs co occured once for /usr/src on freefall since the 2.0 tree, it has never been checked out again. some-header.h is not how the version string gets built, it is needed by /sys/conf/newvers.sh. This would not handle the 3 way branch we now have in cvs. We need to think this throught carefully and come up with somethings that works well, but does not require excessive version reving of a commited file. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Tue Jun 20 05:42:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA18134 for bugs-outgoing; Tue, 20 Jun 1995 05:42:31 -0700 Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA18116 ; Tue, 20 Jun 1995 05:42:27 -0700 Received: from thomas.ge.com ([3.47.28.21]) by ns.ge.com (8.6.12/8.6.11) with ESMTP id IAA05793; Tue, 20 Jun 1995 08:42:25 -0400 Received: from salem.ge.com (carsdb.salem.ge.com [3.29.7.15]) by thomas.ge.com (8.6.12/8.6.12) with SMTP id IAA00522; Tue, 20 Jun 1995 08:43:30 -0400 Received: from combs.salem.ge.com by salem.ge.com (4.1/SMI-4.1) id AA11599; Tue, 20 Jun 95 08:42:40 EDT Received: (from steve@localhost) by combs.salem.ge.com (8.6.12/8.6.11) id IAA09685; Tue, 20 Jun 1995 08:42:40 -0400 Date: Tue, 20 Jun 1995 08:42:40 -0400 From: "Stephen F. Combs" Message-Id: <199506201242.IAA09685@combs.salem.ge.com> To: FreeBSD-hackers@freefall.cdrom.com, FreeBSD-bugs@freefall.cdrom.com Subject: Problems with Installing 2.0.5R Sender: bugs-owner@FreeBSD.org Precedence: bulk I've been trying to install 2.0.5R since last Thursday, 15 June. It's up and running but here's the problems I've been having. First, here's the hardware it's running on: DOLCH 386-33 MB w/20MB RAM, Adaptec 1542CF with BIOS Translation turned off, 2 Serial Ports, NO Parallel Ports, ATI VGAWonder XL w/1MB RAM and onboard Mouse, 3COM 3C503 (8-Bit) Ethernet, USRobotics 14,400 Internal modem w/16550Equiv, Digiboard COM-4 DUMB 4-port Serial I/O. ST31200 1.0GB SCSI-2 Disk, DEC RZ25 400MB SCSI-2 Disk, Archive 2150S QIC-150 1/4" Tape Drive SCSI-1, Sun/Sony CD-ROM SCSI-2 (external). Now the problems: 1) Infamous "missing operating system". I tried to install 2.0.5R on an old CDC WREN SCSI-1 drive which has been running FreeBSD since the days of 1.0E. I backed up the old partitions and began the install using the boot.flp image of 12 June. Built new partitions, assigned new slices, etc... System would not boot, saying "missing operating system". I had a new Seagate 31200 and decided to start fresh. Same problem! I tried again and this time went BACK to the partition table after all was installed but before rebooting and discovered that even tho I had flagged the partition as bootable, IT WASN'T marked as such after installing the distribution. I flagged it as bootable again and all was OK on the reboot! 2) Using the ST31200, I couldn't get it to accept the untranslated geometry. The system has ONLY FreeBSD on it (no DOS, no OS/2, no WinNT). The only way the system would work, is to create a 1MB DOS partition (which forced translated geometry) and then delete it and assign the entire disk to FreeBSD. 3) BIN Dist failed to install. DEBUG Screen said "gunzip: unexpeced EOF" (not exact message). Then "cpio: unexpected EOF". Re-Downloaded new bin dist and tried again (same problem). System was up enough to continue install. 4) Usr.SBin Dist failed to install with the same message as BIN Dist. After getting this series of messages, I tried to list the dist(s) on my SPARC at work. Using "zcat bin.?? | tar tf -" as the command, I got the SAME type of message with the BIN Dist on the Sun. Using the "cat bin.?? | tar ztf -" all worked OK. Same story on the "susbin.??" distribution. The listing failed on the FIRST file in the susbin distribution and on the LAST file on the BIN dist. After these tests, I completely redid the source extraction using the command "cat .?? | (cd ; tar zxf -)" and am (as I write this) doing a "make world" in the source tree. 5) XF86 Failed completely to install via the sysinstall system. I was able to extract it using the command in the Readme file just fine. FYI, the error symptom from sysinstall was an immediate return when selecting the X install. No error, no nuthin' just an immediate return to the menu. Ditto for package installs. I was able to install various packages using the old "pkg_add" command with no problem. This message is not intended to be a bitch, gripe, etc... about the install process. I happen to think (once I've/You've figured out what happened) that the install is the best yet! Beats the old 386BSD 0.1 install hands down (course, it wouldn't take much to beat that!). Overall I think 2.0.5 is quite an acomplishment! Kudos to all!!!!!! The only problem I'm seeing to-date with the system is some 'sio overruns' when my PPP link is up, I'll investigate them later...... Steve Combs Communications Analyst GE Motors & Industrial Systems Drive Systems Salem, VA Voice: (703)387-8828 Internet: CombsSF@Salem.GE.COM Internet-Home: CombsSF-Home@Salem.GE.COM From owner-freebsd-bugs Tue Jun 20 05:55:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA18581 for bugs-outgoing; Tue, 20 Jun 1995 05:55:38 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA18575 for ; Tue, 20 Jun 1995 05:55:30 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA10482; Tue, 20 Jun 1995 22:52:46 +1000 Date: Tue, 20 Jun 1995 22:52:46 +1000 From: Bruce Evans Message-Id: <199506201252.WAA10482@godzilla.zeta.org.au> To: bde@zeta.org.au, rgrimes@gndrsh.aac.dev.com Subject: Re: bogus release version string Cc: asami@cs.berkeley.edu, bugs@freebsd.org Sender: bugs-owner@freebsd.org Precedence: bulk >> `cvs co ...; date >some-header.h' :-) >> >> I'd prefer for `cvs commit' to print the date step commit the changed >> header (not recursively, and without doubly the number of commits). >cvs co occured once for /usr/src on freefall since the 2.0 tree, it has >never been checked out again. >some-header.h is not how the version string gets built, it is needed >by /sys/conf/newvers.sh. Use #include. >This would not handle the 3 way branch we now have in cvs. Each branch should have a different newvers.sh. The same timestamp will do for them all. This gives more timestamps than kernel versions, but this isn't a problem. >We need to think this throught carefully and come up with somethings >that works well, but does not require excessive version reving of a >commited file. Some committed file has to change for the change to be visible in cvs. Revving the file once per day might be good enough. Bruce From owner-freebsd-bugs Tue Jun 20 06:48:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA20936 for bugs-outgoing; Tue, 20 Jun 1995 06:48:53 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA20929 ; Tue, 20 Jun 1995 06:48:41 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id OAA13628; Tue, 20 Jun 1995 14:48:34 +0100 X-Authentication-Warning: whisker.internet-eireann.ie: Host localhost didn't use HELO protocol To: "Stephen F. Combs" cc: FreeBSD-hackers@freefall.cdrom.com, FreeBSD-bugs@freefall.cdrom.com Subject: Re: Problems with Installing 2.0.5R In-reply-to: Your message of "Tue, 20 Jun 1995 08:42:40 EDT." <199506201242.IAA09685@combs.salem.ge.com> Date: Tue, 20 Jun 1995 14:48:34 +0100 Message-ID: <13626.803656114@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: bugs-owner@freebsd.org Precedence: bulk > 2) Using the ST31200, I couldn't get it to accept the > untranslated geometry. The system has ONLY FreeBSD on it Yeah, we're going to be working on this more in the future. Known problem, and it's a sticky one. > 3) BIN Dist failed to install. DEBUG Screen said "gunzip: > unexpeced EOF" (not exact message). Then "cpio: unexpected > EOF". Re-Downloaded new bin dist and tried again (same > problem). System was up enough to continue install. This is weird. How are you installing? Over ftp? From which site? I've had a couple of people report symptoms like this (which I'm utterly unable to reproduce) which leads me to believe that perhaps one of our mirrors has a bogus dist. > 4) Usr.SBin Dist failed to install with the same message as > BIN Dist. After getting this series of messages, I tried Ditto. Can't reproduce at all. > 5) XF86 Failed completely to install via the sysinstall > system. I was able to extract it using the command See above.. :-( > This message is not intended to be a bitch, gripe, etc... about > the install process. I happen to think (once I've/You've figured out > what happened) that the install is the best yet! Beats the old 386BSD 0.1 Thanks, though I'd still like to know why you (and a couple of other folks) are having such a hard time extracting these dists! They all work just fine for me and all the testers hanging around Walnut Creek CDROM.. The only known bug is that /usr/src/bin doesn't extract as part of the src dist, and that's been fixed. Jordan From owner-freebsd-bugs Tue Jun 20 07:10:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA21519 for bugs-outgoing; Tue, 20 Jun 1995 07:10:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA21511 ; Tue, 20 Jun 1995 07:10:02 -0700 Date: Tue, 20 Jun 1995 07:10:02 -0700 Message-Id: <199506201410.HAA21511@freefall.cdrom.com> From: Peter Dufault Reply-To: Peter Dufault To: freebsd-bugs Subject: docs/536: No copyrights in usr/src/lib/libc/stdtime In-Reply-To: Your message of Tue, 20 Jun 1995 10:05:51 -0400 <199506201405.KAA24072@hda.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 536 >Category: docs >Synopsis: No copyrights in usr/src/lib/libc/stdtime >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 20 07:10:01 1995 >Originator: Peter & >Organization: Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: >Description: Neither the header files nor the source code to the routines in lib/libc/stdtime have any copyrights. >How-To-Repeat: >Fix: Determine what the right copyright is and insert it. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 20 07:45:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA22743 for bugs-outgoing; Tue, 20 Jun 1995 07:45:03 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA22736 for ; Tue, 20 Jun 1995 07:45:01 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA10229; Tue, 20 Jun 1995 10:44:56 -0400 Date: Tue, 20 Jun 1995 10:44:56 -0400 From: Garrett Wollman Message-Id: <9506201444.AA10229@halloran-eldar.lcs.mit.edu> To: Peter Dufault Cc: freebsd-bugs@freefall.cdrom.com Subject: docs/536: No copyrights in usr/src/lib/libc/stdtime In-Reply-To: <199506201410.HAA21511@freefall.cdrom.com> References: <199506201405.KAA24072@hda.com> <199506201410.HAA21511@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < said: > Neither the header files nor the source code to the routines in > lib/libc/stdtime have any copyrights. The ``right copyright'' is probably: This software was written by Arthur D. Olson, an employee of the United States government, and is thus in the public domain. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-bugs Tue Jun 20 10:48:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA00130 for bugs-outgoing; Tue, 20 Jun 1995 10:48:18 -0700 Received: from lambda (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA00119 for ; Tue, 20 Jun 1995 10:48:12 -0700 Received: (from paul@localhost) by lambda (8.6.11/8.6.9) id RAA05185; Tue, 20 Jun 1995 17:42:11 +0100 From: Paul Richards Message-Id: <199506201642.RAA05185@lambda> Subject: Re: 2.05R panics on boot To: bde@zeta.org.au (Bruce Evans) Date: Tue, 20 Jun 1995 17:40:55 +0100 (BST) Cc: bde@zeta.org.au, hlew@genome.stanford.edu, bugs@freebsd.org In-Reply-To: <199506180547.PAA15709@godzilla.zeta.org.au> from "Bruce Evans" at Jun 18, 95 03:47:18 pm Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 451 Sender: bugs-owner@freebsd.org Precedence: bulk In reply to Bruce Evans who said > How would that help? You would still need Ontrack somewhere to use more > than 504MB for DOS on the big drive. Putting Ontrack somewhere apparently > affects everywhere. Wouldn't that be expected if it's redirecting INT13 ? -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-bugs Tue Jun 20 11:33:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA02856 for bugs-outgoing; Tue, 20 Jun 1995 11:33:32 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA02841 for ; Tue, 20 Jun 1995 11:33:26 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA27379; Tue, 20 Jun 1995 20:33:14 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA03765; Tue, 20 Jun 1995 20:33:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA16293; Tue, 20 Jun 1995 20:16:53 +0200 From: J Wunsch Message-Id: <199506201816.UAA16293@uriah.heep.sax.de> Subject: Re: misc/531: SCSI Tape Problems To: peterb@muc.de (Peter Bechtold) Date: Tue, 20 Jun 1995 20:16:52 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: from "Peter Bechtold" at Jun 20, 95 08:47:39 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 416 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Peter Bechtold wrote: > > > In case it's still valid: what are the console messages from the > > SCSI subsystem? > > Jun 19 01:25:00 fns /kernel: st0: oops not queued > Jun 19 01:25:01 fns /kernel: biodone: buffer already done Hmm, Peter (Dufault)??? Can you help? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Tue Jun 20 13:06:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA10314 for bugs-outgoing; Tue, 20 Jun 1995 13:06:58 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA10222 ; Tue, 20 Jun 1995 13:06:40 -0700 Received: from jupiter [134.169.34.4] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id WAA01306; Tue, 20 Jun 1995 22:06:10 +0200 Received: from petri@localhost by jupiter.ibr.cs.tu-bs.de (8.6.11/tubsibr) id WAA00698; Tue, 20 Jun 1995 22:06:09 +0200 Date: Tue, 20 Jun 1995 22:06:09 +0200 Message-Id: <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> To: FreeBSD-gnats-submit@freebsd.org, bugs@freebsd.org Subject: pci_bus_config() does not init parent pointers in device list + fix From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de X-send-pr-version: 3.2 Sender: bugs-owner@freebsd.org Precedence: bulk >Submitter-Id: net >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Confidential: no >Synopsis: pci_bus_config() does not init parent pointers in device list >Severity: serious >Priority: medium >Category: kern >Release: FreeBSD 2.0.950412-SNAP i386 >Class: change-request >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; From owner-freebsd-bugs Tue Jun 20 14:19:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA16882 for bugs-outgoing; Tue, 20 Jun 1995 14:19:10 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA16876 for ; Tue, 20 Jun 1995 14:19:08 -0700 Received: (dufault@localhost) by hda.com (8.6.11/8.3) id RAA25453; Tue, 20 Jun 1995 17:15:50 -0400 From: Peter Dufault Message-Id: <199506202115.RAA25453@hda.com> Subject: Re: misc/531: SCSI Tape Problems To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 20 Jun 1995 17:15:50 -0400 (EDT) Cc: peterb@muc.de, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506201816.UAA16293@uriah.heep.sax.de> from "J Wunsch" at Jun 20, 95 08:16:52 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 807 Sender: bugs-owner@FreeBSD.org Precedence: bulk J Wunsch writes: > > As Peter Bechtold wrote: > > > > > In case it's still valid: what are the console messages from the > > > SCSI subsystem? > > > > Jun 19 01:25:00 fns /kernel: st0: oops not queued > > Jun 19 01:25:01 fns /kernel: biodone: buffer already done > > Hmm, Peter (Dufault)??? Can you help? No, I can't. It isn't a general tape problem, so it is something specific to this environment. How about turning on debugging and trying again? That should get us some more info. You'll have to compile your kernel with the SCSIDEBUG option, and then turn on debugging on the tape drive using the scsi(8) "-d" flag. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-bugs Tue Jun 20 14:37:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA17715 for bugs-outgoing; Tue, 20 Jun 1995 14:37:34 -0700 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA17700 ; Tue, 20 Jun 1995 14:37:33 -0700 Date: Tue, 20 Jun 1995 14:37:33 -0700 From: "Andrey A. Chernov" Message-Id: <199506202137.OAA17700@freefall.cdrom.com> To: muir@idiom.com, ache, freebsd-bugs Subject: Changed information for PR bin/113 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: /bin/csh and /usr/local/bin/tcsh choke on my nasty cd alias State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Tue Jun 20 14:36:34 PDT 1995 State-Changed-Why: Now works with both /bin/csh and /usr/local/bin/tcsh From owner-freebsd-bugs Tue Jun 20 15:14:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA19922 for bugs-outgoing; Tue, 20 Jun 1995 15:14:38 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA19916 for ; Tue, 20 Jun 1995 15:14:36 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id AAA23611 ; Wed, 21 Jun 1995 00:14:27 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id AAA26270 ; Wed, 21 Jun 1995 00:14:26 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199506202214.AAA26270@blaise.ibp.fr> Subject: Re: misc/531: SCSI Tape Problems To: peterb@muc.de (Peter Bechtold) Date: Wed, 21 Jun 1995 00:14:26 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, mpp@legarto.minn.net, freebsd-bugs@freefall.cdrom.com In-Reply-To: from "Peter Bechtold" at Jun 20, 95 08:47:39 am X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 478 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > In case it's still valid: what are the console messages from the > > SCSI subsystem? > > Jun 19 01:25:00 fns /kernel: st0: oops not queued > Jun 19 01:25:01 fns /kernel: biodone: buffer already done A friend of mine just opened a PR regarding the same problem. He suffered extensive FS lossage and was forced to reinstall... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-bugs Tue Jun 20 16:53:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA23023 for bugs-outgoing; Tue, 20 Jun 1995 16:53:36 -0700 Received: from beandorf.epilogue.com (beandorf.epilogue.com [128.224.1.153]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA23017 for ; Tue, 20 Jun 1995 16:53:34 -0700 Received: (from alan@localhost) by beandorf.epilogue.com (8.6.9/8.6.9) id TAA01616; Tue, 20 Jun 1995 19:53:29 -0400 Date: Tue, 20 Jun 1995 19:53:29 -0400 Message-Id: <20Jun1995.191111.Alan@Epilogue.Com> From: Alan Bawden To: fenner@parc.xerox.com CC: freebsd-bugs@freefall.cdrom.com In-reply-to: Bill Fenner's message of Wed, 14 Jun 1995 18:05:27 PDT <95Jun14.180529pdt.49859@crevenia.parc.xerox.com> Subject: kern/512: writing to bpf(loopback) causes kernel panic Sender: bugs-owner@FreeBSD.org Precedence: bulk To: Alan Bawden cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/512: writing to bpf(loopback) causes kernel panic Date: Wed, 14 Jun 1995 18:05:27 PDT From: Bill Fenner ... Try these patches. ... Seems to work just fine. Thanks! From owner-freebsd-bugs Tue Jun 20 18:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA25091 for bugs-outgoing; Tue, 20 Jun 1995 18:00:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA25084 ; Tue, 20 Jun 1995 18:00:02 -0700 Date: Tue, 20 Jun 1995 18:00:02 -0700 Message-Id: <199506210100.SAA25084@freefall.cdrom.com> From: "Brian J. McGovern" Reply-To: "Brian J. McGovern" To: freebsd-bugs Subject: bin/537: FSCK Fails In-Reply-To: Your message of Tue, 20 Jun 1995 16:37:16 -0400 <199506202037.QAA02989@spoon.beta.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 537 >Category: bin >Synopsis: FSCK Fails >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 20 18:00:01 1995 >Originator: mcgovern@spoon.beta.com >Organization: BETA.COM >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 486/66 with 2 Seagate Hawk 4GB Drives >Description: When rebooting after installing on twin 4GB drives, fsck fails either with an unknown inconsistency error, or fails with the error "Can not allocate 4752002 bytes for lncntp". This occurs whether I use the drive geometry as supplied by segate during install (FreeBSD Install complains that the geometry is wrong), or during the install when a small DOS partition is used to force FreeBSD's idea of drive geometry. Often, machine will complain of other "out of swap space" or VM errors after several boot attempts. Trouble partitions range from 1.5GB to 2.0GB. >How-To-Repeat: Reinstall OS and try again. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Jun 20 20:24:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA28476 for bugs-outgoing; Tue, 20 Jun 1995 20:24:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA28470 for ; Tue, 20 Jun 1995 20:24:05 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA02379; Wed, 21 Jun 1995 13:22:57 +1000 Date: Wed, 21 Jun 1995 13:22:57 +1000 From: Bruce Evans Message-Id: <199506210322.NAA02379@godzilla.zeta.org.au> To: bde@zeta.org.au, paul@lambda Subject: Re: 2.05R panics on boot Cc: bugs@freebsd.org, hlew@genome.stanford.edu Sender: bugs-owner@freebsd.org Precedence: bulk >> than 504MB for DOS on the big drive. Putting Ontrack somewhere apparently >> affects everywhere. >Wouldn't that be expected if it's redirecting INT13 ? No, it shouldn't translate everything. Would you expect it to translate floppies and cdroms? Bruce From owner-freebsd-bugs Wed Jun 21 11:44:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA10848 for bugs-outgoing; Wed, 21 Jun 1995 11:44:03 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA10824 for ; Wed, 21 Jun 1995 11:43:49 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA18958 (5.65c8/HUTCS-S 1.4 for ); Wed, 21 Jun 1995 21:43:02 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id VAA25228; Wed, 21 Jun 1995 21:43:12 +0300 Date: Wed, 21 Jun 1995 21:43:12 +0300 Message-Id: <199506211843.VAA25228@shadows.cs.hut.fi> To: Steven Wallace Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: Steven Wallace's message of 20 Jun 1995 13:55:49 +0300 Subject: FreeBSD 1.0 incompatability Organization: Helsinki University of Technology, Otaniemi, Finland Sender: bugs-owner@FreeBSD.org Precedence: bulk The tcsh for FreeBSD 1.0 that has worked great for me for the longest time now seg faults in FreeBSD 2.0.5. It only faults if I telnet or rlogin and use the shell. If I use an xterm there is no problem with it. The 2.0.5 tcsh works fine in both cases. Somewhere between 2.0 and 2.0.5 termcap was puffed up with more features, thus making most (all?) programs using curses/termcap to dump core somewhere in termcap routines, when big termcap entries like vt220 are used. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-bugs Wed Jun 21 14:44:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA07026 for bugs-outgoing; Wed, 21 Jun 1995 14:44:43 -0700 Received: from cycle.Stanford.EDU (hlew@cycle.Stanford.EDU [36.159.0.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA07020 for ; Wed, 21 Jun 1995 14:44:41 -0700 Received: by cycle.Stanford.EDU; id AA18930; Wed, 21 Jun 1995 14:39:29 -0700 Date: Wed, 21 Jun 1995 14:39:28 -0700 (PDT) From: Howard Lew To: Bruce Evans Cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506191337.XAA04073@godzilla.zeta.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Mon, 19 Jun 1995, Bruce Evans wrote: > >> DOS has no problems handling >= 504 MB. This is a BIOS problem. > > >This is strange because I can configure the bios for 32 heads and over > >800 Megs, but if I do a fdisk, DOS says the maximum partition size is 504 MB. > > This _is_ strange. How do you know that you can configure the BIOS like > this. I only have old BIOS's that allow you to enter 32 heads in setup > but don't actually support 32 heads. Actually, I really meant configuring the CMOS for 32 heads is possible. Maybe the BIOS doesn't support that CMOS parameter under drive type 47, so DOS says the max is 504 MB per partition. But DOS says over 800 MB when Ontrack DM is installed. From owner-freebsd-bugs Wed Jun 21 14:52:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA08172 for bugs-outgoing; Wed, 21 Jun 1995 14:52:15 -0700 Received: from cycle.Stanford.EDU (hlew@cycle.Stanford.EDU [36.159.0.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA08166 for ; Wed, 21 Jun 1995 14:52:11 -0700 Received: by cycle.Stanford.EDU; id AA18992; Wed, 21 Jun 1995 14:48:18 -0700 Date: Wed, 21 Jun 1995 14:48:18 -0700 (PDT) From: Howard Lew To: Bruce Evans Cc: terry@cs.weber.edu, bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506191350.XAA04517@godzilla.zeta.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Mon, 19 Jun 1995, Bruce Evans wrote: > Er, why are we discussing OS-BS? FreeBSD's sysinstall supports only > bteasy, and someone reported that OS-BS doesn't support booting from > drives other than the first. If you decide to install a boot manager, os-bs20b8 seems to support booting from more than one drive. > then it must be installed on the first drive. Where does FreeBSD put > it if you install FreeBSD on the second drive? I have not figured out the last question yet. But I'll see if I can install os-bs also on my second drive. Is it possible? I tried last night with os-bs, but it would only write to the first drive. From owner-freebsd-bugs Wed Jun 21 15:29:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10654 for bugs-outgoing; Wed, 21 Jun 1995 15:29:50 -0700 Received: from kryten.atinc.com (kryten.atinc.com [198.138.38.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA10648 for ; Wed, 21 Jun 1995 15:29:48 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8From owner-freebsd-bugs Wed Jun 21 15:50:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA11661 for bugs-outgoing; Wed, 21 Jun 1995 15:50:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA11654 ; Wed, 21 Jun 1995 15:50:01 -0700 Date: Wed, 21 Jun 1995 15:50:01 -0700 Message-Id: <199506212250.PAA11654@freefall.cdrom.com> From: tom@haven.uniserve.com Reply-To: tom@haven.uniserve.com To: freebsd-bugs Subject: bin/539: In-Reply-To: Your message of Wed, 21 Jun 1995 15:49:29 +0100 <95Jun21.154940+0100_pdt.30740+2018@haven.uniserve.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 539 >Category: bin >Synopsis: >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 21 15:50:00 1995 >Originator: Tom Samplonius >Organization: UNIServe >Release: FreeBSD 2.0.5-RELEASE >Environment: >Description: finger scans every home direcotry for .nofinger rather than checking home directories of the users that actually match. >How-To-Repeat: Use finger with large number of users >Fix: Only check home directories if they match. The following patch moves the hide() call just after the match() call so that only home directories of matched users get checked. *** finger.c.old Wed Jun 21 14:19:50 1995 --- finger.c Wed Jun 21 14:29:14 1995 *************** *** 261,270 **** "finger: %s: no such user\n", *p); else { while (pw = getpwent()) { - if (hide (pw)) - continue; for (p = argv, ip = used; *p; ++p, ++ip) ! if (match(pw, *p)) { enter_person(pw); *ip = 1; } --- 261,268 ---- "finger: %s: no such user\n", *p); else { while (pw = getpwent()) { for (p = argv, ip = used; *p; ++p, ++ip) ! if (match(pw, *p) && !hide(pw)) { enter_person(pw); *ip = 1; } >Audit-Trail: >Unformatted: finger checks every home directory for .nofinger From owner-freebsd-bugs Wed Jun 21 16:55:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA13173 for bugs-outgoing; Wed, 21 Jun 1995 16:55:45 -0700 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA13159 ; Wed, 21 Jun 1995 16:55:44 -0700 Date: Wed, 21 Jun 1995 16:55:44 -0700 From: "Andrey A. Chernov" Message-Id: <199506212355.QAA13159@freefall.cdrom.com> To: tom@haven.uniserve.com, ache, freebsd-bugs Subject: Changed information for PR bin/539 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Wed Jun 21 16:55:00 PDT 1995 State-Changed-Why: Fix applied in finger.c rev 1.6 From owner-freebsd-bugs Thu Jun 22 04:48:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA27665 for bugs-outgoing; Thu, 22 Jun 1995 04:48:20 -0700 Received: from lambda (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA27652 ; Thu, 22 Jun 1995 04:48:13 -0700 Received: (from paul@localhost) by lambda (8.6.11/8.6.9) id TAA05363; Tue, 20 Jun 1995 19:08:13 +0100 From: Paul Richards Message-Id: <199506201808.TAA05363@lambda> Subject: Re: Problems with Installing 2.0.5R To: test-owner@salem.ge.com (Stephen F. Combs) Date: Tue, 20 Jun 1995 19:06:58 +0100 (BST) Cc: FreeBSD-hackers@freefall.cdrom.com, FreeBSD-bugs@freefall.cdrom.com In-Reply-To: <199506201242.IAA09685@combs.salem.ge.com> from "Stephen F. Combs" at Jun 20, 95 08:42:40 am Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1105 Sender: bugs-owner@freebsd.org Precedence: bulk In reply to Stephen F. Combs who said > > 2) Using the ST31200, I couldn't get it to accept the > untranslated geometry. The system has ONLY FreeBSD on it > (no DOS, no OS/2, no WinNT). The only way the system would > work, is to create a 1MB DOS partition (which forced > translated geometry) and then delete it and assign the > entire disk to FreeBSD. > Had the same problem. Nothing on the disk at all, completely new disk Couldn't install FreeBSD on it for two reasons. 1) sysinstall no longer allows BIOS-invalid geomtries. I was greeted by an error message "geometry invalid (or something like that)". 2) I didn't know what the NCR standard geometry was. Result: Had to install DOS to find out what geometry to use. There must be some way to do this. Is there something we can do from the botblock before going to protected mode to find out what the SCSI BIOS is going to default to? -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-bugs Thu Jun 22 07:26:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA10197 for bugs-outgoing; Thu, 22 Jun 1995 07:26:17 -0700 Received: from todonix.ping.de (root@todonix.ping.de [193.100.14.43]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA10172 for ; Thu, 22 Jun 1995 07:25:53 -0700 Received: by todonix.ping.de (Smail3.1.28.1 #1) id m0sOn9t-00075wC; Thu, 22 Jun 95 16:23 MET DST Message-Id: From: jan@todonix.ping.de (Jan Wedekind) Subject: Re: 2.05R reboot hangs To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 22 Jun 1995 16:23:05 +0200 (MET DST) Cc: bugs@freebsd.org In-Reply-To: <199506182323.QAA02555@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 18, 95 04:23:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 434 Sender: bugs-owner@freebsd.org Precedence: bulk Hallo Rod & Bug-Readers, > > sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). > > CHeck that you have your external cache set to write-through mode, > and ISA GAT mode disabled in the BIOS setup screens. > Well Rod, thank you for the hint (it was not on write-through and ISA GAT was enabled), but the problem remains; and it seems, that about each 2nd reboot fails. any further suggestions ? Thanxs, Jan From owner-freebsd-bugs Thu Jun 22 09:10:15 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA14577 for bugs-outgoing; Thu, 22 Jun 1995 09:10:15 -0700 Received: from mpp.com (mpp.Minn.Net [204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA14570 for ; Thu, 22 Jun 1995 09:10:13 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id LAA03697 for freebsd-bugs@freebsd.org; Thu, 22 Jun 1995 11:10:11 -0500 From: Mike Pritchard Message-Id: <199506221610.LAA03697@mpp.com> Subject: Majordomo problems To: freebsd-bugs@freebsd.org Date: Thu, 22 Jun 1995 11:10:10 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 596 Sender: bugs-owner@freebsd.org Precedence: bulk It looks like the subcription lists for most of the popular mailing lists got trashed. I noticed that I wasn't getting any mail from hackers, current & questions. Checking with Majordomo showed that I wasn't subscribed anymore, and neither was anyone else! It looks like this happened sometime in the last 24 hours, since I have some freebsd-questions mail from yesterday. Freebsd-bugs still looks good, so I'm sending this there. Can someone go take a look and see what happened? -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-bugs Thu Jun 22 10:29:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA17999 for bugs-outgoing; Thu, 22 Jun 1995 10:29:02 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA17993 for ; Thu, 22 Jun 1995 10:29:00 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA06690; Thu, 22 Jun 1995 10:25:21 -0700 From: "Rodney W. Grimes" Message-Id: <199506221725.KAA06690@gndrsh.aac.dev.com> Subject: Re: 2.05R reboot hangs To: jan@todonix.ping.de (Jan Wedekind) Date: Thu, 22 Jun 1995 10:25:21 -0700 (PDT) Cc: bugs@freebsd.org In-Reply-To: from "Jan Wedekind" at Jun 22, 95 04:23:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1051 Sender: bugs-owner@freebsd.org Precedence: bulk > > Hallo Rod & Bug-Readers, > > > > sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). > > > > CHeck that you have your external cache set to write-through mode, > > and ISA GAT mode disabled in the BIOS setup screens. > > > Well Rod, thank you for the hint (it was not on write-through > and ISA GAT was enabled), but the problem remains; > > and it seems, that about each 2nd reboot fails. > > any further suggestions ? Have you customized the kernel for the machine? Or are you running the GENERIC kernel. I have had 2 sites report ASUS-PCI/I-486SP3G boot hangs when using the GENERIC kernel (though I can not duplicate them here) that went away once they built a kernel specifically for the hardware they had. Have you triple checked your SCSI bus termination, and when the hang happens does your SCSI drive LED tend to be on solid indicating a scsi bus hang? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Thu Jun 22 12:00:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA20629 for bugs-outgoing; Thu, 22 Jun 1995 12:00:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA20622 ; Thu, 22 Jun 1995 12:00:01 -0700 Date: Thu, 22 Jun 1995 12:00:01 -0700 Message-Id: <199506221900.MAA20622@freefall.cdrom.com> From: Ollivier Robert Reply-To: Ollivier Robert To: freebsd-bugs Subject: kern/540: ed0 is loosing packets on input In-Reply-To: Your message of Thu, 22 Jun 1995 20:12:59 +0200 (MET DST) <199506221812.UAA07756@keltia.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 540 >Category: kern >Synopsis: ed0 is loosing packets on input >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 22 12:00:00 1995 >Originator: Ollivier Robert >Organization: A Happy FreeBSD 2.1-current Usenet Site >Release: FreeBSD 2.0-BUILT-19950618 i386 >Environment: 486DX-33, 32 MB SMC 8013EP in 16 bits mode CTM cvs-cur #786 date: 19950617080001Z FreeBSD 2.0-BUILT-19950618 #3: Sun Jun 18 00:08:36 MET DST 1995 roberto@keltia:/src/src/sys/compile/KELTIA CPU: i486DX (486-class CPU) real memory = 33161216 (8096 pages) avail memory = 31420416 (7671 pages) Probing for devices on the ISA bus: [...] ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:4d:ed:08, type WD8013EP (16 bit) bpf: ed0 attached Tadpole Sparcbook with build-in ethernet. Kernel config file : ------------------------------------------------------------ machine "i386" cpu "I486_CPU" ident "KELTIA" maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Berkeley Fast Filesystem options LFS #Berkeley Log Filesystem options PROCFS #Berkeley proc Filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_2_DEF" #hack for the mp1624 options UCONSOLE #for xconsole options "AUTO_EOI_1" options "AUTO_EOI_2" options DUMMY_NOPS options TEST_LABELLING options "COMPAT_LINUX" options SYSVSHM options SYSVSEM options SYSVMSG options "SHMMAXPGS=128" # 512 KB of sharable memory options GATEWAY options KTRACE config kernel root on sd0 swap on sd0 and sd1 and sd2 dumps on sd0 controller isa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr controller scbus0 at bt0 disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 tape st0 at scbus0 target 4 device cd0 at scbus0 target 6 # new sound config. controller snd0 device sb0 at isa? port 0x220 irq 5 drq 3 vector sbintr device opl0 at isa? port 0x388 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 24 pseudo-device speaker pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device disc #Discard device pseudo-device tun 1 #Enable user-level PPP see ppp(8) ------------------------------------------------------------ >Description: The ethernet driver is having a lot of error on incoming packets. Transfert between Keltia (FreeBSD-current) and Sidhe (Sparcbook 2) : 489 [19:56] roberto@keltia:networking/dns> ncftp sidhe:/sources/networking/dns/bind-4.9.3-BETA21.tar.gz Receiving file: /sources/networking/dns/bind-4.9.3-BETA21.tar.gz 100% 0 1583300 bytes. ETA: 0:00 /sources/networking/dns/bind-4.9.3-BETA21.tar.gz: 1583300 bytes received in 34.60 seconds, 44.68 K/s. ^^^^^^^^^^ @keltia:~# netstat -i VVVVV Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 87471 560 77750 0 6 ed0 1500 FR-ATL-NET keltia.frmug.fr 87471 560 77750 0 6 lp0* 1500 0 0 0 0 0 ds0* 65532 0 0 0 0 0 lo0 16384 6377 0 6377 0 0 lo0 16384 127 localhost 6377 0 6377 0 0 ppp0* 1500 9993 1 10517 0 0 sl0* 552 0 0 0 0 0 tun0* 1500 0 0 0 0 0 295 [19:57] root@keltia:~# netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 90396 598 81004 0 6 ed0 1500 FR-ATL-NET keltia.frmug.fr 90396 598 81004 0 6 lp0* 1500 0 0 0 0 0 ds0* 65532 0 0 0 0 0 lo0 16384 6540 0 6540 0 0 lo0 16384 127 localhost 6540 0 6540 0 0 ppp0* 1500 9993 1 10517 0 0 sl0* 552 0 0 0 0 0 tun0* 1500 0 0 0 0 0 The error rate is high... When doing a transfert from Keltia to Sidhe, the speed is better (240 Kbps) but not lighting quick either. There are only the 2 machines on the ethernet. 297 [20:02] root@keltia:~# netstat -i VVVVV Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 91336 599 82386 0 6 ed0 1500 FR-ATL-NET keltia.frmug.fr 91336 599 82386 0 6 lp0* 1500 0 0 0 0 0 ds0* 65532 0 0 0 0 0 lo0 16384 6562 0 6562 0 0 lo0 16384 127 localhost 6562 0 6562 0 0 ppp0* 1500 9993 1 10517 0 0 sl0* 552 0 0 0 0 0 tun0* 1500 0 0 0 0 0 298 [20:02] root@keltia:~# netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.4d.ed.08 91988 601 83307 0 6 ed0 1500 FR-ATL-NET keltia.frmug.fr 91988 601 83307 0 6 lp0* 1500 0 0 0 0 0 ds0* 65532 0 0 0 0 0 lo0 16384 6573 0 6573 0 0 lo0 16384 127 localhost 6573 0 6573 0 0 ppp0* 1500 9993 1 10517 0 0 sl0* 552 0 0 0 0 0 tun0* 1500 0 0 0 0 0 >How-To-Repeat: FTP a file from/to Keltia shows this behaviour each time. This behaviour seems new but I cannot garantee when it started :-( >Fix: Unknown unfortunately. Open to suggestions, tests. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 22 12:17:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21400 for bugs-outgoing; Thu, 22 Jun 1995 12:17:20 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA21394 for ; Thu, 22 Jun 1995 12:17:16 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA03437 (5.65c8/HUTCS-S 1.4 for ); Thu, 22 Jun 1995 22:16:28 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id WAA26209; Thu, 22 Jun 1995 22:16:37 +0300 Date: Thu, 22 Jun 1995 22:16:37 +0300 Message-Id: <199506221916.WAA26209@shadows.cs.hut.fi> To: Mike Pritchard Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: Mike Pritchard's message of 22 Jun 1995 19:16:08 +0300 Subject: Majordomo problems Organization: Helsinki University of Technology, Otaniemi, Finland Sender: bugs-owner@FreeBSD.org Precedence: bulk Majordomo showed that I wasn't subscribed anymore, and neither was anyone else! It looks like this happened sometime in the Majordomo doesn't handle cleanly disk becoming full while it is adding or removing users on lists. Ie. it zeroes the list in question. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-bugs Thu Jun 22 12:33:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA22244 for bugs-outgoing; Thu, 22 Jun 1995 12:33:32 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA22237 for ; Thu, 22 Jun 1995 12:33:29 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id VAA25478 for ; Thu, 22 Jun 1995 21:33:06 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id VAA04530 for freebsd-bugs@FreeBSD.ORG; Thu, 22 Jun 1995 21:33:06 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.7.Beta.5/keltia-uucp-2.2) id VAA08206 for freebsd-bugs@FreeBSD.ORG; Thu, 22 Jun 1995 21:20:39 +0200 (MET DST) From: Ollivier Robert Message-Id: <199506221920.VAA08206@keltia.frmug.fr.net> Subject: Pb with some tapes To: freebsd-bugs@FreeBSD.ORG (FreeBSD Bugs' list) Date: Thu, 22 Jun 1995 21:20:39 +0200 (MET DST) Reply-To: roberto@keltia.freenix.fr (Ollivier Robert) X-Operating-System: FreeBSD 2.0-BUILT-19950618 ctm#786 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: bugs-owner@FreeBSD.ORG Precedence: bulk I have a problem with some tapes produced with a 60 MB tape drive (Archive). I don't have the exact model but I guess it is a 2060S. Sympthoms : reading the table of content is satisfactory : 370 [21:11] roberto@keltia:/sources/sound> tar tv -rw-r--r-- regnauld/bin 2485966 Jun 20 20:26 1995 condat_france_culture.au.gz Then trying to extract the file yields the following result : 372 [21:13] roberto@keltia:/sources/sound> tar xv tar: read error on /dev/rst0 : Input/output error 373 [21:13] roberto@keltia:/sources/sound> tar xv tar: read error on /dev/rst0 : Input/output error and the following messages appear in syslog : st0(bt0:4:0): ILLEGAL REQUEST field replaceable unit: 20 st0: Cannot set selected modest0: oops not queued st0(bt0:4:0): ILLEGAL REQUEST field replaceable unit: 20 st0: Cannot set selected modest0: oops not queued Getting the tape out of the drive and back is satisfactory : 374 [21:15] roberto@keltia:/sources/sound> tar xv condat_france_culture.au.gz but trying to reread the tape doesn't work : 375 [21:18] roberto@keltia:/sources/sound> tar tv tar: read error on /dev/rst0 : Input/output error To resume, dealing with 60 MB works the first time (on /dev/rst0) but not afterward. When dealing with multiple filesets per tape, it also fails unless one use the /dev/nrst0 (I know I should use it but I typed /dev/rst0 by mistake and the problem first appeared). -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.0-BUILT-19950618 #3: Sun Jun 18 00:08:36 MET DST 1995 From owner-freebsd-bugs Thu Jun 22 12:47:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA22824 for bugs-outgoing; Thu, 22 Jun 1995 12:47:58 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA22814 for ; Thu, 22 Jun 1995 12:47:51 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id VAA25591 for ; Thu, 22 Jun 1995 21:47:47 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id VAA04584 for freebsd-bugs@FreeBSD.ORG; Thu, 22 Jun 1995 21:47:46 +0200 Received: (from roberto@localhost) by keltia.frmug.fr.net (8.7.Beta.5/keltia-uucp-2.2) id VAA08362 for freebsd-bugs@FreeBSD.ORG; Thu, 22 Jun 1995 21:47:13 +0200 (MET DST) From: Ollivier Robert Message-Id: <199506221947.VAA08362@keltia.frmug.fr.net> Subject: Re: kern/540: ed0 is loosing packets on input To: freebsd-bugs@FreeBSD.ORG (FreeBSD Bugs' list) Date: Thu, 22 Jun 1995 21:47:13 +0200 (MET DST) Reply-To: roberto@keltia.freenix.fr (Ollivier Robert) In-Reply-To: <199506221900.MAA20618@freefall.cdrom.com> from "FreeBSD-gnats@freefall.cdrom.com" at Jun 22, 95 12:00:00 pm X-Operating-System: FreeBSD 2.0-BUILT-19950618 ctm#786 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: bugs-owner@FreeBSD.ORG Precedence: bulk It seems that FreeBSD-gnats@freefall.cdrom.com said: > Date: Thu, 22 Jun 1995 12:00:00 -0700 > Message-Id: <199506221900.MAA20618@freefall.cdrom.com> > To: roberto@keltia.frmug.fr.net ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > From: FreeBSD-gnats@freefall.cdrom.com [...] > Thank you very much for your problem report. > It has the internal identification `kern/540'. > The individual assigned to look at your > bug is: freebsd-bugs (FreeBSD bugs mailing list). > > >Category: kern > >Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >Synopsis: ed0 is loosing packets on input > >Arrival-Date: Thu Jun 22 12:00:00 1995 The program used by GNATS is ignoring the Reply-To: header I have in my mails : env: REPLYTO=roberto@keltia.freenix.fr (Ollivier Robert) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia 2.0-BUILT-19950618 #3: Sun Jun 18 00:08:36 MET DST 1995 From owner-freebsd-bugs Thu Jun 22 13:41:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA24725 for bugs-outgoing; Thu, 22 Jun 1995 13:41:50 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA24718 for ; Thu, 22 Jun 1995 13:41:45 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA08702; Fri, 23 Jun 1995 04:55:43 +1000 Date: Fri, 23 Jun 1995 04:55:43 +1000 From: Bruce Evans Message-Id: <199506221855.EAA08702@godzilla.zeta.org.au> To: bde@zeta.org.au, hlew@cycle.Stanford.EDU Subject: Re: 2.05R panics on boot Cc: bugs@freebsd.org, terry@cs.weber.edu Sender: bugs-owner@freebsd.org Precedence: bulk >> then it must be installed on the first drive. Where does FreeBSD put >> it if you install FreeBSD on the second drive? >I have not figured out the last question yet. But I'll see if I can >install os-bs also on my second drive. Is it possible? I tried last >night with os-bs, but it would only write to the first drive. That's where it should be, but the FreeBSD install apparently either doesn't install it or wants to write it to the FreeBSD drive(s). The latter works if FreeBSD is on the first drive. Bruce From owner-freebsd-bugs Thu Jun 22 13:59:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA25364 for bugs-outgoing; Thu, 22 Jun 1995 13:59:53 -0700 Received: from marmite.Stanford.EDU (2842@marmite.Stanford.EDU [36.159.0.58]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA25358 for ; Thu, 22 Jun 1995 13:59:51 -0700 Received: (hlew@localhost) by marmite.Stanford.EDU (8.6.10/8.6.4) id NAA05767; Thu, 22 Jun 1995 13:59:36 -0700 Date: Thu, 22 Jun 1995 13:59:35 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506182125.AA19481@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sun, 18 Jun 1995, Terry Lambert wrote: > What you need to do is: > > 1) Make sure DM is on the first drive [this is done] done > > 2) Boot the first drive under DOS to activate the DM INT 13 > redirector. done > > 3) Use the DOS installation to install OS-BS onto the first drive > as a replacement for the displace DOS MBR. The partition table > will exist in the OS-BS MBR instead of the DOS MBR. > done > *) At this point, you should be able to boot of the first drive into > the OS-BS menu and select "DOS", acusing the DOS to boot correctly. > Do not proceed past this point until this is the case. > done > 4) At this point you should be able to ask it to boot of the second > drive (assuming you have OS-BS installed correctly. This will > fail, but you should make sure that you can attempt to boot off > the second drive. > yes it fails. but done. > > Subsequent steps will [potentially] require the reinstallation of BSD. > If you are not prepared to do this, you should rely on booting with a > floppy. To make it more convenient, you can change the default device > in the floppy boot blocks, which will result in the floppy booting the > correct device. The method for doing this is well documented in the > hackers list archive on freefall.cdrom.com. This archive can also be > accessed via www at http://www.freebsd.org. > > 5) Install OS-BS on the second drive. This may or may not be > easy to accomplish. If the partition table on the second os-bs would not install on the second drive, so I had to use booteasy instead. > drive is a remnant of a DOS install, then this will be easy; > otherwise you will have to use the DOS command fdisk/mbr on > the second DOS drive. YOU MUST GIVE THE DOS DRIVE LETTER AS > A PARAMETER. In addition, the /mbr option is not available > in DOS revisions prior to 5.0. At this point you can install > OS-BS and reinstall BSD. > > Now when you boot, you will get an option to choose the DOS partition > or the second drive. Tho boot BSD, choose the second drive option in > the OS-BS menu. You will get another OS-BS menu (the DOS option in > this menus will not work). Choose the FreeBSD option, and it should > boot correctly. > The system starts up with the Ontrack DM dynamic overlay, and then goes into os-bs, and I am presented with a menu for DOS or FreeBSD. I choose FreeBSD, and I see the booteasy prompt for BSD or Disk 1. I choose BSD, but the system hangs. I also tried booting with booteasy installed on both drives. It still hangs after I choose BSD for the second drive. DOS boots okay though. I guess I'll have to boot from a modified boot.flp. From owner-freebsd-bugs Thu Jun 22 14:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA27161 for bugs-outgoing; Thu, 22 Jun 1995 14:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA27154 ; Thu, 22 Jun 1995 14:40:01 -0700 Date: Thu, 22 Jun 1995 14:40:01 -0700 Message-Id: <199506222140.OAA27154@freefall.cdrom.com> From: regnauld@tetard.frmug.fr.net Reply-To: regnauld@tetard.frmug.fr.net To: freebsd-bugs Subject: i386/541: Alternate Reset method by unmapping ALSO broken In-Reply-To: Your message of Thu, 22 Jun 1995 20:01:46 +0200 <199506221801.UAA01032@tetard.freenix.fr> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 541 >Category: i386 >Synopsis: Alternate Reset method by unmapping ALSO broken >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 22 14:40:01 1995 >Originator: Philippe Regnauld >Organization: >Release: FreeBSD 2.0-BUILT-19950615 i386 >Environment: - 486 DX 2/80 (*Processor is AMD*) - Motherboard is 30pin/72pin RAM 486 VLB Isa (keyboard controller could not be located) - FreeBSD 2.0.5 current >Description: Keyboard Reset supposedly bogus, and shutdown -r or reboot systematically produces: Keyboard reset did not work, attempting CPU shutdown ... and then the system hangs. I've tried localizing the problem by inserting visual checkpoints in /sys/i386/i386/vm_machdep.c (line 786+) ---- /* force a shutdown by unmapping entire address space ! */ -> printf("Unmapping address space:"); bzero((caddr_t) PTD, NBPG); -> printf(" Done.\n"); /* "good night, sweet prince .... " */ -> printf("Pmap Update:"); pmap_update(); -> printf(" Done.\n"); /* NOTREACHED */ while(1); --- After recompiling a kernel and booting it, the result is this: Keyboard reset did not work, attempting CPU shutdown Unmapping address space: ... and nothing more. Obviously bzero((caddr_t) PTD, NBPG) never makes it... (Pretty annoying, as I can't be away long if it crashes and attempts to reboot while I'm not around (like this summer...)) >How-To-Repeat: # shutdown -r now or # reboot >Fix: Unknown. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jun 22 14:54:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA27708 for bugs-outgoing; Thu, 22 Jun 1995 14:54:29 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA27698 for ; Thu, 22 Jun 1995 14:54:26 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA08312; Thu, 22 Jun 1995 14:54:16 -0700 From: "Rodney W. Grimes" Message-Id: <199506222154.OAA08312@gndrsh.aac.dev.com> Subject: Re: i386/541: Alternate Reset method by unmapping ALSO broken To: regnauld@tetard.frmug.fr.net Date: Thu, 22 Jun 1995 14:54:16 -0700 (PDT) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506222140.OAA27154@freefall.cdrom.com> from "regnauld@tetard.frmug.fr.net" at Jun 22, 95 02:40:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2884 Sender: bugs-owner@FreeBSD.org Precedence: bulk > Attempting to debug this piece of code with printf's is futile!! You need to either use an Intel ICE emulator or use inline asm outb's to a latch port with LED's on it. Attempting to call printf ofter an unmap of the address space usually sends you to never never land. Put the code back to the stock code and try just the option to not use the keyboard reset. Your printfs may be causing more problems. If this still fails let me know..., it means you have 2 bugs, a broken keyboard controller, and a motherboard that does not correctly detect a CPU shutdown condition. Not that uncommon in the high volume low dollar VLB ISA motherboard market :-(. The real sad news is I don't have another alternative at this time to try to make the thing report, perhaps it has the port 92 alternate reset logic. > > >Number: 541 > >Category: i386 > >Synopsis: Alternate Reset method by unmapping ALSO broken > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-bugs (FreeBSD bugs mailing list) > >State: open > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Thu Jun 22 14:40:01 1995 > >Originator: Philippe Regnauld > >Organization: > >Release: FreeBSD 2.0-BUILT-19950615 i386 > >Environment: > > - 486 DX 2/80 (*Processor is AMD*) > - Motherboard is 30pin/72pin RAM 486 VLB Isa > (keyboard controller could not be located) > - FreeBSD 2.0.5 current > > >Description: > > Keyboard Reset supposedly bogus, and shutdown -r or reboot > systematically produces: > > Keyboard reset did not work, attempting CPU shutdown > > ... and then the system hangs. > > I've tried localizing the problem by inserting visual checkpoints > in /sys/i386/i386/vm_machdep.c (line 786+) > > ---- > > /* force a shutdown by unmapping entire address space ! */ > -> printf("Unmapping address space:"); > bzero((caddr_t) PTD, NBPG); > -> printf(" Done.\n"); > > /* "good night, sweet prince .... " */ > -> printf("Pmap Update:"); > pmap_update(); > -> printf(" Done.\n"); > > /* NOTREACHED */ > while(1); > > --- > > After recompiling a kernel and booting it, the result is this: > > Keyboard reset did not work, attempting CPU shutdown > Unmapping address space: > > ... and nothing more. > > Obviously bzero((caddr_t) PTD, NBPG) never makes it... > (Pretty annoying, as I can't be away long if it crashes and > attempts to reboot while I'm not around (like this summer...)) > > >How-To-Repeat: > > # shutdown -r now > or > # reboot > > > >Fix: > > Unknown. > > >Audit-Trail: > >Unformatted: > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Thu Jun 22 15:27:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01404 for bugs-outgoing; Thu, 22 Jun 1995 15:27:04 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA01396 for ; Thu, 22 Jun 1995 15:27:02 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id PAA20462 for ; Thu, 22 Jun 1995 15:25:55 -0700 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.12/8.6.5) with ESMTP id PAA19342 for ; Thu, 22 Jun 1995 15:25:36 -0700 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id NAA00333 for bugs@freebsd.org; Thu, 22 Jun 1995 13:44:39 -0700 Date: Thu, 22 Jun 1995 13:44:39 -0700 From: "Russell L. Carter" Message-Id: <199506222044.NAA00333@geli.clusternet> To: bugs@freebsd.org Subject: st bug again. Sender: bugs-owner@freebsd.org Precedence: bulk Well, my tape is nice and cool today, but has started failing again. Backing up say 100MB works, but attempting to grab the whole 1GB of stuff crashes the system reliably. The symptom is the same, ncrcontrol shows tps decaying to zero, then I lose all the filesystems. An interesting message did show up in /var/log/messages, one time out of four crashes: Jun 22 10:57:49 geli /kernel: st0(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted Jun 22 11:05:13 geli /kernel: st0(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted I used pax -wvf /dev/nrst0. I suppose it could be the drive, unfortunately my easy access is just to FreeBSD systems right now. Here's dmesg: FreeBSD 2.0.5-ALPHA #0: Thu Jun 15 21:05:46 PDT 1995 rcarter@geli.clusternet:/usr/src/sys/compile/RLCDE CPU: 100-MHz Pentium 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 66715648 (16288 pages) avail memory = 63012864 (15384 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 lpt0 at 0x278-0x27f 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 npx0 on motherboard npx0: INT 16 interface Probing for devices on the pci0 bus: configuration mode 1 allows 32 devices. pci0:0: INTEL CORPORATION, device=0x122d, class=bridge [not supported] pci0:7: INTEL CORPORATION, device=0x122e, class=bridge [not supported] ncr0 rev 2 int a irq 9 on pci0:9 reg20: virtual=0xf58a1000 physical=0xfbfef000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) ncr0 waiting for scsi devices to settle (ncr0:1:0): "SEAGATE ST32550N 0012" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2047MB (4194058 512 byte sectors) (ncr0:3:0): "TEAC CD-ROM CD-50 1.06" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): asynchronous. cd0(ncr0:3:0): UNIT ATTENTION asc:28,0 cd0(ncr0:3:0): Not ready to ready transition, medium may have changed cd present.[400000 x 2048 byte records] (ncr0:6:0): "ARCHIVE 4326XX 27871-XXX 494A" type 1 removable SCSI 2 st0(ncr0:6:0): Sequential-Access st0(ncr0:6:0): 200ns (5 Mb/sec) offset 8. density code 0x13, 512-byte blocks, write-enabled vga0 rev 0 int a irq 12 on pci0:10 de0 rev 17 int a irq 10 on pci0:11 reg20: virtual=0xf58a2000 physical=0xfafff000 size=0x80 de0: DC21140 [10-100Mb/s] pass 1.1 Ethernet address 00:00:c0:dd:f7:9d de0: enabling 100baseTX UTP port de1 rev 35 int a irq 11 on pci0:12 reg20: virtual=0xf58a3000 physical=0xfaffe000 size=0x80 de1: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:c0:95:ec:20:ff de1: enabling 10baseT/UTP port pci0: uses 8389120 bytes of memory from faffe000 upto fbfef0ff. pci0: uses 512 bytes of I/O space from d800 upto e4ff. WARNING: / was not properly dismounted. From owner-freebsd-bugs Thu Jun 22 16:22:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA04340 for bugs-outgoing; Thu, 22 Jun 1995 16:22:28 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA04332 ; Thu, 22 Jun 1995 16:22:26 -0700 Message-Id: <199506222322.QAA04332@freefall.cdrom.com> X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Russell L. Carter" cc: bugs@freebsd.org Subject: Re: st bug again. In-reply-to: Your message of "Thu, 22 Jun 95 13:44:39 PDT." <199506222044.NAA00333@geli.clusternet> Date: Thu, 22 Jun 1995 16:22:26 -0700 From: "Justin T. Gibbs" Sender: bugs-owner@freebsd.org Precedence: bulk >Well, my tape is nice and cool today, but has started failing again. >Backing up say 100MB works, but attempting to grab the whole 1GB >of stuff crashes the system reliably. The symptom is the same, >ncrcontrol shows tps decaying to zero, then I lose all the filesystems. > >An interesting message did show up in /var/log/messages, one time >out of four crashes: > >Jun 22 10:57:49 geli /kernel: st0(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapp >ed commands attempted >Jun 22 11:05:13 geli /kernel: st0(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapp >ed commands attempted This means that a tagged command was attempted while a non-tagged command was active or vice-versa. My guess in this area would be that a request sense command was pending on the target and hadn't returned when a tagged command was sent to the target. To fix this kind of problem, you need to need to block commands to targets that have pending non-tagged commands. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-bugs Thu Jun 22 16:48:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA05456 for bugs-outgoing; Thu, 22 Jun 1995 16:48:34 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA05450 for ; Thu, 22 Jun 1995 16:48:33 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA04029; Thu, 22 Jun 95 17:41:33 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506222341.AA04029@cs.weber.edu> Subject: Re: i386/541: Alternate Reset method by unmapping ALSO broken To: regnauld@tetard.frmug.fr.net Date: Thu, 22 Jun 95 17:41:33 MDT Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506222140.OAA27154@freefall.cdrom.com> from "regnauld@tetard.frmug.fr.net" at Jun 22, 95 02:40:01 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > /* force a shutdown by unmapping entire address space ! */ > -> printf("Unmapping address space:"); > bzero((caddr_t) PTD, NBPG); > -> printf(" Done.\n"); > > /* "good night, sweet prince .... " */ > -> printf("Pmap Update:"); > pmap_update(); > -> printf(" Done.\n"); > > /* NOTREACHED */ > while(1); > > --- > > After recompiling a kernel and booting it, the result is this: > > Keyboard reset did not work, attempting CPU shutdown > Unmapping address space: > > ... and nothing more. > > Obviously bzero((caddr_t) PTD, NBPG) never makes it... > (Pretty annoying, as I can't be away long if it crashes and > attempts to reboot while I'm not around (like this summer...)) Theory: printf will fail with an unmapped address space. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-bugs Thu Jun 22 17:50:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA08959 for bugs-outgoing; Thu, 22 Jun 1995 17:50:19 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA08953 for ; Thu, 22 Jun 1995 17:50:15 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id RAA09004; Thu, 22 Jun 1995 17:50:08 -0700 From: "Rodney W. Grimes" Message-Id: <199506230050.RAA09004@gndrsh.aac.dev.com> Subject: Re: i386/541: Alternate Reset method by unmapping ALSO broken To: terry@cs.weber.edu (Terry Lambert) Date: Thu, 22 Jun 1995 17:50:08 -0700 (PDT) Cc: regnauld@tetard.frmug.fr.net, freebsd-bugs@freefall.cdrom.com In-Reply-To: <9506222341.AA04029@cs.weber.edu> from "Terry Lambert" at Jun 22, 95 05:41:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1913 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > /* force a shutdown by unmapping entire address space ! */ > > -> printf("Unmapping address space:"); > > bzero((caddr_t) PTD, NBPG); > > -> printf(" Done.\n"); > > > > /* "good night, sweet prince .... " */ > > -> printf("Pmap Update:"); > > pmap_update(); > > -> printf(" Done.\n"); > > > > /* NOTREACHED */ > > while(1); > > > > --- > > > > After recompiling a kernel and booting it, the result is this: > > > > Keyboard reset did not work, attempting CPU shutdown > > Unmapping address space: > > > > ... and nothing more. > > > > Obviously bzero((caddr_t) PTD, NBPG) never makes it... > > (Pretty annoying, as I can't be away long if it crashes and > > attempts to reboot while I'm not around (like this summer...)) > > Theory: printf will fail with an unmapped address space. Not so much theory. I've tried to debug in this area of code in the past. It is quite painful and I found the only practical solution was to go out to Intel and use an ICE to find out just what was going on. What happens depends a lot on just what is in the TLB before we bzero the PTD. If you have the TLB entries that cover the pages for printf then you are usually okay. And since we call printf right before we do the bzero this is normally the case. Take that ``printf("Unmapping address space:");'' out and any later printf is probably going to blow chunks all over the place. Even the fact that this printf: printf("Keyboard reset did not work, attempting CPU shutdown\n"); works on some systems amazes me, as gateA20 should have been slammed by then screwing up any hope of doing much else. I guess if the reset fails so does the gateA20 switch :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Thu Jun 22 21:24:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA19328 for bugs-outgoing; Thu, 22 Jun 1995 21:24:23 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA19322 for ; Thu, 22 Jun 1995 21:24:20 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA10720; Fri, 23 Jun 1995 06:24:15 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA08343; Fri, 23 Jun 1995 06:24:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id AAA26335; Fri, 23 Jun 1995 00:43:01 +0200 From: J Wunsch Message-Id: <199506222243.AAA26335@uriah.heep.sax.de> Subject: Re: Pb with some tapes To: roberto@keltia.freenix.fr Date: Fri, 23 Jun 1995 00:43:00 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199506221920.VAA08206@keltia.frmug.fr.net> from "Ollivier Robert" at Jun 22, 95 09:20:39 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1308 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > I have a problem with some tapes produced with a 60 MB tape drive > (Archive). I don't have the exact model but I guess it is a 2060S. > To resume, dealing with 60 MB works the first time (on /dev/rst0) but not > afterward. When dealing with multiple filesets per tape, it also fails > unless one use the /dev/nrst0 (I know I should use it but I typed /dev/rst0 > by mistake and the problem first appeared). Same happens for any Tandberg QIC drive, but e.g. not for an Archive Viper 150S. I've never digged into the error condition returned by the Tandberg. Interestingly, reading back and forth on the non-rewind device does work, even with intermittent ``mt rewind'' commands, but any ``mt rewoffl'' command is treated like closing the rewind device and will result in an IO error on next access. The error condition is always being cleared by opening and closing the drive door. Btw., i've seen the SCSI tape driver from Data General's DG/UX. Be assured, our Rogue's Gallery is a rather nice hack compared to their drive-dependant kludges. Handling SCSI tapes seems to be a rather non-trivial task, alas. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Thu Jun 22 21:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA20201 for bugs-outgoing; Thu, 22 Jun 1995 21:40:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA20194 ; Thu, 22 Jun 1995 21:40:02 -0700 Date: Thu, 22 Jun 1995 21:40:02 -0700 Message-Id: <199506230440.VAA20194@freefall.cdrom.com> From: Jeffrey Hsu Reply-To: Jeffrey Hsu To: freebsd-bugs Subject: bin/542: typeahead fails after rsh In-Reply-To: Your message of Thu, 22 Jun 1995 21:35:59 -0700 <199506230435.VAA19893@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 542 >Category: bin >Synopsis: typeahead fails after rsh >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 22 21:40:01 1995 >Originator: Jeffrey & >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-2.0.5R >Description: Typing commands before receiving a return prompt from the shell after a rsh command fails. The subsequent commands are lost. >How-To-Repeat: % rsh localhost sleep 5 % echo ^G >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 03:04:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA01415 for bugs-outgoing; Fri, 23 Jun 1995 03:04:48 -0700 Received: from lambda.demon.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA01409 for ; Fri, 23 Jun 1995 03:04:44 -0700 Received: (from paul@localhost) by lambda.demon.co.uk (8.6.11/8.6.9) id LAA06128; Fri, 23 Jun 1995 11:04:30 +0100 From: Paul Richards Message-Id: <199506231004.LAA06128@lambda.demon.co.uk> Subject: Re: Majordomo problems To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Fri, 23 Jun 1995 11:04:29 +0100 (BST) Cc: mpp@legarto.minn.net, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506221916.WAA26209@shadows.cs.hut.fi> from "Heikki Suonsivu" at Jun 22, 95 10:16:37 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 648 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Heikki Suonsivu who said > > > Majordomo showed that I wasn't subscribed anymore, and neither > was anyone else! It looks like this happened sometime in the > > Majordomo doesn't handle cleanly disk becoming full while it is adding or > removing users on lists. Ie. it zeroes the list in question. This seems to be a general FS problem which has bitten me several times. Anyone know what actually takes place and how we could fix it? -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-bugs Fri Jun 23 03:29:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA02301 for bugs-outgoing; Fri, 23 Jun 1995 03:29:38 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA02293 for ; Fri, 23 Jun 1995 03:29:24 -0700 Received: from achill [134.169.34.18] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id LAA10970; Fri, 23 Jun 1995 11:18:47 +0200 Received: from petri@localhost by achill.ibr.cs.tu-bs.de (8.6.10/tubsibr) id LAA29871; Fri, 23 Jun 1995 11:18:45 +0200 Date: Fri, 23 Jun 1995 11:18:45 +0200 From: Stefan Petri Message-Id: <199506230918.LAA29871@achill.ibr.cs.tu-bs.de> To: rgrimes@gndrsh.aac.dev.com CC: jan@todonix.ping.de, bugs@FreeBSD.org In-reply-to: "Rodney W. Grimes"'s message of Thu, 22 Jun 1995 10:25:21 -0700 (PDT) <199506221725.KAA06690@gndrsh.aac.dev.com> Subject: 2.05R reboot hangs Reply-to: petri@ibr.cs.tu-bs.de Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi! > > > sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). > > CHeck that you have your external cache set to write-through mode, > > and ISA GAT mode disabled in the BIOS setup screens. Rodney> Have you customized the kernel for the machine? Or are you running Rodney> the GENERIC kernel. I have had 2 sites report ASUS-PCI/I-486SP3G boot Rodney> hangs when using the GENERIC kernel Rodney> Have you triple checked your SCSI bus termination, and when the hang Rodney> happens does your SCSI drive LED tend to be on solid indicating a Rodney> scsi bus hang? I also have an 486-DX4-100 PCI ASUS SP3G, and with 2.0.5, reboot from GENERIC kernel hangs on about every 2nd try. This was never a problem with the 950412-SNAP, which I have rebootet remotely about 100 times without need to run to the machine's console. I have build a custom kernel only yesterday, I dont know yet if that behaves better. I have cache-write-back and ISA-GAT-enabled, and my SCSI-bus is triple-terminated (dont ask why ;-) but is quiescent when reboot hangs, However, as I said, this was no problem with the SNAP installation. Stefan From owner-freebsd-bugs Fri Jun 23 05:43:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA05100 for bugs-outgoing; Fri, 23 Jun 1995 05:43:41 -0700 Received: from todonix.ping.de (root@todonix.ping.de [193.100.14.43]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA05089 for ; Fri, 23 Jun 1995 05:43:02 -0700 Received: by todonix.ping.de (Smail3.1.28.1 #1) id m0sP81H-00076PC; Fri, 23 Jun 95 14:39 MET DST Message-Id: From: jan@todonix.ping.de (Jan Wedekind) Subject: uucico: page not present in kernel mode To: bugs@freebsd.org Date: Fri, 23 Jun 1995 14:39:34 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 506 Sender: bugs-owner@freebsd.org Precedence: bulk Well, while working with 2.0.5R beneath the hanging on reboot we now got an other error: Fatal Trap 12: page fault while in kernel mode fault virt. Adr = 0x38 code = supervisor read, page not present current process = ... (uucico) (sorry, it was not me who wrote down these notes) Jan -- PING e.V. Jan Wedekind (Kassenwart) jan@ping.de Emil-Figge-Str. 85 Lindemannstr. 12 kasse@ping.de 44227 Dortmund 44137 Dortmund vorstand@ping.de Tel.: 0231 / 97 91 - 0 Tel.: +49 (231) 13 44 04 info@ping.de From owner-freebsd-bugs Fri Jun 23 06:07:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA05535 for bugs-outgoing; Fri, 23 Jun 1995 06:07:32 -0700 Received: from todonix.ping.de (root@todonix.ping.de [193.100.14.43]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA05363 for ; Fri, 23 Jun 1995 05:59:36 -0700 Received: by todonix.ping.de (Smail3.1.28.1 #1) id m0sP8IE-00076BC; Fri, 23 Jun 95 14:57 MET DST Message-Id: From: jan@todonix.ping.de (Jan Wedekind) Subject: Re: 2.05R reboot hangs To: petri@ibr.cs.tu-bs.de Date: Fri, 23 Jun 1995 14:57:05 +0200 (MET DST) Cc: bugs@freebsd.org In-Reply-To: <199506230918.LAA29871@achill.ibr.cs.tu-bs.de> from "Stefan Petri" at Jun 23, 95 11:18:45 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 7358 Sender: bugs-owner@freebsd.org Precedence: bulk Hi again, > I also have an 486-DX4-100 PCI ASUS SP3G, and with 2.0.5, reboot from > GENERIC kernel hangs on about every 2nd try. This was never a problem > with the 950412-SNAP, which I have rebootet remotely about 100 times > without need to run to the machine's console. I have build a that's the same with us! those problems occured with 2.0.5R > custom kernel only yesterday, I dont know yet if that behaves better. > I have cache-write-back and ISA-GAT-enabled, and my SCSI-bus is > triple-terminated (dont ask why ;-) but is quiescent when reboot > hangs, However, as I said, this was no problem with the SNAP > installation. > Well, today we tried several things: we started with the following ChipSet setup: DRAM write page Mode Enabled DRAM code read page Mode Enabled DRAM refresh mode Normal DRAM wait state 0 CPU to DRAM write buffer Enabled CPU to PCI write buffer Enabled PCI to DRAM write buffer Enabled PCI memory burst Disabled Video BIOS cache Disabled Ext. Cache WS 0 Cache update policy Wr-Through PCI posted write buffer Enabled ISA GAT mode Disabled DMA line buffer mode Standard ISA master buffer mode Standard and we tested the machine (partly without the 2nd NCR Controller) until we reached the BIOS defaults (all features disabled, Write Throu, 1 Wait State). The behaviour remained, but now it more occured randomly, about each 3rd or 4th time. Eventually we should test it with an other Kernel where only the really nessesary drivers are configured ? (our kernel config as follows) Jan kernel config LEARY: machine "i386" cpu "I486_CPU" ident GATE maxusers 32 #options MATH_EMULATE #Support for x87 emulation options "OPEN_MAX=256" options "CHILD_MAX=128" config kernel root on sd0 swap on sd0 dumps on sd0 options "COMPAT_43" # WINE support #options USER_LDT #allow user-level control of i386 ldt # System V IPC support #options SYSVSHM #options SYSVSEM #options SYSVMSG # Debug options #options DDB options KTRACE #options DIAGNOSTIC # needed for running X #options UCONSOLE # Network options INET #Internet communications protocols #options CCITT #X.25 network layer #options NS #Xerox NS communications protocols # Network devices pseudo-device ether #Generic Ethernet #pseudo-device fddi #Generic FDDI pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device sl 20 #Serial Line IP pseudo-device ppp 20 #Point-to-point protocol #pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) #options NSIP #XNS over IP #options LLC #X.25 link layer for Ethernets #options HDLC #X.25 link layer for serial lines # INET options options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options GATEWAY #internetwork gateway options MROUTING # Multicast routing #options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #print information about options IPACCT #ipaccounting # dropped packets #options ARP_PROXYALL # global proxy ARP # Filesystem options options FFS #Fast filesystem options NFS #Network File System #options NQNFS #Enable NQNFS lease checking #options "CD9660" #ISO 9660 filesystem #options FDESC #File descriptor filesystem #options KERNFS #Kernel filesystem #options LFS #Log filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System #options NULLFS #NULL filesystem #options PORTAL #Portal filesystem options PROCFS #Process filesystem #options UMAPFS #UID map filesystem #options UNION #Union filesystem # Make space in the kernel for a MFS rootfilesystem. Define to the number # of kilobytes to reserve for the filesystem. #options "MFS_ROOT=10" # Allow this many swap-devices. options "NSWAPDEV=2" # SCSI controller pci0 controller ncr0 controller scbus0 device sd0 device sd1 device sd2 device sd3 device st0 # the scsi-code needs cdinit(), so don't remove! device cd0 #Only need one of these, the code dynamically grows #controller scbus0 #base SCSI code #device ch0 #SCSI media changers #device sd0 #SCSI disks #device st0 #SCSI tapes #device cd0 #SCSI CD-ROMs #device worm0 at scbus? # SCSI worm #device pt0 at scbus? # SCSI processor type #device sctarg0 at scbus? # SCSI target #options SCSIDEBUG #options NO_SCSI_SENSE #options SCSI_REPORT_GEOMETRY # misc. devices and options pseudo-device pty 32 #Pseudo ttys - can go as high as 64 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. # These are non-optional for ISDN #pseudo-device isdn #pseudo-device ii 4 #pseudo-device ity 4 #pseudo-device itel 2 #pseudo-device ispy 1 # Hardware device configuration controller isa0 options "AUTO_EOI_1" #options "AUTO_EOI_2" options BOUNCE_BUFFERS #options DUMMY_NOPS #options "TUNE_1542" #options "BROKEN_KEYBOARD_RESET" # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # The syscons console driver (sco color console compatible) - default. device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr #options HARDFONTS options "MAXCONS=4" device npx0 at isa? port "IO_NPX" irq 13 vector npxintr #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # Other standard PC hardware device lpt0 at isa? port? tty #device lpt0 at isa? port "IO_LPT3" tty irq 7 vector lptintr #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr # Options for sio: #options COMCONSOLE #prefer serial console to video console #options COM_MULTIPORT #code for some cards with shared IRQs #options DSI_SOFT_MODEM #code for DSI Softmodems #options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to options COM_MULTIPORT # 1st AST board device sio2 at isa? port "0x2a0" tty flags 0x0501 vector siointr device sio3 at isa? port "0x2a8" tty flags 0x0501 vector siointr device sio4 at isa? port "0x2b0" tty flags 0x0501 vector siointr device sio5 at isa? port "0x2b8" tty irq 7 flags 0x0501 iomem 0x02bf vector siointr # 2nd AST board device sio6 at isa? port "0x1a0" tty flags 0x0901 vector siointr device sio7 at isa? port "0x1a8" tty flags 0x0901 vector siointr device sio8 at isa? port "0x1b0" tty flags 0x0901 vector siointr device sio9 at isa? port "0x1b8" tty irq 5 flags 0x0901 iomem 0x01bf vector siointr device ed0 at isa? port 0x300 net irq 12 iomem 0xd8000 vector edintr device cy0 at isa? tty irq 10 iomem 0xd4000 iosiz 0x2000 vector cyintr device cy1 at isa? tty irq 11 iomem 0xd6000 iosiz 0x2000 vector cyintr From owner-freebsd-bugs Fri Jun 23 07:21:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA06974 for bugs-outgoing; Fri, 23 Jun 1995 07:21:25 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA06965 ; Fri, 23 Jun 1995 07:21:24 -0700 Date: Fri, 23 Jun 1995 07:21:24 -0700 Message-Id: <199506231421.HAA06965@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (stefan Petri) To: freebsd-bugs Subject: kern/543: pci_bus_config() does not init parent pointers in device list + fix In-Reply-To: Your message of Tue, 20 Jun 1995 22:06:09 +0200 <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 543 >Category: kern >Synopsis: pci_bus_config() does not init parent pointers in device list >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:21:23 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:21:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07066 for bugs-outgoing; Fri, 23 Jun 1995 07:21:50 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07059 ; Fri, 23 Jun 1995 07:21:50 -0700 Date: Fri, 23 Jun 1995 07:21:50 -0700 Message-Id: <199506231421.HAA07059@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (stefan Petri) To: freebsd-bugs Subject: kern/544: pci_bus_config() does not init parent pointers in device list + fix In-Reply-To: Your message of Tue, 20 Jun 1995 22:06:09 +0200 <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 544 >Category: kern >Synopsis: pci_bus_config() does not init parent pointers in device list >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:21:49 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:27:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07347 for bugs-outgoing; Fri, 23 Jun 1995 07:27:19 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07340 ; Fri, 23 Jun 1995 07:27:18 -0700 Date: Fri, 23 Jun 1995 07:27:18 -0700 Message-Id: <199506231427.HAA07340@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (stefan Petri) To: freebsd-bugs Subject: kern/546: pci_bus_config() does not init parent pointers in device list + fix In-Reply-To: Your message of Tue, 20 Jun 1995 22:06:09 +0200 <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 546 >Category: kern >Synopsis: pci_bus_config() does not init parent pointers in device list >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:27:18 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:34:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07738 for bugs-outgoing; Fri, 23 Jun 1995 07:34:27 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07731 ; Fri, 23 Jun 1995 07:34:26 -0700 Date: Fri, 23 Jun 1995 07:34:26 -0700 Message-Id: <199506231434.HAA07731@freefall.cdrom.com> From: Lapinsky Alexander Reply-To: Lapinsky Alexander To: freebsd-bugs Subject: bin/544: timed & timedc bugs In-Reply-To: Your message of Mon, 20 Mar 1995 21:05:28 +0300 <199503201805.VAA01545@flox.kiam1.rssi.ru> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 544 >Category: bin >Synopsis: timed & timedc bugs >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:34:19 1995 >Originator: Lapinsky Alexander >Organization: Keldysh Institute of Applied Mathematics, >Organization: Moscow, Russia >Release: FreeBSD 2.0-RELEASE i386 >Environment: >Description: time daemon -- timed: Message displayed: "bind: Can't assign requested address" and very big time difference displayed by timedc clockdiff lotos >How-To-Repeat: I can fix it. I guess, it will be better. >Fix: directory: usr/src/usr.sbin/timed/timed files to patch: measure.c timed.c rebuild: timed timedc -------------------------------- Cut here ---------------------------- *** measure.c.orig Mon Mar 20 16:46:47 1995 --- measure.c Mon Mar 20 20:07:49 1995 *************** *** 151,157 **** */ if (trials < TRIALS) { trials++; ! oicp->icmp_otime = ((tcur.tv_sec % SECDAY) * 1000 + tcur.tv_usec / 1000); oicp->icmp_cksum = 0; oicp->icmp_cksum = in_cksum((u_short*)oicp, --- 151,157 ---- */ if (trials < TRIALS) { trials++; ! oicp->icmp_otime = htonl((tcur.tv_sec % SECDAY) * 1000 + tcur.tv_usec / 1000); oicp->icmp_cksum = 0; oicp->icmp_cksum = in_cksum((u_short*)oicp, *** timed.c.orig Fri Jan 7 18:25:16 1994 --- timed.c Fri Jan 7 18:27:00 1994 *************** *** 312,317 **** --- 312,318 ---- exit(1); } port = srvp->s_port; + bzero(&server,sizeof(struct sockaddr_in)); server.sin_port = srvp->s_port; server.sin_family = AF_INET; sock = socket(AF_INET, SOCK_DGRAM, 0); -------------------------- End of message ---------------------------- >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:35:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07824 for bugs-outgoing; Fri, 23 Jun 1995 07:35:17 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07817 ; Fri, 23 Jun 1995 07:35:16 -0700 Date: Fri, 23 Jun 1995 07:35:16 -0700 Message-Id: <199506231435.HAA07817@freefall.cdrom.com> From: kubus@Austran.Unibase.COM Reply-To: kubus@Austran.Unibase.COM To: freebsd-bugs Subject: kern/545: SCSI DDS tape does not work In-Reply-To: Your message of Tue, 23 May 1995 09:41:39 -0600 <199505231541.JAA00945@Austran.Unibase.COM> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 545 >Category: kern >Synopsis: System can not access SCSI DAT tape. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:35:15 1995 >Originator: Jake J Sadowski >Organization: Home, sweet home. >Release: FreeBSD 2.1.0-Development i386 >Environment: Look at the description, all devices are listed. >Description: /kern: FreeBSD 2.0.950418-SNAP #0: Tue May 23 06:57:31 CST 1995 /kern: root@Austran.Unibase.COM:/usr/src/sys/compile/AUSTRAN /kern: CPU: i486 DX2 (486-class CPU) /kern: Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 /kern: real memory = 16384000 (4000 pages) /kern: avail memory = 15257600 (3725 pages) /kern: Probing for devices on the ISA bus: /kern: sc0 at 0x60-0x6f irq 1 on motherboard /kern: sc0: VGA color <16 virtual consoles, flags=0x0> /kern: sio0 at 0x3f8-0x3ff irq 4 on isa /kern: sio0: type 16450 /kern: sio1 at 0x2f8-0x2ff irq 3 on isa /kern: sio1: type 16550A /kern: sio2 at 0x3e8-0x3ef irq 5 on isa /kern: sio2: type 16550A /kern: lpt0 at 0x378-0x37f irq 7 on isa /kern: lpt0: Interrupt-driven port /kern: lp0: TCP/IP capable interface /kern: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa /kern: fdc0: NEC 765 /kern: fd0: 1.44MB 3.5in /kern: fd1: 1.2MB 5.25in /kern: wdc0 at 0x1f0-0x1f7 irq 14 on isa /kern: wdc0: unit 0 (wd0): /kern: wd0: 813MB (1665216 sectors), 1652 cyls, 16 heads, 63 S/T, 512 B/S /kern: npx0 on motherboard /kern: npx0: INT 16 interface /kern: Probing for devices on the pci0 bus: /kern: configuration mode 1 allows 32 devices. /kern: pci0:0: vendor=0x1080, device=0x600, class=bridge [not supported] /kern: ncr0 rev 2 int a irq 9 on pci0:2 /kern: reg20: virtual=0xf2a91000 physical=0x80000000 size=0x100 /kern: ncr0: restart (scsi reset). /kern: ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) /kern: ncr0 waiting for scsi devices to settle /kern: (ncr0:0:0): 250ns (4 Mb/sec) offset 8. /kern: (ncr0:0:0): "FUJITSU M2263S-512 0189" type 0 fixed SCSI 2 /kern: sd0(ncr0:0:0): Direct-Access 640MB (1312344 512 byte sectors) /kern: (ncr0:6:0): "SONY SDT-5000 3.02" type 1 removable SCSI 2 /kern: st0(ncr0:6:0): Sequential-Access /kern: st0(ncr0:6:0): 200ns (5 Mb/sec) offset 8. /kern: density code 0x13, /kern: ncr0 targ 6?: ERROR (80:140) (e-2e-0) (88/13) @ (3a8:87030000). /kern: reg: da 10 80 13 47 88 6 1f 6 e 86 af 80 0 7 0. /kern: ncr0: restart (fatal error). /kern: /kern: st0(ncr0:6:0): COMMAND FAILED (9 2) @f0503a00. /kern: drive empty /kern: pci0:4: vendor=0x1095, device=0x640, class=storage [not supported] /kern: pci0: uses 256 bytes of memory from 80000000 upto 800000ff. /kern: pci0: uses 256 bytes of I/O space from f000 upto f0ff. I tried the 2.0 release, snap-shots and the most current sources. The tape drive (SONY SDT-5000) works fine with Linux (sorry...) so I do not think that it is any hardware problem. I do not have any access to news, so I do not know if any poor soul already reported any similar problem. I wonder if anyone succeeded with any DAT tape on a NCR53C810 controller. Thanks. ... Jake >How-To-Repeat: It looks rather obvious. >Fix: I wish I knew. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:35:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07911 for bugs-outgoing; Fri, 23 Jun 1995 07:35:59 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07904 ; Fri, 23 Jun 1995 07:35:58 -0700 Date: Fri, 23 Jun 1995 07:35:58 -0700 Message-Id: <199506231435.HAA07904@freefall.cdrom.com> From: taob@gate.sinica.edu.tw Reply-To: taob@gate.sinica.edu.tw To: freebsd-bugs Subject: docs/546: Shared memory manual pages In-Reply-To: Your message of Sun, 4 Jun 1995 11:02:03 +0800 <199506040302.LAA14739@leo.ibms.sinica.edu.tw> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 546 >Category: docs >Synopsis: Shared memory manual pages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:35:58 1995 >Originator: Brian Tao >Organization: Institute of Biomedical Sciences, Academia Sinica >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: >Description: We are missing the man pages for the SHM-related functions in (shminit(), shmget(), shmat(), shmctl(), etc., etc.). Joerg Wunsch suggests: "Since the code is copyrighted by Charles Hannum, maybe NetBSD has them already?" >How-To-Repeat: "man shmget". :) >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:37:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08026 for bugs-outgoing; Fri, 23 Jun 1995 07:37:51 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08017 ; Fri, 23 Jun 1995 07:37:50 -0700 Date: Fri, 23 Jun 1995 07:37:50 -0700 Message-Id: <199506231437.HAA08017@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (stefan Petri) To: freebsd-bugs Subject: kern/547: pci_bus_config() does not init parent pointers in device list + fix In-Reply-To: Your message of Tue, 20 Jun 1995 22:06:09 +0200 <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 547 >Category: kern >Synopsis: pci_bus_config() does not init parent pointers in device list >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:37:49 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:38:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08086 for bugs-outgoing; Fri, 23 Jun 1995 07:38:33 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08079 ; Fri, 23 Jun 1995 07:38:33 -0700 Date: Fri, 23 Jun 1995 07:38:33 -0700 Message-Id: <199506231438.HAA08079@freefall.cdrom.com> From: Stefan Petri Reply-To: Stefan Petri To: freebsd-bugs Subject: i386/548: missing break in isa/if_el.c causes panic in bpf.c + fix In-Reply-To: Your message of Fri, 9 Jun 1995 17:58:15 +0200 <199506091558.RAA05474@achill.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 548 >Category: i386 >Synopsis: missing break in isa/if_el.c causes panic in bpf.c + fix >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:38:32 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0-950412-SNAP i386 >Environment: FreeBSD 2.0-950412-SNAP, some PC with (dont laugh) 3C501 Ethernet card. >Description: The kernel's bpf module panics when turning off promiscous mode on a 3C501 ethernet card (interface el0). The reason is a missing ``break'' statement after the SIOCSIFFLAGS case in the big switch in el_ioctl() in i386/isa/if_el.c >How-To-Repeat: > tcpdump -i el0 tcpdump: listening on el0 [..packet printout deleted..] ^C panic: bpf: ifpromisc failed [..] >Fix: *** /usr/src/sys/i386/isa/if_el.c-2.0-950412-SNAP Wed Apr 12 22:47:48 1995 --- if_el.c Thu Jun 8 19:13:53 1995 *************** *** 768,773 **** --- 768,774 ---- ((ifp->if_flags & IFF_RUNNING) == 0)) el_init(ifp->if_unit); } + break; case SIOCSIFMTU: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:38:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08146 for bugs-outgoing; Fri, 23 Jun 1995 07:38:56 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08139 ; Fri, 23 Jun 1995 07:38:56 -0700 Date: Fri, 23 Jun 1995 07:38:56 -0700 Message-Id: <199506231438.HAA08139@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (Stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (Stefan Petri) To: freebsd-bugs Subject: bin/549: make chokes on empty rules + fix In-Reply-To: Your message of Mon, 12 Jun 1995 11:05:36 +0200 <199506120905.LAA14341@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 549 >Category: bin >Synopsis: make chokes on empty rules + fix >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:38:55 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: Any FreeBSD >Description: make aborts with fatal error if a Makefile rule line contains a tab followed by an emtpy shell command line. This is very annoying, because the Makefiles in almost every piece of software on the net contain such lines, notably Makefiles that are generated by the gnu configure utility. The correctness of such lines might be arguable, but since every other version of make simply ignores such lines, I propose the following fix, which will print out a warning about such a line, but will continue to make the target. [send-pr did not like ``Severity: seriuosly annoying'' ;-] >How-To-Repeat: Creat a Makefile with only a tabulator in a rule line, then invoke make. >Fix: *** /usr/src/usr.bin/make/parse.c-950412-SNAP Mon Jan 23 22:01:46 1995 --- parse.c Mon Jun 12 10:44:13 1995 *************** *** 715,721 **** * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_FATAL, "Need an operator"); return; } *cp = '\0'; --- 715,721 ---- * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_WARNING, "Need an operator"); return; } *cp = '\0'; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:40:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08219 for bugs-outgoing; Fri, 23 Jun 1995 07:40:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08208 ; Fri, 23 Jun 1995 07:40:01 -0700 Date: Fri, 23 Jun 1995 07:40:01 -0700 Message-Id: <199506231440.HAA08208@freefall.cdrom.com> From: kubus@Austran.Unibase.COM Reply-To: kubus@Austran.Unibase.COM To: freebsd-bugs Subject: kern/550: SCSI DDS tape does not work In-Reply-To: Your message of Tue, 23 May 1995 09:41:39 -0600 <199505231541.JAA00945@Austran.Unibase.COM> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 550 >Category: kern >Synopsis: System can not access SCSI DAT tape. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:40:01 1995 >Originator: Jake J Sadowski >Organization: Home, sweet home. >Release: FreeBSD 2.1.0-Development i386 >Environment: Look at the description, all devices are listed. >Description: /kern: FreeBSD 2.0.950418-SNAP #0: Tue May 23 06:57:31 CST 1995 /kern: root@Austran.Unibase.COM:/usr/src/sys/compile/AUSTRAN /kern: CPU: i486 DX2 (486-class CPU) /kern: Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 /kern: real memory = 16384000 (4000 pages) /kern: avail memory = 15257600 (3725 pages) /kern: Probing for devices on the ISA bus: /kern: sc0 at 0x60-0x6f irq 1 on motherboard /kern: sc0: VGA color <16 virtual consoles, flags=0x0> /kern: sio0 at 0x3f8-0x3ff irq 4 on isa /kern: sio0: type 16450 /kern: sio1 at 0x2f8-0x2ff irq 3 on isa /kern: sio1: type 16550A /kern: sio2 at 0x3e8-0x3ef irq 5 on isa /kern: sio2: type 16550A /kern: lpt0 at 0x378-0x37f irq 7 on isa /kern: lpt0: Interrupt-driven port /kern: lp0: TCP/IP capable interface /kern: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa /kern: fdc0: NEC 765 /kern: fd0: 1.44MB 3.5in /kern: fd1: 1.2MB 5.25in /kern: wdc0 at 0x1f0-0x1f7 irq 14 on isa /kern: wdc0: unit 0 (wd0): /kern: wd0: 813MB (1665216 sectors), 1652 cyls, 16 heads, 63 S/T, 512 B/S /kern: npx0 on motherboard /kern: npx0: INT 16 interface /kern: Probing for devices on the pci0 bus: /kern: configuration mode 1 allows 32 devices. /kern: pci0:0: vendor=0x1080, device=0x600, class=bridge [not supported] /kern: ncr0 rev 2 int a irq 9 on pci0:2 /kern: reg20: virtual=0xf2a91000 physical=0x80000000 size=0x100 /kern: ncr0: restart (scsi reset). /kern: ncr0 scanning for targets 0..6 (V2 pl21 95/03/21) /kern: ncr0 waiting for scsi devices to settle /kern: (ncr0:0:0): 250ns (4 Mb/sec) offset 8. /kern: (ncr0:0:0): "FUJITSU M2263S-512 0189" type 0 fixed SCSI 2 /kern: sd0(ncr0:0:0): Direct-Access 640MB (1312344 512 byte sectors) /kern: (ncr0:6:0): "SONY SDT-5000 3.02" type 1 removable SCSI 2 /kern: st0(ncr0:6:0): Sequential-Access /kern: st0(ncr0:6:0): 200ns (5 Mb/sec) offset 8. /kern: density code 0x13, /kern: ncr0 targ 6?: ERROR (80:140) (e-2e-0) (88/13) @ (3a8:87030000). /kern: reg: da 10 80 13 47 88 6 1f 6 e 86 af 80 0 7 0. /kern: ncr0: restart (fatal error). /kern: /kern: st0(ncr0:6:0): COMMAND FAILED (9 2) @f0503a00. /kern: drive empty /kern: pci0:4: vendor=0x1095, device=0x640, class=storage [not supported] /kern: pci0: uses 256 bytes of memory from 80000000 upto 800000ff. /kern: pci0: uses 256 bytes of I/O space from f000 upto f0ff. I tried the 2.0 release, snap-shots and the most current sources. The tape drive (SONY SDT-5000) works fine with Linux (sorry...) so I do not think that it is any hardware problem. I do not have any access to news, so I do not know if any poor soul already reported any similar problem. I wonder if anyone succeeded with any DAT tape on a NCR53C810 controller. Thanks. ... Jake >How-To-Repeat: It looks rather obvious. >Fix: I wish I knew. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:40:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08249 for bugs-outgoing; Fri, 23 Jun 1995 07:40:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08233 ; Fri, 23 Jun 1995 07:40:03 -0700 Date: Fri, 23 Jun 1995 07:40:03 -0700 Message-Id: <199506231440.HAA08233@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (stefan Petri) To: freebsd-bugs Subject: kern/551: pci_bus_config() does not init parent pointers in device list + fix In-Reply-To: Your message of Tue, 20 Jun 1995 22:06:09 +0200 <199506202006.WAA00698@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 551 >Category: kern >Synopsis: pci_bus_config() does not init parent pointers in device list >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 07:40:02 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: 486 with PCI bus, FreeBSD kernel with ``option DIAGNOSTIC'' enabled >Description: /usr/src/sys/pci.c::pci_bus_config() does not initialize the parent pointers in the devconf list; there is also a comment that this should be added. In the GENERIC kernel, this seems not to be a real problem, because the freshly malloced devconf structure almost always is pre-set with 0 resp. NULL. However, if ``option DIAGNOSTIC'' is enabled, malloc() will fill all memory areas with pattern 0xdeadbeef. If lsdev(8) is invoked on such a kernel, it will result in a panic when trying to get the descriptions for the PCI bus via sysctl(3). >How-To-Repeat: short version: invoke lsdev(8) on a kernel compiled with DIAGNOSTIC, on a machine with PCI bus long version: instrument lsdev and /sys/kern/kern_devconf.c with printf()s, and then: jupiter:/tmp 2 # sync;sync;sync;./lsdev+printf Device State Description ---------- --------------- -------------------------------------------------- cpu0 Busy i486 DX4 [..] npx0 Busy Floating-point unit > sysctl( {6, 11, 12}, 3, dc, &size, 0, 0) jupiter /kernel: make_devconf(name=chip unit=0 number=12 parent=0xdeadbeef ^^^^ ^^^^^^^^^^ jupiter /kernel: Fatal trap 12: page fault while in kernel mode [..] >Fix: simply disabling DIAGNOSTIC would be the equivalent to wearing my Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses, so I suggest the following: --- pci.c-2.0.950412-SNAP Thu Mar 23 07:14:44 1995 +++ pci.c Tue Jun 20 21:27:04 1995 @@ -551,7 +551,10 @@ pdcp -> pdc_kdc.kdc_name = dvp->pd_name; pdcp -> pdc_kdc.kdc_unit = unit; + pdcp -> pdc_kdc.kdc_parent = NULL; + pdcp -> pdc_kdc.kdc_md.mddc_devtype = MDDT_PCI; + pdcp -> pdc_kdc.kdc_md.mddc_flags = 0; pdcp -> pdc_kdc.kdc_externalize = pci_externalize; pdcp -> pdc_kdc.kdc_internalize = pci_internalize; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 07:53:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA08919 for bugs-outgoing; Fri, 23 Jun 1995 07:53:21 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA08878 ; Fri, 23 Jun 1995 07:53:05 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA01703; Fri, 23 Jun 1995 16:52:51 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA12232; Fri, 23 Jun 1995 16:52:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id HAA28006; Fri, 23 Jun 1995 07:35:57 +0200 From: J Wunsch Message-Id: <199506230535.HAA28006@uriah.heep.sax.de> Subject: Re: bin/542: typeahead fails after rsh To: hsu@freefall.cdrom.com Date: Fri, 23 Jun 1995 07:35:57 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506230440.VAA20194@freefall.cdrom.com> from "Jeffrey Hsu" at Jun 22, 95 09:40:02 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 645 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Jeffrey Hsu wrote: > > Typing commands before receiving a return prompt from the shell after > a rsh command fails. The subsequent commands are lost. > > >How-To-Repeat: > > % rsh localhost sleep 5 > % echo ^G I think this ain't a bug, it's a feature (and unless somebody objects, i would close the PR again). Rsh connects the stdin of the other side with the local tty, so it's your own hard luck that the sleep 5 command didn't consume the input that has been propagated to the remote end. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jun 23 08:12:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09722 for bugs-outgoing; Fri, 23 Jun 1995 08:12:19 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09712 ; Fri, 23 Jun 1995 08:12:18 -0700 Date: Fri, 23 Jun 1995 08:12:18 -0700 Message-Id: <199506231512.IAA09712@freefall.cdrom.com> From: taob@gate.sinica.edu.tw Reply-To: taob@gate.sinica.edu.tw To: freebsd-bugs Subject: docs/553: Shared memory manual pages In-Reply-To: Your message of Sun, 4 Jun 1995 11:02:03 +0800 <199506040302.LAA14739@leo.ibms.sinica.edu.tw> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 553 >Category: docs >Synopsis: Shared memory manual pages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 08:12:17 1995 >Originator: Brian Tao >Organization: Institute of Biomedical Sciences, Academia Sinica >Release: FreeBSD 2.0-BUILT-19950527 i386 >Environment: >Description: We are missing the man pages for the SHM-related functions in (shminit(), shmget(), shmat(), shmctl(), etc., etc.). Joerg Wunsch suggests: "Since the code is copyrighted by Charles Hannum, maybe NetBSD has them already?" >How-To-Repeat: "man shmget". :) >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 08:12:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09828 for bugs-outgoing; Fri, 23 Jun 1995 08:12:44 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA09820 ; Fri, 23 Jun 1995 08:12:42 -0700 Date: Fri, 23 Jun 1995 08:12:42 -0700 Message-Id: <199506231512.IAA09820@freefall.cdrom.com> From: petri@ibr.cs.tu-bs.de (Stefan Petri) Reply-To: petri@ibr.cs.tu-bs.de (Stefan Petri) To: freebsd-bugs Subject: bin/554: make chokes on empty rules + fix In-Reply-To: Your message of Mon, 12 Jun 1995 11:05:36 +0200 <199506120905.LAA14341@jupiter.ibr.cs.tu-bs.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 554 >Category: bin >Synopsis: make chokes on empty rules + fix >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 08:12:42 1995 >Originator: Stefan Petri >Organization: TU Braunschweig, Inst. f. Betriebssysteme u. Rechnerverbund >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: Any FreeBSD >Description: make aborts with fatal error if a Makefile rule line contains a tab followed by an emtpy shell command line. This is very annoying, because the Makefiles in almost every piece of software on the net contain such lines, notably Makefiles that are generated by the gnu configure utility. The correctness of such lines might be arguable, but since every other version of make simply ignores such lines, I propose the following fix, which will print out a warning about such a line, but will continue to make the target. [send-pr did not like ``Severity: seriuosly annoying'' ;-] >How-To-Repeat: Creat a Makefile with only a tabulator in a rule line, then invoke make. >Fix: *** /usr/src/usr.bin/make/parse.c-950412-SNAP Mon Jan 23 22:01:46 1995 --- parse.c Mon Jun 12 10:44:13 1995 *************** *** 715,721 **** * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_FATAL, "Need an operator"); return; } *cp = '\0'; --- 715,721 ---- * Ending a dependency line without an operator is a Bozo * no-no */ ! Parse_Error (PARSE_WARNING, "Need an operator"); return; } *cp = '\0'; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 08:23:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10611 for bugs-outgoing; Fri, 23 Jun 1995 08:23:38 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10593 ; Fri, 23 Jun 1995 08:23:35 -0700 Date: Fri, 23 Jun 1995 08:23:35 -0700 From: Paul Richards Message-Id: <199506231523.IAA10593@freefall.cdrom.com> To: kubus@Austran.Unibase.COM, paul, freebsd-bugs Subject: Changed information for PR kern/550 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: System can not access SCSI DAT tape. State-Changed-From-To: open-closed State-Changed-By: paul State-Changed-When: Fri Jun 23 08:23:05 PDT 1995 State-Changed-Why: This is a duplicate of PR 545 From owner-freebsd-bugs Fri Jun 23 08:25:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10795 for bugs-outgoing; Fri, 23 Jun 1995 08:25:03 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10778 ; Fri, 23 Jun 1995 08:25:01 -0700 Date: Fri, 23 Jun 1995 08:25:01 -0700 From: Paul Richards Message-Id: <199506231525.IAA10778@freefall.cdrom.com> To: petri@ibr.cs.tu-bs.de, paul, freebsd-bugs Subject: Changed information for PR kern/547 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: pci_bus_config() does not init parent pointers in device list State-Changed-From-To: open-closed State-Changed-By: paul State-Changed-When: Fri Jun 23 08:24:06 PDT 1995 State-Changed-Why: This is a duplicate of PR 543 From owner-freebsd-bugs Fri Jun 23 08:42:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA11898 for bugs-outgoing; Fri, 23 Jun 1995 08:42:00 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA11891 for ; Fri, 23 Jun 1995 08:41:56 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id RAA08348 ; Fri, 23 Jun 1995 17:41:23 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id RAA08111 ; Fri, 23 Jun 1995 17:41:23 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199506231541.RAA08111@blaise.ibp.fr> Subject: Re: bin/554: make chokes on empty rules + fix To: petri@ibr.cs.tu-bs.de Date: Fri, 23 Jun 1995 17:41:22 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506231512.IAA09820@freefall.cdrom.com> from "Stefan Petri" at Jun 23, 95 08:12:42 am X-Operating-System: FreeBSD BUILT-19950501 ctm#617 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 354 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > >Number: 554 > >Category: bin > >Synopsis: make chokes on empty rules + fix > >Release: FreeBSD 2.0.950412-SNAP i386 Already fixed in -current. One should close this PR. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD keltia 2.0-BUILT-19950503 #3: Wed May 3 19:53:04 MET DST 1995 From owner-freebsd-bugs Fri Jun 23 08:44:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12050 for bugs-outgoing; Fri, 23 Jun 1995 08:44:23 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA12029 ; Fri, 23 Jun 1995 08:42:27 -0700 Received: from achill [134.169.34.18] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id RAA14744; Fri, 23 Jun 1995 17:40:02 +0200 Received: from petri@localhost by achill.ibr.cs.tu-bs.de (8.6.10/tubsibr) id RAA00719; Fri, 23 Jun 1995 17:40:01 +0200 Date: Fri, 23 Jun 1995 17:40:01 +0200 From: Stefan Petri Message-Id: <199506231540.RAA00719@achill.ibr.cs.tu-bs.de> To: paul@freefall.cdrom.com CC: kubus@Austran.Unibase.COM, freebsd-bugs@freefall.cdrom.com In-reply-to: Paul Richards's message of Fri, 23 Jun 1995 08:23:35 -0700 <199506231523.IAA10593@freefall.cdrom.com> Subject: Changed information for PR kern/550 Reply-to: petri@ibr.cs.tu-bs.de Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi! I have just noticed, that in 2.0.5 the devinfo-struct is bzero()ed before using it, thus the bug fix that I have sent is obsolete now :-) Stefan From owner-freebsd-bugs Fri Jun 23 09:32:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA14822 for bugs-outgoing; Fri, 23 Jun 1995 09:32:01 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA14815 ; Fri, 23 Jun 1995 09:31:58 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id JAA00884; Fri, 23 Jun 1995 09:31:57 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id JAA00332; Fri, 23 Jun 1995 09:32:20 -0700 Message-Id: <199506231632.JAA00332@corbin.Root.COM> To: petri@ibr.cs.tu-bs.de cc: paul@freefall.cdrom.com, kubus@austran.unibase.com, freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR kern/550 In-reply-to: Your message of "Fri, 23 Jun 95 17:40:01 +0200." <199506231540.RAA00719@achill.ibr.cs.tu-bs.de> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 23 Jun 1995 09:32:17 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Hi! > >I have just noticed, that in 2.0.5 the devinfo-struct is bzero()ed >before using it, thus the bug fix that I have sent is obsolete now :-) Yeah, I fixed it awhile ago: revision 1.22 date: 1995/05/04 06:57:11; author: davidg; state: Exp; lines: +2 -1 bzero the malloced pci_devconf structure. This should fix the problem with several of freefall's recent crashes. -DG From owner-freebsd-bugs Fri Jun 23 09:52:18 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA16189 for bugs-outgoing; Fri, 23 Jun 1995 09:52:18 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA16183 for ; Fri, 23 Jun 1995 09:52:15 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA10776; Fri, 23 Jun 1995 09:51:01 -0700 From: "Rodney W. Grimes" Message-Id: <199506231651.JAA10776@gndrsh.aac.dev.com> Subject: Re: 2.05R reboot hangs To: petri@ibr.cs.tu-bs.de Date: Fri, 23 Jun 1995 09:51:01 -0700 (PDT) Cc: jan@todonix.ping.de, bugs@FreeBSD.org In-Reply-To: <199506230918.LAA29871@achill.ibr.cs.tu-bs.de> from "Stefan Petri" at Jun 23, 95 11:18:45 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2467 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Hi! > > > > > sometimes the reboot hangs on an 486-DX4-100 PCI (ASUS4SP3G - Board). > > > > CHeck that you have your external cache set to write-through mode, > > > and ISA GAT mode disabled in the BIOS setup screens. > > Rodney> Have you customized the kernel for the machine? Or are you running > Rodney> the GENERIC kernel. I have had 2 sites report ASUS-PCI/I-486SP3G boot > Rodney> hangs when using the GENERIC kernel > > Rodney> Have you triple checked your SCSI bus termination, and when the hang > Rodney> happens does your SCSI drive LED tend to be on solid indicating a > Rodney> scsi bus hang? > > I also have an 486-DX4-100 PCI ASUS SP3G, and with 2.0.5, reboot from > GENERIC kernel hangs on about every 2nd try. This was never a problem > with the 950412-SNAP, which I have rebootet remotely about 100 times > without need to run to the machine's console. I have build a > custom kernel only yesterday, I dont know yet if that behaves better. > I have cache-write-back and ISA-GAT-enabled, and my SCSI-bus is > triple-terminated (dont ask why ;-) but is quiescent when reboot > hangs, However, as I said, this was no problem with the SNAP > installation. Set your cache to write through mode or expect to get signall 11's at random. The board (all version) has a cache write back coherency problem when used with bus master PCI devices (the NCR SCSI controller is a PCI bus master). Turn off ISA GAT mode, though you may not need to if you don't have any ISA bus masters. Properly terminate your SCSI bus. There is *NEVER* a reason to have 3 terminators on a scsi bus, plain and simple you are asking for trouble if you do that. Please tell exactly what the last thing on the screen is after you type reboot when the hang occurs (just the last line is all I need). Compile a kernel with: # BROKEN_KEYBOARD_RESET disables the use of the keyboard controller to # reset the CPU for reboot. This is needed on some systems with broken # keyboard controllers. options "BROKEN_KEYBOARD_RESET" in the config file. Does doing that fix the problem? What revision of the board do you have (printed on the board next to the model number)? I am starting to collect data on the versions of the boards effected by this problem and if the BROKEN_KEYBOARD_RESET fixes the problem. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Fri Jun 23 10:44:43 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18351 for bugs-outgoing; Fri, 23 Jun 1995 10:44:43 -0700 Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA18335 for ; Fri, 23 Jun 1995 10:44:36 -0700 Received: from fns.muc.de ([193.174.4.223]) by colin.muc.de with SMTP id <25549-2>; Fri, 23 Jun 1995 19:44:24 +0200 Received: (from peterb@localhost) by fns.muc.de (8.6.11/8.6.9) id TAA02484; Fri, 23 Jun 1995 19:34:13 +0200 Date: Fri, 23 Jun 1995 19:34:07 +0200 From: Peter Bechtold To: Peter Dufault cc: joerg_wunsch@uriah.heep.sax.de, freebsd-bugs@freefall.cdrom.com Subject: Re: misc/531: SCSI Tape Problems In-Reply-To: <199506202115.RAA25453@hda.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Yes, Peter, you are right. I changed some BIOS parameters (sorry, don't remember, which one, I tried 'til it worked ...). Now, I have SCSI-1 devices on the 1542 and SCSI-2 devices on the 2842. Everything works fine, even the tape drive. Peter. -- # Peter Bechtold # Tel./Fax (+49 / 0) 89 / 542 0774 # # e-Mail: peterb@muc.de # Scall: 01681-1694153 # On Tue, 20 Jun 1995, Peter Dufault wrote: > J Wunsch writes: > > > > As Peter Bechtold wrote: > > > > > > > In case it's still valid: what are the console messages from the > > > > SCSI subsystem? > > > > > > Jun 19 01:25:00 fns /kernel: st0: oops not queued > > > Jun 19 01:25:01 fns /kernel: biodone: buffer already done > > > > Hmm, Peter (Dufault)??? Can you help? > > No, I can't. It isn't a general tape problem, so it is something > specific to this environment. > > How about turning on debugging and trying again? That should get > us some more info. > > You'll have to compile your kernel with the SCSIDEBUG option, and > then turn on debugging on the tape drive using the scsi(8) "-d" > flag. > > Peter > > -- > Peter Dufault Real Time Machine Control and Simulation > HD Associates, Inc. Voice: 508 433 6936 > dufault@hda.com Fax: 508 433 5267 > From owner-freebsd-bugs Fri Jun 23 10:48:29 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18701 for bugs-outgoing; Fri, 23 Jun 1995 10:48:29 -0700 Received: from kryten.atinc.com (kryten.atinc.com [198.138.38.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA18692 for ; Fri, 23 Jun 1995 10:48:26 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id NAA24814; Fri, 23 Jun 1995 13:41:35 -0400 Date: Fri, 23 Jun 1995 13:41:34 -0400 (EDT) From: "Jonathan M. Bresler" Subject: 2.0.5R install To: bugs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk in installing 2.0.5R, trying to use the lp0 device, i get DEBUG: Executing command `ifconfig lp0 inet 10.0.0.2 netmask 255.0.0.0' (Magic=0) ifconfig: ioctl (SIOCAIFADDR): Can't assign requested address DEBUG: Command `ifconfig lp0 inet 10.0.0.2 netmask 255.0.0.0' returns status of 1 anyone else seen this? tried again by hand on vty3--same results ;-/ cant ifconfig sl0 either ;(( Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-bugs Fri Jun 23 10:50:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18887 for bugs-outgoing; Fri, 23 Jun 1995 10:50:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18879 ; Fri, 23 Jun 1995 10:50:01 -0700 Date: Fri, 23 Jun 1995 10:50:01 -0700 Message-Id: <199506231750.KAA18879@freefall.cdrom.com> From: peter@haywire.dialix.com Reply-To: peter@haywire.dialix.com To: freebsd-bugs Subject: kern/555: net/if.c can possibly choose incorrect net i/face. In-Reply-To: Your message of Sat, 24 Jun 1995 01:42:16 +0800 <199506231742.BAA00998@jhome.DIALix.COM> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 555 >Category: kern >Synopsis: net/if.c can possibly choose incorrect net i/face. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 10:50:00 1995 >Originator: Peter Wemm >Organization: DIALix Services >Release: FreeBSD 2.0-BUILT-19950616 i386 >Environment: FreeBSD jhome.DIALix.COM 2.0-BUILT-19950616 FreeBSD 2.0-BUILT-19950616 #0: Fri Jun 16 22:36:04 WST 1995 pwroot@jhome.DIALix.COM:/usr/src/sys/compile/JHOME i386 >Description: Although the current code solves the original problem [a program that attempts to broadcast to the local ethernet was causing the wrong output interface to be selected, by mistakenly applying the netmask to the local address of a point-to-point link], it still isn't quite correct. This is possibly because of a typo in the patch that I sent in originally. Although the current code does not appear to break anything as it stands, this is not a guarantee that it wont ever. Hence the low priority. Additionally, the code does not examine interfaces that have no netmask set, even though the netmask is meant to be meaningless for P2P interfaces. >How-To-Repeat: read the source >Fix: *** if.c.dist Fri Jun 16 15:12:44 1995 --- if.c Fri Jun 16 15:16:08 1995 *************** *** 238,247 **** register char *cp, *cp2, *cp3; ! if (ifa->ifa_addr->sa_family != af || ifa->ifa_netmask == 0) next: continue; if (ifp->if_flags & IFF_POINTOPOINT) { ! if (equal(addr, ifa->ifa_addr)) return (ifa); } else { cp = addr_data; cp2 = ifa->ifa_addr->sa_data; --- 238,249 ---- register char *cp, *cp2, *cp3; ! if (ifa->ifa_addr->sa_family != af) next: continue; if (ifp->if_flags & IFF_POINTOPOINT) { ! if (equal(addr, ifa->ifa_dstaddr)) return (ifa); } else { + if (ifa->ifa_netmask == 0) + continue; cp = addr_data; cp2 = ifa->ifa_addr->sa_data; >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 10:52:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19115 for bugs-outgoing; Fri, 23 Jun 1995 10:52:23 -0700 Received: (from rgrimes@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19101 ; Fri, 23 Jun 1995 10:52:21 -0700 Date: Fri, 23 Jun 1995 10:52:21 -0700 From: "Rodney W. Grimes" Message-Id: <199506231752.KAA19101@freefall.cdrom.com> To: kubus@Austran.Unibase.COM, rgrimes, freebsd-bugs Subject: Changed information for PR kern/545 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: System can not access SCSI DAT tape. State-Changed-From-To: open-closed State-Changed-By: rgrimes State-Changed-When: Fri Jun 23 10:51:56 PDT 1995 State-Changed-Why: Duplicated in 550 From owner-freebsd-bugs Fri Jun 23 10:53:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19250 for bugs-outgoing; Fri, 23 Jun 1995 10:53:13 -0700 Received: from lambda.demon.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA19244 for ; Fri, 23 Jun 1995 10:53:08 -0700 Received: (from paul@localhost) by lambda.demon.co.uk (8.6.11/8.6.9) id SAA01108 for bugs@freebsd.org; Fri, 23 Jun 1995 18:53:19 +0100 From: Paul Richards Message-Id: <199506231753.SAA01108@lambda.demon.co.uk> Subject: edit-pr changes To: bugs@freebsd.org Date: Fri, 23 Jun 1995 18:53:19 +0100 (BST) Reply-to: paul@freebsd.org 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: 977 Sender: bugs-owner@freebsd.org Precedence: bulk Ok, as you probably noticed, I've been playing with gnats over the last couple of hours, I've cleaned out most of pending and all the gnats-queue (which contains incorrectly submitted PR's). While I was doing this I ran into a few problems so some PR's got duplicated, most of which I've closed. Since the link seemed quite quick I did some work on edit-pr. I implemented suggestions from various people to allow editing multiple PR's in one go and also to use the editor to enter the reason for the state changes. This seems to be working. I also tried to give the option of retaining a previous message, like the ! option in cvs but I haven't had a chance to test this and won't get a chance to work on gnats for at least a week now. If someone else wants to play with it feel free. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home) From owner-freebsd-bugs Fri Jun 23 10:56:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19529 for bugs-outgoing; Fri, 23 Jun 1995 10:56:19 -0700 Received: (from root@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA19515 ; Fri, 23 Jun 1995 10:56:18 -0700 Date: Fri, 23 Jun 1995 10:56:18 -0700 From: Paul Richards Message-Id: <199506231756.KAA19515@freefall.cdrom.com> To: petri@ibr.cs.tu-bs.de, paul, freebsd-bugs Subject: Changed information for PR bin/554 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: make chokes on empty rules + fix State-Changed-From-To: open-closed State-Changed-By: paul State-Changed-When: Fri Jun 23 10:54:33 PDT 1995 State-Changed-Why: This is already fixed in current according to Ollivier Robert (23 June 95). Since this was a backlogged PR then it entered the gnats database long after the problem was fixed which is why there's no reference to the cvs entry. From owner-freebsd-bugs Fri Jun 23 11:01:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA19635 for bugs-outgoing; Fri, 23 Jun 1995 11:01:17 -0700 Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA19629 ; Fri, 23 Jun 1995 11:01:07 -0700 Received: from achill [134.169.34.18] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id UAA17562; Fri, 23 Jun 1995 20:00:31 +0200 Received: from petri@localhost by achill.ibr.cs.tu-bs.de (8.6.10/tubsibr) id UAA00930; Fri, 23 Jun 1995 20:00:30 +0200 Date: Fri, 23 Jun 1995 20:00:30 +0200 From: Stefan Petri Message-Id: <199506231800.UAA00930@achill.ibr.cs.tu-bs.de> To: rgrimes@freefall.cdrom.com CC: freebsd-bugs@freefall.cdrom.com In-reply-to: "Rodney W. Grimes"'s message of Fri, 23 Jun 1995 10:48:40 -0700 <199506231748.KAA18755@freefall.cdrom.com> Subject: multiple bug reports [re: Changed information for PR kern/543] Keywords: I am not _that_ stupid! Reply-to: petri@ibr.cs.tu-bs.de Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi! Well, since I start getting complaints: Something is making me look stupid before the entire FreeBSD mailing list. ---> I sent my reports _once_ each some bug at the gnats server site / software replicated my reports n-times. Sorry for the inconveniences, but its not my fault. Stefan From owner-freebsd-bugs Fri Jun 23 11:08:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20151 for bugs-outgoing; Fri, 23 Jun 1995 11:08:38 -0700 Received: (from rgrimes@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20137 ; Fri, 23 Jun 1995 11:08:37 -0700 Date: Fri, 23 Jun 1995 11:08:37 -0700 From: "Rodney W. Grimes" Message-Id: <199506231808.LAA20137@freefall.cdrom.com> To: kubus@Austran.Unibase.COM, rgrimes, freebsd-bugs Subject: Changed information for PR kern/545 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: System can not access SCSI DAT tape. State-Changed-From-To: closed-open State-Changed-By: rgrimes State-Changed-When: Fri Jun 23 11:07:49 PDT 1995 State-Changed-Why: Paul and I closed opposite duplicates, change this one back to open... From owner-freebsd-bugs Fri Jun 23 11:09:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20214 for bugs-outgoing; Fri, 23 Jun 1995 11:09:22 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA20207 ; Fri, 23 Jun 1995 11:09:19 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA11230; Fri, 23 Jun 1995 11:09:24 -0700 From: "Rodney W. Grimes" Message-Id: <199506231809.LAA11230@gndrsh.aac.dev.com> Subject: Re: Changed information for PR kern/550 To: paul@freefall.cdrom.com (Paul Richards) Date: Fri, 23 Jun 1995 11:09:24 -0700 (PDT) Cc: kubus@Austran.Unibase.COM, paul@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506231523.IAA10593@freefall.cdrom.com> from "Paul Richards" at Jun 23, 95 08:23:35 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 453 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Synopsis: System can not access SCSI DAT tape. > > State-Changed-From-To: open-closed > State-Changed-By: paul > State-Changed-When: Fri Jun 23 08:23:05 PDT 1995 > State-Changed-Why: > This is a duplicate of PR 545 WHoopsss... I closed 545, you closed 550. I went and opened 545 back up. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Fri Jun 23 11:10:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20330 for bugs-outgoing; Fri, 23 Jun 1995 11:10:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20322 ; Fri, 23 Jun 1995 11:10:01 -0700 Date: Fri, 23 Jun 1995 11:10:01 -0700 Message-Id: <199506231810.LAA20322@freefall.cdrom.com> From: Paul Richards Reply-To: Paul Richards To: freebsd-bugs Subject: misc/556: Bug in /etc/rc In-Reply-To: Your message of Fri, 23 Jun 1995 19:01:56 +0100 <199506231801.TAA01235@lambda.demon.co.uk> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 556 >Category: misc >Synopsis: Bug in /etc/rc >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 23 11:10:00 1995 >Originator: Thomas Krebs >Organization: Institute for Manufacturing Automation >Release: FreeBSD 2.0-RELEASE i386 >Environment: Existing vi recovery files in /var/tmp/vi.recover. >Description: Utiliy at line 134 does not recover recovery files. The quoted string "$virecovery" is always "/var/tmp/vi.recover/recover.*" and so the test is always false! >How-To-Repeat: Have recovery files in /var/tmp/vi.recover and reboot. >Fix: Apply a fix like the following: *** rc Thu Dec 1 23:47:08 1994 --- rc.orig Thu Dec 1 23:45:19 1994 *************** *** 132,141 **** fi # Recover vi editor files. ! nfiles=`ls /var/tmp/vi.recover/ | fgrep recover | wc -l` ! if [ $nfiles -gt 0 ]; then echo 'Recovering vi editor sessions' - virecovery=/var/tmp/vi.recover/recover.* for i in $virecovery; do sendmail -t < $i done --- 132,140 ---- fi # Recover vi editor files. ! virecovery=/var/tmp/vi.recover/recover.* ! if [ "$virecovery" != "/var/tmp/vi.recover/recover.*" ]; then echo 'Recovering vi editor sessions' for i in $virecovery; do sendmail -t < $i done -- Thomas Krebs Department for Manufacturing Automation and Production Systems FAPS University of Erlangen krebs@faps.uni-erlangen.de >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jun 23 11:10:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20438 for bugs-outgoing; Fri, 23 Jun 1995 11:10:31 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA20432 ; Fri, 23 Jun 1995 11:10:28 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA11245; Fri, 23 Jun 1995 11:10:33 -0700 From: "Rodney W. Grimes" Message-Id: <199506231810.LAA11245@gndrsh.aac.dev.com> Subject: Re: Changed information for PR kern/547 To: paul@freefall.cdrom.com (Paul Richards) Date: Fri, 23 Jun 1995 11:10:33 -0700 (PDT) Cc: petri@ibr.cs.tu-bs.de, paul@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506231525.IAA10778@freefall.cdrom.com> from "Paul Richards" at Jun 23, 95 08:25:01 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 482 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Synopsis: pci_bus_config() does not init parent pointers in device list > > State-Changed-From-To: open-closed > State-Changed-By: paul > State-Changed-When: Fri Jun 23 08:24:06 PDT 1995 > State-Changed-Why: > This is a duplicate of PR 543 Ditto... sorry about that... I am going to leave dup's alone from here on out. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Fri Jun 23 11:18:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20614 for bugs-outgoing; Fri, 23 Jun 1995 11:18:22 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA20608 ; Fri, 23 Jun 1995 11:18:21 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16678(6)>; Fri, 23 Jun 1995 11:17:34 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49859>; Fri, 23 Jun 1995 11:17:23 -0700 X-Mailer: exmh version 1.6 4/21/95 To: Jeffrey Hsu cc: freebsd-bugs@freefall.cdrom.com Subject: Re: bin/542: typeahead fails after rsh In-reply-to: Your message of "Thu, 22 Jun 95 21:40:02 PDT." <199506230440.VAA20194@freefall.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Jun 1995 11:17:15 PDT From: Bill Fenner Message-Id: <95Jun23.111723pdt.49859@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199506230440.VAA20194@freefall.cdrom.com> you write: >Typing commands before receiving a return prompt from the shell after >a rsh command fails. The subsequent commands are lost. By default, rsh thinks the remote command wants input, so it sucks up stdin. Try rsh -n if the remote command doesn't require any input. % rsh -n localhost sleep 5 echo hi jeffrey % hi jeffrey Bill From owner-freebsd-bugs Fri Jun 23 11:30:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA21042 for bugs-outgoing; Fri, 23 Jun 1995 11:30:05 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA21025 ; Fri, 23 Jun 1995 20:30:04 +0200 Date: Fri, 23 Jun 1995 20:30:04 +0200 From: Joerg Wunsch Message-Id: <199506231830.UAA21025@freefall.cdrom.com> To: taob@gate.sinica.edu.tw, joerg, freebsd-bugs Subject: Changed information for PR docs/553 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Shared memory manual pages State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Fri Jun 23 20:27:59 MET DST 1995 State-Changed-Why: This is a duplicate entry for [1995/01/22] docs/177 man pages missing for SYSV IPC funtions From owner-freebsd-bugs Fri Jun 23 11:30:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA21083 for bugs-outgoing; Fri, 23 Jun 1995 11:30:12 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA21020 for ; Fri, 23 Jun 1995 11:30:03 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA06120; Fri, 23 Jun 1995 20:29:50 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA14082; Fri, 23 Jun 1995 20:29:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA00114; Fri, 23 Jun 1995 20:26:23 +0200 From: J Wunsch Message-Id: <199506231826.UAA00114@uriah.heep.sax.de> Subject: Re: docs/553: Shared memory manual pages To: taob@gate.sinica.edu.tw Date: Fri, 23 Jun 1995 20:26:23 +0200 (MET DST) Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506231512.IAA09712@freefall.cdrom.com> from "taob@gate.sinica.edu.tw" at Jun 23, 95 08:12:18 am Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 521 Sender: bugs-owner@FreeBSD.org Precedence: bulk As taob@gate.sinica.edu.tw wrote: > > We are missing the man pages for the SHM-related functions in > (shminit(), shmget(), shmat(), shmctl(), etc., etc.). > Joerg Wunsch suggests: "Since the code is copyrighted by Charles > Hannum, maybe NetBSD has them already?" This is a duplicate for [1995/01/22] docs/177 man pages missing for SYSV IPC funtions -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jun 23 11:38:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA21659 for bugs-outgoing; Fri, 23 Jun 1995 11:38:31 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA21644 ; Fri, 23 Jun 1995 20:38:30 +0200 Date: Fri, 23 Jun 1995 20:38:30 +0200 From: Joerg Wunsch Message-Id: <199506231838.UAA21644@freefall.cdrom.com> To: peterb@muc.de, joerg, freebsd-bugs Subject: Changed information for PR misc/531 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: writing a scsi tape doesn't work State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Fri Jun 23 20:35:13 MET DST 1995 State-Changed-Why: ~Date: Fri, 23 Jun 1995 19:34:07 +0200 ~From: Peter Bechtold ~To: Peter Dufault ~Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-bugs@freefall.cdrom.com ~Subject: Re: misc/531: SCSI Tape Problems ~Message-Id: Yes, Peter, you are right. I changed some BIOS parameters (sorry, don't remember, which one, I tried 'til it worked ...). Now, I have SCSI-1 devices on the 1542 and SCSI-2 devices on the 2842. Everything works fine, even the tape drive. Peter. From owner-freebsd-bugs Fri Jun 23 11:42:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA21911 for bugs-outgoing; Fri, 23 Jun 1995 11:42:10 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA21896 ; Fri, 23 Jun 1995 20:42:09 +0200 Date: Fri, 23 Jun 1995 20:42:09 +0200 From: Joerg Wunsch Message-Id: <199506231842.UAA21896@freefall.cdrom.com> To: hsu, joerg, freebsd-bugs Subject: Changed information for PR bin/542 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: typeahead fails after rsh State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Fri Jun 23 20:40:27 MET DST 1995 State-Changed-Why: The described behaviour is intentional: ~To: Jeffrey Hsu ~cc: freebsd-bugs@freefall.cdrom.com ~Subject: Re: bin/542: typeahead fails after rsh ~Date: Fri, 23 Jun 1995 11:17:15 PDT In message <199506230440.VAA20194@freefall.cdrom.com> you write: >Typing commands before receiving a return prompt from the shell after >a rsh command fails. The subsequent commands are lost. By default, rsh thinks the remote command wants input, so it sucks up stdin. Try rsh -n if the remote command doesn't require any input. % rsh -n localhost sleep 5 echo hi jeffrey % hi jeffrey Bill From owner-freebsd-bugs Fri Jun 23 11:45:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA22130 for bugs-outgoing; Fri, 23 Jun 1995 11:45:45 -0700 Received: from unlisys.unlisys.NET (unlisys.unlisys.net [194.64.15.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA22124 for ; Fri, 23 Jun 1995 11:45:42 -0700 Received: by unlisys.unlisys.NET from deadline.snafu.de with smtp (Smail3.1.28.1 [@@]) id m0sPCca-0000JJC; Fri, 23 Jun 95 19:34 MET DST Received: by deadline.snafu.de id m0sPCcV-000IzmC; Fri, 23 Jun 95 19:34 MET DST (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Xterms hang after open? To: freebsd-bugs@freebsd.org Date: Fri, 23 Jun 1995 19:34:19 +0200 (MET DST) Organization: -D-E-A-D-L-I-N-E- Public access UN*X system - 13347 Berlin. X-Mailer: ELM [version 2.4 PL24 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1688 Sender: bugs-owner@freebsd.org Precedence: bulk Hi! --- I'm noticing a strange behaviour of my x(c)terms nearly since I use FreeBSD in the 2.0 and above versions. Although I would suggest it's merely the tcsh shell which causes this behaviour. Well, what happens exactly is: You open an xterm or xcterm, position the window, and all you get is an empty window with the cursor being in the upper left corner of the window, but the shell doesn't come up with a shell prompt or anything. As I can say this doesn't happen on a freshly rebooted machine, but more often when the the machine has already been running for a while. Also it seems that this problem does not occur, when using a shell other than the tcsh shell (I just tried it out with an sh shell, and the window just popped up and was there). Again... this is no problem I'm having sinc yesterday, but it is a problem I'm having since nearly 2.0R. I'm using the tcsh-6.0.5 shell, which says about itself: (tcsh 6.05.00 (Cornell) 94/19/06 (i386-intel-bsd44) options 8b,nls,dl,rh) Apart from that I'm using FreeBSD 2.0.5 current (I think about Jun 21) on an i486DX system with Buslogic Bt747S controller. I would be _very_ thankful for any advice or help on getting rid of this problem, since it really sucks after a certain amount of time, when you have to wait for about 2 minutes for every xterm you open. Thanks in advance.... Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-bugs Fri Jun 23 12:29:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA23096 for bugs-outgoing; Fri, 23 Jun 1995 12:29:54 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA23089 ; Fri, 23 Jun 1995 12:29:52 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA11465; Fri, 23 Jun 1995 12:23:57 -0700 From: "Rodney W. Grimes" Message-Id: <199506231923.MAA11465@gndrsh.aac.dev.com> Subject: Re: multiple bug reports [re: Changed information for PR kern/543] To: petri@ibr.cs.tu-bs.de Date: Fri, 23 Jun 1995 12:23:57 -0700 (PDT) Cc: rgrimes@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199506231800.UAA00930@achill.ibr.cs.tu-bs.de> from "Stefan Petri" at Jun 23, 95 08:00:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 599 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Hi! > > Well, since I start getting complaints: > > Something is making me look stupid before the entire FreeBSD mailing > list. > > ---> I sent my reports _once_ each > > some bug at the gnats server site / software replicated my reports > n-times. Sorry for the inconveniences, but its not my fault. Your right, sorry about that. It was Paul Richards in cleaning up the back queued gnats reports and fixing some other problems. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-bugs Fri Jun 23 21:24:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA07433 for bugs-outgoing; Fri, 23 Jun 1995 21:24:19 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA07420 ; Fri, 23 Jun 1995 21:24:14 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA23485; Sat, 24 Jun 1995 06:24:12 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id GAA17896; Sat, 24 Jun 1995 06:24:11 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA00477; Fri, 23 Jun 1995 20:59:22 +0200 From: J Wunsch Message-Id: <199506231859.UAA00477@uriah.heep.sax.de> Subject: Re: edit-pr changes To: paul@FreeBSD.org Date: Fri, 23 Jun 1995 20:59:21 +0200 (MET DST) Cc: bugs@FreeBSD.org In-Reply-To: <199506231753.SAA01108@lambda.demon.co.uk> from "Paul Richards" at Jun 23, 95 06:53:19 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 386 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Paul Richards wrote: > > I implemented suggestions from various people to allow editing > multiple PR's in one go and also to use the editor to enter the > reason for the state changes. Thank you, Paul! I most appreciate those changes. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jun 23 22:25:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA12352 for bugs-outgoing; Fri, 23 Jun 1995 22:25:09 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA12344 for ; Fri, 23 Jun 1995 22:25:07 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id WAA07484; Fri, 23 Jun 1995 22:24:05 -0700 Received: (dillon@localhost) by shell1.best.com (8.6.12/8.6.5) id WAA26119; Fri, 23 Jun 1995 22:23:44 -0700 Date: Fri, 23 Jun 1995 22:23:44 -0700 From: Matt Dillon Message-Id: <199506240523.WAA26119@shell1.best.com> To: Bruce Evans Cc: bugs@FreeBSD.org Subject: Re: connect() bug found and fixed (uninitialized pointer) Sender: bugs-owner@FreeBSD.org Precedence: bulk :> couple of other programs. As best as I can tell, :> something gets confused and the parameter offsets :> get skewed, causing corruption when a bad pointer :> (due to the skew) is dereferenced. : :Runtime problems are most likely caused by %d or %ld format specifiers :mismatched with quad_t arguments, e.g., off_t's. quad_t's should be :printed in format %qd. Casts shouldn't normally be used except for :pointers. Pointer types should be cast to (void *) and printed in :format %p. -Wall finds most mismatches to give you some chance of :detecting int vs. long mismatches but it is sloppy about pointers. : :Bruce Yes, I finally figured that out. I think there is a serious problem though, because MOST third party programs do not put -Wall in their Makefile, and without -Wall you get not a single warning about possible quad_t conflicts... everything appears to compile and link just fine, except the resulting binary does weird things. Now, for us... obviously we will be putting -Wall in everything we compile from now on, but I think you will find a lot of people having serious problems with this quad_t change... rightly, new procedure names should have been chosen for the relatively few system calls that need quad_t's (lseek, ftruncate could become lqseek, fqtruncate). You may wish to consider turning -Wall or, at least, the warning regarding unprototyped procedure calls, ON by default in gcc. Personally, I think keeping the same naming conventions was ill-considered. -Matt Matthew Dillon VP Engineering, BEST Internet Communications, Inc. , [always include a portion of the original email in any response!] From owner-freebsd-bugs Fri Jun 23 22:43:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA13495 for bugs-outgoing; Fri, 23 Jun 1995 22:43:41 -0700 Received: from alumni.EECS.Berkeley.EDU (hsu@alumni.EECS.Berkeley.EDU [128.32.156.234]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA13483 for ; Fri, 23 Jun 1995 22:43:39 -0700 Received: (from hsu@localhost) by alumni.EECS.Berkeley.EDU (8.6.11/UCSEE-0.9a) id WAA17445; Fri, 23 Jun 1995 22:43:35 -0700 Date: Fri, 23 Jun 1995 22:43:35 -0700 From: Jeffrey Hsu Message-Id: <199506240543.WAA17445@alumni.EECS.Berkeley.EDU> To: fenner@parc.xerox.com, freebsd-bugs@freefall.cdrom.com, j@uriah.heep.sax.de Subject: Re: bin/542: typeahead fails after rsh Cc: '@alumni.EECS.Berkeley.EDU Sender: bugs-owner@FreeBSD.org Precedence: bulk Okay, I see the error of my ways. Thanks for pointing that out to me. Jeffrey From owner-freebsd-bugs Fri Jun 23 23:26:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA16958 for bugs-outgoing; Fri, 23 Jun 1995 23:26:32 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA16952 for ; Fri, 23 Jun 1995 23:26:29 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA25761; Sat, 24 Jun 1995 08:26:24 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA18169; Sat, 24 Jun 1995 08:26:24 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id HAA02575; Sat, 24 Jun 1995 07:59:45 +0200 From: J Wunsch Message-Id: <199506240559.HAA02575@uriah.heep.sax.de> Subject: Re: Xterms hang after open? To: root@deadline.snafu.de (Andreas S. Wetzel) Date: Sat, 24 Jun 1995 07:59:44 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: from "Andreas S. Wetzel" at Jun 23, 95 07:34:19 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 691 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Andreas S. Wetzel wrote: > > Also it seems that this problem does not occur, when using a shell other > than the tcsh shell (I just tried it out with an sh shell, and the window > just popped up and was there). Again... this is no problem I'm having > sinc yesterday, but it is a problem I'm having since nearly 2.0R. How long's your $path variable? Mine contains 10 elements, and i've never noticed such behaviour. tcsh is known to perform some (rather inefficient) lookups along the path in order to build the internal tables on startup. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Fri Jun 23 23:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA17436 for bugs-outgoing; Fri, 23 Jun 1995 23:30:02 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17414 ; Sat, 24 Jun 1995 08:29:59 +0200 Date: Sat, 24 Jun 1995 08:29:59 +0200 From: Joerg Wunsch Message-Id: <199506240629.IAA17414@freefall.cdrom.com> To: petri@ibr.cs.tu-bs.de, joerg, freebsd-bugs Subject: Changed information for PR i386/548 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: missing break in isa/if_el.c causes panic in bpf.c + fix State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sat Jun 24 08:28:46 MET DST 1995 State-Changed-Why: The problem has already been fixed in 2.0.5R, and the fixe moved into the HEAD by revision 1.14 of if_el.c. From owner-freebsd-bugs Sat Jun 24 04:30:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA04948 for bugs-outgoing; Sat, 24 Jun 1995 04:30:10 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA04941 for freebsd-bugs; Sat, 24 Jun 1995 04:30:09 -0700 Date: Sat, 24 Jun 1995 04:30:09 -0700 From: GNU GNATS Message-Id: <199506241130.EAA04941@freefall.cdrom.com> To: freebsd-bugs Subject: List of open Problem Reports Sender: bugs-owner@FreeBSD.org Precedence: bulk This is the list of currently open problem reports [1994/09/14] kern/1 Toshiba MK156FB scsi drive does not work with 2.0 ke [1994/10/07] kern/6 System hangs while using slip or ppp connection [1994/11/13] i386/14 No MBR put on prestine IDE disk drive [1994/11/14] bin/17 "mount -t foo /dev/wd1h /mnt" gives incorrect error [1994/11/18] kern/21 kernel panic. [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/03] kern/39 Recent config changes hosed ft config [1994/12/04] kern/40 Floppy tape probe hosed (FIX) [1994/12/06] kern/42 PC-NFS on -current can't access disks [1994/12/07] docs/43 manpage for keysu is missing. reference from keyinit [1994/12/07] kern/44 ep driver won't work with anything but bnc [1994/12/08] kern/46 ed driver don't know the link0 flag (IFF_LINK0) [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/21] misc/75 Netboot ignores gateway [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/09] kern/102 PANIC after running Merged Buffer Cache kernel for a [1995/01/10] bin/104 pax -rwl may corrupt filesystem [1995/01/11] i386/105 Distributed libm (msun) has non-standard error handl [1995/01/13] gnu/107 kernel build produces internal compiler error [1995/01/14] bin/109 at command doesn't parse dates time and doesn't prom [1995/01/14] misc/112 ^C cause panic during install [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/119 you cannot tune your newfs parameters at intall time [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/14] bin/135 not enough ptys; virtual console names conflict with [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] bin/163 telneting sometimes doesn't yield a "login:" prompt [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] docs/171 No documentation on .forward files. [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/175 Syscons does not recover X graphics mode [1995/01/22] kern/176 EIDRM not defined in errno.h [1995/01/22] docs/177 man pages missing for SYSV IPC funtions [1995/01/23] kern/180 Fiddling with process stack and using scanf with inv [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] misc/220 Cancel still doesn't work during install [1995/02/16] misc/221 lots of error messages during unpacking via ftp inst [1995/02/16] i386/222 boot prompt doesn't always work [1995/02/16] misc/223 default domain shouldn't be hostname [1995/02/18] kern/224 ppp net serial [1995/02/18] kern/225 Panic: invalid wire count when GDB kills stopped inf [1995/03/02] misc/229 acos() core dump [1995/03/03] bin/230 C++ contructors not being called [1995/03/05] gnu/231 send-pr initializes Organization with ~/.signature [1995/03/05] docs/232 The mandoc .St macro doesn't work or misses IEEE754 [1995/03/10] misc/236 2.0-950210-SNAP/src/extract.sh references "release" [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/17] kern/248 scbus attach/probe information is inconsistent [1995/03/18] i386/251 disklabel(8) refuses to install new bootstrap [1995/03/18] kern/253 Tagged queuing with an Adaptec 2842 controller doesn [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] docs/265 mtrace command lacks man pages [1995/03/21] kern/266 ifconfig panics kernel built without option NFS [1995/03/27] bin/274 touch -t with century doesn't work [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/280 the new slice code is bitching about my old slices [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] conf/286 'make depend' on GENERIC kernel stops [1995/03/30] kern/287 Several header files are not consistent [1995/03/31] kern/288 panic: free: multiple frees [1995/04/01] gnu/289 info(1) cannot handle arrow keys on a VT100 [1995/04/01] kern/291 PCI devices still probe/attach after being disabled [1995/04/01] kern/293 wd0: interrupt timeout [1995/04/02] kern/294 Bootstrap has problems with -g compiled kernels [1995/04/04] i386/297 matcd does not play audio CDs from cdplay [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/08] bin/308 Do-it-yourself FTP needs to prompt for what to downl [1995/04/08] bin/309 Do-it-yourself FTP deletes /usr/tmp dir rather than [1995/04/08] bin/310 ^C or ^Z in do-it-yourself FTP installation crashes [1995/04/08] bin/311 Do-it-yourself FTP deletes /usr/tmp dir rather than [1995/04/09] bin/314 CTRL-Z during installation crashes install FDIV008 [1995/04/09] bin/315 Kernel and boot block don't agree on kernel name FD [1995/04/09] bin/316 SNAP950322 less stable on IDE than earlier releases [1995/04/09] docs/317 Install README doesn't list matcd as install choice [1995/04/09] bin/318 matcd driver not on boot or fixit floppy FDIV012 [1995/04/09] bin/319 Install doesn't strip sys name in prompt for domain [1995/04/09] bin/320 TCP/IP settings entered b4 install are not kept FDIV [1995/04/09] bin/321 TCP/IP settings given during install are not kept FD [1995/04/09] bin/322 No way to restart a failed FTP download FDIV016 [1995/04/09] bin/323 Creating lost+found causes fsck to stop fsck -y FDIV [1995/04/09] bin/324 /usr/include/sys -> /usr/sys/sys -> /usr/sys/sys FD [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/328 Checking for -c kernel changes randomly hangs FDIV02 [1995/04/09] bin/329 FTP transfers above 99K shown in scientific notation [1995/04/11] kern/332 Incorrect routes can cause system to reset [1995/04/11] kern/336 make world fails on NCR-SCSI machine [1995/04/11] i386/337 seagate controller code hangs on boot. [1995/04/14] docs/341 vnconfig(8) disagrees with its man page [1995/04/14] bin/342 lpd can allow users access to all of root's groups [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/24] bin/359 BS/DEL is still not quite right. [1995/04/26] kern/365 if_fddisubr.c doesn't compile (it never has...?!?) [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/04/29] kern/371 panic: msdosfs_unlock: denode not locked [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/01] bin/375 NIS does not seem to work with Kerberos [1995/05/02] kern/376 tcpdump seems to cause spontaneous reboots [1995/05/02] kern/377 Can't config any but first bus of a host adapter [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] bin/406 Sendmail 8.6.11 was not imported correctly. [1995/05/14] bin/410 bad144(8) should probably scan the bad block remap s [1995/05/14] kern/411 bad144 allow you to add blocks in the remap area [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/15] kern/424 3COM 3C509 driver doesn't support multicast [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] kern/430 SCSI Tape dont work [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] bin/441 more does not call vi with +linenum when EDITOR=vi [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/26] docs/447 typos in vnconfig.8 [1995/05/26] kern/448 ktrace not enabled in default kernel [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/28] misc/453 The release/Makefile does not make all des/eBones ta [1995/05/28] bin/454 compile ports/x11/iv and ld got sig11 [1995/05/28] misc/455 library wont compile [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/30] bin/461 Bogus lseek warning when dump large filesystems [1995/05/30] kern/462 struct utsname.version corrupted after calling uname [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] ports/467 utils/kp wrong distfile place after make fetch [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/01] kern/472 'mount /foo /foo' causes panic: ufs_lock [1995/06/01] gnu/474 typos in /usr/src/gnu/usr.bin/yppush/yppush.c [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/483 at doesn't seem to accept the time formats it's supp [1995/06/04] bin/486 ls includes utmp.h but doesn't use it [1995/06/05] misc/487 [1995/06/05] kern/488 System can not access SCSI DAT tape. [1995/06/05] bin/489 timed & timedc bugs [1995/06/05] kern/492 sysinstall shows "success" after "no space" failure. [1995/06/07] kern/496 kzip'ed kernel & modload problem [1995/06/07] kern/497 system calls to the kernel for BSDI uname() compatib [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/08] kern/501 CTRL-ALT-DEL at config> prompt causes trap 12 [FDIV [1995/06/09] bin/502 xdr_double is missing [1995/06/10] kern/503 removing floppy during write causes reboot [1995/06/12] bin/506 "Release" id generated by send-pr looks incorrect. [1995/06/13] bin/508 getnetgrent() prints un-helpful error message (with [1995/06/13] bin/509 netgroup cycle detection is too "greedy" [1995/06/13] bin/510 netgroup host matching doesn't appear to work [1995/06/14] kern/512 writing to bpf(loopback) causes kernel panic [1995/06/14] bin/513 Suspending and resuming vi gives TIOCGWINSIZ error [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] kern/516 Crynwr compatibility mode for PLIP driver. [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/15] kern/522 [1995/06/16] conf/525 The file-command does not recognice adpcm4 [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/19] misc/533 typo prevents send-pr info from being accessed [1995/06/19] bin/534 chmod doesn't work through symlinks [1995/06/19] misc/535 Sysinstall takes down the network. [1995/06/20] docs/536 No copyrights in usr/src/lib/libc/stdtime [1995/06/20] bin/537 FSCK Fails [1995/06/21] docs/538 MAP_FILE not mentioned in mmap man page. [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] kern/543 pci_bus_config() does not init parent pointers in de [1995/06/23] kern/545 System can not access SCSI DAT tape. [1995/06/23] docs/546 Shared memory manual pages [1995/06/23] bin/549 make chokes on empty rules + fix [1995/06/23] kern/551 pci_bus_config() does not init parent pointers in de [1995/06/23] bin/552 timed & timedc bugs [1995/06/23] kern/555 net/if.c can possibly choose incorrect net i/face. [1995/06/23] misc/556 Bug in /etc/rc [1995/06/23] bin/557 ar utility exausts all available file descriptors /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat Jun 24 04:43:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA05980 for bugs-outgoing; Sat, 24 Jun 1995 04:43:23 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA05972 for ; Sat, 24 Jun 1995 04:43:20 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id EAA29260 for ; Sat, 24 Jun 1995 04:42:18 -0700 Received: (dillon@localhost) by shell1.best.com (8.6.12/8.6.5) id EAA11425; Sat, 24 Jun 1995 04:41:58 -0700 Date: Sat, 24 Jun 1995 04:41:58 -0700 From: Matt Dillon Message-Id: <199506241141.EAA11425@shell1.best.com> To: bugs@freebsd.org Cc: rdy@best.com Subject: non-fatal bug in vm/vm_pageout.c Sender: bugs-owner@freebsd.org Precedence: bulk I think I've found an algorithmic bug in the pager code. in vm/vm_pageout.c, in vm_pageout_scan(), a page is moved to the end of the active queue if: * if its busy or held * if it has been referenced * act_count is greater the zero. The problem is that in the case where the page has been referenced, the reference flag is *cleared* and the page is then moved to the end of the queue. Noe, if the scan happens to reach the end of the queue, it will hit that page AGAIN, the reference count will be cleared, so it will decrement the act_count and move the page to the end of the queue AGAIN... in otherwords, it will repeatedly access the last N pages hundreds of times in that one loop, blowing their act_count and then deciding to page them out, EVEN THOUGH THEY MAY BE HEAVILY REFERENCED! The result is that act_count is effectively defeated. vm_pageout_object_deactivate_pages() would also have this problem but since it limits its scan to object->resident_page_count I think it's safe. My suggestion: When act_count is decremented, leave the page where it is... don't move it to the end of the queue. That is, around line 717 of vm/vm_pageout.c, remove the TAILQ_REMOVE/TAILQ_INSERT calls in the else. This way, all page's act_count's get equal treatment, and if the page happens to get referenced again it will be moved to the end of the queue anyway. Secondary problem: act_count only declines when paging is required. This virtually guarentees that no pages will necessarily be pagable in the first loop, before it resorts to vm_daemon(). What really needs to happen is for the active queue to be scanned say once every few seconds and act_count decremented or incremented according to whether the page has been referenced or not. Thus, when paging finally becomes necessary, act_count already has a basis. My suggestion: wakeup the pagedaemon once every 5 seconds and have it do a full scan checking for referenced/unreferenced pages, incrementing or decrementing act_count as appropriate. It would move pages to the end of the queue if it finds them referenced (as per normal), and it would move pages to the front of the queue if act_count reaches 0 (never minding the fact that newer pages more recently dropping to 0 will be paged out before older pages that have dropped to 0). -Matt Matthew Dillon VP Engineering, BEST Internet Communications, Inc. , [always include a portion of the original email in any response!] From owner-freebsd-bugs Sat Jun 24 04:56:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA06560 for bugs-outgoing; Sat, 24 Jun 1995 04:56:49 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA06554 for ; Sat, 24 Jun 1995 04:56:48 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id EAA29738 for ; Sat, 24 Jun 1995 04:55:47 -0700 Received: (dillon@localhost) by shell1.best.com (8.6.12/8.6.5) id EAA13277; Sat, 24 Jun 1995 04:55:27 -0700 Date: Sat, 24 Jun 1995 04:55:27 -0700 From: Matt Dillon Message-Id: <199506241155.EAA13277@shell1.best.com> To: bugs@freebsd.org Cc: rdy@best.com Subject: more on the paging thing Sender: bugs-owner@freebsd.org Precedence: bulk Ach! And here I thought I had found a problem... I didn't see the pcount-- in the while() loop, so the end-of-queue problem cannot occur. Damn. But the second part of my suggestion still holds.... since act_count is not touched when the system is not paging, the pages that DO get paged out are determined in a problematic fashion. So I would change my suggestions as follows: * keep the TAILQ_REMOVE/TAILQ_INSERT_TAIL in the else that I previously thought should be taken out. * run through ALL the pages in the active queue once every 5 seconds testing pmap_is_referenced() and adjusting act_count up or down. If the active count hits 0, insert the page at the head of the queue If the page was referenced, move it to the tail. This would work quite well... you can optimize it by keeping a pointer to the last page with a 0 act_count occuring before any page with a non-0 act_count, and use that as the insertion point for new pages that are decremented to 0, inserting them into the queue at that point rather then at the head of the queue. -Matt Matthew Dillon VP Engineering, BEST Internet Communications, Inc. , [always include a portion of the original email in any response!] From owner-freebsd-bugs Sat Jun 24 07:20:49 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA09301 for bugs-outgoing; Sat, 24 Jun 1995 07:20:49 -0700 Received: (from dyson@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA09292 ; Sat, 24 Jun 1995 07:20:47 -0700 From: John Dyson Message-Id: <199506241420.HAA09292@freefall.cdrom.com> Subject: Re: more on the paging thing To: dillon@best.com (Matt Dillon) Date: Sat, 24 Jun 1995 07:20:47 -0700 (PDT) Cc: bugs@freebsd.org, rdy@best.com In-Reply-To: <199506241155.EAA13277@shell1.best.com> from "Matt Dillon" at Jun 24, 95 04:55:27 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 998 Sender: bugs-owner@freebsd.org Precedence: bulk > > * run through ALL the pages in the active queue once every 5 seconds > testing pmap_is_referenced() and adjusting act_count up or down. > If the active count hits 0, insert the page at the head of the queue > If the page was referenced, move it to the tail. > 5 Seconds might be too often, and some of our iterations did do something like that. The major concern would be the scanning overhead on large systems, and the drain on CPU associated with it. > This would work quite well... you can optimize it by keeping a pointer > to the last page with a 0 act_count occuring before any page with > a non-0 act_count, and use that as the insertion point for new pages > that are decremented to 0, inserting them into the queue at that > point rather then at the head of the queue. > I'll experiment with it next time that I can get a chance. Your observations are quite astute -- and DG & I will look into them!!! John dyson@root.com From owner-freebsd-bugs Sat Jun 24 08:28:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12308 for bugs-outgoing; Sat, 24 Jun 1995 08:28:38 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12292 ; Sat, 24 Jun 1995 08:28:36 -0700 Date: Sat, 24 Jun 1995 08:28:36 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241528.IAA12292@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/308 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Do-it-yourself FTP needs to prompt for what to download FDIV001 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:27:55 PDT 1995 State-Changed-Why: This was for the old install program. From owner-freebsd-bugs Sat Jun 24 08:32:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12551 for bugs-outgoing; Sat, 24 Jun 1995 08:32:32 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12533 ; Sat, 24 Jun 1995 08:32:30 -0700 Date: Sat, 24 Jun 1995 08:32:30 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241532.IAA12533@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/310 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: ^C or ^Z in do-it-yourself FTP installation crashes system State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:32:01 PDT 1995 State-Changed-Why: Old install program. From owner-freebsd-bugs Sat Jun 24 08:33:09 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12762 for bugs-outgoing; Sat, 24 Jun 1995 08:33:09 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12747 ; Sat, 24 Jun 1995 08:33:08 -0700 Date: Sat, 24 Jun 1995 08:33:08 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241533.IAA12747@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/311 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Do-it-yourself FTP deletes /usr/tmp dir rather than contents State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:32:33 PDT 1995 State-Changed-Why: Old install program. From owner-freebsd-bugs Sat Jun 24 08:33:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12910 for bugs-outgoing; Sat, 24 Jun 1995 08:33:36 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA12894 ; Sat, 24 Jun 1995 08:33:34 -0700 Date: Sat, 24 Jun 1995 08:33:34 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241533.IAA12894@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/314 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: CTRL-Z during installation crashes install FDIV008 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:33:10 PDT 1995 State-Changed-Why: Old install program. From owner-freebsd-bugs Sat Jun 24 08:34:23 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13072 for bugs-outgoing; Sat, 24 Jun 1995 08:34:23 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13056 ; Sat, 24 Jun 1995 08:34:20 -0700 Date: Sat, 24 Jun 1995 08:34:20 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241534.IAA13056@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/315 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Kernel and boot block don't agree on kernel name FDIV010 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:33:38 PDT 1995 State-Changed-Why: caused by a SNAP not updating the boot block From owner-freebsd-bugs Sat Jun 24 08:35:17 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13228 for bugs-outgoing; Sat, 24 Jun 1995 08:35:17 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13213 ; Sat, 24 Jun 1995 08:35:12 -0700 Date: Sat, 24 Jun 1995 08:35:12 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241535.IAA13213@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/318 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: matcd driver not on boot or fixit floppy FDIV012 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:34:27 PDT 1995 State-Changed-Why: it is on boot now. fixit is dead for the time being. From owner-freebsd-bugs Sat Jun 24 08:35:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13369 for bugs-outgoing; Sat, 24 Jun 1995 08:35:58 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13348 ; Sat, 24 Jun 1995 08:35:54 -0700 Date: Sat, 24 Jun 1995 08:35:54 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241535.IAA13348@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/319 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Install doesn't strip sys name in prompt for domain FDIV013 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:35:20 PDT 1995 State-Changed-Why: old install program From owner-freebsd-bugs Sat Jun 24 08:37:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13569 for bugs-outgoing; Sat, 24 Jun 1995 08:37:05 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13553 ; Sat, 24 Jun 1995 08:37:02 -0700 Date: Sat, 24 Jun 1995 08:37:02 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241537.IAA13553@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/322 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: No way to restart a failed FTP download FDIV016 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:36:04 PDT 1995 State-Changed-Why: old install program From owner-freebsd-bugs Sat Jun 24 08:37:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13724 for bugs-outgoing; Sat, 24 Jun 1995 08:37:51 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13704 ; Sat, 24 Jun 1995 08:37:45 -0700 Date: Sat, 24 Jun 1995 08:37:45 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241537.IAA13704@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/324 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: /usr/include/sys -> /usr/sys/sys -> /usr/sys/sys FDIV018 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:37:09 PDT 1995 State-Changed-Why: old snap - long since fixed From owner-freebsd-bugs Sat Jun 24 08:38:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13914 for bugs-outgoing; Sat, 24 Jun 1995 08:38:41 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA13892 ; Sat, 24 Jun 1995 08:38:35 -0700 Date: Sat, 24 Jun 1995 08:38:35 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241538.IAA13892@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/328 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Checking for -c kernel changes randomly hangs FDIV023 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:37:54 PDT 1995 State-Changed-Why: author of this PR hasn't seen the problem since. From owner-freebsd-bugs Sat Jun 24 08:40:35 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA14160 for bugs-outgoing; Sat, 24 Jun 1995 08:40:35 -0700 Received: (from jkh@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA14145 ; Sat, 24 Jun 1995 08:40:33 -0700 Date: Sat, 24 Jun 1995 08:40:33 -0700 From: "Jordan K. Hubbard" Message-Id: <199506241540.IAA14145@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, jkh, freebsd-bugs Subject: Changed information for PR bin/309 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Do-it-yourself FTP deletes /usr/tmp dir rather than contents State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Sat Jun 24 08:40:07 PDT 1995 State-Changed-Why: old install program. From owner-freebsd-bugs Sat Jun 24 09:50:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA15955 for bugs-outgoing; Sat, 24 Jun 1995 09:50:48 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA15945 ; Sat, 24 Jun 1995 09:50:40 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA27648; Sun, 25 Jun 1995 02:45:48 +1000 Date: Sun, 25 Jun 1995 02:45:48 +1000 From: Bruce Evans Message-Id: <199506241645.CAA27648@godzilla.zeta.org.au> To: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, uhclem%nemesis@fw.ast.com Subject: Re: Changed information for PR bin/328 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Synopsis: Checking for -c kernel changes randomly hangs FDIV023 >State-Changed-From-To: open-closed >State-Changed-By: jkh >State-Changed-When: Sat Jun 24 08:37:54 PDT 1995 >State-Changed-Why: >author of this PR hasn't seen the problem since. It was probably a version mismatch. dset does _no_ checking that the kernel that is modifiying is consistent with the kernel that it was compiled for. Thus if `struct isa_device' is changed, dset at best does nothing, at second best it hangs, and at worst it corrupts the kernel. Bruce From owner-freebsd-bugs Sat Jun 24 10:19:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA17544 for bugs-outgoing; Sat, 24 Jun 1995 10:19:05 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA17530 ; Sat, 24 Jun 1995 19:19:04 +0200 Date: Sat, 24 Jun 1995 19:19:04 +0200 From: Joerg Wunsch Message-Id: <199506241719.TAA17530@freefall.cdrom.com> To: muir@idiom.com, joerg, freebsd-bugs Subject: Changed information for PR bin/483 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: at doesn't seem to accept the time formats it's supposed to State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sat Jun 24 19:16:51 MET DST 1995 State-Changed-Why: Version 1.3 of at/parsetime.c did already fix most of the complaints. The last point of the PR has been based on a misunderstanding: the date specification _must_ follow the time-of-day spec. Version 1.2 of the man pages clarifies this. From owner-freebsd-bugs Sat Jun 24 10:22:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA17792 for bugs-outgoing; Sat, 24 Jun 1995 10:22:00 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA17778 ; Sat, 24 Jun 1995 19:21:59 +0200 Date: Sat, 24 Jun 1995 19:21:59 +0200 From: Joerg Wunsch Message-Id: <199506241721.TAA17778@freefall.cdrom.com> To: tinguely@opus.cs.ndsu.NoDak.edu, joerg, freebsd-bugs Subject: Changed information for PR bin/461 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Bogus lseek warning when dump large filesystems State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sat Jun 24 19:16:51 MET DST 1995 State-Changed-Why: Suggested fix applied in version 1.3 of dump/traverse.c From owner-freebsd-bugs Sat Jun 24 10:22:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA17939 for bugs-outgoing; Sat, 24 Jun 1995 10:22:48 -0700 Received: (from joerg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA17924 ; Sat, 24 Jun 1995 19:22:46 +0200 Date: Sat, 24 Jun 1995 19:22:46 +0200 From: Joerg Wunsch Message-Id: <199506241722.TAA17924@freefall.cdrom.com> To: joerg_wunsch@uriah.heep.sax.de, joerg, freebsd-bugs Subject: Changed information for PR i386/251 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: disklabel(8) refuses to install new bootstrap State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Sat Jun 24 19:16:51 MET DST 1995 State-Changed-Why: Fixed by version 1.15 of libdisk/write_disk.c From owner-freebsd-bugs Sat Jun 24 11:46:31 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA20766 for bugs-outgoing; Sat, 24 Jun 1995 11:46:31 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA20760 for ; Sat, 24 Jun 1995 11:46:29 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id LAA00367; Sat, 24 Jun 1995 11:46:26 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00459; Sat, 24 Jun 1995 11:46:48 -0700 Message-Id: <199506241846.LAA00459@corbin.Root.COM> To: Matt Dillon cc: bugs@freebsd.org, rdy@best.com Subject: Re: more on the paging thing In-reply-to: Your message of "Sat, 24 Jun 95 04:55:27 PDT." <199506241155.EAA13277@shell1.best.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 24 Jun 1995 11:46:47 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk > Ach! And here I thought I had found a problem... I didn't see the > pcount-- in the while() loop, so the end-of-queue problem cannot > occur. Yup. > Damn. But the second part of my suggestion still holds.... since > act_count is not touched when the system is not paging, the pages > that DO get paged out are determined in a problematic fashion. Well, we used to do it that way, but the overhead of scanning all the pages was prohibitively high. After doing some fairly extensive performance tests, we found only a very slight decrease in paging performance when adjusting act_count only when memory was short. On CPU poor machines (386's), it is higher performance to do it the way it is being done now. > So I would change my suggestions as follows: > > * keep the TAILQ_REMOVE/TAILQ_INSERT_TAIL in the else that I previously > thought should be taken out. > > * run through ALL the pages in the active queue once every 5 seconds > testing pmap_is_referenced() and adjusting act_count up or down. > If the active count hits 0, insert the page at the head of the queue > If the page was referenced, move it to the tail. Actually, this won't work very well. We depend a great deal on the pseudo LRU ordering of the page queues; the more we've diverged from this, the more the performance decreases. An examination of the act_count of pages shows why - the numbers are typically low on most pages, with a small percentage (say 10- 20%) being relatively high. This means that there are "hot" pages that need to stay resident and a whole lot of other pages that need only to be carefully ordered. > This would work quite well... you can optimize it by keeping a pointer > to the last page with a 0 act_count occuring before any page with > a non-0 act_count, and use that as the insertion point for new pages > that are decremented to 0, inserting them into the queue at that > point rather then at the head of the queue. You can't do that. The state of the queues changes dynamically as processes free their private pages on exit. -DG From owner-freebsd-bugs Sat Jun 24 11:54:38 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA21245 for bugs-outgoing; Sat, 24 Jun 1995 11:54:38 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA21233 for ; Sat, 24 Jun 1995 11:54:35 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA13195; Sat, 24 Jun 1995 20:54:19 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA22802; Sat, 24 Jun 1995 20:54:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id UAA10134; Sat, 24 Jun 1995 20:44:32 +0200 From: J Wunsch Message-Id: <199506241844.UAA10134@uriah.heep.sax.de> Subject: Re: kvm_getprocs(3) man page To: abe@cc.purdue.edu Date: Sat, 24 Jun 1995 20:44:31 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199506090057.TAA10052@vic.cc.purdue.edu> from "Vic Abell" at Jun 8, 95 07:57:49 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 399 Sender: bugs-owner@FreeBSD.org Precedence: bulk As Vic Abell wrote: > > I believe the kvm_getprocs(3) man page in the 2.0 and 2.0.5-ALPHA > releases has two errors: ... > Perhaps the kvm_getprocs(3) man page needs to be updated. Thanks for pointing this out. I'm going to commit an updated man page. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jun 24 16:26:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA29488 for bugs-outgoing; Sat, 24 Jun 1995 16:26:47 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA29482 for ; Sat, 24 Jun 1995 16:26:46 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id QAA02259; Sat, 24 Jun 1995 16:25:47 -0700 Received: (dillon@localhost) by shell1.best.com (8.6.12/8.6.5) id QAA16868; Sat, 24 Jun 1995 16:25:27 -0700 Date: Sat, 24 Jun 1995 16:25:27 -0700 From: Matt Dillon Message-Id: <199506242325.QAA16868@shell1.best.com> To: davidg@Root.COM Cc: bugs@freebsd.org Subject: Re: more on the paging thing Sender: bugs-owner@freebsd.org Precedence: bulk Hmm... well, here's the problem I see: * shell machine, 130 users on line, sitting at around a load of 8 * vmstat shows free pages steadily declining * system does a spurt of paging * 30-50 processes suddenly go into the 'w' column, the 'r' column jumps to 30 as well, for about 4 seconds * things slowly smooth out again .. back to normal after 4 seconds * repeat 30 seconds later... The problem is that whenever this occurs, EVERYONE gets glitched... everything comes to a screaming stop for a few seconds, then picks up again. Obviously, some heavily used pages are being paged out when they should not be! The question is how to solve the problem. The system is not paging heavily. It's got 128MB of ram and nominally about 12M free, which drops steadily over 30 seconds to 2M or less, then the system does a spurt of paging for a few seconds which bumps the free back up to 12M, and so on.... What I would like to do is lock the pages associated with the c shared library and a few critical executable text areas (telnet, rlogind, and possibly tcsh) into memory. -Matt :> Ach! And here I thought I had found a problem... I didn't see the :> pcount-- in the while() loop, so the end-of-queue problem cannot :> occur. : : Yup. : :> Damn. But the second part of my suggestion still holds.... since :> act_count is not touched when the system is not paging, the pages :> that DO get paged out are determined in a problematic fashion. : : Well, we used to do it that way, but the overhead of scanning all the pages :was prohibitively high. After doing some fairly extensive performance tests, :we found only a very slight decrease in paging performance when adjusting :act_count only when memory was short. On CPU poor machines (386's), it is :higher performance to do it the way it is being done now. : :> So I would change my suggestions as follows: :> :> * keep the TAILQ_REMOVE/TAILQ_INSERT_TAIL in the else that I previously :> thought should be taken out. :> :> * run through ALL the pages in the active queue once every 5 seconds :> testing pmap_is_referenced() and adjusting act_count up or down. :> If the active count hits 0, insert the page at the head of the queue :> If the page was referenced, move it to the tail. : : Actually, this won't work very well. We depend a great deal on the pseudo :LRU ordering of the page queues; the more we've diverged from this, the more :the performance decreases. An examination of the act_count of pages shows why - :the numbers are typically low on most pages, with a small percentage (say 10- :20%) being relatively high. This means that there are "hot" pages that need to :stay resident and a whole lot of other pages that need only to be carefully :ordered. : :> This would work quite well... you can optimize it by keeping a pointer :> to the last page with a 0 act_count occuring before any page with :> a non-0 act_count, and use that as the insertion point for new pages :> that are decremented to 0, inserting them into the queue at that :> point rather then at the head of the queue. : : You can't do that. The state of the queues changes dynamically as processes :free their private pages on exit. : :-DG : Matthew Dillon VP Engineering, BEST Internet Communications, Inc. , [always include a portion of the original email in any response!] From owner-freebsd-bugs Sat Jun 24 16:40:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA00134 for bugs-outgoing; Sat, 24 Jun 1995 16:40:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA00127 ; Sat, 24 Jun 1995 16:40:02 -0700 Date: Sat, 24 Jun 1995 16:40:02 -0700 Message-Id: <199506242340.QAA00127@freefall.cdrom.com> From: "Jordan K. Hubbard" Reply-To: "Jordan K. Hubbard" To: freebsd-bugs Subject: docs/559: joy(4) contains a small error. In-Reply-To: Your message of Sun, 25 Jun 1995 00:21:13 +0100 <199506242321.AAA00575@whisker.internet-eireann.ie> Sender: bugs-owner@freebsd.org Precedence: bulk >Number: 559 >Category: docs >Synopsis: joy(4) contains a small error. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 24 16:40:01 1995 >Originator: Jordan K. Hubbard >Organization: FreeBSD >Release: FreeBSD 2.0.5-RELEASE i386 >Environment: >Description: The man page for the joystick driver claims that it appeared in FreeBSD 2.1. This should be changed to 2.0.5 to prevent confusion. >How-To-Repeat: >Fix: *** joy.4.orig Sun Jun 25 00:20:16 1995 --- joy.4 Sun Jun 25 00:20:35 1995 *************** *** 61,64 **** .Sh AUTHOR Jean-Marc Zucconi .Sh HISTORY ! The joystick driver appeared in FreeBSD 2.1 --- 61,64 ---- .Sh AUTHOR Jean-Marc Zucconi .Sh HISTORY ! The joystick driver appeared in FreeBSD 2.0.5 >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jun 24 18:15:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA02932 for bugs-outgoing; Sat, 24 Jun 1995 18:15:21 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA02926 for ; Sat, 24 Jun 1995 18:15:19 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id SAA01382; Sat, 24 Jun 1995 18:15:19 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id SAA00280; Sat, 24 Jun 1995 18:15:42 -0700 Message-Id: <199506250115.SAA00280@corbin.Root.COM> To: Matt Dillon cc: bugs@freebsd.org Subject: Re: more on the paging thing In-reply-to: Your message of "Sat, 24 Jun 95 16:25:27 PDT." <199506242325.QAA16868@shell1.best.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 24 Jun 1995 18:15:42 -0700 Sender: bugs-owner@freebsd.org Precedence: bulk > Hmm... well, here's the problem I see: > > * shell machine, 130 users on line, sitting at around a load of 8 > * vmstat shows free pages steadily declining > * system does a spurt of paging > * 30-50 processes suddenly go into the 'w' column, the 'r' column > jumps to 30 as well, for about 4 seconds > * things slowly smooth out again .. back to normal after 4 seconds > > * repeat 30 seconds later... > > The problem is that whenever this occurs, EVERYONE gets glitched... > everything comes to a screaming stop for a few seconds, then picks up > again. Not good... > Obviously, some heavily used pages are being paged out when they should > not be! It may seem that way, but things in this area can be quite misleading. I think the problem has to do with swapping, not the regular paging algorithm. If you're game, I think I'd like to try disabling swapping on your system and see if the problem improves. A diff is attached for this purpose. There is also a chance that this problem is another manifestation of pages being cleaned even if memory isn't really very tight; I hesitate calling this behavior a bug, but it might be good to look at it more carefully. > The question is how to solve the problem. The system is not paging > heavily. It's got 128MB of ram and nominally about 12M free, which > drops steadily over 30 seconds to 2M or less, then the system does a > spurt of paging for a few seconds which bumps the free back up to 12M, > and so on.... What I would like to do is lock the pages associated > with the c shared library and a few critical executable text areas > (telnet, rlogind, and possibly tcsh) into memory. Keep in mind that "real" free memory isn't really the complete picture. In post-FreeBSD 2.0, there is another category of free memory that is /almost/ free. We call this "VM cache pages". These pages are clean and not mapped in any process. They can be freed at anytime except during interrupts. They generally contain cached file data, but may contain parts of executables. "vmstat " hasn't yet been updated to include cache pages, but this information is available with "vmstat -s". -DG Index: vm_pageout.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_pageout.c,v retrieving revision 1.51 diff -c -r1.51 vm_pageout.c *** 1.51 1995/05/30 08:16:18 --- vm_pageout.c 1995/06/25 01:13:41 *************** *** 747,752 **** --- 747,753 ---- wakeup((caddr_t) &vfs_update_wakeup); } } + #if 0 /* * now swap processes out if we are in low memory conditions */ *************** *** 755,760 **** --- 756,762 ---- vm_pageout_req_swapout = 1; vm_req_vmdaemon(); } + #endif } if ((cnt.v_inactive_count + cnt.v_free_count + cnt.v_cache_count) < From owner-freebsd-bugs Sat Jun 24 18:35:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA03179 for bugs-outgoing; Sat, 24 Jun 1995 18:35:34 -0700 Received: from vic.cc.purdue.edu (abe@vic.cc.purdue.edu [128.210.15.16]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA03173 for ; Sat, 24 Jun 1995 18:35:33 -0700 Received: (from abe@localhost) by vic.cc.purdue.edu (8.6.12/8.6.10) id UAA15732; Sat, 24 Jun 1995 20:34:58 -0500 From: Vic Abell Message-Id: <199506250134.UAA15732@vic.cc.purdue.edu> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-bugs@FreeBSD.org Subject: Re: kvm_getprocs(3) man page In-reply-to: Your message of Sat, 24 Jun 95 20:44:31 +0200. <199506241844.UAA10134@uriah.heep.sax.de> Reply-to: abe@cc.purdue.edu Date: Sat, 24 Jun 95 20:34:57 -0500 Sender: bugs-owner@FreeBSD.org Precedence: bulk J"org, In message <199506241844.UAA10134@uriah.heep.sax.de> you write: > >As Vic Abell wrote: >> >> I believe the kvm_getprocs(3) man page in the 2.0 and 2.0.5-ALPHA >> releases has two errors: >... >> Perhaps the kvm_getprocs(3) man page needs to be updated. > >Thanks for pointing this out. I'm going to commit an updated man >page. Thank you. Keep up the good work with FreeBSD. Vic From owner-freebsd-bugs Sat Jun 24 20:39:21 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA06391 for bugs-outgoing; Sat, 24 Jun 1995 20:39:21 -0700 Received: from kryten.atinc.com (kryten.atinc.com [198.138.38.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA06385 ; Sat, 24 Jun 1995 20:39:18 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id XAA17865; Sat, 24 Jun 1995 23:31:48 -0400 Date: Sat, 24 Jun 1995 23:31:47 -0400 (EDT) From: "Jonathan M. Bresler" Subject: install from scsi tape works. To: bugs@freebsd.org cc: Jordan K Hubbard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@freebsd.org Precedence: bulk regarding: [1995/06/18] misc/530 Failed install from SCSI tape i was able to install FreeBSD 2.0.5R onto my laptop tonight using the scsi tape media. boot with tape in drive and slider closed. do all the install menu stuff...select scsi tape as the installation media the install will fail. and on vty1 it reads: st0(sea0:5:0)ILLEGAL REQUEST st0: Cannot set selected modest0: bad request, must be between 0 and 0 switch to the emergency holographic shell on vty3 mt -f /dev/rst0 fsf 1 spin the tape mt -f /dev/rst0 rewind rewind back to the start switch to vty0--the install menu screen try the install again.....voila! c'est bien! tape spins and extracts into /. 2782 blocks NOW THE RUB, on my tape at least: trying for piece 58 of 59: bin/bin.cg gunzip: stdin: unexpected end of file /stand/cpio: premature end of file switch back to vty3 cat /usr/tmp/bin/* | gunzip -t does not report any problems cat /usr/tmp/bin/* | gunzip | tar xvf - works fine. last file extracted is kernel.GENERIC cksum /kernel.GENERIC 3818494457 1085639 /kernel.GENERIC the sysinstall then cleans up from the 'failed install' and remakes all devices....hmmm then the 'Install completed sucessfully,...' message appears no option to go back and get more distributions back to vty3, get them by hand....etc jmb ps. cut the tape carefully....it wants bin/bin*, i had put bin* there. tar cvbf 10 /dev/rst0 bin/* does the trick Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346