[lkml]   [2004]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: [ACPI] [PATCH][RFC] fix ACPI IRQ routing after S3 suspend

>-----Original Message-----
>[] On Behalf Of
>Stefan Dösinger
>Sent: Friday, August 20, 2004 9:36 AM
>To: Nathan Bryant
>Cc:; Brown, Len; Linux Kernel
>list; Li, Shaohua
>Subject: Re: [ACPI] [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
>Am Freitag, 20. August 2004 14:18 schrieb Nathan Bryant:
>> Stefan -
>> Also - did suspend/resume for the ipw2100 ever work under any kernel
>> version?
>Yes, it works with acpi=noirq at least up to 2.6.7(not tested
>with later
>versions, but I'm sure it does)
>It works with 2.6.8-rc2 and 2.6.8-rc4 and with acpi IRQs and a
>modified dsdt which forces LNKE to IRQ 10. I attached a dmesg
>output of a
>successful resume.

This seems to be the same resume order issue, that Shaohua is hitting.

On my system the resume order looks like this:
Resuming System Devices
Resuming type 'cpu':
aux driver resume 0xc010e410 (mtrr_restore)
aux driver resume 0xc03365f0 (cpufreq_resume)
Resuming type 'i8259':
Resuming type 'timer':
Resuming type 'pit':
Resuming type 'lapic':
Resuming type 'irqrouter':
Resuming type 'i8042':

The current theory I have for this issue is we resume pci_link driver
A bit too late, which is causing this problem.

Say a particular device doesn't do anything for suspend and resume.
So, as soon as we resume this particular device can start
generating interrupts. Once we have PIC enabled, it starts sending
interrupts and no one handles that original IRQ. As pci_link that
resumes later is reprogramming the device to different IRQ, where the
driver is handling the device.

That's probably the reason why it works with acpi=noirq or
modified DSDT. Does it make sense?

I think we have to resume pci_link device before PIC.
We should be able to achieve this my changing the makefile orders.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:05    [W:0.047 / U:2.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site