Bug 168942 - Illegal Interrupt configuration (or code out of date)!
Summary: Illegal Interrupt configuration (or code out of date)!
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
: 168943 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-21 14:45 UTC by Jason
Modified: 2015-01-04 22:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-24 00:36:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jason 2005-09-21 14:45:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Description of problem:
Sep 21 09:24:27 cisit6 kernel: piix4_smbus 0000:00:0f.0: Found 0000:00:0f.0 device
Sep 21 09:24:28 cisit6 kernel: piix4_smbus 0000:00:0f.0: Unusual config register value
Sep 21 09:24:28 cisit6 kernel: piix4_smbus 0000:00:0f.0: Try using fix_hstcfg=1 if you experience problems
Sep 21 09:24:28 cisit6 kernel: piix4_smbus 0000:00:0f.0: Illegal Interrupt configuration (or code out of date)!

I have an HP LC2000 netserver with FC4 (fully patched) installed.  When I boot I get the above message.  I don't know if I was getting this in earlier kerenels.  I was checking the /var/log/messages for an error about a problem I was having and I saw the messages.  Everything seems to work fine.

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

How reproducible:
Always

Steps to Reproduce:
1. install fc4
2. boot 2.6.12-1.1447
3.
  

Additional info:

Comment 1 Jason 2005-09-21 14:48:50 UTC
*** Bug 168943 has been marked as a duplicate of this bug. ***

Comment 2 Dave Jones 2005-09-24 00:36:56 UTC
BIOS bug.
Do as it says (boot with fix_hstcfg=1)

From the code..

    /* Some BIOS will set up the chipset incorrectly and leave a register
       in an undefined state (causing I2C to act very strangely). */



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