Summary: | kernel hangs and shows lots of infos - too fast to read | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Georg Müller <georgmueller> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kernel config from athlon64
dmesg output |
Description
Georg Müller
2004-10-25 11:04:06 UTC
Created attachment 42630 [details]
kernel config from athlon64
here is the config of my athlon 64
Is the system bootable despite all the messages flying past? Can you confirm that you don't have kernel debugging enabled in your .config? The system is not bootable when this happens. And the output never stops. I have set CONFIG_DEBUG_KERNEL to have the possibility to use magic sysrq (CONFIG_MAGIC_SYSRQ) - nothing more. Is there any possibility to "freeze" the screen to read the content? I tried to do a photo, put it wasn't very good... Could you see if the issue is still present with development-sources-2.6.10-rc1? Also, one possible way you could catch some error messages is with a serial console. Is this an option for you? Created attachment 43208 [details]
dmesg output
Ok, I was wrong with my thougt that nothing works, than this happens. I now
have a dmesg-output of these things.
It allways mentions the process consolelog.sh (which has as its only line: echo
"$1 [$2] $3" >/dev/vc/10 ), part of metalog.
Eeesh! The first entry in that attachment is the 1975th oops that has occured since bootup, thats quite an achievement ;) If you remove metalog from your runlevels, do you still encounter the problem? ok, my problem seems to be de duplicate of #65164 |