I have seen a brief error using ifconfig :
/tmp > ifconfig
: error fetching interface information: Device not found
Then, a second later :
/tmp > ifconfig
eth0 Link encap:Ethernet HWaddr 00:A0:C9:4C:B5:B9
inet addr:134.10.44.245 Bcast:134.10.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8838310 errors:605 dropped:0 overruns:0 frame:2203
TX packets:4708368 errors:0 dropped:0 overruns:0 carrier:0
collisions:113062 txqueuelen:100
Interrupt:9 Base address:0xd400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:1664 errors:0 dropped:0 overruns:0 frame:0
TX packets:1664 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
/tmp >
I am running kernel 2.2.2-ac7.
====================================================================
Another thing is the NFS mount time. I am using autofs to automount
my NFS partitions.
After the idle time, the partitions are umounted. That's OK.
When I access a umounted partition again, it takes sometimes up to 10
seconds to mount the partition.
I have rebooted to test it with a 2.2.1-ac3, and it takes around 1 second.
Back to 2.2.2-ac7, and it takes 10 seconds.
Next (worst) thing, as mentionned two days ago, I may receive some
corrupted data when compiling over a NFS server (in that case,
a 2.2.1-ac3 box running knfsd). It never happened using a 2.2.1-ac3
kernel. Sometimes, data looks like the content of the termcap file.
Sometimes, the shell does not find the '.' directory.
And, in a general manner, compilation that took around 19/20 minutes
with 2.2.1-ac3 now takes 27 or more minutes.
Have anyone else observed the phenomenum ?
Thanks,
A+
-- Thierry Danis
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/