Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Aug 1996 03:31:05 -0400 (EDT)
From:      gpalmer@freebsd.org
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/1558: PCI probe seems to have lost a device in -current
Message-ID:  <199608310731.DAA09658@mutara.noc.webspan.net>
Resent-Message-ID: <199608310740.AAA27550@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>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 <generic PCI bridge (vendor=8086 device=1237 subclass=0)> rev 2 on pci0:0
Aug 20 22:00:25 news /kernel: chip1 <Intel 82371 PCI-ISA bridge> rev 1 on pci0:7:0
Aug 20 22:00:25 news /kernel: chip2 <Intel 82371 Bus-Master IDE controller> 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 <generic PCI bridge (vendor=8086 device=1237 subclass=0)> rev 2 on pci0:0
Aug 24 16:31:42 news2 /kernel: chip1 <generic PCI bridge (vendor=8086 device=7000 subclass=1)> 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:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608310731.DAA09658>