From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Igor Mammedov <imammedo@redhat.com>,
Toshi Kani <toshi.kani@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTED][REGRESSION] Kernel does not boot on EeePC
Date: Tue, 10 Jun 2014 20:19:43 +0100 [thread overview]
Message-ID: <20140610191943.GA19896@sucs.org> (raw)
In-Reply-To: <20140609140215.GA1579@gmail.com>
On Mon, Jun 09, 2014 at 04:02:15PM +0200, Ingo Molnar wrote:
>
> * H. Peter Anvin <hpa@zytor.com> wrote:
>
> > I really want to say *THANK YOU* to Sitsofe for a very timely and
> > complete report. You really saved us some highly valuable time.
>
> Seconded!
You're welcome. For what it's worth these are the things that allowed
this drive-by testing to occur:
git bisect:
Without this there would have been a generic complaint that would have
only gone to the general kernel mailing list. I thought the issue was
going to lie with the GPU drivers but just following the bisection and
testing the final commit zoned in on the true cause.
Able to cut out most features:
I tend to build cut down kernels which only supports my hardware because
they take less time to compile and boot faster.
Single file builds:
I often do builds on Internet connected machines. Because I can
can build everything in I only have one file to copy at the end.
Distro doesn't need initrd/initramfs:
One less thing to setup because everything is built in but some distros
seem dependent on having one these days.
I guess the one nice thing to have in the future would be a make
checkedconfig that automatically turned on all checking/verification
features (e.g. slab debugging/memory poisoning) for the current config.
This is would make it easier to get such kernels
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-06-10 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 9:02 [BISECTED][REGRESSION] Kernel does not boot on EeePC Sitsofe Wheeler
2014-06-08 9:45 ` Ingo Molnar
2014-06-08 17:50 ` H. Peter Anvin
2014-06-09 14:02 ` Ingo Molnar
2014-06-10 19:19 ` Sitsofe Wheeler [this message]
2014-06-09 10:26 ` Igor Mammedov
2014-06-11 6:16 ` Sitsofe Wheeler
2014-06-11 12:48 ` Igor Mammedov
2014-06-11 13:05 ` Sitsofe Wheeler
2014-06-11 13:19 ` Igor Mammedov
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=20140610191943.GA19896@sucs.org \
--to=sitsofe@gmail.com \
--cc=hpa@zytor.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.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