suppress eth0 PHY reset messages in syslog??

tandp7877 · 02-09-2010, 05:17 AM

I'm getting 10000000's of syslog messages :
"eth0: PHY reset until link up"
- I have wireless and don't normally use an ethernet cable. From Googling round I found this bug report https://bugs.launchpad.net/ubuntu/+s...ux/+bug/270184 which appears to match the problem, however I do not feel happy/competent enough to recompile the driver as suggested in the bug fix.
Is there a way to configure the driver so that it only tries the eth0 connection a limited number of times?

This is Ubuntu 8.04 2.4.26-27 and SIS 191 chipset

devwatchdog · 02-09-2010, 09:16 PM

You should have read all the responses on the bug web page. This one looks like something you could do without fear of breaking anything:

Code:

Emilio wrote on 2009-07-31:	 #4
This is the workaround to stop that really annoying logs that fill the system log with useless information

add this line to /etc/modprobe.d/options.conf

    options sis190 debug=0

You can then remove the module with this command:

sudo rmmod sis190

then:

sudo modprobe sis190

That will reload the module and hopefully remove the logging issue.

You can also reboot the system.

Keep in mind, though, you'll never see errors in syslog for this module again.

tandp7877 · 02-10-2010, 05:55 AM

I don't have this file options.conf:

Code:

ls /etc/modprobe.d
aliases                blacklist-local     fuse        ndiswrapper
alsa-base              blacklist-modem     ipw3945     nvidia-kernel-nkc
arch                   blacklist-oss       isapnp      options
arch-aliases           blacklist-scanner   libpisock9  toshiba_acpi.modprobe
blacklist              blacklist-watchdog  libsane
blacklist-framebuffer  bluez               lrm-video

Can I just add it? Is it correct that the eth0 driver will still work?

devwatchdog · 02-11-2010, 04:38 AM

You can create a new options.conf file in /etc/modprobe.d, named 'options.conf'. Actually, the name of the file doesn't really matter as anything that ends with '.conf' will be parsed in that directory. The module for the ethernet port will work, it just won't fill your syslog logs with spew when it isn't connected.

When you get done making changes, and have reloaded the module, you can test to see if it is still functioning by typing this:

(and I'm assuming it shows up as eth0)

ifconfig eth0 10.123.238.1 netmask 255.255.255.0

ping 10.123.238.1

You should then see ping responses. That's not a permanent configuration change, and will go away when you shut your system down. If that IP interferes with your network, pick another private network IP to use.

tandp7877 · 02-12-2010, 09:21 AM

Great!

Thanks for the assistance, that works.

T.