All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Fitzner <kfitzner@excelcia.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Machine hanging during high-traffic NFS
Date: Thu, 21 Jul 2005 18:29:46 -0600	[thread overview]
Message-ID: <42E03DFA.6040808@excelcia.org> (raw)
In-Reply-To: <200507212328.j6LNSfto010960@hiauly1.hia.nrc.ca>

John David Anglin wrote:

> I know that 32-bit 2.6.10 isn't stable on my c3k.  There is a known
> bug with kernel memcpy and fpregs.

Well, as far as the bug I am reporting goes, so far I have narrowed it
down to a kernel later than 2.6.10-pa11 and before 2.6.11-pa4.  It
appears that whatever went into 2.6.10 isn't to blame.

It looks like the interrupt storm theory is best.  The functions I get
from the TOC data this time are:

GRO2 0x101060e0 handle_interruption+6c
IOAQ 0x101120dc handle_unaligned+2c0

I am curious, though.  This time when it hung the hearbeat didn't stop.
 Does this mean that it didn't hang as solid as the other times?  Are
interrupts still being handled at some kernel level if the heartbeat LED
is flashing normally?  If this is the case, then this means the TOC data
may be useless this time around, right?

	Kurt.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-07-22  0:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 21:02 [parisc-linux] Machine hanging during high-traffic NFS Kurt Fitzner
2005-07-19 23:36 ` Michael S. Zick
2005-07-20  1:04 ` Kyle McMartin
2005-07-20  3:31   ` John David Anglin
2005-07-20  2:57     ` Thibaut VARENE
2005-07-20 14:56       ` Matthew Wilcox
2005-07-20  6:59   ` Kurt Fitzner
2005-07-20 16:40     ` Grant Grundler
2005-07-21  7:42       ` Kurt Fitzner
2005-07-21 12:36         ` Grant Grundler
2005-07-21 23:28           ` John David Anglin
2005-07-22  0:29             ` Kurt Fitzner [this message]
2005-07-22  3:55               ` Grant Grundler
2005-07-21 16:04         ` Kyle McMartin

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=42E03DFA.6040808@excelcia.org \
    --to=kfitzner@excelcia.org \
    --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.