From: Heiko Gerstung <heiko@am-anger-1.de>
To: linux-kernel@vger.kernel.org
Subject: Bug related to bonding
Date: Mon, 15 May 2006 11:35:28 +0200 [thread overview]
Message-ID: <44684B60.1070705@am-anger-1.de> (raw)
Hi!
I am at a total loss with this one. My vanilla 2.4.32 crashes when I
try to use bonding together with my rtl8150 based (USB-Ethernet) NICs.
If this is a known error, I apologize for bothering the list and would
appreciate any pointers to a working solution/workaround.
Reproduce:
# modprobe bonding mode=1 miimon=100 maxbonds=4
# ifconfig bond0 172.16.10.111 netmask 255.255.255.0 up
# ifenslave bond0 eth1 eth2
Ethernet Channel Bonding Driver: v2.6.0 (January 14, 2004)
bonding: MII link monitoring set to 100 ms
00:60:6E:30:07:Scheduling in interrupt
kernel BUG at sched.c:564!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c011461d>] Not tainted
EFLAGS: 00010282
...(following the CPU registers and Call Trace)....
Please let me know which details I have to provide from the bug message
(I have to type it in manually, no copy'n'paste possible:-)).
It is not clear to me whether this is a bug in the bonding module, in
the network driver or in the kernel itself.
All 2.6.x kernels I tried worked fine, but I am currently bound to a
2.4.x kernel and all 2.4.x kernels I tried (2.4.20, 2.4.29) showed
similiar problems when activating bonding.
Thank you in advance,
kind regards,
Heiko
next reply other threads:[~2006-05-15 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 9:35 Heiko Gerstung [this message]
2006-05-16 4:53 ` Willy Tarreau
2006-05-16 5:03 ` Heiko Gerstung
2006-05-16 5:07 ` Heiko Gerstung
2006-05-16 12:33 ` Willy Tarreau
2006-05-16 15:09 ` Heiko Gerstung
2006-05-16 18:23 ` Willy Tarreau
2006-05-17 18:31 ` USB net driver hacker wanted (was Re: Bug related to bonding) Heiko Gerstung
2006-05-17 20:55 ` Willy Tarreau
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=44684B60.1070705@am-anger-1.de \
--to=heiko@am-anger-1.de \
--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
all inboxes | Powered by JetHome®