Bug 3282

Summary: (sata sis) irq xx: nobody cared! after loading modules libata, sata_sis
Product: IO/Storage Reporter: echo
Component: Serial ATAAssignee: Jeff Garzik (jgarzik)
Status: CLOSED PATCH_ALREADY_AVAILABLE    
Severity: high CC: bunk
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.8.1 Subsystem:
Regression: --- Bisected commit-id:
Attachments: Full boot listing captured by redirecting console to serial port
/proc/interrupts from hardware running under 2.6.7 kernel
Output from scripts/ver_linux from system running under 2.6.7 kernel

Description echo 2004-08-26 19:13:28 UTC
Distribution        : SuSE 9.1 professional

Hardware Environment: ASUS P4S800D-E Deluxe MB, Intel P4, 1GB RAM
                      SIS 655TX & SIS 964 chipsets
                      SiS 180 SATA controller

Software Environment: Kernel compiled from kernel.org source using default SuSE
kernel configs through "make oldconfig".  Defaults were chosen for newer kernel
options.

Problem Description : Root disk is SATA.  Attempts to boot fail as IRQ
supporting libata is disabled following "irq 17: nobody cared!" msg.

Steps to reproduce  : Happens on every boot with 2.6.8.1 kernel on this hardware.
Comment 1 echo 2004-08-26 19:14:56 UTC
Created attachment 3573 [details]
Full boot listing captured by redirecting console to serial port
Comment 2 echo 2004-08-26 19:16:29 UTC
Created attachment 3574 [details]
/proc/interrupts from hardware running under 2.6.7  kernel
Comment 3 echo 2004-08-26 19:17:24 UTC
Created attachment 3575 [details]
Output from scripts/ver_linux from system running under 2.6.7 kernel
Comment 4 echo 2004-08-26 19:22:02 UTC
Also tried booting with variations of: pci=noacpi, acpi=off, noapic
This results in problem being reported with IRQ 10 instead of IRQ 17
Comment 5 echo 2004-10-08 10:36:14 UTC
Problem appears to be resolved after patching up to snapshot 2.6.9-rc3-bk8.
Comment 6 echo 2005-06-09 17:52:52 UTC
I just wanted to point out that I have NOT had this problem since 2.6.9-rc3-bk8.
 Currently running SuSE 9.3 / Kernel 2.6.11.4 on this hardware without issue.
Comment 7 Adrian Bunk 2005-08-12 03:27:12 UTC
According to the bug logs, it seems this issue is already fixed in recent kernels.