From: Nils Holland <nholland@tisys.org>
To: netdev@vger.kernel.org
Subject: tg3 broken in 3.18.0?
Date: Thu, 11 Dec 2014 00:06:34 +0100 [thread overview]
Message-ID: <20141210230634.GA22884@teela.fritz.box> (raw)
Hi everyone,
I just upgraded a machine from 3.17.3 to 3.18.0 and noticed that after
the upgrade, the machine's network interface (which is a tg3) would no
longer run correctly (or, for that matter, run at all). During the
upgrade, I didn't change any kernel config options or any other parts
of the system.
Since the machine is remote and I don't have direct access to it, it's
kind of hard currently to give more details, but here's what I'm
seeing in the logs:
[Booting 3.17.3:]
[ 1.383151] tg3.c:v3.137 (May 11, 2014)
[ 1.387296] libphy: tg3 mdio bus: probed
[ 1.452600] tg3 0000:02:00.0 eth0:
Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address
00:19:99:ce:13:a6
[ 1.454660] tg3 0000:02:00.0 eth0:
attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=200:01)
[ 1.456764] tg3 0000:02:00.0 eth0:
RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[ 1.458911] tg3 0000:02:00.0 eth0:
dma_rwctrl[76180000] dma_mask[64-bit]
[...]
[ 6.602608] tg3 0000:02:00.0
enp2s0: renamed from eth0
[ 9.865638] tg3 0000:02:00.0: irq 25 for MSI/MSI-X
[ 9.887584] IPv6:
ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 10.469819] tg3 0000:02:00.0
enp2s0: Link is down
[ 12.477396] tg3 0000:02:00.0
enp2s0: Link is up at 100 Mbps, full duplex
[ 12.477404] tg3 0000:02:00.0
enp2s0: Flow control is off for TX and off for RX
[Booting 3.18.0:]
[ 2.192915] tg3.c:v3.137 (May 11, 2014)
[ 2.196767] libphy: tg3 mdio bus: probed
[ 2.256294] tg3 0000:02:00.0 eth0:
Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address
00:19:99:ce:13:a6
[ 2.258387] tg3 0000:02:00.0 eth0:
attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=200:01)
[ 2.260530] tg3 0000:02:00.0 eth0:
RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[ 2.262679] tg3 0000:02:00.0 eth0:
dma_rwctrl[76180000] dma_mask[64-bit]
[...]
[ 7.431176] tg3 0000:02:00.0
enp2s0: renamed from eth0
[ 10.422839] tg3 0000:02:00.0: irq 25 for MSI/MSI-X
[ 12.530363] tg3 0000:02:00.0
enp2s0: No firmware running
That's the last thing I find about the card in the logs, the machine
will then just sit there, working normally but being unreachable from
the network.
If I see things correctly, there were only two patches affecting tg3
between 3.17(.3) and 3.18:
2c7c9ea429ba30fe506747b7da110e2212d8fefa
a620a6bc1c94c22d6c312892be1e0ae171523125
The affected machine being, like I said, remote, I've not yet been
able to do more thorough tests. So I thought I'd report the issue and
see if someone else has also seen it already, or can test things with
a more easily accesible machine. Otherwise, I might start digging
deeper.
Greetings,
Nils
next reply other threads:[~2014-12-10 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:06 Nils Holland [this message]
2014-12-11 16:45 ` tg3 broken in 3.18.0? Marcelo Ricardo Leitner
2014-12-12 14:50 ` Jonathan Bither
2014-12-12 20:31 ` Nils Holland
2014-12-13 1:14 ` [bisected] " Nils Holland
2014-12-13 1:18 ` David Miller
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=20141210230634.GA22884@teela.fritz.box \
--to=nholland@tisys.org \
--cc=netdev@vger.kernel.org \
/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).