strange NIC reboots

Hi,

I have openSuse 11.4 installed, which has two NIC (eth0 and eth1), but I recognized that eth1 produces some messages in /var/log/messages and dmesg.
So it seems that it does many reboots while network isnt availible and I don’t know why.


Sep 26 13:21:03 server kernel: [1127829.428839] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 26 13:27:26 server kernel: [1128212.468844] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 26 13:32:19 server kernel: [1128505.428843] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 26 13:34:24 server smartd[3774]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 109
Sep 26 13:34:25 server smartd[3774]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 109
Sep 26 13:38:02 server kernel: [1128848.476852] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 26 13:40:50 server kernel: [1129016.492848] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 26 13:52:03 server kernel: [1129689.527846] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

If you need some extra infos from me please tell me…

Thanks

On 27.09.2011 11:36, Thorus wrote:
>
> Hi,
>
> I have openSuse 11.4 installed, which has two NIC (eth0 and eth1), but
> I recognized that eth1 produces some messages in /var/log/messages and
> dmesg.
> So it seems that it does many reboots while network isnt availible and
> I don’t know why.
>

I’ve had that.
It was a problem in my ISP’s DSLAM.
It took some effort to convince them but I kept sending them logs like
yours.

tail -f /var/log/messages | grep eth > somefile.txt.

I emailed those logs to them daily until after a few days they fixed it.

Vahis

http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 12.1 Milestone 5 (x86_64) 3.1.0-rc6-2-desktop in VBox
openSUSE 11.4 (i586) 3.0.4-43-desktop “Tumbleweed” in EeePC 900

But eth1 is the NIC to the LAN and eth0 the NIC to an SoHo- Router of Telekom, so its still possible that it is a problem of my ISP’s DSLAM?

It may be a driver issue. Please show us what is the ethernet hardware in question and what driver it is using :

lspci -nnk

Best regards,
Greg

Hi,


01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)
        Subsystem: ASUSTeK Computer Inc. M3A78-EH Motherboard [1043:82c6]
        Kernel driver in use: r8169

05:00.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05)
        Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter [8086:1376]
        Kernel driver in use: e1000

The 05:00.0 one should be eth1 because of the kernel messages, which were also with e1000…

By quick searching I didn’t find people having particular problems with this driver.

Did You check the cable ?
Dose ifconfig show anything suspicious like a lot of errors on the interface ?

Best regards,
Greg

Hi,

ifconfig shows 2 errors at RX packets…

I will check the cable at the weekend, is there a method to test a cable?

There are some cable testers or You could probably use a simple Volt-Ohm meter but I guess it will be easiest to try a different cable :slight_smile:

Best regards,
Greg