Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Dec 1999 22:17:16 +0100
From:      Andre Oppermann <oppermann@pipeline.ch>
To:        bjp aka rbw <rbw@nikita.rbwland.org>
Cc:        Mike Smith <msmith@FreeBSD.ORG>, freebsd-alpha@FreeBSD.ORG
Subject:   Re: 3.3-S crashing with "ncr0: queue empty." after ~2 weeks
Message-ID:  <384ECADC.D94CA286@pipeline.ch>
References:  <Pine.BSF.4.20.9912070135370.256-100000@nikita.rbwland.org>

next in thread | previous in thread | raw e-mail | index | archive | help
bjp aka rbw wrote:
> 
> On Mon, 6 Dec 1999, Mike Smith wrote:
> 
> > > the next time, i decided to run Crack v5.0 to see if i had any weak
> > > passwords on my system.  this seemed to be semi-disk I/O intensive.  it
> > > crashed with the repeating "ncr0: queue empty." error after about 6 days.
> >
> > I've only seen this error in conjunction with failing NCR controllers;
> > usually dying due to overheating in Multias.
> 
> the box doesn't seem to be running much higher than room temp, so i kind
> of doubt it's heat.  (it's nothing like the multias... that's for sure.)
> if it is heat, do you think that maybe the NCR controller is permanently
> damaged?  or do you think i should just look into cooling this thing?
> 
> also, do you think there is a chance that this is an odd problem in
> 3.3-STABLE?  (from what i can gather, most of the poeple on this list are
> running 4.0-CURRENT.)  i will try 4.0-CURRENT when i can find the time and
> see if that fixes it.
> 
> oh yeah... and anyone have some sort of test i can run that is highly disk
> intensive so i can try to force this problem to pop up?

I had the same problem some month ago for some time, but I'm running
-current on that box. At that time Stefan Esser did some modifications
to ncr.c, I checked out the version before these changes but it didn't
fix the problem. I suspect some other circumstances in the CAM stack
to be the cause for it. "queue empty" is the default in a case
statement.

If someone can/want to track this down I'll help where I can. For some
time now I havent got that error anymore, probably because I don't hit
the HDD that hard anymore.

-- 
Andre


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?384ECADC.D94CA286>