Re: Very strange Marvell/Yukon Gigabit NIC networking problems

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

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)

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Stephen Hemminger]

On Tue, 30 Aug 2005 12:54:31 +0100
Daniel Drake <dsd@gentoo.org> 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

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

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

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Steve Kieu]

> 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 

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

Forwarding on, please reply-to-all in future.

Steve Kieu wrote:
> Hi all,
> 
> I have "fixed" the problem in a very wierd way.Reading
> your post I thought maybe when removing the driver
> itself it set some bit incorrectly. Then I decided to
> do:
> 
> Boot with init=/bin/bash  so bypass all other things.
> modprobe skge
> 
> run ifconfig eth0 ip_num  up
> 
> 
> ping  a host
> 
> then while pinging hit Ctrl+Alt+Del key to hot reboot
> the system.
> 
> I still see the light at the hub lits. Now I boot to
> winXP and as I expected , it worked!
> 
> No I boot 2.6.11 and it worked, so the problem resolve
> but I am tooooo scared to run 2613 now :-)
> 
> Hope this information helps debuging the driver.
> 
> Thanks.
> 
> S.KIEU

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Jesse Brandeburg]

on 2.6.11/12 when it isn't working maybe you should send us the output
of lspci -vvv

just a hint, I'm guessing its power management related, and / or
something to do with the pci bus code.

On 8/30/05, Daniel Drake <dsd@gentoo.org> wrote:
> Forwarding on, please reply-to-all in future.
> 
> Steve Kieu wrote:
> > Hi all,
> >
> > I have "fixed" the problem in a very wierd way.Reading
> > your post I thought maybe when removing the driver
> > itself it set some bit incorrectly. Then I decided to
> > do:
> >
> > Boot with init=/bin/bash  so bypass all other things.
> > modprobe skge
> >
> > run ifconfig eth0 ip_num  up
> >
> >
> > ping  a host
> >
> > then while pinging hit Ctrl+Alt+Del key to hot reboot
> > the system.
> >
> > I still see the light at the hub lits. Now I boot to
> > winXP and as I expected , it worked!
> >
> > No I boot 2.6.11 and it worked, so the problem resolve
> > but I am tooooo scared to run 2613 now :-)
> >
> > Hope this information helps debuging the driver.
> >
> > Thanks.
> >
> > S.KIEU
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Stephen Hemminger]

On Tue, 30 Aug 2005 13:18:57 -0700
Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:

> on 2.6.11/12 when it isn't working maybe you should send us the output
> of lspci -vvv
> 
> just a hint, I'm guessing its power management related, and / or
> something to do with the pci bus code.

Also, the dmesg output with skge driver will show chip version and revision.
The problem is obviously some of the chip initialization that is complex
with the Marvell chips. Something is probably missing.  There was a fix
in the latest 2.6.13 that is probably related:

	http://www.mail-archive.com/netdev@vger.kernel.org/msg00438.html

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Steve Kieu]

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]


Ok, I reproduce the problem and attached several lspci
log here


--- Stephen Hemminger <shemminger@osdl.org> wrote:

> On Tue, 30 Aug 2005 13:18:57 -0700
> Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:
> 
> > on 2.6.11/12 when it isn't working maybe you
> should send us the output
> > of lspci -vvv
> > 
> > just a hint, I'm guessing its power management
> related, and / or
> > something to do with the pci bus code.
> 
> Also, the dmesg output with skge driver will show
> chip version and revision.
> The problem is obviously some of the chip
> initialization that is complex
> with the Marvell chips. Something is probably
> missing.  There was a fix
> in the latest 2.6.13 that is probably related:
> 
> 
>
http://www.mail-archive.com/netdev@vger.kernel.org/msg00438.html
> 

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

[-- Attachment #2: 2772971102-dmesg-2.6.12-nowork.log.gz --]
[-- Type: application/x-gzip, Size: 5927 bytes --]

[-- Attachment #3: 3668832883-dmesg-2613.log.gz --]
[-- Type: application/x-gzip, Size: 4868 bytes --]

[-- Attachment #4: 3470857198-lspci-2612-nowork.log.gz --]
[-- Type: application/x-gzip, Size: 2012 bytes --]

[-- Attachment #5: 1122749440-lspci-2613.log.gz --]
[-- Type: application/x-gzip, Size: 1672 bytes --]

[-- Attachment #6: 267994485-lspci-2612-work.log.gz --]
[-- Type: application/x-gzip, Size: 1672 bytes --]

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Stephen Hemminger]

You have a version of the Marvell Yukon that was affected
by a fix in 2.6.13.
	skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9

Both the skge and sk98lin driver were fixed to check for this.
Without the fix, the chip will be in the wrong power mode.

The version of sk98lin driver from SysKonnect already had the
fix, so if your distro used that one, it would have the reset
the power mode as needed.

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Steve Kieu]

--- Stephen Hemminger <shemminger@osdl.org> wrote:

> You have a version of the Marvell Yukon that was
> affected
> by a fix in 2.6.13.
> 	skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
> 
> Both the skge and sk98lin driver were fixed to check
> for this.
> Without the fix, the chip will be in the wrong power
> mode.
> 
> The version of sk98lin driver from SysKonnect
> already had the
> fix, so if your distro used that one, it would have
> the reset
> the power mode as needed.

I am afraid not. The last time, I reproduced the
problem using the latest sk98lin driver from
SysKonnect  (run create patch and patch the kernel
2.6.13). Problem still there. The file I got from
sysconnect is:

install-8_23.tar.bz2

> 


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

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Stephen Hemminger]

On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
Steve Kieu <haiquy@yahoo.com> wrote:

> 
> --- Stephen Hemminger <shemminger@osdl.org> wrote:
> 
> > You have a version of the Marvell Yukon that was
> > affected
> > by a fix in 2.6.13.
> > 	skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
> > 
> > Both the skge and sk98lin driver were fixed to check
> > for this.
> > Without the fix, the chip will be in the wrong power
> > mode.
> > 
> > The version of sk98lin driver from SysKonnect
> > already had the
> > fix, so if your distro used that one, it would have
> > the reset
> > the power mode as needed.
> 
> I am afraid not. The last time, I reproduced the
> problem using the latest sk98lin driver from
> SysKonnect  (run create patch and patch the kernel
> 2.6.13). Problem still there. The file I got from
> sysconnect is:
> 
> install-8_23.tar.bz2

Just look for references to CHIP_REV_YU_LITE_A3 in the driver
	sk98lin/skgeinit.c and sk98lin/skxmac2.c
The comparison should always be:
	pAC->GIni.GIChipRev >= CHIP_REV_YU_LITE_A3
otherwise it will not correctly take chip out of powerdown (coma) mode.

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Steve Kieu]

--- Stephen Hemminger <shemminger@osdl.org> wrote:

> On Wed, 31 Aug 2005 07:49:37 +1000 (EST)

> > 
> > install-8_23.tar.bz2
> 
> Just look for references to CHIP_REV_YU_LITE_A3 in
> the driver
> 	sk98lin/skgeinit.c and sk98lin/skxmac2.c
> The comparison should always be:

Have a look but no clue to patch it, there are one
instance of comparing

> 	pAC->GIni.GIChipRev >= CHIP_REV_YU_LITE_A3
> otherwise it will not correctly take chip out of
> powerdown (coma) mode.

please send me a patch to the install-8_23.tar.bz2
then I can test. Or intruct more details, which line
and what should change then I can do manually.

I have nerver done device driver programming in my
life!



> 


S.KIEU

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

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Stephen Hemminger]

On Wed, 31 Aug 2005 10:09:48 +1000 (EST)
Steve Kieu <haiquy@yahoo.com> wrote:

> 
> --- Stephen Hemminger <shemminger@osdl.org> wrote:
> 
> > On Wed, 31 Aug 2005 07:49:37 +1000 (EST)
> 
> > > 
> > > install-8_23.tar.bz2
> > 
> > Just look for references to CHIP_REV_YU_LITE_A3 in
> > the driver
> > 	sk98lin/skgeinit.c and sk98lin/skxmac2.c
> > The comparison should always be:
> 
> Have a look but no clue to patch it, there are one
> instance of comparing

I don't fix the out of tree vendor driver. sorry.

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

Stephen Hemminger wrote:
> You have a version of the Marvell Yukon that was affected
> by a fix in 2.6.13.
> 	skge addr 0xfeaf8000 irq 19 chip Yukon-Lite rev 9
> 
> Both the skge and sk98lin driver were fixed to check for this.
> Without the fix, the chip will be in the wrong power mode.
> 
> The version of sk98lin driver from SysKonnect already had the
> fix, so if your distro used that one, it would have the reset
> the power mode as needed.

So, am I right in saying we can't do anything in skge to work around this to 
allow those older buggy drivers to work on the next reboot? More reports are 
cropping up, e.g.:

	http://forums.gentoo.org/viewtopic-t-375828.html

Given that it seems to be affecting the Windows drivers too, it would be great 
if something could be done.

Thanks,
Daniel

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

Steve Kieu wrote:
>>Are you using skge or sk98lin?
> 
> 
> sk98lin
> 
> thanks

Can you test the new skge driver instead? If that one is broken then we 
probably have more chance of getting it fixed :)

Thanks,
Daniel

Re: Very strange Marvell/Yukon Gigabit NIC networking problems

[Daniel Drake]

Steve Kieu wrote:
> Ok it sound wierd enough to assume that the latest
> kernel 2.6.13 ethernet driver has done something wrong
> with the NIC and sustain the condition after reboot or
> turn off the machine.
> 
> Here is my configuration.
> 
> Laptop Asus A4500d. dmesg shows:
> 
> eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter

Are you using skge or sk98lin?

> It is working as normal with 2.6.12 and winXP before.
> Today I did upgrade the kernel to 2.6.13 and it still
> works. The problem is now I switch to the older kernel
> that is 2.6.12.5 and .6  it no longer works. dmesg
> shows like this:
>      
> eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
>       PrefPort:A  RlmtMode:Check Link State
> 
> 
> Boot window XP now, and the link always shows that
> media disconnected. So the NIC is unuseable with
> WinXP, 2.6.12  __but__ still works with 2.6.13. and
> power off the machine does not restore the NIC.