No ACPI interrupts after resume from S1
Hi,
Suspending and resuming from S1 disables ACPI interrupts for my machine (ASUS L3800C laptop). No further interrupts and events are generated, /proc/interrupts shows no change w.r. to ACPI. This happens regardless of whether the specific IRQ is shared or not.
Versions affected: 2.6.0-test[5-8], 2.6.0-test5-mm4, 2.6.0-test6-mm4. Versions unaffected: 2.6.0-test3, 2.4.22 with 20030918 ACPI.
Note: it seems that running a pmdisk cycle after resume from S1 reenables the interrupts somehow (though treat it as a not-thoroughly-tested observation for now).
http://bugme.osdl.org/show_bug.cgi?id=1185 may contain information relevant to the matter (DSDT, dmesg, etc.).
I'll be happy to provide any further info.
Best regards,
Signature · 2 lines
Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/[email protected]
Quoted 4 lines · Karol Kozimor
Suspending and resuming from S1 disables ACPI interrupts for my machine (ASUS L3800C laptop). No further interrupts and events are generated,
/proc/interruptsshows no change w.r. to ACPI. This happens regardless of whether the specific IRQ is shared or not.
I've got an Asus M2400E laptop, and have seen similar things. After a suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Signature · 2 lines
Måns Rullgård [email protected]
Thus wrote M?ns Rullg?rd:
Quoted 9 lines
Quoted 4 lines
Suspending and resuming from S1 disables ACPI interrupts for my machine (ASUS L3800C laptop). No further interrupts and events are generated,
/proc/interruptsshows no change w.r. to ACPI. This happens regardless of whether the specific IRQ is shared or not.suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
Best regards,
Signature · 2 lines
Karol 'sziwan' Kozimor [email protected]
Quoted 9 lines · Karol Kozimor
Quoted 5 lines
suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
standby, at least.
After echo -n mem > /sys/power/state, the display light won't turn on, so I don't know what's going on. I've never managed to resume from a suspend to disk. It just boots normally and makes a fuss about the filesystems.
Signature · 2 lines
Måns Rullgård [email protected]
Hi!
Quoted 8 lines
Quoted 4 lines
working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
Find out which versions break it, pay special atetion to hwsleep.c.
Signature · 10 lines
Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need... ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/
Hi!
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
Quoted 6 lines
standby, at least.
After echo -n mem >
/sys/power/state, the display light won't turn on, so I don't know what's going on. I've never managed to resume from a suspend to disk. It just boots normally and makes a fuss about the filesystems.
Are you passing resume= option?
Signature · 2 lines
Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
Quoted 10 lines · Pavel Machek
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
Quoted 8 lines
Quoted 6 lines
standby, at least.
After echo -n mem >
/sys/power/state, the display light won't turn on, so I don't know what's going on. I've never managed to resume from a suspend to disk. It just boots normally and makes a fuss about the filesystems.Are you passing resume= option?
I've been trying the new suspend to disk implementation (pmdisk, I think) lately. I get these lines in the kernel log when starting after a suspend:
PM: Reading pmdisk image.
PM: Resume from disk failed.
ACPI: (supports S0 S1 S3 S4 S5)
Last time I tried swsusp, I did pass the resume= option, but it didn't work.
Could it be that some disk cache is never flushed properly? Occasionally, some random filesystem is reported as not being cleanly unmounted when booting normally, which seems to point in the same direction.
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 31 lines · Måns Rullgård
Quoted 10 lines · Pavel Machek
Quoted 10 lines
Quoted 10 lines
Quoted 6 lines
suspend, the extra buttons (I use them to fire up programs) stop working. Normally, they will generate an ACPI event, that is processed by acpid etc. After a suspend, each button will work once. If I then close and open the lid, they will work one more time, and so on. Any way I can help?
Please specify the type of suspend. The situation I described only occurs for S1 (or, echo -n standby, more specifically), and only in certain kernel versions.
Quoted 9 lines
Quoted 7 lines
standby, at least.
After echo -n mem >
/sys/power/state, the display light won't turn on, so I don't know what's going on. I've never managed to resume from a suspend to disk. It just boots normally and makes a fuss about the filesystems.Are you passing resume= option?
I've been trying the new suspend to disk implementation (pmdisk, I think) lately. I get these lines in the kernel log when starting after a suspend:
PM: Reading pmdisk image.
PM: Resume from disk failed.
ACPI: (supports S0 S1 S3 S4 S5)
Quoted 8 lines
Last time I tried swsusp, I did pass the resume= option, but it didn't work.
Could it be that some disk cache is never flushed properly? Occasionally, some random filesystem is reported as not being cleanly unmounted when booting normally, which seems to point in the same direction.
Try turning your disk cache off, or set it to write through caching (even so I heard some IDE drives don't turn it off anyway!). See if it helps.
Quoted 17 lines · Nick Piggin
Quoted 8 lines
I've been trying the new suspend to disk implementation (pmdisk, I think) lately. I get these lines in the kernel log when starting after a suspend:
PM: Reading pmdisk image.
PM: Resume from disk failed.
ACPI: (supports S0 S1 S3 S4 S5)Quoted 8 lines
Last time I tried swsusp, I did pass the resume= option, but it didn't work.
Could it be that some disk cache is never flushed properly? Occasionally, some random filesystem is reported as not being cleanly unmounted when booting normally, which seems to point in the same direction.
Quoted 3 lines
Try turning your disk cache off, or set it to write through caching (even so I heard some IDE drives don't turn it off anyway!). See if it helps.
That took me one step further. Now it loaded the image swap, but them immediately rebooted. I didn't have time to see if there were any error messages. I don't have a serial port, so I can't put a console there. This was with lots of modules loaded, so maybe unloading some would help. Are there any known broken drivers in this list:
Module Size Used by ide_cd 36612 0 cdrom 32160 1 ide_cd evdev 7808 1 ipv6 226496 12 iptable_filter 2304 1 ip_tables 15616 1 iptable_filter sis_agp 4224 1 agpgart 25896 1 sis_agp ohci_hcd 16128 0 usbcore 94940 3 ohci_hcd snd_intel8x0 28164 0 snd_ac97_codec 50948 1 snd_intel8x0 snd_pcm 84004 1 snd_intel8x0 snd_timer 20996 1 snd_pcm snd_page_alloc 9092 2 snd_intel8x0,snd_pcm snd_mpu401_uart 6144 1 snd_intel8x0 snd_rawmidi 19616 1 snd_mpu401_uart snd 43364 6 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi soundcore 7104 1 snd ohci1394 31112 0 ieee1394 68396 1 ohci1394 sis900 16516 0 crc32 4096 1 sis900 ds 10884 4 yenta_socket 14336 0 pcmcia_core 60768 2 ds,yenta_socket rtc 10552 0
In case it matters, sisfb is compiled into the kernel.
Signature · 2 lines
Måns Rullgård [email protected]
Thus wrote Pavel Machek:
Quoted 2 lines
Find out which versions break it, pay special atetion to
hwsleep.c.
I stated in my original mail that the last working version was 2.6.0-test3. test4 is broken w.r. to S1, and test5 resumes with ACPI interrupts gone. I'll try to be more specific, though.
Best regards,
Signature · 2 lines
Karol 'sziwan' Kozimor [email protected]
Hi!
Quoted 21 lines
Quoted 17 lines
Quoted 8 lines
I've been trying the new suspend to disk implementation (pmdisk, I think) lately. I get these lines in the kernel log when starting after a suspend:
PM: Reading pmdisk image.
PM: Resume from disk failed.
ACPI: (supports S0 S1 S3 S4 S5)Quoted 8 lines
Last time I tried swsusp, I did pass the resume= option, but it didn't work.
Could it be that some disk cache is never flushed properly? Occasionally, some random filesystem is reported as not being cleanly unmounted when booting normally, which seems to point in the same direction.
Quoted 3 lines
Try turning your disk cache off, or set it to write through caching (even so I heard some IDE drives don't turn it off anyway!). See if it helps.
Quoted 5 lines
That took me one step further. Now it loaded the image swap, but them immediately rebooted. I didn't have time to see if there were any error messages. I don't have a serial port, so I can't put a console there. This was with lots of modules loaded, so maybe unloading some would help. Are there any known broken drivers in this list:
Try it completely without modules. I'm not sure how it should work with modules which means it probably does not work at all.
Pavel
Signature · 2 lines
When do you have a heart between your knees? [Johanka's followup: and *two* hearts?]
Quoted 2 lines · Pavel Machek
Try it completely without modules. I'm not sure how it should work with modules which means it probably does not work at all.
Are you saying it doesn't work with any modules? What about all the people who have reported success with suspend-to-disk? I thought everyone used at least some modules.
Signature · 2 lines
Måns Rullgård [email protected]
Some modules cause problems. If I suspend with the intel-agp driver loaded, for example, the computer reboots when copying the original kernel back, because the hardware state doesn't match. I can suspend and resume my i830 based laptop just fine without it. Once the right changes are made to the driver, the module will work, but not yet.
Pavel, excuse me for jumping in here.
Regards,
Nigel
Quoted 8 lines · Måns Rullgård
Quoted 2 lines · Pavel Machek
Try it completely without modules. I'm not sure how it should work with modules which means it probably does not work at all.
Are you saying it doesn't work with any modules? What about all the people who have reported success with suspend-to-disk? I thought everyone used at least some modules.
Signature · 5 lines
Nigel Cunningham 495 St Georges Road South, Hastings 4201, New Zealand Evolution (n): A hypothetical process whereby infinitely improbable events occur with alarming frequency, order arises from chaos, and no one is given credit.
Quoted 8 lines · Pavel Machek
Quoted 5 lines
That took me one step further. Now it loaded the image swap, but them immediately rebooted. I didn't have time to see if there were any error messages. I don't have a serial port, so I can't put a console there. This was with lots of modules loaded, so maybe unloading some would help. Are there any known broken drivers in this list:
Try it completely without modules. I'm not sure how it should work with modules which means it probably does not work at all.
OK, so I tried it with just the a few modules loaded (those I couldn't unload, for some reason), and it worked. Now I guess I'll have to track down which modules are being evil.
Signature · 2 lines
Måns Rullgård [email protected]
Hi!
Quoted 7 lines
Some modules cause problems. If I suspend with the intel-agp driver loaded, for example, the computer reboots when copying the original kernel back, because the hardware state doesn't match. I can suspend and resume my i830 based laptop just fine without it. Once the right changes are made to the driver, the module will work, but not yet.
Pavel, excuse me for jumping in here.
No problem, I'm actually tired of replying to all those mails myself ;-).
Pavel
Signature · 9 lines
When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/