Juergen Kreileder writes: > BTW, xmon doesn't work for me. 'echo x > /proc/sysrq-trigger' gives > me a :mon> prompt but I can't enter any commands. We don't have polled interrupts-off input methods for USB keyboards. If you get a "stealth" serial port for your G5 you can run xmon over that. Paul. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: "David S. Miller" <[email protected]>
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- References:
- [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: Oleg Nesterov <[email protected]>
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: Andrew Morton <[email protected]>
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: Juergen Kreileder <[email protected]>
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- From: Juergen Kreileder <[email protected]>
- [PATCH] fix __mod_timer vs __run_timers deadlock.
- Prev by Date: [Benchmark] Linux 2.6.11.6 ARM MMU mode vs. noMMU mode vs. MVista 2.4.20
- Next by Date: Re: Mercurial 0.4b vs git patchbomb benchmark
- Previous by thread: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- Next by thread: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
- Index(es):
 |