Re: em(4) problems.

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 05/07/04

  • Next message: John Baldwin: "Re: spin lock sleepq chain held by 0xc0fc3540 for > 5 seconds"
    To: freebsd-current@FreeBSD.org
    Date: Fri, 7 May 2004 14:01:17 -0400
    
    

    On Thursday 06 May 2004 04:47 pm, Scott Long 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.
    >
    > 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.

    Ugh, does the interrupt storm stuff in -current help at all?

    -- 
    John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
    "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: John Baldwin: "Re: spin lock sleepq chain held by 0xc0fc3540 for > 5 seconds"

    Relevant Pages

    • Re: em(4) problems.
      ... I suspect you get an message about that when booting. ... > and then the system locks up hard. ... an interrupt routing problem, not a driver problem. ...
      (freebsd-current)
    • Re: em(4) problems.
      ... I suspect you get an message about that when booting. ... > and then the system locks up hard. ... an interrupt routing problem, not a driver problem. ...
      (freebsd-net)
    • Re: em(4) problems.
      ... On Thursday 06 May 2004 04:47 pm, Scott Long wrote: ... > Søren Schmidt wrote: ... >> and then the system locks up hard. ... > an interrupt routing problem, ...
      (freebsd-net)
    • Re: em(4) problems.
      ... Andre Oppermann wrote: ... > Søren Schmidt wrote: ... >>and then the system locks up hard. ... To unsubscribe, ...
      (freebsd-current)
    • Re: em(4) problems.
      ... Andre Oppermann wrote: ... > Søren Schmidt wrote: ... >>and then the system locks up hard. ... To unsubscribe, ...
      (freebsd-net)