Date: Mon, 12 Mar 2001 02:20:12 -0500 From: "Andrew C. Hornback" <hornback@wireco.net> To: "Charles Burns" <burnscharlesn@hotmail.com> Cc: <questions@freebsd.org> Subject: RE: ProLiant 1500 questions... Message-ID: <026401c0aac4$e18585f0$0f00000a@eagle> In-Reply-To: <F211Vn20lbhsKd6QR7j00001911@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of > Charles Burns > Sent: Sunday, March 11, 2001 12:44 AM > To: hornback@wireco.net; questions@freebsd.org > Subject: RE: ProLiant 1500 questions... > > > Err, I have absolutely no idea why FreeBSD is reporting 8 > PCI bridges. As > long as it isn't causing problems I would just write it off > as a weird > glitch. I think it may have something to do with the way that the ProLiant handles I/O, since it does seem to scream as far as I/O goes. > As far as the controller issue, from what I gather > the driver for > many Compaq RAID controller, including yours, isn't in a > 'final' form due to > Compaq's lack of helpful hardware specs or detailed > programming interface > information. I have never worked with this controller, so > the best that I > can do is give some general and probably useless advice: > > Try updating the controllers firmware. Updates can usually > be found at > http://www.compaq.com/support/files/server/us/index.html Already upgraded to the newest version possible. > Try using an older version of the driver. The current one > is a rewrite of > Mark Dawson's drivers which can be found at > http://www.doc.ic.ac.uk/~md/ida/ > > Andy Doran (ad@netbsd.org) wrote a driver for NetBSD last > year. You might > ask him to release it for FreeBSD if it hasn't already been done I might do that, but, the machine seems to run fine as soon as it boots properly. Just one of those quirks, I guess. > I have no idea how to reload the kernel multiple times > other than by doing > it manually at the initial timed prompt. If the controller > needs some more > time to initialize, you can increase the delay time of that > initial prompt. > I can't for the life of me remember how at the moment, but > it's really > simple. Perhaps after some sleep. I'm sure someone on this > board will > remember better than myself as I am still a FreeBSD novice myself. Talking to the friend of mine that originally helped me set the box up, he mentioned something about editing the /boot/loader.rc file, and adding what I needed to do to the end of it. I'm going to investigate that solution and see what I can come up with. Basically, it's just an inconvenience that the system has to have manual intervention when it boots, but, since this is going to be a server/firewall machine on my network, and it won't have a head setup on it, it needs to be "hands off"... > Sorry I couldn't help more. The problem does sound similar > to one that > occurs on my server with it's SCSI controller if the SCSI > timeout is set too > low. While the SCSI timeout apparently doesn't apply to your RAID > controller, the need for a timeout may apply. *nods* We think that the drive array doesn't "settle" properly until there's an intervening read to the drive. There could be something about the way that the RAID is set up, or something like that. > Here's a shot in the dark--if the disks aren't spinning up > fast enough...and > I am probably utterly on the wrong track here...you may be > able to set the > disks to spin up immediately upon powerup rather than on > the SCSI-bus > startup command (which is often default). > My Seagate Elite SX4464524 requires around a 20 second > pause at boot time if > I don't enable that feature. The controller determines when the drives spin up. This sounds like it could be the culprit though, since they may not have settled back down properly from the initial spin up, due to the fact that FreeBSD boots like a speed demon. Thoroughly impressive speed. > Must. Sleep. Now. > > Charles Burns > > >From: "Andrew C. Hornback" <hornback@wireco.net> > >To: "Charles Burns" <burnscharlesn@hotmail.com> > >CC: <questions@freebsd.org> > >Subject: RE: ProLiant 1500 questions... > >Date: Sat, 10 Mar 2001 20:16:26 -0500 > > > >Charles, > > > > Thanks for the reply, but I think we're in the wrong area. > > > > I'm including my dmesg output below. As you can see, > the problem > >with ida0 shows up a good deal before the "Waiting 5 > seconds for SCSI > >devices to settle" in the dmesg entry. > > > > I've been told that I should go through the > /boot/loader.rc and tell > >it to unload and reload the kernel (at least once) to prevent this > >error, since that's what I do manually to make the machine boot... > > > > Any ideas? > > > > Also, any idea why this machine sees 8 separate PCI > busses? It's > >only got one, as far as I know. One bus with 3 slots, all > filled... 8 > >slots total, 3 PCI / 5 EISA, with none of the EISA slots used. > > > > > >--- Andy > >------------------------ dmesg output --- > > > >Copyright (c) 1992-2000 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.2-RELEASE #0: Fri Mar 9 02:31:20 EST 2001 > > root@CLASSIFIED:/usr/src/sys/compile/CLASSIFIED > >Timecounter "i8254" frequency 1193182 Hz > >CPU: Pentium/P54C (133.61-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > > Features=0x3bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC> > >real memory = 67108864 (65536K bytes) > >avail memory = 62533632 (61068K bytes) > >Changing APIC ID for IO APIC #0 from 0 to 2 on chip > >Programming 16 pins in IOAPIC #0 > >IOAPIC #0 intpin 2 -> irq 0 > >FreeBSD/SMP: Multiprocessor motherboard > > cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 > > cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 > > io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 > >Preloaded elf kernel "kernel" at 0xc02d1000. > >Intel Pentium detected, installing workaround for F00F bug > >md0: Malloc disk > >npx0: <math processor> on motherboard > >npx0: INT 16 interface > >pcib0: <Host to PCI bridge> on motherboard > >pci0: <PCI bus> on pcib0 > >ncr0: <ncr 53c825 fast10 wide scsi> port 0x7100-0x71ff mem > >0x4300000-0x43000ff irq 10 at device 10.0 on pci0 > >pcib8: <IBM 82351 PCI-PCI bridge> at device 12.0 on pci0 > >pci1: <PCI bus> on pcib8 > >ida0: <Compaq SMART-2/P array controller> port 0x8000-0x80ff mem > >0x42000000-0x43ffffff,0x40000000-0x400000ff irq 11 at device 0.0 on > >pci1 > >ida0: drives=1 firm_rev=1.24 > >idad0: <Compaq Logical Drive> on ida0 > >idad0: 4012MB (8217440 sectors), blocksize=512 > >tx0: <SMC EtherPower II 10/100> port 0x7200-0x72ff mem > >0x4400000-0x4400fff irq 9 at device 13.0 on pci0 > >miibus0: <MII bus> on tx0 > >nsphy0: <QS6612 10/100 media interface> on miibus0 > >nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >tx0: address 00:e0:29:22:36:ee, type SMC9432TX > >tx1: <SMC EtherPower II 10/100> port 0x7000-0x70ff mem > >0x4200000-0x4200fff irq 5 at device 14.0 on pci0 > >miibus1: <MII bus> on tx1 > >nsphy1: <QS6612 10/100 media interface> on miibus1 > >nsphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >tx1: address 00:e0:29:21:e8:17, type SMC9432TX > >isab0: <Intel 82375EB PCI-EISA bridge> at device 15.0 on pci0 > >eisa0: <EISA bus> on isab0 > >mainboard0: <CPQ0811 (System Board)> on eisa0 slot 0 > >isa0: <ISA bus> on isab0 > >pcib1: <Host to PCI bridge> on motherboard > >pci2: <PCI bus> on pcib1 > >pcib2: <Host to PCI bridge> on motherboard > >pci3: <PCI bus> on pcib2 > >pcib3: <Host to PCI bridge> on motherboard > >pci4: <PCI bus> on pcib3 > >pcib4: <Host to PCI bridge> on motherboard > >pci5: <PCI bus> on pcib4 > >pcib5: <Host to PCI bridge> on motherboard > >pci6: <PCI bus> on pcib5 > >pcib6: <Host to PCI bridge> on motherboard > >pci7: <PCI bus> on pcib6 > >pcib7: <Host to PCI bridge> on motherboard > >pci8: <PCI bus> on pcib7 > >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 > >atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > >atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > >kbd0 at atkbd0 > >psm0: <PS/2 Mouse> irq 12 on atkbdc0 > >psm0: model Generic PS/2 mouse, device ID 0 > >vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem > 0xa0000-0xbffff on > >isa0 > >sc0: <System console> at flags 0x100 on isa0 > >sc0: VGA <16 virtual consoles, flags=0x300> > >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > >sio0: type 16550A > >sio1 at port 0x2f8-0x2ff irq 3 on isa0 > >sio1: type 16550A > >stray irq 7 > >APIC_IO: Testing 8254 interrupt delivery > >APIC_IO: routing 8254 via IOAPIC #0 intpin 2 > >Waiting 5 seconds for SCSI devices to settle > >SMP: AP CPU #1 Launched! > >sa0 at ncr0 bus 0 target 6 lun 0 > >sa0: <ARCHIVE Python 27871-XXX 1214> Removable Sequential Access > >SCSI-2 device > >sa0: 5.000MB/s transfers (5.000MHz, offset 8) > >no devsw (majdev=0 bootdev=0xa0300000) > >Mounting root from ufs:/dev/idad0s2a > >cd0 at ncr0 bus 0 target 5 lun 0 > >cd0: <COMPAQ CRD-254V 1.06> Removable CD-ROM SCSI-2 device > >cd0: 3.300MB/s transfers > >cd0: cd present [326227 x 2048 byte records] > > > > > -----Original Message----- > > > From: owner-freebsd-questions@FreeBSD.ORG > > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of > > > Charles Burns > > > Sent: Saturday, March 10, 2001 9:53 AM > > > To: questions@freebsd.org > > > Subject: RE: ProLiant 1500 questions... > > > > > > > > > You can increase the time that the kernel waits for SCSI > > > devices by changing > > > the line "SCSI_DELAY=" in the kernel configuration file > located in > > > /sys/i386/conf (for x86 machines anyway) > > > You might try a value of 20000 to 30000 (to and 30 seconds > > > respectively) > > > > > > > > > >From: "Andrew C. Hornback" <hornback@wireco.net> > > > >To: "Wai Chan" <waichan@hpu.edu> > > > >CC: <questions@FreeBSD.ORG> > > > >Subject: RE: ProLiant 1500 questions... > > > >Date: Fri, 9 Mar 2001 21:42:57 -0500 > > > > > > > >Wai Chan, > > > > > > > > Thanks for the info. I've redone the entire > > > installation, compiled > > > >the kernel, got all of the memory and both processors > running. I > > > >sincerely appreciate the help. > > > > > > > > But, I have run into another small problem. > > > Occasionally, on boot, > > > >it will give me the following: > > > > > > > >ida0: <Compaq SMART2/P array controller> port 0x8000-0x80ff mem > > > >0x42000000-0x43ffffff, 0x40000000-0x400000ff irq 11 at > > > device 0.0 on > > > >pci1 > > > >panic: ida_wait: timeout waiting for completion > > > >mp_lock = 00000001; cpuid = 0; lapic.id=00000000 > > > >Uptime: 0s > > > >Automatic reboot in 15 seconds - press a key on the > > > console to abort > > > > > > > > When we did the previous installation, the friend of > > > mine that set it > > > >up put in a larger pause delay earlier in the booting > process. He > > > >told me that he set it up to load and unload the > kernel four times, > > > >which would give the drives a chance to settle so that the > > > controller > > > >could be queried properly. > > > > > > > > Any ideas on remedying this problem? > > > > > > > > Thanks, > > > > > > > >--- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?026401c0aac4$e18585f0$0f00000a>