eth0 (not plugged) auto-negotiating every 10s

[®om]

Binary package hint: network-manager

My eth0 is unplugged, but in /var/log/syslog, every 10 seconds, I have "eth0: auto-negotiating...", is it normal?

Mar 28 17:04:37 rom-laptop kernel: [ 657.552032] eth0: auto-negotiating...
Mar 28 17:04:47 rom-laptop kernel: [ 667.576029] eth0: auto-negotiating...
Mar 28 17:04:57 rom-laptop kernel: [ 677.601010] eth0: auto-negotiating...
Mar 28 17:05:07 rom-laptop kernel: [ 687.624031] eth0: auto-negotiating...
Mar 28 17:05:17 rom-laptop kernel: [ 697.648029] eth0: auto-negotiating...
Mar 28 17:05:27 rom-laptop kernel: [ 707.672031] eth0: auto-negotiating...
Mar 28 17:05:37 rom-laptop kernel: [ 717.696030] eth0: auto-negotiating...
Mar 28 17:05:47 rom-laptop kernel: [ 727.720031] eth0: auto-negotiating...
Mar 28 17:05:57 rom-laptop kernel: [ 737.744031] eth0: auto-negotiating...
Mar 28 17:06:07 rom-laptop kernel: [ 747.768030] eth0: auto-negotiating...
Mar 28 17:06:17 rom-laptop kernel: [ 757.793456] eth0: auto-negotiating...
Mar 28 17:06:27 rom-laptop kernel: [ 767.816033] eth0: auto-negotiating...
Mar 28 17:06:37 rom-laptop kernel: [ 777.840032] eth0: auto-negotiating...
Mar 28 17:06:47 rom-laptop kernel: [ 787.864031] eth0: auto-negotiating...
Mar 28 17:06:57 rom-laptop kernel: [ 797.888030] eth0: auto-negotiating...
Mar 28 17:07:07 rom-laptop kernel: [ 807.912030] eth0: auto-negotiating...
Mar 28 17:07:17 rom-laptop kernel: [ 817.936030] eth0: auto-negotiating...
Mar 28 17:07:27 rom-laptop kernel: [ 827.960029] eth0: auto-negotiating...
Mar 28 17:07:38 rom-laptop kernel: [ 837.984029] eth0: auto-negotiating...
Mar 28 17:07:48 rom-laptop kernel: [ 848.009025] eth0: auto-negotiating...
Mar 28 17:07:58 rom-laptop kernel: [ 858.032029] eth0: auto-negotiating...
Mar 28 17:08:08 rom-laptop kernel: [ 868.057019] eth0: auto-negotiating...
Mar 28 17:08:18 rom-laptop kernel: [ 878.080029] eth0: auto-negotiating...
Mar 28 17:08:28 rom-laptop kernel: [ 888.104030] eth0: auto-negotiating...
Mar 28 17:08:38 rom-laptop kernel: [ 898.128029] eth0: auto-negotiating...
Mar 28 17:08:48 rom-laptop kernel: [ 908.152033] eth0: auto-negotiating...

[Alexander Sack (asac)]

driver bug. please provide info about your chipset/driver used.

[Leann Ogasawara (leannogasawara)]

Yes, please provide the following:

sudo lspci -vnvn > lspci-vnvn.log
dmesg > dmesg.log
cat /proc/version_signature

[®om (rom1v)]

I will attach the requested files.

I have (maybe) interesting lines in syslog :
Apr 20 01:04:10 rom-laptop console-kit-daemon[2537]: WARNING: Couldn't read /proc/2536/environ: Failed to open file '/proc/2536/environ': No such file or directory
Apr 20 01:04;44 rom-laptop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion 'NM_IS_SETTING_802_1X (setting)' failed

$ cat /proc/version_signature
Ubuntu 2.6.28-11.41-generic

[®om (rom1v)]

(sorry, dmesg will not be very useful, since I rebooted and I have an hardware hard-drive problem -fsck failed every time-)

[®om (rom1v)]

My new dmesg.log which is complete.

[®om (rom1v)]

It still happens on jaunty final.

[Spencer Gibb (spencer-gibb)]

I also have the same issue:
$ cat /proc/version_signature
Ubuntu 2.6.28-6.20-386

[Miguel Gaspar (ghaspias)]

Affects me too. Attached lspci log.

[Miguel Gaspar (ghaspias)]

Using karmic beta, updated 7/Oct.
Is this a bug in sis190 module? Should it be reported elsewhere?

[Miguel Gaspar (ghaspias)]

The satus of the device as reported by ethtool:

miguel@sully:~$ sudo ethtool eth0
Settings for eth0:
 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 10Mb/s
 Duplex: Half
 Port: MII
 PHYAD: 1
 Transceiver: internal
 Auto-negotiation: on
 Current message level: 0x00000037 (55)
 Link detected: no

[Francesc Oller (francesc-oller)]

Patch http://people.ubuntu.com/~apw/lp381196-jaunty/ should be applied. This is a known and solved issue.
Andy Whitcroft applied this patch to a 2.6.28-14 kernel and solved it. What I don't understand is why this patch isn't applied to newer kernels

[®om (rom1v)]

Still happens in Karmic…

[Nick Howden (24doeway)]

Still happening with Ubuntu 2.6.31-14.48-generic on Ei-System Laptop with SiS191 Ethernet chipset

[Miguel Gaspar (ghaspias)]

Why isn't this fixed yet? Is there really a working patch? If so, how hard is it for a normal user to apply it?

[tankdriver (stoneraider-deactivatedaccount)]

I have the same chipset on an ASUS Notebook, having problems with standby/resume. After waking up no ethernet connection is detected. Could this be related to this bug?

[Miguel Gaspar (ghaspias)]

@tankdriver: I don't think so, in my case this never limited my ability to connect, the issue is only with improper detection of unplugged state.

[Miguel Gaspar (ghaspias)]

According to http://marc.info/?l=linux-netdev&m=126753029717458&w=2:
>> Applied, thanks for giving life to this patch Jeff.
>>
>> I'll stick this into 2.6.34 and if we want we can backport it
>> to -stable after it cooks there for a while.

So it seems we'll have to wait some time, but there's hope!

[tankdriver (stoneraider-deactivatedaccount)]

I can confirm: This bug is fixed in Kernel 2.6.34-rc1.
(Source: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc1/ )

[improponibile (essereimproponibile)]

I've still this problem on Ubuntu 2.6.32-25.43-generic

Is there any patch to fix it on Lucid?

[Jonas Schwabe (jonas-schwabe)]

To fix it on lucid you simply need to use this patch against sis190.c and then compile it...
BTW:
Anyone tried 10.10? Does it work there ootb? It should as the used kernel version contains the patch attached thought.
I had no possibility to test the Alpha/Beta (already?) till now but I will do the next days...

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Bill Woodger (bill-woodger)]

I hope this is an appropriate place for this.

I have the same problem as the above, "eth0: auto-negotiating..." every 10 seconds. I have 10.04 LTS Kernel 2.6.32-39-generic, loaded onto this system last week, it has a hard-disk to itself, not running underneath anything, entire disk under its control.

I had another problem reported, about cpu being a bit hot. Got a hit from here and cleaned several inches of dust from heat-sink, fans etc. Cpu problem gone away, ethernet "problem" persists.

On the other disk I have Windows XP, which does report "cable unplugged" for the ethernet.

The ethernet cable has never been plugged in under Ubuntu, only has a wireless connection.

There is no apparent problem caused by this, I just don't like the idea that it might be warning me of something I'm unaware of, yet is only able to say "gahh" as far as my knowledge is concerned.

I'm looking at the messages only because another machine went very slow a couple of weeks ago, and it turned out to be a problem with the hard-disk, manifesting itself originally by screwing-up something to do the the USB-controlling software, causing constant retries on multiple USB ports even though nothing was plugged into them. I have tested (both) disks here and as far as I can tell they are OK but a little concerned if I'm going to end up a week down the track doing a load of data recovery again.

As Ubuntu is new on this machine, I have no idea if it is slower than it was before (which was noticeable suddenly on the other machine).

Until a few months ago, under the Windows XP, this machine was connected via the ethernet.

I'm sure more information is needed, as I'm somewhat new to this (which made the data-recovery even more "interesting"), so please bear with me as I respond as best as I can to requests for more.

Kind regards,

Bill

PS. If this is in the wrong place, or should be opened as "new" or something, I apologise, but there is so much stuff out there it is difficult to spend the time when I'm a bit nervous about the unlikely event of another hard-disk failure at any moment.

PPS. Having written all this now, I've just had the "brilliant" thought to close this machine down and do the research from the other one...