From: John David Anglin <dave.anglin@bell.net>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>, linux-parisc@vger.kernel.org
Subject: Re: Boot failure with 3.0.3: swapper (pid 0): Protection id trap (code 7)
Date: Tue, 06 Sep 2011 10:41:16 -0400 [thread overview]
Message-ID: <4E66310C.1050201@bell.net> (raw)
In-Reply-To: <20110906140029.GB25825@bombadil.infradead.org>
On 9/6/2011 10:00 AM, 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.
The fault was code 7. Also, I don't think this instruction is in
flush_cache_all_local
(at least I don't see it in 64-bit kernel). So, I think the problem is
in setting up the address
space map.
In my testing with 64-bit kernels, I have noticed that the first call to
flush_cache_range
doesn't have a range consistent with our 32-bit user address space.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2011-09-06 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 17:58 Boot failure with 3.0.3: swapper (pid 0): Protection id trap (code 7) Rolf Eike Beer
2011-08-31 9:54 ` Rolf Eike Beer
2011-08-31 15:48 ` Kyle McMartin
2011-08-31 16:04 ` Kyle McMartin
2011-09-01 19:13 ` Rolf Eike Beer
2011-09-02 10:30 ` Rolf Eike Beer
2011-09-06 7:40 ` Rolf Eike Beer
2011-09-06 13:46 ` Kyle McMartin
2011-09-06 14:00 ` Kyle McMartin
2011-09-06 14:15 ` James Bottomley
2011-09-06 14:20 ` Kyle McMartin
2011-09-06 15:06 ` Rolf Eike Beer
2011-09-07 8:00 ` Rolf Eike Beer
2011-10-12 7:26 ` Rolf Eike Beer
2011-10-12 13:41 ` James Bottomley
2011-10-18 15:51 ` James Bottomley
2011-10-26 13:02 ` Rolf Eike Beer
2011-10-28 15:11 ` Jeroen Roovers
2011-09-06 14:41 ` John David Anglin [this message]
2011-09-06 15:06 ` Rolf Eike Beer
2011-09-04 1:46 ` John David Anglin
2011-09-04 16:35 ` Rolf Eike Beer
2011-09-04 17:59 ` John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E66310C.1050201@bell.net \
--to=dave.anglin@bell.net \
--cc=eike-kernel@sf-tec.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.