Created attachment 72132 [details] /proc/cpuinfo Hello If I boot my machine fresh and start oprofile, for example like: opcontrol --setup -e IBS_OP_ALL:50000:0x00 opcontrol --start everything works (oprofiled shows up in top with 1-2% CPU usage, opreport produces some meaningful output). If I do the same after suspend to RAM and resume, it doesn't complain about anything, but produces no samples ("error: no sample files found: profile specification too strict ?") and doesn't eat any CPU. New reboot or suspend to disk and resume makes it work again (I'm inserting the oprofile module anew each time, not keeping it in for the suspend). It works OK with 3.1.9. It works with the performance counters even after the suspend to RAM on 3.2.1. My guess is that the suspend to RAM leaves the CPU in some different state than it was before the suspend and the interrupts which should be triggered by the IBS are not fired. Which other information might be helpful? Thank you
This one looks forgotten and oprofile is gone since v5.12 so lemme close...