From dap@damon.com  Tue Jun  4 07:53:37 2002
Return-Path: <dap@damon.com>
Received: from damon.com (damon.com [199.98.84.130])
	by hub.freebsd.org (Postfix) with ESMTP id F110D37B404
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  4 Jun 2002 07:53:36 -0700 (PDT)
Received: from damon.com (localhost [127.0.0.1])
	by damon.com (8.12.3/8.12.3) with ESMTP id g54EreGJ033213
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 4 Jun 2002 09:53:40 -0500 (CDT)
	(envelope-from dap@damon.com)
Received: (from dap@localhost)
	by damon.com (8.12.3/8.12.3/Submit) id g54EreSo033212;
	Tue, 4 Jun 2002 09:53:40 -0500 (CDT)
	(envelope-from dap)
Message-Id: <200206041453.g54EreSo033212@damon.com>
Date: Tue, 4 Jun 2002 09:53:40 -0500 (CDT)
From: Damon Anton Permezel <dap@damon.com>
Reply-To: Damon Anton Permezel <dap@damon.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Dell PowerEdge 4600 PCI Bus scan problems
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         38894
>Category:       i386
>Synopsis:       [patch] Dell PowerEdge 4600 PCI Bus scan problems
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 04 08:00:12 PDT 2002
>Closed-Date:    Tue Oct 25 03:31:12 GMT 2005
>Last-Modified:  Tue Oct 25 03:31:12 GMT 2005
>Originator:     Damon Anton Permezel
>Release:        FreeBSD 4.6-RC i386
>Organization:
>Environment:
System: FreeBSD damon.com 4.6-RC FreeBSD 4.6-RC #0: Sun Jun 2 13:52:20 CDT 2002 dap@damon.com:/usr/obj/usr/src/sys/GENERIC i386

	Dell PowerEdge 4600

	
>Description:
	Devices in the last two PCI slots (6 and 7) were not being
	configured at boot time.

>How-To-Repeat:
	Insert PCI device in slot 6 and/or 7.
	Reboot.

>Fix:

	Fixes courtesy of Mark Tinguely and Andrew Gallatin.

*** pcibus.c    Sun Apr  7 07:57:25 2002
--- /root/pcibus.c      Tue Jun  4 09:47:39 2002
***************
*** 191,196 ****
--- 191,198 ----
        case 0x00061166:
                /* FALLTHROUGH */
        case 0x00081166:
+       case 0x00101166:
+       case 0x02011166:
                s = "ServerWorks host to PCI bridge";
                *busnum = pci_cfgread(cfg, 0x44, 1);
                break;
***************
*** 199,204 ****
--- 201,211 ----
                s = "ServerWorks NB6635 3.0LE host to PCI bridge";
                *busnum = pci_cfgread(cfg, 0x44, 1);
                break;
+ 
+        case 0x00111166:
+                s = "ServerWorks CMIC-HE";
+                *busnum = pci_cfgread(cfg, 0x44, 1);
+                break;
  
                /* Integrated Micro Solutions -- vendor 0x10e0 */
        case 0x884910e0:

>Release-Note:
>Audit-Trail:

From: Jung-uk Kim <jkim@niksun.com>
To: freebsd-gnats-submit@FreeBSD.org, dap@damon.com,
	gallatin@FreeBSD.org
Cc:  
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 12:31:04 -0400

 Following patch says 0x02011166 is host to PCI bridge but it is not. It 
 is a southbridge.
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
 
 My SuperMicro P4DSE motherboard says:
 
 isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
 rev=0x93 hdr=0x00
 
 

From: Andrew Gallatin <gallatin@cs.duke.edu>
To: Jung-uk Kim <jkim@niksun.com>
Cc: freebsd-gnats-submit@FreeBSD.org, dap@damon.com
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 15:15:29 -0400 (EDT)

 Jung-uk Kim writes:
  > Following patch says 0x02011166 is host to PCI bridge but it is not. It 
  > is a southbridge.
  > 
  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
  > 
  > My SuperMicro P4DSE motherboard says:
  > 
  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
  > rev=0x93 hdr=0x00
  > 
 
 I was afraid of that..
 
 Damon,
 
 If you comment out 0x02011166 in pci_bus.c, does your system still
 work?
 
 Drew

From: Damon Anton Permezel <dap@damon.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Jung-uk Kim <jkim@niksun.com>, freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 15:49:06 -0500

 On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 > 
 > Jung-uk Kim writes:
 >  > Following patch says 0x02011166 is host to PCI bridge but it is not. It 
 >  > is a southbridge.
 >  > 
 >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
 >  > 
 >  > My SuperMicro P4DSE motherboard says:
 >  > 
 >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
 >  > rev=0x93 hdr=0x00
 >  > 
 > 
 > I was afraid of that..
 > 
 > Damon,
 > 
 > If you comment out 0x02011166 in pci_bus.c, does your system still
 > work?
 
 I was wondering why the loonix source kept appearing on my system...
 I keep downloading it so I can see what they do, and then forgetting,
 and deleting it...
 
 #define PCI_VENDOR_ID_SERVERWORKS	  0x1166
 #define PCI_DEVICE_ID_SERVERWORKS_HE	  0x0008
 #define PCI_DEVICE_ID_SERVERWORKS_LE	  0x0009
 #define PCI_DEVICE_ID_SERVERWORKS_CIOB30  0x0010
 #define PCI_DEVICE_ID_SERVERWORKS_CMIC_HE 0x0011
 #define PCI_DEVICE_ID_SERVERWORKS_OSB4	  0x0200
 #define PCI_DEVICE_ID_SERVERWORKS_CSB5	  0x0201
 #define PCI_DEVICE_ID_SERVERWORKS_OSB4IDE 0x0211
 #define PCI_DEVICE_ID_SERVERWORKS_CSB5IDE 0x0212
 #define PCI_DEVICE_ID_SERVERWORKS_OSB4USB 0x0220
 #define PCI_DEVICE_ID_SERVERWORKS_CSB5USB PCI_DEVICE_ID_SERVERWORKS_OSB4USB
 #define PCI_DEVICE_ID_SERVERWORKS_CSB5ISA 0x0230
 
 
 The CSB5 (according to http://www.serverworks.com/products/GCHE.html)
 is for legacy I/O, including 32-bit PCI.
 
 I think I'd like to keep it, no?
 
 

From: Andrew Gallatin <gallatin@cs.duke.edu>
To: Damon Anton Permezel <dap@damon.com>
Cc: Jung-uk Kim <jkim@niksun.com>, freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 17:15:52 -0400 (EDT)

 Damon Anton Permezel writes:
  > On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
  > > 
  > > Jung-uk Kim writes:
  > >  > Following patch says 0x02011166 is host to PCI bridge but it is not. It 
  > >  > is a southbridge.
  > >  > 
  > >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
  > >  > 
  > >  > My SuperMicro P4DSE motherboard says:
  > >  > 
  > >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
  > >  > rev=0x93 hdr=0x00
  > >  > 
  > > 
  > > I was afraid of that..
  > > 
  > > Damon,
 
 Well, class=0x060100 is definately an ISA bridge. So I think we're
 going to have to start looking at the class codes.  
 
 Perhaps the host bridge is at another function on the same device?
 Can you both me the output of 'pciconf -lv' on your systems, please?
 
 Are you both willing to test patches?
 
 Thanks,
 
 Drew

From: Jung-uk Kim <jkim@niksun.com>
To: Damon Anton Permezel <dap@damon.com>,
	Andrew Gallatin <gallatin@cs.duke.edu>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 17:25:26 -0400

 Damon Anton Permezel wrote:
 > On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 > > Jung-uk Kim writes:
 >
 > I was wondering why the loonix source kept appearing on my system...
 > I keep downloading it so I can see what they do, and then forgetting,
 > and deleting it...
 >
 > #define PCI_VENDOR_ID_SERVERWORKS	  0x1166
 > #define PCI_DEVICE_ID_SERVERWORKS_HE	  0x0008
 > #define PCI_DEVICE_ID_SERVERWORKS_LE	  0x0009
 > #define PCI_DEVICE_ID_SERVERWORKS_CIOB30  0x0010
 > #define PCI_DEVICE_ID_SERVERWORKS_CMIC_HE 0x0011
 > #define PCI_DEVICE_ID_SERVERWORKS_OSB4	  0x0200
 > #define PCI_DEVICE_ID_SERVERWORKS_CSB5	  0x0201
 > #define PCI_DEVICE_ID_SERVERWORKS_OSB4IDE 0x0211
 > #define PCI_DEVICE_ID_SERVERWORKS_CSB5IDE 0x0212
 > #define PCI_DEVICE_ID_SERVERWORKS_OSB4USB 0x0220
 > #define PCI_DEVICE_ID_SERVERWORKS_CSB5USB PCI_DEVICE_ID_SERVERWORKS_OSB4USB
 > #define PCI_DEVICE_ID_SERVERWORKS_CSB5ISA 0x0230
 >
 > The CSB5 (according to http://www.serverworks.com/products/GCHE.html)
 > is for legacy I/O, including 32-bit PCI.
 >
 > I think I'd like to keep it, no?
 
 Yes, but it is not the right place to keep. PCI-to-ISA bridge code is move to 
 dev/pci/isa_pci.c in -CURRENT. I believe you may have to patch dev/pci/pci.c 
 to add a quirk. You can put it in pci/pcisupport.c for -STABLE.
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pci/pci.c.diff?r1=1.175&r2=1.176&f=h
 
 AFAIK, the chip is very similar to 0x02001166 (OSB4?). So, you may want to 
 'grep -R 0x02001166 *' to make sure.
 
 Jung-uk Kim

From: Jung-uk Kim <jkim@niksun.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>,
	Damon Anton Permezel <dap@damon.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 17:28:01 -0400

 Andrew Gallatin wrote:
 > Damon Anton Permezel writes:
 >  > On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 >  > > Jung-uk Kim writes:
 >  > >  > Following patch says 0x02011166 is host to PCI bridge but it is
 >  > >  > not. It is a southbridge.
 >  > >  >
 >  > >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.di
 >  > >  >ff?r1=1.81&r2=1.82
 >  > >  >
 >  > >  > My SuperMicro P4DSE motherboard says:
 >  > >  >
 >  > >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9
 >  > >  > chip=0x02011166 rev=0x93 hdr=0x00
 >  > >
 >  > > I was afraid of that..
 >  > >
 >  > > Damon,
 >
 > Well, class=0x060100 is definately an ISA bridge. So I think we're
 > going to have to start looking at the class codes.
 
 It is already done in -CURRENT. I believe -STABLE does it, too.
 
 > Perhaps the host bridge is at another function on the same device?
 
 Yes, it works as power management controller.
 
 > Can you both me the output of 'pciconf -lv' on your systems, please?
 
 I will certainly do it when I have some time.
 
 > Are you both willing to test patches?
 
 Me? Sure.
 
 > Thanks,
 >
 > Drew
 
 Thanks,
 
 Jung-uk Kim

From: Damon Anton Permezel <dap@damon.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Jung-uk Kim <jkim@niksun.com>, freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 16:47:21 -0500

 On Tue, Jul 23, 2002 at 05:15:52PM -0400, Andrew Gallatin wrote:
 > 
 > Damon Anton Permezel writes:
 >  > On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 >  > > 
 >  > > Jung-uk Kim writes:
 >  > >  > Following patch says 0x02011166 is host to PCI bridge but it is not. It 
 >  > >  > is a southbridge.
 >  > >  > 
 >  > >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
 >  > >  > 
 >  > >  > My SuperMicro P4DSE motherboard says:
 >  > >  > 
 >  > >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
 >  > >  > rev=0x93 hdr=0x00
 >  > >  > 
 >  > > 
 >  > > I was afraid of that..
 >  > > 
 >  > > Damon,
 > 
 > Well, class=0x060100 is definately an ISA bridge. So I think we're
 > going to have to start looking at the class codes.  
 > 
 > Perhaps the host bridge is at another function on the same device?
 > Can you both me the output of 'pciconf -lv' on your systems, please?
 > 
 > Are you both willing to test patches?
 
 At least one of us is.
 
 
 chip0@pci0:0:0:	class=0x060000 card=0x00000000 chip=0x00111166 rev=0x22 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CMIC-HE'
     class    = bridge
     subclass = HOST-PCI
 chip1@pci0:0:1:	class=0x060000 card=0x00000000 chip=0x00111166 rev=0x00 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CMIC-HE'
     class    = bridge
     subclass = HOST-PCI
 chip2@pci0:0:2:	class=0x060000 card=0x00000000 chip=0x00111166 rev=0x00 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CMIC-HE'
     class    = bridge
     subclass = HOST-PCI
 chip3@pci0:0:3:	class=0x060000 card=0x00000000 chip=0x00111166 rev=0x00 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CMIC-HE'
     class    = bridge
     subclass = HOST-PCI
 fxp0@pci0:4:0:	class=0x020000 card=0x01061028 chip=0x12298086 rev=0x08 hdr=0x00
     vendor   = 'Intel Corporation'
     device   = '82557/8/9 EtherExpress PRO/100(B) Ethernet Adapter'
     class    = network
     subclass = ethernet
 ahc0@pci0:6:0:	class=0x010000 card=0x01061028 chip=0x001f9005 rev=0x01 hdr=0x00
     vendor   = 'Adaptec'
     device   = 'AHA-2940U2/AHA-2940U2W AIC-7890/1 Ultra2 SCSI Controller'
     class    = mass storage
     subclass = SCSI
 ahc1@pci0:8:0:	class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 hdr=0x00
     vendor   = 'Adaptec Inc'
     device   = 'AHA-2940U/UW/2940D Ultra/Ultra Wide/Dual SCSI Host Adapter'
     class    = mass storage
     subclass = SCSI
 none0@pci0:14:0:	class=0x030000 card=0x01061028 chip=0x47521002 rev=0x27 hdr=0x00
     vendor   = 'ATI Technologies'
     device   = 'Rage XL PCI'
     class    = display
     subclass = VGA
 chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CSB5 PCI to ISA Bridge'
     class    = bridge
     subclass = HOST-PCI
 atapci0@pci0:15:1:	class=0x010182 card=0x02121166 chip=0x02121166 rev=0x93 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CSB5 PCI EIDE Controller'
     class    = mass storage
     subclass = ATA
 ohci0@pci0:15:2:	class=0x0c0310 card=0x02201166 chip=0x02201166 rev=0x05 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'OSB4 OpenHCI Compliant USB Controller'
     class    = serial bus
     subclass = USB
 isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     class    = bridge
     subclass = PCI-ISA
 chip5@pci0:16:0:	class=0x060000 card=0x00000000 chip=0x00101166 rev=0x03 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CIOB30'
     class    = bridge
     subclass = HOST-PCI
 chip6@pci0:16:2:	class=0x060000 card=0x00000000 chip=0x00101166 rev=0x03 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CIOB30'
     class    = bridge
     subclass = HOST-PCI
 chip7@pci0:17:0:	class=0x060000 card=0x00000000 chip=0x00101166 rev=0x03 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CIOB30'
     class    = bridge
     subclass = HOST-PCI
 chip8@pci0:17:2:	class=0x060000 card=0x00000000 chip=0x00101166 rev=0x03 hdr=0x00
     vendor   = 'Reliance Computer Corp./ServerWorks'
     device   = 'CIOB30'
     class    = bridge
     subclass = HOST-PCI
 bge0@pci1:6:0:	class=0x020000 card=0x01061028 chip=0x164414e4 rev=0x14 hdr=0x00
     vendor   = 'Broadcom Corporation'
     device   = 'BCM5700/1 Gigabit Ethernet Controller'
     class    = network
     subclass = ethernet
 pcib5@pci1:8:0:	class=0x060400 card=0x00000068 chip=0x03098086 rev=0x01 hdr=0x01
     vendor   = 'Intel Corporation'
     device   = '80303 I/O Processor PCI-to-PCI Bridge Unit'
     class    = bridge
     subclass = PCI-PCI
 aac0@pci1:8:1:	class=0x010400 card=0x01061028 chip=0x000a1028 rev=0x01 hdr=0x00
     vendor   = 'Dell Computer Corporation'
     device   = 'PowerEdge 3/Di Expandable RAID Controller'
     class    = mass storage
     subclass = RAID
 none1@pci2:6:0:	class=0x010000 card=0x00c51028 chip=0x00c59005 rev=0x01 hdr=0x00
     vendor   = 'Adaptec'
     device   = 'RAID Subsystem HBA'
     class    = mass storage
     subclass = SCSI
 none2@pci2:6:1:	class=0x010000 card=0x00c51028 chip=0x00c59005 rev=0x01 hdr=0x00
     vendor   = 'Adaptec'
     device   = 'RAID Subsystem HBA'
     class    = mass storage
     subclass = SCSI
 none3@pci9:6:0:	class=0x020000 card=0x11078086 chip=0x10088086 rev=0x02 hdr=0x00
     vendor   = 'Intel Corporation'
     device   = '82544 PRO/1000 Gigabit Ethernet Controller'
     class    = network
     subclass = ethernet
 pcib6@pci3:6:0:	class=0x060400 card=0x00000068 chip=0xa5001044 rev=0x02 hdr=0x01
     vendor   = 'Adaptec (Formerly: Distributed Processing Technology (DPT))'
     device   = 'PCI Bridge'
     class    = bridge
     subclass = PCI-PCI
 asr0@pci3:6:1:	class=0x0e0001 card=0xc03c1044 chip=0xa5011044 rev=0x02 hdr=0x00
     vendor   = 'Adaptec (Formerly: Distributed Processing Technology (DPT))'
     device   = 'I2O SmartRAID V Controller'
 isp0@pci3:8:0:	class=0x010000 card=0x00021077 chip=0x22001077 rev=0x05 hdr=0x00
     vendor   = 'Q Logic'
     device   = 'ISP2200'
     class    = mass storage
     subclass = SCSI
 bge1@pci14:6:0:	class=0x020000 card=0x000814e4 chip=0x164514e4 rev=0x15 hdr=0x00
     vendor   = 'Broadcom Corporation'
     device   = 'BCM5701 NetXtreme Gigabit Ethernet'
     class    = network
     subclass = ethernet
 
 Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 	The Regents of the University of California. All rights reserved.
 FreeBSD 4.6-STABLE #16: Sun Jul 21 16:47:14 CDT 2002
     dap@damon.com:/usr/obj/usr/src/sys/FUBAR
 Calibrating clock(s) ... TSC clock: 1984675976 Hz, i8254 clock: 1193326 Hz
 CLK_USE_I8254_CALIBRATION not specified - using default frequency
 Timecounter "i8254"  frequency 1193182 Hz
 CLK_USE_TSC_CALIBRATION not specified - using old calibration method
 Timecounter "TSC"  frequency 1984489484 Hz
 CPU: Pentium 4 (1984.49-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf24  Stepping = 4
   Features=0x3febfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,<b28>,ACC>
 real memory  = 536805376 (524224K bytes)
 Physical memory chunk(s):
 0x00001000 - 0x0009ffff, 651264 bytes (159 pages)
 0x00410000 - 0x1ffe7fff, 532512768 bytes (130008 pages)
 avail memory = 518557696 (506404K bytes)
 bios32: Found BIOS32 Service Directory header at 0xc00ffe80
 bios32: Entry = 0xffe90 (c00ffe90)  Rev = 0  Len = 1
 pcibios: PCI BIOS entry at 0xc67e
 pnpbios: Found PnP BIOS data at 0xc00fe2d0
 pnpbios: Entry = f0000:e2f4  Rev = 1.0
 Other BIOS signatures found:
 ACPI: 000fdc60
 Preloaded elf kernel "kernel" at 0xc03e9000.
 md0: Malloc disk
 Creating DISK md0
 pci_open(1):	mode 1 addr port (0x0cf8) is 0x800078ac
 pci_open(1a):	mode1res=0x80000000 (0x80000000)
 pci_cfgcheck:	device 0 [class=060000] [hdr=80] is there (id=00111166)
 Using $PIR table, 13 entries at 0xc00fc140
 pcib-: pcib1 exists, using next available unit number
 pcib-: pcib1 exists, using next available unit number
 pcib-: pcib3 exists, using next available unit number
 pcib-: pcib9 exists, using next available unit number
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
 pcib0: <ServerWorks CMIC-HE> on motherboard
 found->	vendor=0x1166, dev=0x0011, revid=0x22
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0011, revid=0x00
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0011, revid=0x00
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0011, revid=0x00
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x8086, dev=0x1229, revid=0x08
 	class=02-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 32, base fe204000, size 12
 	map[14]: type 1, range 32, base 0000ecc0, size  6
 	map[18]: type 1, range 32, base fe000000, size 20
 found->	vendor=0x9005, dev=0x001f, revid=0x01
 	class=01-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=10
 	map[10]: type 1, range 32, base 0000e800, size  8
 	map[14]: type 1, range 64, base fe203000, size 12
 found->	vendor=0x9004, dev=0x8178, revid=0x00
 	class=01-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 32, base 0000e400, size  8
 	map[14]: type 1, range 32, base fe202000, size 12
 found->	vendor=0x1002, dev=0x4752, revid=0x27
 	class=03-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	map[10]: type 1, range 32, base fd000000, size 24
 	map[14]: type 1, range 32, base 0000e000, size  8
 	map[18]: type 1, range 32, base fe201000, size 12
 found->	vendor=0x1166, dev=0x0201, revid=0x93
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0212, revid=0x93
 	class=01-01-82, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	map[10]: type 1, range 32, base 000008c0, size  3
 	map[14]: type 3, range 32, base 000008c8, size  2
 	map[18]: type 1, range 32, base 000008d0, size  3
 	map[1c]: type 3, range 32, base 000008d8, size  2
 	map[20]: type 1, range 32, base 000008b0, size  4
 found->	vendor=0x1166, dev=0x0220, revid=0x05
 	class=0c-03-10, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=5
 	map[10]: type 1, range 32, base fe200000, size 12
 found->	vendor=0x1166, dev=0x0225, revid=0x00
 	class=06-01-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0010, revid=0x03
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0010, revid=0x03
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0010, revid=0x03
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 found->	vendor=0x1166, dev=0x0010, revid=0x03
 	class=06-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 pci0: <PCI bus> on pcib0
 fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xecc0-0xecff mem 0xfe000000-0xfe0fffff,0xfe204000-0xfe204fff irq 11 at device 4.0 on pci0
 fxp0: using memory space register mapping
 fxp0: Ethernet address 00:06:5b:88:18:bc
 fxp0: PCI IDs: 8086 1229 1028 0106 0008
 fxp0: Dynamic Standby mode is disabled
 inphy0: <i82555 10/100 media interface> on miibus0
 inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 bpf: fxp0 attached
 ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xe800-0xe8ff mem 0xfe203000-0xfe203fff irq 10 at device 6.0 on pci0
 ahc0: Reading SEEPROM...done.
 ahc0: Manual LVD Termination
 ahc0: BIOS eeprom is present
 ahc0: Secondary High byte termination Enabled
 ahc0: Secondary Low byte termination Enabled
 ahc0: Primary Low Byte termination Enabled
 ahc0: Primary High Byte termination Enabled
 ahc0: Downloading Sequencer Program... 416 instructions downloaded
 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
 ahc1: <Adaptec 2940 Ultra SCSI adapter> port 0xe400-0xe4ff mem 0xfe202000-0xfe202fff irq 11 at device 8.0 on pci0
 ahc1: Reading SEEPROM...done.
 ahc1: internal 50 cable not present, internal 68 cable not present
 ahc1: external cable not present
 ahc1: BIOS eeprom is present
 ahc1: High byte termination Enabled
 ahc1: Low byte termination Enabled
 ahc1: Downloading Sequencer Program... 439 instructions downloaded
 	using shared irq11.
 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
 pci0: <ATI Mach64-GR graphics accelerator> (vendor=0x1002, dev=0x4752) at 14.0
 atapci0: <ServerWorks CSB5 ATA100 controller> port 0x8b0-0x8bf,0x8d8-0x8db,0x8d0-0x8d7,0x8c8-0x8cb,0x8c0-0x8c7 at device 15.1 on pci0
 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x08b0
 ata0: mask=03 ostat0=50 ostat2=01
 ata0-master: ATAPI 14 eb
 ata0-slave: ATAPI 14 eb
 ata0: mask=03 stat0=00 stat1=01
 ata0: devices=0c
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x08b8
 ata1: at 0x170 irq 15 on atapci0
 ohci0: <OHCI (generic) USB controller> mem 0xfe200000-0xfe200fff irq 5 at device 15.2 on pci0
 ohci0: (New OHCI DeviceId=0x02201166)
 ohci_init: start
 usb0: OHCI version 1.0, legacy support
 ohci_init: SMM active, request owner change
 usb0: SMM does not respond, resetting
 usb0: resetting
 usb0: <OHCI (generic) USB controller> on ohci0
 usb0: USB revision 1.0
 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 isab0: <PCI to ISA bridge (vendor=1166 device=0225)> at device 15.3 on pci0
 isa0: <ISA bus> on isab0
 pcib1: <ServerWorks CMIC-HE> on motherboard
 found->	vendor=0x14e4, dev=0x1644, revid=0x14
 	class=02-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=10
 	map[10]: type 1, range 64, base fcf00000, size 16
 found->	vendor=0x8086, dev=0x0309, revid=0x01
 	class=06-04-00, hdrtype=0x01, mfdev=1
 	subordinatebus=2 	secondarybus=2
 found->	vendor=0x1028, dev=0x000a, revid=0x01
 	class=01-04-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 32, base f0000000, size 27
 pci1: <PCI bus> on pcib1
 bge0: <Broadcom BCM5700 Gigabit Ethernet> mem 0xfcf00000-0xfcf0ffff irq 10 at device 6.0 on pci1
 	using shared irq10.
 bge0: Ethernet address: 00:06:5b:88:18:bd
 miibus1: <MII bus> on bge0
 brgphy0: <BCM5401 10/100/1000baseTX PHY> on miibus1
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
 bpf: bge0 attached
 pcib5: <PCI to PCI bridge (vendor=8086 device=0309)> at device 8.0 on pci1
 found->	vendor=0x9005, dev=0x00c5, revid=0x01
 	class=01-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 32, base 0000dc00, size  8
 	map[14]: type 1, range 64, base fcdff000, size 12
 found->	vendor=0x9005, dev=0x00c5, revid=0x01
 	class=01-00-00, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	intpin=b, irq=10
 	map[10]: type 1, range 32, base 0000d800, size  8
 	map[14]: type 1, range 64, base fcdfe000, size 12
 pci2: <PCI bus> on pcib5
 pci2: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.0 irq 11
 pci2: <unknown card> (vendor=0x9005, dev=0x00c5) at 6.1 irq 10
 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 11 at device 8.1 on pci1
 aac0: i960RX 100MHz, 118MB cache memory, optional battery present
 aac0: Kernel 2.7-0, Build 3153, S/N b821d3
 pcib9: <ServerWorks CMIC-HE> on motherboard
 found->	vendor=0x8086, dev=0x1008, revid=0x02
 	class=02-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 64, base ebf20000, size 17
 	map[18]: type 1, range 64, base ebf00000, size 17
 	map[20]: type 1, range 32, base 00008ce0, size  5
 pci9: <PCI bus> on pcib9
 pci9: <unknown card> (vendor=0x8086, dev=0x1008) at 6.0 irq 11
 pcib255: <ServerWorks CMIC-HE> on motherboard
 pci255: <PCI bus> on pcib255
 pci-: pci2 exists, using next available unit number
 pcib2: <ServerWorks host to PCI bridge> on motherboard
 found->	vendor=0x1044, dev=0xa500, revid=0x02
 	class=06-04-00, hdrtype=0x01, mfdev=1
 	subordinatebus=4 	secondarybus=4
 found->	vendor=0x1044, dev=0xa501, revid=0x02
 	class=0e-00-01, hdrtype=0x00, mfdev=1
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=11
 	map[10]: type 1, range 32, base ec000000, size 25
 found->	vendor=0x1077, dev=0x2200, revid=0x05
 	class=01-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=10
 	map[10]: type 1, range 32, base 0000bc00, size  8
 	map[14]: type 1, range 32, base eff00000, size 12
 pci3: <PCI bus> on pcib2
 pcib6: <PCI to PCI bridge (vendor=1044 device=a500)> at device 6.0 on pci3
 pci4: <PCI bus> on pcib6
 asr0: <Adaptec Caching SCSI RAID> mem 0xec000000-0xedffffff irq 11 at device 6.1 on pci3
 asr0: major=154
 asr0: ADAPTEC 2100S FW Rev. 370F, 1 channel, 256 CCBs, Protocol I2O
 Qlogic ISP Driver, FreeBSD Version 4.16, Core Version 2.6
 isp0: <Qlogic ISP 2200 PCI FC-AL Adapter> port 0xbc00-0xbcff mem 0xeff00000-0xeff00fff irq 10 at device 8.0 on pci3
 isp0: using I/O space register mapping
 isp0: Board Type 2200, Chip Revision 0x5, loaded F/W Revision 2.1.36
 isp0: Installed in 64-Bit PCI slot
 isp0: Last F/W revision was 2.0.27
 isp0: 985 max I/O commands supported
 isp0: NVRAM Port WWN 0x210000e08b01138a
 pci-: pci3 exists, using next available unit number
 pcib3: <ServerWorks host to PCI bridge> on motherboard
 pci5: <PCI bus> on pcib3
 pci-: pci4 exists, using next available unit number
 pcib4: <ServerWorks host to PCI bridge> on motherboard
 pci6: <PCI bus> on pcib4
 pcib10: <ServerWorks host to PCI bridge> on motherboard
 pci10: <PCI bus> on pcib10
 pcib14: <ServerWorks host to PCI bridge> on motherboard
 found->	vendor=0x14e4, dev=0x1645, revid=0x15
 	class=02-00-00, hdrtype=0x00, mfdev=0
 	subordinatebus=0 	secondarybus=0
 	intpin=a, irq=10
 	map[10]: type 1, range 64, base ead00000, size 16
 pci14: <PCI bus> on pcib14
 bge1: <Broadcom BCM5701 Gigabit Ethernet> mem 0xead00000-0xead0ffff irq 10 at device 6.0 on pci14
 bge1: Ethernet address: 00:10:18:02:2c:d8
 miibus2: <MII bus> on bge1
 brgphy1: <BCM5701 10/100/1000baseTX PHY> on miibus2
 brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
 bpf: bge1 attached
 ata-: ata0 exists, using next available unit number
 Trying Read_Port at 203
 Trying Read_Port at 243
 Trying Read_Port at 283
 Trying Read_Port at 2c3
 Trying Read_Port at 303
 Trying Read_Port at 343
 Trying Read_Port at 383
 Trying Read_Port at 3c3
 isa_probe_children: disabling PnP devices
 isa_probe_children: probing non-PnP devices
 orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcc7ff,0xd4000-0xd9fff,0xda000-0xda7ff,0xec000-0xeffff on isa0
 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 ata2 failed to probe at port 0x1f0 irq 14 on isa0
 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
 atkbd: the current kbd controller command byte 0065
 atkbd: keyboard ID 0x41ab (2)
 kbd0 at atkbd0
 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000
 psm0: current command byte:0065
 psm0: failed to reset the aux device.
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 fb0: vga0, vga, type:VGA (5), flags:0x7007f
 fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
 fb0: init mode:24, bios mode:3, current mode:24
 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
 VGA parameters upon power-up
 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 
 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
 VGA parameters in BIOS for mode 24
 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
 EGA/VGA parameters to be used for mode 24
 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
 sc0: <System console> at flags 0x100 on isa0
 sc0: VGA <16 virtual consoles, flags=0x300>
 sc0: fb0, kbd0, terminal emulator: sc (syscons terminal)
 sio0: irq maps: 0x1 0x11 0x1 0x1
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1: irq maps: 0x1 0x9 0x1 0x1
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: parallel port found at 0x378
 ppc0: using extended I/O port range
 ppc0: ECP SPP SPP
 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/8 bytes threshold
 lpt0: <Printer> on ppbus0
 lpt0: Interrupt-driven port
 isa_probe_children: probing PnP devices
 BIOS Geometries:
  0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
  1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
  2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors
  3:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors
  0 accounted for
 Device configuration finished.
 bpf: lo0 attached
 Linux ELF exec handler installed
 ata0-slave: ATAPI identify retries exceeded
 ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1
 ata0-master: success setting PIO4 on generic chip
 acd0: <LG DVD-ROM DRN-8080B/2.13> DVD-ROM drive at ata0 as master
 acd0:  512KB buffer, PIO4
 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet
 acd0: Writes:
 acd0: Audio: play, 255 volume levels
 acd0: Mechanism: ejectable tray, unlocked
 acd0: Medium: CD-ROM 120mm data disc
 (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted.
 aacd0: <RAID 5> on aac0
 aacd0: 32768MB (67108992 sectors)
 Creating DISK aacd0
 aacd1: <RAID 5> on aac0
 aacd1: 32768MB (67108992 sectors)
 Creating DISK aacd1
 aacd2: <RAID 5> on aac0
 aacd2: 38601MB (79056000 sectors)
 Creating DISK aacd2
 isp0: Firmware State <Config Wait->Loss Of Sync>
 (ahc0:A:6:0): Sending WDTR 1
 (ahc0:A:6:0): Received WDTR 1 filtered to 1
 ahc0: target 6 using 16bit transfers
 (ahc0:A:6:0): Sending SDTR period a, offset 7f
 (ahc0:A:6:0): Received SDTR period a, offset 20
 	Filtered to period a, offset 20
 ahc0: target 6 synchronous at 40.0MHz, offset = 0x20
 (ahc0:A:6:0): Sending WDTR 1
 (ahc0:A:6:0): Received WDTR 1 filtered to 1
 ahc0: target 6 using asynchronous transfers
 (ahc0:A:6:0): Sending SDTR period a, offset 20
 (ahc0:A:6:0): Received SDTR period a, offset 20
 	Filtered to period a, offset 20
 ahc0: target 6 synchronous at 40.0MHz, offset = 0x20
 Creating DISK da0
 sa0 at ahc0 bus 0 target 6 lun 0
 sa0: <ARCHIVE Python 06408-XXX 9050> Removable Sequential Access SCSI-3 device 
 sa0: Serial Number HN019LL
 sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)
 pass0 at ahc0 bus 0 target 6 lun 0
 pass0: <ARCHIVE Python 06408-XXX 9050> Removable Sequential Access SCSI-3 device 
 pass0: Serial Number HN019LL
 pass0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)
 pass1 at asr0 bus 0 target 8 lun 0
 pass1: <ADAPTEC RAID-5 370F> Fixed Direct Access SCSI-2 device 
 pass1: Serial Number +
 pass1: Tagged Queueing Enabled
 da0 at asr0 bus 0 target 8 lun 0
 da0: <ADAPTEC RAID-5 370F> Fixed Direct Access SCSI-2 device 
 da0: Serial Number +
 da0: Tagged Queueing Enabled
 da0: 26283MB (53827584 512 byte sectors: 255H 63S/T 3350C)
 Mounting root from ufs:/dev/aacd0s1a
 aacd0s1: type 0xa5, start 63, end = 67103504, size 67103442 : OK
 start_init: trying /sbin/init
 da0s1: type 0xa5, start 63, end = 26908874, size 26908812 : OK
 da0s2: type 0xa5, start 26908875, end = 53817749, size 26908875 : OK
 aacd1s1: type 0xa5, start 63, end = 67103504, size 67103442 : OK
 aacd2s1: type 0xa5, start 63, end = 79055864, size 79055802 : OK
 aacd1s1: type 0xa5, start 63, end = 67103504, size 67103442 : OK
 aacd1s1: type 0xa5, start 63, end = 67103504, size 67103442 : OK
 aacd2s1: type 0xa5, start 63, end = 79055864, size 79055802 : OK
 da0s1: type 0xa5, start 63, end = 26908874, size 26908812 : OK
 da0s2: type 0xa5, start 26908875, end = 53817749, size 26908875 : OK
 splash: image decoder found: logo_saver
 bge0: gigabit link up
 bge0: gigabit link up
 fxp0: promiscuous mode enabled
 fxp0: promiscuous mode disabled
 fxp0: promiscuous mode enabled
 fxp0: promiscuous mode disabled
 fxp0: promiscuous mode enabled
 fxp0: promiscuous mode disabled
 fxp0: promiscuous mode enabled
 fxp0: promiscuous mode disabled
 fxp0: promiscuous mode enabled
 fxp0: promiscuous mode disabled

From: Damon Anton Permezel <dap@damon.com>
To: Jung-uk Kim <jkim@niksun.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 17:10:01 -0500

 On Tue, Jul 23, 2002 at 05:28:01PM -0400, Jung-uk Kim wrote:
 > Andrew Gallatin wrote:
 > > Damon Anton Permezel writes:
 > >  > On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 > >  > > Jung-uk Kim writes:
 > >  > >  > Following patch says 0x02011166 is host to PCI bridge but it is
 > >  > >  > not. It is a southbridge.
 > >  > >  >
 > >  > >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.di
 > >  > >  >ff?r1=1.81&r2=1.82
 > >  > >  >
 > >  > >  > My SuperMicro P4DSE motherboard says:
 > >  > >  >
 > >  > >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9
 > >  > >  > chip=0x02011166 rev=0x93 hdr=0x00
 > >  > >
 > >  > > I was afraid of that..
 > >  > >
 > >  > > Damon,
 > >
 > > Well, class=0x060100 is definately an ISA bridge. So I think we're
 > > going to have to start looking at the class codes.
 > 
 > It is already done in -CURRENT. I believe -STABLE does it, too.
 > 
 > > Perhaps the host bridge is at another function on the same device?
 > 
 > Yes, it works as power management controller.
 
 Per the dox:
 
 
 	CSB5
 
 	PCI 2.2 32bit/33MHz
 	Legacy functions (8237DMA, 8259PIC, 8254Timer) 
 	PCI to LPC bridge 
 	XIO-APIC for multiprocessor systems 
 	4 Port USB 1.0 interface
 	ACPI power management and event detection support
 	Dual Channel ATA-100 hard disk controller 
 

From: Andrew Gallatin <gallatin@cs.duke.edu>
To: Damon Anton Permezel <dap@damon.com>
Cc: Jung-uk Kim <jkim@niksun.com>, freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Tue, 23 Jul 2002 18:11:42 -0400 (EDT)

 Damon Anton Permezel writes:
 
  > chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93 hdr=0x00
  >     vendor   = 'Reliance Computer Corp./ServerWorks'
  >     device   = 'CSB5 PCI to ISA Bridge'
  >     class    = bridge
  >     subclass = HOST-PCI
 
 
 This is interesting.  According to the class code, it IS a host-pci
 bridge on Damon's Dell, and not an isa bridge like the device ID code
 on file would indicate.
 
 Drew

From: Jung-uk Kim <jkim@niksun.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>,
	Damon Anton Permezel <dap@damon.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 12:48:48 -0400

 Andrew Gallatin wrote:
 > Damon Anton Permezel writes:
 >  > chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93
 >  > hdr=0x00 vendor   = 'Reliance Computer Corp./ServerWorks'
 >  >     device   = 'CSB5 PCI to ISA Bridge'
 >  >     class    = bridge
 >  >     subclass = HOST-PCI
 >
 > This is interesting.  According to the class code, it IS a host-pci
 > bridge on Damon's Dell, and not an isa bridge like the device ID code
 > on file would indicate.
 
 Indeed it is very interesting. I don't know it is possible or not but it seems 
 the chip can 'act like a PCI bridge' when the following function is enabled.
 
 isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00 
 hdr=0x00
      vendor   = 'Reliance Computer Corp./ServerWorks'
      class    = bridge
      subclass = PCI-ISA
 
 The following link has several entries for CSB5. :-(
 
 http://www.yourvote.com/pci/pciread.asp?venid=0x1166
 
 Jung-uk Kim
 
 > Drew
 

From: Damon Anton Permezel <dap@damon.com>
To: Jung-uk Kim <jkim@niksun.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 12:01:08 -0500

 On Wed, Jul 24, 2002 at 12:48:48PM -0400, Jung-uk Kim wrote:
 > Andrew Gallatin wrote:
 > > Damon Anton Permezel writes:
 > >  > chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93
 > >  > hdr=0x00 vendor   = 'Reliance Computer Corp./ServerWorks'
 > >  >     device   = 'CSB5 PCI to ISA Bridge'
 > >  >     class    = bridge
 > >  >     subclass = HOST-PCI
 > >
 > > This is interesting.  According to the class code, it IS a host-pci
 > > bridge on Damon's Dell, and not an isa bridge like the device ID code
 > > on file would indicate.
 > 
 > Indeed it is very interesting. I don't know it is possible or not but it seems 
 > the chip can 'act like a PCI bridge' when the following function is enabled.
 > 
 > isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00 
 > hdr=0x00
 >      vendor   = 'Reliance Computer Corp./ServerWorks'
 >      class    = bridge
 >      subclass = PCI-ISA
 > 
 
 It can act like a PCI bridge because it is, among other things, a PCI bridge.
 Take a look at the documentation at serverworks.com per the link
 I posted yesterday.  It is a multi-function device.

From: Jung-uk Kim <jkim@niksun.com>
To: Damon Anton Permezel <dap@damon.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 14:27:20 -0400

 Damon Anton Permezel wrote:
 > On Wed, Jul 24, 2002 at 12:48:48PM -0400, Jung-uk Kim wrote:
 > > Andrew Gallatin wrote:
 > > > Damon Anton Permezel writes:
 > > >  > chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166
 > > >  > rev=0x93 hdr=0x00 vendor   = 'Reliance Computer Corp./ServerWorks'
 > > >  >     device   = 'CSB5 PCI to ISA Bridge'
 > > >  >     class    = bridge
 > > >  >     subclass = HOST-PCI
 > > >
 > > > This is interesting.  According to the class code, it IS a host-pci
 > > > bridge on Damon's Dell, and not an isa bridge like the device ID code
 > > > on file would indicate.
 > >
 > > Indeed it is very interesting. I don't know it is possible or not but it
 > > seems the chip can 'act like a PCI bridge' when the following function is
 > > enabled.
 > >
 > > isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00
 > > hdr=0x00
 > >      vendor   = 'Reliance Computer Corp./ServerWorks'
 > >      class    = bridge
 > >      subclass = PCI-ISA
 >
 > It can act like a PCI bridge because it is, among other things, a PCI
 > bridge. Take a look at the documentation at serverworks.com per the link
 > I posted yesterday.  It is a multi-function device.
 
 I believe CMIC-HE turned on the feature. Note that SuperMicro P4DSE has 
 CMIC-SL (Check http://www.serverworks.com/products/GCSL.html for block 
 diagram).
 
 chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x00171166 rev=0x01 
 hdr=0x00
 
 Please note that web page says 64-bit PCI is supported by CSB5 for CMIC-SL. On 
 the other hand, CSB5 supports 32-bit PCI for CMIC-HE. I assume that the 
 function is controlled by CMIC-HE/SL. When there is CMIC-SL, the chip acts as 
 traditional southbridge. When there is CMIC-HE, 0x02011166 is pass-through 
 and 0x02251166 is enabled to take the task.
 
 We may have to check subclass for the CSB5. :-(
 
 Any idea?
 
 Jung-uk Kim

From: Andrew Gallatin <gallatin@cs.duke.edu>
To: jkim@niksun.com
Cc: Damon Anton Permezel <dap@damon.com>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 14:32:01 -0400 (EDT)

 Jung-uk Kim writes:
  > We may have to check subclass for the CSB5. :-(
 
 Yeah, that's what I said yesterday ;)
 
 Drew

From: Jung-uk Kim <jkim@niksun.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Damon Anton Permezel <dap@damon.com>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 16:43:34 -0400

 Andrew Gallatin wrote:
 > Jung-uk Kim writes:
 >  > We may have to check subclass for the CSB5. :-(
 >
 > Yeah, that's what I said yesterday ;)
 
 My buddy at work suggested very interesting idea. If you look carefully at the 
 GC-SL chipset web page, it claims it uses CSB6, not CSB5.
 
 CSB5
 
     * PCI 2.2 32bit/33MHz
     * Legacy functions (8237DMA, 8259PIC, 8254Timer)
     * PCI to LPC bridge
     * XIO-APIC for multiprocessor systems
     * 4 Port USB 1.0 interface
     * ACPI power management and event detection support
     * Dual Channel ATA-100 hard disk controller
 
 CSB6
 
     * PCI 2.2 64-bit/33MHz
     * Legacy functions (8237DMA, 8259PIC, 8254Timer)
     * PCI to LPC bridge
     * XIO-APIC for multiprocessor systems
     * 4 Port USB 1.1 interface
     * ACPI power management and event detection support
     * Three ATA channels supporting up to 6 hard disk drives
     * Server Appliance functions: Watchdog timer, NVRAM support, LCD and 
 Keypad support
 
 However, diagram still shows it uses CSB5. :-( His point was one of us may 
 have CSB6, not CSB5, although there's no difference in device ID and revision 
 numbers.
 
 Here is P4DSE's pciconf:
 
 isab0@pci0:15:0:	class=0x060100 card=0x405515d9 chip=0x02011166 rev=0x93 
 hdr=0x00
 atapci0@pci0:15:1:	class=0x01018a card=0x021211d9 chip=0x02121166 rev=0x93 
 hdr=0x00
 none1@pci0:15:2:	class=0x0c0310 card=0x405515d9 chip=0x02201166 rev=0x05 
 hdr=0x00
 chip2@pci0:15:3:	class=0x060000 card=0x405515d9 chip=0x02251166 rev=0x00 
 hdr=0x00
 
 This is Dell's pciconf:
 
 chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93 
 hdr=0x00
 atapci0@pci0:15:1:	class=0x010182 card=0x02121166 chip=0x02121166 rev=0x93 
 hdr=0x00
 ohci0@pci0:15:2:	class=0x0c0310 card=0x02201166 chip=0x02201166 rev=0x05 
 hdr=0x00
 isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00 
 hdr=0x00
 
 The only difference I can see is the functions of 0x02011166 and 0x02251166 
 are switched. Somebody did very screw-up job. ServerWorks? SuperMicro? Dell? 
 I don't know.
 
 Jung-uk Kim
 
 > Drew
 

From: Damon Anton Permezel <dap@damon.com>
To: Jung-uk Kim <jkim@niksun.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 15:54:34 -0500

 On Wed, Jul 24, 2002 at 04:43:34PM -0400, Jung-uk Kim wrote:
 > Andrew Gallatin wrote:
 > > Jung-uk Kim writes:
 > >  > We may have to check subclass for the CSB5. :-(
 > >
 > > Yeah, that's what I said yesterday ;)
 > 
 > My buddy at work suggested very interesting idea. If you look carefully at the 
 > GC-SL chipset web page, it claims it uses CSB6, not CSB5.
 > 
 > CSB5
 > 
 >     * PCI 2.2 32bit/33MHz
 >     * Legacy functions (8237DMA, 8259PIC, 8254Timer)
 >     * PCI to LPC bridge
 >     * XIO-APIC for multiprocessor systems
 >     * 4 Port USB 1.0 interface
 >     * ACPI power management and event detection support
 >     * Dual Channel ATA-100 hard disk controller
 > 
 > CSB6
 > 
 >     * PCI 2.2 64-bit/33MHz
 >     * Legacy functions (8237DMA, 8259PIC, 8254Timer)
 >     * PCI to LPC bridge
 >     * XIO-APIC for multiprocessor systems
 >     * 4 Port USB 1.1 interface
 >     * ACPI power management and event detection support
 >     * Three ATA channels supporting up to 6 hard disk drives
 >     * Server Appliance functions: Watchdog timer, NVRAM support, LCD and 
 > Keypad support
 > 
 > However, diagram still shows it uses CSB5. :-( His point was one of us may 
 > have CSB6, not CSB5, although there's no difference in device ID and revision 
 > numbers.
 
 http://www.supermicro.com/PRODUCT/MotherBoards/GC_SL/P4DSE.htm
 claims to have the GC-SL.
 
 Can the "card" be used to distinguish?
 
 > 
 > Here is P4DSE's pciconf:
 > 
 > isab0@pci0:15:0:	class=0x060100 card=0x405515d9 chip=0x02011166 rev=0x93 
 > hdr=0x00
 > atapci0@pci0:15:1:	class=0x01018a card=0x021211d9 chip=0x02121166 rev=0x93 
 > hdr=0x00
 > none1@pci0:15:2:	class=0x0c0310 card=0x405515d9 chip=0x02201166 rev=0x05 
 > hdr=0x00
 > chip2@pci0:15:3:	class=0x060000 card=0x405515d9 chip=0x02251166 rev=0x00 
 > hdr=0x00
 > 
 > This is Dell's pciconf:
 > 
 > chip4@pci0:15:0:	class=0x060000 card=0x02011166 chip=0x02011166 rev=0x93 
 > hdr=0x00
 > atapci0@pci0:15:1:	class=0x010182 card=0x02121166 chip=0x02121166 rev=0x93 
 > hdr=0x00
 > ohci0@pci0:15:2:	class=0x0c0310 card=0x02201166 chip=0x02201166 rev=0x05 
 > hdr=0x00
 > isab0@pci0:15:3:	class=0x060100 card=0x02301166 chip=0x02251166 rev=0x00 
 > hdr=0x00
 > 
 > The only difference I can see is the functions of 0x02011166 and 0x02251166 
 > are switched. Somebody did very screw-up job. ServerWorks? SuperMicro? Dell? 
 > I don't know.
 > 
 > Jung-uk Kim
 > 
 > > Drew
 
 -- 
 --
 Damon Permezel
 dap@damon.com
 

From: Jung-uk Kim <jkim@niksun.com>
To: Damon Anton Permezel <dap@damon.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
	freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 17:09:56 -0400

 Damon Anton Permezel wrote:
 > http://www.supermicro.com/PRODUCT/MotherBoards/GC_SL/P4DSE.htm
 > claims to have the GC-SL.
 >
 > Can the "card" be used to distinguish?
 
 No, that cannot be used. It only tells you who made the motherboard. 0x15d9 is 
 SuperMicro. 0x11d9 is a kind of screwup. Yours shows 0x1166 because the 
 motherboard maker didn't change the default values. I still believe that 
 0x02011166 is PCI-to-ISA and 0x02251166 is host-to-PCI bridge because I can 
 use any buses without any patch. 0x02001166 was old chip ID. Naturally they 
 must increase the number by one. ;)
 
 FYI, this is dump from my Intel STL2 mobo:
 
 isab0@pci0:15:0:	class=0x060100 card=0x02001166 chip=0x02001166 rev=0x50 
 hdr=0x00
 atapci0@pci0:15:1:	class=0x01018e card=0x00000000 chip=0x02111166 rev=0x00 
 hdr=0x00
 
 Jung-uk Kim

From: Damon Anton Permezel <dap@damon.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Jung-uk Kim <jkim@niksun.com>, freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 24 Jul 2002 18:18:25 -0500

 On Tue, Jul 23, 2002 at 03:15:29PM -0400, Andrew Gallatin wrote:
 > 
 > Jung-uk Kim writes:
 >  > Following patch says 0x02011166 is host to PCI bridge but it is not. It 
 >  > is a southbridge.
 >  > 
 >  > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/pci/pci_bus.c.diff?r1=1.81&r2=1.82
 >  > 
 >  > My SuperMicro P4DSE motherboard says:
 >  > 
 >  > isab0@pci0:15:0:        class=0x060100 card=0x405515d9 chip=0x02011166 
 >  > rev=0x93 hdr=0x00
 >  > 
 > 
 > I was afraid of that..
 > 
 > Damon,
 > 
 > If you comment out 0x02011166 in pci_bus.c, does your system still
 > work?
 > 
 
 Yes.

From: John Baldwin <jhb@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org, dap@damon.com
Cc:  
Subject: Re: kern/38894: Dell PowerEdge 4600 PCI Bus scan problems
Date: Wed, 31 Dec 2003 11:03:11 -0500

 Does current work on this box?  Current does treat 0x00111166 device id as a 
 serverworks host-pci bridge.  It looks like -stable might still need to add 
 that device id however.
 
 -- 
 John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
 "Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
 
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Oct 25 03:30:10 GMT 2005 
State-Changed-Why:  
Feedback timeout (> 1 year). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=38894 
>Unformatted:
