From: Andrea Arcangeli <andrea@suse.de>
To: Marcus Hartig <m.f.h@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-aa1
Date: Mon, 5 Apr 2004 21:02:25 +0200 [thread overview]
Message-ID: <20040405190225.GL2234@dualathlon.random> (raw)
In-Reply-To: <4071A601.5000402@web.de>
On Mon, Apr 05, 2004 at 08:31:29PM +0200, Marcus Hartig wrote:
> Andrea Arcangeli wrote:
>
> >That should reduce the scope of the problem, I had a look at the
> >diff between rc3 and 2.6.5 final but I found nothing obvious that could
> >explain your problem (yet).
>
> It seems to be CONFIG_PREEMPT. I have compiled the 2.6.5-aa1 only without
> it and ET runs now 30min without a signal11.
sounds good, probably a preempt bug in the alsa code or an rcu issue or
something like that. my tree has the most important fixes in the
writeback code from Takashi to provide the same lowlatency w/ or w/o
CONFIG_PREEMPT so you shouldn't notice much difference either ways. It
was a good decision to leave preempt off for higher reliability too,
preempt isn't just a matter of spinlocks, sometime you need explicit
preempt_disable to make it work right.
still it'd be nice to fix it purerly as an exercise, exercises are
useful nevertheless ;).
next prev parent reply other threads:[~2004-04-05 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 21:05 2.6.5-aa1 Marcus Hartig
2004-04-04 22:59 ` 2.6.5-aa1 Jeff Sipek
2004-04-05 0:20 ` 2.6.5-aa1 Andrea Arcangeli
2004-04-05 2:18 ` 2.6.5-aa1 Jeff Sipek
2004-04-05 5:39 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 7:03 ` 2.6.5-aa1 Jeff Sipek
[not found] ` <1081185096.8036.3.camel@nosferatu.lan>
2004-04-05 17:28 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 18:31 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 19:02 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 5:22 2.6.5-aa1 Andrea Arcangeli
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=20040405190225.GL2234@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.f.h@web.de \
/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