From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267519AbUJIWzi (ORCPT ); Sat, 9 Oct 2004 18:55:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267526AbUJIWzi (ORCPT ); Sat, 9 Oct 2004 18:55:38 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:64508 "EHLO av.mvista.com") by vger.kernel.org with ESMTP id S267519AbUJIWyT (ORCPT ); Sat, 9 Oct 2004 18:54:19 -0400 From: "Sven Dietrich" To: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= , Cc: "Ext-Rt-Dev@Mvista. Com" Subject: RE: [ANNOUNCE] Linux 2.6 Real Time Kernel Date: Sat, 9 Oct 2004 15:54:41 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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! > [] schedule+0x4e5/0x4ea > [] try_to_wake_up+0x99/0xa8 > [] __p_mutex_down+0xfe/0x190 > [] alloc_skb+0x32/0xc3 > [] kmutex_is_locked+0x1f/0x33 > [] skb_queue_tail+0x1c/0x45 > [] unix_stream_sendmsg+0x22c/0x38c > [] sock_sendmsg+0xc9/0xe3 > [] skb_dequeue+0x4a/0x5b > [] unix_stream_recvmsg+0x119/0x430 > [] __alloc_pages+0x1cc/0x33f > [] autoremove_wake_function+0x0/0x43 > [] sock_readv_writev+0x6e/0x97 > [] sock_writev+0x37/0x3e > [] sock_writev+0x0/0x3e > [] do_readv_writev+0x1db/0x21f > [] autoremove_wake_function+0x0/0x43 > [] vfs_read+0xd0/0xf5 > [] vfs_writev+0x49/0x52 > [] sys_writev+0x47/0x76 > [] 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 > #include > #include > +#include > > # if defined CONFIG_PMUTEX > # include > @@ -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/ >