<HTML>
<HEAD>
<TITLE>Weird CentOS 5.3 problem</TITLE>
</HEAD>
<BODY>
<FONT FACE="Courier, Courier New"><SPAN STYLE='font-size:11pt'>I reimaged a compute node on our cluster with the latest 5.3 updates (we were previously running 5.2), but we kept the kernel at 2.6.18-92.1.10.el5 until I can find time to rebuild some of our kernel modules. After the image install finishes and the system reboots, the eth0 ethernet interface disappears. If I do an ifconfig –a, I see what should be eth0, but it’s listed as __tmp2081258173.<BR>
<BR>
[root@node0770 ~]# ifconfig -a<BR>
__tmp2081258173 Link encap:Ethernet HWaddr 00:1E:68:86:67:04 <BR>
BROADCAST MULTICAST MTU:1500 Metric:1<BR>
RX packets:0 errors:0 dropped:0 overruns:0 frame:0<BR>
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<BR>
collisions:0 txqueuelen:1000 <BR>
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)<BR>
Interrupt:66 <BR>
<BR>
The dmesg output isn’t very helpful:<BR>
<BR>
[root@node0770 ~]# dmesg|grep eth0<BR>
eth0: forcedeth.c: subsystem: 0108e:534b bound to 0000:00:08.0<BR>
<BR>
<BR>
If I remove our lustre modules that were built for the 2.6.18-92.1.10.el5 kernel and reboot, the eth0 interface reappears. Another piece to this puzzle is that this problem only seems to happen on our Sun X2200’s. Our Dell 1950’s work just fine after putting on the 5.3 updates. Anyone know what could cause this behavior?<BR>
<BR>
Thanks,<BR>
Randy</SPAN></FONT>
</BODY>
</HTML>