From owner-freebsd-bugs Sun May 21 01:00:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA28063 for bugs-outgoing; Sun, 21 May 1995 01:00:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA28047 ; Sun, 21 May 1995 01:00:03 -0700 Date: Sun, 21 May 1995 01:00:03 -0700 Message-Id: <199505210800.BAA28047@freefall.cdrom.com> From: pritc003@maroon.tc.umn.edu Reply-To: pritc003@maroon.tc.umn.edu To: freebsd-bugs Subject: bin/432: mixer should print out the current mixer settings by default In-Reply-To: Your message of Sun, 21 May 1995 02:50:43 -0500 <199505210750.CAA01918@mpp.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 432 >Category: bin >Synopsis: mixer should print out the current mixer settings by default >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun May 21 01:00:02 1995 >Originator: Mike Pritchard >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-current, w/sound blaster 16 >Description: It would be nice if the "mixer" command printed out all of the current mixer settings when run with no arguments instead of printing the command usage. This would allow a person to check all of the current mixer settings at once instead of having to run "mixer vol", "mixer cd", "mixer bass", etc...for each setting they are interested in. >How-To-Repeat: >Fix: The following patch changes mixer to display all of the valid settings when run with no arguments. *** /usr/src/usr.sbin/mixer/mixer.c Wed Feb 15 11:33:03 1995 --- mixer.c Sun May 21 02:43:56 1995 *************** *** 90,97 **** --- 90,113 ---- case 2: bar = 0; break; + case 1: + bar = -1; + break; default: usage(); + } + + if (bar < 0) { + for (foo = 0; foo < SOUND_MIXER_NRDEVICES; foo++) { + if (!((1 << foo) & devmask)) + continue; + if (ioctl(baz, MIXER_READ(foo),&bar)== -1) { + perror("MIXER_READ"); + continue; + } + printf("Mixer %-8s is currently set to %3d:%d\n", names[foo], bar & 0x7f, (bar >> 8) & 0x7f); + } + return(0); } for (foo = 0; foo < SOUND_MIXER_NRDEVICES && strcmp(names[foo], argv[1]); foo++); >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun May 21 03:22:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA17412 for bugs-outgoing; Sun, 21 May 1995 03:22:11 -0700 Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA17403 for ; Sun, 21 May 1995 03:22:05 -0700 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.18.7]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id MAA08409 for ; Sun, 21 May 1995 12:08:48 +0200 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.12/8.6.9) id MAA15933; Sun, 21 May 1995 12:08:42 +0200 Date: Sun, 21 May 1995 12:08:42 +0200 Message-Id: <199505211008.MAA15933@caramba.cs.tu-berlin.de> To: bugs@FreeBSD.org Subject: unused manpages MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: bugs-owner@FreeBSD.org Precedence: bulk [2.0-950412-SNAP] $ find /usr/share/man/man* -path '*/i386/*' -links 1 /usr/share/man/man4/i386/apm.4.gz /usr/share/man/man4/i386/matcd.4.gz /usr/share/man/man8/i386/bad144.8.gz Wolfram From owner-freebsd-bugs Sun May 21 05:02:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA19130 for bugs-outgoing; Sun, 21 May 1995 05:02:50 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA19124 for ; Sun, 21 May 1995 05:02:46 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id IAA17558; Sun, 21 May 1995 08:03:10 -0400 From: Peter Dufault Message-Id: <199505211203.IAA17558@hda.com> Subject: Re: kern/430: bug in tape drivers To: bugs@ns1.win.net (Mark Hittinger) Date: Sun, 21 May 1995 08:03:10 -0400 (EDT) Cc: bugs@FreeBSD.org In-Reply-To: <199505200134.VAA07349@ns1.win.net> from "Mark Hittinger" at May 19, 95 09:34:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1082 Sender: bugs-owner@FreeBSD.org Precedence: bulk Mark Hittinger writes: > > > I have seen the same problem since 2.0R. I have a WangDAT3400DX. When a > process closes the tape drive I get "bt0a: try to abort". I believe this > is due to the lengthy rewind, although recently I noted that there was a > problem with scsi commands that contained no data. In any event I > still see the problem in -current. I will try a 2940 controller this > weekend and see if the problem exists there. > > After a few "bt0a try to abort" I get a "bt0a abort timed out". It is > at this point that horrible things happen. The driver corrupts the ccb > chain and bit sprays your disks. If the rewind finishes before the > "bt0a abort timed out" then no badness happens to your disks. > > As a short term kludge/workaround for myself I use the following patch > to sys/i386/isa/bt742a.c: > Does anyone have the console output of one of these disk splatters? 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 Sun May 21 10:52:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24456 for bugs-outgoing; Sun, 21 May 1995 10:52:10 -0700 Received: from kithrup.com (kithrup.com [140.174.23.40]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA24450 ; Sun, 21 May 1995 10:52:07 -0700 Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id KAA12689; Sun, 21 May 1995 10:52:04 -0700 Date: Sun, 21 May 1995 10:52:04 -0700 From: Sean Eric Fagan Message-Id: <199505211752.KAA12689@kithrup.com> To: freebsd-bugs@FreeBSD.org, tege@cygnus.com Subject: MAJOR problem with FreeBSD-2.0-RELEASE Sender: bugs-owner@FreeBSD.org Precedence: bulk We put together yet another system yesterday. This one had: Zappa Pentium/PCI motherboard Pentium-90 32MBytes RAM BusLogic PCI SCSI controller Spider Tarantula PCI graphics card WD8013 ethernet card (ed0 found it, no problem) We installed from the CD-ROM. After getting it all up and installed, I proceeded to play with it a bit -- the first thing I wanted to do was build a new kernel. So, I did cd /usr/src/sys/i386/conf cp GENERIC TEGE vi TEGE The kernel panic'ed, in vm_bounce. It does this fairly reliably. The owner of the system also reports that it dies when gcc runs, as well. Help! We have until about Wednesday to get a working version of FreeBSD on this system, or else some other *nix goes on it (yech ;)). Sean. From owner-freebsd-bugs Sun May 21 10:57:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA24631 for bugs-outgoing; Sun, 21 May 1995 10:57:39 -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 KAA24625 for ; Sun, 21 May 1995 10:57:37 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA22523; Sun, 21 May 1995 11:00:36 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id KAA00140; Sun, 21 May 1995 10:57:37 -0700 Message-Id: <199505211757.KAA00140@corbin.Root.COM> To: Sean Eric Fagan cc: freebsd-bugs@FreeBSD.org, tege@cygnus.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 10:52:04 PDT." <199505211752.KAA12689@kithrup.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 21 May 1995 10:57:36 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >We put together yet another system yesterday. This one had: > > Zappa Pentium/PCI motherboard > Pentium-90 > 32MBytes RAM > BusLogic PCI SCSI controller > Spider Tarantula PCI graphics card > WD8013 ethernet card (ed0 found it, no problem) > >We installed from the CD-ROM. After getting it all up and installed, I >proceeded to play with it a bit -- the first thing I wanted to do was build >a new kernel. So, I did > > cd /usr/src/sys/i386/conf > cp GENERIC TEGE > vi TEGE > >The kernel panic'ed, in vm_bounce. It does this fairly reliably. The owner >of the system also reports that it dies when gcc runs, as well. Try to generate a kernel without options "BOUNCE_BUFFERS". If you can't get the machine to stay up long enough to do this, take out 16MB of memory (this effectively disables bounce buffers). I don't know what the problem is - I haven't seen it here, but then I don't use bounce buffers. -DG From owner-freebsd-bugs Sun May 21 11:08:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA24762 for bugs-outgoing; Sun, 21 May 1995 11:08:37 -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 LAA24756 for ; Sun, 21 May 1995 11:08:33 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA03558; Sun, 21 May 1995 11:08:16 -0700 From: "Rodney W. Grimes" Message-Id: <199505211808.LAA03558@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: sef@kithrup.com (Sean Eric Fagan) Date: Sun, 21 May 1995 11:08:16 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org, tege@cygnus.com In-Reply-To: <199505211752.KAA12689@kithrup.com> from "Sean Eric Fagan" at May 21, 95 10:52:04 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: 1704 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > We put together yet another system yesterday. This one had: > > Zappa Pentium/PCI motherboard Take that motherboard and through it in the nearest garbage can, you have not been following my posts on the lists about this board. It is trash, garbage, junk, crappola, etc etc etc... > Pentium-90 > 32MBytes RAM > BusLogic PCI SCSI controller I no longer support BusLogic products, too many problems, and too long on hold with tech support (I wasted 4 hours on hold trying to get the new PROMS for my BT946, after that much time I just cross a mfg off my list due to lack of ``reasonable techinical support''. > Spider Tarantula PCI graphics card > WD8013 ethernet card (ed0 found it, no problem) > > We installed from the CD-ROM. After getting it all up and installed, I > proceeded to play with it a bit -- the first thing I wanted to do was build > a new kernel. So, I did > > cd /usr/src/sys/i386/conf > cp GENERIC TEGE > vi TEGE > > The kernel panic'ed, in vm_bounce. It does this fairly reliably. The owner > of the system also reports that it dies when gcc runs, as well. Ehh??? We should not be doing vm_bounce with a PCI BT946 card, it has 32 bit addressing. What did the probe say about the Bt946 card? Does the kernel you are running have BOUNCE_BUFFERS in it. > Help! We have until about Wednesday to get a working version of FreeBSD on > this system, or else some other *nix goes on it (yech ;)). I'll try, but given the fact your using 2 products I won't touch with a 10 foot pole it might be hard :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun May 21 11:16:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA24857 for bugs-outgoing; Sun, 21 May 1995 11:16:19 -0700 Received: from relay3.UU.NET (relay3.UU.NET [192.48.96.8]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA24851 for ; Sun, 21 May 1995 11:16:18 -0700 Received: from cygnus.com by relay3.UU.NET with ESMTP id QQyqsf25577; Sun, 21 May 1995 14:16:04 -0400 Received: from localhost.cygnus.com (rtl.cygnus.com [140.174.1.2]) by cygnus.com (8.6.12/8.6.9) with ESMTP id LAA23750; Sun, 21 May 1995 11:16:04 -0700 Message-Id: <199505211816.LAA23750@cygnus.com> To: davidg@Root.COM cc: Sean Eric Fagan , freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 1995 10:57:36 PDT." <199505211757.KAA00140@corbin.Root.COM> Date: Sun, 21 May 1995 11:16:04 -0700 From: Torbjorn Granlund Sender: bugs-owner@FreeBSD.org Precedence: bulk We already tried with a kernel without "BOUNCE_BUFFERS". The kernel still panics for lots and lots of commands. Now the panics are differewnt, things like "page fault while in kernel mode". I cannot take out 16M of memory, since the two 16M SIMMS are both needed for the Triton chip set to be happy. (And I don't have any 8M SIMMs to try.) Another problem is the driver for the buslogic card (bt742.c?). It doesn't do synchronuous SCSI with my Buslogic KT-946C. I cannot get to ftp.cdrom.com, so I cannot check if the driver is improved. Is it? Note that we observed the exact same behaviour when using FreeBSD 2.0 on a completely different system (different CPU, motherboard, disks, SCSI card) . This makes it unlikely to be hardware problems. From owner-freebsd-bugs Sun May 21 11:17:48 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA24879 for bugs-outgoing; Sun, 21 May 1995 11:17: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 LAA24873 for ; Sun, 21 May 1995 11:17:45 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA11603; Mon, 22 May 1995 04:16:57 +1000 Date: Mon, 22 May 1995 04:16:57 +1000 From: Bruce Evans Message-Id: <199505211816.EAA11603@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.org, sef@kithrup.com, tege@cygnus.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE Sender: bugs-owner@FreeBSD.org Precedence: bulk > Zappa Pentium/PCI motherboard > Pentium-90 > 32MBytes RAM > BusLogic PCI SCSI controller > Spider Tarantula PCI graphics card > WD8013 ethernet card (ed0 found it, no problem) >The kernel panic'ed, in vm_bounce. It does this fairly reliably. The owner >of the system also reports that it dies when gcc runs, as well. There have been several reports that bounce buffering is broken. The bt driver always enables bounce buffering, although this at best wastes time on non-ISA systems. Bruce From owner-freebsd-bugs Sun May 21 11:48:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25598 for bugs-outgoing; Sun, 21 May 1995 11:48:10 -0700 Received: from kithrup.com (kithrup.com [140.174.23.40]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA25592 for ; Sun, 21 May 1995 11:48:09 -0700 Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id LAA13914; Sun, 21 May 1995 11:47:44 -0700 Date: Sun, 21 May 1995 11:47:44 -0700 From: Sean Eric Fagan Message-Id: <199505211847.LAA13914@kithrup.com> To: bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org, tege@cygnus.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE Sender: bugs-owner@FreeBSD.org Precedence: bulk >There have been several reports that bounce buffering is broken. The bt >driver always enables bounce buffering, although this at best wastes time >on non-ISA systems. Some more information: the system has a Quantum 4.1GByte drive on it (one of the Grand Prix, supposedly, although it apparantly identifies itself as a slightly different model). I just tried running a kernel without bounce buffers, without an ed0 driver, and with MAXMEM set to 16384. I booted, and then tried to build bash by cd /usr/src/local/bash* make It first gave a warning/error message from the buslogic driver, saying something about there being more than 33 mbxs (I think it was); there was then a message from the scsi code saying "oops" something wasn't queued. The system then got a kernel page fault, and paniced. Before that, with slightly different kernels, I'd noticed that cd /sys/i386/conf vi TEGE would get the buslogic warnings/errors, and vi would come up with an empty file, or core dump. If, however, I did vi :e TEGE it would work. I think he is going to install Linux. This is the second motherboard he's been unsuccessful in running FreeBSD-2.0 on. Sean. From owner-freebsd-bugs Sun May 21 12:19:19 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA25947 for bugs-outgoing; Sun, 21 May 1995 12:19:19 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA25940 ; Sun, 21 May 1995 12:19:18 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Sean Eric Fagan cc: bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org, tege@cygnus.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 11:47:44 PDT." <199505211847.LAA13914@kithrup.com> Date: Sun, 21 May 1995 12:19:17 -0700 Message-ID: <25939.801083957@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > I think he is going to install Linux. This is the second motherboard he's > been unsuccessful in running FreeBSD-2.0 on. Probably not a bad idea. Your friend is clearly cursed, as I've put together dozens of PCI/Buslogic combos with both FreeBSD 2.0R and later and never had even one of the problems you're experiencing. Are you guys wearing wrist straps? :-) Jordan From owner-freebsd-bugs Sun May 21 12:44:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA26504 for bugs-outgoing; Sun, 21 May 1995 12:44:42 -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 MAA26498 for ; Sun, 21 May 1995 12:44:39 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA03687; Sun, 21 May 1995 12:44:11 -0700 From: "Rodney W. Grimes" Message-Id: <199505211944.MAA03687@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: tege@cygnus.com (Torbjorn Granlund) Date: Sun, 21 May 1995 12:44:11 -0700 (PDT) Cc: davidg@Root.COM, sef@kithrup.com, freebsd-bugs@FreeBSD.org In-Reply-To: <199505211816.LAA23750@cygnus.com> from "Torbjorn Granlund" at May 21, 95 11:16:04 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: 1975 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > We already tried with a kernel without "BOUNCE_BUFFERS". The kernel still > panics for lots and lots of commands. Now the panics are differewnt, things > like "page fault while in kernel mode". I cannot take out 16M of memory, > since the two 16M SIMMS are both needed for the Triton chip set to be happy. > (And I don't have any 8M SIMMs to try.) If this is the Intel Zappa board, make sure you are using TIN connectors on the SIMM modules, if they are gold you may have a very serious memory system problem. (The data book that came with your Zappa board will say to use only Tin SIMM modules, believe it!!!). This really smells like memory system problems. Are you running a 90Mhz or 100Mhz CPU?? The Zappa board is not rated for 100Mhz operation (or at least the 2 board I looked at clearly stated 75 or 90Mhz but not 100 Mhz.) > Another problem is the driver for the buslogic card (bt742.c?). It doesn't > do synchronuous SCSI with my Buslogic KT-946C. I cannot get to > ftp.cdrom.com, so I cannot check if the driver is improved. Is it? Humm.. been running bt946's in sync mode for over a year, what version of the board/BIOS/firmware do you have? Do you have the sync options enabled on the bt946C? > Note that we observed the exact same behaviour when using FreeBSD 2.0 on a > completely different system (different CPU, motherboard, disks, SCSI card) . > This makes it unlikely to be hardware problems. Ahh... FreeBSD 2.0, been a long time since I've run it, could very well be problems in that release. Though I have run make world using it to upgrade a system to 2.0 current back in February (initial boot strapping of my build environment here after being gone for some time). That was run on a Opti based P54C-90 with a BT946C and 16MB, would not have seen a bounce buffer bug :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun May 21 13:21:34 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27435 for bugs-outgoing; Sun, 21 May 1995 13:21:34 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA27428 for ; Sun, 21 May 1995 13:21:30 -0700 Received: from cygnus.com by relay2.UU.NET with ESMTP id QQyqsn27804; Sun, 21 May 1995 16:21:28 -0400 Received: from localhost.cygnus.com (rtl.cygnus.com [140.174.1.2]) by cygnus.com (8.6.12/8.6.9) with ESMTP id NAA25309; Sun, 21 May 1995 13:21:27 -0700 Message-Id: <199505212021.NAA25309@cygnus.com> To: "Rodney W. Grimes" cc: davidg@Root.COM, sef@kithrup.com, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 1995 12:44:11 PDT." <199505211944.MAA03687@gndrsh.aac.dev.com> Date: Sun, 21 May 1995 13:21:26 -0700 From: Torbjorn Granlund Sender: bugs-owner@FreeBSD.org Precedence: bulk If this is the Intel Zappa board, make sure you are using TIN connectors on the SIMM modules, if they are gold you may have a very serious memory system problem. (The data book that came with your Zappa board will say to use only Tin SIMM modules, believe it!!!). The SIMMs have tin connectors. This really smells like memory system problems. Are you running a 90Mhz or 100Mhz CPU?? The Zappa board is not rated for 100Mhz operation (or at least the 2 board I looked at clearly stated 75 or 90Mhz but not 100 Mhz.) I use a 90 MHz CPU. (Becasue of the 20ns SRAMs I didn't dare to set the jumpers for a 66 MHz external clock rate.) > Another problem is the driver for the buslogic card (bt742.c?). It doesn't > do synchronuous SCSI with my Buslogic KT-946C. I cannot get to > ftp.cdrom.com, so I cannot check if the driver is improved. Is it? Humm.. been running bt946's in sync mode for over a year, what version of the board/BIOS/firmware do you have? I don't remember, but the card is brand new. (I'll check the version in a bit.) Do you have the sync options enabled on the bt946C? They are enabled correctly. And the BIOS recognizes that the drive is capable of synchronuous transfers! > Note that we observed the exact same behaviour when using FreeBSD 2.0 on > a completely different system (different CPU, motherboard, disks, SCSI > card) . This makes it unlikely to be hardware problems. Ahh... FreeBSD 2.0, been a long time since I've run it, could very well be problems in that release. Though I have run make world using it to upgrade a system to 2.0 current back in February (initial boot strapping of my build environment here after being gone for some time). That was run on a Opti based P54C-90 with a BT946C and 16MB, would not have seen a bounce buffer bug :-(. Could you possibly make a newer kernel that I can try? From owner-freebsd-bugs Sun May 21 13:23:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27519 for bugs-outgoing; Sun, 21 May 1995 13:23:45 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA27508 for ; Sun, 21 May 1995 13:23:38 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id QAA18523; Sun, 21 May 1995 16:23:28 -0400 From: Peter Dufault Message-Id: <199505212023.QAA18523@hda.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: sef@kithrup.com (Sean Eric Fagan) Date: Sun, 21 May 1995 16:23:27 -0400 (EDT) Cc: bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org, tege@cygnus.com In-Reply-To: <199505211847.LAA13914@kithrup.com> from "Sean Eric Fagan" at May 21, 95 11:47:44 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2262 Sender: bugs-owner@FreeBSD.org Precedence: bulk Sean Eric Fagan writes: > > >There have been several reports that bounce buffering is broken. The bt > >driver always enables bounce buffering, although this at best wastes time > >on non-ISA systems. > > Some more information: > > the system has a Quantum 4.1GByte drive on it (one of the Grand Prix, > supposedly, although it apparantly identifies itself as a slightly different > model). > > I just tried running a kernel without bounce buffers, without an ed0 driver, > and with MAXMEM set to 16384. I booted, and then tried to build bash by > > cd /usr/src/local/bash* > make > > It first gave a warning/error message from the buslogic driver, saying > something about there being more than 33 mbxs (I think it was); there was > then a message from the scsi code saying "oops" something wasn't queued. > The system then got a kernel page fault, and paniced. > > Before that, with slightly different kernels, I'd noticed that > > cd /sys/i386/conf > vi TEGE > > would get the buslogic warnings/errors, and vi would come up with an empty > file, or core dump. If, however, I did > > vi > :e TEGE > > it would work. > > I think he is going to install Linux. This is the second motherboard he's > been unsuccessful in running FreeBSD-2.0 on. > > Sean. > "oops not queued" should be changed to be a panic (kick me if you disagree, Julian, but I'd change it now even before 2.0.5 burns). Now I'll go out on a limb and guess: our Buslogic support is broken. Someone has to provide an alternate SCSI board to these customers until it is fixed. In spite of what Rodney said earlier, I like Buslogic because they have been extremely helpful to me in the past, and so the help they gave me cancels the four hour phone wait Rodney had, and FreeBSD customers should give them another chance and let's not put them on our "Don't buy this stuff" list (It wasn't that long ago that I regularly saw "buy Buslogic" postings). Is anyone in a position to get a known working PCI SCSI board to sef? This is a FreeBSD support challenge and I'd like to see us rise to it. 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 Sun May 21 13:29:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27710 for bugs-outgoing; Sun, 21 May 1995 13:29:28 -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 NAA27703 for ; Sun, 21 May 1995 13:29:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA03831; Sun, 21 May 1995 13:29:05 -0700 From: "Rodney W. Grimes" Message-Id: <199505212029.NAA03831@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: tege@cygnus.com (Torbjorn Granlund) Date: Sun, 21 May 1995 13:29:05 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199505212021.NAA25309@cygnus.com> from "Torbjorn Granlund" at May 21, 95 01:21:26 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: 3320 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > If this is the Intel Zappa board, make sure you are using TIN connectors > on the SIMM modules, if they are gold you may have a very serious memory > system problem. (The data book that came with your Zappa board will > say to use only Tin SIMM modules, believe it!!!). > > The SIMMs have tin connectors. Okay, good! > This really smells like memory system problems. Are you running a 90Mhz > or 100Mhz CPU?? The Zappa board is not rated for 100Mhz operation (or > at least the 2 board I looked at clearly stated 75 or 90Mhz but not > 100 Mhz.) > > I use a 90 MHz CPU. (Becasue of the 20ns SRAMs I didn't dare to set the > jumpers for a 66 MHz external clock rate.) That is why the board is rate for 90Mhz, and even then they have to be pushing the limits a little. All the other boards I use have 15nS cache chips, this is the first 90Mhz board I have seen with 20nS chips in it :-(. > > Another problem is the driver for the buslogic card (bt742.c?). It doesn't > > do synchronuous SCSI with my Buslogic KT-946C. I cannot get to > > ftp.cdrom.com, so I cannot check if the driver is improved. Is it? > > Humm.. been running bt946's in sync mode for over a year, what version > of the board/BIOS/firmware do you have? > > I don't remember, but the card is brand new. (I'll check the version in a > bit.) Brand new means little with Bus Logic, and the time it takes for new versions of the board to trickly through the distribution channel. I have found my old versions of the cards to actually work better then the newer versions!! [Just ask Jordan, he had a nightmare with the latest version of cards from Bus Logic, so have I, basically can't get the d*mn things to work with several of my newer motherboards, and due to lack of Bus Logic's technical support have shit canned the whole product line :-(] > Do you have the sync options enabled on the bt946C? > > They are enabled correctly. And the BIOS recognizes that the drive is > capable of synchronuous transfers! But then reports to FreeBSD that the board is in async mode, seems we had someone else with this problem, seems BL has changed a bit definition on us :-(. > > Note that we observed the exact same behaviour when using FreeBSD 2.0 on > > a completely different system (different CPU, motherboard, disks, SCSI > > card) . This makes it unlikely to be hardware problems. > > Ahh... FreeBSD 2.0, been a long time since I've run it, could very well > be problems in that release. Though I have run make world using it > to upgrade a system to 2.0 current back in February (initial boot strapping > of my build environment here after being gone for some time). That was > run on a Opti based P54C-90 with a BT946C and 16MB, would not have seen > a bounce buffer bug :-(. > > Could you possibly make a newer kernel that I can try? Could, but it will have lots of problems with 2.0 binaries, especially networking code. You could also grab the kernel from freefall, or grab the 950412 snap floppies and get a kernel from there. These will all have 2.0R compatibility problems, but at least it should be more stable. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun May 21 13:37:47 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27908 for bugs-outgoing; Sun, 21 May 1995 13:37:47 -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 NAA27901 ; Sun, 21 May 1995 13:37:44 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Torbjorn Granlund cc: "Rodney W. Grimes" , davidg@Root.COM, sef@kithrup.com, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 13:21:26 PDT." <199505212021.NAA25309@cygnus.com> Date: Sun, 21 May 1995 13:37:44 -0700 Message-ID: <27900.801088664@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > They are enabled correctly. And the BIOS recognizes that the drive is > capable of synchronuous transfers! And if you're using a Quantum GP or Seagate Barracuda drive, sync transfers are broken with the Buslogic controller (I've verified this from the adapter _BIOS_, so the operating system has nothing to do with it) - try turning sync negotiation off. Jordan From owner-freebsd-bugs Sun May 21 13:39:54 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27957 for bugs-outgoing; Sun, 21 May 1995 13:39:54 -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 NAA27950 ; Sun, 21 May 1995 13:39:52 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Peter Dufault cc: sef@kithrup.com (Sean Eric Fagan), bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org, tege@cygnus.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 16:23:27 EDT." <199505212023.QAA18523@hda.com> Date: Sun, 21 May 1995 13:39:51 -0700 Message-ID: <27949.801088791@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > Is anyone in a position to get a known working PCI SCSI board to > sef? If he wants an Adaptec 2940, he's free to come up and get it (I'm not driving to Palo Alto AGAIN - he owes me the next visit :-). I'll happily swap for the Buslogic. I'll even give him a kernel boot floppy that works with it. We can burn 2.0-950412-SNAP onto a CD or something to go with it. Jordan From owner-freebsd-bugs Sun May 21 13:40:11 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA27987 for bugs-outgoing; Sun, 21 May 1995 13:40:11 -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 NAA27978 for ; Sun, 21 May 1995 13:40:06 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA03864; Sun, 21 May 1995 13:39:46 -0700 From: "Rodney W. Grimes" Message-Id: <199505212039.NAA03864@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: dufault@hda.com (Peter Dufault) Date: Sun, 21 May 1995 13:39:46 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199505212023.QAA18523@hda.com> from "Peter Dufault" at May 21, 95 04:23:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4397 Sender: bugs-owner@FreeBSD.org Precedence: bulk [CC: trimmed back to bugs list] > Sean Eric Fagan writes: > > > > >There have been several reports that bounce buffering is broken. The bt > > >driver always enables bounce buffering, although this at best wastes time > > >on non-ISA systems. > > > > Some more information: > > > > the system has a Quantum 4.1GByte drive on it (one of the Grand Prix, > > supposedly, although it apparantly identifies itself as a slightly different > > model). Well, if it where not for the Quantum Grand Prix I would offer the loan of a NCR 810 card, but I know that to be a problem :-(. > > I just tried running a kernel without bounce buffers, without an ed0 driver, > > and with MAXMEM set to 16384. I booted, and then tried to build bash by > > > > cd /usr/src/local/bash* > > make > > > > It first gave a warning/error message from the buslogic driver, saying > > something about there being more than 33 mbxs (I think it was); there was > > then a message from the scsi code saying "oops" something wasn't queued. > > The system then got a kernel page fault, and paniced. > > > > Before that, with slightly different kernels, I'd noticed that > > > > cd /sys/i386/conf > > vi TEGE > > > > would get the buslogic warnings/errors, and vi would come up with an empty > > file, or core dump. If, however, I did > > > > vi > > :e TEGE > > > > it would work. > > > > I think he is going to install Linux. This is the second motherboard he's > > been unsuccessful in running FreeBSD-2.0 on. > > > > Sean. > > > > "oops not queued" should be changed to be a panic (kick me if you > disagree, Julian, but I'd change it now even before 2.0.5 burns). Agreed, I have never seen it recover from this once it happens. > Now I'll go out on a limb and guess: our Buslogic support is broken. Could be, I quite using them :-(. > Someone has to provide an alternate SCSI board to these customers until > it is fixed. I would, but the only other PCI card I have won't play with the Grand Prix drive that he has (or so I've been told, haven't been able to test it out here since I don't have any Grand Prix drives). > In spite of what Rodney said earlier, I like Buslogic because they > have been extremely helpful to me in the past, and so the help they > gave me cancels the four hour phone wait Rodney had, and FreeBSD > customers should give them another chance and let's not put them > on our "Don't buy this stuff" list (It wasn't that long ago that > I regularly saw "buy Buslogic" postings). I use to boast that Bus Logic was one of the best products around to get, and would still if not only myself, but David and Jordan both spent similiar N hour sessions tryings to get to there technical support folks. It is a very clear indication that when tech support gets that far back logged (I left no less than 5 messages, and still 30 days later have not had a return call!!!) that they have a *real* product problem. There tech support use to be *excelent*, I have even said so in many mail messages. It is sad to see this has changed for the worse :-(. I will not be pursuaded to change my stance on Bus Logic due to past record. There current record is horrible, and that is enough for me to pursuade people to seek alternatives, realize I sell these products, and customers of mine would not be very happy if I sold them something I know to have compatibility problems, and know that tech support is lacking for. > Is anyone in a position to get a known working PCI SCSI board to > sef? I would, but don't have an alternative that would work in his setup, well, wait, I have a aha2940 here, sef, you want to try that out? I could send it out UPS Red on monday, you would have it Tuesday. Wait, that won't work, he is trying to install 2.0R which does not have proper support for the aha2940 :-(, arghh...!!! > This is a FreeBSD support challenge and I'd like to see us rise to > it. I am trying, but can't do much when the system has products in it that have known problems that I have tried to resolve as best I can myself (why do you think I wasted 4 hours long distance on hold to Bus Logic.) I would rather go after the Quantum/NCR problem at this point in the game than I would go after BusLogic any further. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Sun May 21 13:43:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA28133 for bugs-outgoing; Sun, 21 May 1995 13:43:36 -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 NAA28127 ; Sun, 21 May 1995 13:43:33 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id NAA22859; Sun, 21 May 1995 13:46:37 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA00165; Sun, 21 May 1995 13:43:39 -0700 Message-Id: <199505212043.NAA00165@corbin.Root.COM> To: "Jordan K. Hubbard" cc: Torbjorn Granlund , "Rodney W. Grimes" , sef@kithrup.com, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 13:37:44 PDT." <27900.801088664@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 21 May 1995 13:43:38 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >> They are enabled correctly. And the BIOS recognizes that the drive is >> capable of synchronuous transfers! > >And if you're using a Quantum GP or Seagate Barracuda drive, sync >transfers are broken with the Buslogic controller (I've verified this >from the adapter _BIOS_, so the operating system has nothing to do >with it) - try turning sync negotiation off. If it's a Grand Prix, it won't work _without_ sync negotiation turned on. -DG From owner-freebsd-bugs Sun May 21 14:01:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA28592 for bugs-outgoing; Sun, 21 May 1995 14:01:12 -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 OAA28585 ; Sun, 21 May 1995 14:01:10 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: davidg@Root.COM cc: Torbjorn Granlund , "Rodney W. Grimes" , sef@kithrup.com, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 13:43:38 PDT." <199505212043.NAA00165@corbin.Root.COM> Date: Sun, 21 May 1995 14:01:09 -0700 Message-ID: <28584.801090069@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > >And if you're using a Quantum GP or Seagate Barracuda drive, sync > >transfers are broken with the Buslogic controller (I've verified this > >from the adapter _BIOS_, so the operating system has nothing to do > >with it) - try turning sync negotiation off. > > If it's a Grand Prix, it won't work _without_ sync negotiation turned on. Uhhh. That's not at all consistent with my experience. Jordan From owner-freebsd-bugs Sun May 21 14:05:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA28700 for bugs-outgoing; Sun, 21 May 1995 14:05: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 OAA28694 ; Sun, 21 May 1995 14:05:52 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id OAA22898; Sun, 21 May 1995 14:08:55 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id OAA02260; Sun, 21 May 1995 14:05:57 -0700 Message-Id: <199505212105.OAA02260@corbin.Root.COM> To: "Jordan K. Hubbard" cc: Torbjorn Granlund , "Rodney W. Grimes" , sef@kithrup.com, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 14:01:09 PDT." <28584.801090069@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 21 May 1995 14:05:57 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >> >And if you're using a Quantum GP or Seagate Barracuda drive, sync >> >transfers are broken with the Buslogic controller (I've verified this >> >from the adapter _BIOS_, so the operating system has nothing to do >> >with it) - try turning sync negotiation off. >> >> If it's a Grand Prix, it won't work _without_ sync negotiation turned on. > >Uhhh. That's not at all consistent with my experience. Nonetheless, that is what happend when I assembled wcarchive in its multiple forms. The Barracuda's didn't care, but the Grand Prix's would not work without sync negotiation turned on. -DG From owner-freebsd-bugs Sun May 21 16:37:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA01476 for bugs-outgoing; Sun, 21 May 1995 16:37:46 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA01470 for ; Sun, 21 May 1995 16:37:40 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id AAA04352; Mon, 22 May 1995 00:37:12 +0100 From: Paul Richards Message-Id: <199505212337.AAA04352@isl.cf.ac.uk> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 22 May 1995 00:37:12 +0100 (BST) Cc: tege@cygnus.com, freebsd-bugs@FreeBSD.org In-Reply-To: <199505212029.NAA03831@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 21, 95 01:29:05 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 912 Sender: bugs-owner@FreeBSD.org Precedence: bulk In reply to Rodney W. Grimes who said > > Brand new means little with Bus Logic, and the time it takes for new versions > of the board to trickly through the distribution channel. I have found my > old versions of the cards to actually work better then the newer versions!! > [Just ask Jordan, he had a nightmare with the latest version of cards from > Bus Logic, so have I, basically can't get the d*mn things to work with > several of my newer motherboards, and due to lack of Bus Logic's technical > support have shit canned the whole product line :-(] Brand new can actually mean broke :-( It took me ages to get my 946C working on a Plato motherboard and in the end I got it to work by using *older* firmware! -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.isl.cf.ac.uk/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) From owner-freebsd-bugs Sun May 21 16:47:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA01541 for bugs-outgoing; Sun, 21 May 1995 16:47:44 -0700 Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id QAA01535 for ; Sun, 21 May 1995 16:47:31 -0700 Date: Mon, 22 May 1995 00:00:00 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <624@nwpeople.demon.co.uk> To: bugs@FreeBSD.org Subject: 2.0-950412-SNAP install problem X-Mailer: PCElm 1.10 Lines: 72 Sender: bugs-owner@FreeBSD.org Precedence: bulk Hi, I have encountered a problem trying to install 2.0-950412-SNAP. Hardware: Gateway 4DX2-66P Diamond Stealth 64 VRAM (PCI) Oak EIDE Controller (PCI) WD Caviare 540MB IDE disk (1048 cyls) Adaptec 2940 SCSI controller Seagate ST31250 SCSI disk (all other cards removed) The IDE disk (wd0) has DOS and FreeBSD 1.1 slices. The FreeBSD 1.1 slice starts below cylinder 1024. BIOS LBA translation is disabled; I lied to the BIOS and told it the disk has 1024 cylinders. I am attempting to install FreeBSD 2.0 on the entire SCSI disk (sd0). I have reached the point where I can boot from the hard disk (sd0, using hd(1,a)/kernel at boot prompt). The kernel boots successfully, and finds all expected devices, but the message wd0: can't handle 32 heads from partition table... appears. All the filesystems on sd0 are fsck'd without error. I then attempt to load the distributions from the DOS slice on wd0. I specify /dev/wd0e as the device to mount, it seems to mount successfully. I specify the path from mount point as freebsd/950412.snp, but then I get an error message saying it can't cd to that directory. At this point I exit from the installation utility to a shell. 'mount' shows /dev/wd0e mounted on /mnt. 'ls /mnt' shows the contents of the DOS root directory. 'ls /mnt/thing', where thing is an existing DOS directory, produces either garbage (but garbage formatted like a ls listing), or an error message such as the following: wd0e: hard error reading fsbn 296033 of 296033-296040 (wd0 bn 296096; cn 146 tn 27 sn 59): status 51 error 54 (repeated twice) When I try to 'umount /mnt', the system hangs. After all this I boot DOS, run scandisk, and it reports no errors. I boot FreeBSD 1.1 (from wd0), and it successfully mounts and reads the DOS filesystem. I have been through the above cycle several times with the same results each time. I have tried a BT-946C in place of the AHA-2940, with no improvement. Basically I'm stumped. Any suggestions? I'll be happy to attempt more detailed diagnostics if you can point me in the right direction. I've been using FreeBSD 1.1 daily for over a year, and it has proved extremely robust. I have installed 2.0-950412-SNAP on an HP Vectra 486/66VL (on the second IDE disk), and on a Gateway 4DX2-66V (on slice of IDE disk), and I'm impressed. Thank you all and keep up the good work! iain -- Iain Baird Network People International Tel: +44 (0)1732 743591 From owner-freebsd-bugs Sun May 21 20:15:50 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA07578 for bugs-outgoing; Sun, 21 May 1995 20:15:50 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id UAA07572 for ; Sun, 21 May 1995 20:15:47 -0700 Message-Id: <199505220315.UAA07572@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA23952; Sun, 21 May 1995 23:15:40 -0400 Date: Sun, 21 May 1995 23:15:40 -0400 From: Charles Henrich To: freebsd-bugs@FreeBSD.org Subject: MAJOR problem with FreeBSD-2.0-RELEASE X-Newsreader: NN version 6.5.0 #10 (NOV) Sender: bugs-owner@FreeBSD.org Precedence: bulk I will not be pursuaded to change my stance on Bus Logic due to past record. There current record is horrible, and that is enough for me to pursuade people to seek alternatives, realize I sell these products, ^^^^^^^^^^^^^^^^^ Wait a minute, your telling me that because the support for the buslogic cards are broken (when not two weeks ago it was the card suggested as the best and most reliable by many on the freebsd-hackers lists) that we should buy different cards instead of fixing the broken drivers? If this is how broken drivers are handled (okay, dont use THAT one) FreeBSD has some serious problems... Tell me Im misunderstanding something here, afterall I know I chose FreeBSD over Linux primarily because I felt it was better supported with a central core team and such. Is this not a true statement? -Crh -- Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Sun May 21 21:21:30 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA09150 for bugs-outgoing; Sun, 21 May 1995 21:21:30 -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 VAA09138 for ; Sun, 21 May 1995 21:21:28 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id VAA23389; Sun, 21 May 1995 21:24:31 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id VAA03476; Sun, 21 May 1995 21:21:33 -0700 Message-Id: <199505220421.VAA03476@corbin.Root.COM> To: Charles Henrich cc: freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 23:15:40 EDT." <199505220315.UAA07572@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 21 May 1995 21:21:32 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >I will not be pursuaded to change my stance on Bus Logic due to past >record. There current record is horrible, and that is enough for me >to pursuade people to seek alternatives, realize I sell these products, > ^^^^^^^^^^^^^^^^^ > >Wait a minute, your telling me that because the support for the buslogic cards >are broken (when not two weeks ago it was the card suggested as the best and >most reliable by many on the freebsd-hackers lists) that we should buy >different cards instead of fixing the broken drivers? If this is how broken >drivers are handled (okay, dont use THAT one) FreeBSD has some serious >problems... Tell me Im misunderstanding something here, afterall I know I >chose FreeBSD over Linux primarily because I felt it was better supported with >a central core team and such. Is this not a true statement? I don't know who recommended Buslogic cards a week ago, but I can say that I've personally had bad experiance with Buslogic tech support for the last several months. I've made multiple calls to them, spent more than $50 in long distance waiting on hold, and when I finally gave up waiting on hold and left messages instead, my calls were never returned. I've never been treated this way by any other company, and this bad experiance really leaves a sour taste. There is a difference between what is the best supported card in FreeBSD and what is the best supported card by the vendor. FreeBSD has good Buslogic support - I use a bt-946C myself with little trouble. Buslogic, however, has lousy support for their products. If you happen to have a card with broken firmware, you're screwed. If you can't even get your damn drives to probe correctly in the BIOS, then you don't have a snowball's chance of getting the thing booted. In my case, I was trying to get help from Buslogic on a problem where the card's BIOS would sometimes hang just before starting the device probe on the SCSI bus - it made rebooting wcarchive extremely risky; more than 2/3rds of the time the machine would hang rather than boot. It wasn't a FreeBSD problem because it would happen even if the machine was freshly powered on - and it never got far enough to read any blocks off the disk. The best working SCSI driver in FreeBSD at the moment is the one for the Adaptec 2x40 controllers. The card doesn't have any BIOS hang problems, and Justin Gibbs has been very good about fixing all the bugs. 2940's is what I ended up using in wcarchive - 3 of them. -DG From owner-freebsd-bugs Sun May 21 21:27:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA09850 for bugs-outgoing; Sun, 21 May 1995 21:27: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 VAA09843 ; Sun, 21 May 1995 21:27:52 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Charles Henrich cc: freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 95 23:15:40 EDT." <199505220315.UAA07572@freefall.cdrom.com> Date: Sun, 21 May 1995 21:27:52 -0700 Message-ID: <9842.801116872@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > Wait a minute, your telling me that because the support for the buslogic card s > are broken (when not two weeks ago it was the card suggested as the best and > most reliable by many on the freebsd-hackers lists) that we should buy No, he's saying because Buslogic's support for _their own cards_ is broken. Their tech support is making a large sucking sound, and the latest firmware revisions appear to have broken multiple things. If someone can demonstrate a software problem, of course we'll do our best to fix it. Jordan From owner-freebsd-bugs Sun May 21 21:29:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA10052 for bugs-outgoing; Sun, 21 May 1995 21:29:41 -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 VAA10042 for ; Sun, 21 May 1995 21:29:37 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id VAA04277; Sun, 21 May 1995 21:29:14 -0700 From: "Rodney W. Grimes" Message-Id: <199505220429.VAA04277@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Sun, 21 May 1995 21:29:14 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199505220315.UAA07572@freefall.cdrom.com> from "Charles Henrich" at May 21, 95 11:15:40 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: 2700 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > I will not be pursuaded to change my stance on Bus Logic due to past > record. There current record is horrible, and that is enough for me > to pursuade people to seek alternatives, realize I sell these products, > ^^^^^^^^^^^^^^^^^ > > Wait a minute, your telling me that because the support for the buslogic cards > are broken (when not two weeks ago it was the card suggested as the best and > most reliable by many on the freebsd-hackers lists) that we should buy > different cards instead of fixing the broken drivers? No, that is not what I said. Bus Logic cards are *broken* with respect to there bt946 working with PCI motherboards. It has nothing to do with booting FreeBSD, it has to do with the fact that I can't take a brand new BT946 and plug it in the 5 different PCI motherboards I have and expect it to work. Rather than be getting past POST, or even installing DOS on the box. Bus Logic has been pointing fingers at MB manufactures the whole time saying that motherboard manufactures don't under stand how the PCI scsi BIOS is to work. Well, gee, it seems I can take my 2940 and plug it in all the boards and it works, I can take my NCR 810 and plug it in and it all works (this is with an NCR card that has it's own BIOS on it and I disable the MB NCR support). But when I try that Bt946 card, it don't. I've been through 4 revs of PROMS for the cards, and I have to very carefull match the PROMS to the MB to get it to work. If you want to read another person's horry story about Bus Logic and PCI MB, I can dig up the pointer to Paul Vixies home page, he has been here just like me. (Only he has to keep using the Bus Logic as BSDI does not (yet) have support for any other PCI disk controller.) > If this is how broken > drivers are handled (okay, dont use THAT one) FreeBSD has some serious > problems... Tell me Im misunderstanding something here, afterall I know I > chose FreeBSD over Linux primarily because I felt it was better supported with > a central core team and such. Is this not a true statement? I can't debug the bt742.c driver if I can't get there bloody cards to play with motherboards. I can't get there bloody cards to play with my new series of MB, because I can't get tech support from them to get the new proms to try and make it work with yet another set of boards. Just to make sure I am clear here, I can't install DOS on any of my PCI systems using a Bus Logic BT946C except 1 because the card at revision 4.84/4.21 will not talk to the motherboard. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Mon May 22 01:31:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA16536 for bugs-outgoing; Mon, 22 May 1995 01:31:06 -0700 Received: from relay3.UU.NET (relay3.UU.NET [192.48.96.8]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA16523 ; Mon, 22 May 1995 01:31:00 -0700 Received: from cygnus.com by relay3.UU.NET with ESMTP id QQyquk12780; Mon, 22 May 1995 04:30:56 -0400 Received: from localhost.cygnus.com (rtl.cygnus.com [140.174.1.2]) by cygnus.com (8.6.12/8.6.9) with ESMTP id BAA12252; Mon, 22 May 1995 01:30:52 -0700 Message-Id: <199505220830.BAA12252@cygnus.com> To: "Jordan K. Hubbard" cc: Peter Dufault , sef@kithrup.com (Sean Eric Fagan), bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Sun, 21 May 1995 13:39:51 PDT." <27949.801088791@freefall.cdrom.com> Date: Mon, 22 May 1995 01:30:52 -0700 From: Torbjorn Granlund Sender: bugs-owner@FreeBSD.org Precedence: bulk Now my machine begins to work. And I didn't cheat and downgraded to Linux... :-) I swapped my Buslogic 964C for an Adaptec 2940, and downloaded the latest snapshot. I got one panic during install (the to me all too familiar "page fault while in kernel mode") but since that the machine has stayed up. SCSI transfers now go at 10 MB/s according to the driver. However, I only get about 5.4 MB/s in practice for large file transfers. The disk documentation claims that the drive can do 9.7 MB/s on the outermost tracks. It is too early to say that the system now works reliably. But it certainly crashes less than it used to, with a plain 2.0 kernel. I wish to thank you all for your timely help! I would probably have had less problems had I not bought the disk Jordan warned us for, the motherboard Rodney says is garbage, and the SCSI controller you warn people from using... Hey, it could have been worse, I could have had a broken frame buffer! (About the Buslogic card: I briefly ran Linux on the system today, and it kept warning about "buslogic: interrupt recieved but no mail sent". So the problems with that board are certainly not FreeBSD-specific.) Torbjörn From owner-freebsd-bugs Mon May 22 02:06:26 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA17947 for bugs-outgoing; Mon, 22 May 1995 02:06:26 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA17932 ; Mon, 22 May 1995 02:06:23 -0700 Date: Mon, 22 May 1995 02:06:23 -0700 From: David Greenman Message-Id: <199505220906.CAA17932@freefall.cdrom.com> To: fenner@parc.xerox.com, davidg, freebsd-bugs Subject: Changed information for PR kern/429 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: de driver BPF/Multicast logic is broken State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Mon May 22 02:05:24 PDT 1995 State-Changed-Why: Fixed in rev 1.25 by applying Bill's patch. From owner-freebsd-bugs Mon May 22 02:56:44 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA19681 for bugs-outgoing; Mon, 22 May 1995 02:56:44 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA19666 ; Mon, 22 May 1995 02:56:43 -0700 Date: Mon, 22 May 1995 02:56:43 -0700 From: David Greenman Message-Id: <199505220956.CAA19666@freefall.cdrom.com> To: ylo@fx7.cs.hut.fi, davidg, freebsd-bugs Subject: Changed information for PR i386/395 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: All spl functions implemented incorrectly in both FreeBSD and NetBSD State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Mon May 22 02:54:14 PDT 1995 State-Changed-Why: Bruce says that gcc's behavior for inlined functions isn't any different than it is for real functions WRT caching of variables or intermediates...and an analysis of the generated code seems to confirm this. It appears to be a non-problem with the current gcc. From owner-freebsd-bugs Mon May 22 04:32:45 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA22406 for bugs-outgoing; Mon, 22 May 1995 04:32:45 -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 EAA22400 ; Mon, 22 May 1995 04:32:38 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA26415 (5.65c8/HUTCS-S 1.4); Mon, 22 May 1995 14:32:09 +0300 Received: (ylo@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id OAA18301; Mon, 22 May 1995 14:32:10 +0300 Date: Mon, 22 May 1995 14:32:10 +0300 Message-Id: <199505221132.OAA18301@shadows.cs.hut.fi> From: Tatu Ylonen To: davidg@freefall.cdrom.com Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505220956.CAA19666@freefall.cdrom.com> (davidg@freefall.cdrom.com) Subject: Re: Changed information for PR i386/395 Organization: Helsinki University of Technology, Finland Sender: bugs-owner@FreeBSD.org Precedence: bulk > Bruce says that gcc's behavior for inlined functions isn't any > different than it is for real functions WRT caching of variables > or intermediates...and an analysis of the generated code seems > to confirm this. It appears to be a non-problem with the current > gcc. Well, code like ... some code using variable/expression foo ... x = spl*(); ... more code using variable/expression foo ... does not recompute foo if spl* is an inline function, and does recompute it if it is not (because then the function might have unknown side-effects changing foo). While I am not sure if spl functions are really used in a way that this would cause problems, I think it would be much safer to eliminate this possibility of erroneus (or at least very unexpected) code. The problem does not appear to be as severe with current compilers and standardized semantics as I thought, but in my opinion there still is a problem. There is a simple way to play safe; I wouldn't consider the current code that safe. Tatu Ylonen From owner-freebsd-bugs Mon May 22 05:57:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA23512 for bugs-outgoing; Mon, 22 May 1995 05:57:56 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA23506 for ; Mon, 22 May 1995 05:57:54 -0700 Message-Id: <199505221257.FAA23506@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA19738; Mon, 22 May 1995 08:57:30 -0400 From: Charles Henrich Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 22 May 1995 08:57:30 -0400 (EDT) Cc: henrich@crh.cl.msu.edu, freebsd-bugs@FreeBSD.org In-Reply-To: <199505220429.VAA04277@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 21, 95 09:29:14 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 773 Sender: bugs-owner@FreeBSD.org Precedence: bulk > No, that is not what I said. Bus Logic cards are *broken* with respect to > there bt946 working with PCI motherboards. It has nothing to do with > booting FreeBSD, it has to do with the fact that I can't take a brand > new BT946 and plug it in the 5 different PCI motherboards I have and > expect it to work. Rather than be getting past POST, or even installing > DOS on the box. Okay, this thread started with software problems, so I thought your reply was also related to software problems (especially in light of my recent tape bug report). I too have a BusLogic 946C that will not, no matter what, work in a PCI system here. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Mon May 22 06:33:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA24213 for bugs-outgoing; Mon, 22 May 1995 06:33: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 GAA24204 ; Mon, 22 May 1995 06:32:57 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA07692; Mon, 22 May 1995 23:30:54 +1000 Date: Mon, 22 May 1995 23:30:54 +1000 From: Bruce Evans Message-Id: <199505221330.XAA07692@godzilla.zeta.org.au> To: davidg@freefall.cdrom.com, ylo@cs.hut.fi Subject: Re: Changed information for PR i386/395 Cc: freebsd-bugs@freefall.cdrom.com Sender: bugs-owner@FreeBSD.org Precedence: bulk >> Bruce says that gcc's behavior for inlined functions isn't any >> different than it is for real functions WRT caching of variables >> or intermediates...and an analysis of the generated code seems >> to confirm this. It appears to be a non-problem with the current >> gcc. >Well, code like > ... some code using variable/expression foo ... > x = spl*(); > ... more code using variable/expression foo ... >does not recompute foo if spl* is an inline function, and does recompute >it if it is not (because then the function might have unknown >side-effects changing foo). >While I am not sure if spl functions are really used in a way that >this would cause problems, I think it would be much safer to eliminate I added __asm __volatile("" : : : "memory") to spl*. This is supposed to say that spl* clobber memory, so that all variable/expressions involving memory get re-evaluated. I examined all the resulting code changes for my kernel (but not for the LINT kernel). There were no significant changes. It's not hard to explain why there is no problem. For there to be a problem: 1) the variable/expression foo must be incorrectly declared as non-volatile. This error (?) is very common, but it may not actually be an error, because if variables are only examined and changed inside appropriate spl's, then they are sort of nonvolatile. 2) the variable/expression foo must be evaluated before the spl*. This should almost never be done. Code such as (if buf->count == 0) goto done might be safe if it is known that buf->count >= 0 and that interrupt handlers only decrease it and that it is loaded atomically, but in general you can't base decisions based on the values of volatile variables. A minor change to your example shows a possible problem: ... some code using variable/expression foo ... splx(x); ... more code using variable/expression foo ... Here it would be reasonable to access foo before the spl. There is currently no problem because splx() sometimes calls splz() and gcc doesn't optimize for the case it isn't called: cpl = ipl; if (ipending & ~ipl) splz(); /* * gcc always reloads everything here. There would be a problem i * it generated: * { splz(); reload_everything(); } * } else { dont_reload_anything(); } */ This could be fixed by putting the memory-clobber asm after the if statement. Bruce From owner-freebsd-bugs Mon May 22 06:45:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA24428 for bugs-outgoing; Mon, 22 May 1995 06:45:39 -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 GAA24421 ; Mon, 22 May 1995 06:45:38 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Torbjorn Granlund cc: Peter Dufault , sef@kithrup.com (Sean Eric Fagan), bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Mon, 22 May 95 01:30:52 PDT." <199505220830.BAA12252@cygnus.com> Date: Mon, 22 May 1995 06:45:36 -0700 Message-ID: <24419.801150336@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: bugs-owner@FreeBSD.org Precedence: bulk > I swapped my Buslogic 964C for an Adaptec 2940, and downloaded the latest > snapshot. I got one panic during install (the to me all too familiar "page > fault while in kernel mode") but since that the machine has stayed up. Great. We've fixed a lot of problems with the 2940 driver, so I certainly hope that you can grab a copy of of -current and `make world' from it before you go! If not, I'll be happy to send you a 2.0.5 CDROM in Sweden. > I wish to thank you all for your timely help! I would probably have had less > problems had I not bought the disk Jordan warned us for, the motherboard > Rodney says is garbage, and the SCSI controller you warn people from using... > Hey, it could have been worse, I could have had a broken frame buffer! :-) I'm just glad this all ended well! Jordan From owner-freebsd-bugs Mon May 22 10:49:59 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA29966 for bugs-outgoing; Mon, 22 May 1995 10:49:59 -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 KAA29960 for ; Mon, 22 May 1995 10:49:57 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA14812; Mon, 22 May 95 11:43:14 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505221743.AA14812@cs.weber.edu> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 22 May 95 11:43:13 MDT Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199505220315.UAA07572@freefall.cdrom.com> from "Charles Henrich" at May 21, 95 11:15:40 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk Rod> I will not be pursuaded to change my stance on Bus Logic due to past Rod> record. There current record is horrible, and that is enough for me Rod> to pursuade people to seek alternatives, realize I sell these products, > Wait a minute, your telling me that because the support for the buslogic cards > are broken (when not two weeks ago it was the card suggested as the best and > most reliable by many on the freebsd-hackers lists) that we should buy > different cards instead of fixing the broken drivers? If this is how broken > drivers are handled (okay, dont use THAT one) FreeBSD has some serious > problems... Tell me Im misunderstanding something here, afterall I know I > chose FreeBSD over Linux primarily because I felt it was better supported with > a central core team and such. Is this not a true statement? Please provide some mechanism to indicate quoted material. I barely recognized the quoted text as coming from Rod. The problem is *not* the drivers. Let me explain this. A computer is like a car. We have a left front quarter panel from a 67 Mustang (the driver), only Buslogic has this year manufactured about 10 model years of cars, and not suprisingly, the panel doesn't fit all of them. We need about 5 panels. Basically, the Buslogic people have made many small design changes without an attempt at maintaining anything other than BIOS compatability between the boards. To correctly support the cards, the maintainer of the Buslogic driver would need one of each card delta to test with, and documentation of the card changes so that a diff can be done to provide a minimal set of replaceable components to cram these 5 drivers into a single driver. Needless to say, the people willing to take this work on have been refused the necessary information by denial-of-service from the support department -- the second thing that needs to change at that company is proper categorization of support requests. The first thing, of course, is that they need to apply responsible release engineering practices both to their board and ROM designs. In general, that means an 800 pound Gorilla with the ability to say "that doesn't ship". Unlikely for a company with less than two assembly lines, and I'm currently too busy to take the job for the next several months. Perhaps they can hire a consultant, since it's a process problem, not a personel problem, and in typical Harvard fashion, they are probably following Jesus Monroy's suggestion and hanging the engineers. Some of their "left front quarter panels" in fact have no mounting holes in them whatsoever: the PCI controllers with firmware versions that won't talk to Plato PCI motherboards (apparently in violation of the PCI 2.0 specification). Potentially they fail on other PCI boards as well, but sice they are know flakey, people who have a lot of hardware that could test this typically wouldn't buy one, especially if the expected outcome was that the board would be totally inoperable. Now you have several choices as a Buslogic purchaser: 1) Write your own driver; I'm sure the changes will be rolled back in, and there will be 40% coverage instead of the 20% you are complaining about. 2) Replace your firmware. On some versions of the board firmware, the board will remain inoperative because of failure of the board/firmware combination to meet the PCI 2.0 specification. The only alternative in these cases is to bring the firmware into compliance or replace the board with a compliant one, if it's a board problem. 3) Use a known good board/firmware combination. The "good" in this context refers both to the standards compliance of the card and to the driver availability. 4) Port VM86() from NetBSD and write a VM86() based disk driver. This will only cover the boards which are in spec, meaning 40% of the boards (a roughy guess) will probably continue to fail to operate. On the minus side, performance will be crap because DOS performance is crap. On the plus side, if it works with DOS, it'll work with BSD. This option is tantamount to following the suggestion "run DOS". 5) Return your card to the dealer for a card from a different manufacturer. Of these, option 5 has the best change of guaranteeing 100% success in your attempt to use the products. Currently, you have also purchased a Quantum Grand Prix drive, which are known to have the same type of QC problems as Buslogic. For BSD, that means your choice is limited to an AHA2940 card for PCI, unless you want to wait for the NCR 810/815/825 driver to be modified to work around the problems in the Grand Prix. Unfortunately, since it is a known flakey drive, the people maintaining the driver, being more familiar with the stability of SCSI drives, didn't choose to buy one. At this point, they would need a "loaner" (they are in Germany) to fix the problem (assuming they are interested). I would think the "path of least hassle" is to trade the Buslogic in for an Adaptec, which despite their developer support practices have had a driver written for them. Complaining to people who give away software about it not working with hardware you have and they don't (which puts you in a better position to track down the problem than they are) is unlikely to do nothing but get you arguments and suggestions that you fix the problem yourself. Regards, 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 May 22 11:09:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00983 for bugs-outgoing; Mon, 22 May 1995 11:09:25 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA00977 for ; Mon, 22 May 1995 11:09:23 -0700 Message-Id: <199505221809.LAA00977@freefall.cdrom.com> Received: by crh.cl.msu.edu (1.38.193.4/16.2) id AA03950; Mon, 22 May 1995 14:09:17 -0400 From: Charles Henrich Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 22 May 1995 14:09:17 -0400 (EDT) Cc: henrich@crh.cl.msu.edu, freebsd-bugs@FreeBSD.org In-Reply-To: <9505221743.AA14812@cs.weber.edu> from "Terry Lambert" at May 22, 95 11:43:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 792 Sender: bugs-owner@FreeBSD.org Precedence: bulk > Please provide some mechanism to indicate quoted material. I barely > recognized the quoted text as coming from Rod. I did, it was the standard practice if > the quoted materials. > The problem is *not* the drivers. I understand that in the current context that it isnt the drivers, however the thread was started with a system panic'ing and such, not just system hangs. I do have software problems with the drivers, if you write to a tape drive while using the driver, it will randomly write bits all over all drives, thats bad! > Currently, you have also purchased a Quantum Grand Prix drive, which Wrong "you", I have an EISA buslogic system. -Crh Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/ From owner-freebsd-bugs Mon May 22 11:19:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01229 for bugs-outgoing; Mon, 22 May 1995 11:19:33 -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 LAA01223 for ; Mon, 22 May 1995 11:19:29 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA16469; Mon, 22 May 95 12:12:41 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505221812.AA16469@cs.weber.edu> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Mon, 22 May 95 12:12:40 MDT Cc: henrich@crh.cl.msu.edu, freebsd-bugs@FreeBSD.org In-Reply-To: <9505221802.AA16354@cs.weber.edu> from "Charles Henrich" at May 22, 95 02:09:17 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > Please provide some mechanism to indicate quoted material. I barely > > recognized the quoted text as coming from Rod. > > I did, it was the standard practice if > the quoted materials. Here is the entire message as I received it; the quoting ']' is mine: ]Return-Path: ]Date: Sun, 21 May 1995 23:15:40 -0400 ]To: freebsd-bugs@FreeBSD.org ]Subject: MAJOR problem with FreeBSD-2.0-RELEASE ]X-Newsreader: NN version 6.5.0 #10 (NOV) ]Sender: bugs-owner@FreeBSD.org ]Precedence: bulk ] ]I will not be pursuaded to change my stance on Bus Logic due to past ]record. There current record is horrible, and that is enough for me ]to pursuade people to seek alternatives, realize I sell these products, ] ^^^^^^^^^^^^^^^^^ ] ]Wait a minute, your telling me that because the support for the buslogic cards ]are broken (when not two weeks ago it was the card suggested as the best and ]most reliable by many on the freebsd-hackers lists) that we should buy ]different cards instead of fixing the broken drivers? If this is how broken ]drivers are handled (okay, dont use THAT one) FreeBSD has some serious ]problems... Tell me Im misunderstanding something here, afterall I know I ]chose FreeBSD over Linux primarily because I felt it was better supported with ]a central core team and such. Is this not a true statement? ] ]-Crh ]-- ] ] Charles Henrich Michigan State University henrich@crh.cl.msu.edu ] ] http://rs560.msu.edu/~henrich/ Sorry, but having had wierd material misattributed to me (the worst case was part of a respose by someone to a Jesus Monry posting), I get a bit picky. 8-(. > I understand that in the current context that it isnt the drivers, however the > thread was started with a system panic'ing and such, not just system hangs. I > do have software problems with the drivers, if you write to a tape drive while > using the driver, it will randomly write bits all over all drives, thats bad! > > > Currently, you have also purchased a Quantum Grand Prix drive, which > > Wrong "you", I have an EISA buslogic system. Sorry about that; the problem here was it was a reply to Rod's post to the other "you", and I (incorrectly) assumed it was the same thread by virtue of it being the same subject. Please note the intentional public reply to clear up any misunderstanding. 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 May 22 16:24:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA00836 for bugs-outgoing; Mon, 22 May 1995 16:24:39 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA03071 ; Mon, 22 May 1995 12:30:01 -0700 Date: Mon, 22 May 1995 12:30:01 -0700 Message-Id: <199505221930.MAA03071@freefall.cdrom.com> From: "Garrett A. Wollman" Reply-To: "Garrett A. Wollman" To: freebsd-bugs Subject: kern/434: umapfs panics when mounting ufs over itself In-Reply-To: Your message of Mon, 22 May 1995 15:21:41 -0400 <199505221921.PAA00426@khavrinen.lcs.mit.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 434 >Category: kern >Synopsis: umapfs panics when mounting ufs over itself >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 May 22 12:30:00 1995 >Originator: Garrett A. Wollman >Organization: MIT Laboratory for Computer Science >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD 2.0-BUILT-19950512 #395: Fri May 12 14:53:28 EDT 1995 >Description: 1) Fix bug in mount_umap that will be committed after freeze is lifted. 2) mount_umap -u /tmp/uidfile -g /tmp/gidfile /tmp /tmp This ought to insert a `umap' layer into the existing UFS structure under /tmp. Instead, I get a `panic: ufs_ihashget: recursive lock not expected -- pid %d'. Unfirtunately, I didn't save the core dump, so I can't provide a traceback. /tmp is on the root filesystem on my machine. >How-To-Repeat: as above >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 01:20:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA16963 for bugs-outgoing; Tue, 23 May 1995 01:20:08 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA16953 ; Tue, 23 May 1995 01:20:05 -0700 Date: Tue, 23 May 1995 01:20:05 -0700 Message-Id: <199505230820.BAA16953@freefall.cdrom.com> From: Heikki Suonsivu Reply-To: Heikki Suonsivu To: freebsd-bugs Subject: kern/435: mb_map full, network starts jumping off and on, finally stays down In-Reply-To: Your message of Tue, 23 May 1995 11:17:10 +0300 <199505230817.LAA14469@katiska.clinet.fi> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 435 >Category: kern >Synopsis: mb_map full, network starts jumping off and on, finally stays down >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 23 01:20:04 1995 >Originator: Heikki Suonsivu >Organization: Helsinki University of Technology, Finland >Release: FreeBSD 2.0-BUILT-19950507 i386 >Environment: P90 as news server plus various other jobs. FreeBSD 2.0-BUILT-19950519 #0: Fri May 19 18:19:14 EET DST 1995 hsu@katiska.clinet.fi:/usr/src/sys/compile/CLINETSERVER CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping=4 Features=0x1bf real memory = 33161216 (8096 pages) avail memory = 30777344 (7514 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:cd:b9:a3, type WD8013EPC (16 bit) bpf: ed0 attached lpt0 not found at 0x3bc 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 sio3 not found at 0x2e8 pca0 on isa pca0: PC speaker audio driver bt0 not found at 0x330 aha0 not found at 0x330 wdc0 not found at 0x1f0 wdc1 not found at 0x170 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in mcd0: timeout getting status mcd0 not found at 0x300 le0: no board found at 0x300 le0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface matcd0 not found at 0xffffffff matcd1 not found at 0xffffffff matcd2 not found at 0xffffffff matcd3 not found at 0xffffffff bio_imask c0000040 tty_imask c003003a net_imask c003003a Probing for devices on the pci0 bus: configuration mode 1 allows 32 devices. pci0:0: vendor=0x1039, device=0x406, class=bridge [not supported] pci0:1: vendor=0x1039, device=0x8, class=bridge [not supported] ncr0 rev 2 int a irq 12 on pci0:13 reg20: virtual=0xf61ddf00 physical=0xffbdff00 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:0:0): 200ns (5 Mb/sec) offset 8. (ncr0:0:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1003MB (2055035 512 byte sectors) (ncr0:1:0): "SEAGATE ST32550N 0012" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2047MB (4194058 512 byte sectors) (ncr0:3:0): "SEAGATE ST31200N 9348" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1011MB (2072435 512 byte sectors) vga0 rev 0 on pci0:17 pci0: uses 8388864 bytes of memory from ff000000 upto ffbdffff. pci0: uses 256 bytes of I/O space from fc00 upto fcff. changing root device to sd0a bpf: ds0 attached bpf: lo0 attached bpf: ppp0 attached bpf: ppp1 attached bpf: ppp2 attached bpf: ppp3 attached bpf: ppp4 attached bpf: ppp5 attached bpf: ppp6 attached bpf: ppp7 attached bpf: ppp8 attached bpf: ppp9 attached bpf: ppp10 attached bpf: ppp11 attached bpf: ppp12 attached bpf: ppp13 attached bpf: ppp14 attached bpf: ppp15 attached bpf: ppp16 attached bpf: ppp17 attached bpf: ppp18 attached bpf: ppp19 attached bpf: ppp20 attached bpf: ppp21 attached bpf: ppp22 attached bpf: ppp23 attached bpf: ppp24 attached bpf: ppp25 attached bpf: ppp26 attached bpf: ppp27 attached bpf: ppp28 attached bpf: ppp29 attached bpf: ppp30 attached bpf: ppp31 attached bpf: sl0 attached bpf: sl1 attached bpf: sl2 attached bpf: sl3 attached bpf: sl4 attached bpf: sl5 attached bpf: sl6 attached bpf: sl7 attached bpf: sl8 attached bpf: sl9 attached bpf: sl10 attached bpf: sl11 attached bpf: sl12 attached bpf: sl13 attached bpf: sl14 attached bpf: sl15 attached bpf: tun0 attached WARNING: / was not properly dismounted. >Description: Kernel spits out May 23 00:00:32 katiska /kernel: mb_map full And network interface starts dropping packets. Occasionally a packet or two gets through, as sometimes nfs says is alive again, and even a login gets though. A couple of hours later the connections die completely. >How-To-Repeat: Don't know, but suspect high load. >Fix: Don't know, but I assume it is a too small fixed-size table somewhere, and probably a leak somewhere else. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 01:36:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA17537 for bugs-outgoing; Tue, 23 May 1995 01:36:03 -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 BAA17531 for ; Tue, 23 May 1995 01:36:00 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id BAA25300; Tue, 23 May 1995 01:39:00 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id BAA01926; Tue, 23 May 1995 01:36:01 -0700 Message-Id: <199505230836.BAA01926@corbin.Root.COM> To: Heikki Suonsivu cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/435: mb_map full, network starts jumping off and on, finally stays down In-reply-to: Your message of "Tue, 23 May 95 01:20:05 PDT." <199505230820.BAA16953@freefall.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 May 1995 01:36:00 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk > P90 as news server plus various other jobs. ... >May 23 00:00:32 katiska /kernel: mb_map full > >And network interface starts dropping packets. Occasionally a packet >or two gets through, as sometimes nfs says is alive again, and even a >login gets though. A couple of hours later the connections die >completely. How many simultaneous TCP connections does the machine typically have, and how many mbuf clusters do you have configured in the kernel? -DG From owner-freebsd-bugs Tue May 23 07:04:56 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA03746 for bugs-outgoing; Tue, 23 May 1995 07:04:56 -0700 Received: from clinet.fi (root@clinet.fi [193.64.6.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA03737 for ; Tue, 23 May 1995 07:04:43 -0700 Received: from katiska.clinet.fi (root@katiska.clinet.fi [193.64.6.3]) by clinet.fi (8.6.10/8.6.4) with ESMTP id RAA21057; Tue, 23 May 1995 17:04:18 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by katiska.clinet.fi (8.6.11/8.6.4) id RAA03308; Tue, 23 May 1995 17:04:18 +0300 Date: Tue, 23 May 1995 17:04:18 +0300 Message-Id: <199505231404.RAA03308@katiska.clinet.fi> To: davidg@Root.COM Cc: Heikki Suonsivu , freebsd-bugs@freefall.cdrom.com Subject: Re: kern/435: mb_map full, network starts jumping off and on, finally stays down In-Reply-To: <199505230836.BAA01926@corbin.Root.COM> References: <199505230820.BAA16953@freefall.cdrom.com> <199505230836.BAA01926@corbin.Root.COM> Organization: Helsinki University of Technology, Otaniemi, Finland Sender: bugs-owner@FreeBSD.org Precedence: bulk David Greenman writes: > > P90 as news server plus various other jobs. > ... > >May 23 00:00:32 katiska /kernel: mb_map full > > > >And network interface starts dropping packets. Occasionally a packet > >or two gets through, as sometimes nfs says is alive again, and even a > >login gets though. A couple of hours later the connections die > >completely. > > How many simultaneous TCP connections does the machine typically have, and Haven't counted, now it is about 40 but we are not at the peak hours yet. I would guess it stays less 200, probably less than 100 connections. Even less active connections. > how many mbuf clusters do you have configured in the kernel? Haven't changed the number of MBUFs. maxusers is 256. It still is a problem it the system locks up all IO when mbufs run out, it probably should panic if a critical resource isn't available, though I can see that it isn't easy to know when it did run out all of the available space. But it is the difference between short break and driving 10 miles down there to reboot the damn thing. Linux is particularly bad in these things, I have hardly ever seen it panic, it always locks up either IO or itself, although less often than FreeBSD panics :-(. -- 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 Tue May 23 07:20:27 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA04012 for bugs-outgoing; Tue, 23 May 1995 07:20:27 -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 HAA04004 for ; Tue, 23 May 1995 07:20:21 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id HAA25513; Tue, 23 May 1995 07:23:24 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id HAA00246; Tue, 23 May 1995 07:20:27 -0700 Message-Id: <199505231420.HAA00246@corbin.Root.COM> To: Heikki Suonsivu cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/435: mb_map full, network starts jumping off and on, finally stays down In-reply-to: Your message of "Tue, 23 May 95 17:04:18 +0300." <199505231404.RAA03308@katiska.clinet.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 May 1995 07:20:26 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk > >David Greenman writes: > > > P90 as news server plus various other jobs. > > ... > > >May 23 00:00:32 katiska /kernel: mb_map full > > > > > >And network interface starts dropping packets. Occasionally a packet > > >or two gets through, as sometimes nfs says is alive again, and even a > > >login gets though. A couple of hours later the connections die > > >completely. > > > > How many simultaneous TCP connections does the machine typically have, and > >Haven't counted, now it is about 40 but we are not at the peak hours yet. >I would guess it stays less 200, probably less than 100 connections. Even >less active connections. > > > how many mbuf clusters do you have configured in the kernel? > >Haven't changed the number of MBUFs. maxusers is 256. That's the problem. >It still is a problem it the system locks up all IO when mbufs run out, it >probably should panic if a critical resource isn't available, though I can >see that it isn't easy to know when it did run out all of the available >space. But it is the difference between short break and driving 10 miles >down there to reboot the damn thing. Linux is particularly bad in these >things, I have hardly ever seen it panic, it always locks up either IO or >itself, although less often than FreeBSD panics :-(. The system should be more dynamic about things like this. It definately shouldn't gratuitously panic when transient resource problems occur, however. In your case, the limit is so low that TCP connections waiting to run-down will consume all of them and result in a deadlock. Please add: options "NMBCLUSTERS=2048" to your kernel config file and monitor the peak number of in-use mbuf clusters with netstat -m, as in the following: [corbin:davidg] netstat -m 24 mbufs in use: 16 mbufs allocated to data 5 mbufs allocated to packet headers 2 mbufs allocated to protocol control blocks 1 mbufs allocated to socket names and addresses 17/26 mbuf clusters in use 55 Kbytes allocated to network (67% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines The ratio of "x/y mbuf clusters in use" in the above is the current/peak mbuf cluster usage. If the peak hits your kernel configured maximum, then the maximum isn't high enough and you should increase it. Someday this will be based on maxusers...and will be better documented. -DG From owner-freebsd-bugs Tue May 23 09:50:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA07417 for bugs-outgoing; Tue, 23 May 1995 09:50:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA07410 ; Tue, 23 May 1995 09:50:00 -0700 Date: Tue, 23 May 1995 09:50:00 -0700 Message-Id: <199505231650.JAA07410@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: bin/436: "file" doesn't print longs right with %d format In-Reply-To: Your message of Tue, 23 May 1995 09:46:17 PDT <199505231646.JAA01278@fenestro.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 436 >Category: bin >Synopsis: "file" doesn't print longs right with %d format >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 23 09:50:00 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-2.0 SNAP950412 >Description: The "file" command displays only the least significant byte of a "belong" with the /etc/magic entry >16 belong x %d Hz Example: % hexdump -e '"%07.7_ax " 4/4 "%08X " "\n"' foo.snd | head 0000000 646E732E 80000000 00C0EA03 03000000 0000010 44AC0000 02000000 00000000 00000000 0000020 00000000 00000000 00000000 00000000 Note that the big-endian long at offset 16 is 0xac44, or 44100 Hz. % file foo.snd foo.snd: audio data: 16-bit linear PCM, stereo, 68 Hz Note that 0x44 is 68 Hz. >How-To-Repeat: Run "file" on a sound file and note the sampling rate. 44.1Khz comes out as 68Hz 11Khz comes out as 119Hz 8Khz comes out as 64Hz >Fix: Remove "(unsigned char)" cast from mprint() in softmagic.c. This fixes the long printing and doesn't appear to affect byte/char printing. *** ../file/softmagic.c Sat Sep 3 12:16:22 1994 --- softmagic.c Tue May 23 09:38:13 1995 *************** *** 216,222 **** } v = signextend(m, v) & m->mask; ! (void) printf(m->desc, (unsigned char) v); } /* --- 216,222 ---- } v = signextend(m, v) & m->mask; ! (void) printf(m->desc, v); } /* >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 10:10:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA07770 for bugs-outgoing; Tue, 23 May 1995 10:10:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA07763 ; Tue, 23 May 1995 10:10:00 -0700 Date: Tue, 23 May 1995 10:10:00 -0700 Message-Id: <199505231710.KAA07763@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: misc/437: addition for /usr/src/usr.bin/file/Magdir/zyxel In-Reply-To: Your message of Tue, 23 May 1995 10:05:20 PDT <199505231705.KAA01407@fenestro.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 437 >Category: misc >Synopsis: addition for /usr/src/usr.bin/file/Magdir/zyxel >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue May 23 10:10:00 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-2.0 SNAP950412 >Description: ZyXEL has added some new types to their voice file format >How-To-Repeat: >Fix: I also changed spaces to tabs, that's why some of the lines look unchanged *** /usr/src/usr.bin/file/Magdir/zyxel Sat Sep 3 12:16:28 1994 --- zyxel Tue May 23 10:02:05 1995 *************** *** 3,9 **** # ZyXEL U-1496E DATA/FAX/VOICE modems. (This header conforms to a # ZyXEL-defined standard) ! 0 string ZyXEL\002 ZyXEL voice data ! >10 byte 0 - CELP encoding ! >10 byte 1 - ADPCM2 encoding ! >10 byte 2 - ADPCM3 encoding --- 3,12 ---- # ZyXEL U-1496E DATA/FAX/VOICE modems. (This header conforms to a # ZyXEL-defined standard) ! 0 string ZyXEL\002 ZyXEL voice data ! >10 byte 0 - CELP encoding ! >10 byte&0x0B 1 - ADPCM2 encoding ! >10 byte&0x0B 2 - ADPCM3 encoding ! >10 byte&0x0B 3 - ADPCM4 encoding ! >10 byte&0x0B 8 - New ADPCM3 encoding ! >10 byte&0x04 4 with resync >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 15:07:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA18544 for bugs-outgoing; Tue, 23 May 1995 15:07:46 -0700 Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA18534 for ; Tue, 23 May 1995 15:07:29 -0700 Date: Tue, 23 May 1995 22:50:36 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <636@nwpeople.demon.co.uk> To: bde@zeta.org.au Cc: bugs@FreeBSD.org Subject: Re: 2.0-950412-SNAP install problem X-Mailer: PCElm 1.10 Lines: 41 Sender: bugs-owner@FreeBSD.org Precedence: bulk Thanks for your reply. I have a few questions: In message <199505220031.KAA18598@godzilla.zeta.org.au> Bruce Evans writes: > >I have encountered a problem trying to install 2.0-950412-SNAP. > >... > > WD Caviare 540MB IDE disk (1048 cyls) > >... > >The IDE disk (wd0) has DOS and FreeBSD 1.1 slices. The FreeBSD 1.1 > >slice starts below cylinder 1024. BIOS LBA translation is disabled; > >I lied to the BIOS and told it the disk has 1024 cylinders. > > >I am attempting to install FreeBSD 2.0 on the entire SCSI disk (sd0). > >I have reached the point where I can boot from the hard disk (sd0, using > >hd(1,a)/kernel at boot prompt). The kernel boots successfully, and finds > >all expected devices, but the message > > > wd0: can't handle 32 heads from partition table... > > Yes, it can't handle 32 heads. 32 heads are another form of BIOS > translation. For the 950412 SNAP, you need to use a more reasonable > translation (try telling the BIOS that the disk has 16 cylinders, > or the actual number) and remove all stale partitions tables and > labels that depend on the old number. I don't think there is a problem with the BIOS. BIOS translation only happens with >1024 cyls, the BIOS thinks there are 1024. In any case the BIOS is only involved while booting, and both FreeBSD 1.1 and 2.0 boot successfully, and 1.1 can read the DOS filesystem. wd0 has a FreeBSD 1.1 disklabel. Perhaps this could be the problem. Are the 1.1 and 2.0 disklabels compatible? I have resisted relabelling wd0 as I want to be able to continue to use 1.1 until I am happy that 2.0 is solid on my system. iain -- Iain Baird Network People International Tel: +44 (0)1732 743591 From owner-freebsd-bugs Tue May 23 15:30:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA20057 for bugs-outgoing; Tue, 23 May 1995 15:30:58 -0700 Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA20051 for ; Tue, 23 May 1995 15:30:53 -0700 Date: Tue, 23 May 1995 23:27:15 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <639@nwpeople.demon.co.uk> To: bugs@FreeBSD.org Subject: console lockup X-Mailer: PCElm 1.10 Lines: 23 Sender: bugs-owner@FreeBSD.org Precedence: bulk The following problem has occurred several times with 2.0-9504120-SNAP on Gateway 2000 4DX2-66V: FreeBSD boots successfully and presents the login prompt. Typing then has no effect, nor can I use Alt-Fn to switch virtual consoles. I can login to the system using telnet from a remote host. wall(1) has no effect on the console, nor has shutdown(8), although the system seems to shutdown correctly. The problem seems usually to occur immediately after power-on. I'm not too distressed about this, trying again usually sorts it. Hopefully the information will be useful to you. Let me know if you want more details. Thankyou! iain -- Iain Baird Network People International Tel: +44 (0)1732 743591 From owner-freebsd-bugs Tue May 23 15:58:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA20565 for bugs-outgoing; Tue, 23 May 1995 15:58:07 -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 PAA20546 for ; Tue, 23 May 1995 15:57:55 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA31185; Wed, 24 May 1995 08:55:43 +1000 Date: Wed, 24 May 1995 08:55:43 +1000 From: Bruce Evans Message-Id: <199505232255.IAA31185@godzilla.zeta.org.au> To: iain@nwpeople.demon.co.uk Subject: Re: 2.0-950412-SNAP install problem Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> > wd0: can't handle 32 heads from partition table... >> >> Yes, it can't handle 32 heads. 32 heads are another form of BIOS >> translation. For the 950412 SNAP, you need to use a more reasonable >> translation (try telling the BIOS that the disk has 16 cylinders, >> or the actual number) and remove all stale partitions tables and >> labels that depend on the old number. >I don't think there is a problem with the BIOS. BIOS translation only >happens with >1024 cyls, the BIOS thinks there are 1024. In any case >the BIOS is only involved while booting, and both FreeBSD 1.1 and 2.0 >boot successfully, and 1.1 can read the DOS filesystem. >wd0 has a FreeBSD 1.1 disklabel. Perhaps this could be the problem. >Are the 1.1 and 2.0 disklabels compatible? I have resisted relabelling >wd0 as I want to be able to continue to use 1.1 until I am happy that >2.0 is solid on my system. The labels should be compatible. 950412-SNAP should be no different from 2.0 or 1.1.5 in this area. The 950414 version of wd.c is different. It only looks for the number of heads in one place (in the controller parameters) instead of in 3 places (in the controller parameters, in the partition table and in the label), so it has less chance of being confused; OTOH if the controller parameters say that there are more than 16 heads (a value not supported by the controller interface, but required for certain BIOS translation schemes), then the driver won't be able to recover. Bruce From owner-freebsd-bugs Tue May 23 17:09:36 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA22367 for bugs-outgoing; Tue, 23 May 1995 17:09:36 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA22358 for ; Tue, 23 May 1995 17:09:32 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id UAA25314; Tue, 23 May 1995 20:09:25 -0400 From: Peter Dufault Message-Id: <199505240009.UAA25314@hda.com> Subject: Re: console lockup To: iain@nwpeople.demon.co.uk Date: Tue, 23 May 1995 20:09:25 -0400 (EDT) Cc: bugs@FreeBSD.org In-Reply-To: <639@nwpeople.demon.co.uk> from "Iain Baird" at May 23, 95 11:27:15 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1449 Sender: bugs-owner@FreeBSD.org Precedence: bulk Iain Baird writes: > The following problem has occurred several times with 2.0-9504120-SNAP > on Gateway 2000 4DX2-66V: > > FreeBSD boots successfully and presents the login prompt. > Typing then has no effect, nor can I use Alt-Fn to switch virtual > consoles. I can login to the system using telnet from a remote host. > wall(1) has no effect on the console, nor has shutdown(8), although > the system seems to shutdown correctly. > > The problem seems usually to occur immediately after power-on. > > I'm not too distressed about this, trying again usually sorts it. > > Hopefully the information will be useful to you. Let me know if > you want more details. The "Gateway keyboard" bug is back! This went away when we switched over to syscons. I have this motherboard, but I almost never bring my system down and so I don't know about this anymore. When you log in remotely over the network try this: 1. Hit a key on the keyboard; 2. Echo something to the console. If this is the same as the old bug the keyboard will then come to life. There has never been an adequate solution to this problem because (I think) no one really understands it. The usual redress is to read the Van Gilluwe book and then sprinkle delays around in the keyboard probe code. 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 May 23 17:43:51 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA23237 for bugs-outgoing; Tue, 23 May 1995 17:43:51 -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 RAA23224 for ; Tue, 23 May 1995 17:42:57 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA01430; Wed, 24 May 1995 10:42:15 +1000 Date: Wed, 24 May 1995 10:42:15 +1000 From: Bruce Evans Message-Id: <199505240042.KAA01430@godzilla.zeta.org.au> To: dufault@hda.com, iain@nwpeople.demon.co.uk Subject: Re: console lockup Cc: bugs@FreeBSD.org Sender: bugs-owner@FreeBSD.org Precedence: bulk >> The following problem has occurred several times with 2.0-9504120-SNAP >> on Gateway 2000 4DX2-66V: >> >> FreeBSD boots successfully and presents the login prompt. >> Typing then has no effect, nor can I use Alt-Fn to switch virtual >The "Gateway keyboard" bug is back! This went away when we switched over >to syscons. I have this motherboard, but I almost never bring my system >down and so I don't know about this anymore. It probably just migrated to the boot blocks. The keyboard probe in the boot blocks was quite broken between 19950120 and 950414. Bruce From owner-freebsd-bugs Tue May 23 18:10:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA23691 for bugs-outgoing; Tue, 23 May 1995 18:10:01 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA23682 ; Tue, 23 May 1995 18:10:01 -0700 Date: Tue, 23 May 1995 18:10:01 -0700 Message-Id: <199505240110.SAA23682@freefall.cdrom.com> From: Pierre Beyssac Reply-To: Pierre Beyssac To: freebsd-bugs Subject: kern/438: panic: vwakeup: neg numoutput In-Reply-To: Your message of Wed, 24 May 1995 02:55:13 +0200 <199505240055.CAA12412@fasterix.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 438 >Category: kern >Synopsis: panic: vwakeup: neg numoutput >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 May 23 18:10:00 1995 >Originator: Pierre Beyssac >Organization: Pierre Beyssac >Release: FreeBSD 2.0-BUILT-19950522 i386 >Environment: PC 486 with IDE drive, booted via NFS on a FreeBSD-current PC. (i.e., the 'diskless' PC boots without using its IDE drive) It gets its root and swap partitions via NFS. >Description: Panic when trying to disklabel the IDE drive attached on the 'diskless' PC. >How-To-Repeat: # disklabel -w -r /dev/wd0s2 labelname -> console messages fixlabel: invalid magic fixlabel: invalid magic panic: vwakeup: neg numoutput Notes: - I used wd0s2. That's obviously wrong, but I'm not sure that's relevant. - the filesystem containing the inode for /dev/wd0s2 was NFS-mounted - Slice 1 is a DOS partition on that PC. Slice 2 was an extended DOS partition with no previous disklabel, but with its ID changed to become a FreeBSD partition. - the drive was previously completely unlabelled. >Fix: I finally managed to correctly disklabel that disk, after many tries. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 18:50:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA24576 for bugs-outgoing; Tue, 23 May 1995 18:50:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA24569 ; Tue, 23 May 1995 18:50:01 -0700 Date: Tue, 23 May 1995 18:50:01 -0700 Message-Id: <199505240150.SAA24569@freefall.cdrom.com> From: Mike Grupenhoff Reply-To: Mike Grupenhoff To: freebsd-bugs Subject: bin/439: pppd: fprintf had too few arguments (with fix) In-Reply-To: Your message of Tue, 23 May 1995 21:46:36 -0400 <199505240146.VAA01692@snarf.umiacs.umd.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 439 >Category: bin >Synopsis: pppd: fprintf had too few arguments (with fix) >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 May 23 18:50:01 1995 >Originator: Mike Grupenhoff >Organization: >Release: FreeBSD 2.0.0-SNAP950322 i386 >Environment: FreeBSD 2.0.0-SNAP950322 (also in current) >Description: An error message in pppd calls fprintf with too few arguments, usually causing a seg fault. >How-To-Repeat: pppd [...] escape 0x2b [...] >Fix: /usr/src/usr.sbin/pppd/options.c --- options.c.orig Tue May 23 21:40:54 1995 +++ options.c Tue May 23 21:41:21 1995 @@ -1009,7 +1009,7 @@ } p = endp; if (n < 0 || 0x20 <= n && n <= 0x3F || n == 0x5E || n > 0xFF) { - fprintf(stderr, "%s: can't escape character 0x%x\n", n); + fprintf(stderr, "%s: can't escape character 0x%x\n", progname, n); ret = 0; } else xmit_accm[0][n >> 5] |= 1 << (n & 0x1F); >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue May 23 18:57:25 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA24875 for bugs-outgoing; Tue, 23 May 1995 18:57:25 -0700 Received: (from davidg@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA24860 ; Tue, 23 May 1995 18:57:24 -0700 Date: Tue, 23 May 1995 18:57:24 -0700 From: David Greenman Message-Id: <199505240157.SAA24860@freefall.cdrom.com> To: kashmir@umiacs.UMD.EDU, davidg, freebsd-bugs Subject: Changed information for PR bin/439 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: pppd: fprintf had too few arguments (with fix) State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Tue May 23 18:57:00 PDT 1995 State-Changed-Why: The supplied patch was applied. Thanks. From owner-freebsd-bugs Tue May 23 19:55:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA26485 for bugs-outgoing; Tue, 23 May 1995 19:55:58 -0700 Received: (from ache@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA26468 ; Tue, 23 May 1995 19:55:56 -0700 Date: Tue, 23 May 1995 19:55:56 -0700 From: "Andrey A. Chernov" Message-Id: <199505240255.TAA26468@freefall.cdrom.com> To: fenner@parc.xerox.com, ache, freebsd-bugs Subject: Changed information for PR bin/436 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: "file" doesn't print longs right with %d format State-Changed-From-To: open-closed State-Changed-By: ache State-Changed-When: Tue May 23 19:54:56 PDT 1995 State-Changed-Why: Fix applied in softmagic.c v1.2 From owner-freebsd-bugs Tue May 23 23:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA01089 for bugs-outgoing; Tue, 23 May 1995 23:30:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA01082 ; Tue, 23 May 1995 23:30:01 -0700 Date: Tue, 23 May 1995 23:30:01 -0700 Message-Id: <199505240630.XAA01082@freefall.cdrom.com> From: Daniel Ortmann Reply-To: Daniel Ortmann To: freebsd-bugs Subject: i386/440: want vidcontrol option to apply settings to all sysconsoles In-Reply-To: Your message of Wed, 24 May 1995 01:25:45 -0500 <199505240625.BAA01327@localhost.nodak.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 440 >Category: i386 >Synopsis: want vidcontrol option to apply settings to all sysconsoles >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue May 23 23:30:00 1995 >Originator: Daniel Ortmann >Organization: North Dakota State University >Release: FreeBSD 2.0.950418-SNAP i386 >Environment: Kernel and sources rebuilt on: FreeBSD 2.0-BUILT-19950512 (...) #0: Fri May 12 20:42:36 CDT 1995 >Description: If vidcontrol could apply color and video modes to all sysconsoles as well as to just the current console, then /etc/sysconfig could conveniently set those items. E.g. I want to do the following from /etc/sysconfig: vidcontrol brown black vidcontrol VGA_80x50 A related suggestion would be to update /etc/sysconfig to something like the following: # Set foreground and background colors [local addition] (or NO for default) foreground=brown background=black # Set overall video mode [local addition] (or NO for default) # Don't forget to set the terminal type in /etc/ttys to agree with this. videomode=VGA_80x50 /etc/rc.386 might also be updated to use it like this: # foreground and background colors if [ "X${foreground}" != X"NO" -a "X${background}" != X"NO" ]; then echo -n ' colors'; vidcontrol ${foreground} ${background} fi # video mode if [ "X${videomode}" != X"NO" ]; then echo -n ' videomode'; vidcontrol ${videomode} fi >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed May 24 02:14:01 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA05370 for bugs-outgoing; Wed, 24 May 1995 02:14:01 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA05352 for ; Wed, 24 May 1995 02:13:54 -0700 Received: from cygnus.com by relay2.UU.NET with ESMTP id QQyrbw24763; Wed, 24 May 1995 05:13:46 -0400 Received: from localhost.cygnus.com (rtl.cygnus.com [140.174.1.2]) by cygnus.com (8.6.12/8.6.9) with ESMTP id CAA02700; Wed, 24 May 1995 02:13:38 -0700 Message-Id: <199505240913.CAA02700@cygnus.com> To: bugs@xfree86.org, freebsd-bugs@FreeBSD.org cc: tege@cygnus.com Subject: XFree86 3.1.1 and Spider Tarantula 64 v2.0 Date: Wed, 24 May 1995 02:13:37 -0700 From: Torbjorn Granlund Sender: bugs-owner@FreeBSD.org Precedence: bulk Using FreeBSD 2.0.950412-SNAP and the precompiled XFree86 3.1.1, I cannot get a Spider Tarantula 64 PCI card to work. I have set up systems with older versions of the same card, and now the same XF86Config file will not work. My motherboard is a Intel Zappa with the Triton chipset. This board has gotten a poor reputation, but I doubt it can cause the observed effects. (The other systems I have built with older Spider Tarantulas had different motherboards, but ran FreeBSD also.) I noticed that the Spider Tarantula cards I have been using before had version number 1.x, while the card that I am having problems with now, calls itself 2.0. The only modes I have been able to get working are 320x200, and the plain screen mode the system starts up in (which might actually be equivalent to 320x200). When trying other modes with the generic SVGA server (XF86_SVGA) I get a badly distorted picture, with several pictures overlaid. When using XF86_S3, the screen looks much less distorted, but windows are invisible. The only way to know were windows are, is by watching the cursor change when moving the mouse around. Similarly, menus are invisble, but they apparently works. Have you heard of similar problems with this card from other users of XFree86 3.1.1? I am not sure on how to usefully report a problem like this one. I will be glad to provide any information that you might want, or make experiments in order to debug this. Torbjorn From owner-freebsd-bugs Wed May 24 02:40:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA07425 for bugs-outgoing; Wed, 24 May 1995 02:40:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA07412 ; Wed, 24 May 1995 02:40:03 -0700 Date: Wed, 24 May 1995 02:40:03 -0700 Message-Id: <199505240940.CAA07412@freefall.cdrom.com> From: Philippe CHARNIER Reply-To: Philippe CHARNIER To: freebsd-bugs Subject: bin/441: more does not call vi with +linenum when EDITOR=vi In-Reply-To: Your message of Wed, 24 May 1995 11:23:27 +0200 <199505240923.LAA07097@pcdif01.lirmm.fr> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 441 >Category: bin >Synopsis: more does not call vi with +linenum when EDITOR=vi >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 May 24 02:40:01 1995 >Originator: Philippe CHARNIER >Organization: Philippe CHARNIER >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: >Description: The `v' command (more) does not use vi +linenum file request when EDITOR is already set to vi. >How-To-Repeat: >Fix: Index: command.c =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/usr.bin/more/command.c,v retrieving revision 1.3 diff -u -r1.3 command.c --- 1.3 1994/10/09 15:40:03 +++ command.c 1995/05/23 19:26:05 @@ -600,7 +600,8 @@ if (editor == NULL) { editor = getenv("EDITOR"); /* pass the line number to vi */ - if (editor == NULL || *editor == '\0') { + if (editor == NULL || *editor == '\0' || + !strcmp(editor, _PATH_VI) || !strcmp(editor,"vi")) { editor = _PATH_VI; dolinenumber = 1; } >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed May 24 18:20:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01706 for bugs-outgoing; Wed, 24 May 1995 18:20:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA01699 ; Wed, 24 May 1995 18:20:01 -0700 Date: Wed, 24 May 1995 18:20:01 -0700 Message-Id: <199505250120.SAA01699@freefall.cdrom.com> From: Daniel Ortmann Reply-To: Daniel Ortmann To: freebsd-bugs Subject: gnu/442: when invoked from "make' cc not including name lists in some library objects In-Reply-To: Your message of Wed, 24 May 1995 20:17:19 -0500 <199505250117.UAA09582@localhost.nodak.edu> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 442 >Category: gnu >Synopsis: when invoked from "make' cc not including name lists in some library objects >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 24 18:20:00 1995 >Originator: Daniel Ortmann >Organization: North Dakota State University >Release: FreeBSD 2.0.950418-SNAP i386 >Environment: I am running "current", but this problem has been around for quite awhile. >Description: When "make"ing some library object files "cc" apparently goofs up and forgets to include names in the object files. This causes any routine that tries to use that library object to not link because a name is not found. This happens *only* inside of "make", and never when manually compiling that object. >How-To-Repeat: The following libraries/object files have this problem. To locate the problem object files on your system use the following bash code fragment. Following the fragment is a slightly edited summary of the results when run on my system. To repeat the problem, delete the mentioned object file under the appropriate library subdirectory and type "make" in that library subdirectory. You will see an error message when linking, but you can run "nm" explicitly on the resulting library to see if the names are missing. Now delete the offending object file and run cc directly in the obj subdirectory. Go up a level and "make" again. This time the names are in the object file and the library is made correctly. Executables that are linked against that library now find the referenced functions. for i in `find /usr/lib/lib* -type f` do echo $i >&2 nm $i >&- sleep 1 # maybe not needed, but timing you know... done 2>&1 | more /usr/lib/libc.a nm: bt_debug.o: no name list. (Note that this comes from src/lib/libc/db/btree/bt_debug.c) /usr/lib/libc_pic.a nm: bt_debug.so: no name list. /usr/lib/libcurses.a nm: ctrace.o: no name list. /usr/lib/libf2c.a nm: Version.o: no name list. /usr/lib/libforms.a nm: debug.o: no name list. /usr/lib/libg++.a nm: math.o: no name list. /usr/lib/librpcsvc.a nm: yppasswd_xdr.o: no name list. nm: spray_xdr.o: no name list. nm: sm_inter_xdr.o: no name list. nm: rwall_xdr.o: no name list. nm: rstat_xdr.o: no name list. nm: rquota_xdr.o: no name list. nm: rnusers_xdr.o: no name list. nm: rex_xdr.o: no name list. nm: nlm_prot_xdr.o: no name list. nm: nfs_prot_xdr.o: no name list. nm: mount_xdr.o: no name list. nm: klm_prot_xdr.o: no name list. >Fix: Re-compile and re-link the offending object file manually as mentioned above. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu May 25 03:10:07 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA20845 for bugs-outgoing; Thu, 25 May 1995 03:10:07 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA20837 ; Thu, 25 May 1995 03:10:04 -0700 Date: Thu, 25 May 1995 03:10:04 -0700 Message-Id: <199505251010.DAA20837@freefall.cdrom.com> From: David Muir Sharnoff Reply-To: David Muir Sharnoff To: freebsd-bugs Subject: kern/443: 65 sendmails crashes system In-Reply-To: Your message of Wed, 31 May 1995 22:00:06 -0700 <199506010500.WAA00734@idiom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 443 >Category: kern >Synopsis: 65 sendmails crashes system >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu May 25 03:10:01 1995 >Originator: David Muir Sharnoff >Organization: Idiom Consulting >Release: FreeBSD 2.0-RELEASE i386 >Environment: FreeBSD 2.0R on a Pentium 90, 32MB ram, NCR53c810, ST32550Ns >Description: I'm writing a little program to see how fast email can be sent. It kinda stresses the system a bit. I don't mind if my system pauses while it tries to cope, but it shouldn't crash. >How-To-Repeat: Run the following perl5 program on a system that's been configured to handle lots of processes (eg: Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on procfs 4 4 0 100% 47 997 5% /proc Don't forget to change the email address first! I'm not sure what triggered the crash. I was trying to type renice -20 $$ on the console, I had a top running in an xterm, and of course, I had all the usuall things running like innd and xntpd. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # mtt_send # echo x - mtt_send sed 's/^X//' >mtt_send << 'END-of-mtt_send' X#!/usr/local/bin/perl X X# X# Send fixed-size email messages very quickly for througput X# testing purposes. X# X# Each message has the following header: X# Subject: TTM $count $payload $interval $pid $message_number $current_time X# X# David Muir Sharnoff , 5/24/95 X# X X$mail_to = 'testmail'; X$count = 300; # messages X$payload = 200; # bytes in body X$interval = 0.2; # seconds, fractional okay X X$sendmail = '/usr/sbin/sendmail'; X$a_long_time = 2; # seconds for an email to really get there X X# ---------------------------------------------------------- X Xrequire 5.000; X$mail_from = getpwuid($<); X Xdie "no $sendmail" unless -x $sendmail; X X$body = "012345678901234567890123456789012345678\n" x ($payload+40 / 40); X$body = substr($body,1,$payload-1); X$body .= "\n"; X X$now = time; Xopen(SENDMAIL,"|$sendmail -t -oem -i") || die "open $sendmail: $!"; Xprint SENDMAIL < $actual) { X # going too fast X $delay = $ideal - $actual; X print STDERR "waiting for $delay seconds\n"; X select(undef,undef,undef,$delay); X } X X $pid = fork(); X redo unless defined $pid; X next if $pid; X X open(SENDMAIL,"|$sendmail -t -oem -i") || die "open $sendmail: $!"; X X $now = time; X print SENDMAIL < $ideal * 1.10 + 1.0); X X END-of-mtt_send exit >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu May 25 16:30:46 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA21881 for bugs-outgoing; Thu, 25 May 1995 16:30:46 -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 QAA21791 ; Thu, 25 May 1995 16:27:50 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14482(4)>; Thu, 25 May 1995 16:25:14 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49871>; Thu, 25 May 1995 16:25:03 -0700 X-Mailer: exmh version 1.6 4/21/95 To: Mark Tinguely cc: freebsd-questions@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: multicasts In-reply-to: Your message of "Thu, 25 May 95 13:08:05 PDT." <199505252008.PAA28848@plains.nodak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 May 1995 16:24:48 PDT From: Bill Fenner Message-Id: <95May25.162503pdt.49871@crevenia.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <199505252008.PAA28848@plains.nodak.edu> you write: > mail forwarded from freebsd-bugs: Pardon me if I'm being obtuse, but... > The following diff to /usr/src/sys/i386/isa/if_ep.c > > *************** > *** 1336,1341 **** > --- 1337,1363 ---- > ifp->if_mtu = ifr->ifr_mtu; > } > break; > + > + case SIOCADDMULTI: > + case SIOCDELMULTI: > + /* > + * Update our multicast listeners > + */ > + if (cmd == SIOCADDMULTI) { > + ether_addmulti(ifr, &sc->arpcom); > + } else { > + ether_delmulti(ifr, &sc->arpcom); > + } Where, exactly, does "error" get set? > + if (error == ENETRESET) { > + /* It doesn't seem like epreset() actually sets up multicast filters. Of course, I don't know what FIL_GROUP means; maybe it's promiscuous multicast, in which case there is really no need for the ether_*multi calls, just let the ioctl's succeed. Bill From owner-freebsd-bugs Thu May 25 19:10:32 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA29443 for bugs-outgoing; Thu, 25 May 1995 19:10:32 -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 TAA29430 for ; Thu, 25 May 1995 19:10:26 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA14727 (5.65c8/HUTCS-S 1.4 for ); Fri, 26 May 1995 05:10:13 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id FAA12487; Fri, 26 May 1995 05:10:12 +0300 Date: Fri, 26 May 1995 05:10:12 +0300 Message-Id: <199505260210.FAA12487@shadows.cs.hut.fi> To: davidg@Root.COM Cc: freebsd-bugs@freefall.cdrom.com In-Reply-To: David Greenman's message of 22 May 1995 07:34:28 +0300 Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE Organization: Helsinki University of Technology, Otaniemi, Finland Sender: bugs-owner@FreeBSD.org Precedence: bulk I've personally had bad experiance with Buslogic tech support for the last several months. I've made multiple calls to them, spent more than $50 in long distance waiting on hold, and when I finally gave up waiting on hold and left Buslogic may be loosing it as cheap NCR SCSI cards have taken over the market. Thus they might be downsizing and concentrate on something else. where the card's BIOS would sometimes hang just before starting the device probe on the SCSI bus - it made rebooting wcarchive extremely risky; more than 2/3rds of the time the machine would hang rather than boot. It wasn't a I'm currently having serious trouble with disks on one of our machines. This had the same symptoms, the system paniced after SCSI locking up and it wouldn't find the disks after boot. So, I removed BT and replaced it with a NCR controller. Result is that it still gets SCSI lockups, but now it seems to survive the panic as the controller BIOS apparently does reset the bus which BT isn't apparently doing. The is why FreeBSD SCSI driver doesn't survive this? It probably should do a SCSI reset somewhere, but instead it just returns I/O error for all subsequent accesses until the system panics or someone reboots. We have got three disks on the system, 1G seagate hawk, 2G seagate barracuda and IBM 0662, but the troublemaker is still unclear; the errors turn out from any of the disks in the system, not always the same one, but all accesses to the disk which first generated an error fail. Everything around the disks, including cables have been changed several times, so it is either the disks or the software. -- 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 May 25 19:14:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA29732 for bugs-outgoing; Thu, 25 May 1995 19:14:28 -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 TAA29719 for ; Thu, 25 May 1995 19:14:23 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id TAA29374; Thu, 25 May 1995 19:17:23 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA00145; Thu, 25 May 1995 19:14:28 -0700 Message-Id: <199505260214.TAA00145@corbin.Root.COM> To: Heikki Suonsivu cc: freebsd-bugs@freefall.cdrom.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Fri, 26 May 95 05:10:12 +0300." <199505260210.FAA12487@shadows.cs.hut.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 25 May 1995 19:14:27 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >all accesses to the disk which first generated an error fail. Everything >around the disks, including cables have been changed several times, so it >is either the disks or the software. Probably both. One of the drives is hanging the SCSI bus, and FreeBSD doesn't cope with it correctly. I've seen this happen myself... -DG From owner-freebsd-bugs Thu May 25 22:22:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA13295 for bugs-outgoing; Thu, 25 May 1995 22:22:06 -0700 Received: from gimli.Informatik.Uni-Oldenburg.DE (gimli.Informatik.Uni-Oldenburg.DE [134.106.1.10]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA13280 ; Thu, 25 May 1995 22:21:00 -0700 Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1) id ; Fri, 26 May 95 06:52 CES Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13) id ; Fri, 26 May 95 06:41 MES Received: from jelal.hb.north.de by oytix.hb.north.de with bsmtp (Smail3.1.29.0 #1) id m0sEjeV-0004jvM; Thu, 25 May 95 22:37 MET DST Received: by jelal.hb.north.de (SMail-ST 0.95gcc/2.5+) id AA00108; Thu, 25 May 1995 22:12:38 +0200 (CEDT) Subject: Re: Changed information for PR misc/409 To: terry@cs.weber.edu (Terry Lambert) Date: Thu, 25 May 95 22:12:34 CEDT From: Juergen Lock Cc: ache@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <9505201915.AA06222@cs.weber.edu>; from "Terry Lambert" at May 20, 95 1:15 pm X-Mailer: ELM [version 2.3/ST PL11] Message-Id: <9505252012.AA00108@jelal.hb.north.de> Sender: bugs-owner@FreeBSD.org Precedence: bulk Terry Lambert writes: > > Hmm. my xterm termcap doesn't have a ti string... looks like vi > > and bash, and definitely elvis (another vi-alike i happen to have > > source around) all set keypad mode directly using the ks/ke strings. > > They aren't supposed to do this automatically; if they *do* do it > automatically, then they are supposed to have a seperate internal > token for the key, and decode it as if it were the numeric value. This is also what i thought... > > Look at the 'K' capabilities in the termcap database. for digits? (and + - * / enter?) looks like there are none in 2.0R, at least not in the manpage. > > > xterm|vs100|xterm terminal emulator (X window system):\ > > :do=^J:le=^H:ho=\E[H:\ > > :co#80:li#65:cl=\E[H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:\ > > :ce=\E[K:cd=\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:\ > > :md=\E[1m:mr=\E[7m:me=\E[m:\ > > :ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:\ > > :k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:pt:sf=\n:sr=\EM:\ > > :al=\E[L:dl=\E[M:im=\E[4h:ei=\E[4l:mi:dc=\E[P:\ > > :MT:ks=\E[?1h\E=:ke=\E[?1l\E>:xn:\ > > :AL=\E[%dL:DL=\E[%dM:DC=\E[%dP:\ > > :hs:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:\ > > :is=\E\E[m\E[?7h\E[?1;4l:cs=\E[%i%d;%dr:\ > > :rs=\E[r\E<\E[m\E[H\E[2J\E[?7h\E[?1;3;4;6l: > > You notice that the ks/ke have \E[?1h and \E[?1l ? These are actually > the codes for "application" mode, not keypad mode, and their effect > is on the cursor keys, not the keypad keys -- hard to believe that > they are supposed to be there. hmm. this is getting intresting... if i throw them out (ks=\E=:ke=\E>) then vi's and elvis cursor keys don't work anymore! (bash's still do) > > The Sun rs/is (as opposed to the xterm) (you mean this xterm termcap?) > actually contain \E> to forcibly > reset from keypad mode. no change if i add this. > > > so for vi/bash/elvis that means either patch sources or the ks/ke strings? > > The correct place to patch would be vi/bash/elvis, since the ks/ke are > well documented and used. looks like vi and elvis actually use the ks/ke to get the cursor keys right and the non-working keypad is just a side effect of this... :/ > > What you really need is the SCO, Informix, or TERM termcap, all of which > have standard extensions to the 'K' values for handling keypad. looks so. and for the time being i just put this in .exrc: :map! ^[Op 0 :map! ^[Oq 1 :map! ^[Or 2 :map! ^[Os 3 :map! ^[Ot 4 :map! ^[Ou 5 :map! ^[Ov 6 :map! ^[Ow 7 :map! ^[Ox 8 :map! ^[Oy 9 :map! ^[Oj * :map! ^[Ok + :map! ^[Om - :map! ^[On . :map! ^[Oo / :map! ^[OM ^M > > You might also, if you have a Sun, want to look at the codes generated > for the R1->R keys (the Sun keypad) and where they are coded in the > termcap. no Sun where i'm here, but it seems at least elvis wouldn't look for anything like this anyway. > > > or am i still overlooking something... > > It's a vi/bash/elvis bug. The ks/ke is not supposed to be destructive, > it's supposed to allow an application to distinguish the keypad and > non-keypad characters with the same keycaps (in the case of the PC, > when numlock is on). i think there is some confusion somewhere as to what the ks/ke strings really should do... thanx aynway, Juergen (now with a working keypad :) -- J"urgen Lock / nox@jelal.hb.north.de / UUCP: ..!uunet!unido!uniol!jelal!nox ...ohne Gewehr PGP public key fingerprint = 8A 18 58 54 03 7B FC 12 1F 8B 63 C7 19 27 CF DA From owner-freebsd-bugs Fri May 26 01:24:37 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA19577 for bugs-outgoing; Fri, 26 May 1995 01:24:37 -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 BAA19566 for ; Fri, 26 May 1995 01:24:19 -0700 Received: by todonix.ping.de (Smail3.1.28.1 #1) id m0sEufb-0007EUC; Fri, 26 May 95 10:22 MET DST Message-Id: From: jan@todonix.ping.de (Jan Wedekind) Subject: /etc/sysinstall not found: solved! To: bugs@FreeBSD.org Date: Fri, 26 May 1995 10:22:59 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 604 Sender: bugs-owner@FreeBSD.org Precedence: bulk Hello, about a week ago i noticed some problems with an 386-40, that /etc/sysinstall has not been found due to an 'Inflate-error=2' reported while booting. This problem has been caused by the IDE or FDD controller; after replacing it everything works fine now! (Well, i'm still wondering: you could work with it under DOS & Linux without any problems!) Tanks for all comments, 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 May 26 05:23:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA24464 for bugs-outgoing; Fri, 26 May 1995 05:23:05 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA24458 for ; Fri, 26 May 1995 05:23:01 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id IAA05683; Fri, 26 May 1995 08:21:34 -0400 From: Peter Dufault Message-Id: <199505261221.IAA05683@hda.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: davidg@Root.COM Date: Fri, 26 May 1995 08:21:33 -0400 (EDT) Cc: hsu@cs.hut.fi, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505260214.TAA00145@corbin.Root.COM> from "David Greenman" at May 25, 95 07:14:27 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1114 Sender: bugs-owner@FreeBSD.org Precedence: bulk David Greenman writes: > > >all accesses to the disk which first generated an error fail. Everything > >around the disks, including cables have been changed several times, so it > >is either the disks or the software. > > Probably both. One of the drives is hanging the SCSI bus, and FreeBSD > doesn't cope with it correctly. I've seen this happen myself... Properly resetting the SCSI bus, the host adapter, renegotiating sync transfers, waiting for all devices to come ready again and getting their "bus device reset occurred" message, reaping all outstanding I/O transactions, and then retrying those outstanding transactions is an effort that includes modifying all the host adapter drivers (and looking for a common interface to pull up out of them) and so will be a tough job to adequately test. It should also be done in conjunction with better I/O transaction scheduling to cleanly support tag queuing. This is a 2.1 adventure. -- 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 May 26 08:00:04 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27608 for bugs-outgoing; Fri, 26 May 1995 08:00:04 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27599 ; Fri, 26 May 1995 08:00:03 -0700 Date: Fri, 26 May 1995 08:00:03 -0700 Message-Id: <199505261500.IAA27599@freefall.cdrom.com> From: Pierre Beyssac Reply-To: Pierre Beyssac To: freebsd-bugs Subject: kern/445: write() returns EAGAIN during uucico 'i' transfers In-Reply-To: Your message of Fri, 26 May 1995 16:55:44 +0200 <199505261455.QAA00522@fasterix.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 445 >Category: kern >Synopsis: write() returns EAGAIN during uucico 'i' transfers >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 26 08:00:02 1995 >Originator: Pierre Beyssac >Organization: Pierre Beyssac >Release: FreeBSD 2.0-BUILT-19950521 i386 >Environment: Two FreeBSD-current PCs communicating through V32bis modems with uucico, protocol 'i' (bidirectionnal). >Description: uucico gets an error from write(), apparently when trying to write() on a temp file. All of /var is a locally-mounted FFS partition on a SCSI drive. uucico tetard news (1995-05-21 12:27:10.27 8877) ERROR: write: Resource temporarily unavailable >How-To-Repeat: See above. >Fix: Using protocol 'g' _seems_ to cure the problem. Its main result is that the receive and send transfers are done separately. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri May 26 08:00:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27604 for bugs-outgoing; Fri, 26 May 1995 08:00:03 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA27585 ; Fri, 26 May 1995 08:00:02 -0700 Date: Fri, 26 May 1995 08:00:02 -0700 Message-Id: <199505261500.IAA27585@freefall.cdrom.com> From: Pierre Beyssac Reply-To: Pierre Beyssac To: freebsd-bugs Subject: i386/444: problems with sound driver for GUS In-Reply-To: Your message of Fri, 26 May 1995 16:26:16 +0200 <199505261426.QAA00364@fasterix.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 444 >Category: i386 >Synopsis: GUS sound driver does not seem to work. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 26 08:00:01 1995 >Originator: Pierre Beyssac >Organization: Pierre Beyssac >Release: FreeBSD 2.0-BUILT-19950526 i386 >Environment: FreeBSD-current kernel, Gravis Ultrasound Max card. >Description: cat'ting a long (620Kb) .au file to /dev/audio results in the driver looping on (approx) the first 8 seconds. cat is probably stuck in a write() because a kill -KILL does not stop it. cat'ting the same file to /dev/audio1 correctly plays the entire file but there are 'holes' in the sound in at least two places (about 0.1s filled with garbage or repeating previous sounds), around 12s and 26s from the beginning. $ ls -l /dev/audio /dev/audio1 crw-rw-rw- 1 root wheel 30, 4 May 26 14:53 /dev/audio crw-rw-rw- 1 root wheel 30, 20 May 26 16:10 /dev/audio1 Here are the boot messages. Note that "gusmax0" is not found. May 26 16:04:43 fasterix /kernel: gus0 at 0x220 irq 12 drq 1 on isa May 26 16:04:43 fasterix /kernel: gus0: May 26 16:04:43 fasterix /kernel: gusmax0 not found at 0x32c Relevant bits from kernel config : options CONFIGURE_SOUNDCARD options "EXCLUDE_MPU401" options EXCLUDE_SB options EXCLUDE_SBPRO options "EXCLUDE_SB16" options "EXCLUDE_YM3812" options "EXCLUDE_OPL3" options EXCLUDE_PAS options EXCLUDE_MIDI # Controls all sound devices controller snd0 # Gravis UltraSound - for GUS, GUS16, GUSMAX device gus0 at isa? port 0x220 irq 12 drq 1 vector gusintr # Gravis UltraSound MAX - for GUSMAX - requires gus0 device gusmax0 at isa? port 0x32c "file" describes the file as (note the strange sampling rate) : audio data: 8-bit u-law, mono, 64 Hz Note: the same file works fine on a Sun Sparc running SunOS 4. >How-To-Repeat: See above. I can provide the file if necessary. Or you can look for casimir.au with archie :-) >Fix: None known. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri May 26 10:17:33 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA00653 for bugs-outgoing; Fri, 26 May 1995 10:17: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 KAA00646 for ; Fri, 26 May 1995 10:17:20 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA02456; Fri, 26 May 1995 10:16:54 -0700 From: "Rodney W. Grimes" Message-Id: <199505261716.KAA02456@gndrsh.aac.dev.com> Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE To: dufault@hda.com (Peter Dufault) Date: Fri, 26 May 1995 10:16:54 -0700 (PDT) Cc: davidg@Root.COM, hsu@cs.hut.fi, freebsd-bugs@freefall.cdrom.com In-Reply-To: <199505261221.IAA05683@hda.com> from "Peter Dufault" at May 26, 95 08:21:33 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: 1346 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > David Greenman writes: > > > > >all accesses to the disk which first generated an error fail. Everything > > >around the disks, including cables have been changed several times, so it > > >is either the disks or the software. > > > > Probably both. One of the drives is hanging the SCSI bus, and FreeBSD > > doesn't cope with it correctly. I've seen this happen myself... > > Properly resetting the SCSI bus, the host adapter, renegotiating > sync transfers, waiting for all devices to come ready again and > getting their "bus device reset occurred" message, reaping all > outstanding I/O transactions, and then retrying those outstanding > transactions is an effort that includes modifying all the host > adapter drivers (and looking for a common interface to pull up out of > them) and so will be a tough job to adequately test. It should > also be done in conjunction with better I/O transaction scheduling > to cleanly support tag queuing. This is a 2.1 adventure. This is a 2.2 adventure, we are not going to do that kind of massive work in any part of the system until after 2.1 ships. We simply can not afford the risk factor at this time. This is of cource, IMHO. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-bugs Fri May 26 10:42:20 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01401 for bugs-outgoing; Fri, 26 May 1995 10:42:20 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01328 ; Fri, 26 May 1995 10:40:07 -0700 Date: Fri, 26 May 1995 10:40:07 -0700 Message-Id: <199505261740.KAA01328@freefall.cdrom.com> From: Pierre Beyssac Reply-To: Pierre Beyssac To: freebsd-bugs Subject: docs/447: typos in vnconfig(8) man page In-Reply-To: Your message of Fri, 26 May 1995 18:37:06 +0200 <199505261637.SAA02728@fasterix.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 447 >Category: docs >Synopsis: typos in vnconfig.8 >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 May 26 10:40:05 1995 >Originator: Pierre Beyssac >Organization: Pierre Beyssac >Release: FreeBSD 2.0-BUILT-19950526 i386 >Environment: -current. >Description: The vnconfig man page needs updating (change vndXX to vnXX). The -a option description is not very visible. >How-To-Repeat: >Fix: --- vnconfig.8.old Fri May 26 18:31:34 1995 +++ vnconfig.8 Fri May 26 18:32:31 1995 @@ -116,5 +116,7 @@ .El .Pp -The second (-a) form of the command reads a command file and performs the +The second ( +.Fl a +) form of the command reads a command file and performs the specified actions for each device/file pair. With @@ -140,19 +142,19 @@ .Sh EXAMPLES .Pp -.Dl vnconfig /dev/vnd0c /tmp/diskimage +.Dl vnconfig /dev/vn0c /tmp/diskimage .Pp Configures the vnode disk -.Pa vnd0c . +.Pa vn0c . .Pp -.Dl vnconfig -e /dev/vnd0c /var/swapfile swap +.Dl vnconfig -e /dev/vn0c /var/swapfile swap .Pp Configures -.Pa vnd0c +.Pa vn0c and enables swapping on it. .Pp -.Dl vnconfig -d /dev/vnd0c myfilesystem mount=/mnt +.Dl vnconfig -d /dev/vn0c myfilesystem mount=/mnt .Pp Unmounts (disables) -.Pa vnd0c . +.Pa vn0c . .Pp .Dl vnconfig -ae >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri May 26 10:55:53 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01800 for bugs-outgoing; Fri, 26 May 1995 10:55:53 -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 KAA01793 ; Fri, 26 May 1995 10:55:47 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA27266; Fri, 26 May 95 11:33:32 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505261733.AA27266@cs.weber.edu> Subject: Re: Changed information for PR misc/409 To: nox@jelal.hb.north.de (Juergen Lock) Date: Fri, 26 May 95 11:33:31 MDT Cc: ache@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com In-Reply-To: <9505252012.AA00108@jelal.hb.north.de> from "Juergen Lock" at May 25, 95 10:12:34 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > Look at the 'K' capabilities in the termcap database. > > for digits? (and + - * / enter?) looks like there are none in 2.0R, > at least not in the manpage. This is why I suggested the SCO, Informix, and TERM termcaps. They are common extensions. > > You notice that the ks/ke have \E[?1h and \E[?1l ? These are actually > > the codes for "application" mode, not keypad mode, and their effect > > is on the cursor keys, not the keypad keys -- hard to believe that > > they are supposed to be there. > > hmm. this is getting intresting... if i throw them out (ks=\E=:ke=\E>) > then vi's and elvis cursor keys don't work anymore! (bash's still do) That's because the values have been matched to the application mode start/end in the termcap -- nothing mysterious there. > > The correct place to patch would be vi/bash/elvis, since the ks/ke are > > well documented and used. > > looks like vi and elvis actually use the ks/ke to get the cursor > keys right and the non-working keypad is just a side effect of this... :/ Right. I think use of the ks/ke for the application keypad when the keypad is not the only means of getting cursor key sequences is probably in error. TERM uses this (as does Informix and the SCO console) to differentiate between keypad and non keypad keys. TERM needs to do this to emulate going in and out of keypad mode on the emulated VTxxx series terminals; SCO and Informix use it for different reasons. > looks so. and for the time being i just put this in .exrc: > > :map! ^[Op 0 > :map! ^[Oq 1 > :map! ^[Or 2 > :map! ^[Os 3 > :map! ^[Ot 4 > :map! ^[Ou 5 > :map! ^[Ov 6 > :map! ^[Ow 7 > :map! ^[Ox 8 > :map! ^[Oy 9 > :map! ^[Oj * > :map! ^[Ok + > :map! ^[Om - > :map! ^[On . > :map! ^[Oo / > :map! ^[OM ^M Yah. This is a common workaround to the problem, though it's quite terminal specific and the resulting digits are not usable in all modes of control within vi. 8-(. > i think there is some confusion somewhere as to what the ks/ke strings > really should do... Me too. 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 Fri May 26 11:04:03 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01957 for bugs-outgoing; Fri, 26 May 1995 11:04:03 -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 LAA01948 for ; Fri, 26 May 1995 11:04:00 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA00496; Fri, 26 May 1995 11:07:00 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00347; Fri, 26 May 1995 11:04:05 -0700 Message-Id: <199505261804.LAA00347@corbin.Root.COM> To: Peter Dufault cc: hsu@cs.hut.fi, freebsd-bugs@freefall.cdrom.com Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE In-reply-to: Your message of "Fri, 26 May 95 08:21:33 EDT." <199505261221.IAA05683@hda.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 26 May 1995 11:04:02 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk >to cleanly support tag queuing. This is a 2.1 adventure. I hope you meant 2.2... -DG From owner-freebsd-bugs Fri May 26 12:34:06 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01321 for bugs-outgoing; Fri, 26 May 1995 10:40:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01312 ; Fri, 26 May 1995 10:40:04 -0700 Date: Fri, 26 May 1995 10:40:04 -0700 Message-Id: <199505261740.KAA01312@freefall.cdrom.com> From: Pierre Beyssac Reply-To: Pierre Beyssac To: freebsd-bugs Subject: kern/446: Unable to ROOT filesystem: Not owner In-Reply-To: Your message of Fri, 26 May 1995 19:19:31 +0200 <199505261719.TAA00555@fasterix.frmug.fr.net> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 446 >Category: kern >Synopsis: unable to diskless-boot a PC when the server mounts from it >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 May 26 10:40:02 1995 >Originator: Pierre Beyssac >Organization: Pierre Beyssac >Release: FreeBSD 2.0-BUILT-19950526 i386 >Environment: 2 PCs under -current. >Description: One of the PCs ("client") boots from the other ("server") via NFS. "client" NFS-mounts its root from "server" "server" NFS-mounts a disk from "client" If "client" crashes, it is unable to reboot. >How-To-Repeat: - boot server - boot client server$ mount client:/u /u (mounting with options -i and -s doesn't help) - crash client - try to reboot client -> message from netboot.com : Unable to mount ROOT filesystem: Not owner >Fix: Workaround : reboot server. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri May 26 13:30:02 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA00325 for bugs-outgoing; Fri, 26 May 1995 13:30:02 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA00318 ; Fri, 26 May 1995 13:30:02 -0700 Date: Fri, 26 May 1995 13:30:02 -0700 Message-Id: <199505262030.NAA00318@freefall.cdrom.com> From: "Daniel L. Grillo" Reply-To: "Daniel L. Grillo" To: freebsd-bugs Subject: kern/448: ktrace not enabled in default kernel In-Reply-To: Your message of Fri, 26 May 1995 12:13:39 -0700 <199505261913.MAA00464@free.next.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 448 >Category: kern >Synopsis: ktrace not enabled in default kernel >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 May 26 13:30:01 1995 >Originator: Daniel L. Grillo >Organization: NeXT Computer, Inc >Release: FreeBSD 2.1.0-Development i386 >Environment: some random pc :-) >Description: Default kernel does not have ktrace enabled; this is annoying, since tracing is very useful, esp. at install time. For example, my nfs mounts are hanging, and I don't know why. Ktrace would help. >How-To-Repeat: install 950412 snap and ktrace program >Fix: add line "options KTRACE" to default kernel >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri May 26 15:34:00 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA04323 for bugs-outgoing; Fri, 26 May 1995 15:34:00 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA04317 for ; Fri, 26 May 1995 15:33:53 -0700 Received: by sequent.kiae.su id AA07086 (5.65.kiae-2 ); Sat, 27 May 1995 02:31:59 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 27 May 95 02:31:58 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id CAA02172; Sat, 27 May 1995 02:28:50 +0400 To: Juergen Lock , Terry Lambert Cc: freebsd-bugs@freefall.cdrom.com References: <9505261733.AA27266@cs.weber.edu> In-Reply-To: <9505261733.AA27266@cs.weber.edu>; from Terry Lambert at Fri, 26 May 95 11:33:31 MDT Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 27 May 1995 02:28:49 +0400 (MSD) X-Mailer: Mail/@ [v2.37 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Changed information for PR misc/409 Lines: 18 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 707 Sender: bugs-owner@FreeBSD.org Precedence: bulk In message <9505261733.AA27266@cs.weber.edu> Terry Lambert writes: >> > Look at the 'K' capabilities in the termcap database. >> >> for digits? (and + - * / enter?) looks like there are none in 2.0R, >> at least not in the manpage. >This is why I suggested the SCO, Informix, and TERM termcaps. They >are common extensions. We already have extensions too. Look at src/share/termcap/terminfo_extensions.doc -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-bugs Fri May 26 16:20:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA05045 for bugs-outgoing; Fri, 26 May 1995 16:20:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA05038 ; Fri, 26 May 1995 16:20:03 -0700 Date: Fri, 26 May 1995 16:20:03 -0700 Message-Id: <199505262320.QAA05038@freefall.cdrom.com> From: Bill Fenner Reply-To: Bill Fenner To: freebsd-bugs Subject: gnu/449: perl's $] variable is broken In-Reply-To: Your message of Fri, 26 May 1995 16:12:10 PDT <199505262312.QAA04792@fenestro.parc.xerox.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 449 >Category: gnu >Synopsis: perl's $] variable is broken >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 26 16:20:02 1995 >Originator: Bill Fenner >Organization: Xerox PARC >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-2.0 SNAP-950412 >Description: Perl's $] variable returns "4", not "4.036": % perl print $] + 0; 4% On a Sun: crevenia% perl print $] + 0; 4.0359999999999995879crevenia% This also appears to (from reading the code) break the auto running of taintperl and suidperl. >How-To-Repeat: print the perl $] value in a numerical context. >Fix: Believe it or not, the fix is to put the rcsid back. Given the existing rcsid of $RCSfile: perl.c,v $$Revision: 1.2 $$Date: 1994/10/27 23:16:54 $ the "patchlevel" variable gets set to "4/136", which atof() returns 4.0 for. The Revision needs to be 4.0 to get the proper behavior. (see usr/src/gnu/usr.sbin/perl/perl/perl.c, line 128: sprintf(patchlevel,"%3.3s%2.2d", index(rcsid,'4'), PATCHLEVEL); Of course, another fix would simply be to change this to sprintf(patchlevel,"%3.3s%2.2d", "4.0", PATCHLEVEL); since it's pretty ill to use the rcsid in this manner... >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat May 27 01:20:05 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA14332 for bugs-outgoing; Sat, 27 May 1995 01:20:05 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA14325 ; Sat, 27 May 1995 01:20:04 -0700 Date: Sat, 27 May 1995 01:20:04 -0700 Message-Id: <199505270820.BAA14325@freefall.cdrom.com> From: Philippe CHARNIER Reply-To: Philippe CHARNIER To: freebsd-bugs Subject: gnu/450: tar --exclude -c doesn't work In-Reply-To: Your message of Sat, 27 May 1995 10:10:02 +0200 <199505270810.KAA10281@pcdif01.lirmm.fr> Sender: bugs-owner@FreeBSD.org Precedence: bulk >Number: 450 >Category: gnu >Synopsis: tar --exclude -c doesn't work >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat May 27 01:20:02 1995 >Originator: Philippe CHARNIER >Organization: >Release: FreeBSD 2.0.950412-SNAP i386 >Environment: Also in my current machine >Description: tar can't use --exclude feature when creating archives >How-To-Repeat: $ tar --exclude a -cvf t a b a b $ tar --exclude a -tvf t b >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat May 27 04:30:12 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA20799 for bugs-outgoing; Sat, 27 May 1995 04:30:12 -0700 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA20792 for freebsd-bugs; Sat, 27 May 1995 04:30:11 -0700 Date: Sat, 27 May 1995 04:30:11 -0700 From: GNU GNATS Message-Id: <199505271130.EAA20792@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/113 /bin/csh and /usr/local/bin/tcsh choke on my nasty c [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] misc/292 rfc1323 and rfc1644 support can confuse terminal ser [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] pending/307 request for a customer id [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/15] pending/346 request for a customer id [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/04/30] pending/372 request for a customer id [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/09] bin/392 Simultaneous cp and ls of files on dos f/s hangs pro [1995/05/11] i386/394 IP multicast not supported by ep driver [1995/05/11] bin/396 telnetd problems. [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] pending/404 request for a customer id [1995/05/14] kern/405 The gpio driver does not work with the AT-GPIB, only [1995/05/14] pending/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] ports/412 should tracker-4.29 really depend on gmake? [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/14] ports/422 pkg_add doesn't find gmake-3.73.tgz [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] pending/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] pending/433 request for a customer id [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] kern/438 panic: vwakeup: neg numoutput [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/445 write() returns EAGAIN during uucico 'i' transfers [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/26] gnu/449 perl's $] variable is broken [1995/05/27] gnu/450 tar --exclude -c doesn't work /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat May 27 11:52:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA29645 for bugs-outgoing; Sat, 27 May 1995 11:52:13 -0700 Received: (from asami@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA29628 ; Sat, 27 May 1995 11:52:12 -0700 Date: Sat, 27 May 1995 11:52:12 -0700 From: Satoshi Asami Message-Id: <199505271852.LAA29628@freefall.cdrom.com> To: fenner@parc.xerox.com, asami, freebsd-bugs Subject: Changed information for PR ports/412 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: should tracker-4.29 really depend on gmake? State-Changed-From-To: open-analyzed State-Changed-By: asami State-Changed-When: Sat May 27 11:50:48 PDT 1995 State-Changed-Why: Known problem of bsd.port.mk, on Satoshi's fix list for 2.1. From owner-freebsd-bugs Sat May 27 17:43:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA14009 for bugs-outgoing; Sat, 27 May 1995 17:43:28 -0700 Received: (from bde@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA13995 ; Sat, 27 May 1995 17:43:27 -0700 Date: Sat, 27 May 1995 17:43:27 -0700 From: Bruce Evans Message-Id: <199505280043.RAA13995@freefall.cdrom.com> To: uhclem%nemesis@fw.ast.com, bde, freebsd-bugs Subject: Changed information for PR bin/392 Sender: bugs-owner@FreeBSD.org Precedence: bulk Synopsis: Simultaneous cp and ls of files on dos f/s hangs procs [FDIV025] State-Changed-From-To: open-analyzed State-Changed-By: bde State-Changed-When: Sat May 27 17:39:13 PDT 1995 State-Changed-Why: msdosfs locking is broken as designed. Deadlock is possible in msdosfs_lookup because the directory buffer is not released before attempting to lock the denode. Another process may have the denode locked and be waiting for the directory buffer to be unlocked.