Date: Sun, 28 May 1995 00:43:38 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: agl@mac.glas.apc.org (Anthony Graphics) Cc: freebsd-hackers@FreeBSD.org Subject: Re: 950412 hangs on ncr0 probing: Message-ID: <199505280743.AAA05343@gndrsh.aac.dev.com> In-Reply-To: <Pine.LNX.3.91.950527173916.18428B-100000@mail.redline.ru> from "Anthony Graphics" at May 27, 95 05:45:51 pm
next in thread | previous in thread | raw e-mail | index | archive | help
>
> On Fri, 26 May 1995, Rodney W. Grimes wrote:
>
> > Date: Fri, 26 May 1995 10:46:57 -0700 (PDT)
> > From: Rodney W. Grimes <rgrimes@gndrsh.aac.dev.com>
> > To: Anthony Graphics <agl@redline.ru>
> > Cc: freebsd-hackers@FreeBSD.org
> > Subject: Re: 950412 hangs on ncr0 probing:
> >
> > There have been no changes to the ncr.c driver since the 0412 SNAP
> > was made.
> >
> > >
> > > ncr0 <ncr 53c810 scsi> rev 2 int a irq 9 on pci0:1
> > > reg 20: virtual=0xf4786000 physical=0xfbfff000 size=0x100
> >
> > Can you provide information about what devices are on your
> > scsi bus?
> >
> > Have you tripple checked that you have only the two ends of the scsi
> > bus terminated and nothing in the middle?
> Look, what I have on the bus is just NCR itself and Quantum lightning
> that used to work with aha1542 under 0412 before, so there nothing
> like a terminated device in the middle.
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.
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.
> 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!!
> 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 :-(
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.
--
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?199505280743.AAA05343>