linux-kernel - Re: [BUG] 2.6.18-rc6: hda is allready "IN USE" when booting / pi futex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060912214822.GA20437@core>
Date:	Tue, 12 Sep 2006 23:48:22 +0200
From:	Christian Leber <christian@...er.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: [BUG] 2.6.18-rc6: hda is allready "IN USE" when booting / pi futex

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)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/