From owner-freebsd-current Wed Jul 24 11:57:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06590 for current-outgoing; Wed, 24 Jul 1996 11:57:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA06584 for ; Wed, 24 Jul 1996 11:57:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id MAA19986 for ; Wed, 24 Jul 1996 12:57:47 -0600 (MDT) Message-Id: <199607241857.MAA19986@rover.village.org> To: current@freebsd.org Subject: Kernel hang Date: Wed, 24 Jul 1996 12:57:46 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just tried to boot my machine with a Jul 18th -current kernel. I have two scsi disks (sd0 and sd1). It fscks sd0 fine, but fails to fsck sd1. It will set there for up to 30 minutes (I waited that long one, 5 minutes longer than normal the other times (total 10)). This is true over multiple attempts to boot the kerenl. A Jul 12 -current kernel doesn't exibit this behavior. The only delta between the two kernels (modulo source changes between those dates) is that I upped max users from 10 to 20 so that my X builds won't fail with can't for in imake. My system is a 486DX2-66 with 32M of memory, a VLB bus with an UltraStor 34F and a SMC8216C that has been running FreeBSD in this configuration since about FreeBSD 1.1R (and 1.0GAMMA w/o the SMC card or 16M of memory). I know this is scant information. How do I force FreeBSD to dump a core file that I can use gdb to send a reasonable traceback for further analysis. I'll be trying again in a day or three with the then current kernel. Thanks for your help Warner