Return-Path: <linux-kernel-owner+willy=40w.ods.org-S267505AbUJIWWK@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S267505AbUJIWWK (ORCPT <rfc822;willy@w.ods.org>);
	Sat, 9 Oct 2004 18:22:10 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267507AbUJIWWJ
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 9 Oct 2004 18:22:09 -0400
Received: from mail.broadpark.no ([217.13.4.2]:36522 "EHLO mail.broadpark.no")
	by vger.kernel.org with ESMTP id S267505AbUJIWWB convert rfc822-to-8bit
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 9 Oct 2004 18:22:01 -0400
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, ext-rt-dev@mvista.com
Subject: Re: [ANNOUNCE] Linux 2.6 Real Time Kernel
References: <41677E4D.1030403@mvista.com> <yw1xk6u0hw2m.fsf@mru.ath.cx>
	<1097356829.1363.7.camel@krustophenia.net>
	<yw1xis9ja82z.fsf@mru.ath.cx>
	<1097358925.1363.17.camel@krustophenia.net>
From: =?iso-8859-1?q?M=E5ns_Rullg=E5rd?= <mru@mru.ath.cx>
Date: Sun, 10 Oct 2004 00:21:50 +0200
In-Reply-To: <1097358925.1363.17.camel@krustophenia.net> (Lee Revell's
 message of "Sat, 09 Oct 2004 17:55:25 -0400")
Message-ID: <yw1x4ql3a5xd.fsf@mru.ath.cx>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2013
Lines: 51

Lee Revell <rlrevell@joe-job.com> writes:

> On Sat, 2004-10-09 at 17:35, M?ns Rullg?rd wrote:
>> Lee Revell <rlrevell@joe-job.com> writes:
>> 
>> > On Sat, 2004-10-09 at 09:15, M?ns Rullg?rd wrote:
>> >> 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:
>> >> 
>> >
>> > I am getting the same message.   Also, leaving all the default debug
>> > options on, I got this debug output, but it did not coincide with the
>> > "bad" messages.
>> >
>> > Mtx: dd84e644 [773] pri (0) inherit from [3] pri(92)
>> > Mtx dd84e644 task [773] pri (92) restored pri(0). Next owner [3] pri (92)
>> > Mtx: dd84e644 [773] pri (0) inherit from [3] pri(92)
>> > Mtx dd84e644 task [773] pri (92) restored pri(0). Next owner [3] pri (92)
>> > Mtx: dd84e644 [773] pri (0) inherit from [3] pri(92)
>> > Mtx dd84e644 task [773] pri (92) restored pri(0). Next owner [3] pri (92)
>> 
>> Well, those don't give me any clues.
>> 
>> I had the system running that kernel for a bit over an hour and got
>> five of the "bad" messages, approximately evenly spaced in a
>> two-minute interval about 20 minutes after boot.
>> 
>
> I am getting these too:
>
> bad: scheduling while atomic!
>  [<c0279c5a>] schedule+0x62a/0x630
>  [<c013b137>] kmutex_unlock+0x37/0x50
>  [<c013ab0d>] __p_mutex_down+0x1ed/0x360
>  [<c013b1e0>] kmutex_is_locked+0x20/0x40
>  [<c01cba47>] journal_dirty_data+0x77/0x230
>  [<c01bf2e2>] ext3_journal_dirty_data+0x12/0x40

My machine is mostly XFS, which might explain why I haven't seen any
of those.  I've found XFS to perform better with the multi-gigabyte
files I often deal with.

-- 
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/