I am trying to transport a dd image between to hosts over a cross
linked gigabit connection. Both hosts have an eth1 configured to a
non routable ip addr on a shared network. No other devices exist on
this link.
When transferring via sftp I received a stall warning. Checking the
logs I see thi
On 11/08/12 22:17, James B. Byrne wrote:
> I am trying to transport a dd image between to hosts over a cross
> linked gigabit connection. Both hosts have an eth1 configured to a
> non routable ip addr on a shared network. No other devices exist on
> this link.
>
> When transferring via sftp I re
On Sun, August 12, 2012 12:00, Ned Slider wrote:
> On 11/08/12 22:17, James B. Byrne wrote:
>> I am trying to transport a dd image between to hosts over a cross
>> linked gigabit connection. Both hosts have an eth1 configured to a
>> non routable ip addr on a shared network. No other devices ex
On 13/08/12 14:08, James B. Byrne wrote:
>
> On Sun, August 12, 2012 12:00, Ned Slider wrote:
>> On 11/08/12 22:17, James B. Byrne wrote:
>>> I am trying to transport a dd image between to hosts over a cross
>>> linked gigabit connection. Both hosts have an eth1 configured to a
>>> non routable ip
James,
James B. Byrne wrote:
> On Sun, August 12, 2012 12:00, Ned Slider wrote:
>> On 11/08/12 22:17, James B. Byrne wrote:
> The network card for eth1 seems to have disappeared somehow.
> On the problem host:
>
> # /sbin/lspci -nn | grep -i net
> 00:19.0 Ethernet controller [0200]: Intel Corpora
On Mon, August 13, 2012 10:37, Ned Slider wrote:
> Faulty hardware maybe? Try a reboot and see if it reappears. If it's
> located on a card try reseating the card (although I suspect this is
> an integrated NIC on the motherboard?).
>
> The chipset is not necessarily the same in the second exampl
On 13/08/12 19:50, James B. Byrne wrote:
>
> On Mon, August 13, 2012 10:37, Ned Slider wrote:
>
>> Faulty hardware maybe? Try a reboot and see if it reappears. If it's
>> located on a card try reseating the card (although I suspect this is
>> an integrated NIC on the motherboard?).
>>
>> The chipse
On Mon, August 13, 2012 18:48, Ned Slider wrote:
> On 13/08/12 19:50, James B. Byrne wrote:
>>
>> On Mon, August 13, 2012 10:37, Ned Slider wrote:
>>
>>> Faulty hardware maybe? Try a reboot and see if it reappears. If
>>> it's
>>> located on a card try reseating the card (although I suspect this
>
James B. Byrne wrote:
> On Mon, August 13, 2012 18:48, Ned Slider wrote:
>> On 13/08/12 19:50, James B. Byrne wrote:
>>> On Mon, August 13, 2012 10:37, Ned Slider wrote:
>>>
Faulty hardware maybe? Try a reboot and see if it reappears. If
it's located on a card try reseating the card (alth
Having replaced the suspect card and rebooted the host I see these
messages in /var/log/messages repeated over and over:
Aug 15 07:17:10 vhost01 ntpd[2044]: Listening on interface #62 eth1,
fe80::20a:cdff:fe1d:32e7#123 Enabled
Aug 15 07:17:10 vhost01 ntpd[2044]: Listening on interface #63 eth1,
19
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:
> Aug 15 07:20:13 vhost01 kernel: r8169 :01:00.0: eth1:
> RTL8168d/8111d at 0xc9001258c000, 00:0a:cd:1d:32:e7, XID 081000c0
> IRQ 30
> Aug 15 0
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%2Frtl8168d-1.fw
r8169 :01:00.0: eth1: invalid firwmare
> r8169 :01:00.0: eth1: unable to load firmware patch
> rtl_nic/rtl8168d-1.fw (-22)
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%2Frtl8168d-1.fw
> r8169 :01:00.0: eth1: invalid firwmare
>> r8169 :01:00.0: eth1: unable to loa
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%2Frtl8168d-1.fw
> r8169 :01:00.0: eth1: invalid firwmare
>> r8169 :01:00.0: eth1: unable to loa
On Wed, August 15, 2012 09:26, m.r...@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
15 matches
Mail list logo
