From owner-freebsd-stable Mon Jan 28 11:56:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-168-72.hispeed.ch [217.162.168.72]) by hub.freebsd.org (Postfix) with ESMTP id 81D4B37B420 for ; Mon, 28 Jan 2002 11:56:24 -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 g0SJuJT05870 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Mon, 28 Jan 2002 20:56:22 +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 g0SJuJp05869; Mon, 28 Jan 2002 20:56:19 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Mon, 28 Jan 2002 20:56:19 +0100 (CET) Message-Id: <200201281956.g0SJuJp05869@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery To: freebsd-stable@freebsd.org Subject: 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 Serwus 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. When I connect instead to the xl0 card in the same machine, I have no problems at all. I'm just partially looking into this now, if someone else wants to try this and see if I'm full of hot air, or what. The first time I tried this after going multi-user with both the ep0 and xl0 card installed, I think the machine froze, but an attempt to switch consoles (Alt-F?) resulted in the block cursor disappearing, but nothing more. Scroll lock and such keys toggled the LEDs, but I couldn't switch consoles. I could get into the debugger, from which I *could* switch consoles (which I've never tried in normal operation so I don't know if it means anything), but upon `c'ontinuing, things were wedged again. I'm pretty sure that I was able to break into the debugger when I set things up to run dhclient on ep0 as part of the boot, which otherwise seemed to hang forever. Then I pulled out the xl0 card. After going multi-user, I had no problems the one time I used dhclient to configure ep0. Honest. But when I tried to use an identical config file as part of the boot process, whammo -- wedge city. Today I thought I'd try a different machine, and a different slot to boot (same machine model, though, which a friend was eager to throw away though I've had no unresolvable problems so far). The same wedges at boot happen, and I can't get into the debugger (but it's also a different kernel which *should* have DDB and should be otherwise very similar). What I still haven't done is to swap the card into a completely different make of machine and see if I get the same wedges, or if it's a problem with the one particular old 1994-vintage machine I'm using (Digital Venturis 575). I won't rule out a 3C509-card- specific hardware problem too, given that it's an ISA card and my friend who gave it plus the two Digital PCs to me has had much unluck with hardware. Anyway, I just thought that I'd mention that under a fresh -stable I'm seeing this problem, and I'll be looking more at it (at least, juggling hardware) to see if it's a Real Problem or just some odd hardware quirk. More later, like anyone cares thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message