Weird CentOS 5.3 problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Title: Weird CentOS 5.3 problem
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.

[root@node0770 ~]# ifconfig -a
__tmp2081258173 Link encap:Ethernet  HWaddr 00:1E:68:86:67:04  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:66

The dmesg output isn’t very helpful:

[root@node0770 ~]# dmesg|grep eth0
eth0: forcedeth.c: subsystem: 0108e:534b bound to 0000:00:08.0


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?

Thanks,
Randy
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux