linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	linux-efi@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: v4.4-rc8 based tip tree kernel hangs on boot.
Date: Fri, 15 Jan 2016 21:50:11 +0530	[thread overview]
Message-ID: <20160115162011.GA2935@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160112103043.GA5707@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

> 
> it's the first commit in the branch in fact.
> 
> To double check, it would be nice to check that applying that commit to v4.4 
> breaks the boot too:
> 
>   git checkout v4.4
>   git cherry-pick 21cdb6b568
> 

This actually boots. i.e cherry-pick 21cdb6b568 on top of v4.4 boots
well. Next I kept on adding cherry-picks from tip/x86/efi

git log --oneline tip/x86/efi looked like this 

e2c90dd x86/efi-bgrt: Replace early_memremap() with memremap()
98f9127 Merge tag 'efi-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi into x86/efi
50a0cb5 x86/efi-bgrt: Fix kernel panic when mapping BGRT data
26d7f65 x86/efi: Preface all print statements with efi* tag
3bb9eee doc: efi-stub.txt: Fix arm64 paths
7f83773 efi/esrt: Don't preformat name
ff3d0a1 Documentation/x86: Update EFI memory region description
67a9108 x86/efi: Build our own page table structures
c9f2a9a x86/efi: Hoist page table switching code into efi_call_virt()
b61a76f x86/efi: Map RAM into the identity page table for mixed mode
edc3b91 x86/mm/pat: Ensure cpa->pfn only contains page frame numbers
21cdb6b x86/mm: Page align the '_end' symbol to avoid pfn conversion bugs


So when I cherry-pick 67a9108 "x86/efi: Build our own page table
structures", the built kernel stops booting.

i.e until until I cherry-pick c9f2a9a, the kernel boots.

I still have to verify why git bisect was failing to give the right
commit.

Attached the dmesg of a good kernel boot as requested by Matt.

--
Thanks and Regards
Srikar

> ... but assuming the bisection is reliable, I'd say the evidence is pretty 
> conclusive already.
> 
> Srikar, could you please send the good and bad System.map files, so that we see 
> what the effects of the aligning were? The two interesting sha1's to test are:
> 
>   21cdb6b56843: first bad commit
>   6ffeba960734: last good commit (parent commit of 21cdb6b56843)
> 
> Thanks,
> 
> 	Ingo
> 

-- 
Thanks and Regards
Srikar Dronamraju

[-- Attachment #2: dmesg_good.txt.bz2 --]
[-- Type: application/octet-stream, Size: 25675 bytes --]

  parent reply	other threads:[~2016-01-15 16:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 19:29 v4.4-rc8 based tip tree kernel hangs on boot Srikar Dronamraju
2016-01-11 14:01 ` Matt Fleming
2016-01-11 15:10   ` Ingo Molnar
2016-01-11 16:47     ` Srikar Dronamraju
2016-01-12 10:30   ` Ingo Molnar
2016-01-14 12:25     ` Matt Fleming
2016-01-15 16:20     ` Srikar Dronamraju [this message]
2016-01-15 22:29       ` Matt Fleming
2016-01-17 17:32         ` Srikar Dronamraju
2016-01-18 15:40           ` Matt Fleming
2016-01-19 10:47             ` Srikar Dronamraju
2016-01-19 15:42               ` Matt Fleming
2016-01-19 18:17                 ` Srikar Dronamraju

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=20160115162011.GA2935@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).