From: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: "irq 11: nobody cared" after S3
Date: Sun, 1 Aug 2004 18:50:25 +0200 [thread overview]
Message-ID: <200408011850.25991.stefandoesinger@gmx.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Hello,
I have a really odd problem with acpi interrupts and ipw2100.
I use 2.6.8-rc2 + acpi-20040715 and the system works fine after S3 as long no
driver uses IRQ11. But if I have ipw2100 loaded before I suspend or load it
afterwards, irq11 and irq10 are disabled.
The odd thing is that it worked for 2 days with the (hopefully) same
configuration. Then I tried to make a clear patch which calls
acpi_leave_sleep_state before resuming the devices which is needed on my
notebook(see pci device resume too early?). I recombiled the kernel and my
nice setup stopped working. Returning to the original code didn't help.
The problem occurs when ipw2100(or ndiswrapper) is loaded before I suspend(see
dmesg.loadbefore) or if I load it after resume(see dmesg.loadlater. In both
cases IRQ11 and IRQ10 are disabled. IRQ10 works nicely as long IRQ11 is not
used. The IRQ crash occues eighter when PIT is resumed or when ipw2100
registers the irq line.
This is my /proc/interrupts with a normally booted system(no S3):
CPU0
0: 1508252 XT-PIC timer
1: 2953 XT-PIC i8042
2: 0 XT-PIC cascade
5: 19552 XT-PIC uhci_hcd, eth0
8: 2 XT-PIC rtc
9: 168 XT-PIC acpi
10: 94435 XT-PIC ehci_hcd, uhci_hcd, uhci_hcd,
radeon@PCI:1:0:0, Intel ICH4
11: 1166 XT-PIC wlan0
12: 5382 XT-PIC i8042
14: 14433 XT-PIC ide0
NMI: 0
LOC: 1508373
ERR: 0
MIS: 0
After this crash, 11 hase a count of exactly 100000.
I tried with and without APIC, IOAPIC, hpet, power management timer.
If I reverse the patch from http://bugme.osdl.org/show_bug.cgi?id=2643, the
messages disappear, but the interrupts still do not work.
Any ideas?
Best regards,
Stefan
[-- Attachment #2: dmesg.loadbefore.bz2 --]
[-- Type: application/x-bzip2, Size: 4670 bytes --]
[-- Attachment #3: dmesg.loadlater.bz2 --]
[-- Type: application/x-bzip2, Size: 4635 bytes --]
[-- Attachment #4: acpidump.out.bz2 --]
[-- Type: application/x-bzip2, Size: 12275 bytes --]
[-- Attachment #5: config.bz2 --]
[-- Type: application/x-bzip2, Size: 8267 bytes --]
next reply other threads:[~2004-08-01 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 16:50 Stefan Dösinger [this message]
[not found] ` <200408011850.25991.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-02 4:21 ` "irq 11: nobody cared" after S3 Nathan Bryant
[not found] ` <410DC163.1090109-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-03 14:29 ` Stefan Dösinger
[not found] ` <200408031629.19466.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-03 15:32 ` Nathan Bryant
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 6:47 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F0376876A-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-02 14:17 ` Nathan Bryant
2004-08-03 1:12 Li, Shaohua
[not found] ` <B44D37711ED29844BEA67908EAF36F03768BD0-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-03 1:27 ` Nathan Bryant
2004-08-03 2:21 ` Nathan Bryant
2004-08-03 1:43 Li, Shaohua
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=200408011850.25991.stefandoesinger@gmx.at \
--to=stefandoesinger-rbzlaithdce@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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