From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: Eran Mann <emann@mrv.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc5-V0.7.47-15
Date: Tue, 31 May 2005 10:55:34 +0200 [thread overview]
Message-ID: <429C2686.7030004@stud.feec.vutbr.cz> (raw)
In-Reply-To: <1117527531.19367.31.camel@ibiza.btsn.frna.bull.fr>
Serge Noiraud wrote:
> Kernel: arch/i386/boot/bzImage is ready
> Building modules, stage 2.
> MODPOST
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/scsi/qla2xxx/qla2xxx.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/pci/hotplug/shpchp.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/pci/hotplug/pciehp.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/pci/hotplug/pci_hotplug.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/pci/hotplug/ibmphp.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/pci/hotplug/cpqphp.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/net/plip.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/char/watchdog/cpu5wdt.ko] undefined!
> *** Warning: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/block/sx8.ko] undefined!
Have you tried loading and using some of these modules with older -RT
kernels? If they have been using init_MUTEX_LOCKED on RT semaphores,
they should have BUG & Oops. Recent -RT kernels have added extra check
for this during linking. The fact that you are prevented from building
these modules is a Good Thing(TM).
Maybe these drivers should be using completions instead of semaphores.
A quick fix would be changing the 'struct semaphore' to 'struct
compat_semaphore'.
Michal
next prev parent reply other threads:[~2005-05-31 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 7:28 [patch] Real-Time Preemption, -RT-2.6.12-rc5-V0.7.47-10 Ingo Molnar
2005-05-27 12:48 ` Gene Heskett
2005-05-31 7:28 ` Eran Mann
2005-05-31 8:18 ` [patch] Real-Time Preemption, -RT-2.6.12-rc5-V0.7.47-15 Serge Noiraud
2005-05-31 8:55 ` Michal Schmidt [this message]
2005-05-31 12:09 ` Gene Heskett
2005-05-31 16:17 ` Gene Heskett
2005-06-01 8:01 ` [patch] Real-Time Preemption, -RT-2.6.12-rc5-V0.7.47-10 Ingo Molnar
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=429C2686.7030004@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=emann@mrv.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=serge.noiraud@bull.net \
/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