Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Dec 2002 14:10:28 -0500
From:      Mike Tancsa <mike@sentex.net>
To:        Thomas Nystrom <thn@saeab.se>
Cc:        stable@FreeBSD.ORG
Subject:   Re: Fix for hanging of vr interface (Rhine Ethernet)
Message-ID:  <5.2.0.9.0.20021223134745.04ec8038@marble.sentex.ca>
In-Reply-To: <3E075744.76187334@saeab.se>
References:  <5.2.0.9.0.20021220151835.03a72a48@marble.sentex.ca> <5.2.0.9.0.20021223102240.07303e80@marble.sentex.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
At 07:34 PM 23/12/2002 +0100, Thomas Nystrom wrote:
>Ok, I have found that the board should have a VT6103 PHY-chip. There is no
>specific support for that chip in FreeBSD and the default PHY driver is
>used instead.

Hi,
By no specific driver, does that mean none is needed ? Or just that nothing 
is available now, so the lowest common denominator is used.  Basically, I 
am asking, is this "a bad thing" ?

> > Also, while pushing the board network wise, I got a
> > vr0: Using force reset command.
> > Is this normal ?
>
>Did you get some other message before or after the 'force reset' message?

Nothing else that I saw.


>Did the interface work after the forced reset?

Yes, it seemed to.  Is there any extra debugging info I can provide ?

         ---Mike 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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