Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 06 May 2004 14:47:07 -0600
From:      Scott Long <scottl@freebsd.org>
To:        =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
Cc:        John Polstra <jdp@polstra.com>
Subject:   Re: em(4) problems.
Message-ID:  <409AA44B.9010404@freebsd.org>
In-Reply-To: <409A92FA.6080104@DeepCore.dk>
References:  <XFMail.20040505115403.jdp@polstra.com> <409938F7.2090603@DeepCore.dk> <409A8675.3080102@he.iki.fi> <409A92FA.6080104@DeepCore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
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.
> 

I'm looking a t a similar system right now and it definitely looks like 
an interrupt routing problem, not a driver problem.  The interesting 
thing is that (with 5.2-current as of two days ago) disabling neither
ACPI nor APIC helps.  I guess that we might want to get John Baldwin
involved.

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409AA44B.9010404>