On Tue, 2011-09-06 at 10:00 -0400, Kyle McMartin wrote:
> On Tue, Sep 06, 2011 at 09:46:11AM -0400, Kyle McMartin wrote:
> > > >> I suspect bootmem changes have broken somewhere on 32-bit... try
> > > >> inserting a few printk between each of the function calls at the start
> > > >> of paging_init to try to narrow down exactly where it fails.
> > > >
> > > > It's flush_cache_all_local() that fails.
> > >
> > > 2.6.39.4 works.
> > >
> >
> > Well... that's weird.
> >
> 0: 43 ff ff 40 ldb 7fa0(r31),r31
>
> Is the faulting insn, and %r31 is 00000000... so
> we're looking at 32672, which looks suspiciously like
> a negative offset from 32768.
>
> Looks like it's a null pointer dereference, there shouldn't be anything
> useful at this address, if I remember our address space map correctly.
It's possible that one of the flushing patches is to blame; I just can't
see how. Most likely is
commit d7dd2ff11b7fcd425aca5a875983c862d19a67ae
Author: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu Apr 14 18:25:21 2011 -0500
[PARISC] only make executable areas executable
Least likely:
commit b7d45818444a31948cfc7849136013a0ea54b2fb
Author: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri Apr 15 12:37:22 2011 -0500
[PARISC] prevent speculative re-read on cache flush
James
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
