From: Lee <linuxtwidler@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Bug Report
Date: Fri, 15 Jul 2005 14:24:05 -0500 [thread overview]
Message-ID: <20050715142405.0117dc21@localhost> (raw)
In-Reply-To: <1121455191.12420.40.camel@mindpipe>
Hi,
> > [20975.978911] PREEMPT SMP DEBUG_PAGEALLOC
> > [20976.029194] Modules linked in: vmnet vmmon nvidia
> > [20976.090907] CPU: 695757158
> > [20976.090909] EIP: 0060:[<c0119ed8>] Tainted: P VLI
>
> Please reproduce the bug without these proprietary modules loaded. And
> make sure to include the stack trace.
My current setup has the kernel and metalog logging to the serial port, which I am monitoring using kermit rom another machine.
Would you mind explaining to me how to generate the strace track and/or how to do "proper" debugging when this crash occurs?
ATM, the machine writes the report to the serial console, and completely freezes. I imagine that gdb would be involved here, but Im not sure how to go about setting that up.
--
Lee
linuxtwidler@gmail.com
14:21:30 up 5:40, 0 users, load average: 0.29, 0.20, 0.10
next prev parent reply other threads:[~2005-07-15 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 19:04 Kernel Bug Report Lee
2005-07-15 19:19 ` Lee Revell
2005-07-15 19:24 ` Lee [this message]
2005-07-15 19:38 ` Lee Revell
2005-07-15 19:41 ` Lee
-- strict thread matches above, loose matches on Subject: below --
2005-07-14 17:10 Paul Vander Griend
2005-07-14 17:30 ` Alexander Nyberg
2005-07-19 9:32 ` Alexander Nyberg
2004-06-19 19:34 David Michael Leo Brown Jr.
2004-06-20 8:50 ` Arjan van de Ven
2002-04-19 0:53 vinny.k
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=20050715142405.0117dc21@localhost \
--to=linuxtwidler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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