From muir@charm.idiom.com  Wed Nov 15 01:27:21 2000
Return-Path: <muir@charm.idiom.com>
Received: from charm.idiom.com (charm-gif1.idiom.com [216.240.32.237])
	by hub.freebsd.org (Postfix) with ESMTP id 6B5DD37B4CF
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 15 Nov 2000 01:27:20 -0800 (PST)
Received: (from muir@localhost)
	by charm.idiom.com (8.9.3/8.9.3) id BAA06444;
	Wed, 15 Nov 2000 01:27:16 -0800 (PST)
	(envelope-from muir)
Message-Id: <200011150927.BAA06444@charm.idiom.com>
Date: Wed, 15 Nov 2000 01:27:16 -0800 (PST)
From: muir@idiom.com
Sender: muir@charm.idiom.com
Reply-To: muir@idiom.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: ncr driver problem with 4.2-BETA
X-Send-Pr-Version: 3.2

>Number:         22862
>Category:       kern
>Synopsis:       ncr probe fails with CACHE TEST FAILED: ? write ? read
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-scsi
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 15 01:30:01 PST 2000
>Closed-Date:    Thu Aug 26 21:59:14 GMT 2004
>Last-Modified:  Sat Jun 07 06:09:21 UTC 2008
>Originator:     David Muir Sharnoff
>Release:        FreeBSD 4.2-STABLE i386
>Organization:
Idiom
>Environment:

	FreeBSD 4.0-STABLE boot messages:

	ncr0: <ncr 53c825 fast10 wide scsi> port 0x7400-0x74ff mem 0xe4102000-0xe41020ff irq 12 at device 10.0 on pci0
	ncr0: driver is using old-style compatability shims

	I can't be sure that my hardware is completely function.  I do
	know that it's been working for a long time (>1yr) and my
	system is generally very stable .

>Description:

	I tried to upgrade to the latest -STABLE.  That happens to
	be 4.2-BETA.  My scsi controller no longer probes.  Big 
	problem.

	It fails with a message like:

		ncr0: CACHE TEST FAILED: ? write 1 ? read 2 

		or maybe write 2 read 1.

	Sorry my notes aren't perfect.

>How-To-Repeat:

	Try to boot 4.2-BETA on my home system.  Sigh.

>Fix:

	I'm compiling a kernel with the 4.0 version of ncr.c in 
	the hopes that it will work.   That's a short-term fix
	though.


>Release-Note:
>Audit-Trail:

From: David Muir Sharnoff <muir@idiom.com>
To: freebsd-gnats-submit@FreeBSD.org, muir@idiom.com
Cc:  
Subject: Re: kern/22862: ncr probe fails with CACHE TEST FAILED: ? write ? read
Date: Wed, 15 Nov 2000 01:35:47 -0800

 The 4.0 version of ncr.c worked.  I'm very glad my setup allowed
 me to fix the problem rather than reinstalling!
 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: muir@idiom.com
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/22862: ncr driver problem with 4.2-BETA 
Date: Wed, 15 Nov 2000 14:41:04 +0200

 On Wed, 15 Nov 2000 01:27:16 PST, muir@idiom.com wrote:
 
 > 	I tried to upgrade to the latest -STABLE.  That happens to
 > 	be 4.2-BETA.  My scsi controller no longer probes.  Big 
 > 	problem.
 
 If this isn't a hardware problem, I'd recommend switching to the sym(4)
 driver, which recently grew support for almost all the hardware
 previously supported by the ncr(4) driver.
 
 Ciao,
 Sheldon.
 

From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
To: muir@idiom.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/22862: ncr driver problem with 4.2-BETA
Date: Wed, 15 Nov 2000 20:50:49 +0100 (CET)

 The CACHE TEST in `ncr' tries to detect a possible misconfiguration as
 cacheable of the chip's MMIO window. It may also display a failure
 message, if the MMIO address is just wrong, for example. When it fails
 (that is, when it succeeds detecting a problem :-) ), then MMIO does not
 work at all for the chip, and not attaching the device is the only
 reasonnable behaviour. The `sym' driver uses the exact same test,
 inherited from `ncr', and in my opinion, will likely succeeds such a
 failure detection :) in the same situation with exactly the same message.
 
 My first idea is that, either the driver is hitting a wrong MMIO window
 for some reason, or the MMIO window has been set cacheable for some other
 reason :). In the latter case, it could be some driver or some other part
 that changed a MTRR, for example, or that made cacheable the page entry
 that maps the chip's MMIO window.
 
   G=E9rard.
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: mjacob 
State-Changed-When: Mon Oct 1 21:55:32 PDT 2001 
State-Changed-Why:  
Is this still broken for you? Is it broken with the sym driver? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22862 

From: David Muir Sharnoff <muir@idiom.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/22862: ncr probe fails with CACHE TEST FAILED: ? write ? read
Date: Fri, 26 Oct 2001 02:07:32 -0700

 This problem is not fixed as of 4.4-STABLE Oct 25, 2001.
 It is not fixed even when using the build option
 
 options         SYM_SETUP_LP_PROBE_MAP=0x40
State-Changed-From-To: feedback->open 
State-Changed-By: keramida 
State-Changed-When: Tue Dec 17 06:27:18 PST 2002 
State-Changed-Why:  
Followup from indicates this is still a problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22862 
Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Aug 26 20:05:34 GMT 2004 
Responsible-Changed-Why:  
Is this still a problem with modern versions of FreeBSD? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22862 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Thu Aug 26 20:06:08 GMT 2004 
State-Changed-Why:  
Is this still a problem with modern versions of FreeBSD? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22862 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Thu Aug 26 21:58:59 GMT 2004 
State-Changed-Why:  
Submitter no longer can duplicate the problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22862 
>Unformatted:
