From owner-freebsd-current@FreeBSD.ORG Thu May 6 13:23:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD77616A4CF for ; Thu, 6 May 2004 13:23:22 -0700 (PDT) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA6BD43D46 for ; Thu, 6 May 2004 13:23:21 -0700 (PDT) (envelope-from andre@freebsd.org) Received: (qmail 79334 invoked from network); 6 May 2004 20:23:21 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 6 May 2004 20:23:21 -0000 Message-ID: <409A9EB7.D0D2AC4A@freebsd.org> Date: Thu, 06 May 2004 22:23:19 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt , freebsd-net@freebsd.org, freebsd-current@freebsd.org, John Polstra References: <409938F7.2090603@DeepCore.dk> <409A8675.3080102@he.iki.fi> <409A92FA.6080104@DeepCore.dk> <409A9458.D73EBB18@freebsd.org> <409A96E7.7020601@DeepCore.dk> <409A9936.78CC31A0@freebsd.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: em(4) problems. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2004 20:23:23 -0000 Andre Oppermann wrote: > > Søren Schmidt wrote: > > > > Andre Oppermann wrote: > > > Søren Schmidt wrote: > > > > > >>Petri Helenius wrote: > > >> > > >>>I´m highly confident that this is a case of integrated "CSA" ethernet > > >>>with broken BIOS. I suspect you get an message about that when booting. > > >> > > >>Nope. no messages to that effect, oh and it works in windows(tm)... > > >> > > >>The last thing I see if I try to use em0 is: > > >>em0: Link is up 100 Mbps Full Duplex > > >>and then the system locks up hard. > > > > > > What MIIPHY does the card have? > > > > No idea, builtin of sorts, there is no mention of it in the probe, and > > no HW to see on the boards. I have two different boards with these on > > them both show the problem... > > There must be some sort of MII message in dmesg. I'm wrong. em uses built in PHYs indeed. Which also means link_state doesn't work there... Check out the function em_local_timer() in sys/dev/em/if_em.c and maybe you get some more insight by enabling if debugging or putting some printf's in there. What makes me a little bit wondering is the direct use of printf() instead of dev_printf(). I don't know what the locking implications are if any. -- Andre