James B. Byrne wrote:
> Having replaced the suspect card and rebooted the host I see these
> messages in /var/log/messages repeated over and over:
<snip>
> Aug 15 07:20:13 vhost01 kernel: r8169 0000:01:00.0: eth1:
> RTL8168d/8111d at 0xffffc9001258c000, 00:0a:cd:1d:32:e7, XID 081000c0
> IRQ 30
> Aug 15 07:20:13 vhost01 kernel: r8169 0000:01:00.0: eth1: jumbo
> features [frames: 9200 bytes, tx checksumming: ko]
> Aug 15 07:20:14 vhost01 kernel: r8169 0000:01:00.0: eth1: invalid
> firwmare
> Aug 15 07:20:14 vhost01 kernel: r8169 0000:01:00.0: eth1: unable to
> load firmware patch rtl_nic/rtl8168d-1.fw (-22)
<snip>
> So, what is going on? This host is the first one of two nearly
> identically configured machines. The second host does not report or
> evidence any problem with its eth1.
My eyes uncrossed, and I saw, buried in there, the firstlink, above, and
the last. You might want to see if a) the 8168d firmware patch will work
on that card; b) vhost - it's a virtual host? perhaps it's trying to load
the firmware patch to the real NIC, and as a guest VM, it doesn't have
rights?
mark