On 01/11/14 21:12, Barry wrote:
Btw no hw alterations have been made, and I have been running mageia2
for the last 2 weeks or so with no problems. Would I be correct in
assuming a faulty software driver is the cause of my problem?
Is Mageia set to auto updates from the repos the Mageia developer wiki
will have a bugs report list there may be a listing of a
similar lock up problem.
The "ifplugd client siocsifmtu invalid argument" is the driver error
message indicating the hardware doesn't support the packet
MTU frame size. Most kernels are set to auto tune frame size according
to other devices such as switches on the network.
You can check if kernel is using auto tune of the frame size in a
terminal a return of [1] indicates it is ON.
cat /proc/sys/net/ipv4/tcp_moderate_rcvbuf
Examples of manual method to adjust MTU also made persistent by
configuring /etc/sysctl.conf
http://www.cyberciti.biz/faq/centos-rhel-redhat-fedora-debian-linux-mtu-size/
If anything the "ifplugd client siocsifmtu invalid argument" is not
something to be concerned about if the internet connection
speed is normal its most adverse effect is that the connection speed
could be slowed down until the kernel auto adjusts mtu
but it will not lock.
Usb devices connected to the pc could cause the mouse and keyboard to
lock however that type of problem is normally
apparent immediately after boot up.
Trying a newer kernel might fix the problem I would still watch the logs
and developer bugs list to narrow down the cause
of the lock up.
--
keith
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
