Bug 154630 - Kernel 2.6.11-1.14_FC3issues method_name_crs failure error msg
Kernel 2.6.11-1.14_FC3issues method_name_crs failure error msg
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
3
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-13 02:21 EDT by Mark Koljack
Modified: 2015-01-04 17:18 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-15 19:17:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark Koljack 2005-04-13 02:21:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
When I start the newly released kernel 2.6.11-1.14_FC3  i686 i686 i386 GNU/Linux , I receive a message in the first few lines, PNP: PnPACPI: METHOD_NAME_CRS FAILURE for PNP0C01 and the next line the same except the last part says PNP0C02.  The kernel then continues to boot fine.  Should I be concerned about this message.  How do I fix it or get rid of it?  Thank you.  Mark Koljack

Version-Release number of selected component (if applicable):
kernel 2.6.11-1.14_FC3  i686 i686 i386 GNU/Linux

How reproducible:
Always

Steps to Reproduce:
1. Start the PC, message appears every time.
2.
3.
  

Actual Results:  Error message prints and the kernel continues to boot normally

Expected Results:  No error message should be printed

Additional info:
Comment 1 Jonathan Earl Brassow 2005-04-13 02:34:39 EDT
Do you mean 'kernel' instead of GFS-kernel?
Comment 2 Mark Koljack 2005-04-13 02:51:08 EDT
Yes I mean kernel and not GFS-kernel, sorry. 
Comment 3 Mark Koljack 2005-04-20 00:35:13 EDT
Is there any news on this?  Or should I sit tight and be patient?
Comment 4 Davide Bolcioni 2005-05-25 06:10:31 EDT
Something very similar happens to me with kernel 2.6.11-1.27_FC3:

pnp: PnPACPI: METHOD_NAME_CRS FAILURE for PNP0c01

followed by the selinux audit message. This is the output of lspci:

00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface
(rev 02)
00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller
#1 (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller
#2 (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller
#4 (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller
(rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge
(rev 02)
00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97
Audio Controller (rev 02)
01:00.0 VGA compatible controller: STMicroelectronics STG4000 [3D Prophet Kyro
Series] (rev 0f)
02:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 01)
Comment 5 Dave Jones 2005-07-15 15:45:46 EDT
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.
Comment 6 Mark Koljack 2005-07-15 18:45:10 EDT
I have upgraded to Fedora Core 4 and all is fine. 

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