Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759802AbbLCMJt (ORCPT ); Thu, 3 Dec 2015 07:09:49 -0500 Received: from axentia.se ([87.96.186.132]:38578 "EHLO EMAIL.axentia.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756720AbbLCMJr convert rfc822-to-8bit (ORCPT ); Thu, 3 Dec 2015 07:09:47 -0500 From: Peter Rosin To: Russell King - ARM Linux CC: "'linux-arm-kernel@lists.infradead.org'" , "'linux-kernel@vger.kernel.org'" Subject: RE: Domain faults when CONFIG_CPU_SW_DOMAIN_PAN is enabled Thread-Topic: Domain faults when CONFIG_CPU_SW_DOMAIN_PAN is enabled Thread-Index: AdEtnmv+793Els3qRoSjRBiCkZdNQQABlROQAAMt1YAAA3GJ4P//8rWA///rC2A= Date: Thu, 3 Dec 2015 12:08:11 +0000 Message-ID: <533b0f1f264e42e78b94bbff9570fb50@EMAIL.axentia.se> References: <1267b061b66c4d1fa8af1955825bc97a@EMAIL.axentia.se> <20151203110041.GK8644@n2100.arm.linux.org.uk> <20151203115143.GM8644@n2100.arm.linux.org.uk> In-Reply-To: <20151203115143.GM8644@n2100.arm.linux.org.uk> Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [217.210.101.82] x-gfi-smtp-submission: 1 x-gfi-smtp-hellodomain: EMAIL.axentia.se x-gfi-smtp-remoteip: 192.168.2.5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1526 Lines: 41 Russell King wrote: > On Thu, Dec 03, 2015 at 11:38:20AM +0000, Peter Rosin wrote: > > Russell King wrote: > > > On Thu, Dec 03, 2015 at 08:33:13AM +0000, Peter Rosin wrote: > > > > I wrote: > > > > > If I enable CONFIG_CPU_SW_DOMAIN_PAN, I sometimes (but not always) get the > > > > > following (or very similar) on boot. > > > > > > > > I should have said "if I don't disable", as the option is "default y". > > > > > > > > Also, if it survives on boot, below is an example of later trouble (after > > > > 30+ minutes on this occasion). > > > > > > Please apply this patch so we (might) get a slightly better oops dump, > > > and then try to reproduce. > > > > Sure thing, but it's still "DAC: 00000051"... > > Thanks, that confirms that something in the uaccess-with-memcpy code > is clearing the DACR back to 0x51. > > This has come up several times before, and I really can't spot the > problem in this code, so I've always said to disable the > uaccess-with-memcpy code. Personally, I'd like to see the back > of that code... Ok, but it's not me doing crazy things if that's what you are implying (not saying that you are), because the sama5_defconfig has CONFIG_UACCESS_WITH_MEMCPY=y So, something needs to happen or sama5 remains default-broken. Cheers, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/