From: Grant Likely <grant.likely@secretlab.ca>
To: Sebastian Heutling <sheutlin@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
Date: Thu, 05 Jan 2006 09:04:48 -0700 [thread overview]
Message-ID: <43BD43A0.5060509@secretlab.ca> (raw)
In-Reply-To: <43BCFA15.5070304@gmx.de>
Sebastian Heutling wrote:
> Hi Sven,
>
> Before trying to build a kernel myself I tried the debian linux binary
> image. An image for powerpc is not there yet so I used rc7. I netbooted
> "/boot/vmlinuz-2.6.15-rc7-powerpc" and the result was that I got a lot
> of output saying that there is something wrong. I assume the output was
> from the firmware because the kernel usually doesn't report an endless
> list of errors saying something about "stack exception" every now and
> then and mostly printing zeros followed by a new line character.
Have you tried 2.6.14? I'm having a similar issue with PReP images
using QEMU. 2.6.14 works, but 2.6.15 is busted. It *might* be the same
issue.
http://ozlabs.org/pipermail/linuxppc-dev/2005-December/020782.html
I was able to use git-bisect to narrow it down to 20 or so changes, but
I didn't get any farther.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
next prev parent reply other threads:[~2006-01-05 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EtnU9-0008HI-I0@spohr.debian.org>
[not found] ` <20051230171705.32043.38767.reportbug@sengor.ath.cx>
[not found] ` <handler.345424.D345424.113629990832428.notifdone@bugs.debian.org>
2006-01-05 10:51 ` How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1) Sebastian Heutling
2006-01-05 11:05 ` Sven Luther
2006-01-05 12:59 ` Sebastian Heutling
2006-01-05 16:04 ` Grant Likely [this message]
[not found] ` <oqr77koggf.fsf@merlin.sez.to>
2006-01-07 4:25 ` Grant Likely
2006-01-07 19:55 ` Sebastian Heutling
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=43BD43A0.5060509@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=sheutlin@gmx.de \
/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).