[rhn-users] Re: Net interface flap, Dell 2650, RH ES 3.0, 2.4.21-15.ELsmp, Broadcom BCM5701

Tim Pickard tpickard at crossref.org
Tue May 25 15:56:36 UTC 2004 

Jed,

You may have better luck at the Dell Linux site and specifically the
PowerEdge list.  I have the same 2650's but have not upgraded or experienced
those problems yet.  Odds are you will get good help on the list.  The
archives have been very helpful.

http://linux.dell.com/
Linux-PowerEdge at dell.com

Tim Pickard
Systems Support Analyst and Administrator
crossref.org

-----Original Message-----
From: rhn-users-bounces at redhat.com
[mailto:rhn-users-bounces at redhat.com]On Behalf Of
rhn-users-request at redhat.com
Sent: Tuesday, May 25, 2004 9:39 AM
To: rhn-users at redhat.com
Subject: rhn-users Digest, Vol 3, Issue 26


Send rhn-users mailing list submissions to
	rhn-users at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.redhat.com/mailman/listinfo/rhn-users
or, via email, send a message with subject or body 'help' to
	rhn-users-request at redhat.com

You can reach the person managing the list at
	rhn-users-owner at redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of rhn-users digest..."


Today's Topics:

   1.  Net interface flap, Dell 2650, RH ES 3.0 2.4.21-15.ELsmp,
      Broadcom BCM5701 (Jed Donnelley)
   2. shared memory and hyperthreading (espen.ekeroth at om.com)
   3. rpms and NOKEY error when not using up2date (John Coroneus)
   4. still not working (kassim kasmani)
   5. Re:  Net interface flap, Dell 2650,	RH ES 3.0
      2.4.21-15.ELsmp, Broadcom BCM5701 (Maila Fatticcioni)
   6. Linksys PCI adapter WMP11 (El Gato Feo)
   7. Re: still not working (Corn? Beerse)


----------------------------------------------------------------------

Message: 1
Date: Mon, 24 May 2004 12:14:46 -0700
From: Jed Donnelley <jed at nersc.gov>
Subject: [rhn-users]  Net interface flap, Dell 2650, RH ES 3.0
	2.4.21-15.ELsmp, Broadcom BCM5701
To: rhn-users at redhat.com
Message-ID: <6.1.0.6.0.20040520164009.0694ccf0 at imap4.lbl.gov>
Content-Type: text/plain; charset="us-ascii"; format=flowed

I've been running RH ES 3.0 on a Dell 2650 server with for some time with a
GigE interface
with the Broadcom NetXtreme BCM5701 technology the tg3 driver, most
recently with the
2.4.21-9.0.1.ELsmp kernel.  Last week I tried upgrading to the
2.4.21-15.ELsmp kernel.
When I ran with that newer kernel the network interface on the box went
into a loop of
going up and down every few seconds.

Here's what I believe is the relevant part of the message log:

May 20 15:58:30 tsi kernel: Linux version 2.4.21-15.ELsmp
(bhcompile at bugs.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat
Linux 3.2.3-34)) #1 SMP Thu Apr 22 00:18:24 EDT 2004
...
May 20 15:58:31 tsi kernel: Processors: 4
May 20 15:58:31 tsi kernel: xAPIC support is present
May 20 15:58:31 tsi kernel: Enabling APIC mode: Flat.^IUsing 3 I/O APICs
May 20 15:58:31 tsi kernel: Kernel command line: ro root=/dev/md0
May 20 15:58:31 tsi kernel: Initializing CPU#0
May 20 15:58:31 tsi kernel: Detected 1993.566 MHz processor.
<actually 2 hyperthreaded procesors>
...
May 20 15:58:38 tsi kernel: eth0: Tigon3 [partno(BCM95701A10) rev 0105
PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f8:0f:04
May 20 15:58:38 tsi kernel: eth0: HostTXDS[0] RXcsums[1] LinkChgREG[1]
MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
May 20 15:58:38 tsi kernel: eth1: Tigon3 [partno(BCM95701A10) rev 0105
PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f8:0f:05
May 20 15:58:38 tsi kernel: eth1: HostTXDS[0] RXcsums[1] LinkChgREG[1]
MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
May 20 15:58:38 tsi kernel: ip_tables: (C) 2000-2002 Netfilter core team
May 20 15:58:38 tsi kernel: ip_conntrack version 2.1 (8192 buckets, 65536
max) - 304 bytes per conntrack
May 20 15:58:38 tsi kernel: tg3.c:v3.1 (April 3, 2004)
May 20 15:58:38 tsi kernel: eth0: Tigon3 [partno(BCM95701A10) rev 0105
PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f8:0f:04
May 20 15:58:38 tsi kernel: eth0: HostTXDS[0] RXcsums[1] LinkChgREG[1]
MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
May 20 15:58:38 tsi kernel: eth1: Tigon3 [partno(BCM95701A10) rev 0105
PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f8:0f:05
May 20 15:58:38 tsi kernel: eth1: HostTXDS[0] RXcsums[1] LinkChgREG[1]
MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
May 20 15:58:38 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
May 20 15:58:38 tsi kernel: tg3: eth0: Flow control is on for TX and on for
RX.
May 20 15:58:38 tsi kernel: tg3: eth0: Link is down.
May 20 15:58:38 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
May 20 15:58:38 tsi kernel: tg3: eth0: Flow control is on for TX and on for
RX.
...
May 20 15:58:43 tsi kernel: tg3: eth0: Link is down.
...
May 20 15:58:46 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
May 20 15:58:46 tsi kernel: tg3: eth0: Flow control is on for TX and on for
RX.
...
May 20 15:58:58 tsi kernel: tg3: eth0: Link is down.
May 20 15:59:01 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
May 20 15:59:01 tsi kernel: tg3: eth0: Flow control is on for TX and on for
RX.
May 20 15:59:02 tsi kernel: tg3: eth0: Link is down.
May 20 15:59:05 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
May 20 15:59:05 tsi kernel: tg3: eth0: Flow control is on for TX and on for
RX.
etc.

Here's the output from ethtool for the interface with the problem:

Settings for eth0:
         Supported ports: [ MII ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
                                 1000baseT/Half 1000baseT/Full
         Supports auto-negotiation: Yes
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
                                 1000baseT/Half 1000baseT/Full
         Advertised auto-negotiation: Yes
         Speed: 1000Mb/s
         Duplex: Full
         Port: Twisted Pair
         PHYAD: 1
         Transceiver: internal
         Auto-negotiation: on
         Supports Wake-on: g
         Wake-on: d
         Current message level: 0x000000ff (255)
         Link detected: no

With the older 2.4.21-9.0.1.ELsmp kernel I get the same output except
that I get:
...
         Link detected: yes

with no flapping and with the interface up and functioning.

Has anybody else seen a comparable problem with 2.4.21-15.EL or 2.4.21-15.WS
with a GigE interface with the Broadcom NetXtreme BCM5701 using the tg3
driver?

I wonder if this problem is related to:

http://www.redhat.com/archives/fedora-test-list/2004-April/msg01880.html

?  I'm open to any suggestions.  I certainly don't want a network interface
problem blocking my kernel updates.

--Jed http://www.nersc.gov/~jed/




------------------------------

Message: 2
Date: Mon, 24 May 2004 23:29:13 +0200
From: espen.ekeroth at om.com
Subject: [rhn-users] shared memory and hyperthreading
To: rhn-users at redhat.com
Message-ID: <C1256E9E.0075FB4A.00 at omext02.omgroup.com>
Content-Type: text/plain; charset="us-ascii"





Our application is not running to well on RH ES 3.0 with the SMP kernel - it
seems to be a problem with the hyperthreading and shared memory or signals.
The
application is stable on RedHat 9 and RedHat ES 3.0 with the EL kernel.

Is there any special items I should be aware of when moving an appication
from
kernel 2.4 to 2.6 or moving to a hyperthreading CPU?

The application is written in C, and the program is compiled on a Compaq
Proliant 360 - P3 running RedHat 9.0 with gcc-3.2.2-5 (std installation -
nothing special). Deployment on Compaq Proliant 380- P4 running RedHat ES
3.0.

Espen





****************************************************************************
****
This e-mail and the information it contains may be privileged and/or
confidential.  It is for the intended addressee(s) only.
The unauthorised use, disclosure or copying of this e-mail, or any
information it contains, is prohibited.
If you are not an intended recipient, please contact the sender and delete
the material from your computer.
****************************************************************************
****




------------------------------

Message: 3
Date: Mon, 24 May 2004 16:00:38 -0700
From: "John Coroneus" <jcoroneu at uci.edu>
Subject: [rhn-users] rpms and NOKEY error when not using up2date
To: <rhn-users at redhat.com>
Message-ID: <013701c441e2$ee5b4630$6197c380 at NOTEBOOK02>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,

I have a setup with two workstation computers (running redhat Ent WS) that
are connected ONLY to a server (running Ent AS) that is in turn connected to
the internet.  I want to update these with rpms, but up2date on these
machines has no direct access to the internet, so I've been downloading the
rpms via the up2date on the server, then copying them down to the other
machines and installing them using rpm -Fvh.  This works for some packages,
but I've been getting a lot of NOKEY errors and packages not installing.

I think that I have the same key in /usr/share/rhn on the two workstation
machines. Anyone have an idea how I can make this configuration work without
having to put these workstations on the internet?

Thanks in advance,

jc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /archives/rhn-users/attachments/20040524/327e3824/attachment.htm

------------------------------

Message: 4
Date: Tue, 25 May 2004 00:28:21 -0400
From: kassim kasmani <kassim.k at glensquare.com>
Subject: [rhn-users] still not working
To: Red Hat Network Users List <rhn-users at redhat.com>
Message-ID: <40B2CB65.7060807 at glensquare.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

I havent been able to update my redhat ws3 for weeks now!  It will just
freeze on its own.  I have the latest up2date files.

Here is what I get:

Testing package set / solving RPM inter-dependencies...
########################################
GConf2-2.2.1-4.i386.rpm:    ########################## Done.
MAKEDEV-3.3.12-1.i386.rpm:  ########################## Done.
SysVinit-2.85-4.2.i386.rpm: ########################## Done.
XFree86-4.3.0-62.EL.i386.rp #                           30 k/sec,
00:06:45 rem.


As soon as it reaches "XFree86-4.3.0-62.EL.i386.rpm" package, it will
freeze.

Any auggestions?




------------------------------

Message: 5
Date: Tue, 25 May 2004 10:51:09 +0200
From: Maila Fatticcioni <mfatticcioni at mbigroup.it>
Subject: Re: [rhn-users]  Net interface flap, Dell 2650,	RH ES 3.0
	2.4.21-15.ELsmp, Broadcom BCM5701
To: Red Hat Network Users List <rhn-users at redhat.com>
Message-ID: <40B308FD.8060904 at mbigroup.it>
Content-Type: text/plain; charset=us-ascii; format=flowed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.
Do you force the full duplex in the modules.conf file?
You have to type these lines:

alias eth0 bcm5701
options bcm5701 auto_speed=0 full_duplex=1 line_speed=1000

Maila

Jed Donnelley wrote:
| I've been running RH ES 3.0 on a Dell 2650 server with for some time
| with a GigE interface
| with the Broadcom NetXtreme BCM5701 technology the tg3 driver, most
| recently with the
| 2.4.21-9.0.1.ELsmp kernel.  Last week I tried upgrading to the
| 2.4.21-15.ELsmp kernel.
| When I ran with that newer kernel the network interface on the box went
| into a loop of
| going up and down every few seconds.
|
| Here's what I believe is the relevant part of the message log:
|
| May 20 15:58:30 tsi kernel: Linux version 2.4.21-15.ELsmp
| (bhcompile at bugs.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat
| Linux 3.2.3-34)) #1 SMP Thu Apr 22 00:18:24 EDT 2004
| ...
| May 20 15:58:31 tsi kernel: Processors: 4
| May 20 15:58:31 tsi kernel: xAPIC support is present
| May 20 15:58:31 tsi kernel: Enabling APIC mode: Flat.^IUsing 3 I/O APICs
| May 20 15:58:31 tsi kernel: Kernel command line: ro root=/dev/md0
| May 20 15:58:31 tsi kernel: Initializing CPU#0
| May 20 15:58:31 tsi kernel: Detected 1993.566 MHz processor.
| <actually 2 hyperthreaded procesors>
| ...
| May 20 15:58:38 tsi kernel: eth0: Tigon3 [partno(BCM95701A10) rev 0105
| PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet
00:06:5b:f8:0f:04
| May 20 15:58:38 tsi kernel: eth0: HostTXDS[0] RXcsums[1] LinkChgREG[1]
| MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
| May 20 15:58:38 tsi kernel: eth1: Tigon3 [partno(BCM95701A10) rev 0105
| PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet
00:06:5b:f8:0f:05
| May 20 15:58:38 tsi kernel: eth1: HostTXDS[0] RXcsums[1] LinkChgREG[1]
| MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
| May 20 15:58:38 tsi kernel: ip_tables: (C) 2000-2002 Netfilter core team
| May 20 15:58:38 tsi kernel: ip_conntrack version 2.1 (8192 buckets,
| 65536 max) - 304 bytes per conntrack
| May 20 15:58:38 tsi kernel: tg3.c:v3.1 (April 3, 2004)
| May 20 15:58:38 tsi kernel: eth0: Tigon3 [partno(BCM95701A10) rev 0105
| PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet
00:06:5b:f8:0f:04
| May 20 15:58:38 tsi kernel: eth0: HostTXDS[0] RXcsums[1] LinkChgREG[1]
| MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
| May 20 15:58:38 tsi kernel: eth1: Tigon3 [partno(BCM95701A10) rev 0105
| PHY(5701)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet
00:06:5b:f8:0f:05
| May 20 15:58:38 tsi kernel: eth1: HostTXDS[0] RXcsums[1] LinkChgREG[1]
| MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
| May 20 15:58:38 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full
| duplex.
| May 20 15:58:38 tsi kernel: tg3: eth0: Flow control is on for TX and on
| for RX.
| May 20 15:58:38 tsi kernel: tg3: eth0: Link is down.
| May 20 15:58:38 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full
| duplex.
| May 20 15:58:38 tsi kernel: tg3: eth0: Flow control is on for TX and on
| for RX.
| ...
| May 20 15:58:43 tsi kernel: tg3: eth0: Link is down.
| ...
| May 20 15:58:46 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full
| duplex.
| May 20 15:58:46 tsi kernel: tg3: eth0: Flow control is on for TX and on
| for RX.
| ...
| May 20 15:58:58 tsi kernel: tg3: eth0: Link is down.
| May 20 15:59:01 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full
| duplex.
| May 20 15:59:01 tsi kernel: tg3: eth0: Flow control is on for TX and on
| for RX.
| May 20 15:59:02 tsi kernel: tg3: eth0: Link is down.
| May 20 15:59:05 tsi kernel: tg3: eth0: Link is up at 1000 Mbps, full
| duplex.
| May 20 15:59:05 tsi kernel: tg3: eth0: Flow control is on for TX and on
| for RX.
| etc.
|
| Here's the output from ethtool for the interface with the problem:
|
| Settings for eth0:
|         Supported ports: [ MII ]
|         Supported link modes:   10baseT/Half 10baseT/Full
|                                 100baseT/Half 100baseT/Full
|                                 1000baseT/Half 1000baseT/Full
|         Supports auto-negotiation: Yes
|         Advertised link modes:  10baseT/Half 10baseT/Full
|                                 100baseT/Half 100baseT/Full
|                                 1000baseT/Half 1000baseT/Full
|         Advertised auto-negotiation: Yes
|         Speed: 1000Mb/s
|         Duplex: Full
|         Port: Twisted Pair
|         PHYAD: 1
|         Transceiver: internal
|         Auto-negotiation: on
|         Supports Wake-on: g
|         Wake-on: d
|         Current message level: 0x000000ff (255)
|         Link detected: no
|
| With the older 2.4.21-9.0.1.ELsmp kernel I get the same output except
| that I get:
| ...
|         Link detected: yes
|
| with no flapping and with the interface up and functioning.
|
| Has anybody else seen a comparable problem with 2.4.21-15.EL or
| 2.4.21-15.WS
| with a GigE interface with the Broadcom NetXtreme BCM5701 using the tg3
| driver?
|
| I wonder if this problem is related to:
|
| http://www.redhat.com/archives/fedora-test-list/2004-April/msg01880.html
|
| ?  I'm open to any suggestions.  I certainly don't want a network
interface
| problem blocking my kernel updates.
|
| --Jed http://www.nersc.gov/~jed/
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAswj9i2q3wPb3FcMRAkcxAKCbUqgVg+Z3rwqVP4/OjDOmloduPwCgqDAu
guH6AW3yBWBwBldRPtorPyY=
=TZyh
-----END PGP SIGNATURE-----




------------------------------

Message: 6
Date: Mon, 24 May 2004 22:12:45 -0700 (PDT)
From: El Gato Feo <dave_almaraz at pacbell.net>
Subject: [rhn-users] Linksys PCI adapter WMP11
To: Red Hat Network Users List <rhn-users at redhat.com>
Message-ID: <20040525051245.47512.qmail at web80701.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii

Do you know where I can get the drivers for this
device?
I will be setting up my RedHat 9 as a wireless node.
Any tips, warnings and encouragement are appreciated.


El Gato Feo




------------------------------

Message: 7
Date: Tue, 25 May 2004 10:45:15 +0200
From: Corn? Beerse <cbeerse at lycos.nl>
Subject: Re: [rhn-users] still not working
To: Red Hat Network Users List <rhn-users at redhat.com>
Message-ID: <40B3079B.1060000 at lycos.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed

kassim kasmani wrote:

> I havent been able to update my redhat ws3 for weeks now!  It will just
> freeze on its own.  I have the latest up2date files.
>
> Here is what I get:
>
> Testing package set / solving RPM inter-dependencies...
> ########################################
> GConf2-2.2.1-4.i386.rpm:    ########################## Done.
> MAKEDEV-3.3.12-1.i386.rpm:  ########################## Done.
> SysVinit-2.85-4.2.i386.rpm: ########################## Done.
> XFree86-4.3.0-62.EL.i386.rp #                           30 k/sec,
> 00:06:45 rem.
>
>
> As soon as it reaches "XFree86-4.3.0-62.EL.i386.rpm" package, it will
> freeze.


Check the quality of the XFree rpm file if it is complete.
If it is not complete or in error, download it manually.

You will notice it is a little larger than an average package. Then if XFree
is
running while it is updated, that might also cosume more time.

In the end, patience will help too.


CBee




------------------------------

_______________________________________________
rhn-users mailing list
rhn-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-users


End of rhn-users Digest, Vol 3, Issue 26
****************************************

More information about the rhn-users mailing list