From owner-freebsd-bugs Sat Aug 31 00:40:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA27557 for bugs-outgoing; Sat, 31 Aug 1996 00:40:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA27550; Sat, 31 Aug 1996 00:40:03 -0700 (PDT) Resent-Date: Sat, 31 Aug 1996 00:40:03 -0700 (PDT) Resent-Message-Id: <199608310740.AAA27550@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, gpalmer@freebsd.org Received: from mutara.noc.webspan.net (gpalmer@mutara.noc.webspan.net [206.154.70.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA27325 for ; Sat, 31 Aug 1996 00:31:14 -0700 (PDT) Received: (from gpalmer@localhost) by mutara.noc.webspan.net (8.7.5/8.6.12) id DAA09658; Sat, 31 Aug 1996 03:31:05 -0400 (EDT) Message-Id: <199608310731.DAA09658@mutara.noc.webspan.net> Date: Sat, 31 Aug 1996 03:31:05 -0400 (EDT) From: gpalmer@freebsd.org Reply-To: gpalmer@freebsd.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/1558: PCI probe seems to have lost a device in -current Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 1558 >Category: kern >Synopsis: PCI probe seems to have lost a device in -current >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Aug 31 00:40:02 PDT 1996 >Last-Modified: >Originator: Gary Palmer >Organization: None >Release: FreeBSD 2.2-CURRENT i386 >Environment: Tyan Titan Pro (?) natoma chipset P6 motherboard >Description: It seems that one of the chip ID's has been lost somewhere, so that a device has a description in -stable but not -current. >From a 2.1.5-RELEASE boot message on the machine: Aug 20 22:00:24 news /kernel: Probing for devices on PCI bus 0: Aug 20 22:00:25 news /kernel: chip0 rev 2 on pci0:0 Aug 20 22:00:25 news /kernel: chip1 rev 1 on pci0:7:0 Aug 20 22:00:25 news /kernel: chip2 rev 0 on pci0:7:1 Now running a -current from a week or so ago: Aug 24 16:31:42 news2 /kernel: Probing for devices on PCI bus 0: Aug 24 16:31:42 news2 /kernel: chip0 rev 2 on pci0:0 Aug 24 16:31:42 news2 /kernel: chip1 rev 1 on pci0:7:0 Aug 24 16:31:42 news2 /kernel: pci0:7:1: Intel Corporation, device=0x7010, class=storage (ide) [no driver assigned] Notice that chip1 (on the motherboard) is not being identified as a PCI-ISA bridge anymore. Either 2.1.5 is ID'ing it wrong, or -current doesn't have the chip id code for some reason. >How-To-Repeat: Play with a natoma based motherboard under both 2.1.5 and -current >Fix: Add the chip id to the table in -current, or fix the id code in -stable >Audit-Trail: >Unformatted: