Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 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 information for your hardware revision. Would you show me dmesg output and revision number of if_re.c? For the record, and if anyone else is having this issue, SVN rev 190587 fixes this. Thanks for taking care of it! Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org This seems to fix it for me too. At least I've had no messages for the last hour (usually 6-10/hour). Good work, now let's get this in 7.2. Already MFCed to RELENG_7. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 short time, then gives re0: PHY read failed over and over. Does anyone have a suggestion on how to debug? I need more information for your hardware revision. Would you show me dmesg output and revision number of if_re.c? For the record, and if anyone else is having this issue, SVN rev 190587 fixes this. Thanks for taking care of it! Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org This seems to fix it for me too. At least I've had no messages for the last hour (usually 6-10/hour). Good work, now let's get this in 7.2. -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 a suggestion on how to debug? I need more information for your hardware revision. Would you show me dmesg output and revision number of if_re.c? For the record, and if anyone else is having this issue, SVN rev 190587 fixes this. Thanks for taking care of it! Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 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 check this.) Nope. If this is not the case something is wrong on RTL8168D. Since you've said re0 works for a short time, can you see re0: link state changed to DOWN on your dmesg output right before seeing re0: PHY read failed message? After boot and DHCP, it works for about a minute, then I see PHY read failed for a few seconds, network continues to work, then I see link state changed to DOWN, network stops working and frequency of read failed message increases. Unplugging the cable and plugging it back in doesn't change anything or cause the system to log any messages beyond PHY read failed. I've also attached patch which may apply to your case. Would you give it spin? Note, the patch was generated against CURRENT, so you should use re(4) in CURRENT. Just save your old re(4)/rl(4) files and download if_re.c, if_rl.c and if_rlreg.h from CURRENT and apply the patch. re.RTL8168D.patch Unfortunately, for me, this patch doesn't change things. Ok, please try again with attached patch. Any progress here? I've checked changes made in RELENG7 but I failed to see what revision broke RTL8168D support. Can you narrow down which revision broke RTL8168D support if previous patch have no effect? Index: sys/dev/re/if_re.c === --- sys/dev/re/if_re.c(revision 189551) +++ sys/dev/re/if_re.c(working copy) @@ -1266,6 +1266,8 @@ /* FALLTHROUGH */ case RL_HWREV_8168CP: case RL_HWREV_8168D: + if (hw_rev-rl_rev == RL_HWREV_8168D) + sc-rl_flags |= 0x1; sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP; /* @@ -2061,6 +2063,8 @@ RL_LOCK_ASSERT(sc); + if ((sc-rl_flags 0x1) != 0) + re_miibus_writereg(sc-rl_dev, 1, 0x1f, 0); mii = device_get_softc(sc-rl_miibus); mii_tick(mii); if ((sc-rl_flags RL_FLAG_LINK) == 0) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 check this.) Nope. If this is not the case something is wrong on RTL8168D. Since you've said re0 works for a short time, can you see re0: link state changed to DOWN on your dmesg output right before seeing re0: PHY read failed message? After boot and DHCP, it works for about a minute, then I see PHY read failed for a few seconds, network continues to work, then I see link state changed to DOWN, network stops working and frequency of read failed message increases. Unplugging the cable and plugging it back in doesn't change anything or cause the system to log any messages beyond PHY read failed. I've also attached patch which may apply to your case. Would you give it spin? Note, the patch was generated against CURRENT, so you should use re(4) in CURRENT. Just save your old re(4)/rl(4) files and download if_re.c, if_rl.c and if_rlreg.h from CURRENT and apply the patch. re.RTL8168D.patch Unfortunately, for me, this patch doesn't change things. Thanks, Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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: link state changed to DOWN(With tail -f /var/log/message, you can easily check this.) Nope. If this is not the case something is wrong on RTL8168D. Since you've said re0 works for a short time, can you see re0: link state changed to DOWN on your dmesg output right before seeing re0: PHY read failed message? After boot and DHCP, it works for about a minute, then I see PHY read failed for a few seconds, network continues to work, then I see link state changed to DOWN, network stops working and frequency of read failed message increases. Unplugging the cable and plugging it back in doesn't change anything or cause the system to log any messages beyond PHY read failed. I've also attached patch which may apply to your case. Would you give it spin? Note, the patch was generated against CURRENT, so you should use re(4) in CURRENT. Just save your old re(4)/rl(4) files and download if_re.c, if_rl.c and if_rlreg.h from CURRENT and apply the patch. re.RTL8168D.patch Unfortunately, for me, this patch doesn't change things. Ok, please try again with attached patch. Index: sys/dev/re/if_re.c === --- sys/dev/re/if_re.c (revision 189551) +++ sys/dev/re/if_re.c (working copy) @@ -1266,6 +1266,8 @@ /* FALLTHROUGH */ case RL_HWREV_8168CP: case RL_HWREV_8168D: + if (hw_rev-rl_rev == RL_HWREV_8168D) + sc-rl_flags |= 0x1; sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP; /* @@ -2061,6 +2063,8 @@ RL_LOCK_ASSERT(sc); + if ((sc-rl_flags 0x1) != 0) + re_miibus_writereg(sc-rl_dev, 1, 0x1f, 0); mii = device_get_softc(sc-rl_miibus); mii_tick(mii); if ((sc-rl_flags RL_FLAG_LINK) == 0) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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? Would you show me devinfo -rv | grep phy?
rgephy0 pnpinfo oui=0x732 model=0x11 rev=0x2 at phyno=1
And unpluging/repluging didn't help?
No, didn't help.
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 check this.)
If this is not the case something is wrong on RTL8168D. Since
you've said re0 works for a short time, can you see re0: link
state changed to DOWN on your dmesg output right before seeing
re0: PHY read failed message?
I've also attached patch which may apply to your case. Would you
give it spin? Note, the patch was generated against CURRENT, so
you should use re(4) in CURRENT. Just save your old re(4)/rl(4)
files and download if_re.c, if_rl.c and if_rlreg.h from CURRENT
and apply the patch.
Index: sys/dev/re/if_re.c
===
--- sys/dev/re/if_re.c (revision 189300)
+++ sys/dev/re/if_re.c (working copy)
@@ -1266,6 +1266,8 @@
/* FALLTHROUGH */
case RL_HWREV_8168CP:
case RL_HWREV_8168D:
+ if (hw_rev-rl_rev == RL_HWREV_8168D)
+ sc-rl_flags |= RL_FLAG_PMCH;
sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR |
RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP;
/*
@@ -1361,7 +1363,8 @@
CSR_WRITE_1(sc, RL_GPIO,
CSR_READ_1(sc, RL_GPIO) ~0x01);
}
-
+ if ((sc-rl_flags RL_FLAG_PMCH) != 0)
+ CSR_WRITE_1(sc, RL_PMCH, CSR_READ_1(sc, RL_PMCH) | 0x80);
/* Take PHY out of power down mode. */
if ((sc-rl_flags RL_FLAG_PHYWAKE) != 0) {
re_gmii_writereg(dev, 1, 0x1f, 0);
@@ -2982,6 +2985,8 @@
CSR_WRITE_1(sc, RL_GPIO,
CSR_READ_1(sc, RL_GPIO) | 0x01);
}
+ if ((sc-rl_flags RL_FLAG_PMCH) != 0)
+ CSR_WRITE_1(sc, RL_PMCH, CSR_READ_1(sc, RL_PMCH) | 0x80);
/* reinitialize interface if necessary */
if (ifp-if_flags IFF_UP)
@@ -3043,6 +3048,8 @@
CSR_WRITE_1(sc, RL_GPIO,
CSR_READ_1(sc, RL_GPIO) ~0x01);
}
+ if ((sc-rl_flags RL_FLAG_PMCH) != 0)
+ CSR_WRITE_1(sc, RL_PMCH, CSR_READ_1(sc, RL_PMCH) ~0x80);
if ((ifp-if_capenable IFCAP_WOL) != 0
(sc-rl_flags RL_FLAG_WOLRXENB) != 0)
CSR_WRITE_1(sc, RL_COMMAND, RL_CMD_RX_ENB);
Index: sys/pci/if_rlreg.h
===
--- sys/pci/if_rlreg.h (revision 189300)
+++ sys/pci/if_rlreg.h (working copy)
@@ -133,6 +133,7 @@
#define RL_GMEDIASTAT 0x006C /* 8 bits */
#define RL_MACDBG 0x006D /* 8 bits, 8168C SPIN2 only */
#define RL_GPIO 0x006E /* 8 bits, 8168C SPIN2 only */
+#define RL_PMCH 0x006F /* 8 bits, 8168D only */
#define RL_MAXRXPKTLEN 0x00DA /* 16 bits, chip multiplies by 8 */
#define RL_GTXSTART 0x0038 /* 8 bits */
@@ -880,6 +881,7 @@
int rl_txstart;
uint32_t rl_flags;
#define RL_FLAG_MSI 0x0001
+#define RL_FLAG_PMCH 0x0002
#define RL_FLAG_PHYWAKE 0x0008
#define RL_FLAG_NOJUMBO 0x0010
#define RL_FLAG_PAR 0x0020
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 20090213113955.ge12...@michelle.cdnetworks.co.kr (Thread: fun with re, Feb 13 on this list) helped for me. You may try it and could also give feedback so it gets included. - Olli -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 and over. Does anyone have a suggestion on how to debug? The Patch from 20090213113955.ge12...@michelle.cdnetworks.co.kr (Thread: fun with re, Feb 13 on this list) helped for me. You may try it and could also give feedback so it gets included. Sorry: From: Pyun YongHyeon Subject: Re: fun with if_re - Olli -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 information for your hardware revision. Would you show me dmesg output and revision number of if_re.c? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe 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 re0: Ethernet address: 00:1f:d0:af:1a:4c re0: [FILTER] re0: link state changed to UP $FreeBSD: src/sys/dev/re/if_re.c,v 1.95.2.41 2009/02/09 01:38:01 yongari Exp $ I get 3 link state DOWN/UP notices when DHCP client starts. It works for exactly 60 seconds after boot, then stops. Patch from earlier fun with if_re thread didn't help, if_re.c from -CURRENT failed to build. Reverting back to rev 1.95.2.36.2.2 fixes it. Thanks, Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 the full dmesg, let me know. re0: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe 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 re0: Ethernet address: 00:1f:d0:af:1a:4c re0: [FILTER] re0: link state changed to UP $FreeBSD: src/sys/dev/re/if_re.c,v 1.95.2.41 2009/02/09 01:38:01 yongari Exp $ 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). for exactly 60 seconds after boot, then stops. 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? Patch from earlier fun with if_re thread didn't help, Your issue is completely different one. if_re.c from -CURRENT failed to build. You have to use if_re.c/if_rl.c and if_rlreg.h from CURRENT to build it on stable. Reverting back to rev 1.95.2.36.2.2 fixes it. Your controller looks like RTL8168D PCIe controller. ATM I have no idea why if_re.c 1.95.2.41 does not work. I'll let you know if I find a clue. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 exactly 60 seconds after boot, then stops. 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 Patch from earlier fun with if_re thread didn't help, Your issue is completely different one. Ok, good to know. if_re.c from -CURRENT failed to build. You have to use if_re.c/if_rl.c and if_rlreg.h from CURRENT to build it on stable. Ok. I can test that if you wish. Reverting back to rev 1.95.2.36.2.2 fixes it. Your controller looks like RTL8168D PCIe controller. ATM I have no idea why if_re.c 1.95.2.41 does not work. I'll let you know if I find a clue. Ok. I'm happy to test any patches. Thanks, Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 didn't help? You have to use if_re.c/if_rl.c and if_rlreg.h from CURRENT to build it on stable. Ok. I can test that if you wish. I guess re(4) in CURRENT may not help as rev 1.95.2.41 still has issues on your controller. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
On Wed, Feb 25, 2009 at 10:47:07PM -0500 I heard the voice of Steve Wills, and lo! it spake thus: re0: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe 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, I have re0: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe Gigabit Ethernet port 0xdc00-0xdcff mem 0xfdfff000-0xfdff irq 19 at device 0.0 on pci2 re0: turning off MSI enable bit. re0: Chip rev. 0x3800 re0: MAC rev. 0x on a recent 7-STABLE (if_re.c,v 1.95.2.41) which is working OK. I have gotten a few Tx interrupt watchdog timeouts, which I don't recall seeing in any quantity before, but they don't seem to cause any problems. It was previously on a ~Dec 2007 RELENG_7 and worked fine there (and had MSI enabled, as well). -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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 rev=0x2 at phyno=1 And unpluging/repluging didn't help? No, didn't help. Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 7.1-R to RELENG_7 upgrade breaks re nic
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: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe 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, I have re0: RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe Gigabit Ethernet port 0xdc00-0xdcff mem 0xfdfff000-0xfdff irq 19 at device 0.0 on pci2 re0: turning off MSI enable bit. re0: Chip rev. 0x3800 re0: MAC rev. 0x on a recent 7-STABLE (if_re.c,v 1.95.2.41) which is working OK. I have gotten a few Tx interrupt watchdog timeouts, which I don't recall seeing in any quantity before, but they don't seem to cause any If the watchdog timeout message contains missed Tx interrupts you can safely ignore them. It's not real watchdog timeouts. problems. It was previously on a ~Dec 2007 RELENG_7 and worked fine there (and had MSI enabled, as well). Try re(4) in HEAD. You may not see watchdog timeouts anymore. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
