All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] PA8800/ZX1 support committed to 2.6.7-rc2-pa2
Date: Fri, 11 Jun 2004 09:27:13 -0600	[thread overview]
Message-ID: <20040611152713.GC10279@colo.lackof.org> (raw)
In-Reply-To: <1086962549.1949.23.camel@mulgrave>

On Fri, Jun 11, 2004 at 10:02:29AM -0400, James Bottomley wrote:
> Could you just hard code it to 32 to make assureances certain that the
> stride value isn't the source of the segv's?

stride=16 doesn't work either.
sshd only page faults (so far) and sometimes "hangs" (^C to kill it).
Out of 9 attempts, I get one hang and 4 page faults.
"Connection closed" on all except the "hang".

Using console, I can
o apt-get update
o apt-get upgrade
o ssh -l grundler 192.168.1.1

So far, everything from the console works.
I'm not sure why sshd is having such a hard time.
I still don't think "stride" is the problem.

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

  parent reply	other threads:[~2004-06-11 15:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 20:25 [parisc-linux] PA8800/ZX1 support committed to 2.6.7-rc2-pa2 Grant Grundler
2004-06-05  6:51 ` Grant Grundler
2004-06-05 14:10   ` James Bottomley
2004-06-05 21:05     ` Grant Grundler
2004-06-05 21:19       ` James Bottomley
2004-06-05 22:21         ` Grant Grundler
2004-06-11  5:58         ` Grant Grundler
2004-06-11 14:02           ` James Bottomley
2004-06-11 15:03             ` Grant Grundler
2004-06-11 15:27             ` Grant Grundler [this message]
2004-06-12  0:38           ` Jim Hull
2004-06-14 18:29             ` Grant Grundler
2004-06-14 22:45               ` Jim Hull
2004-06-14 23:42                 ` 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=20040611152713.GC10279@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=James.Bottomley@steeleye.com \
    --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.