From owner-freebsd-hackers Sat Oct 17 18:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16225 for freebsd-hackers-outgoing; Sat, 17 Oct 1998 18:40:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16202; Sat, 17 Oct 1998 18:40:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA08806; Sat, 17 Oct 1998 18:44:53 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810180144.SAA08806@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jaye Mathisen cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Annoying >2.2.5 oddity on reboot. In-reply-to: Your message of "Fri, 16 Oct 1998 08:27:08 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Oct 1998 18:44:53 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 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 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? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message