4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)
On Mar 2, 4:09am, Don Lewis wrote: } Subject: current hangs during boot if ET/5025-16 card is installed } } I happened to try to install 4.0-CURRENT on a box that has an } Emerging Technologies ET/5025-16 ISA card installed and found that } the kernel wedges during boot. It hangs hard and won't respond to } anything except the reset switch. The motherboard is an Asus P3B-F } and I believe I have the BIOS propery configured with the correct } settings to match the IRQ and memory addresses used by the ET card. } } I also discovered that older versions of -CURRENT will boot correctly } on this box. I did a binary search on the -CURRENT snapshots and found } that the floppies from the January 12th and earlier snapshots boot, } while the floppies from the January 14th and later snapshots hang. By adding a whole bunch of printf statements to the code, I was able to track this problem to ex_isa_identify(). The ET card is jumpered to I/O address 0x240, and it appears to consume 32 bytes starting at this address. When the ioport loop in ex_isa_identify() gets to 0x250, look_for_card() appears to wedge. I don't see how that can happen unless the CPU gets stuck in inb(). I haven't looked at ISA hardware in ages, can an ISA I/O read really hang forever? What really sucks is that there is no way to disable the ex driver at boot time, so the standard install floppies can no longer be used to boot a box that contains one of these ET cards. Should the ex driver be doing all this stuff at identify time, or was the older method of doing this at probe time more correct? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)
On Mar 3, 11:16am, "Matthew N. Dodd" wrote: } Subject: Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs du } On Fri, 3 Mar 2000, Don Lewis wrote: } What really sucks is that there is no way to disable the ex driver } at boot time, so the standard install floppies can no longer be used } to boot a box that contains one of these ET cards. } } Should the ex driver be doing all this stuff at identify time, or was } the older method of doing this at probe time more correct? } } Thats really the only place for such a routine. What needs to happen is } for if_ex to a little more selective about which addresses it } probes. While it is using a non-destructive probe (see } look_for_card()) it should also use the resource manager to check and see } if a port is assigned before it does anything else. Unfortunately the GENERIC kernel doesn't have a driver that could claim the ET card. Also ex_isa_identify() is called before the legacy ISA probes are done. IMHO, the best way to fix this would be for the dual-mode PnP/legacy drivers to identify any cards in PnP mode, then do legacy ISA probes using the old hard-wired port numbers, where legacy ISA probes can be controlled by userconfig. This is really ugly, but then we all agree that ISA sucks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
