All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pieter Palmers <pieterp@joow.be>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lee Revell <rlrevell@joe-job.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: status of: tasklet_unlock_wait() causes soft lockup with -rt and ieee1394	audio
Date: Sat, 27 Jan 2007 11:19:27 +0100	[thread overview]
Message-ID: <45BB272F.3020508@joow.be> (raw)
In-Reply-To: <20070122091035.GA11821@elte.hu>

Ingo Molnar wrote:
> * Pieter Palmers <pieterp@joow.be> wrote:
> 
>> Dear all,
>>
>> What is the status with respect to this problem? I see that in the 
>> current -rt patch the problematic code piece is different. I 
>> personally haven't tried to reproduce this myself on a more recent 
>> kernel, but I just got a report from one of our users who experienced 
>> the same problem with 2.6.19-rt15 and RT preemption (desktop 
>> preemption works fine).
>>
>> Should the latest -rt patches be fixed with respect to this issue? If 
>> so I'll try and test them, otherwise I omit the effort.
> 
> it's not fixed yet. Could you try the patch below?

I just compiled & installed 2.6.20-rc6-rt2, and I saw that this patch 
was in the -rt2 patch, so I gave real-time preemption a shot. It seems 
to work, I don't experience lockups anymore.

Thanks for the fix,

Pieter

      parent reply	other threads:[~2007-01-27 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 15:18 tasklet_unlock_wait() causes soft lockup with -rt and ieee1394 audio Lee Revell
2006-07-09  1:51 ` Steven Rostedt
2006-07-09  2:12   ` Lee Revell
2006-07-09 11:17     ` Pieter Palmers
2006-07-10 14:41       ` Daniel Walker
2007-01-21 23:30 ` status of: " Pieter Palmers
2007-01-22  9:10   ` Ingo Molnar
2007-01-25  9:04     ` Pieter Palmers
2007-01-27 10:19     ` Pieter Palmers [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=45BB272F.3020508@joow.be \
    --to=pieterp@joow.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.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 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.