From owner-freebsd-hackers Wed Sep 27 01:36:40 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA20508 for hackers-outgoing; Wed, 27 Sep 1995 01:36:40 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA20479 for ; Wed, 27 Sep 1995 01:36:21 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id KAA12060; Wed, 27 Sep 1995 10:36:09 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id KAA15591; Wed, 27 Sep 1995 10:36:08 +0200 Message-Id: <199509270836.KAA15591@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: hackers@freebsd.org Subject: Re: make world on FreeBSD-stable impossible. cc1: ... signal 11 Date: Wed, 27 Sep 1995 10:36:08 +0200 From: Mark Murray Sender: owner-hackers@freebsd.org Precedence: bulk > Please describe your machines in detail...output of dmesg would be a good > start. OK - dmesg: FreeBSD 2.1-STABLE #0: Sat Sep 23 12:11:24 1995 root@grudge.grondar.za:/a/src/sys/compile/IAFRICA CPU: i486DX (486-class CPU) real memory = 33554432 (32768K bytes) avail memory = 31465472 (30728K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:40:f6:20:72:6f, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: ahc0 rev 0 int a irq 11 on pci0:13 ahc0: 2940 Single Channel, SCSI Id=7, aic7870, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "HP C3724S 4349" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1149MB (2354660 512 byte sectors) pci0:16: UMC, device=0x8881, class=bridge (host) [no driver assigned] pci0:18: UMC, device=0x886a, class=bridge (isa) [no driver assigned] ...and mu config file: # # IAFRICA -- Internet Africa # machine "i386" cpu "I486_CPU" ident IAFRICA maxusers 16 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options PROCFS #Process filesystem options KERNFS #Process filesystem options KTRACE #kernel tracing options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=5" #Be pessimistic about Joe SCSI device #options BOUNCE_BUFFERS #options UCONSOLE config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log #pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 2 #Snoop device - to look at pty/vty/etc.. > >At the same spot for me. I was suspecting memory/cache problems, so far I > >have ruled out the cache. > > There was one other report about things dieing when one of the shared > libraries got out of sync, but after that was fixed the problems went away. > If you have the ability to try 2.1-stable on different hardware, but with > the same disk drive and binaries, this might help isolate the problem. I have tried a different SCSI controller - briefly. It seemed to work. > It might also help if you could install the new 0922 snapshot. Difficult. My connection is damn slow. This would take a few days :-( M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key