Netlink error no device matches name offset 24 netlink error no such device

Arch Linux

You are not logged in.

#1 2020-06-08 01:11:58

[SOLVED] Ethernet card doesn’t detect carrier while using battery

Hello everyone,
This is my first post so I apologize if I put it in the wrong category or if I’m providing too much/little information with respect to what is needed.

I’m using a Lenovo Thinkpad T495, installed using the normal procedure written in the wiki, in dual boot with windows 10.
I recently noticed that whenever i plug in the ethernet cable with the computer already booted up it doesn’t connect to the network, but only while I’m using the battery as power source.
As soon as i connect the pc to the external power the network is detected and it connects to the network.
I’m also able to access the wired network if i boot the laptop with the ethernet cable already inserted (with or without battery).
Removing external power while the PC is connected to the network leaves the connection up (that is, until i disconnect the ethernet and plug it again, then I’m back in the first case).

What is very strange to me is that the NIC actually connects to the network when I plug in the cable: LEDs on the switch (to which the pc is connected) lights up and signal not only a connection, but that is is 100Mb/s.
This means that my pc recognized the link to be 100Mb/s capable! (yes, unfortunately I don’t have a gigabit LAN)
This happens even though the LEDs on the PC’s card remain off.

I tried looking for solutions on T495 and Ethernet wiki page but found nothing that seems relatable to me.
In particular, I think I’m not affected by the «Realtek no link / WOL problem» because the nic works sometimes without windows intervention, and not «until windows boots up», and the card’s LED turns on at POST time.

I tried also looking into the system logs (linked below) to see if I could find the source of the problem and maybe that lead to something: at a certain point there’s a «r8169 . : can’t disable ASPM; OS doesn’t have ASPM control» warning.
I searched for «ASPM r8169» and found a this AUR package which however prints an error while installing it (it seems it was created for an older kernel and not updated since 2018).
The pacman output is:

After a reboot, ethernet cards simply won’t show anymore and I could only use wifi.

Other possibly useful outputs:
lspci -v (only ethernet portions: this pc has another nic that would be used if i had a docking station)

ip link while the network cable is connected, but not the power chord

journald -b output when ethernet is connected after

1m after boot end (circa 02:36), then I wait

EDIT: corrected ip output

Last edited by quagmire (2020-11-10 00:23:39)

Источник

Установка Linux не будет загружаться из-за ошибки GRUB «нет такого устройства»

Я думаю, что исчерпал все, что я знаю, чтобы сделать, поэтому я посылаю факелы. Я постараюсь охватить все это (хотя и по частям), поэтому, пожалуйста, будьте терпеливы.

Я решил установить Linux Mint 11, где у меня ранее была Ubuntu 10.10. Перед этой установкой у меня был раздел с Windows XP, который — в далеком прошлом — я использовал для двойной загрузки. Я удалил раздел в этой установке.

После установки система не загружается. После проверки CD/DVD он печатает:

Не было проблем с загрузкой Ubuntu. Кажется, я вспомнил похожую проблему в прошлый раз, когда я установил (вместо обновления) Ubuntu. Это было какое-то время, но я решил исправить это с помощью FIXMBR и / или FIXBOOT с компакт-диска XP. Те не работали на этот раз.

Похоже, что запрос GRUB rescue> не работает. Даже help не работает. Я могу ls , что дает:

Кроме того, я не знаю, что это за устройство. Я не могу найти соответствующий UUID в /dev/disk/by-uuid . В связи с этим для моего загрузочного жесткого диска нет идентификаторов UUID (см. Ниже). Моя установка — Frankenbox. Я знаю, что нельзя полагаться на перечисление устройств в таком миксе, но они приведены ниже для удобства обсуждения.

• Ch 0 Master: 250 ГБ PATA (SDA)
  • sda1
• Ch 0 Раб: нет
• Ч. 1 Мастер: 80 ГБ SATA (SDB)
  • SDB1: /
  • sdb2: /home
  • sdb3: swap
• Ч. 1 Раб: DVD SATA
• Карта расширения SATA: 250 ГБ SATA (SDC)
  • sdc1

Я подумал, что ударил в золото, когда обнаружил какие-то затяжные (и вызывающие недоумение) метаданные RAID на sda. Диск ранее не обнаруживался в установке Linux, но появился после использования dmraid -r -E /dev/sda . Однако ошибка загрузки сохраняется.

До сих пор я мог использовать установочный компакт-диск Mint для загрузки с локального диска, что действительно привело бы меня к установке на sdb1. После использования компакт-диска для загрузки с накопителя и запуска приведенного ниже, я усугубил проблему, предоставив приглашение GRUB> вместо загрузки с накопителя.

Несомненно, есть несоответствие, потому что sdb, который имеет 3 раздела, кажется (hd2) в приглашении GRUB rescue> , но (hd1) при фактической загрузке. Однако, если я использовал UUID (и я думаю, что использовал), это не должно быть проблемой. Используя live CD, я вижу, что sdb1:/boot/GRUB/menu.list содержит

Основная проблема, насколько я понимаю, заключается в том, что GRUB по какой-то причине, которую я не понимаю, пытается загрузить устройство, которое не существует. Я не знаю, как определить, что он ищет по указанному UUID. Я не вижу UUID для чего-либо на SDA.

И теперь я даже не могу загрузиться с диска, используя CD.

Обновить:

Я подумал, что размещение раздела /boot на том же диске, что и MBR, может помочь, поэтому я добавил sda2, установил флаг boot и переустановил (что, вероятно, излишне).

Я снова получаю приглашение grub rescue> , но теперь, когда я получаю ls , я получаю

Таким образом, sda не больше (hd0) в этом приглашении, чем sdb (hd1). Я не знаю, почему это так смещено, и почему это важно. Я могу попробовать еще раз, поставив /boot на sdc/(hd0).

Источник

by Arya MA | Jul 7, 2020

Webmaster and online service providers often inform that they are receiving a “no such device” message while using the ethtool command. This happens due to missing interface, driver issue etc.

As a part of our Server Management Services, we have helped online service providers to fix several similar Cloudflare errors.

Today, let’s discuss some tips to fix the DNS resolution error.

Ethtool is a Network Interface Card configuration command that allows you to retrieve information and change your NIC settings. At times users may face a “no such device” error message while using this command. The typical error message looks like :

The common reasons for this error message include:

1. Missing Interface or it renamed to any other name

3. Selinux block

The first step to start troubleshooting the issue would be to check the dmesg output. dmesg is a command that Linux operating systems use to print the message buffer of the kernel. Since we here need the output related to an interface, we can use the following command to collect the required details:

The output of the above command may resemble the one given below:

It confirms that the reason here is that the network interface was renamed from eth0 to eth3. Rename of the interface file or performing a cleanup of the subsystem will help to fix this error.

Let us now look at the steps to fix the error.

Rename the file

As we discussed earlier, if the rename of the interface triggers the no such device message, changing the interface file name fixes the error. For instance, if the interface was renamed from eth0 to eth3, we could follow the steps below:

Another method is actually to clean up all the SUBSYSTEM Information and reboot. Hopefully, the eth0 is mapped back to /etc/sysconfig/network-script/ifcfg-eth0

Alternatively, try modifying the /etc/udev/rules.d/70-persistent-net.rules and reboot. For instance, the contents of the file may resemble:

The value of the NAME field needs to be changed to eth0. Once you are done, reload the udev configuration with the command start_udev

Finally, the network configuration needs to be updated.

Disable Selinux

Another option to fix the no such device error is to disable Selinux. Selinux is a Linux kernel security feature for access control. We could cross-check the status of it using the command below:

To disable SELinux on CentOS 7 temporarily, we can use the command

Similarly to set it disabled permanently, we will need to edit the SELinux configuration file.

Finally, reboot the server for the changes to take effect.

[Need assistance to fix ethtool no such device error? We’ll help you.]

Conclusion

In short, no such device error occurs due to reasons like renamed interface name, SELinux block etc. Today we discussed some tips that our Support Engineers follow to fix the ethtool error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

Please help with «Bringing up interface eth0: RTNETLINK answers: No such device» [LONG]

I’m a struggling RHEL noob trying to configure network interfaces for use as a bridging firewall. I am using RHEL 5.6 for IA-64 on an HP Integrity RX-2600. Previously, I had the network interfaces configured successfully, but after a PCI card shuffle, I started getting RTNETLINK messages. The original PCI configuration had a PCI-X to PCI bridge adapter in slot 1, and a 1000Base-LX adapter in slot 4. I removed the bridge adapter, and put the 1000Base-LX adapter in its place. Then, RTNETLINK complaints arose. I tried removing the network adapter, booted up, and then shutdown. Next, I reinstalled the network adapter, and booted up again, but no luck.

Any light that can be shed upon this problem will be greatly appreciated.

—— BEGIN console boot messages ——

Loading.: Red Hat Enterprise Linux Server
Starting: Red Hat Enterprise Linux Server

ELILO boot: Uncompressing Linux. done
Loading file initrd-2.6.18-274.3.1.el5.img. done
Linux version 2.6.18-274.3.1.el5 (mockbuild@natasha.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Aug 26 18:48:23 EDT 2011
EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
booting generic kernel on platform hpzx1
PCDP: v0 at 0x3fb2c000
Early serial console at MMIO 0xf4050000 (options ‘9600n8’)
rsvd_region[0]: [0xe000000001000000, 0xe0000000010000a8)
rsvd_region[1]: [0xe000000004000000, 0xe000000004e94e68)
rsvd_region[2]: [0xe0000040fea40008, 0xe0000040fea40058)
rsvd_region[3]: [0xe0000040fea43fa4, 0xe0000040fea44008)
rsvd_region[4]: [0xe0000040fea46000, 0xe0000040fef95b16)
rsvd_region[5]: [0xe0000040fef9c008, 0xe0000040fef9c6c8)
rsvd_region[6]: [0xffffffffffffffff, 0xffffffffffffffff)
Initial ramdisk at: 0xe0000040fea46000 (5569302 bytes)
SAL 3.1: HP version 2.31
SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
No logical to physical processor mapping available
cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
ACPI: Local APIC address c0000000fee00000
GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
2 CPUs available, 2 CPUs total
MCA related initialization done
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists. Total pages: 390218
Kernel command line: BOOT_IMAGE=scsi0:EFIredhatvmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00 rhgb quiet ro
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while.
Found volume group «VolGroup00» using metadata type lvm2
Internal error: Maps lock 14778368 CPU 0 (0x0000) vector 48
kernel: 2 CPUs available, 2 CPUs total
kernel: MCA related initialization done
rpc.statd[1807]: Version 1.0.9 Starting
kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
kernel: Built 1 zonelists. Total pages: 390218
kernel: Kernel command line: BOOT_IMAGE=scsi0:EFIredhatvmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00 rhgb quiet ro
kernel: PID hash table entries: 4096 (order: 12, 32768 bytes)
kernel: Console: colour VGA+ 80×25
kernel: Memory: 6154992k/6243488k available (6688k code, 108944k reserved, 4001k data, 464k init)
kernel: McKinley Errata 9 workaround not needed; disabling it
kernel: Calibrating delay loop. 2244.60 BogoMIPS (lpj=1122304)
kernel: Security Framework v1.0.0 initialized
kernel: SELinux: Initializing.
kernel: selinux_register_security: Registering secondary module capability
kernel: Capability LSM initialized as secondary
kernel: Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
kernel: Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
kernel: Mount-cache hash table entries: 1024
kernel: ACPI: Core revision 20060707
hcid[1865]: Bluetooth HCI daemon
kernel: Boot processor id 0x0/0x0
kernel: cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
kernel: Fixed BSP b0 value from CPU 1
sdpd[1869]: Bluetooth SDP daemon
hcid[1865]: Register path:/org/bluez fallback:1
kernel: CPU 1: synchronized ITC with CPU 0 (last diff -27 cycles, maxerr 681 cycles)
kernel: Calibrating delay loop. 2244.60 BogoMIPS (lpj=1122304)
kernel: Brought up 2 CPUs
kernel: Total of 2 processors activated (4489.21 BogoMIPS).
kernel: migration_cost=6421
kernel: checking if image is initramfs. it is
kernel: Freeing initrd memory: 5424kB freed
pcscd: pcscdaemon.c:507:main() pcsc-lite 1.4.4 daemon ready.
kernel: DMI 2.3 present.
kernel: NET: Registered protocol family 16
kernel: ACPI: bus type pci registered
kernel: ACPI: Interpreter enabled
kernel: ACPI: Using IOSAPIC for interrupt routing
kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
kernel: PCI: Firmware left 0000:00:03.0 e100 interrupts enabled, disabling
kernel: ACPI: PCI Root Bridge [PCI1] (0000:20)
kernel: ACPI: PCI Root Bridge [PCI2] (0000:40)
kernel: ACPI: PCI Root Bridge [PCI3] (0000:60)
kernel: ACPI: PCI Root Bridge [PCI4] (0000:80)
kernel: ACPI: PCI Root Bridge [PCI6] (0000:c0)
pcscd: hotplug_libusb.c:402:HPEstablishUSBNotifications() Driver ifd-egate.bundle does not support IFD_GENERATE_HOTPLUG. Using active polling instead.
pcscd: hotplug_libusb.c:411:HPEstablishUSBNotifications() Polling forced every 1 second(s)
kernel: ACPI: PCI Root Bridge [PCI7] (0000:e0)
kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
kernel: pnp: PnP ACPI init
kernel: GSI 34 (edge, high) -> CPU 1 (0x0100) vector 49
kernel: GSI 35 (edge, high) -> CPU 0 (0x0000) vector 50
kernel: pnp: PnP ACPI: found 11 devices
kernel: usbcore: registered new driver usbfs
kernel: usbcore: registered new driver hub
kernel: IOC: zx1 2.3 HPA 0xfed01000 IOVA space 1024Mb at 0x40000000
kernel: NetLabel: Initializing
kernel: NetLabel: domain hash size = 128
kernel: NetLabel: protocols = UNLABELED CIPSOv4
kernel: NetLabel: unlabeled traffic allowed by default
kernel: NET: Registered protocol family 2
kernel: IP route cache hash table entries: 262144 (order: 7, 2097152 bytes)
kernel: TCP established hash table entries: 1048576 (order: 10, 16777216 bytes)
kernel: TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
kernel: TCP: Hash tables configured (established 1048576 bind 65536)
kernel: TCP reno registered
kernel: perfmon: version 2.0 IRQ 238
kernel: perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
kernel: PAL Information Facility v0.5
kernel: perfmon: added sampling format default_format
kernel: perfmon_default_smpl: default_format v2.0 registered
kernel: audit: initializing netlink socket (disabled)
kernel: type=2000 audit(1317827233.157:1): initialized
kernel: Total HugeTLB memory allocated, 0
kernel: VFS: Disk quotas dquot_6.5.1
kernel: Dquot-cache hash table entries: 2048 (order 0, 16384 bytes)
kernel: Initializing Cryptographic API
kernel: alg: No test for crc32c (crc32c-generic)
kernel: ksign: Installing public key data
kernel: Loading keyring
kernel: — Added public key 9B6C3F09471930AE
kernel: — User ID: Red Hat, Inc. (Kernel Module GPG key)
kernel: io scheduler noop registered
kernel: io scheduler anticipatory registered
kernel: io scheduler deadline registered
kernel: io scheduler cfq registered (default)
kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
kernel: ACPI: Thermal Zone [THM0] (27 C)
kernel: EFI Time Services Driver v0.4
kernel: Linux agpgart interface v0.101 (c) Dave Jones
kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 16 ports, IRQ sharing enabled
kernel: 00:04: ttyS0 at MMIO 0xff5e0000 (irq = 49) is a 16550A
kernel: 00:05: ttyS1 at MMIO 0xff5e2000 (irq = 50) is a 16550A
kernel: GSI 82 (level, low) -> CPU 1 (0x0100) vector 51
kernel: ACPI: PCI Interrupt 0000:e0:01.0[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.0: ttyS2 at MMIO 0xf4051000 (irq = 51) is a 16550A
kernel: ACPI: PCI Interrupt 0000:e0:01.1[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.1: ttyS3 at MMIO 0xf4050000 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS4 at MMIO 0xf4050010 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS5 at MMIO 0xf4050038 (irq = 51) is a 16550A
kernel: brd: module loaded
kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
kernel: CMD649: IDE controller at PCI slot 0000:00:02.0
kernel: GSI 21 (level, low) -> CPU 0 (0x0000) vector 52
kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 52
kernel: CMD649: chipset revision 2
kernel: CMD649: 100% native mode on irq 52
kernel: ide0: BM-DMA at 0x0d40-0x0d47, BIOS settings: hda:pio, hdb:pio
kernel: ide1: BM-DMA at 0x0d48-0x0d4f, BIOS settings: hdc:pio, hdd:pio
kernel: hda: DW-224E, ATAPI CD/DVD-ROM drive
kernel: ide0 at 0xd58-0xd5f,0xd66 on irq 52
kernel: ide-floppy driver 0.99.newide
kernel: usbcore: registered new driver hiddev
kernel: usbcore: registered new driver usbhid
kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
kernel: mice: PS/2 mouse device common for all mice
kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
kernel: md: bitmap version 4.39
kernel: EFI Variables Facility v0.08 2004-May-17
kernel: TCP bic registered
kernel: Initializing IPsec netlink socket
kernel: NET: Registered protocol family 1
kernel: NET: Registered protocol family 17
kernel: Adding console on ttyS3 at MMIO 0xf4050000 (options ‘9600n8’)
kernel: Initalizing network drop monitor service
kernel: Freeing unused kernel memory: 464kB freed
kernel: GSI 18 (level, low) -> CPU 1 (0x0100) vector 53
kernel: ACPI: PCI Interrupt 0000:00:01.2[C] -> GSI 18 (level, low) -> IRQ 53
kernel: ehci_hcd 0000:00:01.2: EHCI Host Controller
kernel: ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
kernel: ehci_hcd 0000:00:01.2: irq 53, io mem 0x80021000
kernel: ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
kernel: usb usb1: configuration #1 chosen from 1 choice
kernel: hub 1-0:1.0: USB hub found
kernel: hub 1-0:1.0: 5 ports detected
kernel: GSI 16 (level, low) -> CPU 0 (0x0000) vector 54
kernel: ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 54
kernel: ohci_hcd 0000:00:01.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
kernel: ohci_hcd 0000:00:01.0: irq 54, io mem 0x80023000
kernel: usb usb2: configuration #1 chosen from 1 choice
kernel: hub 2-0:1.0: USB hub found
kernel: hub 2-0:1.0: 3 ports detected
kernel: GSI 17 (level, low) -> CPU 1 (0x0100) vector 55
kernel: ACPI: PCI Interrupt 0000:00:01.1[B] -> GSI 17 (level, low) -> IRQ 55
kernel: ohci_hcd 0000:00:01.1: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
kernel: ohci_hcd 0000:00:01.1: irq 55, io mem 0x80022000
kernel: usb usb3: configuration #1 chosen from 1 choice
kernel: hub 3-0:1.0: USB hub found
kernel: hub 3-0:1.0: 2 ports detected
kernel: USB Universal Host Controller Interface driver v3.0
kernel: SCSI subsystem initialized
kernel: Fusion MPT base driver 3.04.18rh
kernel: Copyright (c) 1999-2008 LSI Corporation
kernel: Fusion MPT SPI Host driver 3.04.18rh
kernel: GSI 27 (level, low) -> CPU 0 (0x0000) vector 56
kernel: ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 27 (level, low) -> IRQ 56
kernel: mptbase: ioc0: Initiating bringup
kernel: ioc0: LSI53C1030 B2: Capabilities=
kernel: scsi0 : ioc0: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=56
kernel: Vendor: HP 73.4G Model: ST373454LC Rev: HPC2
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: target0:0:0: Beginning Domain Validation
kernel: target0:0:0: Ending Domain Validation
kernel: target0:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI WRFLOW PCOMP (6.25 ns, offset 63)
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel: sda: sda1 sda2
kernel: sd 0:0:0:0: Attached scsi disk sda
kernel: GSI 28 (level, low) -> CPU 1 (0x0100) vector 57
kernel: ACPI: PCI Interrupt 0000:20:01.1[B] -> GSI 28 (level, low) -> IRQ 57
kernel: mptbase: ioc1: Initiating bringup
kernel: ioc1: LSI53C1030 B2: Capabilities=
kernel: scsi1 : ioc1: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=57
kernel: device-mapper: uevent: version 1.0.3
kernel: device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com
kernel: device-mapper: dm-raid45: initialized v0.2594l
kernel: kjournald starting. Commit interval 5 seconds
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: SELinux: Disabled at runtime.
hidd[1995]: Bluetooth HID daemon
kernel: type=1404 audit(1317827269.314:2): selinux=0 auid=4294967295 ses=4294967295
kernel: tg3.c:v3.116 (December 3, 2010) GSI 29 (level, low) -> CPU 0 (0x0000) vector 58
kernel: ACPI: PCI Interrupt 0000:20:02.0[A] -> GSI 29 (level, low) -> IRQ 58
kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k3-1-NAPI
kernel: e100: Copyright(c) 1999-2005 Intel Corporation
kernel: GSI 20 (level, low) -> CPU 1 (0x0100) vector 59
kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 59
kernel: e100: eth0: e100_probe: addr 0x80020000, irq 59, MAC addr 00:11:0A:dd:ee:ff
kernel: hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1658kB Cache, UDMA(33)
kernel: Uniform CD-ROM driver Revision: 3.20
kernel: Intel(R) PRO/1000 Network Driver — version 7.3.21-k4-3-NAPI
kernel: Copyright (c) 1999-2006 Intel Corporation.
kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
kernel: tg3 0000:20:02.0: eth1: eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:11:0a:aa:bb:cc
kernel: tg3 0000:20:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[0]
kernel: tg3 0000:20:02.0: eth1: dma_rwctrl[76ff2d0f] dma_mask[64-bit]
kernel: GSI 60 (level, low) -> CPU 0 (0x0000) vector 60
kernel: ACPI: PCI Interrupt 0000:80:01.0[A] -> GSI 60 (level, low) -> IRQ 60
kernel: e1000: 0000:80:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:1b:21:xx:yy:zz
kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
kernel: lp: driver loaded but no devices found
kernel: ACPI: Power Button (FF) [PWRF]
kernel: ACPI: Sleep Button (FF) [SLPF]
kernel: ACPI: Mapper loaded
kernel: md: Autodetecting RAID arrays.
kernel: md: autorun .
kernel: md: . autorun DONE.
kernel: device-mapper: multipath: version 1.0.6 loaded
kernel: loop: loaded (max 8 devices)
kernel: EXT3 FS on dm-0, internal journal
kernel: Adding 8224736k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1 across:8224736k
kernel: Loading iSCSI transport class v2.0-871.
kernel: 802.1Q VLAN Support v1.8 Ben Greear
kernel: All bugs added by David S. Miller
kernel: libcxgbi:libcxgbi_init_module: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
kernel: libcxgbi:ddp_setup_host_page_size: system PAGE 16384, ddp idx 2.
kernel: Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010)
kernel: iscsi: registered transport (cxgb3i)
kernel: NET: Registered protocol family 10
kernel: lo: Disabled Privacy Extensions
kernel: IPv6 over IPv4 tunneling driver
kernel: cnic: Broadcom NetXtreme II CNIC Driver cnic v2.2.13 (Jan 31, 2011)
kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.6.2.3 (Dec 31, 2010)
kernel: iscsi: registered transport (bnx2i)
kernel: iscsi: registered transport (tcp)
kernel: iscsi: registered transport (iser)
kernel: iscsi: registered transport (be2iscsi)
kernel: 8021q: adding VLAN 0 to HW filter on device eth0
kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
kernel: Bluetooth: Core ver 2.10
kernel: NET: Registered protocol family 31
kernel: Bluetooth: HCI device and connection manager initialized
kernel: Bluetooth: HCI socket layer initialized
kernel: Bluetooth: L2CAP ver 2.8
kernel: Bluetooth: L2CAP socket layer initialized
kernel: Bluetooth: RFCOMM socket layer initialized
kernel: Bluetooth: RFCOMM TTY layer initialized
kernel: Bluetooth: RFCOMM ver 1.8
kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
automount[2025]: lookup_read_master: lookup(nisplus): couldn’t locate nis+ table auto.master
hpiod: 1.6.7 accepting connections at 2208.
xinetd[2082]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
xinetd[2082]: Started working: 0 available services
gpm[2118]: *** info [startup.c(95)]:
gpm[2118]: Started gpm successfully. Entered daemon mode.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd[2213]: Red Hat Network Services Daemon starting up.
avahi-daemon[2231]: Found user ‘avahi’ (UID 70) and group ‘avahi’ (GID 70).
avahi-daemon[2231]: Successfully dropped root privileges.
avahi-daemon[2231]: avahi-daemon 0.6.16 starting up.
avahi-daemon[2231]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
avahi-daemon[2231]: Successfully called chroot().
avahi-daemon[2231]: Successfully dropped remaining capabilities.
avahi-daemon[2231]: No service found in /etc/avahi/services.
avahi-daemon[2231]: Network interface enumeration completed.
avahi-daemon[2231]: Registering HINFO record with values ‘IA64’/’LINUX’.
avahi-daemon[2231]: Server startup complete. Host name is ccswall.local. Local service cookie is 3037389712.
smartd[2251]: smartd version 5.38 [ia64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
smartd[2251]: Home page is http://smartmontools.sourceforge.net/
smartd[2251]: Opened configuration file /etc/smartd.conf
smartd[2251]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
smartd[2251]: Device: /dev/hda, opened
smartd[2251]: Device: /dev/hda, packet devices [this device CD/DVD] not SMART capable
smartd[2251]: Device: /dev/sda, opened
smartd[2251]: Device: /dev/sda, is SMART capable. Adding to «monitor» list.
smartd[2251]: Monitoring 0 ATA and 1 SCSI devices
smartd[2253]: smartd has fork()ed into background mode. New PID=2253.
pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found

# PCI-X 1000Base-LX
# Intel PRO/1000 MF Server Adapter — Model PWLA9490LX
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:1b:21:xx:yy:zz

# Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:11:0a:aa:bb:cc

# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth2
HWADDR=00:11:0a:dd:ee:ff
ONBOOT=no
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.100.200
GATEWAY=192.168.100.254
TYPE=Ethernet

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:21:XX:YY:ZZ
UP 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)

eth1 Link encap:Ethernet HWaddr 00:11:0A:AA:BB:CC
UP 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:58 Memory:90800000-90810000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8540 (8.3 KiB) TX bytes:8540 (8.3 KiB)

# ifconfig eth0 down
# ifconfig eth0 up
# ifdown eth0
# ifup eth0
RTNETLINK answers: No such device
#
# ifconfig eth1 down
# ifconfig eth1 up
# ifdown eth1
# ifup eth1
RTNETLINK answers: No such device
#
# udevinfo -a -p /sys/class/net/eth0

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at parent device ‘/devices/pci0000:80/0000:80:01.0’:
/> BUS==»pci»
DRIVER==»e1000″
SYSFS==»0″
SYSFS==»1″
SYSFS==»pci:v00008086d00001027sv00008086sd00001002bc02sc00i00″
SYSFS==»60″
SYSFS==»0x020000″
SYSFS==»0x1002″
SYSFS==»0x8086″
SYSFS==»0x1027″
SYSFS==»0x8086″

looking at parent device ‘/devices/pci0000:80’:
/> BUS==»»
DRIVER==»»

# udevinfo -a -p /sys/class/net/eth1

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at parent device ‘/devices/pci0000:20/0000:20:02.0’:
/> BUS==»pci»
DRIVER==»tg3″
SYSFS==»0″
SYSFS==»1″
SYSFS==»pci:v000014E4d00001645sv0000103Csd000012A4bc02sc00i00″
SYSFS==»58″
SYSFS==»0x020000″
SYSFS==»0x12a4″
SYSFS==»0x103c»
SYSFS==»0x1645″
SYSFS==»0x14e4″

looking at parent device ‘/devices/pci0000:20’:
/> BUS==»»
DRIVER==»»

# udevinfo -a -p /sys/class/net/eth2

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at parent device ‘/devices/pci0000:00/0000:00:03.0’:
/> BUS==»pci»
DRIVER==»e100″
SYSFS==»0″
SYSFS==»1″
SYSFS==»pci:v00008086d00001229sv0000103Csd00001274bc02sc00i00″
SYSFS==»59″
SYSFS==»0x020000″
SYSFS==»0x1274″
SYSFS==»0x103c»
SYSFS==»0x1229″
SYSFS==»0x8086″

looking at parent device ‘/devices/pci0000:00’:
/> BUS==»»
DRIVER==»»

Источник

Hello everyone,
This is my first post so I apologize if I put it in the wrong category or if I’m providing too much/little information with respect to what is needed.

I’m using a Lenovo Thinkpad T495, installed using the normal procedure written in the wiki, in dual boot with windows 10.
I recently noticed that whenever i plug in the ethernet cable with the computer already booted up it doesn’t connect to the network, but only while I’m using the battery as power source.
As soon as i connect the pc to the external power the network is detected and it connects to the network.
I’m also able to access the wired network if i boot the laptop with the ethernet cable already inserted (with or without battery).
Removing external power while the PC is connected to the network leaves the connection up (that is, until i disconnect the ethernet and plug it again, then I’m back in the first case).

What is very strange to me is that the NIC actually connects to the network when I plug in the cable: LEDs on the switch (to which the pc is connected) lights up and signal not only a connection, but that is is 100Mb/s.
This means that my pc recognized the link to be 100Mb/s capable! (yes, unfortunately I don’t have a gigabit LAN)
This happens even though the LEDs on the PC’s card remain off.

I tried looking for solutions on T495 and Ethernet wiki page but found nothing that seems relatable to me.
In particular, I think I’m not affected by the «Realtek no link / WOL problem» because the nic works sometimes without windows intervention, and not «until windows boots up», and the card’s LED turns on at POST time.

I tried also looking into the system logs (linked below) to see if I could find the source of the problem and maybe that lead to something: at a certain point there’s a «r8169 … : can’t disable ASPM; OS doesn’t have ASPM control» warning.
I searched for «ASPM r8169» and found a this AUR package which however prints an error while installing it (it seems it was created for an older kernel and not updated since 2018).
The pacman output is:

...
==> dkms install r8169_aspm/v4.15.3 -k 5.6.15-arch1-1
Error! Bad return status for module build on kernel: 5.6.15-arch1-1 (x86_64)
Consult /var/lib/dkms/r8169_aspm/v4.15.3/build/make.log for more information.
==> Warning, `dkms install r8169_aspm/v4.15.3 -k 5.6.15-arch1-1' returned 10

After a reboot, ethernet cards simply won’t show anymore and I could only use wifi.

Other possibly useful outputs:
lspci -v (only ethernet portions: this pc has another nic that would be used if i had a docking station)

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0e)
        Subsystem: Lenovo Device 5125
        Flags: bus master, fast devsel, latency 0, IRQ 74, IOMMU group 12
        I/O ports at 3400 [size=256]
        Memory at d0814000 (64-bit, non-prefetchable) [size=4K]
        Memory at d0800000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [170] Latency Tolerance Reporting
        Capabilities: [178] L1 PM Substates
        Kernel driver in use: r8169
        Kernel modules: r8169

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
        Subsystem: Lenovo Device 5125
        Flags: bus master, fast devsel, latency 0, IRQ 77, IOMMU group 13
        I/O ports at 2000 [size=256]
        Memory at d0704000 (64-bit, non-prefetchable) [size=4K]
        Memory at d0700000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
        Capabilities: [170] Latency Tolerance Reporting
        Capabilities: [178] L1 PM Substates
        Kernel driver in use: r8169
        Kernel modules: r8169

ip link while the network cable is connected, but not the power chord

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether f8:75:a4:4a:ae:82 brd ff:ff:ff:ff:ff:ff
3: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether f8:75:a4:4a:ae:81 brd ff:ff:ff:ff:ff:ff
4: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 28:7f:cf:80:e0:e4 brd ff:ff:ff:ff:ff:ff

journald -b output when ethernet is connected before boot
https://gist.github.com/c21c8601832a861 … 592a07c78e

journald -b output when ethernet is connected after ~1m after boot end (circa 02:36), then I wait ~1m and then connect the laptop to power
https://gist.github.com/aefd81e8f689c6d … df9ca11d28

EDIT: corrected ip output

Last edited by quagmire (2020-11-10 00:23:39)

I’ve encountered this issue right after I added an OVS bridge in the node.

[root@k8s-master ovs]# kubectl logs -n kube-system weave-net-6rvnc weave
DEBU: 2020/06/23 09:07:39.512668 [kube-peers] Checking peer "de:c6:c1:c7:23:60" against list &{[{06:d9:54:a4:97:cf k8s-master} {de:c6:c1:c7:23:60 k8s-worker-2} {ea:84:4e:3c:35:f8 k8s-worker-1}]}
INFO: 2020/06/23 09:07:39.547342 Command line options: map[conn-limit:200 datapath:datapath db-prefix:/weavedb/weave-net docker-api: expect-npc:true host-root:/host http-addr:127.0.0.1:6784 ipalloc-init:consensus=2 ipalloc-range:10.32.0.0/12 metrics-addr:0.0.0.0:6782 name:de:c6:c1:c7:23:60 nickname:k8s-worker-2 no-dns:true port:6783]
INFO: 2020/06/23 09:07:39.547836 weave  2.6.5
INFO: 2020/06/23 09:07:39.717269 Bridge type is bridged_fastdp
INFO: 2020/06/23 09:07:39.717284 Communication between peers is unencrypted.
INFO: 2020/06/23 09:07:39.738006 Our name is de:c6:c1:c7:23:60(k8s-worker-2)
INFO: 2020/06/23 09:07:39.738039 Launch detected - using supplied peer list: [192.168.2.100 192.168.2.101]
INFO: 2020/06/23 09:07:39.754916 Checking for pre-existing addresses on weave bridge
INFO: 2020/06/23 09:07:39.764297 [allocator de:c6:c1:c7:23:60] Initialising with persisted data
INFO: 2020/06/23 09:07:39.764391 Sniffing traffic on datapath (via ODP)
INFO: 2020/06/23 09:07:39.774026 ->[192.168.2.100:6783] attempting connection
INFO: 2020/06/23 09:07:39.774295 ->[192.168.2.101:6783] attempting connection
INFO: 2020/06/23 09:07:39.788978 Listening for HTTP control messages on 127.0.0.1:6784
INFO: 2020/06/23 09:07:39.789191 Listening for metrics requests on 0.0.0.0:6782
INFO: 2020/06/23 09:07:39.800015 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:07:39.800067 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using fastdp
INFO: 2020/06/23 09:07:39.800092 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection added (new peer)
INFO: 2020/06/23 09:07:39.803155 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:07:39.803215 overlay_switch ->[06:d9:54:a4:97:cf(k8s-master)] using fastdp
INFO: 2020/06/23 09:07:39.803231 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection added (new peer)
INFO: 2020/06/23 09:07:40.613272 [kube-peers] Added myself to peer list &{[{06:d9:54:a4:97:cf k8s-master} {de:c6:c1:c7:23:60 k8s-worker-2} {ea:84:4e:3c:35:f8 k8s-worker-1}]}
DEBU: 2020/06/23 09:07:40.620769 [kube-peers] Nodes that have disappeared: map[]
10.44.0.0
DEBU: 2020/06/23 09:07:40.688427 registering for updates for node delete events
INFO: 2020/06/23 09:08:09.821129 Error checking version: Get https://checkpoint-api.weave.works/v1/check/weave-net?arch=amd64&flag_docker-version=none&flag_kernel-version=4.18.0-147.8.1.el8_1.x86_64&flag_kubernetes-cluster-size=2&flag_kubernetes-cluster-uid=0087fabb-3f55-443a-b07c-4d799ed61e47&flag_kubernetes-version=v1.18.4&flag_network=fastdp&flag_network=fastdp&os=linux&signature=3pT3IQVQhnTj9930uSeDSIcsF%2F1RDuvt%2Bh23Mnmtww0%3D&version=2.6.5: dial tcp: i/o timeout
INFO: 2020/06/23 09:08:39.800601 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using sleeve
INFO: 2020/06/23 09:08:39.802173 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection shutting down due to error: read tcp 192.168.2.102:39071->192.168.2.101:6783: read: connection reset by peer
INFO: 2020/06/23 09:08:39.802282 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection deleted
INFO: 2020/06/23 09:08:39.802341 ->[192.168.2.101:6783] attempting connection
INFO: 2020/06/23 09:08:39.802566 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection shutting down due to error: read tcp 192.168.2.102:44641->192.168.2.100:6783: read: connection reset by peer
INFO: 2020/06/23 09:08:39.802764 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection deleted
INFO: 2020/06/23 09:08:39.802785 Removed unreachable peer ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 09:08:39.802791 Removed unreachable peer 06:d9:54:a4:97:cf(k8s-master)
INFO: 2020/06/23 09:08:39.803011 ->[192.168.2.100:6783] attempting connection
INFO: 2020/06/23 09:08:39.803203 ->[192.168.2.101:58195] connection accepted
INFO: 2020/06/23 09:08:39.803262 ->[192.168.2.100:50043] connection accepted
INFO: 2020/06/23 09:08:39.803671 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:08:39.803712 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using fastdp
INFO: 2020/06/23 09:08:39.803729 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection added (new peer)
INFO: 2020/06/23 09:08:39.804339 ->[192.168.2.101:58195|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:08:39.804375 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using fastdp
INFO: 2020/06/23 09:08:39.804418 ->[192.168.2.101:58195|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection shutting down due to error: Multiple connections to ea:84:4e:3c:35:f8(k8s-worker-1) added to de:c6:c1:c7:23:60(k8s-worker-2)
INFO: 2020/06/23 09:08:39.804521 ->[192.168.2.100:50043|06:d9:54:a4:97:cf(k8s-master)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:08:39.804544 overlay_switch ->[06:d9:54:a4:97:cf(k8s-master)] using fastdp
INFO: 2020/06/23 09:08:39.804554 ->[192.168.2.100:50043|06:d9:54:a4:97:cf(k8s-master)]: connection added (new peer)
INFO: 2020/06/23 09:08:39.806343 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:08:39.806459 overlay_switch ->[06:d9:54:a4:97:cf(k8s-master)] using fastdp
INFO: 2020/06/23 09:08:39.806482 ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: connection shutting down due to error: Multiple connections to 06:d9:54:a4:97:cf(k8s-master) added to de:c6:c1:c7:23:60(k8s-worker-2)
INFO: 2020/06/23 09:08:39.903918 overlay_switch ->[06:d9:54:a4:97:cf(k8s-master)] using sleeve
INFO: 2020/06/23 09:08:39.903938 ->[192.168.2.100:50043|06:d9:54:a4:97:cf(k8s-master)]: connection fully established
INFO: 2020/06/23 09:08:39.907019 sleeve ->[192.168.2.100:6783|06:d9:54:a4:97:cf(k8s-master)]: Effective MTU verified at 1438
INFO: 2020/06/23 09:09:16.528899 Discovered remote MAC da:33:ea:ca:21:80 at 06:d9:54:a4:97:cf(k8s-master)
INFO: 2020/06/23 09:09:30.237420 Discovered remote MAC ca:54:a2:11:fe:65 at ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 09:09:39.806303 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using sleeve
INFO: 2020/06/23 09:09:39.806935 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] sleeve timed out waiting for UDP heartbeat
INFO: 2020/06/23 09:09:39.807479 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection shutting down due to error: no working forwarders to ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 09:09:39.808463 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection deleted
INFO: 2020/06/23 09:09:39.809034 ->[192.168.2.101:6783] attempting connection
INFO: 2020/06/23 09:09:39.811663 ->[192.168.2.101:55721] connection accepted
INFO: 2020/06/23 09:09:39.814335 ->[192.168.2.101:55721|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:09:39.814382 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using fastdp
INFO: 2020/06/23 09:09:39.814396 ->[192.168.2.101:55721|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection added
INFO: 2020/06/23 09:09:39.814409 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection ready; using protocol version 2
INFO: 2020/06/23 09:09:39.814471 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using fastdp
INFO: 2020/06/23 09:09:39.814485 ->[192.168.2.101:55721|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection deleted
INFO: 2020/06/23 09:09:39.814495 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection added
INFO: 2020/06/23 09:09:39.814534 ->[192.168.2.101:55721|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection shutting down due to error: Multiple connections to ea:84:4e:3c:35:f8(k8s-worker-1) added to de:c6:c1:c7:23:60(k8s-worker-2)
INFO: 2020/06/23 09:09:39.815898 overlay_switch ->[ea:84:4e:3c:35:f8(k8s-worker-1)] using sleeve
INFO: 2020/06/23 09:09:39.816501 ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: connection fully established
INFO: 2020/06/23 09:09:39.817494 sleeve ->[192.168.2.101:6783|ea:84:4e:3c:35:f8(k8s-worker-1)]: Effective MTU verified at 1438
INFO: 2020/06/23 09:14:40.628141 Discovered remote MAC a6:ea:1f:01:c3:c8 at ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 09:30:32.615507 Discovered remote MAC a6:ea:1f:01:c3:c8 at ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 09:41:54.416965 Discovered remote MAC da:33:ea:ca:21:80 at 06:d9:54:a4:97:cf(k8s-master)
INFO: 2020/06/23 09:43:38.236619 Discovered remote MAC ca:54:a2:11:fe:65 at ea:84:4e:3c:35:f8(k8s-worker-1)
INFO: 2020/06/23 10:00:27.735771 Discovered remote MAC a6:ea:1f:01:c3:c8 at ea:84:4e:3c:35:f8(k8s-worker-1)
WARN: 2020/06/23 10:07:48.749752 netlink error response: no such device
WARN: 2020/06/23 10:07:48.749807 netlink error response: no such device
netlink reply sequence number mismatch (got 2136, expected 2138)
netlink reply sequence number mismatch (got 2137, expected 2138)
WARN: 2020/06/23 10:07:58.753579 netlink error response: no such device
WARN: 2020/06/23 10:07:58.753611 netlink error response: no such device
netlink reply sequence number mismatch (got 2140, expected 2142)
netlink reply sequence number mismatch (got 2141, expected 2142)
WARN: 2020/06/23 10:08:08.753870 netlink error response: no such device
WARN: 2020/06/23 10:08:08.753923 netlink error response: no such device
netlink reply sequence number mismatch (got 2144, expected 2146)
netlink reply sequence number mismatch (got 2145, expected 2146)
WARN: 2020/06/23 10:08:18.750554 netlink error response: no such device
WARN: 2020/06/23 10:08:18.750588 netlink error response: no such device
netlink reply sequence number mismatch (got 2148, expected 2150)
netlink reply sequence number mismatch (got 2149, expected 2150)
WARN: 2020/06/23 10:08:28.750769 netlink error response: no such device
WARN: 2020/06/23 10:08:28.750804 netlink error response: no such device
netlink reply sequence number mismatch (got 2152, expected 2154)
netlink reply sequence number mismatch (got 2153, expected 2154)
WARN: 2020/06/23 10:08:38.750652 netlink error response: no such device
WARN: 2020/06/23 10:08:38.750804 netlink error response: no such device
netlink reply sequence number mismatch (got 2156, expected 2158)
netlink reply sequence number mismatch (got 2157, expected 2158)
WARN: 2020/06/23 10:08:48.751797 netlink error response: no such device
WARN: 2020/06/23 10:08:48.751849 netlink error response: no such device
WARN: 2020/06/23 10:08:58.753117 netlink error response: no such device
WARN: 2020/06/23 10:08:58.753173 netlink error response: no such device
netlink reply sequence number mismatch (got 2160, expected 2162)
netlink reply sequence number mismatch (got 2161, expected 2162)
netlink reply sequence number mismatch (got 2164, expected 2166)
netlink reply sequence number mismatch (got 2165, expected 2166)
WARN: 2020/06/23 10:09:08.749413 netlink error response: no such device
WARN: 2020/06/23 10:09:08.749429 netlink error response: no such device
netlink reply sequence number mismatch (got 2168, expected 2170)
netlink reply sequence number mismatch (got 2169, expected 2170)
WARN: 2020/06/23 10:09:18.750154 netlink error response: no such device
WARN: 2020/06/23 10:09:18.750175 netlink error response: no such device
WARN: 2020/06/23 10:09:28.749662 netlink error response: no such device
WARN: 2020/06/23 10:09:28.749682 netlink error response: no such device
netlink reply sequence number mismatch (got 2172, expected 2174)
netlink reply sequence number mismatch (got 2173, expected 2174)
netlink reply sequence number mismatch (got 2176, expected 2178)
netlink reply sequence number mismatch (got 2177, expected 2178)
WARN: 2020/06/23 10:09:38.751628 netlink error response: no such device
WARN: 2020/06/23 10:09:38.751671 netlink error response: no such device
netlink reply sequence number mismatch (got 2180, expected 2182)
netlink reply sequence number mismatch (got 2181, expected 2182)
WARN: 2020/06/23 10:09:48.757421 netlink error response: no such device
WARN: 2020/06/23 10:09:48.757466 netlink error response: no such device
netlink reply sequence number mismatch (got 2184, expected 2186)
netlink reply sequence number mismatch (got 2185, expected 2186)
WARN: 2020/06/23 10:09:58.750237 netlink error response: no such device
WARN: 2020/06/23 10:09:58.750266 netlink error response: no such device
netlink reply sequence number mismatch (got 2188, expected 2190)
netlink reply sequence number mismatch (got 2189, expected 2190)
WARN: 2020/06/23 10:10:08.749239 netlink error response: no such device
WARN: 2020/06/23 10:10:08.749253 netlink error response: no such device
netlink reply sequence number mismatch (got 2192, expected 2194)
netlink reply sequence number mismatch (got 2193, expected 2194)
WARN: 2020/06/23 10:10:18.749614 netlink error response: no such device
WARN: 2020/06/23 10:10:18.749654 netlink error response: no such device
netlink reply sequence number mismatch (got 2196, expected 2198)
netlink reply sequence number mismatch (got 2197, expected 2198)
WARN: 2020/06/23 10:10:28.749492 netlink error response: no such device
WARN: 2020/06/23 10:10:28.749511 netlink error response: no such device
netlink reply sequence number mismatch (got 2200, expected 2202)
netlink reply sequence number mismatch (got 2201, expected 2202)
WARN: 2020/06/23 10:10:38.750147 netlink error response: no such device
WARN: 2020/06/23 10:10:38.750181 netlink error response: no such device
netlink reply sequence number mismatch (got 2204, expected 2206)
netlink reply sequence number mismatch (got 2205, expected 2206)
WARN: 2020/06/23 10:10:48.750843 netlink error response: no such device
WARN: 2020/06/23 10:10:48.750873 netlink error response: no such device
WARN: 2020/06/23 10:10:58.751113 netlink error response: no such device
netlink reply sequence number mismatch (got 2208, expected 2210)
netlink reply sequence number mismatch (got 2209, expected 2210)
WARN: 2020/06/23 10:10:58.751296 netlink error response: no such device
WARN: 2020/06/23 10:11:08.751714 netlink error response: no such device
WARN: 2020/06/23 10:11:08.751729 netlink error response: no such device
netlink reply sequence number mismatch (got 2212, expected 2214)
netlink reply sequence number mismatch (got 2213, expected 2214)
netlink reply sequence number mismatch (got 2216, expected 2218)
netlink reply sequence number mismatch (got 2217, expected 2218)
WARN: 2020/06/23 10:11:18.750696 netlink error response: no such device
WARN: 2020/06/23 10:11:18.750744 netlink error response: no such device

Could anybody help me on this one? Thank you very much.
I’ve also posted an issue regarding this error in #3822.

Hello All,

I’m a struggling RHEL noob trying to configure network interfaces for use as a bridging firewall.  I am using RHEL 5.6 for IA-64 on an HP Integrity RX-2600.  Previously, I had the network interfaces configured successfully, but after a PCI card shuffle, I started getting RTNETLINK messages.  The original PCI configuration had a PCI-X to PCI bridge adapter in slot 1, and a 1000Base-LX adapter in slot 4.  I removed the bridge adapter, and put the 1000Base-LX adapter in its place.  Then, RTNETLINK complaints arose.  I tried removing the network adapter, booted up, and then shutdown.  Next, I reinstalled the network adapter, and booted up again, but no luck.

Any light that can be shed upon this problem will be greatly appreciated.

—— BEGIN console boot messages ——

Loading.: Red Hat Enterprise Linux Server                           
Starting: Red Hat Enterprise Linux Server

ELILO boot: Uncompressing Linux… done
Loading file initrd-2.6.18-274.3.1.el5.img…done
Linux version 2.6.18-274.3.1.el5 (mockbuild@natasha.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Aug 26 18:48:23 EDT 2011
EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
booting generic kernel on platform hpzx1
PCDP: v0 at 0x3fb2c000
Early serial console at MMIO 0xf4050000 (options ‘9600n8’)
rsvd_region[0]: [0xe000000001000000, 0xe0000000010000a8)
rsvd_region[1]: [0xe000000004000000, 0xe000000004e94e68)
rsvd_region[2]: [0xe0000040fea40008, 0xe0000040fea40058)
rsvd_region[3]: [0xe0000040fea43fa4, 0xe0000040fea44008)
rsvd_region[4]: [0xe0000040fea46000, 0xe0000040fef95b16)
rsvd_region[5]: [0xe0000040fef9c008, 0xe0000040fef9c6c8)
rsvd_region[6]: [0xffffffffffffffff, 0xffffffffffffffff)
Initial ramdisk at: 0xe0000040fea46000 (5569302 bytes)
SAL 3.1: HP version 2.31
SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
No logical to physical processor mapping available
cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
ACPI: Local APIC address c0000000fee00000
GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
2 CPUs available, 2 CPUs total
MCA related initialization done
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists.  Total pages: 390218
Kernel command line: BOOT_IMAGE=scsi0:EFIredhatvmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00  rhgb quiet ro
Red Hat nash version 5.1.19.6 starting
  Reading all physical volumes.  This may take a while…
  Found volume group «VolGroup00» using metadata type lvm2
  Internal error: Maps lock 14778368 < unlock 14794752
  Internal error: Maps lock 14860288 < unlock 14876672
  2 logical volume(s) in volume group «VolGroup00» now active
                Welcome to Red Hat Enterprise Linux Server
                Press ‘I’ to enter interactive startup.
Setting clock  (utc): Wed Oct  5 08:07:51 PDT 2011 [  OK  ]
Starting udev: [  OK  ]
Loading default keymap (us): [  OK  ]
Setting hostname ccswall:  [  OK  ]
Setting up Logical Volume Management:   /dev/hda: open failed: No medium found
  2 logical volume(s) in volume group «VolGroup00» now active
[  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) — /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 130716/15844224 files, 1474192/15835136 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
INIT: Entering runlevel: 5
Entering non-interactive startup
Starting background readahead: [  OK  ]
Checking for hardware changes [  OK  ]
[  OK  ] iSCSI daemon: [  OK  ]
[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  RTNETLINK answers: No such device
[  OK  ]
Bringing up interface eth1:  RTNETLINK answers: No such device
[  OK  ]
Starting auditd: [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting irqbalance: [  OK  ]
iscsid (pid  1447) is running…
Setting up iSCSI targets: iscsiadm: No records found
[  OK  ]
Starting portmap: [  OK  ]
Starting NFS statd: [  OK  ]
Starting RPC idmapd: [  OK  ]
Starting system message bus: [  OK  ]
[  OK  ] Bluetooth services:[  OK  ]
Mounting other filesystems:  [  OK  ]
Starting PC/SC smart card daemon (pcscd): [  OK  ]
Starting acpi daemon: [  OK  ]
Starting HAL daemon: [  OK  ]
Starting hidd: [  OK  ]
Starting monitoring for VG VolGroup00:   /dev/hda: open failed: No medium found
  2 logical volume(s) in volume group «VolGroup00» monitored
[  OK  ]
Starting autofs:  Loading autofs4: [  OK  ]
Starting automount: [  OK  ]
[  OK  ]
Starting hpiod: [  OK  ]
Starting hpssd: [  OK  ]
Starting sshd: [  OK  ]
Starting cups: [  OK  ]
Starting xinetd: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Starting console mouse services: [  OK  ]
Starting crond: [  OK  ]
Starting xfs: [  OK  ]
Starting anacron: [  OK  ]
[  OK  ] atd: [  OK  ]
Starting salinfo_decode_all: [  OK  ]
Starting background readahead: [  OK  ]
Starting Red Hat Network Daemon: [  OK  ]
Starting yum-updatesd: [  OK  ]
Starting Avahi daemon… [  OK  ]
Starting smartd:
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Kernel 2.6.18-274.3.1.el5 on an ia64

—— END console boot messages ——

—— BEGIN /var/log/messages ——

syslogd 1.4.1: restart.
kernel: klogd 1.4.1, log source = /proc/kmsg started.
kernel: Linux version 2.6.18-274.3.1.el5 (mockbuild@natasha.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Aug 26 18:48:23 EDT 2011
kernel: EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
kernel: booting generic kernel on platform hpzx1
kernel: PCDP: v0 at 0x3fb2c000
kernel: Early serial console at MMIO 0xf4050000 (options ‘9600n8’)
kernel: rsvd_region[0]: [0xe000000001000000, 0xe0000000010000a8)
kernel: rsvd_region[1]: [0xe000000004000000, 0xe000000004e94e68)
kernel: rsvd_region[2]: [0xe0000040fea40008, 0xe0000040fea40058)
kernel: rsvd_region[3]: [0xe0000040fea43fa4, 0xe0000040fea44008)
kernel: rsvd_region[4]: [0xe0000040fea46000, 0xe0000040fef95b16)
kernel: rsvd_region[5]: [0xe0000040fef9c008, 0xe0000040fef9c6c8)
kernel: rsvd_region[6]: [0xffffffffffffffff, 0xffffffffffffffff)
kernel: Initial ramdisk at: 0xe0000040fea46000 (5569302 bytes)
kernel: SAL 3.1: HP version 2.31
kernel: SAL Platform features: None
kernel: SAL: AP wakeup using external interrupt vector 0xff
kernel: No logical to physical processor mapping available
kernel: cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
kernel: ACPI: Local APIC address c0000000fee00000
kernel: GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
kernel: 2 CPUs available, 2 CPUs total
kernel: MCA related initialization done
rpc.statd[1807]: Version 1.0.9 Starting
kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
kernel: Built 1 zonelists.  Total pages: 390218
kernel: Kernel command line: BOOT_IMAGE=scsi0:EFIredhatvmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00  rhgb quiet ro
kernel: PID hash table entries: 4096 (order: 12, 32768 bytes)
kernel: Console: colour VGA+ 80×25
kernel: Memory: 6154992k/6243488k available (6688k code, 108944k reserved, 4001k data, 464k init)
kernel: McKinley Errata 9 workaround not needed; disabling it
kernel: Calibrating delay loop… 2244.60 BogoMIPS (lpj=1122304)
kernel: Security Framework v1.0.0 initialized
kernel: SELinux:  Initializing.
kernel: selinux_register_security:  Registering secondary module capability
kernel: Capability LSM initialized as secondary
kernel: Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
kernel: Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
kernel: Mount-cache hash table entries: 1024
kernel: ACPI: Core revision 20060707
hcid[1865]: Bluetooth HCI daemon
kernel: Boot processor id 0x0/0x0
kernel: cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
kernel: Fixed BSP b0 value from CPU 1
sdpd[1869]: Bluetooth SDP daemon
hcid[1865]: Register path:/org/bluez fallback:1
kernel: CPU 1: synchronized ITC with CPU 0 (last diff -27 cycles, maxerr 681 cycles)
kernel: Calibrating delay loop… 2244.60 BogoMIPS (lpj=1122304)
kernel: Brought up 2 CPUs
kernel: Total of 2 processors activated (4489.21 BogoMIPS).
kernel: migration_cost=6421
kernel: checking if image is initramfs… it is
kernel: Freeing initrd memory: 5424kB freed
pcscd: pcscdaemon.c:507:main() pcsc-lite 1.4.4 daemon ready.
kernel: DMI 2.3 present.
kernel: NET: Registered protocol family 16
kernel: ACPI: bus type pci registered
kernel: ACPI: Interpreter enabled
kernel: ACPI: Using IOSAPIC for interrupt routing
kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
kernel: PCI: Firmware left 0000:00:03.0 e100 interrupts enabled, disabling
kernel: ACPI: PCI Root Bridge [PCI1] (0000:20)
kernel: ACPI: PCI Root Bridge [PCI2] (0000:40)
kernel: ACPI: PCI Root Bridge [PCI3] (0000:60)
kernel: ACPI: PCI Root Bridge [PCI4] (0000:80)
kernel: ACPI: PCI Root Bridge [PCI6] (0000:c0)
pcscd: hotplug_libusb.c:402:HPEstablishUSBNotifications() Driver ifd-egate.bundle does not support IFD_GENERATE_HOTPLUG. Using active polling instead.
pcscd: hotplug_libusb.c:411:HPEstablishUSBNotifications() Polling forced every 1 second(s)
kernel: ACPI: PCI Root Bridge [PCI7] (0000:e0)
kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
kernel: pnp: PnP ACPI init
kernel: GSI 34 (edge, high) -> CPU 1 (0x0100) vector 49
kernel: GSI 35 (edge, high) -> CPU 0 (0x0000) vector 50
kernel: pnp: PnP ACPI: found 11 devices
kernel: usbcore: registered new driver usbfs
kernel: usbcore: registered new driver hub
kernel: IOC: zx1 2.3 HPA 0xfed01000 IOVA space 1024Mb at 0x40000000
kernel: NetLabel: Initializing
kernel: NetLabel:  domain hash size = 128
kernel: NetLabel:  protocols = UNLABELED CIPSOv4
kernel: NetLabel:  unlabeled traffic allowed by default
kernel: NET: Registered protocol family 2
kernel: IP route cache hash table entries: 262144 (order: 7, 2097152 bytes)
kernel: TCP established hash table entries: 1048576 (order: 10, 16777216 bytes)
kernel: TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
kernel: TCP: Hash tables configured (established 1048576 bind 65536)
kernel: TCP reno registered
kernel: perfmon: version 2.0 IRQ 238
kernel: perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
kernel: PAL Information Facility v0.5
kernel: perfmon: added sampling format default_format
kernel: perfmon_default_smpl: default_format v2.0 registered
kernel: audit: initializing netlink socket (disabled)
kernel: type=2000 audit(1317827233.157:1): initialized
kernel: Total HugeTLB memory allocated, 0
kernel: VFS: Disk quotas dquot_6.5.1
kernel: Dquot-cache hash table entries: 2048 (order 0, 16384 bytes)
kernel: Initializing Cryptographic API
kernel: alg: No test for crc32c (crc32c-generic)
kernel: ksign: Installing public key data
kernel: Loading keyring
kernel: — Added public key 9B6C3F09471930AE
kernel: — User ID: Red Hat, Inc. (Kernel Module GPG key)
kernel: io scheduler noop registered
kernel: io scheduler anticipatory registered
kernel: io scheduler deadline registered
kernel: io scheduler cfq registered (default)
kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
kernel: ACPI: Thermal Zone [THM0] (27 C)
kernel: EFI Time Services Driver v0.4
kernel: Linux agpgart interface v0.101 (c) Dave Jones
kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 16 ports, IRQ sharing enabled
kernel: 00:04: ttyS0 at MMIO 0xff5e0000 (irq = 49) is a 16550A
kernel: 00:05: ttyS1 at MMIO 0xff5e2000 (irq = 50) is a 16550A
kernel: GSI 82 (level, low) -> CPU 1 (0x0100) vector 51
kernel: ACPI: PCI Interrupt 0000:e0:01.0[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.0: ttyS2 at MMIO 0xf4051000 (irq = 51) is a 16550A
kernel: ACPI: PCI Interrupt 0000:e0:01.1[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.1: ttyS3 at MMIO 0xf4050000 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS4 at MMIO 0xf4050010 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS5 at MMIO 0xf4050038 (irq = 51) is a 16550A
kernel: brd: module loaded
kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
kernel: CMD649: IDE controller at PCI slot 0000:00:02.0
kernel: GSI 21 (level, low) -> CPU 0 (0x0000) vector 52
kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 52
kernel: CMD649: chipset revision 2
kernel: CMD649: 100% native mode on irq 52
kernel:     ide0: BM-DMA at 0x0d40-0x0d47, BIOS settings: hda:pio, hdb:pio
kernel:     ide1: BM-DMA at 0x0d48-0x0d4f, BIOS settings: hdc:pio, hdd:pio
kernel: hda: DW-224E, ATAPI CD/DVD-ROM drive
kernel: ide0 at 0xd58-0xd5f,0xd66 on irq 52
kernel: ide-floppy driver 0.99.newide
kernel: usbcore: registered new driver hiddev
kernel: usbcore: registered new driver usbhid
kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
kernel: mice: PS/2 mouse device common for all mice
kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
kernel: md: bitmap version 4.39
kernel: EFI Variables Facility v0.08 2004-May-17
kernel: TCP bic registered
kernel: Initializing IPsec netlink socket
kernel: NET: Registered protocol family 1
kernel: NET: Registered protocol family 17
kernel: Adding console on ttyS3 at MMIO 0xf4050000 (options ‘9600n8’)
kernel: Initalizing network drop monitor service
kernel: Freeing unused kernel memory: 464kB freed
kernel: GSI 18 (level, low) -> CPU 1 (0x0100) vector 53
kernel: ACPI: PCI Interrupt 0000:00:01.2[C] -> GSI 18 (level, low) -> IRQ 53
kernel: ehci_hcd 0000:00:01.2: EHCI Host Controller
kernel: ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
kernel: ehci_hcd 0000:00:01.2: irq 53, io mem 0x80021000
kernel: ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
kernel: usb usb1: configuration #1 chosen from 1 choice
kernel: hub 1-0:1.0: USB hub found
kernel: hub 1-0:1.0: 5 ports detected
kernel: GSI 16 (level, low) -> CPU 0 (0x0000) vector 54
kernel: ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 54
kernel: ohci_hcd 0000:00:01.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
kernel: ohci_hcd 0000:00:01.0: irq 54, io mem 0x80023000
kernel: usb usb2: configuration #1 chosen from 1 choice
kernel: hub 2-0:1.0: USB hub found
kernel: hub 2-0:1.0: 3 ports detected
kernel: GSI 17 (level, low) -> CPU 1 (0x0100) vector 55
kernel: ACPI: PCI Interrupt 0000:00:01.1[B] -> GSI 17 (level, low) -> IRQ 55
kernel: ohci_hcd 0000:00:01.1: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
kernel: ohci_hcd 0000:00:01.1: irq 55, io mem 0x80022000
kernel: usb usb3: configuration #1 chosen from 1 choice
kernel: hub 3-0:1.0: USB hub found
kernel: hub 3-0:1.0: 2 ports detected
kernel: USB Universal Host Controller Interface driver v3.0
kernel: SCSI subsystem initialized
kernel: Fusion MPT base driver 3.04.18rh
kernel: Copyright (c) 1999-2008 LSI Corporation
kernel: Fusion MPT SPI Host driver 3.04.18rh
kernel: GSI 27 (level, low) -> CPU 0 (0x0000) vector 56
kernel: ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 27 (level, low) -> IRQ 56
kernel: mptbase: ioc0: Initiating bringup
kernel: ioc0: LSI53C1030 B2: Capabilities={Initiator,Target}
kernel: scsi0 : ioc0: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=56
kernel:   Vendor: HP 73.4G  Model: ST373454LC        Rev: HPC2
kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03
kernel:  target0:0:0: Beginning Domain Validation
kernel:  target0:0:0: Ending Domain Validation
kernel:  target0:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI WRFLOW PCOMP (6.25 ns, offset 63)
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel:  sda: sda1 sda2
kernel: sd 0:0:0:0: Attached scsi disk sda
kernel: GSI 28 (level, low) -> CPU 1 (0x0100) vector 57
kernel: ACPI: PCI Interrupt 0000:20:01.1[B] -> GSI 28 (level, low) -> IRQ 57
kernel: mptbase: ioc1: Initiating bringup
kernel: ioc1: LSI53C1030 B2: Capabilities={Initiator,Target}
kernel: scsi1 : ioc1: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=57
kernel: device-mapper: uevent: version 1.0.3
kernel: device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com
kernel: device-mapper: dm-raid45: initialized v0.2594l
kernel: kjournald starting.  Commit interval 5 seconds
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: SELinux:  Disabled at runtime.
hidd[1995]: Bluetooth HID daemon
kernel: type=1404 audit(1317827269.314:2): selinux=0 auid=4294967295 ses=4294967295
kernel: tg3.c:v3.116 (December 3, 2010)<6>GSI 29 (level, low) -> CPU 0 (0x0000) vector 58
kernel: ACPI: PCI Interrupt 0000:20:02.0[A] -> GSI 29 (level, low) -> IRQ 58
kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k3-1-NAPI
kernel: e100: Copyright(c) 1999-2005 Intel Corporation
kernel: GSI 20 (level, low) -> CPU 1 (0x0100) vector 59
kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 59
kernel: e100: eth0: e100_probe: addr 0x80020000, irq 59, MAC addr 00:11:0A:dd:ee:ff
kernel: hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1658kB Cache, UDMA(33)
kernel: Uniform CD-ROM driver Revision: 3.20
kernel: Intel(R) PRO/1000 Network Driver — version 7.3.21-k4-3-NAPI
kernel: Copyright (c) 1999-2006 Intel Corporation.
kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
kernel: tg3 0000:20:02.0: eth1: eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:11:0a:aa:bb:cc
kernel: tg3 0000:20:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[0]
kernel: tg3 0000:20:02.0: eth1: dma_rwctrl[76ff2d0f] dma_mask[64-bit]
kernel: GSI 60 (level, low) -> CPU 0 (0x0000) vector 60
kernel: ACPI: PCI Interrupt 0000:80:01.0[A] -> GSI 60 (level, low) -> IRQ 60
kernel: e1000: 0000:80:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:1b:21:xx:yy:zz
kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
kernel: lp: driver loaded but no devices found
kernel: ACPI: Power Button (FF) [PWRF]
kernel: ACPI: Sleep Button (FF) [SLPF]
kernel: ACPI: Mapper loaded
kernel: md: Autodetecting RAID arrays.
kernel: md: autorun …
kernel: md: … autorun DONE.
kernel: device-mapper: multipath: version 1.0.6 loaded
kernel: loop: loaded (max 8 devices)
kernel: EXT3 FS on dm-0, internal journal
kernel: Adding 8224736k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1 across:8224736k
kernel: Loading iSCSI transport class v2.0-871.
kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
kernel: All bugs added by David S. Miller <davem@redhat.com>
kernel: libcxgbi:libcxgbi_init_module: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
kernel: libcxgbi:ddp_setup_host_page_size: system PAGE 16384, ddp idx 2.
kernel: Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010)
kernel: iscsi: registered transport (cxgb3i)
kernel: NET: Registered protocol family 10
kernel: lo: Disabled Privacy Extensions
kernel: IPv6 over IPv4 tunneling driver
kernel: cnic: Broadcom NetXtreme II CNIC Driver cnic v2.2.13 (Jan 31, 2011)
kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.6.2.3 (Dec 31, 2010)
kernel: iscsi: registered transport (bnx2i)
kernel: iscsi: registered transport (tcp)
kernel: iscsi: registered transport (iser)
kernel: iscsi: registered transport (be2iscsi)
kernel: 8021q: adding VLAN 0 to HW filter on device eth0
kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
kernel: Bluetooth: Core ver 2.10
kernel: NET: Registered protocol family 31
kernel: Bluetooth: HCI device and connection manager initialized
kernel: Bluetooth: HCI socket layer initialized
kernel: Bluetooth: L2CAP ver 2.8
kernel: Bluetooth: L2CAP socket layer initialized
kernel: Bluetooth: RFCOMM socket layer initialized
kernel: Bluetooth: RFCOMM TTY layer initialized
kernel: Bluetooth: RFCOMM ver 1.8
kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
automount[2025]: lookup_read_master: lookup(nisplus): couldn’t locate nis+ table auto.master
hpiod: 1.6.7 accepting connections at 2208…
xinetd[2082]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
xinetd[2082]: Started working: 0 available services
gpm[2118]: *** info [startup.c(95)]:
gpm[2118]: Started gpm successfully. Entered daemon mode.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd[2213]: Red Hat Network Services Daemon starting up.
avahi-daemon[2231]: Found user ‘avahi’ (UID 70) and group ‘avahi’ (GID 70).
avahi-daemon[2231]: Successfully dropped root privileges.
avahi-daemon[2231]: avahi-daemon 0.6.16 starting up.
avahi-daemon[2231]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
avahi-daemon[2231]: Successfully called chroot().
avahi-daemon[2231]: Successfully dropped remaining capabilities.
avahi-daemon[2231]: No service found in /etc/avahi/services.
avahi-daemon[2231]: Network interface enumeration completed.
avahi-daemon[2231]: Registering HINFO record with values ‘IA64’/’LINUX’.
avahi-daemon[2231]: Server startup complete. Host name is ccswall.local. Local service cookie is 3037389712.
smartd[2251]: smartd version 5.38 [ia64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
smartd[2251]: Home page is http://smartmontools.sourceforge.net/  
smartd[2251]: Opened configuration file /etc/smartd.conf
smartd[2251]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
smartd[2251]: Device: /dev/hda, opened
smartd[2251]: Device: /dev/hda, packet devices [this device CD/DVD] not SMART capable
smartd[2251]: Device: /dev/sda, opened
smartd[2251]: Device: /dev/sda, is SMART capable. Adding to «monitor» list.
smartd[2251]: Monitoring 0 ATA and 1 SCSI devices
smartd[2253]: smartd has fork()ed into background mode. New PID=2253.
pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found

—— END /var/log/messages ——

# /etc/sysconfig/network-scripts/ifcfg-eth0

# PCI-X 1000Base-LX
# Intel PRO/1000 MF Server Adapter — Model PWLA9490LX
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:1b:21:xx:yy:zz

# /etc/sysconfig/network-scripts/ifcfg-eth1

# On-board 10/100/1000Base-T

# Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:11:0a:aa:bb:cc

# /etc/sysconfig/network-scripts/ifcfg-eth2

# On-board 100Base-T

# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth2
HWADDR=00:11:0a:dd:ee:ff
ONBOOT=no
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.100.200
GATEWAY=192.168.100.254
TYPE=Ethernet

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1B:21:XX:YY:ZZ 
          UP 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)

eth1      Link encap:Ethernet  HWaddr 00:11:0A:AA:BB:CC 
          UP 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:58 Memory:90800000-90810000

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8540 (8.3 KiB)  TX bytes:8540 (8.3 KiB)

# ifconfig eth0 down
# ifconfig eth0 up
# ifdown eth0
# ifup eth0
RTNETLINK answers: No such device
#
# ifconfig eth1 down
# ifconfig eth1 up
# ifdown eth1
# ifup eth1
RTNETLINK answers: No such device
#
# udevinfo -a -p /sys/class/net/eth0

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device ‘/class/net/eth0’:
    KERNEL==»eth0″
    SUBSYSTEM==»net»
    SYSFS{weight}==»64″
    SYSFS{tx_queue_len}==»1000″
    SYSFS{flags}==»0x1003″
    SYSFS{mtu}==»1500″
    SYSFS{operstate}==»down»
    SYSFS{dormant}==»0″
    SYSFS{carrier}==»0″
    SYSFS{broadcast}==»ff:ff:ff:ff:ff:ff»
    SYSFS{address}==»00:1b:21:xx:yy:zz»
    SYSFS{link_mode}==»0″
    SYSFS{type}==»1″
    SYSFS{features}==»0xffffffffd00113a9″
    SYSFS{ifindex}==»4″
    SYSFS{iflink}==»4″
    SYSFS{addr_len}==»6″

  looking at parent device ‘/devices/pci0000:80/0000:80:01.0’:
    ID==»0000:80:01.0″
    BUS==»pci»
    DRIVER==»e1000″
    SYSFS{broken_parity_status}==»0″
    SYSFS{enable}==»1″
    SYSFS{modalias}==»pci:v00008086d00001027sv00008086sd00001002bc02sc00i00″
    SYSFS{irq}==»60″
    SYSFS{class}==»0x020000″
    SYSFS{subsystem_device}==»0x1002″
    SYSFS{subsystem_vendor}==»0x8086″
    SYSFS{device}==»0x1027″
    SYSFS{vendor}==»0x8086″

  looking at parent device ‘/devices/pci0000:80’:
    ID==»pci0000:80″
    BUS==»»
    DRIVER==»»

# udevinfo -a -p /sys/class/net/eth1

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device ‘/class/net/eth1’:
    KERNEL==»eth1″
    SUBSYSTEM==»net»
    SYSFS{weight}==»64″
    SYSFS{tx_queue_len}==»1000″
    SYSFS{flags}==»0x1003″
    SYSFS{mtu}==»1500″
    SYSFS{operstate}==»down»
    SYSFS{dormant}==»0″
    SYSFS{carrier}==»0″
    SYSFS{broadcast}==»ff:ff:ff:ff:ff:ff»
    SYSFS{address}==»00:11:0a:aa:bb:cc»
    SYSFS{link_mode}==»0″
    SYSFS{type}==»1″
    SYSFS{features}==»0x500001a3″
    SYSFS{ifindex}==»3″
    SYSFS{iflink}==»3″
    SYSFS{addr_len}==»6″

  looking at parent device ‘/devices/pci0000:20/0000:20:02.0’:
    ID==»0000:20:02.0″
    BUS==»pci»
    DRIVER==»tg3″
    SYSFS{broken_parity_status}==»0″
    SYSFS{enable}==»1″
    SYSFS{modalias}==»pci:v000014E4d00001645sv0000103Csd000012A4bc02sc00i00″
    SYSFS{irq}==»58″
    SYSFS{class}==»0x020000″
    SYSFS{subsystem_device}==»0x12a4″
    SYSFS{subsystem_vendor}==»0x103c»
    SYSFS{device}==»0x1645″
    SYSFS{vendor}==»0x14e4″

  looking at parent device ‘/devices/pci0000:20’:
    ID==»pci0000:20″
    BUS==»»
    DRIVER==»»

# udevinfo -a -p /sys/class/net/eth2

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device ‘/class/net/eth2’:
    KERNEL==»eth2″
    SUBSYSTEM==»net»
    SYSFS{weight}==»16″
    SYSFS{tx_queue_len}==»1000″
    SYSFS{flags}==»0x1002″
    SYSFS{mtu}==»1500″
    SYSFS{operstate}==»down»
    SYSFS{broadcast}==»ff:ff:ff:ff:ff:ff»
    SYSFS{address}==»00:11:0a:dd:ee:ff»
    SYSFS{link_mode}==»0″
    SYSFS{type}==»1″
    SYSFS{features}==»0x0″
    SYSFS{ifindex}==»2″
    SYSFS{iflink}==»2″
    SYSFS{addr_len}==»6″

  looking at parent device ‘/devices/pci0000:00/0000:00:03.0’:
    ID==»0000:00:03.0″
    BUS==»pci»
    DRIVER==»e100″
    SYSFS{broken_parity_status}==»0″
    SYSFS{enable}==»1″
    SYSFS{modalias}==»pci:v00008086d00001229sv0000103Csd00001274bc02sc00i00″
    SYSFS{irq}==»59″
    SYSFS{class}==»0x020000″
    SYSFS{subsystem_device}==»0x1274″
    SYSFS{subsystem_vendor}==»0x103c»
    SYSFS{device}==»0x1229″
    SYSFS{vendor}==»0x8086″

  looking at parent device ‘/devices/pci0000:00’:
    ID==»pci0000:00″
    BUS==»»
    DRIVER==»»

#

{sa_family=AF_NETLINK, pid=0, groups=00000000}, [12]) = 36
[pid  2454] recvfrom(14, 0xbfab7670, 16, 66, 0xbfab7680, 0xbfab6664) = -1 EAGAIN (Resource temporarily unavailable)

[pid  2454] waitpid(2484, Process 2454 suspended
 <unfinished ...>
[pid  2484] <... select resumed> )      = 1 (in [0])
[pid  2484] brk(0)                      = 0x9963000
[pid  2484] brk(0x9984000)              = 0x9984000
[pid  2484] read(0, "", 1052)           = 0
[pid  2484] exit_group(0)               = ?
Process 2454 resumed
Process 2484 detached
[pid  2454] <... waitpid resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 2484
[pid  2454] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=2484, si_status=0, si_utime=0, si_stime=3} (Child exited) ---
[pid  2454] ftruncate(10, 0)            = 0
[pid  2454] close(10)                   = 0
[pid  2454] munmap(0xb7f78000, 4096)    = 0
[pid  2454] unlink("/var/run/pluto.pid") = 0
[pid  2454] unlink("/var/run/pluto.ctl") = 0
[pid  2454] close(7)                    = 0
[pid  2454] close(8)                    = 0
[pid  2454] munmap(0x770000, 9900)      = 0
[pid  2454] open("/usr/lib/ipsec/tls/i686/sse2/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  2454] open("/usr/lib/ipsec/tls/i686/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  2454] open("/usr/lib/ipsec/tls/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  2454] open("/usr/lib/ipsec/libgcc_s.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  2454] open("/etc/ld.so.cache", O_RDONLY) = 7
[pid  2454] fstat64(7, {st_mode=S_IFREG|0644, st_size=12628, ...}) = 0
[pid  2454] old_mmap(NULL, 12628, PROT_READ, MAP_PRIVATE, 7, 0) = 0xb576b000
[pid  2454] close(7)                    = 0
[pid  2454] open("/lib/libgcc_s.so.1", O_RDONLY) = 7
[pid  2454] read(7, "177ELF11133134023004"..., 512) = 512
[pid  2454] fstat64(7, {st_mode=S_IFREG|0644, st_size=160453, ...}) = 0
[pid  2454] old_mmap(NULL, 33636, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 7, 0) = 0x783000
[pid  2454] old_mmap(0x78b000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 7, 0x7000) = 0x78b000
[pid  2454] close(7)                    = 0
[pid  2454] munmap(0xb576b000, 12628)   = 0
[pid  2454] tgkill(2454, 2485, SIGRTMIN) = 0
[pid  2485] <... recvfrom resumed> 0xb7f71f70, 1024, 0, 0xb7f71f60, 0xb7f71f5c) = ? ERESTARTSYS (To be restarted)
[pid  2454] futex(0x929e6c8, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid  2485] --- {si_signo=SIGRTMIN, si_code=SI_TKILL, si_pid=2454, si_uid=0, si_value={int=402, ptr=0x192}} (Unknown signal 32) ---
[pid  2485] futex(0x78b328, FUTEX_WAKE, 2147483647) = 0
[pid  2485] futex(0x929e6c8, FUTEX_WAKE, 1) = 1
[pid  2454] <... futex resumed> )       = 0
[pid  2454] close(13 <unfinished ...>
[pid  2485] _exit(0)                    = ?
Process 2485 detached
[pid  2454] <... close resumed> )       = 0
[pid  2454] close(12)                   = 0
[pid  2454] sendto(14, "$!5315226t233431106"..., 36, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 36
[pid  2454] recvfrom(14, "$2315226t$!5315"..., 4096, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, [12]) = 36
[pid  2454] recvfrom(14, 0xbfab7670, 16, 66, 0xbfab7680, 0xbfab6664) = -1 EAGAIN (Resource temporarily unavailable)
[pid  2454] sendto(14, "$!5316226tn33431106"..., 36, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 36
[pid  2454] recvfrom(14, "$2316226t$!5316"..., 4096, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, [12]) = 36
[pid  2454] recvfrom(14, 0xbfab7670, 16, 66, 0xbfab7680, 0xbfab6664) = -1 EAGAIN (Resource temporarily unavailable)
[pid  2454] tgkill(2454, 2486, SIGRTMIN) = 0
[pid  2454] futex(0x929e6c8, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid  2486] <... recvfrom resumed> 0xb7570f70, 1024, 0, 0xb7570f60, 0xb7570f5c) = ? ERESTARTSYS (To be restarted)
[pid  2486] --- {si_signo=SIGRTMIN, si_code=SI_TKILL, si_pid=2454, si_uid=0, si_value={int=402, ptr=0x192}} (Unknown signal 32) ---
[pid  2486] futex(0x929e6c8, FUTEX_WAKE, 1) = 1

Webmaster and online service providers often inform that they are receiving a “no such device” message while using the ethtool command. This happens due to missing interface, driver issue etc.

As a part of our Server Management Services, we have helped online service providers to fix several similar Cloudflare errors.

Today, let’s discuss some tips to fix the DNS resolution error.

What causes ethtool no such device error?

Ethtool is a Network Interface Card configuration command that allows you to retrieve information and change your NIC settings. At times users may face a “no such device” error message while using this command. The typical error message looks like :

The common reasons for this error message include:

1. Missing Interface or it renamed to any other name

2. Driver issue

3. Selinux block

How to troubleshoot ethtool no such device error?

The first step to start troubleshooting the issue would be to check the dmesg output. dmesg is a command that Linux operating systems use to print the message buffer of the kernel. Since we here need the output related to an interface, we can use the following command to collect the required details:

dmesg | grep 

For example, for the interface eth0 ,

dmesg |grep eth0

The output of the above command may resemble the one given below:

bnx2 0000:04:00.0: eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2)
PCI-X 64-bit 133MHz found at mem c8000000, IRQ 18, node addr 00:14:5e:fd:6d:76
udev: renamed network interface eth0 to eth3

It confirms that the reason here is that the network interface was renamed from eth0 to eth3. Rename of the interface file or performing a cleanup of the subsystem will help to fix this error.

Let us now look at the steps to fix the error.

Rename the file

As we discussed earlier, if the rename of the interface triggers the no such device message, changing the interface file name fixes the error. For instance, if the interface was renamed from eth0 to eth3, we could follow the steps below:

1.Rename ifcfg-eth0 file to ifcfg-eth3

# mv /etc/sysconfig/network-script/ifcfg-eth0 /etc/sysconfig/network-script/ifcfg-eth3

2. Rename DEVICE parameter inside /etc/sysconfig/network-script/ifcfg-eth3

DEVICE=”eth3″
…
…

Another method is actually to clean up all the SUBSYSTEM Information and reboot. Hopefully, the eth0 is mapped back to /etc/sysconfig/network-script/ifcfg-eth0

Alternatively,  try modifying the /etc/udev/rules.d/70-persistent-net.rules and reboot. For instance, the contents of the file may resemble:

# PCI device 0x0000:0x0001 (bnx2)

SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”,
ATTR{address}==”00:00:00:00:00:01″, ATTR{type}==”1″,
KERNEL==”eth*”, NAME=”eth3″

The value of the NAME field needs to be changed to eth0. Once you are done, reload the udev configuration with the command start_udev

# start_udev

Finally, the network configuration needs to be updated.

# service network restart

Disable Selinux

Another option to fix the no such device error is to disable Selinux. Selinux is a Linux kernel security feature for access control. We could cross-check the status of it using the command below:

#sestatus

To disable SELinux on CentOS 7 temporarily, we can use the command

#setenforce 0

Similarly to set it disabled permanently, we will need to edit the SELinux configuration file.

#vi /etc/selinux/config  and set the SELINUX to disabled

Finally, reboot the server for the changes to take effect.

[Need assistance to fix ethtool no such device error? We’ll help you.]

Conclusion

In short, no such device error occurs due to reasons like renamed interface name, SELinux block etc. Today we discussed some tips that our Support Engineers follow to fix the ethtool error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;