LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Latest kernel doesn't boot
Date: Wed, 06 Feb 2008 21:18:59 +0100	[thread overview]
Message-ID: <47AA1633.4000309@m3y3r.de> (raw)
In-Reply-To: <47A8E427.6040205@zytor.com>

H. Peter Anvin schrieb:
> thomas@m3y3r.de wrote:
>> The latest linux kernel doesn't boot on my computer
>> (h=21511abd0a248a3f225d3b611cfabb93124605a7).
>>
>> elilo hangs while booting this kernel. 2.6.24 works.
>
> Wow, so we know it's affected with EFI, since you're using elilo.
>
> You gave absolutely zero other information about your system or what 
> "doesn't boot" mean.
Here is an older bisection try:
$ git bisect log

git-bisect start
# bad: [dd430ca20c40ecccd6954a7efd13d4398f507728] Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
git-bisect bad dd430ca20c40ecccd6954a7efd13d4398f507728
# good: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24
git-bisect good 49914084e797530d9baaf51df9eda77babc98fa8
# good: [f4d900a2cae94256f56be7769734100c7054bf00] [NETLINK]: Mark 
attribute construction exception unlikely
git-bisect good f4d900a2cae94256f56be7769734100c7054bf00
# good: [85040bcb4643cba578839e953f25e2d1965d83d0] [IPV6] ADDRLABEL: Fix 
double free on label deletion.
git-bisect good 85040bcb4643cba578839e953f25e2d1965d83d0
# good: [70fd93c9d9e07dd2ea4465df76a0ddd414fd21ac] x86: export cpu_gdt_descr
git-bisect good 70fd93c9d9e07dd2ea4465df76a0ddd414fd21ac
# bad: [306c142f99caef5a30a0d61a39a956c069941b63] x86: pat: e820 cleanup
git-bisect bad 306c142f99caef5a30a0d61a39a956c069941b63
# bad: [7271339347653f6d652bb47aaee1f57d936002f6] x86: 
arch/x86/kernel/cpu/mcheck/k7.c checkpatch fixes
git-bisect bad 7271339347653f6d652bb47aaee1f57d936002f6
# bad: [7818a1e0294debee02d5135e17b89f28b8871887] x86: provide 64-bit 
with a load_sp0 function.
git-bisect bad 7818a1e0294debee02d5135e17b89f28b8871887
# bad: [2215e69d2cf5024647f9a034807990590d25dd4e] x86 boot: use E820 
memory map on EFI 32 platform
git-bisect bad 2215e69d2cf5024647f9a034807990590d25dd4e
# good: [26048d75e8d6c840742468667f4a7ab8c2df74c9] x86: use the same 
data type for tls_array.
git-bisect good 26048d75e8d6c840742468667f4a7ab8c2df74c9
# good: [341d8854d38fe6e7655f7748babae5c25a51aa70] x86: remove fastcall 
from include/asm-x86
git-bisect good 341d8854d38fe6e7655f7748babae5c25a51aa70
# good: [8c8b8859b64baf6d7c33900e8720c7bafe775b2c] mcheck mce_64: 
mce_read_sem to mutex
git-bisect good 8c8b8859b64baf6d7c33900e8720c7bafe775b2c
# good: [de18c850af701ac9512b7239e88fa45e4c168771] x86: EFI runtime 
service support: EFI runtime services
git-bisect good de18c850af701ac9512b7239e88fa45e4c168771
# bad: [e429795c68d3001ecae74f6465420c9f043b0ece] x86: EFI runtime 
service support: remove duplicated code from efi_32.c
git-bisect bad e429795c68d3001ecae74f6465420c9f043b0ece
# good: [9ad65e4748f55e3159283d7fa9d54fb30c086113] x86: EFI runtime 
service support: document for EFI runtime services
git-bisect good 9ad65e4748f55e3159283d7fa9d54fb30c086113


I can not revert the commit e429795c68d3001ecae74f6465420c9f043b0ece. it 
gave me errors.
but i'm also not sure what could be wrong with this commit!

my first idea was that the commit 
"[2215e69d2cf5024647f9a034807990590d25dd4e] x86 boot: use E820 memory 
map on EFI 32 platform" is the offender, because the macbook pro doesn't 
provide a e820 memory map at all. but bisect showed that i'm wrong here?!

confused greeting
thomas


  parent reply	other threads:[~2008-02-06 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 22:15 thomas
2008-02-05 22:33 ` H. Peter Anvin
2008-02-05 23:57   ` thomas
2008-02-06 20:18   ` Thomas Meyer [this message]
2008-02-06 21:02     ` H. Peter Anvin
2008-02-06 21:27       ` Thomas Meyer
2008-02-06 21:45         ` H. Peter Anvin
2008-02-09 18:39           ` Thomas Meyer
2008-02-11 17:42             ` Jason Fleischli
2008-02-13  2:01             ` Huang, Ying

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=47AA1633.4000309@m3y3r.de \
    --to=thomas@m3y3r.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Latest kernel doesn'\''t boot' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).