Date: Wed, 15 Nov 2000 13:00:03 -0800 (PST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/22862: ncr driver problem with 4.2-BETA Message-ID: <200011152100.NAA78533@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/22862; it has been noted by GNATS. 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. On Wed, 15 Nov 2000 muir@idiom.com wrote: >=20 > >Number: 22862 > >Category: kern > >Synopsis: ncr probe fails with CACHE TEST FAILED: ? write ? read > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Quarter: =20 > >Keywords: =20 > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Nov 15 01:30:01 PST 2000 > >Closed-Date: > >Last-Modified: > >Originator: David Muir Sharnoff > >Release: FreeBSD 4.2-STABLE i386 > >Organization: > Idiom > >Environment: >=20 > =09FreeBSD 4.0-STABLE boot messages: >=20 > =09ncr0: <ncr 53c825 fast10 wide scsi> port 0x7400-0x74ff mem 0xe4102000-= 0xe41020ff irq 12 at device 10.0 on pci0 > =09ncr0: driver is using old-style compatability shims >=20 > =09I can't be sure that my hardware is completely function. I do > =09know that it's been working for a long time (>1yr) and my > =09system is generally very stable . >=20 > >Description: >=20 > =09I tried to upgrade to the latest -STABLE. That happens to > =09be 4.2-BETA. My scsi controller no longer probes. Big=20 > =09problem. >=20 > =09It fails with a message like: >=20 > =09=09ncr0: CACHE TEST FAILED: ? write 1 ? read 2=20 >=20 > =09=09or maybe write 2 read 1. >=20 > =09Sorry my notes aren't perfect. >=20 > >How-To-Repeat: >=20 > =09Try to boot 4.2-BETA on my home system. Sigh. >=20 > >Fix: >=20 > =09I'm compiling a kernel with the 4.0 version of ncr.c in=20 > =09the hopes that it will work. That's a short-term fix > =09though. >=20 >=20 > >Release-Note: > >Audit-Trail: > >Unformatted: >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011152100.NAA78533>