On Tue, Nov 7, 2017 at 11:12 AM, Tomasz Kłoczko
On 7 November 2017 at 10:51, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> Sure, I have a PRi3 running 32 bit too but I'm not seeing it so we
> need more details. What image, what attached devices, what device the
> rootfs is on, when does it happen, when booting, when just runnning
Raw RPi3 connected over eth port.
It is fully updated rawhide image.
Lat OOPS happens just on finish boot before even I'm eble to start login
Except this OOPS it is couple of other issues or lines which looks a bit
Below is full corode dmesg output
Please trim and just include appropriate bits, really don't need a
full boot log for 6 lines...
Fragments which IMO looks a bit odd:
Why do they look odd?
[ 0.258275] dmi: Firmware registration failed.
aarch64 supports DMI, the RPi doesn't have it, how is that odd, it's a
spurious at best and can probably provide a better error message but
it doesn't stop anything from working. If you want to engage with
upstream kernel to make it better feel free!
[ 0.002542] arch_timer: WARNING: Invalid trigger for IRQ16,
[ 0.002598] arch_timer: WARNING: Please fix your firmware
[ 0.002649] arch_timer: WARNING: Invalid trigger for IRQ17, assuming
[ 0.002667] arch_timer: WARNING: Please fix your firmware
As far as I know RPi3 has no firmware ..
Yes, it does, numerous in fact, the GPU runs firmware which boots the
ARM cores, which boots u-boot (which as far as the kernel is concerned
is also a firmware), there's even a kernel driver which explicitly
communicates with the raspberry pi firmware via a mailbox mechanism:
[ 4.518103] raspberrypi-firmware soc:firmware: Attached to firmware
from 2017-09-12 15:21
Ultimately what exactly is your query about the above in relationship
to the crash that you're seeing?