All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Sun4d SMP - retests - patch was not required
Date: Thu, 19 Aug 2004 23:09:23 +0000	[thread overview]
Message-ID: <20040819230923.GF11200@holomorphy.com> (raw)
In-Reply-To: <200408192322.43126.crn@netunix.com>

On Thursday 19 August 2004 11:28 pm, William Lee Irwin III wrote:
>> Yes, though we're really going to have to do more intense diagnostics
>> (targeted printk'ing out of various bits of state etc.) to discover
>> what's really happening with interrupts. Checking detailed dumps of
>> interrupt routing state etc. vs. 2.2.x sound like a good first shot.

On Fri, Aug 20, 2004 at 12:04:52AM +0100, C.Newport wrote:
> Just send me the tests and I will run them.
> Comparisons with 2.2 will not help, there was no SMP capable version.
> I will give 2.4.27 UP a good thrashing tomorrow - any instability there 
> might give us some more clues.

These aren't tests per se, they're C code to print out extra
information. This generally needs to be done by hand and with some
insight into what you're looking at so as to find the relevant things
to print. With no extant working SMP sun4d kernel there's nothing to
really compare against, so I think we're going to have to do something
else here anyway, though some similar information may be useful for it.


-- wli

  parent reply	other threads:[~2004-08-19 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 22:22 Sun4d SMP - retests - patch was not required C.Newport
2004-08-19 22:28 ` William Lee Irwin III
2004-08-19 23:04 ` C.Newport
2004-08-19 23:09 ` William Lee Irwin III [this message]
2004-08-19 23:46 ` C.Newport

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=20040819230923.GF11200@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@vger.kernel.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.