Date: Sat, 19 Jan 2002 17:28:24 -0700 From: Brett Glass <brett@lariat.org> To: "Lawrence Farr" <freebsd-hw@epcdirect.co.uk>, <hardware@FreeBSD.ORG> Subject: RE: 4.4-RELEASE hangs on boot with Promise Ultra100 TX2 installed Message-ID: <4.3.2.7.2.20020119165014.00ddc460@localhost> In-Reply-To: <002501c1a0d9$fd594d00$c80aa8c0@lfarr> References: <4.3.2.7.2.20020118183308.00db4460@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
At 04:11 AM 1/19/2002, Lawrence Farr wrote: >Have you tried the floppies from the 4.5 RC? > >Lawrence Farr >EPC Direct Limited Here's what's happening. I was having trouble finding 4.5-RC2 (Which server is it on? One thing that's missing from the FreeBSD Web pages is a roadmap showing what's on which server...) so I got floppies from the January 18 snapshot on releng4.freebsd.org. (This may in fact be RC2; I'm not sure how to tell which snapshot they have dubbed the second release candidate). After interrupting the boot process and entering "boot -h" to force the install to go headless, I got the hard drives to work on the Promise controller. Hallelujah. I checked the CVS tree to find out why. Apparently, Soren Schmidt changed the code only a couple of weeks ago. It now recognizes the latest Promise chip's identifier. It then sets a couple of bits in a register, and -- presto! -- the chip works. Those bits also had to be set in the previous release of the chip, and will probably need to be set in all future versions. Alas, the way the driver is now coded, each new version of the chip will almost certainly fail to work until the driver is updated to accommodate it. He might want to change the logic so that the register is always twiddled unless the driver sees an OLDER version of the chip. If he does this, newer Promise chips will work by default instead of failing by default. I also checked the other BSDs. The same tweak seems to have been added to OpenBSD-current and NetBSD-current, but neither has put it in a release yet. In short, neither NetBSD 1.5.2 nor OpenBSD 3.0 nor FreeBSD 4.4-RELEASE works out of the box with the Promise Ultra100 TX2 chip, even though the chip has been out nearly a year. FreeBSD 4.5-RELEASE will have the distinction of being the first BSD release that does. The only trouble is, I was hoping to deploy the machine this weekend. Alas, because this is to be a production server the people who own it do not want me to install a "release candidate" of an OS. (They're smart; they know that there are always last-minute "gotchas" and security patches, and they won't always have me there to bring in code as needed.) So, assuming that 4.5-RELEASE is put to bed on the 26th, I may have to tell them that they'll be delayed a week or more. Aargh. --Brett >> -----Original Message----- >> From: owner-freebsd-hardware@FreeBSD.ORG >> [mailto:owner-freebsd-hardware@FreeBSD.ORG] On Behalf Of Brett Glass >> Sent: 19 January 2002 01:52 >> To: hardware@FreeBSD.ORG >> Subject: 4.4-RELEASE hangs on boot with Promise Ultra100 TX2 installed >> >> >> I've been working on a server which has two EIDE chips >> installed: One on >> the motherboard (part of the Intel 440BX chipset) and a >> Promise Ultra100 TX2 >> in a PCI slot. I want to use the latter controller for the >> hard drives -- >> because it's faster -- and use the motherboard chip only for >> the CD-ROM. >> >> Trouble is, FreeBSD 4.4-RELEASE to hang in the middle of the >> bootstrap >> process whenever the Promise card is installed. Here are the >> diagnostic >> messages: >> >> \Console: serial port >> BIOS drive A: is disk0 >> BIOS drive C: is disk1 >> BIOS drive D: is disk2 >> BIOS 639kB/1047296kB available memory >> >> FreeBSD/i386 bootstrap loader, Revision 0.8 >> (root@, Sun Dec 30 00:07:57 MST 2001) >> Loading /boot/defaults/loader.conf >> /kernel text=0xf203b data=0x15694+0x10f10 >> syms=[0x4+0x1d2d0+0x4+0x22048] >> \ >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [kernel]... >> Copyright (c) 1992-2001 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.4-RELEASE #0: Sat Dec 29 23:56:12 MST 2001 >> root@:/usr/src/sys/compile/TRIB >> Timecounter "i8254" frequency 1193182 Hz >> Timecounter "TSC" frequency 534547942 Hz >> CPU: Pentium II/Pentium II Xeon/Celeron (534.55-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0x665 Stepping = 5 >> >> Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR >> ,PGE,MCA,CMOV,PA >> T,PSE36,MMX,FXSR> >> real memory = 1073479680 (1048320K bytes) >> avail memory = 1043091456 (1018644K bytes) >> pnpbios: Bad PnP BIOS data checksum >> Preloaded elf kernel "kernel" at 0xc025a000. >> Preloaded userconfig_script "/boot/kernel.conf" at 0xc025a09c. >> Pentium Pro MTRR support enabled >> Using $PIR table, 7 entries at 0xc00f2ba0 >> npx0: <math processor> on motherboard >> npx0: INT 16 interface >> pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on >> motherboard >> pci0: <PCI bus> on pcib0 >> isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0 >> isa0: <ISA bus> on isab0 >> atapci0: <Intel PIIX4 ATA33 controller> port 0xffa0-0xffaf at >> device 7.1 on pci0 >> >> ata0: at 0x1f0 irq 14 on atapci0 >> ata1: at 0x170 irq 15 on atapci0 >> pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 10 >> chip1: <Intel 82371AB Power management controller> port >> 0x440-0x44f at device 7. >> 3 on pci0 >> fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xef00-0xef3f >> mem 0xff900000-0xff9f >> ffff,0xffaf7000-0xffaf7fff irq 5 at device 12.0 on pci0 >> fxp0: Ethernet address 00:d0:b7:11:7c:38 >> inphy0: <i82555 10/100 media interface> on miibus0 >> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xee80-0xeebf >> mem 0xff800000-0xff8f >> ffff,0xffaf6000-0xffaf6fff irq 5 at device 13.0 on pci0 >> fxp1: Ethernet address 00:d0:b7:11:7c:39 >> inphy1: <i82555 10/100 media interface> on miibus1 >> inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> atapci1: <Promise TX2 ATA100 controller> port >> 0xef90-0xef9f,0xefe0-0xefe3,0xefa8 >> -0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 mem 0xffafc000-0xffafffff >> irq 11 at device 1 >> 4.0 on pci0 >> ata2: at 0xeff0 on atapci1 >> ata3: at 0xefa8 on atapci1 >> fxp2: <Intel Pro 10/100B/100+ Ethernet> port 0xed80-0xedbf >> mem 0xff700000-0xff7f >> ffff,0xffaf5000-0xffaf5fff irq 7 at device 15.0 on pci0 >> fxp2: Ethernet address 00:03:47:ad:c2:b2 >> inphy2: <i82555 10/100 media interface> on miibus2 >> inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> orm0: <Option ROMs> at iomem >> 0xc8000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcbfff,0xd >> c000-0xdffff 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 >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >> sio0: type 16550A, console >> sio1 at port 0x2f8-0x2ff irq 3 on isa0 >> sio1: type 16550A >> RTC BIOS diagnostic error 20<config_unit> >> ata1-slave: ata_command: timeout waiting for intr >> ata1-slave: identify failed >> >> [System hangs indefinitely at this point] >> >> Note that the system recognizes the Promise card but seems to >> hang right at >> the point where it would normally be probing the card for >> attached hard >> drives. >> >> If I remove all hard drives from the Promise card, the card's >> boostrap ROM >> code (which is activated before the MBR is loaded) displays >> the message >> "BIOS not installed." In this case, FreeBSD boots. >> >> Any idea what's wrong? I could venture some guesses, but I'm >> not intimately >> familiar with the IDE code. >> >> --Brett >> >> P.S. -- Just as an aside, what's the "RTC BIOS" message >> about? It doesn't >> appear to be related to this problem, but I'm curious. >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20020119165014.00ddc460>