2005-09-01 18:08:58

by Stephen Hemminger

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

On Tue, 30 Aug 2005 12:54:31 +0100
Daniel Drake <[email protected]> wrote:

> 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.

This is a different problem related to ACPI and other bus
changes in 2.6.13.


> > 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)


Is this the correct summary of the problem scenarios.
Assume each one starts from cold boot (power off).

* 2.6.13(skge) boot => Good
* 2.6.13(sk98lin) boot => Good
* 2.6.13 + SK version of sk98lin => Good
* XP boot => Good

Okay, now the cases where one OS is run first and
a reboot is done to a second, or in the case of
just Linux, this should be the same as rmmoding on
driver and modprobing

Second
First | skge | sk98lin | XP
skge | OK | BAD | BAD
sk98lin | ok | OK | ok
XP | ok | ok | OK



2005-09-01 21:21:13

by Steve Kieu

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

> Is this the correct summary of the problem
> scenarios.
> Assume each one starts from cold boot (power off).
>
> * 2.6.13(skge) boot => Good
> * 2.6.13(sk98lin) boot => Good
> * 2.6.13 + SK version of sk98lin => Good
> * XP boot => Good
XP boot: No good if before 2.6.13 runs on the hardware
and do the normal shuttdown or reboot or power off.

The same for all linux kernel before 2.6.13 (tested
2.6.12, 2.6.11)

>
> Okay, now the cases where one OS is run first and
> a reboot is done to a second, or in the case of
> just Linux, this should be the same as rmmoding on
> driver and modprobing
>
> Second
> First | skge | sk98lin | XP
> skge | OK | BAD | BAD
> sk98lin | ok | OK | ok
> XP | ok | ok | OK
>

a litle bit confusing, just one line to describe it:

If run 2.6.13 and up the NIC, it is working. Shuttdown
or reboot using /sbin/halt (means power completely off
and on) or /sbin/reboot all other OSs failed to enable
the NIC except 2.6.13.

to restore the normal working of the NIC, boot 2.6.13
and do a hot power reset. (press the reset button)

cheers


S.KIEU






____________________________________________________
Do you Yahoo!?
The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database.
http://au.movies.yahoo.com

2005-09-01 21:45:57

by Howard Chu

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems


Steve Kieu wrote:
>> Is this the correct summary of the problem
>> scenarios.
>> Assume each one starts from cold boot (power off).
>>
>> * 2.6.13(skge) boot => Good
>> * 2.6.13(sk98lin) boot => Good
>> * 2.6.13 + SK version of sk98lin => Good
>> * XP boot => Good
>>
> XP boot: No good if before 2.6.13 runs on the hardware
> and do the normal shuttdown or reboot or power off.
>
> The same for all linux kernel before 2.6.13 (tested
> 2.6.12, 2.6.11)
>
It's worth noting that most PCs today with ATX power supplies really
only go into a "Soft Off" state, which is probably why the anomaly
persists across a power off. You should also test if powering off and
removing the power plug will allow booting to XP to work.

--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/

2005-09-11 15:24:39

by Daniel Drake

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Hi,

Steve Kieu wrote:
> If run 2.6.13 and up the NIC, it is working. Shuttdown
> or reboot using /sbin/halt (means power completely off
> and on) or /sbin/reboot all other OSs failed to enable
> the NIC except 2.6.13.
>
> to restore the normal working of the NIC, boot 2.6.13
> and do a hot power reset. (press the reset button)

Stephen recently posted a patch which looks like it might solve this issue.

Steve, maybe you could test it out? I have attached it to this Gentoo bug:

http://bugs.gentoo.org/100258

Stephen, thanks for your hard work!
Daniel

2005-09-11 18:15:37

by Kalin KOZHUHAROV

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Daniel Drake wrote:
> Hi,
>
> Steve Kieu wrote:
>
>> If run 2.6.13 and up the NIC, it is working. Shuttdown
>> or reboot using /sbin/halt (means power completely off
>> and on) or /sbin/reboot all other OSs failed to enable
>> the NIC except 2.6.13.
>>
>> to restore the normal working of the NIC, boot 2.6.13
>> and do a hot power reset. (press the reset button)
>
>
> Stephen recently posted a patch which looks like it might solve this issue.
>
> Steve, maybe you could test it out? I have attached it to this Gentoo bug:
>
> http://bugs.gentoo.org/100258
>
> Stephen, thanks for your hard work!

I will try this one on a problematic ASUS board than now runs on
2.11.11 with sk98lin-8.18.2.2.patch

Applied the patch from #100258 to 2.6.13.1 successfully (some lines
offset) and recompiled. Will try it tomorrow when I am at the machine.

BTW, is this patch submitted to the Linus or -mm tree already?

Kalin.

--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

2005-09-12 00:02:46

by Steve Kieu

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems


> Steve, maybe you could test it out? I have attached
> it to this Gentoo bug:
>
> http://bugs.gentoo.org/100258

Have tested it and it does *not* solve the problem for
me.

Besides lots of other problem with 2.6.13 for me, like
modem device not work, lots of extra modules not
compiled (ov511 ; unionfs etc..) so even it works I
still need to revet back to 2.6.12.

Cheers,


S.KIEU

Send instant messages to your online friends http://au.messenger.yahoo.com

2005-09-12 16:06:33

by Kalin KOZHUHAROV

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Kalin KOZHUHAROV wrote:
> Daniel Drake wrote:
>
>> Hi,
>>
>> Steve Kieu wrote:
>>
>>> If run 2.6.13 and up the NIC, it is working. Shuttdown or
>>> reboot using /sbin/halt (means power completely off and on)
>>> or /sbin/reboot all other OSs failed to enable the NIC except
>>> 2.6.13.
>>>
>>> to restore the normal working of the NIC, boot 2.6.13 and do
>>> a hot power reset. (press the reset button)
>>
>>
>>
>> Stephen recently posted a patch which looks like it might solve
>> this issue.
>>
>> Steve, maybe you could test it out? I have attached it to this
>> Gentoo bug:
>>
>> http://bugs.gentoo.org/100258
>>
>> Stephen, thanks for your hard work!
>
>
> I will try this one on a problematic ASUS board than now runs on
> 2.11.11 with sk98lin-8.18.2.2.patch.
>
> Applied the patch from #100258 to 2.6.13.1 successfully (some
> lines offset) and recompiled. Will try it tomorrow when I am at
> the machine.

Well, I did test it, but skge didn't even find the hardware :-(
No device was created, no dmesg output on load.
Instead I am running 2.6.13.1 with sk98lin-8.23.1.3.patch
The MB is ASUS P5GDC-V-Deluxe and the the on-board NIC:

# lspci -v -s 02:00.0
0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd.
88E8053 Gigabit Ethernet Controller (rev 15)
Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit
Ethernet Controller (Asus)
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at cfffc000 (64-bit, non-prefetchable) [size=16K]
I/O ports at d800 [size=256]
Expansion ROM at cffc0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: 64bit+
Queue=0/1 Enable-
Capabilities: [e0] #10 [0011]


I am not sure it is supposed to be used with the skge driver, but I
thought it will work... Some ASUS boards apparently have problems
with the VPD being broken, but I am not sure how to check that.

> BTW, is this patch submitted to the Linus or -mm tree already?
??

Kalin.

--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

2005-09-12 16:50:09

by Daniel Drake

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Kalin KOZHUHAROV wrote:
> Well, I did test it, but skge didn't even find the hardware :-(
> No device was created, no dmesg output on load.
> Instead I am running 2.6.13.1 with sk98lin-8.23.1.3.patch
> The MB is ASUS P5GDC-V-Deluxe and the the on-board NIC:
>
> # lspci -v -s 02:00.0
> 0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053
> Gigabit Ethernet Controller (rev 15)

This patch was to solve an issue in skge, a driver for Marvell Yukon network
adapters.

Your hardware is a yukon-2 adapter, you want to use the sky2 driver from the
netdev tree.

Daniel

2005-09-12 17:40:40

by Kalin KOZHUHAROV

[permalink] [raw]
Subject: Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Daniel Drake wrote:
> Kalin KOZHUHAROV wrote:
>
>> Well, I did test it, but skge didn't even find the hardware :-(
>> No device was created, no dmesg output on load.
>> Instead I am running 2.6.13.1 with sk98lin-8.23.1.3.patch
>> The MB is ASUS P5GDC-V-Deluxe and the the on-board NIC:
>>
>> # lspci -v -s 02:00.0
>> 0000:02:00.0 Ethernet controller: Marvell Technology Group Ltd.
>> 88E8053 Gigabit Ethernet Controller (rev 15)
>
>
> This patch was to solve an issue in skge, a driver for Marvell Yukon
> network adapters.
>
> Your hardware is a yukon-2 adapter, you want to use the sky2 driver from
> the netdev tree.
Ok, that makes the things clear, thank you.

After quite a lot of fiddling iwth google and git, I found what you
are talking about here:
http://www.mail-archive.com/[email protected]/msg01592.html
http://www.kernel.org/git/?p=linux/kernel/git/jgarzik/netdev-2.6.git;a=commitdiff;h=cd28ab6a4e50a7601d22752aa7ce0c8197b10bdf

Somehow I missed it on LKML.
Unfortunately the machine with this chipset is heavily used, so I
am not very likely to get it off-line for testing.
Will have it in mind and try it if possible.

Kalin.

--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|