From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: sparc next boot failure
Date: Mon, 01 Dec 2008 05:50:17 +0000 [thread overview]
Message-ID: <20081201055017.GA21782@uranus.ravnborg.org> (raw)
In-Reply-To: <49334590.8010703@earthlink.net>
On Sun, Nov 30, 2008 at 09:01:52PM -0500, Robert Reif wrote:
> Current sparc next fails to boot (hangs at Booting Linux...).
>
> I bisected it down to this:
>
> 21cb8a43216e0595b466e903e0f2a7ae615d9e11 is first bad commit
> commit 21cb8a43216e0595b466e903e0f2a7ae615d9e11
> Author: Sam Ravnborg <sam@ravnborg.org>
> Date: Sat Nov 29 21:52:12 2008 -0800
>
> sparc: refactor Makefile
>
> The btfixup step needs knowledge of all the .o files,
> but there is no need to pass them in independent variables.
> Simplify it to use only two variables.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> :040000 040000 d5815835afa54122531d5bc8060f3831b145a1a4
> c8aad1a3c22a8243c5dd0ab2c528198d7d23af3c M arch
Hi Robert.
Thanks for testing and bisecting!
Can I ask you to send me the output of make V=1 for
your kernel before and after the above patch is applied.
It's only the last few lines that are of interest (from btfixup
and onwards).
I hope from that to say what is causing the boot regression.
Sam
next prev parent reply other threads:[~2008-12-01 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 2:01 sparc next boot failure Robert Reif
2008-12-01 5:50 ` Sam Ravnborg [this message]
2008-12-01 8:55 ` Sam Ravnborg
2008-12-01 12:41 ` Robert Reif
2008-12-01 13:15 ` Sam Ravnborg
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=20081201055017.GA21782@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.