Bug 759658 - "Can't allocate mem resource" on pci bus rescan
Summary: "Can't allocate mem resource" on pci bus rescan
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-02 23:24 UTC by Vitaly
Modified: 2014-05-21 13:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-21 13:10:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
RHEL-6, dmesg after unsuccessfull rescan (49.74 KB, application/octet-stream)
2011-12-02 23:24 UTC, Vitaly
no flags Details

Description Vitaly 2011-12-02 23:24:46 UTC
Created attachment 539821 [details]
RHEL-6, dmesg after unsuccessfull rescan

Description of problem:

On HP Proliant DL380 G7 system can't allocate pci mem resources for newly appeared PCI-e device. Vice versa, if device was set by bios, and later device was removed from system then bus rescan does not fully remove it: it is visible in output of lspci.

This has been seen only on HP Proliant and RHEL-6. HP Proliant and RHEL-5 works fine. Non-HP machine and RHEL-6 works fine too.

Version-Release number of selected component (if applicable):

kernel 2.6.32-131.21.1.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Boot system
2. Plug PCI-e device
3. echo 1 > /sys/bus/pci/rescan

Actual results:

Kernel can't allocate memory resources for PCI bars:

pci 0000:0e:00.0: BAR 1: can't allocate mem resource [0x000000-0x1ffffff]
pci 0000:0e:00.0: BAR 0: can't allocate mem resource [0x000000-0x007fff]

Expected results:

BAR resources assigned.

Comment 3 RHEL Program Management 2012-05-03 05:17:03 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Prarit Bhargava 2014-05-21 13:10:52 UTC
Please reopen if still an issue.

P.


Note You need to log in before you can comment on or make changes to this bug.