Hi Mark,
> I am having an issue where eth1 is throwing some messages and stops
> > responding. Restarting networking doesn't work and also just bringing
> down
> > eth1 with 'ifdown' doesn't fix it. I have never seen anything like these
> > messages:
> >
> > eth1: no IPv6 routers present
> > r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10).
> > r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
> > r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25).
> <...>
> > r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25).
> > r8169 0000:03:00.0: eth1: rtl_phy_reset_cond == 1 (loop: 100, delay: 1).
> > r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25).
> <snip>
> > r8169 0000:03:00.0: eth1: rtl_phyar_cond == 1 (loop: 20, delay: 25).
> > r8169 0000:03:00.0: eth1: link up
> >
> > [root@mail jtsm]# lspci | grep -i net
> > 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> > Connection
> > 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
>
> Googling on rtl_counters_cond finds a lot of folks talking about "laptop
> mode" error, and somebody mentions "zero configuration", which I assume
> they mean zeroconf. Is this a laptop? Is this wired or not? If it's wired,
> and not a laptop, I'd shut down avahi-daemon and chkconfig it off (and the
> same with NetworkMangler, er, Manager), and see what happens.
>
I found those same resources. This is NOT a laptop and it is wired. Has
been for a few years.
I tried 'service avahi-daemon stop' and 'service NetworkManager stop' and
both are unrecognized.
Another possibility, if wired, check your patch cord, and make sure it's
> plugged in securely at both ends.
>
I replaced the cable completely just in case and nada.
Jason
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
