Bug 107987
Summary: | up2date --hardware fails on Toshiba Tecra 8100 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Alexandre Oliva <aoliva> | ||||
Component: | up2date | Assignee: | Bret McMillan <bretm> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | jjh | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-10-19 19:33:41 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 120092 | ||||||
Attachments: |
|
Description
Alexandre Oliva
2003-10-25 17:57:03 UTC
Created attachment 102694 [details]
Output of DMI on Supermicro X5DPI board
I'm seeing the same problem with up2date on a dual processor Xeon box with a
Supermicro X5DPI mainboard.
up2date --hardware does this:
[root@wren root]# up2date --hardware
Updating hardware profile...
Reading DMI info failed
The dmidecode command itself works fine (output attached), though there is a
field listed as <OUT OF SPEC>, which doesn't look right.
[root@wren root]# uname -a
Linux wren 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386
GNU/Linux
[root@wren root]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon)
[root@wren root]# rpm -qa | grep up2date
up2date-4.2.33-1
up2date-gnome-4.2.33-1
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |