Messages in this thread | | | Date | Wed, 12 Jul 2006 14:17:04 +0200 (CEST) | From | Roman Zippel <> | Subject | Re: patch for timer.c - two dmesgs |
| |
Hi,
On Wed, 12 Jul 2006, Uwe Bugla wrote:
> Then the boot process does not take any break at all (like in kernel 2.6.18-rc1 and in kernels 2.6.17-mm*), but simply stops completely. > About 7 message lines are missing before X starts for presenting the graphical login prompt (proftpd, xprint etc.). > Perhaps two dmesgs help: one for a functionable 2.6.17.4 kernel (dmesg17), another for the kernel in question (dmesg18).
A lot has changed since then... Did you try using SysRq+P or Alt+ScrollLock? (A SysRq+T might be useful too).
> Simply my intuition tells me that a system timer performs very different > on two very different machines with two very different CPU frequencies > and two very different main processors.
No offense, it's no intuition, but a shot in the dark. If you at least tried a few more kernels (at least 2.6.18-mm1 and 2.6.18-mm2), it would be a much better indication whether it's the timer patch.
bye, Roman - 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/
| |