| Date | Sun, 17 Oct 2004 18:55:09 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U4 |
| |
* Florian Schmidt <mista.tapas@gmx.net> wrote:
> the cpu mhz issue seems to be fixed: > > ~$ uname -a > Linux mango.fruits.de 2.6.9-rc4-mm1-RT-U4-RT #1 Sun Oct 17 17:48:48 CEST 2004 i686 GNU/Linux > ~$ cat /proc/cpuinfo |grep MHz > cpu MHz : 1195.145 > mango:/usr/src/linux-2.6.9-rc4-mm1-VP-U4# grep REALTIME .config > CONFIG_PREEMPT_REALTIME=y > > Might of course be coincidence. Will report as soon as i see the 0.001 Mhz > pop up again.
ok.
> I saw one of these in /var/log/syslog: > > Oct 17 18:53:52 mango kernel: PCI: Found IRQ 3 for device 0000:00:0f.0 > Oct 17 18:53:52 mango kernel: Debug: sleeping function called from invalid context modprobe(109) at kernel/mutex.c:25 > Oct 17 18:53:52 mango kernel: in_atomic():0 [00000000], irqs_disabled():1 > Oct 17 18:53:52 mango kernel: [print_context_stack+78/112] dump_stack+0x1e/0x20 > Oct 17 18:53:52 mango kernel: [sinbin_release_fn+536/864] __might_sleep+0xb8/0xd0 > Oct 17 18:53:52 mango kernel: [__create_workqueue+35/320] _mutex_lock+0x23/0x60 > Oct 17 18:53:52 mango kernel: [__create_workqueue+145/320] _mutex_lock_irqsave+0x11/0x20 > Oct 17 18:53:52 mango kernel: [pg0+809943061/1069765632] get_time_pit+0x15/0x50 [gameport]
ok, does the patch below fix those messages? (gameport.c used its own, private, incompatible prototype for i8253_lock which breaks raw spinlock handling.)
Ingo
--- linux/drivers/input/gameport/gameport.c.orig +++ linux/drivers/input/gameport/gameport.c @@ -37,12 +37,13 @@ static LIST_HEAD(gameport_dev_list); #ifdef __i386__ +#include <asm/i8253.h> + #define DELTA(x,y) ((y)-(x)+((y)<(x)?1193182/HZ:0)) #define GET_TIME(x) do { x = get_time_pit(); } while (0) static unsigned int get_time_pit(void) { - extern spinlock_t i8253_lock; unsigned long flags; unsigned int count; - 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/
|