The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Matthew Johnson <matt@matthew.ath.cx>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: IRQ Mis-matches in 2.6.17.7
Date: Fri, 11 Aug 2006 11:44:36 -0400	[thread overview]
Message-ID: <200608111144.36751.len.brown@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0608110945510.15208@illythia.matthew.ath.cx>

On Friday 11 August 2006 04:53, Matthew Johnson wrote:

ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 4
PCI: setting IRQ 4 as level-triggered
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 4 (level, low) -> IRQ 4
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0f.0: 3Com PCI 3c905B Cyclone 100baseTx at e0802000.

setup_irq: irq handler mismatch
 <c0135b3e> setup_irq+0x10d/0x11a  <e2024b74> irq_handler+0x0/0x4e0 [lirc_serial]
 <c0135bba> request_irq+0x6f/0x8b  <e202410a> set_use_inc+0xab/0x1b9 [lirc_serial]
 <e201f467> irctl_open+0x155/0x1e8 [lirc_dev]  <c015678b> chrdev_open+0x15e/0x17a
 <c015662d> chrdev_open+0x0/0x17a  <c014e9d7> __dentry_open+0xe0/0x1cf
 <c014eb2a> nameidata_to_filp+0x19/0x28  <c014eb64> do_filp_open+0x2b/0x31
 <c014ec4a> do_sys_open+0x3c/0xae  <c014ece9> sys_open+0x16/0x18
 <c0102a5f> syscall_call+0x7/0xb 
lirc_serial: IRQ 4 busy

----------
Matthew,
I think this is an ACPI IRQ routing bug where PCI and legacy clash.

While I don't expect it to make a difference, please reproduce without the NVIDIA binary module.

I expect you will be able to work around this issue by booting with
"acpi_irq_isa=4"

Then try with "acpi=off" or "acpi=noirq"

If it works, then by definition this is an ACPI bug.
Collect the dmesg -s64000 and /proc/interrupts for the the success and failure case,
the .config, the output from adpidump (available in pmtools here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
and attach them to a bugzilla here:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
and mention if this worked before, or if this configuration has always failed.

thanks,
-Len


  reply	other threads:[~2006-08-11 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11  8:53 IRQ Mis-matches in 2.6.17.7 Matthew Johnson
2006-08-11 15:44 ` Len Brown [this message]
2006-08-11 16:05   ` Bjorn Helgaas
2006-08-18  8:58     ` Matthew Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608111144.36751.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@matthew.ath.cx \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox