linux-kernel - ppc32: panic in map_page() via mpic

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 for Android: free password hash cracker in your pocket

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

Message-ID: <70A45419F481654EAC88E8122EAE3B6DB32F47F157@EX-EAST.tellabs-west.tellabsinc.net>
Date:	Tue, 24 Apr 2012 10:13:12 -0500
From:	"Morton, Jonathan" <Jonathan.Morton@...labs.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: ppc32: panic in map_page() via mpic_alloc()

We're trying to bring Linux up on a custom board based on the P2020 SoC.  We've got U-Boot and a devicetree put together, but the kernel is panicing in map_page() due to apparently finding duplicate ioremaps.  This happens quite early - the MPIC seems to be the first real device to be initialised.

I added a printk in map_page() to figure out what is going on, and there don't actually seem to be any genuine duplicates.  The last three calls are setting up the MPIC GREG, CPU and IRQ areas - the IRQ one triggers the panic.  This is presumably well-tested code given the variety of PowerPC platforms supported, so the failure is surprising.

I have already added some code to MPIC to avoid the same panic while setting up the TIMER area, which is within the mapping set up for the GREG area.  This failure is probably related to the same problem.

I've attached gzipped kernel log (extracted from RAM buffer with a BDI debugger), config and devicetree.

Any insight into what is going on, and how to make it work as designed, would be appreciated.

 - Jonathan Morton

============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================

Download attachment "config.gz" of type "application/x-gzip" (3641 bytes)

Download attachment "klog.txt.gz" of type "application/x-gzip" (2348 bytes)

Download attachment "p2020.dts.gz" of type "application/x-gzip" (1762 bytes)