netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ferenc Wagner <wferi@niif.hu>
To: netdev@vger.kernel.org
Subject: netconsole dumbs the system (in initramfs with bonding and vlan)
Date: Mon, 08 Feb 2010 22:01:31 +0100	[thread overview]
Message-ID: <87iqa74f2s.fsf@tac.ki.iif.hu> (raw)

Hi,

I set up networking from the initramfs like this:

----------------------------------------
ifup()
{
    ip addr add $2 dev $1
    ip link set up dev $1
    echo "Configured $1 with address $2"
}

BOND=bond0

modprobe bonding
cd /sys/class/net/$BOND/bonding

echo active-backup >mode
echo +eth0 >slaves
echo +eth1 >slaves
echo eth0 >primary
echo +10.0.0.1 >arp_ip_target
echo +10.0.0.2 >arp_ip_target
echo 1000 >arp_interval

vconfig set_name_type VLAN_PLUS_VID_NO_PAD
vconfig add $BOND 39

ifup $BOND 10.0.0.6/24
ifup vlan39 10.253.1.103/24
----------------------------------------

which mostly works, apart from the occasional flood of "bonding: bond0:
doing slave updates when interface is down" messages as detailed in my
previous mail.  However, if I afterwards issue

# modprobe netconsole netconsole=@10.0.0.6/eth0,@10.0.0.7/

that kills off the consoles: past kernel messages start pouring over all
consoles, the new network console included, then it suddenly dies off in
the middle, with one more line on the VC than sent to the network.  At
this point, the machine still responds to ping, the keyboard leds work,
but otherwise it's impossible to interact with it.  No SysRq, even.
Being in the initramfs, there are no network services to test.  If I
load netconsole in the running system, there isn't much backlog to pour
out, and the problem doesn't appear.  What could be wrong here?
-- 
Thanks,
Feri.

             reply	other threads:[~2010-02-08 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 21:01 Ferenc Wagner [this message]
2010-02-09 11:34 ` netconsole dumbs the system Ferenc Wagner

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=87iqa74f2s.fsf@tac.ki.iif.hu \
    --to=wferi@niif.hu \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).