tg3 fails to get link when kdump starts while using BCM5718
Issue
- On system with BCM5718 the kdump to remote host using ssh fails 3 out of 5 tries because no link is detected.
- The following messages are displayed when it fails:
mapping eth0 to eth0 Saving to remote location root@192.168.110.23 lost connection Attempting to enter user-space to capture vmcore - Please note that:
- The normal kernel always works.
- The problem doesn't happen when testing NetXtream BCM5709 NIC, which unfortunately uses bnx2 driver, instead of tg3.
- Using a small static compiled application to set autoneg on after bring the interface UP to force a PHY reset didn't help.
- passing acpi=off didn't help.
- adding "link_delay 120" still fails 1 out of 5 tries.
eth0 Link Up. Waiting 120 Seconds Continuing Saving to remote location root@XXX.XXX.XXX.XXX lost connection ... Shutting down interface eth0: tg3: eth0: Link is up at 1000 Mbps, full duplex. tg3: eth0: Flow control is on for TX and on for RX - If the interface used by kdump is NOT brought UP in the normal kernel, then it works 100% of the attempts.
- Looping doing ifup eth0; ifdown eth0; in the normal kernel always get a link established.
Environment
- Red Hat Enterprise Linux 5.6
- Red Hat Enterprise Linux 6.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.