DMIStringIndexOutOfRange on HP Proliant ML110 G5

Bug #1025663 reported by Brendan Donegan on 2012-07-17
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Firmware Testing Team

Bug Description

We encountered this error when running certification tests in a HP Proliant ML110 G5:
FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x09 while accessing entry
'Base Board Information (Type 2)' @ 0x000dc082, field 'Asset Tag', offset 0x08

ADVICE: It may be worth checking against section 7.3 of the System Management BIOS (SMBIOS)
Reference Specification (see http://www.dmtf.org/standards/smbios).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-4-generic 3.5.0-4.4
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Jul 17 08:52 seq
 crw-rw---T 1 root audio 116, 33 Jul 17 08:52 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Jul 17 09:25:00 2012
HibernationDevice: RESUME=UUID=c1530c5c-1763-45eb-b575-4504e0de61f6
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Alpha amd64 (20120717)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HP ProLiant ML110 G5
PciMultimedia:

ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US
 LANGUAGE=en_US:
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic root=UUID=90f6a1e1-da49-4ec1-bef7-139784b5a88a ro rootdelay=60 quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-4-generic N/A
 linux-backports-modules-3.5.0-4-generic N/A
 linux-firmware 1.84
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2007
dmi.bios.vendor: HP
dmi.bios.version: O15
dmi.board.name: A61TT2
dmi.board.vendor: Wistron Corporation
dmi.board.version: NA
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 17
dmi.chassis.vendor: HP
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHP:bvrO15:bd10/08/2007:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnA61TT2:rvrNA:cvnHP:ct17:cvrN/A:
dmi.product.name: ProLiant ML110 G5
dmi.product.version: NA
dmi.sys.vendor: HP

Brad Figg (brad-figg) on 2012-07-17
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
assignee: nobody → Colin King (colin-king)
importance: Undecided → Medium
status: Confirmed → In Progress
Colin Ian King (colin-king) wrote :

We encountered this error when running certification tests in a HP Proliant ML110 G5:
FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x09 while accessing entry
'Base Board Information (Type 2)' @ 0x000dc082, field 'Asset Tag', offset 0x08

So, basically this means that the Asset Tag string is the 9th string entry in this DMI data struct, but there aren't that many strings stored, and we've fallen off the end of the DMI entry. This is a firmware bug which means we can't fetch the Asset Tag string because of the bad index value. This won't cause problems because software normally figures out this is a bad entry. It requires a firmware fix to stop this error.

This server is actually quite old (2008) and may have an older BIOS version. I will see if a lab engineer can update the BIOS to make the issue go away.

Colin Ian King (colin-king) wrote :

A newer 2010.10.25 BIOS is available:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3577708&swItem=MTX-8a03a95409d541848a5622a22d&prodNameId=3577715&swEnvOID=4006&swLang=8&taskId=135&mode=4&idx=2

However, the bug isn't exactly a kitten killer, so one should consider the risk/benefit before re-flashing the BIOS.

Colin Ian King (colin-king) wrote :

I've updated the dmi decode test with some improved advice information to help explain these kind of errors, http://kernel.ubuntu.com/git?p=hwe/fwts.git;a=commit;h=fe3ba4850c78281bf5f720b5d361e6506f69f17b

Colin Ian King (colin-king) wrote :

@Brendan, and update on the new BIOS on this machine?

Colin Ian King (colin-king) wrote :

I meant to write: "any update on the new BIOS on this machine?"

Changed in linux (Ubuntu):
status: In Progress → Incomplete

I've created a support ticket (just now, sorry it had slipped my mind) and will let you know if it gets any response.

Colin Ian King (colin-king) wrote :

@Brendan, any update on this issue?

No update unfortunately. I guess I will have to poke IS

Colin Ian King (colin-king) wrote :

Please do.

Colin Ian King (colin-king) wrote :

@Brendan, any update on this one, or will it be stuck on my bug list forever? ;-)

The current status of this is that I believe the bios was updated, however I've never got a chance to retry the test - this system fell victim to the shambles that was the London datacenter move and we are still waiting to get access to it again. If you want to let this bug go to Expired, I don't mind - it's concievable, though higly unlikely, that I may get access to the system before it does

Changed in linux (Ubuntu):
assignee: Colin King (colin-king) → Firmware Testing Team (firmware-testing-team)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers