Bug 201095 - reserve= no longer being respected.
Summary: reserve= no longer being respected.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-02 19:30 UTC by Chris Ball
Modified: 2008-08-02 23:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-05-15 03:09:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Ball 2006-08-02 19:30:07 UTC
Description of problem:

I have an orinoco_cs wavelan PC Card that requires reserve=0xff490000,0x00aff000
to be added to the kernel parameters to boot without a hang.  As of about a
month ago, an update of Rawhide made the hang happen even when reserve= is
added.  The hang happens pre-init, so I suspect that the kernel is ignoring the
reserve=, or that the PCMCIA code is no longer following through with the
request.  The log below shows that the quoted range is not being reserved.

I don't yet know whether this is Fedora-specific or also upstream.

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

kernel-2.6.17-1.2449.fc6

How reproducible:

Every time, on boot.  The output just before the hang is:

    pccard: PCMCIA card inserted into slot 0
    cs: memory probe 0xff400000-0xffcfffff: excluding 0xff400000-0xff48ffff

Comment 1 Chris Ball 2006-08-02 23:59:25 UTC
This happens with current linux-2.6.git too, so it's not Fedora-specific.

Comment 2 Jeff Moyer 2008-02-19 20:17:40 UTC
Sorry this bug hasn't seen any attention.  Are you still having problems with
recent kernels?

Comment 3 Bug Zapper 2008-05-14 02:16:10 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Jon Stanley 2008-05-15 03:09:39 UTC
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming 
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.



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