Date: Mon, 5 Jun 1995 14:17:26 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: temp@temptation.interlog.com (Temptation) Cc: FreeBSD-hackers@FreeBSD.Org (FreeBSD hackers) Subject: Re: NCR810 problem? Message-ID: <199506052117.OAA24238@gndrsh.aac.dev.com> In-Reply-To: <Pine.3.89.9506051451.D21351-0100000@temptation.interlog.com> from "Temptation" at Jun 5, 95 02:41:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506052117.OAA24238>