On Fri, Apr 03, 2009 at 09:34:09PM +0100, ian j hart wrote:
> On Tuesday 31 March 2009 04:52:54 Steve Wills wrote:
> > Hi,
> >
> > On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote:
> > > On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
> > >> Hi,
> > >>
> > >> I upgraded my 7.1-RELEASE
On Tuesday 31 March 2009 04:52:54 Steve Wills wrote:
> Hi,
>
> On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote:
> > On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
> >> Hi,
> >>
> >> I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
> >> booting, re0 works for only a s
Hi,
On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote:
On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
Hi,
I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
booting, re0 works for only a short time, then gives "re0: PHY read
failed" over and over. Does anyone have
On Mon, Mar 09, 2009 at 12:56:13PM +0900, Pyun YongHyeon wrote:
> On Sun, Mar 08, 2009 at 09:52:19PM -0400, Steve Wills wrote:
> > Hi,
> >
> > Sorry for the late reply.
> >
> > On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote:
> > >Ok, when you plug UTP cable can you see "re0: link state changed
On Sun, Mar 08, 2009 at 09:52:19PM -0400, Steve Wills wrote:
> Hi,
>
> Sorry for the late reply.
>
> On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote:
> >Ok, when you plug UTP cable can you see "re0: link state changed to
> >UP" in dmesg output? Or if you unplug the cable, you should see
> >"re0:
Hi,
Sorry for the late reply.
On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote:
Ok, when you plug UTP cable can you see "re0: link state changed to
UP" in dmesg output? Or if you unplug the cable, you should see
"re0: link state changed to DOWN"(With "tail -f /var/log/message",
you can easily c
On Thu, Feb 26, 2009 at 12:36:48AM -0500, Steve Wills wrote:
> On Feb 25, 2009, at 11:27 PM, Pyun YongHyeon wrote:
>
> >On Wed, Feb 25, 2009 at 11:15:38PM -0500, Steve Wills wrote:
> >
> >[...]
> >>>I guess re(4) thinks it lost established link. How about unplug and
> >>>then replug UTP cable? Wou
On Wed, Feb 25, 2009 at 11:06:45PM -0600, Matthew D. Fuller wrote:
> On Wed, Feb 25, 2009 at 10:47:07PM -0500 I heard the voice of
> Steve Wills, and lo! it spake thus:
> >
> > re0: > Gigabit Ethernet> port 0x7e00-0x7eff mem 0xfd3ff000-0xfd3f,
> > 0xfd3f8000-0xfd3fbfff irq 16 at device 0.0 o
On Feb 25, 2009, at 11:27 PM, Pyun YongHyeon wrote:
On Wed, Feb 25, 2009 at 11:15:38PM -0500, Steve Wills wrote:
[...]
I guess re(4) thinks it lost established link. How about unplug and
then replug UTP cable? Would you show me "devinfo -rv | grep phy"?
rgephy0 pnpinfo oui=0x732 model=0x11 r
On Wed, Feb 25, 2009 at 10:47:07PM -0500 I heard the voice of
Steve Wills, and lo! it spake thus:
>
> re0: Gigabit Ethernet> port 0x7e00-0x7eff mem 0xfd3ff000-0xfd3f,
> 0xfd3f8000-0xfd3fbfff irq 16 at device 0.0 on pci8
> re0: Chip rev. 0x2800
> re0: MAC rev. 0x0010
For a data point
On Wed, Feb 25, 2009 at 11:15:38PM -0500, Steve Wills wrote:
[...]
> >I guess re(4) thinks it lost established link. How about unplug and
> >then replug UTP cable? Would you show me "devinfo -rv | grep phy"?
>
> rgephy0 pnpinfo oui=0x732 model=0x11 rev=0x2 at phyno=1
>
And unpluging/repluging d
On Feb 25, 2009, at 11:10 PM, Pyun YongHyeon wrote:
I get 3 link state DOWN/UP notices when DHCP client starts. It works
That's normal(Technically this is not correct behavior but it's the
way how it was implemented in driver).
Ok. Not a huge deal, but would be nice to fix, of course.
for e
On Wed, Feb 25, 2009 at 10:47:07PM -0500, Steve Wills wrote:
> On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote:
> >I need more information for your hardware revision.
> >Would you show me dmesg output and revision number of if_re.c?
>
> I assume you only need the re0 related output. If you need
On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote:
I need more information for your hardware revision.
Would you show me dmesg output and revision number of if_re.c?
I assume you only need the re0 related output. If you need the full
dmesg, let me know.
re0: Gigabit Ethernet> port 0x7e00-0x
On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
> Hi,
>
> I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
> booting, re0 works for only a short time, then gives "re0: PHY read
> failed" over and over. Does anyone have a suggestion on how to debug?
>
I need more
Hi,
On Wed, Feb 25, 2009 at 09:22:39AM +0100, Oliver Brandmueller wrote:
> On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
> > I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
> > booting, re0 works for only a short time, then gives "re0: PHY read
> > failed" over
Hi,
On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote:
> I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
> booting, re0 works for only a short time, then gives "re0: PHY read
> failed" over and over. Does anyone have a suggestion on how to debug?
The Patch from <200
Hi,
I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after
booting, re0 works for only a short time, then gives "re0: PHY read
failed" over and over. Does anyone have a suggestion on how to debug?
Thanks,
Steve
___
freebsd-stable@freebsd
18 matches
Mail list logo
