FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 08-15-2012, 01:26 PM
 
Default Eth1 problem on CentOS-6.3

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

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-15-2012, 03:18 PM
"James B. Byrne"
 
Default Eth1 problem on CentOS-6.3

On Wed, August 15, 2012 09:15, Reindl Harald wrote:
> did you read the output you posted?
> http://lmgtfy.com/?q=unable+to+load+firmware+patch+rtl_nic%2Frtl8168 d-1.fw
r8169 0000:01:00.0: eth1: invalid firwmare
> r8169 0000:01:00.0: eth1: unable to load firmware patch
> rtl_nic/rtl8168d-1.fw (-22)

I cannot seem to find a fix for this even given the references
provided. However, I have discovered that eth1 has problems on the
second host as well, it just does not generate the same messages:

[root@vhost02 ~]# grep eth /var/log/messages
Aug 13 17:10:18 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 13 17:16:19 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:23:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:23:41 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:37:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:37:44 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:38:51 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:38:53 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:40:17 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:40:19 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 11:40:50 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 11:40:52 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 14 15:26:20 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 14 15:26:22 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:28:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:28:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:40:32 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:40:34 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:47:34 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:47:36 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 05:48:21 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 05:48:23 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:16:53 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:16:54 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:18:35 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:18:37 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:22:27 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:22:29 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:31:36 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:31:38 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:40:27 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:40:29 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:41:40 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:41:42 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 06:49:39 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 06:49:41 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:01:59 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:02:01 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:04:08 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:04:10 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:07:28 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:07:30 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:09:54 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:09:56 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:12:07 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:12:09 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:13:58 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:14:00 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:17:04 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:17:06 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:20:14 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:20:16 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 07:29:28 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 07:29:30 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 09:31:56 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 09:31:58 vhost02 kernel: r8169 0000:01:00.0: eth1: link up
Aug 15 09:33:18 vhost02 kernel: r8169 0000:01:00.0: eth1: link down
Aug 15 09:33:20 vhost02 kernel: r8169 0000:01:00.0: eth1: link up


So, my questions are: What is the problem and how do I fix it for both
hosts?

--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3






_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-15-2012, 03:44 PM
Ned Slider
 
Default Eth1 problem on CentOS-6.3

On 15/08/12 16:18, James B. Byrne wrote:
> On Wed, August 15, 2012 09:15, Reindl Harald wrote:
>> did you read the output you posted?
>> http://lmgtfy.com/?q=unable+to+load+firmware+patch+rtl_nic%2Frtl8168 d-1.fw
> r8169 0000:01:00.0: eth1: invalid firwmare
>> r8169 0000:01:00.0: eth1: unable to load firmware patch
>> rtl_nic/rtl8168d-1.fw (-22)
>
> I cannot seem to find a fix for this even given the references
> provided. However, I have discovered that eth1 has problems on the
> second host as well, it just does not generate the same messages:
>

<snip>

>
> So, my questions are: What is the problem and how do I fix it for both
> hosts?
>

Have you tried the updated driver I suggested?

Set up elrepo.org repository and then do:

yum install kmod-r8168

reboot and test.

If it doesn't work you can uninstall it and you've lost nothing but 10
minutes of your time.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-15-2012, 03:58 PM
Ned Slider
 
Default Eth1 problem on CentOS-6.3

On 15/08/12 16:18, James B. Byrne wrote:
> On Wed, August 15, 2012 09:15, Reindl Harald wrote:
>> did you read the output you posted?
>> http://lmgtfy.com/?q=unable+to+load+firmware+patch+rtl_nic%2Frtl8168 d-1.fw
> r8169 0000:01:00.0: eth1: invalid firwmare
>> r8169 0000:01:00.0: eth1: unable to load firmware patch
>> rtl_nic/rtl8168d-1.fw (-22)
>
> I cannot seem to find a fix for this even given the references
> provided. However, I have discovered that eth1 has problems on the
> second host as well, it just does not generate the same messages:
>

<snip>

>
> So, my questions are: What is the problem and how do I fix it for both
> hosts?
>

Do you actually have the kernel-firmware package installed that provides
the firmware?

rpm -q kernel-firmware

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-15-2012, 07:56 PM
"James B. Byrne"
 
Default Eth1 problem on CentOS-6.3

On Wed, August 15, 2012 09:26, m.roth@5-cent.us wrote:

>
> 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?
>

vhost is a kvm host system, not a virtualized guest. As I wrote
elsewhere, I installed the kmod package from elrepo that handles this
device, which solution I believe you may have originally suggested to
me. In any case, that seems to have solved the problem (fingers
crossed).

Thanks for the help. I appreciate it very much.

Sorry about your eyes. But when things are totally unfamiliar to me I
hesitate to trim error logs lest out of ignorance I remove what is
really important.

--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 05:17 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org