On Tue, 8 May 2007, Chris Stromsoe wrote:
On Mon, 12 Mar 2007, Chris Stromsoe wrote:
On Thu, 8 Mar 2007, Chris Stromsoe wrote:
On Thu, 8 Mar 2007, Jay Vosburgh wrote:
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
1) ip link set mtu 9000 eth2 <-- eth2 is no longer responsive
ip link set mtu 1
On Mon, 12 Mar 2007, Chris Stromsoe wrote:
On Thu, 8 Mar 2007, Chris Stromsoe wrote:
On Thu, 8 Mar 2007, Jay Vosburgh wrote:
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
1) ip link set mtu 9000 eth2 <-- eth2 is no longer responsive
ip link set mtu 1500 eth2 <-- eth2 remains unresponsive
2)
On Thu, 8 Mar 2007, Chris Stromsoe wrote:
On Thu, 8 Mar 2007, Jay Vosburgh wrote:
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
1) ip link set mtu 9000 eth2 <-- eth2 is no longer responsive
ip link set mtu 1500 eth2 <-- eth2 remains unresponsive
2) ifup eth2
ifdown eth2
perl -pi -e 's
On Thu, 8 Mar 2007, Jay Vosburgh wrote:
If you're running active-backup and not using the ARP monitor
(arp_interval), then I'm not aware of any possible locking problems in
bonding for the kernel version you reference (2.6.20.1).
I'm not using arp_interval.
On Thu, 8 Mar 2007, Jay Vosburgh
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
>It's active-backup. Testing with the same setup and e100 works fine. I've
>done a few tests without the bonding module, using the dual-port
>separately.
Somebody else a couple of weeks ago was having similar issues
running bonding with skge (in
On Thu, 8 Mar 2007, Stephen Hemminger wrote:
On Thu, 8 Mar 2007 13:31:13 -0800 (PST)
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
Thanks. That fixes the soft lockup.
I've got another problem now. The cards I'm using are dual port
(sk-9844). I am bonding both ports together.
The card presents
On Thu, 8 Mar 2007 13:31:13 -0800 (PST)
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
> Thanks. That fixes the soft lockup.
>
> I've got another problem now. The cards I'm using are dual port
> (sk-9844). I am bonding both ports together.
>
> The card presents as eth2 and eth3. If I remove eth2
Chris Stromsoe <[EMAIL PROTECTED]> wrote:
>Within 2 or 3 minutes after issuing
>
>ip link set bond1 mtu 9000
>
>I get one "NETDEV WATCHDOG: eth2: transmit timed out" to the console, and
>then this starts to repeat:
>
>BUG: soft lockup detected on CPU#0!
I believe this is the same bug that
Thanks. That fixes the soft lockup.
I've got another problem now. The cards I'm using are dual port
(sk-9844). I am bonding both ports together.
The card presents as eth2 and eth3. If I remove eth2 from the bond so
that eth3 is the active interface, I get a hard lock (nothing prints to
s
[SKGE]: Fix deadlock in skge_tx_timeout
dev_watchdog() already holds the device lock, don't take it again in
skge_tx_clean().
Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]>
---
commit 0b1cfafa6f6b8a168d5811d1f65cf540942c52b1
tree 4d3f252d6618adfe812e9da95cd496bb798e7c7b
parent 1ca949299260a
Within 2 or 3 minutes after issuing
ip link set bond1 mtu 9000
I get one "NETDEV WATCHDOG: eth2: transmit timed out" to the console, and
then this starts to repeat:
BUG: soft lockup detected on CPU#0!
[] show_trace_log_lvl+0x19/0x2e
[] show_trace+0x12/0x14
[] dump_stack+0x14/0x16
[] softl
11 matches
Mail list logo
