From: Andre Tomt <andre@tomt.net>
To: netdev@oss.sgi.com
Subject: tg3 link state detection
Date: Tue, 21 Sep 2004 17:55:28 +0200 [thread overview]
Message-ID: <41504EF0.4050208@tomt.net> (raw)
With 2.6.8(.1)+the add_pin_to_irq fix we're seeing problem with link
state detection using tg3 devices. The network in question has a severe
case of cable monkeys, so the link is a bit jumpy.
From time to time the tg3's do not detect that the link is up again,
and thus has to be rebooted (ifdown/up has not been tested due to
triggerhappy non-technical on-site monkeys.)
Is this a known problem?
> tg3.c:v3.8 (July 14, 2004)
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 185
> eth0: Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:fe:4f:e7
> eth0: HostTXDS[1] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> ACPI: PCI interrupt 0000:02:00.1[B] -> GSI 17 (level, low) -> IRQ 193
> eth1: Tigon3 [partno(BCM95704A6) rev 2002 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:fe:4f:e8
> eth1: HostTXDS[1] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
next reply other threads:[~2004-09-21 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 15:55 Andre Tomt [this message]
2004-09-21 15:58 ` tg3 link state detection Andre Tomt
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=41504EF0.4050208@tomt.net \
--to=andre@tomt.net \
--cc=netdev@oss.sgi.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).