From owner-freebsd-bugs Wed Jan 1 00:10:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA17965 for bugs-outgoing; Wed, 1 Jan 1997 00:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA17958; Wed, 1 Jan 1997 00:10:01 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:10:01 -0800 (PST) Resent-Message-Id: <199701010810.AAA17958@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA17911;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:08:50.-0800 (PST) Message-Id: <199701010808.AAA17911@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:08:50 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: docs/2343: help in network config page for PPP connections Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2343 >Category: docs >Synopsis: help in network config page for PPP connections >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:10:00 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: It should mention in the online help (in sysinstall) which things in network setup you have to fill in for a PPP install ie do you have to fill in an IP address if its dynamic etc. Perhaps this is mentioned elsewhere and I just missed it but I think it would be good to have then and there. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:20:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18296 for bugs-outgoing; Wed, 1 Jan 1997 00:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18261; Wed, 1 Jan 1997 00:20:01 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:20:01 -0800 (PST) Resent-Message-Id: <199701010820.AAA18261@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18057;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:12:19.-0800 (PST) Message-Id: <199701010812.AAA18057@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:12:19 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: conf/2344: getting a PPP line for install Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2344 >Category: conf >Synopsis: getting a PPP line for install >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:20:00 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: Would it be possible to include a PPP script in sysinstall that takes a phone number and then just dials it repeatedly unitl itgets a line - the person could then log in manually. Perhaps it should accept several numbers and try them in rotation. I go to a uni with 6 lines for 7.5K students and manually redialling... >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:20:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18321 for bugs-outgoing; Wed, 1 Jan 1997 00:20:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18291; Wed, 1 Jan 1997 00:20:03 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:20:03 -0800 (PST) Resent-Message-Id: <199701010820.AAA18291@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18111;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:15:38.-0800 (PST) Message-Id: <199701010815.AAA18111@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:15:38 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/2345: sysinstall: ppp exited on an error 6 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2345 >Category: bin >Synopsis: sysinstall: ppp exited on an error 6 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:20:02 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: When trying to install 2.2-BETA I would get part way through (from about 17% of bin to part way throughs docs) a PPP install when PPP would exit "on signal 6". I would then have to start the install again. I ended up having to FTP BSD with my mac and use floppies :-( >How-To-Repeat: It happened to me everytime I tried a PPP install >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:20:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18325 for bugs-outgoing; Wed, 1 Jan 1997 00:20:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18317; Wed, 1 Jan 1997 00:20:06 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:20:06 -0800 (PST) Resent-Message-Id: <199701010820.AAA18317@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18200;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:18:11.-0800 (PST) Message-Id: <199701010818.AAA18200@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:18:11 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: misc/2346: sysinstall: /usr/include while telling me I was getting bin Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2346 >Category: misc >Synopsis: sysinstall: /usr/include while telling me I was getting bin >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:20:04 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: /usr/include seems to be fetched as part of bin (ie vty0 says getting bin - vty1 shows /usr/include/*). I wouldn't catagorise /usr/include/* as bin but as this is so minor..... >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18732 for bugs-outgoing; Wed, 1 Jan 1997 00:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18726; Wed, 1 Jan 1997 00:30:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:30:02 -0800 (PST) Resent-Message-Id: <199701010830.AAA18726@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18663;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:29:02.-0800 (PST) Message-Id: <199701010829.AAA18663@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:29:02 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/2347: sysinstall: ppp: recursive call in malloc() Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2347 >Category: bin >Synopsis: sysinstall: ppp: recursive call in malloc() >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:30:01 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: When installing via PPP I got the message on vty2 (the PPP screen anyway): ppp in malloc(): warning: recursive call. I typed show mem to see what was wrong and things froze - modem stopped receiving, ppp didnt respond - I went to vty4 (the emergency holographic shell one) to do a ps and see what was going on - i typed ps and nothing happened. I switched to vty0 and nothing had changed - i could no longer go back to vty4 (it just beeped when i tried). I pressec ^C and was asked if I was sure - the whole machine locked up. I pressed ctrl-alt- delete. On reboot from floppy machine hung at the rootfs is 1440 Kbyte compiled in MFS. Since getting the system installed by floppy PPP still dies the same way after about an hour's "hard use". I have to kill it from another window. If I restart it it just hangs and so I have to reboot the box. >How-To-Repeat: Try getting PPP to transfer a lot of data for an hour or two - It seems to happen when the modem has been flat chat at 28.8 for an hour or so. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:40:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18975 for bugs-outgoing; Wed, 1 Jan 1997 00:40:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18954; Wed, 1 Jan 1997 00:40:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:40:02 -0800 (PST) Resent-Message-Id: <199701010840.AAA18954@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18786;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:32:38.-0800 (PST) Message-Id: <199701010832.AAA18786@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:32:38 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: misc/2348: sysinstall: corrupt file causes restart Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2348 >Category: misc >Synopsis: sysinstall: corrupt file causes restart >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:40:00 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: When installing from floppies if one of the files in corrupt (I guess this is why it happens) it complains that it isnt a real gzip file or something and makes you restart the whole installation. I tend to get a better transfer rate out of my modem than my floppy drive so it can be quite harrowing :-) >How-To-Repeat: Do a floppy install with a corrupt file. >Fix: Perhaps you could make so you just have to replace that file and continue from where you left off. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:40:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18989 for bugs-outgoing; Wed, 1 Jan 1997 00:40:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18969; Wed, 1 Jan 1997 00:40:03 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:40:03 -0800 (PST) Resent-Message-Id: <199701010840.AAA18969@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18831;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:35:07.-0800 (PST) Message-Id: <199701010835.AAA18831@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:35:07 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: bin/2349: sysinstall: If you type anything on vty4 it dies. Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2349 >Category: bin >Synopsis: sysinstall: If you type anything on vty4 it dies. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:40:02 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: Whenever it type anything on the emergency holographic shell in the installer the shell dies - when i switch from that window I cant get back to it. It wasn't a tradgedy for me cause i didnt need to use it but.... >How-To-Repeat: Type a command on vty4 in sysinstall. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:40:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA19005 for bugs-outgoing; Wed, 1 Jan 1997 00:40:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18986; Wed, 1 Jan 1997 00:40:05 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:40:05 -0800 (PST) Resent-Message-Id: <199701010840.AAA18986@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA18873;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:36:54.-0800 (PST) Message-Id: <199701010836.AAA18873@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:36:54 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: conf/2350: sysinstall: Anonymous FTP Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2350 >Category: conf >Synopsis: sysinstall: Anonymous FTP >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:40:04 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: When setting up Anon FTP from sysinstall I told it to use /usr/ftp as the anon ftp directory but it used /var/ftp anyway. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 00:50:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA19338 for bugs-outgoing; Wed, 1 Jan 1997 00:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA19329; Wed, 1 Jan 1997 00:50:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 00:50:02 -0800 (PST) Resent-Message-Id: <199701010850.AAA19329@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, Received:(from nobody@localhost) by.freefall.freebsd.org.id.AAA19015;Wed; (8.8.4/8.8.4);, 1 Jan 1997 00:40:14.-0800 (PST) Message-Id: <199701010840.AAA19015@freefall.freebsd.org> Date: Wed, 1 Jan 1997 00:40:14 -0800 (PST) From: andrew@ugh.net.au To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: kern/2351: panic:timeout table full Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2351 >Category: kern >Synopsis: panic:timeout table full >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 00:50:01 PST 1997 >Last-Modified: >Originator: Andrew Stevenson >Organization: >Release: 2.2-BETA >Environment: FreeBSD sally.ugh.net.au 2.2-BETA_A FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 >Description: After I got my system installed I connected to the net with PPP and had a couple of ftp sessions going (getting the kernel src as it happened). I had also just added a pkg or two when I got the message: panic:timeout table full syncing disks 10 10 10 10 10 giving up - reboot And sure enough it did reboot. >How-To-Repeat: I can't seem to get it to happen again...(thankfully :-) >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 01:18:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20251 for bugs-outgoing; Wed, 1 Jan 1997 01:18:56 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20229; Wed, 1 Jan 1997 01:18:50 -0800 (PST) Date: Wed, 1 Jan 1997 01:18:50 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199701010918.BAA20229@freefall.freebsd.org> To: andrew@ugh.net.au, jkh, freebsd-bugs Subject: Re: docs/2341 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: install.txt contains refs to 2.1 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Wed Jan 1 01:18:36 PST 1997 State-Changed-Why: Thanks! Fixed. From owner-freebsd-bugs Wed Jan 1 01:21:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20429 for bugs-outgoing; Wed, 1 Jan 1997 01:21:40 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20407; Wed, 1 Jan 1997 01:21:28 -0800 (PST) Date: Wed, 1 Jan 1997 01:21:28 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199701010921.BAA20407@freefall.freebsd.org> To: andrew@ugh.net.au, jkh, freebsd-bugs Subject: Re: misc/2346 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: sysinstall: /usr/include while telling me I was getting bin State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Wed Jan 1 01:20:27 PST 1997 State-Changed-Why: This isn't really a bug since /usr/include is, indeed, an intentional part of bin. I know that it might seem unrelated, but so much counts on a reasonable /usr/include that it will have to stay in bin until, at the very least, all compiler tools are put into their own distribtution. From owner-freebsd-bugs Wed Jan 1 01:28:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20810 for bugs-outgoing; Wed, 1 Jan 1997 01:28:57 -0800 (PST) Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20791; Wed, 1 Jan 1997 01:28:52 -0800 (PST) Date: Wed, 1 Jan 1997 01:28:52 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199701010928.BAA20791@freefall.freebsd.org> To: andrew@ugh.net.au, jkh, freebsd-bugs Subject: Re: misc/2348 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: sysinstall: corrupt file causes restart State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Wed Jan 1 01:26:03 PST 1997 State-Changed-Why: I'm afraid that this isn't a bug so much as a pre-requisite of sysinstall - you either have good media or you're hosed, and with the way the tarballs are split into pieces, simply skipping one really isn't an option. If one piece is bad, the whole distribution is effectively toast and there's really not a lot I can do about it. This will all be solved as a side-effect of going to a more robust distribution archive format, so there's not much point in leaving this PR open as it won't be solved by fixing sysinstall in that way (sorry). There's been talking of reviving the automated checksumming, which would at least verify the media before starting. I will look into this. From owner-freebsd-bugs Wed Jan 1 01:30:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20919 for bugs-outgoing; Wed, 1 Jan 1997 01:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA20913; Wed, 1 Jan 1997 01:30:01 -0800 (PST) Date: Wed, 1 Jan 1997 01:30:01 -0800 (PST) Message-Id: <199701010930.BAA20913@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Jordan K. Hubbard" Subject: Re: bin/2349: sysinstall: If you type anything on vty4 it dies. Reply-To: "Jordan K. Hubbard" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/2349; it has been noted by GNATS. From: "Jordan K. Hubbard" To: andrew@ugh.net.au Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/2349: sysinstall: If you type anything on vty4 it dies. Date: Wed, 01 Jan 1997 01:25:23 -0800 > Whenever it type anything on the emergency holographic shell > in the installer the shell dies - when i switch from that window I cant > get back to it. It wasn't a tradgedy for me cause i didnt need to use it > but.... This is a known bug, though I can't say exactly for sure why it's happening. It's a new problem and we're chasing the cause - it could be sysinstall, it could be the console driver, it's hard to say. Thanks for the report. Jordan From owner-freebsd-bugs Wed Jan 1 02:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA22005 for bugs-outgoing; Wed, 1 Jan 1997 02:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA21981; Wed, 1 Jan 1997 02:00:02 -0800 (PST) Date: Wed, 1 Jan 1997 02:00:02 -0800 (PST) Message-Id: <199701011000.CAA21981@freefall.freebsd.org> To: freebsd-bugs Cc: From: Poul-Henning Kamp Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Reply-To: Poul-Henning Kamp Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/2347; it has been noted by GNATS. From: Poul-Henning Kamp To: andrew@ugh.net.au Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Date: Wed, 01 Jan 1997 10:55:42 +0100 In message <199701010829.AAA18663@freefall.freebsd.org>, andrew@ugh.net.au writ >When installing via PPP I got the message on vty2 (the PPP screen anyway): >ppp in malloc(): warning: recursive call. This is actually a pretty devastating thing. It means that a call to malloc(3),free(3) or realloc(3) got interrupted by a SIGALRM and the signal handler called one of them again. I'm not definitively sure what POSIX & friends say about the reentrancy of malloc(3) but I belive it is not required to be reentrant. Anybody know definitively what POSIX say here ? I could add sigprocmask(2) calls around malloc and friends, but that would mean adding two syscalls per malloc/free/realloc calls, so I don't like the idea. It could be an option that the program could select of course. Alternatively any program like ppp that uses SIGALRM for a state machine is severely limited in its implementation. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-bugs Wed Jan 1 03:50:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA24795 for bugs-outgoing; Wed, 1 Jan 1997 03:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA24787; Wed, 1 Jan 1997 03:50:03 -0800 (PST) Date: Wed, 1 Jan 1997 03:50:03 -0800 (PST) Message-Id: <199701011150.DAA24787@freefall.freebsd.org> To: freebsd-bugs Cc: From: Helbig@MX.BA-Stuttgart.De Subject: Re: kern/2305: system hangs with second Ide controller Reply-To: Helbig@MX.BA-Stuttgart.De Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2305; it has been noted by GNATS. From: Helbig@MX.BA-Stuttgart.De To: freebsd-gnats-submit@freebsd.org, wh@helbig.informatik.ba-stuttgart.de Cc: Subject: Re: kern/2305: system hangs with second Ide controller Date: Wed, 1 Jan 1997 12:48:11 +0100 (MET) In the meantime I have been pointed to some URL's (thanks to everyone !) from which I learned that I have a "well known problem", the IDE-Controller CMD 640B, which just doesn't support concurrently use of both channels. Seems that other operating systems either don't use primary and secondary IDE port simultaneously (like DOS ...) or have an option to prevent this (like Linux). I wonder why it's worthwhile to implement a workaround for this hardware flaw in the FreeBSD-Kernel. The URLS are: http://thef-nym.sci.kun.nl/cgi-pieterh/atazip/atafq-3.html#ss3.2 http://www.phyttp://www.physics.ohio-state.edu/~jrdemers/ibm/eide.txt Of the three 640B-flaws mentioned in the second URL only the third seems to apply to my configuration. (lucky me!): Does not support simultaneous I/O on primary and secondary EIDE ports. If someone patched the wd-controller to avoid simultaneous I/O please let me know! Happy New Year, Wolfgang Helbig From owner-freebsd-bugs Wed Jan 1 07:20:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA01082 for bugs-outgoing; Wed, 1 Jan 1997 07:20:33 -0800 (PST) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA01077 for ; Wed, 1 Jan 1997 07:20:30 -0800 (PST) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA00270; Wed, 1 Jan 1997 15:36:27 +0100 From: Luigi Rizzo Message-Id: <199701011436.PAA00270@labinfo.iet.unipi.it> Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() To: phk@critter.dk.tfs.com Date: Wed, 1 Jan 1997 15:36:27 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org In-Reply-To: <199701011000.CAA21981@freefall.freebsd.org> from "Poul-Henning Kamp" at Jan 1, 97 01:59:43 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >When installing via PPP I got the message on vty2 (the PPP screen anyway): > >ppp in malloc(): warning: recursive call. > > Alternatively any program like ppp that uses SIGALRM for a state machine > is severely limited in its implementation. I am using ppp here (basically 2.1R + phkmalloc) without the above problem. On passing, iijppp is extremely bad since it does a couple of malloc()/free() per packet (one for the header, one for the packet itself). On a 14.4 modem this amounts to at least 10 malloc/free per second, think what this means on a modem server. This could be easily fixed, if someone wants to look at it (I am afraid bu I don't have the time to work on this, but some of the people who added NAT might be relatively familiar with iijppp code). The code is relatively well structured and distinguishes between different classes of objects, so handling free lists withih iijppp for each class should be highly efficient. Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-bugs Wed Jan 1 07:51:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA02501 for bugs-outgoing; Wed, 1 Jan 1997 07:51:37 -0800 (PST) Received: (from markm@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA02445; Wed, 1 Jan 1997 07:50:13 -0800 (PST) Date: Wed, 1 Jan 1997 07:50:13 -0800 (PST) From: Mark Murray Message-Id: <199701011550.HAA02445@freefall.freebsd.org> To: brandon@cold.org, markm, freebsd-bugs, markm Subject: Re: misc/2302 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: new crypt() including SHS and an extendable interface State-Changed-From-To: open-feedback State-Changed-By: markm State-Changed-When: Wed Jan 1 07:46:20 PST 1997 State-Changed-Why: I have asked the submitter for a copy of his code. Responsible-Changed-From-To: freebsd-bugs->markm Responsible-Changed-By: markm Responsible-Changed-When: Wed Jan 1 07:46:20 PST 1997 Responsible-Changed-Why: I did the original "multiple personality" crypt(). From owner-freebsd-bugs Wed Jan 1 10:31:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18612 for bugs-outgoing; Wed, 1 Jan 1997 10:31:21 -0800 (PST) Received: (from joerg@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18583; Wed, 1 Jan 1997 10:31:06 -0800 (PST) Date: Wed, 1 Jan 1997 10:31:06 -0800 (PST) From: Joerg Wunsch Message-Id: <199701011831.KAA18583@freefall.freebsd.org> To: andrew@ugh.net.au, joerg, freebsd-bugs Subject: Re: bin/2345 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: sysinstall: ppp exited on an error 6 State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Wed Jan 1 19:28:20 MET 1997 State-Changed-Why: This is basically the same problem as described in more detail in PR # bin/2347. From owner-freebsd-bugs Wed Jan 1 10:35:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18802 for bugs-outgoing; Wed, 1 Jan 1997 10:35:05 -0800 (PST) Received: (from joerg@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA18751; Wed, 1 Jan 1997 10:33:18 -0800 (PST) Date: Wed, 1 Jan 1997 10:33:18 -0800 (PST) From: Joerg Wunsch Message-Id: <199701011833.KAA18751@freefall.freebsd.org> To: andersl@saaf.se, joerg, freebsd-bugs Subject: Re: bin/2335 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: LC_CTYPE ignored by more State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Wed Jan 1 19:32:27 MET 1997 State-Changed-Why: Already fixed in 2.1.6 and 2.2(-BETA...). From owner-freebsd-bugs Wed Jan 1 11:30:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA20236 for bugs-outgoing; Wed, 1 Jan 1997 11:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA20227; Wed, 1 Jan 1997 11:30:01 -0800 (PST) Date: Wed, 1 Jan 1997 11:30:01 -0800 (PST) Message-Id: <199701011930.LAA20227@freefall.freebsd.org> To: freebsd-bugs Cc: From: Garrett Wollman Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Reply-To: Garrett Wollman Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/2347; it has been noted by GNATS. From: Garrett Wollman To: Poul-Henning Kamp Cc: freebsd-gnats-submit@freefall.freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Date: Wed, 1 Jan 1997 14:25:20 -0500 < said: > I'm not definitively sure what POSIX & friends say about the reentrancy > of malloc(3) but I belive it is not required to be reentrant. > Anybody know definitively what POSIX say here ? Well, I can't tell you what POSIX says, but I can tell you what ANSI X3J11 said: the only thing you can do inside a signal handler is set a variable of type `volatile sig_atomic_t'. Hearsay: one of the UNIX standards (maybe P1003.n, maybe XPGn, maybe Spec 1170) specifies a list of *system calls* which may be called from signal handlers. I think one or more of them may also require that longjmp() work from a signal handler, but not necessarily that anything work after doing that. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-bugs Wed Jan 1 12:10:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA21737 for bugs-outgoing; Wed, 1 Jan 1997 12:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA21729; Wed, 1 Jan 1997 12:10:01 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 12:10:01 -0800 (PST) Resent-Message-Id: <199701012010.MAA21729@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, wlloyd@tolstoy.mpd.ca Received: from tolstoy.mpd.ca (wlloyd.HIP.CAM.ORG [199.84.42.209]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA21691 for ; Wed, 1 Jan 1997 12:09:37 -0800 (PST) Received: (from wlloyd@localhost) by tolstoy.mpd.ca (8.7.5/8.7.3) id PAA01007; Wed, 1 Jan 1997 15:11:05 -0500 (EST) Message-Id: <199701012011.PAA01007@tolstoy.mpd.ca> Date: Wed, 1 Jan 1997 15:11:05 -0500 (EST) From: William Lloyd Reply-To: wlloyd@tolstoy.mpd.ca To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2355: www.ca.freebsd.org missing from www.freebsd.org Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2355 >Category: docs >Synopsis: www.ca.freebsd.org missing from www.freebsd.org >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 12:10:00 PST 1997 >Last-Modified: >Originator: William Lloyd >Organization: William Lloyd (wlloyd@mpd.ca) >Release: FreeBSD 2.1.5-STABLE i386 >Environment: >Description: www.ca.freebsd.org is not listed on www.freebsd.org >How-To-Repeat: >Fix: *** index.sgml.orig Wed Jan 1 15:05:40 1997 --- index.sgml Wed Jan 1 15:06:16 1997 *************** *** 54,59 **** --- 54,60 ---- + >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 12:18:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA21960 for bugs-outgoing; Wed, 1 Jan 1997 12:18:53 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA21942 for ; Wed, 1 Jan 1997 12:18:49 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA08477; Wed, 1 Jan 1997 21:18:42 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA24264; Wed, 1 Jan 1997 21:18:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA29617; Wed, 1 Jan 1997 19:30:05 +0100 (MET) From: J Wunsch Message-Id: <199701011830.TAA29617@uriah.heep.sax.de> Subject: Re: bin/2349: sysinstall: If you type anything on vty4 it dies. To: jkh@time.cdrom.com Date: Wed, 1 Jan 1997 19:30:05 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701010930.BAA20913@freefall.freebsd.org> from "Jordan K. Hubbard" at "Jan 1, 97 01:30:01 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > Whenever it type anything on the emergency holographic shell > > in the installer the shell dies - when i switch from that window I cant > > get back to it. It wasn't a tradgedy for me cause i didnt need to use it > > but.... > > This is a known bug, though I can't say exactly for sure why it's > happening. It's a new problem and we're chasing the cause - it could > be sysinstall, it could be the console driver, it's hard to say. syscons, i think. See also my comment to PR # bin/2347. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Jan 1 12:18:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA21972 for bugs-outgoing; Wed, 1 Jan 1997 12:18:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA21947 for ; Wed, 1 Jan 1997 12:18:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA08469; Wed, 1 Jan 1997 21:18:39 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA24263; Wed, 1 Jan 1997 21:18:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA29598; Wed, 1 Jan 1997 19:28:54 +0100 (MET) From: J Wunsch Message-Id: <199701011828.TAA29598@uriah.heep.sax.de> Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 1 Jan 1997 19:28:54 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org, brian@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701011436.PAA00270@labinfo.iet.unipi.it> from Luigi Rizzo at "Jan 1, 97 03:36:27 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Luigi Rizzo wrote: > I am using ppp here (basically 2.1R + phkmalloc) without the above > problem. On passing, iijppp is extremely bad since it does a couple of > malloc()/free() per packet (one for the header, one for the packet > itself). On a 14.4 modem this amounts to at least 10 malloc/free per > second, think what this means on a modem server. > > This could be easily fixed, if someone wants to look at it (I am > afraid bu I don't have the time to work on this, but some of the > people who added NAT might be relatively familiar with iijppp code). > The code is relatively well structured and distinguishes between > different classes of objects, so handling free lists withih iijppp > for each class should be highly efficient. Brian Somers agreed to take over maintenance of iijppp. I'm not sure about your CVS knowledge now, Brian? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Jan 1 12:20:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA22066 for bugs-outgoing; Wed, 1 Jan 1997 12:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA22030; Wed, 1 Jan 1997 12:20:02 -0800 (PST) Date: Wed, 1 Jan 1997 12:20:02 -0800 (PST) Message-Id: <199701012020.MAA22030@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/2347; it has been noted by GNATS. From: J Wunsch To: andrew@ugh.net.au Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Date: Wed, 1 Jan 1997 19:25:38 +0100 (MET) As andrew@ugh.net.au wrote: > When installing via PPP I got the message on vty2 (the PPP screen anyway): > ppp in malloc(): warning: recursive call. So this is now the reason for the problem you're describing in PR # bin/2345, both are duplicates, but this one here is more detailed. For no known to me reason, sysinstall uses an /etc/malloc.conf containing the letter "A", meaning it should abort (signal 6) any program that causes a malloc warning. You could probably work around this by typing "rm /etc/malloc.conf" early in the emergency holographic shell. Hmm, no, you gotta type it _before_ you're starting PPP, so i think the only way to achieve this is to first use the `fixit' floppy. Download the fixit image, copy it to a floppy, then select `fixit' as the first step of your installation session, before installing anything. Remove said symlink from the fixit shell. Ick. ISTR that the fixit process was broken in BETA, i'm not sure. I could provide you with an alternate (more recent) boot floppy, where you can even start the Emergency Holographic Shell before (but i think you need the fixit session anyway, since there's no rm command available that early). > I typed show mem to see what was wrong and things froze - modem stopped > receiving, ppp didnt respond - I went to vty4 (the emergency holographic (signal 6) > shell one) to do a ps and see what was going on - i typed ps and nothing > happened. I switched to vty0 and nothing had changed - i could > no longer go back to vty4 (it just beeped when i tried). I pressec ^C and There are two basically known bugs here. One is broken by design :), in that the console driver prevents you from switching to a screen when no process has this VTY open. This bugfeature has been copied from SCO, but it's IMHO a very silly one. The second is that syscons seems to have serious trouble with VT switching these days. This is also basically known (but i don't think anybody is working on a fix for this right now). It renders the Emergency Holographic Shell fairly unusable. :-( The only workaround i've found for this is starting yet another shell on top of the EHS early during installation. Apparently, this keeps yet another process running on that VTY, and this seems to tell syscons that switching to that screen is possible. > Try getting PPP to transfer a lot of data for an hour or two - It seems > to happen when the modem has been flat chat at 28.8 for an hour or so. Hmm, this would be interesting to find. Maybe it's something related to your setup, i'm not sure. I'm using PPP a lot, and i also have malloc.conf set to `Abort'. Yet, i have not seen this phenomenon. If you can trigger it later, once your system has already been installed, it would be great if you could help us out with a stacktrace from the coredump. I'm afraid this PR will remain open until this. In order to do this, you also have to type ln -s AJ /etc/malloc.conf Errm, nope. :-((( For security reasons, setuid binaries don't generate coredumps now, not even if your real UID matches the UID of the process. So the only chance to get a core is to remove the suid and sgid bits from /usr/sbin/ppp, and run it as root. It would be really great if you could trigger the bug again. (If you did, send it as mail to freebsd-gnats-submit@freebsd.org, with a subject line of just ``bin/2347''. This way, your mail will be appended to the audit-trail of this PR.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Wed Jan 1 12:52:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA23103 for bugs-outgoing; Wed, 1 Jan 1997 12:52:58 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA23098 for ; Wed, 1 Jan 1997 12:52:56 -0800 (PST) Received: from schizo.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vfXeD-0003whC; Wed, 1 Jan 97 12:52 PST Received: from critter.dk.tfs.com (critter-home [193.162.32.19]) by schizo.dk.tfs.com (8.8.2/8.7.3) with ESMTP id VAA25495; Wed, 1 Jan 1997 21:52:21 +0100 (MET) Received: from critter.dk.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id VAA13809; Wed, 1 Jan 1997 21:55:06 +0100 (MET) To: J Wunsch cc: freebsd-bugs@freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() In-reply-to: Your message of "Wed, 01 Jan 1997 12:20:02 PST." <199701012020.MAA22030@freefall.freebsd.org> Date: Wed, 01 Jan 1997 21:55:06 +0100 Message-ID: <13807.852152106@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199701012020.MAA22030@freefall.freebsd.org>, J Wunsch writes: > For no known to me reason, sysinstall uses an /etc/malloc.conf > containing the letter "A", meaning it should abort (signal 6) any > program that causes a malloc warning. I put that in, with the intention to remove it before -RELEASE. It should be obvious why :-) We don't need to reproduce this problem, it is far to obvious in the source why it happens and all we have to do to fix it is to rewrite ppp :-( -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-bugs Wed Jan 1 13:10:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24180 for bugs-outgoing; Wed, 1 Jan 1997 13:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24173; Wed, 1 Jan 1997 13:10:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 13:10:02 -0800 (PST) Resent-Message-Id: <199701012110.NAA24173@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, nsayer@quack.kfu.com Received: from quack.kfu.com (0@quack.kfu.com [204.147.226.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23825 for ; Wed, 1 Jan 1997 13:04:59 -0800 (PST) Received: from icarus.kfu.com (icarus.kfu.com [204.147.226.3]) by quack.kfu.com (8.6.12/8.6.12) with ESMTP id NAA26924 for ; Wed, 1 Jan 1997 13:04:58 -0800 Received: by icarus.kfu.com (8.8.2//ident-1.0) id NAA03421; Wed, 1 Jan 1997 13:04:56 -0800 (PST) Message-Id: <199701012104.NAA03421@icarus.kfu.com> Date: Wed, 1 Jan 1997 13:04:56 -0800 (PST) From: nsayer@quack.kfu.com Reply-To: nsayer@quack.kfu.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2356: relnotes for 2.2-BETA do not list AMD 53C974 Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2356 >Category: docs >Synopsis: relnotes for 2.2-BETA do not list AMD 53C974 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 13:10:01 PST 1997 >Last-Modified: >Originator: Nick Sayer >Organization: just me >Release: FreeBSD 2.2-BETA i386 >Environment: >Description: The new "amd" driver for the AMD 53C974 SCSI controller is not mentioned in the release notes. It works perfectly, so far as I am able to tell. >How-To-Repeat: >Fix: dmesg | grep amd >> relnotes.txt edit as appropriate. :-) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 13:50:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA26277 for bugs-outgoing; Wed, 1 Jan 1997 13:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA26271; Wed, 1 Jan 1997 13:50:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 13:50:02 -0800 (PST) Resent-Message-Id: <199701012150.NAA26271@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, charnier@xp11.frmug.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA25925 for ; Wed, 1 Jan 1997 13:41:30 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.8.2/8.8.2/frmug-1.2) with UUCP id WAA06586 for FreeBSD-gnats-submit@freebsd.org; Wed, 1 Jan 1997 22:41:25 +0100 (MET) Received: (from charnier@localhost) by xp11.frmug.org (8.8.4/8.7.3/xp11-uucp-1.1) id PAA03571; Wed, 1 Jan 1997 15:24:15 +0100 (CET) Message-Id: <199701011424.PAA03571@xp11.frmug.org> Date: Wed, 1 Jan 1997 15:24:15 +0100 (CET) From: Philippe Charnier Reply-To: charnier@xp11.frmug.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2357: documentation not installed properly Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2357 >Category: docs >Synopsis: PRINTER -> PRINTERDEVICE missing in various makefiles >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 13:50:01 PST 1997 >Last-Modified: >Originator: Philippe Charnier >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: >Description: PRINTER is still used in some makefiles, should be renamed to PRINTERDEVICE. >How-To-Repeat: unset PRINTER then make in /usr/share/doc, it will install /usr/share/doc/usd/10.exref/summary..gz /usr/share/doc/usd/12.vi/summary..gz /usr/share/doc/usd/12.vi/viapwh..gz >Fix: go to /usr/src/share/doc/usd and apply the following patch Index: 10.exref/Makefile =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/share/doc/usd/10.exref/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- Makefile 1996/11/01 07:57:05 1.5 +++ Makefile 1997/01/01 14:00:38 @@ -11,9 +11,9 @@ .include .if !defined(NODOCCOMPRESS) -SFILE= summary.${PRINTER}.gz +SFILE= summary.${PRINTERDEVICE}.gz .else -SFILE= summary.${PRINTER} +SFILE= summary.${PRINTERDEVICE} .endif all: ${DFILE} ${SFILE} Index: 12.vi/Makefile =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/share/doc/usd/12.vi/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- Makefile 1996/11/01 07:57:07 1.4 +++ Makefile 1997/01/01 14:20:27 @@ -11,11 +11,11 @@ .include .if !defined(NODOCCOMPRESS) -SFILE= summary.${PRINTER}.gz -VFILE= viapwh.${PRINTER}.gz +SFILE= summary.${PRINTERDEVICE}.gz +VFILE= viapwh.${PRINTERDEVICE}.gz .else -SFILE= summary.${PRINTER} -VFILE= viapwh.${PRINTER} +SFILE= summary.${PRINTERDEVICE} +VFILE= viapwh.${PRINTERDEVICE} .endif all: ${DFILE} ${SFILE} ${VFILE} >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Jan 1 15:40:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA00811 for bugs-outgoing; Wed, 1 Jan 1997 15:40:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA00789; Wed, 1 Jan 1997 15:40:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 15:40:02 -0800 (PST) Resent-Message-Id: <199701012340.PAA00789@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, gurney_j@efn.org Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA00614 for ; Wed, 1 Jan 1997 15:35:07 -0800 (PST) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id SAA12546 for ; Wed, 1 Jan 1997 18:34:24 -0500 (EST) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (8.8.3/8.7.3) with ESMTP id SAA28776 for ; Wed, 1 Jan 1997 18:34:23 -0500 (EST) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.18]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id GAA20946 for ; Wed, 1 Jan 1997 06:26:22 -0500 (EST) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA24221 for ; Wed, 1 Jan 1997 03:25:58 -0800 (PST) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id DAA18580; Wed, 1 Jan 1997 03:25:56 -0800 (PST) Message-Id: <199701011125.DAA18580@hydrogen.nike.efn.org> Date: Wed, 1 Jan 1997 03:25:56 -0800 (PST) From: John-Mark Gurney Reply-To: gurney_j@efn.org To: FreeBSD-gnats@freefall.FreeBSD.org X-Send-Pr-Version: 3.2 Subject: misc/2358: minor bugs in fortune data base Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 2358 >Category: misc >Synopsis: minor bugs in fortune data base >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 15:40:01 PST 1997 >Last-Modified: >Originator: John-Mark Gurney >Organization: Cu Networking >Release: FreeBSD 2.2-960801-SNAP i386 >Environment: probably pretty much any 4.4bsd-lite based system with games installed >Description: basicly CChheecckk dduupplleexx sswwiittcchh... should also duplicate the spaces :) also my previous patch (in pr 2085) didn't patch fortunes2 >How-To-Repeat: run fortune a TON of times, or simply grep the fortune database >Fix: apply this patch: Index: fortunes =================================================================== RCS file: /usr/cvs/src/games/fortune/datfiles/fortunes,v retrieving revision 1.3 diff -c -c -r1.3 fortunes *** fortunes 1996/11/22 22:16:25 1.3 --- fortunes 1997/01/01 11:19:44 *************** *** 2518,2524 **** % Caution: breathing may be hazardous to your health. % ! CChheecckk yyoouurr dduupplleexx sswwiittcchh.. % Cecil, you're my final hope Of finding out the true Straight Dope --- 2518,2524 ---- % Caution: breathing may be hazardous to your health. % ! CChheecckk yyoouurr dduupplleexx sswwiittcchh.. % Cecil, you're my final hope Of finding out the true Straight Dope Index: fortunes2 =================================================================== RCS file: /usr/cvs/src/games/fortune/datfiles/fortunes2,v retrieving revision 1.2 diff -c -c -r1.2 fortunes2 *** fortunes2 1995/12/27 15:30:58 1.2 --- fortunes2 1997/01/01 11:19:29 *************** *** 12663,12669 **** % Caution: Keep out of reach of children. % ! CChheecckk yyoouurr dduupplleexx sswwiittcchh.. % CCI Power 6/40: one board, a megabyte of cache, and an attitude... % --- 12663,12669 ---- % Caution: Keep out of reach of children. % ! CChheecckk yyoouurr dduupplleexx sswwiittcchh.. % CCI Power 6/40: one board, a megabyte of cache, and an attitude... % *************** *** 36434,36440 **** [4] But the only number that is both odd and even is infinity. [5] Therefore, horses must have an infinite number of legs. ! Topics is be covered in future issues include proof by: intimidation, gesticulation (handwaving), "try it; it works", --- 36434,36440 ---- [4] But the only number that is both odd and even is infinity. [5] Therefore, horses must have an infinite number of legs. ! Topics to be covered in future issues include proof by: intimidation, gesticulation (handwaving), "try it; it works", >Audit-Trail: >Unformatted: John-Mark Gurney From owner-freebsd-bugs Wed Jan 1 17:19:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA06334 for bugs-outgoing; Wed, 1 Jan 1997 17:19:09 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA06315; Wed, 1 Jan 1997 17:19:02 -0800 (PST) Date: Wed, 1 Jan 1997 17:19:02 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199701020119.RAA06315@freefall.freebsd.org> To: wlloyd@tolstoy.mpd.ca, jkh, freebsd-bugs Subject: Re: docs/2355 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: www.ca.freebsd.org missing from www.freebsd.org State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Wed Jan 1 17:18:42 PST 1997 State-Changed-Why: Done, thanks! From owner-freebsd-bugs Wed Jan 1 17:31:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA07109 for bugs-outgoing; Wed, 1 Jan 1997 17:31:53 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA07102 for ; Wed, 1 Jan 1997 17:31:51 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA19423; Wed, 1 Jan 1997 17:31:39 -0800 (PST) To: J Wunsch cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() In-reply-to: Your message of "Wed, 01 Jan 1997 12:20:02 PST." <199701012020.MAA22030@freefall.freebsd.org> Date: Wed, 01 Jan 1997 17:31:37 -0800 Message-ID: <19408.852168697@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > For no known to me reason, sysinstall uses an /etc/malloc.conf > containing the letter "A", meaning it should abort (signal 6) any > program that causes a malloc warning. Not sysinstall - /usr/src/release/Makefile plonks one down in the MFS filesystem from the release.8 rule. Poul-Henning added this, and maybe *he* can explain his thoughts in doing so. ;-) I'd have thought it was to catch malloc bogons more swiftly, though I'll agree that making them fatal is probably too much. Were those two lines to vanish from release/Makefile again, I would not cry. ;-) From owner-freebsd-bugs Wed Jan 1 18:01:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA08210 for bugs-outgoing; Wed, 1 Jan 1997 18:01:31 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA08204 for ; Wed, 1 Jan 1997 18:01:27 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id MAA20387; Thu, 2 Jan 1997 12:51:43 +1100 Date: Thu, 2 Jan 1997 12:51:43 +1100 From: Bruce Evans Message-Id: <199701020151.MAA20387@godzilla.zeta.org.au> To: freebsd-bugs@freefall.freebsd.org, wollman@lcs.mit.edu Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm not definitively sure what POSIX & friends say about the reentrancy > > of malloc(3) but I belive it is not required to be reentrant. > > > Anybody know definitively what POSIX say here ? > > Well, I can't tell you what POSIX says, but I can tell you what ANSI > X3J11 said: the only thing you can do inside a signal handler is set a > variable of type `volatile sig_atomic_t'. POSIX doesn't allow it either of course. POSIX does allow calling many syscalls. FreeBSD seems to be broken here. The global variable `errno' may be clobbered by any syscall. There is an upen PR about floating point being available in signal handlers. The user wants to call printf(), which can't be expected to work. Unfortunately, even ANSI requires floating point to work right in signal handlers, because it allows normal operations on auto variables. The variables might be floating point, and even though you can't print them, you can do things like volatile double dfoo = 1.0, dbar = 3.0; volatile float ffoo = 1.0, fbar = 3.0; extern volatile sig_atomic_t baz; baz = (dfoo / dbar = ffoo / fbar); which probably requires runtime floating point no matter what the optimization level is. > Hearsay: one of the UNIX standards (maybe P1003.n, maybe XPGn, maybe > Spec 1170) specifies a list of *system calls* which may be called from > signal handlers. I think one or more of them may also require that > longjmp() work from a signal handler, but not necessarily that > anything work after doing that. POSIX.1 doesn't require longjmp() to work right. It requires simple syscalls like read() and write() to work right. It is under-specified in not saying much about side effects like read() to global memory clobbering the memory. It requires non-simple things like fork() and execve() to work right. It requires not-so-simple things that are implemented as library functions in FreeBSD to work right. Some of them can't possibly be POSIX conformant. E.g., sleep() is very far from being atomic. longjmp() works right in FreeBSD - calling it from a signal handler is no worse than calling it from a random point in the program or library. Even a random non-sequence point, I hope. Bruce From owner-freebsd-bugs Wed Jan 1 18:32:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA09324 for bugs-outgoing; Wed, 1 Jan 1997 18:32:09 -0800 (PST) Received: (from jkh@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA09289; Wed, 1 Jan 1997 18:32:04 -0800 (PST) Date: Wed, 1 Jan 1997 18:32:04 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199701020232.SAA09289@freefall.freebsd.org> To: nsayer@quack.kfu.com, jkh, freebsd-bugs Subject: Re: docs/2356 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: relnotes for 2.2-BETA do not list AMD 53C974 State-Changed-From-To: open-closed State-Changed-By: jkh State-Changed-When: Wed Jan 1 18:31:50 PST 1997 State-Changed-Why: This one has already been fixed. From owner-freebsd-bugs Wed Jan 1 20:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14032 for bugs-outgoing; Wed, 1 Jan 1997 20:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14015; Wed, 1 Jan 1997 20:00:02 -0800 (PST) Resent-Date: Wed, 1 Jan 1997 20:00:02 -0800 (PST) Resent-Message-Id: <199701020400.UAA14015@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, vazquez@IQM.Unicamp.BR Received: from kalypso.iqm.unicamp.br (kalypso.iqm.unicamp.br [143.106.13.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA13716 for ; Wed, 1 Jan 1997 19:51:14 -0800 (PST) Received: (from vazquez@localhost) by kalypso.iqm.unicamp.br (8.8.4/8.7.3/FreeBSD/2.1.5) id CAA02651; Thu, 2 Jan 1997 02:05:44 GMT Message-Id: <199701020205.CAA02651@kalypso.iqm.unicamp.br> Date: Thu, 2 Jan 1997 02:05:44 GMT From: Pedro A M Vazquez Reply-To: vazquez@IQM.Unicamp.BR To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/2359: /usr/share/examples/sunrpc/Makefile defines -lrpclib Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2359 >Category: misc >Synopsis: /usr/share/examples/sunrpc/Makefile uses LIB=-lrpclib >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 20:00:01 PST 1997 >Last-Modified: >Originator: Pedro A M Vazquez >Organization: >Release: FreeBSD 2.1.6 >Environment: FreeBSD2.1.x >Description: The makefiles /usr/share/examples/sunrpc/Makefile /usr/share/examples/sunrpc/dir/Makefile /usr/share/examples/sunrpc/msg/Makefile /usr/share/examples/sunrpc/sort/Makefile define the RPC library as: LIB=-lrpclib instead of LIB= >How-To-Repeat: Just type make >Fix: Remove -lrpclib from the makefiles >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jan 2 00:12:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA22800 for bugs-outgoing; Thu, 2 Jan 1997 00:12:36 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id AAA22795 for ; Thu, 2 Jan 1997 00:12:33 -0800 (PST) Received: from schizo.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vfiFo-0003vyC; Thu, 2 Jan 97 00:11 PST Received: from critter.dk.tfs.com (critter.dk.tfs.com [140.145.230.252]) by schizo.dk.tfs.com (8.8.2/8.7.3) with ESMTP id JAA26397; Thu, 2 Jan 1997 09:11:54 +0100 (MET) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id IAA14530; Thu, 2 Jan 1997 08:16:28 +0100 (MET) To: Bruce Evans cc: freebsd-bugs@freefall.freebsd.org, wollman@lcs.mit.edu Subject: Re: bin/2347: sysinstall: ppp: recursive call in malloc() In-reply-to: Your message of "Thu, 02 Jan 1997 12:51:43 +1100." <199701020151.MAA20387@godzilla.zeta.org.au> Date: Thu, 02 Jan 1997 08:16:27 +0100 Message-ID: <14528.852189387@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199701020151.MAA20387@godzilla.zeta.org.au>, Bruce Evans writes: >> > I'm not definitively sure what POSIX & friends say about the reentrancy >> > of malloc(3) but I belive it is not required to be reentrant. >> >POSIX doesn't allow it either of course. OK, I guess we can conclude that ppp needs fixed then, not malloc. Thanks! -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-bugs Thu Jan 2 06:30:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA06171 for bugs-outgoing; Thu, 2 Jan 1997 06:30:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA06165; Thu, 2 Jan 1997 06:30:03 -0800 (PST) Resent-Date: Thu, 2 Jan 1997 06:30:03 -0800 (PST) Resent-Message-Id: <199701021430.GAA06165@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, wh@MX.BA-Stuttgart.De Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.1.21]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA05884 for ; Thu, 2 Jan 1997 06:23:34 -0800 (PST) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by terminator.informatik.ba-stuttgart.de (8.7.6/8.7.3) with ESMTP id OAA02805 for ; Thu, 2 Jan 1997 14:22:43 +0100 Received: (from wh@localhost) by helbig.informatik.ba-stuttgart.de (8.8.4/8.8.4) id PAA01417; Thu, 2 Jan 1997 15:23:13 +0100 (MET) Message-Id: <199701021423.PAA01417@helbig.informatik.ba-stuttgart.de> Date: Thu, 2 Jan 1997 15:23:13 +0100 (MET) From: Wolfgang Helbig Reply-To: wh@MX.BA-Stuttgart.De To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/2362: make tags does not work with objdir installed Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2362 >Category: bin >Synopsis: make tags does not work with objdir installed >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 2 06:30:02 PST 1997 >Last-Modified: >Originator: Wolfgang Helbig >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: /usr/obj with all subdirs as installed from last `make world'. >Description: ctags and egrep does not get any files when a `make tags' is entered from /sys/i386. >How-To-Repeat: make world cd /sys/i386 make tags >Fix: cd /sys/i386 rm -rf /usr/obj`/bin/pwd' make tags >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jan 2 08:57:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13896 for bugs-outgoing; Thu, 2 Jan 1997 08:57:05 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13873; Thu, 2 Jan 1997 08:57:01 -0800 (PST) Date: Thu, 2 Jan 1997 08:57:01 -0800 (PST) From: Mike Pritchard Message-Id: <199701021657.IAA13873@freefall.freebsd.org> To: charnier@xp11.frmug.org, mpp, freebsd-bugs Subject: Re: docs/2357 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: PRINTER -> PRINTERDEVICE missing in various makefiles State-Changed-From-To: open-closed State-Changed-By: mpp State-Changed-When: Thu Jan 2 08:56:42 PST 1997 State-Changed-Why: Suggested fix applied. From owner-freebsd-bugs Thu Jan 2 09:05:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14515 for bugs-outgoing; Thu, 2 Jan 1997 09:05:21 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14503; Thu, 2 Jan 1997 09:05:16 -0800 (PST) From: Mike Pritchard Message-Id: <199701021705.JAA14503@freefall.freebsd.org> Subject: Re: kern/2325: quota.user enlarged, no boot on 2.2-BETA To: bde@zeta.org.au (Bruce Evans) Date: Thu, 2 Jan 1997 09:05:15 -0800 (PST) Cc: freebsd-bugs@freefall.freebsd.org In-Reply-To: <199612302352.KAA14147@godzilla.zeta.org.au> from "Bruce Evans" at Dec 31, 96 10:52:03 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > [...] > Here the id is unsigned long and the struct has size 64, so these > calculations overflow when the id is >= 2^26 (67108864). The sparse > file would need to be at least 256GB instead of a measly 4GB to > correctly support id 0xffffffff. The overflow probably causes id > 2^26 to be an alias for id 0. There is probably no problem except > for the time that it takes to initialize the 4GB or 256GB file. You > are unlikely to have any aliases for 0 or -2 (really 0xfffffffe). The trouble is, that once you have this huge quota file, quotacheck must examine the entire file looking for quota entries that need to be reset. E.g. it currently has no way of knowing that there are no quota structures in use bewtween the last real uid and 0xfffffffe - it checks each and every one of them, and even though I addded some code to speed this up, it still can take an unacceptable amount of time to process the qouta file. I do have a couple of ideas on how to totally avoid this problem, and as soon as I figure out the way to do this with the least amount of impact on current quota users, I'll go ahead and implement it. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-bugs Thu Jan 2 09:07:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14793 for bugs-outgoing; Thu, 2 Jan 1997 09:07:52 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14721; Thu, 2 Jan 1997 09:07:37 -0800 (PST) Date: Thu, 2 Jan 1997 09:07:37 -0800 (PST) From: Mike Pritchard Message-Id: <199701021707.JAA14721@freefall.freebsd.org> To: Andre.Albsmeier@mchp.siemens.de, mpp, freebsd-bugs Subject: Re: kern/2325 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: quota.user enlarged, no boot on 2.2-BETA State-Changed-From-To: open-analyzed State-Changed-By: mpp State-Changed-When: Thu Jan 2 09:06:38 PST 1997 State-Changed-Why: The problem is that very large uids in the file system can cause quota check to run for an unacceptable amount of time. I have a couple of ideas on how to avoid this problem. From owner-freebsd-bugs Thu Jan 2 09:08:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14882 for bugs-outgoing; Thu, 2 Jan 1997 09:08:09 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA14861; Thu, 2 Jan 1997 09:08:07 -0800 (PST) Date: Thu, 2 Jan 1997 09:08:07 -0800 (PST) From: Mike Pritchard Message-Id: <199701021708.JAA14861@freefall.freebsd.org> To: mpp, freebsd-bugs, mpp Subject: Re: kern/2325 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: quota.user enlarged, no boot on 2.2-BETA Responsible-Changed-From-To: freebsd-bugs->mpp Responsible-Changed-By: mpp Responsible-Changed-When: Thu Jan 2 09:07:39 PST 1997 Responsible-Changed-Why: I'm working on it... From owner-freebsd-bugs Thu Jan 2 11:00:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23509 for bugs-outgoing; Thu, 2 Jan 1997 11:00:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA23489; Thu, 2 Jan 1997 11:00:03 -0800 (PST) Resent-Date: Thu, 2 Jan 1997 11:00:03 -0800 (PST) Resent-Message-Id: <199701021900.LAA23489@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, root Received: from jli.com (jli.com [199.2.111.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA23057 for ; Thu, 2 Jan 1997 10:51:18 -0800 (PST) Received: from cumulus by jli.com with uucp (Smail3.1.29.1 #3) id m0vfsDu-0002TVC; Thu, 2 Jan 97 10:50 PST Message-Id: Date: Thu, 2 Jan 97 10:49 WET From: root@cloud.rain.com Reply-To: root To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/2363: panic during install Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2363 >Category: conf >Synopsis: pressing ESC in System Console Screenmap panics 2.2beta >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 2 11:00:02 PST 1997 >Last-Modified: >Originator: Charlie & >Organization: >Release: FreeBSD 2.2-BETA i386 >Environment: 486/66, 2 IDE drives, installing to SCSI Jaz, 2.2 beta from ftp.freebsd.org >Description: When pressing "escape" on System Console Screenmap window in the post-install configuration, the system panics with "panic: Going nowhere without my init!" >How-To-Repeat: Get to the screenmap window, press escape. I encountered this problem during the automatic post-install invocation after doing a quick install. >Fix: Work around by not pressing escape! (-: I don't know a fix offhand. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Jan 2 12:51:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA01822 for bugs-outgoing; Thu, 2 Jan 1997 12:51:33 -0800 (PST) Received: (from joerg@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA01784; Thu, 2 Jan 1997 12:51:10 -0800 (PST) Date: Thu, 2 Jan 1997 12:51:10 -0800 (PST) From: Joerg Wunsch Message-Id: <199701022051.MAA01784@freefall.freebsd.org> To: root, joerg, freebsd-bugs Subject: Re: conf/2363 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: pressing ESC in System Console Screenmap panics 2.2beta State-Changed-From-To: open-closed State-Changed-By: joerg State-Changed-When: Thu Jan 2 21:48:39 MET 1997 State-Changed-Why: Duplicate for PR # misc/2281, which has alread been closed. From owner-freebsd-bugs Thu Jan 2 16:35:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17277 for bugs-outgoing; Thu, 2 Jan 1997 16:35:12 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA17270 for ; Thu, 2 Jan 1997 16:35:07 -0800 (PST) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by time.cdrom.com (8.8.4/8.6.9) with SMTP id QAA15971; Thu, 2 Jan 1997 16:34:50 -0800 (PST) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id QAA10604; Thu, 2 Jan 1997 16:34:10 -0800 Date: Thu, 2 Jan 1997 16:34:10 -0800 From: "Jin Guojun[ITG]" Message-Id: <199701030034.QAA10604@george.lbl.gov> To: jkh@time.cdrom.com, jmb@freefall.freebsd.org Subject: Re: misc/2321: installation panic before going to past-install menu Cc: freebsd-bugs@time.cdrom.com Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >} All my test systems are SCSI, and I've changed many many settings on >} them without this happening. :-( >} >} Ah well, something is clearly wrong, just to now find out what. >} >} Jordan >} >} > as far as i can tell the common elements are "boot -c" and a scsi bus. >} > >} > Jin Guojun Jordan jmb >} > boot -c ep0 irq 15 ?? ed0 irq 3 i/o 300 mem d4000 >} > scsi ncr aha3940 aha1542CP > >I will try to take scsi interface out and do the install again. >I may not be able to do this before the New Year since that ASUS board is >far away from me. >I have tried many combinations of SCSI cards, motherboards (except that ASUS) >with 3C509B ethernet cards to install 2.2-BATE, however, they are not panic. It is not that motherboard problem. It was caused by an empty SCSI chain. After I add a SCSI disk to the chain, the installation has completed no problem. As other messages we saw for this problem, it sounds like the SCSI code problem. -Jin From owner-freebsd-bugs Thu Jan 2 21:44:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA00429 for bugs-outgoing; Thu, 2 Jan 1997 21:44:45 -0800 (PST) Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA00422 for ; Thu, 2 Jan 1997 21:44:40 -0800 (PST) Received: (from news@localhost) by haywire.DIALix.COM (8.8.4/8.8.2) id NAA18026 for freebsd-bugs@freebsd.org; Fri, 3 Jan 1997 13:44:24 +0800 (WST) X-Authentication-Warning: haywire.DIALix.COM: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-bugs@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-bugs@freebsd.org Date: Fri, 3 Jan 1997 03:06:19 GMT From: mark@putte.seeware.DIALix.oz.au (Mark Hannon) Message-ID: Organization: Private FreeBSD site References: <29233.851651470@time.cdrom.com> Subject: Re: AMD 120 page fault during boot up Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , rory@uic.edu (Rory Imua Lampert) writes: > I did...well something like that. A friend had the exact same motherboard > and cpu. So I put my cpu and ram in his motherboard, it worked just > fine, with another hitch...He was running linux. We tried with my cpu and > his ram, my cpu and my ram, his cpu and my ram and all variations worked. > > -Rory > > On Thu, 26 Dec 1996, Jordan K. Hubbard wrote: > >> > Does anyone have any clue as to what I should try next? >> >> Try swapping that CPU. >> My suggestion would be to change the motherboard speed down to 33MHz and run the chip as a 4/100 instead of 4/120. I had heaps of problems with a 4/120 chip, changed caches, BIOS settings, etc. only thing that worked was to slow it down. Rgds/mark -- +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au| | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | | Australia | seeware@melbourne.DIALix.oz.au | | +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ From owner-freebsd-bugs Fri Jan 3 01:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08252 for bugs-outgoing; Fri, 3 Jan 1997 01:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08241; Fri, 3 Jan 1997 01:00:02 -0800 (PST) Date: Fri, 3 Jan 1997 01:00:02 -0800 (PST) Message-Id: <199701030900.BAA08241@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: kern/2270: Hayes ESP serial card locks system as of 12/01 ke Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2270; it has been noted by GNATS. From: Bruce Evans To: bde@zeta.org.au, george@cia-g.com Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/2270: Hayes ESP serial card locks system as of 12/01 ke Date: Fri, 3 Jan 1997 19:48:32 +1100 >Ok, here is new "development". I recompiled a kernel, without any changes >to the code, and included the kernel debugger, "DDB". I then booted the >new kernel with the switches "-sd". I think I'll show you what I did... > >db>break siostop >db>c > >#cat > /dev/cuaa2 >^D > >db>c > >db>c > >db>c > >It doesn't lock up. I can do this over and over again without any >problems. Unfortunatly, going back into the debugger and deleteing >the breakpoint at siostop and trying the cat again, it completely >locks up again. > >I'm very confused. DDB distorts the enviroment an many ways. There is the obvious unavoidable problem that it changes the timing. Less obviously, DDB doesn't mask interrupts unless they are already masked, so an sio interrupt may occur and happen to clean things up while you're stoipped at the breakpoint at siostop. Try putting a breakpoint a little later, after the "cli" instruction, and single stepping until the "sti" instruction (use "x/ia" to display instructions and "s" to single step). If this prevents the lockup, then the lockup is almost certain to be caused by timing problems. >While looking through the ESP information I found at ftp.hayes.com I found >this: I fetched it too. It doesn't seem to say anything about resetting the UART's fifos. >The note for Step 4 is interresting and explains setting the DMA bit for the >magic outb??? Try adding this to all the outb's to com->fifo. According to the docs, it is necessary to prevent excessive input interrupts that would reduce input efficiency to that of a 16450 (i.e., about 1/4 as efficient as an ordinary 16550). The easiest way to tell if there are too many interrupts iis to look at the sio interrupt count displayed by `systat -vmstat' while input is arriving at a constant rate. >Back to my random changes to sio.c.... I'll commit a change something like the following if we can't find a proper fix. Bruce diff -c2 sio.c~ sio.c *** sio.c~ Tue Dec 24 20:44:53 1996 --- sio.c Fri Jan 3 19:20:22 1997 *************** *** 2129,2132 **** --- 2169,2176 ---- if (rw & FWRITE) { if (com->hasfifo) + #ifdef COM_ESP + /* XXX the outb causes ESPs to hang for some reason. */ + if (!com->esp) + #endif /* XXX does this flush everything? */ outb(com->iobase + com_fifo, *************** *** 2141,2144 **** --- 2185,2191 ---- if (rw & FREAD) { if (com->hasfifo) + #ifdef COM_ESP + if (!com->esp) + #endif /* XXX does this flush everything? */ outb(com->iobase + com_fifo, From owner-freebsd-bugs Fri Jan 3 01:22:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08885 for bugs-outgoing; Fri, 3 Jan 1997 01:22:48 -0800 (PST) Received: (from fenner@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08865; Fri, 3 Jan 1997 01:22:45 -0800 (PST) Date: Fri, 3 Jan 1997 01:22:45 -0800 (PST) From: Bill Fenner Message-Id: <199701030922.BAA08865@freefall.freebsd.org> To: gbuchanan@sympatico.ca, fenner, freebsd-bugs Subject: Re: bin/2339 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: ex/vi/nex/nvi incorrect handling of -- arg State-Changed-From-To: open-closed State-Changed-By: fenner State-Changed-When: Fri Jan 3 01:22:00 PST 1997 State-Changed-Why: This bug does not appear to be present in the version of nvi in 2.2 and -current . From owner-freebsd-bugs Fri Jan 3 01:35:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA10160 for bugs-outgoing; Fri, 3 Jan 1997 01:35:07 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA10143 for ; Fri, 3 Jan 1997 01:35:02 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA26540; Fri, 3 Jan 1997 20:33:59 +1100 Date: Fri, 3 Jan 1997 20:33:59 +1100 From: Bruce Evans Message-Id: <199701030933.UAA26540@godzilla.zeta.org.au> To: brawley@communica.com.au, freebsd-bugs@FreeBSD.ORG Subject: Re: LKMs and character special devices Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >After spending quite some time (too much time) on trying to port >a package to FreeBSD 2.2, I noticed something. > >In the file /usr/src/sys/kern/kern_lkm.c where it does some of the >initializing of the LKMs, noticed that there is code to add a block >special device through a LKM, but not a character special device. >Case statement begins at line 688 (or there abouts) in function >_lkm_dev(). > >Theres just a break in the case statment for the case of LM_DT_CHAR. > >Meaning, for someone to write a LKM that adds a character special >device to the system, must add the entery into the cdevsw list themselves. I think it's the bdev case that's broken. Drivers should add entries to the devswitches themselves in all cases. In 2.2., non-lkm drivers have to do this, so doing it differently for the lkm case just requires more code. Most drivers do it in a poor way using SYSINIT(). This also requires more code and gives worse results than adding the entries at the appropriate time (several drivers have active devswitch entries although their probe has failed, and open routines that can't handle being called when the driver hasn't been attached). >The next querk I found was in /usr/include/sys/lkm.h. > >The MOD_DEV macro seems to be wrong in defining _module (rather, it >tryes to define name ## _module, then when you try to use the >DISPATCH macro, the compiler errs with "_module symbol not found". Apparently the static module object was once always named _module. This only worked when there was only one MOD_DEV() invocation per file. But wcd has two, because lkm doesn't support both cdevs and bdevs in the same module, so someone hacked MOD_DEV() to make the object depend on the module name (and several modules to define _module :-(). Dropping support for initializing devswitches in _lkm_dev() should make supporting cdevs and bdevs in the same module a non-problem. Does the wcd module actually work? It doesn't seem to initialize the devswitches explicitly, so I guess only its block devices work. Bruce From owner-freebsd-bugs Fri Jan 3 13:40:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA16029 for bugs-outgoing; Fri, 3 Jan 1997 13:40:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA16005; Fri, 3 Jan 1997 13:40:02 -0800 (PST) Date: Fri, 3 Jan 1997 13:40:02 -0800 (PST) Message-Id: <199701032140.NAA16005@freefall.freebsd.org> To: freebsd-bugs Cc: From: George Simunovich Subject: Re: kern/2270: Hayes ESP serial card locks system as of 12/01 ke Reply-To: George Simunovich Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2270; it has been noted by GNATS. From: George Simunovich To: Bruce Evans Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/2270: Hayes ESP serial card locks system as of 12/01 ke Date: Fri, 03 Jan 1997 13:55:11 -0700 (MST) On 04-Jan-97 Bruce Evans wrote: >DDB distorts the enviroment an many ways. There is the obvious >unavoidable problem that it changes the timing. Less obviously, DDB >doesn't mask interrupts unless they are already masked, so an sio >interrupt may occur and happen to clean things up while you're >stoipped at the breakpoint at siostop. Try putting a breakpoint a >little later, after the "cli" instruction, and single stepping until >the "sti" instruction (use "x/ia" to display instructions and "s" >to single step). If this prevents the lockup, then the lockup is >almost certain to be caused by timing problems. I set the breakpoint at siostop+0x22: testb $0x2,%bl, which is immediately after the cli instruction. I then stepped through it until the sti instruction the three times it hit the breakpoint after a close. No look ups with that breakpoint either. After delete the breakpoint the look ups continued. >Try adding this to all the outb's to com->fifo. According to the docs, >it is necessary to prevent excessive input interrupts that would reduce >input efficiency to that of a 16450 (i.e., about 1/4 as efficient as an >ordinary 16550). The easiest way to tell if there are too many interrupts >iis to look at the sio interrupt count displayed by `systat -vmstat' while >input is arriving at a constant rate. I watched the "systat -vmstat" display while ftping a file from a computer on the other side of a user-mode ppp modem link. While using sio2 it showed around 3800 interrupts. While using sio1 it showed around 300. Both transfer times, as reported by ftp, where around 3.66 Kbytes/s. I then added the FIFO_DMA_MODE bit to each outb( iobase+com_fifo,...). I then did the same ftp and watched "systat -vmstat". The interrupts went down to around 100. On the other hand the transfer speed went down to 3.15 Kbytes/s. I also got an syslog error message while using "cu -l /dev/cuaa2" with the modified sio.c kernel, "sio2: 264 more interrupt-level buffer overflows (total 264)". I had to use 2400 baud, "cu -l /dev/cuaa2 -s 2400" to get rid of the error messages. I also added the FIFO_DMA_MODE bit to a version of sio.c that used the FIFO-reset outb() in siostop (original RELENG_2_2 version). No change to the lockup problem. Why would the transfer rate decrease while the number of interrupts decrease? Is it because of the buffer overflows? Why would I then only get the error messages while using cu? >I'll commit a change something like the following if we can't find a >proper fix. > >Bruce I'm wondering how hard it would be to work the ESP enhanced mode, instead of the compatibility mode, into the sio driver? Are we talking about a new driver to do this? I've been thinking about trying it, but I don't know too much about the details of architecture of the "PC" or kernel drivers. George ------------------------------------ George Simunovich From owner-freebsd-bugs Fri Jan 3 15:21:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19824 for bugs-outgoing; Fri, 3 Jan 1997 15:21:55 -0800 (PST) Received: (from guido@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA19773; Fri, 3 Jan 1997 15:21:39 -0800 (PST) Date: Fri, 3 Jan 1997 15:21:39 -0800 (PST) From: Guido van Rooij Message-Id: <199701032321.PAA19773@freefall.freebsd.org> To: bradley@dunn.org, guido, freebsd-bugs Subject: Re: bin/2265 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: su(1) does not call skeyaccess() State-Changed-From-To: open-analyzed State-Changed-By: guido State-Changed-When: Sat Jan 4 00:19:51 MET 1997 State-Changed-Why: I will try to get the skeyaccess into su asap. Further I'll try to come up with a manpage for skeyaccess(3). From owner-freebsd-bugs Fri Jan 3 15:55:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21442 for bugs-outgoing; Fri, 3 Jan 1997 15:55:20 -0800 (PST) Received: (from gpalmer@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21385; Fri, 3 Jan 1997 15:54:59 -0800 (PST) Date: Fri, 3 Jan 1997 15:54:59 -0800 (PST) From: Gary Palmer Message-Id: <199701032354.PAA21385@freefall.freebsd.org> To: gpalmer, gnats-admin, freebsd-bugs Subject: Re: bin/2366 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: libc does not consult /etc/services to figure out the dns port Responsible-Changed-From-To: gnats-admin->freebsd-bugs Responsible-Changed-By: gpalmer Responsible-Changed-When: Fri Jan 3 15:54:45 PST 1997 Responsible-Changed-Why: Misfiled PR From owner-freebsd-bugs Fri Jan 3 22:00:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA01672 for bugs-outgoing; Fri, 3 Jan 1997 22:00:11 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA01646 for ; Fri, 3 Jan 1997 22:00:04 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA04294 for ; Fri, 3 Jan 1997 19:56:30 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id WAA01464 for freebsd-bugs@freebsd.org; Fri, 3 Jan 1997 22:55:14 -0500 (EST) From: Charles Henrich Message-Id: <199701040355.WAA01464@crh.cl.msu.edu> Subject: systat -io 1 (2.2-BETA) To: freebsd-bugs@FreeBSD.ORG Date: Fri, 3 Jan 1997 22:55:14 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk systat -io 1 :number wait... Seg fault... -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-bugs Fri Jan 3 22:00:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA01888 for bugs-outgoing; Fri, 3 Jan 1997 22:00:58 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA01869 for ; Fri, 3 Jan 1997 22:00:53 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA04039 for ; Fri, 3 Jan 1997 19:03:25 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id WAA01024 for freebsd-bugs@freebsd.org; Fri, 3 Jan 1997 22:02:09 -0500 (EST) From: Charles Henrich Message-Id: <199701040302.WAA01024@crh.cl.msu.edu> Subject: iostat misbehaves To: freebsd-bugs@FreeBSD.ORG Date: Fri, 3 Jan 1997 22:02:09 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 10:01pm newstest [news] iostat sd10 tty sd20 sd21 sd22 sd0 cpu tin tout sps tps msps sps tps msps sps tps msps sps tps msps us ni sy in id 1 228 112 14 0.0 113 14 0.0 116 15 0.0 211 5 0.0 3 0 5 1 91 Where is sd10? :) -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-bugs Fri Jan 3 22:10:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA03741 for bugs-outgoing; Fri, 3 Jan 1997 22:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA03725; Fri, 3 Jan 1997 22:10:02 -0800 (PST) Resent-Date: Fri, 3 Jan 1997 22:10:02 -0800 (PST) Resent-Message-Id: <199701040610.WAA03725@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tedm@agora.rdrop.com Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA02296 for ; Fri, 3 Jan 1997 22:02:12 -0800 (PST) Received: by agora.rdrop.com with UUCP (Smail3.1.29.1 #17) id m0vgPBG-0008vdC; Fri, 3 Jan 97 22:02 PST Received: from testing.rdrop.com ([198.6.35.101]) by toybox (8.6.12/8.6.12) with ESMTP id JAA05409 for ; Fri, 3 Jan 1997 09:25:06 -0800 Received: (from root@localhost) by testing.rdrop.com (8.8.4/8.8.4) id JAA01699; Fri, 3 Jan 1997 09:25:30 -0800 (PST) Message-Id: <199701031725.JAA01699@testing.rdrop.com> Date: Fri, 3 Jan 1997 09:25:30 -0800 (PST) From: root@testmach%toybox@agora.rdrop.com Reply-To: tedm@agora.rdrop.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2367 >Category: conf >Synopsis: Buslogic SCSI driver bad probe of 742A EISA card >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 3 22:10:01 PST 1997 >Last-Modified: >Originator: Ted Mittelstaedt >Organization: Cool Dudes Club >Release: FreeBSD 2.2-CURRENT i386 >Environment: private test network I have 5 computers on a private Ethernet network in my home, the bug is with a machine with the following configuration: CompuAdd 433E MC full tower, machine was manufactured in mid 1992. Intel 486DX266 processor 8 EISA slots, one of which is a VLB slot 6 slots are busmaster slots, one of which contains SCSI card Bustek (Buslogic) revision G 742A SCSI card, firmware version 2.21 1 16MB simm Operating system shows the same bug on all versions of FreeBSD from 2.1.5 on up, I tested it with a boot floppy from 2.2 current. Following is the bootlog for the hardware configuration Jan 3 02:38:06 testing /kernel: FreeBSD 2.1.6-RELEASE #0: Mon Dec 30 11:44:09 PST 1996 Jan 3 02:38:06 testing /kernel: root@testing.teds.com:/usr/src/sys/compile/TEDS Jan 3 02:38:06 testing /kernel: CPU: i486DX (486-class CPU) Jan 3 02:38:06 testing /kernel: real memory = 16777216 (16384K bytes) Jan 3 02:38:07 testing /kernel: avail memory = 14929920 (14580K bytes) Jan 3 02:38:07 testing /kernel: eisa0: Jan 3 02:38:07 testing /kernel: Probing for devices on the EISA bus Jan 3 02:38:07 testing /kernel: bt0: at 0x330-0x333 0x1c00-0x1cff irq 9 on eisa0 slot 1 Jan 3 02:38:07 testing /kernel: bt0: Bt742A/G0-(32bit) bus Jan 3 02:38:07 testing /kernel: bt0: reading board settings, busmastering, int=9 Jan 3 02:38:07 testing /kernel: bt0: version 2.21, async only, parity, 64 mbxs, 32 ccbs Jan 3 02:38:07 testing /kernel: bt0: Not using Strict Round robin scheme Jan 3 02:38:07 testing /kernel: bt0 waiting for scsi devices to settle Jan 3 02:38:08 testing /kernel: (bt0:0:0): "DEC DSP5200S T384" type 0 fixed SCSI 2 Jan 3 02:38:08 testing /kernel: sd0(bt0:0:0): Direct-Access 1908MB (3907911 512 byte sectors) Jan 3 02:38:08 testing /kernel: (bt0:4:0): "TOSHIBA CD-ROM XM-3401TA 3312" type 5 removable SCSI 2 Jan 3 02:38:08 testing /kernel: cd0(bt0:4:0): CD-ROM Jan 3 02:38:08 testing /kernel: cd0(bt0:4:0): NOT READY asc:3a,0 Medium not present Jan 3 02:38:08 testing /kernel: can't get the size Jan 3 02:38:08 testing /kernel: Jan 3 02:38:08 testing /kernel: (bt0:6:0): "ARCHIVE ANCDA 2800 28889 -900" type 1 removable SCSI 1 Jan 3 02:38:08 testing /kernel: st0(bt0:6:0): Sequential-Access density code 0x0, drive empty Jan 3 02:38:09 testing /kernel: Probing for devices on the ISA bus: Jan 3 02:38:09 testing /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jan 3 02:38:09 testing /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jan 3 02:38:09 testing /kernel: ed0 at 0x300-0x31f irq 10 maddr 0xd8000 msize 16384 on isa Jan 3 02:38:09 testing /kernel: ed0: address 00:00:c0:1f:cf:23, type WD8013EP (16 bit) Jan 3 02:38:09 testing /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jan 3 02:38:09 testing /kernel: sio0: type 16450 Jan 3 02:38:09 testing /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jan 3 02:38:09 testing /kernel: sio1: type 16450 Jan 3 02:38:09 testing /kernel: sio2 not found at 0x3e8 Jan 3 02:38:10 testing /kernel: sio3: disabled, not probed. Jan 3 02:38:10 testing /kernel: lpt0 at 0x378-0x37f irq 7 on isa Jan 3 02:38:10 testing /kernel: lpt0: Interrupt-driven port Jan 3 02:38:10 testing /kernel: lp0: TCP/IP capable interface Jan 3 02:38:10 testing /kernel: pca0 on motherboard Jan 3 02:38:10 testing /kernel: pca0: PC speaker audio driver Jan 3 02:38:11 testing /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jan 3 02:38:11 testing /kernel: fdc0: unknown IC type a0 Jan 3 02:38:11 testing /kernel: fd0: 1.44MB 3.5in Jan 3 02:38:11 testing /kernel: fd1: 1.2MB 5.25in Jan 3 02:38:11 testing /kernel: bt: unit number (1) too high Jan 3 02:38:11 testing /kernel: bt1 not found at 0x330 Jan 3 02:38:11 testing /kernel: npx0 on motherboard Jan 3 02:38:11 testing /kernel: npx0: INT 16 interface >Description: The problem is that if I EISA-config the SCSI adapter to any IRQ number other than Interrupt 9, the machine boots, but as soon as the kernel is loaded and switches over to the compiled-in Buslogic driver in the kernel the SCSI system times out attempting to read the disk. Also, the boot probe shows the interrupt probed at 9. An example of this when the card is configured to use Interrupt 12 (it's default) follows: -------snip snip------------ Jan 3 02:38:07 testing /kernel: avail memory = 14929920 (14580K bytes) Jan 3 02:38:07 testing /kernel: eisa0: Jan 3 02:38:07 testing /kernel: Probing for devices on the EISA bus Jan 3 02:38:07 testing /kernel: bt0: at 0x330-0x333 0x1c00-0x1cff irq 9 on eisa0 slot 1 Jan 3 02:38:07 testing /kernel: bt0: Bt742A/G0-(32bit) bus Jan 3 02:38:07 testing /kernel: bt0: reading board settings, busmastering, int=12 Jan 3 02:38:07 testing /kernel: bt0: version 2.21, async only, parity, 64 mbxs, 32 ccbs ------------snip snip--------- As you see, the first probe reads the wrong IRQ number of 9, while the second probe reads the correct IRQ number of 12. Unfortunately, the driver thinks that the IRQ is 9. The related problem to this is that the probe identifies the card as a 742xB card, when in reality it is a 742A card. This is probably because the /usr/src/sys/i386/eisa/bt74x.c file doesen't have a separate test for the 742A card. >How-To-Repeat: EISA-config the Buslogic 742A as any IRQ other than 9 I don't believe that this problem occurs on the PCI Buslogic cards, only on the EISA card (742) the reason is that one of my other machines is a PCI machine with a Buslogic PCI scsi adapter in it, and I test-booted FreeBSD on it and it worked. This problem DIDN'T occur with FreeBSD version 1.1.5.1 on this machine! This problem affects the installation floppy, what happens is that the system boots, then hangs for a long time. Very annoying! >Fix: I am getting by by EISA-configing the SCSI adapter to Interrupt 9, which makes the real IRQ in agreement with the wrongly probed IRQ number. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Jan 3 23:50:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA04571 for bugs-outgoing; Fri, 3 Jan 1997 23:50:15 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA04539; Fri, 3 Jan 1997 23:50:08 -0800 (PST) Resent-Date: Fri, 3 Jan 1997 23:50:08 -0800 (PST) Resent-Message-Id: <199701040750.XAA04539@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, tbeery@lanl.gov Received: from tchrom.lanl.gov (tchrom.lanl.gov [128.165.103.73]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA04462 for ; Fri, 3 Jan 1997 23:48:18 -0800 (PST) Received: (from beery@localhost) by tchrom.lanl.gov (8.7.5/8.7.3) id AAA00871; Sat, 4 Jan 1997 00:47:29 -0700 (MST) Message-Id: <199701040747.AAA00871@tchrom.lanl.gov> Date: Sat, 4 Jan 1997 00:47:29 -0700 (MST) From: tbeery@lanl.gov Reply-To: tbeery@lanl.gov To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/2368: getty/login hangup Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2368 >Category: bin >Synopsis: serial line logins "freeze" during login prompt >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jan 3 23:50:03 PST 1997 >Last-Modified: >Originator: Thomas Beery >Organization: Los Alamos National Labratory >Release: FreeBSD 2.1-STABLE i386 >Environment: FreeBSD 2.1.5 386 and P100 >Description: I set up for dialup access as decribed in section 11.4 of the FreeBSD Handbook. When I would dial-in sometimes it would work, other times, it would hangup the phone seconds after sending the login prompt. >How-To-Repeat: Edit /etc/ttys to allow serial logins. (I used std.38400), kill -1 1, Edit /etc/remote , Use TIP to issue modem commands , and dial in) >Fix: create .tiprc file with entry "parity=none" I don't know how much of this problem is caused by tip not being a "correct program" as decribed in the sio (4) man pages Kermit seems to be better behaved/able to detect getty settings, but is not as readily available, ie requires compilation. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 03:00:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA11713 for bugs-outgoing; Sat, 4 Jan 1997 03:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA11706; Sat, 4 Jan 1997 03:00:02 -0800 (PST) Date: Sat, 4 Jan 1997 03:00:02 -0800 (PST) Message-Id: <199701041100.DAA11706@freefall.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR conf/2367; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: tedm@agora.rdrop.com Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Date: Sat, 4 Jan 1997 11:40:30 +0100 As root@testmach%toybox, UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR. wrote: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Eeek! :) > Jan 3 02:38:07 testing /kernel: bt0: at 0x330-0x333 0x1c00-0x1cff irq 9 on eisa0 slot 1 > Jan 3 02:38:07 testing /kernel: bt0: Bt742A/G0-(32bit) bus It's been a while ago that i've been using a Bt742A. I remember that it wasn't totally unproblematical for me either. . turn off ISA DMA emulation, . use level-triggered IRQ, and with FreeBSD > 2.1: > Jan 3 02:38:11 testing /kernel: bt: unit number (1) too high > Jan 3 02:38:11 testing /kernel: bt1 not found at 0x330 ...disable the ISA Buslogic driver. Since the EISA device will also respond on the ISA addresses, the driver gets confused otherwise. > This problem DIDN'T occur with FreeBSD version 1.1.5.1 on this machine! Because it didn't have EISA controller code, so the card has been handled as some sort of an ``extended ISA'' device. There was definately no EISA autoprobing in FreeBSD <= 2.1R, but it is there now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jan 4 03:22:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA12227 for bugs-outgoing; Sat, 4 Jan 1997 03:22:37 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA12222 for ; Sat, 4 Jan 1997 03:22:29 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA11198; Sat, 4 Jan 1997 12:21:38 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA04256; Sat, 4 Jan 1997 12:21:38 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id MAA19845; Sat, 4 Jan 1997 12:03:39 +0100 (MET) Message-ID: Date: Sat, 4 Jan 1997 12:03:39 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs@FreeBSD.ORG Cc: henrich@crh.cl.msu.edu (Charles Henrich) Subject: Re: systat -io 1 (2.2-BETA) References: <199701040355.WAA01464@crh.cl.msu.edu> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701040355.WAA01464@crh.cl.msu.edu>; from Charles Henrich on Jan 3, 1997 22:55:14 -0500 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > systat -io 1 > > :number > > wait... > > Seg fault... Perhaps only on your 55-disk system? It works fine on my copy of 2.2-BETA, but that's admittedly only with a single disk. Can you run gdb on it? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jan 4 08:50:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA01781 for bugs-outgoing; Sat, 4 Jan 1997 08:50:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA01768; Sat, 4 Jan 1997 08:50:03 -0800 (PST) Resent-Date: Sat, 4 Jan 1997 08:50:03 -0800 (PST) Resent-Message-Id: <199701041650.IAA01768@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, markd@grizzly.com Received: from scruz.net (nic.scruz.net [165.227.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA01315 for ; Sat, 4 Jan 1997 08:44:50 -0800 (PST) Received: from osprey.grizzly.com by scruz.net (8.7.3/1.34) id IAA05485; Sat, 4 Jan 1997 08:44:45 -0800 (PST) Received: (from root@localhost) by osprey.grizzly.com (8.8.4/8.7.3) id IAA00351; Sat, 4 Jan 1997 08:45:17 -0800 (PST) Message-Id: <199701041645.IAA00351@osprey.grizzly.com> Date: Sat, 4 Jan 1997 08:45:17 -0800 (PST) From: markd@grizzly.com Reply-To: markd@grizzly.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/2371: SCSI disk corruption Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2371 >Category: kern >Synopsis: SCSI disk corruption >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 4 08:50:01 PST 1997 >Last-Modified: >Originator: Mark Diekhans >Organization: >Release: FreeBSD 2.2-BETA_A i386 >Environment: FreeBSD 2.2-BETA_A #0: Sun Dec 29 20:13:01 PST 1996 markd@osprey.grizzly.com:/usr/src/sys/compile/OSPREY Calibrating clock(s) relative to mc146818A clock ... i586 clock: 166188714 Hz, i8254 clock: 1193152 Hz CPU: Pentium (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 64073728 (62572K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 0 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 1 int a irq 10 on pci0:9 ahc0 rev 0 int a irq 11 on pci0:12 ahc0: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "HP C3725S 6039" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "SEAGATE ST32550N 0015" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2047MB (4194058 512 byte sectors) ahc0:A:5: refuses syncronous negotiation. Using asyncronous transfers (ahc0:5:0): "IOMEGA ZIP 100 D.09" type 0 removable SCSI 2 sd2(ahc0:5:0): Direct-Access sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(ahc0:5:0): NOT READY asc:3a,0 Medium not present sd2: could not get size 0MB (0 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 2 buttons? fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface AHC options: controller ahc0 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO >Description: As with many reports of disk corruption, this might not be very useful due to lack of solid data... System was discovered crashed, on reboot, the second scsi disk was corrupt. Fsck reported a large number of errors and it was eventually run with -y. When remounted, all files where in lost+found. The last major activity before the crash was formatting of sd2, an IOMega Zip drive. SCSI format, partition and newfs had generated the following message: Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): UNIT ATTENTION asc:28,0 Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): Not ready to ready transition, medium may have changed Jan 3 22:47:13 osprey /kernel: Debugger("sdopen: no slices") called. Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB Jan 3 22:47:13 osprey /kernel: sd2 could not mode sense (4). Using ficticious geometry Jan 3 22:47:13 osprey /kernel: sd2: invalid primary partition table: no magic The system was alive for two more hours, but only doing routine tasks. The day befofe the following errors where reported in the log: Jan 2 02:34:51 osprey /kernel: st0(ahc0:2:0): timed out in command phase, SCSISIGI == 0x84 Jan 2 02:34:51 osprey /kernel: SEQADDR == 0x5a Jan 2 02:34:51 osprey /kernel: st0(ahc0:2:0): abort message in message buffer Jan 2 02:34:53 osprey /kernel: st0(ahc0:2:0): timed out in dataout phase, SCSISIGI == 0x0 Jan 2 02:34:53 osprey /kernel: SEQADDR == 0xe Jan 2 02:34:53 osprey /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jan 2 02:34:53 osprey /kernel: st0(ahc0:2:0): Target Busy Jan 2 02:34:53 osprey /kernel: st0(ahc0:2:0): Target Busy Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): UNIT ATTENTION info?:4020040 asc:29,0 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred Jan 2 02:34:53 osprey /kernel: , retries:4 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:34:53 osprey /kernel: , retries:3 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): ABORTED COMMAND info?:4020040 asc:4e,0 Overlapped commands attempted Jan 2 02:34:53 osprey /kernel: , retries:2 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:34:53 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:34:53 osprey /kernel: , retries:1 Jan 2 02:35:03 osprey /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Jan 2 02:35:03 osprey /kernel: SEQADDR == 0xb Jan 2 02:35:17 osprey /kernel: SEQADDR == 0xf Jan 2 02:35:17 osprey /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jan 2 02:35:17 osprey /kernel: spec_getpages: I/O read error Jan 2 02:35:17 osprey /kernel: vm_fault: pager input (probably hardware) error, PID 4026 failure Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:17 osprey /kernel: , retries:4 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:17 osprey /kernel: , retries:3 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:17 osprey /kernel: , retries:2 Jan 2 02:35:17 osprey /kernel: pid 4026 (bash), uid 0: exited on signal 11 (core dumped) Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Jan 2 02:35:17 osprey /kernel: SEQADDR == 0xf Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): timed out in dataout phase, SCSISIGI == 0x0 Jan 2 02:35:17 osprey /kernel: SEQADDR == 0xe Jan 2 02:35:17 osprey /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): UNIT ATTENTION info?:4020040 asc:29,0 Jan 2 02:35:17 osprey /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred Jan 2 02:35:17 osprey /kernel: , retries:3 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:18 osprey /kernel: , retries:2 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:18 osprey /kernel: , retries:1 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 Jan 2 02:35:18 osprey /kernel: sd0(ahc0:0:0): Logical unit is in process of becoming ready Jan 2 02:35:18 osprey /kernel: , FAILURE Jan 2 02:36:42 osprey /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 Jan 2 02:36:42 osprey /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Jan 2 02:36:42 osprey /kernel: , retries:4 Note: AHC_TAGENABLE and AHC_SCBPAGING_ENABLE and AHC_ALLOW_MEMIO where enabled. Since I gave up driver writing before SCSI was invented, I can't very useful in the analysis. >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 08:52:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA02008 for bugs-outgoing; Sat, 4 Jan 1997 08:52:22 -0800 (PST) Received: from icarus.cc.uic.edu (rory@ICARUS-FDDI.CC.UIC.EDU [128.248.100.53]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA02003 for ; Sat, 4 Jan 1997 08:52:20 -0800 (PST) Received: from localhost (rory@localhost) by icarus.cc.uic.edu (8.8.3/8.8.3) with SMTP id KAA27809 for ; Sat, 4 Jan 1997 10:53:43 -0600 (CST) X-Authentication-Warning: icarus.cc.uic.edu: rory owned process doing -bs Date: Sat, 4 Jan 1997 10:53:43 -0600 (CST) From: Rory Imua Lampert X-Sender: rory@icarus.cc.uic.edu To: freebsd-bugs@freebsd.org Subject: Re: AMD 120 page fault during boot up In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Worked great, I clocked it at 33 and as a "Enhanced AMD Dx4" and I'm in X right now...haven't tried any heavy compiling but it seems that trick worked. One thing I've noticed is that the cpu runs VERY cool and probably wouldn't need a fan...but I'll throw it on just in case :> Thanks much, Rory Imua Lampert On Fri, 3 Jan 1997, Mark Hannon wrote: > In article , > rory@uic.edu (Rory Imua Lampert) writes: > > I did...well something like that. A friend had the exact same motherboard > > and cpu. So I put my cpu and ram in his motherboard, it worked just > > fine, with another hitch...He was running linux. We tried with my cpu and > > his ram, my cpu and my ram, his cpu and my ram and all variations worked. > > > > -Rory > > > > On Thu, 26 Dec 1996, Jordan K. Hubbard wrote: > > > >> > Does anyone have any clue as to what I should try next? > >> > >> Try swapping that CPU. > >> > > My suggestion would be to change the motherboard speed down to > 33MHz and run the chip as a 4/100 instead of 4/120. I had > heaps of problems with a 4/120 chip, changed caches, BIOS settings, > etc. only thing that worked was to slow it down. > > Rgds/mark > > -- > +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ > | Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au| > | Melbourne, | PGP key available by fingering | epamha@epa.ericsson.se | > | Australia | seeware@melbourne.DIALix.oz.au | | > +-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ > From owner-freebsd-bugs Sat Jan 4 10:57:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA08222 for bugs-outgoing; Sat, 4 Jan 1997 10:57:22 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA08216 for ; Sat, 4 Jan 1997 10:57:20 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id NAA05728; Sat, 4 Jan 1997 13:57:14 -0500 (EST) From: Charles Henrich Message-Id: <199701041857.NAA05728@crh.cl.msu.edu> Subject: Re: systat -io 1 (2.2-BETA) To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 4 Jan 1997 13:57:14 -0500 (EST) Cc: freebsd-bugs@FreeBSD.ORG In-Reply-To: from J Wunsch at "Jan 4, 97 12:03:39 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Charles Henrich wrote: > > > systat -io 1 > > > > :number > > > > wait... > > > > Seg fault... > > Perhaps only on your 55-disk system? It works fine on my copy of > 2.2-BETA, but that's admittedly only with a single disk. > > Can you run gdb on it? Okay, I tracked down my two recent problems with iostat and systat, for some nasty reason the kernel is #defining the max number of disks to keep stats on (grumble grumble grumble) DK_NDRIVE, and its set to 8, I reset it to 16, recompiled kernel and related binaries (iostat/systat) and now both tools notice all 13 of my disks and systat no longer dumps core. Although it is odd that it does.. I'll have too look further, but the problem may have been when I fed systat a drive name that it didnt find in the kernel list it barfed.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-bugs Sat Jan 4 11:10:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA09318 for bugs-outgoing; Sat, 4 Jan 1997 11:10:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA09311; Sat, 4 Jan 1997 11:10:02 -0800 (PST) Date: Sat, 4 Jan 1997 11:10:02 -0800 (PST) Message-Id: <199701041910.LAA09311@freefall.freebsd.org> To: freebsd-bugs Cc: From: tedm@agora.rdrop.com Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Reply-To: tedm@agora.rdrop.com Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR conf/2367; it has been noted by GNATS. From: tedm@agora.rdrop.com To: joerg_wunsch@uriah.heep.sax.de, FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version Date: Fri, 03 Jan 97 21:45:09 +0900 //---------------------------------------------------------------------------- // Ted Mittelstaedt See my "Network Community" columns online // tedm@agora.rdrop.com at http://www.computerbits.com // tedm%toybox@agora.rdrop.com //--- forwarded letter ------------------------------------------------------- > X-Mailer: Mutt 0.55-PL10 > MIME-Version: 1.0 > Date: Sat, 04 Jan 97 11:40:30 +0100 > From: j@uriah.heep.sax.de > To: tedm@agora.rdrop.com > Reply-To: joerg_wunsch@uriah.heep.sax.de > Cc: FreeBSD-gnats-submit@FreeBSD.org > Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version > > As root@testmach%toybox, UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR. wrote: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Eeek! :) > Looks like I munged that one. I just threw together the mail routing quickly, the machine is actually not truly reachable yet. The address should have been: toybox!testmach!root@agora.rdrop.com but it would have bounced anyhow. Besides that, the address isin't truly legal. (the mailer on agora.rdrop.com could have made sense of it but that's it) > > Jan 3 02:38:07 testing /kernel: bt0: at 0x330-0x333 0x1c00-0x1cff irq 9 on eisa0 slot 1 > > Jan 3 02:38:07 testing /kernel: bt0: Bt742A/G0-(32bit) bus > > It's been a while ago that i've been using a Bt742A. I remember that > it wasn't totally unproblematical for me either. Kind of ironic, since the monolithic Buslogic driver was derived from driver code from the 742A EISA card! > > . turn off ISA DMA emulation, > . use level-triggered IRQ, ISA DMA emulation was turned off. I had it to edge-triggered interrupts, but setting to level-trigger doesen't make any difference. > > and with FreeBSD > 2.1: > > > Jan 3 02:38:11 testing /kernel: bt: unit number (1) too high > > Jan 3 02:38:11 testing /kernel: bt1 not found at 0x330 > > ...disable the ISA Buslogic driver. Since the EISA device will also > respond on the ISA addresses, the driver gets confused otherwise. > I tried disabling the bt driver, this did make the above error message about bt unit number 1 too high go away, and the kernel did boot properly. This is probably something that should go into the install FAQ, is the same problem present with the Adaptec 1740 card responding as a 1540 as well? I also tried switching the interrupt to IRQ12 with the bt driver disabled, the EISA probe _still_ thinks that the interrupt is at IRQ 9, and the boot process halts. So, despite the disabled bt ISA driver, the EISA driver is still not correctly autoprobing. The annoying thing is that when the driver reads the actual card settings, it comes up with IRQ12, but it is still using the initial probe of IRQ 9 from the EISA bus which is wrong. > > This problem DIDN'T occur with FreeBSD version 1.1.5.1 on this machine! > > Because it didn't have EISA controller code, so the card has been > handled as some sort of an ``extended ISA'' device. There was > definately no EISA autoprobing in FreeBSD <= 2.1R, but it is there > now. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-bugs Sat Jan 4 12:20:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA13270 for bugs-outgoing; Sat, 4 Jan 1997 12:20:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA13254; Sat, 4 Jan 1997 12:20:03 -0800 (PST) Resent-Date: Sat, 4 Jan 1997 12:20:03 -0800 (PST) Resent-Message-Id: <199701042020.MAA13254@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, wlloyd@tolstoy.mpd.ca Received: from tolstoy.mpd.ca (wlloyd.HIP.CAM.ORG [199.84.42.209]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA12972 for ; Sat, 4 Jan 1997 12:15:37 -0800 (PST) Received: (from wlloyd@localhost) by tolstoy.mpd.ca (8.7.5/8.7.3) id PAA29211; Sat, 4 Jan 1997 15:17:38 -0500 (EST) Message-Id: <199701042017.PAA29211@tolstoy.mpd.ca> Date: Sat, 4 Jan 1997 15:17:38 -0500 (EST) From: William Lloyd Reply-To: wlloyd@tolstoy.mpd.ca To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2372: Changes to mail.sgml Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2372 >Category: docs >Synopsis: Changes to mail.sgml >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 4 12:20:01 PST 1997 >Last-Modified: >Originator: William Lloyd >Organization: William Lloyd (wlloyd@mpd.ca) >Release: FreeBSD 2.1.5-STABLE i386 >Environment: >Description: Second stab at mail.sgml >How-To-Repeat: >Fix: Index: mail.sgml =================================================================== RCS file: /usr/ncvs/src/share/doc/handbook/mail.sgml,v retrieving revision 1.4 diff -c -r1.4 mail.sgml *** mail.sgml 1996/12/31 21:54:17 1.4 --- mail.sgml 1997/01/04 20:03:06 *************** *** 1,4 **** ! Electronic Mail - Basic Information

Contributed by &a.wlloyd;. !

E-mail, as simple as the concept sounds, can be extremely complicated. If you plan on doing anything beyond setting up a simple one machine E-mail system, you should buy and refer to a book on Sendmail. - Introduction

! These are the major programs or components of an e-mail exchange. ! User program !

This is a program like sendmail or delivering it over TCP to your mailhost. ! Transport Agent - Sendmail !

Usually this program is /etc/sysconfig . It is best to leave it on unless you have a specific reason to want it off. Ie: Firewall !

! You should be aware that sendmail is a potential weak link in a secure site. Some versions of sendmail have known security problems. ! !

sendmail will look up in the DNS to determine the actual host that will receive mail for the destination. !

Sendmail will take the message from the local queue and deliver it across the Internet to another sendmail on the receivers computer. !

Sendmail will also be able to do the reverse. It will accept messages and save them on your local machine. ! POP Servers

This program gets the mail from your mailbox and gives it to your browser. If you want to run a POP server on your computer, you will need to do 2 things. ! Get pop software from the ports or packages collection. ! Modify /etc/inetd.conf to load POP server. ! The pop program you get will have instructions with it. Read them. ! ! Configuration

! As your FreeBSD system comes "out of the box" you should be able to send e-mail to external hosts. The problem is no mail will be able to get back to your host. This is not a problem if you are willing to make sure you hand edit the automatic reply to address every time you send a message.

! It is relatively simple to get another host to receive your e-mail under the same username. You can then pick it up over POP or telnet. ! A user account with the SAME USERNAME should exist on both machines. Please use /nonexistent the user will not be allowed to login. ! The mailhost that you will be using must be designated the Mail exchange for your host. This must be arranged in DNS (ie BIND, named). Please refer to a Networking book for more information. ! You basically need to add these lines in your DNS server. ! ! myhost.smalliap.com A xxx.xxx.xxx.xxx ; Your ip ! MX 10 smtp.smalliap.com ; your mailhost ! You cannot do this yourself unless you are running a DNS server. If you do not want to run a DNS server, get somebody else like your Internet Provider to do it. ! This will redirect mail for your host to the MX (Mail eXchange) host. It does not matter what machine the A record points to, the mail will be sent to the MX host. !

! This feature is used to implement Virtual Hosting. !

Example !

! I have a customer with domain foo.bar and I want all mail for foo.bar to be sent to my machine smtp.smalliap.com. You must make an entry in your DNS server like: ! ! foo.bar MX 10 smtp.smalliap.com ; your mailhost - The A record is not needed if you only want e-mail for the domain. ! On the mailhost that actually accepts mail for final delivery to a mailbox, sendmail must be told what hosts it will be accepting mail for. !

Add myhost.smalliap.com to /etc/sendmail.cw (if you are using FEATURE(use_cw_file)), or add a "Cw myhost.smalliap.com" line to /etc/sendmail.cf. ! !

To actually receive mail on your host, you need to have the MX entry above changed to point to your host. You also move the Cw line above in your sendmail.cf. ! !

! This is a Bad Idea if your connection to the Internet is not permanent. Mail will bounce.

! If you plan on doing anything serious with . ! ! FAQ ! ! Why do I have to use the FQDN for hosts on my site? !

! You will probably find that the host is actually in a different ! domain; for example, if you are in foo.bar.edu and you wish to reach ! a host called ``mumble'' in the bar.edu domain, you will have to ! refer to it by the fully-qualified domain name, ``mumble.bar.edu'', ! instead of just ``mumble''. !

! Traditionally, this was allowed by BSD BIND resolvers. However ! the current version of BIND that ships with FreeBSD ! no longer provides default abbreviations for non-fully ! qualified domain names other than the domain you are in. ! So an unqualified host mumble must either be found ! as mumble.foo.bar.edu, or it will be searched for ! in the root domain. !

! This is different from the previous behavior, where the ! search continued across mumble.bar.edu, and ! mumble.edu. Have a look at RFC 1535 for why this ! was considered bad practice, or even a security hole. !

! As a good workaround, you can place the line !

! search foo.bar.edu bar.edu !

! instead of the previous !

! domain foo.bar.edu !

! into your /etc/resolv.conf. However, make sure ! that the search order does not go beyond the ``boundary ! between local and public administration'', as RFC 1535 ! calls it. ! ! Sendmail says ``mail loops back to myself'' !

! This is answered in the sendmail FAQ as follows:- ! ! * I am getting "Local configuration error" messages, such as: ! 553 relay.domain.net config error: mail loops back to myself ! 554 ... Local configuration error ! How can I solve this problem? ! You have asked mail to the domain (e.g., domain.net) to be ! forwarded to a specific host (in this case, relay.domain.net) ! by using an MX record, but the relay machine does not recognize ! itself as domain.net. Add domain.net to /etc/sendmail.cw ! (if you are using FEATURE(use_cw_file)) or add "Cw domain.net" ! to /etc/sendmail.cf. ! !

! The sendmail FAQ is in /usr/src/usr.sbin/sendmail ! and is recommended reading if you want to do any ! ``tweaking'' of your mail setup. ! ! How do I use sendmail for mail delivery with UUCP?

The sendmail configuration that ships with FreeBSD is suited for sites that connect directly to the Internet. --- 9,160 ---- &a.wlloyd; 24 Nov 1996, (c) 1996 ! This section contains basic information on setting up Elecronic Mail on your new FreeBSD box. --> Electronic Mail

Contributed by &a.wlloyd;. !

Electronic Mail configuration is the subject of many books. If you plan on doing anything beyond setting up one mailhost for your network, you need industrial strength help. ! ! Some parts of E-Mail configuration are controlled in the Domain Name System (DNS). If you are going to run your own own DNS server check out /etc/namedb and ' man -k named ' for more information. ! ! Basic Information

! These are the major programs involved in an E-Mail exchange. ! A User program !

This is a program like sendmail or delivering it over TCP. ! ! Mailhost Server Daemon !

Usually this program is /etc/sysconfig . It is best to leave it on, unless you have a specific reason to want it off. Example: You are building a . ! !

You should be aware that sendmail is a potential weak link in a secure site. Some versions of sendmail have known security problems. ! !

sendmail does two jobs. It looks after delivering and receiving mail. ! ! If needs to delivery mail off your site it will look up in the DNS to determine the actual host that will receive mail for the destination. ! !

If it is acting as a delivery agent DNS - Name Service !

The Domain Name System and its daemon POP Servers

This program gets the mail from your mailbox and gives it to your browser. If you want to run a POP server on your computer, you will need to do 2 things. ! Get pop software from the that can be found in /usr/ports ! or packages collection. This handbook section has a complete reference on the system. ! Modify /etc/inetd.conf to load the POP server. ! The pop program will have instructions with it. Read them. ! ! ! ! Configuration ! ! Basic !

! As your FreeBSD system comes "out of the box"[TM], you should be able to send E-mail to external hosts as long as you have /etc/resolv.conf setup or are running a name server. ! If you want to have mail for your host delivered to your specific host,there are two methods: !

! - Run a name server ( man -k named ) and have your own domain smallminingco.com

! - Get mail delivered to the current DNS name for your host. Ie: dorm6.ahouse.school.edu

! No matter what option you choose, to have mail delivered directly to your host, you must be a full Internet host. You must have a permanent IP address. IE: NO dynamic PPP. If you are behind a firewall, the firewall must be passing on smtp traffic to you. From /etc/services ! ! smtp 25/tcp mail #Simple Mail Transfer ! ! If you want to receive mail at your host itself, you must make sure that the DNS MX entry points to your hosts address, or there is no MX entry for your DNS name. ! Try this ! ! newbsdbox# hostname ! newbsdbox.freebsd.org ! newbsdbox# host newbsdbox.freebsd.org ! newbsdbox.freebsd.org has address 204.216.27.xx ! ! If that is all that comes out for your machine, mail directry to root@newbsdbox.freebsd.org will work no problems. ! If instead, you have this ! ! newbsdbox# host newbsdbox.freebsd.org ! newbsdbox.FreeBSD.org has address 204.216.27.xx ! newbsdbox.FreeBSD.org mail is handled (pri=10) by freefall.FreeBSD.org + All mail sent to your host directly will end up on freefall, under the same username. ! This information is setup in your domain name server. This should be the same host that is listed as your primary nameserver in /etc/resolv.conf ! The DNS record that carries mail routing information is the Mail eXchange entry. If no MX entry exists, mail will be delivered directly to the host by way of the Address record. ! The MX entry for freefall.freebsd.org at one time. ! ! freefall MX 30 mail.crl.net ! freefall MX 40 agora.rdrop.com ! freefall HINFO Pentium FreeBSD ! freefall MX 10 freefall.FreeBSD.org ! freefall MX 20 who.cdrom.com ! freefall A 204.216.27.xx ! freefall CNAME www.FreeBSD.org ! freefall has many MX entries. The lowest MX number gets the mail in the end. The others will queue mail temporarily, if freefall is busy or down. ! Alternate MX sites should have seperate connections to the internet, to be most usefull. An Internet Provider or other friendly site can provide this service. + dig, nslookup, and host are your friends. + + Mail for your Domain (Network).

! To setup up a network mailhost, you need to direct the mail from arriving at all the workstations. In other words, you want to hijack all mail for *.smallminingco.com and divert it to one machine, your mailhost. ! The network users on their workstations will most likely pick up their mail over POP or telnet. ! A user account with the SAME USERNAME should exist on both machines. Please use /nonexistant the user will not be allowed to login. ! The mailhost that you will be using must be designated the Mail eXchange for each workstation. This must be arranged in DNS (ie BIND, named). Please refer to a Networking book for indepth information. ! You basically need to add these lines in your DNS server. ! ! pc24.smallminingco.com A xxx.xxx.xxx.xxx ; Workstation ip ! MX 10 smtp.smallminingco.com ; Your mailhost ! ! You cannot do this yourself unless you are running a DNS server. If you do not want to run a DNS server, get somebody else like your Internet Provider to do it. ! This will redirect mail for the workstation to the Mail eXchange host. It does not matter what machine the A record points to, the mail will be sent to the MX host. !

! This feature is used to implement Virtual E-Mail Hosting. !

Example !

! I have a customer with domain foo.bar and I want all mail for foo.bar to be sent to my machine smtp.smalliap.com. You must make an entry in your DNS server like: ! ! foo.bar MX 10 smtp.smalliap.com ; your mailhost ! ! The A record is not needed if you only want E-Mail for the domain. IE: Don't expect ping foo.bar to work unless an Address record for foo.bar exists as well. ! On the mailhost that actually accepts mail for final delivery to a mailbox, sendmail must be told what hosts it will be accepting mail for. !

Add pc24.smallminingco.com to /etc/sendmail.cw (if you are using FEATURE(use_cw_file)), or add a "Cw myhost.smalliap.com" line to /etc/sendmail.cf !

! If you plan on doing anything serious with . + + + Setting up UUCP. +

Stolen from the FAQ.

The sendmail configuration that ships with FreeBSD is suited for sites that connect directly to the Internet. *************** *** 294,301 **** > ^D j@uriah 192% ! How can I do e-mail with a dialup PPP host

You want to connect a FreeBSD box on a lan, to the Internet. The FreeBSD box will be a mail gateway for the lan. The PPP connection is non-dedicated. --- 297,372 ---- > ^D j@uriah 192% + ! FAQ ! !

Migration from FAQ. ! ! ! ! Why do I have to use the FQDN for hosts on my site? !

! You will probably find that the host is actually in a different ! domain; for example, if you are in foo.bar.edu and you wish to reach ! a host called ``mumble'' in the bar.edu domain, you will have to ! refer to it by the fully-qualified domain name, ``mumble.bar.edu'', ! instead of just ``mumble''. !

! Traditionally, this was allowed by BSD BIND resolvers. However ! the current version of BIND that ships with FreeBSD ! no longer provides default abbreviations for non-fully ! qualified domain names other than the domain you are in. ! So an unqualified host mumble must either be found ! as mumble.foo.bar.edu, or it will be searched for ! in the root domain. !

! This is different from the previous behavior, where the ! search continued across mumble.bar.edu, and ! mumble.edu. Have a look at RFC 1535 for why this ! was considered bad practice, or even a security hole. !

! As a good workaround, you can place the line !

! search foo.bar.edu bar.edu !

! instead of the previous ! !

! domain foo.bar.edu !

! into your /etc/resolv.conf. However, make sure ! that the search order does not go beyond the ``boundary ! between local and public administration'', as RFC 1535 ! calls it. ! ! ! ! Sendmail says ``mail loops back to myself'' !

! This is answered in the sendmail FAQ as follows:- ! ! * I am getting "Local configuration error" messages, such as: ! ! 553 relay.domain.net config error: mail loops back to myself ! 554 ... Local configuration error ! ! How can I solve this problem? ! ! You have asked mail to the domain (e.g., domain.net) to be ! forwarded to a specific host (in this case, relay.domain.net) ! by using an MX record, but the relay machine does not recognize ! itself as domain.net. Add domain.net to /etc/sendmail.cw ! (if you are using FEATURE(use_cw_file)) or add "Cw domain.net" ! to /etc/sendmail.cf. ! !

! The sendmail FAQ is in /usr/src/usr.sbin/sendmail ! and is recommended reading if you want to do any ! ``tweaking'' of your mail setup. ! ! ! How can I do E-Mail with a dialup PPP host?

You want to connect a FreeBSD box on a lan, to the Internet. The FreeBSD box will be a mail gateway for the lan. The PPP connection is non-dedicated. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 14:30:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20221 for bugs-outgoing; Sat, 4 Jan 1997 14:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA20215; Sat, 4 Jan 1997 14:30:01 -0800 (PST) Resent-Date: Sat, 4 Jan 1997 14:30:01 -0800 (PST) Resent-Message-Id: <199701042230.OAA20215@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, wlloyd@tolstoy.mpd.ca Received: from tolstoy.mpd.ca (wlloyd.HIP.CAM.ORG [199.84.42.209]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18123 for ; Sat, 4 Jan 1997 14:25:50 -0800 (PST) Received: (from wlloyd@localhost) by tolstoy.mpd.ca (8.7.5/8.7.3) id RAA29997; Sat, 4 Jan 1997 17:27:55 -0500 (EST) Message-Id: <199701042227.RAA29997@tolstoy.mpd.ca> Date: Sat, 4 Jan 1997 17:27:55 -0500 (EST) From: William Lloyd Reply-To: wlloyd@tolstoy.mpd.ca To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2375: Fix some warnings in the ascii handbook Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2375 >Category: docs >Synopsis: Fix some warnings in the ascii handbook >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 4 14:30:01 PST 1997 >Last-Modified: >Originator: William Lloyd >Organization: William Lloyd (wlloyd@mpd.ca) >Release: FreeBSD 2.1.5-STABLE i386 >Environment: >Description: Fixes some of the warnings that come up when making the handbook in ascii. According to jfieber in sgmlfmt lines should not start with a period (.) >How-To-Repeat: >Fix: Index: term.sgml =================================================================== RCS file: /rootfs/galt/usr/ncvs/src/share/doc/handbook/term.sgml,v retrieving revision 1.4 diff -c -r1.4 term.sgml *** term.sgml 1996/11/03 14:46:16 1.4 --- term.sgml 1997/01/04 22:04:25 *************** *** 373,380 **** type does not change, so you can put a real terminal type in this field. ! Users will usually use the /etc/ttys file, users can forego such prompting. --- 373,380 ---- type does not change, so you can put a real terminal type in this field. ! Users will usually use the /etc/ttys file, users can forego such prompting. Index: dialout.sgml =================================================================== RCS file: /rootfs/galt/usr/ncvs/src/share/doc/handbook/dialout.sgml,v retrieving revision 1.2 diff -c -r1.2 dialout.sgml *** dialout.sgml 1996/11/30 23:51:45 1.2 --- dialout.sgml 1997/01/04 22:07:59 *************** *** 42,48 **** just a hard link to ! My stock Hayes modem is not supported—what can I do?

Actually, the man page for ! My stock Hayes modem is not supported, what can I do?

Actually, the man page for Make an entry for your university in /etc/remote ! and use \@ for the big-university:\ :pn=\@:tc=dialout --- 162,168 ---- and several thousand students trying to use them...

Make an entry for your university in /etc/remote ! and use @ for the big-university:\ :pn=\@:tc=dialout Index: kernelopts.sgml =================================================================== RCS file: /rootfs/galt/usr/ncvs/src/share/doc/handbook/kernelopts.sgml,v retrieving revision 1.4 diff -c -r1.4 kernelopts.sgml *** kernelopts.sgml 1997/01/02 17:00:26 1.4 --- kernelopts.sgml 1997/01/04 22:11:58 *************** *** 47,53 **** #ifdef THAT_OPTION ! ... #endif --- 47,53 ---- #ifdef THAT_OPTION ! your code here. #endif Index: mail.sgml =================================================================== RCS file: /rootfs/galt/usr/ncvs/src/share/doc/handbook/mail.sgml,v retrieving revision 1.4 diff -c -r1.4 mail.sgml *** mail.sgml 1996/12/31 21:54:17 1.4 --- mail.sgml 1997/01/04 21:43:47 *************** *** 351,359 **** That way a remote site will deliver straight to you, without trying the customer connection. You then send to your customer. Only works for ! 'hosts', so you need to get your customer to name their mail machine ! 'customer.com' as well as 'hostname.customer.com' in the DNS. Just put ! an A record in the DNS for 'customer.com'. --- 422,430 ---- That way a remote site will deliver straight to you, without trying the customer connection. You then send to your customer. Only works for ! "hosts", so you need to get your customer to name their mail machine ! "customer.com" as well as "hostname.customer.com" in the DNS. Just put ! an A record in the DNS for "customer.com". >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 15:00:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21458 for bugs-outgoing; Sat, 4 Jan 1997 15:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21441; Sat, 4 Jan 1997 15:00:01 -0800 (PST) Date: Sat, 4 Jan 1997 15:00:01 -0800 (PST) Message-Id: <199701042300.PAA21441@freefall.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: kern/2371: SCSI disk corruption Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2371; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: markd@grizzly.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/2371: SCSI disk corruption Date: Sat, 4 Jan 1997 23:43:21 +0100 As markd@grizzly.com wrote: > AHC options: > controller ahc0 > options AHC_TAGENABLE > options AHC_SCBPAGING_ENABLE ^^^^^^^^^^^^^^^^^^^^ Turn this off, and see if your problem persists. I think SCB paging is not yet ready for prime-time. > options AHC_ALLOW_MEMIO I think problems with AHC_ALLOW_MEMIO are rather `binary' in nature: it either works well, or starts to go afoul very early in the game. Problems with tagged commands usually end up in ``Overlapped commands attempted'' or something like this. Eeek, no: > ahc0: target 0 Tagged Queuing Device > (ahc0:0:0): "HP C3725S 6039" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) This one is known to choke on tagged commands! > The last major activity before the crash was formatting of sd2, an IOMega > Zip drive. SCSI format, partition and newfs had generated the following > message: > > Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): UNIT ATTENTION asc:28,0 > Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): Not ready to ready transition, medium may have changed > Jan 3 22:47:13 osprey /kernel: Debugger("sdopen: no slices") called. > Jan 3 22:47:13 osprey /kernel: sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > Jan 3 22:47:13 osprey /kernel: sd2 could not mode sense (4). Using ficticious geometry > Jan 3 22:47:13 osprey /kernel: sd2: invalid primary partition table: no magic That's something different, and basically a known problem. You might get around this by creating a `quirk' record for this device in /sys/scsi/scsiconf.c, and assign it to the `od' driver. This one has a better understanding of removable media devices. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jan 4 15:00:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21470 for bugs-outgoing; Sat, 4 Jan 1997 15:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA21455; Sat, 4 Jan 1997 15:00:02 -0800 (PST) Resent-Date: Sat, 4 Jan 1997 15:00:02 -0800 (PST) Resent-Message-Id: <199701042300.PAA21455@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, root@mach5.compus.com Received: from mach5.compus.com (p14.pm-1.pm.dimcom.net [208.206.177.14]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA21277 for ; Sat, 4 Jan 1997 14:54:53 -0800 (PST) Received: (from root@localhost) by mach5.compus.com (8.8.4/8.7.3) id PAA10407; Sat, 4 Jan 1997 15:50:37 -0700 (MST) Message-Id: <199701042250.PAA10407@mach5.compus.com> Date: Sat, 4 Jan 1997 15:50:37 -0700 (MST) From: Charlie Root Reply-To: root@mach5.compus.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: misc/2376: libpcap does not compile Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2376 >Category: misc >Synopsis: libpcap does not compile >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 4 15:00:02 PST 1997 >Last-Modified: >Originator: Chris Olsen >Organization: COMPUS Services >Release: FreeBSD 3.0-CURRENT i386 >Environment: Source cvsup'ed 1/4/97 >Description: contrib/libpcap/grammer.y needes to include if_var.h due to Garret's recent changes >How-To-Repeat: Try to compile libpcap from scratch >Fix: Add #include to contrib/libpcap/grammer.y >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 16:21:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA00711 for bugs-outgoing; Sat, 4 Jan 1997 16:21:46 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA00703 for ; Sat, 4 Jan 1997 16:21:43 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA00720; Sun, 5 Jan 1997 01:21:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA19276; Sun, 5 Jan 1997 01:21:25 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id BAA26280; Sun, 5 Jan 1997 01:15:06 +0100 (MET) Message-ID: Date: Sun, 5 Jan 1997 01:15:06 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: tedm%toybox@agora.rdrop.com Cc: freebsd-bugs@FreeBSD.org (FreeBSD bugs list) Subject: Re: conf/2367: Buslogic SCSI driver bad probe of 742A early revision IRQ and version References: <9701040606.AA0046@agora.rdrop.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9701040606.AA0046@agora.rdrop.com>; from tedm@agora.rdrop.com on Jan 3, 1997 21:45:09 +0900 Sender: owner-bugs@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As tedm@agora.rdrop.com wrote: > > It's been a while ago that i've been using a Bt742A. I remember that > > it wasn't totally unproblematical for me either. > Kind of ironic, since the monolithic Buslogic driver was derived > from driver code from the 742A EISA card! Yes and no: these cards are dual-personality, and they have been used in their ISA personality only in the beginning. > I tried disabling the bt driver, this did make the above error > message about bt unit number 1 too high go away, and the kernel did > boot properly. Ok. So the basic problem of your PR is solved then? > This is probably something that should go into the install FAQ, is > the same problem present with the Adaptec 1740 card responding as a > 1540 as well? Basically yes. ISTR that you also have to setup a BusLogic card for BSD/OS to not match one of the ISA addresses, for the very same reason. I've had a look at the FAQ, there's a large section about the 742A, but this detail is indeed missing. > I also tried switching the interrupt to IRQ12 with the bt driver > disabled, the EISA probe _still_ thinks that the interrupt is at IRQ > 9, and the boot process halts. That's surprising. I never had problems of this kind with the EISA code. Maybe your mainboard is lying? (Mine was a SiS chipset one.) My Bt742A always ran at IRQ 11 or 12 (i eventually forgot which one). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sat Jan 4 17:00:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA03566 for bugs-outgoing; Sat, 4 Jan 1997 17:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA03559; Sat, 4 Jan 1997 17:00:02 -0800 (PST) Resent-Date: Sat, 4 Jan 1997 17:00:02 -0800 (PST) Resent-Message-Id: <199701050100.RAA03559@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, obrien@cs.ucdavis.edu Received: from guilder.ucdavis.edu (root@guilder.ucdavis.edu [128.120.8.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA03283 for ; Sat, 4 Jan 1997 16:53:20 -0800 (PST) Received: from dragon.nuxi.com by guilder.ucdavis.edu (8.8.3/UCD3.8.1) id QAA14399; Sat, 4 Jan 1997 16:51:27 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id QAA01801; Sat, 4 Jan 1997 16:51:20 -0800 (PST) Message-Id: <199701050051.QAA01801@dragon.nuxi.com> Date: Sat, 4 Jan 1997 16:51:20 -0800 (PST) From: "David O'Brien" Reply-To: obrien@cs.ucdavis.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/2377: minor timed(8) syntax manpage problem Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2377 >Category: bin >Synopsis: minor timed(8) syntax error >Confidential: yes >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 4 17:00:01 PST 1997 >Last-Modified: >Originator: David O'Brien >Organization: NUXI >Release: FreeBSD 2.2-BETA_A i386 >Environment: 2.2-BETA >Description: timed(8)'s manpage states: "network running timed 8." and "When timed 8 is started" >How-To-Repeat: ``man timed'' >Fix: Shouldn't that be "network running timed(8)." or just "running timed."? I see that ".Nm timed 8 ." is used. Should that be ".Xr timed 8"? But of course that won't bold it. What is the correct way for this? >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Jan 4 20:20:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA11541 for bugs-outgoing; Sat, 4 Jan 1997 20:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA11534; Sat, 4 Jan 1997 20:20:02 -0800 (PST) Date: Sat, 4 Jan 1997 20:20:02 -0800 (PST) Message-Id: <199701050420.UAA11534@freefall.freebsd.org> To: freebsd-bugs Cc: From: Mark Diekhans Subject: Re: kern/2371: SCSI disk corruption Reply-To: Mark Diekhans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2371; it has been noted by GNATS. From: Mark Diekhans To: joerg_wunsch@uriah.heep.sax.de Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/2371: SCSI disk corruption Date: Sat, 4 Jan 1997 20:19:39 -0800 (PST) >From: j@uriah.heep.sax.de (J Wunsch) Hey mate, thanks for all the info. >Eeek, no: > >> ahc0: target 0 Tagged Queuing Device >> (ahc0:0:0): "HP C3725S 6039" type 0 fixed SCSI 2 >> sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) > >This one is known to choke on tagged commands! Ack.... Perhaps there should be a warning in LINT about this. Not booting after adding a option is no big deal, but destorying a disk after many days of use is rather painful. Thanks, I owe you a beer, Mark From owner-freebsd-bugs Sat Jan 4 22:30:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA15212 for bugs-outgoing; Sat, 4 Jan 1997 22:30:34 -0800 (PST) Received: (from nate@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA15193; Sat, 4 Jan 1997 22:30:26 -0800 (PST) Date: Sat, 4 Jan 1997 22:30:26 -0800 (PST) From: Nate Williams Message-Id: <199701050630.WAA15193@freefall.freebsd.org> To: smpatel@xi.omniscient.com, nate, freebsd-bugs Subject: Re: kern/2333 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Synopsis: psm0 panics if no mouse attached. State-Changed-From-To: open-closed State-Changed-By: nate State-Changed-When: Sat Jan 4 22:30:01 PST 1997 State-Changed-Why: Fixed in version 1.33 of psm.c.