From owner-freebsd-stable Wed Feb 6 11:24: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-168-252.hispeed.ch [217.162.168.252]) by hub.freebsd.org (Postfix) with ESMTP id DE11137B425 for ; Wed, 6 Feb 2002 11:23:58 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g16J8Sb00712 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Wed, 6 Feb 2002 20:08:32 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g16J8SO00711; Wed, 6 Feb 2002 20:08:28 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Wed, 6 Feb 2002 20:08:28 +0100 (CET) Message-Id: <200202061908.g16J8SO00711@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery To: freebsd-stable@freebsd.org Subject: Re: Weird wedge with ep0 ethernet and dhclient Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: Mountain Informatik AG, Zuerich X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy! I wrote on %.3s, %lld Sep 1993 > > I've been semi-consistently having my machine freeze up in a weird > > way when attempting to run /sbin/dhclient when the Cabal Modem is > > connected to an ep0 3Com 3C509 card. > [...] > up with anything more useful and concrete. And I'll also see how a > Different OS handles this card with the ISC dhclient. more l8r d00dz This will probably be the last I say about this stupid card. However: It seems that I can't get into the debugger when the machine freezes at multi-user startup no matter what I do. It also seems that even when FreeBSD wedges, I can boot into NetBSD, which somehow appears to initialize the card so that it can run the dhclient program without problems. After that, I can usually reboot into FreeBSD and it Just Works. Usually, but not always. Usually after I've used the card successfully with FreeBSD, I can power-down the machine and later boot without problems. Except once when the power cord proper was disconnected for some time. Both FreeBSD-stable and FreeBSD-current suffer this problem at boot. I think I couldn't get dhclient to work after boot with -current, but I could be remembering wrong. I dunno if it's Useful Information that NetBSD boots and runs dhclient with the 3C509 card immediately after FreeBSD wedges and that following that, FreeBSD works, for a while, usually. Unfortunately, since normally syslogd starts after dhclient, none of the info messages get logged, and it's not immediately obvious where it freezes, *if* I wanted to put more work into this rather than just tossing the 3C509 out the window and using a different card. That's enough about that. barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message