Re: [ANNOUNCE] Linux 2.6 Real Time Kernel

From: Måns Rullgård
Date: Sat Oct 09 2004 - 17:24:46 EST


Lee Revell <rlrevell@xxxxxxxxxxx> writes:

> On Sat, 2004-10-09 at 17:35, Måns Rullgård wrote:
>> Lee Revell <rlrevell@xxxxxxxxxxx> 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@xxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/