On Thu, 12 Jul 2007, Stephen Hemminger wrote:
Does this fix your problems? I don't have dual port boards but have an
old SK-9843 fiber board.
Nope. It still hangs with:
fresno:~# ip li set eth2 up
fresno:~# ip li set eth2 down
fresno:~# ip li set eth3 up
This is with 2.6.22.1
If I load th
This is probably going to cause a new entry in regressions list, as at
least Chris Stromsoe has reported bonding-related problems with skge
that don't happen with sklin -
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0707.1/1158.html
It's worse than just bonding related. This al
On Tue, 10 Jul 2007, Chris Stromsoe wrote:
On Tue, 10 Jul 2007, Stephen Hemminger wrote:
On Tue, 10 Jul 2007 12:44:35 -0400 Jeff Garzik <[EMAIL PROTECTED]> wrote:
Adrian Bunk wrote:
This patch contains the scheduled removal of the sk98lin driver.
Signed-off-by: Adrian Bunk <[EMAIL
On Tue, 10 Jul 2007, Stephen Hemminger wrote:
On Tue, 10 Jul 2007 12:44:35 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
Adrian Bunk wrote:
This patch contains the scheduled removal of the sk98lin driver.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Stephen -- ACK?
Yes. Existing driver
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 lin
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 unr
On Mon, 12 Mar 2007, Stephen Hemminger wrote:
Sounds like a dual-port only problem.. Unfortunately, I don't have
actual dual port skge hardware to test. Try this:
That doesn't change the behavior at all. I tested against 2.6.20.2 with
skge from git and against 2.6.21-rc3-git7.
-Chris
-
To
On Mon, 12 Mar 2007, Stephen Hemminger wrote:
When bonding does fail over it calls set_mac_address. When this happens
as the result of another port going down, the phy_mutex that is common
to both ports is held, so it deadlocks. Setting the address doesn't need
to do anything that needs the p
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
7, 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/eth2/eth3/' /etc/network/interfac
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.
T
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
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
Ignore this. I rebooted into the wrong kernel and was testing with 2.6.16
instead of 2.6.20. It works fine with 2.6.20.
-Chris
On Mon, 5 Mar 2007, Chris Stromsoe wrote:
I have a bunch of dual-port SK 98xx cards that work with sk98lin but not
with skge. After loading skge, I get
ACPI
On Mon, 5 Mar 2007, Stephen Hemminger wrote:
What kernel version. Type 0 is XMAC support, and that was added to a
fairly recent kernel (2.6.19?)
It was an old kernel. I booted into 2.6.16 instead of 2.6.20. See my
follow-up (and ignore the report).
-Chris
-
To unsubscribe from this list:
I have a bunch of dual-port SK 98xx cards that work with sk98lin but not
with skge. After loading skge, I get
ACPI: PCI Interrupt :01:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) ->
IRQ 10
skge :01:0a.0: unsupported phy type 0x0
ACPI: PCI interrupt for device :01:0a.0 disabled
skg
16 matches
Mail list logo
