Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: parisc: flush pages through tmpalias space
Date: Wed, 29 Dec 2010 08:51:21 -0600	[thread overview]
Message-ID: <1293634281.2803.4.camel@fuzzy> (raw)
In-Reply-To: <20101229042346.GA973@hiauly1.hia.nrc.ca>

On Tue, 2010-12-28 at 23:23 -0500, John David Anglin wrote:
> On Wed, 22 Dec 2010, James Bottomley wrote:
> 
> > +		if (old_addr == 0 || (old_addr & (SHMLBA - 1)) != (addr & (SHMLBA - 1))) {
> > +			__flush_cache_page(mpnt, addr, page_to_phys(page));
> > +			if (old_addr)
> > +				printk(KERN_ERR "INEQUIVALENT ALIASES 0x%lx and 0x%lx in file %s\n", old_addr, addr, mpnt->vm_file ? mpnt->vm_file->f_path.dentry->d_name.name : "(null)");
> > +			old_addr = addr;
> >  		}
> 
> I'm seeing the above kernel error on shutdown:
> 
> Dec 26 12:30:56 mx3210 kernel: INEQUIVALENT ALIASES 0x13000 and 0x14000 in file killall5
> Dec 26 12:30:56 mx3210 kernel: INEQUIVALENT ALIASES 0x40122000 and 0x40121000 in file ld-2.11.2.so
> Dec 26 12:30:57 mx3210 kernel: INEQUIVALENT ALIASES 0x402a7000 and 0x402a6000 in file libc-2.11.2.so
> 
> This is with 2.6.36.2 and your two patches on a SMP kernel.  I've also seen
> these messages with a similar UP build in the gcc guality tests.  These
> check debug info with gdb.

Yes, I still don't know why, but fortunately the one above is the same
one I see, which only occurs when the system goes down.  I suspect
something is specifying a fixed offset for the library mappings which
violates our 4MB equivalency rule.

James



  reply	other threads:[~2010-12-29 14:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 16:22 parisc: flush pages through tmpalias space James Bottomley
2010-12-23  0:07 ` Carlos O'Donell
2010-12-23  3:04 ` John David Anglin
2010-12-25 21:52 ` Helge Deller
2010-12-29 14:49   ` James Bottomley
2010-12-29  4:23 ` John David Anglin
2010-12-29 14:51   ` James Bottomley [this message]
2010-12-30 15:56     ` John David Anglin
2010-12-30 16:09       ` John David Anglin
2011-01-01 18:31         ` John David Anglin
2011-01-01 19:00           ` John David Anglin
2011-01-05  3:49           ` John David Anglin
2011-01-05 17:37             ` Carlos O'Donell
2011-01-05 18:51               ` John David Anglin
2011-01-09 21:27               ` John David Anglin
2011-01-09 21:52 ` John David Anglin
2011-01-10 20:44   ` James Bottomley
2011-01-10 22:18     ` 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=1293634281.2803.4.camel@fuzzy \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dave.anglin@nrc-cnrc.gc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox