Bug 205477

Summary: kernel error: IRQ handler type mismatch for IRQ 0 during sata initialization
Product: [Fedora] Fedora Reporter: Christian Nolte <ch.nolte>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-12 00:25:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christian Nolte 2006-09-06 17:00:10 UTC
Description of problem:
During bootup initialization of the sata-devices the kernel gives the following
message: "IRQ handler type mismatch for IRQ 0". Bluetooth-Devices are unusable
(the bootup hangs when the bluetooth service is enabled on startup), no sound
through alsa is available. Furthermore the kernel gives the following
BUG-message: "BUG: warning at kernel/lockdep.c:1816/trace_hardirqs_on() (Not
tainted)".

The full dmesg output and lspci -vvv is attached.

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

I have tried the following kernels with the exact same result:
kernel-2.6.17-1.2611.fc6
kernel-2.6.17-1.2617.2.1.fc6

How reproducible:
On every system startup.

Steps to Reproduce:
1. Install the mentioned kernel versions on a FC5-system with all the
   latest updates
2. Reboot the system
  
Actual results:
IRQ assigning problems

Expected results:
It should just work

Additional info:
The mentioned kernel-versions are used on a FC5 system because these are the
only ones working on my system (see bug #207059).

Comment 1 Dave Jones 2006-09-12 00:24:32 UTC
*** Bug 205478 has been marked as a duplicate of this bug. ***

Comment 2 Dave Jones 2006-09-12 00:25:30 UTC

*** This bug has been marked as a duplicate of 205479 ***