From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm2
Date: Fri, 16 Jan 2004 00:56:10 +0100 [thread overview]
Message-ID: <4007289A.3000005@gmx.de> (raw)
In-Reply-To: <20040115152306.2c56d6e3.rddunlap@osdl.org>
> | > When the kernel prints that `badness' message it then prints a stack
> | > backtrace. That's what we want.
> |
> | But how to get that? When the machine locks up, I don't see anything
> | written and only *sometimes* I got above message in the log -whcih I
> | can only see afterwards. But there is nothing else realted to it in the
> | log...
>
> (I didn't see any replies to this...)
>
> The usual answer is to use a serial console to log the kernel messages,
> but not everyone has that option available to them.
>
> Depending on your system, you might be able to use kmsgdump to
> capture the final kernel messages to a floppy disk (if you have a
> "legacy" type floppy). If you are interested in trying that,
> the kmsgdump patch is available at
> http://developer.osdl.org/rddunlap/kmsgdump/
Sounds interesting. I will give it a try. But according to your other
post, it seems to have problems with APIC, so just the case which seems
to make problems for me...
Prakash
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-01-15 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 9:45 2.6.1-mm2 Andrew Morton
2004-01-10 14:55 ` 2.6.1-mm2 Roberto Sanchez
2004-01-12 5:47 ` 2.6.1-mm2 (compile stats) John Cherry
2004-01-13 13:31 ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 17:54 ` 2.6.1-mm2 Andrew Morton
2004-01-13 19:06 ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 19:16 ` 2.6.1-mm2 Andrew Morton
2004-01-13 19:22 ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-15 23:23 ` 2.6.1-mm2 Randy.Dunlap
2004-01-15 23:56 ` Prakash K. Cheemplavam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4007289A.3000005@gmx.de \
--to=prakashkc@gmx.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox