<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Link down messages once Broadcom drivers are loaded during bootup in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621084#M85166</link>
    <description>&lt;BR /&gt;I believe bcm5700 drivers are old and deprecated, use the new 'tg3' drivers.&lt;BR /&gt;&lt;BR /&gt;update your modprobe.conf file with tg3 drivers and see whether it works for you.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gopi</description>
    <pubDate>Thu, 08 Sep 2005 00:15:04 GMT</pubDate>
    <dc:creator>Gopi Sekar</dc:creator>
    <dc:date>2005-09-08T00:15:04Z</dc:date>
    <item>
      <title>Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621083#M85165</link>
      <description>I recently patched a DL560 machine from RHEL 3 update 4 to RHEL 3 update 5.  After the process was complete, I rebooted the system to use the 2.4.21-32.0.1.ELsmp kernel.  During the boot process eth0 and eth1 (which are the on board broadcom interfaces) show up as OK.  However, once I get beyond that point I see the bcm5700: Link Down message on both interfaces.&lt;BR /&gt;&lt;BR /&gt;I was able to get them to work by downing both interfaces, running a modprob -r bcm5700 to remove the driver, and then reinstalling the module by running insmod bcm5700.  It detects both interfaces and they come right up.  The modules.conf has the alias set for eth0 and eth1 to be bcm5700.  Does anyone have any suggestions or further steps to take to resolve this issue?  Thanks.</description>
      <pubDate>Wed, 07 Sep 2005 16:09:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621083#M85165</guid>
      <dc:creator>Joseph Cipolla</dc:creator>
      <dc:date>2005-09-07T16:09:46Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621084#M85166</link>
      <description>&lt;BR /&gt;I believe bcm5700 drivers are old and deprecated, use the new 'tg3' drivers.&lt;BR /&gt;&lt;BR /&gt;update your modprobe.conf file with tg3 drivers and see whether it works for you.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gopi</description>
      <pubDate>Thu, 08 Sep 2005 00:15:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621084#M85166</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-09-08T00:15:04Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621085#M85167</link>
      <description>The system was actually using the tg3 drivers first and I loaded the bcm5700 driver as a fix, but both were experiencing the same issue.  The date according to Broadcom for the driver is 8-23-05.  Is there a newer tg3 driver than this that I can acquire?  Thanks.</description>
      <pubDate>Thu, 08 Sep 2005 08:51:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621085#M85167</guid>
      <dc:creator>Joseph Cipolla</dc:creator>
      <dc:date>2005-09-08T08:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621086#M85168</link>
      <description>&lt;BR /&gt;Check the Proliant support pack 7.40 version it should contain the updated tg3 driver if exists.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gopi</description>
      <pubDate>Thu, 08 Sep 2005 09:06:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621086#M85168</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-09-08T09:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621087#M85169</link>
      <description>I only see the support pack version 7.30, I downloaded the bcm5700 driver individually and installed it.  Here is the output from dmesg:&lt;BR /&gt;&lt;BR /&gt;ip_tables: (C) 2000-2002 Netfilter core team&lt;BR /&gt;Broadcom Gigabit Ethernet Driver bcm5700 with Broadcom NIC Extension (NICE) ver. 8.2.18a (08/01/05)&lt;BR /&gt;divert: allocating divert_blk for eth0&lt;BR /&gt;eth0: HP NC7781 Gigabit Server Adapter found at mem f7ef0000, IRQ 11, node addr 000bcd0de167&lt;BR /&gt;eth0: Broadcom BCM5703 Integrated Copper transceiver found&lt;BR /&gt;eth0: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON, 802.1Q VLAN ON, NAPI ON&lt;BR /&gt;divert: allocating divert_blk for eth1&lt;BR /&gt;eth1: HP NC7781 Gigabit Server Adapter found at mem f7ee0000, IRQ 15, node addr 000bcd0de168&lt;BR /&gt;eth1: Broadcom BCM5703 Integrated Copper transceiver found&lt;BR /&gt;eth1: Scatter-gather ON, 64-bit DMA ON, Tx Checksum ON, Rx Checksum ON, 802.1Q VLAN ON, NAPI ON&lt;BR /&gt;ip_tables: (C) 2000-2002 Netfilter core team&lt;BR /&gt;eth0: Using PCI INTX interrupt&lt;BR /&gt;ip_tables: (C) 2000-2002 Netfilter core team&lt;BR /&gt;eth1: Using PCI INTX interrupt&lt;BR /&gt;bcm5700: eth0 NIC Link is UP, 1000 Mbps full duplex&lt;BR /&gt;Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2-NAPI&lt;BR /&gt;Copyright (c) 1999-2004 Intel Corporation.&lt;BR /&gt;divert: allocating divert_blk for eth2&lt;BR /&gt;e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection&lt;BR /&gt;divert: allocating divert_blk for eth3&lt;BR /&gt;e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection&lt;BR /&gt;ip_tables: (C) 2000-2002 Netfilter core team&lt;BR /&gt;bcm5700: eth1 NIC Link is UP, 1000 Mbps full duplex&lt;BR /&gt;ip_tables: (C) 2000-2002 Netfilter core team&lt;BR /&gt;e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;lp: driver loaded but no devices found&lt;BR /&gt;usb.c: registered new driver serial&lt;BR /&gt;usbserial.c: USB Serial support registered for Generic&lt;BR /&gt;usbserial.c: USB Serial Driver core v1.4&lt;BR /&gt;bcm5700: eth0 NIC Link is Down&lt;BR /&gt;bcm5700: eth1 NIC Link is Down&lt;BR /&gt;mtrr: type mismatch for f6000000,800000 old: uncachable new: write-combining&lt;BR /&gt;mtrr: type mismatch for f6000000,800000 old: uncachable new: write-combining&lt;BR /&gt;e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;&lt;BR /&gt;Like before, during bootup the screen shows OK for starting the interfaces, but then shows link down.  The only way I have been able to restore the connections is when I do a modprobe -r bcm5700 then insmod bcm5700.  This restores the link as normal.  Am I missing something else here?&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Sep 2005 09:28:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621087#M85169</guid>
      <dc:creator>Joseph Cipolla</dc:creator>
      <dc:date>2005-09-09T09:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621088#M85170</link>
      <description>&lt;SNIP&gt;&lt;BR /&gt;bcm5700: eth0 NIC Link is Down&lt;BR /&gt;bcm5700: eth1 NIC Link is Down&lt;BR /&gt;mtrr: type mismatch for f6000000,800000 old: uncachable new: write-combining&lt;BR /&gt;mtrr: type mismatch for f6000000,800000 old: uncachable new: write-combining&lt;BR /&gt;e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex&lt;BR /&gt;&lt;SNIP&gt;&lt;BR /&gt;&lt;BR /&gt;I believe something is happening here. How many Ethernet interfaces you have in this box? According to dmesg output there are 4 ethernet NICs (two broadcom and two Intel). &lt;BR /&gt;&lt;BR /&gt;Also it shows that when broadcom link goes down, Intel nics are coming up!! pretty strange. I assume both are happening almost at the same time. Are you having some sort of load balancing configuration in your network? if it is so then the problem might be there. Also try disabling the intel NICs completely by commenting eth2 and eth3 (containing e1000) lines in /etc/modprobe.conf file, reboot the system and let us know how it goes.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gopi&lt;/SNIP&gt;&lt;/SNIP&gt;</description>
      <pubDate>Fri, 09 Sep 2005 09:37:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621088#M85170</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-09-09T09:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: Link down messages once Broadcom drivers are loaded during bootup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621089#M85171</link>
      <description>I did what you suggested, eth2 and eth3 did not load or plumb up the interfaces.  The same problem still occurred with eth0 and eth1.</description>
      <pubDate>Fri, 09 Sep 2005 16:12:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/link-down-messages-once-broadcom-drivers-are-loaded-during/m-p/3621089#M85171</guid>
      <dc:creator>Joseph Cipolla</dc:creator>
      <dc:date>2005-09-09T16:12:15Z</dc:date>
    </item>
  </channel>
</rss>

