From: Sebastian Heutling <sheutlin@gmx.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Paul Mackerras <paulus@samba.org>, Paul Janzen <pcj@linux.sez.to>,
linuxppc-embedded <linuxppc-embedded@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: Sat, 07 Jan 2006 20:55:50 +0100 [thread overview]
Message-ID: <43C01CC6.5080201@gmx.de> (raw)
In-Reply-To: <43BF42AA.8030906@secretlab.ca>
Grant Likely wrote:
> Paul Janzen wrote:
>
>>grant.likely at secretlab.ca (Grant Likely) writes:
>>
>>
>>
>>>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.
>>
>>
>>This *might* be the problem described in:
>>
>>http://ozlabs.org/pipermail/linuxppc-embedded/2006-January/021550.html
>>
>>It matches the git-bisect ID's you narrowed it down to, and it matches
>>the problem report. I'm just not sure if it matches the environment
>>you're running in.
>
>
> Yes, that's exactly it. QEMU boots prep images again with that patch.
> Thank you.
>
> g.
>
Great! :)
Sebastian
prev parent reply other threads:[~2006-01-07 20:02 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
[not found] ` <oqr77koggf.fsf@merlin.sez.to>
2006-01-07 4:25 ` Grant Likely
2006-01-07 19:55 ` Sebastian Heutling [this message]
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=43C01CC6.5080201@gmx.de \
--to=sheutlin@gmx.de \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=paulus@samba.org \
--cc=pcj@linux.sez.to \
/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).