When booting from the CD or the floppies created from the CD the following messages are shown before a complete freeze (I copied them by hand, so there may be some typos, sorry): ----- begin transcript of the messages before freeze: ... Preloaded elf kernel "kernel" at 0xc033b000. Preloaded mfs-root "/mfsroot" at 0xc033b084. Pentium Pro MTRR support enabled md0: Preloaded image </msroot> 147456 bytes at 0xc0315b98 md1: Malloc disk npx0: <math processot> on motherboard npx0: INT 16 interface pcib0: <Intel 82433LX (440LX) host to PCI bridge> on motherboard pci0: <PCI bus> on pcbi0 pcib1: <Intel 82433LX (440LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <Cirrus Logic GD5465 SVGA controller> at 0.0 irq 9 isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <Intel PIIX4 ATA33 controller> port 0xfcd0-0xfcdf at device 4.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 4.2 irq 9 chip1: <Intel 82371AB Power Management controller> port 0x8800-0x880f at device 4.3 on pci0 ----- end transcript of the messages before freeze At this point the booting freeze completely. The only way to reset the machine is plugging off the wire (power chord) and no other possibility. Fix: I do not know if I am correct, but it seems a conflict between the USB controller and the SVGA controller both trying to use irq 9. In 3.3-RELEASE at config time I was shown the PCI devices (eventhough one could not reconfigure them). This is no longer the case in the 4.0-RELEASE install. Could you please reply to my e-mail addresses above, if this pr is completely nonsense? Thanks. How-To-Repeat: Try it again, and again, and again playing with the BIOS setup does not help. The problem is the same regardless I use the floppy images or the CD-ROM to try the install/upgrade on this machine.
With this follow-up I just want to report that I have experienced exactly the same problem trying to install 4.1-RELEASE on this machine (HP-Vectra 6 / Model 7). So the problem is related to something that changed betweeen 3.x and 4.x. I read today some mails sent to freebsd-stable@FreeBSD.ORG pointing to possible problems with with the new ATA driver (see below). May be that the cause of the lock in my PR? Regards, Lazaro ---------------------- Forwarded by Lazaro Daniel Salem on 24.08.2000 13:06 --------------------------- From: John Indra <john@indocyber.com>@FreeBSD.ORG on 24.08.2000 04:15 Sent by: owner-freebsd-stable@FreeBSD.ORG To: freebsd-stable@FreeBSD.ORG cc: (bcc: Lazaro Daniel Salem) Subject: Is the ata driver buggy? [was Re: 4.1-STABLE panics on boot with Huyundai Laptop (P233)] On Wed, Aug 23, 2000 at 08:42:17PM +0200, Andreas Klemm wrote: |It turns out, that with the (new) ata driver the machine panics |and with the old (obsoleted) wd driver the Laptopmachine boots |flawlessly. Aha... here's what I found reasonable enough for the cause of lock-ups I've been having... I'm not expert enough to prove my statement, but I have a strong hunch that the ata driver is the prime suspect causing the lock-ups. When I found my machine lock-up, the harddrive LED light on all the time, and the harddrive is in condition of spinning... Never have an uptime of more than 2 days since upgrading to RELENG_4. Sigh... Like what I've describe before in my other message, the same machine that lock-up never had any unintentional reboots when running FreeBSD 3.4-RELEASE before... Regards, John Indra Sent by: owner-freebsd-stable@FreeBSD.ORG
On Thu, 24 Aug 2000 04:40:06 MST, "Lazaro D. Salem" wrote: > With this follow-up I just want to report that I have experienced > exactly the same > problem trying to install 4.1-RELEASE on this machine (HP-Vectra 6 / > Model 7). > So the problem is related to something that changed betweeen 3.x and > 4.x. You said in your original PR that you suspected a hardware IRQ conflict. What have you done to try to eliminate that as the cause of your problem? Ciao, Sheldon.
A followup to a related PR has been submitted with a work around this problem See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26686 Also related is the PR: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26736 The IRQ peculiarity mentioned here has nothing to do with the freeze. It has been suggested the culprit is the ex driver probing an installed the NE2000 NIC. Disabling the NE2000 did not not help. Physically removing the NE2000 did help and the boot completed without problems. If the ex driver is the culprit, why cannot we disabled at the kernel configuration stage? This was possible to do in the 3.x releases, but is not possible to do with the 4.x releases. Cheers
State Changed From-To: open->closed Workaround for related problem discussed in bin/26686.