You are not logged in.
After the shutdown/reboot output there's a long pause after which eth0 error appears, right before the computer is turned off:
> REBOOTING
[ 80.505775] e1000e 0000:00:19.0: eth0: Could not acquire PHY
[ 80.505831] Restarting system.The error started to appear after 'initscripts' update (2 days ago), first it was about iwlagn. The error disappears so quickly that I couldn't tell what iwlagn error said (the above error had to be photographed). I think one of these has been present since the initial OS install because my shutdown process always took quite some time. I'm using 'networkmanager' daemon instead of 'network'.
Here's my rc.conf network and daemon settings:
interface=eth0
address=
netmask=
broadcast=
gateway=
NETWORK_PERSIST="no"
NETWORKS=()
DAEMONS=(hwclock syslog-ng !acpid sensors !network netfs dbus networkmanager @samba @alsa @laptop-mode @crond @httpd @mysqld @xinetd)I'm rarely using ethernet connection, I'm usually connected to a wireless network. Any idea what could be causing the error and how to fix it?
Last edited by Camus (2011-08-14 10:01:25)
Offline
Does it break anything or are you just curious why it suddenly started to appear?
It may be because of the VERBOSE parameter http://mailman.archlinux.org/pipermail/ … 21114.html Do you have 'quiet' on you kernel boot line?
Offline
Yes, I have quiet on my kernel boot line. I've tried connecting to ethernet and rebooting with and without wifi connected along the ethernet; the shutdown time is much shorter, there's only a brief pause after ' > REBOOTING' line. I've tried changing interface line to:
interface=wlan0but error and long shutdown time is still there.
So, the issue isn't about initscript update, it's just that because of the update I finally got conformation that my shutdown time is indeed unnecessarily long. Sorry for the confusion, I've changed the thread's title. The system appears to do something with the ethernet connection at shutdown when there is no ethernet connection.
I will remove quiet argument and report back if there's any more output about the error. Thanks for the help.
Last edited by Camus (2011-08-01 18:15:39)
Offline
There's something about udevd being terminated by signal 15, but I don't know if it's related. I have no problems connecting to either wifi network or ethernet while using the computer, the only issue is longer shutdown when I'm not connected to ethernet, because the system appears to think I am connected.
As I've said, the shutdowns were always this long, I just didn't know until now that there was some error causing it. I'm almost always using wireless, so I didn't even notice the difference between wireless and ethernet shutdown times.
Offline
I still have no idea what exactly does the system wants to do with the ethernet connection after shutdown script and why does it want to do it even when there's no ethernet connection present...
$ dmesg | grep eth
[ 6.817738] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) f0:de:f1:19:17:c2
[ 6.817740] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 6.817806] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: A002FF-0FF
[ 17.243637] ADDRCONF(NETDEV_UP): eth0: link is not readyI don't think there's anything unusual in the above output, 'link is not ready' most likely means that there's no connection from the eth0 interface.
Is there any way I could get shutdown output the same way I can see boot output with 'dmesg'? I've looked at logs in /var/log, but I can't find anything.
Offline
Ok, after previously giving up, I've tried to find the cause one more time today. And it was really obvious after I've had a close look at lsmod output; the cause was e1000e module. I've added this to the top of my rc.shutdown:
modprobe -r e1000eShutdowns/restarts are now reasonably fast and without ethernet errors.
Last edited by Camus (2011-08-14 10:02:37)
Offline