[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
Stefan Dösinger wrote:

>If I re-programm the IRQ to something else than IRQ10, the device doesn't
>resume too. So it's not only a problem of IRQ 11.
Seems like an anything-at-all-other-than-IRQ-10 problem. If the current
thinking is right, your BIOS is assigning IRQ10 during boot, so moving
it anywhere else is what causes problems.

But the current thinking doesn't quite seem right, because it seeems
like we're seeing these problems after the irqrouter is resumed. Can you
verify that with the attached patch? The patch should give us enough
information as long as you've got the proper kernel loglevel set.

Now, I wonder if the only reason it works when you set IRQ 10 is that
some other driver is unconditionally claiming the interrupt...


>The ipw2100 driver calls pci_disable_device in it's suspend handler. But I
>think the ipw2100 maintainers need help with suspend/resume because James
>Ketrenos can't test it on his own system.
pci_disable_device() only turns off bus-mastering, it doesn't unmap the
I/O or disable the slot. Maybe we also need to set power state D3 and do
a device-specific disable-interrupts, but I think D0 gets restored for
us pretty early during resume anyway...

Anyway, something doesn't quite add up...

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.032 / U:0.892 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site