From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-acpi@vger.kernel.org, x86@kernel.org,
Dmitry Torokhov <dtor@mail.ru>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, polhallen@fuckaround.org
Subject: Re: [Bugme-new] [Bug 17802] New: touchpad become crazy: disable irq 21
Date: Fri, 26 Nov 2010 15:15:30 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1011261510090.3588@x980> (raw)
In-Reply-To: <20100908153201.91dc03d2.akpm@linux-foundation.org>
CPU0 CPU1
0: 287671 109637 IO-APIC-edge timer
8: 0 1 IO-APIC-edge rtc0
9: 483 479 IO-APIC-fasteoi acpi
16: 36491 15935 IO-APIC-fasteoi uhci_hcd:usb4,
uhci_hcd:usb5, ndiswrapper
18: 23811 10147 IO-APIC-fasteoi uhci_hcd:usb6, ata_piix
19: 1 3 IO-APIC-fasteoi ohci1394
20: 869 298 IO-APIC-fasteoi ehci_hcd:usb2,
uhci_hcd:usb3, HDA Intel
21: 97807 68959 IO-APIC-fasteoi ide0, ide1, ehci_hcd:usb1,
uhci_hcd:usb7
27: 1 0 PCI-MSI-edge eth0
28: 18118 22763 PCI-MSI-edge i915@pci:0000:00:02.0
The DSDT shows that there are no programmable IRQs
in IOAPIC mode on this machine, so it is unlikely that
there is an ACPI interrupt routing issue.
It is more likely that the problem is in one of the devices (above)
using IRQ21. I assume that the touchpad is uhci_hcd:usb7?
What does "lsusb" show on this machine?
Of course I'd recommend trying to reproduce the issue
after excluding "ndiswrapper" from the configuration.
cheers,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-11-26 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17802-10286@https.bugzilla.kernel.org/>
2010-09-08 22:32 ` [Bugme-new] [Bug 17802] New: touchpad become crazy: disable irq 21 Andrew Morton
2010-09-08 22:58 ` Dmitry Torokhov
2010-09-09 0:16 ` Zhang Rui
2010-11-26 20:15 ` Len Brown [this message]
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=alpine.LFD.2.00.1011261510090.3588@x980 \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dtor@mail.ru \
--cc=linux-acpi@vger.kernel.org \
--cc=polhallen@fuckaround.org \
--cc=x86@kernel.org \
/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