Hi All,
I've run nfs-boot stress test (1000 iteration) with Kernel 4.8.0-rc1
it has been failed ~25 times with "Unable to handle kernel paging request at
virtual address 2244"
triggered form n_tty_receive_buf_common().
config: omap2plus_defconfig
Log is below. Any thoughts? Is it smth. known
Hi Matthijs,
On 09/10/2016 01:23 AM, Matthijs van Duin wrote:
> If you look more carefully the first problem is actually a bus error:
> [ 15.776190] Unhandled fault: external abort on non-linefetch (0x1028)
> at 0xf9e3e044
> [ 15.825925] PC is at omap_hwmod_read+0x14/0x28
> [ 15.830583] LR is at o
If you look more carefully the first problem is actually a bus error:
[ 15.776190] Unhandled fault: external abort on non-linefetch (0x1028)
at 0xf9e3e044
[ 15.825925] PC is at omap_hwmod_read+0x14/0x28
[ 15.830583] LR is at omap_rtc_wait_not_busy+0x1c/0x44
I have no idea how the kernel manages to
* Matthijs van Duin [160909 15:23]:
> If you look more carefully the first problem is actually a bus error:
> [ 15.776190] Unhandled fault: external abort on non-linefetch (0x1028)
> at 0xf9e3e044
> [ 15.825925] PC is at omap_hwmod_read+0x14/0x28
> [ 15.830583] LR is at omap_rtc_wait_not_busy+0x1c
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
* 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 h
On 10 September 2016 at 15:10, Tony Lindgren wrote:
> Yeah I don't think we have L3 interrupts working for am335x.
It probably doesn't help that the L3 interconnect registers on the
am335x aren't documented in the TRM. See below for its list of
components, target IDs, address mapping, and L3 erro
On Sat, Sep 10, 2016 at 04:46:49PM +0200, Matthijs van Duin wrote:
> It probably doesn't help that the L3 interconnect registers on the
> am335x aren't documented in the TRM. See below for its list of
> components, target IDs, address mapping, and L3 error irq routing
> (obtained by mostly-automate
8 matches
Mail list logo
