From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753520AbcIJNKL (ORCPT ); Sat, 10 Sep 2016 09:10:11 -0400 Received: from muru.com ([72.249.23.125]:41895 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751873AbcIJNKI (ORCPT ); Sat, 10 Sep 2016 09:10:08 -0400 Date: Sat, 10 Sep 2016 06:10:04 -0700 From: Tony Lindgren To: Matthijs van Duin Cc: Grygorii Strashko , "linux-omap@vger.kernel.org" , linux-arm , Peter Hurley , Lokesh Vutla , lkml Subject: Re: [4.8.0-rc1] am335x-evm boot failure: n_tty_receive_buf_common: "Unable to handle kernel paging request.." Message-ID: <20160910131002.6zyzybd6kcklt6yx@atomide.com> References: <87ceb885-94a6-b9b3-60b3-2017198c4338@ti.com> <20160909234742.becrs3zb4ihc2mq6@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.2-neo (2016-07-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Matthijs van Duin [160909 16:54]: > On 10 September 2016 at 01:47, Tony Lindgren wrote: > > Yeah. Just disable omap_l3_smx/noc driver and you should see > > a proper stack trace. With the L3 driver we're seeing the trace > > for L3 error interrupt. > > Huh what, I see a proper stack trace in his post? I'm pretty sure > omap_l3_noc doesn't even support am335x currently. Oh OK sorry please ignore the post, I obviously did not look at the trace but assumed that was the case based on what I've seen. Yeah I don't think we have L3 interrupts working for am335x. Regards, Tony