From owner-freebsd-stable Sat Oct 17 19:38:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23258 for freebsd-stable-outgoing; Sat, 17 Oct 1998 19:38:21 -0700 (PDT) (envelope-from owner-freebsd-stable@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 TAA23229; Sat, 17 Oct 1998 19:38:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id UAA12379; Sat, 17 Oct 1998 20:37:09 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810180237.UAA12379@panzer.plutotech.com> Subject: Re: Annoying >2.2.5 oddity on reboot. In-Reply-To: <199810180144.SAA08806@dingo.cdrom.com> from Mike Smith at "Oct 17, 98 06:44:53 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 17 Oct 1998 20:37:09 -0600 (MDT) Cc: mrcpu@internetcds.com, hackers@FreeBSD.ORG, stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote... > > > > > > I have a bunch of DEC ZX and HX 6000 P6 boxes. Have been running 2.2.5 > > for heap 'um big long time, zero troubles. > > > > So I upgraded 2 of them to -stable as of yesterday. ^^^^^^^^^^ > > Now neither of them will reboot properly. They shutdown, and get to the > > stage where they should start reloading, and they just hang. > > > > I've tried a couple different BIOS revs, and nothing seems to help. > > > > (These boxes have PCI and EISA slots). > > > > Drop back to 2.2.5 kernel, and they reboot just fine. > > > > Anybody have any idea what may be wrong? Driving down tot he office just > > to finish off a shutdown -r is a big unusability factor. > > > > The chipsets on the boxes are orion and neptune as I recall. > > > > A veeeeery old 3.0 (august of last year I think) runs fine in SMP and > > reboots properly. > > > > Thanks for any tips. > > If these are SCSI systems, and if the hang is about where the SCSI BIOS > should be loading from the disk, it may be that CAM is putting the SCSI ^^^ CAM is not in -stable. > controllers into a state the BIOS doesn't know how to get them out of. > > If so, have you tried updating the SCSI controller BIOSsen as well? > Have you tried a 2.2.7-CAM kernel? That's a good thing to try. There's a full release here: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/development/cam/... Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message