Re: Boot failure with 3.0.3: swapper (pid 0): Protection id trap (code 7)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2011-10-12 at 08:41 -0500, James Bottomley wrote:
> On Wed, 2011-10-12 at 09:26 +0200, Rolf Eike Beer wrote:
> > >> On Tue, Sep 06, 2011 at 09:15:07AM -0500, James Bottomley wrote:
> > >>> 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
> > >>>
> > >>
> > >> This looks promising, the second commit doesn't touch the flush_*_local,
> > >> so I think it's probably not a candidate.
> > >>
> > >> Rolf, can you revert d7dd2ff11b7fcd425aca5a875983c862d19a67ae and see
> > >> what happens?
> > >
> > > What happens is that the system boots and from a first glance seems to
> > > work fine.
> > 
> > James, are you going to revert that commit? Or am I the only one that is
> > seeing this?
> 
> You're the only one whose seeing this.  It works 32 bit on my C360, so I
> really need to know why and I don't seem to have a means to debug if
> it's C3600 only.  If I revert that commit, we start segfaulting again.

Just an update on this, I finally got my J6000 memory problems sorted
out and booted it with 3.1-rc9 32 bit, and it works fine too (SMP as
well).  That's the closest thing I have to a C3600 because it's
Astro/Elroy based, so I've no means at all of reproducing this.

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


[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux