Re: Aw: Re: parsic: strange boot crash on a500

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > > > Command line for kernel: 'root=/dev/sda3 console=ttyS0 
> > > > > palo_kernel=2/vmlinux'
> > > > > Selected kernel: /vmlinux from partition 2
> > > > 
> > > > I'm missing here the information of the various sections
> > > > in the vmlinux file which the boot loader usually prints
> > > > here.
> > > 
> > > Well, I did not leave anything out AFAIK?
> > 
> > It seems palo can't read the vmlinux file (aka get's confused with the contents
> > and doesn't print the ELF section list).
> > 
> > Did you maybe used a recent binutils package?
> > See:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845690
> > https://sourceware.org/ml/binutils/2016-11/msg00348.html
> > 
> > Maybe downgrading binutils helps?
> 
> Sorry, I just noticed that you are pretty aware of this bug
> (you actually opened the ticket) :-)

Yes, but I did not understand it would affect parisc, since the problem 
_seemed_ to be amd64-specific. But looking at the description, it might 
well be related.

However, I seem to have installed version 2.25.1-r1 that seems to be 
from Oct 3 2015 and thus is not likely to have this change.

There is also sys-devel/binutils-hppa64-2.25.1 that is probably used for 
the 64-bit kernel, but this is emerged Jul 6 2016 and packaged Sep 30 
2015.

In summary it seems my binutils last changed in July 2016, but 
4.8.0 kernel was compile on Oct 5 2016, with the same binutils as I am 
using now.

So, any other ideas?

-- 
Meelis Roos (mroos@xxxxxxxx)
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux