HP 6735s; Ethernet does not work after hibernate with 11.1

Hi,

I have a HP 6735s with openSUSE 11.1 x64 installed. The laptop has a Marvell Technology Group Ltd. Device 4357 (rev 10) Ethernet controller.

After waking up from hibernate (suspend to disk) the network sometimes does not work. KNetworkmanager reports then that it did not detect a carrier.

I tried to a restart of /etc/init.d/network and KNetworkmanager as well in both combinations of order, but it never resolved the problem.

Looking into /var/log/messages there are several error messages after coming out of hibernate, from which I don’t know whether they are related to this problem:

08:01:18 Laptop dbus-daemon: Rejected send message, 2 matched rules; type=“error”, sender=":1.0" (uid=0 pid=2258 comm="/usr/sbin/hald --daemon=yes “) interface=”(unset)" member="(unset)" error name=“org.freedesktop.Hal.Device.UnknownError” requested_reply=0 destination=":1.18" (uid=1000 pid=4098 comm="kded4 "))

sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul 2 08:01:21 Laptop kernel: sky2 eth0: enabling interface
Jul 2 08:01:21 Laptop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready

After doing a reboot, at least this kernel message about sky2 is not present anymore.

Can anybody give me some tips how to solve this issue?

Thanks for your help

Did you try

rcnetwork restart

I tried that and it did not make a difference. Tried it in different combinations.

(1) just calling rcnetwork restart
(2) shuthing down knetworkmanager, rcnetwork restart, starting knetworkmanager again
(3) unplugging ethernet, then doing (2)

Nothing worked.

Here is what /var/log/messages shows after a rcnetwork restart


Jul  3 08:02:35 Laptop rcnetwork: Shutting down the NetworkManager
Jul  3 08:02:35 Laptop kernel: sky2 eth0: disabling interface
Jul  3 08:02:35 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:35 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:35 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:35 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:35 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:35 Laptop avahi-daemon[3216]: Withdrawing address record for fe80::221:ff:fedd:2c19 on eth1.
Jul  3 08:02:36 Laptop ifdown:     eth0      device: Marvell Technology Group Ltd. Device 4357 (rev ff)
Jul  3 08:02:36 Laptop ifdown:     eth1      device: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Jul  3 08:02:36 Laptop ifdown:               No configuration found for eth1
Jul  3 08:02:36 Laptop ifdown:               Nevertheless the interface will be shut down.
Jul  3 08:02:36 Laptop ifdown:     pan0
Jul  3 08:02:36 Laptop ifdown:               No configuration found for pan0
Jul  3 08:02:36 Laptop ifdown:               Nevertheless the interface will be shut down.
Jul  3 08:02:36 Laptop ifdown-bridge: bridge-utils not installed
Jul  3 08:02:37 Laptop ifdown:     vboxnet0
Jul  3 08:02:37 Laptop ifdown:               No configuration found for vboxnet0
Jul  3 08:02:37 Laptop ifdown:               Nevertheless the interface will be shut down
Jul  3 08:02:37 Laptop rcnetwork: Starting the NetworkManager
Jul  3 08:02:39 Laptop avahi-daemon[3216]: Registering new address record for fe80::221:ff:fedd:2c19 on eth1.*.
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 0000:02:00.0: eth0: phy I/O error
Jul  3 08:02:41 Laptop kernel: sky2 eth0: enabling interface
Jul  3 08:02:41 Laptop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready

dannori wrote:
> Jul 3 08:02:41 Laptop kernel: sky2 eth0: enabling interface
> Jul 3 08:02:41 Laptop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready

I think the phy I/O error indicates a problem with suspend/resume. On
June 17, a number of fixes for this driver were entered into the
mainline source including several that address problems with shutdown.
As these will not be available until kernel 2.6.31, your only
workaround may be to unload/reload the driver.

Does this sequence work?

sudo /sbin/modprobe -rv sky2
sudo /sbin/modprobe -v sky2

Larry

Thanks Larry for that tip. I will try that the next time it appears.

I did another test and switched off knetworkmanager and that did make any difference. So you are probably right with the driver.

Warming up an old thread. After upgrading from 11.1 to 11.2 I thought this problem would go by, but after a resume from disk today I still got the problem that the network is unavailable.

uname -a shows:

2.6.31.5-0.1-default #1 SMP 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux

Is there another way to fix this or did the patches not make it to this version?

Thanks for your help.