public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Leber <christian@leber.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [BUG] 2.6.18-rc6: hda is allready "IN USE" when booting / pi futex
Date: Tue, 12 Sep 2006 23:48:22 +0200	[thread overview]
Message-ID: <20060912214822.GA20437@core> (raw)
In-Reply-To: <20060912173455.GB6236@elte.hu>

On Tue, Sep 12, 2006 at 07:34:55PM +0200, Ingo Molnar wrote:

> yeah, i too suspect that it's timing related.

I guess that means it's actually a bug in the ide chipset driver.

> The b29739f902ee76a05493fb7d2303490fc75364f4 patch is quite large, so i 
> have created a finegrained, functional splitup of it:
> 
>   sched-cleanups.patch
>   sched-add-task-rq-lock-ops.patch
>   sched-add-rt-mutex-setprio.patch
>   sched-pi-lock.patch
>   sched-add-new-macros.patch
>   sched-add-normal-prio.patch
>   sched-use-has-rt-policy.patch

until here everthing seems to be ok (20 boots)

>   sched-set-user-nice-fix.patch

here we go, that one triggers the problem

>   sched-use-normal-prio.patch
> 
> and have attached the resulting tarball.

Thank you a lot, i didn't know how to split it up.


Christian Leber

-- 
  "Omnis enim res, quae dando non deficit, dum habetur et non datur,
   nondum habetur, quomodo habenda est."       (Aurelius Augustinus)

  reply	other threads:[~2006-09-12 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 13:33 [BUG] 2.6.18-rc6: hda is allready "IN USE" when booting (non-deterministic) Christian Leber
2006-09-12 15:39 ` [BUG] 2.6.18-rc6: hda is allready "IN USE" when booting / pi futex Christian Leber
2006-09-12 17:34   ` Ingo Molnar
2006-09-12 21:48     ` Christian Leber [this message]
2006-09-12 21:55       ` Ingo Molnar
2006-09-13  1:24         ` Christian Leber

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=20060912214822.GA20437@core \
    --to=christian@leber.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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