From: Pfenniger Daniel <daniel.pfenniger@obs.unige.ch>
To: linux-kernel@vger.kernel.org
Subject: Channel bonding kernel crash, workaround
Date: Fri, 23 Mar 2001 09:12:34 +0100 [thread overview]
Message-ID: <3ABB0572.BB100F30@obs.unige.ch> (raw)
Hi,
Up to the latests kernels (-> 2.4.2) channel bonding crashes the kernel
(aille...) when turning it off (e.g. at reboot).
Here is a way to avoid this, which might help gourous to track the bug.
Suppose ifconfig says:
bond0 Link encap:Ethernet HWaddr 00:40:05:A1:C4:13
inet addr:192.168.2.64 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:823297 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:40:05:A1:C4:13
inet addr:192.168.2.64 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:487424 errors:0 dropped:0 overruns:0 frame:0
TX packets:411649 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:19 Base address:0xd000
eth1 Link encap:Ethernet HWaddr 00:40:05:A1:C4:13
inet addr:192.168.2.64 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:487526 errors:0 dropped:0 overruns:0 frame:0
TX packets:411648 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:18 Base address:0xb800
then the exact sequence:
ifconfig eth0 down
ifconfig eth1 down
ifconfig bond0 down
ifconfig eth0 down
ifconfig eth1 down
turns off bond0 without crash. This was tested on several computers with
all kernel 2.4.2, SMP Pentium II and tulip 21140 and/or 21142/3 NICs.
Dan
next reply other threads:[~2001-03-23 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 8:12 Pfenniger Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-24 1:29 Channel bonding kernel crash, workaround Jeff Golds
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=3ABB0572.BB100F30@obs.unige.ch \
--to=daniel.pfenniger@obs.unige.ch \
--cc=linux-kernel@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