public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Genthner <rgenthner@symplicity.com>
To: kexec@lists.infradead.org
Subject: Re: Kexec Reboot Network Issue
Date: Thu, 15 Jul 2010 11:35:43 -0400	[thread overview]
Message-ID: <4C3F2ACF.60601@symplicity.com> (raw)
In-Reply-To: <20100715142003.GB19856@verge.net.au>

I would try a different kenerl but our cluster fs has us locked to this 
kernel until we finish the upgrade to the new cluster fs version. heres 
ethtool on the iface

from lshw
*-network
                 description: Ethernet interface
                 product: NetXtreme BCM5721 Gigabit Ethernet PCI Express
                 vendor: Broadcom Corporation
                 physical id: 0
                 bus info: pci@0000:03:00.0
                 logical name: eth0
                 version: 21
                 serial: 00:25:64:3b:9c:ae
                 size: 1GB/s
                 capacity: 1GB/s
                 width: 64 bits
                 clock: 33MHz
                 capabilities: pm vpd msi pciexpress bus_master cap_list 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
                 configuration: autonegotiation=on broadcast=yes 
driver=tg3 driverversion=3.93 duplex=full firmware=5721-v3.65, ASFIPMI 
v6.25 ip=172.16.1.123 latency=0 link=yes module=tg3 multicast=yes 
port=twisted pair speed=1GB/s


On 07/15/2010 10:20 AM, Simon Horman wrote:
> On Thu, Jul 15, 2010 at 07:59:07AM -0400, Richard Genthner wrote:
>    
>> I'm currently using the following string:
>>
>> kexex --type=elf-x86_64 --args-linux -l /boot/vmlinuz-2.6.18-12.el5
>> --initrid=/boot/initrd-2.6.18-128.el6.img --append="`cat
>> /proc/cmdline`"
>> kexec -e
>>
>> Some times we can get to the box from any subnet, other times we can
>> only get to the box from the same subnet only. Our solution to this
>> is to down the iface and then restart networking. Has anyone else
>> run into this issue?
>>      
> Hi Richard,
>
> could you be more specific about which NIC you are using?
> And is it at all possible to test a newer kernel version?
>
> What I suspect is happening is that the NIC is getting into an unknown
> state. And what I'm hoping is that is a problem thats already been
> addressed.
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
>    

-- 
Richard Genthner
Systems Administration
Symplicity
ph. 703-351-0200 x8051



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2010-07-15 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 11:59 Kexec Reboot Network Issue Richard Genthner
2010-07-15 14:20 ` Simon Horman
2010-07-15 15:35   ` Richard Genthner [this message]
2010-07-16  7:15     ` Simon Horman
2010-07-18  4:25       ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C3F2ACF.60601@symplicity.com \
    --to=rgenthner@symplicity.com \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox