linux-kernel - Re: BUG: 32 Bit Kernel kexec hangs on P2020

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:	Wed, 10 Jul 2013 12:00:12 +0200
From:	Stefani Seibold <stefani@...bold.net>
To:	"tiejun.chen" <tiejun.chen@...driver.com>
Cc:	linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	kexec@...ts.infradead.org
Subject: Re: BUG: 32 Bit Kernel kexec hangs on P2020

Am Mittwoch, den 10.07.2013, 16:48 +0800 schrieb tiejun.chen:
> On 07/10/2013 04:39 PM, Stefani Seibold wrote:
> > Hi,
> >
> > i have tried to kexec a 32 bit kernel on a Freescale P2020 dual core CPU
> > (e500v2, revison 5.1 - pvr 8021 1051), but Kexec will hang after the
> > "Bye!".
> >
> > The host and the kexec kernel are the same, based on the current kernel
> > version 3.10.
> >
> > I have tried it with kexec-tools 2.0.4.git released 30 June 2013.
> >
> > Invoking kexec with
> >
> > kexec --command-line "1 maxcpus=1 noirqdistrib reset_devices $(cat /proc/cmdline)" -t elf-ppc --dtb=rs2020.dtb \
> > --reuse-node="/cpus/PowerPC,P2020@...imebase-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...us-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...lock-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...ext-level-cache" \
> > --reuse-node="/cpus/PowerPC,P2020@...imebase-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...us-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...lock-frequency" \
> > --reuse-node="/cpus/PowerPC,P2020@...ext-level-cache" \
> > --reuse-node="/cpus/PowerPC,P2020@...pu-release-addr" \
> > --reuse-node="/cpus/PowerPC,P2020@...nable-method" \
> > --reuse-node="/soc@...00000/bus-frequency" \
> > --reuse-node="/soc@...00000/serial@...0/clock-frequency" \
> > --reuse-node="/soc@...00000/ethernet@...00/local-mac-address" \
> > -d -l -x vmlinux
> > kexec -e
> 
> Could you try again with one simple command like,
> 
> kexec -l vmlinux --append="`cat /proc/cmdline`";kexec -e
> 

Great, this works.

I did more test and the issue for the fail is the passing of the device
tree. But the device tree is exact the same as the previous used one.

Is passing a new device tree not allowed?

Stefani


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/