Date: Sat, 17 Oct 1998 02:46:56 -0500 (CDT) From: Igor Roshchin <igor@physics.uiuc.edu> To: andymac@bullseye.apana.org.au (Andrew MacIntyre) Cc: stable@FreeBSD.ORG Subject: Re: Annoying >2.2.5 oddity on reboot. Message-ID: <199810170746.CAA18354@alecto.physics.uiuc.edu> In-Reply-To: <Pine.OS2.3.95.981017091545.181B-100000@CENTRAL> from "Andrew MacIntyre" at "Oct 17, 1998 9:51: 5 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > I had an Intel EtherExpress/16 (ie0 driver) installed when I did the > initial install (2.2.7-RELEASE, after several of the initial problems were > fixed), and I had no problems with doing a passive FTP install. The > intitial reboot after FTP went OK - at least there were no error messages. > > At that point I left it for a while, and came back some time later to do > the package installation. > > Despite the fact the ifconfig reported the interface up, I could not > access the network - eventually it timed out (in sendto??? vague > recollection here). Not to mention the fact it worked fine during the > install. > > A subsequent shutdown -r hung immediately after the "going down" message, > very similar to your symptoms, and required a reset to restart. > > I found an Intel EtherExpress Pro/10 ISA card (ex driver), and swapped it > for the EE16, mainly to get rid of some problems the ie driver was > reporting (card/packet errors of some sort). Same thing - detected fine & > ifconfig'ed, but no viable connection. I don't know if this is relevant, but I observed similar symptoms when the ethernet card had either a wrong memory address setting (it was for the smc and 3com card - the addresses like d4000, cc000, etc.. ) or the IRQ was conflicting with some other device (e.g. withthe second com-port) I don't about your particular card - but you can try to run the dos configuration utility for it, check the parameters (IRQ, port address, memory address) and then compare to those which would show up when you start kernel with -c option. Sorry, if you already know that. > > I can't recall the exact process that followed, but I did find that > building a custom kernel produced weird results:- > certain combinations of the ie and ex drivers along with other kernel > settings (no of users I think) produced kernels that would work with one > of the drivers if the other driver was present but disabled. Also > some kernels had the rebooting hang and others were OK. In my case some other driver (ie0) was somewhat detecting the card, but was not doing anything else to it. (In general, ie very often recognizes not its cards) HOpe, this helps. Igor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810170746.CAA18354>