From owner-freebsd-hackers Mon Jun 5 15:12:05 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA13414 for hackers-outgoing; Mon, 5 Jun 1995 15:12:05 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA13408 for ; Mon, 5 Jun 1995 15:12:03 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id RAA21261; Mon, 5 Jun 1995 17:11:48 -0500 Received: by olympus (4.1/TSS2.1) id AA07100; Mon, 5 Jun 95 17:11:58 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9506052211.AA07100@olympus> Subject: Re: NCR810 problem? To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 5 Jun 1995 17:11:58 -0500 (CDT) Cc: temp@temptation.interlog.com, FreeBSD-hackers@FreeBSD.Org In-Reply-To: <199506052117.OAA24238@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 5, 95 02:17:26 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 2441 Sender: hackers-owner@FreeBSD.Org Precedence: bulk > > > > I too, am seeing the 1 boot out of 3 freaks out problem with the exact > > > same symptoms as the above couple of messages. This box (Asus SP3G, > > > 486dx2/66, onboard NCR SCSI driving Quantum Empire 2100S and a HP 35480 > > > DAT drive) used to run 1.1.5.1 perfectly - never a problem on reboot. > > > Now (2.0.5ish) freaks one out of three times with the NCR probing errors > > > and then the river of errors. Can fix it by hitting reset 9 times out of 10. > > > > > Same motherboard, Asus (whatever) 486-66, NCR PCI, 2940, smc pci, > > Seagate, Dat (on or off doesn't matter) > > > > reboots sometimes, Most of the not. Unmount correctly, but the > > screen goes black, and sits there, Install program, Umounts, > > but sits there. > > but then out of the blue it'll reboot correctly. > > Also *NO* disk problems. Nor any problems with anything else, > > NT/WIN95/WARP/LINUX/SCO/UNIXWARE/DOS. > > For those of you with ASUS PCI/I-486SP3G boards I have kinda good news, > I will be getting in my backordered supply of them this week and once > I get done moving will be running at least 2 of them through the tests > right of the bat (due for customer shipment) and have a 3rd for me to > keep as a test board (sold too many of these now not to have one in > the test bench.) The others go to stock and won't last a week :-) > > I have seen this shutdown problem now, but only when using the 2.0.5A > install floppy, and that was on my known good test system. Every kernel > I build here has worked just fine in this respect (and I do run GENERIC > on must of the test bench systems since hardware changes in there like > there is no tomarrow!!). > > Have you folks supped the -current kernel sources and tried with it? > I am wondering if there is something funny going on with the build > environment Jordan is using on these kernels, as it seems to me the > folks installing the 2.0.5A are having problems, but those supping > -current (should be *IDENTICAL*) bits are not seeing many of the > strange problems reported :-(. > > Different kernel configs? I am not seeing this but I have the IDE tape and cdrom stuff commented out. If I didn't, I could not boot at all. Boyd -- _______________________________________________________________________ Boyd Faulkner faulkner@isd.tandem.com _______________________________________________________________________