The system starts to boot, and hangs after the 3c509 attach message shows up. From: Bruce Cole <bcole@cisco.com> Subject: Re: 386bsd hint? Date: Wed, 26 Apr 1995 14:26:55 -0700 To: Paul Traina <pst@cisco.com> cc: Bruce Cole <bcole@cisco.com> > Isn't boot -c wonderful? :-) > What has likely occured is that some other card has wedged the controller > first. I would use boot -c and disable anything that's probing at 0x300 or > on irq 10, leaving just the 3c509 enabled. I had tried disabling all the ones that came after it. Just tried it more completely like you suggested, and still no luck. Then I tried a binary search on getting rid of drivers... Found that it doesn't hang if I disable *both* eg0 and lnc0, but not just one or the other. Either I've got a time dependency or something weird is going on... Fix: Well, it's pretty clear that the probe routines for the eg0 and lnc0 drivers are hosing over the 3c509. I would suggest changing the order of the probes in the ethernet driver section, since the ep driver is in much greater common use than the eg and lnc drivers, and if the ep driver gets attached first, the probes for the eg and lnc drivers will never be executed. How-To-Repeat: Boot a generic kernel on Bruce's box.
Responsible Changed From-To: freebsd-bugs->pst pst's bug. Probably stale.
State Changed From-To: open->closed Stale bug.