From owner-freebsd-hackers Mon May 29 00:47:13 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA19685 for hackers-outgoing; Mon, 29 May 1995 00:47:13 -0700 Received: from redline.ru (root@mail.redline.ru [194.87.69.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA19675 for ; Mon, 29 May 1995 00:46:25 -0700 Date: Mon, 29 May 1995 11:36:57 +0400 (GMT+0400) From: Anthony Graphics X-Sender: agl@mail.redline.ru To: "Rodney W. Grimes" cc: freebsd-hackers@FreeBSD.org Subject: Re: 950412 hangs on ncr0 probing: In-Reply-To: <199505280743.AAA05343@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Sun, 28 May 1995, Rodney W. Grimes wrote: > I think I matched your problem to another person. But do realize > scsi bus termination errors are the #1 cause for failure so I will > always remind people right from the start to check this. Even after > doing that I have found my self on site to repair a ``broken'' system, > only to find what I told them on the phone to check the did not and > infact had an incorrectly terminated bus. > > There are still 2 places for you to have an error in your scsi termination > even with this simple set up. Are the terminators enabled and powered up > on the NCR controller, and on the Quantum Lightning drive. > Ok, ASUS SP3G always comes with NCR termination enabled. As for Quantum lightning, there are two physical units representing terminators and they are in place. Anyway, kernel -c disable wt0 disable mcd0 disable mcd1 helped (well mcd0 and mcd1 was on irq 10 and 11 and these ones are configured for pci Slots 1 & 2 on asus, I have no idea how pci bus works, but when I was installing Mach32 into the slot 1 on the very same board in the machine running linux I had a conflict with AGUS which was using the very same irq. I wonder whether the problem was IRQ conflict or mcd autoprobing) > Just because a scsi bus works on one controller does not make it right, > the termination could have been enabled on the 1542 and disabeld on > the NCR for example. > Sure thing, but it's enabled in my case. > > I booted 2.0-RELEASE ok, but then I was unable to recompile 0412 > > under it (gcc-2.6.3 with -O0 was giving various signals trapped: > ^^^^^^^^^^^^^^^^^^ > > Please don't try to fuss with compiler options when building the kernel, > It can cause problems, we compile the way we set things up because that > is what we know to work. You put more variables into the equations when > you do this type of stuff!! > Ok, I run 'config MYSYSTEMNAME' again and tried to compile: cc1 still boiling out with error 'exited on signal 11(sometimes other random signal, often 10)) Well, somebody pointed out optimization code is broken in 2.6.3 so I tried to simplify freebsd-hacker's life (and can't compile 2.6.2 because I have only one FreeBSD box at the site :-( ) Anyway, 2.6.3 seemed to come with 940412 if my memory serves me and I don't keep 2.6.3 sources here, and 2.6.3 used to compile MYSYSTEMNAME before I switched to the machine with the ASUS SP3G board... One thing to mention: I have compiled and installed gnu make into /usr/local/bin/make and /usr/local/bin precedes /usr/bin in my path, so I cd /sys/compile/MYSYSTEMNAME and /usr/bin/make it have nothing to do with problems with unexpected signal trapped by cc1 I suppose? > > most often it was 11 sometimes 10 rarely 5) > > Well, rerunning /usr/bin/make was helpful with times but I've > > gotr stuck with vfs_func.c or something like that: no matter > > how much I've re running make: signal 11 trapped. > > Well I'm running the 0412-SNAP distribution, still under 0322 > > I have _the same problem_ as in the 0412 :-( > > And I can't roll back to 2.0-RELEASE because kvm_make or something like > > this coredumps (what is probably what should be expected but I was surprised > > ;-) > > So, the kernel hangs on the ncr detection :-( > Now after successfully booting 0412SNAP kvm_mkdb still causes this printing appearing on the console: May 29 11:24:11 relay /kernel: pid 209: kvm_mkdb: uid 0: exited on signal 10 Bus error (core dumped) > That was the exact sympton Boyd had, see my other email, on his system. > I wish you had said up front you where using the on board NCR 810 of > an ASUS PCI/I-486SP3G, it would have tripped my memory sooner that I > had been here before. > I'm sorry: never knew which part would be essential for the trouble report. Thanx! Partially succeeded: 0412 boots at least. Strange: the system I used before was some VLB of unknown origin with SIMMS of unknown origin and it worked, now when I assembled the machine from parts supplied by the well known producers it ain't working ;-) Ok here what it is: super tower case with 2 fans and 400 Watt PSU (nearly empty) ASUS SP3G with 256k cache (that came with the board) and Intel-100Mhz DX4 (to tell you truth we 've purchased Intel 100Mhz just to minimize dip switching on the ASUS ;-) two 16MB NEC SIMMS (with parity sure thing) Then came SMC Ultra 8013TPC and Cirrus Logic (some ISA model) SVGA board. AST4 board & Cronyx. Well all four ISA slots are occupied and no PCI slots are occupied AGL > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD >