RE: 6.0 BETA1: "nve0: device timeout(..)" on amd64 with nForce4 ethernet

From: alan bryan (alanbryan1234_at_yahoo.com)
Date: 07/25/05

  • Next message: Thierry Herbelot: "Current : panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_subr.c:2114" 
    Date: Sun, 24 Jul 2005 21:32:44 -0700 (PDT)
To: dandee@volny.cz, 'Paul Richards' <paul.richards@gmail.com>, freebsd-current@freebsd.org

    Well, it's not perfect on x86 either. I've got a
    Shuttle Small Form Factor Desktop SN25P with an
    Athlon64 but running i386 kernel with the onboard
    ethernet. Under 5.4 it didn't work at all but now on
    6.0beta1 it works for a while and then I get the nve0:
    device timeout(..) errors that repeat forever. If I
    try to ping something there's an error about a buffer
    or something, can't remember the exact syntax.

    Is there an easy way to reload the driver without
    rebooting? I tried ifconfig down and netstart but I
    guess it's dead more low down in the system than that.

    Also, I am running 4BSD right now and it may die once
    a day to several times per day but I can't remember it
    dying when I was testing ULE for a while so I may
    switch back to ULE for a bit and report back if that
    has any positive effect.

    >From my /var/log/messages
    Jul 24 21:27:46 alan kernel: nve0: link state changed
    to DOWN
    Jul 24 21:27:48 alan kernel: nve0: link state changed
    to UP
    Jul 24 21:29:09 alan kernel: nve0: device timeout (4)
    Jul 24 21:29:09 alan kernel: nve0: link state changed
    to DOWN
    Jul 24 21:29:11 alan kernel: nve0: link state changed
    to UP
    Jul 24 21:30:21 alan kernel: nve0: device timeout (4)
    Jul 24 21:30:21 alan kernel: nve0: link state changed
    to DOWN
    Jul 24 21:30:23 alan kernel: nve0: link state changed
    to UP
    Jul 24 21:31:08 alan kernel: nve0: device timeout (4)

    So after a while and tons of these it eventually dies.

    --Alan

    --- Daniel Dvorak <dandee@hellteam.net> wrote:

    > Hi all,
    >
    > I have the same configuration and I can confirm
    > this.
    > Sorry for no details. I do not know how to find
    > them.
    > In /var/log/messages, there is only nve0:device
    > timout.
    >
    > Dan
    >
    > -----Original Message-----
    > From: owner-freebsd-current@freebsd.org
    > [mailto:owner-freebsd-current@freebsd.org] On Behalf
    > Of Paul Richards
    > Sent: Sunday, July 24, 2005 2:44 PM
    > To: freebsd-current@freebsd.org
    > Subject: 6.0 BETA1: "nve0: device timeout(..)" on
    > amd64 with nForce4
    > ethernet
    >
    > Hi,
    > I have an amd64 machine with onboard nForce4
    > ethernet. When I attempt
    > to use the interface nve0 I get no data transfer and
    > errors reporting:
    > nve0: device timeout(..)
    >
    > I reported this same problem a couple of months ago
    > but nobody seemed
    > to know of a solution. I decided to try the 6.0
    > BETA1 release to see
    > if it had been fixed but unfortunately the answer is
    > no.
    >
    > I hope this report is helpful in someway,
    >
    >
    > --
    > Paul Richards
    > _______________________________________________
    > 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"
    >
    > _______________________________________________
    > 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"
    >

    __________________________________________________
    Do You Yahoo!?
    Tired of spam? Yahoo! Mail has the best spam protection around
    http://mail.yahoo.com
    _______________________________________________
    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: Thierry Herbelot: "Current : panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_subr.c:2114"