Date: Thu, 06 May 2004 22:23:19 +0200 From: Andre Oppermann <andre@freebsd.org> To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@DeepCore.dk>, freebsd-net@freebsd.org, freebsd-current@freebsd.org, John Polstra <jdp@polstra.com> Subject: Re: em(4) problems. Message-ID: <409A9EB7.D0D2AC4A@freebsd.org> References: <XFMail.20040505115403.jdp@polstra.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409A9EB7.D0D2AC4A>