From owner-freebsd-bugs Sun Oct 8 11:52:49 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA09120 for bugs-outgoing; Sun, 8 Oct 1995 11:52:49 -0700 Received: from clark.net (root@clark.net [168.143.0.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA09114 for ; Sun, 8 Oct 1995 11:52:47 -0700 Received: from ras2.HAN.UnisysGSG.COM (ras2.HAN.UnisysGSG.COM [128.126.195.242]) by clark.net (8.6.12/8.6.5) with SMTP id OAA10344; Sun, 8 Oct 1995 14:52:32 -0400 Received: by ras2.HAN.UnisysGSG.COM with Microsoft Mail id <01BA958D.CA1F82A0@ras2.HAN.UnisysGSG.COM>; Sun, 8 Oct 1995 14:53:12 -0400 Message-ID: <01BA958D.CA1F82A0@ras2.HAN.UnisysGSG.COM> From: Mark Starner To: "'bugs@freebsd.org'" Cc: "'moriya@ifi.unicamp.br'" Subject: Bug accessing /dev/cd1 Date: Sun, 8 Oct 1995 14:53:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk Was a fix ever found for this bug? I had the same problem, and sent my system info to (what were then) the appropriate people. I just loaded up the current snapshot and have the same problem... a panic as below, at the same place when accessing cd1. (actually it may be worse, it used to never crash with cd0, now it does sometimes) FYI, I am running with a AHA-3940, a NEC 3xi and Plextor 4-Plex CD. Mark >From: Alexandre Moriya - esp Subject: KERNEL BUG !!!! To: bugs@FreeBSD.org Date sent: Fri, 11 Aug 1995 11:25:24 -0300 (BSC) Copies to: hackers@FreeBSD.org, questions@FreeBSD.org, moriya@ifi.unicamp.br (Alexandre Moriya - esp) THIS mail has been sent to {bugs,hackers,questions}@FreeBSD.org Hi all, I don't if it is the right place for this question. If it isn't, could you please send it to the right people ? I believe it is a KERNEL BUG. I have the following configuration: 1 PC/FreeBSD-2.0.5 1 Seven CD Tower (SCSI Express Tower / MDI) 1 Adaptec 1542CF ISA-to-SCSI adaptor The 1542CF adaptor is configured as the kernel messages bellow says: Aug 9 12:54:30 by-tor /kernel: aha0: AHA-1542CF BIOS v2.01-VB.0, enabling mai lbox, enabling residuals Aug 9 12:54:30 by-tor /kernel: aha0: reading board settings, dma=5 int=11 (bus speed defaulted) Aug 9 12:54:30 by-tor /kernel: aha0 at 0x330-0x333 irq 11 drq 5 on isa Aug 9 12:54:30 by-tor /kernel: aha0 waiting for scsi devices to settle Aug 9 12:54:30 by-tor /kernel: (aha0:0:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:30 by-tor /kernel: cd0(aha0:0:0): CD-ROM Aug 9 12:54:30 by-tor /kernel: cd0(aha0:0:0): NOT READY asc:3a,0 Medium not present Aug 9 12:54:30 by-tor /kernel: can't get the size Aug 9 12:54:31 by-tor /kernel: Aug 9 12:54:31 by-tor /kernel: (aha0:1:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:31 by-tor /kernel: cd1(aha0:1:0): CD-ROM Aug 9 12:54:31 by-tor /kernel: cd1(aha0:1:0): NOT READY asc:3a,0 Medium not present Aug 9 12:54:31 by-tor /kernel: can't get the size Aug 9 12:54:31 by-tor /kernel: Aug 9 12:54:31 by-tor /kernel: (aha0:2:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:32 by-tor /kernel: cd2(aha0:2:0): CD-ROM Aug 9 12:54:32 by-tor /kernel: cd2(aha0:2:0): NOT READY asc:3a,0 Medium not present Aug 9 12:54:32 by-tor /kernel: can't get the size Aug 9 12:54:32 by-tor /kernel: Aug 9 12:54:32 by-tor /kernel: (aha0:3:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:32 by-tor /kernel: cd3(aha0:3:0): CD-ROM cd present.[183255 x 204 8 byte records] Aug 9 12:54:32 by-tor /kernel: (aha0:4:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:33 by-tor /kernel: cd4(aha0:4:0): CD-ROM Aug 9 12:54:33 by-tor /kernel: cd4(aha0:4:0): NOT READY asc:3a,0 Medium not present Aug 9 12:54:33 by-tor /kernel: can't get the size Aug 9 12:54:33 by-tor /kernel: Aug 9 12:54:33 by-tor /kernel: (aha0:5:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:33 by-tor /kernel: cd5(aha0:5:0): CD-ROM Aug 9 12:54:33 by-tor /kernel: cd5(aha0:5:0): NOT READY asc:3a,0 Medium not present Aug 9 12:54:33 by-tor /kernel: can't get the size Aug 9 12:54:33 by-tor /kernel: Aug 9 12:54:34 by-tor /kernel: (aha0:6:0): "MDI SE53CD 0925" type 5 removable SCSI 2 Aug 9 12:54:34 by-tor /kernel: cd6(aha0:6:0): CD-ROM Aug 9 12:54:34 by-tor /kernel: cd6(aha0:6:0): NOT READY asc:3a,0 Medium not p resent Aug 9 12:54:34 by-tor /kernel: can't get the size Aug 9 12:54:34 by-tor /kernel: My problem is that I mounted a CD-ROM from the first device (/dev/cd0a) in the directory /0 using "mount_cd9660 /dev/cd0a /0" or by a corresponding line in the /fstab. The CDROM has about 100MB of info in the root dir. When I try to "cat *" the /0 directory, everything is fine. Everything works well when I mount the same CDROM in the /dev/cdNa, where N=[0,5]. (I have created all devices using "cd /dev; sh MAKEDEV cdN;" where N=[0,6]) It does not made any difference if I used /dev/cdNc instead of /dev/cdNa... The "bug" appears when I mount the CDROM in the /dev/cd6a (the last CDROM device). I used "mount_cd9660 /dev/cd6a /0 ; cd /0 ; cat *" and a few seconds later I received the following message: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10a fault code = supervisor read, page not present instruction pointer = 0x8:0xf011efdc code segment = base 0x0, limit 0xfffff, type 0x1b processor eflags = interrupt enabled, resume IOPL=0 current process = 133(cat) interrupt mask = bio panic: page fault syncing disks..................... 4 4 4 4 4 4 4 4 4 giving up Automaitc reboot in 15 seconds - press a key on the console to abort ------- Is it easy to repair ? I took a look in the /usr/src/sys/i386/i386 dir and found something, but nothing that lead me to any conclusion. I have seen something concerning about this in the /usr/src/sys/scsi dir, too. Can you help me ? Any tips ? We here at CCJDR intend to use up to 3 "Seven CD Tower" but will the kernel accept more than 6 devices (0-5) ? We want to use 21 !!! Sorry for my poor english :-( If you have any doubt, ask me please. We should have a solution to this problem as early as possible. I believe that , if it is a kernel bug, it should be repaired before the 2.1 release, isn't it ? Finnaly, I'd like to thank you for the great work in the FreeBSD. It'is working very nice !!! BYE (Ate mais) -- Alexandre Moriya (RA 910061) Centro de Computacao John David Rogers (CCJDR) Instituto de Fisica Gleb Wataghin (IFGW) Universidade Estadual de Campinas (UNICAMP) Campinas - SP - Brasil e-mail: moriya@ifi.unicamp.br moriya@dcc.unicamp.br -------------------- >From: J Wunsch Subject: Re: KERNEL BUG !!!! To: moriya@ifi.unicamp.br (Alexandre Moriya - esp) Date sent: Mon, 14 Aug 1995 20:30:30 +0200 (MET DST) Copies to: joerg_wunsch@uriah.heep.sax.de, starner@clark.net, lenzi@mtm.ufsc.br, davidg@freebsd.org (David Greenman) Send reply to: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) As Alexandre Moriya - esp wrote: > > > fault virtual address = 0x10a > This number is variable. Each time the bug happens we have > a different number. Understandable. It's a bogus address. > > > instruction pointer = 0x8:0xf011efdc > OOOPS !!! The number is wrong. > The correct number is 0xf012135c > > nm /kernel | sort | more > Ok. the new result is: > f0121314 T _incore > f01213b0 T _inmem The bug happens in line 694 of vfs_bio.c: 686 incore(struct vnode * vp, daddr_t blkno) 687 { 688 struct buf *bp; 689 struct bufhashhdr *bh; 690 691 int s = splbio(); 692 693 bh = BUFHASH(vp, blkno); 694 bp = bh->lh_first; ^^^^ Apparently, the BUFHASH macro yielded a bogus number that was an invalid address (but not zero, since you're writing the number is different each time). I'm Cc'ing David Greenman, i think he's the one who would best understand what happens here. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Sun Oct 8 16:50:03 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA15972 for bugs-outgoing; Sun, 8 Oct 1995 16:50:03 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA15966 ; Sun, 8 Oct 1995 16:50:01 -0700 Resent-Date: Sun, 8 Oct 1995 16:50:01 -0700 Resent-Message-Id: <199510082350.QAA15966@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA15840 for ; Sun, 8 Oct 1995 16:42:51 -0700 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id BAA27783 for ; Mon, 9 Oct 1995 01:42:46 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id BAA05786; Mon, 9 Oct 1995 01:42:44 +0200 Message-Id: <199510082342.BAA05786@katiska.clinet.fi> Date: Mon, 9 Oct 1995 01:42:44 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/772: Stable panic Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 772 >Category: kern >Synopsis: page fault while in kernel mode (two cases) >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 8 16:50:01 PDT 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.1-STABLE i386 (send-pr offers -CURRENT here, but sup release is stable?) >Environment: Oct 8 22:50:37 katiska /kernel: CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) Oct 8 22:50:37 katiska /kernel: Origin = "GenuineIntel" Id = 0x524 Stepping =4 Oct 8 22:50:37 katiska /kernel: Features=0x1bf Oct 8 22:50:37 katiska /kernel: real memory = 67108864 (65536K bytes) Oct 8 22:50:37 katiska /kernel: avail memory = 62500864 (61036K bytes) Oct 8 22:50:37 katiska /kernel: Probing for devices on the ISA bus: Oct 8 22:50:38 katiska /kernel: ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16 384 on isa Oct 8 22:50:38 katiska /kernel: ed0: address 00:00:c0:cd:b9:a3, type WD8013EPC (16 bit) Oct 8 22:50:38 katiska /kernel: bpf: ed0 attached Oct 8 22:50:38 katiska /kernel: vt0 at 0x60-0x6f irq 1 on motherboard Oct 8 22:50:38 katiska /kernel: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Oct 8 22:50:38 katiska /kernel: lpt0 at 0x378-0x37f irq 7 on isa Oct 8 22:50:38 katiska /kernel: lpt0: Interrupt-driven port Oct 8 22:50:38 katiska /kernel: lp0: TCP/IP capable interface Oct 8 22:50:38 katiska /kernel: bpf: lp0 attached Oct 8 22:50:38 katiska /kernel: lpt1 not found at 0xffffffff Oct 8 22:50:38 katiska /kernel: lpt2 not found at 0xffffffff Oct 8 22:50:38 katiska /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Oct 8 22:50:38 katiska /kernel: sio0: type 16550A Oct 8 22:50:39 katiska /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Oct 8 22:50:39 katiska /kernel: sio1: type 16550A Oct 8 22:50:39 katiska /kernel: sio2 not found at 0x3e8 Oct 8 22:50:39 katiska /kernel: sio3 not found at 0x2e8 Oct 8 22:50:39 katiska /kernel: pca0 on isa Oct 8 22:50:39 katiska /kernel: pca0: PC speaker audio driver Oct 8 22:50:39 katiska /kernel: bt0 not found at 0x330 Oct 8 22:50:39 katiska /kernel: aha0 not found at 0x330 Oct 8 22:50:39 katiska /kernel: wdc0 not found at 0x1f0 Oct 8 22:50:39 katiska /kernel: wdc1 not found at 0x170 Oct 8 22:50:39 katiska /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Oct 8 22:50:39 katiska /kernel: fdc0: NEC 765 Oct 8 22:50:39 katiska /kernel: fd0: 1.44MB 3.5in Oct 8 22:50:39 katiska /kernel: mcd0: timeout getting status Oct 8 22:50:39 katiska /kernel: mcd0 not found at 0x300 Oct 8 22:50:39 katiska /kernel: le0: no board found at 0x300 Oct 8 22:50:39 katiska /kernel: le0 not found at 0x300 Oct 8 22:50:39 katiska /kernel: npx0 on motherboard Oct 8 22:50:39 katiska /kernel: npx0: INT 16 interface Oct 8 22:50:39 katiska /kernel: matcdc0 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc1 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc2 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc3 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: bio_imask c0000040 tty_imask c00300ba net_imask c00300ba Oct 8 22:50:39 katiska /kernel: Probing for devices on the PCI bus: Oct 8 22:50:39 katiska /kernel: chip0 rev 0 on pci0:0 Oct 8 22:50:39 katiska /kernel: chip1 rev 0 on pci0:1 Oct 8 22:50:39 katiska /kernel: ncr0 rev 1 int a irq 11 on pc i0:13 Oct 8 22:50:39 katiska /kernel: ncr0: restart (scsi reset). Oct 8 22:50:39 katiska /kernel: ncr0 scanning for targets 0..6 (V2 pl22 95/07/0 7) Oct 8 22:50:39 katiska /kernel: ncr0 waiting for scsi devices to settle Oct 8 22:50:39 katiska /kernel: (ncr0:0:0): "SEAGATE ST15230N 0298" type 0 fixe d SCSI 2 Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): Direct-Access Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:39 katiska /kernel: 4095MB (8386733 512 byte sectors) Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): with 3992 cyls, 19 heads, and an average 110 sectors/track Oct 8 22:50:39 katiska /kernel: (ncr0:3:0): 200ns (5 Mb/sec) offset 8. Oct 8 22:50:39 katiska /kernel: (ncr0:3:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Oct 8 22:50:39 katiska /kernel: sd3(ncr0:3:0): Direct-Access Oct 8 22:50:39 katiska /kernel: sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:39 katiska /kernel: 1003MB (2055035 512 byte sectors) Oct 8 22:50:40 katiska /kernel: sd3(ncr0:3:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Oct 8 22:50:40 katiska /kernel: ncr1 rev 2 int a irq 12 on pc i0:15 Oct 8 22:50:40 katiska /kernel: ncr1: restart (scsi reset). Oct 8 22:50:40 katiska /kernel: ncr1 scanning for targets 0..6 (V2 pl22 95/07/0 7) Oct 8 22:50:40 katiska /kernel: ncr1 waiting for scsi devices to settle Oct 8 22:50:40 katiska /kernel: (ncr1:3:0): "SEAGATE ST15230N 0168" type 0 fixe d SCSI 2 Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): Direct-Access Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:40 katiska /kernel: 4095MB (8386733 512 byte sectors) Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): with 3992 cyls, 19 heads, and an average 110 sectors/track Oct 8 22:50:40 katiska /kernel: (ncr1:4:0): "HP C1533A 9503" type 1 removable S CSI 2 Oct 8 22:50:40 katiska /kernel: st7(ncr1:4:0): Sequential-Access Oct 8 22:50:40 katiska /kernel: st7(ncr1:4:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:40 katiska /kernel: density code 0x24, variable blocks, write-enabl ed Oct 8 22:50:40 katiska /kernel: vga0 rev 0 on pci0:17 Oct 8 22:50:40 katiska /kernel: changing root device to sd0a Oct 8 22:50:40 katiska /kernel: bpf: ds0 attached Oct 8 22:50:40 katiska /kernel: bpf: lo0 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp0 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp1 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp2 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp3 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp4 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp5 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp6 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp7 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp8 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp9 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp10 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp11 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp12 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp13 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp14 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp15 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp16 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp17 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp18 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp19 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp20 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp21 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp22 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp23 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp24 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp25 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp26 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp27 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp28 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp29 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp30 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp31 attached Oct 8 22:50:41 katiska /kernel: bpf: sl0 attached Oct 8 22:50:41 katiska /kernel: bpf: sl1 attached Oct 8 22:50:41 katiska /kernel: bpf: sl2 attached Oct 8 22:50:41 katiska /kernel: bpf: sl3 attached Oct 8 22:50:41 katiska /kernel: bpf: sl4 attached Oct 8 22:50:41 katiska /kernel: bpf: sl5 attached Oct 8 22:50:41 katiska /kernel: bpf: sl6 attached Oct 8 22:50:41 katiska /kernel: bpf: sl7 attached Oct 8 22:50:41 katiska /kernel: bpf: sl8 attached Oct 8 22:50:41 katiska /kernel: bpf: sl9 attached Oct 8 22:50:41 katiska /kernel: bpf: sl10 attached Oct 8 22:50:41 katiska /kernel: bpf: sl11 attached Oct 8 22:50:41 katiska /kernel: bpf: sl12 attached Oct 8 22:50:41 katiska /kernel: bpf: sl13 attached Oct 8 22:50:41 katiska /kernel: bpf: sl14 attached Oct 8 22:50:41 katiska /kernel: bpf: sl15 attached Oct 8 22:50:41 katiska /kernel: bpf: tun0 attached Oct 8 22:50:41 katiska /kernel: WARNING: / was not properly dismounted. Oct 8 22:50:41 katiska /kernel: sd7: invalid primary partition table: no magic Oct 8 22:50:41 katiska last message repeated 2 times Oct 8 22:50:42 katiska lpd[128]: restarted # # CLINETSERVER - a bloated kernel for servers, include everything possible # # $Id: LINT,v 1.150 1995/03/04 21:09:21 jkh Exp $ # # # This directive is mandatory; it defines the architecture to be # configured for; in this case, the 386 family. You must also specify # at least one CPU (the one you intend to run on); deleting the # specification for CPUs you don't need to use may make parts of the # system run faster # # clinet: we have got all of these machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) # # This is the ``identification'' of the kernel. Usually this should # be the same as the name of your kernel. # ident CLINETSERVER # # The `maxusers' parameter controls the static sizing of a number of # internal system tables by a complicated formula defined in param.c. # maxusers 256 options "NMBCLUSTERS=2048" options "TTYHOG=4096" options "RS_IBUFSIZE=1024" # # Under some circumstances it is necessary to make the default max # number of proccesses per user and open files per user more than the # defaults on bootup. (an example is a large news server in which # the uid, news, can sometimes need > 100 simultaneous processes running) # clinet: or hoggy administrators with gazillion xterms (yes, I have run out # of 128 processes :-) options "CHILD_MAX=256" options "OPEN_MAX=256" # # A math emulator is mandatory if you wish to run on hardware which # does not have a floating-point processor. Pick either the original, # bogus (but freely-distributable) math emulator, or a much more # fully-featured but GPL-licensed emulator taken from Linux. # options MATH_EMULATE #Support for x87 emulation #options GPL_MATH_EMULATE #Support for x87 emualtion via #new math emulator # # This directive defines a number of things: # - The compiled kernel is to be called `kernel' # - The root filesystem might be on partition wd0a # - The kernel can swap on wd0b and sd0b, defaulting to the former # - Crash dumps will be written to wd0b, if possible # # clinet: we use 4 disks per server, swap distributed on all of them (speeds # up considerably). Dumps may go to sd0. config kernel root on wd0 swap on wd0 and wd1 and sd0 and sd1 and sd2 and sd3 and vn0 dumps on sd0 ##################################################################### # COMPATIBILITY OPTIONS # # Implement system calls compatible with 4.3BSD and older versions of # FreeBSD. # options "COMPAT_43" # # Allow user-mode programs to manipulat their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of). # options USER_LDT #allow user-level control of i386 ldt # # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # options SYSVSHM options SYSVSEM options SYSVMSG ##################################################################### # DEBUGGING OPTIONS # # Enable the kernel debugger. # # options DDB # # Enable dumping of the kernel image to swap for panics. This is not # the default because writing to misconfigured swap may wipe out file # systems. # options DODUMP # # KTRACE enables the system-call tracing facility ktrace(2). # options KTRACE #kernel tracing # # The DIAGNOSTIC option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # options DIAGNOSTIC # # Allow ordinary users to take the console - this is useful for X. options UCONSOLE ##################################################################### # NETWORKING OPTIONS # # Protocol families: # Only the INET (Internet) family is officially supported in FreeBSD. # Source code for the NS (Xerox Network Service), ISO (OSI), and # CCITT (X.25) families is provided for amusement value, although we # try to ensure that it actually compiles. # options INET #Internet communications protocols # options ISO # options CCITT #X.25 network layer # options NS #Xerox NS communications protocols # options TPIP #ISO TP class 4 over IP # options TPCONS #ISO TP class 0 over X.25 # # Network interfaces: # The `loop' pseudo-device is mandatory when networking is enabled. # The `ether' pseudo-device provides generic code to handle # Ethernets; it is mandatory when a Ethernet device driver is # configured. # The `sppp' pseudo-device serves a similar role for certain types # of synchronous PPP links (like `cx'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. # The `disc' pseudo-device implements a minimal network interface, # which throws away all packets sent and never receives any. It is # included for testing purposes. # The `tun' pseudo-device implements the User Process PPP (iijppp) # pseudo-device ether #Generic Ethernet pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device sl 16 #Serial Line IP pseudo-device ppp 32 #Point-to-point protocol pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) #options NSIP #XNS over IP #options EON #ISO CLNP over IP #options LLC #X.25 link layer for Ethernets #options HDLC #X.25 link layer for serial lines # # Internet family options: # # TCP_COMPAT_42 causes the TCP code to emulate certain bugs present in # 4.2BSD. This option should not be used unless you have a 4.2BSD # machine and TCP connections fail. # # GATEWAY allows the machine to forward packets, and also configures # larger static sizes of a number of system tables. # # MROUTING enables the kernel multicast packet forwarder, which works # with mrouted(8). # # IPFIREWALL enables support for IP firewall construction, in # conjunction with the `ipfw' program. IPFIREWALL_VERBOSE does # the obvious thing. # # ARP_PROXYALL enables global proxy ARP. Beware! This can burn # your house down! See netinet/if_ether.c for the gory details. # (Eventually there will be a better management interface.) # options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options GATEWAY #internetwork gateway options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets #options ARP_PROXYALL # global proxy ARP ##################################################################### # FILESYSTEM OPTIONS # # Only the root, /usr, and /tmp filesystems need be statically # compiled; everything else will be automatically loaded at mount # time. (Exception: the UFS family---FFS, MFS, and LFS---cannot # currently be demand-loaded.) Some people still prefer to statically # compile other filesystems as well. # # NB: The LFS, PORTAL, and UNION filesystems are known to be buggy, # and WILL panic your system if you attempt to do anything with them. # They are included here as an incentive for some enterprising soul to # sit down and fix them. # # One of these is mandatory: options FFS #Fast filesystem options NFS #Network File System # The rest are optional: options "CD9660" #ISO 9660 filesystem options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options LFS #Log filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System options NULLFS #NULL filesystem options PORTAL #Portal filesystem options PROCFS #Process filesystem options UMAPFS #UID map filesystem options UNION #Union filesystem # # Disk quotas are supported when this option is enabled. If you # change the value of this option, you must do a `make clean' in your # kernel compile directory in order to get a working kernel. # #options QUOTA #enable disk quotas # # PCI devices: # # The main PCI bus device is `pci'. It provides auto-detection and # configuration support for all devices on the PCI bus, using either # configuration mode defined in the PCI specification. # # The `ncr' device provides support for the NCR 53C810 and 53C825 # self-contained SCSI host adapters. # # The `de' device provides support for the Digital Equipment DC21040 # self-contained Ethernet adapter. # # The PROBE_VERBOSE option enables a long listing of chip set registers # for supported PCI chip sets (currently only intel Saturn and Mercury). # controller pci0 device ncr0 device de0 options PROBE_VERBOSE options "SCSI_DELAY=10" ##################################################################### # SCSI DEVICE CONFIGURATION # # The SCSI subsystem consists of the `base' SCSI code, a number of # high-level SCSI device `type' drivers, and the low-level host-adapter # device drivers. The host adapters are listed in the ISA and PCI # device configuration sections below. # # Beginning with FreeBSD 2.1 you can wire down your SCSI devices so # that a given bus, target, and LUN always come on line as the same # device unit. In earlier versions the unit numbers were assigned # in the order that the devices were probed on the SCSI bus. This # means that if you removed a disk drive, you may have had to rewrite # your /etc/fstab file, and also that you had to be careful when adding # a new disk as it may have been probed earlier and moved your device # configuration around. # This old behavior is maintained as the default behavior. The unit # assignment begins with the first non-wired down unit for a device # type. For example, if you wire a disk as "sd3" then the first # non-wired disk will be assigned sd4. # The syntax for wiring down devices is: # disk sd0 at scbus0 target 0 unit 0 # disk sd1 at scbus0 target 1 # disk sd2 at scbus0 target 3 # tape st1 at scbus0 target 6 # device cd0 at scbus? # "units" (SCSI logical unit number) that are not specified are # treated as if specified as LUN 0. # All SCSI devices allocate as many units as are required. # The "unknown" device (uk? in pre-2.1) is now part of the base SCSI # configuration and doesn't have to be explicitly configured. controller scbus0 #base SCSI code device ch0 #SCSI media changers device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 disk sd4 at scbus0 target 4 disk sd5 at scbus0 target 5 disk sd6 at scbus0 target 6 tape st0 at scbus0 target 0 tape st1 at scbus0 target 1 tape st2 at scbus0 target 2 tape st3 at scbus0 target 3 tape st4 at scbus0 target 4 tape st5 at scbus0 target 5 tape st6 at scbus0 target 6 device cd0 at scbus0 target 0 device cd1 at scbus0 target 1 device cd2 at scbus0 target 2 device cd3 at scbus0 target 3 device cd4 at scbus0 target 4 device cd5 at scbus0 target 5 device cd6 at scbus0 target 6 # SCSIDEBUG: When defined enables debugging macros # NO_SCSI_SENSE: When defined disables sense descriptions (about 4k) # SCSI_REPORT_GEOMETRY: Always report disk geometry at boot up instead # of only when booting verbosely. #options SCSIDEBUG #options NO_SCSI_SENSE options SCSI_REPORT_GEOMETRY ##################################################################### # MISCELLANEOUS DEVICES AND OPTIONS # # Of these, only the `log' device is truly mandatory. The `pty' # device usually turns out to be ``effectively mandatory'', as it is # required for `telnetd', `rlogind', `screen', `emacs', and `xterm', # among others. # pseudo-device pty 256 #Pseudo ttys - can go as high as 64 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. ##################################################################### # HARDWARE DEVICE CONFIGURATION # ISA and EISA devices: # Currently there is no separate support for EISA. There should be. # Micro Channel is not supported at all. # # Mandatory ISA devices: isa, sc, npx # controller isa0 # # Options for `isa': # # ALLOW_CONFLICT_DRQ suppresses the DMA conflict checks. This option is # included so that people with sound cards that support multiple emulations # can setup different sound drivers on the same DMA channel. There are no # other known uses for this option. # # ALLOW_CONFLICT_IOADDR suppresses the I/O address conflict checks, so # that the PS/2 mouse driver doesn't conflict with the console driver. # # ALLOW_CONFLICT_IRQ suppresses the interrupt line conflict checks, so # that multiple devices can share the same IRQ, provided that the # hardware supports it (it usually doesn't). # # ALLOW_CONFLICT_MEMADDR suppresses the memory address conflict checks. # This option is not known to be good for anything. # # AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A # interrupt controller. This saves about 1.25 usec for each interrupt. # No problems are known to be caused by this option. # # AUTO_EOI_2 enables the `automatic EOI' feature for the slave 8259A # interrupt controller. This saves about 1.25 usec for each interrupt. # Automatic EOI is documented not to work for for the slave with the # original i8259A, but it works for some clones and some integrated # versions. # # BOUNCE_BUFFERS provides support for ISA DMA on machines with more # than 16 megabytes of memory. It doesn't hurt on other machines. # Some broken EISA and VLB hardware may need this, too. # # DUMMY_NOPS disables extra delays for some bus operations. The delays # are mostly for older systems and aren't used consistently. Probably # works OK on most EISA bus machines. # # TUNE_1542 enables the automatic ISA bus speed selection for the # Adaptec 1542 boards. Does not work for all boards, use it with caution. # #options ALLOW_CONFLICT_DRQ #options ALLOW_CONFLICT_IOADDR #options ALLOW_CONFLICT_IRQ #options ALLOW_CONFLICT_MEMADDR options "AUTO_EOI_1" #options "AUTO_EOI_2" options BOUNCE_BUFFERS #options DUMMY_NOPS #options TUNE_1542 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 options XSERVER # include code for XFree86 options FAT_CURSOR # start with block cursor # The syscons console driver (sco color console compatible) - default. #device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr #options "NCONS=4" # # Options for `sc': # # HARDFONTS allows the driver to load an ISO-8859-1 font to replace # the default font in your display adapter's memory. # options HARDFONTS # # MAXCONS is maximum number of virtual consoles, no more than 16 # default value: 12 # options "MAXCONS=16" device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Optional ISA and EISA devices: # # # SCSI host adapters: `aha', `ahb', `aic', `bt', `nca' # # aha: Adaptec 154x # ahb: Adaptec 174x # ahc: Adaptec 274x # aic: Adaptec 152x and sound cards using the Adaptec AIC-6360 (slow!) # bt: Most Buslogic controllers # nca: ProAudioSpectrum cards using the NCR 5380 or Trantor T130 # uha: UltraStore 14F and 34F # sea: Seagate ST01/02 8 bit controller (slow!) # wds: Western Digital WD7000 controller (no scatter/gather!). # # Note that the order is important in order for Buslogic cards to be # probed correctly. # controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr #controller ahc0 at isa? bio irq ? vector ahcintr # port??? iomem? #controller ahb0 at isa? bio irq ? vector ahbintr controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x1f84 #controller nca2 at isa? port 0x1f8c #controller nca3 at isa? port 0x1e88 #controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr #controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr # # ST-506, ESDI, and IDE hard disks: `wdc' and `wd' # # NB: ``Enhanced IDE'' is NOT supported at this time. # controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # # Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft' # controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 # # Options for `fd': # # FDSEEKWAIT selects a non-default head-settle time (i.e., the time to # wait after a seek is performed). The default value (1/32 s) is # usually sufficient. The units are inverse seconds, so a value of 16 # here means to wait 1/16th of a second; you should choose a power of # two. # #options FDSEEKWAIT="16" # # Other standard PC hardware: `lpt', `mse', `psm', `sio', etc. # # lpt: printer port # mse: Logitech and ATI InPort bus mouse ports # psm: PS/2 mouse port (needs ALLOW_CONFLICT_IOADDR, above) # sio: serial ports (see sio(4)) # cy: Cyclades high-speed serial driver (ALPHA QUALITY!) # gp: National Instruments AT-GPIB and AT-GPIB/TNT board # gsc: Genius GS-4500 hand scanner. # joy: joystick device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty device lpt2 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? port "IO_KBD" tty irq 12 vector psmintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr #device gp0 at isa? port 0x2c0 tty #device gsc0 at isa? port "IO_GSC1" tty drq 3 #device joy0 at isa? port "IO_GAME" #device cy0 at isa? tty irq 10 iomem 0xd4000 vector cyintr # Options for sio: #options COMCONSOLE #prefer serial console to video console options COM_MULTIPORT #code for some cards with shared IRQs #options DSI_SOFT_MODEM #code for DSI Softmodems # # Network interfaces: `cx', `ed', `el', `ep', `ie', `is', `le', `lnc' # # cx: Cronyx/Sigma multiport sync/async (with Cisco or PPP framing) # ed: Western Digital and SMC 80xx; Novell NE1000 and NE2000; 3Com 3C503 # el: 3Com 3C501 (slow!) # ep: 3Com 3C509 (buggy) # ie: AT&T StarLAN 10 and EN100; 3Com 3C507; unknown NI5210 # le: Digital Equipment EtherWorks 2 and EtherWorks 3 (DEPCA, DE100, # DE101, DE200, DE201, DE202, DE203, DE204, DE205, DE422) # lnc: Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL) # ze: IBM/National Semiconductor PCMCIA ethernet controller. # zp: 3Com PCMCIA Etherlink III (It does not require shared memory for # send/receive operation, but it needs 'iomem' to read/write the # attribute memory) # #device cx0 at isa? port 0x240 net irq 15 drq 7 vector cxintr device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device el0 at isa? port 0x300 net irq 9 vector elintr device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr # ISDN drivers - `isdn'. # # Uncomment one (and only one) of the following 4 drivers for the appropriate # ISDN device you have. For more information on what's considered appropriate # for your given set of circumstances, please read # /usr/src/gnu/usr.sbin/docs/INSTALL. It's a bit sparse at present, but it's # the best we have right now. The snic driver is also disabled at present, # waiting for someone to upgrade the driver to 2.0 (it's in /sys/gnu/scsi/). # #device nic0 at isa? port "IO_COM3" iomem 0xe0000 tty irq 9 vector nicintr #device nnic0 at isa? port 0x150 iomem 0xe0000 tty irq 12 vector nnicintr # This one is also temporarily ill - needs an isa_device structure!! #controller tel0 at isa? iomem 0xe0000 tty irq 9 vector telintr # These are non-optional for ISDN #pseudo-device isdn #pseudo-device ii 4 #pseudo-device ity 4 #pseudo-device itel 2 #pseudo-device ispy 1 # # Audio drivers: `snd', `pca' # # snd: Voxware sound drivers for various cards # see /usr/src/sys/i386/isa/sound/sound.doc for details # pca: PCM audio through your PC speaker # #options AUDIO_PAS #options AUDIO_SB #options AUDIO_ADLIB #options AUDIO_GUS #options AUDIO_MPU401 #options AUDIO_UART6850 #options AUDIO_PSS #options AUDIO_GUS16 #options AUDIO_GUSMAX #options AUDIO_MSS #options AUDIO_SBPRO #options AUDIO_SB16 #options AUDIO_YM3812 #device snd10 at isa? port 0x530 irq 10 drq 1 vector adintr #device snd5 at isa? port 0x330 irq 6 vector mpuintr #device snd4 at isa? port 0x220 irq 15 drq 6 vector gusintr #device snd3 at isa? port 0x388 irq 10 drq 6 vector pasintr #device snd2 at isa? port 0x220 irq 7 drq 1 vector sbintr #device snd6 at isa? port 0x220 irq 7 drq 5 vector sbintr #device snd7 at isa? port 0x300 #device snd1 at isa? port 0x388 device pca0 at isa? tty # # Miscellaneous hardware: `mcd', `wt', `ctx', `apm' # # mcd: Mitsumi CD-ROM # scd: Sony CD-ROM # matcd: Matsushita/Panasonic CD-ROM # wt: Wangtek and Archive QIC-02/QIC-36 tape drives # ctx: Cortex-I frame grabber # apm: Laptop Advanced Power Management (experimental) # spigot: The Creative Labs Video Spigot video-aquisition board # # Notes on the spigot: # The video spigot is at 0xad6. This port address can not be changed. # The irq values may only be 10, 11, or 15 # I/O memory is an 8kb region. Possible values are: # 0a0000, 0a2000, ..., 0fffff, f00000, f02000, ..., ffffff # Note that the start address must be on an even boundary. device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr # for the Sony CDU31/33A CDROM #device scd0 at isa? port 0x230 bio # for the soundblaster 16 multicd - up to 4 devices controller matcd0 at isa? port ? controller matcd1 at isa? port ? controller matcd2 at isa? port ? controller matcd3 at isa? port ? #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device ctx0 at isa? port 0x230 iomem 0xd0000 #device spigot0 at isa? port 0xad6 irq 15 iomem 0xee000 vector spigintr #device apm0 at isa? >Description: (copied by hand, dumping always fails) Page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xf012deb5 code seg = base = 0x0, limit 0xfffff, type = 0x1b, DPL = 0, pres 1, def 32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 16518 (slirp) interrupt mask = panic: page fault syncing disks .... 3 3 3 giving up dumping to dev 20401 offset 278528 dump 64 And then it gets stuck there. It seems to be always getting stuck when it syncs the disks. I also saw another panic with slirp being the current process, but did not take the address up that time. f012db90 T _chflags f012dc8c T _fchflags f012dd60 T _chmod f012de60 T _fchmod f012df3c T _chown f012e03c T _fchown f012e118 T _utimes Another one: fault virtual address = 0xdeadc10a code = supervisor read, page not present instruction pointer 0x8:0xf011233c current process = 10681 (top) otherwise the same as previous. Reading uninitialized memory somewhere? f011210c T _sysctl_rdstring f0112180 T _sysctl_struct f01121e4 T _sysctl_rdstruct f011222c T _sysctl_file f01122d8 T _sysctl_doproc f01124a4 T _fill_eproc f011263c T _ogetkerninfo f0112920 F kern_time.o f0112920 T _gettimeofday f0112920 t ___gnu_compiled_c f0112920 t gcc2_compiled. We had problems with -current, particularly the last sup a week ago (in the beginning of the october), which could not stay up for more than 15 minutes. So I thought to go to -stable instead, but it doesn't look much better :-( A 486 system with BT ISA controller has also paniced similarly, getting stuck when trying to dump (but it is still running -current from a month ago). >How-To-Repeat: Kernel is from oct 5 sup, the system is loaded. >Fix: >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sun Oct 8 19:28:38 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA18758 for bugs-outgoing; Sun, 8 Oct 1995 19:28:38 -0700 Received: from blob.best.net (blob.best.net [204.156.128.88]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA18752 for ; Sun, 8 Oct 1995 19:28:32 -0700 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by blob.best.net (8.6.12/8.6.5) with ESMTP id TAA10414 for ; Sun, 8 Oct 1995 19:28:31 -0700 Received: from freebie (cazares.vip.best.com [204.156.134.136]) by shell1.best.com (8.6.12/8.6.5) with SMTP id TAA08349 for ; Sun, 8 Oct 1995 19:28:29 -0700 Message-Id: <199510090228.TAA08349@shell1.best.com> Date: Sun, 08 Oct 95 19:28:23 0000 From: Leo Cazares X-Mailer: Mozilla 1.1N (X11; I; BSD/386 uname failed) MIME-Version: 1.0 To: bugs@freebsd.org Subject: FreeBSD and CAP with ep0 X-URL: http://www.freebsd.org/When/newsflash.html Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-bugs@freebsd.org Precedence: bulk I don't know if this the appropriate place for my query, but I was wondering if anybody has worked on getting CAP to work with the ep0 device on FreeBSD. I hear that the problem with ep0 is that it does not support multicasting. I don't know if this problem has been addressed. Over a month ago, I posted an article to one of the FreeBSD newsgroups and to the appletalk newsgroup. I did not get any help from the net, but somebody suggested that I send my question to bugs@freebsd.org. With the exception of CAP, everything about FreeBSD seems superior to Linux. I used Linux for about 5 months before I switch to FreeBSD. Unfortunately, CAP does not work (although it compiles) despite the fact that I have the latest FreeBSD patches (patchlevel 195). The FreeBSD patch for CAP explains that it will only work for the "ed" ethernet driver. Any help or advice that you can give me will be appreciated. - Leo Cazares From owner-freebsd-bugs Sun Oct 8 22:21:52 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA25006 for bugs-outgoing; Sun, 8 Oct 1995 22:21:52 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA25000 for ; Sun, 8 Oct 1995 22:21:48 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA17581; Mon, 9 Oct 1995 06:21:06 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA28830; Mon, 9 Oct 1995 06:21:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id DAA03420; Mon, 9 Oct 1995 03:15:11 +0100 From: J Wunsch Message-Id: <199510090215.DAA03420@uriah.heep.sax.de> Subject: Re: Bug accessing /dev/cd1 To: starner@clark.net (Mark Starner) Date: Mon, 9 Oct 1995 03:15:10 +0100 (MET) Cc: bugs@freebsd.org, moriya@ifi.unicamp.br Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <01BA958D.CA1F82A0@ras2.HAN.UnisysGSG.COM> from "Mark Starner" at Oct 8, 95 02:53:10 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1880 Sender: owner-bugs@freebsd.org Precedence: bulk As Mark Starner wrote: > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x10a > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf011efdc > code segment = base 0x0, limit 0xfffff, type 0x1b > processor eflags = interrupt enabled, resume IOPL=0 > current process = 133(cat) > interrupt mask = bio > panic: page fault > > syncing disks..................... 4 4 4 4 4 4 4 4 4 giving up > Automaitc reboot in 15 seconds - press a key on the console to abort > > ------- > > Is it easy to repair ? Unfortunately not. :-( I know only of two people where this happens: you, and Hellmuth Michaelis (but i believe it's a CD changer for him). I seem to remember that there's been another report from someone with two CDs, it happened for the second drive for him. I know of at least one person reliably operating a six-CD configuration under 2.0.5. This basically proves that it's not simply the _amount_ of CD drives available; it must be something else. You forgot to attach the appropriate part of your kernel's name list to your message, but i assume it's still the same. (It's also been the same spot in function incore() for Hellmuth Michaelis.) I guess I have to convince somebody of you to track it down with DDB... > The bug happens in line 694 of vfs_bio.c: > > 686 incore(struct vnode * vp, daddr_t blkno) > 687 { > 688 struct buf *bp; > 689 struct bufhashhdr *bh; > 690 > 691 int s = splbio(); > 692 > 693 bh = BUFHASH(vp, blkno); > 694 bp = bh->lh_first; > ^^^^ Yeah, well, anybody out there who understands the BUFHASH() macro??? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Oct 9 00:29:25 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA27515 for bugs-outgoing; Mon, 9 Oct 1995 00:29:25 -0700 Received: from gateway.sequent.com (gateway.sequent.com [138.95.18.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA27508 for ; Mon, 9 Oct 1995 00:29:22 -0700 Received: from crg8.sequent.com (crg8.sequent.com [138.95.19.9]) by gateway.sequent.com (8.6.12/8.6.9) with ESMTP id AAA17502 for ; Mon, 9 Oct 1995 00:28:43 -0700 Received: from localhost (bjj@localhost) by crg8.sequent.com (8.6.12/8.6.9) with SMTP id AAA13577 for ; Mon, 9 Oct 1995 00:27:22 -0700 Message-Id: <199510090727.AAA13577@crg8.sequent.com> X-Authentication-Warning: crg8.sequent.com: Host localhost didn't use HELO protocol To: bugs@freebsd.org Subject: install of 2.1.0-951005-SNAP Date: Mon, 09 Oct 95 00:27:19 PDT From: Ben Jackson Sender: owner-bugs@freebsd.org Precedence: bulk Someone recently gave me an Archive Viper 150, and I had to be at work on Sunday, so it was the perfect opportunity to upgrade and get rid of the pesky ahc scsi bus lockups that made it impossible to back up /home. First, let me say (to Jordan?) that the install looks really snazzy. I was impressed by all of the new features. I did run into a few bumps, though: 1. When the boot floppy kernel boots, after uncompressing, it says it is booting the "kernelel" [sic]. 2. after I selected my install media (UFS), the shell escape to mount it didn't appear. I searched high and low for a way to get a shell (and even noted that `sh' was installed in /stand). I finally found it on VT3. I actually tried VT2 early in my search, but it didn't have anything, so I had abandoned that line of inquiry. this was really only necessary because I had the path wrong (after disklabeling and commiting, it worked). 2a. stty settings on root shell were wrong (eg ^? vs ^H) 3. re: (2), I was panicked momemtarily after my root partition had been newfs'd, and I couldn't get it to install the tarballs. It might be clever to check and make sure that at least bin.aa is accessible before wiping out the previous installation. 4. ...which reminds me, the 'upgrade from 2.0.5' was a cruel trick! I was disappointed to find it a nop. As far as I can tell, now that I'm done, if I'd just been able to evade that newfs, and a few key config files had been spared (or converted), it would have worked. sparing config files could be as simple as a 'initial config' dist that is conditionally extracted. 5. many dialogs of the "oops, info, we're continuing" have `' at the bottom. The first time I got one I spent some time trying to figure out how to avoid it, since in previous installs, selecting `' always led to starting over from scratch. I think `' would be more intuitive. 6. when it couldn't find my install media, after asking if it should continue, it did regardless of my answer. 7. even dists which fail to install are deselected after an extract pass. 8. in the disklabel menu, the second column of partitions is messed up. the areas that were hilited for me, and the number in the select sequence: 1 2 3 4 12 8 5 9 6 10 7 11 so if you moved from '7', it hilited the end of the first entry in the second column (which started as '*WAP', like it had drawn some bogus swap entry first). 12 wrapped to 1 and vice versa. If I edited the info I could see (which was in the obvious sequence in the table) while I was at `12', it modified the right thing. This made me pretty nervous that a commit would newfs something I didn't want it to. 9. disklabel zapped my bootblocks (which were custom to make the default boot device sd0 even tho it got the block from wd0). 10. timezone setting was kind of neat, but the most common options (ie NA/US) were buried due to alphabetical order. after I gave the current time and selected everything, it presented me with a time that was one hour off (and several years, but I don't know what that was about). It thought I had CMOS clock set at wall time. now that my interactive restore of / has put /etc/localtime link back where I had it under 2.0.5, things are back to normal. 11. after first reboot, there is no /kernel, only /kernel.GENERIC In general, as the GUI gets gooeyer and gooeyer, I dissolve more and more of my stomach lining during an install (I just know one day that newfs is going to go nuts and hit partitions I want to keep...) BTW, all of this was via "custom" install. I didn't see any of the quick install or much of the system configure (tz botch convinced me to just do it by hand). Thanks all, --Ben From owner-freebsd-bugs Mon Oct 9 00:30:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA27555 for bugs-outgoing; Mon, 9 Oct 1995 00:30:06 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA27548 ; Mon, 9 Oct 1995 00:30:03 -0700 Resent-Date: Mon, 9 Oct 1995 00:30:03 -0700 Resent-Message-Id: <199510090730.AAA27548@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, peter@jhome.DIALix.COM Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA27412 for ; Mon, 9 Oct 1995 00:23:06 -0700 Received: (from peter@localhost) by jhome.DIALix.COM (8.6.12/8.6.9) id OAA10701; Mon, 9 Oct 1995 14:51:01 +0800 Message-Id: <199510090651.OAA10701@jhome.DIALix.COM> Date: Mon, 9 Oct 1995 14:51:01 +0800 From: Peter Wemm sfjhgsd fhasldf kjahs Reply-To: peter@jhome.DIALix.COM To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: ports/773: screen-3.6.2 from -current wont work... Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 773 >Category: ports >Synopsis: screen-3.6.2 from -current wont work... >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 9 00:30:02 PDT 1995 >Last-Modified: >Originator: Peter Wemm sfjhgsd fhasldf kjahs >Organization: DIALix >Release: FreeBSD 2.2-CURRENT i386 >Environment: -current kernel, near -current binaries (less than 1 week old), -current ports. FreeBSD jhome.DIALix.COM 2.2-CURRENT FreeBSD 2.2-CURRENT #60: Fri Oct 6 05:23:45 WST 1995 peter@jhome.DIALix.COM:/home/src/sys/compile/JHOME i386 >Description: If screen is installed with the default permissions (setuid-root), it core dumps with a bus error if run as a mortal user, and locks up the tty if run as root. In both cases, a child process sits in a 100% cpu busy loop, while the parent dies. >How-To-Repeat: make install rehash screen >Fix: I really do not know.. I looked at the code where it's dying, and it looks really odd. It almost looks like gcc is mis-compiling the code, but I could easily be wrong. It is dying in one of several areas I have seen, mostly inside: for (display = displays; display; display = display->next) { if (D_status == 0) continue; .... } D_status is a macro for display->d_status. Somehow, at the point of death, it is dereferencing a NULL display variable inside the D_status test. I do not see how it could be doing that.. I must be missing something obvious. The only other thing I can think of, is the MD5 passwords. The port is most definately at -current level, and the patch that increases the string to 30 is present. It is dying when it has read access to master.passwd and the encrypted strings. I have still got more things to try yet, but last time I looked at it, ktrace paniced the system. I'm waiting for the next ctm mailout. I did notice that pass2() in process.c can assemble the encrypted string into "Password" *without* the null terminating character. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Oct 9 01:41:24 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA00852 for bugs-outgoing; Mon, 9 Oct 1995 01:41:24 -0700 Received: from gateway.sequent.com (gateway.sequent.com [138.95.18.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA00844 for ; Mon, 9 Oct 1995 01:41:19 -0700 Received: from crg8.sequent.com (crg8.sequent.com [138.95.19.9]) by gateway.sequent.com (8.6.12/8.6.9) with ESMTP id BAA19331 for ; Mon, 9 Oct 1995 01:40:37 -0700 Received: from localhost (bjj@localhost) by crg8.sequent.com (8.6.12/8.6.9) with SMTP id BAA02561 for ; Mon, 9 Oct 1995 01:39:16 -0700 Message-Id: <199510090839.BAA02561@crg8.sequent.com> X-Authentication-Warning: crg8.sequent.com: Host localhost didn't use HELO protocol To: bugs@freebsd.org Subject: addendum to 951005-SNAP Date: Mon, 09 Oct 95 01:39:14 PDT From: Ben Jackson Sender: owner-bugs@freebsd.org Precedence: bulk Since there was no /kernel (per earlier bug report), make install fails in kernel build dir (mv /kernel /kernel.old -- needs `-f'). I think that funky table of partitions with '*WAP' really did have something beneath that item, since I just found out that my wd0s4b swap paritition wasn't in fstab. Also, automatic detection/mount of msdos hd is gone from install. uname -a reports wrong SNAP release: FreeBSD saturn.ben.com 2.1.0-950928-SNAP FreeBSD 2.1.0-950928-SNAP #0: Mon Oct 9 01:04:41 PDT 1995 root@myname.my.domain:/usr/src/sys/compile/SATURN i386 Looks like the one from a week before. Also, many libs from compat20.tgz are in the bindist. I assume this is so it doesn't have to change in the future, but maybe its unintentional. --Ben From owner-freebsd-bugs Mon Oct 9 03:38:27 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA06670 for bugs-outgoing; Mon, 9 Oct 1995 03:38:27 -0700 Received: from annax.tky.hut.fi (annax.tky.hut.fi [130.233.32.64]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA06665 for ; Mon, 9 Oct 1995 03:38:11 -0700 Received: from pooh.tky.hut.fi (root@pooh.tky.hut.fi [130.233.33.233]) by annax.tky.hut.fi (8.6.12/8.6.5) with ESMTP id MAA07637 for ; Mon, 9 Oct 1995 12:35:29 +0200 Received: by pooh.tky.hut.fi (MAA04586); Mon, 9 Oct 1995 12:37:34 +0200 Date: Mon, 9 Oct 1995 12:37:34 +0200 Message-Id: <199510091037.MAA04586@pooh.tky.hut.fi> From: "Timo J. Rinne" To: freebsd-bugs@freebsd.org Subject: [current] bug in /bin/sh Reply-To: tri@iki.fi Organization: Helsinki University of Technology, Otakaari 1, 02150 ESPOO, Finland Mime-version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-bugs@freebsd.org Precedence: bulk Something seems to be wrong in options.c of /bin/sh in current. Sorry, I don't have time to debug it further at this time. 104.pooh:tri> cat xxx echo "$0" 105.pooh:tri> (export ENV=xxx ; sh ) /usr/src/bin/sh/obj/sh $ ^D 106.pooh:tri> (export ENV=xxx ; /usr/src/bin/sh/obj/sh -c ls ) Memory fault in expand.c (varvalue()) 121.pooh:sh> grep '\$Id' options.c expand.c options.c: * $Id: options.c,v 1.5 1995/10/01 15:11:42 joerg Exp $ expand.c: * $Id: expand.c,v 1.4 1995/05/30 00:07:13 rgrimes Exp $ -- Timo J. Rinne, E-mail: tri@iki.fi WWW : http://www.iki.fi/tri/ Hi! I am a .signature virus. Copy me into your .signature to join in! *** PGP 2.3 public key available *** From owner-freebsd-bugs Mon Oct 9 05:59:28 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA09447 for bugs-outgoing; Mon, 9 Oct 1995 05:59:28 -0700 Received: from clark.net (root@clark.net [168.143.0.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA09442 for ; Mon, 9 Oct 1995 05:59:25 -0700 Received: from ras2.HAN.UnisysGSG.COM (ras2.HAN.UnisysGSG.COM [128.126.195.242]) by clark.net (8.6.12/8.6.5) with SMTP id IAA01751; Mon, 9 Oct 1995 08:59:17 -0400 Received: by ras2.HAN.UnisysGSG.COM with Microsoft Mail id <01BA9625.9D140040@ras2.HAN.UnisysGSG.COM>; Mon, 9 Oct 1995 08:59:59 -0400 Message-ID: <01BA9625.9D140040@ras2.HAN.UnisysGSG.COM> From: Mark Starner To: "'J Wunsch'" , Mark Starner Cc: "bugs@freebsd.org" , "moriya@ifi.unicamp.br" Subject: RE: Bug accessing /dev/cd1 Date: Mon, 9 Oct 1995 08:59:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk Yes, I tracked it down with nm and it is the same place (the bp = bh->lh_first; instruction) ---------- From: J Wunsch[SMTP:j@uriah.heep.sax.de] Sent: Sunday, October 08, 1995 11:15 PM To: Mark Starner Cc: bugs@freebsd.org; moriya@ifi.unicamp.br Subject: Re: Bug accessing /dev/cd1 As Mark Starner wrote: > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x10a > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf011efdc > code segment = base 0x0, limit 0xfffff, type 0x1b > processor eflags = interrupt enabled, resume IOPL=0 > current process = 133(cat) > interrupt mask = bio > panic: page fault > > syncing disks..................... 4 4 4 4 4 4 4 4 4 giving up > Automaitc reboot in 15 seconds - press a key on the console to abort > > ------- > > Is it easy to repair ? Unfortunately not. :-( I know only of two people where this happens: you, and Hellmuth Michaelis (but i believe it's a CD changer for him). I seem to remember that there's been another report from someone with two CDs, it happened for the second drive for him. I know of at least one person reliably operating a six-CD configuration under 2.0.5. This basically proves that it's not simply the _amount_ of CD drives available; it must be something else. You forgot to attach the appropriate part of your kernel's name list to your message, but i assume it's still the same. (It's also been the same spot in function incore() for Hellmuth Michaelis.) I guess I have to convince somebody of you to track it down with DDB... > The bug happens in line 694 of vfs_bio.c: > > 686 incore(struct vnode * vp, daddr_t blkno) > 687 { > 688 struct buf *bp; > 689 struct bufhashhdr *bh; > 690 > 691 int s = splbio(); > 692 > 693 bh = BUFHASH(vp, blkno); > 694 bp = bh->lh_first; > ^^^^ Yeah, well, anybody out there who understands the BUFHASH() macro??? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Oct 9 07:45:45 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12302 for bugs-outgoing; Mon, 9 Oct 1995 07:45:45 -0700 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA12296 for ; Mon, 9 Oct 1995 07:45:41 -0700 Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id KAA05947; Mon, 9 Oct 1995 10:42:49 -0400 Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id JAA12076; Mon, 9 Oct 1995 09:48:09 -0400 Date: Mon, 9 Oct 1995 09:48:09 -0400 From: Gene Stark Message-Id: <199510091348.JAA12076@starkhome.cs.sunysb.edu> To: clinet.fi!hsu@sbstark.cs.sunysb.edu Cc: bugs@freebsd.org In-reply-to: Heikki Suonsivu's message of Mon, 9 Oct 1995 01:42:44 +0200 Subject: kern/772: Stable panic References: <45a47j$9ln@starkhome.cs.sunysb.edu> Sender: owner-bugs@freebsd.org Precedence: bulk >panic: page fault >syncing disks .... 3 3 3 giving up >dumping to dev 20401 offset 278528 >dump 64 > >And then it gets stuck there. It seems to be always getting stuck >when it syncs the disks. I also saw another panic with slirp being >the current process, but did not take the address up that time. > >f012db90 T _chflags >f012dc8c T _fchflags >f012dd60 T _chmod >f012de60 T _fchmod >f012df3c T _chown >f012e03c T _fchown >f012e118 T _utimes This appears to be the same crash as #744 (which didn't get mailed to the list, for some reason). I had a crash dump for this, if anyone is interested. I hope I still have the symbols for that kernel... - Gene Stark From owner-freebsd-bugs Mon Oct 9 09:23:44 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15259 for bugs-outgoing; Mon, 9 Oct 1995 09:23:44 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15254 for ; Mon, 9 Oct 1995 09:23:42 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA08502; Mon, 9 Oct 1995 12:23:34 -0400 Date: Mon, 9 Oct 1995 12:23:34 -0400 From: "Garrett A. Wollman" Message-Id: <9510091623.AA08502@halloran-eldar.lcs.mit.edu> To: Lyndon Nerenberg VE7TCP Cc: freebsd-bugs@freefall.freebsd.org Subject: getbootfile() In-Reply-To: <199510080229.TAA20131@multivac.orthanc.com> References: <199510080229.TAA20131@multivac.orthanc.com> Sender: owner-bugs@FreeBSD.org Precedence: bulk < said: > FreeBSD I can't see how it would be generally useful. Not having > copies of the relevent POSIX standards at hand I'm curious as to > how this information can be obtained portably (if at all). POSIX does not make any guarantees that there even is such a thing as a file that has the kernel in it. POSIX doesn't even guarantee that there is a `kernel' at all. > Is this > routine being standardized at all? No. Any code that attempts to play around with the kernel's namelist is by definiton unportable. If anybody else wants to follow my lead, they are welcome to do so. > It seems that sysctl(3) is a > more logical place for this information to be obtained. You are certainly welcome to retrieve the kern.bootfile MIB varaible if you so desire. You will probably find that only FreeBSD supports this as well. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-bugs Mon Oct 9 10:00:02 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16091 for bugs-outgoing; Mon, 9 Oct 1995 10:00:02 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16083 ; Mon, 9 Oct 1995 10:00:01 -0700 Date: Mon, 9 Oct 1995 10:00:01 -0700 Message-Id: <199510091700.KAA16083@freefall.freebsd.org> To: freebsd-bugs Cc: From: "Garrett A. Wollman" Subject: bin/771: telnet character mode not set and broken when set - FDIV034 Reply-To: "Garrett A. Wollman" Sender: owner-bugs@FreeBSD.org Precedence: bulk The following reply was made to PR bin/771; it has been noted by GNATS. From: "Garrett A. Wollman" To: uhclem%nemesis@fw.ast.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: bin/771: telnet character mode not set and broken when set - FDIV034 Date: Mon, 9 Oct 1995 12:53:36 -0400 < 1. Between 1.1.5.1 and 2.0.5, telnet changed to default to non-raw > operating state to line-mode instead of character-at-a-time > mode. Wrong. TELNET negotiates what mode to use with the other end of the connection. There are three possible modes: 1) DONT LINEMODE, WILL ECHO - old character-at-a-time mode 2) DONT LINEMODE, WONT ECHO - old line-at-a-time mode 3) DO LINEMODE, WONT ECHO - new line-at-a-time mode The problems you report are very likely due to broken option negotiation on the part of the server TELNET, particularly for mode (3) which a lot of implementations have wrong or obsolete versions of if they implement it at all. The only way for anyone to diagnose this problem and determine which piece of software is at fault is to get a complete trace of options negotiation, which can be enabled by a `toggle opt' command at the TELNET prompt BEFORE opening the connection. What's `FDIV035' supposed to indicate? -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-bugs Mon Oct 9 10:26:37 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16535 for bugs-outgoing; Mon, 9 Oct 1995 10:26:37 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA16530 for ; Mon, 9 Oct 1995 10:26:30 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA11955; Mon, 9 Oct 1995 18:21:03 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id SAA03193; Mon, 9 Oct 1995 18:21:03 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id RAA02344; Mon, 9 Oct 1995 17:36:31 +0100 From: J Wunsch Message-Id: <199510091636.RAA02344@uriah.heep.sax.de> Subject: Re: Bug accessing /dev/cd1 To: starner@clark.net (Mark Starner) Date: Mon, 9 Oct 1995 17:36:30 +0100 (MET) Cc: starner@clark.net, bugs@freebsd.org, moriya@ifi.unicamp.br In-Reply-To: <01BA9625.9D140040@ras2.HAN.UnisysGSG.COM> from "Mark Starner" at Oct 9, 95 08:59:58 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 301 Sender: owner-bugs@freebsd.org Precedence: bulk As Mark Starner wrote: > Yes, I tracked it down with nm and it is the same place (the bp = bh->lh_first; instruction) I was afraid of 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 Mon Oct 9 10:28:01 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA16561 for bugs-outgoing; Mon, 9 Oct 1995 10:28:01 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA16520 for ; Mon, 9 Oct 1995 10:24:33 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA11951; Mon, 9 Oct 1995 18:21:02 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id SAA03192; Mon, 9 Oct 1995 18:21:02 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id RAA02329; Mon, 9 Oct 1995 17:35:43 +0100 From: J Wunsch Message-Id: <199510091635.RAA02329@uriah.heep.sax.de> Subject: Re: [current] bug in /bin/sh To: tri@iki.fi Date: Mon, 9 Oct 1995 17:35:43 +0100 (MET) Cc: freebsd-bugs@freebsd.org In-Reply-To: <199510091037.MAA04586@pooh.tky.hut.fi> from "Timo J. Rinne" at Oct 9, 95 12:37:34 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 568 Sender: owner-bugs@freebsd.org Precedence: bulk As Timo J. Rinne wrote: > > Something seems to be wrong in options.c of /bin/sh in current. > Sorry, I don't have time to debug it further at this time. > > 104.pooh:tri> cat xxx > echo "$0" > 105.pooh:tri> (export ENV=xxx ; sh ) > /usr/src/bin/sh/obj/sh > $ ^D > 106.pooh:tri> (export ENV=xxx ; /usr/src/bin/sh/obj/sh -c ls ) > Memory fault in expand.c (varvalue()) Sh...! Ok, my fault, gonna fix 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 Mon Oct 9 12:40:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA19906 for bugs-outgoing; Mon, 9 Oct 1995 12:40:05 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA19896 ; Mon, 9 Oct 1995 12:40:02 -0700 Resent-Date: Mon, 9 Oct 1995 12:40:02 -0700 Resent-Message-Id: <199510091940.MAA19896@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, hsu@clinet.fi Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA19880 for ; Mon, 9 Oct 1995 12:39:44 -0700 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id VAA01056 for ; Mon, 9 Oct 1995 21:39:30 +0200 Received: (root@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id VAA11514; Mon, 9 Oct 1995 21:39:29 +0200 Message-Id: <199510091939.VAA11514@katiska.clinet.fi> Date: Mon, 9 Oct 1995 21:39:29 +0200 From: Heikki Suonsivu Reply-To: hsu@clinet.fi To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/774: dump fails with "slave couldn't reopen disk: Device not configured" Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 774 >Category: kern >Synopsis: dump fails with "slave couldn't reopen disk: Device not configured" >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 9 12:40:01 PDT 1995 >Last-Modified: >Originator: Heikki Suonsivu >Organization: Clinet, Espoo, Finland >Release: FreeBSD 2.1-STABLE >Environment: Oct 8 22:50:37 katiska /kernel: CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) Oct 8 22:50:37 katiska /kernel: Origin = "GenuineIntel" Id = 0x524 Stepping =4 Oct 8 22:50:37 katiska /kernel: Features=0x1bf Oct 8 22:50:37 katiska /kernel: real memory = 67108864 (65536K bytes) Oct 8 22:50:37 katiska /kernel: avail memory = 62500864 (61036K bytes) Oct 8 22:50:37 katiska /kernel: Probing for devices on the ISA bus: Oct 8 22:50:38 katiska /kernel: ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16 384 on isa Oct 8 22:50:38 katiska /kernel: ed0: address 00:00:c0:cd:b9:a3, type WD8013EPC (16 bit) Oct 8 22:50:38 katiska /kernel: bpf: ed0 attached Oct 8 22:50:38 katiska /kernel: vt0 at 0x60-0x6f irq 1 on motherboard Oct 8 22:50:38 katiska /kernel: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Oct 8 22:50:38 katiska /kernel: lpt0 at 0x378-0x37f irq 7 on isa Oct 8 22:50:38 katiska /kernel: lpt0: Interrupt-driven port Oct 8 22:50:38 katiska /kernel: lp0: TCP/IP capable interface Oct 8 22:50:38 katiska /kernel: bpf: lp0 attached Oct 8 22:50:38 katiska /kernel: lpt1 not found at 0xffffffff Oct 8 22:50:38 katiska /kernel: lpt2 not found at 0xffffffff Oct 8 22:50:38 katiska /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Oct 8 22:50:38 katiska /kernel: sio0: type 16550A Oct 8 22:50:39 katiska /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Oct 8 22:50:39 katiska /kernel: sio1: type 16550A Oct 8 22:50:39 katiska /kernel: sio2 not found at 0x3e8 Oct 8 22:50:39 katiska /kernel: sio3 not found at 0x2e8 Oct 8 22:50:39 katiska /kernel: pca0 on isa Oct 8 22:50:39 katiska /kernel: pca0: PC speaker audio driver Oct 8 22:50:39 katiska /kernel: bt0 not found at 0x330 Oct 8 22:50:39 katiska /kernel: aha0 not found at 0x330 Oct 8 22:50:39 katiska /kernel: wdc0 not found at 0x1f0 Oct 8 22:50:39 katiska /kernel: wdc1 not found at 0x170 Oct 8 22:50:39 katiska /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Oct 8 22:50:39 katiska /kernel: fdc0: NEC 765 Oct 8 22:50:39 katiska /kernel: fd0: 1.44MB 3.5in Oct 8 22:50:39 katiska /kernel: mcd0: timeout getting status Oct 8 22:50:39 katiska /kernel: mcd0 not found at 0x300 Oct 8 22:50:39 katiska /kernel: le0: no board found at 0x300 Oct 8 22:50:39 katiska /kernel: le0 not found at 0x300 Oct 8 22:50:39 katiska /kernel: npx0 on motherboard Oct 8 22:50:39 katiska /kernel: npx0: INT 16 interface Oct 8 22:50:39 katiska /kernel: matcdc0 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc1 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc2 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: matcdc3 not found at 0xffffffff Oct 8 22:50:39 katiska /kernel: bio_imask c0000040 tty_imask c00300ba net_imask c00300ba Oct 8 22:50:39 katiska /kernel: Probing for devices on the PCI bus: Oct 8 22:50:39 katiska /kernel: chip0 rev 0 on pci0:0 Oct 8 22:50:39 katiska /kernel: chip1 rev 0 on pci0:1 Oct 8 22:50:39 katiska /kernel: ncr0 rev 1 int a irq 11 on pc i0:13 Oct 8 22:50:39 katiska /kernel: ncr0: restart (scsi reset). Oct 8 22:50:39 katiska /kernel: ncr0 scanning for targets 0..6 (V2 pl22 95/07/0 7) Oct 8 22:50:39 katiska /kernel: ncr0 waiting for scsi devices to settle Oct 8 22:50:39 katiska /kernel: (ncr0:0:0): "SEAGATE ST15230N 0298" type 0 fixe d SCSI 2 Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): Direct-Access Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:39 katiska /kernel: 4095MB (8386733 512 byte sectors) Oct 8 22:50:39 katiska /kernel: sd0(ncr0:0:0): with 3992 cyls, 19 heads, and an average 110 sectors/track Oct 8 22:50:39 katiska /kernel: (ncr0:3:0): 200ns (5 Mb/sec) offset 8. Oct 8 22:50:39 katiska /kernel: (ncr0:3:0): "IBM 0662S12 !O 2 23" type 0 fixed SCSI 2 Oct 8 22:50:39 katiska /kernel: sd3(ncr0:3:0): Direct-Access Oct 8 22:50:39 katiska /kernel: sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:39 katiska /kernel: 1003MB (2055035 512 byte sectors) Oct 8 22:50:40 katiska /kernel: sd3(ncr0:3:0): with 4119 cyls, 5 heads, and an average 99 sectors/track Oct 8 22:50:40 katiska /kernel: ncr1 rev 2 int a irq 12 on pc i0:15 Oct 8 22:50:40 katiska /kernel: ncr1: restart (scsi reset). Oct 8 22:50:40 katiska /kernel: ncr1 scanning for targets 0..6 (V2 pl22 95/07/0 7) Oct 8 22:50:40 katiska /kernel: ncr1 waiting for scsi devices to settle Oct 8 22:50:40 katiska /kernel: (ncr1:3:0): "SEAGATE ST15230N 0168" type 0 fixe d SCSI 2 Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): Direct-Access Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:40 katiska /kernel: 4095MB (8386733 512 byte sectors) Oct 8 22:50:40 katiska /kernel: sd7(ncr1:3:0): with 3992 cyls, 19 heads, and an average 110 sectors/track Oct 8 22:50:40 katiska /kernel: (ncr1:4:0): "HP C1533A 9503" type 1 removable S CSI 2 Oct 8 22:50:40 katiska /kernel: st7(ncr1:4:0): Sequential-Access Oct 8 22:50:40 katiska /kernel: st7(ncr1:4:0): FAST SCSI-2 100ns (10 Mb/sec) of fset 8. Oct 8 22:50:40 katiska /kernel: density code 0x24, variable blocks, write-enabl ed Oct 8 22:50:40 katiska /kernel: vga0 rev 0 on pci0:17 Oct 8 22:50:40 katiska /kernel: changing root device to sd0a Oct 8 22:50:40 katiska /kernel: bpf: ds0 attached Oct 8 22:50:40 katiska /kernel: bpf: lo0 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp0 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp1 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp2 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp3 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp4 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp5 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp6 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp7 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp8 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp9 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp10 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp11 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp12 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp13 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp14 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp15 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp16 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp17 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp18 attached Oct 8 22:50:40 katiska /kernel: bpf: ppp19 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp20 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp21 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp22 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp23 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp24 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp25 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp26 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp27 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp28 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp29 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp30 attached Oct 8 22:50:41 katiska /kernel: bpf: ppp31 attached Oct 8 22:50:41 katiska /kernel: bpf: sl0 attached Oct 8 22:50:41 katiska /kernel: bpf: sl1 attached Oct 8 22:50:41 katiska /kernel: bpf: sl2 attached Oct 8 22:50:41 katiska /kernel: bpf: sl3 attached Oct 8 22:50:41 katiska /kernel: bpf: sl4 attached Oct 8 22:50:41 katiska /kernel: bpf: sl5 attached Oct 8 22:50:41 katiska /kernel: bpf: sl6 attached Oct 8 22:50:41 katiska /kernel: bpf: sl7 attached Oct 8 22:50:41 katiska /kernel: bpf: sl8 attached Oct 8 22:50:41 katiska /kernel: bpf: sl9 attached Oct 8 22:50:41 katiska /kernel: bpf: sl10 attached Oct 8 22:50:41 katiska /kernel: bpf: sl11 attached Oct 8 22:50:41 katiska /kernel: bpf: sl12 attached Oct 8 22:50:41 katiska /kernel: bpf: sl13 attached Oct 8 22:50:41 katiska /kernel: bpf: sl14 attached Oct 8 22:50:41 katiska /kernel: bpf: sl15 attached Oct 8 22:50:41 katiska /kernel: bpf: tun0 attached Oct 8 22:50:41 katiska /kernel: WARNING: / was not properly dismounted. Oct 8 22:50:41 katiska /kernel: sd7: invalid primary partition table: no magic Oct 8 22:50:41 katiska last message repeated 2 times Oct 8 22:50:42 katiska lpd[128]: restarted # # CLINETSERVER - a bloated kernel for servers, include everything possible # # $Id: LINT,v 1.150 1995/03/04 21:09:21 jkh Exp $ # # # This directive is mandatory; it defines the architecture to be # configured for; in this case, the 386 family. You must also specify # at least one CPU (the one you intend to run on); deleting the # specification for CPUs you don't need to use may make parts of the # system run faster # # clinet: we have got all of these machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) # # This is the ``identification'' of the kernel. Usually this should # be the same as the name of your kernel. # ident CLINETSERVER # # The `maxusers' parameter controls the static sizing of a number of # internal system tables by a complicated formula defined in param.c. # maxusers 256 options "NMBCLUSTERS=2048" options "TTYHOG=4096" options "RS_IBUFSIZE=1024" # # Under some circumstances it is necessary to make the default max # number of proccesses per user and open files per user more than the # defaults on bootup. (an example is a large news server in which # the uid, news, can sometimes need > 100 simultaneous processes running) # clinet: or hoggy administrators with gazillion xterms (yes, I have run out # of 128 processes :-) options "CHILD_MAX=256" options "OPEN_MAX=256" # # A math emulator is mandatory if you wish to run on hardware which # does not have a floating-point processor. Pick either the original, # bogus (but freely-distributable) math emulator, or a much more # fully-featured but GPL-licensed emulator taken from Linux. # options MATH_EMULATE #Support for x87 emulation #options GPL_MATH_EMULATE #Support for x87 emualtion via #new math emulator # # This directive defines a number of things: # - The compiled kernel is to be called `kernel' # - The root filesystem might be on partition wd0a # - The kernel can swap on wd0b and sd0b, defaulting to the former # - Crash dumps will be written to wd0b, if possible # # clinet: we use 4 disks per server, swap distributed on all of them (speeds # up considerably). Dumps may go to sd0. config kernel root on wd0 swap on wd0 and wd1 and sd0 and sd1 and sd2 and sd3 and vn0 dumps on sd0 ##################################################################### # COMPATIBILITY OPTIONS # # Implement system calls compatible with 4.3BSD and older versions of # FreeBSD. # options "COMPAT_43" # # Allow user-mode programs to manipulat their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of). # options USER_LDT #allow user-level control of i386 ldt # # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # options SYSVSHM options SYSVSEM options SYSVMSG ##################################################################### # DEBUGGING OPTIONS # # Enable the kernel debugger. # # options DDB # # Enable dumping of the kernel image to swap for panics. This is not # the default because writing to misconfigured swap may wipe out file # systems. # options DODUMP # # KTRACE enables the system-call tracing facility ktrace(2). # options KTRACE #kernel tracing # # The DIAGNOSTIC option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # options DIAGNOSTIC # # Allow ordinary users to take the console - this is useful for X. options UCONSOLE ##################################################################### # NETWORKING OPTIONS # # Protocol families: # Only the INET (Internet) family is officially supported in FreeBSD. # Source code for the NS (Xerox Network Service), ISO (OSI), and # CCITT (X.25) families is provided for amusement value, although we # try to ensure that it actually compiles. # options INET #Internet communications protocols # options ISO # options CCITT #X.25 network layer # options NS #Xerox NS communications protocols # options TPIP #ISO TP class 4 over IP # options TPCONS #ISO TP class 0 over X.25 # # Network interfaces: # The `loop' pseudo-device is mandatory when networking is enabled. # The `ether' pseudo-device provides generic code to handle # Ethernets; it is mandatory when a Ethernet device driver is # configured. # The `sppp' pseudo-device serves a similar role for certain types # of synchronous PPP links (like `cx'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. # The `disc' pseudo-device implements a minimal network interface, # which throws away all packets sent and never receives any. It is # included for testing purposes. # The `tun' pseudo-device implements the User Process PPP (iijppp) # pseudo-device ether #Generic Ethernet pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device sl 16 #Serial Line IP pseudo-device ppp 32 #Point-to-point protocol pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver(user process ppp) #options NSIP #XNS over IP #options EON #ISO CLNP over IP #options LLC #X.25 link layer for Ethernets #options HDLC #X.25 link layer for serial lines # # Internet family options: # # TCP_COMPAT_42 causes the TCP code to emulate certain bugs present in # 4.2BSD. This option should not be used unless you have a 4.2BSD # machine and TCP connections fail. # # GATEWAY allows the machine to forward packets, and also configures # larger static sizes of a number of system tables. # # MROUTING enables the kernel multicast packet forwarder, which works # with mrouted(8). # # IPFIREWALL enables support for IP firewall construction, in # conjunction with the `ipfw' program. IPFIREWALL_VERBOSE does # the obvious thing. # # ARP_PROXYALL enables global proxy ARP. Beware! This can burn # your house down! See netinet/if_ether.c for the gory details. # (Eventually there will be a better management interface.) # options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options GATEWAY #internetwork gateway options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets #options ARP_PROXYALL # global proxy ARP ##################################################################### # FILESYSTEM OPTIONS # # Only the root, /usr, and /tmp filesystems need be statically # compiled; everything else will be automatically loaded at mount # time. (Exception: the UFS family---FFS, MFS, and LFS---cannot # currently be demand-loaded.) Some people still prefer to statically # compile other filesystems as well. # # NB: The LFS, PORTAL, and UNION filesystems are known to be buggy, # and WILL panic your system if you attempt to do anything with them. # They are included here as an incentive for some enterprising soul to # sit down and fix them. # # One of these is mandatory: options FFS #Fast filesystem options NFS #Network File System # The rest are optional: options "CD9660" #ISO 9660 filesystem options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options LFS #Log filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System options NULLFS #NULL filesystem options PORTAL #Portal filesystem options PROCFS #Process filesystem options UMAPFS #UID map filesystem options UNION #Union filesystem # # Disk quotas are supported when this option is enabled. If you # change the value of this option, you must do a `make clean' in your # kernel compile directory in order to get a working kernel. # #options QUOTA #enable disk quotas # # PCI devices: # # The main PCI bus device is `pci'. It provides auto-detection and # configuration support for all devices on the PCI bus, using either # configuration mode defined in the PCI specification. # # The `ncr' device provides support for the NCR 53C810 and 53C825 # self-contained SCSI host adapters. # # The `de' device provides support for the Digital Equipment DC21040 # self-contained Ethernet adapter. # # The PROBE_VERBOSE option enables a long listing of chip set registers # for supported PCI chip sets (currently only intel Saturn and Mercury). # controller pci0 device ncr0 device de0 options PROBE_VERBOSE options "SCSI_DELAY=10" ##################################################################### # SCSI DEVICE CONFIGURATION # # The SCSI subsystem consists of the `base' SCSI code, a number of # high-level SCSI device `type' drivers, and the low-level host-adapter # device drivers. The host adapters are listed in the ISA and PCI # device configuration sections below. # # Beginning with FreeBSD 2.1 you can wire down your SCSI devices so # that a given bus, target, and LUN always come on line as the same # device unit. In earlier versions the unit numbers were assigned # in the order that the devices were probed on the SCSI bus. This # means that if you removed a disk drive, you may have had to rewrite # your /etc/fstab file, and also that you had to be careful when adding # a new disk as it may have been probed earlier and moved your device # configuration around. # This old behavior is maintained as the default behavior. The unit # assignment begins with the first non-wired down unit for a device # type. For example, if you wire a disk as "sd3" then the first # non-wired disk will be assigned sd4. # The syntax for wiring down devices is: # disk sd0 at scbus0 target 0 unit 0 # disk sd1 at scbus0 target 1 # disk sd2 at scbus0 target 3 # tape st1 at scbus0 target 6 # device cd0 at scbus? # "units" (SCSI logical unit number) that are not specified are # treated as if specified as LUN 0. # All SCSI devices allocate as many units as are required. # The "unknown" device (uk? in pre-2.1) is now part of the base SCSI # configuration and doesn't have to be explicitly configured. controller scbus0 #base SCSI code device ch0 #SCSI media changers device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 disk sd4 at scbus0 target 4 disk sd5 at scbus0 target 5 disk sd6 at scbus0 target 6 tape st0 at scbus0 target 0 tape st1 at scbus0 target 1 tape st2 at scbus0 target 2 tape st3 at scbus0 target 3 tape st4 at scbus0 target 4 tape st5 at scbus0 target 5 tape st6 at scbus0 target 6 device cd0 at scbus0 target 0 device cd1 at scbus0 target 1 device cd2 at scbus0 target 2 device cd3 at scbus0 target 3 device cd4 at scbus0 target 4 device cd5 at scbus0 target 5 device cd6 at scbus0 target 6 # SCSIDEBUG: When defined enables debugging macros # NO_SCSI_SENSE: When defined disables sense descriptions (about 4k) # SCSI_REPORT_GEOMETRY: Always report disk geometry at boot up instead # of only when booting verbosely. #options SCSIDEBUG #options NO_SCSI_SENSE options SCSI_REPORT_GEOMETRY ##################################################################### # MISCELLANEOUS DEVICES AND OPTIONS # # Of these, only the `log' device is truly mandatory. The `pty' # device usually turns out to be ``effectively mandatory'', as it is # required for `telnetd', `rlogind', `screen', `emacs', and `xterm', # among others. # pseudo-device pty 256 #Pseudo ttys - can go as high as 64 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. ##################################################################### # HARDWARE DEVICE CONFIGURATION # ISA and EISA devices: # Currently there is no separate support for EISA. There should be. # Micro Channel is not supported at all. # # Mandatory ISA devices: isa, sc, npx # controller isa0 # # Options for `isa': # # ALLOW_CONFLICT_DRQ suppresses the DMA conflict checks. This option is # included so that people with sound cards that support multiple emulations # can setup different sound drivers on the same DMA channel. There are no # other known uses for this option. # # ALLOW_CONFLICT_IOADDR suppresses the I/O address conflict checks, so # that the PS/2 mouse driver doesn't conflict with the console driver. # # ALLOW_CONFLICT_IRQ suppresses the interrupt line conflict checks, so # that multiple devices can share the same IRQ, provided that the # hardware supports it (it usually doesn't). # # ALLOW_CONFLICT_MEMADDR suppresses the memory address conflict checks. # This option is not known to be good for anything. # # AUTO_EOI_1 enables the `automatic EOI' feature for the master 8259A # interrupt controller. This saves about 1.25 usec for each interrupt. # No problems are known to be caused by this option. # # AUTO_EOI_2 enables the `automatic EOI' feature for the slave 8259A # interrupt controller. This saves about 1.25 usec for each interrupt. # Automatic EOI is documented not to work for for the slave with the # original i8259A, but it works for some clones and some integrated # versions. # # BOUNCE_BUFFERS provides support for ISA DMA on machines with more # than 16 megabytes of memory. It doesn't hurt on other machines. # Some broken EISA and VLB hardware may need this, too. # # DUMMY_NOPS disables extra delays for some bus operations. The delays # are mostly for older systems and aren't used consistently. Probably # works OK on most EISA bus machines. # # TUNE_1542 enables the automatic ISA bus speed selection for the # Adaptec 1542 boards. Does not work for all boards, use it with caution. # #options ALLOW_CONFLICT_DRQ #options ALLOW_CONFLICT_IOADDR #options ALLOW_CONFLICT_IRQ #options ALLOW_CONFLICT_MEMADDR options "AUTO_EOI_1" #options "AUTO_EOI_2" options BOUNCE_BUFFERS #options DUMMY_NOPS #options TUNE_1542 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.1 options XSERVER # include code for XFree86 options FAT_CURSOR # start with block cursor # The syscons console driver (sco color console compatible) - default. #device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr #options "NCONS=4" # # Options for `sc': # # HARDFONTS allows the driver to load an ISO-8859-1 font to replace # the default font in your display adapter's memory. # options HARDFONTS # # MAXCONS is maximum number of virtual consoles, no more than 16 # default value: 12 # options "MAXCONS=16" device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Optional ISA and EISA devices: # # # SCSI host adapters: `aha', `ahb', `aic', `bt', `nca' # # aha: Adaptec 154x # ahb: Adaptec 174x # ahc: Adaptec 274x # aic: Adaptec 152x and sound cards using the Adaptec AIC-6360 (slow!) # bt: Most Buslogic controllers # nca: ProAudioSpectrum cards using the NCR 5380 or Trantor T130 # uha: UltraStore 14F and 34F # sea: Seagate ST01/02 8 bit controller (slow!) # wds: Western Digital WD7000 controller (no scatter/gather!). # # Note that the order is important in order for Buslogic cards to be # probed correctly. # controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr #controller ahc0 at isa? bio irq ? vector ahcintr # port??? iomem? #controller ahb0 at isa? bio irq ? vector ahbintr controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x1f84 #controller nca2 at isa? port 0x1f8c #controller nca3 at isa? port 0x1e88 #controller nca4 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xdc000 iosiz 0x2000 vector seaintr #controller wds0 at isa? port 0x350 bio irq 15 drq 6 vector wdsintr # # ST-506, ESDI, and IDE hard disks: `wdc' and `wd' # # NB: ``Enhanced IDE'' is NOT supported at this time. # controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # # Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft' # controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 tape ft0 at fdc0 drive 2 # # Options for `fd': # # FDSEEKWAIT selects a non-default head-settle time (i.e., the time to # wait after a seek is performed). The default value (1/32 s) is # usually sufficient. The units are inverse seconds, so a value of 16 # here means to wait 1/16th of a second; you should choose a power of # two. # #options FDSEEKWAIT="16" # # Other standard PC hardware: `lpt', `mse', `psm', `sio', etc. # # lpt: printer port # mse: Logitech and ATI InPort bus mouse ports # psm: PS/2 mouse port (needs ALLOW_CONFLICT_IOADDR, above) # sio: serial ports (see sio(4)) # cy: Cyclades high-speed serial driver (ALPHA QUALITY!) # gp: National Instruments AT-GPIB and AT-GPIB/TNT board # gsc: Genius GS-4500 hand scanner. # joy: joystick device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty device lpt2 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? port "IO_KBD" tty irq 12 vector psmintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr #device gp0 at isa? port 0x2c0 tty #device gsc0 at isa? port "IO_GSC1" tty drq 3 #device joy0 at isa? port "IO_GAME" #device cy0 at isa? tty irq 10 iomem 0xd4000 vector cyintr # Options for sio: #options COMCONSOLE #prefer serial console to video console options COM_MULTIPORT #code for some cards with shared IRQs #options DSI_SOFT_MODEM #code for DSI Softmodems # # Network interfaces: `cx', `ed', `el', `ep', `ie', `is', `le', `lnc' # # cx: Cronyx/Sigma multiport sync/async (with Cisco or PPP framing) # ed: Western Digital and SMC 80xx; Novell NE1000 and NE2000; 3Com 3C503 # el: 3Com 3C501 (slow!) # ep: 3Com 3C509 (buggy) # ie: AT&T StarLAN 10 and EN100; 3Com 3C507; unknown NI5210 # le: Digital Equipment EtherWorks 2 and EtherWorks 3 (DEPCA, DE100, # DE101, DE200, DE201, DE202, DE203, DE204, DE205, DE422) # lnc: Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL) # ze: IBM/National Semiconductor PCMCIA ethernet controller. # zp: 3Com PCMCIA Etherlink III (It does not require shared memory for # send/receive operation, but it needs 'iomem' to read/write the # attribute memory) # #device cx0 at isa? port 0x240 net irq 15 drq 7 vector cxintr device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device el0 at isa? port 0x300 net irq 9 vector elintr device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr # ISDN drivers - `isdn'. # # Uncomment one (and only one) of the following 4 drivers for the appropriate # ISDN device you have. For more information on what's considered appropriate # for your given set of circumstances, please read # /usr/src/gnu/usr.sbin/docs/INSTALL. It's a bit sparse at present, but it's # the best we have right now. The snic driver is also disabled at present, # waiting for someone to upgrade the driver to 2.0 (it's in /sys/gnu/scsi/). # #device nic0 at isa? port "IO_COM3" iomem 0xe0000 tty irq 9 vector nicintr #device nnic0 at isa? port 0x150 iomem 0xe0000 tty irq 12 vector nnicintr # This one is also temporarily ill - needs an isa_device structure!! #controller tel0 at isa? iomem 0xe0000 tty irq 9 vector telintr # These are non-optional for ISDN #pseudo-device isdn #pseudo-device ii 4 #pseudo-device ity 4 #pseudo-device itel 2 #pseudo-device ispy 1 # # Audio drivers: `snd', `pca' # # snd: Voxware sound drivers for various cards # see /usr/src/sys/i386/isa/sound/sound.doc for details # pca: PCM audio through your PC speaker # #options AUDIO_PAS #options AUDIO_SB #options AUDIO_ADLIB #options AUDIO_GUS #options AUDIO_MPU401 #options AUDIO_UART6850 #options AUDIO_PSS #options AUDIO_GUS16 #options AUDIO_GUSMAX #options AUDIO_MSS #options AUDIO_SBPRO #options AUDIO_SB16 #options AUDIO_YM3812 #device snd10 at isa? port 0x530 irq 10 drq 1 vector adintr #device snd5 at isa? port 0x330 irq 6 vector mpuintr #device snd4 at isa? port 0x220 irq 15 drq 6 vector gusintr #device snd3 at isa? port 0x388 irq 10 drq 6 vector pasintr #device snd2 at isa? port 0x220 irq 7 drq 1 vector sbintr #device snd6 at isa? port 0x220 irq 7 drq 5 vector sbintr #device snd7 at isa? port 0x300 #device snd1 at isa? port 0x388 device pca0 at isa? tty # # Miscellaneous hardware: `mcd', `wt', `ctx', `apm' # # mcd: Mitsumi CD-ROM # scd: Sony CD-ROM # matcd: Matsushita/Panasonic CD-ROM # wt: Wangtek and Archive QIC-02/QIC-36 tape drives # ctx: Cortex-I frame grabber # apm: Laptop Advanced Power Management (experimental) # spigot: The Creative Labs Video Spigot video-aquisition board # # Notes on the spigot: # The video spigot is at 0xad6. This port address can not be changed. # The irq values may only be 10, 11, or 15 # I/O memory is an 8kb region. Possible values are: # 0a0000, 0a2000, ..., 0fffff, f00000, f02000, ..., ffffff # Note that the start address must be on an even boundary. device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr # for the Sony CDU31/33A CDROM #device scd0 at isa? port 0x230 bio # for the soundblaster 16 multicd - up to 4 devices controller matcd0 at isa? port ? controller matcd1 at isa? port ? controller matcd2 at isa? port ? controller matcd3 at isa? port ? #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device ctx0 at isa? port 0x230 iomem 0xd0000 #device spigot0 at isa? port 0xad6 irq 15 iomem 0xee000 vector spigintr #device apm0 at isa? >Description: I switched Seagate hawk (31200N) to IBM 0662, and backups started failing with + /sbin/dump 0ubf 128 - /dev/sd3f + /bin/dd ibs=64k obs=1024k of=/dev/nrst7 DUMP: Date of this level 0 dump: Mon Oct 9 03:11:46 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd3f (/var) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 176780 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: slave couldn't reopen disk: Device not configured DUMP: The ENTIRE dump is aborted. 0+0 records in 0+0 records out 0 bytes transferred in 6 secs (0 bytes/sec) The disk *may* have been taken from 1.1.5.1 system, I'm not sure if it has a slice table at all. I just relabeled it. The partition configuration is similar as it was on seagate hawk 31200. >How-To-Repeat: Repeats every night here, all partitions on this disk fail, while all other disks are successfully backed up. >Fix: Don't know. Maybe go back to seagate hawk 31200. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Mon Oct 9 15:06:17 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA25593 for bugs-outgoing; Mon, 9 Oct 1995 15:06:17 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA25573 for ; Mon, 9 Oct 1995 15:06:08 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA19273; Mon, 9 Oct 1995 23:05:50 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA05273; Mon, 9 Oct 1995 23:05:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id WAA00371; Mon, 9 Oct 1995 22:53:52 +0100 From: J Wunsch Message-Id: <199510092153.WAA00371@uriah.heep.sax.de> Subject: Re: [current] bug in /bin/sh To: freebsd-bugs@freebsd.org Date: Mon, 9 Oct 1995 22:53:52 +0100 (MET) Cc: tri@iki.fi Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199510091635.RAA02329@uriah.heep.sax.de> from "J Wunsch" at Oct 9, 95 05:35:43 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 402 Sender: owner-bugs@freebsd.org Precedence: bulk As J Wunsch wrote: > > > 106.pooh:tri> (export ENV=xxx ; /usr/src/bin/sh/obj/sh -c ls ) > > Memory fault in expand.c (varvalue()) > > Sh...! Ok, my fault, gonna fix it. Fixed. It has been a special problem of this $ENV pre-processing. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-bugs Mon Oct 9 18:30:02 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA00874 for bugs-outgoing; Mon, 9 Oct 1995 18:30:02 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA00868 ; Mon, 9 Oct 1995 18:30:01 -0700 Date: Mon, 9 Oct 1995 18:30:01 -0700 Message-Id: <199510100130.SAA00868@freefall.freebsd.org> To: freebsd-bugs Cc: From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Subject: re: bin/771: telnet - FDIV035 Reply-To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sender: owner-bugs@FreeBSD.org Precedence: bulk The following reply was made to PR bin/771; it has been noted by GNATS. From: uhclem%nemesis@fw.ast.com (Frank Durda IV) To: wollman@lcs.mit.edu, FreeBSD-gnats-submit@freebsd.org Cc: Subject: re: bin/771: telnet - FDIV035 Date: Mon, 9 Oct 95 20:21 WET DST [0]The problems you report are very likely due to broken option [0]negotiation on the part of the server TELNET, particularly for mode [0](3) which a lot of implementations have wrong or obsolete versions of [0]if they implement it at all. The only way for anyone to diagnose this [0]problem and determine which piece of software is at fault is to get a [0]complete trace of options negotiation, which can be enabled by a [0]`toggle opt' command at the TELNET prompt BEFORE opening the [0]connection. Ok, then I say that the negotiation in 2.1.0 and in 2.0.5 is broken. It works under 1.1.5.1. Still, the ability to telnet is broken in 2.1.0 badly enough to limit its use. Here are the configurations I know about: 1.1.5.1 -> 1.1.5.1 worked 2.0.5 -> 1.1.5.1 worked 2.1.0 -> 2.0.5 fails 2.0.5 -> 2.0.5 fails 2.1.0 -> 2.1.0 fails 1.1.5.1 -> SCO worked 2.1.0 -> SCO fails 1.1.5.1 -> SUN OS worked 2.1.0 -> SUN OS fails (Sorry, but not every possible combination is available to me at this time. But it should be pretty obvious from the examples that something changed in 2.0.5 and something broke in 2.1.0, and that 2.0.5 telnetting to itself and 2.1.0 telnetting to itself.) I am not saying everything fails in the 2.0.x and 2.1.x versions, but at least one item mentioned in the problem report. [0]The only way for anyone to diagnose this problem and determine which [0]piece of software is at fault is to get a complete trace of options [0]negotiation, which can be enabled by a `toggle opt' command at the [0]TELNET prompt BEFORE opening the connection. I will do this. Are you the person who is going to research this problem that I should send this information to? If so, I will also send the sample executable that demonstrates the failed [ENTER] operation. You can assist by selecting the configurations and combinations that are "interesting", although it seems that most of the failing ones can be easily checked by anybody. [0]What's `FDIV035' supposed to indicate? That is my own problem report tracking code. It helps me track down old problems I have reported that show up in the "currently open" list, and I will re-test on receipt of new releases and quite frequently close them, rather than forget about them and let them hang around longer than they should. So, it is for my information, that's all. Frank Durda IV |"The Knights who say LETNi or uhclem@nemesis.lonestar.org | demand... A SEGMENT REGISTER!!!" ...uhclem@lerctr.lonestar.org |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-bugs Mon Oct 9 20:20:54 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA05156 for bugs-outgoing; Mon, 9 Oct 1995 20:20:54 -0700 Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id UAA05151 for ; Mon, 9 Oct 1995 20:20:47 -0700 Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA29035; Mon, 9 Oct 1995 23:20:14 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 9 Oct 1995 23:20 EDT Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.11/8.6.5) with ESMTP id VAA02999; Mon, 9 Oct 1995 21:47:29 -0400 Received: (from rivers@localhost) by lakes (8.6.11/8.6.9) id WAA01689; Mon, 9 Oct 1995 22:02:38 -0400 Date: Mon, 9 Oct 1995 22:02:38 -0400 From: Thomas David Rivers Message-Id: <199510100202.WAA01689@lakes> To: lcs.mit.edu!wollman@dg-rtp.dg.com, lyndon@orthanc.com Subject: Re: getbootfile() Cc: freebsd-bugs@freefall.freebsd.org Content-Type: text Content-Length: 644 Sender: owner-bugs@FreeBSD.org Precedence: bulk > > < said: > > > FreeBSD I can't see how it would be generally useful. Not having > > copies of the relevent POSIX standards at hand I'm curious as to > > how this information can be obtained portably (if at all). > > POSIX does not make any guarantees that there even is such a thing as > a file that has the kernel in it. POSIX doesn't even guarantee that > there is a `kernel' at all. Particularly true for the MVS (IBM 370) POSIX system; if you want to figure out just what POSIX allows to be missing - try writing a program there! - Dave Rivers - From owner-freebsd-bugs Mon Oct 9 20:51:17 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA06951 for bugs-outgoing; Mon, 9 Oct 1995 20:51:17 -0700 Received: from gateway.sequent.com (gateway.sequent.com [138.95.18.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA06946 for ; Mon, 9 Oct 1995 20:51:12 -0700 Received: from crg8.sequent.com (crg8.sequent.com [138.95.19.9]) by gateway.sequent.com (8.6.12/8.6.9) with ESMTP id UAA00845 for ; Mon, 9 Oct 1995 20:50:33 -0700 Received: from localhost (bjj@localhost) by crg8.sequent.com (8.6.12/8.6.9) with SMTP id UAA20555 for ; Mon, 9 Oct 1995 20:49:15 -0700 Message-Id: <199510100349.UAA20555@crg8.sequent.com> X-Authentication-Warning: crg8.sequent.com: Host localhost didn't use HELO protocol To: bugs@freebsd.org Subject: 2.1.0-951005-SNAP /usr/bin/telnet broken? Date: Mon, 09 Oct 95 20:48:59 PDT From: Ben Jackson Sender: owner-bugs@freebsd.org Precedence: bulk I got: $ telnet crg8 ld.so failed: Undefined symbol "_enctype_names" in telnet:telnet info: $ ldd =telnet /usr/bin/telnet: -ltermcap.2 => /usr/lib/libtermcap.so.2.1 (0x802b000) -ltelnet.2 => /usr/lib/libtelnet.so.2.0 (0x802f000) -lc.2 => /usr/lib/libc.so.2.2 (0x8031000) $ ll =telnet -r-xr-xr-x 1 bin bin 77824 Sep 29 07:03 /usr/bin/telnet* a rebuilt one from the source dist works. --Ben From owner-freebsd-bugs Tue Oct 10 09:11:17 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA24091 for bugs-outgoing; Tue, 10 Oct 1995 09:11:17 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA24086 for ; Tue, 10 Oct 1995 09:11:14 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15865(4)>; Tue, 10 Oct 1995 09:00:49 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177475>; Tue, 10 Oct 1995 09:00:37 -0700 To: uhclem%nemesis@fw.ast.com (Frank Durda IV) cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/771: telnet - FDIV035 In-reply-to: Your message of "Mon, 09 Oct 95 18:30:01 PDT." <199510100130.SAA00868@freefall.freebsd.org> Date: Tue, 10 Oct 1995 09:00:29 PDT From: Bill Fenner Message-Id: <95Oct10.090037pdt.177475@crevenia.parc.xerox.com> Sender: owner-bugs@FreeBSD.org Precedence: bulk In message <199510100130.SAA00868@freefall.freebsd.org> Garrett wrote: > The problems you report are very likely due to broken option > negotiation on the part of the server TELNET, particularly for mode > (3) which a lot of implementations have wrong or obsolete versions of > if they implement it at all. Using a -stable sup'd on saturday, I can telnet to myself and duplicate Frank's problem #2 (related to control-D). It doesn't happen when connecting from -stable to a SunOS 4.1.3 box. Bill (To self: Trying 13.0.208.199... Connected to fenestro.parc.xerox.com. Escape character is '^]'. SENT DO ENCRYPT SENT WILL ENCRYPT SENT DO SUPPRESS GO AHEAD SENT WILL TERMINAL TYPE SENT WILL NAWS SENT WILL TSPEED SENT WILL LFLOW SENT WILL LINEMODE SENT WILL NEW-ENVIRON SENT DO STATUS SENT WILL XDISPLOC RCVD DO AUTHENTICATION SENT WONT AUTHENTICATION RCVD WILL ENCRYPT SENT IAC SB ENCRYPT SUPPORT RCVD DO ENCRYPT RCVD IAC SB ENCRYPT SUPPORT RCVD WILL SUPPRESS GO AHEAD RCVD DO TERMINAL TYPE RCVD DO NAWS SENT IAC SB NAWS 0 80 (80) 0 24 (24) RCVD DO TSPEED RCVD DO LFLOW RCVD DO LINEMODE SENT IAC SB LINEMODE SLC SYNCH DEFAULT 0; IP VARIABLE|FLUSHIN|FLUSHOUT 3; AO VARIABLE 15; AYT NOSUPPORT 255; ABORT VARIABLE|FLUSHIN|FLUSHOUT 28; EOF VARIABLE 4; SUSP VARIABLE|FLUSHIN 26; EC VARIABLE 8; EL VARIABLE 21; EW VARIABLE 23; RP VARIABLE 18; LNEXT VARIABLE 22; XON VARIABLE 17; XOFF VARIABLE 19; FORW1 NOSUPPORT 255; FORW2 NOSUPPORT 255; SENT DO SUPPRESS GO AHEAD RCVD IAC SB LINEMODE MODE EDIT|TRAPSIG SENT IAC SB LINEMODE MODE EDIT|TRAPSIG|ACK RCVD DO NEW-ENVIRON RCVD WILL STATUS RCVD DO XDISPLOC RCVD DO OLD-ENVIRON SENT WONT OLD-ENVIRON RCVD IAC SB TERMINAL-SPEED SEND SENT IAC SB TERMINAL-SPEED IS 9600,9600 RCVD IAC SB X-DISPLAY-LOCATION SEND SENT IAC SB X-DISPLAY-LOCATION IS "fenestro.parc.xerox.com:0.0" RCVD IAC SB NEW-ENVIRON SEND SENT IAC SB NEW-ENVIRON IS VAR "DISPLAY" VALUE "fenestro.parc.xerox.com:0.0" RCVD IAC SB TERMINAL-TYPE SEND SENT IAC SB TERMINAL-TYPE IS "XTERM" RCVD DO ECHO SENT WONT ECHO RCVD WILL ECHO SENT DO ECHO RCVD IAC SB TOGGLE-FLOW-CONTROL RESTART-ANY RCVD DO BINARY SENT WILL BINARY RCVD WONT ECHO SENT DONT ECHO RCVD IAC SB LINEMODE SLC SYNCH NOSUPPORT 0; EC VARIABLE|ACK 8; SENT IAC SB LINEMODE SLC SYNCH NOSUPPORT|ACK 0; FreeBSD (fenestro.parc.xerox.com) (ttyp6) login: fenner RCVD IAC SB ENCRYPT REQUEST-START RCVD WILL ECHO SENT DO ECHO Password: RCVD IAC SB ENCRYPT REQUEST-END RCVD WONT ECHO SENT DONT ECHO Last login: Tue Oct 10 08:44:58 from fenestro Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 2.1-STABLE (FENESTRO) #3: Sun Oct 8 16:07:26 PDT 1995 You have mail. RCVD IAC SB LINEMODE SLC EC VARIABLE 127; SENT IAC SB LINEMODE SLC EC VARIABLE|ACK 127; Matter cannot be created or destroyed, nor can it be returned without a RCVD IAC SB LINEMODE SLC FORW1 VARIABLE 27; SENT IAC SB LINEMODE SLC FORW1 VARIABLE|ACK 27; receipt. % ls /bin/^D I hit ^D, it echoed and didn't try to do filename completion; it also nuked someone's idea of what was in the line buffer, since if I hit ^R a couple of times, I see: % ls /bin/^R ^R but if I hit enter, the "ls /bin/" works. If I hit ^D after the ^R's, it gets even more interesting: ls /bin/^R ^R SENT IAC EOF [* dd* hostname* pax* rmail* test* cat* df* kill* ps* rmdir* chmod* domainname* ln* pwd* sh* cp* echo* ls* rcp* sleep* csh* ed* mkdir* red* stty* date* expr* mv* rm* sync* % i.e. it actually does the filename expansion (but doesn't reprint the command). Neat. From owner-freebsd-bugs Tue Oct 10 09:50:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA25327 for bugs-outgoing; Tue, 10 Oct 1995 09:50:06 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA25319 ; Tue, 10 Oct 1995 09:50:03 -0700 Resent-Date: Tue, 10 Oct 1995 09:50:03 -0700 Resent-Message-Id: <199510101650.JAA25319@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, kargl@troutmask.apl.washington.edu Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA25268 for ; Tue, 10 Oct 1995 09:49:33 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.12/8.6.9) id JAA02940; Tue, 10 Oct 1995 09:47:46 -0700 Message-Id: <199510101647.JAA02940@troutmask.apl.washington.edu> Date: Tue, 10 Oct 1995 09:47:46 -0700 From: "Steven G. Kargl" Reply-To: kargl@troutmask.apl.washington.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/776: j0 man page fixes. Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 776 >Category: docs >Synopsis: j0 man page has formatting problem and errors >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 10 09:50:02 PDT 1995 >Last-Modified: >Originator: Steven G. Kargl >Organization: Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.x-STABLE | Seattle, WA 98105 |---------------------| >Release: FreeBSD 2.1-STABLE i386 >Environment: >Description: The command "man j0" gives a man page interspersed with `Bessel0' in several places. This is related the `.Em' formatting directive. Corrected two typos. >How-To-Repeat: %man j0 >Fix: *** j0.3.orig Tue Oct 10 09:24:28 1995 --- j0.3 Tue Oct 10 09:37:13 1995 *************** *** 82,101 **** .Fn j1 and .Fn j1f ! compute the ! .Em Bessel function of the first kind of the order ! 0 and the ! .Em order ! 1, respectively, ! for the ! real value .Fa x ; the functions .Fn jn and .Fn jnf ! compute the ! .Em Bessel function of the first kind of the integer order .Fa n for the real value .Fa x . --- 82,95 ---- .Fn j1 and .Fn j1f ! compute the Bessel function of the first kind of the order 0 and the ! order 1, respectively, for the real value .Fa x ; the functions .Fn jn and .Fn jnf ! compute the Bessel function of the first kind of the integer order .Fa n for the real value .Fa x . *************** *** 106,132 **** .Fn y1 , and .Fn y1f ! compute the linearly independent ! .Em Bessel function of the second kind of the order ! 0 and the ! .Em order ! 1, respectively, ! for the ! positive ! .Em integer ! value .Fa x (expressed as a double or float); the functions .Fn yn and .Fn ynf ! compute the ! .Em Bessel function of the second kind for the integer order .Fa n ! for the positive ! .Em integer ! value .Fa x (expressed as a double or float). .Sh RETURN VALUES --- 100,116 ---- .Fn y1 , and .Fn y1f ! compute the linearly independent Bessel function of the second kind of ! the order 0 and the order 1, respectively, for the positive real value .Fa x (expressed as a double or float); the functions .Fn yn and .Fn ynf ! compute the Bessel function of the second kind for the integer order .Fa n ! for the positive real value .Fa x (expressed as a double or float). .Sh RETURN VALUES >Audit-Trail: >Unformatted: From owner-freebsd-bugs Tue Oct 10 11:21:39 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA28726 for bugs-outgoing; Tue, 10 Oct 1995 11:21:39 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA28721 for ; Tue, 10 Oct 1995 11:21:36 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA10316; Tue, 10 Oct 1995 14:20:57 -0400 Date: Tue, 10 Oct 1995 14:20:57 -0400 From: "Garrett A. Wollman" Message-Id: <9510101820.AA10316@halloran-eldar.lcs.mit.edu> To: Bill Fenner Cc: uhclem%nemesis@fw.ast.com (Frank Durda IV), freebsd-bugs@freefall.freebsd.org Subject: Re: bin/771: telnet - FDIV035 In-Reply-To: <95Oct10.090037pdt.177475@crevenia.parc.xerox.com> References: <199510100130.SAA00868@freefall.freebsd.org> <95Oct10.090037pdt.177475@crevenia.parc.xerox.com> Sender: owner-bugs@FreeBSD.org Precedence: bulk < said: > Using a -stable sup'd on saturday, I can telnet to myself and duplicate > Frank's problem #2 (related to control-D). It doesn't happen when connecting > from -stable to a SunOS 4.1.3 box. I have now managed to reproduce this problem. It seems to be a fundamental incompatibility between the expectations of the shell and the way TELNET's LINEMODE option works. The problem is this: LINEMODE has to submodes in which it can operate. One of these is EDIT|TRAPSIG, and is equivalent to the tty driver's ICANON mode. The second is plain TRAPSIG, which works like ISIG mode in the tty driver. However, there is a subtle difference: the tty driver's ISIG mode only interprets the VINTR [IP], VQUIT [ABORT], and VSUSP [SUSPEND] characters. However, LINEMODE's TRAPSIG submode interprets all of the control characters, including (most significantly for our purposes) VEOF [EOF]. This causes the shell to get an end-of-file indication when you type ^D, rather than the ^D character that it was expecting. There are two possible fixes for this problem: 1) Only use LINEMODE to implement ICANON. 2) When switching between EDIT|TRAPSIG and plain TRAPSIG modes (or between ICANON and ISIG or ISIG|IEXTEN in the equivalent TTY driver terms), telnetd must negotiate to have those special characters disabled which would not have been implemented by the TTY driver in that mode. I prefer option (2). Unfortunately, I don't know Dave Borman's current address to ask his opinion... -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-bugs Tue Oct 10 15:50:22 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA08130 for bugs-outgoing; Tue, 10 Oct 1995 15:50:22 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA08125 for ; Tue, 10 Oct 1995 15:50:16 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA09077; Wed, 11 Oct 1995 08:49:42 +1000 Date: Wed, 11 Oct 1995 08:49:42 +1000 From: Bruce Evans Message-Id: <199510102249.IAA09077@godzilla.zeta.org.au> To: fenner@parc.xerox.com, uhclem%nemesis@fw.ast.com Subject: Re: bin/771: telnet - FDIV035 Cc: freebsd-bugs@freefall.freebsd.org Sender: owner-bugs@FreeBSD.org Precedence: bulk >% ls /bin/^D >I hit ^D, it echoed and didn't try to do filename completion; it also >nuked someone's idea of what was in the line buffer, since if I hit ^R a >couple of times, I see: >% ls /bin/^R >^R >but if I hit enter, the "ls /bin/" works. Perhaps a simpler example: under telnet to localhost in September2-current: $ cat 123^D [the ^D is echoed and no newline is printed] 123SENT IAC EOF [another ^D causes the message to overwrite the echo of the first ^D and a newline is printed] SENT IAC EOF 123 [results of a third ^D. No newline] 123SENT IAC EOF $ [results of a fourth ^D. The 123 is from the previous ^D]. Normal syscons tty: $ cat 123123 [^D after 123 causes `cat' to read "123" and echo it like it should] $ [second ^D causes `cat' to read EOF like it should]. The tty settings are the same except for the speed and `extproc'. Bruce From owner-freebsd-bugs Tue Oct 10 18:20:28 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA15791 for bugs-outgoing; Tue, 10 Oct 1995 18:20:28 -0700 Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA15779 for ; Tue, 10 Oct 1995 18:20:21 -0700 Received: (from winter@localhost) by sasami.jurai.net (8.6.11/8.6.9) id UAB03062; Tue, 10 Oct 1995 20:20:33 -0500 Date: Tue, 10 Oct 1995 20:20:29 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: freebsd-bugs@freefall.freebsd.org Subject: 2.1.0-951005-SNAP problems. In-Reply-To: <199510102249.IAA09077@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@FreeBSD.org Precedence: bulk I just installed 951005 and was very pleased with the changes in the install program and such. I like the "visual" configuration mode on the install floppy, but was puzzled that it wasn't on the generic kernel that was installed to the disk. Ok, a few problems I noticed. 1. uname -a gives the SNAP version of 2.1.0-950928-SNAP instead of 951005 (not significant) 2. telnet gives: ld.so failed: Undefined symbol "_enctype_names" in telnet:telnet (I installed the des and secure libs...) 3. telnets TO the machine give: ld.so failed: Undefined symbol "_encrypt_debug_mode" in telnetd:telnetd Connection closed by foreign host. (must be related to #2.) Anyhow slightly annoying. I guess I will install full sources and relink telnet etc... Good job otherwise. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-bugs Tue Oct 10 18:58:49 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA16664 for bugs-outgoing; Tue, 10 Oct 1995 18:58:49 -0700 Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA16658 for ; Tue, 10 Oct 1995 18:58:45 -0700 Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id DAA07277; Wed, 11 Oct 1995 03:58:27 +0200 From: Heikki Suonsivu Received: (hsu@localhost) by katiska.clinet.fi (8.6.12/8.6.4) id DAA03824; Wed, 11 Oct 1995 03:58:27 +0200 Date: Wed, 11 Oct 1995 03:58:27 +0200 Message-Id: <199510110158.DAA03824@katiska.clinet.fi> To: Gene Stark Cc: clinet.fi!hsu@sbstark.cs.sunysb.edu, bugs@freebsd.org Subject: kern/772: Stable panic In-Reply-To: <199510091348.JAA12076@starkhome.cs.sunysb.edu> References: <45a47j$9ln@starkhome.cs.sunysb.edu> <199510091348.JAA12076@starkhome.cs.sunysb.edu> Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@freebsd.org Precedence: bulk Gene Stark writes: > >panic: page fault > >syncing disks .... 3 3 3 giving up > >dumping to dev 20401 offset 278528 > >dump 64 > > > >And then it gets stuck there. It seems to be always getting stuck > >when it syncs the disks. I also saw another panic with slirp being > >the current process, but did not take the address up that time. > > > >f012db90 T _chflags > >f012dc8c T _fchflags > >f012dd60 T _chmod > >f012de60 T _fchmod > >f012df3c T _chown > >f012e03c T _fchown > >f012e118 T _utimes > > This appears to be the same crash as #744 (which didn't get mailed > to the list, for some reason). I had a crash dump for this, if > anyone is interested. I hope I still have the symbols for that kernel... We also got this exactly the same situation (page fault in kernel and then IO lockup when trying to dump) on a 486-40 with IDE disks, so it is very high probability of software problem, not a hardware one. This is very annoying as the systems get stuck, they don't reboot automatically. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi work +358-0-4375209 fax -4555276 home -8031121 From owner-freebsd-bugs Tue Oct 10 19:14:32 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA17063 for bugs-outgoing; Tue, 10 Oct 1995 19:14:32 -0700 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA17058 for ; Tue, 10 Oct 1995 19:14:27 -0700 Received: (from root@localhost) by sbstark.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id WAA08518; Tue, 10 Oct 1995 22:12:39 -0400 Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.6.11/8.6.9) id WAA04016; Tue, 10 Oct 1995 22:14:00 -0400 Date: Tue, 10 Oct 1995 22:14:00 -0400 From: Gene Stark Message-Id: <199510110214.WAA04016@starkhome.cs.sunysb.edu> To: clinet.fi!hsu@sbstark.cs.sunysb.edu CC: freebsd.org!bugs@sbstark.cs.sunysb.edu In-reply-to: <199510110158.DAA03824@katiska.clinet.fi> (message from Heikki Suonsivu on Wed, 11 Oct 1995 03:58:27 +0200) Subject: Re: kern/772: Stable panic Sender: owner-bugs@FreeBSD.org Precedence: bulk > > This appears to be the same crash as #744 (which didn't get mailed > > to the list, for some reason). I had a crash dump for this, if > > anyone is interested. I hope I still have the symbols for that kernel... > >We also got this exactly the same situation (page fault in kernel and then >IO lockup when trying to dump) on a 486-40 with IDE disks, so it is very >high probability of software problem, not a hardware one. This is very >annoying as the systems get stuck, they don't reboot automatically. The "crash in chflags" problem that I observed occurred with slirp as the current process. The system didn't get stuck, it just rebooted automatically. I did some tracing on the crash dump, reported what I found in bug report #744. I only had an hour or two to spend on it, and I concluded that the problem was caused by something in the vnode cache/pool code. Since I have not studied this code, I decided my likelihood of finding this bug quickly was small, and that David Greenman or John Dyson could make more efficient use of the dump information. I don't know if they actually ever saw bug report #744, as at least I didn't get it mailed back to me via the bugs list. - Gene Stark From owner-freebsd-bugs Wed Oct 11 00:42:47 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA26764 for bugs-outgoing; Wed, 11 Oct 1995 00:42:47 -0700 Received: from gildrum.ccon.com.au (gildrum.ccon.com.au [202.20.81.76]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA26759 for ; Wed, 11 Oct 1995 00:42:42 -0700 Received: (from mail@localhost) by gildrum.ccon.com.au (8.6.11/8.6.9) id RAA03715 for ; Wed, 11 Oct 1995 17:42:53 +1000 Received: from jeckyll.ccon.com.au(172.17.12.200) by gildrum.ccon.com.au via smap (V1.3) id sma003710; Wed Oct 11 17:42:30 1995 X-Sender: brett@mail Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 1 (Highest) Date: Wed, 11 Oct 1995 17:43:34 +1000 To: bugs@freebsd.org From: brett_robertson@ccon.com.au (Brett Robertson) Subject: Inability to use certain SCSI drives Sender: owner-bugs@freebsd.org Precedence: bulk Gentlemen, I am experiencing a problem with snapshot 950726. I am trying to install onto a 1G SCSI drive, an IBM DPES 31080. I get a message from the Installer saying that there is a problem with the drive geometry. The drive has 4903 cylinders, 4 heads and 108 sectors. I ignored the problem, created the partition and installed FreeBSD. I then tried to boot from the drive, only to get a message stating that there was no operating system on the drive. I have also tried a Quantum 1050S with a geometry of 2448/12/92, an IBM DSAS-3360 350M, a Fujitsu 1G, a Quantum 350 and a Quantum 540 all with cylinder counts of greater than 2400. The Installer reports that every one of them has a geometry problem. I am using a Compaq 486SX25 with 12M RAM and an Adaptec 1540 SCSI controller. Am I doing something wrong? Have I forgotten to do something? Is this a known problem? Is there a fix/patch available? Thanks in advance Brett R. P.S. I do have a 160M Quantum SCSI drive that is working on this system, but it is far to small to be usable. ---------------------------------------------------------------------------- In this world of NetSurfing, I'm the poor sod who has to wax the surfboards. ---------------------------------------------------------------------------- Brett Robertson | brett_robertson@ccon.com.au. Technical Support Consultant | Choice Connections | this space is intentionally left blank Melbourne, Australia | I couldn't think of anything to put here ---------------------------------------------------------------------------- From owner-freebsd-bugs Wed Oct 11 03:10:10 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA03304 for bugs-outgoing; Wed, 11 Oct 1995 03:10:10 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA03294 ; Wed, 11 Oct 1995 03:10:06 -0700 Resent-Date: Wed, 11 Oct 1995 03:10:06 -0700 Resent-Message-Id: <199510111010.DAA03294@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA02852 for" ; Wed, 11.Oct.1995.03:02:58.-0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id DAA20395; Wed, 11 Oct 1995 03:02:54 -0700 Message-Id: <199510111002.DAA20395@silvia.HIP.Berkeley.EDU> Date: Wed, 11 Oct 1995 03:02:54 -0700 From: asami@cs.berkeley.edu To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/777: patch doesn't realize stdin is closed Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 777 >Category: bin >Synopsis: patch doesn't realize stdin is closed and asks questions forever >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 11 03:10:03 PDT 1995 >Last-Modified: >Originator: Satoshi Asami >Organization: The Awesome FreeBSD Ports Team >Release: FreeBSD 2.2-CURRENT i386 >Environment: I saw this on a very recent stable (thud) as well. >Description: When you logout while a patch is running, and it has to ask questions, it will try to do that anyway -- and goes into an infinite loop. >How-To-Repeat: % rlogin localhost % cat t #!/bin/sh sleep 5 patch < /usr/ports/net/zircon/patches/patch-aa > log 2>&1 % sh ./t & logout % ls -s log % ls -s log % ls -s log % ls -s log and watch it grow forever as it fills up with these two lines: File to patch: No file found--skip this patch? [n] >Fix: No idea, I took a look at the source but patch does too many funny things with stdio. ;) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Wed Oct 11 03:13:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA03516 for bugs-outgoing; Wed, 11 Oct 1995 03:13:05 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA03510 for ; Wed, 11 Oct 1995 03:13:00 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id DAA23946; Wed, 11 Oct 1995 03:12:58 -0700 Date: Wed, 11 Oct 1995 03:12:58 -0700 Message-Id: <199510111012.DAA23946@silvia.HIP.Berkeley.EDU> To: freebsd-bugs@freefall.freebsd.org In-reply-to: <199510111010.DAA03288@freefall.freebsd.org> (FreeBSD-gnats@freefall.freebsd.org) Subject: Re: bin/777: patch doesn't realize stdin is closed From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-bugs@FreeBSD.org Precedence: bulk Not sure who this should go to, so it's to "bugs", who happened to be on the CC: list.... :) * From: FreeBSD-gnats@freefall.freebsd.org * * Thank you very much for your problem report. * It has the internal identification `bin/777'. * The individual assigned to look at your ^^^^^^^^^^ * bug is: freebsd-bugs. Since the reports all go to the "bugs" list, can we change this message to say something like "The group assigned..." or something? :) Satoshi From owner-freebsd-bugs Thu Oct 12 14:10:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA28913 for bugs-outgoing; Thu, 12 Oct 1995 14:10:05 -0700 Received: from escape.com (escape.com [198.6.71.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA28908 ; Thu, 12 Oct 1995 14:10:00 -0700 Received: (from dima@localhost) by escape.com (8.6.12/8.6.9) id QAA01195; Thu, 12 Oct 1995 16:54:46 -0400 Date: Thu, 12 Oct 1995 16:54:45 -0400 (EDT) From: "Dima (ELO)" To: hackers@freebsd.org cc: bugs@freebsd.org Subject: problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk Hello, I have a problem. When I start FreeBSD it says: mountmsdosfs(): root directory is not multiple of clustersize length I have 2 SCSI Hard Drives sd0 (which is not mounted) and sd1 (where Freebsd is located). It's 2 Gig , and partisioned as 500Mb for FreeBSD and 1500Mb for Dos From owner-freebsd-bugs Thu Oct 12 14:20:04 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29306 for bugs-outgoing; Thu, 12 Oct 1995 14:20:04 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29299 ; Thu, 12 Oct 1995 14:20:02 -0700 Resent-Date: Thu, 12 Oct 1995 14:20:02 -0700 Resent-Message-Id: <199510122120.OAA29299@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, "Received:from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29233 for" ; Thu, 12.Oct.1995.14:18:40.-0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id OAA01432; Thu, 12 Oct 1995 14:18:35 -0700 Message-Id: <199510122118.OAA01432@silvia.HIP.Berkeley.EDU> Date: Thu, 12 Oct 1995 14:18:35 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: FreeBSD-gnats-submit@freebsd.org Cc: mark@grondar.za X-Send-Pr-Version: 3.2 Subject: bin/778: tar complains "EOF not on block boundary" Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 778 >Category: bin >Synopsis: tar complains "EOF not on block boundary" on a good tarfile.gz >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 12 14:20:01 PDT 1995 >Last-Modified: >Originator: Satoshi Asami >Organization: The FreeBSD Ports Team >Release: FreeBSD 2.2-CURRENT i386 >Environment: This happens on a very recent -current only, not on -stable. >Description: tar says "EOF not on block boundary" when it is given a perfectly fine (I think) tarfile.gz. It happens on Mark Murray (mark@grondar.za)'s machine too. >How-To-Repeat: tar tvzf /usr/ports/distfiles/dvips558.tar.gz The funny thing is, it doesn't complain if you gunzip the file first and "tar tvf" it. It does print out the entire table of contents in either case. This is the only tarfile I found (so far) to have this problem. (I tried the whole /usr/ports/distfile directory on my machine... it has about 180MB worth of distfiles.) >Fix: No idea. MALLOC_OPTIONS=Z didn't help, by the way. :) >Audit-Trail: >Unformatted: From owner-freebsd-bugs Thu Oct 12 14:31:27 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29850 for bugs-outgoing; Thu, 12 Oct 1995 14:31:27 -0700 Received: from zed.ludd.luth.se (root@zed.ludd.luth.se [130.240.16.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29836 for ; Thu, 12 Oct 1995 14:31:22 -0700 Received: from adolf.ludd.luth.se (adolf.ludd.luth.se [130.240.16.9]) by zed.ludd.luth.se (8.6.12/8.6.11) with ESMTP id WAA25755 for ; Thu, 12 Oct 1995 22:31:17 +0100 Received: (smurfen@localhost) by adolf.ludd.luth.se (8.6.11/8.6.11) id WAA00709; Thu, 12 Oct 1995 22:29:47 +0100 Date: Thu, 12 Oct 1995 22:29:45 +0100 (MET) From: Ola Persson To: bugs@freebsd.org Subject: Disk partitioning in SNAP 95-10-05 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk Hello! When I partition my disks in freeBSD it selects wd1 even though I only mark wd0.. It doesn't matter what I do.. Regards, ------------------------------------------------------------------------- I You have been harassed by: I Ola Persson - smurfen@ludd.luth.se I I http://www.ludd.luth.se/~smurfen I Porsogarden 8:81 I I--------------------------------- I S-977 54 Lulea I I 'A black hole is where I SWEDEN I I God devided by zero.' I Tel. +46 (0)920-151 21 I ------------------------------------------------------------------------- From owner-freebsd-bugs Thu Oct 12 16:20:02 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA03992 for bugs-outgoing; Thu, 12 Oct 1995 16:20:02 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA03986 ; Thu, 12 Oct 1995 16:20:01 -0700 Resent-Date: Thu, 12 Oct 1995 16:20:01 -0700 Resent-Message-Id: <199510122320.QAA03986@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, scott@statsci.com Received: from block.statsci.com (block.statsci.com [198.145.127.26]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA03596 for ; Thu, 12 Oct 1995 16:09:58 -0700 Received: (from scott@localhost) by block.statsci.com (8.6.12/8.6.9) id QAA03608; Thu, 12 Oct 1995 16:09:52 -0700 Message-Id: <199510122309.QAA03608@block.statsci.com> Date: Thu, 12 Oct 1995 16:09:52 -0700 From: Scott Blachowicz Reply-To: scott@statsci.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/779: undefined rune_t Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 779 >Category: bin >Synopsis: #include gets undefined 'rune_t' type. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 12 16:20:00 PDT 1995 >Last-Modified: >Originator: Scott Blachowicz >Organization: StatSci division of Mathsoft, Inc >Release: FreeBSD 2.1-STABLE i386 >Environment: Actually, this is a 2.1.0-950928-SNAP OS on a 486/66 system. >Description: In building the GNU bc-1.03 package, I ran across this error (that I isolated down to a foo.c file included below): In file included from /usr/include/ctype.h:51, from foo.c:3: /usr/include/runetype.h:58: parse error before `rune_t' /usr/include/runetype.h:58: warning: no semicolon at end of struct or union /usr/include/runetype.h:59: warning: data definition has no type or storage class >How-To-Repeat: My foo.c contained the following 3 lines: #define _POSIX_SOURCE #include #include I compiled with 'cc -O -c foo.c'. >Fix: Don't define _POSIX_SOURCE or modify /usr/include/runetype.h to make sure rune_t is always defined (??). >Audit-Trail: >Unformatted: From owner-freebsd-bugs Fri Oct 13 12:21:47 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA09883 for bugs-outgoing; Fri, 13 Oct 1995 12:21:47 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA09878 for ; Fri, 13 Oct 1995 12:21:45 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14551(4)>; Fri, 13 Oct 1995 12:21:04 PDT Received: by crevenia.parc.xerox.com id <177475>; Fri, 13 Oct 1995 12:20:57 -0700 From: Bill Fenner To: bugs@freebsd.org Subject: sio does outb(4,0) while trying to disable interrupts Message-Id: <95Oct13.122057pdt.177475@crevenia.parc.xerox.com> Date: Fri, 13 Oct 1995 12:20:54 PDT Sender: owner-bugs@freebsd.org Precedence: bulk In sio's invasive attempt to disable interrupts on all potential serial ports (which is the cause of the recent Mach64 complaints), it also writes a 0 to port 4, which has nothing to do with any serial stuff as far as I can tell. likely_com_ports[] is 0 terminated, but the loop in sioprobe() uses sizeof() instead of looking for a terminator. Since the solution is really to make this sequence non-destructive, I won't supply a diff, but I thought that whoever is planning to fix the sio/mach64 problem should be aware of this detail. Bill From owner-freebsd-bugs Fri Oct 13 16:01:44 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA15979 for bugs-outgoing; Fri, 13 Oct 1995 16:01:44 -0700 Received: from mail.zrz.TU-Berlin.DE (mail.zrz.TU-Berlin.DE [130.149.4.15]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA15972 for ; Fri, 13 Oct 1995 16:01:37 -0700 Received: from marie.physik.tu-berlin.de by mail.zrz.TU-Berlin.DE with SMTP (PP); Fri, 13 Oct 1995 23:52:01 +0100 Received: (from jan@localhost) by marie.physik.tu-berlin.de (8.6.9/8.6.9) id XAA28973 for freebsd-bugs@freefall.freebsd.org; Fri, 13 Oct 1995 23:51:59 +0100 From: Jan Riedinger Message-Id: <199510132251.XAA28973@marie.physik.tu-berlin.de> Comments: MTA at marie.physik.TU-Berlin.DE is now sendmail v8. Subject: Problems with ftp install 951005-SNAP (fwd) To: freebsd-bugs@freefall.freebsd.org Date: Fri, 13 Oct 1995 23:51:58 +0100 (MET) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 3028 Sender: owner-bugs@FreeBSD.org Precedence: bulk Forwarded message: I had exactly the same problemes as discribed in the following news article with different hardware. At the end I used boot.flp from the SNAP before 951005. Jan > > From comp.unix.bsd.freebsd.misc Fri Oct 13 11:44:30 1995 > Newsgroups: comp.unix.bsd.freebsd.misc > Path: hal!fub!fu-berlin.de!news.belwue.de!scsing.switch.ch!swidir.switch.ch!in2p3.fr!univ-lyon1.fr!jussieu.fr!oleane!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!cs.utexas.edu!news.cs.utah.edu!dog.ee.lbl.gov!newsh> ub.nosc.mil!news!huck > From: huck@nosc.mil (Craig Huckabee) > Subject: Problems with ftp install 951005-SNAP > Message-ID: <1995Oct11.160110.20708@nosc.mil> > Followup-To: huck@nosc.mil, comp.unix.bsd.freebsd.misc > Summary: Problems with ftp install > Sender: huck@nosc.mil > Organization: NISE East > Date: Wed, 11 Oct 1995 16:01:10 GMT > Lines: 40 > > > Hi, > > I've just attempted to install the latest SNAP, and everything goes > fine until I get to the fetching of the distribution via FTP > - it doesn't work. > > ifconfig shows that my ethernet card is up and has the correct > ip address, netmask, and broadcast address. Pings from another > station back to this host work. Boot messages find all of my > hardware correctly. > > I've looked on the debug screen w/extra debugging turned on and it > doesn't even look like it's trying to connect. Previous installs would > show each attempt, the opening banner of each ftp site, and other > info that would let the user know that it was at least trying to > connect - even if the site was busy. > > Now, I get nothing on the debug screen and the first screen just tells > me the install failed and asks me to pick another site. Also, when I > try to out of the ftp site selection screen, it doesn't cancel > but instead tries to fetch the distribution again! I've been stuck in > this menu for a while (only a ^C sets me free). > > Is there anything else I can try? This was a working platform with > the last snap and the 2.0.5 release, both installed via ftp just fine. > > My hardware configuration (if it helps) is : > > ASUS PCI/E P54NP4 motherboard with 1 133Mhz pentium > Cogent PCI 960TP ethernet card > Adaptec 2940 PCI SCSI controller > ATI GUP Video card > > Any help is appreciated... > > Thanks, > Craig > huck@nosc.mil > > -- > e-mail: dirk@hal.in-berlin.de PGP-Public-Key available > > "Ueberfall, Waffen, Schutzgeld, Terror, Plutonium, Sprengstoff, > Bomben, Rauschgift, Drogen, Anschlag, Erpressung, Mord, Raub" > > Microsoft Network is prohibited from redistributing this work in > any form, in whole or in part. License to distribute this post is > available to Microsoft for $1000. Posting without permission > constitutes an agreement to these terms. > From owner-freebsd-bugs Fri Oct 13 16:39:09 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA16752 for bugs-outgoing; Fri, 13 Oct 1995 16:39:09 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id QAA16747 for ; Fri, 13 Oct 1995 16:39:07 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15683(5)>; Fri, 13 Oct 1995 16:38:14 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177475>; Fri, 13 Oct 1995 16:38:08 -0700 X-Mailer: exmh version 1.6.1 5/23/95 To: Bill Fenner cc: bugs@freebsd.org Subject: Re: sio does outb(4,0) while trying to disable interrupts In-reply-to: Your message of "Fri, 13 Oct 95 12:20:54 PDT." <95Oct13.122057pdt.177475@crevenia.parc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Oct 1995 16:38:00 PDT From: Bill Fenner Message-Id: <95Oct13.163808pdt.177475@crevenia.parc.xerox.com> Sender: owner-bugs@freebsd.org Precedence: bulk In message <95Oct13.122057pdt.177475@crevenia.parc.xerox.com> I write: >likely_com_ports[] is 0 terminated I am in space. Ignore me. Bill From owner-freebsd-bugs Fri Oct 13 17:10:04 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17533 for bugs-outgoing; Fri, 13 Oct 1995 17:10:04 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17526 ; Fri, 13 Oct 1995 17:10:02 -0700 Resent-Date: Fri, 13 Oct 1995 17:10:02 -0700 Resent-Message-Id: <199510140010.RAA17526@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, ache@ache.dialup.demos.ru Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA17295 for ; Fri, 13 Oct 1995 17:00:58 -0700 Received: by sequent.kiae.su id AA10392 (5.65.kiae-2 for FreeBSD-gnats-submit@freebsd.org); Sat, 14 Oct 1995 03:58:53 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 14 Oct 95 03:58:52 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id CAA01012; Sat, 14 Oct 1995 02:58:03 +0300 Message-Id: <199510132358.CAA01012@ache.dialup.demos.ru> Date: Sat, 14 Oct 1995 02:58:03 +0300 From: "Andrey A. Chernov" Reply-To: ache@ache.dialup.demos.ru To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/780: PROCFS lkm broken Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 780 >Category: kern >Synopsis: PROCFS tries to call unused function from libkern >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Oct 13 17:10:01 PDT 1995 >Last-Modified: >Originator: Andrey A. Chernov >Organization: Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: -current >Description: _divdi3 function missing: modload error on reboot with procfs lkm'ed. >How-To-Repeat: Remove all optional filesystems rebuild and rerun system. PROCFS want divdi3 from libkern and because it is only one who want, divdi3 not picked from libkern at kernel build time. >Fix: Workaround: add 'options PROCFS' to kernel config. Right: _divdi3 function should be picked to kernel in any case, f.e. called from dummy unused function. >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Oct 14 04:30:12 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA05328 for bugs-outgoing; Sat, 14 Oct 1995 04:30:12 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA05314 for freebsd-bugs; Sat, 14 Oct 1995 04:30:10 -0700 Date: Sat, 14 Oct 1995 04:30:10 -0700 From: GNU GNATS Message-Id: <199510141130.EAA05314@freefall.freebsd.org> To: freebsd-bugs Subject: List of open Problem Reports Sender: owner-bugs@FreeBSD.org Precedence: bulk This is the list of currently open problem reports [1994/10/07] kern/6 System hangs while using slip or ppp connection [1994/11/14] bin/17 "mount -t foo /dev/wd1h /mnt" gives incorrect error [1994/11/18] conf/22 Cannot use links to share kernel objects [1994/11/23] kern/27 Loopback mounts confuse unmount-on-reboot code [1994/11/30] kern/34 nullfs and union mounts can result in wild pointer r [1994/12/06] kern/42 PC-NFS on -current can't access disks [1994/12/07] docs/43 manpage for keysu is missing. reference from keyinit [1994/12/07] kern/44 ep driver won't work with anything but bnc [1994/12/08] kern/46 ed driver don't know the link0 flag (IFF_LINK0) [1994/12/13] misc/48 /etc/rc does not recover recovery files [1994/12/14] kern/51 Panic accessing NFS mounted file system [1994/12/18] misc/67 It took 20 tries to get free-bsd installed [1994/12/18] misc/68 bininst leaves system kinda hung [1994/12/21] misc/75 Netboot ignores gateway [1994/12/20] conf/76 fdisk can't be trusted. [1994/12/21] i386/79 Reboots sometimes don't complete. [1994/12/23] misc/83 System crash after abrupt end of slip session [1995/01/03] kern/95 Configuring a SLIP device with source = destination [1995/01/10] bin/104 pax -rwl may corrupt filesystem [1995/01/11] i386/105 Distributed libm (msun) has non-standard error handl [1995/01/13] gnu/107 kernel build produces internal compiler error [1995/01/14] bin/115 systat iostat display doesn't scale high enough [1995/01/14] bin/116 disk transfer rates reported by systat :iostat are t [1995/01/14] misc/118 use of 386bsd partition tag makes multi-os boot hard [1995/01/14] misc/120 first Initial security report is bogus becuase of ls [1995/01/14] bin/124 traceroute doesn't support -g flag. [1995/01/14] docs/127 locate man page does not have any clues to how the d [1995/01/14] bin/129 fsck cannot take a mount point as an argument [1995/01/14] docs/131 there is no man page for uucpd [1995/01/14] docs/132 gettytab documentation is split between /etc/gettyta [1995/01/14] bin/133 mail program doesn't have editheaders option [1995/01/14] bin/135 not enough ptys; virtual console names conflict with [1995/01/15] bin/146 version of compress is kinda old and slow [1995/01/19] bin/151 One of the pkg_add set /tmp mod to 755 [1995/01/20] bin/153 mount -u improvement for diskless systems [1995/01/21] kern/157 Quota system does not work [1995/01/21] bin/163 telneting sometimes doesn't yield a "login:" prompt [1995/01/21] docs/164 no ptrace(2) manual page. [1995/01/21] docs/165 No documentation on kernel boot flags. [1995/01/21] misc/166 /usr/include/machine/asmacros.h includes uninstalled [1995/01/21] kern/169 Errors from mkdir & mv when directories paths end wi [1995/01/21] bin/170 ar does not print an error message with readonly lib [1995/01/21] docs/171 No documentation on .forward files. [1995/01/21] bin/172 cp -f does not work [1995/01/21] bin/173 rc trys to mount modload fs before ld is available. [1995/01/21] bin/174 Poor error message from stty [1995/01/22] kern/175 Syscons does not recover X graphics mode [1995/01/22] kern/176 EIDRM not defined in errno.h [1995/01/24] gnu/183 can't resolve "operator <<" overload [1995/01/24] bin/184 send-pr says "Aborting ..." and happily removes the [1995/01/25] kern/185 kernel stability problems - can't sustain uptimes > [1995/01/25] bin/188 disklabel uses c partition by default, kernel says d [1995/01/30] gnu/196 size of bss in *.o's reported wrong by size [1995/01/30] bin/198 1.1.5.1 pine binary loops; top shows fancy values [1995/02/01] bin/199 quiz(6) reading database bug, pattern matching bug [1995/02/01] misc/202 System hang or reboot without clues, tcp ppp named r [1995/02/14] kern/214 Using wt driver crashes system [1995/02/14] kern/216 /kernel: panic: ffs_alloccg: map corrupted [1995/02/14] docs/218 dbm references from hash(3) [1995/02/16] kern/219 Performance on local net drops too much when SNDBUF [1995/02/16] misc/220 Cancel still doesn't work during install [1995/02/16] misc/221 lots of error messages during unpacking via ftp inst [1995/02/16] i386/222 boot prompt doesn't always work [1995/02/18] kern/224 ppp net serial [1995/03/02] misc/229 acos() core dump [1995/03/03] bin/230 C++ contructors not being called [1995/03/05] gnu/231 send-pr initializes Organization with ~/.signature [1995/03/05] docs/232 The mandoc .St macro doesn't work or misses IEEE754 [1995/03/11] kern/238 failed assertion in ncr.c --> no more scsi disk acce [1995/03/13] bin/241 strange behavior of /bin/sh [1995/03/17] kern/247 Berkeley Packet Filter fix [1995/03/17] kern/248 scbus attach/probe information is inconsistent [1995/03/19] gnu/256 nasty gdb bug back in 031595 system [1995/03/20] docs/263 There is absolutely no documentation for the dialog [1995/03/21] kern/266 ifconfig panics kernel built without option NFS [1995/03/28] kern/275 qic-02 streamer won't work [1995/03/28] kern/277 netstat -r reports entries with negative expire time [1995/03/28] kern/280 the new slice code is bitching about my old slices [1995/03/28] kern/281 Messages printed when checking CD ROM device too ver [1995/03/28] kern/282 buslogic adapter information WAY too verbose [1995/03/29] kern/284 Network gives permission denied [1995/03/30] kern/287 Several header files are not consistent [1995/03/31] kern/288 panic: free: multiple frees [1995/04/01] kern/291 PCI devices still probe/attach after being disabled [1995/04/01] kern/293 wd0: interrupt timeout [1995/04/04] kern/299 SCSI probes stop at ID 7 even for WIDE busses [1995/04/05] bin/300 __fdnlist fails on kernels created by cc -g and stri [1995/04/06] conf/301 Log rotation wastes _much_ to much space [1995/04/06] kern/302 Changing st tapes after extract crashes system [1995/04/09] bin/316 SNAP950322 less stable on IDE than earlier releases [1995/04/09] docs/317 Install README doesn't list matcd as install choice [1995/04/09] bin/323 Creating lost+found causes fsck to stop fsck -y FDIV [1995/04/09] bin/326 Weekly cron generates some usage and error messages [1995/04/09] bin/327 Clock management punishes you if CMOS != GMT FDIV020 [1995/04/09] bin/329 FTP transfers above 99K shown in scientific notation [1995/04/11] kern/336 make world fails on NCR-SCSI machine [1995/04/14] docs/341 vnconfig(8) disagrees with its man page [1995/04/14] kern/343 tcpdump with filter fails on tun and lo devices [1995/04/14] misc/344 Signal 11 when running a user program [1995/04/15] kern/345 panic "biodone: page busy < 0" [1995/04/17] kern/349 Panic with bad dir [1995/04/20] kern/353 xcdplayer crashes machine (with NCR810 SCSI) [1995/04/20] kern/354 Can't configure two IP aliases with the same network [1995/04/20] misc/355 policy on /usr/local permission in base release [1995/04/20] bin/357 pkg_delete aborts when subcommand fails [1995/04/24] bin/359 BS/DEL is still not quite right. [1995/04/26] kern/366 queue changes broke ISO tpip code [1995/04/26] kern/367 kernel hangs after ep0 attach message appears [1995/04/26] i386/369 AHA-154X-A problems [1995/05/01] gnu/373 In response to admittedly bogus code, gcc emits an o [1995/05/01] kern/374 panic: bad dir [1995/05/01] bin/375 NIS does not seem to work with Kerberos [1995/05/02] kern/376 tcpdump seems to cause spontaneous reboots [1995/05/03] kern/378 (apparently) bounce buffer code gets used on 32bit b [1995/05/05] kern/383 dd to from /dev/mem panics the machine. [1995/05/06] kern/384 ep0 conflicts with some other drivers [1995/05/06] kern/385 ep0 finds card on irq 10 when it's actually on 11 [1995/05/07] kern/387 scsistrategy doesn't use bounce buffers [1995/05/08] bin/389 Simultaneous creation/deletion of dirs corrupts file [1995/05/11] i386/394 IP multicast not supported by ep driver [1995/05/12] bin/398 VI doesnt do the correct thing [1995/05/13] bin/401 Add REMOTE_* variables [1995/05/13] bin/402 w -n shows non-numeric addresses [1995/05/13] misc/403 FreeBSD 1-compiled tcsh, bash and zsh binaries dump [1995/05/14] kern/405 The gpio driver does not work with the AT-GPIB, only [1995/05/14] bin/410 bad144(8) should probably scan the bad block remap s [1995/05/14] kern/411 bad144 allow you to add blocks in the remap area [1995/05/14] kern/416 page fault in syscons.c:scopen() [1995/05/14] bin/419 pkg_delete refuses to delete an incompletely added p [1995/05/15] misc/423 Sound devices are too insecure [1995/05/16] kern/425 arp entries not getting removed when interface chang [1995/05/16] kern/427 eg doesn't work with more than one card [1995/05/16] kern/428 configure is not foolproof [1995/05/19] kern/430 SCSI Tape dont work [1995/05/19] misc/431 Processes sometime's hang and wont die when they hav [1995/05/21] bin/432 mixer should print out the current mixer settings by [1995/05/22] kern/434 umapfs panics when mounting ufs over itself [1995/05/23] kern/435 mb_map full, network starts jumping off and on, fina [1995/05/23] misc/437 addition for /usr/src/usr.bin/file/Magdir/zyxel [1995/05/23] i386/440 want vidcontrol option to apply settings to all sysc [1995/05/24] gnu/442 when invoked from "make' cc not including name lists [1995/05/25] kern/443 65 sendmails crashes system [1995/05/26] i386/444 GUS sound driver does not seem to work. [1995/05/26] kern/446 unable to diskless-boot a PC when the server mounts [1995/05/26] kern/448 ktrace not enabled in default kernel [1995/05/27] gnu/450 tar --exclude -c doesn't work [1995/05/28] gnu/451 cvsinit/cvs doesn't work as expected with perl [1995/05/28] kern/452 vnode swapping panics [1995/05/28] misc/453 The release/Makefile does not make all des/eBones ta [1995/05/28] bin/454 compile ports/x11/iv and ld got sig11 [1995/05/28] misc/455 library wont compile [1995/05/29] bin/457 We may have an obscure csh bug [1995/05/30] docs/458 px doc does not find include figure [1995/05/30] kern/459 Systems freezes w/ 2842 [1995/05/31] bin/464 dialog_gauge goes one char too far for 100% value [1995/05/31] kern/466 Unexpected disk errors during installation/newfs [1995/06/01] misc/469 ctm leaves temp files after errors [1995/06/01] kern/471 System can not access SCSI DAT tape. [1995/06/02] bin/476 kvm_openfiles called w/ too small error buffer [1995/06/02] bin/477 telnet autologin ain't working [1995/06/03] docs/480 We don't have an rhosts.5 man page [1995/06/04] bin/486 ls includes utmp.h but doesn't use it [1995/06/05] kern/492 sysinstall shows "success" after "no space" failure. [1995/06/07] bin/499 pkg_manage percent done is broken/dependancies arent [1995/06/07] bin/500 pkg_manage fails to continue without return sometime [1995/06/12] bin/506 "Release" id generated by send-pr looks incorrect. [1995/06/14] bin/514 Crash recovery impossible without static mt/chflags. [1995/06/14] gnu/515 Info command has no tutorial [1995/06/15] kern/516 Crynwr compatibility mode for PLIP driver. [1995/06/15] bin/517 Bad group change with 'install' [1995/06/15] bin/519 execution of quotacheck from /etc/rc fails [1995/06/15] docs/520 instructions are not clear as to what the url should [1995/06/15] docs/521 catgets() man page error [1995/06/17] kern/527 dump causes assertion in ncr.c [1995/06/17] kern/528 slow 386 reports excessive interrupt-level buffer ov [1995/06/17] conf/529 Please put mountd's '-n' flag into /etc/sysconfig [1995/06/18] misc/530 Failed install from SCSI tape [1995/06/18] kern/532 buslogic bt 445S hangups wit FreeBSD 2.0.5 [1995/06/20] docs/536 No copyrights in usr/src/lib/libc/stdtime [1995/06/20] bin/537 FSCK Fails [1995/06/22] kern/540 ed0 is loosing packets on input [1995/06/22] i386/541 Alternate Reset method by unmapping ALSO broken [1995/06/23] docs/546 Shared memory manual pages [1995/06/23] misc/556 Bug in /etc/rc [1995/06/23] bin/557 ar utility exausts all available file descriptors [1995/06/26] kern/565 [1995/06/27] bin/569 Slattach behaviour inconsistant [1995/07/02] kern/579 sio: RS_IBUFSIZE at 256 bytes serial lines loose dat [1995/07/02] bin/580 xntpd doesn't work with Tobit DCF77 receiver. [1995/07/02] bin/581 iijppp may hang indefinitely [1995/07/02] misc/583 rlogin over PPP does not handle input [1995/07/03] kern/586 Timeouts on SCSI Adaptec 2940 [1995/07/04] kern/587 if_le hangs on OACTIVE with 2k buffer [1995/07/04] kern/588 Configuration of DEC ethernet cards not possible [1995/07/04] conf/589 /etc/rc should eval amd ${amdflags} [1995/07/05] kern/590 pager input errors on NCR SCSI 486 mainboard [1995/07/05] bin/591 SPAP request REJexted in stead of NAKed [1995/07/05] bin/594 "mkdir -p some/path/" fails to create last path comp [1995/07/06] i386/596 and conflict with _POSIX_SOURCE [1995/07/07] bin/599 pkg_add does not stop if dependencies are missing [1995/07/08] i386/602 disklabel : changes to cylinder details not saved [1995/07/09] misc/605 [1995/07/13] kern/611 WIDE-dhcp doesn't work with FreeBSD-2.0 bpf [1995/07/14] kern/614 SCSI tape timeout for forward space file is too shor [1995/07/19] bin/624 pkg_manage doesn't show directory symlinks [1995/07/19] kern/625 keyboard lockups during boot and forever after [1995/07/20] kern/627 vidcontrol causes crash when booted with sc0 disable [1995/07/20] kern/629 user mode ppp dies when sending [1995/07/21] i386/631 if_ix does not support bpf, nor does it appear to su [1995/07/24] docs/633 no manpage for ndbm [1995/07/26] bin/635 makefile for sbin/route doesn't make keywords.h when [1995/07/27] kern/637 If used heavily, ahc will crash, with disk timeouts [1995/07/29] kern/638 Transmitted packets not passed to bpf in if_le.c [1995/08/01] docs/646 vmstat man page out of date [1995/08/01] kern/647 Sound cards fail to work [1995/08/01] bin/648 Formatted output is not converted correctly [1995/08/02] gnu/650 Current flex is outdated [1995/08/03] kern/652 Multiple addresses on one interface interacts badly [1995/08/04] kern/653 ftp or kernel - multiple transfers when sendport dis [1995/08/05] gnu/655 ld -r of shared objects worked in 1.1.5, not in 2.0. [1995/08/07] bin/658 ifconfig alias has to be separately given [1995/08/07] bin/660 /bin/sh has problem with redirection. [1995/08/07] bin/661 Hercules is not capable of having a ISO-Latin1 Scree [1995/08/08] docs/663 newfs man page refers to format(8) [1995/08/08] pending/664 pkg_add(1) man page doesn't reference pkg_manage(1) [1995/08/08] ports/665 pkg_manage can't handle installing dvips [1995/08/08] gnu/666 The ldconfig program in SNAP wasn't good [1995/08/11] gnu/672 Nor all ph headers get created [1995/08/11] pending/673 /bin/sh + inn1.4 innwatch going belly up [1995/08/11] kern/674 quad speed cdrom not being found [1995/08/11] bin/675 make does unnecessary rebuilds [1995/08/12] bin/676 mv -i [1995/08/12] kern/677 X gets a bus error when calling mmap() [1995/08/13] kern/679 chown(2) ignores set-user-id and set-group-id bits f [1995/08/13] bin/680 2.0.5's tip using termios doesn't act the way it did [1995/08/13] docs/681 bad description of Adaptec 2842 in LINT [1995/08/14] bin/683 cron(8) [1995/08/14] docs/686 SIGSYS documented badly [1995/08/14] kern/688 Page fault: supervisor write, page not present [1995/08/15] ports/690 X11 install targets unfriendly [1995/08/15] pending/691 [1995/08/15] i386/692 My modem is not found if my external cache is disabl [1995/08/16] bin/693 `pkg_add' is umask-sensitive [1995/08/16] bin/694 No include file in rpcgen output [1995/08/16] kern/695 cat B > C ; cmp B C can fail! [1995/08/17] misc/697 "make -DCLOBBER" is broken [1995/08/18] kern/700 The comments in /sys/net/in.h are confusing [1995/08/21] pending/703 [1995/08/22] bin/706 increased root DNS traffic and long latencies for r- [1995/08/23] kern/707 Too few printf args [1995/08/27] pending/710 mpeg_play outdated [1995/08/29] pending/711 /etc/magic not installed [1995/08/29] pending/712 problem report [1995/08/29] bin/715 ls gives weird tabular form [1995/08/31] bin/716 W returns wrong results at login [1995/09/01] misc/717 ft.c attach fail on my Mountain tape drive [1995/09/02] bin/718 pkg_add incorrectly prints an error message [1995/09/15] bin/722 Off-by-one error in wbkgd() in ncurses [1995/09/16] pending/723 [1995/09/19] bin/728 /bin/sh messes up quoting when going through eval [1995/09/20] kern/729 unexpected signal 4/10/11 [1995/09/20] kern/730 3Com 3C5x9 probe problem [1995/09/21] docs/731 socketpair(2) and man page inconsistent about return [1995/09/22] bin/732 getpwent() dumps core if NIS password file is malfor [1995/09/23] docs/735 missing description for mount options in fstab(5) ma [1995/09/25] gnu/737 FreeBSD-current/src/gnu/usr.bin/gzip/Makefile [1995/09/26] kern/738 Using ktrace will cause a system reboot [1995/09/26] bin/739 Some problems when an output filter reads all input [1995/09/26] docs/740 man loadfont says /usr/share/misc/vgafonts instead o [1995/09/26] docs/741 netstat -rn not showing all routes in Kernel - not i [1995/09/26] kern/742 syslog errors accessing Mac hard disks [patch] [1995/09/27] bin/743 vi cannot edit a file where the name starts with + [1995/09/27] kern/744 Page fault in fchmod() with Sep 20 -stable kernel [1995/09/27] kern/745 occasional filesystem inconsistencies, and "panic: f [1995/09/27] bin/746 `talk' forbids talking from write-protected terminal [1995/09/27] bin/747 date(1) gives weird time zones and interprets GMT[+- [1995/09/27] docs/748 zic.8 man page refers to /usr/local/etc/zoneinfo [1995/09/27] pending/749 Re: vi cannot edit a file where the name starts with [1995/09/27] kern/750 cd9660 confused by not-ready or I/O errors FDIV030 [1995/09/28] bin/751 crontab(1): `crontab -e' exits on SIGINT [1995/09/28] kern/752 setting multiple addresses for a single interfaces l [1995/09/28] kern/753 my archive scsi tape drive does not work [1995/09/28] docs/754 there is no man page for the psm(4) mouse driver [1995/09/29] docs/755 man page joy(4) has incorrect ioctl() arguments [1995/09/30] kern/756 AHA-1542CF: adapter not taking commands [1995/10/01] kern/757 Removal of mounted CD-ROM causes reboot & single use [1995/10/01] bin/759 nfsd without arg's doesn't work [1995/10/02] kern/761 route add may cause panic when used incorrectly [1995/10/02] misc/762 g++ chokes on /usr/include/machine/spl.h [1995/10/03] kern/765 umount -f can`t umount a NFS filesystem in use [1995/10/04] bin/766 file doesn't grok HTML; /etc/magic in wrong place [1995/10/05] misc/767 Configure-time does time-warp on non-UTC CMOS - FDIV [1995/10/06] bin/769 xntpd does not detach from controlling terminal [1995/10/06] kern/770 Floppy kernel won't boot with T485 or IDT L2 cache F [1995/10/07] bin/771 telnet character mode not set and broken when set - [1995/10/08] kern/772 page fault while in kernel mode (two cases) [1995/10/09] ports/773 screen-3.6.2 from -current wont work... [1995/10/09] kern/774 dump fails with "slave couldn't reopen disk: Device [1995/10/10] pending/775 changing root device was wrong when exist IDE drive [1995/10/10] docs/776 j0 man page has formatting problem and errors [1995/10/11] bin/777 patch doesn't realize stdin is closed and asks quest [1995/10/12] bin/778 tar complains "EOF not on block boundary" on a good [1995/10/12] bin/779 #include gets undefined 'rune_t' type. [1995/10/13] kern/780 PROCFS tries to call unused function from libkern This is the list of problem reports already analyzed: [1994/12/01] kern/35 mount -t union -o -b : lower layer not seen by shell [1995/01/21] misc/162 routes seem to accumulate under 2.0-950112-SNAP [1995/01/22] docs/177 man pages missing for SYSV IPC funtions [1995/02/14] kern/215 SNAP-950112 crashed with "panic: page fault" [1995/03/20] kern/260 msync and munmap don't bother to update mod times [1995/03/20] docs/264 There are no manual pages for the forms library. [1995/03/22] kern/267 NFS code gives error messages, systems jams for a fe [1995/05/09] bin/392 Simultaneous cp and ls of files on dos f/s hangs pro [1995/06/01] ports/467 utils/kp wrong distfile place after make fetch [1995/06/21] docs/538 MAP_FILE not mentioned in mmap man page. [PDT/08/11] bin/671 No quot available. /* EOF -- this list has not been truncated */ From owner-freebsd-bugs Sat Oct 14 04:30:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA05337 for bugs-outgoing; Sat, 14 Oct 1995 04:30:13 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA05319 for freebsd-bugs; Sat, 14 Oct 1995 04:30:10 -0700 Date: Sat, 14 Oct 1995 04:30:10 -0700 From: GNU GNATS Message-Id: <199510141130.EAA05319@freefall.freebsd.org> To: freebsd-bugs Subject: Summary of Problem Reports Sender: owner-bugs@FreeBSD.org Precedence: bulk Number of currently open reports: 304 Number of curently analyzed reports: 11 From owner-freebsd-bugs Sat Oct 14 10:31:56 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA13656 for bugs-outgoing; Sat, 14 Oct 1995 10:31:56 -0700 Received: from xkis.nnov.su (root@gw04.kis.nnov.su [194.87.66.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA13650 for ; Sat, 14 Oct 1995 10:31:38 -0700 Received: by xkis.nnov.su id UAA20828; (8.6.8/D) Sat, 14 Oct 1995 20:19:34 +0300 From: dv@xkis.nnov.su (Dmitry Valdov) Message-Id: <199510141719.UAA20828@xkis.nnov.su> Subject: secure finger is not enought secure To: freebsd-bugs@freebsd.org Date: Sat, 14 Oct 1995 20:19:28 +0300 (MSK) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Content-Length: 728 Sender: owner-bugs@freebsd.org Precedence: bulk Hi! is this a bug or feature? ;-) if i trying to finger host without providing username: -- merahq: {1} finger @localhost [localhost] must provide username -- But i can finger this host anyway (without specifying username): -- merahq: {2} telnet localhost finger Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. -l Login: dv Name: Dmitry Valdov Directory: /usr/u/dv Shell: /bin/csh On since Sat Oct 14 20:09 (MSK) on ttyp0 (messages off) from gw09 No Mail. Mail forwarded to: dv@xkis.nnov.su No Plan. Connection closed by foreign host. -- Is this true? This works on all version from 2.0 to 2.2-current. Dmitry. PS. Sorry for my poor english.. From owner-freebsd-bugs Sat Oct 14 10:57:37 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA14058 for bugs-outgoing; Sat, 14 Oct 1995 10:57:37 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA14053 for ; Sat, 14 Oct 1995 10:57:33 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA02029; Sat, 14 Oct 1995 18:57:24 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id SAA00414; Sat, 14 Oct 1995 18:57:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id SAA11380; Sat, 14 Oct 1995 18:56:46 +0100 From: J Wunsch Message-Id: <199510141756.SAA11380@uriah.heep.sax.de> Subject: Re: secure finger is not enought secure To: dv@xkis.nnov.su (Dmitry Valdov) Date: Sat, 14 Oct 1995 18:56:45 +0100 (MET) Cc: freebsd-bugs@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199510141719.UAA20828@xkis.nnov.su> from "Dmitry Valdov" at Oct 14, 95 08:19:28 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 775 Sender: owner-bugs@freebsd.org Precedence: bulk As Dmitry Valdov wrote: > > is this a bug or feature? ;-) > if i trying to finger host without providing username: > > -- > > merahq: {1} finger @localhost > [localhost] > must provide username This is a feature. > But i can finger this host anyway (without specifying username): > > -- > > merahq: {2} telnet localhost finger > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. This is an entirely different matter. It's not the finger service as invoked via inetd(8). If you've already got access to the local machine, it doesn't make sense if you couldn't run finger locally. -- 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 Oct 14 11:21:04 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14528 for bugs-outgoing; Sat, 14 Oct 1995 11:21:04 -0700 Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14518 for ; Sat, 14 Oct 1995 11:20:37 -0700 Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id AAA28928 for bugs@freebsd.org; Sun, 15 Oct 1995 00:20:12 +0600 Received: by itfs.nsk.su; Sun, 15 Oct 95 00:10:15 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.6.8/8.6.6) id AAA17850; Sun, 15 Oct 1995 00:01:20 +0600 From: nnd@itfs.nsk.su (Nickolay N. Dudorov) To: bugs@freebsd.org Subject: SLIP problem(s) in STABLE Message-ID: Date: Sat, 14 Oct 1995 18:01:09 GMT Sender: owner-bugs@freebsd.org Precedence: bulk It was already discovered that SLIP have some problems in -current. I found some (same ?) problems in -stable. 1) After succesfully establishing a SLIP connection by 'slattach' on a line with modem and loosing/reestablishing carrier I can't use that 'slX' interface due to permanent 'No route to host' messages. Reading the sources of /sys/net/if_sl.c and /sys/kern/tty.c shows that this message must results from: /* /sys/net/if_sl.c - lines from 446 */ if ((sc->sc_ttyp->t_state & TS_CONNECTED) == 0) { m_freem(m); return (EHOSTUNREACH); } which in turn is a result of (!)-marked lines in /* /sys/kern/tty.c - function ttymodem, lines from 1319 */ } else if (flag == 0) { /* * Lost carrier. */ CLR(tp->t_state, TS_CARR_ON); if (ISSET(tp->t_state, TS_ISOPEN) && ! !ISSET(tp->t_cflag, CLOCAL)) { ! SET(tp->t_state, TS_ZOMBIE); ! CLR(tp->t_state, TS_CONNECTED); if (tp->t_session && tp->t_session->s_leader) psignal(tp->t_session->s_leader, SIGHUP); ttyflush(tp, FREAD | FWRITE); return (0); } } else { /* * Carrier now on. */ SET(tp->t_state, TS_CARR_ON); ! if (!ISSET(tp->t_state, TS_ZOMBIE)) ! SET(tp->t_state, TS_CONNECTED); wakeup(TSA_CARR_ON(tp)); ttwakeup(tp); ttwwakeup(tp); } As a temporary "solution" ;-( of this problem I make the next change to /usr/src/sbin/slattach: --- slattach.c.STABLE Sat Oct 14 22:16:12 1995 +++ slattach.c Sat Oct 14 22:55:55 1995 @@ -419,6 +419,18 @@ } syslog(LOG_NOTICE, "Carrier now present on %s (sl%d)", dev, unit); + /* This HACK clears TS_ZOMBIE flag and set */ + /* TS_CONNECTED, which otherwise remains unset. */ + tty.c_cflag |= CLOCAL; + if (tcsetattr(fd, TCSANOW, &tty) < 0) { + syslog(LOG_ERR, "tcsetattr(TCSAFLUSH): %m"); + exit_handler(1); + } + tty.c_cflag &= ~CLOCAL; + if (tcsetattr(fd, TCSANOW, &tty) < 0) { + syslog(LOG_ERR, "tcsetattr(TCSAFLUSH): %m"); + exit_handler(1); + } } } setup_line(0); After that I can use my SLIP connection (and this is a kind of "correctness proof" of my problem analysis :-) 2) There are some "strangenesses(?)" in slattach behaviour - 'slX' interface marked as 'UP' even before carrier is established on a line; - is it really necessary to 'fork' (in 'acquire_line()') every time to run 'redial_cmd' (if there is any) ? - it seens to me than "resetting to tty discipline" in this 'acquire_line' can't be done when redialing because there is no carrier and switching to CLOCAL is done after that ? Unfortunely I have not enough time (and/or knowledges) to find answers to this questions (even in form of a HACKs) :-( N.Dudorov From owner-freebsd-bugs Sat Oct 14 12:47:18 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16359 for bugs-outgoing; Sat, 14 Oct 1995 12:47:18 -0700 Received: from xkis.nnov.su (root@gw04.kis.nnov.su [194.87.66.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA16351 for ; Sat, 14 Oct 1995 12:47:02 -0700 Received: by xkis.nnov.su id WAA22224; (8.6.8/D) Sat, 14 Oct 1995 22:28:13 +0300 From: dv@xkis.nnov.su (Dmitry Valdov) Message-Id: <199510141928.WAA22224@xkis.nnov.su> Subject: secure finger is not enought secure To: freebsd-bugs@freebsd.org Date: Sat, 14 Oct 1995 22:28:12 +0300 (MSK) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Content-Length: 768 Sender: owner-bugs@freebsd.org Precedence: bulk > > > But i can finger this host anyway (without specifying username): > > > > -- > > > > merahq: {2} telnet localhost finger > > Trying 127.0.0.1... > > Connected to localhost. > > Escape character is '^]'. > > This is an entirely different matter. It's not the finger service as > invoked via inetd(8). No. It is finger service, invoked via inetd (because i'm TELNETTING to localhost). localhost is just for an example. > If you've already got access to the local > machine, it doesn't make sense if you couldn't run finger locally. > ok. Try to telnet finger_port_number after connect, type '-l' (without quotes). And u'll see finger information of all users currently logged in. Dmitry. PS. I think, it's a bug in FreeBSD's finger. From owner-freebsd-bugs Sat Oct 14 13:30:05 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA16919 for bugs-outgoing; Sat, 14 Oct 1995 13:30:05 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA16913 ; Sat, 14 Oct 1995 13:30:02 -0700 Resent-Date: Sat, 14 Oct 1995 13:30:02 -0700 Resent-Message-Id: <199510142030.NAA16913@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, volf@oasis.IAEhv.nl Received: from iaehv.IAEhv.nl (root@iaehv.IAEhv.nl [192.87.208.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA16876 for ; Sat, 14 Oct 1995 13:27:31 -0700 Received: from oasis.IAEhv.nl by iaehv.IAEhv.nl (8.6.12/1.63) id VAA16046; Sat, 14 Oct 1995 21:27:26 +0100 Received: by oasis (8.6.12/1.63) id VAA01503; Sat, 14 Oct 1995 21:26:16 +0100 Message-Id: <199510142026.VAA01503@oasis> Date: Sat, 14 Oct 1995 21:26:16 +0100 From: volf@oasis.IAEhv.nl (Frank Volf) Reply-To: volf@oasis.IAEhv.nl To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/781: MAX_OPEN and FD_SETSIZE Sender: owner-bugs@freebsd.org Precedence: bulk >Number: 781 >Category: kern >Synopsis: OPEN_MAX in kernel config and FD_SETSIZE in /usr/include/sys/types.h mismatch >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 14 13:30:01 PDT 1995 >Last-Modified: >Originator: Frank Volf >Organization: ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven - Digitale Stad Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || || volf@dse.dse.nl - use for Digital City of Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: FreeBSD 2.0.5 from CD, nothing fancy in the kernel config >Description: The OPEN_MAX define in the kernel configuration can be used to have a large number of open file descriptors (e.g. 512), getdtablesize returns the value set by OPEN_MAX (this is ok), FD_SETSIZE in /usr/include/sys/types.h is defined as 256. sys_generic.c (containing the code for select()) is compiled with this FD_SETSIZE set to 256. The select() fails at runtime if it is called with a nfds > FD_SETSIZE, because it is compiled with the FD_SETSIZE value, and does not know about OPEN_MAX > 256 >How-To-Repeat: See above. >Fix: Preferable automatic generation of the types.h file from kernel configuration by /usr/sbin/config. Please, let me know the status of this bug report (maybe I did something wrong). Frank >Audit-Trail: >Unformatted: From owner-freebsd-bugs Sat Oct 14 16:46:56 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA22932 for bugs-outgoing; Sat, 14 Oct 1995 16:46:56 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA22927 for ; Sat, 14 Oct 1995 16:46:51 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id JAA29837; Sun, 15 Oct 1995 09:42:25 +1000 Date: Sun, 15 Oct 1995 09:42:25 +1000 From: Bruce Evans Message-Id: <199510142342.JAA29837@godzilla.zeta.org.au> To: bugs@freebsd.org, nnd@itfs.nsk.su Subject: Re: SLIP problem(s) in STABLE Sender: owner-bugs@freebsd.org Precedence: bulk > It was already discovered that SLIP have some problems >in -current. I found some (same ?) problems in -stable. >1) After succesfully establishing a SLIP connection by >'slattach' on a line with modem and loosing/reestablishing carrier >I can't use that 'slX' interface due to permanent >'No route to host' messages. > Reading the sources of /sys/net/if_sl.c and /sys/kern/tty.c >shows that this message must results from: >/* /sys/net/if_sl.c - lines from 446 */ > if ((sc->sc_ttyp->t_state & TS_CONNECTED) == 0) { > m_freem(m); > return (EHOSTUNREACH); > } Urk. The !TS_CONNECTED state is now sticky, as is required by POSIX and for security (*). Once carrier drops, further carrier rises are ignored until after the line is completely (+) closed and then reopened. (*) the sticky state and security can be defeated using CLOCAL unless CLOCAL is locked off. (+) including the virtual open for controlling terminals. This wasn't supposed to affect slattach. slattach is supposed to receive a SIGHUP. After receiving a SIGHUP, it completely closes the line and then reopen it. Completely closing the line is quite complicated because of the requirement to get rid of the old controlling terminal. slattach attempts to do this by forking and exiting from the parent. This was necessary in 1.1.5. 2.0 allows getting changing the controlling terminal by just switching to a new one. I'm not sure if slattach tries this, or what happens for "switching" to the same controlling terminal. > As a temporary "solution" ;-( of this problem I make the >next change to /usr/src/sbin/slattach: >--- slattach.c.STABLE Sat Oct 14 22:16:12 1995 >+++ slattach.c Sat Oct 14 22:55:55 1995 >@@ -419,6 +419,18 @@ > } > syslog(LOG_NOTICE, "Carrier now present on %s (sl%d)", > dev, unit); >+ /* This HACK clears TS_ZOMBIE flag and set */ >+ /* TS_CONNECTED, which otherwise remains unset. */ >+ tty.c_cflag |= CLOCAL; >+ if (tcsetattr(fd, TCSANOW, &tty) < 0) { >+ syslog(LOG_ERR, "tcsetattr(TCSAFLUSH): %m"); >+ exit_handler(1); >+ } >+ tty.c_cflag &= ~CLOCAL; >+ if (tcsetattr(fd, TCSANOW, &tty) < 0) { >+ syslog(LOG_ERR, "tcsetattr(TCSAFLUSH): %m"); >+ exit_handler(1); >+ } > } > } > setup_line(0); Something like this was suggested before slattach did the fork to get rid of the controlling terminal, and the CLOCAL kludge was put in 1.1.5+ David's patch suite to make it work. But why doesn't forking and exiting work? Perhaps you started slattach from inside a terminal program and didn't exit from the terminal program. The terminal program then holds the line open so there is no way for slattach to close it. Terminal programs should be called from inside slattach, not the other way round. >2) There are some "strangenesses(?)" in slattach behaviour > - 'slX' interface marked as 'UP' even before carrier is > established on a line; I suppose slopen() could be cleverer about carrier. > - is it really necessary to 'fork' (in 'acquire_line()') every time > to run 'redial_cmd' (if there is any) ? See above. > - it seens to me than "resetting to tty discipline" in this > 'acquire_line' can't be done when redialing because there is > no carrier and switching to CLOCAL is done after that ? TIOCSETD only requires an open line. It's unnecessary to reset the discipline because reopening resets it. This code is probably leftover from simpler times before forking and and closing everything was necessary. Perhaps slattach should rely on the (unportable!) 2.0 semantics of TIOCSCTTY or the (unportable!) 1.1.5++ semantics of toggling CLOCAL and not do the fork/close. Bruce