linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Gareus <robin@gareus.org>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
	The Linux Audio Developers' Mailing List
	<linux-audio-dev@lists.linuxaudio.org>
Subject: Re: remembering rt-sched attributes - was: [LAD] rtirq script is broken with  2.6.31
Date: Wed, 12 Aug 2009 11:24:17 +0200	[thread overview]
Message-ID: <4A828A41.9040109@gareus.org> (raw)
In-Reply-To: <4A80A0A7.8000807@rncbc.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rui Nuno Capela wrote:
> Robin Gareus wrote:
>> 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?
> 

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
-----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-----

      reply	other threads:[~2009-08-12  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A7B01F3.2060200@gareus.org>
     [not found] ` <4A7B3EA6.1080509@rncbc.org>
     [not found]   ` <4A7C259D.9020409@gareus.org>
2009-08-09 14:52     ` remembering rt-sched attributes - was: [LAD] rtirq script is broken with 2.6.31 Robin Gareus
2009-08-10 22:35       ` Rui Nuno Capela
2009-08-12  9:24         ` Robin Gareus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A828A41.9040109@gareus.org \
    --to=robin@gareus.org \
    --cc=linux-audio-dev@lists.linuxaudio.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rncbc@rncbc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).