Bug 80702 - ACPI + PCMIA = Boot Failure for Dell Inspiron 2500
ACPI + PCMIA = Boot Failure for Dell Inspiron 2500
Status: CLOSED DUPLICATE of bug 82123
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2002-12-29 23:20 EST by Ron H.
Modified: 2013-07-02 22:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Log file excerpt showing error (2.30 KB, text/text)
2002-12-29 23:21 EST, Ron H.
no flags Details

  None (edit)
Description Ron H. 2002-12-29 23:20:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

Description of problem:
My Dell Inspiron will not boot.  It hangs at starting PCMCIA services, and
halts.  I must power off with a hard reset using the power button.  If I choose
interactive mode, and choose not to load PCMCIA, then the machine will boot.  If
I pass the kernel the boot paramater acpi=off, then the machine will also boot,
however, APM will log numerous errors, which I have included since they may give
a better idea of what is going wrong.

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

How reproducible:

Steps to Reproduce:
1. Install Phoebe on Dell Inspiron 2500
2. Boot the machine.
3. Machine will hang at starting PCMCIA
4. Machine fails to boot and requires a hard power off.
Comment 1 Ron H. 2002-12-29 23:21:34 EST
Created attachment 88981 [details]
Log file excerpt showing error
Comment 2 Jeff Garzik 2003-01-17 16:19:24 EST

*** This bug has been marked as a duplicate of 82123 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:50:46 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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