linux-kernel - Re: FVP: kernel BUG at arch/arm64/kernel/traps.c:497 - Internal error: Oops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 14 Jul 2022 13:57:50 +0100
From:   Mark Rutland <mark.rutland@....com>
To:     Mark Brown <broonie@...nel.org>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>, Arnd Bergmann <arnd@...db.de>,
        Anders Roxell <anders.roxell@...aro.org>,
        Aishwarya TCV <Aishwarya.TCV@....com>
Subject: Re: FVP: kernel BUG at arch/arm64/kernel/traps.c:497 - Internal
 error: Oops - BUG: 0

On Thu, Jul 14, 2022 at 12:42:08PM +0100, Mark Brown wrote:
> On Thu, Jul 14, 2022 at 12:26:05PM +0100, Mark Rutland wrote:
> 
> > I note that your log has:
> 
> > | Hit any key to stop autoboot:  1  0 
> > | smh_open: ERROR fd -1 for file 'boot.img'
> > | smh_open: ERROR fd -1 for file 'Image'
> > | smh_open: ERROR fd -1 for file 'devtree.dtb'
> > | smh_open: ERROR fd -1 for file 'ramdisk.img'
> 
> ...
> 
> > | Hit any key to stop autoboot:  0   
> > | smh_open: ERROR fd -1 for file 'boot.img'
> > | loaded file Image from 80080000 to 82F299FF, 02EA9A00 bytes
> > | smh_open: ERROR fd -1 for file 'devtree.dtb'
> > | smh_open: ERROR fd -1 for file 'ramdisk.img'
> > | fdt - flattened device tree utility commands
> 
> > ... and I wonder if that has something to do with it, given it appears that
> > your Image is corrupted somehow.
> 
> Naresh's command line is putting Image directly into RAM with
> 
>     --data cluster0.cpu0=/tuxrun-r4_1075p-lava-1/Image@...0080000

Likewise in mine:

	--data cluster0.cpu0=/mnt/data/models/fvp/naresh/Image@...0080000

... as I'm using the same command line, just with paths altered.

Mark.