Re: initrd fails load with "ERROR: claim of 0xfe49172 in range 0x1340000-0x10000000 failed"

[Dennis Clarke <dc@oetec.com>]

On 03/05/2018 02:12 AM, Mathieu Malaterre wrote:
> On Sun, Mar 4, 2018 at 4:11 AM, Dennis Clarke <dc@oetec.com> wrote:
> > Dear PPC types :
> >
> > So I carefully built kernel 4.15.6 and created the needed
> > initrd.img-4.15.6 in /boot with update-initramfs and checked it
> > carefully against the pre-existing initrd.img-4.13.0-1-powerpc64 for
> > Debian buster/sid.  Everything looks great and my objective was to
> > poke around the RFI flush of L1-D cache issue.  Which may exist. No
> > one really knows ( yet ):
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa8a5e0062ac940f7659394f4817c948dc8c0667
> >
> > I had to take a picture of the screen but really it seems to say that my
> > new initrd will not load into memory for some reason. Perhaps too darn
> > big? This is an old yet well loved PowerMac G5 and I am wondering if
> > there is an nvram or maybe an openfirmware command magic incantation to
> > utter?  I have 8G of memory and surely no reason to not load in a very
> > large initrd image?
>
> Maybe I am missing the whole point here. But why don't you built the
> bindeb target ?

Was not aware of it.

> (not tested):
>
> make ARCH=powerpc g5_defconfig
> make ARCH=powerpc CROSS_COMPILE=powerpc64-linux-gnu- bindeb-pkg
>
> When you dpkg -i the package, make sure the initrd / vmlinux links are
> updated (I do ln -sf manually).

Hrmmm .. well okay .. at the moment I have gotten past my initrd issues 
and am running 4.15.7 just fine.  However it is quite minimal.

nix$ cat /proc/version
Linux version 4.15.7-genunix (dclarke@nix) (gcc version 7.2.1 20171205 
(Debian 7.2.0-17)) #1 SMP Mon Mar 5 08:09:54 GMT 2018
nix$

nix$ lsmod
Module                  Size  Used by

   nothing ... nothing to be seen here :-\


nix$
nix$ ls -lap /boot/
total 322000
drwxr-xr-x  2 root root      4096 Mar  5 12:32 ./
drwxr-xr-x 23 root root      4096 Oct 22 21:04 ../
-rw-r--r--  1 root root    167163 Nov 16 21:04 config-4.13.0-1-powerpc64
-rw-r--r--  1 root root    101634 Mar  5 12:23 config-4.15.7-genunix
lrwxrwxrwx  1 root root        25 Mar  5 12:24 initrd.img -> 
initrd.img-4.15.7-genunix
-rw-r--r--  1 root root  20972026 Dec 10 20:42 initrd.img-4.13.0-1-powerpc64
-rw-r--r--  1 root root   3780671 Mar  5 12:23 initrd.img-4.15.7-genunix
lrwxrwxrwx  1 root root        29 Oct 15 04:33 initrd.img.old -> 
initrd.img-4.13.0-1-powerpc64
-rw-r--r--  1 root root   3965638 Nov 16 21:04 System.map-4.13.0-1-powerpc64
-rw-r--r--  1 root root   5322353 Mar  5 12:23 System.map-4.15.7-genunix
lrwxrwxrwx  1 root root        22 Mar  5 12:25 vmlinux -> 
vmlinux-4.15.7-genunix
-rwxr-xr-x  1 root root  19956624 Nov 16 21:04 vmlinux-4.13.0-1-powerpc64
-rw-r--r--  1 root root 275082872 Mar  5 12:23 vmlinux-4.15.7-genunix
lrwxrwxrwx  1 root root        26 Mar  4 22:16 vmlinux.old -> 
vmlinux-4.13.0-1-powerpc64
nix$


I am now going for a more complete set of modules as well as seeing if a
 large initrd really is an issue.



Dennis