Re: lor on boot

From: Robert Watson (rwatson_at_FreeBSD.org)
Date: 10/03/03

  • Next message: Kris Kennaway: "Re: /bin/sh terminated abnormally" 
    Date: Thu, 2 Oct 2003 20:54:06 -0400 (EDT)
To: Mark Woodson <mwoodson@sricrm.com>

    On Thu, 2 Oct 2003, Mark Woodson wrote:

    > On Thursday 02 October 2003 05:07 pm, Robert Watson wrote:
    > > On Thu, 2 Oct 2003, Mark Woodson wrote:
    > > > I'm getting a lor on a system just upgraded to sources from this
    > > > morning. The systems been running fine for the past month or so.
    > >
    > > What version of src/sys/net/netisr.c are you running with?
    >
    > * $FreeBSD: src/sys/net/netisr.c,v 1.4 2003/10/01 21:31:09 rwatson
    > Exp $
    >
    > That's what I'm showing. So it's from last night then.

    Ah. Ok, this is because the if_rl driver holds the driver mutex across a
    call to the interface input routine, resulting in holding the mutex across
    a call into the remainder of the network stack. The reason this showed up
    for you now is that I temporarily enabled direct dispatch of the isr code
    directly from the driver interrupt threads for an hour or so last night,
    and you updated during that time. I backed it out to work on two issues
    -- one the possible reordering of packets (patch now bing reviewed), and
    the other that a few drivers currently hold their lock over the call into
    the remainder of the stack, which needs to be fixed. If you cvsup, the
    problem should go away.

    Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    robert@fledge.watson.org Network Associates Laboratories

    _______________________________________________
    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: Kris Kennaway: "Re: /bin/sh terminated abnormally"

    Relevant Pages

    • Re: lor on boot
      ... this is because the if_rl driver holds the driver mutex ... > the mutex across a call into the remainder of the network stack. ...
      (freebsd-current)
    • Re: Forcedeth driver bug
      ... > Do you really know that the driver don't get the stuck packet. ... I'm not sure it's the driver's fault. ... Such an important bug in the network stack would hardly go unnoticed. ...
      (Linux-Kernel)
    • Re: Using the net on an XT: Drivers & TCP/IP
      ... LanManager network stack and is called netbind. ... driver to the TCP driver, ...
      (comp.sys.ibm.pc.classic)
    • RE: Marvell Yukon 88E8053 PCI-E Gigabit Ether net Controller
      ... I would start with updating the driver for the NIC. ... If it is a gigabit NIC you should disable some of the advanced features on ... If you can ping localhost then it sounds like your network stack is working ...
      (microsoft.public.windows.server.sbs)
    • Re: Computer Name
      ... I have a system with a device driver that is loaded before the network stack as KM suggests. ... It reads jumpers on the parallel port connector. ... Then it patches Registry IpAddress and ComputerName according to read value. ...
      (microsoft.public.windowsxp.embedded)