12 Aug
2009
12 Aug
'09
7:24 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rui Nuno Capela wrote:
Robin Gareus wrote:
Sure, adding it to
/usr/lib/hal/scripts/linux/hal-system-power-suspend-linux
or a script in /etc/acpi/resume.d/ (depending on the distribution)
does the trick.
However it would be necessary to be included in quite a few
distributions: Ubuntustudio, 64studio, AVlinux, JACKlab, etc. It would
be better if the problem could be solved at the source.
Anyways, can anyone explain why only a particular set of IRQ-threads are
affected by this issue?
robin
Hello rt-users and -devs,
I have a question about per-device-IRQ-threads in 2.6.31-rc5-rt1.1:
After a suspend/resume cycle some IRQ-threads come up with a new PID.
The scheduling policy of those threads is reset to default values
instead of retaining the previously set values.
Is this an issue that is being worked on? Or must userspace from now on
re-init rtprio settings after each suspend/resume cycle?
As you can see from the information below (from linux-audio-dev @
linuxaudio.org) not all IRQ-threads are re-started, but for example the
HDA-Intel is. It may just as well be a specific issue with snd_hda_intel
(and sdhci, e1000e, i810/intelfb,..).
[...]
picking on old subject, why not doing a plain `/etc/init.d/rtirq
restart` on resume?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqCikEACgkQeVUk8U+VK0J0eQCeNPiTVO6wLBkuNc2CaQLpPuK4
h/sAnRGExpwt4zKQ1PH7LSo2NlCF6Y55
=oGVR
-----END PGP SIGNATURE-----