Re: [ANNOUNCE] Linux 2.6 Real Time Kernel

From: Måns Rullgård
Date: Sat Oct 09 2004 - 20:08:21 EST


Lee Revell <rlrevell@xxxxxxxxxxx> writes:

> On Sat, 2004-10-09 at 20:05, Måns Rullgård wrote:
>> 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.
>> >
>> > Pid 773 is the IRQ thread for eth0. I am using the via-rhine driver.
>>
>> I was using a prism54 wireless card.
>
> OK, first bug: I lost my PS/2 keyboard, and had to reboot to get it
> back. Unplugging and replugging it made Num Lock work again, but the
> system did not respond to the keyboard at all. USB mouse continued to
> work fine.

I lost my keyboard as well, though only in X, but I figured that could
be caused by some changes to the input layer that went in between
2.6.9-rc2 and -rc3. My synaptics touchpad also stopped working
properly. USB keyboard and mouse worked properly.

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