All of lore.kernel.org
 help / color / mirror / Atom feed
From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: 2.6.6 lockup
Date: Wed, 26 May 2004 14:11:16 -0700	[thread overview]
Message-ID: <20040526211115.GI6931@polop.usc.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Hi all again,
   After fixing up the failover issues, I got my pair of Itaniums into
production with 2.6.5 and as soon as the real world load went up, the machines
started freezing.  No net response, no console, only sysreq keys work.

   I updated to 2.6.6 and it doesn't freeze up as often, but it's still really
bad, at least a few times a day.  Unfortunately, I can't seem to figure out how
to get a decent kernel trace.  Apperently sysreq-Crash doesn't work in ia64.
And NMI watchdog doesn't work on ia.  And I can't find any info on a hardware
watchdog on the mobo!

I do have some other info from sysreq on the cpu regs, memory, and processes if
anyone would find that interesting.

The work load freezes up the machines under heavy streaming writes from about a
100 processes on at least 60 clients.  A combined load of about 80GB/hour is
enough to freeze up the machine pretty regularly.

I tried Trond's 2.6.6 patches at his website, but those brokes things
considerably.  Since I don't have any actual Oops messages, anyone have any
experimental deadlock-fixing patches they want me to test? :)

-- 
Garrick Staples, Linux/HPCC Administrator
University of Southern California

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-05-26 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 21:11 Garrick Staples [this message]
2004-05-26 21:37 ` 2.6.6 lockupy J. Bruce Fields
2004-05-26 21:44   ` Garrick Staples
2004-05-26 21:55     ` J. Bruce Fields
2004-05-26 22:26       ` Garrick Staples
2004-05-27  4:39       ` Garrick Staples

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=20040526211115.GI6931@polop.usc.edu \
    --to=garrick@usc.edu \
    --cc=nfs@lists.sourceforge.net \
    /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.