Re: Very strange Marvell/Yukon Gigabit NIC networking problems
From: Daniel Drake
Date: Tue Aug 30 2005 - 06:55:08 EST
Hi Stephen,
This looks like an issue I reported previously. After you use a recent skge,
you can't use any older drivers or the windows driver, but skge still works
fine every time.
http://marc.theaimsgroup.com/?l=linux-netdev&m=112268414417743&w=2
The Gentoo bug report is here:
http://bugs.gentoo.org/show_bug.cgi?id=100258
I closed the Gentoo bug as I hoped this patch would solve it:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=0eedf4ac5b536c7922263adf1b1d991d2e2397b9;hp=acdd80d514a08800380c9f92b1bf4d4c9e818125
But according to Steve Kieu, the problem is still there in 2.6.13. It's
slightly odd as Steve was previously a sk98lin user and initially reported
this problem for sk98lin in 2.6.13 whereas it did not happen with sk98lin in
2.6.12.
Any ideas?
Thanks.
Steve Kieu wrote:
Tested , not broken, working now but the same problem,
that is if I reboot to winXP or 2.6.12, 2.6.11, the
NIC is unusaeble. In XP it always says link is down,
or media disconnected (from ipconfig command output in
XP)
is it because the firmware of NIC has changed or any
reason?
I noticed warning messages only with 2.6.13
PCI: Failed to allocate mem resource #10:2000000@0 for
0000:02:01.0
and modem device in 2.6.13 IRQ is disabled.
ACPI: PCI Interrupt Link [LKMO] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [LKMO] ->
GSI 20 (level, low) -> IRQ
17
ACPI: PCI interrupt for device 0000:00:06.1 disabled
not sure if it gives more information.
skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
skge eth0: addr 00:11:d8:f2:1f:18
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKB] ->
GSI 18 (level, low) -> IRQ
16
Yenta: CardBus bridge found at 0000:02:01.0
[1043:1987]
skge eth0: enabling interface
skge eth0: Link is up at 10 Mbps, half duplex, flow
control none
Not sure how can I restore this thing back to normal
(sigh)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/