From owner-freebsd-current Fri Mar 31 10:39:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id 2214E37B897 for ; Fri, 31 Mar 2000 10:39:07 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 31362 invoked by uid 1000); 31 Mar 2000 18:39:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 18:39:06 -0000 Date: Fri, 31 Mar 2000 13:39:06 -0500 (EST) From: Systems Administrator To: Matthew Dillon Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems In-Reply-To: <200003311752.JAA29716@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One more thing, here's my kernel config file just in case you need it: machine i386 cpu I586_CPU ident RAID maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug options DDB_UNATTENDED options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep options NFS #Network Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options NMBCLUSTERS=10240 options VINUMDEBUG #enable Vinum debugging hooks device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # ISA Ethernet NICs. device ed0 at isa? port 0x240 irq 5 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device vinum #Vinum concat/mirror/raid driver pseudo-device snp # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter On Fri, 31 Mar 2000, Matthew Dillon wrote: > ::Jason DiCioccio > > Another possibility -- could you post your 'dmesg' output? One thing > that NFS does do is severely exercise both the network and the SCSI > device in a concurrent fashion. > > If you happen to be using an NCR SCSI chipset, that could be the cause > of the problem (though I have never in my life seen the panic message > you posted in relation to the NCR cards). > > If you can get the panic regularly then it may be worthwhile trying to > get some more information out of it. If you compile up a kernel with > the DDB option and your console is not running X, then the kernel will > drop into DDB on the console when it panics and allow you to do a > stack 'trace'. You may also be able to then dump the machine by typing > 'panic' manually at the ddb prompt after copying down the trace > information. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message