From owner-aic7xxx Tue Sep 22 00:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11178 for aic7xxx-outgoing; Tue, 22 Sep 1998 00:46:57 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from dledford.dialnet.net (dledford.dialnet.net [206.65.249.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11172 for ; Tue, 22 Sep 1998 00:46:54 -0700 (PDT) (envelope-from dledford@dialnet.net) Received: from dialnet.net (dledford@localhost [127.0.0.1]) by dledford.dialnet.net (8.8.7/8.8.7) with ESMTP id CAA12391; Tue, 22 Sep 1998 02:46:20 -0500 Message-ID: <360755CC.C967DECE@dialnet.net> Date: Tue, 22 Sep 1998 02:46:20 -0500 From: Doug Ledford X-Mailer: Mozilla 4.06 [en] (X11; I; Linux 2.0.35 i686) MIME-Version: 1.0 To: "Robert G. Brown" CC: aic7xxx Mailing List Subject: Re: One more 2300 healthy (rats?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert G. Brown wrote: > Anyway, the 9/19 cam boot.flp image booted my "sick" PowerEdge 2300, > found the 7890 device, and I could have proceeded to install freebsd if > I had any idea how to install freebsd from just one floppy. It also > rewrote whatever internal register was causing the trouble, as > 5.1.0pre10 booted flawlessly immediately thereafter. I have to confess > that I'm amazed that there is something that critical to function that > isn't cleared by a power cycle (including one where I jumpered NVRAM > clear and pulled the plug and punched the power button and...), but > there it is. Now, the next real question is, if you go ahead and power that system down, unplug the cord, discharge the capacitors in the power supply, clear the NVRAM, and do everything else you cna imagine to make that system go back to original, will the pre10 boot up without first booting the FreeBSD-CAM floppy? If so, then I'm stumped and amazed. To the best of my knowledge, everything the FreeBSD ahc cam driver sets and everything the linux aic7xxx driver set are *all* volatile registers and locations in the sense that they go away with a power down. So, if the machine is "fixed" so to speak now and no longer needs pre-booted after a power down to get pre10 to work, then something weird is going on. Any clues what it might be in that case Justin? > So, Doug, I think that you are probably correct about something not > getting written to, if only to clear it and get its parity right, during > the initialization phase. Unfortunately (;-) I'm now down to just ONE > system that is exhibiting the problem. Presumably I could fix it by > booting freebsd (well, not FIX it exactly as it has a hard memory error > showing up too, but clear whatever is ailing the SCSI controller). If > you like, I will try to hold onto this system for a few days without > doing so until you see if you can reproduce the error on something > there. If nothing else, I can be a final test site for whatever > solution you come up with in pre11. Yeah, don't "fix" that machine just yet :) If you can, run the test above first. -- Doug Ledford Opinions expressed are my own, but they should be everybody's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-aic7xxx" in the body of the message