Bug 81310
Summary: | The command "lsdev" doesn't seem to work | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Peter van Egdom <p.van.egdom> |
Component: | procinfo | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED DUPLICATE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | andy.piper, srevivo |
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: | 2006-02-21 18:50:59 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: | 79579 |
Description
Peter van Egdom
2003-01-07 22:57:00 UTC
This also occurs on RH8.0, procinfo-18-5. Same error. [mharris@devel RPMS]$ lsdev -h Device DMA IRQ I/O Ports ------------------------------------------------ ATI 2000-20ff cascade 4 2 cciss 3000-30ff cciss0 10 Compaq 1800-18ff 3000-30ff D-Link 2400-247f 4800-487f 4880-48ff dma 0080-008f dma1 0000-001f dma2 00c0-00df eepro100 4c00-4c3f eth3 5 fpu 00f0-00ff ide0 14 01f0-01f7 03f6-03f6 2480-2487 ide1 2488-248f Intel 4c00-4c3f keyboard 1 0060-006f LSI 4000-40ff 4400-44ff Mouse 12 PCI 0cf8-0cff pic1 0020-003f pic2 00a0-00bf rtc 8 0070-007f serial 02f8-02ff 03f8-03ff ServerWorks 2480-248f sundance 2400-247f 4800-487f 4880-48ff sym53c8xx 11 15 4000-40ff 4400-44ff timer 0 0040-005f vga+ 03c0-03df I can't reproduce this on 6 systems locally, so it is probably a hardware specific bug I presume. This package is on our low priority package list, which means it's unlikely to get further investigation due to inability to reproduce. Try reporting it to the official procinfo reporter upstream, and if he/she fixes the issue, or if someone else has a patch, update this report with such info/patch and reopen, and I'll add it to a future build. Without being able to reproduce though, there's not much that I can do. This problem has been reported by someone else as well, and a bit further digging seems to show that it was actually a bug in the perl interpreter. If you upgrade perl to the latest release available via updates the problem should theoretically go away. *** This bug has been marked as a duplicate of 82432 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |