Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Rick Jones <rick.jones2@hp.com>, Matthew Wilcox <matthew@wil.cx>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Cupertino test ring problem?
Date: Wed, 30 Jul 2008 23:15:24 -0600	[thread overview]
Message-ID: <20080731051524.GC18732@colo.lackof.org> (raw)
In-Reply-To: <1217369386.6103.73.camel@localhost.localdomain>

On Tue, Jul 29, 2008 at 05:09:45PM -0500, James Bottomley wrote:
> On Tue, 2008-07-29 at 13:57 -0700, Rick Jones wrote:
> > > gsyprf11 and gsyprf10 are still not responding to pings ... could the
> > > IP routings have changed or something?
> > 
> >  > I can't connect to port 22 on any of gsyprf3, gsyprf10 or gsyprf11.
> > 
> > Well, the IP's have remained the same, but the systems are physically in 
> > a different building.  Both netperf.org and ftp.cup.hp.com have moved 
> > from the same starting point to the same end-point.  If folks cannot 
> > ping them or cannot get to port 22 on those then there is still 
> > something amis in the network.  Otherwise there is still something amis 
> > with gsyprf[3|10|11].
> 
> gsyprf10 at least is one of the ia64 boxes.  Helpfully it identifies
> itself as lp1000 or something at the login prompt.

gsyprf10 is an x86 machine (HP lp1000r netserver).

> gsyprf11 is a PA A500 type box.  It should identify as gsyprf11
> at the login prompt.  We
> only need one up and running to begin diagnosing as we should be able to
> then get to other remote consoles.

I'll check with Rick tomorrow to see when I can drop by to help resurrect
them.

I expected gsyprf10 to auto reboot on it's own.
I'll change gsyprf11 and gsyprf3 to also autoboot since I don't think they
do at the moment.

cheers,
grant

> 
> James
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-07-31  5:15 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 [this message]
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         ` Cupertino test ring problem? Matthew Wilcox
2008-08-01 23:32           ` 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=20080731051524.GC18732@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-parisc@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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