From owner-freebsd-i386@FreeBSD.ORG Thu Sep 7 00:58:57 2006 Return-Path: X-Original-To: freebsd-i386@freebsd.org Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 720E016A4E7 for ; Thu, 7 Sep 2006 00:58:57 +0000 (UTC) (envelope-from workdamyou@yahoo.ca) Received: from web32102.mail.mud.yahoo.com (web32102.mail.mud.yahoo.com [68.142.207.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 99B2D43D76 for ; Thu, 7 Sep 2006 00:58:53 +0000 (GMT) (envelope-from workdamyou@yahoo.ca) Received: (qmail 58279 invoked by uid 60001); 7 Sep 2006 00:58:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3LrhG6mVWc7o9vwZGLGjxP0hFygU+tJ9LGPLnJ89R1pD4FURWFzBQUVBe1njCWXpgLtZUPhdpldtweaual8L44tFQmNNwGMZZVWib0r6fah1IGf0zsa3qdO8BTe7bSrPc4IQ4SVJWhnV9WAnpGWfJo9dSK5o3iwuOSZ0KebIHrU= ; Message-ID: <20060907005852.58277.qmail@web32102.mail.mud.yahoo.com> Received: from [206.248.137.118] by web32102.mail.mud.yahoo.com via HTTP; Wed, 06 Sep 2006 17:58:52 PDT Date: Wed, 6 Sep 2006 17:58:52 -0700 (PDT) From: -MM- To: freebsd-i386@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: missing bridge X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2006 00:58:57 -0000 Greetings, I've asked around a couple of places, and really got no answer to this. I'm wondering if someone here can assist, as I'm out of ideas. Pardon the lengthy email, however I'm just about at my wits end with this!! Currently I have FBSD4.9 (G)eneric (R)elease installed on a HD that's located on a Symbios 53C896 harddrive controller. Also, FBSD6.1 (GR) is installed on a HD via a Qlogic 2200. My problem is that the disk array that the Qlogic is connected to isn't mine, and that I'd like to get 6.1 to run off of the internal (attached to the mobo) 896. The problem is that the 896 is behind some host -> PCI bus, and that 6.1 'doesn't see pcib2', yet 4.9 does. By means of using floppies and booting different versions, the change occurs between 4.11 and 5.0 (AFAIK, when acpi was implemented.) However, there is a lot of code changes, thus it's tough to pinpoint where the issue may be. The system is a Intergraph TDZ 2000 GT1 workstation, Phoenix BIOS 4.0 R6.0 (V8990T) (most recent curr. ver.), dual 700Mhz, 1GB RAM. (http://support.intergraph.com/itservices/sysdocs/workstation/dha029520.pdf) The 6.1 system has been hacked at a couple of times in attempt to get things like DMI/DRM to work with my hardware, but not much else is different. ACPI doesn't work on this machine. There is mention about SMBUS / ACPI on irq 9 within the system setup manual. (p.67 http://support.intergraph.com/itservices/sysdocs/workstation/dha029420.pdf) However, back to the bus problem... As you can see from pirtool (below), the bus is there, the hardware (vendor 0x1000 device 0x000b) is hiding on that bus (2) however lspci doesn't show it. scanpci shows that it's there. - Is there a loader.conf hint /device.hint to map this hardware so that the kernel will see it? - Is this some odd irq mapping issue? - Does anyone have any suggestions as to where to throw in a couple of printf statements into the kernel code, to show why the kernel is skipping / dropping pcib2? Any suggestions would help and be appreciated. Thank-you for your time in advance. ~Michael. -- other locations for things that might be useful: 6.1 & 4.9 dmesgs http://groups.google.com/group/comp.unix.bsd.freebsd.misc/browse_frm/thread/49dfc32ab3593bbd/8bdd58ee98b58589#8bdd58ee98b58589 ======================================= Currently, biosdecode shows; (read from /dev/mem) ======================================= # biosdecode 2.8 SMBIOS 2.1 present. Structure Table Length: 1293 bytes Structure Table Address: 0x000F14A0 Number Of Structures: 41 Maximum Structure Size: 137 bytes BIOS32 Service Directory present. Revision: 0 Calling Interface Address: 0x000FD6C0 PNP BIOS 1.0 present. Event Notification: Not Supported Real Mode 16-bit Code Address: F000:A048 Real Mode 16-bit Data Address: 0040:0000 16-bit Protected Mode Code Address: 0x000FA066 16-bit Protected Mode Data Address: 0x00000400 PCI Interrupt Routing 1.0 present. Router ID: ff:1f.7 Exclusive IRQs: None Slot Entry 1: ID 00:00, on-board Slot Entry 2: ID 01:00, slot number 15 Slot Entry 3: ID 00:0f, on-board Slot Entry 4: ID 00:01, on-board Slot Entry 5: ID 03:03, on-board Slot Entry 6: ID 00:03, on-board Slot Entry 7: ID 02:01, on-board Slot Entry 8: ID 03:02, on-board Slot Entry 9: ID 00:0c, slot number 1 Slot Entry 10: ID 00:0d, slot number 2 Slot Entry 11: ID 00:0e, slot number 3 Slot Entry 12: ID 02:0c, slot number 4 Slot Entry 13: ID 02:0d, slot number 5 Slot Entry 14: ID 02:0e, slot number 6 Slot Entry 15: ID 03:0b, slot number 7 ======================================= and pirtool shows... PCI Interrupt Routing Table at 0x000FDE60 ----------------------------------------- 0x00: Signature: $PIR 0x04: Version: 1.0 0x06: Size: 272 bytes (15 entries) 0x08: Device: 255:31:7 0x0a: PCI Exclusive IRQs: 0x00000000 0x0c: Compatible with: 0x00000000 unknown chipset 0x10: Miniport Data: 0x00000000 0x1f: Checksum: 0xC5 Entry 0: Device 0:0:0 Slot 0 (on-board) Entry 1: Device 1:0:0 Slot 15 INTA: 10h INTB: 0dh Entry 2: Device 0:15:0 Slot 0 (on-board) INTA: 11h Entry 3: Device 0:1:0 Slot 0 (on-board) INTA: 08h Entry 4: Device 3:3:0 Slot 0 (on-board) INTA: 0fh Entry 5: Device 0:3:0 Slot 0 (on-board) INTA: 0fh Entry 6: Device 2:1:0 Slot 0 (on-board) INTA: 0bh INTB: 0ch Entry 7: Device 3:2:0 Slot 0 (on-board) INTA: 0eh Entry 8: Device 0:12:0 Slot 1 INTA: 05h INTB: 06h INTC: 07h INTD: 08h Entry 9: Device 0:13:0 Slot 2 INTA: 06h INTB: 07h INTC: 08h INTD: 05h Entry 10: Device 0:14:0 Slot 3 INTA: 07h INTB: 08h INTC: 05h INTD: 06h Entry 11: Device 2:12:0 Slot 4 INTA: 09h INTB: 0ah INTC: 0bh INTD: 0ch Entry 12: Device 2:13:0 Slot 5 INTA: 0ah INTB: 0bh INTC: 0ch INTD: 09h Entry 13: Device 2:14:0 Slot 6 INTA: 0ch INTB: 09h INTC: 0ah INTD: 0bh Entry 14: Device 3:11:0 Slot 7 INTA: 0dh INTB: 0eh INTC: 0fh INTD: 10h ** lspci's *** =========================== TDZ2KGT1# /bin/lspci -M 00:00.0 0600: 1166:0007 (rev 04) 00:00.1 0604: 1166:0005 (rev 02) ## 00.00:1 is a bridge from 00 to 01-01 00:01.0 0200: 10b7:9055 (rev 24) 00:03.0 0401: 1274:1371 (rev 02) 00:0c.0 0300: 121a:0005 (rev 01) 00:0e.0 0401: 1220:4242 (rev 02) 00:0f.0 0601: 1166:0200 (rev 4d) 00:11.0 0600: 1166:0007 (rev 04) 00:11.1 0600: 1166:0005 (rev 02) 03:02.0 0100: 1000:0006 (rev 13) 03:0b.0 0100: 1077:2100 (rev 03) Summary of buses: 00: Primary host bus 00.1 Bridge to 01-01 03: Secondary host bus (?) =========================== TDZ2KGT1# /bin/lspci -vvv 00:00.0 0600: 1166:0007 (rev 04) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-SERR- TAbort-SERR- TAbort-Reset- FastB2B- Capabilities: [80] AGP version 1.0 Status: RQ=17 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans-64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW-Rate=x1 00:01.0 0200: 10b7:9055 (rev 24) Subsystem: 1091:9055 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort-SERR- TAbort-SERR- (32-bit, prefetchable) 00:11.1 0600: 1166:0005 (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-SERR-