Red Hat Bugzilla – Bug 125592
fedora crash on startup of /etc/init.d/pcmcia start
Last modified: 2007-11-30 17:10:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
I installed FC-2 x86_64 on my Laptop ( AMD Mobile Athlon64 (2800+
MHz, 1 MByte L2-Cache), VIA K8T800, CB1410 Cardbus Controller
(yenta_socket). After the reboot, fedora hang on startup
of /etc/init.d/pcmcia start. After this, i boot in single user mode
and remove the pcmcia startup and switch into runlevel 3 (later in
runlevel 5). Now fedora starts. If i start pcmcia manually, the same.
Fedora crash and i can't nothing do except power off. There is no
message in /var/log/messages or dmesg.
Then i installed the minimal fedora system, the same.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: fedora crash
Expected Results: Start of pcmcia, load the modules, cardmgr and so
After i add the kernelparameter acpi=off, the sound works fine. In
the /var/log/messages i found an entry
ACPI-0179: *** Warning: The ACPI AML in your computer contains
errors, please nag the manufacturer to correct it.
ACPI-0182: *** Warning: Allowing relaxed access to fields; turn on
CONFIG_ACPI_DEBUG for details.
Can be this the problem?
What i mean ist, the pcmcia start fine, with acpi=off.
i guess this is the same machine as in bug 125594
Please aditionally add the output from lspci -vv
with and without acpi=off.
Created attachment 101021 [details]
Output from lspci -vv with acpi=off as bootparameter
Created attachment 101022 [details]
output from lspci -vv with acpi=on as bootparameter
Hi Len Brown,
you are right, it's the same machine as in bug #125594.
And i think also the same problem, so i will close the bug #125594
and reference to this one.
Further i wanna to search the bugzilla after the acpi problem. Maybe
this is a known problem.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Closed per above message and lack of response. Note that FC2 is not even
supported by Fedora Legacy currently.