RE: Returning Network stability problems on R710 servers and BCM5709

2010-02-03 Thread Stephan van Hienen
No issues on a new R510 server. I have transferred a few TB's the past days with full gigabit speeds (arround 100Megabyte/sec using rsync) OS Redhat 5.4 kernel 2.6.18-164.11.1.el5 component type: BIOS current version: 1.1.4 component: NetXtreme II BCM5716 Gigabit Ethernet rev 20 (eth0)

RE: PowerEdge 1950 ECC question...

2010-02-03 Thread Henrik Schmiediche
The RAM passes Memtest86+ v4.0. I know it is strange. - Henrik -Original Message- From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Hostmaster Sent: Wednesday, February 03, 2010 10:27 AM To: linux-powere...@lists.us.dell.com Subject: RE:

RE: PowerEdge 1950 ECC question...

2010-02-03 Thread Henrik Schmiediche
Did that. The system is up using new RAM and OMSA and related utilities are running. There are no memory related entries in the ESM log. Old ram freezes system, but no error of any kind is generated in ESM, memtest, mpmemory, dell diags. -Henrik -Original Message- From:

Re: PowerEdge 1950 ECC question...

2010-02-03 Thread Tim Small
It seems probable that the memory fault is causing the BIOS to crash before it gets a chance to enable ECC - thus no errors are logged. It could also be a bus-loading issue with the FB-DIMMs (such that no memory can be issued - maybe a faulty AMB chip on one of the sticks). Try the system

Re: R410's shipped out with BIOS showing 4 cores instead of 8

2010-02-03 Thread Matt Domsch
On Sun, Jan 31, 2010 at 10:05:40AM -0600, Rahul Nabar wrote: Has anyone seen this problem before? I have dual socket Nehalems with twin quad core chips. When I booted the OS it showed only 4 cores. I went to the BIOS and found under Processor Settings the entry Cores-per-processor set to Dual

R210 / L3426 power consumption figures - 40w idle!

2010-02-03 Thread Tim Small
Hi, I've had an R210 recently to set up for a client and thought I'd share the power consumption figures that I recorded with the list. Basically, very impressive results IMO, when you consider the last R200 (X3220) which I set up used 135-odd watts idle... Disks: 2x 250G Seagate ES.3 SATA

Re: R210 / L3426 power consumption figures - 40w idle!

2010-02-03 Thread Matt Domsch
On Wed, Feb 03, 2010 at 05:33:59PM +, Tim Small wrote: The CPU frequency scaling module doesn't seem to load. This is either because Dell's BIOS doesn't support it, or it Dell's BIOS cpu frequency interface doesn't work with the Debian Lenny kernel. The Dell Advanced Power Control feature

memory and drive test.

2010-02-03 Thread Noble Athimattathil
Hello, Can someone please hook me up with the link to the latest dell online and offline memory and drive tests? Also was wondering if these tests can be preformed on non-dell systems. Thanks, Noble Athimattathil admob Enriching Mobile no...@admob.commailto:no...@admob.com P: (415) 533 1317

RE: PowerEdge 1950 ECC question...

2010-02-03 Thread Henrik Schmiediche
Hmm... the parts in the Dell where Dell parts, the replacement parts (that work) are non-Dell. Before the RAM swap fixed the problem I thought the problem might be mainboard as well (and it still may be). I am not sure how I will proceed, but you are right in think this may be a voltage/main

Re: PowerEdge 1950 ECC question...

2010-02-03 Thread Tim Small
Henrik Schmiediche wrote: My original question (turning of ECC for memory testing) was hopefully going to narrow down the issue. It's probably possible to disable ECC after boot time using setpci (I've used it to read and write the ECC status registers on Intel chipsets in the past), but

OMSA help in unsupported install...

2010-02-03 Thread Eric Rostetter
I'm trying to install what is probably an unsupported OMSA (5.1.0) on a very much unsupported OS (rpath linux, specifically OpenFiler NAS/SAN appliance 2.3). And I'm hoping despite that maybe someone on this list might be able to help me. :) I have OMSA installed and running. omreport works

Public key for Server_BIOS rpm is not installed

2010-02-03 Thread Rodney McKee
Updating the BIOS etc on an RHEL systems results in the following: yum install $(bootstrap_firmware) ...

Re: Public key for Server_BIOS rpm is not installed

2010-02-03 Thread J. Epperson
On Wed, February 3, 2010 20:44, Rodney McKee wrote: Updating the BIOS etc on an RHEL systems results in the following: yum install $(bootstrap_firmware) ...

Re: Public key for Server_BIOS rpm is not installed

2010-02-03 Thread Rodney McKee
That look promising, will try that on the next system. This certainly is a big improvement for maintaining firmware levels. But are their any detailed logs for these processes that might explain why this failed? /var/log/firmware-updates.log does not exactly say much. What sorta msg is: Update

Re: Public key for Server_BIOS rpm is not installed

2010-02-03 Thread Rodney McKee
Hmm, What key needs to be installed? I'm starting to look at systems that I like to ensure have valid keys for packages on and again getting errors: warning: rpmts_HdrFromFdno: Header V4 DSA signature: NOKEY, key ID 5e3d7775 fwupdate/gpgkey | 1.4 kB 00:00 Public key for