From: "Sven Dietrich" <sdietrich@mvista.com>
To: "Måns Rullgård" <mru@mru.ath.cx>, linux-kernel@vger.kernel.org
Cc: "Ext-Rt-Dev@Mvista. Com" <ext-rt-dev@mvista.com>
Subject: RE: [ANNOUNCE] Linux 2.6 Real Time Kernel
Date: Sat, 9 Oct 2004 15:54:41 -0700 [thread overview]
Message-ID: <EOEGJOIIAIGENMKBPIAEOEGLDKAA.sdietrich@mvista.com> (raw)
In-Reply-To:
Thanks for giving it a try!
The "bad: scheduling while atomic!" are indicative
of blocking on a mutex while holding a spinlock.
You can see the __p_mutex_down in the trace.
See the notes in the original announce
regarding the partitioning : work in progress.
I can't offer a fix for that now, but I will
post an updated mutex patch for the
EXPORT_SYMBOLS / module build issue.
Sven
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Måns Rullgård
> Sent: Saturday, October 09, 2004 6:15 AM
> To: linux-kernel@vger.kernel.org
> Subject: Re: [ANNOUNCE] Linux 2.6 Real Time Kernel
>
>
>
> I got this thing to build by adding a few EXPORT_SYMBOL, patch below.
> Now it seems to be running quite well. I am, however, getting
> occasional "bad: scheduling while atomic!" messages, all alike:
>
> bad: scheduling while atomic!
> [<c02ef301>] schedule+0x4e5/0x4ea
> [<c0114cbe>] try_to_wake_up+0x99/0xa8
> [<c01332e2>] __p_mutex_down+0xfe/0x190
> [<c029e238>] alloc_skb+0x32/0xc3
> [<c01335e0>] kmutex_is_locked+0x1f/0x33
> [<c029fa63>] skb_queue_tail+0x1c/0x45
> [<c02eb43e>] unix_stream_sendmsg+0x22c/0x38c
> [<c029ab03>] sock_sendmsg+0xc9/0xe3
> [<c029f95a>] skb_dequeue+0x4a/0x5b
> [<c02eb9e6>] unix_stream_recvmsg+0x119/0x430
> [<c0137f06>] __alloc_pages+0x1cc/0x33f
> [<c01168ca>] autoremove_wake_function+0x0/0x43
> [<c029af4b>] sock_readv_writev+0x6e/0x97
> [<c029afec>] sock_writev+0x37/0x3e
> [<c029afb5>] sock_writev+0x0/0x3e
> [<c014ebb8>] do_readv_writev+0x1db/0x21f
> [<c01168ca>] autoremove_wake_function+0x0/0x43
> [<c014e5ca>] vfs_read+0xd0/0xf5
> [<c014ec94>] vfs_writev+0x49/0x52
> [<c014ed5a>] sys_writev+0x47/0x76
> [<c0103f09>] sysenter_past_esp+0x52/0x71
>
> USB, sound and wireless are all working nicely.
>
> Now the patch:
>
> --- kernel/kmutex.c~ 2004-10-09 12:51:37 +02:00
> +++ kernel/kmutex.c 2004-10-09 13:50:43 +02:00
> @@ -20,6 +20,7 @@
> #include <linux/config.h>
> #include <linux/kmutex.h>
> #include <linux/sched.h>
> +#include <linux/module.h>
>
> # if defined CONFIG_PMUTEX
> # include <linux/pmutex.h>
> @@ -40,11 +41,14 @@
> return p_mutex_trylock(&(lock->kmtx));
> }
>
> +EXPORT_SYMBOL(kmutex_trylock);
>
> inline int kmutex_is_locked(struct kmutex *lock)
> {
> return p_mutex_is_locked(&(lock->kmtx));
> }
> +
> +EXPORT_SYMBOL(kmutex_is_locked);
> # endif
>
>
> @@ -60,6 +64,7 @@
> #endif
> }
>
> +EXPORT_SYMBOL(kmutex_init);
>
> /*
> * print warning is case kmutex_lock is called while preempt count is
> @@ -88,6 +93,8 @@
> #endif
> }
>
> +EXPORT_SYMBOL(kmutex_lock);
> +
> void kmutex_unlock(struct kmutex *lock)
> {
> #if defined CONFIG_KMUTEX_DEBUG
> @@ -102,6 +109,7 @@
> #endif
> }
>
> +EXPORT_SYMBOL(kmutex_unlock);
>
> void kmutex_unlock_wait(struct kmutex * lock)
> {
> @@ -111,4 +119,4 @@
> }
> }
>
> -
> +EXPORT_SYMBOL(kmutex_unlock_wait);
>
>
> --
> Måns Rullgård
> mru@mru.ath.cx
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next reply other threads:[~2004-10-09 22:55 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 22:54 Sven Dietrich [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 15:28 Vadim Lebedev
2004-10-11 15:50 ` Eugeny S. Mints
2004-10-09 11:38 John Hedditch
2004-10-09 5:59 Sven-Thorsten Dietrich
2004-10-09 6:40 ` Lee Revell
2004-10-09 7:33 ` Daniel Walker
2004-10-09 7:42 ` Lee Revell
2004-10-09 23:40 ` Matthias Urlichs
2004-10-09 8:52 ` Lee Revell
2004-10-09 23:20 ` Dave Hansen
2004-10-09 23:24 ` Lee Revell
2004-10-09 10:51 ` Måns Rullgård
2004-10-09 13:15 ` Måns Rullgård
2004-10-09 21:20 ` Lee Revell
2004-10-09 21:35 ` Måns Rullgård
2004-10-09 21:37 ` Lee Revell
2004-10-09 21:45 ` Måns Rullgård
2004-10-09 21:55 ` Lee Revell
2004-10-09 22:21 ` Måns Rullgård
2004-10-09 23:52 ` Lee Revell
2004-10-10 0:05 ` Måns Rullgård
2004-10-10 0:45 ` Lee Revell
2004-10-10 1:05 ` Måns Rullgård
2004-10-10 1:09 ` Lee Revell
2004-10-10 0:43 ` Micha Feigin
2004-10-10 1:08 ` Måns Rullgård
2004-10-09 17:41 ` Karim Yaghmour
2004-10-09 18:30 ` Lee Revell
2004-10-09 21:26 ` stefan.eletzhofer
2004-10-09 19:30 ` Lee Revell
2004-10-09 19:38 ` Måns Rullgård
2004-10-09 21:38 ` stefan.eletzhofer
2004-10-09 19:47 ` Lee Revell
2004-10-09 20:11 ` Karim Yaghmour
2004-10-09 20:14 ` Lee Revell
2004-10-09 20:53 ` Karim Yaghmour
2004-10-09 20:59 ` Lee Revell
2004-10-09 20:20 ` Robert Love
2004-10-09 20:25 ` Lee Revell
2004-10-10 1:15 ` Lee Revell
2004-10-10 8:46 ` Ingo Molnar
2004-10-10 19:41 ` Daniel Walker
2004-10-10 19:46 ` Ingo Molnar
2004-10-10 21:20 ` Andrew Morton
2004-10-10 21:59 ` Ingo Molnar
2004-10-11 17:53 ` Daniel Walker
2004-10-11 20:49 ` Ingo Molnar
2004-10-11 21:44 ` Sven Dietrich
2004-10-11 21:54 ` Ingo Molnar
2004-10-11 23:05 ` Sven Dietrich
2004-10-12 5:50 ` Ingo Molnar
2004-10-14 5:09 ` Dipankar Sarma
2004-10-14 7:18 ` Ingo Molnar
2004-10-15 14:59 ` Paul E. McKenney
2004-10-15 15:45 ` Ingo Molnar
2004-10-15 16:40 ` Paul E. McKenney
2004-10-15 16:45 ` Paul E. McKenney
2004-10-17 17:12 ` Ingo Molnar
2004-10-12 18:50 ` Daniel Walker
2004-10-10 12:21 ` John Richard Moser
2004-10-10 17:26 ` Lee Revell
2004-10-10 18:45 ` John Richard Moser
2004-10-10 20:20 ` Ingo Molnar
2004-10-10 20:44 ` John Richard Moser
2004-10-10 17:29 ` Daniel Walker
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=EOEGJOIIAIGENMKBPIAEOEGLDKAA.sdietrich@mvista.com \
--to=sdietrich@mvista.com \
--cc=ext-rt-dev@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@mru.ath.cx \
/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
all inboxes | Powered by JetHome®