> I presume you're looking for ide0 and ide1 interrupts, yes, after
> suspending to ram twice the command showed that interrupt 14 (ide0)
> increased from 994 to 1011 and for 15 (ide1) it stayed at 24. My hdd is
> on hda so that'll be on ide0, dvd-rw is on hdc or ide1.
> The interrupt counts for cascade (irq 2), rtc (irq 8) and acpi (irq 9)
> stayed constant though, at 0, 2 and 4 respectively.
> No NMI or ERR conditions were ever signaled.
> Now, with APIC, but no IO-APIC there is a bug notice during resume.
> Going to type it over (from dmesg):
> Back to C!
> Debug: sleeping function called from invalid context at mm/slab.c:2472
> in_atomic():0, irqs_disabled():1
I know, it is scary, but it is also known and harmless. You can ignore
> ACPI: PCI Interrupt 0000:00:14.1[A] -> Link [LNK0] -> GSI 11 (level,
> low) -> IRQ 11
> ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK0] -> GSI 11 (level,
> low) -> IRQ 11
> Restarting tasks... done
> Both cases looks identical. /proc/interrupts doesn't list 11 as an
> interrupt ?!?
Talk to acpi people about that.
> Also, this time round the auto-repeat on the keys is working again after
> resume. In fact, everything seems to be working. Just that debug
> stacktrace that bothers me. Oh, and my console blanking time also seems
> to get lost but I can fix that with the help of echo and /dev/tty*.
> Anyhow, suspended twice to ram now in succession, make cleaned and
> rebuilt the kernel, installed it, and the only thing that even suggests
> there is a glitch is that trace.
> Looks like I need APIC on and IO-APIC off. Any explanations very
> welcome: and don't tell me the IO-APIC is buggy - I've been running
> with both those options on for as long as I've had this notebook now.
I do not know enough explanations, feel free to investigate.
Anyway so both suspend-to-ram and suspend-to-disk now works for you,
right? No need to press keys to make it write image on disk?
Oh and thanks for video.txt diff, applied.