Re: NVE

From: Maxime Henrion (mux_at_FreeBSD.org)
Date: 07/27/05

  • Next message: Kövesdán Gábor: "Re: NVE"
    Date: Wed, 27 Jul 2005 15:08:05 +0200
    To: K?vesd?n G?bor <gabor.kovesdan@t-hosting.hu>
    
    

    K?vesd?n G?bor wrote:
    > Maxime Henrion wrote:
    >
    > >K??vesd??n G??bor wrote:
    > >
    > >
    > >>yerenkow@uct.ua wrote:
    > >>
    > >>
    > >>
    > >>>Hello list users.
    > >>>
    > >>>I have bougth motherboard Epox 8kda3J, which has NV ethernet adapter
    > >>>MCP7.
    > >>>My system was FreeBSD 5.4 and i found NV MCP Driver for FreeBSD here:
    > >>>http://www.onthenet.com.au/~q/nvnet/
    > >>>Ok, I got it, install and kldloaded; then ifconfig tells me that my
    > >>>ethernet card see cable, but I started to receive these messages:
    > >>>device nv0 timeout(5), with ascending numbers;
    > >>>
    > >>>Ok, I get Freebsd 6.0-BETA1, where driver pre-built in kernel.
    > >>>The different were only interface name, whic is nve0, but also shows
    > >>>timeouts.
    > >>>
    > >>>This was tested with cross cable between two pcs, and with normal cable
    > >>>pc-switch.
    > >>>I tried to turn on debugging nve driver, but then system just hangs.
    > >>>
    > >>>Can anyone comment?
    > >>>
    > >>>
    > >>>
    > >>>
    > >>>
    > >>Hi,
    > >>
    > >>I have the same network interface on Asus A8N-SLI Deluxe. That nve
    > >>driver in the FreeBSD6.0-BETA1
    > >>is very poor. Sometimes it causes a kernel panic, sometimes it hangs
    > >>with device timeouts. I've sent a PR
    > >>about that kernel panic with trace included but nobody has taken care of
    > >>that yet.
    > >>
    > >>
    > >
    > >
    > >I have committed a fix to the nve(4) driver very recently in HEAD. I
    > >don't think it could fix the device timeout issues, however, it might
    > >help with the panics you were getting. If you could give this fix a
    > >try, I'd be grateful.
    > >
    > >Cheers,
    > >Maxime
    > >
    > Ok, I'll. If it seems okay, is it possible to commit it to RELENG_6?

    That's the plan. I'm actually waiting for feedback to know whether this
    helps make things better or not. I'll ask re@ for permission to MFC it
    once I know it's good (I have no nve(4) hardware myself).

    Cheers,
    Maxime
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: Kövesdán Gábor: "Re: NVE"

    Relevant Pages

    • Re: dump/restore corrupted filesystems
      ... and fsck can't fix the damage. ... That might be worth filing a PR for, especially the panics. ... If dump dies on ... So if any of these is corrupt, ...
      (freebsd-questions)
    • Re: dump/restore corrupted filesystems
      ... and fsck can't fix the damage. ... That might be worth filing a PR for, especially the panics. ... So if any of these is corrupt, ...
      (freebsd-questions)
    • Patch: sym(4) "VTOBUS FAILED" panics on amd64, amd64/89550
      ... This fixes the sym "VTOBUS FAILED" panics that I got consistently on ... fix so that it is supported, or having a note in the hardware guide. ...
      (freebsd-stable)
    • Re: dump/restore corrupted filesystems
      ... and fsck can't fix the damage. ... That might be worth filing a PR for, especially the panics. ... failed: Bad file descriptor ...
      (freebsd-questions)
    • Re: Random panics with 5.3-REL, SMP
      ... On Tuesday 23 November 2004 01:22 pm, Hogan Whittall wrote: ... so I swapped out the wireless card with one supported ... > I'm still getting random panics, ... > has experienced something like this before and knows of a fix, ...
      (freebsd-current)