headers
Sébastien Estienne | 1 Jan 2007 16:26
Picon
Gravatar

Re: PE 1850/2800: BIOS A06 and IPMI access

Bram Metsch a écrit :
> Hi,
> 
> after upgrading the BIOS to revision A06, the kernel cannot find the IPMI
> device any more:
> 
> prompt# modprobe ipmi_si
> FATAL: Error inserting ipmi_si
(/lib/modules/2.6.15-26-amd64-server/kernel/drivers/char/ipmi/ipmi_si.ko): No such device
> 
> I use the following parameters for the ipmi device:
> 
> options ipmi_si type="kcs" ports="0xca8" regspacings="4"
> 
> which work perfectly for BIOS revision A04
> 
> dmesg tells me:
> 
> [1831781.675142] IPMI System Interface driver.
> [1831781.675151] ipmi_si: Trying "kcs" at I/O port 0xca8
> [1831781.675157]  Could not set up I/O space
> [1831781.687878] Trying to free nonexistent resource <00000ca8-00000cac>
> [1831781.687902] ipmi_si: Unable to find any System Interface(s)
> 
> dmidecode says:
> 
> IPMI Device Information
>         Interface Type: KCS (Keyboard Control Style)
>         Specification Version: 1.5
>         I2C Slave Address: 0x10
(Continue reading)

Permalink | Reply | 0 comments |
headers
Krishnaprasad_K | 2 Jan 2007 05:34
Picon
Favicon

RE: "command response could not be provided"


Are you using the correct BMC firmware version available .

-----Original Message-----
From: linux-poweredge-bounces <at> dell.com
[mailto:linux-poweredge-bounces <at> dell.com] On Behalf Of Rob Munsch
Sent: Friday, December 29, 2006 10:54 PM
To: linux-poweredge-Lists
Subject: "command response could not be provided"

I've gotten the IPMI drivers, ipmitool, and assorted other goodies all
working on a Poweredge 1750, but half the sensors come up with (very
verbose) errors, thusly:

-----
~# ipmitool sdr
Basebrd Mgt Ctlr | Static MC  <at>  20h   | ok
Error reading sensor CPU 1 (#01): Command response could not be provided
Error reading sensor CPU 2 (#02): Command response could not be provided
Error reading sensor CPU 3 (#03): Command response could not be provided
Error reading sensor CPU 4 (#04): Command response could not be provided
CPU Planar       | 32 degrees C      | ok
Ambient          | 19 degrees C      | ok
CPU              | 1.51 Volts        | ok
-----

Is this a problem with the BMC itself, does it mean those sensors aren't
present, did i not do this right, all three, or something else..?

--
(Continue reading)

Permalink | Reply | 5 comments |
headers
Harald_Jensas | 2 Jan 2007 09:36
Picon
Favicon

RE: IPMItool returns false value on PowerEdge 1950

> -----Original Message-----
> From: Simon Gao [mailto:gao <at> schrodinger.com] 
> Sent: 29 December 2006 20:39
> To: Jensas, Harald
> Cc: linux-poweredge-Lists
> Subject: Re: IPMItool returns false value on PowerEdge 1950
> 
> Harald_Jensas <at> dell.com wrote:
> >> To: linux-poweredge-Lists
> >> Subject: Re: IPMItool returns false value on PowerEdge 1950
> >>
> >>     
> >
> > Have a look at page 86, 87 and 89 in this document.
> >
> > http://www.intel.com/design/xeon/datashts/313355.htm
> >
> > There is no diode in the new processors to read an absolute 
> CPU temperature from. The value you are seeing as negative is 
> a releative value that the system use to control the fan's.
> >
> > Quote:
> > "Fan speed control solutions utilize a TControl value stored in the 
> > processor IA32_TEMPERATURE_TARGET MSR. Prior to Dual-Core 
> Intel Xeon 
> > Processor 5100 Series, TControl represented a diode 
> temperature. With 
> > Dual-Core Intel Xeon Processor 5100 Series, TControl represents an 
> > offset from TCC activation temperature.The DTS outputs temperature 
> > offsets over the PECI interface in response to a GetTemp0()
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kevin Foote | 2 Jan 2007 15:53
Picon

sense errors..

hi all
some questions here.
I have multiple pe6800 boxes with the same disk configuration.
we are using linux md raid. each 73g drive is partitioned with boot, /, and swap thats it.
md1 = /boot
md3 = /

I am getting multiple boxes with identical errors at boot time, but the boxes all come up
and the raid sets are mounted etc.. I'd like to believe that these are simple disk errors but
they are at same sector / block on the different servers .. this is a bit odd to me. I guess
It could infact be a bad run of disks?? All the sense errors seem to be on sd[a,b]3 which
would equate to the / partition.

Again I just want to bounce this problem off a few people framiliar with PE hardware and
the linux kernel to make sure I don't replace all my disks  for  a non issue.

Dec 28 05:46:28 hostX kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 08 8b 8f 0f 0
0 00 80 00
Dec 28 05:46:28 hostX kernel: Info fld=0x88b8f17, Current sda: sense key Medium Error
Dec 28 05:46:28 hostX kernel: Additional sense: Data synchronization mark error
Dec 28 05:46:28 hostX kernel: end_request: I/O error, dev sda, sector 143363863
Dec 28 05:46:28 hostX kernel: Buffer I/O error on device sda3, logical block 129756808
Dec 28 05:46:28 hostX kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 08 8b 8f 18 0
0 00 77 00
Dec 28 05:46:28 hostX kernel: Info fld=0x88b8f18, Current sda: sense key Medium Error
Dec 28 05:46:28 hostX kernel: Additional sense: Data synchronization mark error
Dec 28 05:46:28 hostX kernel: end_request: I/O error, dev sda, sector 143363864
Dec 28 05:46:29 hostX kernel: Buffer I/O error on device sda3, logical block 129756809
Dec 28 05:46:29 hostX kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 08 8b 8f 19 0
0 00 76 00
Dec 28 05:46:29 hostX kernel: Info fld=0x88b8f19, Current sda: sense key Medium Error
Dec 28 05:46:29 hostX kernel: Additional sense: Data synchronization mark error
Dec 28 05:46:29 hostX kernel: end_request: I/O error, dev sda, sector 143363865
Dec 28 05:46:29 hostX kernel: Buffer I/O error on device sda3, logical block 129756810
Dec 28 05:46:29 hostX kernel: scsi1: ERROR on channel 0, id 5, lun 0, CDB: Read (10) 00 08 8b 8f 0f 0
0 00 80 00
Dec 28 05:46:29 hostX kernel: Info fld=0x88b8f17, Current sdb: sense key Medium Error
Dec 28 05:46:29 hostX kernel: Additional sense: Unrecovered read error
Dec 28 05:46:29 hostX kernel: end_request: I/O error, dev sdb, sector 143363863
Dec 28 05:46:29 hostX kernel: Buffer I/O error on device sdb3, logical block 129756808
Dec 28 05:46:29 hostX kernel: scsi1: ERROR on channel 0, id 5, lun 0, CDB: Read (10) 00 08 8b 8f 18 0
0 00 77 00
Dec 28 05:46:29 hostX kernel: Info fld=0x88b8f18, Current sdb: sense key Medium Error
Dec 28 05:46:29 hostX kernel: Additional sense: Data synchronization mark error
Dec 28 05:46:29 hostX kernel: end_request: I/O error, dev sdb, sector 143363864
Dec 28 05:46:29 hostX kernel: Buffer I/O error on device sdb3, logical block 129756809
Dec 28 05:46:29 hostX kernel: Adding 6289436k swap on /dev/sdb2.  Priority:-1 extents:1
Dec 28 05:46:29 hostX kernel: Adding 6289436k swap on /dev/sda2.  Priority:-2 extents:1
Dec 28 05:46:29 hostX kernel: SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_co
ntexts
Dec 28 05:46:29 hostX kernel: scsi1: ERROR on channel 0, id 5, lun 0, CDB: Read (10) 00 08 8b 8f 19 0
0 00 76 00
Dec 28 05:46:29 hostX kernel: Info fld=0x88b8f19, Current sdb: sense key Medium Error
Dec 28 05:46:29 hostX kernel: Additional sense: Data synchronization mark error
Dec 28 05:46:29 hostX kernel: end_request: I/O error, dev sdb, sector 143363865
Dec 28 05:46:29 hostX kernel: Buffer I/O error on device sdb3, logical block 129756810


--
:wq!
kevin.foote 

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 2 comments |
headers
Senthil_OR | 2 Jan 2007 16:54
Picon
Favicon

RE: IPMItool returns false value on PowerEdge 1950 [REASON FOUND]

Peter Kjellstrom wrote:
---
> 
> IMHO this is no longer anything that should be reported as a
> temperatur, too confusing that. Maybe it should be called a
> cpu-feeling-ok-index ;-) 
> 
> Btw, I'm curious, how does OMSA handle this new behaviour?

OMSA as observed on 9G machines, does not return the CPU temp values.
However, it returns the other values correctly.

--

-- 
Senthil

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Marc DeTrano | 2 Jan 2007 18:39

PowerEdge 750 and newer kernels

I am having trouble with a couple of PE 750 systems we support, running
Mandriva Linux (2006).  It seems that after upgrading to a kernel
version  2.6.12.x or higher, these systems are prone to kernel panic
once in a while (the busier system will usually die within a week).  
After much trial and error, I found a downgrade to a 2.6.11.x kernel
(smp) will eliminate these occurrences.   Not sure if this is observed
for Linux distros in general, or just something in Mandriva's kernel
packages.  We have tried updating the bios, but the same problem was
observed.  Just wondering if anyone has seen the same issue, and may
know of a way to fix it?

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 1 comment |
headers
Ray Van Dolson | 2 Jan 2007 18:53
Favicon

DHCP and KickStart issue; PowerEdge 2950

This issue seems to be mentioned in the following RHEL bugs:

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110036
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151872

Brief overview of problem:  I am running a KickStart CD via CD 1 (RHEL4).  My
installation sources are on an NFS server, so that is also passed as a boot
parameter.  It's a 100Mb network and the server is a 2950.

However, when Anaconda gets to the point where it attempts to acquire an IP
address via DHCP, generally pump times out and can't get an IP.  It's worked
one time -- after I walked away for an hour or so, came back, hit retry and it
magically got an IP, but I've never again been able to dupliate that success.

If I manually assign an IP it works fine.

Using ISC's dhcp client via rescue mode or once the OS installed works fine as
well.

Per the bug reports above the suggestion is to either dis or enable Spanning
Tree / Port Fast on the switch port.  I'll have to put in a request for this,
but in my mind if it works with ISC without any changes to the switch, it
should work with pump.

Again, this is with RHEL4 (latest updates) so I feel like the patches
mentioned in the bugs above should already be applied since they are more than
a year old.  Maybe not though.

Just wondering if anyone on this list has run into this issue before and if so
how you resolved it.

Hopefully I can get a sniffer on the segment and see what's going on with the
DHCP packets on the wire -- pump vs ISC and maybe that'll get me pointed in
the right direction.

TIA,
Ray

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Jerry Yu | 2 Jan 2007 19:14
Picon

Re: firmware version 1.98R is newer than 197O for PERC 3/DCL, per OMSA 5.1

thanks, Dmitriy. Steve from Dell sent me a private email informing me the same. 
In reply to Steve, I requested that the pages for PERC 3/DCL be updated to reflect the fact that newer versions of firmware do exist, assuming many (if not most) people would only follow links to the exact match of their particular model/make.

On 12/30/06, Dmitriy Beloslyudtsev <beloslyu1 <at> gmail.com> wrote:
Apparently the latest firmware version for PERC  3/QC, 3/DC, 3/DCL and 3/SC is 199A.

Check this: http://ftp.us.dell.com/scsi-raid/perc3-FWP3199A-A40.txt

And the link to floppy version of this update is: http://ftp.us.dell.com/scsi-raid/BR126654.exe



On 12/29/06, Jerry Yu <jjj863 <at> gmail.com> wrote:
Yesterday I had OMSA 5.1 installed on a dell PE6650 server running CentOS 4.1.  'omreport storage controller' reported the PERC3/DCL controller in a state of 'Degraded'. Nothing wrong with the single RAID 5 logical drive or its physical disks (all with state=ready and status=OK).  Viewing the system/status page via the "Managed Node Web Server",  it seems the only complaint is that the firmware version for the main RAID controller is too old. I upgraded it to the latest earlier in the year.  Searching the server's ervice tag on Dell's support site confirmed that version 197O (07/22/2004) is still the latest for PERC 3/DCL on a PE6650 as of a minute ago.
So, here come two questions: is 1.98R truly newer than 197O?  If so, where can I find it?


 Controller  PERC 3/DCL (Slot 5)

Controllers
ID                                : 0
Status                            : Non-Critical
Name                              : PERC 3/DCL
Slot ID                           : PCI Slot 5
State                             : Degraded
Firmware Version                  : 197O
Minimum Required Firmware Version : 1.98R


_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq


_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
William Warren | 2 Jan 2007 19:19

Re: PowerEdge 750 and newer kernels

have you tried Centos 4?  It's based off RHEL 4 and the 2.6.9 kernel 
with several features and fixes backported.

Marc DeTrano wrote:
> I am having trouble with a couple of PE 750 systems we support, running
> Mandriva Linux (2006).  It seems that after upgrading to a kernel
> version  2.6.12.x or higher, these systems are prone to kernel panic
> once in a while (the busier system will usually die within a week).  
> After much trial and error, I found a downgrade to a 2.6.11.x kernel
> (smp) will eliminate these occurrences.   Not sure if this is observed
> for Linux distros in general, or just something in Mandriva's kernel
> packages.  We have tried updating the bios, but the same problem was
> observed.  Just wondering if anyone has seen the same issue, and may
> know of a way to fix it?
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge <at> dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
> 
> 

-- 
My "Foundation" verse:
Isa 54:17  No weapon that is formed against thee shall prosper; and 
every tongue that shall rise against thee in judgment thou shalt 
condemn. This is the heritage of the servants of the LORD, and their 
righteousness is of me, saith the LORD.

-- carpe ductum -- "Grab the tape"
CDTT (Certified Duct Tape Technician)

Linux user #322099
Machines:
206822
256638
276825
http://counter.li.org/

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 0 comments |
headers
Keith | 2 Jan 2007 21:01

Re: BIOS / firmware update CD?

Except not all of dell's updates come in floppy form to be PXE'd.  Some
are .iso's only.  While I can yank out the image from the boot blocks of
the CD-Rom I hate the need to do this for each and every update, not to
mention that each one needs a reboot an human intervention.  Currently I
have to dowload and setup a boot for each of these updates on my 2950s:

Dell BMC Core - Dell

Dell BMC Firmware

Dell SAS Backplane Firmware

Dell Server BIOS
 Dell PERC 5/i Integrated

Dell SAS Hard Drive Firmware Utility

That means building 6 pxe images and then booting that on 32 servers
meaning 192 reboots.  Not to mention that most of the updates need human
intervention (the don't just boot and install).  

I want to be able to download the "update" .iso/pxe image which updates
all of the bios's/firmwares in my system.  Preferably there would be a
kickstart like file which could be used to configure the iso/pxe image
as to which firwmare you wanted upgraded.

On Thu, 2006-12-14 at 17:29 -0500, J. Epperson wrote:
> On Thu, December 14, 2006 14:42, David Sparks wrote:
> > Everyone seems to be missing the point.  Other vendors have a single
> > bootable CD that contains BIOS' and firmware for all their hardware.  On
> > a single CD!
> >
> The point I was speaking to was the issue of how to do firmware updates on
> a farm of fresh hardware without having to load OS or even media on each. 
> That issue was specifically raised in the thread.  A pxeboot of MEMDISK
> with the firmware floppy image as the initrd addresses it.
> 
> Your situation appears to be different.
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge <at> dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
> 

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
Permalink | Reply | 3 comments |

Gmane