From: Zhang Le <r0bertz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel BUG
Date: Tue, 4 Nov 2008 21:36:11 +0800 [thread overview]
Message-ID: <20081104133610.GG27047@adriano.hkcable.com.hk> (raw)
In-Reply-To: <20081104074318.777c538e@osage.osagesoftware.com>
On 07:43 Tue 04 Nov , David Relson wrote:
...
>
> Questions:
>
> Is there a better way to capture the full BUG output???
> Once I have the full BUG output, what's the next useful thing to do?
Chances are the bug has already been fixed in later version.
Before you send the bug report, I suggest you to try a more recent version and
see if the bug disappears.
If you are interested in find the cause yourself, you can take a look at this:
/usr/src/linux/Documentation/oops-tracing.txt
Zhang, Le
prev parent reply other threads:[~2008-11-04 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 12:43 [gentoo-user] Kernel BUG David Relson
2008-11-04 13:17 ` Hazen Valliant-Saunders
2008-11-04 13:33 ` Jorge Peixoto de Morais Neto
2008-11-04 13:40 ` David Relson
2008-11-04 17:01 ` Volker Armin Hemmann
2008-11-04 13:36 ` Zhang Le [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=20081104133610.GG27047@adriano.hkcable.com.hk \
--to=r0bertz@gentoo.org \
--cc=gentoo-user@lists.gentoo.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