From owner-freebsd-current Tue Mar 21 09:53:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA28551 for current-outgoing; Tue, 21 Mar 1995 09:53:14 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA28543 for ; Tue, 21 Mar 1995 09:53:13 -0800 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.11/8.6.5) with ESMTP id JAA18920 for ; Tue, 21 Mar 1995 09:52:49 -0801 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id JAA00306 for freebsd-current@freebsd.org; Tue, 21 Mar 1995 09:52:06 -0800 Date: Tue, 21 Mar 1995 09:52:06 -0800 From: "Russell L. Carter" Message-Id: <199503211752.JAA00306@geli.clusternet> To: freebsd-current@FreeBSD.org Subject: intel P590+ncr+de+current panics, P54SP4 fine. Sender: current-owner@FreeBSD.org Precedence: bulk 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. The hand copied down panic on the intel mb looks like this: [normal looking stuff deleted] Probing for devices on the pci0 bus: configuration mode 2 allows 16 devices. chip0 on pci0:0 chip1 on pci0:2 de0 int a irq 15 on pci0:6 reg20: virtual=0xf48d8000 physical=0xffbffc00 de0: can't read ENET ROM (why=-3) (ffffffffffffffffffff de0: DC21040 [10Mb/s] pass 2.3 ethernet address unknown ncr0 int a irq 11 on pci0:14 reg20: virtual=0xf48d9000 physical=0xffbff800 CACHE TEST FAILED: reg dstat-stat2 readback ffffffff CACHE INCORRECTLY CONFIGURED