From owner-freebsd-stable Fri Oct 16 08:29:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11136 for freebsd-stable-outgoing; Fri, 16 Oct 1998 08:29:17 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11121; Fri, 16 Oct 1998 08:29:11 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id IAA18910; Fri, 16 Oct 1998 08:27:08 -0700 (PDT) Date: Fri, 16 Oct 1998 08:27:08 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Annoying >2.2.5 oddity on reboot. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message