Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: irq 169: nobody cared! (screaming interrupt?) https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145530 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-18 03:03 EST ------- comment #1 - comment #4 are an acpi_irq failure in IRQ 169. > ASUS P2L97-DS Intel 440LX > [<c01c9b13>] (acpi_irq+0x0/0x14) > Disabling IRQ #169 It is unusual for ACPI to bind to an IRQ above 16. Is it possible to attach the output from dmesg -s64000 and acpidump found in pmtools here: http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/ As this is the acpi_irq, you should be able to try the workaround in comment #8. If a combination works, then we're actually on the correct IRQ and the trigger/polarity are incorrect, but if none of the 4 combinations work, then acpi_irq is bound to the wrong IRQ. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
