Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael S.Zick <mszick@goquest.com>
To: Thibaut VARENE <varenet@esiee.fr>,
	Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@lists.parisc-linux.org, grundler@cup.hp.com,
	Randolph Chung <randolph@tausq.org>
Subject: Re: [parisc-linux] 2.4.18-pa35 SMP process hangs on a J200
Date: Tue, 11 Jun 2002 07:10:04 -0500	[thread overview]
Message-ID: <02061107100403.00732@localhost.localdomain> (raw)
In-Reply-To: <5BA66B90-7D12-11D6-B01F-0030656F07A2@esiee.fr>

On Tuesday 11 June 2002 03:08 am, Thibaut VARENE wrote:
> Le mardi 11 juin 2002, à 07:36 , Ryan Bradetich a écrit :
> > Digging into the system a bit, here is what I found:
> >
> > 	* The setiathome process that hung (PID 326) will hang any other
> > 	  process that tries to access /proc/326/*.  (This is why top,
> > 	  ps, etc all hang after the process gets stuck).
Sirs...

I SEEM to experience a similar situation on 2.4.18-linux-x86-SMP using the 
P111-S processors (with 512K L2 cache).
Quite rare; evidently some very small window for failure.
I don't have any solid leads yet (although I have theories).

Just a note that it might not be HPPA specific.

Mike

  reply	other threads:[~2002-06-11 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11  5:36 [parisc-linux] 2.4.18-pa35 SMP process hangs on a J200 Ryan Bradetich
2002-06-11  5:52 ` Randolph Chung
2002-06-11  8:08 ` Thibaut VARENE
2002-06-11 12:10   ` Michael S.Zick [this message]
2002-06-11 14:58     ` Randolph Chung
2002-06-11 15:04       ` John David Anglin
2002-06-11 18:39       ` Michael S.Zick
2002-06-12 13:45         ` Michael S.Zick
2002-06-13 21:52           ` Grant Grundler
2002-06-14  2:05             ` Matthew Wilcox
2002-06-12 14:11         ` Matthew Wilcox
2002-06-12 10:49 ` Thibaut VARENE

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=02061107100403.00732@localhost.localdomain \
    --to=mszick@goquest.com \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.org \
    --cc=rbradetich@uswest.net \
    --cc=varenet@esiee.fr \
    /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