From owner-freebsd-current Tue Mar 21 10:11:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA29176 for current-outgoing; Tue, 21 Mar 1995 10:11:19 -0800 Received: from FileServ2.MI.Uni-Koeln.DE (FileServ2.MI.Uni-Koeln.DE [134.95.212.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA29170 for ; Tue, 21 Mar 1995 10:11:12 -0800 Received: by FileServ2.MI.Uni-Koeln.DE id AA13218 (5.67b/IDA-1.5 for current@freebsd.org); Tue, 21 Mar 1995 19:09:13 +0100 Message-Id: <199503211809.AA13218@FileServ2.MI.Uni-Koeln.DE> From: se@MI.Uni-Koeln.DE (Stefan Esser) Date: Tue, 21 Mar 1995 19:09:12 +0100 In-Reply-To: "Russell L. Carter" "intel P590+ncr+de+current panics, P54SP4 fine." (Mar 21, 9:52) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Russell L. Carter" , current@FreeBSD.org Subject: Re: intel P590+ncr+de+current panics, P54SP4 fine. Sender: current-owner@FreeBSD.org Precedence: bulk On Mar 21, 9:52, "Russell L. Carter" wrote: } Subject: intel P590+ncr+de+current panics, P54SP4 fine. } Hello, } } My intel P590-de-ncr panics on boot with -current, but is fine with } kernels older than a couple of weeks. My ASUS P54SP4, identically } configured, boots -current fine. Hmm, please try to rebuild your kernel with: options PCI_REMAP and send boot message logs for both systems. } ncr0 int a irq 11 on pci0:14 } reg20: virtual=0xf48d9000 physical=0xffbff800 ^^^^^^^^^^ The NCR was mapped to that address by the BIOS, and the latest PCI code doesn't remap it by default anymore. } CACHE TEST FAILED: reg dstat-stat2 readback ffffffff } CACHE INCORRECTLY CONFIGURED Well, that's not necessarily a cache problem (so I'll change the message), but I guess the chip has not been fully enabled, or has been mapped to some bogus address by the BIOS ... Regards, STefan