[CentOS] Re: eth1 changed to __tmp78668633 in recent kernels

henry ritzlmayr centos at rc0.at
Thu May 15 12:51:02 UTC 2008


Am Donnerstag, den 15.05.2008, 14:06 +0200 schrieb henry ritzlmayr:
> Hi list,
> 
> kernel-xen-2.6.18-53.1.14.el5 and 
> kernel-xen-2.6.18-53.1.19.el5 
> do not detect/initialize/whatever my eth1 network card any more. 
> 
> With 
> kernel-xen-2.6.18-53.1.13.el5 
> everything is working as expected. 
> 
> With the two recent kernels I only get an Interface named __tmp786686833
> which is not added to xenbr...
> 
> lspci -v to the adapter in question says
> 
> 02:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet
> Controller (Copper) (rev 06)
>         Subsystem: Intel Corporation PRO/1000 PT Desktop Adapter
>         Flags: bus master, fast devsel, latency 0, IRQ 17
>         Memory at febe0000 (32-bit, non-prefetchable) [size=128K]
>         Memory at febc0000 (32-bit, non-prefetchable) [size=128K]
>         I/O ports at ec00 [size=32]
>         Expansion ROM at feba0000 [disabled] [size=128K]
>         Capabilities: [c8] Power Management version 2
>         Capabilities: [d0] Message Signalled Interrupts: 64bit+
> Queue=0/0 Enable-
>         Capabilities: [e0] Express Endpoint IRQ 0
> 
> ip link says
> 
> 2: __tmp786686833: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:1b:21:0e:a9:3b brd ff:ff:ff:ff:ff:ff
> 
> In modprobe.conf I have 
> alias eth1 e1000
> for the adapter in question. The module itself is loaded.
> 
> 
> 
> Any Ideas how to fix this?
> 
> cheers 
> Henry

Update: Thanks to Christopher Isip from the xen-list. I found a solution
for the problem. Disabling xend at runlevel 2. With this configuration
every kernel works as expected. With xend enabled at runlevel 2 only the
older kernel works as expected. 

Is this intended - did I miss something?

cheers
Henry 

 





More information about the CentOS mailing list