From: Matthew Wilcox <matthew@wil.cx>
To: Rick Jones <rick.jones2@hp.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Cupertino test ring problem?
Date: Tue, 29 Jul 2008 14:26:03 -0600 [thread overview]
Message-ID: <20080729202603.GF24924@parisc-linux.org> (raw)
In-Reply-To: <488F777E.6090405@hp.com>
On Tue, Jul 29, 2008 at 01:03:10PM -0700, Rick Jones wrote:
> A couple of the rx2600's were not powered-up, so I've powered them up.
> One of the rp34xx's does not seem "happy" and will need further
> diagnosis. If there are other things still "not right" with the ring,
> please feel free to let me know the specifics.
I can't connect to port 22 on any of gsyprf3, gsyprf10 or gsyprf11.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-07-29 20:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 14:19 Cupertino test ring problem? James Bottomley
2008-07-28 14:57 ` Matthew Wilcox
2008-07-28 17:09 ` Rick Jones
2008-07-28 17:15 ` Matthew Wilcox
2008-07-29 20:03 ` Rick Jones
2008-07-29 20:25 ` James Bottomley
2008-07-29 20:57 ` Rick Jones
2008-07-29 22:09 ` James Bottomley
2008-07-31 5:15 ` Grant Grundler
2008-07-31 17:26 ` Rick Jones
2008-08-01 23:31 ` Grant Grundler
2008-08-04 8:59 ` Thibaut VARENE
2008-08-04 15:34 ` John David Anglin
2008-08-04 15:39 ` Thibaut VARENE
2008-08-06 1:42 ` X won't start with VisEG and 2.6.22.19 John David Anglin
2008-08-06 5:11 ` Guy Martin
2008-08-14 20:54 ` Helge Deller
2008-08-14 21:24 ` John David Anglin
2008-08-15 15:09 ` Helge Deller
2008-08-23 14:49 ` John David Anglin
2008-07-29 20:26 ` Matthew Wilcox [this message]
2008-08-01 23:32 ` Cupertino test ring problem? Grant Grundler
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=20080729202603.GF24924@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-parisc@vger.kernel.org \
--cc=rick.jones2@hp.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