From owner-freebsd-current Sat Jun 19 2:21:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 5DE4814E93 for ; Sat, 19 Jun 1999 02:21:47 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 59647 invoked by uid 1001); 19 Jun 1999 09:21:46 +0000 (GMT) To: dfr@nlsystems.com Cc: jlemon@americantv.com, current@freebsd.org Subject: Re: New-bus questions From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 19 Jun 1999 06:16:52 +0100 (BST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 19 Jun 1999 11:21:46 +0200 Message-ID: <59645.929784106@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a Compaq 3000 which I'm trying to get working. Under > > -STABLE, it detects 4 PCI buses, and probes the devices on > > the buses correctly. Under -current, it only detects 2 PCI > > buses. Unfortunatly, my boot device is on one of the non- > > detected buses, making debugging slightly difficult. > > > > FWIW, I can't get SMP working on this machine either, since > > only two PCI buses are listed in the MP table; and I can't see > > any "set Full MPTable" in Compaq's blasted Ctrl-A config utility. > > > > > > 1. Why does -stable work and not -current? > > 2. Does new-bus require an MP table (or equivalent) to detect the buses? > > I think this is a machine with multiple host-pci bridges. Could you send > me a dmesg so that I can see what chipset is being used. I think we can > support this by pretending the second bridge is a pci-pci bridge. If it's the Proliant 3000, it does indeed have two host-pci bridges. Here's the dmesg output for a box running 3.2-STABLE. (Those of you with sharp eyes might wonder about the memory lines. The box has 576 MB memory. We had some stability problems, and I suspected part of the upper memory was being used by the BIOS etc - so I made a kernel with MAXMEM of 572 MBytes. Later it turned out that the stability problems were probably due to insufficient mbuf clusters. After we upped this to 4096, the box has been extremely stable.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #0: Wed Jun 2 23:21:41 CEST 1999 sthaug@newsfeed1.telia.no:/local/freebsd/src/sys/compile/NEWSFEED1 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff> real memory = 599785472 (585728K bytes) avail memory = 580280320 (566680K bytes) Programming 28 pins in IOAPIC #0 EISA INTCONTROL = 00000620 IOAPIC #0 intpint 24 -> irq 5 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x001b0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02cd000. eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 vga0: rev 0x22 int a irq 255 on pci0.6.0 chip1: rev 0x07 on pci0.15.0 chip2: rev 0x03 on pci0.17.0 Probing for devices on PCI bus 1: ncr0: rev 0x14 int a irq 19 on pci1.4.0 ncr1: rev 0x14 int b irq 18 on pci1.4.1 fxp0: rev 0x05 int a irq 18 on pci1.7.0 fxp0: Ethernet address 00:90:27:13:f6:21 tl0: rev 0x10 int a irq 17 on pci1.8.0 tl0: Ethernet address: 00:08:c7:1e:a7:35 tl0: autoneg complete, link status good (half-duplex, 100Mbps) Probing for devices on PCI bus 2: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0: failed to get data. psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 1378KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 ccd0-3: Concatenated disk drivers Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s3da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da2 at ncr0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da3 at ncr0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message