All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: kyle@mcmartin.ca (Kyle McMartin)
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: call_init in libc6 2.3.6.ds1-11
Date: Mon, 19 Feb 2007 23:49:49 -0500 (EST)	[thread overview]
Message-ID: <200702200449.l1K4nn04019104__27377.883034251$1416624307$gmane$org@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20070219182112.GA32148@athena.road.mcmartin.ca> from "Kyle McMartin" at Feb 19, 2007 01:21:12 pm

> Keep in mind James pointed out that while he fixed the primary source of
> corruption, there still might be second-order problems...

There's always bugs...

While this might be a kernel TLB management problem, there's no strong
evidence of that and I wouldn't automatically assign the problem to the
pa8800 bug black hole.  This could just as easily be a bug in the dynamic
loader.  The system now runs for weeks with only occasional problems in
UP mode.  Will see about SMP mode.

The memory corruption is very limited and appears to occur in the
initial phase of loading libc.  It's happened twice while the echo
command tried to generate a file list building libjava.  Tens of
thousands of other applications have been launched successfully.
Probably, a lot more applications would die if memory corruption
was rampant.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2007-02-20  4:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070219182112.GA32148@athena.road.mcmartin.ca>
2007-02-19 19:22 ` [parisc-linux] Re: call_init in libc6 2.3.6.ds1-11 John David Anglin
2007-02-20  4:49 ` John David Anglin [this message]
     [not found] <119aab440702192113ta4d23d7hffde41cf0e5a614@mail.gmail.com>
2007-02-20 14:57 ` John David Anglin
     [not found] <119aab440702192022pd57d4deibd2c919cd86e1177@mail.gmail.com>
2007-02-20  4:56 ` John David Anglin
     [not found] <119aab440702191908r773a00capade2bc7ec19c4160@mail.gmail.com>
2007-02-20  4:08 ` John David Anglin
     [not found] <119aab440702190834p36f92f95ue4ded14fa5a25a5@mail.gmail.com>
2007-02-19 16:56 ` John David Anglin
     [not found] ` <200702191656.l1JGuVkq018705@hiauly1.hia.nrc.ca>
2007-02-19 18:21   ` Kyle McMartin
     [not found] <119aab440702181115y47923d8x5a2381ac8290a028@mail.gmail.com>
2007-02-19 14:49 ` John David Anglin
     [not found] <119aab440702181047x5719075ey97f0f76f939dde90@mail.gmail.com>
2007-02-18 19:07 ` John David Anglin
     [not found] <200702181445.l1IEjV7B012366@hiauly1.hia.nrc.ca>
2007-02-18 16:44 ` John David Anglin
     [not found] <200702180423.l1I4NCa8000957@hiauly1.hia.nrc.ca>
2007-02-18 14:45 ` John David Anglin
     [not found] <119aab440702171419v57a40e89i4f5baeb9702a15a@mail.gmail.com>
2007-02-18  4:23 ` John David Anglin
     [not found] <119aab440702171334w77152427s24c8317a21953518@mail.gmail.com>
2007-02-17 21:50 ` John David Anglin
     [not found] <119aab440702171237p32753949i7ade700ee405cead@mail.gmail.com>
2007-02-17 20:43 ` John David Anglin
     [not found] <no.id>
2007-02-17 20:32 ` 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='200702200449.l1K4nn04019104__27377.883034251$1416624307$gmane$org@hiauly1.hia.nrc.ca' \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=kyle@mcmartin.ca \
    --cc=parisc-linux@lists.parisc-linux.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.