From owner-freebsd-smp Sat Oct 10 21:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13662 for freebsd-smp-outgoing; Sat, 10 Oct 1998 21:34:35 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13657 for ; Sat, 10 Oct 1998 21:34:34 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA11212; Sat, 10 Oct 1998 22:34:02 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810110434.WAA11212@panzer.plutotech.com> Subject: Re: reboot no work In-Reply-To: from Satya Devireddy at "Oct 10, 98 11:43:50 pm" To: satya@dspsoft.com (Satya Devireddy) Date: Sat, 10 Oct 1998 22:34:02 -0600 (MDT) Cc: freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satya Devireddy wrote... > > > Can you pop it into the debugger when it hangs? > > > > > > A stack trace might help diagnose the problem. > > > > > Sorry, no. THe keyboard is froze and only the reset button will bring > > me back. Have tried turning off all local script startups but still > > have problem. If I don't wait a respectable time after issuing the reboot > > I get a improper umount into fsck land. Have also noticed a somewhat long > > time delay after local startups when booting. This reboot problem has only > > been around since about the 10/8 or 10/9. > > I too am having a similar problem... > I cannot seem to build a working kernel for about a day. My previous > working kernel was about 9 days old. > > The new kernels seem to hang immeditely after the boot prompt after they > display that code addresses (i think) > > No output of the devices recognized show up on the screen. But I can > see my floppy drive, cd, hard disks light up. > If I reboot at this time and boot using the saved kernle (9 days old), > it fscks / and all as they are not properly dismounted. > > Somehow it seems to be doing all the device detection and probably > mounting the disks but the system does not respond. Although it sounds similar, this is a different problem. Tom's problem is that one of his disks doesn't like the cache sync command. The cache sync doesn't happen until you close the disk device, or until a reboot happens. Your problem happens on boot, so it must be something else. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message