public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Testing new kernels - saving dumps / strip down kernel options
Date: Tue, 08 Jan 2013 13:14:16 +0100	[thread overview]
Message-ID: <50EC0D98.6070104@xunil.at> (raw)


I recently pulled in the vanilla linux-kernel-sources via git and
compiled my own "daily" kernel to simply test things on my thinkpad.

I get kernel crashes and would like to report them back upstream somewhere.

* to store the crash messages:

Is this still the way to go?

http://wiki.gentoo.org/wiki/Kernel_Crash_Dumps

Any other method recommended?

* should the reports go straight to the lkml-mailinglist?

I feel kind of misplaced there, plain stupid user amongst all those
kernel-devs ;-)

* I remember a thread here where this was discussed already:

How do you guys get to your .config for a recent kernel? "make
oldconfig" doesn't always work out best, I recall?

My kernel config is maintained along for years now and has survived
several hardware changes. I don't have any obvious problems but I wonder
if I have something in there that is deprecated and might be better
thrown out.

Does it make sense to take the .config from the gentoo install dvd for
example and remove all the stuff I don't have? Maybe still too much
enabled options in the end.

"make allnoconfig" as a start?

allmodconfig ?

I'd be happy to hear your opinions.

Stefan


             reply	other threads:[~2013-01-08 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 12:14 Stefan G. Weichinger [this message]
2013-01-10  9:38 ` [gentoo-user] Re: Testing new kernels - saving dumps / strip down kernel options Nuno J. Silva
2013-01-11  6:56   ` Stefan G. Weichinger
2013-01-11  6:28 ` [gentoo-user] " Stroller
2013-01-11  6:59   ` Stefan G. Weichinger

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=50EC0D98.6070104@xunil.at \
    --to=lists@xunil.at \
    --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