From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: pavel@pavlinux.ru,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Clark Williams <williams@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Tue, 09 Jun 2015 20:10:10 -0700 [thread overview]
Message-ID: <5577AA92.5070203@localhost> (raw)
In-Reply-To: <5577633A.2060100@pavlinux.ru>
On 06/09/2015 03:05 PM, Pavel Vasilyev wrote:
> 09.06.2015 19:45, Fernando Lopez-Lezcano пишет:
>
>> This is still happening, about once a day. John Dulaney help me set up a
>> crash kernel dump (thanks!) so now I have a kernel core dump for this
>> one,
>
> Asus,Fedora,CGROUPS, iptables,snd_ac97,radeon,raid1,kvm - this realtime
> system? :D
:-P
Yup. I have been using rt for many years - and packaging it - for (very)
low latency sound processing. Linux + rt + jackd + rtirq + threaded irqs
+ jack clients, everything with the right priorities. Runs very nicely
unless you hit an issue like the one I'm asking about[*]. Usually
running snd_hdspm with RME hardware when in concert situations (this one
with Asus mobo is my - quite old by now - desktop at work, but I'm also
having the same problem in my Lenovo laptop).
-- Fernando
[*] for example a whole concert for a 24.8 3D sound system with a remote
ethernet driven D/A and running all the time with 64 frame x 2 buffers
at 48KHz.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: pavel@pavlinux.ru,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
Clark Williams <williams@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Tue, 09 Jun 2015 20:10:10 -0700 [thread overview]
Message-ID: <5577AA92.5070203@localhost> (raw)
In-Reply-To: <5577633A.2060100@pavlinux.ru>
On 06/09/2015 03:05 PM, Pavel Vasilyev wrote:
> 09.06.2015 19:45, Fernando Lopez-Lezcano пишет:
>
>> This is still happening, about once a day. John Dulaney help me set up a
>> crash kernel dump (thanks!) so now I have a kernel core dump for this
>> one,
>
> Asus,Fedora,CGROUPS, iptables,snd_ac97,radeon,raid1,kvm - this realtime
> system? :D
:-P
Yup. I have been using rt for many years - and packaging it - for (very)
low latency sound processing. Linux + rt + jackd + rtirq + threaded irqs
+ jack clients, everything with the right priorities. Runs very nicely
unless you hit an issue like the one I'm asking about[*]. Usually
running snd_hdspm with RME hardware when in concert situations (this one
with Asus mobo is my - quite old by now - desktop at work, but I'm also
having the same problem in my Lenovo laptop).
-- Fernando
[*] for example a whole concert for a 24.8 3D sound system with a remote
ethernet driven D/A and running all the time with 64 frame x 2 buffers
at 48KHz.
next prev parent reply other threads:[~2015-06-10 3:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51 ` Pavel Vasilyev
2015-05-20 7:12 ` Sebastian Andrzej Siewior
2015-05-20 7:12 ` Sebastian Andrzej Siewior
2015-05-20 13:18 ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20 3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09 ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08 ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22 ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04 ` Mats Karrman
2015-06-11 13:14 ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12 7:22 ` Vinod Koul
2015-06-12 10:37 ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38 ` Steven Rostedt
2015-05-26 13:48 ` Clark Williams
2015-05-26 14:49 ` Mike Galbraith
2015-05-26 15:19 ` Steven Rostedt
2015-05-26 15:43 ` Clark Williams
2015-05-26 19:41 ` Fernando Lopez-Lezcano
2015-05-29 1:56 ` Fernando Lopez-Lezcano
2015-06-09 16:45 ` Fernando Lopez-Lezcano
2015-06-09 16:45 ` Fernando Lopez-Lezcano
2015-06-09 22:05 ` Pavel Vasilyev
2015-06-10 2:41 ` Mike Galbraith
2015-06-10 2:41 ` Mike Galbraith
2015-06-10 3:10 ` Fernando Lopez-Lezcano [this message]
2015-06-10 3:10 ` Fernando Lopez-Lezcano
2015-06-09 22:10 ` Pavel Vasilyev
2015-06-09 22:10 ` Pavel Vasilyev
2015-06-11 12:38 ` Sebastian Andrzej Siewior
2015-06-11 12:38 ` Sebastian Andrzej Siewior
2015-05-28 8:41 ` Joakim Hernberg
2015-06-11 12:34 ` Sebastian Andrzej Siewior
2015-05-27 9:44 ` Joakim Hernberg
2015-05-27 10:19 ` Jeremy Jongepier
2015-05-28 8:33 ` Joakim Hernberg
2015-05-28 8:33 ` Joakim Hernberg
2015-05-27 15:50 ` Ralf Mardorf
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=5577AA92.5070203@localhost \
--to=nando@ccrma.stanford.edu \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@pavlinux.ru \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.