LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Santiago Garcia Mantinan <manty@manty.net>
Cc: linux-kernel@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: uli526x doesn't get link if no link when interface is set up
Date: Tue, 5 Feb 2008 23:15:07 -0700	[thread overview]
Message-ID: <20080206061507.GA22107@colo.lackof.org> (raw)
In-Reply-To: <20080202145638.GA5871@dis.manty.net>

On Sat, Feb 02, 2008 at 03:56:38PM +0100, Santiago Garcia Mantinan wrote:
> Hi!
> 
> I've been experiencing problems with this (internal) card ever since I
> bought this motherboard, lately I've been doing some tests and I found out
> some things, maybe not enough to let us debug this, but I'll explain it just
> in case.

Santiago,
Thanks for the excellent bug report.
Is this perhaps the same problem as described here?

    http://bugzilla.kernel.org/show_bug.cgi?id=5839

It sounds similar but I only skimmed over your report.
If you think it is, could you add (just cut/paste)
you email to that bug for me?
Could you also try the patch I attached to that bug report?
If it works for you, we can both pester Kyle McMartin to
push it upstream. ;)

Thanks for the excellent bug report...I'll take a closer look
at it later this week or weekend.

thanks,
grant

> 
> The problem is that if the uli526x card is set up (ifconfig ethX up) when
> there is no cable plugged or the cable is plugged to something that is off
> at that time, this means, when there is no link for the card to detect,
> then, when the cable or the switch or whatever is plugged, the link is not
> detected by the uli526x card an thus no link is stablished (led on the
> switch remains off).
> 
> This is the status reported by ethtool when the link should be on but the
> driver is not detecting this condition and thus it is off:
> 
>         Supported ports: [ MII ]
>         Supported link modes:   10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>         Supports auto-negotiation: Yes
>         Advertised link modes:  10baseT/Half 10baseT/Full 
>                                 100baseT/Half 100baseT/Full 
>         Advertised auto-negotiation: Yes
>         Speed: Unknown! (65535)
>         Duplex: Unknown! (255)
>         Port: MII
>         PHYAD: 1
>         Transceiver: external
>         Auto-negotiation: on
>         Supports Wake-on: pg
>         Wake-on: d
>         Link detected: no
> 
> If at this time we run: "ifconfig ethX down" and after some time: "ifconfig
> ethX up" then the link is detected, but if we run this two commands without
> waiting a time between them, the link remains undetected.
> 
> In fact, if with an stablished and detected link, we run: "ifconfig ethX
> down;ifconfig ethX up" the link is lost again and is not detected till we
> run the two commands waiting some time between them.
> 
> Once the link is stablished if we don't touch the interface config (we don't
> ifconfig it down) then we can unplug the cable or turn off the switch or
> whatever and the card will detect the link whenever it becomes available
> again.
> 
> This makes me think that the problem is something related to the way on
> which we are setting the card up.
> 
> I'm running 2.6.24 on a amd64 machine, these are the messages I get from the
> driver on load:
> uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29)
> ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 20 (level, low) -> IRQ 20
> eth1: ULi M5263 at pci0000:00:12.0, 00:13:8f:a7:af:b4, irq 20.
> uli526x: eth1 NIC Link is Up 100 Mbps Full duplex
> 
> This is my lspci output:
> 00:12.0 0200: 10b9:5263 (rev 60)
>         Subsystem: 1849:5263
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 32 (5000ns min, 10000ns max), Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 20
>         Region 0: I/O ports at c800 [size=256]
>         Region 1: Memory at dedefc00 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Kernel driver in use: uli526x
>         Kernel modules: uli526x
> 
> I don't know what else to add but I offer myself to do all the wanted tests.
> 
> Regards...
> -- 
> Manty/BestiaTester -> http://manty.net
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2008-02-06  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 14:56 Santiago Garcia Mantinan
2008-02-06  6:15 ` Grant Grundler [this message]
2008-02-06 18:44   ` Santiago Garcia Mantinan
2008-02-06 19:43     ` Grant Grundler
2008-02-11 16:22       ` Santiago Garcia Mantinan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080206061507.GA22107@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manty@manty.net \
    --subject='Re: uli526x doesn'\''t get link if no link when interface is set up' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).