Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Stuart Anderson <anderson@netsweng.com>
To: Mark E Mason <mark.e.mason@broadcom.com>
Cc: linux-mips@linux-mips.org
Subject: RE: [RFC] SMP initialization order fixes.
Date: Fri, 24 Feb 2006 15:02:50 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0602241452540.7427@localhost> (raw)
In-Reply-To: <7E000E7F06B05C49BDBB769ADAF44D077D618E@NT-SJCA-0750.brcm.ad.broadcom.com>

On Fri, 24 Feb 2006, Mark E Mason wrote:

> Hello Stuart,
>
> Um - define "hung"...

Networking stops happening. At this point, processes are still active.
Because I am using NFS root, any process that touches the filesystem
will then hang. It doesn't take too long for enough processes to touch
the FS for the system to be useless. As a test, I put a tmpfs on /tmp,
and ran sash from there. That shell would remain responsive after the
rest of the system was hung waiting on NFS.

                                  Stuart

Stuart R. Anderson                               anderson@netsweng.com
Network & Software Engineering                   http://www.netsweng.com/
1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
                                                   BD03 0A62 E534 37A7 9149

  reply	other threads:[~2006-02-24 19:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 19:43 [RFC] SMP initialization order fixes Mark E Mason
2006-02-24 20:02 ` Stuart Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-24 20:44 Mark E Mason
2006-02-25 15:28 ` Stuart Anderson
2006-02-24 18:12 Mark E Mason
2006-02-22 19:09 Ralf Baechle
2006-02-22 21:41 ` Stuart Anderson
2006-02-23 11:31   ` Ralf Baechle
2006-02-24  0:56     ` Stuart Anderson
2006-02-24  1:42   ` Martin Michlmayr
2006-02-24  1:42     ` Martin Michlmayr
2006-02-28 20:26     ` Martin Michlmayr
2006-02-23  9:52 ` Rojhalat Ibrahim
2006-02-23 11:55   ` Ralf Baechle

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=Pine.LNX.4.62.0602241452540.7427@localhost \
    --to=anderson@netsweng.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.e.mason@broadcom.com \
    /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