From: Tony Breeds <tony@bakeyournoodle•com>
To: Christian Kujau <lists@nerdbynature•de>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: 3.5+: yaboot, Invalid memory access
Date: Wed, 1 Aug 2012 12:02:47 +1000 [thread overview]
Message-ID: <20120801020245.GC6467@thor.bakeyournoodle.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1207302235170.26923@trent.utfs.org>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Mon, Jul 30, 2012 at 10:46:39PM -0700, Christian Kujau wrote:
> Hi,
>
> when trying to upgrade from 3.5 (final) to today's git checkout from
> Linus' tree, yaboot cannot boot and the following is printed:
>
> [...]
> returning from prom_init
> Invalid memory access at %SRR0: 00c62fd4 %SRR1: 00003030
>
> The whole message: http://nerdbynature.de/bits/3.5.0/yaboot/
>
> The Yaboot version is 1.3.16 (from Debian/testing), I haven't tried 1.3.17
> yet, its changelog does not say anything about "newer kernel support" so
> I'm not sure if this would help here.
Well the "returning from prom_init" message is from the kernel so yaboot
has done something. We'll work out if it was the right thing ;P
I had a look at the URL you provided.
1) can you also upload you vmlinux so we can poke at it.
2) What is the dmseg.txt file there? If you're unable to boot 3.5 how
did you get the dmesg?
Yours Tony
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-01 2:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 5:46 3.5+: yaboot, Invalid memory access Christian Kujau
2012-08-01 2:02 ` Tony Breeds [this message]
2012-08-01 7:30 ` Christian Kujau
2012-09-04 6:18 ` Christian Kujau
2012-09-04 6:51 ` Michael Ellerman
2012-09-04 9:32 ` Christian Kujau
2012-09-05 1:08 ` Benjamin Herrenschmidt
2012-09-05 5:25 ` Christian Kujau
2012-09-05 5:29 ` Benjamin Herrenschmidt
2012-09-04 14:27 ` Steven Rostedt
2012-09-04 19:49 ` Benjamin Herrenschmidt
2012-09-04 19:40 ` Benjamin Herrenschmidt
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=20120801020245.GC6467@thor.bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=lists@nerdbynature$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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